ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Foxworthy (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-9134) Add required skills to Routing Tasks
Date Sun, 04 Dec 2016 00:04:58 GMT

    [ https://issues.apache.org/jira/browse/OFBIZ-9134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15718972#comment-15718972
] 

Paul Foxworthy commented on OFBIZ-9134:
---------------------------------------

Thanks Pierre,

No, I'm not sure. I think this area is one many OFBiz adopters will want to customise. What
I'm contemplating is a simple example implementation, and support in the data model so it
would be fairly easy to write a customised service to assign parties to a routing task.

You have implemented OFBiz in a manufacturing situation, so if you think there's no prospect
for a simple implementation, I'd be happy to accept your advice.

What really got me going on this was OFBIZ-5852. It is absolutely better than nothing, but
won't scale. Associating a fixed party with a task means when that party is unavailable, there
can be no automatic assignment at all. In contrast, if the assignment is skills based, when
a party goes on leave or ceases to work for the organisation, the service can assign or suggest
another party with appropriate skills.

In the default implementation in OFBiz, I would be happy if the skills associated with the
task are used to filter a list of parties, so only parties with the appropriate skills are
offered to the production manager. If there are no skills, allow the production manager to
browse all parties. Where skills have been set up, perhaps offer a list of parties filtered
by skills first, with the ability to browse all parties if that's what the production manager
wants to do.

You say a production manager would only be able to assign parties that he or she can direct,
members of a team over which the manager has some authority. So maybe the filter would not
just be on skills. If we attach a party filter to a task to narrow down parties that might
possibly perform it, we should think about criteria. Membership of a PartyGroup (a team or
department) would be one, skills would be another. Are there any more we can think of?

Cheers

Paul

> Add required skills to Routing Tasks
> ------------------------------------
>
>                 Key: OFBIZ-9134
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-9134
>             Project: OFBiz
>          Issue Type: New Feature
>          Components: manufacturing
>    Affects Versions: Trunk
>            Reporter: Paul Foxworthy
>            Assignee: Deepak Dixit
>            Priority: Minor
>         Attachments: OFBIZ-9134.patch, OFBIZ-9134.patch
>
>
> OFBIZ-5852 enables you to add a Party to a Routing Task (the WorkEffortPartyAssignment
entity), to specify a person who is preferred to perform the task.
> If the person is on leave or unavailable, the production manager would have to manually
specify a different person.
> It would be better to specify skill or skills required for the Routing Task. Then on
each production run, any Party with the right skills could be scheduled to perform the task.
> There are already entities WorkEffortSkillStandard, PartySkill and SkillType  which could
be used to enable this.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message