Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ALIM | Exor
  • Product Communities
  • AssetWise
  • ALIM | Exor
  • Cancel
ALIM | Exor
ALIM | Exor - Wiki Populate grid references on Road Studs defects
    • Sign In
    • -Exor - Wiki
      • +ALIM Document Manager
      • An Attempt to Reset Your Password Has Failed
      • +AWLRS
      • +Exor Asset Manager
      • +Exor CIM / FIM
      • +Exor Document Manager
      • +Exor Enquiry Manager
      • +Exor Information Manager
      • +Exor Information Manager TMA Reporting Pack
      • -Exor Maintenance Manager
        • Adding a BOQ causes FRM-40200:Field is protected against update
        • Adding new standard item causes HIG-0169 Database constraint violated CNI_INDEX_P1
        • +Budgets - Exor Maintenance Manager
        • Can't Instruct Defects
        • Cannot amend instructed work orders
        • Changing v2 Asset Type Attributes on MAI1400
        • Complete defect manually when interfaces on
        • Could not create map in locator
        • Create new budgets after financial year start
        • +Cyclic Maintenance - Exor Maintenance Manager
        • Defect details changed after load
        • Defect priority list
        • +Defects - Exor Maintenance Manager
        • Duplicate defects created
        • +E5 Payment Run - Exor Maintenance Manager
        • Erroneous defect repair dates
        • Error during Inspection Loader Part 2
        • Error instructing Work Orders M_MGR-0267
        • Error message ‘REP-271468672: A temporary file cannot be created’ is appearing.
        • Error messages HIG-0530 and HIG-0556 on inspection loading
        • Exor MAI M_MGR-0234 in cyclic work orders
        • Forced to add road group when adding standard item to contract
        • HIG-0067 when query cyclic work orders
        • -Hosting/Accessibility - Exor Maintenance Manager
          • Create an Inspection and defect manually or retrospective inspection.
          • Defect not going onto works order
          • Defects not automatically going onto work orders when loaded
          • Populate grid references on Road Studs defects
          • Warning: No Automatic Work Order Rules defined for Repair target date DD-MON-YYYY
        • How to find MAP Viewer log files
        • How to restart MapViewer Service
        • Illegal Activity Area Code in inspection by group form
        • In Map, zooming in takes a lot of time
        • Inspection Date less on loading RDI files
        • Inspection Loader 'could not read file content'
        • Inspection upload failure (from MCP to Exor MAI)
        • +Inspections - Exor Maintenance Manager
        • +Interface - Exor Maintenance Manager
        • Invalid path when running interfaces
        • Loader creates doc assoc record but doesnt move files post load
        • +Loaders - Inspection - Exor Maintenance Manager
        • +Loaders - Inventory - Exor Maintenance Manager
        • +Locator - Exor Maintenance Manager
        • Method to clear older defect at zero cost
        • Missing Financial Code EXORR feeder
        • Missing LOCATION keyword when single quote in filename
        • M_MGR-0090 date raised must be <= todays date
        • Notify field on defects form
        • On loading Work Order Invoice (WI) file an error ‘ORA-06502’ appears
        • On scroll BOQ items error “FRM-41050:You cannot update this record” appears
        • ORA 00001 IC PK violation when processing WC file
        • ORA-01400: cannot insert NULL into ("HIGHWAYS"."BOQ_ITEMS"."BOQ_EST_DIM1")
        • ORA-06502: PL/SQL: numeric or value error: character string buffer too small
        • Prevent budget being selected mid way through financial year
        • +Reference - Inspections - Exor Maintenance Manager
        • Unable to run reports
        • Unknown Module MAI3620
        • +Work Orders - Exor Maintenance Manager
      • +Exor Maintenance Mobile
      • +Exor MapCapture
      • +Exor MapCapture (ESRI)
      • +Exor MCI MapCapture Interface
      • +Exor Network Event Manager
      • +Exor Network Manager
      • +Exor Oracle
      • Exor Problems and Solutions
      • +EXOR product placeholder
      • Exor Public Enquiry Manager API
      • +Exor Schemes Manager
      • +Exor Spatial Manager
      • +Exor Street Gazetteer Manager
      • Exor Streetworks Manager
      • Exor Streetworks Mobile
      • +Exor Structures Manager
      • Exor Structures Mobile
      • +Exor TMA Noticing Manager
      • +Exor TMA Permitting Manager
      • +Exor UKPMS
      • Remove @ from the AWLRS Local Password Policy
      • +Transportation Intelligence Gateway
      • Unable to connect to Power BI dataset
      • +Video Series for Exor
      • Working From Home with Exor
    • +AssetWise ALIM for Transportation
    • How To Import SSL Certificate 11g Weblogic

     
     Questions about this article, topic, or product? Click here. 

    Populate grid references on Road Studs defects

    Product(s): Exor Maintenance Manager
    Version(s): 04.07.00.01
    Environment: N\A
    Area: Hosting/Accessibility
    Subarea: N\A

    Problem Description

    When our inspectors have completed their driven surveys to check the reflectivity of the road studs on our network they input their results into the system manually. They do this by creating an inspection in form MAI3808 for each section that they have covered.


    From this they populate the associated ‘Defects on Inspection’ form and then the ‘Repairs for Defect‘ form which when populated correctly sets up an Auto Works Order as we’d expect.
    So far so good. Defect created, WO created as per automation rules.

    Now, as these defects get remedied on site we of course want to close these out. Because of the nature of how we put these right we would like to complete these ‘in bulk’ and get several WO’s and defects completed at once.


    Our ideal choice would be to complete Defects WO Lines in MapCapture.
    So we have attempted to do this but, we are finding that none of the WO’s that have been created for these defects will display in MCP. Neither will any of the Defects Asset ID’s.

    We were perplexed so set about trying to work out why. We created several defects and WO’s  to try different scenarios and we think we have found the problem.

    In the Defects on Inspection form there are tabs for the Coordinates. These are not auto populated even though the maintenance section and chainage of the defect will have been populated within the required forms. Because this information is missing we think this is the reason that they don’t download to MCP because they have no spatial representation that MCP can use to plot either the WO or the Defect.

    We created a defect in the form and populated the Coordinates manually. We then tried to download this defect to MCP and it was successful and plotted correctly.

    Problem.
    We have 2211 Road studs defects that have been created this way. We can’t download these into MCP for quick and easy bulk completion of the WO’s.
    Further to this, when we complete this type of work again (at the start of next winter) as the forms stand we will have the same issue again.

    Firstly, can we get the defects and WO’s already raised updated with coordinates required so they can be represented in MCP?

    Secondly, can the Defects on Inspection form be updated to automatically capture the required coordinates so this issue doesn’t happen again?

    Steps to Resolve

    In order to generate missing grid references on existing data contact support to run a script to do. Generate from section and chainage.

    Options 1 and 3 look favourable below in order to prevent occuring again, .


    1. create the defect in locator, this then populates grid references ( although not sure if one defect / inspection)
    2. Can get a map of the section up in locator and have mai3808 up at the same time ( split screen if you will ) , when creating the defect at the grid ref point on mai3808, just move mouse on locator to see grid references in the bottom screen ) , so copy grid ref you see with pointer in Locator, has to be roughly right doesn't matter which layer you are viewing as long as you can see a road.
    3. Could use send xy in locator to populate locator with grid ref of point selected, this is selectable from the screen and can cut and paste the co-ords into mai380 grif references  , trim to 3dp as doesn't like more or copy to 3dp this enables the defect co-ords to be populated too without writing anything down. I think this works well and is my preferred solution.

    Also, with multiple defects on a section after creating a defect with a grid reference  you could insert a new defect and duplicate the previous record ( which if it had grid references would then be auto populated with the same value) and amend chainage if appropriate  to cut down data entry.
    4. Run the script to work out grid ref for future RS data to populate on a scheduled job.

     

    • Map Capture
    • Locator
    • inspections
    • Exor
    • Defects
    • Road Studs
    • 04.07.00.01
    • Maintenance Manager
    • Share
    • History
    • More
    • Cancel
    • Clive T Created by Bentley Colleague Clive T
    • When: Tue, Apr 17 2018 5:45 AM
    • Revisions: 1
    • Comments: 0
    Recommended
    Related
    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies