Location IntelligenceInfrastructure Asset Management

Confirm®

Network Manager

v20.20f.AM

Information in this document is subject to change without notice and does not represent a commit-ment on the part of the vendor or its representatives. No part of this document may be reproducedor transmitted in any form or by any means, electronic or mechanical, including photocopying,without the written permission of Confirm.

© 2020 Confirm. All rights reserved.

Products named herein may be trademarks of their respective manufacturers and are hereby re-cognized. Trademarked names are used editorially, to the benefit of the trademark owner, withno intent to infringe on the trademark.

Open Source Attribution NoticeThe Confirm suite of products contain the following open source software:

• Feature Data Objects v 3.5.0, which is licensed under GNU Lesser General Public License,Version 2.1, February 1999 with the unRAR restriction. The license can be downloaded from:http://fdo.osgeo.org/licenceAndGovernance.html. The source code for this software isavailable from http://fdo.osgeo.org/content/fdo-350-downloads

• MrSID software (specifically the mrsid32.dll) is used under license and is Copyright © 1995-2002,LizardTech, Inc., 1008 Western Ave., Suite 200, Seattle, WA 98104. All rights reserved. MrSIDis protected by U.S. Patent No. 5,710,835. Foreign patents are pending. Unauthorized use orduplication prohibited.Patented technology in the Software was developed in part through a project at the Los AlamosNational Laboratory, funded by the U.S. Government andmanaged by the University of California.The U.S. Government has reserved rights in the technology, including a non-exclusive, nontrans-ferable, irrevocable, paid-up license to practice or have practiced throughout the world, for oron behalf of the United States, inventions covered by the patent, and has other rights under 35U.S.C. § 200-212 and applicable implementing regulations.For further information, contact Lizardtech.

• NodaTime, version number 1.3.10, which is licensed under the Apache license, version number2.0. The license can be downloaded from http://www.apache.org/licenses/LICENSE-2.0 . Thesource code for this software is available from http://nodatime.org/.

• Chromium Embedded Framework, version 3, which is licensed under the New BSD License.The license can be downloaded from http://opensource.org/licenses/BSD-3-Clause. The sourcecode for this software is available from http://code.google.com/p/chromiumembedded/down-loads/list.

• Xilium.CefGlue, version 3, which is licensed under the MIT License (with portions licensed underthe New BSD License). The licenses can be downloaded from http://opensource.org/licenses/MITand http://opensource.org/licenses/BSD-3-Clause. The source code for this software is availablefrom http://xilium.bitbucket.org/cefglue/.

• D3 Data Driven Documentation, version 3.4.1, which is licensed under the New BSD License.The license can be downloaded from from https://github.com/mbostock/d3/blob/master/LICENSE.The source code for this software is available from http://d3js.org/.

• OpenLayers, version 2.12, which is licensed under the Modified BSD License. The license canbe downloaded from http://svn.openlayers.org/trunk/openlayers/license.txt. The source code forthis software is available from http://trac.osgeo.org/openlayers/browser.

• OpenLayers, version 3, which is licensed under the BSD 2-Clause Licence. The license whichcan be downloaded from https://github.com/openlayers/ol3/blob/master/LICENSE.md. The sourcecode for this software is available from https://github.com/openlayers/ol3.

• Proj4js, version 1+, which is licensed under the Apache License, Version 2, January 2004. Thelicense can be downloaded from http://www.apache.org/licenses/LICENSE-2.0.html. The sourcecode for this software is available from http://trac.osgeo.org/proj4js/.

• requireJS, version 2.1.2, which is licensed under the MIT License or the New BSD License. Thelicense can be downloaded from https://github.com/jrburke/requirejs/blob/master/LICENSE. Thesource code for this software is available from http://requirejs.org/.

• Apache Cordova, version 8.1.2, which is licensed under the Apache License, Version 2, January2004. The license can be downloaded from http://www.apache.org/licenses/LICENSE-2.0.html.The source code for this software is available from http://phonegap.com/download/.

• Xilium.CefGlue, version 75.1, which is unlicensed. The source code for this software is availablefrom https://gitlab.com/xiliumhq/chromiumembedded/cefglue.

• Chromium Embedded Framework, version 75.0, which is licensed according to the followingcriteria:Copyright (c) 2008-2014 Marshall A. Greenblatt. Portions Copyright (c) 2006-2009 Google Inc.All rights reserved.Redistribution and use in source and binary forms, with or without modification, are permittedprovided that the following conditions are met:* Redistributions of source code must retain the above copyright notice, this list of conditionsand the following disclaimer.* Redistributions in binary form must reproduce the above copyright notice, this list of conditionsand the following disclaimer in the documentation and/or other materials provided with the distri-bution.* Neither the name of Google Inc. nor the name Chromium Embedded Framework nor the namesof its contributors may be used to endorse or promote products derived from this software withoutspecific prior written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIEDWARRANTIESOFMERCHANTABILITYANDFITNESSFORAPARTICULARPURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CON-TRIBUTORSBE LIABLE FORANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENTOFSUBSTITUTEGOODSORSERVICES; LOSSOFUSE, DATA,ORPROFITS;ORBUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.The source code for this software is available from http://opensource.spotify.com/cefbuilds/in-dex.html#

August 20, 2020

Contents

Network Manager

PMS 8

Street Register forPMS 9

Feature 10

FeatureIdentificationImage 11

Feature SystemSettings 12

Allocate FeatureType 15

Feature -Inventorytab 16

AllocateConditionValues 16

Survey Data 17

Survey 17

DocumentLinks 18

SurveySection 22

BatchButton 25

Network Utilities 27

ImportUtilities 27

Import SurveyData 29

AggregateMeasurements 32

Node ReferenceBatch 33

Create InventoryLinks 34

Deleteinventory 34

InventoryAttributeDependentUpdate 34

Network Reports 36

InventorySummaryReport 38

Network SurveyCoverageReport 39

Network SurveyCoverage DetailReport 40

Network Lookups 41

Node 41

ConnectionMode 41

Cross SectionalPosition(XSP) 42

Unit ofMeasure 43

MeasurementType 44

AttributeTypes 45

FeatureGroup 49

FeatureType 72

NamedSelection 74

Network 75

ExternalNetworkSection 75

Feature TypeImportSettings 78

Network ImportSettings 79

Network SystemSettings 80

Network SeedNumbers 81

Survey DataLookups 83

ObservationType 83

ObservationParameter 87

ObservationImpact 89

SurveyType 89

ActionOfficer 91

NotebookCode 94

Network ImportSettings 94

ObservationImportCodes 95

Network SystemSettings 96

Survey SeedNumbers 97

HDM-4 Interface 98

StrategyAnalysisInterface 98

ProgrammeAnalysisInterface 99

HomogenousData Report 101

HomogenisationSystemSettings 103

HDM-4 SystemSettings 108

HDM-4 InterfaceReference Manual 114

StrategyAnalysis 114

ProgrammeAnalysis 116

MaintenanceAlternatives 118

HDM-4DatabaseMapping 119

Network ManagerThe Network Manager folder contains libraries, utilities and reports for themanagement of Street data relating to PMS.

For details on producing the National Indicator reports see UKPMS Indic-ator Reports.

For details on producing financial information for asset management seeUKPMS Financial Information.

In this section

PMS 8Street Register for PMS 9Feature 10Survey Data 17Network Utilities 27Network Reports 36Network Lookups 41Survey Data Lookups 83HDM-4 Interface 98HDM-4 Interface Reference Manual 114

PMSPMS Street Sections are held in the Network Manager folder, together with Inventory and Survey data.Inventory and Surveys are linked with Street Sections. Street Sections are held on Streets. Street In-formation is stored in the Confirm Street folder and information on creating, editing, and viewing Streetsis covered in the Street Register manual.

8 of 123Confirm

| Network Manager |

Street Register for PMSMost of the Street Lookups and entries are not specific to PMS and will be used for Maintenance andreporting. Only the following Street Lookup has a specific PMS function:

This is a mandatory requirement of PMS for grouping Streets together accordingto their priority or hierarchy for processing and analyses. Network Priority set at

Network Priority:

Street Level will default to Street Sections and Inventory, but may be edited ateither of those levels.

Note: The Network Hierarchy for PMS processing is set at PMS Section level inInventory

9 of 123Confirm

| Network Manager |

Feature

The Feature form displays the basic Feature information in the top part of the form, with associatedInventory, references and attributes in tabs along the bottom. The lower portion of the form remainsblank until the form is populated with Features. The associated Inventory and Attributes are added byreference to the Feature Group, and may be edited but not added directly in the form.

The Feature screen will optionally display an image of the Feature currently being viewed. See FeatureIdentification Image on page 11 for more information.

The name of the Site that contains the Feature.Site:Note: Entering the Site for a new Feature will automatically populate the CostCode and Classification fields from the Site.

A free text field into which a reference Feature number can be entered. (Optional)Asset Id:The system can be set to accept only unique entries in this field.Feature System Setting

Each Feature must have a unique Plot Number within the Site.Asset Number:This number can be set automatically by Confirm using the following rules:1. If the Feature Group of the Feature being created has a range set then this is

used. Feature Group - Additional tab on page 512. If the Feature Group is not set, the range in the Feature System Settings is

used. Feature System Settings on page 123. If the two checks above fail, a new Plot Number will be assigned by Confirm

from the range 0-99999999.99 - This range cannot be changed.

The date at which the Feature became or will become active. The box to the rightwill show the status of the Feature. It will be one of the following:

Start Date:

• Live for a Feature with a Start Date in the past and no End Date

10 of 123Confirm

| Network Manager |

• Live Until for a Feature with a Start Date in the past and an End Date in the fu-ture. The End Date is also shown.

• End Dated for a Feature with an End Date in the past. The End Date is alsoshown.

• Proposed for a Feature with a Start Date in the future. If it has an End Date, thatis shown too.

The date at which the Feature has reached the end of its useful life, or is replacedby another version.

To:

Features are end dated using the 'End Date' button, or when the Feature is made'Dead'

Select from the Feature Type library.Feature Type:Feature Type on page 72Entering a Feature Type will bring in default Measurement Types and Units ofMeasure for the Type (through the Feature Group). Attributes Types, Smart Attrib-ute Types, Date Types, and Inventory Types will also default from the FeatureType through the Feature Group.Note: It is not possible to manually change the Feature Type of an existing Featureto one which is in a different Feature Group. If this is required, the 'AllocateFeature Type on page 15' utility must be used.

A free text field for the optional entry of a location.Location:Location details will be displayed on Works Orders and (optionally) on WorksTickets

(Asset Validation module)Validated Date andValidated By: These fields are not editable, but show the date and time the Feature passed

validation using the ‘Batch Validate Features’ utility, and the User who ran theutility.The fields are only visible for a Feature belonging to a Feature Group configuredfor validation, i.e. one with a Validation Data Source specified.If a Feature has been validated, then editing the Feature will result in a warningbeing displayed on saving. If the user chooses to proceed with the save, thesefields will be cleared.See Batch Validate Features for more information.

Update access to Asset Id, Feature Type, Start Date and Location of a feature is controlled by ’FeatureMain (Security)’ user level security setting within user and group security.

Feature Identification Image

The Feature screen will optionally display an image of the Feature currently being viewed, if thishas been activated for the Feature Group (using the 'Show Identification Image' setting on theDisplay tab), and a suitable image is available.The image must be an image file (bmp, jpg, png or gif) attached as a Document Link to the Feature.A URL link will not be considered.The Feature System Settings screen has a ‘Maximum Size for Identification Image’ which can beused to limit the size of the image files considered, to prevent performance issues with large files.By default files up to 1,000kB in size are considered.

11 of 123Confirm

| Network Manager |

A user can indicate the preferred Identification Image on the Document Links screen. If this is notdone, an image will be automatically chosen as either the oldest or most recent Document Linkfor the Feature (depending on the setting on the Feature Group screen), that corresponds to animage file of an appropriate size.Clicking the image will launch it in the same way as it can be launched from the Document Linkscreen.

Feature System Settings

The Feature System settings allow the defaults for some of the Feature fields to be altered.

Enter the Feature Type that has been used for the Whole Site Feature.Whole Site Fea-ture Type: Note: The whole site feature is a plot - usually numbered 9999 - which rep-

resents the whole of the Site. It is used to enable work or valuations to becarried out on the whole Site rather than to one individual Feature

Check this to set the System to refuse duplicate entries in the Feature ID field.Unique FeatureIds:

Check this to make the Feature ID field un-editable once a Feature ID hasbeen entered and the Feature record saved.

Protect ExistingFeature Ids:

If this is checked Confirm will disable the following fields on the Feature, andFeature Details screens.

Protect FeatureAdditional Data:

• Ward• Area• Cost Code• Classification• Customer• Contract Area

12 of 123Confirm

| Network Manager |

It will also update the above list of fields on a Site's Features if the currentvalues match when changed. This setting will also update the Road Statuson a Site's Interest if it matches the Classification on the Site and that valueis then changed on the Site.

When checked, Confirm will always update the fields mentioned above if anyof them are changed on a Site. This update will occur regardless of whetherthe Site and Feature values are the same or not.

Always UpdateFeature from Site:

Note: If the 'Update Sites' flag is used with any of the batch updating tools,the changes will not be cascaded back to the Features.

Check this to enable Action Officers to be designated Feature Groups. SeeAction Officer - Specialists for more details.

Enable FeatureGroup Security:

Asset Maintenance\Action Officer - Specialist

(Activity Log module)AllowMultiple Pro-posed Activities: Check this to enable several proposed Activities per Activity Class to be stored

against a Feature.

Note: If the setting is unchecked after having been checked (i.e. to preventmultiple proposed activities) all but the latest proposed activity is set to 'Can-celled'.

Supply a range of numbers which will be used to set the Plot Number for aFeature being created if there is no range specified on the Feature Group.

Plot NumberRange From / To:

Confirm will choose the first available number in the Site, in the specifiedrange. The range can therefore include numbers already used.

Enter here the number by which Plot Numbers are to be incremented whenassigning numbers to duplicated incoming Features.

Plot Number Incre-ment:

You may specify the Feature sort for lookup lists accessed from Feature pickbuttons. You may enter an expression, or use the Expression dialog to buildan expression.

Feature DisplayOrder Expression:

Features in pick-list lookups will display in the stated order (within each Site).Features with the same value as the expression are sorted by Plot Number.The expression could be a single column (e.g. the Feature Type) or somethingcomputed from multiple columns (e.g. the first character of the Feature Idplus the Start Date).

You may enter an expression, or click on the pick button to display the Expres-sion dialog where an expression may be built:

13 of 123Confirm

| Network Manager |

Double click on Functions in the Function list, and Columns in the Columnslist, to build up an Expression in the Expression field. You may also directlyedit the Expression, and add operators from the buttons on the left-hand side.

Click on OK to return the Feature Display Order Expression field.

The Feature screen will show an Identification Image, selected from theDocument Links attached to a Feature, if this functionality has been activatedfor the Feature Group.

Maximum Size forIdentification Im-age

This setting allows a limit to be set on the largest size of file that will be con-sidered, to prevent performance issues with large files.

See Feature Identification Image on page 11 for more information.

Select from:Create FeatureType..: 'None' - No Feature Type will be created to match the Feature Group being

created.

'Assets Only' - A new Feature Type, with a matching Code and Description,will be created when a Feature Group is created in the main Feature Groupform.

'Inventory Only' - A new Feature Type, with a matching Code and Description,will be created when a new Inventory Feature Group is created in the InventoryFeature Groups form. This will be set by default.

'All' - A new Feature Type, with a matching Code and Description, will becreated when a new Feature Group, or a new Inventory Feature Group iscreated.

(Inventory module)Show Attributes inInventory Labels: Where Inventory items are stored on the Inventory tab of the Feature form,

and the Inventory Items vary by attribute, you may select the format of theItem label (viewed in the left-hand pane of the Inventory tab). Select from:

'Name' - Inventory Items that Vary by Attribute will be labelled with the AttributeValue Code.

14 of 123Confirm

| Network Manager |

'Code' - Inventory Items that Vary by Attribute will be labelled with the AttributeValue Name.

ConfirmConnect® only:Display Asset No.at Start of..: When Features are displayed on a mobile device the location of the Plot

Number can be configured. When this setting is unchecked the Feature willbe displayed in the following format:

Feature_ID Feature_Type [Plot_Number]

When disabled Features will be displayed in the following format:

[Plot_Number] Feature_ID Feature_Type.

Specify the Attribute Type which will be used to identify whether a TrafficCount Feature should not have Factors applied to it's Count Data by theTraffic Count Summary Report.

Traffic CountType:

Specify an Attribute Value from the Attribute Type selected in the Traffic CountType setting. This setting is mandatory if the Traffic Count Type setting hasbeen specified.

Traffic Count TypeContinuous Value:

If a Feature has an Attribute Value which matches the Traffic Count TypeContinuous Value setting, then the Traffic Count Summary Report will notapply Factors to the Feature's Traffic Count Data.

Specify a Text Attribute Type which will be used to capture IoT Device Id inConfirmConnect® Asset Survey.

IoT Device Id At-tribute Type

On Asset Survey Complete with this attribute, if IoT device provisioning is notsuccessful in the Confirm IoT cloud platform, the attribute value in the Confirmfeature will be appended by the provisioning failure message like 'IoT devicenot provisioned'. If successfully provisioned via Asset Survey in ConfirmCon-nect, the attribute value will contain only the IoT device Id.

Note: For ConfirmConnect to be able to validate this attribute on the ConfirmIoT cloud platform, following system settings need to be configured in theConfirm database by the Confirm system administrator:

'THINGS_API_URL' - URL of the Confirm IoT cloud platform.

'THINGS_API_REGION' - Region of the Confirm IoT cloud platform.

'THINGS_API_ACCESS_KEY' - User Id to access the Confirm IoT cloudplatform.

'THINGS_API_SECRET' - User password to access the Confirm IoT cloudplatform.

Allocate Feature Type

The top part of the form (above the grey line) has a field for the entry of the new Feature Type.

The pick list references the Feature Type lookup. New Feature Types must therefore have beenentered in the lookup before they can be entered here.

The lower portion of the form defines the Features that will take on the new Feature Type.

Click on OK to display a preview list of the Features that will take on the new Feature Type. Savethe Preview to effect the change.

15 of 123Confirm

| Network Manager |

Feature - Inventory tab

(Inventory Module)

The Inventory tab is only present for those Features which have Inventory Types associated withthem. Inventory Types are created on the Inventory tab of the Feature Group.

The Inventory tab shows each relevant Inventory Type as a folder in the left-hand pane.

If a whole folder is selected, the right-hand pane will show a list of Inventory Items contained inthe folder. Double clicking an Item will display the Item details in the right-hand pane. In the illus-trated example, a lighting point has been selected, and so the details of the lighting point are dis-played on the right-hand side.

The way in which an Inventory Type behaves, and the information that may be stored with it dependson the parameters that were set for it against the Feature Group.

Allocate Condition Values

The Feature Condition batch allocate tool allows a Condition Grade to be set for an existing Ob-servation Type (Observation Types must be linked to the Features through the Feature Group).

Use the top part of the form (above the grey line) to select the Observation type, and the Gradeto assign. The Drop down lists reference the Observation type, and the Observation Parameterlookups.

The following choices are available form the drop down list:Type of Change:

'Set Grade' - The grade dropdown menu displays the Grades associated withthe selected Observation Type Parameter. Selecting one of these Gradeswill update the Score field with the value of the Grade.

'Set Score' - The Grade field will be disabled and Score enabled. By enteringan applicable value in the Score, the corresponding Grade will be set.

'Add' - Grade will be disabled and cleared. The Score will be added to theFeatures current value. The Score will not change the Grade value on thefilter.

'Subtract' - Grade will be disabled and cleared. The Score will be subtractedfrom the Features current value. The Score will not change the Grade valueon the filter.

Use the lower portion of the form (below the grey line) to limit the Features that will take on thischange in Condition grade.

16 of 123Confirm

| Network Manager |

Survey DataSurvey data may be entered into Confirm PMS using the Confirm standard type of input screen. However,survey or condition data generally consists of very large quantities of data. It is therefore appropriatethat the data is imported from the output files produced by processed machine surveys or from hand-held devices used in visual surveys. The input screen that relates to the survey data can then be usedfor editing or entering small batches of data where appropriate.

The Confirm PMS data import facilities enable the majority of survey or condition data to be enteredfrom simple text files. These import files may be Comma Separated Variable (CSV), Tab Separated,and Highway Management Data Interchange Format (HMDIF) files. CSV and Tab Separated files areeasily constructed or edited using standard spreadsheet and text editor facilities. HMDIF files can beedited in the same way but the changing format from row to row of data, depending on the record typewithin the file, makes this more difficult to work with. HMDIF is more appropriate to its primary purposefor export from one computer-based system into another.

Survey

The Survey screen contains all the details relating to a single survey and provides access to theindividual survey or condition data readings.

An 8 digit number. This is automatically entered by Confirm from the nextavailable seed number.

Survey Number:

If a number is entered by the user that does not already exist a warning isgiven.

A 30 character name or description as appropriate for each Survey. The namegiven to the survey may come from the import files, although it is possible tochange it subsequently using this screen.

Name:

17 of 123Confirm

| Network Manager |

A 20 character description as appropriate for each survey. This survey numbercan be entered for a new survey or may be imported from the import files.This number cannot be edited once saved.

External Ref.:

This is entered from the import file or from the dropdown data window formanual entry. The Survey Type must exist in the database and is set up inthe Survey Lookups. This cannot be edited once saved.

Survey Type:

There are two possible options for this field: Loaded into Edit Area and Accep-ted into Database. A survey that is loaded into the edit area can be edited -down to individual observations if required.

Survey Status:

Changing the Survey Status to 'Accepted into Database' and then clicking onthe 'Save' button on the screen will change the status flag for the data in thissurvey in the database. The status is changed using the dropdown data win-dow.

Surveys held in the edit area are not available for data processing by thesystem.

'Accepted into Database' means that:-

• APPENDIX A - It is no longer possible to edit any parts of the survey• APPENDIX B - The data will be included in data analysis.• APPENDIX C - The data is available for all reports.

If the data in the survey needs to be edited, the Survey Status can be changedback to 'Loaded into Edit Area'. Clicking on the 'Save' button again will 'move'the data back into the edit area.

Note: When survey data is imported, it is automatically placed into the editarea.

The data analyser will ignore surveys that are in the edit area. By default,some reports will not report data from surveys in the edit area.

A free form text description of virtually unlimited length. This field is used forstoring notes about the survey.

Survey Notes:

This field stores the location of video files, where these have been providedwith the survey.

File Location:

The filename and path can be entered directly or selected from the SelectFile screen using the 'Pick' button.

Document Links

Document Links can be created to point to any file in the system, allowing relevant photographsor text documents to be associated with a record.Click the Links button

todisplaythe Document Links form, listing the documents linked to the corresponding record. If there arealready Document Links associated with the record then the Links button will be highlighted with

a border.

18 of 123Confirm

| Network Manager |

The screen lists the currently linked files. The fields below the list give specific information aboutthe selected Link.

For Documents Links created from Street Works Notice, Inspections and Fixed PenaltyNotices an extra column will be displayed. This column will notify whether this document

