EXOR Structures Manager Admin Guide - Bentley · PDF fileEXOR STRUCTURES MANAGER ADMIN GUIDE DOCUMENT TRACKER Version: 4.7 ii CONFIDENTIALITY STATEMENT The contents of this

EXOR

Structures Manager Admin Guide

February 2014

Version: 4.7

Submitted by:

Bentley Systems (UK) Ltd.,

9th Floor,

20 Gracechurch Street,

London

EC3V 0BG

EXOR

STRUCTURES MANAGER ADMIN GUIDE

DOCUMENT TRACKER

Version: 4.7 i

CONFIDENTIALITY STATEMENT

The contents of this document, including system ideas and concepts, are confidential and proprietary in nature and are not to be distributed in any form without the prior written consent of Bentley, Inc.

EXOR Structures Manager Admin Guide

Trademark

Bentley and the "B" Bentley logo are either registered or unregistered trademarks or service marks of

Bentley Systems, Incorporated, or one of its direct or indirect wholly-owned subsidiaries.

Other brands and product names are trademarks of their respective owners.

Copyright

Copyright © 2013 Bentley Systems, Incorporated.

All Rights Reserved.

Including software, file formats, and audiovisual displays; may only be used pursuant to applicable

software license agreement; contains confidential and proprietary information of Bentley Systems,

Incorporated and/or third parties which is protected by copyright and trade secret law and may not be

provided or otherwise made available without proper authorization.

Restricted Rights Legend

If this software is acquired for or on behalf of the United States of America, its agencies and/or

instrumentalities ("U.S. Government"), it is provided with restricted rights. This software and

accompanying documentation are "commercial computer software" and "commercial computer software

documentation", respectively, pursuant to 48 C.F.R. 12.212 and 227.7202, and "restricted computer

software" pursuant to 48 C.F.R. 52.227-19(a), as applicable. Use, modification, reproduction, release,

performance, display or disclosure of this software and accompanying documentation by the U.S.

Government are subject to restrictions as set forth in this Agreement and pursuant to 48 C.F.R. 12.212,

52.227-19, 227.7202, and 1852.227-86, as applicable.

Contractor/Manufacturer is Bentley Systems, Incorporated, 685 Stockton Drive, Exton, PA 19341-0678.

Unpublished - rights reserved under the Copyright Laws of the United States and International treaties.

EXOR


DOCUMENT TRACKER

Version: 4.7 ii



Document Tracker

Document Details

File:

Structures Manager Admin Guide V4.7.docx

Prepared by:

I Skinner

Manual Name:

Structures Manager Admin Guide

Reviewed by:

Version:

1.0

Approved for issue by:

T. C. Stewart

Date of Issue:

Feb 2014

Product Manager:

I. Skinner

File Name:

Document Centre/Exor/Product Manuals/4.7 Product Manuals/4.7 completed documentation/ Structures Manager Admin Guide V4.7.docx

Document Version Control

Revision Date By Chapter/Page Description

1 21 Oct 2009 AH All Upgrade to version 4.1

2 20 Aug 2010 IS All Upgrade to Version 4.3

Update product options STRINSCOMB

STRSHOWDAT

3 May 2011 IS None No changes for 4.4

4 Nov 2011 IS None No changes for 4.5

5 Oct 2012 IS All Document reviewed for 4.6 release

6 Feb 2014 BA/IS All Re-formatted into Bentley template for 4.7 release

EXOR


TABLE OF CONTENTS

Version: 4.7 iii



Table of Contents

1 Core Reference Data ............................................................................................................................. 1

1.1 Product Options – HIG9130 ......................................................................................................... 2

1.1.1 General Information .............................................................................................................. 3

1.1.2 Product Options..................................................................................................................... 4

2 Inventory Reference Data ..................................................................................................................... 5

2.1 Prerequisites .................................................................................................................................. 5

2.2 General Information ...................................................................................................................... 5

2.2.1 Flow Diagram of Structure Maintenance Process ................................................................. 6

2.2.2 Flow Diagram of Structure Inspections Reference Data Setup ............................................. 7

2.2.3 Flow Diagram of Structure Inspection Process ..................................................................... 8

2.3 Attribute Domains – STR2010 ..................................................................................................... 9

2.3.1 General Information .............................................................................................................. 9

2.3.2 Attribute Domains ............................................................................................................... 10

2.3.3 Values ................................................................................................................................. 10

2.4 Attribute Types – STR2020 ........................................................................................................ 11

2.4.1 General Information ............................................................................................................ 11

2.4.2 Attribute Types ................................................................................................................... 12

2.5 Structure Item Types – STR2030 ................................................................................................ 14


2.5.2 Structure Item Type ............................................................................................................ 15

2.5.3 Valid Attributes ................................................................................................................... 15

2.5.4 Hierarchy Parents ................................................................................................................ 17

2.6 Attribute Groups – STR2024 ...................................................................................................... 18


2.6.2 Attribute Groups ................................................................................................................. 19

2.6.3 Attribute Group Membership .............................................................................................. 19

2.6.4 Attribute Group Permissions ............................................................................................... 20

2.7 Templates – STR2040 ................................................................................................................. 21


2.7.2 Template ............................................................................................................................. 22

2.7.3 Hierarchy ............................................................................................................................. 22

2.8 Obstruction Types – STR2050 .................................................................................................... 23


2.8.2 Obstruction Types ............................................................................................................... 24

3 Inspection Reference Data .................................................................................................................. 26

3.1 Inspection Sets – STR2068 ......................................................................................................... 27

EXOR


TABLE OF CONTENTS

Version: 4.7 iv




3.1.2 Inspection Sets .................................................................................................................... 28

3.1.3 Inspection Types ................................................................................................................. 28

3.2 Inspection Types – STR2060 ...................................................................................................... 29


3.2.2 Selection Criteria................................................................................................................. 30

3.2.3 Valid Structural Inspections ................................................................................................ 30

3.2.4 Inspectable Components ..................................................................................................... 31

3.2.5 Inspectable Attributes ......................................................................................................... 32

3.3 Inspection Cycles – STR2062 ..................................................................................................... 33


3.3.2 Inspection Cycles ................................................................................................................ 34

3.4 Inspection Equipment – STR2064 .............................................................................................. 35


3.4.2 Inspection Equipment ......................................................................................................... 36

3.5 Organisations – STR2070 ........................................................................................................... 37


3.5.2 Organisations ...................................................................................................................... 38

3.6 BCI Reference Data – STR3002 ................................................................................................. 40


3.6.2 Bridge Condition Reference Data ....................................................................................... 40

3.6.3 Element Condition Score Data ............................................................................................ 41

3.6.4 Type Rules .......................................................................................................................... 42

3.6.5 Element Importance Factors ............................................................................................... 43

3.6.6 Copy Selected Ruleset ........................................................................................................ 45

3.6.7 Type Combinations ............................................................................................................. 46

3.6.8 Importance Weightings ....................................................................................................... 47

3.7 Defect Code Maintenance – STR3003 ........................................................................................ 48


3.7.2 Defect Codes ....................................................................................................................... 49

3.7.3 Copy Defect Set .................................................................................................................. 50

4 Structures Reference Data Reports ..................................................................................................... 51

4.1.1 Running Reports ................................................................................................................. 52

4.2 List of Attribute Domains – STR5004 ........................................................................................ 53



4.3 List of Attribute Types – STR5005 ............................................................................................. 56

4.4 List of Item Types – STR5006 .................................................................................................... 57

EXOR


TABLE OF CONTENTS

Version: 4.7 v




