Method and apparatus for optimizing management of spare components for network infrastructure

Information

  • Patent Application
  • 20050071317
  • Publication Number
    20050071317
  • Date Filed
    September 26, 2003
    21 years ago
  • Date Published
    March 31, 2005
    19 years ago
Abstract
Method and apparatus for optimizing spare component management for a network having a plurality of nodes is described. In one example, availability parameters associated with an inventory of spare components are obtained. A plurality of management configurations are determined in response to the availability parameters. Each management configuration includes at least one warehouse node selected from the plurality of nodes in the network and a quantity of spare components in the inventory that are to be stored at the at least one warehouse node.
Description
BACKGROUND OF THE INVENTION

1. Field of the Invention


The present invention generally relates to information systems and, more particularly, to optimizing management of spare components for network infrastructure, which includes determining number of spares and the correct geographical area to minimize impact of availability to the network.


2. Description of the Related Art


Presently, spare components for elements of network infrastructure are maintained at each location or node of the network. For example, spare components for communication equipment may be stored at each office, service location, warehouse, and central office, of a communications network. In addition, the number of spare components to be stored at a given location for a given network element is based on a recommendation of the equipment vendor. While some algorithms have been developed to determine the number of required spare components in accordance with the reliability of the equipment, such solutions typically address only the number of spares that should be stored at a location given the quantities of the network elements in service. Such “sparing solutions” do not account for repair times, distance traveled, minimum downtimes, capital expenditures, or customer satisfaction.


SUMMARY OF THE INVENTION

These and other deficiencies of the prior art are addressed by the present invention of a method, apparatus, and computer readable medium for optimizing spare component management for a network having a plurality of nodes. In one embodiment of the invention, availability parameters associated with an inventory of spare components are also obtained. A plurality of management configurations are determined in response to the availability parameters. Each management configuration includes at least one warehouse node selected from the plurality of nodes in the network and a quantity of spare components in the inventory that are to be stored at the at least one warehouse node.




BRIEF DESCRIPTION OF THE DRAWINGS

So that the manner in which the above recited features of the present invention are attained and can be understood in detail, a more particular description of the invention, briefly summarized above, may be had by reference to the embodiments thereof which are illustrated in the appended drawings.


It is to be noted, however, that the appended drawings illustrate only typical embodiments of this invention and are therefore not to be considered limiting of its scope, for the invention may admit to other equally effective embodiments.



FIG. 1 is a block diagram depicting an exemplary embodiment of a network;



FIG. 2 is a data flow diagram depicting an exemplary embodiment of a process for optimizing spare component management for a network;



FIG. 3 is a flow diagram depicting an exemplary embodiment of a warehouse and location optimization process; and



FIG. 4 is a block diagram depicting an exemplary embodiment of a computer suitable for implementing processes and methods described herein.




DETAILED DESCRIPTION

The inventors have determined that as the communications industry becomes more competitive and capital becomes more constrained, it becomes imperative to optimize the reliability of the network by maintaining an accurate sparing solution. As such, a method and apparatus for optimizing spare component management for a network having a plurality of nodes is described. One or more aspects of the invention are related to optimizing spare component management within a telecommunications network. Those skilled in the art will appreciate, however, that the present invention may be employed to optimize spare component management in other types of networks having nodes dispersed within a particular region and elements requiring spare components.



FIG. 1 is a block diagram depicting an exemplary embodiment of a network 100. The network 100 comprises a plurality of nodes 102, illustratively, nodes 1021, through 1026. Each of the nodes 102 is disposed at a different location within a region 101. In this exemplary embodiment, nodes 1021 through 1024 each comprise an in-service network portion 104 having in-service network components (“network components”). Nodes 1023, 1025, and 1026 each comprise a warehouse portion 106 for storing spare network components (“spare components”). In this embodiment, the node 1023 includes both an in-service network portion 104 and a warehouse portion 106. In general, the network 100 may comprise any number nodes that have an in-service network portion, a warehouse portion, or both. For example, in a telecommunications network, several of the nodes may be central offices (COs) having telephone switching equipment and others of the nodes may be warehouses for storing spare components. In addition, some of the COs may be capable of storing spare components.


