Method and system for concurrent error identification in resource scheduling

Information

  • Patent Grant
  • 7752508
  • Patent Number
    7,752,508
  • Date Filed
    Monday, October 8, 2007
    17 years ago
  • Date Issued
    Tuesday, July 6, 2010
    14 years ago
Abstract
A method and system for handling real-time indications of resource scheduling conflicts. In one embodiment, the method includes a computer system including a user interface, display, processor, and some form of memory. Contained within the memory is a resource scheduling process that analyzes resource data, scheduling criteria, and work parameters to create a working schedule. In conjunction with the creation of a working schedule, the scheduling process detects resource conflicts that can inhibit the schedule's functionality. Once detected an identification process conveys the error to the user concurrently with the schedule process to provide the user with a real-time indication of resource conflicts. The indication is presented in an unobtrusive manner so as to not interfere or impede the scheduling process. In addition, should the specific resource causing the conflict be identifiable, the indication process conveys that information in a similar real-time methodology.
Description
FIELD OF THE INVENTION

The invention is in the field of real-time error handling. More particularly, this invention relates to the real-time handling of resource scheduling conflicts and resolution of these conflicts in a complex scheduling environment.


BACKGROUND OF THE INVENTION

Resource scheduling is a complex task that requires satisfaction of several potentially conflicting goals and constraints. In a complex environment a resource scheduling algorithm may reach its conclusion with several unfulfilled goals and exceptions. These unfulfilled goals frustrate the intended result of a working resource schedule. One such complex environment of resource scheduling is call center forecasting and agent scheduling. In this complex an diverse setting, a significant amount of configuration and parameter specifications must be done via user interfaces before a final result can be produced. Existing applications for resource scheduling do not adequately produce an unobtrusive interactive mechanism for warning the user of parameter or configuration selections that are likely to result in poor performance or failure of the schedule.


Current algorithms produce warnings or an indication of a conflict that interrupt the scheduling process. Present systems, known to one skilled in the art, use modal interfaces to detect and inform the user of errors. Errors that are detected in mid-stream of the user's work forcibly interrupt the user with a warning message. This warning message prevents the user from continuing work without at least acknowledging its presence. These warning mechanisms are rigid in their application and, if disabled, are completely ineffective at providing any type of failure notification. For example, this warning process is accomplished through a series of programmed communications between the error detection program and the primary scheduling program that results in the scheduling operations ceasing.


The prior art fails to provide an unobtrusive or concurrent means to notify a user of a resource scheduling conflict. By forcing the user to interact with a warning or notification of a pending error, the efficiency of the scheduling process suffers. If the user elects to dismiss the warning, no further indication is present to convey to the user that the conflict is still present. Furthermore, should a user elect to correct the conflict upon receiving notification, the user is required to navigate independently in the program to the position in the program that contains the cause of the conflict, which is both inefficient and costly.


SUMMARY OF THE DISCLOSURE

A method and system for handling real-time identification and notification of resource scheduling conflicts is described. In one embodiment, the claimed method works concurrently with a resource scheduling process to indicate to the user in an unobtrusive manner that a resource conflict has occurred. The user, upon selecting the indication of an error, is provided with a description of the conflict and the option of suppressing or resolving the resource conflict. In another embodiment the indication is represented by a visual depiction of a stoplight located at the lower right corner of the display. The colors red and yellow are used to depict unsuppressed and suppressed conflicts respectively. One skilled in the art will recognize that the identification and notification of the conflict may bee through any number of media including but not limited to visual, aural, or tactile means.


If the user elects to resolve the resource conflict, one embodiment provides a hyperlink utilizing ordinary Hypertext Markup Language (“HTML”) to link the user to the corresponding portion of the scheduling process where the conflict exists. Furthermore, should the user elect to use the hyperlink to access the appropriate page, the entry that is creating the conflict is highlighted for ease of identification. Once the conflict has been resolved, the real-time indication, in this embodiment the stoplight, will revert to a green light indicating that no resource conflicts exists. Conversely if the user elects to suppress the conflict the red light will change to yellow and remain illuminated until the suppressed conflict is resolved. Should a new conflict arise, both the red light and the yellow light will illuminate indicating that suppressed as well as unsuppressed resource conflicts exist. Throughout these indications of conflicts the functionality of the scheduling process remains unaffected and the user is unimpeded should he or she decide to ignore the conflict indication.