4.5 List of Attribute Groups – STR5007 ........................................................................................... 58


4.6 List of Valid Item/Attributes – STR5008 ................................................................................... 59


4.7 List of Valid Item/Inspections – STR5009 ................................................................................. 60


5 Bulk Data Loading .............................................................................................................................. 61

5.1.1 Prerequisites ........................................................................................................................ 61

5.1.2 Structure Locking ................................................................................................................ 61

5.1.3 Flow Diagram of Structures Inspection Process ................................................................. 63

5.2 Inspecting with a Data Capture Device ....................................................................................... 64


5.3 Manual Inspections ..................................................................................................................... 64


5.4 Download Control Data – STR1001 ........................................................................................... 64


5.5 Download Inspection Parameters – STR1002 ............................................................................ 65



5.6 Upload Inspection Details – STR1003 ........................................................................................ 66



5.7 Load Structure Inventory onto Database – STR1004 ................................................................. 67


5.7.2 Bulk Structure Loading Flow Diagram ............................................................................... 67

5.7.3 Discard File ......................................................................................................................... 67

5.7.4 Error Message File .............................................................................................................. 67

5.7.5 Structures Inventory Loader File Specification .................................................................. 68

5.7.6 File Format .......................................................................................................................... 68

5.7.7 Validation Rules .................................................................................................................. 69

5.7.8 Structure Header Record – Type 01 .................................................................................... 69

5.7.9 Network Intersection – Type 02 .......................................................................................... 70

5.7.10 Structure Header Record – Type 04 .................................................................................... 71

5.7.11 Component Detail – Type 05 .............................................................................................. 72

5.7.12 Component Attribute Detail – Type 07 ............................................................................... 73

5.7.13 Loading the File .................................................................................................................. 73

5.7.14 Example Load File .............................................................................................................. 74

EXOR


TABLE OF CONTENTS

Version: 4.7 vi



EXOR


CORE REFERENCE DATA

Version: 4.7 1



1 Core Reference Data

This chapter describes the forms used for maintaining the reference data and assigning attributes to specific items of the

Structures by Exor database.

They are the following options:

Product Options –STR2010

The form descriptions provide you with detailed information about reference data in Structures by Exor, including:

an overall description of the form

a detailed explanation of each field, including available features (such as List of Values, default values and other

characteristics)

helpful information for using the form or report

EXOR


CORE REFERENCE DATA

Version: 4.7 2



1.1 Product Options – HIG9130

Figure 1 – Product Options Menu Option

Figure 2 – Product Options

EXOR


CORE REFERENCE DATA

Version: 4.7 3



1.1.1 General Information

Product Options allow ‘switches’ or default values to be set, which defines how certain functionality operates within the

Exor suite of Products. The following Structure Manager related Product Options should be set to suit your

organisational requirements. Product Options are set using Product Options – HIG9130.

The values for Product Options are normally defined during Product Implementation or Upgrade and should not be

amended without consultation with Exor support staff.

Product Options values are maintained using Product Options – HIG9130.

The Product Options themselves are 'registered' and defined using Product Option List – HIG9135.

Several Product Options may have a User Option of the same name. The Product Option will act as the default settings.

The system will check for the existence of a User Option value that will take precedence over the Product Option value. If

no User Option value has been defined for the User the Product Option value will be used. Product Options that also have

an accompanying User Option are marked with an Asterisk (*) below.

EXOR


CORE REFERENCE DATA

Version: 4.7 4



1.1.2 Product Options

The following Product Options must be defined in Product Options – HIG9130 to ensure that your system meets your

requirements.

Warning! Product options are set up during installation and should not be changed without first consulting with Exor

support staff.

Product Option Id Option Name Sample Value Usage Remarks

STR DECK_AREA Deck Area Attribute Value

AREA This option is used to define which attribute value is used to define Deck Area.

This option is not used in version 4.1

STR STRDATMASK STR Date Attribute Mask

DD/MM/YY This option is used to define the date mask to be used for Structure attributes of type DATE.

STR STRDELSTRS Delete Structures

Y This option is used to determine whether structures are deleted or closed when using form Delete Structures – STR3030.

If set to Y structures will be deleted.

If set to N structures will be end dated (closed).

STR STRINSCOMB Use Insp Detail combination

N Refer to BD63/07

http://www.standardsforhighways.co.uk/dmrb/vol3/section1/bd6307.pdf

If set to Y the system will enforce inspection combinations based on BD63/07

This has been edited to include a missing combination for D4 combination in line with support log 720841.

STR STRSHOWDAT Show Start and End Dates

N This option is used to determine whether the start and end dates are displayed in form Structure Inventory – STR3020.

If set to Y the dates will be displayed in the main window.

If set to N the dates will be displayed in the expansion block.

NOTE: From version 4.3 this product option is no longer required as the start/end dates have now been incorporated back into the main STR3020 form

EXOR


INVENTORY REFERENCE DATA

Version: 4.7 5



2 Inventory Reference Data


structures by Exor database.


Attribute Domains – STR2010

Attribute Types – STR2020

Attribute Groups – STR2024

Structure Item Types – STR2030

Templates – STR2040

Obstruction Types – STR2050

The form descriptions provide you with detailed information about reference data in structures by Exor, including:



characteristics)


2.1 Prerequisites

Before starting to load the attribute values into structures by Exor you should check that both the installation of Oracle

and structures by Exor has been successful.

2.2 General Information

The following diagrams are used to indicate the order in which certain processes should be carried out when using

Structures by Exor. They also indicate which processes are optional or required.

EXOR



Version: 4.7 6



2.2.1 Flow Diagram of Structure Maintenance Process

Figure 3

EXOR



Version: 4.7 7



2.2.2 Flow Diagram of Structure Inspections Reference Data Setup

Figure 4

EXOR



Version: 4.7 8



2.2.3 Flow Diagram of Structure Inspection Process

Figure 5

EXOR



Version: 4.7 9



2.3 Attribute Domains – STR2010

Figure 6 – Attribute Domains Menu Option

Figure 7 – Attribute Domains


Use this form to maintain the lists of values used by selected attributes. The list of values is associated to an attribute

using Attribute Control Data – STR2020.

EXOR



Version: 4.7 10



2.3.2 Attribute Domains

This window is used to create new, delete or change existing lists of values.

When you enter this window, the cursor sits in the List Name field waiting for you to enter your new data. Press [Execute

Query] to obtain existing information.

List Name (Required)

You must enter a unique name for the list of values.

Screen Title (Required)

Enter a description of the list of values

2.3.3 Values

The content of the selected list is maintained here.

Seq No. (Required)

This is sequence number and is used to order the display of the attribute values. This would be used frequently because

the most commonly used attributes could be forced to the top of the listing.

Value (Required)

A unique value code corresponding to the attribute type must be entered.

Meaning (Required) List

An explanation of the value code must be entered.

Start Date (Optional)

Enter the date from which this value is to be used.

End Date (Optional)

If the value is no longer required, enter the end date.

EXOR



Version: 4.7 11



2.4 Attribute Types – STR2020

Figure 8 – Attribute Types Menu Option

Figure 9 – Attribute Types


This form is used for the maintenance of attribute type definitions and to determine the characteristics of attributes that

can be associated with a structure item.

EXOR



Version: 4.7 12



A standard set of attributes is supplied with the system. Any new attributes required are entered here. Once entered they

will be associated to a structure item using Structure Item Types – STR2030.

2.4.2 Attribute Types

Attribute types inserted, updated or deleted here, an attribute cannot be deleted if it has been used against a structure and

has an associated value.

