ofbiz-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre Smits (JIRA)" <j...@apache.org>
Subject [jira] [Comment Edited] (OFBIZ-9134) Add Party criteria to Routing Tasks
Date Sun, 04 Dec 2016 08:44:58 GMT

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

Pierre Smits edited comment on OFBIZ-9134 at 12/4/16 8:44 AM:
--------------------------------------------------------------

Hi Paul,

It is, for sure, part of a bigger scheduling solution. Which entail enhanced scheduling of
all kinds of available resources assigned to all kinds of work efforts. This indeed involves
knowing the pre-scheduling criteria, like skills and such of workers regarding production
runs. As such, the patch to make the (advised/required) skills visible on schema tasks - as
provided in the patch file(s) - is a first step. And should be enough given the title and
description of this issue.

The filtering/scheduling of workers does not take place on production schema and schema task.
But on production run and production run tasks. And, with current manufacturing management
solution in place, that is limited to pre-execution. Changes in resource allocation (due to
unforeseen circumstances) can't be effected while a production run is being executed. But
this is subject of another improvement issue.

Anyway, I have reviewed the patch provided. And my conclusion is that:
* would bring an enhancement to the component vis-a-vis features
* does introduce a low to moderate (non-technical) risk to the project

The risk is regarding adoption. I believe the issue and a patch is part of bigger feature
enhancement. To name an example: without the proper demo data, this is just another piece
where we let the (potential) adopter figure out how to use it. but that seems to be addresses.

I suggest to wait with committing this patch until the demo data has been provided.








was (Author: pfm.smits):
Hi Paul,

It is, for sure, part of a bigger scheduling solution. Which entail enhanced scheduling of
all kinds of available resources assigned to all kinds of work efforts. This indeed involves
knowing the pre-scheduling criteria, like skills and such of workers regarding production
runs. As such, the patch to make the (advised/required) skills visible on schema tasks - as
provided in the patch file(s) - is a first step. And should be enough given the title and
description of this issue.

The filtering/scheduling of workers does not take place on production schema and schema task.
But on production run and production run tasks. And, with current manufacturing management
solution in place, that is limited to pre-execution. Changes in resource allocation (due to
unforeseen circumstances) can't be effected while a production run is being executed. But
this is subject of another improvement issue.

Anyway, I have reviewed the patch provided. And my conclusion is that:
* would bring an enhancement to the component vis-a-vis features
* does introduce a low to moderate (non-technical) risk to the project

The risk is regarding adoption. I believe the issue and a patch is part of bigger feature
enhancement. To name an example: without the proper demo data, this is just another piece
where we let the (potential) adopter figure out how to use it. but that seems to be addresses.

I suggest waiting to wait with committing this patch until the demo data has been provided.







> Add Party criteria 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