BRIEF DESCRIPTION OF THE DRAWINGS


FIG. 1 is a block diagram of an embodiment of a network system for real-time resource scheduling error identification.



FIG. 2 is a depiction of an embodiment for real-time resource scheduling error identification showing a conflict situation.



FIG. 3 is a depiction of an embodiment for real-time resource scheduling error identification showing a situation with no resource conflicts.



FIG. 4 is a depiction of an embodiment for real-time resource scheduling error identification showing a conflict description and resolution window.



FIG. 5 is a depiction of an embodiment for real-time resource scheduling error identification associated with specific resources.



FIG. 6 is a depiction of an embodiment for real-time resource scheduling error identification illustrating a typical list of rule based conflicts associated with a specific resource.



FIG. 7 is a depiction of an embodiment for real-time resource scheduling error identification showing a calendar based conflict associated with a specific resource.



FIG. 8 is a depiction of an embodiment for real-time resource scheduling error identification showing a resolution window associated with a calendar conflict of a specific resource.



FIG. 9 is a flow diagram of concurrent real-time error identification according to an embodiment.





DETAILED DESCRIPTION

A system and method for real-time handling of error identification and notification in complex environments, such as call centers, are described. In the description that follows, numerous specific details are set forth in order to provide a thorough understanding of the present invention. It will be evident, however, to one skilled in the art that the method and system presented may be practiced without these specific details.



FIG. 1 is an embodiment of a system, 100, for providing a real-time identification and notification of resource scheduling conflicts. The system includes multiple client computers, 102-105, which are coupled to the server, 106, through a network, 108. The network, 108, can be any network, such as a local area network, a wide area network, or the Internet. The client computers each include one or more processors and one or more storage devices. Each of the client computers also includes a display device, and one or more storage devices. All of the storage devices store various data and software programs. In one embodiment, the method for providing a real-time indication of resource conflicts in a resource scheduling process is carried out on the system, 100, by software instructions executing on one or more of the client computers, 102-105. The software instructions may be stored on the server, 106, or on any of the client computers. For example, one embodiment presents a hosted application used by a call center of an enterprise that requires complex scheduling of many employees. The software instructions are stored on the server and accessed through the network by a client computer operator of the enterprise. In other embodiments, the software instructions may be stored and executed on the client computer. A user of the client computer with the help of a user interface can enter data required for the execution of the software instructions. Data required for the execution of the software instructions can also be accessed via the network and can be stored anywhere on the network.


One embodiment of a method for providing a real-time identification of resource conflicts during a scheduling process can be used in the call center environment. A call center is an organization that answers and responds to telephone calls from customers for one or more particular organizations. Call centers also respond to other customer contacts, such as e-mail, faxes, voice over Internet protocol, and web chat. Such centers possess a plurality of resources. A resource can be the equipment, the employees, the facilities, or any other asset that facilitates the business in achieving its purpose. In a call center the individual employees answering the calls are agents and each possesses a particular skill set. Each employee is therefore an example of a resource with specialized skills. For example one agent may be able to respond to technical problems, another may specialize in billing questions, and still another may specialize in taking product orders. Each agent likely possesses multiple skill sets and a call center manager's challenge is to optimize the agents' schedules so as to maximize the utilization of these skill sets without compromising the functionality of the center, thus minimizing cost.


As the call center schedule is developed, minor modifications in an employee's availability schedule or the call center's resource requirements can require the entire schedule to be regenerated. Numerous working parameters and employee criteria are established to ensure the profitability and efficiency of day to day operations. Considerations such as the maximum number of hours worked per pay period per employee, the maximum period of work without a break, or the necessity for at least two experienced call agents to be on call at any one time are examples of such criteria and parameters. In one embodiment of the present method, as a scheduler inputs changes into a working schedule, a real-time indication is presented to the user if the alteration in the schedule affects a parameter or criteria adversely and will impair the overall functionality of the schedule.


