[
https://issues.apache.org/jira/browse/OFBIZ-5569?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325894#comment-14325894 ]
Christian Carlow commented on OFBIZ-5569:
-----------------------------------------
Hey Pierre,
I don't disagree with your concern about injecting rejected pieces back into the production run but would like to ignore for now to focus on the primary problem which is to support worker productivity tracking in production runs. Though any number of workers can be associated to a task with WorkEffortPartyAssignment, there is still no way to determine the quantity produced by a workers at specific times of completion because declarations just update workEffort.quantityProduced which is the sum of all worker quantities.
Ignoring the injection of rejected pieces back in the production run, can the data in my last post be determined?
> 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)
Locked
