eB workorder design advice or best practices

I am still new to workorder design and would greatly appreciate some best practice advice.

I have created a fairly basic and linear workorder with the below tasks.

Task

T001 - GENERAL   INFORMATION

T002A - EXECUTIVE   OFFICES DIVISION REVIEW

T002B - LEGAL   DIVISION REVIEW

T002C - HUMAN   RESOURCES DIVISION REVIEW

T002D - INFORMATION   TECHNOLOGY DIVISION REVIEW

T002E - FINANCE   DIVISION REVIEW

T002F - ENGINEERING   DIVISION REVIEW

T002G -   OPERATIONS:COLLECTION SYSTEMS REVIEW

T002H -   OPERATIONS:DRAINAGE & FLOOD PROTECTION REVIEW

T002I -   OPERATIONS:SUPPORT SERVICES REVIEW

T002J -   OPERATIONS:TREATMENT FACILITIES REVIEW

T003 - BUDGET REVIEW

T004 - SUPPLIER   DIVERSITY REVIEW

T005 - LEGAL REVIEW

T006 - EXECUTIVE   OFFICES REVIEW

T007 - PURCHASING   REVIEW

 

The biggest branch is going from the 1st task to the 2nd task, which has 10 options, one for each department, and 9 of them are excluded as soon as you pick one. After the 2nd task it all mergers back together and takes a linear path again.

                        

When you look at all of the tasks under the workorder all of the excluded tasks show up. The users find this distracting and confusing.

I have been told that there is not away to not get these to show up. If this is correct I am thinking maybe it would be better to create 10 templates of the workflow, one for each department.

I have also thought about breaking it up into 2 workflows,

  1. Creatition Workflow
  2. Approval Workflow

I am not sure how this would work out because; the user uses a document template to create a PMDF document which adds the original complete workorder to the document because there is an approval task at the end of the workflow. If I broke this one workflow down into the two workflows nested. Could the document still add both workflow and be approved by the final task?

 


So as I see it I have 3 choices please let me know if there are others.

1.  Leave it as one workflow and some how eliminate the excludeded tasks from the display in the workorder.

2.  Create 10 templates that make a workflow that is linear and specific for a department and limiting its use to that department.  This would require extra security roles

3.Create two nested workflows one that takes care of the creation of the document and department review and the second company wide review workflow that would appprove the document that started the process.

Thanks for your help.

 

  • Hi Alex,

    User who creates the work order is able to check his tasks. User can check which path is selected to complete the workflow that's why it is shown under Work Order.
    All three choices will give you the same result as when a user who creates a WO can view the included and excluded task.

    But the person who accept the Task is not able to view the excluded one. He can only view the possible paths he can have but not able to view the already excluded tasks.

    Though I will consult this with my team but I think 1st Choice is the best way to work on, as for rest of the choices, you have to created different workflows but that too with the same exclude-include issue.

    Regards,
    Manav B.



  • We are using eB web 15.5.1 and mainly using reports that take the user to the document that created the work order and than going to the workorder from the document.  The user does not specifically create the workorder.  They create a document that has an approval task that creates the work order.  I am not sure if any of the above matters just trying to be clear in our setup.

    I am not sure if I have not configured something properly but it has been our experience that all users see all the tasks of a workorder when they go to the work order.  They can even go to a specific task even if they are not part of the skill level for that task.  They just cant do anything once they are in the task.

    Thanks for your help.

  • Hi Alex, I think your missing the part where you delegate the Task to specific user.  Then that user has to accept the task and then it will be in their IN box to be worked.  Hope that helps.

    -Derek



  • I am not sure if it makes a difference but we are using skill areas.  The people still go in and accept the task and complete it.  I know that the person will only see their task in their work exchange area but what I am talking about is the listing of tasks on the workorder object and how it lists all the tasks, excluded or not.  Thanks for your help.

    Alex

  • Yes, it would list as same for the user who creates the task.

    If a user creates a task then it will be listed under the task topic, it doesn't matter if it is excluded-included or you choose skill area or assign it directly to the person.

    It is designed for user to check and to modify the list if needed.

    Excluded and included are just the description for a task to notify a user whether it is used or not.

    Regards,
    Manav B.



    Answer Verified By: Alex Talbott