Request: Time Entry Blocks (15 minute selection intervals) on date fields definable in settings,
This adds at minimum 2 clicks per line, but more often 6-8 towards end of hour
This is a critical improvement need for tool usability.
This is a known issue for GE, Bayer and Horiba
Idea 1347 is similar request.
Absolutely, highly desired for increased efficiency.
This will be on the roadmap to be addressed in next 1-2 release on MFL.
The irony here is that this used to be in 15 minutes increments but we had customers stating that they needed more precision hence the app was updated to have 1 minute increments. When we make this enhancement, we will enable to increment to be configurable between 1 minute and 15 minutes.
Hi Joseph - can you confirm that when you say MFL you're also referring to online SFM? Thanks. Chris Wada
Hello Ramesh! You could use a custom field on the WD which has fractions of an hour which represent 15 minute increments. Then map the start date time from the WO and calculate the end date/time field using the 15 minute increment value. The only action the engineer would need to do is enter that 15 minute increment- the rest would populate automatically.
Thank you for the reply Michael- very much appreciated. Have you done something similar in your org? We've gone through the thought exercise and some testing but cannot arrive at a place where a similar approach works to save entry time. Here are some further details from our evaluation:
1) Start Date/Time Default Mapped from WO: We default Start Date/Time = TODAY() because the Scheduled WO date is never when the work is actually done or entered, so mapping in from Work Order is not effective for us. So the Technician always has to enter Start Date, Hour and Minute (seeing 00-59)
2) Custom field on Work Detail for Time Spent: Many of our jobs are multiple hours per Work Detail line. We have considered setting up a picklist of .25, .5, .75, 1, 1.25, 1.5, etc. etc. This quickly becomes more cumbersome than entering the End Date/Time directly. In the end for entering time we're in need of simpler selection list by configuration as Start Date/Time will always require entry.
3) End Date/Time Logic based on Start Date/Time: Idea 1411 is a related solution that is related to what we're talking about. We've requested a form-fill type function that can be set off entered field so that real-time fill given. Not sure if this is possible but being looked into
4) Formula Behavior: To my knowledge, formula fill only happens on save which is too late for proper time entry, otherwise we'd just default End Date/Time to equal Start Date/Time. Suppose an "evaluate formulas" button that doesn't initiate a save would be helpful here so our follow-on logic isn't applied to WIP.
In any case, it seems you have a great deal of expertise in this area, so if we're missing something please feel free to let us know as you're able. Thanks again for taking the time to provide input!
We will coordinate to make this consistent across online and mobile apps.
Mapping Work Start Date/Time from header to Work Detail line makes sense because the Engineer is going to stamp the Date/Time when arriving onsite which is the beginning of the labor hours. Then the engineer would just have to select the picklist of hours. One way to get around such a lengthy list of values is to choose values which are typical but not necessarily comprehensive: 0.25,0.50,0.75,1,1.5,2.2.5,3.3.5,9,10,11,12. That insight can come directly from the Engineers or from reviewing the data on prior work orders 'Line QTY' field- they may never have used 11.75 hours as a pick-list value.
To populate the End Date/Time, you could use a combination of mapping the Start Date/Time from the header plus a workflow rule to populate the End Date/Time using the hours pick-list value selected. You might run into issues if the engineer is working offline as the workflow would not execute until online, but since you already have the pick-list value showing how many hours were spent on that line (value could be copied to Line QTY using SFM formula), do you really need the End Date/Time populated while offline? Or is it really used downstream for reporting. That would depend on how you actually use the data from the Start and End Date/Times as to whether you needed that calculated even when offline.
I like that ServiceMax is thinking about bringing back the 15 minute increments. That would help. Coupled with a form-fill capability and a default increment of time, this would get much simpler for the Engineers to Debrief.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.