What’s new in Bentley Exor INTRODUCTION 3 CORE CHANGES ...
Transcript of What’s new in Bentley Exor INTRODUCTION 3 CORE CHANGES ...
Contents
INTRODUCTION ....................................................................................................................................................... 3
CORE CHANGES ....................................................................................................................................................... 4
PROCESS MONITOR (ENHANCEMENT) .................................................................................................................................. 4
NAVIGATOR, ASSET HIERARCHY (NEW) ................................................................................................................................. 4
LOCATOR, LAYER CONTROL TOOL (ENHANCEMENT) ................................................................................................................ 5
ENQUIRY MANAGER ................................................................................................................................................ 6
PRODUCT OPTION ENQRECDATE (NEW) ............................................................................................................................ 6
4 CHARACTER XSPS (ENHANCEMENT) .................................................................................................................................. 6
ADMIN UNIT BASED RULE SET (ENHANCEMENT) .................................................................................................................... 6
ENQUIRY PRIORITIES – DOC0132 (ENHANCEMENT) ............................................................................................................... 6
STANDARD ACTIONS – DOC0155 (ENHANCEMENT) ............................................................................................................... 6
ENQUIRY REDIRECTION – DOC0157 (ENHANCEMENT) ........................................................................................................... 7
PUBLIC ENQUIRIES – DOC0150 (ENHANCEMENT) ................................................................................................................. 7
MAINTENANCE MANAGER ...................................................................................................................................... 8
4 CHARACTER XSPS (ENHANCEMENT) .................................................................................................................................. 8
CYCLIC MAINTENANCE (ENHANCEMENT) ............................................................................................................................... 8
ITEM CODE BREAKDOWNS - MAI1940 (ENHANCEMENT) ........................................................................................................ 8
ADMIN UNIT BASED RULE SET (ENHANCEMENT) .................................................................................................................... 9
DEFECT PRIORITIES – MAI3812 (ENHANCEMENT) ................................................................................................................. 9
ENQUIRY/DEFECT PRIORITIES – MAI1325 (ENHANCEMENT).................................................................................................. 10
MAINTAIN AUTOMATIC DEFECT PRIORITISATION – MAI3813 (ENHANCEMENT) ........................................................................ 10
LOCATOR CREATE DEFECTS – MAI3807 (ENHANCEMENT) ..................................................................................................... 10
INSPECTIONS – MAI3808 (ENHANCEMENT) ....................................................................................................................... 11
WORK ORDERS – MAI3800 (ENHANCEMENT) .................................................................................................................... 11
WORK ORDER AUTOMATION RULES – MAI3818 (ENHANCEMENT)......................................................................................... 11
CIM INTERFACE (ENHANCEMENT) ..................................................................................................................................... 11
INSPECTION LOADER (ENHANCEMENT)................................................................................................................................ 12
PEDIF FILE CREATION (ENHANCEMENT) ............................................................................................................................. 12
UKPMS .................................................................................................................................................................. 13
EXPORTING HMDIF FILES (NEW) ...................................................................................................................................... 13
TMA NOTICING AND PERMITTING ......................................................................................................................... 14
NOTE ........................................................................................................................................................................... 14
ATTACHMENTS ............................................................................................................................................................... 14
PRODUCT OPTION RECTRANSQ ...................................................................................................................................... 14
DELETION OF ‘NO LONGER REQUIRED’ INSPECTIONS.............................................................................................................. 14
CATEGORY D INSPECTIONS ............................................................................................................................................... 14
TPI QUARTERLY EXTRACT – TMA5540 .............................................................................................................................. 15
STREET GAZETTEER MANAGER .............................................................................................................................. 15
MAINTAIN NSG GAZETTEER – NSG0010 (ENHANCEMENT) ................................................................................................... 15
Introduction The major focus of the 4.5 to 4.7 release is on the following aspects of the system:
A technology change in that it has been adapted to be used on the Oracle forms 11
Release 2 with an update to the Java version on the middle tier
Consolidation of changes to TMA in support of the ETON 6 requirements (4.5.10 release)
Consolidation of changes to the UKPMS in support of the recent annual health check
Changes to Core, Maintenance Manager and Enquiry Manager to cater for
4 Character XSP’s
Admin Unit based rulesets
Introduction of Assets into the Navigator Hierarchy
A large number of outstanding bugs have been fixed.
Core Changes The majority of changes to the core modules are technical in nature and have no effect on the
user Interface. Details of the core changes are summarised in the Core release notes v4.7.0.0.
Additional changes that affect the user are as follows:
Process Monitor (Enhancement)
The process monitor has been enhanced to allow the user to restrict the processes that are to be
reviewed or maintained with the addition of some selection criteria fields at the top of the form as
shown in Figure 1.
Figure 1
Additional checkboxes have also been added to aid in the selection of processes that are to be
maintained in bulk as shown in Figure 1.
Navigator, Asset Hierarchy (New)
Navigator now also displays the asset data hierarchy and the assets history. The hierarchy will
display all relevant records including, but not restricted to, Enquiries, Documents, Defects,
Inspections, Work orders, Cyclic Schedules etc.
Navigator will also display any asset child items that form part of the asset hierarchy.
An example of an asset with its associated data hierarchy and one item of the asset history is
shown in Figure 2.
Figure 2
Locator, Layer Control Tool (Enhancement)
The layer control tool has been re-designed and enhanced to include a search field as
shown in Figure 3.
Figure 3
The search field allows the entry of all or part of the Layer Name in the Search dialogue with
wildcards as shown below
1. TMA%, entering TMA followed by the wildcard (%) will result in all layers starting with
‘TMA’ being displayed
2. %TMA%, entering TMA between wildcards (%) will result in all layers containing ‘TMA’
anywhere in the layer name being displayed.
Once the search criteria has been entered the [Submit] button is selected. To remove the search
restriction and display the full list of layers the [Reset] button is selected.
Enquiry Manager
Product Option ENQRECDATE (New)
Defines when the Enquiry Date Recorded is initially populated, either when the user first saves
the enquiry or when the user starts entering the enquiry details
4 Character XSPs (Enhancement)
The following Enquiry Manager module has been updated to work with 4 character XSPs.
Enquiries – DOC0150
Admin Unit Based Rule Set (Enhancement)
Enquiry Manager has been modified to allow Enquiry Priorities, Standard Actions and Enquiry
Redirection rules to be defined by Admin Unit, providing the flexibilty to define a separate set of
rules for each Admin Unit, if required.
The following enquiry manager modules have been updated to work with the enhanced Admin
Unit Based Rule Set functionality.
Enquiry Priorities – DOC0132
Standard Actions – DOC0155
Enquiry Redirection – DOC0157
Public Enquiries – DOC0150
Enquiry Priorities – DOC0132 (Enhancement)
This module has been modified to include the Admin Unit field (Figure 4) allowing for Intervals to
be defined by Admin Unit. The following rules apply, for any user accessing this form.
Only rules to which the User has been granted Admin Unit privileges will be accessible by
the User.
Any rules defined for an Admin Unit will override those defined at a higher level in the
Admin Unit hierarchy.
Figure 4
Standard Actions – DOC0155 (Enhancement)
This module has been modified to include the Admin Unit field (Figure 5) . When Enquiries are
created, the Admin Unit on the enquiry must match that defined for the Standard Action, along
with all of the other Enquiry criteria specified, for that Standard action to be applied.
Only Rules to which the User has been granted Admin Unit privileges will be accessible
by the User.
Validation will ensure that only the Users Admin Unit and Admin Units below , within the
Admin Unit hierarchy, will be available for selection
Figure 5
Enquiry Redirection – DOC0157 (Enhancement)
This module has been modified to include the Admin Unit field (Figure 6) allowing for redirection
rules to be applied to an enquiry where:
The Admin Unit matches that defined in the Redirection Rules
The Admin Unit is within the Admin Unit hierarchy of any defined rule where all other
criteria matches.
Figure 6
Public Enquiries – DOC0150 (Enhancement)
This module has been modified to accomodate the addition of the Admin Unit to Enquiry
Priorities and Defect Priorities (Maintenance Manager) ensuring that the validation will include
the Admin Unit of the enquiry when identifying the appropriate values.
In addition to the above changes the following modifications have also been made:
Responsibility of is restricted to the Users Admin Unit. Where product option
ENQRESPROL = 'CONT' (ie Responsibility of role is Contact, rather than User), the User
recording the enquiry will still be included in the list of valid values, to allow for the
recording of the enquiry
Admin Unit will be restricted to the Responsibility of Users Admin Unit hierarchy, to
ensure the Responsibility of user will have access to the enquiry, once recorded
Where product option ENQAURDID = 'Y' (ie. Admin Unit based on the Road), The list of
Users available in Responsibility of will be restricted to those users within the Admin Unit
hierarchy of the Road
Priority will take account of the Admin Unit recorded on the enquiry, ensuring that Enquiry
Priorities are correct for the currently selected Admin Unit.
When raising a Defect, the Defect Priority will be based on the Admin Unit of the enquiry,
the Enquiry Priority and the selected Activity
Change of Road, or Admin Unit, will not be permitted once a defect has been raised
against an enquiry
The Enquiry Target date is based on the Interval, defined in Enquiry Priorities form
(DOC0132) for the associated Enquiry Admin Unit. If the Admin Unit changes, the
enquiry Target date will be recalculated, and may change as a result
Maintenance Manager
4 Character XSPs (Enhancement)
The following Maintenance Manager forms and reports have been updated to work with 4
character XSPs.
Defects - MAI3806
Locator Create Defects - MAI3807
Inspections - MAI3808
Match Duplicate Defects - MAI2730
Batch Setting of Repair Dates - MAI2775
Work Orders (Defects) - MAI3800
Maintain Work Orders - Contractor Interface - MAI3802
Maintenance Inspection Summary/Error Correction - MAI4405
Print Inventory Summary - MAI2325
Cyclic Maintenance (Enhancement)
A number of changes have been made for cyclic maintenance when the "Schedule By Asset" flag
is set to 'Y' in Cyclic Maintenance Schedules form (MAI3860):
Correct the calculation of quantities.
Calculated Quantity is now automatically copied to the Actual Quantity.
Changed the Cyclic Works Order form (MAI3800A) to generate a Works Order Line for
each Asset regardless of the USECYCGRP product option.
Corrected the display of Asset information on Works Order Lines in the Cyclic Works
Order form (MAI3800A).
Schedules with the "By Asset" flag set to 'Y' can no longer be queried in the Cyclic
Maintenance By Road Section Form (MAI3862).
Item Code Breakdowns - MAI1940 (Enhancement)
This module has been modified to allow all users, who have been granted access, to define ICB
details for any Agency to which they have access. Product option ICBFGAC will influence the
details that can be defined as follows:
1. Setting the option to ‘N’ will ensure ICB details are unique at system level. This will prevent
the duplication of Item Code Breakdown details across all Agencies.
2. Setting the option to ‘Y’ will ensure ICB details are unique at agency level. This will allow for
Item Code Breakdown details to be defined for each Agency
Admin Unit Based Rule Set (Enhancement)
Maintenance Manager has been modified to allow Defect Priorities, to be defined by Admin Unit,
providing the flexibilty to define a separate set of rules for each Admin Unit, if required.
The following Maintenance Manager modules have been updated to work with the enhanced
Admin Unit Based Rule Set functionality.
Defect Priorities – MAI3812
Enquiry/Defect Priorities – MAI1325
Maintain Automatic Defect Prioritisation – MAI3813
Locator Create Defects – MAI3807
Inspections – MAI3808
Work Order Automation Rules – MAI3818
Inspection Loader
Defect Priorities – MAI3812 (Enhancement)
This module has been modified to include the Admin Unit field (Figure 7) allowing for Target
Response times to be defined by Admin Unit. The following rules will apply when using data that
has been entered into this module:
Only rules to which the User has been granted Admin Unit privileges will be accessible by
the User.
Any rules defined for an Admin Unit will override those defined at a higher level in the
Admin Unit hierarchy.
Figure 7
Enquiry/Defect Priorities – MAI1325 (Enhancement)
This module has been modified to include the Admin Unit field (Figure 8) associated with the
Defect Priority. The following rules will apply when using data that has been entered into this
module:
Only Rules to which the User has been granted Admin Unit privileges will be accessible
by the User.
Specification of Enquiry Priority, for the selected Defect Priority, will take account of the
selected Defect Priorities Admin Unit ensuring that Enquiry Priorities are correct for the
currently selected Admin Unit.
Figure 8
Maintain Automatic Defect Prioritisation – MAI3813 (Enhancement)
This module has been modified to include the Admin Unit field (Figure 9). The following rules will
apply when using data that has been entered into this module:
Only Rules to which the User has been granted Admin Unit privileges will be accessible
by the User.
Figure 9
Locator Create Defects – MAI3807 (Enhancement)
This module has been modified to accommodate the addition of the Admin Unit to Defect
Priorities as follows:
Valid priorities will be based on the list of Defect Priorities defined in Defect Priorities -
MAI3812 (Figure 7) for the Activity, and where the Admin Unit is within the Admin Unit
hierarchy of the associated network.
Allowed repair types, defined in Defect Priorities - MAI3812 (Figure 7), for a defect, are
based on the Activity and the Admin Unit of the associated Network.
The calculation of the Repair due date will take the Admin Unit of the associated Network
into account, when identifying the appropriate Defect Priorities values to be used in the
calculation.
If Automatic Defect Prioritisation is being used (defined by product option DEFAUTOPRI),
the Admin Unit of the Network assigned to the Defect, along with the Defect Activity, will
be used to identify appropriate details, defined in Maintain Automatic Defect Prioritisation
- MAI3813 (Figure 9).
Inspections – MAI3808 (Enhancement)
This module has been modified to accommodate the addition of the Admin Unit to Defect
Priorities as follows:
Determination of whether Repair Time specification is mandatory, will be based on the
associated Defects Priority entry, defined Defect Priorities - MAI3812 (Figure 7) for the
Activity, and where the Admin Unit is within the Admin Unit hierarchy of the associated
network.
Allowed repair types, defined in Defect Priorities - MAI3812 (Figure 7), for a defect, are
based on the Activity and the Admin Unit of the associated Network.
The calculation of the Repair due date will take the Admin Unit of the associated Network
into account, when identifying the appropriate Defect Priorities values to be used in the
calculation.
If Automatic Defect Prioritisation is being used (defined by product option DEFAUTOPRI),
the Admin Unit of the Network assigned to the Defect, along with the Defect Activity, will
be used to identify appropriate details, defined in Maintain Automatic Defect Prioritisation
- MAI3813 (Figure 9).
Work Orders – MAI3800 (Enhancement)
The calculation of the Work Order Target Date has been enhanced. New product Option
UPDWOTGT will influence the calculation of the Target Date as follows:
1. Setting the option to ‘Y’, the Work Order Target date in will not be automatically calculated,
based on the Work Order Line target dates and Work Order Priority, but will allow for manual
specification.
The Work Order Target date will only be populated if a Work Order Priority is entered.
Otherwise, the value will be NULL requiring population before Authorisation or Instruction.
2. The default value for the option is ‘N’, allowing the Target Date to be calculated based on the
Work Order Line target dates and Work Order Priority
Work Order Automation Rules – MAI3818 (Enhancement)
This module has been modified to accommodate the addition of the Admin Unit to Defect
Priorities as follows:
Allowed repair types, defined in Defect Priorities - MAI3812 (Figure 7), for a defect, are
based on the Activity and the Admin Unit of the associated Network.
CIM Interface (Enhancement)
CIM has been enhanced to allow for the processing of multiple Final Invoice files. Product option
CIMMULTIF will influence the details that can be defined as follows:
1. Setting the option to ‘Y’, final Invoices will be processed, even though a Final Invoice file has
subsequently been processed.
The Final invoices will be treated similar to the Interims. So a Final sequence number will
need to be specified in the Record Type 5 (currently null for Final invoices) so that the
Finals are processed in the correct order
For each Final invoice received the Work Order line completion date will be updated
according to the Date Completed on the record Type 10.
The Completion Date on a Work Order will be the latest completion date received on a
Final Invoice for a Work Order Line
2. Setting the option to ‘N’, processing will be performed as it is currently i.e. only a single Final
Invoice is permitted. This is the default value.
Inspection Loader (Enhancement)
This module has been modified to accommodate the addition of the Admin Unit to Defect
Priorities as follows:
Allowed repair types, defined in Defect Priorities - MAI3812 (Figure 7), for a defect, are
based on the Activity and the Admin Unit of the associated Network.
Validation of the Defect Priority will ensure that the value is valid for the Defect Activity
and the Admin Unit of the associated Network.
The calculation of the Repair due date will take the Admin Unit of the associated Network
into account, when identifying the appropriate Defect Priorities values to be used in the
calculation.
The Admin Unit of the associated Network will be used in the identification of the rules
defined in Work Order Automation Rules - MAI3818 to determine if Work Orders should
be automatically created for the details being processed.
PEDIF File Creation (Enhancement)
The creation of the PEDIF file has been enhanced to allow the Date Attributes to be defined.
Product option PEDDATEATR will determine the date attributes export format as follows:
1. Setting the option to ‘Y’, date Attributes are exported as a type ‘12’ record with ‘D’ as the
datatype and a length of 11.
2. Setting the option to ‘N’, date Attributes are exported as a type ‘12’ record with ‘S’ as the
datatype and a length of 7 as it is currently. This is the Default value.
UKPMS
Exporting HMDIF files (New)
A new module has been defined to allow HMDIF files of the following types of data to be
exported:
Network Data
Inventory Data
Survey data for CVI, DVI, SCANNER and FNS)
This will allow the export of the selected data and attributes based on the criteria entered as
shown in Figure 10 below.
Figure 10
TMA Noticing and Permitting
Note
There are no changes between the 4.5.10 and 4.7 releases of TMA Noticing and Permitting. The
information detailed below is a summary of the changes in the 4.5.10 release and is included in
this document for completeness.
Attachments
Within EToN 6, Attachments are now active on the majority of notices and as such the Attachment subsystem has been changed.
Within each sub area Works, Restrictions, Inspection, FPNs and Directions, attachments will be associated to that object and when sending a notice you will have the option to choose which attachments are sent.
Attachments within works can be associated to either Works, Sites or Inspections and depending on how and where the manage attachments screen is invoked from will determine what this association is.
Product Option RECTRANSQ
If there are a large number transactions to process, this product option, will, when set, will act like a drip-feed for the processing of the transactions.
If RECTRANSQ is null, then all applicable transactions will be processed in one go, if for example, you set RECTRANSQ to 100, then only the first 100 transactions will be processed in that iteration.
Deletion of ‘No Longer Required’ Inspections
Since the introduction of Category D Ad-Hoc Inspections, it has become apparent that there could be a large number of scheduled inspections that may never be resolved. We have therefore, introduced an option (if required) for unresolved inspections to be deleted.
A new ‘Deletion Rules’ tab has been added to Inspections Metadata - TMA5200 where the Deletion rules are specified.
An example is shown in Figure 11:
Figure 11
Category D Inspections
Additional functionality has been added for Category D inspections only
1. Product Option IAUTOSCHED This product option has a default value of ‘0’. The value entered added to today’s date to calculate the schedule date, i.e. if set to 1 then the process which runs on 30-Jul-2012 00:01:00 will have a schedule date of 31-Jul-2012, etc.
Note: This if only for Category D Ad-Hoc Inspections scheduled via the Process Framework.
2. Auto-schedule Category D Ad-Hoc Inspections This new functionality gives the Users the ability to automatically schedule TMA inspections for the Authority/Promoter combination they require and at a time they want.
3. Scheduling Category D Stop Inspections a) In Schedule Inspections - TMA5100, when scheduling Category D Stop Inspections, the
number of working days prior to the schedule date can be specified. If the number of working days is set to 0, it will schedule inspections for the scheduled date entered.
b) A new product option CATDSTOPOV has been introduced, which, when set to ‘Y’ any completed works/phases selected will have their inspection date set to the day after their actual end date, regardless whether it’s a working day or not. If however the actual end date is <= today’s date then the inspection date will be the current date +1. If CATDSTOPOV is set to ‘N’, then the inspection date will be the schedule date as per normal procedures. This is to cater for users who choose to schedule their inspections on a weekly basis and for a schedule date in the future.
TPI Quarterly Extract – TMA5540
This new module has been introduced to allow the user to generate the TPI Quarterly Extract.
This module will allow:
1. An Authority to generate an extract for their organisation for:
Individual Promoters
All Promoters
For a selected year / Quarter combination 2. An individual Promoter to generate an extract for their organisation for:
Individual Authorities
All Authorities
For a selected year / Quarter combination
An example is shown in Figure 12:
Figure 12
Street Gazetteer Manager
Maintain NSG Gazetteer – NSG0010 (Enhancement)
The NSG Gazetteer form has been modified to prevent duplicate sequence numbers from being entered when the designation code is the same. This prevents designations from being overwritten during the load when the sequence number is repeated for two different designation types.