Note:

was received via EToN or not. This column will not be displayed for Document Links onFeatures, Enquiry or Jobs.

To add new Links:Click on the New button and enter the document details .

A free text field used to annotate the file.This field is required while publishinga document from Street Works, otherwise it is optional.

Description

Enter or select the path to the required document.Document Loca-tion

Copy Button: This button will copy the fully-qualified path of the DocumentLocation to the clipboard, resolving any location prefixes.

19 of 123Confirm

| Network Manager |

A date and time for the Link. This defaults to the current system time but canbe edited freely.

Document Date

The date and time when this Link was last modified, and the User who madethe change. This cannot be edited.

Last Modified (by)

This is only available if a 'Document Store Folder' or a 'Web Service URL'has been specified in the Document Link System Settings screen.

Upload to Docu-ment Store

If this is ticked, the Document will be transferred from its current location toa central document store when the screen is saved. After uploading the fileto a central document store the 'Document Location' value will be changedto reflect the new location of the document, and depending on the type ofdocument store being used the location may be prefixed with either '$Docu-ment Store$' if the central document store is set to 'Folder', or '$DocumentURL$' if set to 'Web (PUT)' or 'Web (POST)'. This prefix will be applied to alllinks uploaded to a Folder document store, but this may not be true for a 'Web'document store if no part of the returned URL matches the 'Document LinkURL Prefix'.For more information on Document Stores see Document Link SystemSettings.

This is only available if Upload to Document Store is ticked.Delete OriginalFile after Upload If this is ticked, the local file will be deleted after it has been successfully

transferred to the Document Store.

Allow to browse to an accessible location and download the attachment.DownloadThis is only available when viewing Feature Document Links, where theFeature belongs to a Feature Group for which an image is shown on theFeature screen.

Identification Im-age

By default, the first appropriate Document Link in the list will be used as theimage. This field may be ticked to override this behaviour and choose a spe-cific image for display. The Description of the Document Link record will beupdated to show that this has been done.For more details see Feature Identification Image.

Once the details for one or more Links have been entered, click Save to store the details.

Document Location PrefixesIf a document was selected for transfer to a central document store, or was a Street Works linkthat was published, then part of the path or URL to that file is often replaced with a prefix. Thereare several prefixes in use and each has a different value.

This is used for photos uploaded from a hand held device via the Confirmconnector. Its value is equivalent to the 'Document Store Folder' settingin the Document links System Settings screen.

$Document$

This is used for documents uploaded to a central document store that isset to be a 'Folder' type. Its value is also equivalent to the 'DocumentStore Folder' setting in the Document links System Settings screen.

$Document Store$

This is used for documents uploaded to a central document store that isset to be a 'Web (PUT)' or 'Web (POST)' types. Its value is also equivalent

$Document URL$

to the 'Document Link URL Prefix' setting in the Document links SystemSettings screen.

20 of 123Confirm

| Network Manager |

This is specific to Street Works document links and is used when adocument is Published. It's value is dependant on the Organisation that

$ORG_PREFIX$

the document link is related to. The value is equivalent to the 'Attach.URL' setting in the Organisation screen, for the Organisation that thelink is related to.

To modify an existing Link:Click the link in the list and modify the Description or Document Location as required, then clickSave.

To view a currently linked file:With the required file highlighted, click on the 'Launch' button. The associated program is launchedand the file displayed.

To delete a Link:Click the link in the list, then click the 'Delete' button. The link will be removed from the list, but thefile will not be deleted.

Security of Linked items:There is a generic User Security option which can be used to selectively prevent Users from eitheradding, deleting or modifying (e.g. changing the Description or Document Location) items linkedto entities in Confirm. This option appears in the Security section of the menu when configuringprivileges on the User Security and Group Security screens.

Document Links in Street WorksThe document links feature within Street Works has extended functionality. Refer to the documentlinks section of the Street Works help for more information.Street Works\Document Links

Problems Uploading to the Document StoreProblems may be encountered when using the 'Upload to Document Store' setting, especiallywhen using a web service document store, where the document may travel across a network toan external application.If problems do arise then any changes made to the document link details, such as dates and de-scription, will still be saved to the Confirm database, however the document link will not be updatedand the document will remain in its original location. It will not be deleted, even if 'Delete OriginalFile after upload' was selected.Uploading to a Web Service is highly dependant on external applications, and it is not possiblefor Confirm to interpret all of the possible errors that may arise once the document is sent out. Ifan error does occur then Confirm will display "Failed to upload - the following error was returned

21 of 123Confirm

| Network Manager |

by the Web Service:" followed by the error message that is returned to it from the external applic-ation.

Survey Section

Clicking on the 'Detail' button in the Survey window will display Survey Section screen.

These fields are automatically completed from the parent Survey screen.Survey, Name,Ext. Ref.:

These can be entered using the 'Pick' buttonsStreet, Label,Locn., Seq. No:

or known reference codes manually or from reference codes in the importfiles.

The date at which the survey is carried outStart Date:

The date at which the survey is completed.End Date:

Note: Start and End date are normally the same even for machine surveysthat may have taken place overnight.

The date at which the survey data is no longer valid either due to subsequentSurveys.

Expiry Date:

22 of 123Confirm

| Network Manager |

Entered manually from the drop down or by code in the import file. The optionsare forward or reverse. A forward survey is one carried out in the normal dir-

Original SurveyDirection:

ection of the section i.e. from chainage 0 to the end chainage. A reversesurvey is carried out in the opposite direction i.e. from the end chainage tothe start chainage 0.

Entered manually from the drop down or by code in the import file. The optionsare Master or Partial. This data connects to the 'Action' button and the option

Master or PartialSection:

to Merge in Partial Sections. When this option is selected on aMaster SectionConfirm checks through other surveys for candidate survey sections ( thoseLoaded into the edit area only). A list of all survey section marked as partialwith the same survey section and of the same survey type is then displayed.Selecting a partial section from this list moves that partial section from itsoriginal survey to the survey containing the Master Section.

Note: The Action Button is only enabled when the survey is Loaded into theEdit Area

The Action Officer for the survey. This can be entered manually using the'Pick' button and associated Action Officer Lookup or by code from the importfile.

Officer:

Note: This is not a mandatory field and can be left blank.

The length of the section held under section information in the database,which cannot be modified in this screen or from an import file.

Section Length:

This field is in 6.2 format, i.e. 6 numbers before and 2 numbers after thedecimal point. This is the start chainage on the survey for the survey obser-vations corresponding to the start of the section.

Chainage From:

Typically for a machine survey observations are taken over a route that willcomprise of many street sections. The survey data will be held against arunning chainage that has to be mapped on to the Confirm street section.

This field is in 6.2 format, i.e. 6 numbers before and 2 numbers after thedecimal point. This is the end chainage on the survey for the survey observa-tions corresponding to the end of the section.

To:

A free form text description of virtually unlimited length. This can be enteredmanually or imported from file.

Comments:

The list at the bottom of the screen shows all the Observations made on the selected SurveySection.

If any of those Observation records are of an Observation Type that can have additional valuesstored against it, a ‘Parameters’ heading will be shown to the right of ‘Value’ and those valueslisted underneath.

Survey Section - Action Button

The list shows all Partial instances of this Section on other Edit Area Surveys of the same type asthe current one.

The selected Section will be moved into the current Survey and merged with the current Sectionwhen committed.

23 of 123Confirm

| Network Manager |

Survey Section - Detail Button

Survey ObservationClicking on the 'Detail' button on the Survey Section screen displays the Survey Observationscreen.This screen displays the details of the individual observations, brief details of which are viewed inthe window at the bottom of the Survey Section screen.

These fields are automatically completed from the parent Survey screen.Survey, Name,Ext. Ref.:

These fields are automatically completed from the parent Survey Sectionscreen.

Street, Label, Seq.No.,Locn:

Selected from the drop down of defined Feature Groups or imported from thecode in the import file.

Feature Group:

Selected using the 'Pick' button and Lookup of defined Observation Types orimported from the code in the import file. Only the observation types applicableto the survey type are displayed.

Observe Type:

This is automatically completed from the data held against the ObservationType.

Parameter:

This is automatically completed from the data held against the ObservationType and includes both the units and the unit type.

Units:

The section start chainage for the Survey Observation.From:

The section end chainage for the Survey ObservationTo:

The cross section position is selected from the dropdown data window ofdefined types or imported from the code in the import file.

XSP:

The option is selected from the drop down of defined types or imported fromthe code in the import file.

Option:

24 of 123Confirm

| Network Manager |

Note: The Option is dependent on the Observation parameter assigned tothe Observation Type in the Survey Lookups.

The value of the observation where appropriate either entered manually orimported from the import file.

Value:

A free form text description or comment of virtually unlimited length. This canbe entered manually or imported from the code in the import file

Comment:

An Observation Type may be able to have additional values stored against it, if in the Survey Typescreen others have this one specified as their Parent Observation Type. In this case, the namesof the relevant additional Observation Types will be listed under the ‘Comment’ field, with a numericvalue field next to each one.

Entry Button - Survey Section

The Entry screen provides the means of entering values where there are multiple observations atthe same chainage.

Click on the 'Entry' button to display the Survey Data Entry form:

Batch Button

Clicking the 'Batch' button displays a pop-up menu. Select from:

'Add Sections' - A filter will be displayed to allow a selection of Sections to be added to the Survey.

'Add Whole-Length Observations' - Two filters will be displayed:

The first is to allow the selection of Observation Type, Feature Group and the XSP codes.

25 of 123Confirm

| Network Manager |

The second is for selecting the Section and XSP Combinations Observations will be added. Theselected Observation details will then be created for the selected Feature and XSP combinationswith the Observation covering the entire Section length.

26 of 123Confirm

| Network Manager |

Network Utilities

Import Utilities

Data may be imported into Confirm using Import Utilities. Each Utility requires a tab separated, orcomma separated text file which must conform in layout to an Import Specification. Import specific-ations are available from Confirm, and from the Confirm User Support section on the Confirm webpage.

The available Import Utilities are:

See Confirm PMS Import Specification.Import SurveyData: The import utility will import data against a Section that has been end dated

which was live at the time of the Survey and will pass this data down to des-cendent Sections of the now dead Section. Confirm will not be able to passthis data down if the Section has been Split or Merged in a way that theLengths can no longer be matched. A warning will be generated when SurveyData is imported against a Section that has been end dated.

A Survey HMDIF file can be produced using the Save As option from anyscreen or report showing Survey data. Irrespective of the data in thescreen/report, only data from a single Survey can be included in the file. Thereare two variants of the format:

• HMDIF Survey - this option saves the full Survey including all (currentlylive) Sections.

• HMDIF Survey Section - This option is only available where Section leveldata is shown in the screen or report. It saves only those Sections withinthe Survey which are also shown in the data.

See Confirm PMS Import Specification.Import NetworkData: A Network HMDIF file can be produced using the Save As option from any

screen or report showing Linear Features.

See Confirm PMS Import Specification.Import InventoryData: Import Type:

Select from:

• Full - This option will End Date all Inventory for the surveyed Section andreplace it with the Inventory in the import file.

• Partial - This option will check for overlaps in the data and allows the addi-tional Inventory to be added to the Sections within the import file.

• Full by Inventory Type - The 'coverage' of a Survey is derived from theimport file on a per Section basis. If any items of a particular Inventory Typeare being imported for a Section, then all existing items of that Type on thatSection are End Dated.

An Inventory HMDIF file can be produced using the Save As option from anyscreen or report showing Linear Features. There are two variants of the format:

• HMDIF Inventory - the file will contain all Inventory Items for the selectedFeature(s).

• HMDIF Inventory Type - this option is only available where Inventory leveldata is shown in the screen or report, specifically depending on the presence

27 of 123Confirm

| Network Manager |

of the Inventory Type field. It saves only records of Inventory Types that areshown in the data, but will include all Inventory of those types. So for ex-ample if the report shows Carriageway the file will contain all Carriagewayitems for the Features in the report.

See Confirm Import Specification.Import Observa-tion Lookups:

See Confirm Import Specification.Import NetworkTranslation:

See Confirm Import Specification.Import SurveyType:

See Confirm - BS7666 Level 3 Gazetteer Compiler - Network Cross-ReferenceFile Import Specification - Document Reference CAH-6-129

Import NetworkCorrelations:

Field Format, Restrictions and Details

Field Format, Restrictions and Details• APPENDIX I - Fields containing an invalid character will cause an error during import.• APPENDIX J - Fields requiring uppercase characters but containing lower case or mixed casecharacters will be automatically converted to all uppercase during import.

• APPENDIX K - Fields that must be unique or Key Fields will be ignored if they are duplicatedand an error generated during import.

• APPENDIX L - Imported fields that reference Lookup tables must exist, i.e. have correspondingentries, in the database or appropriate parent Lookup table, if not an error will be generatedduring import. In certain circumstances, the appropriate Lookup record will automatically begenerated from the field using the field code for both the Lookup table code and description

Note: See the Survey & Condition Data Import Specifications Document for specific details oneach import files formats, headers and special restrictions.

Survey Data Entry - Survey Data Lookups

As outlined above the appropriate Lookup Tables have to be populated prior to the import of datafrom the files. This must be done before file import of the Survey data or errors will occur duringimport that will have to be corrected before the import can be completed and saved. i.e. no 'Onthe fly' entries can be made during the import process. The Survey Lookup files have to be popu-lated manually although the codes associated with any default Rules and Parameters sup-plied/loaded into the database will already be present.

The Survey Data Lookups that must be populated prior to the import of the Network Section filesare as follows:-

1. Observation Type2. Observation Parameter3. Observation Impact4. Survey Type on page 895. Action Officer6. Notebook Code on page 947. Network Import Settings on page 798. Observation Import Codes on page 959. Network System Settings on page 8010. Survey Seed Numbers on page 97

28 of 123Confirm

| Network Manager |

Import Survey Data

The Survey Data is imported from three delimited text files or a single HMDIF file. The delimitedimport files can be either CSV or Tab Separated, but the two types cannot be used in the sameimport operation. The file headings must be included and the data columns can be in any order.The file types, field codes (headings) and field formats for each of these are given in the ImportSpecification.

The Import File Type is selected from the drop down data window.Import File Type:

When the import file type HMDIF is chosen only one file is required for import.

If Import File Type of Comma Separated or Tab Separated is chosen thenthis screen provides the facility to import the separate delimited text files for:Surveys, Sections, and Observations.

The Survey Type is selected from the drop down data window of availabletypes and is only required when the using the 'multiple Value column import'feature.

Survey Type:

If the Survey Type is specified, the system can import multiple ObservationTypes on each length. This works for the first 10 Observation Types withinthe Survey Type, in the order they are defined against the Observation Type.

The Import Files section of the import filter is used for specifying a singleHMDIF import file or the multiple ASCII type files.

Import Files:

Surveys This is the file containing the basic Survey information or for HMDIFimport the HMDIF file containing all the information for Survey, Section andObservations.

Sections - Observations These are the files containing the information asdescribed by their respective headings.

To select the individual files click on the 'Pick' button at the end of the filename data window for each different type of file. This displays the Select Filewindow from which the file is selected in the usual way.

The Import ProcessWhen the required files have been selected, they are imported by clicking on the 'OK' button inthe top right corner of the Condition Import Filter.The files are then read into the system and the data is checked and validated by the program.When the data has been checked the Inventory Import screen displays the File Import Summary.

29 of 123Confirm

| Network Manager |

This allows the user to check that the correct import file has been used and that the expectednumber of records have been imported. Options are also available for printing and exporting thereport as with all Confirm report screens. If the data is accepted then the 'Save' button is clickedand the data is then saved to the database. Small progress windows display the various elementsof data being saved as the process is carried out.Importing the file or files produces the File Import Summary. This is the standard Network importscreen whether using HMDIF or delimited text files. The report summarises the following informa-tion:-

In this case - ConditionImport Type

Ready - This indicates the import verification process has not found any errorsand the data is ready to import into the database The 'Save' button is also

Import Status

shown in full. When errors are present the 'Save' button is greyed out andrecords cannot be saved to the database.

Only the file name of the Sections file is shown even when multiple files areimported.

File Name

The record identifier describes the main record type imported from each rowin the file or files.

Record Identifier-Number of Re-cords The number of records for each is the count of the records ready for import.

This should match the number of rows in the file for this type of record lessheader rows for CSV & Tab Separated files.

Clicking on the 'Save' button results in the records being written to the database with the corres-ponding Updating Database screen which shows progress.

Survey Import Error ReportsConfirm PMS provides extensive error reporting facilities through the File Import Error Report.This report is automatically generated whenever the validation process comes across an error.The error report provides information on the line number, the record type, the item label and detailsof the error.The initial validation check is on the record type header codes. Where an error is found in thesecodes a warning screen is displayed. An example of such a screen is shown below.

This allows the import process to be abandoned immediately or for the process to be continuedwith the remaining validation of the import file. The error may be non-fatal so caution needs to beexercised to ensure that the data is not saved to the database with errors or missing information.If errors are detected by Confirm when importing data, one of two things will occur. If the errorsdo not prevent the data being imported, Confirm will show warning messages. Warnings may beignored and the data saved. If the errors would prevent the data being imported, Confirm will displayan error message. When this occurs, you will be unable to save the data, and the import files willneed to be corrected before the data import is repeated.When the files are imported, the Condition Data Import screen displays the File Import Summaryas shown below.

30 of 123Confirm

| Network Manager |

As can be seen, there has been several warnings and errors reported. The save box on the reporthas also been greyed out, meaning that the imported data cannot be saved to the database andthe Import Status is 'Failed'.This is accompanied by a screen requesting whether the user wishes to view the error report.Selecting Yes will display the File Import Error Report.Note: If No is selected the import must be repeated to be able to view the File Import Error Report.The report shows the details on the error. From this, it can be determined in which files and onwhich lines that the problems exist. The import files can now be examined and the problems rec-tifiedError reporting may show both non-fatal warnings and fatal errors. The difference between thetwo is that a warning will not cause Confirm to prevent the user from saving the data whereas anerror will.For convenience, once the File Import Error Report has been closed after errors or warnings havebeen reported, the system returns to the File Import Summary report. Clicking on the Re-RetrieveRecords button returns to the Import Filter screen. Files can then be corrected and re-imported.Note: care should be taken to avoid minimising the Error Report screen since no other action canbe taken in Confirm until this screen is closed.

Examining and Reporting Survey DataOnce the survey or condition data has been imported and saved into the database then it can beviewed in several different ways.

• APPENDIX D - The data may be examined (and edited) using the Survey input and editingscreen.

• APPENDIX E - It may be viewed in one of the several available reports.• APPENDIX F - It may be exported to spreadsheet programs to graph and chart.• APPENDIX G - It may be exported to statistical analysis programs.• APPENDIX H - It may be exported to strip diagrams or a GIS for visual representation and re-porting.

Condition Data Import TipsNetwork not definedThis will occur if the contractor providing you with the survey data has given an entry for the networkin their files, and this entry does not tie up with a named network in your database. There are anumber of solutions to this problem.If the data you are importing is correctly referenced for your network (i.e. Network Translation isnot required), you can create a new network (Preparation, Network Manager, Network Lookups,Network). Give the new network the appropriate code to tie in with that used in the data to be im-

31 of 123Confirm

| Network Manager |

ported. Next find your current base network (Base Network ticked) and clear the Base Networkbox. Save this change, then move back to your new network, tick the Base Network box and save.You can now import the data without further changes. Remember to return the original networkto being the base network after the import, and also note that you will have to clear the BaseNetwork box on one network before you can set it on another.Once you have created names for other networks, the next time you wish to import data that refersto that network, you can simply change the network that is set as the base network to that one.Note that this method is only used when no network translation is needed - where translation isrequired, the base network should not be changed.As an alternative to switching the base network in Confirm, and again only if the network does notrequire translation, you could carry out a search and replace in the import file(s). Load the file intoa text editor (i.e. Wordpad) and search for occurrences of the name given to the network by thecontractor and replace it with the name of your base network. The import should then proceedcorrectly. Note that whilst this may be quicker if there are only one or two files to import, themethod above will be far easier if a number of files are to be imported. Once the new name hasbeen created if subsequent data is received referring to the same network importing it will onlyinvolve changing the Base Network setting. It should also be noted that care must be exercisedwhen using a search and replace, as data other than the network may match and therefore bereplaced. For this reason, the search and replace method is not recommended.Finally, if the network does require translation, you will have to set up the new network and createa translation for it. Note that a network that is translated to the base network should not itself beset as the base network. For more details on network translations, refer to the Network Fundament-als Input section in the Network Setup and Maintenance training material.Setting up OfficersSome import files may contain a reference to the officer carrying out the survey. This is often ac-tually used to indicate the contractor. When you have to import a file with the officer field in itcompleted, you will need to ensure that that officer exists in Confirm's list of officers, and has accessto the Work Group / Contract Area in which the survey took place. To access the Officer lookup(actually called Action Officer in Confirm), choose Preparation, Asset Maintenance, MaintenanceLookups, Action Officer. This will bring up a form allowing you to enter a code (this is what will bein the survey import file) along with Name, Telephone numbers etc as well as the Work Group.The required fields are Code, Name andWork Group. Once details have been entered, and saved,it will be possible to import survey data attributed to that officer.

Aggregate Measurements

This utility will aggregate the Measurements held against Inventory Items and apply a total to theFeature.

The aggregation is of the measurements held in the 'Measurement' field(s) of the specified Inventoryitem. The Inventory Group to which the item belongs must have a Primary Measurement Typespecified, which is the same as a Measurement Type applied to the Feature.

The Inventory Group Primary Measurement is applied in the Inventory Feature Group .

Feature Measurement Types are applied through the Feature Group.

32 of 123Confirm

| Network Manager |

Use the upper part of the form to define the Feature(s) that will have measurements aggregated.

Use the lower portion of the form to specify the Inventory Item(s) which will contribute to the ag-gregation.

Click on Ok to view the preview. The Aggregation will total Inventory Primary Measurements, andapply the total to the same Measurement Type in the Feature. So if Inventory Items all carry thePrimary Measure: 'Length', then the total of all these measures will be applied to the MeasurementType 'Length' on the Feature.

Click on 'Save' in the preview window to save the aggregations.

Node Reference Batch

Module 4050 (LRPs)

The Node Reference batch will realign all Inventory Data, or Observation Data, which referencesa Node, from that Node to another.

Use the top part of the form to enter details of the old Node.

Data Type: select Inventory, or Observation, from the drop down list to indicate which type of datashould be re-referenced.

Use the lower part of the form to select the New Node.

Note: both the old Node and the new Node should already exist on the Section.

33 of 123Confirm

| Network Manager |

Click on OK To run the utility, and save the preview to carry out the re-referencing.

Create Inventory Links

Where maintained Features do not exist in the Confirm database, they can be generated fromInventory Items. This utility will create one Feature per Inventory Item with the following information:

• The primary measurement of the new Feature will be set from the Inventory Itemsmeasurement.• The Feature Location will be created from Section Label plus chainage and XSP of the InventoryItem.

• The Survey Date will be the Inventory Items Survey Date.

Delete inventory

Inventory Items may be batch deleted from Sections using the Delete Inventory utility

Use the filter fields to define the Inventory Items to be deleted.