Real-time indications are a result of the scheduling program constantly recalculating the viability of the proposed data into a working schedule. As new data is input the entire schedule is reconfigured and checked for conflicts without any interface or input by the user other than the original entry of the data. The feedback to the user of any conflicts is immediate. For example, an alteration of an agent's ability to maintain a work shift may have dramatic overall affects. Since the agent possesses a certain skill set and the call center must be maintained with a minimum level of skilled individuals, the deletion of the agent's skills from the working schedule may result in the center being understaffed for a particular period. In such a situation, the real-time error identification system would present, in one embodiment, a red light depicted as, but not limited to, a stoplight at the bottom of the display to notify the user of the conflict.


The indication would occur as soon as the user altered the employee's schedule. Since the indication of the error is unobtrusive, meaning that the display of the conflict or scheduling problem would not interfere with the normal operation of the scheduling program, the user can continue to alter the schedule as he or she fees fit. Thus, if in this example the user was aware that the alteration of the agent's work schedule would present a problem but has already envisioned a resolution of the conflict, the user need not waste time by having to interact with warning system needlessly. Upon seeing the indication of a conflict, the user could input the potential solution and see if the red light is removed indicating the conflict has been resolved thus validating the envisioned solution.


Likewise, in another embodiment, a user can first become aware of a conflict through the real-time identification system. In this situation, if a user alters the schedule, the concurrent identification will unobtrusively notify him or her that a problem exists. The system described in this embodiment does not require the entire form or schedule to be completed before an error is detected. The user in this embodiment can select the identification symbol, the red light in this case, and be presented with a new window containing a description of the conflict as well as a proposed solution. The user can then elect to suppress or ignore the conflict resulting in the illumination of a yellow light in the stoplight depiction or select a hyperlink located within the description that will open the primary scheduling process window centered on the functional area containing the conflict. The window containing the conflict will further have the entry causing the problem highlighted for easy recognition. With the conflict resolved, the new window can be closed and the original scheduling process continued without the presence of an error indication.


If the user elects to suppress the conflict, the yellow light indication will remain illuminated until the conflict is resolved. The suppression of the conflict does not impede the real-time identification of other conflicts. If an additional conflict is identified, a new red light indication is displayed in conjunction with the yellow light indicating a new conflict as well as the multiple warnings or conflicts that are suppressed. Selection of the conflict identification will, in this embodiment, present not only descriptions and potential solutions of the current conflict but of the suppressed conflicts as well. Further, if multiple conflicts exist that are not suppressed, selecting the red light will list all of the conflicts for the user's review. The resolution of the resource conflict removes the scheduling error and cancels any indication present. This can be accomplished by following advice given in the resolution window or by disregarding the potential solution and inputting a different change that will alleviate the conflict.


An additional embodiment provides the user with a means to associate a conflict with a particular resource and provides a real-time indication of that association to the user. As with the previous embodiments, the identification and handling of resource conflicts occurs concurrently with the primary scheduling process. Once a conflict occurs, an indication of the conflict is presented to the user in such a manner as to not interfere with his or her use of the application. In addition to the real-time communication of a problem, this embodiment provides a method wherein the specific resource associated with or causing the conflict is readily identified to the user.


In one embodiment, a visual indication or symbol is placed next to the resource that is associated with a conflict. Furthermore, this method of identification can differentiate the type of conflicts associated with each resource. If, for example, the conflict is rule based such as exceeding the maximum number of hours worked per week, this embodiment conveys this information to user without interrupting the scheduling process by placing a symbol next to the resource. Likewise if a conflict is due to a scheduled meeting or similar calendar event, the method can similarly communicate such information to the user without disrupting the normal operation of the scheduling process. In one embodiment the method places a visual symbol next to the conflicted resource and alters the color of the exclamation mark based on the type of conflict. Likewise, the indication could be aural or any other similar medium to communicate the identification of a conflict to the user. If, in this embodiment, the exclamation mark is blue the conflict associated with that employee rises from a rule problem whereas if the exclamation mark is red the problem is based in a conflict with a meeting or other calendar events. These and other depictions are described in the following diagrams.



