|Publication number||US6941514 B2|
|Application number||US 09/892,474|
|Publication date||Sep 6, 2005|
|Filing date||Jun 28, 2001|
|Priority date||Apr 30, 2001|
|Also published as||US20040260668|
|Publication number||09892474, 892474, US 6941514 B2, US 6941514B2, US-B2-6941514, US6941514 B2, US6941514B2|
|Inventors||David L. Bradford|
|Original Assignee||Bellsouth Intellectual Property Corporation|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (10), Referenced by (76), Classifications (14), Legal Events (4)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This application claims the benefit of U.S. Provisional Patent Application 60/286,967, filed Apr. 30, 2001.
1. Field of the Invention
The present invention relates generally to computerized scheduling systems. More particularly, the present invention relates to managing work order scheduling according to priority levels that are assigned to work order requests.
2. Background of the Invention
Utility companies that provide services such as telecommunications capabilities, electric power, natural gas, or cable television, are generally organized into particular geographical regions for providing installation, build out, and repair services (“installations”). Engineers, designers, and other managers (“engineers”) are primarily responsible for designing and managing projects and work orders within respective geographical areas, or zones. The engineers create specifications for various project builds, and store them in the form of work orders to be completed. Construction crews and foremen, linemen, and other service agents (“construction agents”) are responsible for performing the installations required to complete the work orders to implement the engineers' designs. A significant problem that arises in conventional work order scheduling is the allocation of scarce resources (e.g., construction agents and equipment) to complete the work orders in a timely and efficient manner.
Work orders can be broken down into a set of tasks that must be completed to process the work order. Each of these tasks can be assigned a time required to complete the task. In this manner, the time required to complete a particular work order can be estimated by summing the time estimates for completing the series of tasks that must be performed to process the work order.
Engineers and construction agents generally participate in periodic scheduling meetings to schedule installations to complete new work orders and discuss the status of pending work orders. During these meetings, the engineers and construction agents determine how to allocate limited installation resources (e.g., construction agents and equipment) to complete new and pending work orders. The number of construction hours available to a particular construction team is a function of the number of construction agents in the team, and the length of their work weeks in hours. For example, if a team of construction agents in a particular area has 10 construction agents working a 40-hour week, that area has 400 construction hours per week that it can allocate. These construction hours are assigned to work order tasks during the scheduling meeting.
During the scheduling meetings, engineers negotiate with one another to determine when particular work orders will be processed. Engineers whose area (or zones) require immediate service are expected to negotiate with engineers with less urgent needs to maximize the effective allocation of the construction agent hours in the entire service region. Customer complaints, desires for new or expanded service and service upgrades are examples of the parameters engineers consider to determine the urgency of particular work orders. At these meetings, construction agents may also provide status updates to the engineers for pending work orders for which service has begun.
Engineers are evaluated on their ability to process work orders. Engineers who do not process work orders effectively or efficiently may be ineligible for bonuses and/or subject to reprimand. Accordingly, engineers have incentives to lobby intensively for the completion of their work orders, even if this means exaggerating the urgency of their work orders. That is, certain engineers may seek to schedule their work orders without regard to the consequences for other, more pressing work orders. As a result, construction agents are often assigned in an inefficient manner, and work orders having bona fide urgency can be delayed for work orders whose urgency has been exaggerated. Further scheduling is often a “personality contest” where engineers having a close personal or working relationship with the scheduling manager have their projects scheduled first despite inefficiencies that are likely to occur.
An additional problem with conventional scheduling of work orders is that the scheduling meetings are generally memorialized only in the individual notes of the participants. Consequently, any knowledge transferred during the meeting is only as good as the notes that are taken. These notes are often incomplete or inaccurate. Such incomplete notes or misunderstandings can also result in ineffective work order scheduling. Moreover, where resource allocation disagreements result in impasse, work order schedules do not result from the scheduling meeting. This is unacceptable because it may allow resources to become idle until such time as the impasse is resolved and a work order schedule is in place.
Another factor affecting the efficiency of work order processing is that engineers can communicate with one another or with construction agent managers outside of the scheduling meeting to make arrangements for completing work orders. Such conversations do not take into account the needs of other engineers. Moreover, such out-of-meeting dealing reduces the possibility of meaningful coordination that occurs during the scheduling meeting.
Another problem with conventional work order tracking systems is that engineers may not receive timely updates concerning the status of existing work orders to report to their customers or respond to customer queries. Consequently, engineers are not always able to respond to customer queries in a satisfactory manner.
To overcome the problems and difficulties associated with conventional work order scheduling systems as described above, the present invention is directed to a system and method for priority-based scheduling of work orders. The system includes a work order entry computer into which work order information is entered in the form of work order tickets. The work order information contained in the work order tickets is converted to a series of tasks. Each task is assigned an estimate of the amount of time required to complete the task. The sum of the time estimates required to complete each task for all tasks required to complete a work order is an estimate of the time required to complete the work order. The work order information and time required to complete the work order is stored in a database management system.
Priorities are assigned by the engineers responsible for particular work orders. The priorities indicate the relative importance of a particular work order. Work orders are scheduled according to these assigned priorities. In an ideal system, all work orders having a higher priority are completed before any work order having a lower priority is begun. But in actual implementation, it is allowable that work at different priority levels can occur simultaneously. This allows for resources that might be on a high priority that fails for some reason to perform work on a lower priority work order. No work is performed on work orders having a priority level of 4. Thus, a priority level of 4 is essentially a holding condition. The default is to assign work orders a priority level of 4.
To prevent engineers from assigning the highest priority to all of their work orders, engineers are allocated a predetermined number of priorities for a pre-determined number of priority levels. For example, in an embodiment of the present invention, there are 4 priority levels, 1-4, with 1 being the highest. Each engineer is allotted 5 priority assignments for each priority level 1-3 to assign priorities to the work orders that he or she is responsible for. Thus, an engineer can assign up to 5 work orders priority level 1, up to 5 work orders priority level 2 and up to 5 work orders priority level 3. As work orders are completed, the engineer is given the priority level of the job to assign. Thus, if an engineer has previously assigned 3 work orders priority level 1, the engineer can only assign 2 additional work orders priority level 1. When one of the 3 previously assigned priority level 1 work orders is completed, the engineer will be able to assign an additional priority 1 work order. In certain situations, engineers can borrow a priority level from another engineer.
To access work order information stored in the database, a user navigates displays in a graphical user interface. The displays include a search window for allowing the user to search the work order information, a report window for generating reports and an update window to access and update work order information.
The search window allows the user to enter search terms for searching the work order information in the database. Categories are provided to limit the search. For example, a user can search on the engineer's name or the job's name. Within each category, the user can search for a particular term. Multiple categories and search terms can be searched.
The report window allows a user to select a report format to output at least a portion of the work order data. Any desired report can be generated, and specific reports are generally implementation dependent. Reports provide a convenient format for reviewing the work order data.
The update window displays a record associated with a particular work order. For example, the update window displays the priority of the work order, the category of the work order, the engineer creating the work order, and other information. Any of this information can be changed using the update window.
The work order data is updated as work is reported to provide a mechanism for tracking the status of work orders. For example, when tasks are completed, the time remaining to complete the work order is reduced. When subsequent reports are generated, the reports display the reduced time remaining to complete the work order. Consequently, the present invention tracks the progress of work order processing. Preferably, these updates are performed at night via the work order update computer.
The present invention is described in greater detail in the detailed description of the invention, the appended drawings and the attached claims.
Web server 108 can be any web server. For example, it could be the well-known Apache web server. Preferably, web server 108 executes the PHP language. The PHP language is a web-based scripting language. The PHP language outputs HTML to communicate with web browser 106.
In operation, the user submits a work order information request using web browser 106. This request is sent to web server 108, which converts the request into a database query. Web server 108 sends the database query to DBMS server 104. DBMS server 104 processes the request and sends the requested information back to Web server 108. Web server 108 sends the requested information back to web browser 106 which displays the information to the user.
Work order information is stored in DBMS server 104 in the following manner. Work order information in the form of work order tickets is input via a work order entry system 112 at the design time of the engineering work order or later. Work order entry system 112 converts the work order into a series of tasks that need to be performed to complete the work order. Alternately, an operator converts the work order into a series of tasks using work order entry system 112. Work order entry system 112 is any computer in which work order ticket information can be entered and converted to task information. Work order entry system 112 creates reports from the information it receives. These reports are available for printing or storage in a file, for example, a comma-delimited file. The information comprising these reports is updated periodically as described below. Preferably, the information is updated daily.
Periodically, or on demand, the work order information is sent to DBMS server 104 through a network 114 and Unix server 110. The work order information can be any information that is stored in work order entry system 112. Preferably, network 114 is an intranet that is not accessible generally over the Internet. Limiting access provides security to the work order system of the present invention.
A work order update system 116 allows for updates to be made for current work orders in the system. For example, as tasks are completed for particular work orders, the time required for that particular task is added back to the available time that construction agents working on that task have. In addition, the time required to complete the work order is reduced by the same amount. For example, if a task required 8 hours to complete, when it is finished the available time for the construction agent assigned to that task is increased by 8, and the time required to complete the work order is decreased by 8. In addition, as work orders are completed, the priorities associated with that task are freed for the engineer assigning the work order. Work order update system 116 provides the updated information to work order entry system 112.
In the present invention, job priorities are used to establish the relative importance of work orders and thereby the order in which work orders are scheduled for completion. The present invention forces the engineers have to determine the relative priorities of the jobs for which they are responsible. The engineers generally determine how to select the priorities on the basis of external pressures, for example, whether there are other immediate service order requests, new housing subdivisions or other subdivisions requiring service and other pressures.
Jobs having the highest priority are assigned a priority of 1, and are scheduled to be worked on first. Jobs having the next highest priority are assigned a priority of 2. These jobs are preferably worked on after all jobs having priority 1. In other implementations of the present invention, there is no requirement that jobs having a higher priority are completed prior to beginning work on jobs having lower priorities. Jobs having the next highest priority are assigned a priority of 3. These jobs are worked on after all jobs having priority 1 or 2 are completed. Jobs having priority 4 are not worked on. Initially, all jobs are assigned a priority of 4. Therefore, jobs will not be worked on until an engineer assigns them a priority of 1, 2 or 3.
To prevent engineers from assigning all jobs a priority of 1, limited numbers of each class of priority are allocated to each engineer. For example, each engineer may be given 5 priority 1's, 5 priority 2's and 5 priority 3's. The engineer can allocate these priorities to his or her work orders as he or she deems appropriate. Allocating priorities to engineers in this manner “levels the playing field” so that no one engineer can command more than an appropriate share of resources. That is, unlike the situation found in conventional work order scheduling, using the system of the present invention largely eliminates the advantage engineers who are more articulate or friendlier with scheduling managers would otherwise have over their peers. With the present invention, they, like other engineers, are allocated a fixed number of priorities at each level to assign to their work orders.
The system tracks priority use by the engineers. One way of tracking the priorities is to have a priority table of remaining priorities. The priority table has an entry for each engineer. Each entry contains the number of priorities at each level remaining for each engineer. The table is initialized so that the engineer has the maximum number of priorities for each level. If the value of the table for a particular engineer for a particular priority level is 0—indicating that the engineer has assigned all or his or her allocated priorities of the level to other jobs—that engineer cannot assign that particular priority level, and must choose a different priority level. When an engineer attempts to change a priority for a job, the table is accessed to be sure that the priority level to which the engineer desires to change the priority is not 0. If is not, the priority of the work order is changed and priority table entry corresponding to the new priority level for that engineer is decremented by 1. In addition, if the job order is changed from a priority level other than 4, the table entry corresponding to the priority level from which the priority of the work order was changed is incremented by 1. If the value is 0, the engineer is so informed, and must choose a different priority value or not change the job's priority. It would be apparent to those skilled in the art that there are numerous ways in which the priorities can be tracked.
In a second embodiment of the present invention, engineers are allowed to borrow priorities from one another. Thus, if an engineer has used up all of his or her allocated level 1 priorities, the engineer can negotiate with another engineer to borrow a level 1 priority. If the other engineer can loan the priority the loan is made. Incrementing and decrementing as described above are performed for the priorities of the two engineers. However, in this case, the system tracks the ownership of the priority. When a work order having the loaned priority level is completed for the engineer to whom the loan was made, the priority level of the table entry for the loaning engineer is incremented. Whether the other engineer can loan the priority can be determined by querying the priority table. Allowing borrowing, provides an alternative for engineers that have emergency situations arise.
The priorities can be seen via reporting described below. Thus, the present invention provides an ability to manage, update and track the engineers' use of priorities.
Using the present invention, users can obtain information regarding pending work orders, modify pending work orders, delete pending work orders and enter new work orders via a graphical user environment (GUI). Preferably the GUI is a web browser such as web browser 106.
The selected category is searched for terms entered in the CONTAINING text block. Multiple categories and terms can be searched using addition SEARCH FOR/CONTAINING pairs. Any number of such additional pairs can be implemented, though only two have been explicitly shown in the present application. When the desired categories and terms are entered, the user selects the RETRIEVE WORK ORDERS button to submit the work order data request. In response to the user's selection, the system returns work order data corresponding to the request.
The jobs can be listed according to any category by selecting the category in the ARRANGE BY pull down menu. The categories can be listed alphabetically, numerically or in any other desired order, depending on the category and what is reasonable for that category. For example, jobs are generally listed alphanumerically. Engineers are generally listed alphabetically by last name. The default listing arrangement is by job name.
Work order data that is found as a result of the search or reports that are generated can be printed. The number of lines per page for printing can be input in the LINES PER PAGE text block. If there is a large amount of data to be printed, this value should be set high so that the largest number of lines is used per page. If left to a low number, for example, leaving this field blank, the present invention provides an index showing ranges. For example, if this field is set to 10, and there are 100 jobs to print, upon printing, 10 jobs will be displayed per page, with an index having ranges for printing jobs 1-10, 21-30, 31-40, . . . and 91-100.
Using the data entered in the SCHEDULE window, the system generates an information request. The system sends uses the information request as described above to search for and collect the work order data responsive to the information request. This information is gathered and displayed to the user. If the user does not select specific data to search for, the system defaults to returning to the user all of the work order information in DBMS server 104.
More particularly, the CA field represents via NORNA (needed, ordered, received, not applicable) fields the status or need of that material item. This field is modifiable by users of the present invention, unlike conventional systems. The HW field represent via NORNA fields the status or need of that material item. The HW field provides a way to report details, previously available only from a separate system, via a button. The HW field is used to provide information in the scheduling meeting regarding items that were discussed in another meeting. Consequently, providing the HW field is a time saving measure. The PLGS field is similar to the HW field just described. The PRMT field is a manual input via a button to indicate whether a permit to work has been obtained or is required from the municipality involved in a particular work order. The SITE RDY field indicates whether a remote electronic cabinet site has been prepared for installation. The PRE CT field indicates whether or not a particular job is a candidate for a pre-service order site visit by one or more installation technicians. The PRE CT field can be used, for example, to assist managers in scheduling installation technician visits to sites. The GO field is an indicator of whether a work order will be completed or not.
Initially, the REM HRS field is populated with a time estimate corresponding to the amount of time that estimated to be required to complete the job. This is determined from the tasks required to perform the job. Each job can be divided into a series of tasks. Each of these tasks is assigned a time estimate of the time required to complete the task. The time required to complete a job is estimated as the sum of the time estimates for each of the tasks required to complete the job. This sum is entered as the initial value of the REM HRS field for a particular job.
The REM HRS field is a dynamic field that is updated to reflect progress of the job. As described above, time reports from the construction agents are entered into MTR system 116. Preferably, the time reports are entered daily or nightly. These time reports contain the time that was spent on each job for the day. This time is subtracted from the REM HRS field of the job. Thus, each day, an estimate of the time required to complete a job is readily available by querying the REM HRS field for the job.
If a user desires more information about a particular job, or desires to change or update the parameters for a particular job, the user can choose the job from scheduling display 401. When the user makes such a choice, a work order display is shown to the user.
In addition, work order display 501 includes additional status categories. These categories standardize responses that are received to questions that arise during scheduling meetings. These questions can be asked during a scheduling meeting and the answers input using the present invention by selecting the appropriate radio button. For example, in a job requiring contract work, the status of the contract can be entered. Where a line crew is required, the status of the line crew can be entered. The same is true for splicing requirements and electronics package (DLC) requirements. These parameters can also be changed by an engineer that has authority to make changes to a work order outside the scheduling meeting. Authorization can be provided using well-known user name/password security schemes.
Work order display 501 also provides standard terminology that serves to standardize the terminology used by the participants in the scheduling process. That is, by providing radio buttons, the system of the present invention forces the user to press a button that is converted into a standard text, rather than having the user enter in his or her own individual notations.
The present invention provides various reports to obtain work order information.
In addition, where a responsibility for engineering design and construction is divided into districts, the reports can be generated for each district. Generally, one engineer and one or more construction agents are responsible for each district. For example, in
The Resource Statistics report provides information regarding resource use. The Action Needed report provides a listing of those work orders for which an action needed item is set in the NOTES field of the work order. The suspected bad hours report generates a report of those work orders that the system determines are not viable work orders. Such “test” work orders are used by engineers as placeholders and are to be deleted when the engineer is finished with it. However, oftentimes the test work orders are not deleted. Construction agents cannot be sure that the test work order are not to be implemented. Consequently, to the extent that construction agents attempt to implement them or concern themselves with their implementation, there are inefficiencies introduced by the test work orders. This report is a listing of the test work orders.
An example of two of the reports is provided in detail below.
The present invention also allows engineers' current priorities usage to be reviewed.
The present invention can be used during scheduling meetings to manage work orders and modifications of work orders. For example, the work order information is accessible to any person using a web browser that has appropriate authorization. Such a person, for example, the scheduling manager responsible for the scheduling meeting, can access work order information, modify work order information, delete work order information, add work order information or otherwise update work order information by navigating the displays and windows described above. Any changes that are made are stored in the system at the time the change is made. Thus, there is little, or no, loss of knowledge due to inaccurate or incomplete notes because the knowledge of the scheduling meeting is captured and stored during the scheduling meeting.
In addition, to its use during scheduling meetings, the present invention can be used by engineers to modify work orders for which they are responsible, outside the context of a scheduling meeting. That is, engineers can be authorized to modify the work order data for the work orders they are responsible for using the above-described GUI displays. For example, engineers can allocate, update or change work order priorities, within the allotted priorities. Providing engineers access to the work order system reduces the need for and number of scheduling meetings. In addition, scheduling meetings will be reduced in duration. The risks associated with work order modifications made with considering the requirements of other engineers are essentially eliminated because the priorities can only be allocated on the basis of the allotted priorities. Engineers know they only have so many of each priority level to allocate. In the case, where an engineer “borrows” a priority, the needs of the loaning engineer are taken into account as there will be no loan if the loaning engineer does not believe such a loan is consistent with his or her needs.
The foregoing disclosure of the preferred embodiments of the present invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many variations and modifications of the embodiments described herein will be obvious to one of ordinary skill in the art in light of the above disclosure. The scope of the invention is to be defined only by the claims appended hereto, and by their equivalents.
Further, in describing representative embodiments of the present invention, the specification may have presented the method and/or process of the present invention as a particular sequence of steps. However, to the extent that the method or process does not rely on the particular order of steps set forth herein, the method or process should not be limited to the particular sequence of steps described. As one of ordinary skill in the art would appreciate, other sequences of steps may be possible. Therefore, the particular order of the steps set forth in the specification should not be construed as limitations on the claims. In addition, the claims directed to the method and/or process of the present invention should not be limited to the performance of their steps in the order written, and one skilled in the art can readily appreciate that the sequences may be varied and still remain within the spirit and scope of the present invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5093794 *||Aug 22, 1989||Mar 3, 1992||United Technologies Corporation||Job scheduling system|
|US5911136 *||Mar 26, 1997||Jun 8, 1999||Proprietary Financial Products, Inc.||System for prioritized operation of a personal financial account comprising liabilities and investment assets|
|US5913201 *||Mar 31, 1997||Jun 15, 1999||Gte Laboratories Incoporated||Method and apparatus for assigning a plurality of work projects|
|US6115640 *||Jan 16, 1998||Sep 5, 2000||Nec Corporation||Workflow system for rearrangement of a workflow according to the progress of a work and its workflow management method|
|US6438436 *||Feb 16, 1999||Aug 20, 2002||Kabushiki Kaisha Toshiba||Production scheduling management system, and method of managing production scheduling|
|US6463346 *||Oct 8, 1999||Oct 8, 2002||Avaya Technology Corp.||Workflow-scheduling optimization driven by target completion time|
|US20020010615 *||Apr 2, 2001||Jan 24, 2002||Simon Jacobs||Methods and systems for scheduling complex work orders for a workforce of mobile service technicians|
|US20020073226 *||Sep 18, 2001||Jun 13, 2002||Sridhar Manickam R.||Distributed quality-of-service system|
|US20020111842 *||Feb 9, 2001||Aug 15, 2002||Jon Miles||Work order management system|
|US20030167199 *||Mar 1, 2002||Sep 4, 2003||Thomann Karen S.||Automated workflow means and method for pension products|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7197469 *||Jun 26, 2001||Mar 27, 2007||International Business Machines Corporation||Method for allocating limited component supply and capacity to optimize production scheduling|
|US7228547||Jul 30, 2001||Jun 5, 2007||International Business Machines Corporation||Method, system, and program for enabling access to a plurality of services|
|US7296056 *||Jul 30, 2001||Nov 13, 2007||International Business Machines Corporation||Method, system, and program for selecting one user to assign a work item in a workflow|
|US7467161 *||May 15, 2002||Dec 16, 2008||Franklin Frisina||Computer system for maintenance resource optimization|
|US7693594 *||Dec 29, 2005||Apr 6, 2010||Sap Ag||System and method for scheduling driven availability check|
|US7698427||Jul 30, 2001||Apr 13, 2010||International Business Machines Corporation||Method, system, and program for transferring data from an application engine|
|US7937414 *||Dec 5, 2003||May 3, 2011||At&T Intellectual Property I, L.P.||Fiber splice assignment and management system|
|US8019573 *||Dec 5, 2003||Sep 13, 2011||At&T Intellectual Property I, L.P.||Drawing conversion assignment and management system|
|US8060401||Jul 17, 2007||Nov 15, 2011||At&T Intellectual Property I, Lp||Methods, systems, and computer-readable media for providing an indication of a schedule conflict|
|US8069072||Jul 17, 2007||Nov 29, 2011||At&T Intellectual Property I, Lp||Methods, systems, and computer-readable media for providing an indication of hightime|
|US8239232 *||Jul 17, 2007||Aug 7, 2012||At&T Intellectual Property I, L.P.||Methods, systems, and computer-readable media for providing commitments information relative to a turf|
|US8249905||Jul 17, 2007||Aug 21, 2012||At&T Intellectual Property I, Lp||Methods, systems, and computer-readable media for providing future job information|
|US8286183||Oct 22, 2005||Oct 9, 2012||Cisco Technology, Inc.||Techniques for task management using presence|
|US8341547||Jul 17, 2007||Dec 25, 2012||At&T Intellectual Property I, L.P.||Methods, systems, and computer-readable media for providing contact information at turf level|
|US8352302||Jul 17, 2007||Jan 8, 2013||At&T Intellectual Property I, L.P.||Methods, systems, and computer-readable media for determining a plurality of turfs from where to reallocate a workforce to a given turf|
|US8380744||Jul 17, 2007||Feb 19, 2013||At&T Intellectual Property I, L.P.||Methods, systems, and computer-readable media for generating a report indicating job availability|
|US8433598||Jun 26, 2012||Apr 30, 2013||At&T Intellectual Property I, L.P.||Methods, systems, and computer-readable media for providing future job information|
|US8478624 *||Jul 17, 2012||Jul 2, 2013||International Business Machines Corporation||Quality of records containing service data|
|US8489441 *||Aug 13, 2012||Jul 16, 2013||International Business Machines Corporation||Quality of records containing service data|
|US8543439||Nov 29, 2012||Sep 24, 2013||At&T Intellectual Property I, L.P.||Methods, systems, and computer-readable media for determining a plurality of turfs from where to reallocate a workforce to a given turf|
|US8635095 *||Sep 12, 2005||Jan 21, 2014||At&T Intellectual Property I, L.P.||Method and apparatus for tracking an intent|
|US8683436 *||Dec 19, 2007||Mar 25, 2014||Sap Ag||Timer patterns for process models|
|US8731999||Feb 11, 2010||May 20, 2014||Certusview Technologies, Llc||Management system, and associated methods and apparatus, for providing improved visibility, quality control and audit capability for underground facility locate and/or marking operations|
|US8751278||Jun 18, 2012||Jun 10, 2014||At&T Intellectual Property I, L.P.||Methods, systems, and computer-readable media for providing commitments information relative to a turf|
|US8799046 *||Dec 27, 2006||Aug 5, 2014||Verizon Patent And Licensing Inc.||Dispatching prioritized jobs at multiple locations to workers|
|US8849691||Dec 29, 2005||Sep 30, 2014||Microsoft Corporation||Modeling user input and interaction in workflow based applications|
|US9158834 *||Jan 21, 2013||Oct 13, 2015||Snap-On Incorporated||Methods and systems for mapping repair orders within a database|
|US9189759||Sep 14, 2012||Nov 17, 2015||At&T Intellectual Property I, L.P.||Methods, systems, and computer-readable media for providing contact information at turf level|
|US9224114||Feb 4, 2013||Dec 29, 2015||At&T Intellectual Property I, L.P.||Methods, systems, and computer-readable media for generating a report indicating job availability|
|US9354847||Dec 29, 2008||May 31, 2016||Microsoft Technology Licensing, Llc||Interface infrastructure for a continuation based runtime|
|US9378511 *||Jul 15, 2009||Jun 28, 2016||International Business Machines Corporation||Real-time appointment of enterprise mobile agents in response to customer requests|
|US9536264||Nov 14, 2011||Jan 3, 2017||Microsoft Technology Licensing, Llc||Host agnostic messaging in a continuation based runtime|
|US9563863||Feb 11, 2010||Feb 7, 2017||Certusview Technologies, Llc||Marking apparatus equipped with ticket processing software for facilitating marking operations, and associated methods|
|US9578678||Jul 31, 2015||Feb 21, 2017||Certusview Technologies, Llc||Methods and apparatus for facilitating locate and marking operations|
|US9633340||Oct 10, 2015||Apr 25, 2017||Snap-On Incorporated||Methods and systems for mapping repair orders within a database|
|US20020198757 *||Jun 26, 2001||Dec 26, 2002||International Business Machines Corporation||Method for allocating limited component supply and capacity to optimize production scheduling|
|US20030023472 *||Jul 30, 2001||Jan 30, 2003||International Business Machines Corporation||Method, system, and program for transferring data from an application engine|
|US20030023662 *||Jul 30, 2001||Jan 30, 2003||International Business Machines Corporation||Method, system, and program for enabling access to a plurality of services|
|US20030023728 *||Jul 30, 2001||Jan 30, 2003||International Business Machines Corporation||Method, system, and program for selecting one user to assign a work item in a workflow|
|US20030187865 *||May 15, 2002||Oct 2, 2003||Franklin Frisina||Computer system for maintenance resource optimization|
|US20040024784 *||Apr 9, 2003||Feb 5, 2004||Spall Walter Dale||Information system for manipulating data related to the ordering and performance of services and communication of results|
|US20050123252 *||Dec 5, 2003||Jun 9, 2005||Thornton Diane C.||Fiber splice assignment and management system|
|US20050125304 *||Dec 5, 2003||Jun 9, 2005||Thornton Diane C.||Drawing conversion assignment and management system|
|US20050255194 *||Apr 2, 2003||Nov 17, 2005||Willett Paul E||Method of scheduling a production run of bakery products|
|US20060184437 *||May 18, 2005||Aug 17, 2006||Deutsche Boerse Ag||Settlement engine for settling transactions and a method for settling transactions|
|US20070061175 *||Sep 12, 2005||Mar 15, 2007||Sbc Knowledge Ventures L.P.||Method and apparatus for tracking an intent|
|US20070094661 *||Oct 22, 2005||Apr 26, 2007||Cisco Technology, Inc.||Techniques for task management using presence|
|US20070156273 *||Dec 29, 2005||Jul 5, 2007||Von Helmolt Hans-Ulrich A||System and method for scheduling driven availability check|
|US20070156485 *||Dec 29, 2005||Jul 5, 2007||Microsoft Corporation||Modeling user input and interaction in workflow based applications|
|US20070156486 *||Dec 29, 2005||Jul 5, 2007||Microsoft Corporation||Multiple concurrent workflow persistence schemes|
|US20070156487 *||Dec 29, 2005||Jul 5, 2007||Microsoft Corporation||Object model on workflow|
|US20080103843 *||Oct 27, 2006||May 1, 2008||Sap Ag-Germany||Integrating information for maintenance|
|US20080162242 *||Dec 27, 2006||Jul 3, 2008||Verizon Services Organization Inc.||Dispatching Prioritized Jobs At Multiple Locations To Workers|
|US20080163214 *||Dec 28, 2006||Jul 3, 2008||Caterpillar Inc.||Online task monitoring tool|
|US20080177587 *||Jan 23, 2007||Jul 24, 2008||Sonia Jean Cushing||Prioritizing orders using business factors|
|US20090006170 *||Jun 26, 2007||Jan 1, 2009||Wachovia Corporation||Production center system|
|US20090020297 *||Jul 17, 2007||Jan 22, 2009||Robert Ingman||Methods, Systems, and Computer-Readable Media for Providing Commitments Information Relative to a Turf|
|US20090024431 *||Jul 17, 2007||Jan 22, 2009||Robert Ingman||Methods, Systems, and Computer-Readable Media for Providing Future Job Information|
|US20090024436 *||Jul 17, 2007||Jan 22, 2009||Robert Ingman||Methods, Systems, and Computer-Readable Media for Determining a Plurality of Turfs from Where to Reallocate a Workforce to a Given Turf|
|US20090024437 *||Jul 17, 2007||Jan 22, 2009||Robert Ingman||Methods, Systems, and Computer-Readable Media for Providing A Ratio of Tasks Per Technician|
|US20090024438 *||Jul 17, 2007||Jan 22, 2009||Robert Ingman||Methods, Systems, and Computer-Readable Media for Providing Workforce To Load Information|
|US20090024455 *||Jul 17, 2007||Jan 22, 2009||Robert Ingman||Methods, Systems, and Computer-Readable Media for Providing an Indication of Hightime|
|US20090024957 *||Jul 17, 2007||Jan 22, 2009||Robert Ingman||Methods, Systems, and Computer-Readable Media for Providing Contact Information At Turf Level|
|US20090024999 *||Jul 17, 2007||Jan 22, 2009||Robert Ingman||Methods, Systems, and Computer-Readable Media for Providing an Indication of a Schedule Conflict|
|US20090138311 *||Nov 28, 2007||May 28, 2009||Michael Anthony Iacovone||System and method for computer aided work order scheduling|
|US20090150206 *||Dec 7, 2007||Jun 11, 2009||Mci Communications Services||Notification system and method|
|US20090165001 *||Dec 19, 2007||Jun 25, 2009||Baeuerle Stefan A||Timer Patterns For Process Models|
|US20090199192 *||Feb 5, 2008||Aug 6, 2009||Robert Laithwaite||Resource scheduling apparatus and method|
|US20100063858 *||Jan 22, 2009||Mar 11, 2010||Ko Chien-Ho||Method for reducing finished goods inventory for precast fabricator|
|US20100287025 *||Dec 17, 2009||Nov 11, 2010||Brian Fletcher||Mobile resource task scheduling|
|US20100324948 *||Jun 18, 2009||Dec 23, 2010||Microsoft Corporation||Managing event timelines|
|US20110015963 *||Jul 15, 2009||Jan 20, 2011||International Business Machines Corporation||Real-Time Enterprise Workforce Management|
|US20110035252 *||Jul 15, 2010||Feb 10, 2011||Certusview Technologies, Llc||Methods, apparatus, and systems for processing technician checklists for locate and/or marking operations|
|US20110060623 *||Sep 8, 2009||Mar 10, 2011||Flower City Group||System and Method for Resource Workflow Scheduling|
|US20140207771 *||Jan 21, 2013||Jul 24, 2014||Snap-On Incorporated||Methods and Systems for Mapping Repair Orders within a Database|
|US20150170153 *||Dec 17, 2013||Jun 18, 2015||Oracle International Corporation||Prioritizing threads for agent routing|
|U.S. Classification||715/700, 705/32, 705/7.13|
|International Classification||G06Q10/10, G06Q10/06, G06F7/00, G06F17/00, G06F17/30|
|Cooperative Classification||G06Q10/06311, G06Q10/1091, G06Q10/06|
|European Classification||G06Q10/06, G06Q10/06311, G06Q10/1091|
|Jun 28, 2001||AS||Assignment|
Owner name: BELLSOUTH INTELLECTUAL PROPERTY CORPORATION, DELAW
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:BRADFORD, DAVID L.;REEL/FRAME:011950/0362
Effective date: 20010627
|Sep 30, 2008||FPAY||Fee payment|
Year of fee payment: 4
|Feb 25, 2013||FPAY||Fee payment|
Year of fee payment: 8
|Apr 14, 2017||REMI||Maintenance fee reminder mailed|