Click on OK to run the utility. A preview report will list all the Inventory Items that will be deleted.

Click on the 'Delete' button to continue and delete all the listed items. Click on 'Close', and on 'No'in the 'Do you wish to Save' dialog, to close without deleting Inventory.

Inventory Attribute Dependent Update

The Inventory Attribute Update utility will update Inventory Attributes in line with the Attribute de-pendencies set up in the Attribute Type Lookup.The utility will not add Attribute Types to Inventory Items, nor carry out any updates other thanthose dictated by the Attribute Type dependencies set up in the Attribute Type Lookup.Use the top part of the filter to restrict the selection of Inventory Items for update. You may leavethe top section blank to update all Inventory Items.The bottom part of the filter screen is for the selection of Attribute Type Values to be updated.

You may select an Attribute from the drop down list. Only those AttributeTypes with a Dependent Attribute Type can be updated. Hence, only thesewill be seen in the drop down list.

Attribute Type:

You may specify a value to restrict the update to the attributes currentlyholding that value.

Attribute Value:

This will be entered automatically by reference to the Attribute Type if youhave entered on in the Attribute Type field. Otherwise youmay pick an Attribute

Depend On Type:

34 of 123Confirm

| Network Manager |

Type from the drop down list to restrict the update to the attributes dependenton that attribute typeYou may specify a value to restrict the update to attributes dependent on theabove attribute type, which have that value.

Depend On Value:

Select from:'All Attribute Values' - To update values without reference to the current value.

Include:

'Disallowed Attribute Values' - To update only those values that are disallowedaccording to the Dependency rules set up for the Attribute Types.'Allowed with Warning only' - To update only those values that are flagged togive a warning in the Dependency rules set up for the Attribute Types.'Disallowed and Allowed withWarning' - to update all values that are disallowedor flagged to give a warning in the Dependency rules set up for the AttributeTypes.

Click on OK to run the utility and display the preview.

35 of 123Confirm

| Network Manager |

Network Reports

Section Overall ReportProvides an overall report on the Features including attributes and their values.

Street Section Condition Summary

The Street Section Condition Summary provides a report summarising the network condition by Obser-vation Type and Parameter for individual Street Sections and the associated Feature Groups.The report will list Data Analysis and/or Survey records for a single Survey and Data Set or all Surveysand Data Sets at a time. Use of the Street and Named Selection options on the filter are recommendedfor the avoidance of excessively large reports.Note: Survey status must be selected as either 'Loaded into Edit Area' or 'All' for data to be returned.A similar report, grouped at Network level is available by running the Network Condition Summary.

Street Section Current Condition

Completing the appropriate fields to restrict the report listing then clicking on the OK button commencesthe report processing. In order to report only on structural condition index the correct surveys and ob-servation type should be selected in the filter.

Multiple Observations List

This report can be used to provide a listing of survey observations from either a single survey or anumber of surveys or analyses.

Section Survey Need ReportThis report is used to highlight Sections that have not been surveyed since a provided cut of date.Sections which have been completed will be displayed with the Survey Type and date that the Surveywas completed.

External Network Section Current Condition

This report allows reporting on the Current Condition of External Network Sections.

Network Summary by...The Network Summary reports by Type, Attribute, Condition provide a means of viewing a summaryvalue of the total primary measurement for all Features that meet the specified criteria. An overall totalis shown as well as one for each Type, Attribute or Condition.

Inventory SummaryThis report provides a summary report of Inventory. It displays the total quantity of Inventory per FeatureType.

36 of 123Confirm

| Network Manager |

Inventory Summary by SectionThis report provides a summary report of Inventory grouped by Feature. It displays the total quantity ofInventory per Feature Type.There are two report levels available:'Summary' - This displays the proportion of a Feature Type in relation to other Feature Types of thesame Inventory Type.'Detailed' -When this is selected the report will show the data at XSP level but does not show theproportion of the Feature Type.

Unlinked Inventory Feature ListThis report provides a means of identifying Features of a Type that could be 'Referenced' by Inventorywhere no such reference exists.

Unlinked Inventory Item ListThis report provides a means of identifying Inventory items of a Type that could be linked to a Featurewhere no such link exists.

Survey Inconsistency ReportThis report highlights inconsistencies between the imported Survey Data and the Network Inventorythat is in the Confirm database.

Inventory Attribute Dependency Exceptions Report

The Inventory Attribute Update utility will update Inventory Attributes in line with the Attribute depend-encies set up in the Attribute Type Lookup.The utility will not add Attribute Types to Inventory Items, nor carry out any updates other than thosedictated by the Attribute Type dependencies set up in the Attribute Type Lookup.Use the top part of the filter to restrict the selection of Inventory Items for update. You may leave thetop section blank to update all Inventory Items.The bottom part of the filter screen is for the selection of Attribute Type Values to be updated.

You may select an Attribute from the drop down list. Only those Attribute Typeswith a Dependent Attribute Type can be updated. Hence, only these will be seenin the drop down list.

Attribute Type:

You may specify a value to restrict the update to the attributes currently holdingthat value.

Attribute Value:

This will be entered automatically by reference to the Attribute Type if you haveentered on in the Attribute Type field. Otherwise you may pick an Attribute Type

Depend On Type:

from the drop down list to restrict the update to the attributes dependent on thatattribute typeYou may specify a value to restrict the update to attributes dependent on theabove attribute type, which have that value.

Depend On Value:

Select from:'All Attribute Values' - To update values without reference to the current value.

Include:

'Disallowed Attribute Values' - To update only those values that are disallowedaccording to the Dependency rules set up for the Attribute Types.

37 of 123Confirm

| Network Manager |

'Allowed with Warning only' - To update only those values that are flagged to givea warning in the Dependency rules set up for the Attribute Types.'Disallowed and Allowed with Warning' - to update all values that are disallowedor flagged to give a warning in the Dependency rules set up for the Attribute Types.

Click on OK to run the utility and display the preview.

Inventory Summary Report

This report shows a summary of Inventory quantities, with subtotals shown for user defined groupsof data.

It can be used in the UK to provide financial information for asset management. For further detailssee UKPMS Financial Information.

The filter screen for the report is divided into three sections. The top section allows Feature selectioncriteria to be entered. The centre section is used to select the Inventory data to be included. Thebottom section allows the user to specify how data in the report is to be grouped, by specifyingup to three criteria to define the groups.

The report displays a row for each group within each Inventory Type. For each combination, theinformation described below is shown.

The ‘Network’ values summarise Feature information. These values are shown for an InventoryType if all Features can be categorised unambiguously. If ‘Inventory Classification’ or ‘Construction’has been chosen to define the groups, there could be different values for Inventory Items withinthe same Feature. Hence if either of these fields is chosen the Network values are only shown ifall Items of an Inventory Type have the same value.

• Total Number: The total number of Features in this group.• Total Length: The total length of these Features.

38 of 123Confirm

| Network Manager |

The ‘With Inventory’ values summarise those Features with Inventory Items. These are also shownonly where a Feature can be categorised.

• Total Number: The total number of Features in this group with at least one Inventory Item ofthis Inventory Type.

• Total Length: The total length of these Features.

The ‘Inventory Items’ values summarise the actual Inventory data:

• Total Number: The total number of Inventory Items of this Inventory Type in this group.• Total Length: The total length of these Inventory Items.• Total Area: The total area of these Inventory Items.• Average Width: The average width of these Inventory Items.

The Average Width calculation depends on the Inventory Type as follows:

• Carriageway: Total Area / Total Length of Features with Inventory Items.• Others: Total Area / Total Length of Inventory Items.

A row of summary values is also shown for each Inventory Type.

Network Survey Coverage Report

This report is used to summarize how much of the network has been surveyed in a chosen daterange. The top half of the filter screen allows Feature selection criteria to be entered. The bottomhalf is used to select the Survey data to be used.

Note: "Feature Group Like" refers to the Feature Group of the Survey Observations, not the Fea-tures themselves.

The report can group the results in different ways by selecting the appropriate 'Report Type'. Detailsof the different report types are as follows:

1. Finance Year Breakdown

The report displays a list of all the Finance Years wholly or partially contained in the entereddate range, with a summary of Survey coverage information for each. For each year the reportshows the number and length of surveyed Features. There is also a summary row showing thenumber and length of Features surveyed at any time in the entered date range.

For each Finance Year, the following information is shown:

• Observation Length: The total length of Observations for the Features in this Finance Year.If a feature is surveyed twice in the Finance year then this column will show only the latestsurvey.

• Number Surveyed: The number of selected Features with a Survey in this Finance Year.The percentage of all selected Features that this represents is also shown.

• Length Surveyed: The total length of these Features, and the percentage of the total lengthof all selected Features that this represents.

2. Footway Hierarchy Breakdown

The report displays a list of Footway Hierarchy values, with a summary of Survey coverageinformation for each, as well as the total number and length of Features surveyed.

For each Footway Hierarchy, the following information is shown:

• Network Count: The number of selected Features in this Footway Hierarchy.• Network Length: The total length of these Features.• Observation Length: The total length of Observations for the Features in this FootwayHierarchy.

39 of 123Confirm

| Network Manager |

• Number Surveyed: The number of selected Features with a Survey in this Footway Hierarchy.The percentage of all selected Features that this represents is also shown.

• Length Surveyed: The total length of these Features and the percentage of the total lengthof all selected Features that this represents.

The report can be used to provide Survey information on parts of the network, but its primarypurpose is to produce theUKPMS Footway Network Survey Coverage report. For further detailssee UKPMS Indicator Reports.

It can also be used in the UK to provide financial information for asset management. For furtherdetails see UKPMS Financial Information.

Network Survey Coverage Detail Report

This report is similar to Network Survey Coverage report but shows more detailed results. Theresults are broken down by each Observation type for each Footway Hierarchy.

The filter is divided in three sections where the top section allows Feature selection criteria to beentered. The middle section is used to select the Survey data to be used and the bottom part toselect Observations to report on.

The report displays selected Observation values for all Footway Hierarchies. For each FootwayHierarchy the report shows:

• Surveyed Length: Length of sections surveyed.

Then within this, for each of the chosen Observations the report shows:

• Length: The number of selected Features with a Survey within the specified date range. Thepercentage of all selected Features that this represents is also shown.

• %: Percentage this Observation represents of the Length Surveyed.• Average: Average value for this Observation.• Indicator: This column shows totals for each Observation for which Indicator checkbox wasticked. The Percentage of lengths here is the headline indicator and is highlighted in bold.

The report’s primary purpose is to produce the UKPMS Footway Network Survey Headline In-dicator report. For further details see UKPMS Indicator Reports.

40 of 123Confirm

| Network Manager |

Network LookupsThe Network Lookups section is used to pick each of the options required to populate the databasewith the base Network information. The use of each library will be described in detail. For those lookupswhich are not covered by this manual, please refer to the Asset Register manual.

Node

Nodes can be entered 'on the fly' i.e. as they are required during entry of a PMS section or theymay be imported from existing data. For manual entry of a larger number of nodes, enter them asa batch using the Node input screen.

Nodes can also be imported from a pre-prepared file, which is dealt with under the Data Importtopic.

New Nodes are entered directly using a blank input screen. A blank screen is automatically selectedwhen the Node screen is started using the Node icon on the Network Lookups branch. Alternatively,a blank input screen can be selected when editing using the 'Clear/New' button.

The node reference number may be up to 30 alpha/numeric characters long,this should be the standard node number used for referencing the network.

Node:

A free form text description of virtually unlimited length used to enter the de-scription of the Node, this may be as simple as Start, End, Junction etc. More

Comment:

informative descriptions, particularly in relation to local features, will be helpfulfor future reference as well as time saving in the ongoing collection andhandling of data.

The coordinates of the Node as eastings and northings may be recorded inthe appropriate boxes. This field is in 8.2 format, i.e. 8 numbers before and2 numbers after the decimal point.

Easting andNorthing:

Connection Mode

The Connection Mode input screen allows for the definition of a new type of node, its method ofconnection and the opposite or reverse connection. Connection Mode is not currently used forany processing within the PMS system however the Connection Mode and Opposite Mode mustbe defined to comply with Confirm requirements for possible future functionality. For instance,connectivity of sections can be established if the same node is defined as an end or start nodeon a section and a junction node on another.

41 of 123Confirm

| Network Manager |

For an intermediate type of node e.g. 'Junction' or 'Speed Sign' the connection mode and oppositemode are the same.

A unique code of up to 4 alpha/numeric characters and a 30 character descrip-tion as appropriate for each Connection or a suitable description for the nodetype being created, e.g. Junction.

ConnectionMode:

A unique code of up to 4 alpha/numeric characters and a 30 character descrip-tion as appropriate for each Connection or a suitable description for the nodetype being created, e.g. Junction.

Opposite Mode:

Cross Sectional Position (XSP)

Cross Sectional Positions define the various points on any cross section for a particular propertysuch as a lane edge, kerb, footpath, etc. Confirm PMS has the a default set of cross sectionalpositions defined as standard in the database. Cross Sectional Positions are used by the ConfirmData Transformation Engine in PMS processing therefore it is essential that the defined XSP codesmatch those expected by the processing systems rules and parameters.

Cross Sectional Positions may be defined to have vertical as well as horizontal positions to allowfor items that may be above or below the carriageway. Vertical components are not currently usedin PMS processing. However a user can extend the rules and parameters for local conditions toinclude such items as buried services, foundations, drains, etc. below the carriageway and struc-tures, signage, street furniture above the carriageway that can effect the cost of works or the viab-ility of applying a particular treatment.

42 of 123Confirm

| Network Manager |

A unique code of up to 6 alpha/numeric characters plus a 30 character de-scription as appropriate for each XSP in the adjacent box to the right.

XSP Code:

A unique code of up to 6 alpha/numeric characters plus a 30 character de-scription as appropriate for each Reverse XSP in the adjacent box to the right.

Reverse XSP:

This is the equivalent XSP to that entered as the XSP Code when handedabout the centreline position. e.g. The opposite of CL3 - Permanent Left Lane3 is CR3 - Permanent Right Lane 3.

A unique code of up to 6 alpha/numeric characters plus a detailed descriptionin the adjacent box to the right.

Minimal XSP:

The standard codes for Minimal XSP, for use where minimal XSP referencingis used, are L (Left), C (Carriageway) or R (Right). Minimal XSP allows theuser to set up a useable system without collecting detailed inventory informa-tion, however, the accuracy of the results will reflect the lack of detailed in-formation being processed.

Confirm PMS allows further user defined minimal XSP's to be entered if re-quired for user defined processing. (NB. These will not conform to the defaultstandard and therefore will not be used in processing of the standard rulesand parameters set).

This is the level of detail for the cross sectional position model and is selectedfrom the drop down. It is defined as either Full or Minimal, these are pre-set

Detail Model:

in Confirm and are not user definable. The full cross sectional position modeldescribes the position of each item being referenced in the inventory in termsof its location relative to the centreline of a section. Theminimal cross sectionalposition model is a simplified system that describes the item in terms of onor off carriageway and to the left or right of the centreline.

This is defined as either 'Transverse' or 'Not Transverse' and is entered fromthe drop down, these are pre-set in Confirm and are not user definable.

Transverse:

Transverse XSP's enable the referencing of items such as a kerb or footpathat the end of a cul-de-sac, or similar items that run parallel to the line of thecross section i.e. perpendicular to the section centre line.

This can be defined as either 'On Carriageway' or 'Off Carriageway' and isentered from the drop down, these are pre-set in Confirm and are not userdefinable.

Carriageway:

Lane Offset is an arbitrary figure to locate that particular XSP horizontally inrelation to the other XSP's. This figure is used by Confirm in spatial represent-

Lane Offset:

ation and therefore only the relative position in relation to other XSP's needsto be considered. The lower number will represent a position closer to thecentreline. Minus numbers will indicate right offset and positive numbers willindicate a left offset. Using numbers with a separation of say 10 will allow foradditional XSP's to be placed in between those currently defined withouthaving to renumber all the XSP's. Confirm will use the widths entered for aparticular cross section or the default width if not specified.

Unit of Measure

The Unit of Measure lookup should contain a list of all the Units of Measure that will be requiredwithin Confirm. The library can be added to as units become necessary.

43 of 123Confirm

| Network Manager |

The list would usually comprise the standard metric measures such a Metre and Square Metre,an Hour - for hourly paid work, a Pound (£) for raising work for which a price has been quoted anda Number for counting items.

Up to four alphanumeric charactersCode:

Up to thirty charactersDescription:

Checked by default, to indicate that Items priced using this measure (e.g. -per Square Metre), may be uplifted when a Rate Uplift is applied.

Rate Uplift:

Note: usually only one item is NOT checked for Rate Uplift: the Unit ofMeasure for a currency unit. An SOR item representing a unit of currency,which is used to directly apply a value to work, should not suddenly acquirea greater value.

Check these boxes if you wish to used the relevant components to entermeasurements. If you checked Length and Width for the Unit 'Square Metre'

This Unit uses:

for instance - you would be required to enter Length andWidth when enteringthe Measurements for a Job. If you prefer to work directly in Square Metres(and not Length and Width) then do not check these boxes.

Measurement Type

The Measurement Type defines the Measurements that will be taken for a Feature, with the Unitof Measure used for the Measurement.Using Measurement Types allows several measurement to be entered against a Feature whichall use the same Unit. So, for instance, Height, and Spread can be entered against a tree - bothmeasured by the Metre.Measurement Type can also be used to define work by defining the Measurement to which workwill be done. So a flowerbed can have a measurement for 'Mulching Area, which is distinct fromthe 'Overall Area'.Measurement Types are therefore used to define the Feature Measurements, and, possibly, todefine the work that will be carried out.

Up to four alphanumeric charactersCode:

Up to thirty charactersDescription:

Select, from the Drop down list, the Unit of Measure used to take this Meas-urement. The drop down list references the Unit of Measure Lookup.

Unit of Measure:

44 of 123Confirm

| Network Manager |

Optionally specify a Device Data Key.Device Data Key:ConfirmConnect® user whose data security group includes view access tothis data security key will be able to view this measurement type as an attributeon their Survey tasks.

Leaving this field blank will allow all users to view this date type inConfirmConnect®.

Note:

Attribute Types

(Extended Attributes)Attribute types can be used to describe any aspect of the Feature that can be set as a type witha range of values. Attributes are set up as Types, each with a range of possible Values.(Asset Valuation Module)Where the Asset Valuation Module is present, Text Attribute values may be used to factor theReplacement and life values for Features that carry these Attributes and values.

Up to four alphanumeric charactersCode:

Up to thirty charactersName:

An optional, free text field. This value is used in ConfirmConnect® to givefurther information about the Attribute Type in order to aid the setting of theValue.

Description:

This value will be used on any Feature which has this Type applied and hasnot yet been assigned a Value. This has a default of NA, the Code and de-scription may be changed.

Not ApplicableValue:

Affects the order in which the Type appears in the Feature tab and whenFeatures are viewed on a mobile device. A type numbered 1 will appear at

Display Order:

the top of the numbered list, a Type numbered 9999 will appear at the bottom.Unnumbered Types will be listed before numbered ones.

Select from:Type:'Pick List' - To define values that will form a drop down list from which a userwill pick when assigning values in this Attribute Type.'Text' - To apply free text as the value in this Attribute Type.The following Types are only applicable in the Inventory module to Attributeapplied to Inventory Items:'Number' - To apply a number value in this Attribute Type'Date' - To apply a date value in this Attribute Type'Date Time' - To apply a date and time value in this Attribute Type.

Only Pick List and Text Attribute Types may be chosen for use asFeature Attributes, since Number and Date Attributes are implemented

Note:

as Measurement and Date Types respectively. The Number, Dateand Date Time Types are used for Inventory Attributes.

(Inventory module)Case:Where a 'Text' Type this field will be available. Select from:'Any' - To allow text entries in Upper or lower case, or a combination of both.

45 of 123Confirm

| Network Manager |

'Upper' - To force text entries to Upper case.'Lower' - To force text entries to lower case.

(Inventory module)Decimal Places:Where a 'Number' type is selected this field will be available for defining thenumber of decimal places displayed for a number entry.

(Inventory module)Maximum Width:Where a 'Text' type is selected this field will be available for defining themaximum width (in number of characters) of the text entry field.

(Inventory module)Proportional:Where a 'Number' type is selected this field will be available to indicate if theParameter Value is proportional to the 'size' of the field that it is recordedagainst. For example, the area of cracking on a Feature would reduce if theFeature was split (proportional), but the number of lanes would not (not pro-portional).

If the current Attribute Type's Values are dependent on another AttributeTypes Values then specify the appropriate Attribute Type here. This will apply

Depends on:

a default value for this Attribute Type when a value for the dependent AttributeType is entered. See Setting Attribute Dependencies on page 46.

(Inventory module)Unit of Measure:Where a 'Number' type is selected this field will be available for the selectionof a Unit of Measure. The drop down list references the Unit of Measurelookup.

Optionally specify a Device Data Key.Device Data Key:ConfirmConnect® user whose data security group includes view access tothis data security key will be able to view this attribute type on their Surveytasks.

Leaving this field blank will allow all users to view this date type inConfirmConnect®.

Note:

Setting Attribute Dependencies

Set the Attribute Value Dependencies by clicking on the Depend Button on the Attribute Typeform.

Note: The Depend button will only become active if an Attribute Type has been specified in the'Depends on' field in the Attribute Type form.

46 of 123Confirm

| Network Manager |

The top part of the Attribute Value Dependencies form will display the Attribute Values for the de-pendent Attribute Type (entered in the 'Depends on' field of the Attributes Type form). The DefaultValue is set in the drop down lists. The drop down lists reference the Values set against this AttributeType.

In this way an association is made between this Attribute Type and the dependent Attribute Typesuch that a default value is entered for this Attribute Type when the associated dependent attributeType has an Attribute Value entered. So that in the above example, if 'Carriageway Types' is se-lected as the Dependent Attribute Type, the value 'Dual (M) type', automatic entry of '70 MPHMax' will be made against the Attribute Type: 'Statutory Speed Limit'.

The lower part of the form specifies which Dependent Values are Allowable in each Default Value.Select a default value by clicking in the field, and then check the values, which will be allowableif the default value is to be changed. In addition the user may check the Warning column to havethe system issue a warning when the dependency relationship is used.

Note: The Attribute Value drop downs will not be restricted by the relationships configured here.The Feature Attribute Dependent Update and Inventory Attribute Dependent Update utilities canbe used to correct any inconsistencies highlighted by running the Attribute Dependency Exceptionsreports.

Attribute Value

Click on the 'Attr Value button to display the Attribute Value form.

47 of 123Confirm

| Network Manager |

Up to four alphanumeric charactersAttribute Value:Up to 30 characters.Description:Affects the order in which the Value appears in a drop down list. A Valuenumbered 1 will appear at the top of the numbered list, a Value numbered

Display Order:

9999 will appear at the bottom. Unnumbered Values will be listed beforenumbered ones.These fields are used in 'Number' type Attribute Types to define the allowablenumber range (by setting a 'Minimum' and 'Maximum') and to ascribe a defaultvalue (by setting a 'Nominal' value).

Minimum / Maxim-um /Nominal:

To remove this value from the list of values the user may chose from whenassigning a value to an Attribute on a Feature or Inventory item.