The nodes 102 are logistically connected to one another via pathways 108. For example, spare components residing at the node 1023 may be moved to the node 1021 using the pathways 108. In this exemplary embodiment, not all of the nodes 102 are directly connected to one another via one of the pathways 108. As such, the distance between pairs of the nodes 102, and hence the time it takes to travel between pairs of the nodes 102, depends on the configuration of the pathways 108. In general, a given one of the nodes 102 may be logistically connected to one or more others of the nodes 102 via one or more of the pathways 108.


As used herein, the term “warehouse node” refers to any node of the network 100 having a warehouse portion (i.e., capable of storing spare components). The number of warehouse nodes in the network 100 is referred to herein as the “warehouse configuration”. For example, a given network may employ a distributed warehouse configuration in which each of the warehouse nodes in the network stores spare components. In another example, a given network may employ a centralized warehouse configuration in which one or more, but not all, of the warehouse nodes store spare components. In general, a warehouse configuration includes at least one warehouse node. In this exemplary embodiment, a centralized warehouse configuration is employed, where three of the nodes 102 are warehouse nodes.


Specifically, in this exemplary embodiment, nodes 1023, 1025, and 1026 are warehouse nodes. Nodes 1023, 1025, and 1026 each store a particular quantity of spare components for the network 100, where the total quantity of spare components comprises the inventory. The term “quantity”, as used herein, is meant to encompass any number of spare components including zero spare components. For purposes of clarity by example, the present example refers to “spare components” without regard to class, category, or type. In reality, however, a typical network may be defined by a multiplicity of different types of network components requiring spares, thus yielding a multiplicity of different types of spare components. As such, a warehouse node may store different quantities of spare components depending on the spare component types. Although the present example refers to a quantity of spare components without regard to different types of spare components, it is to be understood that a given inventory for a network may include multiple types of spare components of different quantities, as will be described below with respect to the warehouse spare and location optimization process 300.


A specific implementation of a warehouse configuration given a particular network of nodes, along with specific quantities of spare components to be stored at the selected warehouse nodes, is referred to herein as a “spare component management configuration” or simply a “management configuration”. That is, a management configuration comprises at least one warehouse node selected from the nodes of the network and a quantity of spare components in the inventory of the network to be stored at the at least one warehouse node. The optimal determination of a management configuration for a given network is discussed below with respect to the optimization process 200.



FIG. 2 is a data flow diagram depicting an exemplary embodiment of a process 200 for optimizing spare component management for a network. Inventory data (“inventory 204”), operator constraint data (“operator constraints 206”), and availability parameters 210 are stored in a database 202. The inventory 204 may include the quantity of spare components for the network and the current locations within the network that are storing the spare components. The availability parameters 210 include data that affects the availability of the spare components within the network. For example, the availability parameters 210 may include failure rates, minimum repair times, restocking times, stockout probabilities, delivery times, and like type availability parameters known in the art. The availability parameters 210 may include different data for each type of spare component that is to be warehoused within the network. The operator constraints 206 include data provided the network operator that represents minimum requirements for the warehousing solution. For example, the operator constraints 206 may include critical repair times related to service level agreements (SLAs) and target stockout probabilities.


The inventory 204, the operator constraints 206, and the availability parameters 210 are provided to a warehouse spare and location optimization process 300 as parametric input. The warehouse spare and location optimization process 300 is described below with respect to FIG. 3. The warehouse spare and location optimization process 300 produces results 208. The results 208 may include, for example, minimum downtimes and the number of critical repair time violations for various management configurations for various warehouse configurations. That is, the results 208 may include data for multiple warehouse configurations (e.g., distributed, centralized with a single warehouse node, centralized with two warehouse nodes, etc). For each warehouse configuration, the results 208 may include data for multiple management configurations. The management configurations may include the quantities of spare components to be stored at the warehouse nodes of the network, as well as minimum downtimes, and critical repair time violations. The management configuration with the least minimum downtime and least violations of critical repair times may then be selected as the optimal management configuration for each warehouse configuration. In turn, the optimal warehouse configuration may be selected based on the optimal management configurations.


From the results 208, an optimal warehousing solution may be implemented within the network 100. After implementation of the warehousing solution, the parameters input to the warehouse spare and location optimization process 300 may change. For example, several of the availability parameters 210 may change due to the optimization provided by the selected warehousing solution. Thus, in one embodiment of the invention, the inventory 204, the operator constraints 206, and the availability parameters 210 stored within the database 202 may be dynamically updated during operation of the network after implementation of the selected warehousing solution. The process 200 may then be repeated for additional optimization of the warehousing solution.