Attribute Code (Required)

Enter up to four characters for an attribute code. For new attributes this value must be unique.

Attribute Name (Required)

An attribute name must be entered which more fully describes the attribute code.

Validation (Y/N) (Required, Default)

This field is used when you require attributes to be validated against specific criteria.

If ‘Y’ is selected, you will be prompted for a data type. If ‘N’ is selected, you will go the description field. The default

value is ‘Y’.

Data Type (Required)

This field will associate a set of attribute values with an attribute code. Valid values are CHAR, LIST, INT, NUM and

DATE. If CHAR is entered then Length is prompted. If LIST is entered then Length/List of Values is prompted. If INT is

entered then Maximum/Minimum are prompted. If NUM is entered then Decimal Places/Maximum/Minimum are

prompted and if DATE is entered the cursor moves to the Description field.

Length (Required)

If CHAR is entered the length of the character field should be specified.

List of Values (Required) List

This field specifies which List of Values is used for this attribute. This list must exist and is created using Attribute

Domains – STR2010.

Decimal Places (Optional)

If NUM is entered then you can specify the number of decimal places.

Minimum Value (Optional)

A minimum numeric value can be entered for the attribute.

Maximum Value (Optional)

A maximum numeric value can be entered for the attribute.

Description (Optional) Edit

A description of the attribute may be entered.

EXOR



Version: 4.7 13



Govt Ref (Optional)

Enter the Government Reference number for this attribute.



End Date (Optional)


EXOR



Version: 4.7 14



2.5 Structure Item Types – STR2030

Figure 10 – Structure Item Types Menu Option

Figure 11 – Structure Item Types


This form is used to maintain and associate a set of attributes with selected item types.

You will be supplied with a default set of structure items with associated attributes that can be modified to suit your

individual requirements. There are also times that you will be required to inspect a structure that is owned by another

organisation, e.g., railway bridge over a road. If this is the case you may only want to hold a limited number of attributes

EXOR



Version: 4.7 15



against that structure. This will require that you set up a new item as type of, for example, RBRI with a restricted set of

attributes.

2.5.2 Structure Item Type

Item types that will appear within structures can be inserted, updated and deleted here. Items that have been used and have

associated attributes with values cannot be deleted.

Item Type Code (Required)

Enter a unique four-character item type code.

Level Number (Required)

Enter the level number of the item type within the structure. This provides a sort of validation when creating a structure,

preventing the creation of invalid structures, i.e., you can create a structure that consists of two level 1 items following

each other in the hierarchy, but you cannot create a structure with a level 1 item following a level 3 item.

The Hierarchy Parents tab shown the parents of this item within the structure hierarchy.

Item Type Name (Required)

A unique name for the item type must be entered.

Enforce Hierarchy (Required, checkbox)

Check this box to enforce the structure hierarchy.


A description of the item type may be entered.



End Date (Optional)


Govt Ref. (Optional)

A government reference number can be entered.

2.5.3 Valid Attributes

Insert, update and delete attributes for the selected item type.

Seq No (Required)

A sequence number must be entered to order the display of the attributes. This order can be changed to force commonly

used attributes to the top of the display.

EXOR



Version: 4.7 16



Code (Required) List

A valid attribute code must be entered. These would have been entered previously using Attribute Types – STR2020.

Attribute Name (Display Only)

The attribute name associated with the attribute code will be displayed.

Data Type (Display Only)

The associated data type will be displayed in this field.

Length (Display Only)

The length of the attribute field will be displayed here.



End Date (Optional)


Required (Required, Checkbox)

Check this box to indicate whether the attribute has to have a mandatory value.

EXOR



Version: 4.7 17



Figure 12 – Hierarchy Parents

2.5.4 Hierarchy Parents

This tab will display the parent elements within the structure hierarchy for the selected element.

EXOR



Version: 4.7 18



2.6 Attribute Groups – STR2024

Figure 13 – Attribute Groups Menu Option

Figure 14 – Attribute Groups

EXOR



Version: 4.7 19




This form is used to allocate any set of attribute to a group, with a view of updating those attributes together at a later

date. This allows some security within the system, as only certain users will have the ability to update certain sets of

attributes. This is useful if you wish to restrict contractors access to certain attributes.

2.6.2 Attribute Groups

When you enter this window, the cursor sits in the Attribute Gp Name field waiting for you to enter details of a new

group. To retrieve details of existing groups press [Enter Query], enter your selection criteria followed by [Execute

Query].

Attribute Gp Name (Required)

Enter the name of the Attribute Group.

Attribute Gp Usage (Required) Edit

Enter full details of the use of this attribute group.

Structure Type (Required) List

Enter the structure type to which this attribute group will be associated. A description will be displayed in the adjacent

field.

2.6.3 Attribute Group Membership

Enter the associated attributes that will be contained within this group.

Seq (Required, Default)

The system will automatically generate a unique sequence number.

Item (Required) List

Enter a valid item code.

Item Type (Display Only)

A description of the selected item will be displayed.

Attr. (Required) List

Enter a valid attribute code for the selected item.

Attribute Name (Display Only)

A description of the selected attribute will be displayed.

EXOR



Version: 4.7 20



Figure 15 – Attribute Group Permissions

2.6.4 Attribute Group Permissions

This window is used to associate either Read or Update permissions to individual users. This will be used when updating

attributes using Structure Attributes – STR3024.

Initials (Required) List

Enter the initials of the selected user. The users initials must have been previously entered by the system administrator

with the module Users – HIG1832.

Name (Display Only)

The full name of the user will be displayed.

Permission (Required)

Enter the user’s permission for the selected attributes. Enter ‘R’ for Read Only Access or ‘U’ for Update.

EXOR



Version: 4.7 21



2.7 Templates – STR2040

Figure 16 – Templates Menu Option

Figure 17 - Templates


The majority of typical highway structures can be built from a small number of templates.

This form is used to maintain these template definitions which are used to speed up the process of building new structures.

Templates are used in Create Structures from a Template – STR3010.

EXOR



Version: 4.7 22



Note: The [Copy Structure] button in Maintain Structures Hierarchy and Attributes – STR3020 may also be used

to create new structures from an existing structure. The advantage of using this is that it will copy the complete

structure including attribute values etc.

2.7.2 Template

When you enter this window, the cursor sits in the Type field waiting for you to enter a new template or select [Enter

Query], enter your selection criteria followed by [Execute Query] to obtain existing data.

Type (Required) List

Enter the type of structure that is to be used for the template.

Template Name (Required)

Enter the name of the template.

Description (Optional)

Enter a description of the template.

2.7.3 Hierarchy

The template hierarchy is defined here. The chevrons (>) preceding each item in the hierarchy indicate the level of that

item in the hierarchy. When inserting new items into the hierarchy, the chevrons should not be entered.

Structures by Exor will display the chevrons depending on the item type and its level within the hierarchy.

Type (Required)

This field must contain a valid pre-defined item type that conforms to the hierarchy conditions set up using the Level

Number field in Structure Item Types – STR2030.

When entering the item types there is a parent/child condition in operation, e.g., a bridge may be a parent of the children

span1, span2 and span3. Span1 may, in turn, be a parent of the children joint1 and bearing1. You must use the sequence

number to order the display of the children within the parent hierarchy. Since all the items except the first, are children of

a parent, the order of the complete hierarchy can be controlled. To create a child of a parent, position the cursor on the

intended parent, press [Insert Record] and enter the child. Notice the chevrons, indicating the level in the hierarchy.

Item Name (Required, Default)

This field will display a default value. This name should be changed to make more sense of the structures hierarchy, e.g.,