Inactive:

Flag this to display a warning when this Parameter Value is used.Warning if Used:This settingmay be used to determine the Feature Status (whether the Featureis 'Live' or 'Dead') based on the value applied to the Feature Attribute. Selectfrom:'No Effect' - Setting this value on a Feature Attribute will not affect the FeatureStatus.

Feature Status:

'Set to Active' - Setting this value on a Feature Attribute will set the FeatureStatus to 'Live'.'Set to Inactive' - Setting this value on a Feature Attribute will set the FeatureStatus to 'Dead' and apply an End date.

48 of 123Confirm

| Network Manager |

(Dashboard module)You may set a colour value to Attribute values that will display results in theDashboard).

Colour:

SeeReporting\Dashboard\Attribute Types for full details on using AttributeTypes in the Dashboard.

This setting allows a warning message to be specified that will appear whena Feature or Inventory Item carrying this Pick List value is selected on a Job.Note: Risk Warnings are not applicable to Date, Text or Number Attributes.

Risk Warning:

(Traffic Count Data module)This field is used to group Attribute Values together on the Traffic CountSummary Report.

External Refer-ence:

(Condition Survey - BCI Reports module)When using the Structures Data Export utility to export Structures data thisfield is exported andmust be exactly the same as the Structures Toolkit values.See Structure Toolkit Export SystemSettings for full details on configuringyour Structures data.

Feature Group

The Feature Group provides the means of grouping Feature Types so that parameters, which arecommon to a group of Feature Types, can be applied. The parameters include MeasurementTypes, Text Attributes and Observation Types. The Groups also provide a means of selectingwhich Features will be available for Ad hoc inspection (Condition Survey Module), whether TextAttributes and Smart Attributes will be shown on Works orders (Extended Attributes module) anda means of applying a condition grade Weighting within the Feature Group.Where the Inventory module is present, Groups may have Inventory Types assigned to them sothat Features in that Group can have Inventory Items in the specified Inventory Types added tothem. Inventory Types are in turn allocated to Inventory Groups to assign the Attribute Types thatare to be available for an Inventory Item.

49 of 123Confirm

| Network Manager |

Up to four alphanumeric characters.Code:

Up to thirty charactersName:

Select from the drop down list. The drop down list references theMeasurementType Lookup.

Primary Measure-ment:

(The Primary Measurement will be entered in the Measurement field of theFeature tab of the Feature form)

(Asset Valuation module)ValuationMeasure-ment: Enter (or select from the drop down list) the Measurement type that will be

used when calculating the value or depreciation for Assets in this Group.Where the Asset Valuation module is not present, this field can be left blank.

(Condition Survey module)Select for AdhocInspections: Check this box to include all Features in this Group in the list of Features

available for Ad Hoc inspection on mobile devices.Features that are not available for Ad Hoc inspection cannot have Ad HocDefects raised against them from a mobile device. However, on the Host, thissetting does not apply and any Feature can have a Defect raised against it.See Condition Survey for details of Ad Hoc inspections. If the Condition Surveymodule is not used - this check box can be ignored.

(Asset Register - Audit Trails module)Maintain History:

50 of 123Confirm

| Network Manager |

Check this box to include all Features in this Group in a Feature Entity Historyreport on changes made to Features.

(Asset Register - Linear Assets)Feature GroupClass: This field will only be visible if the Linear Assets Module is present. Select

from:'Linear Asset' - To allow linear parameters in Features of this Group.'Discrete Asset' - To disallow linear parameters in Features of this Group.

In ConfirmConnect, this controls what Features can be created. A user canonly create a Feature of a Feature Group to which they have at least View

Device and WebData Key:

access. It has no impact on what Features are visible on ConfirmConnect butit does restrict the Features that can be added as Inventory links or references.In Confirm web interface, this controls what Features are visible on the Enquirymap. A user will only see Features of a Feature Group to which they have atleast View access.

Select a Cost Code which is to be used for the creation of Features in thisFeature Group when imported from the mobile. If this is not set then theFeatures will inherit the Cost Code from the Site.

Cost Code:

Select which Contract Area is to be used for the creation of Features in thisFeature Group when imported from the mobile. If this is not set then theFeatures will inherit the Contract Area from the Site.

Contract Area:

Select which Customer is to be used for the creation of Features in this FeatureGroup when imported from the mobile. If this is not set then the Features willinherit the Customer from the Site.

Customer Code:

Confirm Database Map Layer

When first setting up Confirm to use a Confirm Database Map Layer, some configuration stepsare required, if these steps have not been performed you may receive errors. Please refer to thesection in the help for further advice on how to set up your database to support using internalConfirm tables as map layers.

Feature Group - tabs

The tabs are used to define the ways in which the Feature on the Groups may be accessed andviewed, as well as defining the parameters that will default to a Feature when a Feature Type isselected. (Feature Types are placed in Groups in the Feature Type lookup).The following can be added: Measurement Types, Text Attributes, Smart Attributes, Date Typesand Observation Parameters. All the tabs can be left blank if there are no parameters required -including a parameter does not force a Value to be added for any particular Feature.Types can be added to the tabs at any time after the creation of the Feature Group. Adding Typesto the Feature Group will offer the option of adding the Type (with no Value) to all the pre-existingFeatures. This may be accepted or refused.

Feature Group - Additional tab

51 of 123Confirm

| Network Manager |

The default Site Group will be entered and may be altered by selection fromthe drop down list.

Site Group

The default Site Group is set in the Site System Defaults.Site Register\Site Lookups\General Site LookupsSite Groups are stored in the Site Group Lookup.Site Register\Site General\General Site LookupsAssigning a Feature Group to a Site Group allows Features in that FeatureGroup to be added to Sites in the associated Site Group.

If you wish to set up a Price Factor Matrix for this Feature Group, you mustselect the Smart Attribute whose values will be used in the Price Factor matrix.

PF Smart AttributeType

See 'PFactor button' below for information on setting up a Price Factor matrix.The drop down list references the Smart Attribute Lookup.

Select a Data Source that will be used for Feature Discrepancy checks.Discrepancy DataSource These checks will be run whenever a Feature is created or updated in the

Feature screen, of a Feature Group that has a Discrepancy Data Sourcespecified. This is to validate the entries made for the Feature against a user-defined set of criteria, in addition to the standard validation carried out byConfirm.The Data Source is run and a message displayed to the user if anything isreturned. Note that this does not prevent or undo the update, but just providesa warning to the User.For details on configuring the Data Source to be used see Validation DataSources

(Asset Validation Module)Validation DataSource If the Batch Validate Features utility is to be used for Features in this Feature

Group, select the Data Source that will be used for this validation.See Batch Validate Features for more information.

Supply a range of numbers which will be used to automatically allocate theAsset Number for new Features created in this Feature Group.

Asset NumberRange From / To

If these settings remain blank, Confirm will use the range set in the FeatureSystem Settings. If these are blank, a number between 0-99999999.99 willbe used when Features are created.

52 of 123Confirm

| Network Manager |

Supply an increment which will be used for each Feature created.Asset Number In-crement

Select this option to create a map layer containing all Features from the se-lected Feature Group that have spatial information recorded against them in

Mapping Options:Use ConfirmData-base Map Layer the Confirm database. Spatial data for all the valid and unmapped point fea-

tures will also be created if Map Layer Geometry Type is set to 'All', 'Point' or'Multipoint'.The layer's name will be the Feature Group name and it will bestored in the Confirm database with the Feature data. The layer will be avail-able for selection from the Workspace Manager.De-selecting this option will remove the layer from the Workspace Managerand it will no longer be available for selection. The original layer will remainon any Workspaces it was assigned to before it was deleted.A 'Referential Integrity Map Layer' can still be picked when this option is se-lected which will export Feature changes to the selected layer but this wouldnot be the layer that is maintained.

Selecting a Layer Type will only allow spatial geometry of that specific geo-metry type to be created for Features belonging to this Feature Group.

Mapping Options:Map Layer Geo-metry Type Only available when "Use Confirm Database Map Layer" is enabled and is

defaulted to "All".The "All" option will allow any supported Spatial Geometry Types.On saving a Feature Group, that uses the "Use Confirm Database Map Layer"option, a warning message may display a list of geometry types which alreadyexist for Features in this Feature Group.Changing this value will not change the Geometry data for Features storedin Confirm.

Selecting this option will mean that Feature Group layers will not be createdfor the selected Feature Group.

Mapping Options:Do Not Use Con-firm DatabaseMap Layer Instead there will be an option to use a Referential Integrity Layer (selected

underneath this option) to maintain Feature geometry.

(0440 - Referential Integrity module and 0425 Map module)Referential Integ-rity Map Layer If the 'Do Not Use Confirm Database Map Layer' option is selected then this

field can be used to select a registered layer as a designated Referential In-tegrity Layer for the selected Feature Group.When Features in this Feature Group are created or updated the attributeson this map layer will also be updated when the Referential Integrity Agentruns.The spatial representation on this layer will be placed at the Centroid coordin-ate. If the Feature's spatial representation already exists it will only be updatedif the map shape is a point.

Feature Group - Display tab

The display tab allows you to add Feature Groups as menu items in the Confirm Explorer, and toconfigure a display order for the tab on the Feature form.

Check this to indicate that this Feature Group should be available in a menuoption in the Asset Register folder in the Confirm Explorer. Up to 85 FeatureGroups can be configured to appear in the Explorer.

Specific MenuOp-tion

In the above example the 'Trees' group has the flag set, which results in anew menu option appearing in the Confirm Explorer.

53 of 123Confirm

| Network Manager |

Feature Groups with a Feature Group Class of 'Linear Asset' will also appearin the Network Manager folder. Up to 15 Feature Groups can be configuredto appear there.Note: You will need to log out of Confirm (for example use the Coffee Cupicon), and log back in for the menu item to become available. It then needsto be added to the program rights of each user who will need the menu item,by selecting it in the User Security form (for an individual User), or in the UserSecurity Group form (for all user in that Group, when the 'Users' button isclicked)

The Feature screen will show an Identification Image, selected from theDocument Links attached to a Feature, if this functionality has been activated.

Show Identifica-tion Image

Select here whether to default to showing the oldest or most recent Link asthe Identification Image (according to the 'Document Date' field).See Feature Identification Image on page 11 for more information.

Each tab may be assigned a number, which will place it in order in the Featurewindow from left to right. In the illustrated example, the Attribute tab will be

Tab Display Order

the first tab on the left for Features in this Feature Group, followed by theAdditional tab, then Geography and Smart Attributes.Where no number is entered the tab will be hidden when viewing Featuresin that Feature Group. In the above example the Valuation Tab and the Ref-erences tab will not be seen when viewing Features in the Trees Group.

Feature Group - Measures tab

The Measures tab lists all Measurement Types (including the Primary Measurement) associatedwith this Group and makes them available in the Feature Windows.

To add a new Measurement Type:Click on Detail to display the Group Measurement form.

54 of 123Confirm

| Network Manager |

The Primary Measure will already be entered. Click on the 'new page' button, and select from thedrop down list to add aMeasurement Type. The drop down list references theMeasurement Typeslookup

Check this box to display the Measurement Types and associated measure-ments on a Non-routine Works Order.

Show on WorksOrder:

Feature Group - Conditions tab

The Conditions tab lists all Observation Types associated with this Group andmakes them availablein Condition Grades window off the Feature form (found under 'Conditions' on the 'Other' button).

To add a new Observation Type:Select the Condition tab and click on Detail to display the Group Condition form.

55 of 123Confirm

| Network Manager |

Select from the pick list to add an Observation Type. The pick list references the ObservationTypes lookup.Note: Selecting an Observation Type to link with this Group will make these Types availablewithin the Condition Surveymodule when an Inspection batch is raised. You should therefore includeagainst a Group all the Observations you will wish to make when you inspect.

Enter a number here to weight the score associated with the ObservationParameters linked to the Observation Type. The weighting multiplies the score

Weighting:

so that a 'Poor' parameter, scored at 8, will acquire greater weight for Featuresin a Feature Group weighted at 3 (the score becomes 24), than for Featuresin a Feature Group weighted at 1 (the score becomes 8).Where a score has been applied, there must therefore be a weighting of morethan zero (because multiplying by zero will return zero score).

Note: An Observation Type can also be linked to a Group through the Observation Type lookup.

Feature Group - Attributes tab

The Attributes tab lists all Attributes associated with this Group and makes them available in theFeature screens.

To add a new Attribute:Select the Attributes tab and click the 'Detail' button to display the Group Attribute Type form.

56 of 123Confirm

| Network Manager |

Select from the drop down list to add an Attribute Type. The drop down list references the AttributeTypes lookup and displays all Attribute Types of a 'pick list' or 'text' Type. Adding an Attribute Typeto a Feature Group will automatically create the Attribute with its default value against all Featuresof the Feature Group – for Pick List Attribute Types this is the Not Applicable Value, for Text AttributeTypes it is blank.Note: Only Pick List and Text Attribute Types may be added. To add numeric or date values toFeatures, use the ‘Measures’ and ‘Date Types’ tabs respectively.

Check this to ensure that this Attribute is supplied before a Feature carryingit can be saved. This check will be performed on the Feature and Feature

Mandatory:

Details screens when Feature Attributes are being edited. Confirm will preventthe save if a Mandatory Attribute is left with the 'Not Applicable' value (or forText Attributes, is left as blank or just containing space characters).The Feature screen will also prevent the save if any Mandatory Attributes forInventory Items have not been supplied.

Check this box to display the Text Attribute Types and Values associated withthe Feature on a Non-routine Works Order.

Show on WorksOrder:

To Delete an AttributeDeleting an Attribute Type from a Feature Group where there are existing Features with a valueset for the Attribute will display a warning to the user. The user then has the choice to either deletethe Attributes from all the Features, or to leave those with values set and delete only the Attributesstill set to the default value.

Feature Group - Date Types tab

The Date Types tab lists all Date Types associated with this Group and makes them available inthe Feature Windows.

57 of 123Confirm

| Network Manager |

To add a Date Type:Select the Date Type tab and click on Detail to display the Group Date Type form.

Select from the drop down list to add a Date type. The drop down list references the Date Typeslookup

Check this box to display the Date Type andassociated Dates on a Non-routineWorks Order.

Show on Works Order:

Feature Group - Smart Attributes tab

The Smart Attributes tab lists all Smart Attributes associated with this Group and makes themavailable in the Feature Windows.

58 of 123Confirm

| Network Manager |

To add a Smart Attribute:Select the Smart Attrib tab and click on Detail to display the Group Smart Type form.

Select from the drop down list to add a Smart type. The drop down list references the Smart AttributeTypes lookup

Check this box to display the Smart Type andassociated values on a Non-routine Works Or-der.

Show on Works Order:

Feature Groups - Inventory tab

(Inventory module)The Inventory tab will only be present if the Inventory module is 'turned on'.The Inventory lists all the Inventory Types associated with this Group and makes them availablein the Features window. Inventory Types are assigned to one or more Inventory Feature Groups.This allows Attributes to be specified for the Inventory Type such that attributes may be assignedto them in the Feature window.

The illustrated example results in the Inventory items which are seen in the illustrated Feature.Inventory Items may be viewed or added by clicking on the 'Detail' button.

Inventory Items

59 of 123Confirm

| Network Manager |

This will default to 'Inventory', indicating that any inventory Items added herewill be shown on the Inventory tab of the Feature window. You may type in

Tab Name:

another name to create a new tab of that name, which will become availablein the Feature window for Features in this Group. Once new tab names havebeen created they become available for subsequent selection from the Pickbutton.

Affects the order in which the Inventory Type appears in the Feature windowtab. A type numbered 1 will appear at the top of the numbered list, a Type

Display Order:

numbered 9999 will appear at the bottom. Unnumbered Types will be listedbefore numbered ones.

Up to four charactersCode:(PMS) - This will be the code from the Rules & Parameters set being used.(This is a 2 letter code in UKPMS.)

Up to 30 charactersDescription:(PMS) - Normally the description should be the same as that in the Rules &Parameters set being used.

Make a selection to define the way in which the measurement will be derived,and whether or not Inventory Items in this Type vary by distance, i.e. more

Item Type:

than one Inventory Item may be assigned to the Feature provided they arein different positions on the FeatureSelect from:'No Distance or Width' - No measurement is required against the inventoryItem on the Feature. This selection is appropriate to Inventory Items thatrepresent discrete assets whose position is not calculated relative to chainage.An item with no Distance or Width may not vary by distance (but may varyby XSP)

60 of 123Confirm

| Network Manager |

'Point (NoWidth)' - Provides a 'Start Distance' field against the Inventory Itemon the Feature. Themeasurement entered in the 'Start Distance' field is copiedinto the 'Measurement' field against the Inventory Item on the Feature, if theMeasurement is set to 'Automatic'.'Point (Width)' - Provides a 'Start Distance' field and a 'Start Width' field againstthe Inventory Item on the Feature. The measurement entered in the 'StartWidth' field is copied into the 'Measurement' field against the Inventory Itemon the Feature, if the Measurement is set to 'Automatic'.Multiple 'point' items may exist against a Feature providing that no two Itemsare placed at the same point (in the same XSP. Items may exist at the samepoint in a different XSP).'Linear (No Width)' - Provides a 'Start Distance' field and an 'End Distance'field against the Inventory Item on the Feature. The 'Measurement' will bederived from the difference between the End distance and the Start distance,if the Measurement is set to 'Automatic'.'Linear (Width)' - Provides a 'Start Distance' field, an 'End Distance' field anda 'Start Width' field against the Inventory Item on the Feature. The 'Measure-ment' will be derived from the difference between the End distance and theStart distance, if the Measurement is set to 'Automatic'.Multiple 'Linear' items may exist against a Feature providing that no two Itemshave overlapping chainage (in the same XSP. Items may exist in the samechainage in a different XSP).'Area (One Width)' - Provides a 'Start Distance' field, an 'End Distance' fieldand a 'Start Width' field against the Inventory Item on the Feature. The'Measurement' will be derived from the difference between the End distanceand the Start distance multiplied by the Start Width, if the Measurement isset to 'Automatic'.'Area (Two Widths)' - Provides a 'Start Distance' field, and an 'End Distance'field with a 'Start Width' field and an End Width field against the InventoryItem on the Feature. The 'Measurement' will be derived from the differencebetween the End distance and the Start distance multiplied by half the sumof the Start and End Widths (i.e. an average width), if the Measurement is setto 'Automatic'.Multiple 'Area' items may exist against a Feature providing that no two Itemshave overlapping chainage (in the same XSP. Items may exist in the samechainage in a different XSP).

Make a selection to define the way in which a Measurement may be enteredinto the 'Measurement' field of the Inventory item in a Feature.

Measurement:

Select from:'Automatic' - The Measurement field of the inventory item will not be editable,and the entry will be calculated from the 'Start Distance', 'End Distance', 'StartWidth', 'End Width' entries, as defined for Item Type above.'User Defined' - The Measurement field of the inventory item will be editable,and no calculation will be made.'Hidden' - The Measurement filed will not appear at all for Inventory Items onthe Feature. This should be selected if 'No Distance or Width' is selected asthe item Type.

(PMS)Lane Location:Select from 'Inside', 'Outside' or 'Centre'

Select from:Parent Site Class:

61 of 123Confirm

| Network Manager |

'Maintain' - To apply the Feature Site Classification to the Inventory Item, andto update the Inventory Item in line with changes to the Feature. This willresult in the Inventory item always carrying the same Site Classification asthe Feature to which it is applied.'Default' - To apply the Feature Site Classification to the Inventory Item whenit is first created, and to ignore subsequent changes to the Feature. This mayresult in the Inventory item carrying a different Site Classification from theFeature to which it is applied.'Hidden' - The Site Classification will not be shown against the Inventory item.

Select from:Parent Customer:'Maintain' - To apply the Feature Customer to the Inventory Item, and to updatethe Inventory Item in line with changes to the Feature. This will result in theInventory item always carrying the same Customer as the Feature to whichit is applied.'Default' - To apply the Feature Customer to the Inventory Item when it is firstcreated, and to ignore subsequent changes to the Feature. This may resultin the Inventory item carrying a different Customer from the Feature to whichit is applied.'Hidden' - The Customer will not be shown against the Inventory item.

(PMS)Vary by CrossSectional Position: Check this to allow several occurrences of this Inventory Type against a

Feature, provided that each occurrence is in a different Cross Sectional Pos-ition.

Check this to display the 'Survey' field against the Inventory Item on theFeature. The Survey field displays the date of the last Survey carried outwhich involved this Inventory Item.

Show SurveyDate:

(PMS)Allow Multiples(full XSP model): The box is checked when the item can have more than one occurrence at

the same chainage for a Full Cross Section Position.

(PMS)Show Temporary:Check this to display the 'Temporary' checkbox against the Inventory Item onthe Feature.

(PMS)Allow Multiples(minimal XSPmodel): The box is checked when the item can have more than one occurrence at

the same chainage for a Minimal Cross Section Position.

(PMS)Show Reversed:Check this to display the 'Reversed' checkbox against the Inventory Item onthe Feature

An Attribute Typemay be selected so that the associated values may be usedto add more than one Inventory Item in this Inventory Type to the Feature.

Vary by Attribute:

If not 'Vary by ' attribute is specified, than there may only be one instance ofthis Inventory item against the Feature.For example:In the illustrated example the Text Attribute 'Electrical - Type of Point' hasbeen specified. The Values associated with this Attribute Type are for thevarious type of electrical outlet (mains, shaver point, cooker).

62 of 123Confirm

| Network Manager |

This allows one Inventory Item to be added to the Feature in each of theValues - an Item for all the 'Mains' points, an Item for all the 'Shaver points',an item for all the 'Cooker' points and so on.See Feature - Inventory tab on page 16 for an illustration of Inventory Itemson a Feature.

Select from:Linked Feature:'None' - To indicate that this Inventory item will not also exist as a Feature.'Optional' - To indicate that a linked Feature may be optionally specified againstthe Inventory Item on the Feature.'Mandatory' - To indicate that a linked Feature must be specified against theInventory Item on the Feature, i.e. the user will not be permitted to save theFeature until the Inventory Item has a linked Feature specified.

Defaults to unchecked, only available when 'Linked Feature' is set to 'Optional'or 'Mandatory'.

Copy 'ReferencedBy' of linked Fea-ture: Check this to copy the details from the 'Referenced By' tab on the Feature

screen to a new version of a Feature during the End-Dating process.

Set a Data Security Key in order to limit the availability of this record to Userswith rights to this Data Security Key through their Data Security Group.

Data Key:

Users will only be able to view / update Inventory Type and Inventory Item ifthey have been granted access to the Data Key associated with the InventoryType.Select from the drop down list. The drop down list references the Data SecurityKey library.

This option is only visible if the current user has "Assign Data KeyManually" enabled in User Security.

Note:

Inventory Types - Transform button

(PMS)The 'Transform' button on the Inventory Type input screen opens the Feature Group Transformationswindow, and provides the facility to control whether or not to allow Transformation or mapping ofimported observations, e.g. condition data surveyed as belonging to a particular inventory group,to the inventory group held in the database for that section.

63 of 123Confirm

| Network Manager |

