INX Preserve

Make the box where you have to manually add the number of containers collected per sample run pre-set with the option to edit if required. This value is usually dependent on the analysis conducted and a majority of the time remains consistent. Making pre-set will be in line with InViron and assist in saving time required to manually enter details per sample run.

The lab import file requires a site to be included that lines up with the name of the overall site or an error is received from the automatic import yet there is no section on the COC for denoting site. This is causing errors with the lab not entering the correct site. Please add a section above project name on the COC as Site.

Sometimes data for a CoC is received in more than one import. Allow a CoC to be selected for more than one lab report.

When Standing Water Level (bToC) is entered in Preserve but SWL (RL) or SWL (GL) are not in the list of Field parameters in the related Monitoring Program, then the system doesn't auto-calculate the SWL (GL) and SWL (RL) values. If a user post-sampling event or data import then links SWL (GL) / SWL (RL) to the Monitoring Program - it still doesn't go back and auto-create these values based on the Casing Height and reference level (e.g. mAHD). Can some function please be added that allows us to trigger the software to retrospectively calculate the SWL (RL) and SWL (GL) values where the necessary calculated metadata exists to enable this. It should not overwrite any existing values (especially as casing height may have changed over time).

When we click into the auto lab import section to see a successful or failed import the files do not always show up as clickable links. You have to sometimes close out the whole program and get back to try and trigger then to show up as a clickable link.

In the future develop the ability to create runs and COCs in Preserve, but back track to add field data later? I know we can ‘skip’ adding field data for samples now, but we first have to either untick each parameter or add a comment next to each one. For a few samples that’s ok, but if we have 3 pages of samples that’s very time consuming. Just wanted to check since we used to do this in INVIRON sometimes. Given creating the COC is often urgent for us (we may only have hours to do it), we don’t always have time to add all of the field data at the same time.

When you view the unpublished lab results it doesn't display the monitoring run or type information or the sample date and time makes it difficult to mark off as complete.

Table format that is exported from Insights data table not report friendly. You can play around with a pdf but not adaptable for a report.

Workflow from monitoring run>COC>Lab results can be improved. It's difficult to track a monitoring run through to its field results as there is no linkage and no use of common language eg. site and monitoring type not visible. Different system generated numbers are used and cause confusion. Process within InViron worked for tracking results from field to lab and closing the run out.

It has been brought to our attention that certain Labs are submitting results with a combination of "~" and "<" or ">" as a numeric field e.g. "~>". This is causing the results to be rejected as valid numeric values and therefore not getting auto-imported. Can a solution for this please be investigated as it is causing unnecessary manual reworking of lab results by clients?