bearing span 1.

Seq. (Required)

You must enter a sequence number to order the items within the hierarchy level.


Enter a description of the item. These descriptions will more fully describe the template that is being created.

EXOR



Version: 4.7 23



2.8 Obstruction Types – STR2050

Figure 18 – Obstruction Types Menu Option

EXOR



Version: 4.7 24



Figure 19 – Obstruction Types


This form is used to maintain Obstruction definitions, e.g., Height, Width, etc. that can be associated with structures.

These obstructions are associated with structures in the Obstruction window in Structure Hierarchies and Attributes –

STR3020. They are used when calculating abnormal load routes using List of Obstructions on a Route – STR5030.

2.8.2 Obstruction Types

New obstruction types are defined here. There is no restriction to the number or type of obstructions defined.

Code (Required)

A unique code must be entered that identifies an obstruction type.

Obstruction (Required)

The name by which the obstruction is normally known must be entered.

Units (Required)

The units that the obstruction type is normally measured by must be entered, e.g., metres, tonnes etc.


A description of the obstruction may be entered.

EXOR



Version: 4.7 25




Enter the start date the obstruction type will be used.

End Date (Optional)

Enter the end date of the obstruction.

EXOR


INSPECTION REFERENCE DATA

Version: 4.7 26



3 Inspection Reference Data


Structures by Exor database.


Inspection Sets – STR2068

Inspection Types – STR2060

Inspection Cycles – STR2062

Inspection Equipment – STR2064

Organisations – STR2070

BCI Reference Data – STR3002

Defect Code Maintenance – STR3003

The form descriptions provide you with detailed information about reference data in Structures by Exor, including:



characteristics)


EXOR



Version: 4.7 27



3.1 Inspection Sets – STR2068

Figure 20 – Inspection Sets Menu Option

Figure 21 – Inspection Sets

EXOR



Version: 4.7 28




This form is used to group a number of inspection types together in a set, e.g., a non-destructive testing set may consist of

sonar and x-ray inspections.

These inspection sets will be used in conjunction with the structure type when scheduling inspections using Inspection

Types – STR2060.

3.1.2 Inspection Sets

When you enter this window, the cursor sits in the Set field waiting for you to either enter a new inspection set or press

[Enter Query], enter your selection criteria and press [Execute Query] to obtain existing inspection sets.

Set (Required)

Enter a unique code for the inspection set ID.

Name (Required)

Enter the name of the inspection set.


Enter the date from which this inspection set is to be used.

End Date (Optional)

If the inspection set is no longer required, enter the end date.

3.1.3 Inspection Types

When you enter this window, existing inspection types will be displayed. Inspection types are associated to inspection

sets.

Type (Required)

Enter a code for the inspection type.

Name (Required)

Enter the name of the inspection type.


Enter a description of the inspection type.


Enter the date from which this inspection type is to be used.

End Date (Optional)

If the inspection type is no longer required, enter the end date.

EXOR



Version: 4.7 29



3.2 Inspection Types – STR2060

Figure 22 – Inspection Types Menu Option

Figure 23 – Inspection Types

EXOR



Version: 4.7 30




This form allows an association to be made between an Inspection Set and a Structure Type. For each inspection type,

inspectable intervals and inspectable components/attributes may be defined.

Any number of Inspection Sets can be associated with a Structure Type. When the routine for Auto-Schedule Inspections

– STR3070 is run, it will schedule the inspections based on the intervals nominated for each inspection type/structure type

combination.

3.2.2 Selection Criteria

The inspection sets, set up using Inspection Sets – STR2068, are associated with the relevant structure type here.

Inspection Set (Required) List

Enter the code for the inspection set. A description will be displayed in the adjacent field.

Structure Type (Required) List

Enter the code for the structure type. A description will be displayed in the adjacent field. Only structures defined as level

1 within the structure hierarchy in Structure Item Types – STR2030 will be displayed in the list.

3.2.3 Valid Structural Inspections

When you enter this window, the cursor sits in the Structure Type field with existing structural inspections automatically

queried, waiting for you select [Insert Record] to enter new data.

The inspection types that are valid for the selected structure type and the intervals at which they occur are defined here.

Inspection Type (Required) List

Enter the code for the inspection type for the selected structure. The options available will depend upon the inspection set

selected. A description will be displayed in the adjacent field.

Mandated Interval (Required)

Enter the mandated interval, in months, between inspections of this type, as specified the Department of Transport.

Preferred Interval (Required)

Enter the preferred interval, in months, between inspections of this type. This value must be less than or equal to the

mandated interval and represents the interval at which inspections will normally be scheduled. The preferred intervals

must be multiples of each other for scheduling purposes. To override these values use Inspection Controls for a

Structure – STR3022.

Use for CI? (Optional)

Check this box if this type of inspection is to be used by Calculate Bridge Condition Indicators – STR3001.

EXOR



Version: 4.7 31



3.2.4 Inspectable Components

Figure 24 – Inspectable Components

When you select the [Inspectable Components] button this window will be displayed, the cursor will sit in the

Component field with existing components automatically queried, waiting for you to select [Insert Record] to enter new

data.

A default set of inspectable components, which may be inspected during this type of inspection on this particular structure

type are defined here. The inspection that is to be carried out will rate the deterioration of these components.

This default set of inspectable components can be overwritten with the actual items defined within the structure and their

associated descriptions using Inspection Controls for a Structure – STR3022.

Inspectable component details can be entered using Scheduled Inspections for a Structure – STR3072.

Inspectable component details can be printed using Profile of a Structure – STR5015.

No. (Required)

Enter the number of the component.

Component (Required) List

Enter the component of the structure that is to be inspected during an inspection of this type. A general rating for each

component type will be entered during the inspection.

Detailed (Optional)

If a Y is entered, the full description for each individual component of the type selected will be downloaded so each

component can be rated during the inspection.

EXOR



Version: 4.7 32



3.2.5 Inspectable Attributes

Figure 25 – Inspectable Attributes

When you select the [Inspectable Attributes] button this window will be displayed, the cursor sits in the Component

field with existing components and attributes automatically queried, waiting for you to select [Insert Record] to enter new

data.

This window is used to set up a set of inspectable attributes that may be recorded during this type of inspection on this

particular structure type. Note that there is NO association between inspectable components and inspectable attributes, i.e.

,an attribute may be recorded even though its component is not being inspected.

This allows you to keep your structure inventory up to date when carrying out inspections.

When an inspection is carried out and values for these components are entered the inventory will automatically be updated

to reflect the new values in 2 ways.

An inspection batch is created and downloaded onto a DCD, following the inspection the batch will be uploaded from the

DCD and the new values will be associated with the inspected structures.

A manual inspection is carried out using Inspection Records for a Structure – STR3086, the new values will be

manually entered, once the inspection is saved the new values will be associated with the inspected structures.

Inspectable attribute details can be entered using Scheduled Inspections for a Structure – STR3072.

Inspectable attribute details can be printed using Profile of a Structure – STR5010.

If the structure to be inspected does not contain one or more of the components set up here they will not be displayed

when inspected or printed.

Component (Required) List

Enter the code for an inspectable component of the structure. A description will be displayed in the adjacent field.

Attribute (Required) List

Enter the attribute for the specified component. A description will be displayed in the adjacent field.

EXOR



Version: 4.7 33



3.3 Inspection Cycles – STR2062

Figure 26 – Inspection Cycles Menu Option

Figure 27 – Inspection Cycles

EXOR



Version: 4.7 34