FIG. 3 is a flow diagram depicting an exemplary embodiment of a warehouse and location optimization process 300. The process 300 begins at step 302, where an inventory is obtained. At step 304, availability parameters are obtained. At step 306, operator constraints are obtained. At step 308, a warehouse configuration is selected. At step 310, management configurations are determined using the inventory, availability parameters, operator constraints, and the selected warehouse configuration. At step 312, a determination is made as to whether additional warehouse configurations are to be selected. If so, the process 300 returns to step 308 and repeats. If not, the process 300 outputs results at step 314. For example, step 310 may be repeated for a distributed warehouse configuration and for a centralized warehouse configuration having various numbers of warehouse nodes.


The process 300 may be more thoroughly understood with reference to the following mathematical description of the warehouse and location optimization process. The process will be described first with respect to a distributed warehouse configuration and then with respect to a centralized warehouse configuration. For the distributed warehouse configuration, the inventory in the network may be represented as:
x=[x1xixN]T=[x11x1kx1Mxi1xikxiMxN1xNkxNM],

where i represents the ith node in the network, k is the kth type of in-service network component (“inventory item”), xik is the quantity of the kth in-service network element at the ith node that requires spare components, N is the total number of potential warehouse nodes, and M is the total number of inventory items. The inventory failure rates may be represented as:

λ=[λ1 . . . λk . . . λM],

where λk is the failure rate for the kth inventory item and is expressed in units of failures in time (FIT) (e.g., equal to 10−9 failures/hour). The expected failures for the network is then given by:
f=[f1fifN]T=[f11f1kf1Mfi1fikfiMfN1fNkfNM],

where fik=xik·λk is the total number of failures per hour for the kth inventory item at the ith node of the network. The minimum repair times may be represented as follows:
t=[t1titN]T=[t11t1kt1Mti1tiktiMtN1tNktNM],

where tik is the minimum repair time for the kth inventory item at the ith node of the network.


The quantity of spare components and the stockout probabilities for the network may be represented as follows:
s=g(ai·Pt)[s1sisN]T=[s11s1ks1Msi1siksiMsN1sNksNM]p=h(ai·Pt)[p1pipN]T=[s11s1ks1Msi1siksiMsN1sNksNM],

where ai=Niρiτ, Pt is the target stockout probability, sik is the quantity of spare components for the kth inventory item at the ith node of the network, and pik is the stockout probability for the kth inventory item at the ith node of the network. The variable ai is the quantity of spare components to be replenished for the ith node of the network, Ni is the in-service population of the spare components served by the sparing pool for the ith node of the network, ρi is the spare component removal rate (e.g., per 109 hours) for the ith node of the network, and τ is the mean time to restock a spare component.


Operators g and h are the Erlang-C spare and stockout probability functions defined below. The g function returns the quantity of spare components, sik, for each inventory item, k, for each node, i. The h function returns the stockout probabilities, pso, of each inventory item, k, at each node, i. The following Erlang-C equation is used to determine the quantity of spare components and stockout probabilities for the inventory:
pso=aisisi!(1-ai/si)aisisi!(1-ai/si)+k=0si-1aikk!.

The quantity of spares is increased until the stockout probability, pso, is equal to or less than the target stockout probability, Pt. The total number of spares required for the network is given by:
k=1Mi=1Nsik.


The inventory downtime for available spare components is given by:
rs=[r1srisrNs]T=[t11f11t1kf1kt1Mf1Mti1filtikfiktiMfiMtN1fN1tNkfNktNMfNM].

The inventory downtime for unavailable or out-of-stock spare components is given by:
rs_=[r1s_ris_rNs_]T=[τ1f11τkf1kτMf1Mτ1filτkfikτMfiMτ1fN1τkfNkτMfNM],

where τk is the restocking time for the kth inventory item. The total inventory downtime may then be expressed as:
r=[r1rirN]T=[r11r1kr1Mri1rikriMrN1rNkrNM],

where rik=tikfik(1−pik)+τikfikpik is the total inventory downtime for the kth inventory item at the ith node of the network. The total downtime for the network under the distributed warehousing configuration is then given by:
DTD=k=1Mi=1Nrik.


