IBM Sustainability Software - Ideas Portal
This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
I would think you could set this up as an escalation? Update the status to INPRG if the task status does not match the work order status if the ID of the task is greater than the workorder ID and the date of the task is greater than the reported date of the work order? Just thinking out loud, but seems like something that can be automated OOTB now w/o an ehancement request. Perhaps an automation script is possible also upon saving the work order as well?
Thank you for your submission but we also agree with the overall sentiment that the new task should not take on the parents INPROG status - as some of the other comments mention. Sounds like you already have a solution that will work for your organization. There are no plans to change this in the core product.
You all make fair points, but those are the reasons why I suggested that this functionality be optional -- possibly as a WO checkbox (it could be populated/crossed-over from a WO classification field). The field could be disabled by default and only enabled for low-risk types of WOs where it makes sense (i.e. an additional task to replace the signal light on a vehicle -- no approval required). Our divisions have unanimously requested this functionality. I've customized Maximo to behave this way, but it occurred to me that it would better as OOB functionality, so that's why I submitted it as an RFE.
If the new task is really already in progress, then maybe instead of entering a task the user should enter a new Quick Report and make the existing WO its Parent. Granted the new Quick Report will be a Child WO, not a Task, but it's almost what you're describing. And this approach is not a system-wide setting but controlled on a per-WO basis by the person creating the Quick Report.
Who would control if new tasks were automatically approved?
The approval process is there to ensure that work is thought through/safe etc.
There could be a legal risk to the organisation e.g.
Worker A is new to the organisation and isn't aware of specific safety related working practices.
Worker A adds a new task to an approved work order (and the task gets automatically approved) without taking into account the safety related working practices. An accident occurs and the employer is liable because that person was working on an approved work order
"Or worse, workers aren't aware of the WAPPR task and it gets missed." - this sounds like a candidate for a new RFE which includes an indicator to highlight if a WAPPR task has been added.
Whilst I do understand what your saying, I cannot support because when you are adding a new task, that task itself may not be already started. your assumption is that the new task is at the same lifecycle point as the parent and that is not true for the most part.