Notification and Order User Statuses - Examples

[3ngin33ring]

Hi All,

I haven’t been able to find very thorough information on how companies are using notification and order user statuses in their business processes. Also on how they decide if the status should be numbered or non numbered.

If possible please share some examples of how you’re using user statues in your business processes. The thought is that by sharing examples we can better visualize how these statuses could fit into our own business processes.

I’m especially interested in examples of how to differentiate whether a notification or order requires planning vs when a maintenance technician can just pick the work up and solve without planning and scheduling.

Our desire is to keep the system flexible so that notifications and orders can move between two queues “planning needed” and “ready to execute/open order” / no planning required

ex. Work order started and then left

ex. Work order needs planning vs doesn’t need planning

ex. Holds for materials, hold for planning, hold for scheduling

ex. Scheduled

[bob_pennington]

There are many ways to keep your maintenance work practices in alignment with your system processes user statuses being chief amongst them. User statuses are extremely useful as they are selectable parameters in the order and notification list edit reports. Now as far as the statuses themselves they are broken into two different types: numbered and unnumbered. We use the numbered status to keep the system process in alignment with the maintenance work practice. In our configuration we limit the ability to do certain business functions until after a predecessor step is completed such as a management review and subsequent approval. We use non-numbered user statuses as additional meta data on orders such as restricting business functions such as orders to labor only, held orders, etc... Another aspect of user statuses is that they can be restricted by authorization code so that the ability to put an order on hold is restricted to the plant's senior scheduler.

I would encourage you to spend some time searching the web as there are a couple of very good blogs describing how to influence objects (notifications/orders). This will help provoke thought.
Additionally, I would strongly suggest starting simple with the numbering schema representing major stage gates in your core maintenance work practice. You can configure additional non-numbered user statuses to help you identify orders that are on-hold, out-for-bid, etc... that makes for easier list edit reporting.

Good luck in your design,

Bob

[3ngin33ring]

Thanks Bob. I appreciate your detailed reply. I followed your recommendation to look at the blog posts about status influencing objects. We will definitely implement an approval process with authorizations for our orders. We have used this with equipment statuses for some time but never implemented for our work order processes.

Hold statuses are another thing we are working through. In our legacy system our orders can only be in one status at a time. (Similar to PMs numbered user statuses). There we include holds for materials, shutdown, approvals etc. Similar to Maximo.

If using non numbered User Statuses do you also include a numbered user status that indicates the order is on hold or not ready then look to the non numbered statuses as meta data to see the details?

I see using a status profile for planned work orders with numbered statuses like:

Outstanding

Approved

Hold (maybe we don’t need this on and can rely on Approved and a Hold Non Numbered Status?)

Scheduled

In Process

Completed

Non Numbered:

Hold - Materials

Hold - Shutdown

Hold - Scheduling

Hold - Engineering

Material Kit Completed

Etc