PI Manual Logger Web should honor the Conditional Manual Data Entry (CMDE) settings in the tour definitions
CMDE provides a cleaner method of skipping tags, as it does not rely on the user to manually skip data entry for the correct tags during each tour.
Agreed! Without CMDE working using mobile devices in the field and PIML Web, it is wasting a lot of time to search for values that we don't require based on certain conditions. There is no way for an operator to know from a handheld device which items they do not need to record. The idea would be if they choose the "navigate to remaining items only" option it factors in any items that can be skipped.
I agree that not having this functionality in PIML Web is a huge issue for our operators and operator rounds system as a whole. We are migrating from an old and obsolete operator rounds system to PIML, and even that system made it so easy to do conditional rules, so it is very disappointing that PIML Web doesn't have that functionality.
This feature for PIML Web would be very beneficial
CDME is essential for us, along with clock scheduling. Not having these is causing us major issues, as the operators will struggle with what routes to do when, and what points to skip if a machine is offline for example.
In addition to David's comments, CMDE is an essential part of adopting a true Condition Based Maintenance strategy. For example, if we want to record a manual temperature reading every 500 operating hours or trigger which parts of a lubrication tour need to be completed based on either operating hours or temperature. Lack of this capability is a significant barrier to adoption in our business.
I wonder if this is supposed to be in the minor release announced for 9/30/17.
Conditional Entry Conditions (CDME), is integral to our work flow. We employ SKIPS in our tours to avoid prompting for data that does not need to be collected in certain circumstances. For example if one train or assembly line is off line, many data points do not need to be taken. The skips that worked on the PI Mobile do not work on PI Web. See page 127 of PI Manual Logger 2014 R3 Administrator Guide, the fact that this basic functionality was not included in the Pi Web system is a gross oversight and has literally derailed our migration to a tablet based operational tool that had plans for Pi Vision. Since we are running Windows 10 pro on our tablets and have extra Mobile device licenses we are attempting to run an embedded windows OS emulator to reduce the burden of paging through data that need not be recorded. If that doesn't work we will have to create "mini-tours" for our operators by production line/train. This has been disruptive to our operation. David Martorana, Operations Program Manager Tenaska Inc. REFERENCE: OSIsoft TechSupport Case # 782443