|
|

楼主 |
发表于 2011/3/31 09:50:38
|
显示全部楼层
red1最新测试结果更新。
http://sourceforge.net/projects/adempiere/forums/forum/639403/topic/4437035
2011-03-30 23:25:28 UTC
I have some good news and bad news depending on who you are. If you are a commercial person (you are in the wrong place as this a community project but no issue, just get in touch with the right community contributor and you be safe when thinking of applying this into your production / commercial environment), it is bad news because Libero Manufacturing is not backward compatible with a pure core ADempiere instance (meaning overiding of core code happens that for one breaks it even with its own Libero Cost Engine. It also redo old BOM structures instead of extending it cleanly).
It is good news as a FOSS project where all information should be made open for you to improve broken things better rather than hide behind sales talk. The information is also given below with testable code that I have committed into SVN. By the way, noticed that hardly anyone else commit real useful code here nowadays. I hope the admins of this project recognise my unbroken track record of commitment and restore my admin rights which gives me assurance that this project is still a bazaar that honours contributors as the name ADempiere is originally meant to be. At the moment i do not feel it is but still (as in Compiere project before) i always speak out critically, as a peer, and committing often. Ok, enough of my ranting and now to the good news.
I have really good news for community members. This Libero Manufacturing is a vast improvement in functionality from old Compiere's BOM Production which is too one step simplistic. It has a true shop floor assembly line where my testing for a single product has been fruitful and evident. I have written up a full set of Fitnesse Test here http://red1.org/adempiere/viewtopic.php?f=28&t=1204.
I have made earlier documentation in the same forum if you like to refer to background notes on how Libero really works. However i focus on the MakeToOrder option as it is a more compact summary of it all. It gives full cycle from requisition of a BOM product to governing the workflow activity associated. The WF of course interface with info such as BOM formula, assembly reosurces schedule and Cost Collection.
I am most interested in the time scheduling as this is what i considered to be core in a Master Production Schedule, but i cannot make sense of the Backward Forward Schedule Type which even though does go thru their own separate ways in formulating, does not give discerning meaningful results i.e. they give the same times or does not follow what i read up about such function. But i noted and gave the code concerned in the the issue tracker for Libero in this project space. However after a number of days since then till now, there has been no response from anyone associated with Libero.
While going thru the code, i noted that the engine is well advised in terms of functionality meaning there is a subject matter expert behind it. However there has been comments raised elsewhere on the lack of more up to date Mfg such as the incorporation of the 'Theory of Constraints'. But after some cursory reading of http://en.wikipedia.org/wiki/Theory_of_Constraints i am of the layman opinion that Libero Mfg feature wise has what it takes to be improved in that direction. By improved i mean added on minimally as Liber already has many elements if not almost all for deriving the constraining elements such as time to market, availability of machinery, forward/backward options in the time managing framework. There are already settings to exploit resources such as units grouping at each production cycle and scrap units.
In essense production is production or the conversion of raw materials to finished goods thru a process of activity in sequence. For that, Libero seems to have it. Please try out the code i committed under FitnesseMfg and FitnesseStory and improve or extend it to cover the daunting full set of Libero Mfg.
A sidenote here in case someone is to ask, "what it takes to make Libero compatible with OSGI the future?" Answer:
1. Check the overiding core classes to refactor them out into separate classes that are called either via Callout or ModelValidators, or
2. Modify the core classes to plugin such extension without breaking the other calls to the core.
Who can do that? None other than Heng Sin and Carlos Ruiz. I am just the journalist writing all this action. So do not shoot me. Just send in your mail in to the news editor.
Cheers from freezing 13 degrees celcius dawn here in Korat highlands, east of Thailand, with web access given by the GPRS phone of my room-mate Thammatat, manager of Korat Software Park. The code was committed and forum posted via this slow way from last nite but i gave up when the line got stuck and just now i noticed it cranks back up again.
|
|