[
https://issues.apache.org/jira/browse/OFBIZ-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14324487#comment-14324487
]
Christian Carlow edited comment on OFBIZ-5569 at 2/17/15 5:20 PM:
------------------------------------------------------------------
Hey Pierre,
I need the ability to support the following data for a production run to create
100 goods:
1. Worker1 finished a manufacturing task on 10 pieces 1/1/15 and moved it to
the next inspection task location
1.1 Inspector1 rejected 2 of Worker1 on 1/2/15 because of scratches and moved
to next rework task or scrap location
1.2 Inspector2 rejected 1 of Worker1 on 1/3/15 because of cracks and moved to
next rework task or scrap location
1.3 Inspector3 accepted 7 of Worker1 on 1/4/15 and moved to next task location
2. Worker2 finished the next manufacturing task on 7 pieces (goods from
Inspector3 for Worker1) 1/5/15 and moved it to the next inspection task location
2.1 Inspector4 rejected 2 of Worker2 on 1/6/15 because of scratches and moved
to next rework task or scrap location
2.2 Inspector5 rejected 1 of Worker2 on 1/7/15 because of cracks and moved to
next rework task or scrap location
2.3 Inspector5 accepted 4 of Worker2 on 1/8/15 and moved to next task location
Is this supported?
was (Author: ofbizzer):
Hey Pierre,
I need the ability to support the following data for a production run to create
100 goods:
1. Worker1 finished a manufacturing task on 10 pieces 1/1/15 and moved it to
the next inspection task location
1.1 Inspector1 rejected 2 of Worker1 on 1/2/15 because of scratches and moved
to next rework task or scrap location
1.2 Inspector2 rejected 1 of Worker1 on 1/3/15 because of cracks and moved to
next rework task or scrap location
1.3 Inspector3 accepted 7 of Worker1 on 1/4/15 and moved to next task location
2. Worker2 finished the next manufacturing task on 7 pieces (goods from
Inspector3 for Worker1) 1/5/15 and moved it to the next inspection task location
2.1 Inspector4 rejected 2 of Worker1 on 1/6/15 because of scratches and moved
to next rework task or scrap location
2.2 Inspector5 rejected 1 of Worker1 on 1/7/15 because of cracks and moved to
next rework task or scrap location
2.3 Inspector5 accepted 4 of Worker1 on 1/8/15 and moved to next task location
Is this supported?
> Add production run task inspection capabilities using time entry improvements
> -----------------------------------------------------------------------------
>
> Key: OFBIZ-5569
> URL: https://issues.apache.org/jira/browse/OFBIZ-5569
> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing
> Affects Versions: Trunk
> Reporter: Christian Carlow
> Assignee: Pierre Smits
>
> There doesn't seem to be a standard method for handling production run
> inspections that offer any real power in terms of reporting. The system
> already lacks time entry functionality which will be added in OFBIZ-5532.
> Once time entry functionality is added to the declaration services,
> TimeEntryAssoc could be created to link an inspection time entries to a
> manufacturing work time entries to represent an inspection of manufacturing
> work. The goal is to be able to determine the number of bad pieces produced
> per manufacturing worker and who was the inspector. The functionality should
> also be flexible and powerful enough to distinguish who is actually at fault
> for the bad piece. In most cases, the manufacturing workers will be at
> fault, but there could be times where an inspector might accidentally drop a
> good or potentially good piece and the system should be able to flag them as
> the party actually responsible for the defect.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