The Feature Group Transformation table is a matrix of all the Inventory Feature Groups assignedto that Inventory Type (as defined on the Inventory Feature Groups tab). Where an Inventory Typehas no Feature Group specified, there are no entries in the Transformation table. The columnsfor Observation Feature Group and Inventory Feature Group are automatically completed byConfirm when the Transformation screen is launched.Only the 'Transform' column may be edited. To change the option for transformation click in theTransform column for the appropriate row and select from:

• 'Yes' - Observations are transformed to the inventory's feature group.• 'No Transform' - Observations are considered valid but keep their original feature group.• 'Not Allowed' - Observations will be discarded.

Clicking on the desired option will place it in the transform field. When all the desired changeshave been made click on the 'Save' button to save the changes to the database and return to theInventory Type screen.

Inventory Types - Default Widths tab

(PMS)The Inventory Default Width is set using the base unit for linear measure, normally metres. Anyitem that has width e.g. carriageway, channel block etc., and has a Feature Group Class of 'LinearAsset', can have a default width set that will automatically be applied in the absence of specificdetails being entered against the Feature. The user may then override this width for an individualinventory item at the appropriate input stage. For any item without width or for which a default isinappropriate, default width should be set at 0.00.Select the Default Widths tab and click on the 'detail' button to display the Inventory Default Widthsscreen

The top part of the form will show the current Feature Group and Inventory Type, and may not beedited.

Select from the pick list. The pick list references all Feature Types associatedwith the current Feature Group.

Feature Type:

Note: The Feature Group must be of the Feature Group Class 'Linear Asset'in order for a selection of Feature Type to be made.

Enter a number that represents the default width of Features in this FeatureType. The default width entered is based on the users estimate or the con-

Default Width:

sidered 'normal' or average width for the type of inventory being defined.Default widths will be used in PMS calculations where no detailed inventorydata exists.

64 of 123Confirm

| Network Manager |

Inventory Types - Inventory Feature Groups tab

The Inventory Feature Groups tab defines the Inventory Feature Group (as distinct from the FeatureGroup) to which the Inventory Item belongs. This in turn allows Attributes to be specified for theInventory Item.Select the Inventory Feature Groups tab and click on the 'Detail' button to display the InventoryFeature Groups window:

Enter a code and name to create and Inventory Feature Group for this Invent-ory item. The code must be unique within Inventory Feature Groups andFeature Groups.

Inventory FeatureGroup:

(PMS)Certainty withinType: Enter a number to set the priority of transformation within an Inventory Type

for Feature Type Transformations.

(PMS)Allow Transforma-tion: Check this to allow transformation from one observed Feature Group to an-

other during the Automatic Pass Process.

This field is only available if the 'Linked Feature' field in the Inventory itemwindow is set to 'Mandatory' or 'Optional'. If either of those is set then a selec-

Linked FeatureGroup:

tion must be made in this field to determine the Feature Group from which aselection of linked Features may be made for the Inventory item on the Fea-ture.The drop down list references the Feature Group lookup.

Enter here the Measurement Type that applies to the measurement shownagainst the Inventory Item in the Feature.

Primary Measure-ment:

Note: The Measurement field will only display if the Inventory Type has'Automatic' or 'User Defined' entered in the Measurement field of the InventoryType form.

Inventory Feature Groups tab - Attributes

65 of 123Confirm

| Network Manager |

Attribute Types may be associated with Inventory Feature Groups to make them available in theInventory type on the Feature.Click on the 'Detail' button to display the Feature Group Attributes window:

The 'Vary by ' Attribute Type will already be entered by default.Select from the drop down list to add a Text Attribute Type. The drop downlist references the Attribute Types lookup for all Attribute Types.

Attribute Type:

Relevant to Pavement Management System - all other asset types shouldleave the default entry.

Priority Level:

Check this box to display the Text Attribute Types and Values associated withthe Inventory Item.

Show on WorksOrder:

Inventory Feature Groups tab - Other button

SOR Item Update AttributesInventory Item Attribute parameters may be updated automatically when work is raised on Featuresin this Feature Group, using any of the SORs specified in the SOR Item Update Attributes window.This is done to update a number attribute in line with the quantities specified in a Job so that, forinstance, the quantity is added to the number when a Job is completed to install Inventory items.The update is carried out when:

• When the Job is subject to Request Checking if the 'Update Attribs\Warranties when RequestChecking' flag is set in the Payment System Settings.

• When Payment on the Job is committed

Note: The Attribute Types that may be updated at the Payment Batch commit or RequestChecking stage are restricted to numeric ones that are valid for the Feature Group.Click on the Inventory Feature Groups tab - Other button, and select SOR Item, to display theSOR Item Update Attributes window:

66 of 123Confirm

| Network Manager |

The top part of the form displays the current Inventory Feature Group and the Feature Groupclass, and may not be edited.The central pane displays all the SORs currently assigned to this Inventory Feature Group.The fields in the lower portion of the form displays additional information about the SOR currentlyselected in the SORs pane.

To add a new SOR and define its behaviour:Click on the 'New' button to the right of the SORs pane to move to a new row and clear the fieldsin the lower part of the form.

Enter, or select from the pick list, the required SOR Item. The pick list refer-ences the SOR Item library.

SOR Item:

Asset Maintenance\SOR Item

From the SOR Item, may not be edited.Full Description:

The 'Vary by ' Attribute Type is entered (as defined in the Inventory Itemswindow) and may not be edited.

Attribute Type:

Note: only 'pick list' Attribute Types may be used in this context. Where theVary by attribute is not a pick list type then no automatic attribute updatesmay be carried out.

Select the Attribute Value of the Inventory Item that is to be updated. Thedrop down list references the Values for the 'Vary by ' attribute.

Attribute Value:

Select from:Type of update:'Add' - To add the SOR Item quantity on the Job to the Attribute specifiedbelow.'Remove' - To remove the SOR Item quantity on the Job from the Attributespecified below.

67 of 123Confirm

| Network Manager |

Select the Attribute type whose value is to be updated. The drop down listreferences Attribute Types added to this Inventory Type, of the type 'Number'as defined in the Text Attributes Lookup.

Update AttributeType:

You may add as many SORs items as required, and each SOR will have its behaviour set in therelated fields.Click on 'Update' to save the SOR Item Update Attributes.

Spatial Geometry Types

Feature Group Geometry TypesWhen Feature Groups are using ConfirmDatabaseMap Layers, the Feature's spatial representationwill be stored in the Confirm Database. When configuring these Feature Groups, a summary ofthe Geometry Types of Features within this Feature Group will be shown.Below, is a list of geometry sub-types that fall within the Geometry Type options available on theFeature Group screen.1. Point Types

• Point

2. Multi-Point Types• MultiPoint

3. Line Types• LineString• MultiLineString• Curve• MultiCurve

4. Polygon Types• Polygon• MultiPolygon

The following types may also appear in the confirmation message when setting the Map LayerGeometry Type value.

• Geometry• GeometryCollection• CircularString• CurvePolygon• CompoundCurve• Surface• MultiSurface• PolyhedralSurface• TIN• Triangle

Feature Group - 'Other' button

The 'Other' button gives access to the following options.Note: The 'SOR Item' option is only available if Module 0745 (Warranty Dates) is active.

68 of 123Confirm

| Network Manager |

Price Factor Matrix

You may optionally set up a relationship between Smart Attribute values, and Priorities, such thata Price Factor is automatically selected on Non Routine Jobs when a Feature carrying a particularSmart value is used together with a particular Priority. The Price Factors to be used in each com-bination of Smart Attribute and Priority is determined in the Price Factor matrix.Click on the PFactor button to display the Price Factor Matrix:

The top part of the form shows the Feature Group and PF Smart Attribute Type selected in theFeature Group form.This column will list each Value found in the Smart Attribute specified as the PF Smart AttributeType.This column will list every Priority found in the Priority Lookup.Asset Maintenance\Maintenance LookupsThis column will be blank in a new matrix, and is for the selection of the Price Factor that shouldbe used when the accompanying combination of Smart Attribute Value and Priority is found. Youmay select from the drop down list. The drop down references the Price Factor Lookup.Asset Maintenance\Maintenance LookupsUsing the Price Factor MatrixWhere a Price Factor Matrix exists for a particular Feature (as determined by the Feature Groupto which the Feature belongs) then the Price factor will be applied when raising Non-Routine Jobsin the following ways:

• Manually in the Job, or Order Job screens• When Jobs are Batch Allocated onto Order (providing that no Price Factor is entered in the OrderJob Batch Filter).

• Jobs raised by means of the Raise Jobs from Regimes, or Raise Jobs from Defects utilities.• Jobs being uploaded from a mobile device. Where a Feature's Smart Value has been alteredon the mobile device, then the upload will update the Smart value on the host before applyinga Price Factor to any jobs raised on the amended Feature (thus ensuring that the Price Factorreflects the new Smart Value for the Feature).

Note: The Price Factor supplied from the matrix is a default for the Job and may be altered in anyparticular Job.

69 of 123Confirm

| Network Manager |

Where no Price Factor Matrix has been set up then Price Factor default is assigned by referenceto Priority.

Failure Matrix

(Performance Monitoring module)The Failure Matrix combines a Feature Group with Classification and Failure Type so that thesystem can select the correct Failure Type when an 'unacceptable' parameter is applied to aFeature during a Feature Monitoring Inspection.Select Failure Matrix in the 'Other' button drop down menu to display the Failure Matrix:

The top part of the form displays the current Feature Group.The central pane contains one row for each Site Classification found in the Classification Lookup.Site\Site Lookups\Operational Lookups\ClassificationsThe Site Classifications are displayed in the left-hand column, the remaining column to the rightdisplay the information about Failure Type and follow-ups.Note: use the bottom scroll bar to view column to the right.The lower portion of the form is for selection of the parameter for the currently selected row in thecentral pane:

Displays the Classification that is currently highlighted in the pane above.Site Class:

Select the Failure Type that will be applied to Feature in this Feature Group,carrying this Classification, if they are assigned an unacceptable Condition

Failure Type:

Grade on a first inspection. The drop down list references the Failure TypeLookup for all Failure Types that are set to: 'All Inspections' or 'First InspectionsOnly'.Performance Monitoring\Monitoring Lookups

This field will be available if the Failure Type selected in the previous field isone that has been flagged for 'Re-inspection'.

Follow Up:

70 of 123Confirm

| Network Manager |

Select the appropriate Follow Up for the second Inspection. The drop downlist references the Follow Up Lookup.Asset Maintenance\Maintenance Lookups

Select the Failure Type that will be applied to Feature in this Feature Group,carrying this Classification, if they are assigned an unacceptable Condition

Failure Type:

Grade on a subsequent inspection. The drop down list references the FailureType Lookup for all Failure Types that are set to: 'All Inspections' or 'Re-In-spections Only'.Performance Monitoring\Monitoring LookupsNote: a subsequent Inspection is one where a Failure exists, with a Reinspec-tion date

This field will be available if the Failure Type selected in the previous field isone that has been flagged for 'Re-inspection'.

Follow Up:

Select the appropriate Follow Up for a subsequent Inspection. The drop downlist references the Follow Up Lookup.Asset Maintenance\Maintenance Lookups

The Failure Matrix is completed for each required Feature Group, in each relevant Classification.

SOR Item

This option is only available for Feature Groups of the Feature Group Class 'Discrete Asset'.Feature Attribute values may be updated automatically when work is raised on a Feature in thisFeature Group, using any of the SORs specified in the SOR Item Update Attributes window. Thecommittal of payment for the Job will update the Attribute value to that specified in the SOR ItemUpdate Attributes window.Click on the 'Other' button, and select SOR Item, to display the SOR ItemUpdate Attributes window:

71 of 123Confirm

| Network Manager |

The top part of the form displays the current Feature Group and the Feature Group class, andmay not be edited.The central pane displays all the SORs currently assigned to this Feature Group.The fields in the lower portion of the form displays additional information about the SOR currentlyselected in the SORs pane.

To add a new SOR and define its behaviour:Click on the 'New' button to the right of the SORs pane to move to a new row and clear the fieldsin the lower part of the form.

Enter, or select from the pick list, the required SOR Item. The pick list refer-ences the SOR Item library.

SOR Item:

From the SOR Item, may not be edited.Full Description:

Select an Attribute Type from the drop down list. The drop down list referencesthe Attribute Type for Pick List Attribute Types.

Attribute Type:

Select the value that is to be applied to the Attribute Type for a Feature thathas work carried out on it using this SOR Item.

Attribute Value:

Note: the Feature must already have the Attribute Type assigned to it. Feature Group - Attributestab on page 56 - for information on assigning Text Attributes to Features.

This field is not available for Feature Attribute updates.Type of update:

This field is not available for Feature Attribute updates.Update AttributeType:

You may add as many SORs items as required, and each SOR will have its Attribute and Attributevalue set in the related fields.Click on 'Update' to save the SOR Item Update Attributes.

Feature Type

A Feature Type will define a Feature for the purposes of maintenance and/or valuation. BecauseFeatures Types are assigned to Feature Groups, and Feature Groups carry a set of MeasurementTypes, Text and Smart Attributes Types, Inventory Types, Observation Types; and Date Types,setting the Feature Type will set default Types for a Feature by reference to the GroupFeature Types may also be called: Species (Confirm Arboriculture), or Carriageway Type (ConfirmStreet Works and Confirm Highways). Please see the Confirm Books Overviewmanual for details.Confirm Books Overview\Terminology in Confirm Products

72 of 123Confirm

| Network Manager |

Up to four alphanumeric characters.Code:

Up to thirty characters.Description:

Select from the drop down list. The drop down list references the FeatureGroup Lookup.

Feature Group:

Note: It is not possible to change the Feature Group of an existing FeatureType if any Features or Inventory Items exist.

(Asset Valuation Module)Feature Types may be linked with Asset Categories and Hierarchy Levels to provide defaults forassociated Features.

Enter or select from the pick list. The pick list references the Asset CategoryLookup. This Asset Category will be the default for new Features of this Type.

Asset Category:

Select from the pull down list. The pull down references the Hierarchy LevelLookup.

Hierarchy:

You may assign a display order to the Feature Type. The lower the number,the higher up the lookup list the Feature Type will appear. Where several

Order:

Feature Types are assigned the same sort number, they will sort alphabeticallyby Feature Type Name within the sort number.Note: Types with no Order number assigned will appear first in the list, fol-lowed by those with Order numbers in the assigned order.

(PMS - Observation Data module)Number of Lanes:Enter the number of Lanes that this Feature Type will have.

(PMS - Observation Data module)Number ofNearside ...: Enter the number of surveying directions for this Feature Type.

(Condition Survey - BCI Reports module)External Refer-ence: When using the Structures Data Export utility to export Structures data this

field is exported andmust be exactly the same as the Structures Toolkit values.

73 of 123Confirm

| Network Manager |

See Structures Toolkit Export SystemSetting for full details on configuringyour Structures data.

Maintenance Regimes will be automatically entered for their related Feature Types when the 'Al-locate Applicable Regimes' utility is run. SeeAsset Maintenance - Allocate Applicable Regimes.

Named Selection

A Named Selection groups together any set of Features in any order that the user defines. NamedSelections can be used throughout Confirm wherever there is a filter option for Named Selection.It allows the selection of groups of Features that cannot be picked out by any other filter criteria.The named Selection lookup will more usually be used to view and edit existing Selections, ratherthan to create Named Selections from scratch (although that can be done)Note: Named Selections are restricted by Work Group throughout Confirm. When a new recordis created it will be assigned the Work Group automatically from the current User.

Up to eight alphanumeric charactersCode:

Up to fifty charactersDescription:

Displays Primary Measures for the Features. Cannot be edited.Total Measure-ment:

Optional free text fieldNotes:

A Named Selection can be created anywhere the Named Selection button can be seen, which willusually be on Asset / Inventory forms, lookup lists, and report previews.Clicking on the Named Selection button will allow the user to save whatever list of Features ispresent in the report (if a report has been run) or lookup list (if a filter has been run).See System Fundamentals\Common Buttons, for details on how to create a Named Selection.

74 of 123Confirm

| Network Manager |

Network

More than one Network can be defined for the same area. These networks may be completelyseparate but it is more likely that they will be a different definition of streets and sections over thesame street network. This option is designed to cater only for the case when there is a base networkto which any other network translates to some or all of the same streets. The purpose being toallow data collected using one network referencing system to be translated to the base Networkused to set up the Confirm database. A typical example would be a base network set up on aStreet Gazetteer model with machine survey set up on a different type of network (e.g. Departmentof Transport). This then allows translation of data referenced on the survey network to be automat-ically translated by Confirm to the base network. This not only obviates the need to enter the samedata twice but also caters for adjusting the data to fit the base network where there are dimensionaldifferences in the lengths. This translation is a one way process from any network to the basenetwork. The base network is where all the data is held and processed.

The Network reference code is entered and may be up to 6 alpha/numericcharacters long.

Code:

A 50 character description as appropriate for each network.Name:

The Base Network checkbox should be ticked for the network against whichdata is stored in the Confirm database

Base Network:

External Network Section

This is the process by which a secondary Network, as described above, can be translated ontothe base network. This allows the user to take whole or part sections from one network and definethem as equivalent to a whole or part section on the base network. This facility also allows fordiscrepancies in the measurements between the two networks to be catered for by automaticallyshrinking or expanding the translated network to fit. One of the primary uses of this is to translatemachine survey networks to the base network while overcoming any measurement discrepanciesat the same time.

75 of 123Confirm

| Network Manager |

The 'External Network' i.e. the network that is being translated from. The dropdown will list all the defined networks in the database. Please see Networkon page 75for further details.

Network:

A unique code of up to 20 alpha/numeric characters. The code is enteredcorresponding to the section code for the translated network section. When

Code:

translating from Waylen files for PANDEF and SKID processing the directionletters at the end of the code should be stripped out as the section does notneed to be defined in both directions (for single carriageway situations).

A 50 character description as appropriate for each External Network Section.The description used originally for the Translated Section or another suitabledescription would normally be entered here.

Description:

This field is in 6.2 format, i.e 6 numbers before and 2 numbers after thedecimal point. The measured length of the translated section is entered here.

Measurement:

This should be the actual measurement for this section, not corrected in anyway, even if there is a known discrepancy to the true length. This is becauseany correction is automatically applied by Confirm PMS in the translation andthe data stretched or shrunk to fit accordingly.

When Current is selected, only Network Sections that have not been enddated will be displayed. Selecting All will result in both End dated and CurrentNetwork Sections being displayed.

Current/All Field:

External Network Section Link

The Network and Section fields are automatically completed from the External Network SectionScreen. The External Network Section Link screen is now used to link the External Section to oneor more existing sections on the base network.

The External Network Section Link window is started using the 'Detail' button on the ExternalNetwork Section screen.

76 of 123Confirm

| Network Manager |

Automatically completed by the system from the External Network Sectionscreen.

Network:

Automatically completed by the system from the External Network Sectionscreen.

Section:

The street or first street of the base network on which the section is to betranslated can now be selected either by directly inputting the name or code

Street:

to the screen. Alternatively, the street can be selected through the Street Filterand Street Lookup Tables using the 'Pick' button . Refer to the Named Selec-tion Item for screenshot examples.

The Section Label (Feature Label) can be entered directly or selected throughthe Feature Filter and Filter Lookup Tables using the 'Pick' button . As the

Label:

Feature Filter will select all features, not just sections, it is advisable to refinethe search using the Feature Group window and selecting Street Section fromthe drop down. (Street Section is the default name for the PMS Feature Groupbut may have been set up differently by an individual user. The Feature GroupWhole Street Section is normally associated with routine maintenance func-tionality in Confirm Engineering, Highways etc. and not the PMS) Refer toNamed Selection Item for screenshot examples.

Note: - The section can be selected directly using the 'Pick' button withoutfirst selecting a street. The Street part of the screen will then be automaticallycompleted when the section is selected from the Section Lookup Table.

The Sequence Number can be entered directly, when it is known, as an al-ternative to selecting the Feature Label as described above. This field isautomatically completed if the Section (Feature) is selected by Label.

Seq. No.:

This field is in 6.2 format, i.e 6 numbers before and 2 numbers after thedecimal point. This is the start chainage and will normally be zero for the first

External SectionFrom:

Link on the External Network Section. Where the External Network Sectionis longer or diverges from the first Section on the base network there will besubsequent links until the end of the External Network Section is reached.Each new link will have a start chainage equivalent to the end chainage ofthe previous link.

This field is in 6.2 format, i.e 6 numbers before and 2 numbers after thedecimal point. This is the chainage at which the mapping from the External

To:

Network Section onto the Base Network Section finishes for this link. If thewhole of the External Network Section translates onto this first Base NetworkSection or for the last External Network Section Link in the translation thenthis will be it's end chainage.

This field is in 6.2 format, i.e 6 numbers before and 2 numbers after thedecimal point. This is the chainage at which the Start of the External Network

Section From:

77 of 123Confirm

| Network Manager |

section or the start point for that particular link maps onto (coincides with) theBase Network Section.

This field is in 6.2 format, i.e 6 numbers before and 2 numbers after thedecimal point. This is the end chainage for that particular link where the Ex-ternal Network Section maps onto the Base Network Section.

To:

This chainage needs to reflect any adjustments in the length between thelength defined for the external network section and the base network section.i.e. if the external network section has a defined length of 94.5m but thistranslates to a base network length of 93.7m then the 93.7m needs to beentered here whereas the To measurement for the external network sectionwould be 94.5m.N.B. If the External Network Section has been defined in theopposite direction to the Base Network Section then the Section Fromchainage and To chainage are 'reversed', i.e. the from chainage will be thehigher value and the to chainage the lower value.

Feature Type Import Settings

The Feature Type Import Setting input screen provides a means of assigning the relevant Rulesand Parameters codes for Inventory items.

The Feature Import Setting lists all the available Inventory Feature types by Code and Descriptionas the first two columns. This is automatically completed by Confirm which searches the FeatureType Lookup table when Feature Type Import Settings is started. Also, any previously enteredFeat. (Feature) & Cons. (Construction) Codes are also displayed. The associated Inventory Type(Feat.) and Construction Type (Cons.) codes can be entered in the appropriate columns on theright of the screen. These combinations of features and construction type entered must be unique.Feat. and Cons. are the codes that would appear in any import file which you wish to be mappedto a particular Feature Type.

Inventory Feature Types and their associated construction type can then be imported using animport file in the appropriate Confirm import routine. In the import file the feature and its constructiontype can be specified as a single code provided that the code is sufficient for confirm to identifywhich Feature Type is intended.

78 of 123Confirm

| Network Manager |

The user can enter part of the description shown in the Type column to 'jump'to that item in the table.

Search:

The existing code for the Feature Type belonging to the Feature Groups witha Feature Group Class of 'Inventory' or 'Maintained Inventory' as alreadyentered in the database.

Code:

The Inventory Type code used in the import file - a unique code of up to 4alpha/numeric characters. Please seeAsset Register\Feature Lookups\Fea-ture Group - Inventory tab.

Feat.:

The Construction code - this is the Attribute Value associated with the AttributeType 'Construction' and is a unique code of up to 4 alpha/numeric characters.Please see Asset Register\Feature Lookups\Attribute Type.

Cons.:

The 'Save' button must be used to save the new entries before exiting thetable as no reminder to Save Changes is given.

