[
https://issues.apache.org/jira/browse/OFBIZ-5985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15210223#comment-15210223
]
Swapnil Shah edited comment on OFBIZ-5985 at 3/24/16 1:36 PM:
--------------------------------------------------------------
In order to enable MRP to make more informed decisions and suggest more
intelligent capacity/resource plan, i think we can try to maintain the proper
mapping and distinction between primary and alternate resources at DB level.
Although i am not too sure what level of support we have got as per current
data model.
If not, Possibly we can have a separate entity (something like
WorkEffortFixedAssetStdAlt) to manage the association between primary and set
of available alternate resources(fixed assets) with its capacity defined for
each operation(WorkEffort/routing task). Also, We can try to define the
priority for each alternate resources (under WorkEffortFixedAssetStdAlt) that
could be honored by MRP during planning run.
MRP engine logic could be enhanced to first fully utilize the primary
resource's capacity and once its fully exhausted then can start consuming
alternate resources as per their priority order.
Whereas on production run screen at the time of execution, same model can make
the valid suggestions for alternate available resources that a
production/operations manager can switch over.
Tagging [~jacopoc]
was (Author: swash78):
In order to enable MRP to make more informed decisions and suggest more
intelligent capacity/resource plan, i think we can try to maintain the proper
mapping and distinction between primary and alternate resources at DB level.
Although i am not too sure what level of support we have got as per current
data model).
If not, Possibly we can have a separate entity (something like
WorkEffortFixedAssetStdAlt) to manage the association between primary and set
of available alternate resources(fixed assets) with its capacity defined for
each operation(WorkEffort/routing task). Also, We can try to define the
priority for each alternate resources (under WorkEffortFixedAssetStdAlt) that
could be honored by MRP during planning run.
MRP engine logic could be enhanced to first fully utilize the primary
resource's capacity and once its fully exhausted then can start consuming
alternate resources as per their priority order.
Whereas on production run screen at the time of execution, same model can make
the valid suggestions for alternate available resources that a
production/operations manager can switch over.
Tagging [~jacopoc]
> Support routing task standard quantity tracking of fixed assets
> ---------------------------------------------------------------
>
> Key: OFBIZ-5985
> URL: https://issues.apache.org/jira/browse/OFBIZ-5985
> Project: OFBiz
> Issue Type: Improvement
> Components: workeffort
> Affects Versions: Trunk
> Reporter: Christian Carlow
>
> I need the ability to assign track the standard quantity that can be run by
> fixed assets for a routing task. WorkEffortFixedAssetStd contains a
> fixedAssetTypeId instead of fixedAssetId I've found no code using the entity
> other than the one that allows the entity data to be manipulated. Therefore,
> to prevent adding another entity to the model, would replacing
> fixedAssetTypeId with fixedAssetId be a worthy solution?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