FIG. 2 is a depiction of a Recorded Call Volumes page, 220, of an embodiment for real-time identification and notification of resource conflicts. In this embodiment the depiction of a stoplight, 210, presents an indication of a resource conflict to the user. Here, the stoplight can be found in the lower rightmost corner of the window with the left, 230, red light illuminated indicating that a conflict exists. The stoplight, or any other suitable depiction to convey the existence of a resource conflict, can be located at a plurality of locations on the window. The stoplight in this embodiment is configured as a single row of lights in a horizontal orientation near the navigation and home icons located in lower right hand corner of the window. The stoplight depicts a conventional configuration of a traffic signal with a red light being the furthermost left light, the green light being furthermost to the right, and a yellow light in the center.



FIG. 3 is a depiction of an Operations Parameters page, 320, of an embodiment for identification and notification of resource conflicts where no conflicts exist. This window possesses a similar stoplight, 310, as described above which is also located in the lower right corner. In this embodiment the stoplight has the far right, 330, green light illuminated indicating to the user that no resource conflicts are present. In either of these embodiments using a stoplight pictogram for indicating a resource conflict, the center light, if illuminated, would be yellow and would indicate that a conflict or multiple conflicts have been suppressed by the user.



FIG. 4 depicts the resolution window of one embodiment of a method for real-time identification of resource scheduling conflicts. This window appears after an indication of a conflict has been presented to the user, such as a red light illustrated above, and the user has clicked on the light to view the potential solution in an effort to resolve the conflict. The window in FIG. 4 indicates that there are multiple conflicts to be resolved, 410 and 420. The error identification program identifies and informs the user of the location of the potential problem on the top line, 430. In this embodiment, the conflict has been found in a shift named “New Shift,” 440. The method has been determined that New Shift does not have a start time and is in violation of a program rule. The window offers a solution to the conflict by stating that New Shift must have at least one valid start time. Furthermore, this embodiment presents a hyperlink, 450, to the location in the scheduling program where correct start times should be input. If the user selects the hyperlink “here,” 450, the program will open a window where the user can define a start time thus resolving the conflict. The new window will highlight the area that must be altered to resolve the conflict. Also depicted in FIG. 4 are two suppress buttons, 460, associated with the two displayed conflicts. These buttons allow the user to suppress the current conflicts and illuminate the yellow light in the stoplight pictogram.



FIG. 5 is a Calendar page, 520 using one embodiment of a method for identification and notification of resource conflicts where conflicts are associated with specific resources. The depiction shows a schedule calendar for the date Monday, Jan. 29, 2001. Under the date, 530, is a plurality of columns including one categorizing the resource being scheduled as “employee”. In one embodiment illustrated in FIG. 5 there are ten resources 540, all of the category “employee”. To the right of the category listing is another column that individually identifies each resource. This column contains employee identification numbers 550, which include empl#1 through empl#10, 550. In this embodiment, for the resources identified as empl#1, 460, empl#2, 570, and empl#4, 580, an exclamation mark 590 is located in the column immediately adjacent to the employee identification number. This exclamation mark 590 indicates that there is a resource conflict associated with each of employees 560, 570, and 580.


An additional embodiment further allows the user to review all the conflicts associated with a particular resource and individually select which conflicts are to be resolved.



FIG. 6 is a Conflicts page, 620, of an embodiment of the method for identification and notification of resource conflicts in which employee has been associated with a conflict and the user has chosen to review the conflicts. After the user clicks on the associated symbol, a list of conflicts associated with that resource is displayed, 630. In FIG. 6 empl#1 has three rule based conflicts 630.