Save:

Network Import Settings

The Network Import Settings screen provides settings relating to the import and export of Network,Inventory and Survey data.

When a Feature in a Network import file contains no Site inform-ation, it will be assigned to this Site.

Default SiteNetwork Data

In each case, the Attribute Type to which this field in a Networkimport file is to be assigned.

DTPCLASS,STEPLEVEL,FWAYOPEN,etc.

The Attribute Type to which Construction Type is to be assigned.ConstructionType

Inventory Data

The Attribute Type to which Kerb Material is to be assigned.Kerb Material

The length tolerance for Inventory Import is entered here as bothan absolute length and as a percentage of the section length.

Length Toler-ance

These fields are in 6.2 format, i.e. 6 numbers before and 2numbers after the decimal point.

This is the XSP position to which imported condition data defaultsif no XSP data is provided in the Survey Data Import file(s) oron the Survey Observation screen.

Default XSP

By default, Import Survey Data will reject any Survey files con-taining one or more Survey Features with no Observations and

Allow import ofSurvey with no

Condition Data

report an error. If this setting is checked, then a warning will bereported and it is possible to proceed with importing the Survey.

Observationsfor a Feature

When importing survey data in HMDIF format observation resultsshould be provided in either an option or value field, depending

Allow eitherOption or

on the observation type. Setting this allows the observation valueValue to beto be supplied in the value field where the parameter is primarilyan option one, or vice versa.

supplied forObservations

Ticking this box will add extra validation to some of the valuesin exported files. Specifically:

Restrict expor-ted values to

HMDIF Export

79 of 123Confirm

| Network Manager |

official UKPMSvalues

• When an HMDIF Network file is exported, any values in theHIER and FWHIER fields that do not correspond to a UKPMSstandard code will be ignored and an empty string exported.

• When an HMDIF Survey file is exported, if there are non-nu-meric characters in the Survey External Reference field thenthe Survey Number will be exported as NUMBER instead.

• When an HMDIF Survey file is exported, the NUMBER field islimited to 4 digits and the MACHINE field is limited to 5 charac-ters.

Network System Settings

The Network System Settings screen allows the setting of several default options relating to theNetwork.

The XSP for Default Inventory is entered here using the drop down that liststhe descriptions of all the defined XSP's. Care should be taken where user

XSP for DefaultInv.:

defined XSP's not included in the Rules & Parameters set have been definedto ensure that data is not defined to an XSP that is not used in the data ana-lyser processing.

Select the XSP that will be used by default for Features being added to a'Machine' Inspection Route.

Inspection RouteXSP:

The Survey and Analyse field is completed using the drop downwhich containsthe two pre-set options of 'All Groups' or 'PMS Sections Only'. This toggles

Survey and Ana-lyse:

between a PMS only analysis and the facility to use the Data Analyser on allgroups.

This setting is used by the Network Indicator List (the BVPI report) which re-ports on how much of the Network has been Surveyed. You may exclude

Not AssessedObsParm:

section lengths with the indicated Parameter recorded from the report totalsby entering the Parameter here. The pick list references the ObservationParameter Lookup.

For Footway Observations, the Section's Footway Hierarchy Attribute is usedas a default in the absence of Inventory, in preference to the Section's SiteClassification. Select the Inventory Type that corresponds to Footway.

Footway InventoryType:

80 of 123Confirm

| Network Manager |

The Nodes Mandatory check box should normally be checked so that thesystem requires all street sections to have start and end nodes. In this situ-

NodesMandatory:

ation, nodes will also have to be defined if a section is to be split. If the checkbox is unchecked sections can be defined or split without start and end nodes.

Note: This setting is not enforced for ESU Features.

Note: Nodes are mandatory in UKPMS for machine surveys so it is recom-mended that mandatory nodes is always set except where only visual inspec-tion surveys will ever be carried out.

This checkbox should be completed to have the system complete the surveychainage automatically if left blank.

Set Survey Chain-age if blank:

Network Seed Numbers

Seed numbers are set within each Work Group for:

1. Street Section2. Inventory Item3. Node4. Cross Reference

Two ranges are available allowing you to issues two batches of non-contiguous numbers.

Each Work Group must have a unique range of numbers, but if you issue one range to start with,which proves to be too few numbers, you can later come back and use the second range. Youcan also amend the 'Maximum' number to make room for a range of numbers for a new WorkGroups.

Enter a Work Group Code, or use the 'Find' button to recall all Work Groups.Work Group:

System Administration\Security\Work Groups

Will be automatically entered when a Work Group Code is selected.Name:

Street Sections are numbered from these seed numbers when they are created, or imported, intoConfirm. The number allocated may be displayed in the Central Asset field of the Additional tabof the Feature form (unless a specific number has been entered by the user, in which case thatnumber will be displayed and the seed number will not be seen on the Feature form).

Enter the number ranges for this Work Group.

Inventory Items are similarly numbered from Seed numbers on creation.

81 of 123Confirm

| Network Manager |

Each connection that is established between one Feature and another has a seed number allocated.These are not seen on the Feature Connection form.

Enter the number ranges for this Work Group.

Cross References are numbered from these seed numbers when they are created in the Obser-vation Type lookup. The numbers are not seen in the Observation Type form.

Enter the number ranges for this Work Group.

82 of 123Confirm

| Network Manager |

Survey Data LookupsThese Survey Data Lookups are the lookups or libraries required to import or create surveys withinConfirm. They contain the definitions of different survey types and of the observations that can be re-corded within these surveys. For standard surveys, all the lookups are populated with the appropriatedefinitions in the default database. Where the user requires to import differing survey types, using otherobservations the set of definitions may be added to and edited as required.

The Survey Data Lookups section is used to pick each of the options required to populate the databasewith the base Survey information.

The data must be in place before many of the detail input screens can be completed. In order to followa logical path and facilitate speed and ease of data entry it is recommended that the libraries are setup prior to commencing any other data input. However if errors, omissions or additions are needed theymay be edited or added later. Alternatively and/or additionally, they may also be entered 'on the fly'.

Please refer to the Asset Register manual for details on Observations.

Observation Type

Observation Type, used in conjunction with Observation Parameter and Observation Impact, setup the parameters for judging the condition of a Feature.Where Observation Types are being used in the Risk module Observation Types define the FailureModes, or the manner in which an Asset may fail, for example 'Structural', 'Capacity'.Observations are usually carried out as part of a Condition Survey inspection (Condition Surveymodule). However, details for Feature condition can be entered directly against Features in theAsset Register, even when the Condition Survey module is not present.The Observation Type will list the Condition Types that will be judged for a Feature.

83 of 123Confirm

| Network Manager |

Up to six alphanumeric characters.Code:

Up to thirty charactersName:

An optional, free text field. This is used in ConfirmConnect® so that furtherinformation can be provided about the Observation Type in order to aid thesetting of the value.

Description:

Select from the pick list, the Parameter list that will be used in conjunctionwith this Type. The pick list references the Observation Parameter lookups

Parameter:

Select, from the drop down list, the Observation Impact that applies to thisType. The drop down list references the Observation Impact Lookup.

Impact:

Affects the order in which the Type appears in the Feature Condition screen.A type numbered 1 will appear at the top of the numbered list, a Type

Display Order:

numbered 9999 will appear at the bottom. Unnumbered Types will be listedbefore numbered ones.

Select from:Data Type:'Pick List' - To make Condition Grade selections from the pick list of availableparameter descriptions.'Numerical Value' - To assign Condition Grade by entering a numerical valuewithin the minimum and maximum score assigned to parameters.

Optionally specify a Device Data Key.Device Data Key:

84 of 123Confirm

| Network Manager |

ConfirmConnect® user whose data security group includes view access tothis data security key will be able to view this observation type on their Con-dition Survey tasks.

Leaving this field blank will allow all users to view this observationtype in ConfirmConnect®.

Note:

(Condition Survey - BCI Reports module)External Refer-ence: This field is used when creating the mapping between 'Full Name of Element'

to 'Component/Material Type' and 'Proximity to Traffic Spray Zone'. SeeStructure Toolkit Export System Settings for full details on configuringyour Structures data.

Observation Type - Feature Groups

Observation Types can be assigned to Features manually on the Feature screen, by associationwith a Feature Group - Conditions tab on page 55, or by using the Allocate Condition Valueson page 16.

Click on the 'Detail' button to display Observation Type Feature Group form.Use the Drop down to add a Feature Group. The drop down list referencesthe Feature Group lookup.

Feature Group:

Note: AnObservation Type can also be linked to a Group through the FeatureGroup - Conditions tab on page 55 lookup.

The screen also shows the UKPMSDefect Code and Severity detailsfor this Observation Type and Feature Group combination. The inform-

Note:

ation is not editable here but is maintained through the ObservationImport Codes screen.

Observation Type - Defect Types

It is possible to associate Defect Types with the current Observation Type so that when this Ob-servation Type is entered in the Defect screen the selection of Defect Types is limited to thosechecked here. This restriction will be applied when raising Defects directly in Confirm and whenusing ConfirmConnect®.

85 of 123Confirm

| Network Manager |

The Observation Types Defect Type tab lists all the Defects contained in the Defect library, noneof which are checked by default. Check those that may be used when this Observation Type isused.

Observation Type - Additional tab

Only relevant for the PMS Linear Assets module, this can be ignored for allother users.

Aggregation:

Select the method by which Observations of this Type being entered arecombined when fitting them to fixed lengths, merging etc. Length WeightedMean is the normal or most usual form of Aggregation for UKPMS.

The numerical value that is assigned to this observation type as a default. (Ifother than zero).

Default Value:

Checked by default, and should not normally be changed.Condition Assess-ment:

(Activity Log and Risk Assessment modules)Failure Mode:Check this for Observation Types that are being used for Risk Assessment,or for recording a Failure type in the Activity Log.

(PMS)Store Zero Values:Determines if the database will ignore zero values (the default), or, whenchecked, will actually store zeros as a legitimate data value.

86 of 123Confirm

| Network Manager |

(PMS)Functional Defect:When checked, during Data Analysis processes, all Observations will auto-matically break wherever any Functional Defect changes. Functional Defectsare relevant only in Automatic Condition Based Analysis processing andbeyond.Note: Functional Defects are defects that are not rated but a treatment isselected. e.g. SCRIM threshold.

(PMS)Base Date:Base Date is for use with Tranche 3 functionality - see relevant documentationfor more details.

Observation Parameter

The Observation Parameters are the 'grades' that can be assigned to different Observation Types.Many of the conditions (Observation Types) that may be observed on a defect will be identical formany different Observation Types e.g. 'Good', 'Fair' and 'Poor'. By using Observation Parametersthese grades only need be defined once and used on multiple Observations Types.In addition to setting out the condition grades the Parameters allow for these grades to be scored.The score is also used to provide a ‘Condition Rating’ for the Feature and does this by applyinga weighted value within a Feature Group e.g. a grade of 'Fair' providing a score of 5 will be multipliedby the weighted value specified in the Feature Group to provide a higher or lower score that con-tributes to the Features overall ‘Condition Rating’.Where Performance Monitoring is being used to monitor Features, as opposed to monitoringWorks, the assigned grade can be used to generate Failure Notices, based on the value of the‘Acceptable’ flag for the grade.Note: Once created an Observation Parameter may continue to be changed until it is used. Oncein use the value fields will no longer be editable and it may not be possible to add more Options.

Up to four alphanumeric charactersCode:

87 of 123Confirm

| Network Manager |

Up to 30 charactersName:

An optional free-text field. This is used in ConfirmConnect® so that furtherinformation can be provided about the Observation Parameter in order to aidthe setting of the value.

Full Description:

You may optionally select a unit of Measure for the scoring ('Percent' for in-stance, if the score values represent percentages, or 'Number' if the scoresrepresent number of problems found in the asset).

Unit of Measure:

(PMS - Observation Data - Module 4010)DefectivenessFactor: This can be used to modify the score value to provide a number or percentage

where the scoring is based on a length or area.Select the type of Defectiveness Factor from the drop down list and enter theDefectiveness Factor value in the adjacent field.

(PMS - Observation Data - Module 4010)Can be Aggreg-ated: This checkbox is ticked where aggregation of this Observation Parameter is

allowed.

(PMS - Observation Data - Module 4010)Can Record asPercentage: This checkbox is ticked where the Defectiveness Factor can be recorded as

a percentage rather than a pure number.

The lower portion of the form, entitled 'Options' is for the entry of each of the values that thisParameter will use.

Up to four alphanumeric charactersCode:

Up to 30 charactersName:

An optional free-text fieldOption Descrip-tion:

A numerical value may be optionally entered for this parameter option. If avalue is set, this will be assigned by default to any Feature that acquires this

Value:

Parameter Option. These Scores may be altered for any individual Featurewithin the Minimum and Maximum values set in the Minimum and Maximumfields.The value may be equal to the Minimum value but may only be equal to theMaximum value on the last option or if there is no difference between theMinimum and the Maximum values.

These fields are used to set the maximum and minimum scores that may beset for Features acquiring this Parameter Option.

Minimum\ Maxim-um:

Flag the 'Option' that will be used when the Feature does not currently carrya Grade. It is required that one Option be flagged as NA.

NA Value:

(Performance Monitoring)Acceptable:All Parameter Values are flagged as 'Acceptable' by default. The flag is re-moved for those Parameter Values that will attract a Failure under FeatureMonitoring.

88 of 123Confirm

| Network Manager |

Observation Impact

Observation Impact provides a means of grouping Observation Types together for reporting andfiltering.

Up to four alphanumeric charactersCode:

Up to 30 charactersDescription:

Survey Type

Survey Type defines the types of Survey that will be imported into Confirm PMS. From this screenthe Survey Name, Detail Level, etc. can be defined as well as the Feature Groups (i.e. Carriagewaybituminous, Footway flagged etc.) to which the Survey applies and the Observation Types thatthe Survey can contain.(Traffic Count Data module)Where the Traffic Count Data module is present, Traffic Count Survey Types can be created andtheir Time Slot Levels and Attribute Type (e.g. Vehicle Type) can be selected.

A unique code of up to 4 alpha/numeric characters.Code:

A 4 digit number. The same Survey Type may exist with different versionnumbers.

Version:

A 30 character description as appropriate for each Survey Type.Name:

The Detail Level is chosen from the dropdown list. This indicates the level ofdetail that this Survey produces. The entries are for information only. Theoptions are Coarse and Detailed.

Detail Level:

89 of 123Confirm

| Network Manager |

This checkbox is used to mark the Survey Type as no longer live or in use.The details remain held on the Database and the Survey Type can be madelive by 'unmarking' the checkbox.

Dead:

The Source Type is chosen from the dropdown list. This defines the sourceof the Survey data. This is for information purposes only. The options are:

Source Type:

• Visual• Machine Based• Aggregated• Traffic Count (only available when the Traffic Count Data module is present.)

This checkbox is used to indicate if Observations that extend past the end ofa Section will be trimmed.

Trim Obs.:

(Traffic Count Data module)Time Slot Level:Time Slot Level is only enabled when the Source Type is set to Traffic Count.Select from the drop down list the Time Slot Level that applies to the SurveyType. Time Slot Level is a mandatory field and determines which Time Slotsare displayed against a Traffic Count Survey.The Time Slot Level cannot be edited for Survey Types which have TrafficCount Surveys created against them.

(Traffic Count Data module)Aggr. Slot Level:Aggr. Slot Level is only enabled when the Source Type is set to Traffic Countand the Time Slot Level field has been populated.Optionally select from the drop list the Time Slot Level that will be used tocalculate the aggegrate Time Slots for this Survey Type. The Values of theaggregate Time Slots are calculated by adding the Values of the Time Slotsfrom the primary Time Slot Level that fall within the Start Time and End Timeof the aggregate Time Slot.It is not possible to select the same Time Slot Level record in both the TimeSlot Level field and the Aggr. Slot Level field.The Aggr. Slot Level cannot be edited for Survey Types which have TrafficCount Surveys created against them.

(Traffic Count Data module)Attribute Type:Attribute Type is only enabled when the Source Type is set to Traffic Count.Select from the drop down list the Attribute Type that applies to the SurveyType. Attribute Type is an optional field and determines whether a TrafficCount Survey is broken down by Attribute Type (e.g. Vehicle Type) and TimeSlot, or just by Time Slot.Attribute Type cannot be edited for Survey Types which have Traffic CountSurveys created against them.

This defines howmuch of a difference between imported Survey data lengthsand actual Section lengths will be accepted (the units are defined in terms ofthe Section measurement type).

Absolute LengthTolerance:

This defines howmuch of a difference between imported Survey data lengthsand actual Section lengths will be accepted. The value is entered as a per-centage of the Section length.

Percent LengthTolerance:

90 of 123Confirm

| Network Manager |

Feature Groups Tab

The Feature Groups tab lists those feature groups on which this survey may contain observations.E.g. For CVI survey, this includes various types of carriageway, as well as cycletracks, kerbs,footways and verges.

Clicking on the 'Detail' button on the Survey Type screen with the Feature Groups tab selectedwill display the Survey Type Feature Group screen. From this screen you can add a new featuregroup or delete an existing feature group.

Observation Types Tab

The Observation Types tab lists those Observation Types applicable to be recorded on Surveysof this Survey Type.

Clicking on the 'Detail' button will display the Survey Type Observation Type screen. In this screenObservation Types can be added to or removed from the Survey Type.

A Parent Observation Type may be specified if an Observation Type is to be stored as an additionalvalue on an Observation record, rather than being an entry in the database in its own right. In thiscase, a Sequence Number should also be specified. Observation Types with a Parent ObservationType are distinguished in the list by the Sequence Number being displayed in front of the Code.

A Parent Observation Type may not be specified for an Observation Type which is itselfthe Parent Observation Type for others.

Note:

Action Officer

Action Officers have responsibility for certain actions carried out within Confirm. For instance: Jobsare assigned to Action Officers, and each stage (Status) of the Job's life is associated with anAction Officer.

91 of 123Confirm

| Network Manager |

Action Officers can be linked to Users, so that when a User logs in to Confirm they are recognisedas a particular Action Officer. Action Officers need not be users - they can be created independentlyof User logins.

Up to four alphanumeric charactersCode:

Tick this to prevent new records from being assigned to the current ActionOfficer. Confirm will not allow an Action Officer to be 'Inactive' if it is used onthe Enquiry Subject or Enquiry Subject Site records.

Inactive:

If an Action Officer needs to be active again, untick this setting. If the linkedUser is also 'Inactive' Confirm will request that the User is activated first beforethe Action Officer can be.

Up to 30 charactersName:

(Optional)Telephone Num-ber: Up to 20 alphanumeric characters

(Optional)External Ref.Up to 20 alphanumeric characters. A reference used by external systems toidentify this Action Officer

(Optional)Corresponds toUser: Select a User to link this Action Officer to. By linking an Action Officer to a

User, Confirm will know which Action Officer to use by default when usingvarious entry screens within Confirm.The User ID can be typed directly into the field or the pick button can be usedto search for a User to link the Action Officer to.System Administration\SecurityNote: Contractor Users are not able to remove the value in this field.

Where the Action Officer is linked with a User - the Work Group to which theUser belongs is entered and the field cannot be edited.

Work Group:

Where an Action Officer is not linked with a User - a Work Group must beselected.The drop down list references the Work Groups list.System Administration\Security

Setting this value gives Enquiries assigned to this Action Officer additionalsecurity.

Enquiries DataKey:

Where an Enquiry is assigned to an Action Officer with this Data Key set, onlyUsers with Data Key access to the Enquiry Subject and the assigned ActionOfficer's Enquiries Data Key will be able to view the Enquiry.

(Performance Monitoring module)Inspecting Officer:Where Monitoring Batches are created automatically at Request Checking,the Action Officer associated with the last Job Status log on the Job is usedto determine who should be the Inspecting officer based on the entry in thisfield.

Device Settings(Optional - ConfirmConnect® - Condition Survey)Default Priority:

92 of 123Confirm

| Network Manager |

Enter the Priority that will be assigned to Jobs raised through the 'Fast Defect'functionality in Condition Survey on the device.

(Confirm Connector)Device Data Key:Optionally specify a Data Key to restrict which Users will have this lookupavailable on the device. Please see the Confirm Connect manual for furtherdetails.Note: This lookup will still be transferred, it will simply be hidden from theUser when logged into the device.

(Jobs in the Field module)Device Job Of-ficer: Check this to set the current Action Officer as an Officer which will have 'Job'

tasks sent to the device when they transfer their tasks.

Redirect Tasks to the selected Officer in case of absence. It is only possibleto redirect to an Officer in the same Workgroup.

Task Redirect Of-ficer:

It is possible to redirect multiple Officers to the same Officer. If theOfficer has other Officers redirecting to them, it will not be possible

Note:

to redirect this Officer to another. Use the Action Officer List to viewany existing Officer Redirects.

Street Works Settings(Optional - Street Works module)Route:Select a Route. The pick list references the Site Route lookup.Site Register\Site Lookups\Operational LookupsNote: The Route provides a default entry for Inspection Sampling in StreetWorks. It is not relevant in any other context.

(Optional - Street Works module)No of Inspections:Enter the maximum number of Sampled Programmed Inspections an ActionOfficer may have outstanding at any time. This limit does not include nonSampled Programmed Inspections, such as Defect Follow Up Inspections,which are already assigned to the Action Officer.

(Optional - Street Works module)Organisation:Enter an Organisation to provide a default entry in the 'From' field of the StreetWork Notice window for this Action OfficerNote: The default is only provided where the Action Officer is linked to a User,since the identification of the Action Officer is made by reference to the Userwho is currently logged in.

(Optional - Works Management module)Labour Type:Select the Labour Type for the Action Officer if they are the member of aGang. The pick list references the Labour lookup.Works Management\Works Costing\Works Costing Lookups

(Optional - Works Management module)Cost per hour:

93 of 123Confirm

| Network Manager |

This will override the Cost per hour specified in the linked Labour Type. Costper hour on Action Officer is multiplied with Cost per hour multiplier on theLabour Type Lookup to determine the Action Officer’s labour rate.

Action Officers can be assigned an area of specialism defined by Feature Groups, with the AssetSpecialist module. Please see the Specialist section for details.

Notebook Code

Used to set up Notebook Codes.

A unique code of up to 4 alpha/numeric characters.Code:

A free form text description of virtually unlimited length.Note Text:

Network Import Settings

The Network Import Settings screen provides settings relating to the import and export of Network,Inventory and Survey data.

When a Feature in a Network import file contains no Site inform-ation, it will be assigned to this Site.

Default SiteNetwork Data

In each case, the Attribute Type to which this field in a Networkimport file is to be assigned.

DTPCLASS,STEPLEVEL,FWAYOPEN,etc.

The Attribute Type to which Construction Type is to be assigned.ConstructionType

Inventory Data

The Attribute Type to which Kerb Material is to be assigned.Kerb Material

The length tolerance for Inventory Import is entered here as bothan absolute length and as a percentage of the section length.

Length Toler-ance

These fields are in 6.2 format, i.e. 6 numbers before and 2numbers after the decimal point.

This is the XSP position to which imported condition data defaultsif no XSP data is provided in the Survey Data Import file(s) oron the Survey Observation screen.

Default XSP