This form is used to set up the inspection cycles to which structures may be associated so that inspection workloads will

be evenly distributed when using Auto-Schedule Inspections – STR3070.

In effect, the cycle start date determines the date from which the Auto-Scheduler attempts to start scheduling inspections,

this will generally be the date of the last Principal inspection of the selected structure, although it will never schedule

inspections prior to the system date.

Inspection cycles are associated to structures using Inspection Controls for a Structure – STR3022.

3.3.2 Inspection Cycles

When you enter this window, the cursor sits in the Cycle Number field waiting for you to enter new data. Press [Execute

Query] to obtain existing information.

Cycle Num. (Required)

Enter a unique inspection cycle number.

Cycle Name (Required)

Enter the name of the inspection cycle.

Start Date (Required)

Enter the date the inspection cycle is due to start. This must be in the default format of DD-MON-YYYY.


Enter a description of the inspection cycle.

EXOR



Version: 4.7 35



3.4 Inspection Equipment – STR2064

Figure 28 – Inspection Equipment Menu Option

Figure 29 – Inspection Equipment

EXOR



Version: 4.7 36




This form is used to register any specialist equipment that might be used on an inspection. This information would be used

in Inspection Controls for a Structure – STR3022.

3.4.2 Inspection Equipment

When you enter this window, the cursor sits in the field waiting for you to enter new data. Press [Execute Query] to

obtain existing information.

Code (Required)

Enter an equipment code.

Name (Required)

Enter the name of the specialist equipment that will be used whilst carrying out an inspection.


Enter a description of the specialist equipment.


Enter the date from which this piece of equipment is to be used.

End Date (Optional)

If the piece of equipment is no longer required, enter the end date.

EXOR



Version: 4.7 37



3.5 Organisations – STR2070

Figure 30 – Organisations Menu Option

EXOR



Version: 4.7 38



Figure 31 - Organisations


This form is used to register any organisations that might need to be notified when work is to be carried out on a structure.

This information would be used in Inspection Controls for a Structure – STR3022.

3.5.2 Organisations

When you enter this window, the cursor sits in the field waiting for you to enter new data. Press [Execute Query] to

obtain existing information.

Organisation (Required)

Enter a unique organisation code.

Name (Required)

Enter the name of the organisation.

Type (Optional)

Enter an organisation code. These are set up and maintained in Domains – HIG9120 updating the domain name

STR_NOTIFIABLE_ORGS.

Description (Display only)

EXOR



Version: 4.7 39



A description of the organisation type will be displayed

Admin Unit (Optional)

Enter the admin unit to which this organisation belongs

Name (Display Only)

The description of the admin unit will be displayed.

Address (Required)

Enter the postal address of the organisation.

Phone (Optional)

Enter the contacts phone number.

Fax (Optional)

Enter the organisations fax number.

Contact Name (Optional)

Enter the contact name.

Vat No (Optional)

Enter a VAT number

Credit Type (Optional)

Enter their credit type

Credit Ref. (Optional)

Enter their credit reference.


Enter the start date for this organisation.

End Date (Optional)

Enter the end date for this organisation.

Comments (Optional)

Enter any additional comments.

EXOR



Version: 4.7 40



3.6 BCI Reference Data – STR3002

Figure 32 – BCI Reference Data Menu Option

Figure 33 – BCI Reference Data


This form is used to maintain what are known as Rulesets. A Ruleset is a set of Meta Data that is used in the Calculate

Bridge Condition Indicators – STR3001. Rulesets are useful as they can be copied and then altered to suit local needs.

Structures Manager is shipped with a default Ruleset called RULESET V2.0. This is the current National set of Meta Data

for calculating BCIs as detailed in the ‘Evaluation of Bridge Condition Indicators’ document produced on behalf of the

UK CSS Bridges Group. Only when all Inspection Components have an Element Importance Factor and the Default Deck

Areas have been set should you consider copying this Ruleset for further amendment.

3.6.2 Bridge Condition Reference Data

This window is used to create new, delete or change existing BCI Rulesets.

When you enter this window, the cursor sits in the Name field waiting for you to select a Ruleset for viewing or

modification. To create a new Ruleset either use the [Copy Ruleset] button to copy an existing ruleset or select [Create

Record] to enter a new one.

When deleting a ruleset all the child items in the other windows must be deleted and saved first.

EXOR



Version: 4.7 41



Id (Default)

A unique system generated Id will be displayed for each Ruleset.

Name (Required)

Enter a short Ruleset name.

Date (Required)

Enter the date from which the Ruleset becomes available for use. This date has no effect on the BCI calculation dates.

Description (Required)

Enter a full description of the new Ruleset.

3.6.3 Element Condition Score Data

Figure 34 – Element Condition Score Data

This window defines how a given Extent and Severity recorded against each component using Inspection Records for a

Structure – STR3086 are turned into an Element Condition Score (1-5).

UK customers should not need to modify this data within the default Ruleset, however if local Rulesets are to be used

these may be changed if the user wishes to have different scoring calculations.

The Extent and Severity values must be a unique combination.

Extent (Required) List

Enter an Extent. The extent list of values is maintained using Attribute Domains – STR2010 within the

DEFECT_EXTENT list of values.

Severity (Required) List

Enter a Severity. The extent list of values is maintained using Attribute Domains – STR2010 within the

DEFECT_SEVERITY list of values

EXOR



Version: 4.7 42



Condition Score (Required)

Enter a condition score, this must be in the range 0.0 to 9.9.

3.6.4 Type Rules

Figure 35 – Type Rules

This window is used to define the rules associated with each element type.

To quickly set the deck area for each structure use Bulk Maintenance of Attribute Values – STR3050.

Element Code (Required) List

Select an element that is to have an associated size attribute and default values. A description will be displayed in the

adjacent field.

Default Value (Required)

If the system cannot find this attribute for a given structure then it will use a default value. These values should be updated

for each individual structure type to be more realistic.

Enter a default value that is most appropriate for the selected element.

Size Attribute (Required) List

When calculating the Bridge Stock Condition Indices the system expects to find an attribute stored against each structure

that defines the size of the structure that will be used in the calculations (area or length).

If the system cannot find this attribute for a given structure then it will use the default value defined above. .

Enter the attribute that will be used to store the size attribute as held against the structure type. These attributes are

standard attributes and will be defined using Attribute Types – STR2020 and associated to a structure type using

Structure Item Types – STR2030.

AVF (Optional)

Enter the Asset Valuation Factor. This is used to weight one structure type against another in the equations used in the

calculations. If no value is entered against an element type the Bridge Stock calculations will fail and will be set to zero.

EXOR



Version: 4.7 43



3.6.5 Element Importance Factors

Figure 36 – Element Importance

Each Inspectable Component must have an Element Importance Factor defined if it is to contribute to the Overall

Bridge Condition Index. This factor is essentially a weighting based on how important the element is to the overall

Structural Integrity of the Structure in terms of load carrying capacity, durability and public safety.

A default set of Components and their Importance Factors has been defined in the Default Ruleset.

Any components used as part of an inspection should have an element importance factor defined. However, this will not

be required if the components do not contribute to the bridge condition index calculation such as Vegetation or Voussoirs,

however others must be added to ensure an accurate Bridge Condition Index is obtained.

Due to the flexible nature of the Structures Manager product certain Inspectable Items that have been defined by a given

Customer will not exist at this point and so need to be added manually BEFORE the Bridge Condition Indices can be

calculated accurately.

A component that has not been added to the Ruleset and does not have an EIF defined will have a valued of –1 in the EIF