For a centralized warehouse configuration having a single warehouse node, the inventory, failure rates, and expected failures may be represented as described above (i.e., the x-matrix, the λ-vector, and the f-matrix, respectively). In addition, the quantity of spare components (s-matrix) and the stockout probabilities (p-matrix) for the network may be represented substantially as described above. However, unlike the distributed warehouse configuration, the elements in each row of the s-matrix provide the total quantity of spare components for each inventory item for each of the possible warehouse nodes, rather than the quantity of spare components stored at each node of the network.


The inventory repair times are the same as those of the distributed warehouse configuration, since the repair times are not dependent on the type of warehouse configuration. The minimum repair times may be represented as:
tr=[t1rtirtNr]T=[t11rt1krt1Mrti1rtikrtiMrtN1rtNkrtNMr],

where tikr is the repair time for the kth inventory item at the ith potential warehouse node. The algorithm for the centralized warehouse configuration may also take into account the delivery times. The inventory delivery times from the mth (m ranges from 1 to N, to total number of nodes in the network) potential warehouse node to each faulted location may be represented as follows:
d=[d1didN]T=[d11d1jd1Ndi1dijdiNdN1dNjdNN],

where i is the warehouse node and j is the location where the spare is needed. The total repair time may then be computed for each potential warehouse node in the network. Thus, the total repair time associated with the mth potential warehouse node is given by:
tm=[t1mtimtNm]T=[t11rt1krt1Mrti1rtikrtiMrtN1rtNkrtNMr]+[dm1dm1dm1dmidmidmidmNdmNdmN]=[t11t1kt1Mti1tiktiMtN1tNktNM]

where tik=tikr+dmi.


As described above, the network operator may provide critical repair times for each inventory item. A critical repair time (CRT) is the minimum time in which a particular inventory item must be replaced. Each tik must therefore satisfy the CRT for the kth inventory item (i.e., tik≦CRTk). Violation of CRT occurs whenever tik>CRTk. The number of violations for the mth potential warehouse node is therefore given by:
vm=[vimvkmvMm]T=[i=1Nu(ti1)i=1Nu(tik)i=1Nu(tiM)]T,

where
u(tik)=1iftik>CRTk=0iftikCRTk.


If spares are available, the downtime for the kth inventory item at the ith node is:
[t11f11tlkflktlMflmtilfiltikfiktiMfiMtNlfNltNkfNktNMfNM]

The inventory downtime for each inventory item for the mth potential warehouse node may be represented as follows:
rmS=[i=1Nti1fi1i=1Ntikfiki=1NtiMfiM]=[r1mSrkmSrMmS]

If spares are unavailable, the downtime for the kth inventory item at the ith node is:
[τ1f11τkf1kτMf1Mτ1fi1τkfikτMfiMτ1fN1τkfNkτMfNM],

where τk is the restocking time for the kth inventory item. The inventory downtime for each inventory item for the mth potential warehouse node may be represented by:
rmS_=[i=1Nτ1fi1i=1Nτkfiki=1NτMfiM]=[r1mS_rkmS_rMmS_]

The total inventory downtime for the mth potential warehouse is given by:

rm=[rlm . . . rkm . . . rMm]
rkm=rkmS(1−pmk)+rkm{overscore (S)}pmk

The total inventory downtime for all potential warehouse nodes may then be expressed as:
r=[r1rmrN]T=[r11r1kr1Mrm1rmkrmMrN1rNkrNM],

such that the total downtime for the mth potential warehouse node is:
k=1Mrmk.


The total downtime for the network using the centralized warehouse configuration is given by:
DTc=[k=1Mr1kk=1Mrmkk=1MrNk]T

The ranking of total downtimes for the potential warehouse nodes is given by:
RC=Rank[k=1Mr1kk=1Mrmkk=1MrNk]T.


The computation for a centralized warehouse configuration having two warehouse nodes, m and n, is similar to that of a single warehouse node centralized warehouse configuration. For a single warehouse node system, the total number of potential warehouse nodes is equal to N, assuming that all nodes in the network can be considered as warehouse nodes. For a two-warehouse node system, however, the maximum number of potential warehouse node combinations is given by:
C=N!(N-r)!r!,