By default, Import Survey Data will reject any Survey files con-taining one or more Survey Features with no Observations and

Allow import ofSurvey with no

Condition Data

94 of 123Confirm

| Network Manager |

report an error. If this setting is checked, then a warning will bereported and it is possible to proceed with importing the Survey.

Observationsfor a Feature

When importing survey data in HMDIF format observation resultsshould be provided in either an option or value field, depending

Allow eitherOption or

on the observation type. Setting this allows the observation valueValue to beto be supplied in the value field where the parameter is primarilyan option one, or vice versa.

supplied forObservations

Ticking this box will add extra validation to some of the valuesin exported files. Specifically:

Restrict expor-ted values to

HMDIF Export

official UKPMSvalues • When an HMDIF Network file is exported, any values in the

HIER and FWHIER fields that do not correspond to a UKPMSstandard code will be ignored and an empty string exported.

• When an HMDIF Survey file is exported, if there are non-nu-meric characters in the Survey External Reference field thenthe Survey Number will be exported as NUMBER instead.

• When an HMDIF Survey file is exported, the NUMBER field islimited to 4 digits and the MACHINE field is limited to 5 charac-ters.

Observation Import Codes

The Observation Feature Group Import Codes facility is used to define how codes in the surveyare translated, if necessary, when imported into Confirm, based on the inventory to which theyrelate. The translation of these codes is based on the requirements of the Rules and Parametersset or sets being used for processing.

The columns for Observation Type, Code and Feature Group are generated automatically byConfirm from the database. They are based on the observation types that have been entered andthe feature groups that were listed against them.

A code of up to 4 alpha/numeric characters. This is the code in the survey import file that is requiredto be mapped against the Feature Group and Observation Type combination. E.g. In the abovescreen, it can be seen that the combination of Major Cracking (Observation Type) FBCJ (Code),and the Feature Group of Footway Bituminous, is translated from the FBCJ (Import) code in thesurvey import file.

The version number for the survey can be entered here or the field left blank.

95 of 123Confirm

| Network Manager |

The severity of the defect can be entered here if additional information is required to identify towhich Observation Type and Feature Group combination a survey defect code should be translated.

The Default checkbox is used to specify the default selection when Ver. or Sev. Data is omittedand a survey defect code (Import) could relate to 2 or more Observation Type and Feature Groupcombinations.

Network System Settings

The Network System Settings screen allows the setting of several default options relating to theNetwork.

The XSP for Default Inventory is entered here using the drop down that liststhe descriptions of all the defined XSP's. Care should be taken where user

XSP for DefaultInv.:

defined XSP's not included in the Rules & Parameters set have been definedto ensure that data is not defined to an XSP that is not used in the data ana-lyser processing.

Select the XSP that will be used by default for Features being added to a'Machine' Inspection Route.

Inspection RouteXSP:

The Survey and Analyse field is completed using the drop downwhich containsthe two pre-set options of 'All Groups' or 'PMS Sections Only'. This toggles

Survey and Ana-lyse:

between a PMS only analysis and the facility to use the Data Analyser on allgroups.

This setting is used by the Network Indicator List (the BVPI report) which re-ports on how much of the Network has been Surveyed. You may exclude

Not AssessedObsParm:

section lengths with the indicated Parameter recorded from the report totalsby entering the Parameter here. The pick list references the ObservationParameter Lookup.

For Footway Observations, the Section's Footway Hierarchy Attribute is usedas a default in the absence of Inventory, in preference to the Section's SiteClassification. Select the Inventory Type that corresponds to Footway.

Footway InventoryType:

The Nodes Mandatory check box should normally be checked so that thesystem requires all street sections to have start and end nodes. In this situ-

NodesMandatory:

ation, nodes will also have to be defined if a section is to be split. If the checkbox is unchecked sections can be defined or split without start and end nodes.

96 of 123Confirm

| Network Manager |

Note: This setting is not enforced for ESU Features.

Note: Nodes are mandatory in UKPMS for machine surveys so it is recom-mended that mandatory nodes is always set except where only visual inspec-tion surveys will ever be carried out.

This checkbox should be completed to have the system complete the surveychainage automatically if left blank.

Set Survey Chain-age if blank:

Survey Seed Numbers

Seed numbers for survey related items are set from this screen. Survey Seeds are primarily usedby the internal working of Confirm. For most uses it is sufficient to set the range from 1 to 9999999for all fields.

This is the Work Group code to which the seed Numbers relate.WorkGroupCode:

The Name of the Work Group.Name:

This is the range of survey typeSurvey Types:

This is the range for Observation TypesObservationTypes:

This is the range for SurveysSurveys:

This is the range for Survey FeaturesSurvey Features:

This is the range for TreatmentsTreatments:

97 of 123Confirm

| Network Manager |

HDM-4 InterfaceHDM-4 Interface contains libraries and utilities that can be configured to interface Confirm with HDM-4.

It allows Confirm asset and survey data to be sent to HDM-4 for strategy and program analysis. Theinterface is compliant with HDM-4 version 2.08

Strategy Analysis Interface

Strategy Analysis Interface screen updates HDM-4 strategy analysis database file for NSM IDlengths as calculated from selections made in Homogenisation System Settings screen.

Filters asset data, corresponding inventory data and survey observations tobe considered for strategy analysis. Data that is latest and live as on Effective

Effective Date:

Date is considered. In case it is not set, system date is considered as EffectiveDate.

If checked, Strategy Analysis Interface RUN uses absolute homogenous datagenerated and does not consider merge algorithm to compute PRS sectionsfor updating NSM lengths. It is unchecked by default.

Use UnmergedData:

Displays all named selections in the system. It filters homogenous sectionsunder consideration for strategy analysis to those passing named selection.

Feature NamedSelection:

N.B: User is expected to choose a named selection that belongs to featureGroup selected on Homogenisation System Settings screen.

Points to HDM-4 strategy analysis NSM ID file that needs to be used to updateNSM ID lengths. It supports MS access database formats.

NSM Input File:

98 of 123Confirm

| Network Manager |

Output file that will be created using NSM input file. This NSM output file willbe updated for NSM ID lengths on Run. NSM ID length is limited by MaximumNSM Length set on HDM-4 System Setting - General Tab.

NSM Output File:

Enables the functionality to correct effective year of existing alternatives andmultiply them to create new set(s) of maintenance alternatives for HDM-4strategy analysis mdb database on RUN.

Maintenance Al-ternatives:

Defines Start Year of strategy analysis in Strategy Output File.Start Year:

Number of times that the original proposed alternatives will be repeated inthe strategy analysis.

Number of BudgetPeriods:

Number of years to space between the generated alternatives.Budget PeriodLength (Years):

Numbers of years by which all existing non-base alternatives (and new altern-atives) should be delayed.

Delay Mainten-ance by (Years):

Points to HDM-4 strategy database file to correct and multiply maintenancealternatives.

Strategy InputFile:

Output file that will be created using Strategy Input File with corrected andnew multiplied alternatives.

Strategy OutputFile:

Updates section length in NSM Output file with system generated PRS databy default or absolute homogenous data if Use Unmerged Data is checked.

Run:

Corrects existing alternatives and create new maintenance alternatives.Refer Strategy Analysis andMaintenance Alternatives inHDM-4 InterfaceReference Manual for details of actions performed.

Programme Analysis Interface

Programme Analysis Interface screen updates HDM-4 road network mdb file with planning roadsections (PRS) generated from Confirm. It also generates HDM-4 programme mdb file with trafficdata, traffic growth sets and maintenance alternatives assigned to each PRS section. Settingsmade inHomogenisation SystemSettings andHDM-4 SystemSettings screen are used whilerunning Programme Analysis Interface.

99 of 123Confirm

| Network Manager |

Filters asset data, corresponding inventory data and survey observations tobe considered for programme analysis. Data that is latest and live as on Ef-

Effective Date:

fective Date is considered. In case it is not set, system date is considered asEffective Date.

Displays all named selections in the system. It will limit the homogenoussections under consideration for programme analysis to those passing namedselection.

Feature NamedSelection:

User is expected to choose a named selection that belongs to featureGroup selected on Homogenisation System Settings screen.

Note:

Points to HDM-4 NSM ID file that needs to be used to generate PRS file. Itsupports MS access database formats.

NSM Input File:

Output file that will be created using NSM input file. This network output filewill be updated with PRS sections and traffic data on ‘Run’. PRS data is cre-

Network OutputFile:

ated as per settings onHomogenisation SystemSettings screen and usingMerge Method applied.

Enables the section to create programme mdb database on RUN.Programme:

Defines start year of programme analysis in programme database file.Start Year:

Number of times that the original proposed alternatives in the strategy analysiswill be repeated in programme output file.

Number of BudgetPeriods:

Number of years to space between the generated alternatives in programmeoutput file.

Budget PeriodLength (Years):

Number of years by which all existing non-base alternatives (and new altern-atives) should be delayed in programme output file.

Delay Mainten-ance by (Years):

Points to HDM-4 strategy database file that is required to generate programmedatabase file with maintenance alternatives. It supports MS access databaseformats.

Strategy InputFile:

Programme Output file that will be created to have –Programme Out-put File: • PRS references from PRS Output File

100 of 123Confirm

| Network Manager |

• Populated with corrected and new multiplied alternatives using StrategyInput File.

Inserts PRS data from Confirm into Network Output file and creates pro-gramme database file to Programme Output File path.

Run:

Refer Programme Analysis and Maintenance Alternatives in HDM-4 Interface Reference Manual for actions performed on RUN button

Note:

• Existing Alternatives from Strategy Input file are Inserted in Programme Output file by mappingSECT_ID of Prg_Selsections file to the SECT_ID of Str_SelSections file using NSM ID in homo-genous data internally generated in Confirm.

• Correction of existing alternatives' effective year as per start year and specified.

Homogenous Data Report

Homogenous Data Report screen is used to generate homogenised data from Confirm data. Onclick of OK button, a csv report is generated as per selections made on Homogenisation SystemSettings screen.

Filters asset data, corresponding inventory data and survey observationsto be considered for strategy analysis. Data that is latest and live as on

Effective Date

Effective Date is considered. In case it is not set, system date is con-sidered as Effective Date.

Displays all named selections in the system. It filters homogenous sec-tions under consideration for report output to those passing named se-lection.

Feature Named Selec-tion

Local or network path where output .csv report will be placed.Export file path

If checked, homogenised data is merged in report output as per MergeMethod applied on Homogenisation System Settings screen.

Merge

If checked, individual XSPs as defined at feature inventory and surveyobservation level are used for report output. In default (unchecked) state,

Use Individual XSPs

all data is aggregated into single ‘All’ XSP level. Report output with ‘All’XSP is used in Strategy Analysis Interface and Programme AnalysisInterface .

The output file contains road sections that are homogenised for Feature-XSP combination.

101 of 123Confirm

| Network Manager |

File FormatFor output road sections (fixed columns starting from 1st column)

DescriptionColumn NameAsset ID of output road sectionFeature_ID

Cross section position, cannot be NULL. Aggregates to ‘All’ by defaultXSP

Start distance/ chainage point, cannot be NULLStart_Distance

End distance/ chainage point, cannot be NULLEnd_Distance

Absolute difference of Start_Distance and End_DistanceSubsection_length

Site codeSite_Code

Site name as specified in ConfirmSite_Name

Feature locationLocation

Feature type codeFeature_Type

Area codeArea_CodeContract area codeContract_Area

Classification codeClassification

Feature 'primary measurement' specified on feature group. The reportalways renames it to Section_Length as homogenisation is done only

Section_Length

on linear features. It should be set to linear metrics (like linear meters,meters, millimeters)

After fixed column, user defined inventory attributes as selected on Homogenisation SystemSettings - Inventory Tab are listed:

• Columns are displayed in same order as inventory attributes selected.• Format of column display is {inventory type code}_{attribute type code}.• Average width attribute is displayed as {inventory type code}_WDTH.• Survey Date is displayed as {inventory type code}_SRDT.• Inventory which does not vary by XSP is merged with all other inventory on same feature thatvary by XSP.

After user defined inventory attributes, user defined survey observation as selected onHomogen-isation System Settings-Survey Tab are listed:

• Columns are displayed in same order as survey observations selected.• Format of column display is {survey type code}_{observation type code}.• Survey Observations on feature and/or inventory matching 'Feature Group' selected on Homo-genisation System Settings only are part of report output.

• Point observations are not part of report output and are ignored.

After user defined Survey observation columns, Computed Columns as defined onHomogenisationSystem Settings-Computed Columns Tab are listed:

• Columns are displayed in same order as defined.• Format of column display is {Expression Name}.

After user defined inventory, survey and Computed columns, HDM-4 System Settings screenselections are listed in following order:

• 'nsm_id', 'traffic_growth_set'. These columns map to NSM_ID and Traffic Growth Set respectivelyon HDM-4 System Settings screen-General tab.

102 of 123Confirm

| Network Manager |

• 'traffic_grwoth_set', this column maps to Traffic Growth Set on HDM-4 System Settings screen-General tab.

• 'exclude_if_true', this column maps to Exclude if True on HDM-4 System Settings screen-Gen-eral tab.

• {HDM-4 Field} as selected on HDM-4 System Settings screen-Sections tab.

Homogenisation System Settings

Homogenisation System Settings Screen allows user to select asset Inventory and Survey basedon which asset data is homogenised. The homogenised data is available as output through Ho-mogeneous Data report. It can also be interfaced directly to HDM-4 database files throughStrategy Analysis Interface or Programme Analysis Interface.

Feature Group: This drop down lists those Feature Group that are of Feature Group Class: LinearAsset.

103 of 123Confirm

| Network Manager |

Minimum Section Length: A section will not be split any further if either of the resulting sub-sections would be shorter than the specified minimum section length. It is used in ProgrammeAnalysis Interface and merged Homogenous Data Report.

Maximum Section Length: If all of the variables on a section are within tolerance the section willstill be split if it is longer than the specified maximum section length. This is constrained by outputof unmerged homogeneous data, which means, any sub section in unmerged (or absolute) homo-genous data cannot be split further. It is used in Programme Analysis Interface and merged Ho-mogenous Data Report.

Feature Inventory and Survey tabs lists corresponding Inventory Type and Survey Type basedon which asset data is homogenised.

Merge Method

The merge Method algorithm works by first considering the whole length of the road section anddeciding whether all of the specified variables are within tolerance over the entire length. If not,or if the section is longer than theMaximum Section Length, then the section will be split in two.The algorithm decides on the best place to split the section by finding the split point that minimisesthe overall variance of the specified variables. This whole process is then repeated for the tworesulting sections, i.e. deciding whether they need to be split further and if so where to split themuntil all of the variables are within tolerance or the Minimum Section Length is reached.

The algorithms used to determine whether to split and where to split are discussed in more detailbelow:

For the current section, each variable is considered in the order of itsWeighting (highest weightingfirst) to see if it is within tolerance. A Continuous (or numerical) variable is considered outsidetolerance if any minimum length subsection can be found whose mean value is different from theoverall mean value for the section by the specified maximum Difference. A Dominant (or non-numerical) variable is considered to be outside tolerance if any minimum length subsection hasa dominant value which is different from the dominant value of the whole section.

If a variable is found to be outside tolerance then this variable and all of the other variables withthe same or higherWeighting are used to determine where to split the section. If no variablesare outside tolerance but the section is still longer than the Maximum Section Length then allvariables are used to determine where to split.

The algorithm determines where to split by considering each possible split point along the lengthof the section that would not result in a length shorter than the Minimum Section Length. Foreach possible split point the length weighted variance of each variable is calculated. The variancesfor each of the selected variables are multiplied by their respectiveWeighting and added togetherto give an overall variance for the chosen split point. The split point that results in the lowestoverall variance is then chosen and the whole process repeat for the two resulting sections.

Average:Only applies to numeric values and used where a mathematical mean and variance canbe calculated

Dominant: Applied to non-numeric values or numeric values where a mathematical mean wouldnot be appropriate. The dominant value is the value that occurs on the most subsections, basedon their total length. Variance is calculated by comparing each individual value with the dominantvalue, with any values that are different having a variance of one.

Weighting: Only variables with a non-zero weighting are considered when determining whetherand where to split. Variables are considered in weighting order (highest first) to determine whethera split is needed. The weighting is also used to factor the variance of each variable when consid-ering where to split.

Difference: Used to determine whether to split Continuous variables with a non-zero weighting.If any minimum length subsection has a mean value that is more than this difference from theoverall mean then the section will be split

104 of 123Confirm

| Network Manager |

Show selected items only: If checked, only selected and saved options are displayed in FeatureInventory and Survey tab.

Show names in expression builder: If checked, 'Columns' in expression builder on HDM-4System Settings screen are displayed as Inventory attribute (or Observation type) names followedby code for feature inventory and survey observations selected on Homogenisation SystemSettingsscreen. Also homogeneous data report displays names followed by code.

Note: Asset data homogenisation refers to dividing asset data in chainages such that value of aninventory attribute and an observation type selected does not change across unique chainage-cross section position in homogenised output.

Homogenisation System Settings - Feature Inventory tab

Based on Feature Group selected, feature inventory tab lists Inventory Types and attributes ofassociated Inventory Feature Groups. Both inventory types and attributes are displayed as namefollowed by code as defined in Confirm. Attributes are grouped by inventory types and are userselectable.

105 of 123Confirm

| Network Manager |

For example, in the screen shot above HDM-4 Pavement Strength (RPVS) is an inventory typein Confirm and HDM4-SNP (INSP) is an attribute associated with it.

Note:

1) Only those Inventory Types are listed that pass the following criteria:

• Item Type is one of the following:Linear (NoWidth), Linear (Width), Area (OneWidth), Area (TwoWidths)

• None of the Allow multiples check box is checked.• Vary by Attribute is set to null or blank.

2) Average width and/or Survey Date are first inventory attribute(s) by default if Inventory Typehas width and/or Show Survey Date enabled. Both These attributes do not display code becausethey are system defined and not user defined.

Homogenisation System Settings - Survey tab

Survey tab lists all survey types and associated parent/child observation types configured inConfirm. Child observation types are grouped by parent Observation Type and are displayed intree-like structure. Further observation types are grouped by survey types and are user selectable.Selecting any child observation type will automatically select its parent observation type. Conversely,deselecting a parent will deselect all child observation types associated with it.

Both survey and observation types are displayed as name followed by code as defined in Confirm.

106 of 123Confirm

| Network Manager |

For example, in the screen shot above Machine Live (HDM) is a Survey Type in Confirm andHDM4 - Cracking (Asphalt) (CCRA) is anObservation Type associated with it. HDM4 - Cracking(Concrete) (CCRC) comes next prefixed by hyphen (--). This indicates that CCRC is child obser-vation type of CCRA.

Only those Survey types are displayed which have Source Type as Visual or Machine Based. Thelist displays dead survey and associated observation types as well.

Only those Observation Types that are selected by the user, participate in data homogenisation.

An observation type is displayed with survey type, despite being detached from it if andonly if Observation type was previously selected on Homogenisation System Settingsscreen.

Note:

Homogenisation System Settings - Computed Columns tab

Computed Column tab provides an interface to create expressions, which can be used as interme-diate expressions while creating expressions on HDM-4 System Settings. The evaluated valuesare also displayed on Homogenous Data Report for each row of output data.

107 of 123Confirm

| Network Manager |

Name given to expression. This name is available as column in expressionbuilder on HDM-4 System Settings screen and Homogenous Data Report. It

Expression Name

is free text alphanumeric field allowing up to 30 characters and cannot beduplicate.

Provides expression builder to build expression around fixed columns, userdefined inventory attributes and user defined survey observations.

Expression

Both fields need to exist for a valid expression.

HDM-4 System Settings

HDM-4 System Settings screen provides an interface to map HDM-4 field(s) with homogeniseddata output from Confirm. The mapping is through an expression builder which provides capabilityto write expressions on feature inventory attributes and survey observation types selected in Ho-mogenisation System Settings screen. The value calculated as per expression is inserted intocorresponding HDM-4 field(s) when Strategy Analysis or Program Analysis is done.

108 of 123Confirm

| Network Manager |

Expression builderExpression builder provides capability to write expressions on feature inventory attributes andsurvey observation types selected in Homogenisation System Settings screen.

The buttonagainst each label will open the Confirm Expression builder screen.

109 of 123Confirm

| Network Manager |

Double click on Functions in the Function list, and Columns in the Columns list, to build up anExpression in the Expression field. You may also directly edit the Expression, and add operatorsfrom the buttons on the left-hand side.Columns displayed are in following order:

• Fixed columnswhich are Feature_ID, XSP, Start_Distance, End_Distance, Site_Code, Site_Name,Location, Feature_Type, Contract_Area, Classification, Section_Length.

• User defined inventory attributes as selected onHomogenisation System Settings - InventoryTab in {inventory type code}_{attribute type code} format. If 'Show names in expression builder'is checked on HDM-4 System Setting - General Tab, format is {attribute type Name}({inventorytype code}_{attribute type code}).

• User defined survey observations as selected on Homogenisation System Settings - SurveyTab in{survey type code}_{observation type code} format. If 'Show names in expression builder'is checked onHDM-4 System Setting - General Tab, format is {Observation type name}({surveytype code}_{observation type code}).

• Expression Names as defined on Homogenisation System Settings – Computed ColumnsTab.

If user defined columns contain any special character other than an underscore ‘_’, it is replacedby an underscore ‘_’ and appended a number 1. If such replacements result in two identical codes,the next code is appended a number 2. Like:

Code in expression builderCode inHomogenisa-tion System Settings

Inventory AttributeInventory Type

TY_P_AT_B1TY#P_AT#BAT@BTY#P

TY_P_AT_B2TY#P_AT$BAT$BTY#P

Expression builder evaluated value should match with corresponding HDM-4 mdb database ac-ceptable data type and range. If expression against a field is null, it is considered as 'blank' fortext and '0' for numeric fields. For details, refer HDM-4 Database Mapping in HDM-4 InterfaceReference Manual.

110 of 123Confirm

| Network Manager |

HDM-4 System Settings Sections tab

Sections tab provides an interface to map homogenised data output from Confirm with HDM-4fields as available in sections table of HDM-4 road network mdb file.

• The value calculated as per expression is inserted into corresponding HDM-4 field(s) in roadnetwork mdb file when Programme Analysis Interface is 'Run'.

• All HDM-4 field(s) saved on this screen also gets listed on Homogenous Data Report as columnswhen HomogeneousData Report is run. The value calculated as per expression of each HDM-4 field is assigned to corresponding road section element in the report output.

Lists all columns contained in SECTIONS table of HDM-4 road network mdbfile. User can select or search any field from drop down list and build map itto Confirm data using expression.

A mapping of HDM-4 field column names (with their data types) to HDM-4 UIlabels is provided at HDM-4 Road Network Database Mapping in HDM-4Interface reference Manual for commonly used fields/columns.

HDM-4 field:

User editable free text field to describe HDM-4 field selected.Description:

Provides expression builder to build expression around fields of HomogenousData Report. The value of each expression is inserted into corresponding

Expression:

HDM-4 field(s) in HDM-4 road network mdb file when Program Analysis Inter-face is 'Run'.

HDM-4 System Settings Traffic tab

