Users are running an Insurance Claims Report to identify defects on an individual section highlighted by safety inspectors over a 12 month period. The summary of inspections is being generated but no defects are showing on some sections. We are able to identify defects that were identified during the period but they do not show on the insurance report.
Looks like when you populate the section in the form it populates the end chainage for the report to be the section length (411) . The defects aren't appearing as their chainage is greater than this length and there is a test to see that they lie within, as they don't ( they lie outside the length) they wont get selected.
So I created a report CT-TEST (on production ) results enclosed that allowed me to put in a larger end chainage value, I tried 450 but that failed ( I haven't checked why yet ) but guess there is a tolerance - need to check....so for now I put in 415 and that was accepted. I ran the report and the defects appeared as they were within this chainage value.
I would change my procedures from now if want to include defect data that has a chainage greater > section length on a section the report needs to be run on. Would query back the section details first and check the max chain value first and use this, value in the report end chainage parameter ie override default section length value when greater . Or setup a discoverer report that can detail that people can reference as a check. The max chainage value can usually be found on the network elements form, Query back the section , select the attributes tab, look for Max Chain attribute by scrolling down or querying.
If creating a report for the first time the report defaults to the correct length( if overwrite with a different one ) so run the report or save the first time. Then re-query the report name back and change the length and this new length should be accepted the second time of running.
Without analysing more deeply in order to prevent occurring:-
Check why the max chainage value stored for the section is greater than the section length ( is it historical or due to condition data from ukpms ? etc )
Does the max chainage or section length need altering ?
Can a defect be loaded > section length or max_chain ( where value greater ) ? Might want to check this product option too as it can allow defect chainages to be loaded > values of the section length.
DEFRECALUPUpper Tolerance For Survey Len.This option defines the tolerance (as a % of section length) within which an inspections survey length may be greater thanthe section length. This is applied to all survey types.
These are business questions appropriate to your site.