FIG. 7 presents another embodiment including a Calendar page 720. Shown on the Calendar page 720 is a calendar conflict, 730, associated with empl#2. As depicted in FIG. 7, the calendar conflict is resolvable by selecting the button on the bottom of the page, 740. By selecting the resolution button, 740, one embodiment opens a new window on top of the conflict window to offer possible solutions and also to present links to the area of the program where alterations to the resource's utilization can be made.



FIG. 8 depicts a Resolve Calendar Conflict page, 820, which gives giving the user an interactive means to correct the conflict. The conflict is repeated to the user, 830, and then, in this embodiment, the user is presented with a solution that marks empl#2 as not attending the meeting thus removing the calendar conflict, 840. The user may also ignore the conflict until a new schedule is created, 850. Having made a choice the user then can apply the selection, cancel the resolution process, or seek additional help by using the three interactive “Apply, Cancel, and Help” buttons located at the bottom of the page, 860.



FIG. 9 is a flow diagram illustrating a process of concurrent real-time error identification according to an embodiment. The process begins at 902 when a user of a scheduling system enters new data. In one embodiment, an error identification method operates within and concurrent with the primary resource scheduling process and analyzes data for any conflicts. While error identification and notification of resource conflicts can operate independently of the primary resource scheduling process, in one embodiment error identification is a part of a primary resource scheduling process.


At 904, it is determined whether a conflict exists. If no conflict exists, a green light is displayed to the user at 908. If a conflict does exist, it is determined at 909 whether the conflict is resource specific, for example, whether the conflict relates to a particular employee. If the conflict is resource specific, it is determined at 910 whether the conflict is rule based or calendar based. If the conflict is rule base, a blue exclamation point is displayed at 911. If the conflict is calendar base, a red exclamation point is displayed at 913.


Referring again to block 909, if it is determined the conflict is not resource specific, it is then determined at 914 whether the conflict has been previously suppressed. If the conflict is suppressed, it is then determined at 915 whether there are other conflicts that are unsuppressed. If there are other conflicts that are unsuppressed, both a red and a yellow light are displayed at 918. If there are no unsuppressed conflicts, a green light is displayed at 920.


Referring again to 914, if the conflict is not suppressed, a red light is displayed at 916.


When a red, green or yellow light is displayed, the user can then click on the light for further information. If the user clicks on the red light, a new window containing an HTML page is generated describing the conflict and suggesting potential solutions. To do this, one embodiment utilizes a warning template file and the Windows registry.


If the user clicks on the yellow indication light, an HTML page is generated describing the suppressed conflict or conflicts and potential solutions. Contained within the new HTML page is a hyperlink that connects the user to the specific window within the primary scheduling resource software where the conflicted resource can be altered. If the user clicks on the hyperlink, one embodiment communicates with the primary resource scheduling software, causing the display of the specific window necessary to modify the data causing the error. Additionally, the data that should be altered is highlighted to facilitate resolving the conflict. If the user elects to suppress the conflict, the conflict is marked appropriately and stored in the Windows registry. If the user elects to un-suppress the conflict, an HTML page is generated based on the new unsuppressed conflict.


From the above description and drawings, it will be understood by those of ordinary skill in the art that the particular embodiments shown and described are for purposes of illustration only and are not intended to limit the scope of the invention. Those of ordinary skill in the art will recognize that the invention may be embodied in other specific forms without departing from its spirit or essential characteristics. References to details of particular embodiments are not intended to limit the scope of the claims.

