PM Scheduling: Single Activity vs Multiple Activity PM Definitions

Hi.  I have set up many PM schedules using multiple activities.  For example, on one PM definition, I have an activity set for 750 engine hours, a different activity for 2000 engine hours, one for 4000 engine hours, and one for 8000 engine hours.  After setting these up (and after asking a question here at the Oracle Community), I found out that these don't work exactly the way I had expected -- at least not for a meter-based PM schedule where the next service date is determined using the previous completion date.

There is only one Interval Count for the entire PM schedule, and only the most recently completed PM work order determines the Current Interval Count.  For example, if the 750-hour work orders are often completed early, that will advance the Current Interval Count for the entire schedule, which causes the 2000-hour work orders to be generated sooner than expected.  If the expectation is that the next 2000-hour activity is based solely on the completion of the previous 2000-hour activity, you will end up surprised when your 2000-hour work orders are generated too soon.  This is the situation we are currently