where r is the number of nodes considered at a time (e.g., 2). If the total number of potential warehouse nodes is six (i.e., N=6), the total number of potential warehouse node combinations is 15 for a two-warehouse node system.


The inventory repair times and delivery times may be represented as shown above for the centralized warehouse configuration having a single warehouse node. Assume that there are q scenarios ranging from 1 to C. The shortest delivery times from potential warehouse nodes m or n to the faulted location for the qth scenario is given by:

dq=[d1q . . . diq . . . dNq]T=[min(dm1,dn1) . . . mindmi,dni) . . . min(dmN,dnN)]T

The spare components for each inventory item, k, must now be stored in either the mth or nth potential warehouse nodes. The following matrix keeps tracking of where the spare components should be stored:

Iq=[I1q . . . Iiq . . . INq]T,

where
Iiq=1ifdnidmi;warehousenode1=2ifdmi>dni;warehousenode2.


The spare components and the stockout probabilities for the two warehouse node centralized warehouse configuration may be determined as follows:
N1kq=i=1Nxiku1i;N2kq=i=1Nxiku2i,whereIiq=1ifu1i=1;u2i=0=2ifu1i=0;u2i=1.

In addition,

aikqkτk(N1kq); a2kqkτk(N2kq),

where a1kq,a2kq is the total number of inventory items to be replenished at nodes m and n; N1kq,N2kq is the in-service population of the kth inventory item served by the sparing pool at nodes m and n; ρk is the removal rate of the kth inventory item (e.g., per 109 hours); and τk is the time to restock the kth inventory item. The quantity of spare components is then given by:

s1q=[s11q . . . s1kq . . . s1Mq]
s2q=[s21q . . . s2kq . . . s2Mq];
s1kq=g(a1kq,Ptk)
s2kq=g(a2kq,Ptk)

and the stockout probabilities are given by:

p1q=[p11q . . . p1kq . . . p1Mq]
p2q=[p21q . . . p2kq . . . p2Mq],
p1kq=h(a1kq,Ptk)
p2kq=h(a2kq,Ptk)

where Ptk is the target stockout probability for the kth inventory item, and where g and h are the Erlang-C spare and stockout probability functions, as described above. Unlike the single node centralized warehouse configuration, two spare pools are kept for the inventory items to replenish failed items at different nodes. Since the total number of in-service inventory items each node has to protect is dependent on the shortest delivery time from the spare pool to the faulted location, it therefore changes for each scenario, q. Spare and stockout probability matrices, s and p, must therefore by computed for each scenario, q, and cannot be computed ahead of time.


The total repair times from warehouse nodes m or n may be represented as:
tq=[t1titN]T=[t11qt1kqt1Mqti1qtikqtiMqtN1qtNkqtNMq],

where tikq=tikq+diq, where d is the delivery time. Each tikq must satisfy the CRT for the inventory item, k. The number of violations for each warehouse node located at node i is therefore:
vq=[k=1Mv1kk=1Mvikk=1MvNk]T,

where
vik=1iftikq>CRTk=0iftikqCRTk.


The inventory downtime for a 2-warehouse node centralized warehouse configuration may be represented as shown below. If spares are available, the downtime for the kth inventory item at the ith location is:
[tllqflltlkqflktlMqflMtilqfi1tikqfiktiMqfiMtNlqfNltNkqfNktNMqfNM].

If spares are available, the downtime for a given scenario, q, is thus:
rqs=[i=1Nti1qfi1i=1Ntikqfiki=1NtiMqfiM].

Likewise, if spare components are unavailable, the downtime for the kth inventory item at the ith location is:
[τ1f11τkf1kτMf1Mτ1fi1τkfikτMfiMτ1fN1τkfNkτMfNM].

If spares are unavailable, the downtime for a given scenario, q, is thus:
rqS_=[i=1Nτ1fi1i=1Nτkfiki=1NτMfiM].

Accounting for the stockout probability,
rqS=[rq1SrqkSrqMS]=[i=1Nti1qfi1uii=1Ntikqfikuii=1NtiMqfiMui],

where
ui=(1-p1kq)ifIiq=1=(1-p2kq)ifIiq=2.

In addition,
rqS_=[rq1S_rqkS_rqMS_]=[i=1Nτ1fi1uii=1Nτkfikuii=1NτMfiMui],