Traffic tab provides an interface to map homogenised data output from Confirm with HDM-4 fieldsas available in Traffic table of HDM-4 road network mdb file. VEH_ID, CATEGORY and valuecalculated as per expression is inserted into HDM-4 Traffic table in road network mdb file whenProgramme Analysis Interface is ‘Run’.

111 of 123Confirm

| Network Manager |

Mapped to YEAR column in TRAFFIC table of HDM-4 road section mdb file.Survey Year

User editable free text field to describe VEH_ID and CATEGORY combination.Vehicle TypeName

User editable field to contain whole numbers. Mapped to VEH_ID column inTRAFFIC table of HDM-4 road section mdb file.

VEH_ID

User editable field to contain whole numbers. Mapped to VEH_CAT columnin TRAFFIC table of HDM-4 road section mdb file.

VEH_CAT

Provides expression builder to build expression around fields of HomogenousData Report. Its value is mapped to AADT column in TRAFFIC table of HDM-4 road section mdb file

Expression

Combination of VEH_ID, CATEGORY has to be unique on the grid. User needs to map VEH_ID,CATEGORY to the structure defined (and intended to be used) for Vehicle fleet in HDM-4. Thesame can be found in Vehicle fleet mdb file (Selecting defined Vehicle fleet and using Exportbutton in HDM-4)

The complete grid as defined on Traffic tab (VEH_ID, CATEGORY and evaluated Expression) isinserted for each road section inserted. And Survey Year as evaluated is applied to each row in-serted in Traffic table of HDM-4 road section mdb file.

HDM-4 System Settings General tab

112 of 123Confirm

| Network Manager |

Maps HDM-4 NSM road sections to Confirm homogeneous road sections inHDM-4 NSM Input File (mapped to SECT_ID column of Sections table) forStrategy Analysis Interface and Programme Analysis Interface.

NSM ID

HDM-4 Road Network Database Mapping for details on NSM ID.Note:

Assigns Traffic Growth Set to each road section on RUN of ProgrammeAnalysis Interface. It is mapped to GRTHSET_NAME column of Prg_sec-SecVehGrthSet table in Programme output file.

Traffic Growth Set

Programme Analysis details affected table and columns.

Evaluates the expression for each row (road section) of homogenised dataoutput. Road sections that evaluate to true/TRUE as per Boolean or conditional

Exclude if True

expression are filtered to be excluded from Strategy Analysis (non-mergeddata) and Programme Analysis (merged data).

Maximum NSM length allowed by system while running Strategy AnalysisInterface. Any NSM exceeding the specified length splits existing NSM ID.

Maximum NSMSection Length

No value specifies is considered as no limit set. For details, refer StrategyAnalysis.

113 of 123Confirm

| Network Manager |

HDM-4 Interface Reference ManualHDM-4 Interface Reference Manual specifies the requirements, considerations and mapping of ConfirmHDM-4 Interface and mapping with HDM-4 v2.08 databases.

Strategy Analysis

On RUN of Strategy Analysis Interface:

• Creates copy of NSM Input file to NSM output file location.• Homogenise data internally based on settings in Homogenisation System Settings screen, tohave absolute homogenised sections.

• Computes NSM ID as per expression in HDM- 4 System Settings screen for each row of homo-genised data.

• In NSM output file (mdb), finds match of calculated NSM ID to existing NSM ID, which is storedin 'SECT_ID' column of 'SECTIONS' table.

• Updates 'LENGTH' in the 'SECTIONS' table of the NSM Output File (mdb) with total length ofeach matching NSM ID.

• Section in HDM-4 'SECTIONS' table which does not find an NSM ID match in Confim's homo-genised data are deleted from NSM Output file.

• A warnings is logged if Confirm calculated NSM IDs does not find a match in 'SECT_ID' columnof 'SECTIONS' table in NSM Output File (mdb).

If Maintenance alternatives is checked, Strategy Output file is created by copying Strategy InputFile and following actions performed on it:

• STRATEGY table update

Updated ValueSTRATEGY table columnStart Year specifiedSTART_YEAR

END_YEAR + Shift in original START_ YEAREND_YEAR

Count of rows in Str_SelSections tableNUM_SECSEL

• Correction of existing alternatives' effective year as per start year and specified.

Updated ValueStr_SectOptMaint table columnUpdated with total number of alternatives foreach SEC_ID in Str_sectOptDesc

EFF_YEAR + Shift in original START_ YEARfor all base alternatives

EFF_YEAR + Shift in original START_ YEAR +delay for all non- base alternatives

• Multiplication of existing maintenance alternatives to create new alternatives as per number ofbudget periods, budget period length (years), delay maintenance by (years) specified and usinglogic described in Maintenance Alternatives. Tables updated are:

Updated ValueStr_sectAnalOptions table columnUpdated with total number of alternatives foreach SEC_ID in Str_sectOptDesc

NUMOPTIONS

114 of 123Confirm

| Network Manager |

Updated ValueStr_sectOptDesc table columnUpdated for non –base alternatives 'mainten-ance standards by appending EFF_YEAR, ifdelay is specified

OPT_DESC

As per Maintenance Alternatives logicNew Rows Inserted

Updated ValueStr_sectOptMaint table columnUpdated for non –base alternatives ' mainten-ance standards, if delay is specified

MAINTIT_ID

As per Maintenance Alternatives logicNew Rows Inserted

• If any NSM ID length as computed by Confirm exceeds the Maximum Section NSM Length seton HDM-4 System Setting - General Tab, SECTIONS table is updated in NSM output file withnew NSM records and corresponding entries are made in other tables of NSM output file andStrategy Output file.

For example, following is one of the existing SECTION data in NSM input file

SECT_ID : A

SECT_NAME: Section A

It has corresponding entries in TRAFFIC table of Network file. It also has corresponding entriesin Str_SelSections, Str_secSecVehGrthSet, Str_sectAnalOptions, Str_sectOptDesc and Str_sec-tOptMaint tables of Strategy Input file

Now, In Confirm:

Maximum NSM Section Length: 3000

NSM Length as computed by system for NSM ID 'A' = 7050

In NSM Output File:

SECTIONS table

OtherColumns

IDLENGTHSECT_NAMESECT_ID

Existing valuesExisting Num-ber

3000Section AAExisting NSMSection

Same valuesas above

New auto num-ber (M)

3000Section A-1A-1NewNSMSec-tion

Same valuesas above

New auto num-ber (N)

1050Section A-1A-2NewNSMSec-tion

TRAFFIC table

Other ColumnsIDExisting valuesExisting NumberExisting Data

Same values as aboveNew auto number (M)New Data

Same values as aboveNew auto number (N)New Data

In Strategy Output File:

Str_SelSections table

115 of 123Confirm

| Network Manager |

Other ColumnsSECT_IDDESCSECTION_IDExisting valuesExisting NumberSection AAExisting Data

Same values asabove

New auto number(X)

Section A-1A-1New Data

Same values asabove

New auto number(Y)

Section A-1A-2New NSM Data

Str_secSecVehGrthSet table

Other ColumnsSEC_IDExisting valueExisting NumberExisting Data

Same values as aboveNew auto number (X)New Data

Same values as aboveNew auto number (Y)New Data

Str_sectAnalOptions, Str_sectOptDesc and Str_sectOptMaint tables

Other ColumnsSEC_IDExisting value post multiplyingalternatives

Existing NumberExisting Data

Same values as aboveNew auto number (X)New Data

Same values as aboveNew auto number (Y)New Data

Programme Analysis

On RUN of Programme Analysis Interface ,Programme road sections (PRS) are created:

• Copy of NSM Input file is created to Network output file location.• Generate PRS data internally based on settings in Homogenisation System Settings screen.• Computes nsm_id for each row of PRS data as per expression in HDM-4 System Settings -General tab.

• Creates PRS sections in Network output file by matching calculated nsm_id in PRS data to ex-isting NSM ID, which is stored in 'SECT_ID' column of 'SECTIONS' table.

• Number of PRS records created in Network Output file is same as no. of records matched.• Updates all columns set in HDM- 4 System Settings - Sections tab in the 'SECTIONS' table ofthe output Network mdb file for each PRS inserted.

• The PRS data generated in Confirm which does not find its nsm_id match in 'SECTIONS' table'SECT_ID' column is ignored and not inserted in Network Output file.

• At the end of operation, Network Output file contains only PRS data inserted from Confirm.• A warnings is logged if Confirm calculated where a match could not found between Confirm PRSdata’s nsm_id and NSM ID stored 'SECT_ID' column of 'SECTIONS' table in NSM Input file.

If 'programme' is checked, Programme database is created:

• STRATEGY table contents from Strategy input file are copied to PROGRAMME table of Pro-gramme output file.

• Post insert from STRATEGY table, contents of PROGRAMME table are updated fromProgrammeAnalysis Interface as described below:

Updated ValuePROGRAMME table columnFile name specified on 'Programme output filepath'

NAME

116 of 123Confirm

| Network Manager |

Updated ValuePROGRAMME table columnFile name of 'Network output file'NETWORK

Start Year specifiedSTART_YEAR

END_YEAR + Shift in original START_ YEAREND_YEAR

Count of rows in Prg_SelSections tableNUM_SECSEL

• Prg_SelSections table is updated (with as many rows are there are in Network output file) asbelow:

Updated ValuePrg_SelSections table columnSame as PROGRAM_ID in 'Programme' tableAnalysis_ID

starts from 0 and increase by 1 for every rowinserted

Sec_ID

Corresponding row's SECT_ID from 'Sections'table of Network output file

SECTION_ID

Corresponding row's SECT_NAME from 'Sec-tions' table of Network output file

DESC

• Based on expression value of Vehicle Growth Set, for each section inserted in SECTIONS table,Following are updated in Prg_secSecVehGrthSet table in Programme output file:

Inserted ValuePrg_secSecVehGrthSet table columnSame as PROGRAM_ID in 'Programme' tableAnalysis_ID

starts from 0 and increase by 1 for every rowinserted

Sec_ID

Vehicle Growth Set expression value. For eachSEC_ID, corresponds to SECT_ID from 'Sec-tions' table of Network output file

GRTHSET_NAME

• Existing Alternatives from Strategy Input file are Inserted in Programme Output file by mappingSECT_ID of Prg_Selsections file to the SECT_ID of Str_SelSections file using NSM_ID in homo-genous data internally generated in Confirm.

• Correction of existing alternatives' effective year as per start year and specified.

Updated ValuePrg_SectOptMaint table columnEFF_YEAR + Shift in original START_YEAR forall base alternatives

EFF_YEAR

EFF_YEAR + Shift in original START_YEAR +delay for all non-base alternatives

• Multiplication of existing maintenance alternatives to create new alternatives as per number ofbudget periods, budget period lengths (years), delay maintenance by (years) specified and usinglogic described in Maintenance Alternatives on page 118. Tables updated are:

Updated ValuePrg_sectAnalOptions table columnUpdated with total number of alternatives foreach SEC_ID in Str_sectOptDesc

NUMOPTIONS

Updated ValuePrg_sectOptDesc table columnUpdated for non-base alternatives' maintenancestandards by appending EEF_YEAR, if delay isspecified.

OPT_DESC

117 of 123Confirm

| Network Manager |

Updated ValuePrg_sectOptMaint table columnUpdated for non-base alternatives' maintenancestandards, if delay in specified

MAINTIT_ID

As perMaintenance Alternatives on page 118logic

New Rows Inserted

Maintenance Alternatives

This page describes the logic which corrects and multiplies maintenance alternatives for Strategyand Programmemdb file on RUN of Strategy Analysis Interface and Programme Analysis Interface.If a strategy analysis template was set in 2010 with one set of maintenance alternatives for oneroad section as:

• Base Alternative:

• 2010 – Routine Maintenance

• Alternative 1:

• 2010 – Reconstruct

• Alternative 2:

• 2010 – Resurface• 2015 – Reconstruct

And the parameters are set as:

ValueParameter2012Start year

3Number of Budget Periods

2Budget Period Length (Years)

4Delay Maintenance by (Years)

Then the following alternatives are available after correction and multiplying:

• Base Alternative:

• 2012 – Routine Maintenance (original year + base year difference)

• Alternative 1 from 2016:

• 2012 – Routine Maintenance• 2016 – Reconstruct (original year + base year difference + delay)

• Alternative 2 from 2016:

• 2012 – Routine Maintenance• 2016 – Resurface (original year + base year difference + delay)• 2021 – Reconstruct (original year + base year difference + delay)

• Alternative 1 from 2018:

• 2012 – Routine Maintenance• 2018 – Reconstruct (original year + base year difference + delay + 1xBudget Period Length)

• Alternative 2 from 2018:

118 of 123Confirm

| Network Manager |

• 2012 – Routine Maintenance• 2018 – Resurface (original year + base year difference + delay + 1xBudget Period Length)• 2023 – Reconstruct (original year + base year difference + delay + 1xBudget Period Length)

• Alternative 1 from 2020:

• 2012 – Routine Maintenance• 2020 – Reconstruct (original year + base year difference + delay + 2xBudget Period Length)

• Alternative 2 from 2020:

• 2012 – Routine Maintenance• 2020 – Resurface (original year + base year difference + delay + 2xBudget Period Length)• 2025 – Reconstruct (original year + base year difference + delay + 2xBudget Period Length)

If the “Delay Maintenance By” was set to zero then the first set of non-base alternativeswould not include the Routine Maintenance from the Base Alternative.

Note:

This logic is repeated for all road sections in Strategy mdb file (or workspace) on RUN of StrategyAnalysis Interface and programme mdb file (or workspace) on RUN of Programme Analysis Inter-face.

HDM-4 Database Mapping

HDM-4 .mdb databases schema accepts data in form of various data types. Expression builderprovided onHDM-4 system settings screen should be configured so as to result in matching datatype against HDM-4 field for which it is being mapped.Data type, field type or range mismatch in expression builder evaluated value will result in corres-ponding cell value for the HDM-4 column to be skipped and value as in Input .mdb file will be re-tained. Similar will happen for any expression evaluating to NULL or blank. The HomogenousData Report however, will still report the evaluated values.

Expected value fromConfirmexpression builder

HDM-4 : field type and rangeHDM-4 : Data type

Within 255 characters limitedby corresponding HDM-4column Field Size

0-255 charactersText

Integer: 0 to 255ByteNumber

Integer: -32767 to 32767IntegerNumber

Integer: -2147483648 to2147483647

Long IntegerNumber

-3.4028235E+38 through -1.401298E-45 for negative val-

SingleNumber

ues and from 1.401298E-45through 3.4028235E+38 forpositive values.True/False-1, 0Yes/No

HDM-4 Road Network Database Mapping

HDM-4 System Settings – Sections tab

119 of 123Confirm

| Network Manager |

HDM-4 System Settings – Sections tab provides an interface to map homogenised data outputfrom Confirm with HDM-4 fields as available in SECTIONS table of HDM-4 road network mdb file.Following is a mapping of HDM-4 field column names (with their data types) to HDM-4 UI labelsfor commonly used fields/columns

HDM-4 road networkworkspace UI: Label

HDM-4 road networkworkspace UI: Loca-tion (tab)

SECTIONS table: DataType

SECTIONS table:HDM-4 field

IDDefinitionTextSECT_IDName (or Description)DefinitionTextSECT_NAMELink IDDefinitionTextLINK_IDLink NameDefinitionTextLINK_NAMESpeed Flow TypeDefinitionTextSPEED_FLOWTraffic Flow PatternDefinitionTextTRAF_FLOWAccident ClassDefinitionTextACC_CLASSRoad ClassDefinitionTextROAD_CLASSCimate ZoneDefinitionTextCLIM_ZONESurface ClassDefinitionNumberSURF_CLASSLengthDefinitionNumberLENGTHCway WidthDefinitionNumberCWAY_WIDTHShoulder WidthDefinitionNumberSHLD_WIDTHRise + Fall (m/km)GeometryNumberRFNo. of rises + falls(no./km)

GeometryNumberNUM_RFS

Superelevation (%)GeometryNumberSUPERELEVAvg horiz curvature(deg/km)

GeometryNumberCURVATURE

adral (m/ sq. s)GeometryNumberSIGM_ADRALSpeed Limit (km/h)GeometryNumberSPEED_LIMSpeed limit Enforce-ment

GeometryNumberENFORCEMNT

Spped reductionFactors-XNMT

GeometryNumberXNMT

Spped reductionFactors-XMT

GeometryNumberXMT

Spped reductionFactors-Road side fric-tion

GeometryNumberXFRI

Most recent surfacingthickness(mm)

PavementNumberHSNEW

Previous/old surfacingthickness(mm)

PavementNumberHSOLD

Relative compactionOtherNumberREL_COMPCTStructural NumberPavement -> StrengthNumberSNSubgrade CBRPavement -> StrengthNumberCBR

120 of 123Confirm

| Network Manager |

HDM-4 road networkworkspace UI: Label

HDM-4 road networkworkspace UI: Loca-tion (tab)

SECTIONS table: DataType

SECTIONS table:HDM-4 field

Dry Season/ Wet Sea-son

Pavement -> StrengthYes/NoSNP_DRY

Condition at end ofyear

ConditionNumberCOND_YEAR

Roughness (IRI -m/km)

ConditionNumberROUGHNESS

All Structural Cracks(%)

ConditionNumberCRACKS_ACA

Wide Structural Cracks(%)

ConditionNumberCRACKS_ACW

Thermal Cracks (%)ConditionNumberCRACKS_ACTRavelled area (%)ConditionNumberRAVEL_AREANumber of Potholes(No./km)

ConditionNumberPHOLE_NUM

Edge break area (sq.m/km)

ConditionNumberEDGEBREAK

Mean rut depth (mm)ConditionNumberRUT_DEPTHRut depth standard de-viation (mm)

ConditionNumberRUTDEPTH_SD

Texture depth (mm)ConditionNumberTEXT_DEPTHSkid resistance(SCRIM 50km/h)

ConditionNumberSKIDRESIST

DrainageConditionNumberDRAIN_CONDLast construct or newconstruction

PavementNumberLAST_CONST

Last surfacing (reseal-ing)

PavementNumberLAST_SURF

Last preventive treat-ment

PavementNumberLAST_PRVNT

Last rehabilitationPavementNumberLAST_REHABArea of all structuralcracking(%)

Other ->Previous Sur-faceCondition (Butimin-ous only)

NumberPREV_ACA

Area of wide crack-ing(%)

Other ->Previous Sur-faceCondition (Butimin-ous only)

NumberPREV_ACW

Traverse thermalcracks(no/km)

Other ->Previous Sur-faceCondition (Butimin-ous only)

NumberPREV_NCT

Drainage-Drain typeOtherNumberDRAIN_TYPEAltitudeGeomatryNumberALTITUDESeparate NMT lanesOtherYes/NoNMT_SEPARNumber of SeparateNMT lanes

OtherNumberNMTLANES

121 of 123Confirm

| Network Manager |

HDM-4 road networkworkspace UI: Label

HDM-4 road networkworkspace UI: Loca-tion (tab)

SECTIONS table: DataType

SECTIONS table:HDM-4 field

ELANESOtherNumberELANESCalibration ItemDefinitionTextCALIB_ITEMReplacement costAsset ValuationNumberREPCOSTCondition/ProductBased

Asset valuation -> As-set Valuation methodfor Road Pavementlayers

Yes/NoCONDBASED

Initial roughnessAsset valuation -> As-set Valuation method

NumberINIROUGH

for Road Pavementlayers

Terminal roughnessAsset valuation -> As-set Valuation method

NumberTERROUGH

for Road Pavementlayers

Replacement cost(%)-Road formation andsub-grade

Asset valuationNumberRDFOSBGR_PRRECO

Replacement cost(%)-Road pavement layers

Asset valuationNumberRDPVLA_PRRECO

Replacement cost(%)-FW,FP,CW(NMT lanes)

Asset valuationNumberFTCYCLE_PRRECO

Replacement cost(%)-Bridges and structures

Asset valuationNumberBRDGSTR_PRRECO

Replacement cost(%)-Traffic facilities, signs

Asset valuationNumberTRFSGN_PRRECO

Residual value(%)-Road formation andsub-grade

Asset valuationNumberRDFOSBGR_RESVAL

Residual value(%)-Road pavement layers

Asset valuationNumberRDPVLA_RESVAL

Residual value(%)-FW,FP,CW(NMT lanes)

Asset valuationNumberFTCYCLE_RESVAL

Residual value(%)-Bridges and structures

Asset valuationNumberBRDGSTR_RESVAL

Residual value(%)-Traffic facilities, signs

Asset valuationNumberTRFSGN_RESVAL

Useful life(years)-Roadformation and sub-grade

Asset valuationNumberRDFOSBGR_USELFE

Useful life(years)-Roadpavement layers

Asset valuationNumberRDPVLA_USELFE

Useful life(years)-FW,FP,CW(NMT lanes)

Asset valuationNumberFTCYCLE_USELFE

Useful life(years)-Bridges and structures

Asset valuationNumberBRDGSTR_USELFE

122 of 123Confirm

| Network Manager |

HDM-4 road networkworkspace UI: Label

HDM-4 road networkworkspace UI: Loca-tion (tab)

SECTIONS table: DataType

SECTIONS table:HDM-4 field

Useful life(years)-Traffic facilities, signs

Asset valuationNumberTRFSGN_USELFE

Age in year 0-Roadformation and sub-grade

Asset valuationNumberRDFOSBGR_AGE

Age in year 0-Roadpavement layers

Asset valuationNumberRDPVLA_AGE

Age in year 0-FW,FP,CW(NMT lanes)

Asset valuationNumberFTCYCLE_AGE

Age in year 0-Bridgesand structures

Asset valuationNumberBRDGSTR_AGE

Age in year 0-Trafficfacilities, signs

Asset valuationNumberTRFSGN_AGE

Year asset componentage defined for(years)

Asset valuationNumberCOMPAGEYEAR

HDM-4 System Settings – Traffic tabHDM-4 System Settings – Traffic tab provides an interface to map homogenised data outputfrom Confirm with HDM-4 fields as available in TRAFFIC table of HDM-4 road network mdb file.Following is a mapping of HDM-4 field column names (with their data types) to HDM-4 UI labelsfor commonly used fields/columns

HDM-4 TRAFFIC table: datatype

HDM-4 TRAFFIC table:column name

Confirm Traffic tab: fieldname

Number : Long IntegerYEARSurvey YearNumber : IntegerVEH_IDVehicle_IDNumber : IntegerVEH_CATCategoryNumber : SingleAADTExpression

YEAR_IDX column in HDM-4 TRAFFIC table is always set to '0' by Confirm.SEC_ID column in HDM-4 TRAFFIC table corresponds to ID column of SECTIONS table andrepresents corresponding section for which TRAFFIC table is updated.HDM-4 System Settings – General tabIn HDM-4 strategy analysis, a road network in HDM-4 is generally decomposed into a character-istic multi-dimensional matrix called Network State matrix (NSM). NSM matrix is stored as roadnetwork workspace in HDM-4 and is used by Confirm for Strategy Analysis and ProgrammeAnalysis.

HDM-4 SECTIONS table: datatype

HDM-4 NSM Input file SEC-TIONS table: column name

Confirm General tab: fieldname

Text : 20 charsSECT_IDNSM ID

123 of 123Confirm

| Network Manager |