Hi Richard,
Firstly, the field is required i.e. mandatory, so yes that could be changed. Will that solve your issue? Yes with a, however.
However, the MBO class supplies the default value instead of a database default. Will that solve your issue? No, you would have to create either a Java class to override or an automation script to override, setting null for an on-add of a new work order. Would that solve your issue? I think you might stuff up something else potentially. I say that only because I haven't done that and I am thinking of what uses the ESTDURfield.
You're better off using an automation script or Workflow to validate that the ESTDUR field is >0 at whatever is the key step in the approval process that needs this information. It's not usually essential that an ESTDUR is defined (i.e. >0) when simply creating the work order, rather it's more important when the work order either gets into the hands of the Schedulers (essential for Graphical Scheduling) so they have an accurate outline of how much time and effort it will take to do the job. An example is that you define a window (ESTDUR) of 10 hours, this allows for all permits, gathering of tools, travel, work, clean-up and handover, whereas the effort is a total of 30 hours as you have assigned three (3) fitters for the duration of the work.
An automation script or Workflow can present a message to the user at the validation point if the ESTDUR field = 0. This is my preference, but I would also look into the overall process to see when and where is the value of ensuring the ESTDUR field > 0.
Please think about the validation as you may have emergency work orders where the work order raising is done after the fact or is raised at the point of the emergency so the maintenance technician can have a work order number to record their findings, etc... i.e. it is unplanned work that is "auto" approved and pushed into INPRG status, similar to what happens in Quick Reporting. Emergency work can't be planned, it just needs to get done, so in this can ESTDUR will not do you any good other than to see that there were 10 unplanned emergency work orders as an example.
Do you have a mobile solution? if yes, how does this (if any) fit in with field-raised work orders?
Do you have planners? Well, what are they doing about approving of work orders with zero duration?
What about approving work orders with no planned labour? This should also never happen with the exception of emergency work. Though with 'repeat' emergency work you can still have a job plan ready.
------------------------------
===============================
Craig Kokay,
Lead Senior Maximo/IoT Consultant
ISW
Sydney, NSW, Australia
Ph: 0411-682-040
=================================
#IBMChampion2022
------------------------------
Original Message:
Sent: Tue August 09, 2022 03:42 AM
From: Richard White
Subject: WORKORDER - ESTDUR default values
When creating a new workorder the WORKORDER.ESTDUR field has been set as required to force the user to ensure it is completed, however Maximo is setting a default of 0:00.
Is it possible to change this behaviour so the field is required but blank rather than 0:00.
------------------------------
Richard White
------------------------------
#AssetandFacilitiesManagement
#Maximo