where
ui=p1kqifIiq=1=p2kqifIiq=2.


Then,

rq=[rq1 . . . rqk . . . rqM],

where rqk=rqkS+rqk{overscore (S)}.


The total downtime for a 2-warehouse node centralized warehouse configuration may be computed as follows:
r=[r11r1kr1Mrq1rqkrqMrC1rCkrCM].


The total downtime for each scenario, q is thus:
k=1Mrqk.

The total downtime for the 2-warehouse node centralized warehouse configuration is:
DTC2=[k=1Mr1kk=1Mrqkk=1MrCk]T.

The ranking of total downtime is given by:
RC=Rank[k=1Mr1kk=1Mrqkk=1MrCk]T.


In reality, the real or actual value of the parameters used above (e.g., availability parameters) at any one time is uncertain. As such, in another embodiment, the uncertainty of such parameters may be modeled by their respective probability distributions. Notably, the value of each variable is sampled using the associated probability distribution using, for example, a Latin Hypercube sampling technique. The Latin Hypercube sampling technique is a stratified sampling technique that will accurately recreate the probability distributions specified by the distribution functions in fewer iterations than traditional sampling techniques, such as Monte Carlo sampling.



FIG. 4 is a block diagram depicting an exemplary embodiment of a computer 400 suitable for implementing processes and methods described above. The computer 400 includes a central processing unit (CPU) 401, a memory 403, various support circuits 404, and an I/O interface 402. The CPU 401 may be any type of microprocessor known in the art. The support circuits 404 for the CPU 402 include conventional cache, power supplies, clock circuits, data registers, I/O interfaces, and the like. The I/O interface 402 may be directly coupled to the memory 403 or coupled through the CPU 401. The I/O interface 402 may be coupled to various input devices 412 and output devices 411, such as a conventional keyboard, mouse, printer, display, and the like. In addition, the I/O interface 402 may be coupled to a network 413 and may be adapted for communication with the database 202 to receive and transmit data, such as data files and the like.


The memory 403 may store all or portions of one or more programs and/or data to implement the processes and methods described above. Although the invention is disclosed as being implemented as a computer executing a software program, those skilled in the art will appreciate that the invention may be implemented in hardware, software, or a combination of hardware and software. Such implementations may include a number of processors independently executing various programs and dedicated hardware, such as application specific integrated circuits (ASICs).


The computer 400 may be programmed with an operating system, which may be OS/2, Java Virtual Machine, Linux, Solaris, Unix, Windows, Windows95, Windows98, Windows NT, and Windows2000, WindowsME, and WindowsXP, among other known platforms. At least a portion of an operating system may be disposed in the memory 403. The memory 403 may include one or more of the following random access memory, read only memory, magneto-resistive read/write memory, optical read/write memory, cache memory, magnetic read/write memory, and the like, as well as signal-bearing media as described below. The memory 403 may store all or a portion of the warehouse and location optimization process 300 of FIG. 3.


An aspect of the invention is implemented as a program product for use with a computer system. Program(s) of the program product defines functions of embodiments and can be contained on a variety of signal-bearing media, which include, but are not limited to: (i) information permanently stored on non-writable storage media (e.g., read-only memory devices within a computer such as CD-ROM or DVD-ROM disks readable by a CD-ROM drive or a DVD drive); (ii) alterable information stored on writable storage media (e.g., floppy disks within a diskette drive or hard-disk drive or read/writable CD or read/writable DVD); or (iii) information conveyed to a computer by a communications medium, such as through a computer or telephone network, including wireless communications. The latter embodiment specifically includes information downloaded from the Internet and other networks. Such signal-bearing media, when carrying computer-readable instructions that direct functions of the invention, represent embodiments of the invention.


While the foregoing is directed to the illustrative embodiments of the present invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof, and the scope thereof is determined by the claims that follow.