Claims
  • 1. A method for performing complex resource scheduling of many resources, the method comprising: analyzing resource scheduling data for resource scheduling conflicts;generating at least one resource scheduling conflict based on the analyzed resource scheduling data;generating a schedule based on the resource scheduling data without receiving a response to the at least one resource scheduling conflict; andpresenting to a user, upon selection, a description of the resource scheduling conflicts and a choice to suppress the resource scheduling conflicts.
  • 2. The method of claim 1, wherein presenting includes providing the user a potential resolution of the resource scheduling conflicts.
  • 3. The method of claim 2, wherein the potential resolution further comprises a hyperlink to a relevant portion of the resource scheduling method allowing the resource scheduling conflicts to be resolved.
  • 4. The method of claim 1, further comprising conveying unobtrusively to the user an indication that the resource scheduling conflicts exist, wherein conveying the indication of the resource scheduling conflicts occurs concurrently with the resource scheduling process, the indication including a visual representation.
  • 5. The method of claim 4, wherein the visual representation includes using colors to represent the resource scheduling conflicts, including red to represent unsuppressed resource scheduling conflicts and yellow to represent suppressed resource scheduling conflicts.
  • 6. A method for performing complex resource scheduling of many resources, the method comprising: providing real-time identification of resource scheduling conflicts;analyzing resource scheduling data for the resource scheduling conflicts;generating at least one resource scheduling conflict based on the analyzed resource scheduling data;generating a schedule based on the resource scheduling data without receiving a response to the at least one resource scheduling conflict; andpresenting to a user, upon selection, a description of the resource scheduling conflicts and a choice to suppress the resource scheduling conflicts.
  • 7. The method of claim 6, wherein presenting includes providing the user a choice of viewing the description of the resource scheduling conflicts.
  • 8. The method of claim 6, wherein presenting includes providing the user a potential resolution of the resource scheduling conflicts, the potential solution including a hyperlink to a relevant portion of the resource scheduling process allowing the resource scheduling conflicts to be resolved.
  • 9. The method of claim 6, further comprising conveying unobtrusively to the user an indication that the resource scheduling conflicts exist, wherein conveying the indication of the resource scheduling conflicts occurs concurrently with the resource scheduling process, the indication including a visual representation.
  • 10. The method of claim 9, wherein the visual representation includes a first color for an unsuppressed resource scheduling conflict and a second color for a suppressed resource scheduling conflict.
  • 11. The method of claim 6, wherein the resource scheduling conflicts include conflicts of multiple different types, and wherein identifying includes indicating a type of a resource conflict.
  • 12. The method of claim 11, wherein the multiple different types include a rule-based conflict and a calendar based conflict.
  • 13. The method of claim 12, wherein the multiple different types are visually represented including using a third color for a rule-based conflict and a fourth color for a calendar based conflict.
RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 09/837,251, filed Apr. 18, 2001 now U.S. Pat. No. 6,959,405 and U.S. patent application Ser. No. 11/237,456, filed Nov. 15, 2005 now U.S. Pat. No. 7,281,173.

