Franchisor Ideas

18 VOTE

Drytrack - Removed / Demo option

***Drytrack - need a "removed for demo" button under MPs

  • Stephen VanVladricken
  • Mar 10 2017
  • Under Consideration
Idea Type Enhancement
Urgency High
  • Attach files
  • Travis Roaten commented
    June 6, 2017 15:44
  • Travis Roaten commented
    June 6, 2017 18:35

    So if you Remove a Moisture Point for demo, that point never removes itself from the DryTrack report and then doesn't allow the Drying Completed date to be filled in.

    This happens if when you begin the first day of drying, you might have carpet on the floor. After the second day, you decide that it will be better to remove the carpet and dry the surface underneath. You have already entered the carpet into DryTrack as a Moisture Point. You need to then "Remove" that carpet reading, and begin a new reading on the floor beneath the carpet. Even though you have told the DryTrack that this point no longer needs to be dried, the DryTrack Report is not notified of this change.

     

    There can be multiple reasons for demoing a surface or structure, and there should be a way to reflect that in the DryTrack Report


    In the screenshots below, the Moisture Point was removed on visit 5, but since it didn't reach it's Dry Goal before removal, the DryTrack Report has yet to fill in the Drying Completed date.

     

    https://dash-ngs.net/NextGear/Enterprise/Module/GppChart/DryTrackReport.aspx?JI=SrWDHyTKdBA=&JN=xO/DP/1L7Xn/mCY1Uru4B3ZecMtkUDz7

  • Travis Roaten commented
    June 6, 2017 18:47

    The DryTrack Report should have some sort of notifier like these screenshots that allows it to know to fill in the Drying Completed date.

  • Travis Roaten commented
    June 6, 2017 19:12

    There is one possible negative side that needs to be looked into. This section of the DryTrack Report uses an average of all MP's of the same material and meter used.

     

    in the below screenshot("Removed MP warning.PNG"), I have added in another MP on visit 4 with a reading of 52. On the DryTrack Report, it shows the average of 51 for visits 4 and 5 since the original reading is 50, and the new is 52.

     

    we should also start breaking this section up individually by point, instead of averaging all the points. This could be an issue because as is denoted in the other screenshots listed here, one point could be dry, and the other not dry, but the DryTrack Report will average them together and code it as dry.