Community: Inventory and MRP mailing list archives
I have observed that some requirements are rather basic and other requirements are rather specific.
I think strategically, it is useful to think about core-readiness (!) and plugability of any module.
So I would suggest, that requirements are clustered into incremental categories of specificity and/or production types. Out of that several interconnected modules could be crafted.
I think in order to structure well the underlying infromation (requirements), we should apply both dimensions (specificity and production type)
An intial suggestion for specificity (KISS-style):
A, B, C
An initial suggestion for production types:
Can someone proably contribute based on well established theory a better well spread clustering. Or will this do the job?
Do you have objections to / concerns about this suggestion?