US Referenced Citations (180)
Number Name Date Kind
3594919 De Bell et al. Jul 1971 A
3705271 De Bell et al. Dec 1972 A
4510351 Costello et al. Apr 1985 A
4684349 Ferguson et al. Aug 1987 A
4694483 Cheung Sep 1987 A
4763353 Canale et al. Aug 1988 A
4815120 Kosich Mar 1989 A
4924488 Kosich May 1990 A
4937743 Rassman et al. Jun 1990 A
4953159 Hayden et al. Aug 1990 A
5016272 Stubbs et al. May 1991 A
5101402 Chiu et al. Mar 1992 A
5117225 Wang May 1992 A
5210789 Jeffus et al. May 1993 A
5239460 LaRoche Aug 1993 A
5241625 Epard et al. Aug 1993 A
5267865 Lee et al. Dec 1993 A
5299260 Shaio Mar 1994 A
5311422 Loftin et al. May 1994 A
5315711 Barone et al. May 1994 A
5317628 Misholi et al. May 1994 A
5347306 Nitta Sep 1994 A
5388252 Dreste et al. Feb 1995 A
5396371 Henits et al. Mar 1995 A
5432715 Shigematsu et al. Jul 1995 A
5465286 Clare et al. Nov 1995 A
5475625 Glaschick Dec 1995 A
5485569 Goldman et al. Jan 1996 A
5491780 Fyles et al. Feb 1996 A
5499291 Kepley Mar 1996 A
5535256 Maloney et al. Jul 1996 A
5572652 Robusto et al. Nov 1996 A
5577112 Cambray et al. Nov 1996 A
5590171 Howe et al. Dec 1996 A
5597312 Bloom et al. Jan 1997 A
5619183 Ziegra et al. Apr 1997 A
5696906 Peters et al. Dec 1997 A
5717879 Moran et al. Feb 1998 A
5721842 Beasley et al. Feb 1998 A
5742670 Bennett Apr 1998 A
5748499 Trueblood May 1998 A
5778182 Cathey et al. Jul 1998 A
5784452 Carney Jul 1998 A
5790798 Beckett, II et al. Aug 1998 A
5796952 Davis et al. Aug 1998 A
5809247 Richardson et al. Sep 1998 A
5809250 Kisor Sep 1998 A
5825869 Brooks et al. Oct 1998 A
5835572 Richardson, Jr. et al. Nov 1998 A
5862330 Anupam et al. Jan 1999 A
5864772 Alvarado et al. Jan 1999 A
5884032 Bateman et al. Mar 1999 A
5907680 Nielsen May 1999 A
5918214 Perkowski Jun 1999 A
5923746 Baker et al. Jul 1999 A
5933811 Angles et al. Aug 1999 A
5944791 Scherpbier Aug 1999 A
5948061 Merriman et al. Sep 1999 A
5958016 Chang et al. Sep 1999 A
5964836 Rowe et al. Oct 1999 A
5978648 George et al. Nov 1999 A
5982857 Brady Nov 1999 A
5987466 Greer et al. Nov 1999 A
5990852 Szamrej Nov 1999 A
5991373 Pattison et al. Nov 1999 A
5991796 Anupam et al. Nov 1999 A
6005932 Bloom Dec 1999 A
6009429 Greer et al. Dec 1999 A
6014134 Bell et al. Jan 2000 A
6014647 Nizzari et al. Jan 2000 A
6018619 Allard et al. Jan 2000 A
6035332 Ingrassia et al. Mar 2000 A
6038544 Machin et al. Mar 2000 A
6039575 L'Allier et al. Mar 2000 A
6049776 Donnelly et al. Apr 2000 A
6057841 Thurlow et al. May 2000 A
6058163 Pattison et al. May 2000 A
6061798 Coley et al. May 2000 A
6072860 Kek et al. Jun 2000 A
6076099 Chen et al. Jun 2000 A
6078894 Clawson et al. Jun 2000 A
6091712 Pope et al. Jul 2000 A
6108711 Beck et al. Aug 2000 A
6122665 Bar et al. Sep 2000 A
6122668 Teng et al. Sep 2000 A
6130668 Stein Oct 2000 A
6138139 Beck et al. Oct 2000 A
6144991 England Nov 2000 A
6146148 Stuppy Nov 2000 A
6151622 Fraenkel et al. Nov 2000 A
6154771 Rangan et al. Nov 2000 A
6157808 Hollingsworth Dec 2000 A
6167379 Dean et al. Dec 2000 A
6171109 Ohsuga Jan 2001 B1
6182094 Humpleman et al. Jan 2001 B1
6195679 Bauersfeld et al. Feb 2001 B1
6201948 Cook et al. Mar 2001 B1
6211451 Tohgi et al. Apr 2001 B1
6225993 Lindblad et al. May 2001 B1
6230197 Beck et al. May 2001 B1
6236977 Verba et al. May 2001 B1
6244758 Solymar et al. Jun 2001 B1
6282548 Burner et al. Aug 2001 B1
6286030 Wenig et al. Sep 2001 B1
6286046 Bryant Sep 2001 B1
6288753 DeNicola et al. Sep 2001 B1
6289340 Puram et al. Sep 2001 B1
6301462 Freeman et al. Oct 2001 B1
6301573 McIlwaine et al. Oct 2001 B1
6324282 McIlwaine et al. Nov 2001 B1
6347374 Drake et al. Feb 2002 B1
6351467 Dillon Feb 2002 B1
6353851 Anupam et al. Mar 2002 B1
6360250 Anupam et al. Mar 2002 B1
6370574 House et al. Apr 2002 B1
6381580 Levinson Apr 2002 B1
6404857 Blair et al. Jun 2002 B1
6411989 Anupam et al. Jun 2002 B1
6418471 Shelton et al. Jul 2002 B1
6459787 McIlwaine et al. Oct 2002 B2
6487195 Choung et al. Nov 2002 B1
6493758 McLain Dec 2002 B1
6502131 Vaid et al. Dec 2002 B1
6510220 Beckett, II et al. Jan 2003 B1
6535909 Rust Mar 2003 B1
6542602 Elazer Apr 2003 B1
6546405 Gupta et al. Apr 2003 B2
6560328 Bondarenko et al. May 2003 B1
6583806 Ludwig et al. Jun 2003 B2
6606657 Zilberstein et al. Aug 2003 B1
6647448 Brelin Nov 2003 B1
6665644 Kanevsky et al. Dec 2003 B1
6674447 Chiang et al. Jan 2004 B1
6683633 Holtzblatt et al. Jan 2004 B2
6697858 Ezerzer et al. Feb 2004 B1
6724887 Eilbacher et al. Apr 2004 B1
6732080 Blants May 2004 B1
6738456 Wrona et al. May 2004 B2
6757361 Blair et al. Jun 2004 B2
6772396 Cronin et al. Aug 2004 B1
6775377 McIlwaine et al. Aug 2004 B2
6792575 Samaniego et al. Sep 2004 B1
6810414 Brittain Oct 2004 B1
6820083 Nagy et al. Nov 2004 B1
6823384 Wilson et al. Nov 2004 B1
6870916 Henrikson et al. Mar 2005 B2
6901438 Davis et al. May 2005 B1
6959078 Eilbacher et al. Oct 2005 B1
6965886 Govrin et al. Nov 2005 B2
7092894 Crone Aug 2006 B1
7281173 Hite et al. Oct 2007 B2
7340328 Matheson et al. Mar 2008 B2
7499869 Iknoian Mar 2009 B2
20010000962 Rajan May 2001 A1
20010032335 Jones Oct 2001 A1
20010043697 Cox et al. Nov 2001 A1
20020038363 MacLean Mar 2002 A1
20020052948 Baudu et al. May 2002 A1
20020065700 Powell et al. May 2002 A1
20020065911 Von Klopp et al. May 2002 A1
20020065912 Catchpole et al. May 2002 A1
20020128925 Angeles Sep 2002 A1
20020143925 Pricer et al. Oct 2002 A1
20020165954 Eshghi et al. Nov 2002 A1
20030055883 Wiles et al. Mar 2003 A1
20030079020 Gourraud et al. Apr 2003 A1
20030144900 Whitmer Jul 2003 A1
20030154240 Nygren et al. Aug 2003 A1
20040100507 Hayner et al. May 2004 A1
20040165717 Mcllwaine et al. Aug 2004 A1
20050091098 Brodersen et al. Apr 2005 A1
20050138560 Lee et al. Jun 2005 A1
20050197877 Kalinoski Sep 2005 A1
20060015386 Moore Jan 2006 A1
20060026052 Klett et al. Feb 2006 A1
20080033778 Boss et al. Feb 2008 A1
20080082389 Gura Apr 2008 A1
20080300954 Cameron et al. Dec 2008 A1
20080306805 Vajracharya et al. Dec 2008 A1
20080313005 Nessland et al. Dec 2008 A1
Foreign Referenced Citations (11)
Number Date Country
0453128 Oct 1991 EP
0773687 May 1997 EP
0817455 Jan 1998 EP
0863650 Sep 1998 EP
0989720 Mar 2000 EP
1039732 Sep 2000 EP
1162814 Dec 2001 EP
2339643 May 2002 GB
2369263 May 2002 GB
WO 9843380 Nov 1998 WO
WO 0016207 Mar 2000 WO
Related Publications (1)
Number Date Country
20080091984 A1 Apr 2008 US
Continuations (2)
Number Date Country
Parent 11237456 Nov 2005 US
Child 11868656 US
Parent 09837251 Apr 2001 US
Child 11237456 US