I borrow this screenshot from MaximoSecrets (love your work there, Andrew!):
This flow seems to indicate quite a bit of operational maturity built into it. For example, to have WMATL immediately after WAPPR hints that
1) This is going to a Planner;
2) The Planner knows what parts will be needed, perhaps by way of a Job Plan that already exists;
3) (possibly) The Items needed exist in Maximo as Item/Tool records;
4) Those things have been inventoried; so that
5) The Planner can determine whether or not everything needed to complete the job is available.
Then, once the materials are available, the Planner would Approve it, and then it could be Scheduled. APPR comes before WSCH. I've always treated it the other way around, like, if you're going to schedule it, that needs to be done as part of the planning and preparation. APPR then acts as the handoff from the office to the field tech to go do it.
Does it have to be in the order presented in the diagram? Can that diagram be changed? Is there anything in MAS that forces you to follow this "flow" (hint: we don't have Planners or Schedulers here; Job Plans largely aren't developed; in many cases we wouldn't find out we don't have the parts until we get into the job and then come back to get the parts from the warehouse; etc.).
The way we're doing it is more like:
WAPPR -----------------------> APPR -----------> INPRG ------> WMATL if applicable ----|------> FCOMP (a custom status so we could "undo" COMP) -----> COMP
WSCH (if it's a PM) ------------^ ^-------------------------------------------|
Any reason to believe we can't do the same on MAS?
#Administration#EndUser#MaximoApplicationSuite#WorkManagement------------------------------
Travis Herron
Pensacola Christian College
------------------------------