Ratjoy.com » Forums » Suggestions, Technical Support and Feedback » Show the limiting factor to production
You need to register or login to post a reply.
Show the limiting factor to production
|
John Galt RJ: John Galt CO: John Galt Post Rating: 0 + / - Total Posts: 23 Karma: 97 Joined: Apr 6, 2012 |
Posted on May 12, 2012 Right now, if you go into a factory, choose a product, and set the number of units to the maximum, you can see what material is the one limiting you. That's great. However, there are two problems with this:First, if time is your limiting factor, you're not going to have an easy way of knowing which of the materials is the one currently limiting your production capability. Second, getting to this information, even when time isn't the limiting factor, requires extra clicking. Could there be an indicator when you are setting up a production run that highlights or in some way marks the material that you will run out of first (presuming that you were to produce forever, even beyond the bounds of what you'd normally be allowed to set as a time to produce)? This would make keeping track of what materials you need to make more of so much easier. |
|
Josh Millard RJ: Tex Corman CO: J. Quaff Arabica Post Rating: 0 + / - Total Posts: 167 Karma: 231 Joined: Apr 3, 2012 |
Posted on May 12, 2012 You know what would be a neat way to do that? Just a scaled bar graph for each of the components involved. Whatever component you have the most of (or at least a week's worth of, so possibly multiple components would be maxed) would be a bar a full unit in height; everything else would be a shorter bar proportional to how much supply you have of that compared to the top items.So if you had enough stock for an entire week run, it'd be a flat row of maxed out bars; if you had an empty queue and so a week's worth of time available, but only two days worth of wheat and one day worth of electricity, you'd have a wheat bar 2/7ths high and an electricity bar 1/7ths high. Etc. The bottleneck would be obviously as the lowest bar, and you could tell if there was a (currently effectively hidden) bottleneck in some other component that was also lowish compared to the others. |
You need to register or login to post a reply.