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

Julien NICOLAS commented on OFBIZ-5218:
---------------------------------------

Hello Pierre,

Our way of thinking is not to avoid the redundancy of the data but really to 
have efficient user interface.
For exemple, if your customer ask you to know the production status of his 
order.
You can go to manufacturing interface, found the production run linked to the 
order and get his status.
But why sellers have to go in manufacturing component just to have the 
production status of one order ?
If production run is waiting instead of ready as expected, sellers must know 
easily this kind of information.

I hope this explanation could help you to understand the goal of this kind of 
dashboard that is mixing data from several components.

Kind regards,

Julien.
                
> MRF Landing Page as Portal Page with some Portlet proposals
> -----------------------------------------------------------
>
>                 Key: OFBIZ-5218
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5218
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: manufacturing
>    Affects Versions: SVN trunk
>         Environment: any
>            Reporter: Carsten Schinzer
>            Priority: Minor
>             Fix For: SVN trunk
>
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> I would like to introduce a portal page when landing into the manufacturing 
> component after login. Just as we have already on e.g. ordermgr.
> Ideas for portlets to be displayed are currently:
> - stats on configuration data (how many routings/routing tasks/boms/... are 
> configured)
> - stats on runtime data (how many production runs by status ...)
> - top ten list of runs by status or duration
> More ideas are welcome, of course !
> My plan is to collect the requirements into a design document/sheet per 
> portlet that I would attach here before moving on to implementation. For 
> personal reasons I will not be able to start with the implementation design 
> before ca. end July 2013.
> Any other portlet ideas for MRP/MRF are appreciated until that deadline. Then 
> I would like to close the scoping and start writing designs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to