The invention pertains to digital data processing and, more particularly, to automated methods and apparatus for managing and routing work. The invention has application, by way of non-limiting example, in call service centers and in other applications requiring routing and/or assignment of tasks to resources.
Work can be thought of, by way of non-limiting example, as consisting of individual work items that are subject to a workflow that solves a particular problem. A resource is a person, system or a piece of equipment, by way of further example, that has a capacity for work. Intelligent routing, assignment and/or work management (sometimes referred to below collectively as “routing”) of work items to resources is a critically important problem in today's large and complex business environments.
Regardless of the specifics, routing problems share the following characteristics: there may be a large number of tasks (e.g., many call service center customers waiting in queues for service); workflows are often complex and may not be highly differentiated; available resources typically vary greatly in level of skill, and the more skilled or apt resources are typically scarce. The bottom line in many business applications, at least, is that customers expect fast, efficient service, so routing decisions have to be good and have to be made quickly. They also have to be effectively managed in light of evolving deadlines and circumstances.
Computer based systems for assigning work to resources are well known in the art. Such systems include discrete-parts manufacturing scheduling systems, batch process scheduling systems, optimization systems for matching energy producers with consumers, and call center workflow routers. Simple systems of this type consider one work item at a time; they take the next work item from a queue, search for a resource that is capable of performing the work, and make the assignment.
The advantages of such a simple system are that it is easy to implement, and that it makes fast decisions. The main drawback of such a system is that it can easily make bad decisions. The resource assigned in this simple way may be better utilized if it were assigned to a work item further back in the queue. Thus, more sophisticated systems consider multiple work items at the same time. Assignments are made taking into account costs and capacities of resources, so that the cheapest resources are used whenever possible. This results in significantly better decisions, than those from the most simple system. However, there are still problems that more sophisticated systems in the prior art do not properly address.
An object of this invention is to provide improved methods and systems for routing (and/or assigning) items to resources.
A further object is to provide such methods and systems for managing a pool of assigned items to pursue continued optimizations.
A related object is to provide such methods and systems as facilitate the ongoing management, e.g., reassignment, of items as deadlines and other service levels are passed.
Another object of the invention is to provide such methods and apparatus for service level driven skills-based routing.
Another more particular object of the invention is to provide such methods and systems as achieve optimal assignment of work items to resources.
Still another object of the invention is to provide such methods and systems as can be applied in a range of applications, business-related or otherwise.
Still other objects are to provide such methods and systems as can be implemented on a variety of platforms and without undue expense or resource consumption.
The foregoing are among the objects achieved by the invention which provides, in one aspect, improved methods and apparatus for skills-based routing. These assign a work item to one (or more) of a plurality of resources based on fitness, for example, of skills required by the former to those provided by the latter. Assignment takes into account the level of stress on the work item and/or resources, such that the number of resources—or size of the resource pool—fit for assignment varies as the level of stress varies. Moreover, as the level of stress changes (for example, increasing as a result of a missed goal deadline) the work item can be evaluated for reassignment to other resources.
Systems according to the invention can be used, by way of example, to route a call or other request made by a customer to a service center. The requirements for processing the call (determined, for example, by an incoming call operator) are matched against the skill sets of available customer service agents, taking call and/or resource stress levels into account. In some embodiments of the invention, the pool size may increase in size as stress levels go higher, while in other embodiments, it may get smaller.
For example, some implementations may match an incoming call having a low stress factor (e.g., a newly received call from a standard customer) to a smaller pool of agents with both required and desired skills, while assigning a call with a higher stress factor to a larger pool of agents with at least required skills. Other embodiments may match an incoming call having a low stress factor to the larger pool of agents having at least the required skills, while assigning a call with a higher stress factor (e.g., a call from a priority customer) to an agent from the smaller pool of agents who have both required and desired skills.
To give a few examples, a system according to the invention can assign a newly received technical support call from a native German-speaking customer to the next available agent from a pool of service agents who also speak native German and who are expected to become available (e.g., from handling prior calls) within ten minutes. If the call is from a priority customer, on the other hand, the system can assign the call to a larger pool of service agents who are proficient in German—though not necessarily native German speakers—who are expected to become available more quickly. Alternatively, the system can assign the priority customer's call to a smaller pool of agents who are proficient in German and who have particular expertise in the class of problem experienced by the caller. Still further alternatives provide for assignment of the priority customer's call “out of band,” e.g., to a CEO, vice president, or other person or thing who, though not intended to address the caller's problem directly, can provide assurances that it will be handled expertly, as quickly as possible, and so forth.
Related aspects of the invention provide methods as described above in which at least selected resources are assigned skill levels indicating their respective proficiencies with respect to a given skill. Likewise, resources can have skill preferences, e.g., identifying skills the use of which is preferred (e.g., by the resource himself, herself or itself). Moreover, work items can require skill levels.
One or more of the foregoing can be taken into account when the resources are evaluated for assignment to the work items. In the example above, for example, calls with low stress factors may be assigned to service agents who have the required proficiency at a given skill and who prefer (or whom are preferred for) handling the respective types of calls. Calls with high stress factors, on the other hand, may be assigned among a larger pool of service agents with sufficient proficiency at the requisite task, e.g., regardless of whether they prefer (or are preferred) to handle the calls.
The invention provides, in other aspects, methods as described above in which work items are associated with both desired and required skills. By way of example, a bilingual caller to a service center may have a question regarding detailed operation of a specific product. A skill required of an agent assigned to handling the call is knowledge of the product and basic proficiency in the language. A desired skill is native proficiency in the caller's language of choice.
Other aspects of the invention provide methods as described above in which the completion status of work items are taken into account as a stress factor in assigning resources. For example, work items that will be completed by a first deadline (e.g., a goal deadline) can have lower stress factor. Those that will not be completed until a second deadline (e.g., a due deadline), a higher stress factor. And, those that will not be completed until after the second deadline, a still higher factor. Using a foreign language translation service as an example, an incoming technical translation received early has a low stress factor and can be assigned to any available translator among the pool of those having appropriate language skills (i.e., a required skill) and technical background (i.e., a preferred skill). A late arriving job on the other hand has a higher stress factor and may be assigned among a pool of translators simply having necessary language skills, thereby, insuring that the job will be completed by deadline.
Related aspects of the invention provide for reevaluation and assignment of work items, e.g., as they approach and pass deadlines. Continuing the above example, the translation job received from a client early can be “deskilled,” i.e., reassigned among the larger pool simply having the required language skills, e.g., if or as the first, goal deadline is passed. Alternatively, the job can be reassigned among a small pool of translators who have not only the required language skills and preferred technical skills, but who also have a complimentary skill (such as previous experience with client or in the specific technical field covered by the translation). Likewise, if and as first or subsequent deadlines are passed, the job can be assigned out of band, e.g., to a CEO, who can provide necessarily explanations and/or facilitate execution of the job.
Further related aspects of the invention provide methods as described above in which resource utilization is taken into account in assigning resources to work items. These factors can be a measure of a utilization level of each of the plurality of resources with respect to its utilization capacity or capacities and can identify a complimentary stress level for each resource. For example, resources in use at or below a maximum utilization capacity can have a lower stress factor. Those in use above that capacity but below an emergency capacity can have a higher stress factor. Resources in use above the emergency capacity can have a still higher stress factor. In the example above, regular and/or overtime hours can provide a basis for determining resource stress factors used in assigning translators to incoming jobs.
Further aspects of the invention provide methods as described above in which an optimization, which utilizes a cost function based on a matrix of values of the respective fitnesses, is used to assign each of a plurality of work items to one (or more) of a plurality of resources.
Still further aspects of the invention provide digital data processing and other systems operating in accord with the methods summarized above.
These and other aspects of the invention are evident in the drawings and in the description that follows.
A more complete understanding of the invention may be attained by reference to the drawings, in which:
The processing center 12 can be any service provider or other person, business or entity that utilizes work item routing (or, in the illustrated instance, request routing). Non-limiting examples include retailers, mail order houses, professional service providers, counseling centers, and “help” bureaus, and so forth. A common characteristic among these is that they field one or more work items (e.g., requests) for processing by one or more resources (e.g., service agents).
Illustrated “customers” 14 represent any persons, businesses, entities or other sources of work items (or, in the illustrated instance, requests) or to which work items (e.g., requests) are attributable. In the case of a service provider, such as a help bureau, work items can be, by way of non-limiting examples, requests from callers for assistance. In the case of a mail order house, work items can be requests from customers for goods. In the case of a professional service provider, work items can be requests from clients for services. Of course, it will be appreciated that, in any given embodiment, customers 14 may have access to the service center 12 other than via the illustrated mediums.
Illustrated requests represent any “work items” requiring routing (or assignment). In the illustrated embodiment, these are requests that will be processed by employee-agents 18. In other embodiments, they can be other items of information requiring routing/assignment to other resources of the processing center 12.
Agents 18 represent any resources to which items can be routed and/or assigned. In the illustrated embodiment, these are employee-agents of the service center 12. In other embodiments they may represent other persons, businesses and/or entities to which work items are assigned and/or routed for processing.
Turning back to the drawing, requests or other work items received by the processing center 12 are initially processed by intake processing personnel and/or apparatus 16. These can include call operators, receptionists, automated phone answering equipment, web servers, or otherwise. Intake processing 16 comprises identifying, evaluating and/or augmenting incoming work items—e.g., in the illustrated embodiment, requests and the customers to which they are attributable. This also includes encoding the work items in a preferably common format for routing by a routing system 20 described below.
By way of non-limiting example, intake processing 16 at a retailer can include a combination of telephone operators, customer order desk personnel and web site servers. Order requests received by each of these can be categorized and encoded as “work items” requiring fulfillment by warehouse and back-office personnel 18.
Routing system 20 represents digital data processing apparatus, e.g., a workstation, mainframe, embedded processor or other processing device, that routes and/or assigns work items placed in routing queue(s) 20B to resources. The operation of the routing system 20 is described below. Although the illustrated embodiment shows intake processing as being separate from routing system 20, those skilled in the art will appreciate that intake processing may utilize or may itself include, or be part of, system 20, e.g., as indicated by the double arrows connecting elements 18 and 20.
The Routing Problem
The routing problem starts with a set of work items and a set of resources. The problem is to assign resources to work items in an optimal way, subject to constraints based on detailed information about the resources and work items. Exactly what “optimal” means will vary greatly depending on the details of a particular application, and can be expressed in a variety of ways, as will be discussed. For example, in some applications, the most important priority may be to minimize the number of work items that are past due, whereas in other applications, efficient use of resources may be most important.
Queue Configurations
Work items appear to the router in one or more queues 20B, the configuration of which can have an important effect on the kind or routing that can be done. The simplest case is a single queue where work items are processed, one at a time, in a first in, first out (FIFO) sequence, as shown
In such a simple case, the router 20A has relatively little information upon which to base decisions, because it considers only the next work item, not all the work items in the queue. The best it can do is dispatch the work item to the next available resource (e.g., 18A) that is capable of performing the work.
A more sophisticated system has parallel queues, as shown in
Work Item and Resource Detailed Information
As mentioned previously, the fitness of a particular resource assignment depends on detailed information about the corresponding work item and resource. The representation of this information will be discussed next. After this, the details of the algorithms will be given.
Representation of Skills
In the illustrated embodiment, a skill is represented as a pair of skill name (a string) and proficiency (an integer). Examples of this representation, e.g., useful in a assigning administrative tasks, e.g., to a clerical services processing center, are:
Those skilled in the art will appreciate that though the illustrated embodiment utilizes this simple pairing of a skill name expressed as a string and proficiency level expressed as an integer, other embodiments may use alternate mechanisms as well. For example, the skill could be implemented as a database record with multiple fields, one of which is the skill name, and one of which is the skill level. Skill level itself need not be limited to integers; real numbers, or enumerated set values could be used.
Representation of Skills in Resources
In the illustrated embodiment, each resource (e.g., agent 18) has three sets of skills: preferred skills, secondary skills, and tertiary skills. Preferred skills are the skills that are most consistent with the job function of the resource. Secondary and tertiary skills are ones the resource has, possibly from previous job functions, that are not part of the resource's current job function. For example, the preferred skills for a manager would be managerial duties. Secondary skills might include skills normally associated with the manager's subordinates. Tertiary skills might be skills obtained from a previous job.
Note that, in the illustrated embodiment, the dimension of preferred/secondary/tertiary is orthogonal to that of skill level. Thus, this representation allows for preferred skills that have lower skill levels than secondary skills (even though this is unlikely in practice).
The preferred/secondary/tertiary dimension can be generalized to be an integer in order to allow for more than three levels of preference. A skill is then represented as a triple of name, proficiency level, and preference level. In the following discussion, however, the preferred/secondary/tertiary is used.
Representation of Skills in Work Items
In the illustrated embodiment, each work item has two sets of skills: desired skills and required skills. For work items, the skill level integer represents the minimum level needed. Either the desired skills, or the required skills, but not necessarily both, have to be fulfilled by a resource assigned to this work item.
Representation of Service Level
In the illustrated embodiment, service level is represented, within a work item, as a triple of name, absolute time, and priority rating.
Examples of service levels are:
Service levels are concatenated into lists that are associated with work items. For example, the three example service levels above might be sequenced together to express the service level requirements for a particular work item. Such a sequence can be thought of as the “order” for a work item. Note that the dramatic increase in priority rating represents escalation of the work item's urgency as it becomes past due. In addition to changing resource assignments as that urgency increases, a system according to the invention can cause additional, secondary work items related to the primary work item to be invoked and/or cancelled.
Service level information in (or derivable on behalf of) a work item may be derived from rules, from manual inputs, or otherwise. Service level symbols or names (e.g., “Gold Service”) may be used to facilitate this. The rules may specify the information in a more convenient form than that shown above. For example, rules can be used to specify relative times as well as absolute ones. Thus, rules may specify an absolute date for the goal service level, and cumulative offsets for subsequent service levels. Similarly, rules may specify absolute or additive (incremental) values for the priority ratings. Rules may also specify arbitrary expressions for both time and priority rating components. This allows these values to become functions of any other variable in the system.
Routing Algorithm Details
The illustrated router 20a uses a routing algorithm to evaluate the fitness of individual work-item/resource assignments, and to evaluate combinations of these assignments, attempting to pick that combination which maximizes overall fitness. This functionality is represented in the drawings by evaluator module 24.
Fitness of Resource Assignments
A “resource assignment” is the assignment of a particular resource to a particular work item. The fitness of a resource assignment is a measure (e.g., numerical value or grade) that is a function of skill information for the work item and resource. Thus, an assignment that has a good match of skill required by a work item and provided by a resource will have a higher fitness level. This sort of skill matching is depicted in
Fitness is also a function of the service level of the work item. For example, let's assume the above-described service level sequence (goal, deadline, past deadline). Suppose that the required skills are language proficiency in French or German. The resource pool may include individuals with native language proficiency in one of these languages. Such individuals are a subset of all individuals with good proficiency in one of these languages. Finally, there may be some resources that have a low, but acceptable, level of proficiency (exchange students, for example). The individuals with native language proficiency would include this proficiency in their preferred skills. Other individuals would include their proficiency in their secondary skills, with an appropriate skill level.
Continuing this example, suppose that the current time precedes the goal deadline. In this case, resources that have preferred skills that match the work item's desired skills are given a high fitness. Thus, the native French or German speakers would be considered, but the other resources might not be, even though they have a certain level of proficiency. Suppose now that the work item isn't completed and the current time now falls between the goal deadline and the due deadline. At this point, more resources have to be considered, so resources that have preferred or secondary skills matching the work item's desired or required skills are given a high fitness. Thus, the non-native French or German speakers would now be included in the pool of resources to consider.
Finally, suppose that the work item is past due (or it is estimated that the job will not be completed until it would be past due). At this point, it might be best to apologize to the customer, and defer the work item. To compensate the customer for the delay, the deferred work item might be assigned to special resources by including skills that are not on the preferred list. For example, the work item might be assigned to a manager who knows the customer personally, and who happens to be extremely proficient in French.
The pool of resources available for assignment to any given work item may vary, not only as a function of the stress of that item and/or of the individual resources, but also as a function of all pending work items and all available resources. Future work items (and resources) may factor in as well. This is captured in the cost function z, discussed below, which determines the optimal assignment of work items to resources.
Take, for example, embodiments that increase pool size, as work item stress increases, by making available resources with required skills (as well as desired skills). In some such situations, a larger pool of resources with skills matching the work item's required skills is not utilized until the work item falls past the goal and/or due deadlines. However, if the result of the cost function can be lowered by doing so, then indeed the larger pool will be utilized even though the work item is not past due. This can happen, for example, in situations where assignment of predicted future work items—as well as of existing work items that are not imminently due—are considered during optimization.
Thus, fitness is always a function of a resource and a work item. Specifically, it is a function of the service level of the work item (current priority), and the skill information in the resource and work item. The fitness number approach allows for a declarative specification of the “cost” or “optimality” of a decision made by the routing algorithm. The cost value of a particular solution is the sum of the fitness of all the assignments of resources to work items. Note that this does not dictate a particular algorithm for routing; it merely provides a cost evaluation function that allows the routing algorithm to evaluate the optimality of its decisions.
Fitness functions can be expressed using rules or tables. This allows for a very flexible way to specify escalation, as in the above example.
Level of Stress in a System
Two very useful metrics for how the system is performing are deadline stress and resource stress. Deadline stress is defined as the percentage (or other measure or characterization) of work items that are past deadline. Resource stress is defined as the percentage (or other measure or characterization) of resources utilized.
Partitioning (segmentation) according to work item or resource characteristics is possible. This is just a filtered query of the overall set of work items or resources. Typically, the characteristic being filtered is a desired or required skill of a work item, or a preferred or secondary skill of a resource. For example, the set of all work items requiring the “Verbal French >3” skill would be such a filter. This allows for stress metrics for a particular restricted group (partition) of work items or resources.
Note that the stress metrics are just metrics; they are typically not used for resource assignment decisions. Resource assignment decisions are made by the router 20a based on the fitness ratings described above. The stress metrics give a good overview of what is going on in the system, and thus are useful for higher-level management decisions (whether to allocate overtime, hire temps, etc.). The stress metrics can be stored so that they can be analyzed over time. This might reveal trends important for resource planning.
Those skilled in the art will appreciate that deadline stress and resource stress are but two factors that can be used in assessing system performance. Other embodiments of the invention may use these and/or other assessments of system performance in evaluating a fitness of skills required by a work item and skills provided by a resource.
Safety Valves
What does the system do when work items go past deadline? One “safety valve” has already been mentioned above; when a particular work item's service level reaches a certain priority (usually associated with being past deadline), the fitness ratings of potential resource assignments for that work item are adjusted so that a larger number of resources may be considered (see previous discussion).
If this does not solve the problem, the system goes into deadline stress. A problem formulation where a cost penalty for unassigned work items is subtracted from the overall value of the solution allows the router 20a to account for this situation. Thus, the routing algorithm strives to find solutions that minimize the number of un-assigned work items. If the best solution has un-assigned work items, then the problem exists.
An enhancement to the problem formulation allows the system to not only indicate that there are un-assigned work items, but also to predict when they might be done. Here, the routing algorithm assigns resources not just for the current time, but over some finite time horizon. This capability to estimate when work items will be done allows the system to also estimate when resources will become available. Because such an algorithm schedules things in the future based on current assumptions, and because these assumptions may change, the schedule generated at any time may have to be adjusted in the future. This more sophisticated kind of router 20a is better because the cost penalty is a function not only of the number of un-assigned work items, but also, the extent to which they are late. This allows for more sophisticated trade-off decisions between getting a job done earlier with a less than ideal resource vs. getting it done later with an ideal resource.
An alternate embodiment estimates when resources will become available for further assignment. This can be based on pre-coded or past recorded information regarding each resource's schedule, as well as on estimation of the time when each resource will complete a prior assignment. As above, the routing algorithm takes these estimates into account when making new assignments.
This sort of trade-off suggests an additional safety valve. Any work item can optionally have a secondary work item that may be performed as a “delaying” action when the work item is deadline-stressed. For example, it is often the case that a customer would prefer a scheduled interaction (at some later time) to waiting for a half hour in a queue. Thus, the router 20a has the option of assigning a resource to the secondary work item and leaving the primary work item un-assigned (or assigned to an imaginary resource, in the case of certain routing algorithms). Whether this is actually done is up to the router 20a which makes its decision based on the various cost trade-offs. This process is depicted in
The representation of the secondary work item includes all types of information that the primary work item has. For example, the secondary work item has its own set of desired and required skills.
Detailed Problem Formulation
Problem formulation involves translating the information in the work items, resources, and associated rules into a form that allows for efficient solution by the routing algorithms. Many resource assignment algorithms require the problem data to be in a very specific format, so correct problem formulation is crucial to good performance.
A general resource assignment problem can be stated mathematically as shown in the following way:
Let
xij=1 if resource i is assigned to work item j
xij=0 otherwise Eq. 1
and
cij be the cost of assigning resource i to work item j
then the optimal solution is obtained by minimizing z where
subject to the constraints
This sort of problem formulation is compatible with an important class of resource assignment algorithms. The algorithms are based on linear programming, but are much more specialized for resource assignment, and are therefore much faster than general linear programming at finding an optimal assignment solution. This class of algorithms includes the well-known “Hungarian” algorithm for resource assignment.
The goal is thus to transform the previously described information residing in work items, resources, and associated rules into the mathematically precise formulation of Eqs. 1-3. The first step is to compute the resource assignment cost matrix; the cij values in Eq. 2 above. Such a matrix is depicted, by way of example, in
fitness=f(workitem.service_level, workitem.desired_skills, workitem.required_skills, resource.preferred_skills, resource.secondary_skills, resource.tertiary_skills) Eq. 4
This sort of function may be expressed using a combination of data tables and rules. The rules access the data tables to compute the overall fitness. For example, suppose that the fitness function calculator begins with a work item's desired skills. The calculator iterates over these skills, calling the following function for each skill:
skillmatch(workitem_skill, workitem.service_level, resource)
This function returns a number indicating how well the resource matches the skill. Thus, if the resource does not have the skill at all, this function would return 0. Otherwise, it would return a number based on whether the skill is preferred, secondary, or tertiary in the resource, and on the work item service level. Computation of this number could be based on a table, as shown in
The skillmatch numbers for all desired or required skills are multiplied together to get an overall fitness. Thus, if any are 0, the overall fitness is 0, indicating that the resource does not provide all the skills needed by the work item.
After the overall fitness for each potential resource assignment has been computed, the resource assignment cost matrix (cij values in Eq. 2) is known.
In addition to the fitness ratings, it is useful to represent the notion of work item priority, lateness, customer importance and/or risk in the cost function. This allows the routing algorithm to prioritize important work, and to trigger secondary work flows when appropriate (see previous discussion on safety valves). The key issue here is what to do when there are not enough resources to assign to all the work items. For the benefit of the routing algorithms, it is useful to introduce the concept of a “dummy” resource; an imaginary resource that represents no work for the work item. Assignment of such a resource results in a negative fitness rating; a penalty. The penalty is proportional to the service-level priority of the work item. Thus, the resource assignment cost matrix includes potential resource assignments to dummy resources with associated negative fitness ratings (or positive costs).
This representation can be extended to incorporate secondary workflows by simply adding the secondary work items to the resource assignment cost matrix right at the beginning. An additional constraint must be added that states that real (non-dummy) resources cannot be assigned to both a primary work item and its associated secondary work item. This can be expressed mathematically as shown in Eq. 3.
An important point with this overall formulation is that although it represents the notion of work item lateness using work item priorities and service levels, it does not explicitly predict when work items will get done. Such a prediction capability is possible to implement, but this leads to a general scheduling problem over some finite time horizon. This is much more complex than a resource assignment problem. Thus, the trick is to avoid turning this into a scheduling problem, but to retain the ability to defer work items in an intelligent way.
Those skilled in the art will appreciate that though the illustrated embodiment utilizes the mathematical formulation given in Eqs. 1-3, other embodiments may use alternate mechanisms as well. For example, fitness values returned by eq. 4 may be utilized by local dispatching algorithms that don't necessarily attempt to find a global optimal solution. Such algorithms may use simple heuristics, combined with the fitness values, to make fast, simple decisions that are not necessarily globally optimal, but are adequate for the application.
Routing Algorithms
Simple Algorithms
The fitness function methodology greatly simplifies the work of the routing algorithms. Consider the first queue configuration case where there is a single work item that must be assigned to one of a set of resoures. The fitness of each potential resource assignment is evaluated. The routing algorithm then just picks the resource assignment with the best fitness.
The problem is similar for the case when there is one resource and a set of work items that must be assigned. The decision here is which work item to assign to the resource next. As with the previous case, each potential resource assignment is evaluated, and the best one is chosen.
Multiple Resource Assignment Algorithms
The simple algorithms are simple because they only make one resource assignment at a time. The situation becomes quite a bit more complicated when there are m resources and m work items to be assigned. Now, there is a large combination of possible resource assignments. The first step is, for every work item, evaluate the fitness of every possible resource assignment. This results in an m×n fitness matrix, where m is the number of work items, and n is the number of resources. The next step is to consider various combinations of resource assignments and pick the best one. Theoretically, every such combination of resource assignments must be considered. The overall cost value is then the sum of all the fitness values in the combination, as stated mathematically in Eq. 2.
Note that the problem can easily be extended to handle the case of more work items than resources, or more resources than work items. Also, work items needing more than one resource can be handled by breaking such work items into separate work items, each requiring only one resource.
The exhaustive evaluation of all combinations of resource assignments would be prohibitively expensive for all but the smallest problems. Fortunately, there are good algorithms that achieve the optimal solution but without exhaustive evaluation. One such algorithm that is particularly well suited for this sort of problem is called the “Hungarian” algorithm.
The Hungarian method, as described, for example, in Kuhn, “The Hungarian Method For The Assignment Problem,” Naval Research Logistics Quarterly, 2 (1955), pp. 83-97, is analogous to the simplex method for general linear programming, but is so specialized that there is very little resemblance. The Hungarian method is also much faster for assignment problems than the simplex method. The previously described problem formulation which results in a cost matrix and in Eqs. 1-3 provide a preferred input to the Hungarian method.
Thus, although the formulation does not restrict the type of solution algorithm used, it is suitable as input to an important, well-known class of optimization algorithms that solve assignment problems quickly and efficiently.
Those skilled in the art will appreciate that though the illustrated embodiment utilizes the Hungarian method, other embodiments may use alternate mechanisms as well. For example, a dispatching algorithm that combines heuristics with fitness values may be a viable alternative in many applications.
Depicted below is the equation for the primary-secondary work item constraint which is used in problem formulation. Particularly, for any primary work item j and associated secondary work item k,
Described above are methods and systems that achieve the desired objects. Those skilled in the art will appreciate that the illustrated embodiment is only one example of the invention and that others, incorporating modifications thereto, fall within the scope of the invention. Thus, by way of non-limiting example, it will be appreciated that work items can require any variety of skills or their analogs, in addition to or instead of those described above. Likewise, resources can provide any variety of skills or their analogs. Moreover, it will be appreciated that any variety of stress metrics can be utilized to reflect the stress of the system, in addition to or in place of those described above. In view of these and other modifications, what we claim is:
Number | Name | Date | Kind |
---|---|---|---|
4047059 | Rosenthal | Sep 1977 | A |
4344142 | Diehr, II et al. | Aug 1982 | A |
4602168 | Single | Jul 1986 | A |
4607232 | Gill, Jr. | Aug 1986 | A |
4659944 | Miller, Sr. et al. | Apr 1987 | A |
4701130 | Whitney et al. | Oct 1987 | A |
4866634 | Reboh et al. | Sep 1989 | A |
4884217 | Skeirik et al. | Nov 1989 | A |
4895518 | Arnold et al. | Jan 1990 | A |
4930071 | Tou et al. | May 1990 | A |
4953106 | Gansner et al. | Aug 1990 | A |
5077491 | Heck et al. | Dec 1991 | A |
5093794 | Howie et al. | Mar 1992 | A |
5119465 | Jack et al. | Jun 1992 | A |
5129043 | Yue | Jul 1992 | A |
5136184 | Deevy | Aug 1992 | A |
5136523 | Landers | Aug 1992 | A |
5140671 | Hayes et al. | Aug 1992 | A |
5193056 | Boes | Mar 1993 | A |
5199068 | Cox | Mar 1993 | A |
5204939 | Yamazaki et al. | Apr 1993 | A |
5228116 | Harris et al. | Jul 1993 | A |
5259766 | Sack et al. | Nov 1993 | A |
5262941 | Saladin et al. | Nov 1993 | A |
5267175 | Hooper | Nov 1993 | A |
5267865 | Lee et al. | Dec 1993 | A |
5270920 | Pearse et al. | Dec 1993 | A |
5276359 | Chiang | Jan 1994 | A |
5276885 | Milnes et al. | Jan 1994 | A |
5291394 | Chapman | Mar 1994 | A |
5291583 | Bapat | Mar 1994 | A |
5295256 | Bapat | Mar 1994 | A |
5297279 | Bannon et al. | Mar 1994 | A |
5301270 | Steinberg et al. | Apr 1994 | A |
5310349 | Daniels et al. | May 1994 | A |
5311422 | Loftin et al. | May 1994 | A |
5326270 | Ostby et al. | Jul 1994 | A |
5333254 | Robertson | Jul 1994 | A |
5339390 | Robertson et al. | Aug 1994 | A |
5353229 | Tanaka | Oct 1994 | A |
5374932 | Wyschogrod et al. | Dec 1994 | A |
5379366 | Noyes | Jan 1995 | A |
5379387 | Carlstedt et al. | Jan 1995 | A |
5381332 | Wood | Jan 1995 | A |
5386559 | Eisenberg et al. | Jan 1995 | A |
5395243 | Lubin et al. | Mar 1995 | A |
5412756 | Bauman et al. | May 1995 | A |
5421011 | Camillone et al. | May 1995 | A |
5421730 | Lasker, III et al. | Jun 1995 | A |
5446397 | Yotsuyanagi | Aug 1995 | A |
5446885 | Moore et al. | Aug 1995 | A |
5450480 | Man et al. | Sep 1995 | A |
5463682 | Fisher et al. | Oct 1995 | A |
5473732 | Chang | Dec 1995 | A |
5477170 | Yotsuyanagi | Dec 1995 | A |
5481647 | Brody et al. | Jan 1996 | A |
5499293 | Behram et al. | Mar 1996 | A |
5504879 | Eisenberg et al. | Apr 1996 | A |
5512849 | Wong | Apr 1996 | A |
5519618 | Kastner et al. | May 1996 | A |
5537590 | Amado | Jul 1996 | A |
5542024 | Balint et al. | Jul 1996 | A |
5542078 | Martel et al. | Jul 1996 | A |
5548506 | Srinivasan | Aug 1996 | A |
5561740 | Barrett et al. | Oct 1996 | A |
5579223 | Raman | Nov 1996 | A |
5579486 | Oprescu et al. | Nov 1996 | A |
5596752 | Knudsen et al. | Jan 1997 | A |
5597312 | Bloom et al. | Jan 1997 | A |
5608789 | Fisher et al. | Mar 1997 | A |
5627979 | Chang et al. | May 1997 | A |
5630127 | Moore et al. | May 1997 | A |
5649192 | Stucky | Jul 1997 | A |
5655118 | Heindel et al. | Aug 1997 | A |
5664206 | Murow et al. | Sep 1997 | A |
5678039 | Hinks et al. | Oct 1997 | A |
5715450 | Ambrose et al. | Feb 1998 | A |
5732192 | Malin et al. | Mar 1998 | A |
5754740 | Fukuoka et al. | May 1998 | A |
5761063 | Jannette et al. | Jun 1998 | A |
5761673 | Bookman et al. | Jun 1998 | A |
5765140 | Knudson et al. | Jun 1998 | A |
5768480 | Crawford, Jr. et al. | Jun 1998 | A |
5788504 | Rice et al. | Aug 1998 | A |
5795155 | Morrel-Samuels | Aug 1998 | A |
5809212 | Shasha | Sep 1998 | A |
5815415 | Bentley et al. | Sep 1998 | A |
5819257 | Monge et al. | Oct 1998 | A |
5822780 | Schutzman | Oct 1998 | A |
5825260 | Ludwig et al. | Oct 1998 | A |
5826077 | Blakeley et al. | Oct 1998 | A |
5826239 | Du et al. | Oct 1998 | A |
5826250 | Trefler | Oct 1998 | A |
5826252 | Wolters, Jr. et al. | Oct 1998 | A |
5829983 | Koyama et al. | Nov 1998 | A |
5832483 | Barker | Nov 1998 | A |
5841673 | Kobayashi et al. | Nov 1998 | A |
5873096 | Lim et al. | Feb 1999 | A |
5875334 | Chow et al. | Feb 1999 | A |
5875441 | Nakatsuyama et al. | Feb 1999 | A |
5880614 | Zinke et al. | Mar 1999 | A |
5880742 | Rao et al. | Mar 1999 | A |
5886546 | Hwang | Mar 1999 | A |
5890146 | Wavish et al. | Mar 1999 | A |
5890166 | Eisenberg et al. | Mar 1999 | A |
5907490 | Oliver | May 1999 | A |
5907837 | Ferrel et al. | May 1999 | A |
5910748 | Reffay et al. | Jun 1999 | A |
5918222 | Fukui et al. | Jun 1999 | A |
5920717 | Noda | Jul 1999 | A |
5930795 | Chen et al. | Jul 1999 | A |
5945852 | Kosiec | Aug 1999 | A |
5974441 | Rogers et al. | Oct 1999 | A |
5974443 | Jeske | Oct 1999 | A |
5978566 | Plank et al. | Nov 1999 | A |
5983267 | Shklar et al. | Nov 1999 | A |
5987415 | Breese et al. | Nov 1999 | A |
5990742 | Suzuki | Nov 1999 | A |
5995948 | Whitford et al. | Nov 1999 | A |
5995958 | Xu | Nov 1999 | A |
6008673 | Glass et al. | Dec 1999 | A |
6012098 | Bayeh et al. | Jan 2000 | A |
6020768 | Lim | Feb 2000 | A |
6023704 | Gerard et al. | Feb 2000 | A |
6023714 | Hill et al. | Feb 2000 | A |
6023717 | Argyroudis | Feb 2000 | A |
6028457 | Tihanyi | Feb 2000 | A |
6037890 | Glass et al. | Mar 2000 | A |
6044373 | Gladney et al. | Mar 2000 | A |
6044466 | Anand et al. | Mar 2000 | A |
6078982 | Du et al. | Jun 2000 | A |
6085188 | Bachmann et al. | Jul 2000 | A |
6085198 | Skinner et al. | Jul 2000 | A |
6091226 | Amano | Jul 2000 | A |
6092036 | Hamann | Jul 2000 | A |
6092083 | Brodersen et al. | Jul 2000 | A |
6094652 | Faisal | Jul 2000 | A |
6105035 | Monge et al. | Aug 2000 | A |
6122632 | Botts et al. | Sep 2000 | A |
6125363 | Buzzeo et al. | Sep 2000 | A |
6130679 | Chen et al. | Oct 2000 | A |
6137797 | Bass et al. | Oct 2000 | A |
6144997 | Lamming et al. | Nov 2000 | A |
6151595 | Pirolli et al. | Nov 2000 | A |
6151624 | Teare et al. | Nov 2000 | A |
6154738 | Call | Nov 2000 | A |
6167441 | Himmel | Dec 2000 | A |
6177932 | Galdes et al. | Jan 2001 | B1 |
6185516 | Hardin et al. | Feb 2001 | B1 |
6185534 | Breese et al. | Feb 2001 | B1 |
6192371 | Schultz | Feb 2001 | B1 |
6194919 | Park | Feb 2001 | B1 |
6212502 | Ball et al. | Apr 2001 | B1 |
6216135 | Brodersen et al. | Apr 2001 | B1 |
6233617 | Rothwein et al. | May 2001 | B1 |
6240417 | Eastwick et al. | May 2001 | B1 |
6243713 | Nelson et al. | Jun 2001 | B1 |
6246320 | Monroe | Jun 2001 | B1 |
6275073 | Tokuhiro | Aug 2001 | B1 |
6275790 | Yamamoto et al. | Aug 2001 | B1 |
6300947 | Kanevsky | Oct 2001 | B1 |
6308163 | Du et al. | Oct 2001 | B1 |
6314415 | Mukherjee | Nov 2001 | B1 |
6324693 | Brodersen et al. | Nov 2001 | B1 |
6330554 | Altschuler et al. | Dec 2001 | B1 |
6338074 | Poindexter et al. | Jan 2002 | B1 |
6341277 | Coden et al. | Jan 2002 | B1 |
6341293 | Hennessey | Jan 2002 | B1 |
6349238 | Gabbita et al. | Feb 2002 | B1 |
6351734 | Lautzenheiser et al. | Feb 2002 | B1 |
6359633 | Balasubramaniam et al. | Mar 2002 | B1 |
6369819 | Pitkow et al. | Apr 2002 | B1 |
6380910 | Moustakas et al. | Apr 2002 | B1 |
6381738 | Choi et al. | Apr 2002 | B1 |
6389460 | Stewart et al. | May 2002 | B1 |
6393605 | Loomans | May 2002 | B1 |
6396885 | Ding et al. | May 2002 | B1 |
6405211 | Sokol et al. | Jun 2002 | B1 |
6405251 | Bullard et al. | Jun 2002 | B1 |
6415259 | Wolfinger et al. | Jul 2002 | B1 |
6415283 | Conklin | Jul 2002 | B1 |
6418448 | Sarkar | Jul 2002 | B1 |
6426723 | Smith et al. | Jul 2002 | B1 |
6429870 | Chen et al. | Aug 2002 | B1 |
6437799 | Shinomi et al. | Aug 2002 | B1 |
6446089 | Brodersen et al. | Sep 2002 | B1 |
6446200 | Ball et al. | Sep 2002 | B1 |
6446256 | Hyman et al. | Sep 2002 | B1 |
6448964 | Isaacs et al. | Sep 2002 | B1 |
6463440 | Hind et al. | Oct 2002 | B1 |
6473467 | Wallace et al. | Oct 2002 | B1 |
6473748 | Archer | Oct 2002 | B1 |
6493331 | Walton et al. | Dec 2002 | B1 |
6493399 | Xia et al. | Dec 2002 | B1 |
6493754 | Rosborough et al. | Dec 2002 | B1 |
6496812 | Campaigne et al. | Dec 2002 | B1 |
6496833 | Goldberg et al. | Dec 2002 | B1 |
6502239 | Zgarba et al. | Dec 2002 | B2 |
6509898 | Chi et al. | Jan 2003 | B2 |
6513018 | Culhane | Jan 2003 | B1 |
6526440 | Bharat | Feb 2003 | B1 |
6526457 | Birze | Feb 2003 | B1 |
6529899 | Kraft et al. | Mar 2003 | B1 |
6530079 | Choi et al. | Mar 2003 | B1 |
6539374 | Jung | Mar 2003 | B2 |
6542912 | Meltzer et al. | Apr 2003 | B2 |
6546406 | DeRose et al. | Apr 2003 | B1 |
6549904 | Ortega et al. | Apr 2003 | B1 |
6556983 | Altschuler et al. | Apr 2003 | B1 |
6556985 | Karch | Apr 2003 | B1 |
6560592 | Reid et al. | May 2003 | B1 |
6567419 | Yarlagadda | May 2003 | B1 |
6571222 | Matsumoto et al. | May 2003 | B1 |
6577769 | Kenyon et al. | Jun 2003 | B1 |
6583800 | Ridgley et al. | Jun 2003 | B1 |
6584464 | Warthen | Jun 2003 | B1 |
6584569 | Reshef et al. | Jun 2003 | B2 |
6594662 | Sieffert et al. | Jul 2003 | B1 |
6597775 | Lawyer et al. | Jul 2003 | B2 |
6598043 | Baclawski | Jul 2003 | B1 |
6606613 | Altschuler et al. | Aug 2003 | B1 |
6625657 | Bullard | Sep 2003 | B1 |
6629138 | Lambert et al. | Sep 2003 | B1 |
6636850 | Lepien | Oct 2003 | B2 |
6636901 | Sudhakaran et al. | Oct 2003 | B2 |
6643638 | Xu | Nov 2003 | B1 |
6643652 | Helgeson et al. | Nov 2003 | B2 |
6661908 | Suchard et al. | Dec 2003 | B1 |
6678679 | Bradford | Jan 2004 | B1 |
6678773 | Marietta et al. | Jan 2004 | B2 |
6678882 | Hurley et al. | Jan 2004 | B1 |
6684261 | Orton et al. | Jan 2004 | B1 |
6691230 | Bardon | Feb 2004 | B1 |
6701314 | Conover et al. | Mar 2004 | B1 |
6711565 | Subramaniam et al. | Mar 2004 | B1 |
6721747 | Lipkin | Apr 2004 | B2 |
6728702 | Subramaniam et al. | Apr 2004 | B1 |
6728852 | Stoutamire | Apr 2004 | B1 |
6732095 | Warshavsky et al. | May 2004 | B1 |
6732111 | Brodersen et al. | May 2004 | B2 |
6748422 | Morin et al. | Jun 2004 | B2 |
6750858 | Rosenstein | Jun 2004 | B1 |
6751663 | Farrell et al. | Jun 2004 | B1 |
6754475 | Harrison et al. | Jun 2004 | B1 |
6756994 | Tlaskal et al. | Jun 2004 | B1 |
6763351 | Subramaniam et al. | Jul 2004 | B1 |
6771706 | Ling et al. | Aug 2004 | B2 |
6772148 | Baclawski | Aug 2004 | B2 |
6772350 | Belani et al. | Aug 2004 | B1 |
6778971 | Altschuler et al. | Aug 2004 | B1 |
6782091 | Dunning, III | Aug 2004 | B1 |
6785341 | Walton et al. | Aug 2004 | B2 |
6788114 | Krenzke et al. | Sep 2004 | B1 |
6792420 | Chen et al. | Sep 2004 | B2 |
RE38633 | Srinivasan | Oct 2004 | E |
6804330 | Jones et al. | Oct 2004 | B1 |
6820082 | Cook et al. | Nov 2004 | B1 |
6829655 | Huang et al. | Dec 2004 | B1 |
6831688 | Cras et al. | Dec 2004 | B2 |
6839682 | Blume et al. | Jan 2005 | B1 |
6847982 | Parker et al. | Jan 2005 | B2 |
6851089 | Erickson et al. | Feb 2005 | B1 |
6856575 | Jones | Feb 2005 | B2 |
6856992 | Britton et al. | Feb 2005 | B2 |
6859787 | Fisher et al. | Feb 2005 | B2 |
6865546 | Song | Mar 2005 | B1 |
6865575 | Smith et al. | Mar 2005 | B1 |
6867789 | Allen et al. | Mar 2005 | B1 |
6918222 | Lat et al. | Jul 2005 | B2 |
6920615 | Campbell et al. | Jul 2005 | B1 |
6925457 | Britton et al. | Aug 2005 | B2 |
6927728 | Vook et al. | Aug 2005 | B2 |
6934702 | Faybishenko et al. | Aug 2005 | B2 |
6940917 | Menon et al. | Sep 2005 | B2 |
6944644 | Gideon | Sep 2005 | B2 |
6954737 | Kalantar et al. | Oct 2005 | B2 |
6956845 | Baker et al. | Oct 2005 | B2 |
6959432 | Crocker et al. | Oct 2005 | B2 |
6961725 | Yuan et al. | Nov 2005 | B2 |
6965889 | Serrano-Morales et al. | Nov 2005 | B2 |
6976144 | Trefler et al. | Dec 2005 | B1 |
6985912 | Mullins et al. | Jan 2006 | B2 |
7020869 | Abrari et al. | Mar 2006 | B2 |
7028225 | Maso et al. | Apr 2006 | B2 |
7031901 | Abu El Ata | Apr 2006 | B2 |
7058367 | Luo et al. | Jun 2006 | B1 |
7058637 | Britton et al. | Jun 2006 | B2 |
7076558 | Dunn | Jul 2006 | B1 |
7089193 | Newbold | Aug 2006 | B2 |
7103173 | Rodenbusch et al. | Sep 2006 | B2 |
7124145 | Surasinghe | Oct 2006 | B2 |
7139999 | Bowman-Amuah | Nov 2006 | B2 |
7143116 | Okitsu et al. | Nov 2006 | B2 |
7171145 | Takeuchi et al. | Jan 2007 | B2 |
7171415 | Kan et al. | Jan 2007 | B2 |
7174514 | Subramaniam et al. | Feb 2007 | B2 |
7289793 | Norwood et al. | Oct 2007 | B2 |
RE39918 | Slemmer | Nov 2007 | E |
7302417 | Iyer | Nov 2007 | B2 |
7318020 | Kim | Jan 2008 | B1 |
7318066 | Kaufman et al. | Jan 2008 | B2 |
7334039 | Majkut et al. | Feb 2008 | B1 |
7406475 | Dorne et al. | Jul 2008 | B2 |
7412388 | Dalal et al. | Aug 2008 | B2 |
7505827 | Boddy et al. | Mar 2009 | B1 |
7536294 | Stanz et al. | May 2009 | B1 |
7555645 | Vissapragada | Jun 2009 | B2 |
7574494 | Mayernick et al. | Aug 2009 | B1 |
7596504 | Hughes et al. | Sep 2009 | B2 |
7640222 | Trefler | Dec 2009 | B2 |
7665063 | Hofmann et al. | Feb 2010 | B1 |
7711919 | Trefler et al. | May 2010 | B2 |
7983895 | McEntee et al. | Jul 2011 | B2 |
8037329 | Leech et al. | Oct 2011 | B2 |
8073802 | Trefler | Dec 2011 | B2 |
8250525 | Khatutsky | Aug 2012 | B2 |
20010013799 | Wang | Aug 2001 | A1 |
20010035777 | Wang et al. | Nov 2001 | A1 |
20010047355 | Anwar | Nov 2001 | A1 |
20010049682 | Vincent et al. | Dec 2001 | A1 |
20010052108 | Bowman-Amuah | Dec 2001 | A1 |
20020010855 | Reshef et al. | Jan 2002 | A1 |
20020013804 | Gideon | Jan 2002 | A1 |
20020029161 | Brodersen et al. | Mar 2002 | A1 |
20020042831 | Capone et al. | Apr 2002 | A1 |
20020049603 | Mehra et al. | Apr 2002 | A1 |
20020049715 | Serrano-Morales et al. | Apr 2002 | A1 |
20020049788 | Lipkin et al. | Apr 2002 | A1 |
20020054152 | Palaniappan et al. | May 2002 | A1 |
20020059566 | Delcambre et al. | May 2002 | A1 |
20020091677 | Sridhar | Jul 2002 | A1 |
20020091678 | Miller et al. | Jul 2002 | A1 |
20020091710 | Dunham et al. | Jul 2002 | A1 |
20020091835 | Lentini et al. | Jul 2002 | A1 |
20020107684 | Gao | Aug 2002 | A1 |
20020118688 | Jagannathan | Aug 2002 | A1 |
20020120598 | Shadmon et al. | Aug 2002 | A1 |
20020120762 | Cheng et al. | Aug 2002 | A1 |
20020133502 | Rosenthal et al. | Sep 2002 | A1 |
20020177232 | Melker et al. | Nov 2002 | A1 |
20020178232 | Ferguson | Nov 2002 | A1 |
20020184610 | Chong et al. | Dec 2002 | A1 |
20030004934 | Qian | Jan 2003 | A1 |
20030004951 | Chokshi | Jan 2003 | A1 |
20030009239 | Lombardo et al. | Jan 2003 | A1 |
20030014399 | Hansen et al. | Jan 2003 | A1 |
20030037145 | Fagan | Feb 2003 | A1 |
20030050834 | Caplan | Mar 2003 | A1 |
20030050927 | Hussam | Mar 2003 | A1 |
20030050929 | Bookman et al. | Mar 2003 | A1 |
20030061209 | Raboczi et al. | Mar 2003 | A1 |
20030065544 | Elzinga et al. | Apr 2003 | A1 |
20030066031 | Laane | Apr 2003 | A1 |
20030074352 | Raboczi et al. | Apr 2003 | A1 |
20030074369 | Schuetze et al. | Apr 2003 | A1 |
20030084401 | Abel et al. | May 2003 | A1 |
20030109951 | Hsiung et al. | Jun 2003 | A1 |
20030135358 | Lissauer et al. | Jul 2003 | A1 |
20030191626 | Al-Onaizan et al. | Oct 2003 | A1 |
20030200254 | Wei | Oct 2003 | A1 |
20030200371 | Abujbara | Oct 2003 | A1 |
20030202617 | Casper | Oct 2003 | A1 |
20030222680 | Jaussi | Dec 2003 | A1 |
20030229529 | Mui et al. | Dec 2003 | A1 |
20030229544 | Veres et al. | Dec 2003 | A1 |
20040024603 | Mahoney et al. | Feb 2004 | A1 |
20040034651 | Gupta et al. | Feb 2004 | A1 |
20040049509 | Keller et al. | Mar 2004 | A1 |
20040054610 | Amstutz et al. | Mar 2004 | A1 |
20040088199 | Childress et al. | May 2004 | A1 |
20040103014 | Teegan et al. | May 2004 | A1 |
20040117759 | Rippert et al. | Jun 2004 | A1 |
20040122652 | Andrews et al. | Jun 2004 | A1 |
20040133416 | Fukuoka et al. | Jul 2004 | A1 |
20040133876 | Sproule | Jul 2004 | A1 |
20040162822 | Papanyan et al. | Aug 2004 | A1 |
20040167765 | Abu El Ata | Aug 2004 | A1 |
20040205672 | Bates et al. | Oct 2004 | A1 |
20040220792 | Gallanis et al. | Nov 2004 | A1 |
20040236566 | Simske | Nov 2004 | A1 |
20040268221 | Wang | Dec 2004 | A1 |
20040268299 | Lei et al. | Dec 2004 | A1 |
20050027563 | Fackler et al. | Feb 2005 | A1 |
20050039191 | Hewson et al. | Feb 2005 | A1 |
20050044198 | Okitsu et al. | Feb 2005 | A1 |
20050050000 | Kwok et al. | Mar 2005 | A1 |
20050055330 | Britton et al. | Mar 2005 | A1 |
20050059566 | Brown et al. | Mar 2005 | A1 |
20050060372 | DeBettencourt et al. | Mar 2005 | A1 |
20050104628 | Tanzawa et al. | May 2005 | A1 |
20050125683 | Matsuyama et al. | Jun 2005 | A1 |
20050165823 | Ondrusek et al. | Jul 2005 | A1 |
20050216235 | Butt et al. | Sep 2005 | A1 |
20050234882 | Bennett et al. | Oct 2005 | A1 |
20050288920 | Green et al. | Dec 2005 | A1 |
20060020783 | Fisher | Jan 2006 | A1 |
20060041861 | Trefler et al. | Feb 2006 | A1 |
20060063138 | Loff et al. | Mar 2006 | A1 |
20060064486 | Baron et al. | Mar 2006 | A1 |
20060080082 | Ravindra et al. | Apr 2006 | A1 |
20060100847 | McEntee et al. | May 2006 | A1 |
20060139312 | Sinclair et al. | Jun 2006 | A1 |
20060173724 | Trefler et al. | Aug 2006 | A1 |
20060173871 | Taniguchi et al. | Aug 2006 | A1 |
20060206303 | Kohlmeier et al. | Sep 2006 | A1 |
20060206305 | Kimura et al. | Sep 2006 | A1 |
20060218166 | Myers et al. | Sep 2006 | A1 |
20060271920 | Abouelsaadat | Nov 2006 | A1 |
20070028225 | Whittaker et al. | Feb 2007 | A1 |
20070038765 | Dunn | Feb 2007 | A1 |
20070055938 | Herring et al. | Mar 2007 | A1 |
20070094199 | Deshpande et al. | Apr 2007 | A1 |
20070130130 | Chan et al. | Jun 2007 | A1 |
20070203756 | Sears et al. | Aug 2007 | A1 |
20070208553 | Hastings et al. | Sep 2007 | A1 |
20070233902 | Trefler et al. | Oct 2007 | A1 |
20070239646 | Trefler | Oct 2007 | A1 |
20070294644 | Yost | Dec 2007 | A1 |
20080046462 | Kaufman et al. | Feb 2008 | A1 |
20080077384 | Agapi et al. | Mar 2008 | A1 |
20080085502 | Allen et al. | Apr 2008 | A1 |
20080184230 | Leech et al. | Jul 2008 | A1 |
20080208785 | Trefler et al. | Aug 2008 | A1 |
20080216055 | Khatutsky | Sep 2008 | A1 |
20090132232 | Trefler | May 2009 | A1 |
20100088266 | Trefler | Apr 2010 | A1 |
20100107137 | Trefler et al. | Apr 2010 | A1 |
Number | Date | Country |
---|---|---|
19911098 | Dec 1999 | DE |
0669717 | Aug 1995 | EP |
996916 | May 2000 | EP |
1015997 | Jul 2000 | EP |
1019807 | Jul 2000 | EP |
1073955 | Feb 2001 | EP |
1073992 | Feb 2001 | EP |
1135723 | Sep 2001 | EP |
1163604 | Dec 2001 | EP |
1183636 | Mar 2002 | EP |
1196882 | Apr 2002 | EP |
1203310 | May 2002 | EP |
1208482 | May 2002 | EP |
1212668 | Jun 2002 | EP |
1240592 | Sep 2002 | EP |
1277102 | Jan 2003 | EP |
1277119 | Jan 2003 | EP |
1277120 | Jan 2003 | EP |
1277153 | Jan 2003 | EP |
1277155 | Jan 2003 | EP |
1277329 | Jan 2003 | EP |
1374083 | Jan 2004 | EP |
1382030 | Jan 2004 | EP |
1386241 | Feb 2004 | EP |
1393172 | Mar 2004 | EP |
1393188 | Mar 2004 | EP |
1402336 | Mar 2004 | EP |
1407384 | Apr 2004 | EP |
1 430 396 | Jun 2004 | EP |
1438649 | Jul 2004 | EP |
1438654 | Jul 2004 | EP |
1438672 | Jul 2004 | EP |
1483685 | Dec 2004 | EP |
1490747 | Dec 2004 | EP |
1490809 | Dec 2004 | EP |
1492232 | Dec 2004 | EP |
1782183 | May 2007 | EP |
1830312 | Sep 2007 | EP |
1840803 | Oct 2007 | EP |
2115581 | Nov 2009 | EP |
WO-9838564 | Sep 1998 | WO |
WO-9840807 | Sep 1998 | WO |
WO-9905632 | Feb 1999 | WO |
WO-9945465 | Sep 1999 | WO |
WO-9950784 | Oct 1999 | WO |
WO-0033187 | Jun 2000 | WO |
WO-0033217 | Jun 2000 | WO |
WO-0033226 | Jun 2000 | WO |
WO-0033235 | Jun 2000 | WO |
WO-0033238 | Jun 2000 | WO |
WO-0052553 | Sep 2000 | WO |
WO-0052603 | Sep 2000 | WO |
WO-0140958 | Jun 2001 | WO |
WO-0175610 | Oct 2001 | WO |
WO-0175614 | Oct 2001 | WO |
WO-0175747 | Oct 2001 | WO |
WO-0175748 | Oct 2001 | WO |
WO-0176206 | Oct 2001 | WO |
WO-0177787 | Oct 2001 | WO |
WO-0179994 | Oct 2001 | WO |
WO-0221254 | Mar 2002 | WO |
WO-0244947 | Jun 2002 | WO |
02056249 | Jul 2002 | WO |
WO-02080006 | Oct 2002 | WO |
WO-02080015 | Oct 2002 | WO |
WO-02082300 | Oct 2002 | WO |
WO-02084925 | Oct 2002 | WO |
WO-02088869 | Nov 2002 | WO |
WO-02091346 | Nov 2002 | WO |
WO-02101517 | Dec 2002 | WO |
WO-02103576 | Dec 2002 | WO |
WO-03021393 | Mar 2003 | WO |
WO-03029923 | Apr 2003 | WO |
WO-03029955 | Apr 2003 | WO |
WO-03030005 | Apr 2003 | WO |
WO-03030013 | Apr 2003 | WO |
WO-03030014 | Apr 2003 | WO |
WO-03058504 | Jul 2003 | WO |
WO-03069500 | Aug 2003 | WO |
WO-03071380 | Aug 2003 | WO |
WO-03071388 | Aug 2003 | WO |
WO-03073319 | Sep 2003 | WO |
WO-03077139 | Sep 2003 | WO |
WO-03085503 | Oct 2003 | WO |
WO-03085580 | Oct 2003 | WO |
WO-2004001613 | Dec 2003 | WO |
WO-2004003684 | Jan 2004 | WO |
WO-2004003766 | Jan 2004 | WO |
WO-2004003885 | Jan 2004 | WO |
WO-2004046882 | Jun 2004 | WO |
WO-2004061815 | Jul 2004 | WO |
WO-2004086197 | Oct 2004 | WO |
WO-2004086198 | Oct 2004 | WO |
WO-2004095207 | Nov 2004 | WO |
WO-2004095208 | Nov 2004 | WO |
WO-2004114147 | Dec 2004 | WO |
WO-2005001627 | Jan 2005 | WO |
WO-2005003888 | Jan 2005 | WO |
WO-2005010645 | Feb 2005 | WO |
WO-2005117549 | Dec 2005 | WO |
2006081536 | Aug 2006 | WO |
2008109441 | Sep 2008 | WO |
2009097384 | Aug 2009 | WO |
Number | Date | Country | |
---|---|---|---|
20060173724 A1 | Aug 2006 | US |