Allow the Analysis Run to recalculate precedent Analyses before running itself.

I realize that Batch Run calculates all Analyses from top to bottom however if a COF references a Data Miner which referenced a preceding COF, the data will not necessarily be up to date. This means that the COF must be updated manually, the Data Miner must be updated manually, and the the subsequent COF must be updated. More importantly the dependency tree must be remember by the user or the data could be erroneous.

Same problem when running Data Miners that reference preceding Data Miners or reference Analyses in the Analysis tab.

Currently, when importing CCTV inspection data, InfoAsset Planner looks for the inspection based upon Upstream and Downstream assets. If it finds a match, it does not check if the pipe segment reference/facility ID match as well. It only checks the pipe segment reference if a match is not found via US/DS IDs.

Ideally, I would like the import tool to identify any case when the pipe segment reference does not match the GIS (in addition to identifying if the US/DS do not match). This would be beneficial because it helps ensure the quality of CCTV and GIS data. Survey and GIS data can have many inconsistencies and just because the US/DS are accurate does not mean the pipe segment reference is accurate.

For now, we are checking pipe segment references outside of InfoAsset Planner, which can be more time consuming.

Thanks!

I would like to be able to validate the existence of CCTV survey videos linked to CCTV Surveys.

I have found a CCTV survey that has an invalid "Media_Label". In this case I believe the .mpg file was renamed after the survey was submitted since the video name in the .xml file does not match the saved video. A way to select CCTV surveys referencing invalid CCTV video files would be very helpful.

This might be something that needs to be pre-processed on the InfoAsset Manager side of things but would be nice if InfoAsset Planner users could run the query themselves.

When importing sewer inspection data, if an asset (manhole / pipe) is not found, then a "dummy" asset is inserted automatically by InfoAsset Planner as a placeholder to be able to continue working without having to edit the GIS. PACP/MACP data as it has all of the necessary data to place these temporary assets. Having to get GIS just right (missing features, up/downstream manholes, etc.) to be able to import the inspection data can slow and if it fills in "dummy" assets based on the PACP/MACP data, you can quickly see where things are off between inspection data and GIS records.

The intersection tool within InfoMaster / Infoasset planner requires a specific buffer distance. It appears that it takes the worst case scenario within this buffer distance as opposed to the closed point to it. It would be nice to add a check box as to whether you'd like the data to be joined from the closest point within the buffer distance or the worst value within the buffer distance.
For example, if I have a point feature class with available fire flow deficiencies and try to perform a LOF by intersection and apply a buffer distance of 200ft, it looks like it takes the largest fire flow deficiency within 200ft and not the point closest to it.