column in Calculate Bridge Condition Indicators – STR3001. If the item does contribute to the overall BCI it must be

added before the calculation can give an accurate reading.

Element (Required) List

Select an element that is to be used in the BCI calculation. A description will be displayed in the adjacent field.

Element Importance (Required) List

Enter an element importance factor for the selected element. A description will be displayed in the adjacent field

The table below shows the default elements and their associated Element Importance Factors. Use this information to

match your existing elements to the default ones and add them to the ruleset accordingly.

EXOR



Version: 4.7 44



Set Item No. Element Description Element Importance

Deck Elements 1 Primary deck element Very High

2 Secondary deck element/s

Transverse beams High

3 Element from Table 2 of Ref. A

Very High

4 Half joints Very High

5 Tie beam/rod Very High

6 Parapet beam or cantilever Very High

7 Deck bracing High

Load-Bearing Substructure

8 Foundations High

9 Abutments (incl. arch springing) High

10 Spandrel wall/head wall High

11 Pier/column Very High

12 Cross-head/capping beam Very High

13 Bearings High

14 Bearing plinth/shelf Medium

Durability Elements 15 Superstructure drainage Medium

16 Substructure drainage Medium

17 Water proofing Medium

18 Movement/expansion joints High

19 Painting: deck elements Medium

20 Painting: substructure elements Medium

21 Painting: parapets/safety fences Medium

Safety Elements 22 Access/walkways/gantries Medium

23 Handrail/parapets/safety fences High

24 Carriageway surfacing Medium

25 Footway/verge/footbridge surfacing Low

Other Bridge Elements

26 Invert/river bed Medium

27 Aprons Medium

28 Fenders/cutwaters/collision protection Medium

29 River training works Medium

30 Revetment/batter paving Low

31 Wing walls High

32 Retaining walls Medium

33 Embankments Low

34 Machinery Medium

EXOR



Version: 4.7 45



Set Item No. Element Description Element Importance

Ancillary Elements 35 Approach rails/barriers/walls

Elements not used in BCI evaluation, thus importance not required.

36 Signs

37 Lighting

38 Services

3.6.6 Copy Selected Ruleset

Figure 37 – Copy Selected Ruleset

Before a Ruleset is copied ensure that the default Ruleset includes Element Importance Factors for all of the inspection

components used. If the components have been created by the user they will not exist in the standard Ruleset.

When deciding which EIF value to enter for a given inspection component it may be that there is a choice for the valued

assigned to it. In order to assess the impact of the different EIF a copy Ruleset can be created. The same component can

have a different EIF value in the copied Ruleset.

A Ruleset may be copied if you wish to give a higher EIF value to certain components in an area due to local

environmental factors etc.

Once a copy of a Ruleset has been created it can be amended as required to suit your local requirements.

New Ruleset Name (Required)

Enter the name of the new Ruleset.

New Ruleset Description (Optional)

Enter the description of the new Ruleset.

EXOR



Version: 4.7 46



3.6.7 Type Combinations

Figure 38 – Type Combinations

When two similar elements are reported separately the one that takes precedence over the other within the calculation of

the average condition indicator needs to be specified.

Item Pair (1) (Optional) List

Enter the first element that will form the pair of elements.

Item Pair (2) (Required) List

Enter the second element that will form the pair of elements.

Action (Required) List

Enter the action to be carried out when the paired items are found during an inspection on a bridge.

EXOR



Version: 4.7 47



3.6.8 Importance Weightings

Figure 39 – Importance Weightings

This form is used to maintain the importance score and associated weightings that are to be used in the BCI calculations.

EXOR



Version: 4.7 48



3.7 Defect Code Maintenance – STR3003

Figure 40 – Defect Code Maintenance Menu Option

Figure 41 0 Defect Code Maintenance


This form is used to maintain both the defect code and its severity for each associated Inspectable item during an

inspection. This code helps identify the work that is required.

The Defect Code/Severity combination must be unique by item type, i.e., there can only be one occurrence of Defect Code

‘7.1’ with a Severity ‘1’ for an item type ‘APRN’

Item Type (Display Only)

Additional item types and their associated defect codes are added to this selection using the [Copy Defect Set] button as

described below.

EXOR



Version: 4.7 49



3.7.2 Defect Codes

Figure 42 – Defect Codes

Each item type can have a number of defect codes associated with it, these defect codes are created and maintained here.

Defect Code (Optional)

Enter the unique defect code for this item.

Sev. (Optional) List

Enter the severity of the defect.

Defect Description (Optional)

Enter the full description of the defect code.

Order By:

Order the display of the defect codes by either Defect Code or Severity.

EXOR



Version: 4.7 50



3.7.3 Copy Defect Set

Figure 43 – Copy Defect Set

Copy defect set is used to:

Create a new defect set for an existing Item Type as a copy of the defects for the currently selected Item Type.

Create a new defect set for an existing Item Type with a default set of defects.

Both defect sets can then be updated as required.

When creating a new defect set the only item codes that will be available are those that do not already have a defect code

set created for them.

Item Type (Required) List

Select the Item that is to have a defect set created. A description will be displayed in the adjacent field.

Select [Create Defect Set] to create a copy of the defect set for the highlighted Item in the previous window.

Select the check box [Create Default Defect Code Only] followed by [Create Defect Set] to create a default set

of defects for modification as required.

Select [Cancel] to cancel the copy.

EXOR


STRUCTURES REFERENCE DATA REPORTS

Version: 4.7 51



4 Structures Reference Data Reports

This chapter provides examples and the required selection criteria for all the Structures Reference Data Reports.

List of Attributes Domains – STR5004

List of Attribute Types – STR5005

List of Item Types – STR5006

List of Attribute Groups – STR5007

List of Valid Item/Attributes – STR5008

List of Valid Item/Inspections – STR5009

Figure 44 – Structures Reference Data Reports Menu Option

EXOR



Version: 4.7 52



4.1.1 Running Reports

The majority of reports within Highways by Exor are accessed using a standard window called the Generic Reporting

Interface (GRI). Whilst the selection criteria for each report will change from report to report, the way the reports are run,

viewed and printed remains constant.

Below is an example of the Generic Reporting Interface.

Figure 45 – Reports GRI

The title of the report is displayed at the top of the window.

There are three buttons down the left hand side, they are as follows:

Run report – When the selection criteria have been entered, this will run the report and place the

output in the report previewer.

Save Parameters – The Parameters for reports that have to be constantly re-run or have complex

selection criteria can be saved to a file and re-used. You will be prompted to enter a file name.

Each user can have their own set of saved parameters.

Load Parameters – Previously saved parameters for the selected report can be loaded directly

into the GRI. You will be prompted to enter a file name, if you have a number of saved

parameters, double-clicking the field will result in a list of saved parameters being displayed.

EXOR



Version: 4.7 53



4.2 List of Attribute Domains – STR5004


This report gives details of each of the lists of values available when selecting attributes. This information is maintained

using Attribute Domains – STR2010 .


Domain (Optional) List

Enter the domain that is to be reported on, if this field is left blank all domains will be reported on.

EXOR



Version: 4.7 54



Figure 46

EXOR



Version: 4.7 55



Figure 47

EXOR



Version: 4.7 56



4.3 List of Attribute Types – STR5005

This report gives details of all attribute types set up on the system with details of the attributes domain, minimum and

maximum values data type, etc. This information is maintained using Attribute Control Data – STR2020.

No selection criteria is required to run this report.

Figure 48

EXOR



Version: 4.7 57



4.4 List of Item Types – STR5006


This report gives details of all the structures item types that exist on the system. This information is maintained using