Claims
  • 1. A method of optimizing spare component management for a network having a plurality of nodes, comprising: obtaining availability parameters associated with an inventory of spare components; and determining a plurality of management configurations in response to said availability parameters, each of said plurality of management configurations comprising at least one warehouse node selected from said plurality of nodes and a quantity of spare components in said inventory to be stored at said at least one warehouse node.
  • 2. The method of claim 1, further comprising: selecting at least one warehouse configuration for said plurality of nodes; and repeating said determining step for each said warehouse configuration.
  • 3. The method of claim 2, wherein said at least one warehouse configuration comprises a distributed warehouse configuration and a centralized warehouse configuration.
  • 4. The method of claim 1, wherein said inventory of spare components is defined by a plurality of component types, and said availability parameters comprise at least one of a failure rate, a minimum repair time, a restocking time, and a stockout probability associated with each of said plurality of component types.
  • 5. The method of claim 4, further comprising: for each of said plurality of management configurations, computing an expected downtime of said network using said minimum repair time associated with at least one of said plurality of component types.
  • 6. The method of claim 5, wherein, for each of said plurality of management configurations, said expected downtime of said network is further computed using delivery times from said at least one warehouse node to remaining ones of said plurality of nodes.
  • 7. The method of claim 4, further comprising: obtaining a critical repair time associated with each of said plurality of component types; and for each of said plurality of management configurations, computing a number of expected critical repair time violations.
  • 8. The method of claim 4, wherein said determining comprises: obtaining a target stockout probability for each of said plurality of component types; for each of said plurality of management configurations, computing said quantity of spare components to be stored at said at least one warehouse node by adjusting a quantity of each of said plurality of component types until said respective stockout probability is less than or equal to said respective target stockout probability.
  • 9. The method of claim 1, wherein said inventory of spare components is obtained dynamically from said network.
  • 10. The method of claim 1, wherein said availability parameters are obtained dynamically from said network.
  • 11. A computer readable medium having stored thereon instructions that, when executed by a processor, cause the processor to perform a method of optimizing spare component management for a network having a plurality of nodes, comprising: obtaining availability parameters associated with an inventory of spare components; and determining a plurality of management configurations in response to said availability parameters, each of said plurality of management configurations comprising at least one warehouse node selected from said plurality of nodes and a quantity of spare components in said inventory to be stored at said at least one warehouse node.
  • 12. The computer readable medium of claim 11, further comprising: selecting at least one warehouse configuration for said plurality of nodes; and repeating said determining step for each said warehouse configuration.
  • 13. The computer readable medium of claim 12, wherein said at least one warehouse configuration comprises a distributed warehouse configuration and a centralized warehouse configuration.
  • 14. The computer readable medium of claim 11, wherein said inventory of spare components is defined by a plurality of component types, and said availability parameters comprise at least one of a failure rate, a minimum repair time, a restocking time, and a stockout probability associated with each of said plurality of component types.
  • 15. The method of claim 4, further comprising: for each of said plurality of management configurations, computing an expected downtime of said network using said minimum repair time associated with at least one of said plurality of component types.
  • 16. The computer readable of claim 15, wherein, for each of said plurality of management configurations, said expected downtime of said network is further computed using delivery times from said at least one warehouse node to remaining ones of said plurality of nodes.
  • 17. The computer readable medium of claim 14, further comprising: obtaining a critical repair time associated with each of said plurality of component types; and for each of said plurality of management configurations, computing a number of expected critical repair time violations.
  • 18. The computer readable medium of claim 14, wherein said determining comprises: obtaining a target stockout probability for each of said plurality of component types; for each of said plurality of management configurations, computing said quantity of spare components to be stored at said at least one warehouse node by adjusting a quantity of each of said plurality of component types until said respective stockout probability is less than or equal to said respective target stockout probability.
  • 19. An apparatus for optimizing spare component management for a network having a plurality of nodes, comprising: means for obtaining availability parameters associated with an inventory of spare components; and means for determining a plurality of management configurations in response to said availability parameters, each of said plurality of management configurations comprising at least one warehouse node selected from said plurality of nodes and a quantity of spare components in said inventory to be stored at said at least one warehouse node.
  • 20. A system optimizing spare component management for a network having a plurality of nodes, comprising: a processing unit having access to one or more storage devices; at least a portion of the one or more storage devices storing an inventory of spare components and availability parameters associated with said inventory; at least another portion of said one or more storage devices having a program product configured to determine a plurality of management configurations in response to said availability parameters, each of said plurality of management configurations comprising at least one warehouse node selected from said plurality of nodes and a quantity of spare components in said inventory to be stored at said at least one warehouse node.