ofbiz-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pierre Smits (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OFBIZ-5569) Add production run task inspection capabilities using time entry improvements
Date Fri, 13 Feb 2015 14:47:11 GMT

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

Pierre Smits commented on OFBIZ-5569:


Inspection tasks can be added to production runs. How does that not deliver what you want
c.q. need?

Best regards,


> 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

This message was sent by Atlassian JIRA

View raw message