Structure Item Types – STR2030.


Figure 49

EXOR



Version: 4.7 58



4.5 List of Attribute Groups – STR5007


This report gives details of all the attribute groups that exist on the system. This information is maintained using

Attribute Groups – STR2024


Figure 50

EXOR



Version: 4.7 59



4.6 List of Valid Item/Attributes – STR5008


This report gives details of the attributes associated with each item type. This information is maintained using Structure

Item Types – STR2030.


Figure 51

EXOR



Version: 4.7 60



4.7 List of Valid Item/Inspections – STR5009


This report gives details of the inspections that are associated with each item type. This information is maintained using

the Inspection Types – STR2060.


Figure 52

EXOR


BULK DATA LOADING

Version: 4.7 61



5 Bulk Data Loading

This chapter describes the forms used in carrying out the inspections of structures using a Data Capture Device. They are

the following options:

Download Control Data into DCD File – STR1001

Download Inspection Parameters into DCD File – STR1002

Upload Inspection Records from DCD File – STR1003

Load Structures Inventory onto Database – STR1004

The form descriptions provide you with detailed information about each Inspections Management form in Structures by

Exor, including:

an overall description of the


characteristics)


5.1.1 Prerequisites

Before starting to inspect structures you should check that the Reference Data has been successfully loaded and that the

inspectable components and attributes of the structure have been set up. In addition the following will have been set up:

Inspection Sets – STR2068

Inspection Types – STR2060

Inspection Cycles – STR2062

Inspection Equipment – STR2064

5.1.2 Structure Locking

Structure locking stops users from changing a structure or its attributes and will occur for the two following reasons:

A structure or its attributes are currently being modified by another user. This structure will remain locked until the user

that is modifying the structure commits it to the database. If you attempt to modify this structure you will receive the

following error message:

ERROR: Structure currently locked by another user.

A structure has been downloaded onto a Data Capture Device (DCD) for inspection purposes. If you attempt to modify

this structure you will receive the following error message:

ERROR: Inspection in progress; cannot modify record.

When creating inspection batches, it is advisable to keep the duration of an inspection low, typically a week. This is due to

structure locking while an inspection is taking place. If a 3-month batch was created, all the structures contained within

that batch will be locked on the system until the inspection is uploaded back onto the system. This could cause problems

in maintaining the structures.

If you are intending to do inspections manually, it is still recommended that the inspection be downloaded into an

inspection file. This will have the effect of locking the structures while the manual inspection is taking place. Another

advantage of using the download function is that it will automatically print the required paperwork for the manual

inspection.

EXOR


BULK DATA LOADING

Version: 4.7 62



If the inspection is to be carried out manually, the data should be loaded onto the system via Inspection Records for a

Structure – STR3086.

EXOR


BULK DATA LOADING

Version: 4.7 63



5.1.3 Flow Diagram of Structures Inspection Process

EXOR


BULK DATA LOADING

Version: 4.7 64



Figure 53

5.2 Inspecting with a Data Capture Device


If you are carrying out inspections using a Data Capture Device (DCD), you will need to create and load the following

two files onto the DCD prior to carrying out any inspections:

Control Data file

Inspection file

The above files will be created on your workstation. These files will require re-naming and transferring onto a DCD via a

PC.

Inspection Files

The files created when using a DCD will reside in either your home directory or your reports directory. There is no

automatic routine for the removal of these files. It is the responsibility of the System Administrator to backup these files if

required, and remove them from the database.

5.3 Manual Inspections


If you wish to take advantage of structure locking when carrying out manual inspections, the following procedures must

be carried out:

Download the inspection batch using Download Inspection Parameters – STR1002. This locks the structures.

Print the inspection batch using Profile of an Inspection – STR5015.

Carry out the inspections, filling in the details on the printout.

When the inspection is complete, upload the selected inspection batch using Upload Inspection Details –

STR1003. This unlocks the structures.

Enter the details of the inspection from the printout onto the system using Inspection Records for a Structure –

STR3086. Be sure to enter the date inspected, the inspector’s initials and comments.

5.4 Download Control Data – STR1001


This option is used to download the reference data from Structures into a file suitable for loading onto a DCD.

This option uses the GRI and will prompt you to enter a 'Y' to continue with the download.

This file will contain the following four record types:

DCD filename and date file created.

EXOR


BULK DATA LOADING

Version: 4.7 65



Attribute control data. Supplied as meta data when Structures is first installed, and maintained using Attribute

Types – STR2020.

List of valid attribute values. Supplied as meta data when Structures is first installed, and maintained using

Attribute Domains – STR2010.

List of people who will be using the Highways database. These details will have been entered using Users

(Installation and Configuration Guide).

When this file is transferred to the DCD it will need renaming to the format the DCD software requires.

5.5 Download Inspection Parameters – STR1002


This option is used to download an inspection batch into a file format suitable for transfer onto a DCD. This allows the

inspector to inspect a series of structure attributes against what is held on the database.


This window is used to select an existing inspection batch that is to be downloaded to a DCD.

Batch No (Required) List

Select an existing batch that has not been downloaded.

Use Previous Inspection (Optional)

Enter a 'Y' to have the results of the previous inspection downloaded onto the DCD for comparison purposes. The

following inspection data will be loaded:

severity

extent

defect

priority

action

comments

Select the [Run] button to execute the download.

EXOR


BULK DATA LOADING

Version: 4.7 66



5.6 Upload Inspection Details – STR1003


This option is used to upload the inspection data contained in a DCD file back into the structures database. The content of

the DCD file will be validated when uploaded.


Load File Path (Required)

Enter the full path and filename of the file to be uploaded.

EXOR


BULK DATA LOADING

Version: 4.7 67



5.7 Load Structure Inventory onto Database – STR1004


This section details the utility that is available for the bulk loading Structures inventory into the structures database.

This utility requires an operating system text file in the format given below.

The following diagram shows the flow of data and the files produced when using the bulk loader.

5.7.2 Bulk Structure Loading Flow Diagram

Figure 54

5.7.3 Discard File

This file is in the same format as the original file. It has the same name as the original load file with a ‘.dis’ suffix, e.g.,

‘filename.dis’. It contains the comments from the original file as well as all the records that failed the validation checks.

This file can be re-edited and then re-submitted. If you wish to retain a valid file for historical purposes you should also

correct the original file.

5.7.4 Error Message File

This file contains all the records that failed the load with associated error messages explaining the reason for the failure.

You should note that both the discard and error file are written onto the path entered for the load file. You should

therefore ensure that you have appropriate O/S write permissions to its path.

EXOR


BULK DATA LOADING

Version: 4.7 68



5.7.5 Structures Inventory Loader File Specification

To enable customers to bulk load Structures Inventory data, a standard Inventory Loader file will be used. The use of a

standardised file format ensures that all Inventory data can be loaded accurately and reliably.

The general principle behind the Structures Inventory loader is that each structure is represented by a 'batch' of records

within the file. Each 'batch' commences with a Structure Header record followed by a number of records of differing types

describing it's hierarchical breakdown into components (including main structure), related component attributes and

associated road network details.

The file must be comma delimited, of variable length format. Each record must be on a single line. None of the individual

fields can contain commas.

There are five available record types:

Type 1 – Structure Header

Type 2 – Structure Position

Type 4 – Structure Description

Type 5 – Component Details

Type 7 – Component Attribute Details

Each of these is detailed below.

5.7.6 File Format

The exact composition of an Inventory Loader file will differ depending on the type of Structures and the Components

contained within it but in general, the following rules will be true:

