So JeffM if you would still like to help me, i would highly appreciate that!
We are here to help you do the work. The wikipedia article on inventory models cites a number of textbooks on this topic in English. You might see whether any of them are available to you through a university library.
It would help us help you if we knew more about your education. How good is your probability theory, your differential calculus, your microeconomics, your computer programming skills? It is hard to give advice in a void.
I suggest that you read READ BEFORE POSTING before posting again. I further suggest, because you will be doing the work, that you start a new thread for each problem as it comes up. People tend not to look at threads with multiple postings because they assume that one of the posts has already given the answer.
OK Now to answer the questions you have already asked.
First, it is good that you have a number of ideas. It may be that the problem will require a number of solutions to deal with different aspects of the problem.
Second, you may want to break down spare parts into categories, such as by unit cost, by frequency of need, and by time from order to delivery. In other words, how best to handle a part that is needed daily, takes a week to get delivery, and has a low unit cost may differ from how best to handle a part that is needed two or three times a year, has a three month delivery period, and has a very high unit cost. That categorization is merely an example and may not apply to your situation. The point is that a solution that is appropriate for some parts may not be appropriate for others. That is something for you to think about.
Third, ultimately, a solution will have to apply to individual parts. A bolt is not money. At some point, you need to figure out how many bolts to keep in inventory on average, order point, and order quantity, and you must do so part by part. That is where the computer comes in. You might start by going to see how your company does that now. At the very least, you may learn some practical constraints that a solution will have to address.
Fourth, your aggregated model that you asked about initially may be too conceptual for application, but that aggregated model is certainly good for presentations to discuss the purpose of your solution. Explaining your solution well enough that it is adopted is every bit as important as developing the solution because, if it is not adopted, your development is in vain. Moreover, your aggregated model may have practical use in setting budget guidelines.
Fifth, total cost is NOT necessarily minimized where holding cost equals downtime cost. As I explained before, let
v = monetary value of average level of inventory
h(v) = holding cost per period as a function of v
d(v) = cost of downtime per period as a function of v
t(v) = total cost as a function of v = h(v) + d(v).
Conceptually this is fine. It likely is true in practice that h(v) = a * v, where a > 0. The practical problem is that it may be difficult or even impossible to specify d(v) numerically, particularly because it assumes that the monetary value is allocated to various parts optimally, and that optimum has yet to be found.
However, it is certainly true that d'(v) < 0 and it is almost certainly true that d''(v) > 0 for all non-negative v. Consequently, the optimum value of v is v such that d'(v) = - a.
Sixth, you may want to do a little research on Monte Carlo methods if you are not familiar with them. It may give you something new to think about.