[
https://issues.apache.org/jira/browse/OFBIZ-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14504972#comment-14504972
]
Pierre Smits commented on OFBIZ-6085:
-------------------------------------
Christian,
It seems you're pulling more and more together into this, so that many issues
are addressed: inspection, quality measurements, WIP, time registrations, etc...
For review and acceptance purposes the distributed/separated approach is
easier, swallowing the elephant in one piece is way harder than piece by piece.
Apart from the above, please indulge me for a moment to explain my viewpoint on
the whole of manufacturing mgt with OFBiz (issues - and comments thereon -
registered by others, you and me) in relation to the various entities in other
applications/components and the DRMBs (1 and 2).
Executing a production run (manufacturing) is in essence a simple set of
processes, triggered by others (e.g. order and/or requirements registration -
and their related entities), governed/directed by again others (defining
schemas,tasks and BoMs) effecting yet another set of other processes and
entities (time registrations, inventory items).
This simplicity is fairly well implemented in OFBiz, while at the same time
allowing for some of the required complexities individual companies might have.
As we can surmise, we are not there yet regarding the OSFA (One Size Fits All).
But with your help we are getting to something that can be applied to your
specific needs as well, that's for sure.
Now, on to the details (given the above, and reiterating a bit more - my
apologies for that):
# the WorkEffort entity is for the registration of the activity (schema, schema
task, production and production run task). It relates to the resource (person,
production equipment et all) and the facility.
# the InventoryItem entity is for the registration of the goods (raw material,
intermediate, end product, waste, rejects, etc) going in and coming out of the
the activity. And it relates to the activity, the facility and worker (the
latter somehow).
# the TimeEntry is for registration of time spent on the activity. And it
relates to the resource (person or other production resource).
What you are trying to achieve is extending existing entity elements (I must
confess: in my assertion) in order to have more insights in the whole down to
the nitty-gritty details. This, is for sure, the domain of data
warehousing/data analysis/reporting.
But how you want to achieve the latter should not be done by extending the
former in that way (and that much).
To give as example(s):
* you're proposing to change the TimeEntry entity by including elements for
quantity produced and quantity rejected. That is not needed as quantity
produced (and rejected) can be registered through the entities in the product
component.
* you're proposing to change the InventoryItemDetail entity to include the Id
of the TimeEntry record to have a relation with the elements stated above and
the time spent. That is also not needed as there is a relation to TimeEntry
records via the association of the WorkEffort record.
Now, the aspects to bring it all together (more/better) for data
warehousing/analysis and reporting (according to DRMB vol 2, page 70 and
following) is the Star Schema for Manufacturing feeding into ofbizolap (the
targeted db) as opposed to ofbiz (for transactions) and pre-eminently the
'ProductionRunFact' entity.
Another aspect (more high level) to consider is this: if we were to apply the
associated patch as is, how much more would it complicate/confuse other
operators/users of OFBiz manufacturing? Way more, I surmise.
Can it be configured to work in that other way for that other kind of user? At
the moment (given current feature/requirement set) it can't. And with the
implementation of the associated patch it can't either...
On the whole a degradation in the adoption potential of OFBiz in general, and
of OFBiz Manufacturing in particular. (I fear).
Best regards,
Pierre
> Add support for production run inventory tracking
> -------------------------------------------------
>
> Key: OFBIZ-6085
> URL: https://issues.apache.org/jira/browse/OFBIZ-6085
> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing
> Affects Versions: Trunk
> Reporter: Christian Carlow
> Assignee: Pierre Smits
> Attachments: OFBIZ-6085.patch
>
>
> Production run inventory tracking seems worthy of support so that production
> managers can get an idea of the department work load. InventoryItemDetails
> should be created during production run declarations so that the material
> that was stocked out for the production run can be tracked while it is being
> manufacturing into the good. Essentially is would be like stock moves or
> inventory xfers occuring within the production runs for the task fixed asset
> facilities/locations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