Each Structure will commence with a Type 1 (parent level only) record.

The Type 1 can optionally be followed with a Type 2 record to locate the Structure on the Road Network and/or

via Grid References.

The Type 1 or type 2 if used, will always be followed by one Type 4 record. This contains the description of the

Structure.

The Type 4 will always be followed by one or more Type 5 records for each structure to define the Components

making up the Structure. The first of these will always contain details of the main Structure itself.

The Type 5 can optionally be followed by one or more Type 7 records defining the Attribute values for this

Structure Component.

Note: Each Type 5 can be followed by as many Type 7 records as required to define all the attributes for each

Component.

EXOR


BULK DATA LOADING

Version: 4.7 69



5.7.7 Validation Rules

The following validation is carried out on the supplied input file:

The Record Type must be valid (1, 2, 4, 5, or 7)

The Level must be between 1 and 9

There must only be a single Type 1 record per Structure



There can be as many Type 5 records as required

Levels must follow a logical sequence within a Structure

Type 7 records must follow immediately after the corresponding Type 5 record.

All ‘reference’ details e.g., Structure Type, Road Id or Attribute Id must be valid in the Structures system.

5.7.8 Structure Header Record – Type 01

This record will be in the form:

<Record Type>,<Local Reference>,<Level>,<Admin Unit>,<Inspection Cycle>

An example of which is:

01,A123,1,1,1

Record Type (Required)

Maximum 2 numbers. Should always contain 01 for record type 01.

Local Reference (Required)

Maximum 30 characters. Enter the unique structure reference.

Level (Required)

Maximum 1 number. Should always contain 1 for record type 01.

Admin Unit (Required)

Maximum 8 numbers. This is the Id of the admin unit to which the structure belongs. The admin units must exist on the

system prior to the load and are set up using Admin Units – HIG1860.

Inspection Cycle (Required)

Maximum 8 numbers. This is the inspection cycle id. The inspection cycle id must exist on the system prior to the load

and are set up using Inspection Cycles – STR2062.

EXOR


BULK DATA LOADING

Version: 4.7 70



5.7.9 Network Intersection – Type 02

The record type 02 is optional and defines the structures position on the highways network. Once entered these details can

be viewed in the intersections window in Structure Hierarchies and Attributes – STR3020.


<Record Type>,<Local Reference>,<Level>,<Sequence>,<Road Id>,<Start Chainage>,<End Chainage>,<Primary

Route>,<Location>,<Start Easting>,<End Easting>,<Start Northing>,<End Northing>


02,A123,1,1,1234A999 1/00010,20,60,Y,OVER THE RAILWAY,0123456,0123458, 987654,987652


Maximum 2 numbers. Always should contain 02 for record type 02.


Maximum 30 characters. Enter the unique structure reference, this should be the same as the reference entered for the type

01 record.

Level (Required)


Sequence (Required)


Road Id (Required)

Maximum 20 characters. This is the unique identifier for the road section and should be in the form:

<Agency Code><Linkcode>/<Section Number>

Agency Code – 4 Characters

Linkcode – 6 Characters

Section Number – 2 numbers for DoT roads, 5 numbers for local roads

The agency, linkcode and section number should exist and are set up and maintained using modules in the Network

Manager volume.

Start Chainage (Required)

Numeric value. This gives the start chainage of the structure along the road section.

End Chainage (Required)

Numeric value. This gives the end chainage of the structure along the road section.

Primary Route (Required)

Enter either ‘Y’ or ‘N’ indicating if the road selected is the primary route.

EXOR


BULK DATA LOADING

Version: 4.7 71



Location (Required)

Maximum 25 characters. This describes the structures location on or near the road.

Start Easting (Optional)

6 numeric. This is the ordinance survey easting grid reference for the start of the structure.

End Easting (Optional)

6 numeric. This is the ordinance survey easting grid reference for the end of the structure.

Start Northing (Optional)

6 numeric. This is the ordinance survey northing grid reference for the start of the structure.

End Northing (Optional)

6 numeric. This is the ordinance survey northing grid reference for the end of the structure.

5.7.10 Structure Header Record – Type 04


<Record Type>,<Local Reference>,<Level>,<Description>


04,A123,1,SINGLE SPAN RIVER CROSSING





01 record.

Level (Required)



Enter the textual description for the structure.

The description can be viewed when in Structure Hierarchies and Attributes – STR3020 by selecting the structure

followed by the [Expand] button.

EXOR


BULK DATA LOADING

Version: 4.7 72



5.7.11 Component Detail – Type 05


<Record Type>,<Local Reference>,<Level>,<Structure Type>,<Start Date>,<End Date>,<Component

Name>,<Component Description>


05,A123,1,BRID,01-JAN-1900,AXMANSFORD BRIDGE,,





01 record.

Level (Required)

Maximum 1 number. Defines the level of the item within the structures hierarchy.

Structure Type (Required)

Enter the structure or component type. These must exist on the system prior to the load and are set up using Structure

Item Types – STR2030.


Enter the start date of the structure or component. The date should be in the standard format of DD-MON-YYYY.

End Date (Optional)

Enter the end date of the structure or component. The date should be in the standard format of DD-MON-YYYY.

This date will only be entered if you wish to load historical structure details. If the end date is entered use Resequence

Structure Hierarchies – STR3060 to view the structure details or select the [Historical] button in Structure Hierarchies

and Attributes – STR3020.

Component Name (Required)

Maximum 30 Characters. Enter a unique component name. This can be viewed in the Hierarchies window in Structure

Hierarchies and Attributes – STR3020.

Component Description (Not Currently Used)

40 Characters.

EXOR


BULK DATA LOADING

Version: 4.7 73



5.7.12 Component Attribute Detail – Type 07


<Record Type>,<Local Reference>,<Level>,<Attribute Data>


07,A123,1,BRTY=1





01 record.

Level (Required)

Maximum 1 number. Defines the level of the item within the structures hierarchy and should be the same as the previous

05 record.

Attribute Data (Required)

Maximum 120 characters. This should be in the format XXXX=YYYY……. Where XXXX is a valid four character

attribute as set up using Attribute Types – STR2020 and YYYY….. is the assigned value. If the assigned value is from a

list of values these lists will have been previously set up using Attribute Domains – STR2010.

Upon successful completion of a bulk load you may modify the structure details using Structure Hierarchy and

Attributes – STR3020.

To obtain a report on the loaded structures details use Profile of a Structure – STR5010.

5.7.13 Loading the File

You will be asked to supply the following information:

Load File Path (Required)

Enter the location of the load file and the load file name on the server. The path and file name must be in uppercase.

Press to load the file.

EXOR


BULK DATA LOADING

Version: 4.7 74



5.7.14 Example Load File

An example load file is shown below:

01,A130,1,1,1

04,A130,1,SINGLE SPAN RIVER CROSSING

05,A130,1,BRID,,AXMANSFORD BRIDGE,,

07,A130,1,BRTY=1

07,A130,1,NOSP=1

07,A130,1,SEVS=123456

05,A130,2,BRNG,,BEARING 1,,

07,A130,2,BECO=000202

05,A130,3,JNTS,,JOINT FOR BEARING 1,

07,A130,3,JTCO=000203

This will result in the following structure being loaded onto the system:

EXOR


BULK DATA LOADING

Version: 4.7 75



Figure 55 – Example data load

Documents

EXOR Structures Manager Admin Guide - Bentley · PDF fileEXOR STRUCTURES MANAGER ADMIN GUIDE DOCUMENT TRACKER Version: 4.7 ii CONFIDENTIALITY STATEMENT The contents of this