US20120259540A1 - Methods and systems for workforce management - Google Patents

Methods and systems for workforce management Download PDF

Info

Publication number
US20120259540A1
US20120259540A1 US13/111,472 US201113111472A US2012259540A1 US 20120259540 A1 US20120259540 A1 US 20120259540A1 US 201113111472 A US201113111472 A US 201113111472A US 2012259540 A1 US2012259540 A1 US 2012259540A1
Authority
US
United States
Prior art keywords
work ticket
field
request
ticket
computing device
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US13/111,472
Other languages
English (en)
Inventor
Pradeep Kishore
Visvanathan Lakshmi Narayan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Infosys Ltd
Original Assignee
Infosys Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Infosys Ltd filed Critical Infosys Ltd
Assigned to INFOSYS TECHNOLOGIES LIMITED reassignment INFOSYS TECHNOLOGIES LIMITED ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: KISHORE, PRADEEP, NARAYAN, VISVANATHAN LAKSHMI
Assigned to Infosys Limited reassignment Infosys Limited CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: INFOSYS TECHNOLOGIES LIMITED
Publication of US20120259540A1 publication Critical patent/US20120259540A1/en
Priority to US14/754,309 priority Critical patent/US9785897B2/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G01—MEASURING; TESTING
    • G01C—MEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
    • G01C21/00—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00
    • G01C21/26—Navigation; Navigational instruments not provided for in groups G01C1/00 - G01C19/00 specially adapted for navigation in a road network
    • G01C21/34—Route searching; Route guidance
    • G01C21/36—Input/output arrangements for on-board computers
    • G01C21/3605—Destination input or retrieval
    • G01C21/362—Destination input or retrieval received from an external device or application, e.g. PDA, mobile phone or calendar application
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
    • G06Q10/06311—Scheduling, planning or task assignment for a person or group
    • G06Q10/063118—Staff planning in a project environment
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/103—Workflow collaboration or project management
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/105—Human resources

Definitions

  • Workforce management strives to get the right number of technicians in the right places at the right times to maximize service and minimize cost. Optimization is difficult since it involves intelligent scheduling and dispatching of multiple technicians to different locations, while minimizing cost and maintaining good customer service. Workforce management may be useful, for example, for companies that need to manage a field force of technicians for installations or servicing existing systems. Typical workforce management systems may interface with ticket management systems to schedule and assign jobs to technicians. Optimal workforce management, however, requires more than an optimal schedule for technicians. Immediate and unexpected changes, such as changes in technician status or unforeseen changes in the workload, may require spontaneous adjustments.
  • Some current workforce management systems provide map centric tools, such as the systems provided by CLICKSOFTWARETM. These systems attempt to optimize efficiency by scheduling and dispatching a qualified technician to a location near the technician.
  • these workforce management systems generally come bundled with land base data (e.g., maps or other cartographical data). The bundled land base data may quickly become out-of-date and result in less than optimal scheduling and dispatch. This may also lead to inaccurate driving instructions being provided to a technician, thus further reducing efficiency.
  • typical workforce management systems may contribute to inefficiencies due to lack of real time location data. For example, a typical system may see that a technician was scheduled to do a job at a first location and, thus, ad hoc schedule this same technician to assist with an emergency repair at a location near the first location. However, if technician finished the first job they may no longer be near the first location. Typical workforce management systems fail to adopt dynamic scheduling and real-time dispatch using real-time location data to increase efficient allocation.
  • typical standalone workforce management systems are resource intensive, expensive to operate, and difficult to integrate with other enterprise level systems.
  • a company may purchase a custom made workforce management system to manage field technicians. These systems may be cost preclusive for small companies. Additionally, these systems may be difficult to integrate with allied systems, for example technician time entry systems, ticket management systems, vehicle tracking systems, payroll and benefits systems, human resources systems, and the like.
  • FIG. 1 shows a functional block diagram of a workforce management system.
  • FIG. 2 shows an exemplary workforce management system architecture having a workforce management subsystem operatively coupled to a maps API.
  • FIG. 3A-B show exemplary user interfaces for interacting with a workforce management system.
  • FIG. 4A-D show additional exemplary user interfaces for interacting with a workforce management system.
  • FIG. 5 shows an exemplary computing device useful for implementing systems and performing methods disclosed herein.
  • Embodiments provide computer-implemented methods and systems for managing a workforce.
  • Embodiments may be configured to reduce operational costs through managing unplanned and ad hoc jobs generated due to emergency, short service level agreement (“SLA”) times, missed appointments, and the like.
  • Embodiments may implement Geographic Information System (“GIS”) based location intelligence and location based services to optimize work force allocation and management.
  • GIS Geographic Information System
  • Embodiments may also integrate with existing and allied systems, such as trouble ticket systems, field force tracking systems, and the like.
  • FIG. 1 shows a functional block diagram of a workforce management system (“WFMS”) 101 .
  • WFMS 101 may include one or more workforce management computing device(s) 102 configured to effectively plan and dispatch field service technicians (or other field operatives).
  • workforce management computing device 102 may be configured to dispatch technicians substantially in real-time in response to ad hoc work tickets (e.g., in the case of an emergency).
  • Workforce management computing device 102 may be operatively coupled to an integration computing device 105 for integrating with allied and existing systems 118 .
  • Integration computing device 105 may be a computing device configured to integrate existing and allied computing systems 118 with workforce management computing device 102 .
  • integration computing device 105 may include one or more data stores configured to convert data from allied and existing systems 118 into a format useful for workforce management computing device 102 .
  • integration computing device 105 may be configured to receive trouble tickets from a ticketing system, for example REMEDYTM, that may need to be assigned to a technician from an existing system 108 and convert the trouble tickets into a format required by workforce management computing device 102 .
  • Integration computing device 105 may, alternatively or in addition, perform services to assist in integration, for example caching services to speed data access for workforce management computing device 102 .
  • Integration computing device 105 may be configured to convert data from legacy systems to formats useful for the workforce management system 101 and then replace the functionality of the legacy systems. For example, integration computing device 105 may convert existing trouble tickets to a required format then, going forward, receive all new trouble tickets and, thus, replace the legacy system.
  • integration computing device 105 is described above as integrating workforce management computing device 102 with a trouble ticket system, integration computing device 105 may integrate with any allied and existing systems, for example inventory systems, human resource systems, reporting systems, scheduling systems, customer relation systems, and the like. Alternatively, integration computing device 105 may be omitted, thereby allowing existing and allied systems 118 to be operatively coupled directly to workforce management computing device 102 . Further, integration computing device 105 may be configured to provide various systems, such as trouble ticket systems, if no such systems previously existed or to simply replace such existing systems.
  • System 100 also includes a technician interface computing device 103 operatively coupled to workforce management computing device 102 .
  • Technician interface computing device 103 may be operatively coupled to one or more technician computing device, for example over a network 119 such as the Internet, a local area network (“LAN”), a wide area network (“WAN”), mobile service provider network (e.g., from VERIZONTM WIRELESS), and the like.
  • Technician interface computing device 103 may be coupled to technician computing devices such as a laptop 114 , a tablet 112 (e.g., an IPADTM), a smartphone 111 (e.g., an IPHONETM, a BLACKBERRYTM, or an ANDROIDTM based phone).
  • a network 119 such as the Internet, a local area network (“LAN”), a wide area network (“WAN”), mobile service provider network (e.g., from VERIZONTM WIRELESS), and the like.
  • Technician interface computing device 103 may be coupled to technician computing devices such as a laptop 114
  • technician interface computing device 103 may also be coupled to custom-made computing devices, conventional cell phones (i.e., dumbphones), personal computers, set top boxes, or any other communication device.
  • Technician computing devices may be useful for providing an interface for technicians to view and interact with work tickets assigned to the technician, for example accept a work ticket, decline a work ticket, update the status of a work ticket, and the like. Exemplary user interfaces are discussed below with reference to FIGS. 3A-B and 4 A-D.
  • Technician computing devices may also provide routing instructions relating to a work ticket (e.g., by showing directions on a map), provide a technician with access to allied and existing systems (e.g., provide access to a payroll or time entry system), and the like.
  • network 119 may be a private network. For example, for a WFMS 101 configured to manage a workforce of security personnel it may be desirable to transmit classified data only over a secure, private network.
  • WFMS 101 also may include a vehicle tracking computing device 104 configured to track one or more vehicles 116 , such as work trucks driven by technicians. Each vehicle 116 may be equipped with one or more sensors configured to determine the vehicle's location and transmit the location to vehicle tracking computing device 104 .
  • vehicle 116 may be equipped with a Global Positioning System (“GPS”) sensor configured to receive signals from plural GPS satellites 117 to determine its position.
  • GPS Global Positioning System
  • Vehicle 116 may be operatively coupled to vehicle tracking computing device 104 , for example over a radio frequency connection, such as over a mobile service provider network or other network connection. Vehicle 116 may transmit various data to vehicle tracking computing device 104 , for example the location of the vehicle.
  • the vehicle may transmit any additional information, such as diagnostic information about the vehicle 116 (e.g., a check engine indication), inventory information regarding inventory available in the vehicle 116 (e.g., inventory of replacement parts), and the like.
  • Vehicle tracking computing device 104 may store vehicle tracking information for a determined period of time.
  • WFMS 101 may be operatively coupled to an existing or allied vehicle tacking computing device via integration computing device 105 rather than, or in addition to, including vehicle tracking computing device 104 .
  • WFMS 101 may also include a mapping integration computing device 106 configured to integrate map information from one or more map services 114 with workforce management computing device 102 .
  • Mapping integration computing device 106 may be coupled to one or more map services 114 , such as GOOGLETM MAPS services, ESRITM ARCGISTM online services, YAHOO!TM MAPS services, MICROSOFTTM BINGTM MAPS services, and the like, for example over an Application Programming Interface (“API”) via network 115 .
  • Maps 114 such as GOOGLETM MAPS services, ESRITM ARCGISTM online services, YAHOO!TM MAPS services, MICROSOFTTM BINGTM MAPS services, and the like, for example over an Application Programming Interface (“API”) via network 115 .
  • Mapping integration computing device 106 may include mapping information in a GIS, for example using ESRITM ARCSDETM.
  • Mapping integration computing device 106 may include a Feature Manipulation Engine (“FME”), an integrated collection of spatial extract, transform, and load (“ETL”) tools for spatial data transformation and translation.
  • FME Feature Manipulation Engine
  • ETL spatial extract, transform, and load
  • Mapping integration computing device 106 may use an FME to convert spatial data from a Spatial Database Engine (“SDE”) format to Keyhole Mark-up Language (“KML”), an eXtensible Markup Language (“XML”) schema for expressing geographic annotation and visualization within Internet-based, two-dimensional maps and three-dimensional Earth browsers, such as the services provided by GOOGLETM MAPS.
  • KML may be useful for inserting objects, such as overlays, images, icons, and the like, into a map.
  • the objects may correspond to service requests, the current location of technicians, warehouses or other locations for technicians to resupply, and the like.
  • alternative embodiments may utilize alternative engines or systems other than FTE.
  • an embodiment may integrate a map into a webpage or application via the mapping services like GOOGLETM MAPS API, BINGTM MAPS API, and the like.
  • Such embodiments may overlay various data points and objects on the map corresponding to technician locations, truck locations, technician service areas, work locations, warehouses, offices, and the like.
  • the various data points and objects may be selectable so that a user, such as a technician, may determine which should be displayed on a user interface.
  • Data points and objects may be displayed depending on a profile of each user. For example, a technician's profile may provide that only work tickets assigned to that technician should be displayed on the technician's user interface while a dispatcher's profile may provide that all technicians' locations should be displayed on the dispatcher's user interface.
  • FIG. 1 shows WFMS 101 comprising several independent computing devices
  • alternative embodiments may include one or more computing devices implementing WFMS 101 .
  • Such embodiments may execute modules corresponding to the various computing device shown in WFMS 101 .
  • FIG. 2 shows an exemplary WFMS architecture 200 having a WFMS subsystem 210 operatively coupled to a maps API 230 .
  • a user 205 may place a request for customer service with a customer care subsystem 215 .
  • a user 205 having problems with their internet service provider may call a service number to place a service request.
  • a call center operator may then enter the service request into the customer care system 215 .
  • a user 205 may enter a service request directly into the customer care subsystem, for example through a web interface.
  • customer care subsystem 215 may receive service requests from a user 205 in any fashion.
  • customer care subsystem 215 may classify the service request, convert the service request into a service ticket (i.e., a trouble ticket or a work ticket) in an appropriate format for WFMS subsystem 210 , and forward the service ticket to WFMS subsystem 210 .
  • a service ticket i.e., a trouble ticket or a work ticket
  • the service ticket may be reclassified according to the service area, the ticket type, and the priority and then allocated to one or more field operatives.
  • a local WFMS database 212 may store all service tickets.
  • the service tickets may, for example, be stored in a job assignment table with a ticket status field initially being updated to “open” to indicate that the ticket is awaiting allocation to a technician.
  • a geocoder 213 within WFMS subsystem 210 may identify the service area corresponding to the service ticket. Geocoder 213 may then send a request to a maps API 230 , for example GOOGLETM MAPS API or ArcGISTM online services, to request information regarding technicians in or near the service area.
  • a mapping engine 231 may have access to local spatial data (e.g., showing service areas, real time technician locations from a technician tracking system, and the like) from a local spatial database 225 mapped to or overlaid on the mapping service's spatial data from a spatial data database 232 . Mapping engine 231 may return through maps API 230 the identity, location, and additional information regarding technicians in or near the service area.
  • a scheduler 214 within WFMS subsystem 210 may receive the information from maps API 230 and filter the information to determine which technicians in the service area have the required skills and/or supplies to handle the ticket. Next, with the technicians filtered to identify the technicians in or near the service area and having the skill set and/or supplies to respond to the type of service request, the WFMS subsystem 210 may check the priority of the ticket. If a service ticket has the highest priority, then an available technician in the service area having the requisite skill set may be assigned to the service ticket by subsystem 210 . If no available technicians in or near the service area have the requisite qualifications, then the technician in the service area with the requisite qualifications assigned to a job that is most likely to finish first may be assigned to the service ticket by subsystem 210 .
  • the nearest available technician outside the service area having the skill set, or the nearest available technician outside the service area having the skill set and most likely to complete their current task shortly may be assigned to the service ticket by subsystem 210 .
  • lower priority service tickets may be assigned dynamically to technicians in similar fashion to high priority service tickets. However, if higher priority service tickets exist in a service area, lower priority service tickets may be queued behind higher priority service tickets. Additionally, if a technician is assigned to a lower priority service ticket and has not yet arrived at the service location to do the work, the technician may be reassigned to the higher priority service ticket. In some instances, a ticket may have such high priority that one or more technicians may be reassigned even while they are working on a service ticket. For example, WFMS subsystem 210 may receive an emergency ticket and immediately (dynamically) reassign technicians to the emergency ticket. Thus, the technician assignment can be in either of two modes.
  • scheduler 214 may run to automatically assign tickets that are open (i.e., unassigned). Once the tickets start flowing in for the day (i.e., being received), dynamic scheduling may kick in and reassign technicians to tickets different from the ones already assigned. This dynamic scheduling may be based on current location of technicians and distance from the location of higher priority in addition to various parameters considered during the original scheduling.
  • Service tickets may have many different priority levels for example priority levels one to ten, with one being the highest priority and ten being the lowest.
  • WFMS subsystem 210 may be configured to increase the priority of tickets the longer they remain unassigned.
  • Priority level increases may be tied, for example, to SLA times or to the estimated time of arrival (“ETA”) of a technician that was initially given a user 205 when they placed a service request. In other words, priority may be increased after a threshold is met, for example an SLA threshold or an ETA threshold.
  • ETA estimated time of arrival
  • WFMS subsystem 210 may update records in the local WFMS database 212 to reflect the same. For example, an assignment table with a ticket status field initially may be updated to “assigned”, “in progress”, “closed”, and the like to indicate the status of the ticket. Additionally, a service ticket table in WFMS database 212 may be updated over time, for example to adjust the priority of a ticket as time passes, to remove, or otherwise flag, completed tickets, and the like.
  • WFMS application server 211 may provide a user interface (“UI”) to WFMS subsystem 211 .
  • WFMS application server 211 may provide a UI 300 as shown in FIG. 3A .
  • UI 300 may include a view details tab 301 displaying an employee table 310 and a ticket table 320 .
  • Employee table 310 may show each technician, their location, and their allocation status.
  • Employee table 310 may provide UI controls to allow a user to filter the data shown, for example a location filter 311 may be used by a user to display technicians only in or near a certain service area and an allocated filter 312 may be used by a user to display only technicians having certain allocated attributes (e.g., “available”, “allocated”, etc.).
  • Ticket table 320 may show each service ticket, the ticket type, the location, and the priority of the ticket.
  • Ticket table 320 may also include UI controls to allow a user to filter the data shown, for example a location filter 322 may be used by a user to display tickets only in a certain service area and a priority filter 323 may be used by a user to display tickets having a certain priority.
  • UI controls are shown as drop-down menus, any UI controls may be used.
  • additional or different UI controls may be implemented to allow a user to filter data in various other ways.
  • UI 300 may also include an assign employee control 324 .
  • UI 300 may be configured to allow a user to select (e.g., highlight or click on) a technician in employee table 310 , select a ticket in ticket table 320 , and select assign employee control 324 to assign the technician to the ticket.
  • an additional user interface control may allow a user to select a technician to assign to a ticket.
  • Map 330 may be a map retrieved from maps API 320 showing real time technician and service ticket indicators overlaid on an up-to-date map. Additionally, indicators on map 330 (not shown) may be displayed or hidden depending on a user's selection of various UI controls, for example location filter 311 , allocated filter 312 , location filter 322 , and priority filter 323 . Map 330 may additionally be overlaid with additional data from local spatial database 225 , for example various service areas, locations of warehouses for supplies, and the like.
  • Map 330 may additionally include various user controls 331 to allow a user to navigate (e.g., pan in various directions, zoom in or out, toggle on and off information such as traffic, satellite view, and the like, view a GOOGLETM STREETVIEW, etc.).
  • various user controls 331 to allow a user to navigate (e.g., pan in various directions, zoom in or out, toggle on and off information such as traffic, satellite view, and the like, view a GOOGLETM STREETVIEW, etc.).
  • FIG. 3B shows an exemplary add details tab 302 of UI 300 including an add employee area 340 and an add ticket area 350 .
  • Add details tab 302 may be useful, for example, for a user, such as a call center employee, to enter new work tickets and new technicians into the WFMS subsystem 210 .
  • Add employee area 340 may include multiple fields 341 for a user to input data about a technician and a UI control 342 for the user to enter the data about the technician into the WFMS subsystem 210 .
  • Add ticket area 350 may likewise include multiple fields 351 for use to input data about a work ticket and a UI control 352 for the user to enter the data about the work ticket into the WFMS subsystem 210 .
  • an object may appear overlaid on map 330 indicating the technician or work ticket. Of course, different or additional data may be entered for each technician and/or work ticket.
  • WFMS subsystem 210 may additionally provide UIs corresponding to other features.
  • FIG. 4A shows an exemplary vehicle tracking UI 410 .
  • UI 410 may include a track vehicles control area 411 configured to provide a user with controls to indicate one or more vehicles to track, toggle on and off vehicle tracking, clear the map of vehicle tracking, and the like.
  • a user may select to track a vehicle 412 .
  • a GPS sensor in vehicle 412 may track the location of vehicle 412 and a system within vehicle 412 may be configured to substantially continuously or periodically (e.g., every minute) transmit the vehicle's location to WFMS 200 of FIG. 2 .
  • WFMS 200 may update the data to overlay a map provided by a map service provider 230 to display up-to-date location information of vehicle 412 .
  • UI 410 may additionally display a vehicle trail 415 showing turn by turn path vehicle 412 travels.
  • UI 410 shows vehicle trail 415 showing the route vehicle 412 traveled after leaving a work ticket location 413 .
  • UI 410 may be useful for ensuring that a technician travels directly from one work location 413 to another work location 414 , thereby saving both time and gas and optimizing the response of the workforce.
  • Vehicle trail 415 in UI 410 shows that vehicle 412 is traveling in the opposite direction of a work location 414 , thus a dispatcher may contact the technician to inform them of the error.
  • FIG. 4B shows an exemplary WFMS statistics UI 420 .
  • WFMS statistics UI 420 may include a statistics charts control area 421 configured to provide a user with controls 422 to select one or more areas 423 of the map and statistics 424 related to the areas 423 of the map. For example, a user may select a tool 422 that allows the user to click and drag a cursor to define a rectangular area 423 on the map.
  • Statistics 424 such as a pie chart, may show statistics related to the selected area 432 .
  • the exemplary statistics 424 pie chart shown in FIG. 4B shows that the vast majority of the work orders in the selected area 432 are low priority, a smaller amount are medium priority, and a small percent are high priority.
  • Statistics charts control area 421 may additional display text 425 or other indicators with statistics, such as showing that 2.7% of the work orders are high priority.
  • UI 420 may show real time statistics in alternative formats, such as by displaying other or additional graphs or charts.
  • FIG. 4C shows an exemplary technician service area UI 430 .
  • Technician service area UI 430 may include technician service area control 431 configured to allow a user to select the technician whose service area they would like to see overlaid on the map as well as various other options related to display of the technician's service area. For example, a user may select a technician 435 and indicate that they would like to see a first service area 432 , a second service area 433 , and a third service area 434 for technician 435 .
  • a user may indicate how they would like the service areas determined, for example the first service area 432 may encompass locations the technician can drive to within 3 minutes, the second service area 433 may encompass locations the technician can drive to within 10 minutes, and the third service area may encompass locations the technician can drive to within 15 minutes.
  • the location of the technician 435 may be retrieved in real time from a vehicle tracking subsystem in or coupled to WFMS 200 .
  • a map API 230 may then be queried for locations that the technician 435 would be able to travel to within the time constraints set for the first service area 432 , the second service area 433 , and the third service area 434 .
  • maps API 230 providing ranges based on driving time rather than merely based on physical distance, WFMS 200 may optimize scheduling of technicians. For example, as shown in FIG. 4C , service areas may follow highways or roads, therefore allowing a technician proximate a major highway reach a work order location faster than another technician who may be physically closer to the work order location.
  • FIG. 4D shows an exemplary landscape UI 440 showing a GOOGLETM STREETVIEW of a location.
  • a user of any of the UIs shown in FIGS. 4A , 4 B, and 4 C may select a user control to see landscape UI 440 of a particular location on the map. This may be useful, for example, for a technician traveling to a location to confirm that the location he arrives at corresponds to the work location. This may also be useful for a technician en route to determine if they are on the right path.
  • a directions UI may be useful for providing directions to a work location to a technician.
  • WFMS 200 may request directions from a technician's real-time location to a work order location by transmitting a request for directions to a maps API 230 .
  • Maps API 230 may then return a map including the directions overlaid thereon, thereby providing a technician with turn-by-turn directions to a work order location.
  • WFMS system 200 may be useful for optimizing a technician's response route, thereby both decreasing the technician's response time as well as potentially decreasing the technician's fuel expenses.
  • WFMS system 200 may be useful for optimizing a technician's response route, thereby both decreasing the technician's response time as well as potentially decreasing the technician's fuel expenses.
  • a workforce of technicians may be optimized to provide technicians with requisite skill sets in various work areas to respond to user demand.
  • Embodiments may be implemented with software, for example modules executed on computing devices such as computing device 510 of FIG. 5 .
  • Embodiments may, for example, execute modules to implement the systems and methods disclosed herein.
  • a single step may be performed by more than one module, a single module may perform more than one step, or any other logical division of various steps disclosed herein may be used to implement the processes as software executed on a computing device.
  • Computing device 510 has one or more processing device 511 designed to process instructions, for example computer readable instructions (i.e., code) stored on a storage device 513 .
  • Storage device 513 may be any type of storage device (e.g., an optical storage device, a magnetic storage device, a solid state storage device, etc.), for example a non-transitory storage device.
  • instructions may be stored in remote storage devices, for example storage devices accessed over a network or the internet.
  • Computing device 510 additionally has memory 512 , an input controller 516 , and an output controller 515 .
  • a bus 514 operatively couples components of computing device 510 , including processor 511 , memory 512 , storage device 513 , input controller 516 , output controller 515 , and any other devices (e.g., network controllers, sound controllers, etc.).
  • Output controller 515 may be operatively coupled (e.g., via a wired or wireless connection) to a display device 520 (e.g., a monitor, television, mobile device screen, touch-display, etc.) in such a fashion that output controller 515 can transform the display on display device 520 (e.g., in response to modules executed).
  • Input controller 516 may be operatively coupled (e.g., via a wired or wireless connection) to input device 530 (e.g., mouse, keyboard, touch-pad, scroll-ball, touch-display, etc.) in such a fashion that input can be received from a user.
  • input device 530 e.g., mouse, keyboard, touch-pad, scroll-ball, touch-display, etc.
  • FIG. 5 illustrates computing device 510 , display device 520 , and input device 530 as separate devices for ease of identification only.
  • Computing device 510 , display device 520 , and input device 530 may be separate devices (e.g., a personal computer connected by wires to a monitor and mouse), may be integrated in a single device (e.g., a mobile device with a touch-display, such as a smartphone or a tablet), or any combination of devices (e.g., a computing device operatively coupled to a touch-screen display device, a plurality of computing devices attached to a single display device and input device, etc.).
  • Computing device 510 may be one or more servers, for example a farm of networked servers, a clustered server environment, or a cloud network of computing devices.
  • embodiments disclosed herein may be useful for dynamically dispatching a workforce to provide optimal services while minimizing cost.
  • workforce management systems disclosed herein may fluidly and substantially continuously reroute members of the workforce as needs change.
  • cost in creating and maintaining such a workforce management system may be substantially reduced while reliability of such a system (e.g., vintage of map information) improved.
  • Workforce management systems disclosed herein may additionally be scalable.
  • a central workforce management system may manage separate work forces (e.g., workforces for non-related companies and/or relating to non-related services).
  • work forces e.g., workforces for non-related companies and/or relating to non-related services.
  • both work tickets and technicians may be identified as corresponding to a certain business to ensure the correct technicians are assigned to the correct work tickets.
  • combined systems may be optimized for various business rules.
  • such services may include referral services or substitute services so that if the company that received a work ticket does not have the bandwidth or expertise to respond to the work ticket, they may refer the work ticket to a company who can.
  • Workforce management systems disclosed herein may be hosted by an entity in similar fashion to conventional workforce management systems, for example by having one or more computing device hosting the workforce management system located at an entity's office.
  • workforce management systems disclosed herein may be implemented according to a hosted services model.
  • a workforce management system may be offered as a service (i.e., as Software as a Service (“SaaS”)). This may allow a company to simply provide its technician, vehicle tracking, and similar data to the workforce management system over an internet connection and the workforce management system can be completely hosted and provided by a third party entity. In this fashion, even companies with meager means may be able to afford sophist acted workforce management systems.
  • SaaS Software as a Service

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Economics (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Operations Research (AREA)
  • General Business, Economics & Management (AREA)
  • Marketing (AREA)
  • Quality & Reliability (AREA)
  • Tourism & Hospitality (AREA)
  • Theoretical Computer Science (AREA)
  • Remote Sensing (AREA)
  • Radar, Positioning & Navigation (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Game Theory and Decision Science (AREA)
  • Data Mining & Analysis (AREA)
  • Automation & Control Theory (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
US13/111,472 2011-04-07 2011-05-19 Methods and systems for workforce management Abandoned US20120259540A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/754,309 US9785897B2 (en) 2011-04-07 2015-06-29 Methods and systems for optimizing efficiency of a workforce management system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN1189CH2011 IN2011CH01189A (enExample) 2011-04-07 2011-04-07
IN1189/CHE/2011 2011-04-07

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/754,309 Continuation-In-Part US9785897B2 (en) 2011-04-07 2015-06-29 Methods and systems for optimizing efficiency of a workforce management system

Publications (1)

Publication Number Publication Date
US20120259540A1 true US20120259540A1 (en) 2012-10-11

Family

ID=46966737

Family Applications (2)

Application Number Title Priority Date Filing Date
US13/111,472 Abandoned US20120259540A1 (en) 2011-04-07 2011-05-19 Methods and systems for workforce management
US14/754,309 Active 2031-06-16 US9785897B2 (en) 2011-04-07 2015-06-29 Methods and systems for optimizing efficiency of a workforce management system

Family Applications After (1)

Application Number Title Priority Date Filing Date
US14/754,309 Active 2031-06-16 US9785897B2 (en) 2011-04-07 2015-06-29 Methods and systems for optimizing efficiency of a workforce management system

Country Status (2)

Country Link
US (2) US20120259540A1 (enExample)
IN (1) IN2011CH01189A (enExample)

Cited By (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120046927A1 (en) * 2009-05-01 2012-02-23 Eric Nettleton Integrated automation system with picture compilation system
US20120166074A1 (en) * 2010-12-23 2012-06-28 Research In Motion Limited Updating map data from camera images
US20120323992A1 (en) * 2011-06-20 2012-12-20 International Business Machines Corporation Geospatial visualization performance improvement for contiguous polylines with similar dynamic characteristics
US20130159038A1 (en) * 2011-12-14 2013-06-20 Stanley Convergent Security Solutions, Inc. System and Method for Interacting With Customers
US8606611B1 (en) * 2011-10-13 2013-12-10 Intuit Inc. Scheduling via multiple dimensions including worker, time, and location
US8781865B2 (en) * 2012-08-03 2014-07-15 International Business Machines Corporation Handling consolidated tickets
US20140257895A1 (en) * 2013-03-07 2014-09-11 Sas Institute Inc. Constrained service restoration
US20140278654A1 (en) * 2013-03-15 2014-09-18 International Business Machines Corporation Spatio-temporal approach to scheduling field operations
US20150081400A1 (en) * 2013-09-19 2015-03-19 Infosys Limited Watching ARM
US20150161969A1 (en) * 2012-05-10 2015-06-11 Hitachi Construction Machinery Co., Ltd. Industrial vehicle management system
US9188453B2 (en) 2013-03-07 2015-11-17 Sas Institute Inc. Constrained service restoration with heuristics
US9382797B2 (en) 2009-05-01 2016-07-05 The University Of Sydney Integrated automation system
US20160224908A1 (en) * 2015-01-30 2016-08-04 Accenture Global Services Limited End-to-end project management
US20170256013A1 (en) * 2016-03-02 2017-09-07 Mastercard International Incorporated Systems and methods for dynamic ambulance deployment
US9916539B2 (en) 2012-06-18 2018-03-13 The University Of Sydney Systems and methods for processing geophysical data
US20180302742A1 (en) * 2017-04-14 2018-10-18 Sysmex Corporation Position management method, position management system, position management program and mobile communication apparatus
US10423907B2 (en) * 2013-10-18 2019-09-24 Salesforce.Com, Inc. Geolocation based work data on a mobile device using a database system
US10567236B2 (en) * 2017-12-18 2020-02-18 United States Of America As Represented By Secretary Of The Navy Communication assets survey and mapping, next generation
CN111768089A (zh) * 2020-06-19 2020-10-13 广东电网有限责任公司 工作票审核方法、装置、设备及存储介质
US11126939B2 (en) * 2018-12-06 2021-09-21 At&T Intellectual Property I, L.P. Telecommunication network customer premises service dispatch optimization
CN113642835A (zh) * 2021-07-01 2021-11-12 国网福建省电力有限公司 一种基于数据相似度的工作票生成方法及终端
JP2021182414A (ja) * 2015-08-14 2021-11-25 エアリス コミュニケイションズ, インコーポレイテッドAeris Communications, Inc. ユーザ定義の地理的領域に関連して装置を監視するシステムおよび方法
US20220245647A1 (en) * 2021-02-02 2022-08-04 Nice Ltd. Systems and methods to triage contact center issues using an incident grievance score
US11553655B2 (en) * 2012-05-21 2023-01-17 Smart Rain Systems, LLC Irrigation management
US20230171094A1 (en) * 2020-04-07 2023-06-01 Endress+Hauser Process Solutions Ag Method for connecting a field device to a cloud
US11684030B2 (en) 2019-04-26 2023-06-27 Smart Rain Systems, LLC Irrigation system map integration
US11684029B2 (en) 2018-01-03 2023-06-27 Smart Rain Systems, LLC Landscaper integration
US12295298B2 (en) 2022-11-30 2025-05-13 Smart Rain Systems, Lcc Devices, systems, and methods for cloud-based irrigation control
US12349023B2 (en) 2017-06-22 2025-07-01 Aeris Communications, Inc. Learning locations of interest using IoT devices
US20250307833A1 (en) * 2024-03-28 2025-10-02 Atlassian Pty Ltd Methods, apparatuses and computer program products for generating contextualized user interfaces in an integrated service and asset computing platform

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
IN2011CH01189A (enExample) * 2011-04-07 2012-10-19
US20180268704A1 (en) * 2017-03-16 2018-09-20 Allstate Insurance Company Logic Based Dispatch Control
US20190130413A1 (en) * 2017-10-30 2019-05-02 Ricoh Company, Ltd. Service ticket assignment and collaboration
US11105528B2 (en) 2017-11-15 2021-08-31 Johnson Controls Tyco IP Holdings LLP Building management system with automatic synchronization of point read frequency
CN107944618B (zh) * 2017-11-20 2020-03-20 阿里巴巴集团控股有限公司 共享车辆的布点规划方法、装置以及电子设备
US10721142B1 (en) * 2018-03-08 2020-07-21 Palantir Technologies Inc. Computer network troubleshooting
US20200210961A1 (en) 2018-12-27 2020-07-02 Clicksoftware, Inc. Systems and methods for work capacity planning
US20230057537A1 (en) * 2021-08-06 2023-02-23 At&T Intellectual Property I, L.P. Facilitating striated random restart during allocation of resources using a heuristic approach
WO2025052454A1 (en) * 2023-09-05 2025-03-13 Unisteps It Solutions Private Limited System and method for an enterprise resource planning (erp)
CN118761602B (zh) * 2024-09-03 2025-03-25 深圳轻喜到家科技有限公司 家政人员工作状态检测方法及系统

Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5920846A (en) * 1996-02-27 1999-07-06 Southwestern Bell Telephone Co. Method and system for processing a service request relating to installation, maintenance or repair of telecommunications services provided to a customer premises
US20020035493A1 (en) * 2000-01-04 2002-03-21 Bahram Mozayeny Method and system for coordinating appointments
US6415259B1 (en) * 1999-07-15 2002-07-02 American Management Systems, Inc. Automatic work progress tracking and optimizing engine for a telecommunications customer care and billing system
US20050222762A1 (en) * 2004-03-31 2005-10-06 International Business Machines Corporation Method and system for automated incident traffic reporting and dynamic routing
US6990458B2 (en) * 1997-08-28 2006-01-24 Csg Systems, Inc. System and method for computer-aided technician dispatch and communication
US7069333B1 (en) * 1999-08-13 2006-06-27 Fieldcentrix, Inc. Method and systems for wireless communication for a field service system
US20060148492A1 (en) * 2000-09-27 2006-07-06 Arkray, Inc. Position information system and dispatch support system
US20070179829A1 (en) * 2006-01-27 2007-08-02 Sbc Knowledge Ventures, L.P. Method and apparatus for workflow scheduling and forecasting
US7346531B2 (en) * 2000-03-31 2008-03-18 Mdsi Software Srl Methods and systems for scheduling complex work orders for a workforce of mobile service technicians
US7464046B2 (en) * 2003-07-15 2008-12-09 At&T Intellectual Properties I, L.P. Dispatch and service support system
US20090171718A1 (en) * 2008-01-02 2009-07-02 Verizon Services Corp. System and method for providing workforce and workload modeling
US20090204470A1 (en) * 2008-02-11 2009-08-13 Clearshift Corporation Multilevel Assignment of Jobs and Tasks in Online Work Management System
US20100312604A1 (en) * 2009-06-09 2010-12-09 Accenture Global Service Gmbh Technician control system
US20110098918A1 (en) * 2009-10-28 2011-04-28 Google Inc. Navigation Images
US20110112943A1 (en) * 2009-11-09 2011-05-12 Dietz Jay B Location-based mobile workforce management system
US20110119101A1 (en) * 2009-11-13 2011-05-19 Accenture Global Services Gmbh Case Management Services
US20110213634A1 (en) * 2010-03-01 2011-09-01 Business Equipment Information Services, Inc. System and method for effective workload distribution for service technicians
US20120191665A1 (en) * 2011-01-20 2012-07-26 Southern Company Services, Inc. Integrated Distribution Management System Channel Adapter

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040203854A1 (en) * 2002-04-26 2004-10-14 Nowak Steven P. Formatting location information based on output device specifications
US9359880B2 (en) * 2011-04-07 2016-06-07 Infosys Limited Methods and systems for managing underground assets
IN2011CH01189A (enExample) * 2011-04-07 2012-10-19
US8600956B2 (en) * 2011-08-16 2013-12-03 Nokia Corporation Method, apparatus and computer program product for providing conflicting point of interest information

Patent Citations (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5920846A (en) * 1996-02-27 1999-07-06 Southwestern Bell Telephone Co. Method and system for processing a service request relating to installation, maintenance or repair of telecommunications services provided to a customer premises
US6990458B2 (en) * 1997-08-28 2006-01-24 Csg Systems, Inc. System and method for computer-aided technician dispatch and communication
US6415259B1 (en) * 1999-07-15 2002-07-02 American Management Systems, Inc. Automatic work progress tracking and optimizing engine for a telecommunications customer care and billing system
US7069333B1 (en) * 1999-08-13 2006-06-27 Fieldcentrix, Inc. Method and systems for wireless communication for a field service system
US20020035493A1 (en) * 2000-01-04 2002-03-21 Bahram Mozayeny Method and system for coordinating appointments
US7346531B2 (en) * 2000-03-31 2008-03-18 Mdsi Software Srl Methods and systems for scheduling complex work orders for a workforce of mobile service technicians
US20060148492A1 (en) * 2000-09-27 2006-07-06 Arkray, Inc. Position information system and dispatch support system
US7464046B2 (en) * 2003-07-15 2008-12-09 At&T Intellectual Properties I, L.P. Dispatch and service support system
US20050222762A1 (en) * 2004-03-31 2005-10-06 International Business Machines Corporation Method and system for automated incident traffic reporting and dynamic routing
US20070179829A1 (en) * 2006-01-27 2007-08-02 Sbc Knowledge Ventures, L.P. Method and apparatus for workflow scheduling and forecasting
US20090171718A1 (en) * 2008-01-02 2009-07-02 Verizon Services Corp. System and method for providing workforce and workload modeling
US20090204470A1 (en) * 2008-02-11 2009-08-13 Clearshift Corporation Multilevel Assignment of Jobs and Tasks in Online Work Management System
US20100312604A1 (en) * 2009-06-09 2010-12-09 Accenture Global Service Gmbh Technician control system
US20110098918A1 (en) * 2009-10-28 2011-04-28 Google Inc. Navigation Images
US20110112943A1 (en) * 2009-11-09 2011-05-12 Dietz Jay B Location-based mobile workforce management system
US20110119101A1 (en) * 2009-11-13 2011-05-19 Accenture Global Services Gmbh Case Management Services
US20110213634A1 (en) * 2010-03-01 2011-09-01 Business Equipment Information Services, Inc. System and method for effective workload distribution for service technicians
US20120191665A1 (en) * 2011-01-20 2012-07-26 Southern Company Services, Inc. Integrated Distribution Management System Channel Adapter

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"How Far Can I Travel HTML Source," http://www.freemaptools.com/how-far-can-i-travel.htm, as archived on Mar. 30, 2010 *

Cited By (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9297256B2 (en) * 2009-05-01 2016-03-29 The University Of Sydney Integrated automation system with picture compilation system
US20120046927A1 (en) * 2009-05-01 2012-02-23 Eric Nettleton Integrated automation system with picture compilation system
US9382797B2 (en) 2009-05-01 2016-07-05 The University Of Sydney Integrated automation system
US20120166074A1 (en) * 2010-12-23 2012-06-28 Research In Motion Limited Updating map data from camera images
US9429438B2 (en) * 2010-12-23 2016-08-30 Blackberry Limited Updating map data from camera images
US20120323992A1 (en) * 2011-06-20 2012-12-20 International Business Machines Corporation Geospatial visualization performance improvement for contiguous polylines with similar dynamic characteristics
US8694603B2 (en) * 2011-06-20 2014-04-08 International Business Machines Corporation Geospatial visualization performance improvement for contiguous polylines with similar dynamic characteristics
US20140181189A1 (en) * 2011-06-20 2014-06-26 International Business Machines Corporation Geospatial visualization performance improvement for contiguous polylines with similar dynamic characteristics
US9635137B2 (en) * 2011-06-20 2017-04-25 International Business Machines Corporation Geospatial visualization performance improvement for contiguous polylines with similar dynamic characteristics
US8606611B1 (en) * 2011-10-13 2013-12-10 Intuit Inc. Scheduling via multiple dimensions including worker, time, and location
US20130159038A1 (en) * 2011-12-14 2013-06-20 Stanley Convergent Security Solutions, Inc. System and Method for Interacting With Customers
US10319347B2 (en) 2012-05-10 2019-06-11 Hitachi Construction Machinery Co., Ltd. Industrial vehicle management system
US20150161969A1 (en) * 2012-05-10 2015-06-11 Hitachi Construction Machinery Co., Ltd. Industrial vehicle management system
US11553655B2 (en) * 2012-05-21 2023-01-17 Smart Rain Systems, LLC Irrigation management
US9916539B2 (en) 2012-06-18 2018-03-13 The University Of Sydney Systems and methods for processing geophysical data
US8781865B2 (en) * 2012-08-03 2014-07-15 International Business Machines Corporation Handling consolidated tickets
US20140257895A1 (en) * 2013-03-07 2014-09-11 Sas Institute Inc. Constrained service restoration
US9188453B2 (en) 2013-03-07 2015-11-17 Sas Institute Inc. Constrained service restoration with heuristics
US20140278654A1 (en) * 2013-03-15 2014-09-18 International Business Machines Corporation Spatio-temporal approach to scheduling field operations
US11880790B2 (en) * 2013-03-15 2024-01-23 Utopus Insights, Inc. Spatio-temporal approach to scheduling field operations
US20150081400A1 (en) * 2013-09-19 2015-03-19 Infosys Limited Watching ARM
US10423907B2 (en) * 2013-10-18 2019-09-24 Salesforce.Com, Inc. Geolocation based work data on a mobile device using a database system
US10198702B2 (en) * 2015-01-30 2019-02-05 Acccenture Global Services Limited End-to end project management
US20160224908A1 (en) * 2015-01-30 2016-08-04 Accenture Global Services Limited End-to-end project management
JP2021182414A (ja) * 2015-08-14 2021-11-25 エアリス コミュニケイションズ, インコーポレイテッドAeris Communications, Inc. ユーザ定義の地理的領域に関連して装置を監視するシステムおよび方法
US20170256013A1 (en) * 2016-03-02 2017-09-07 Mastercard International Incorporated Systems and methods for dynamic ambulance deployment
US10600137B2 (en) * 2016-03-02 2020-03-24 Mastercard International Incorporated Systems and methods for dynamic ambulance deployment
US20180302742A1 (en) * 2017-04-14 2018-10-18 Sysmex Corporation Position management method, position management system, position management program and mobile communication apparatus
US10623886B2 (en) * 2017-04-14 2020-04-14 Sysmex Corporation Position management method, position management system, and position management program providing position information to server using mobile communication apparatus carried by user in vehicle
US12349023B2 (en) 2017-06-22 2025-07-01 Aeris Communications, Inc. Learning locations of interest using IoT devices
US10567236B2 (en) * 2017-12-18 2020-02-18 United States Of America As Represented By Secretary Of The Navy Communication assets survey and mapping, next generation
US12464992B2 (en) 2018-01-03 2025-11-11 Smart Rain Systems, LLC Landscaper integration
US11684029B2 (en) 2018-01-03 2023-06-27 Smart Rain Systems, LLC Landscaper integration
US11126939B2 (en) * 2018-12-06 2021-09-21 At&T Intellectual Property I, L.P. Telecommunication network customer premises service dispatch optimization
US12324381B2 (en) 2019-04-26 2025-06-10 Smart Rain Systems, LLC Irrigation system map integration
US11684030B2 (en) 2019-04-26 2023-06-27 Smart Rain Systems, LLC Irrigation system map integration
US12231554B2 (en) * 2020-04-07 2025-02-18 Endress+Hauser Process Solutions Ag Method for connecting a field device to a cloud
US20230171094A1 (en) * 2020-04-07 2023-06-01 Endress+Hauser Process Solutions Ag Method for connecting a field device to a cloud
CN111768089A (zh) * 2020-06-19 2020-10-13 广东电网有限责任公司 工作票审核方法、装置、设备及存储介质
US20220245647A1 (en) * 2021-02-02 2022-08-04 Nice Ltd. Systems and methods to triage contact center issues using an incident grievance score
US12333553B2 (en) * 2021-02-02 2025-06-17 Nice Ltd. Systems and methods to triage contact center issues using an incident grievance score
CN113642835A (zh) * 2021-07-01 2021-11-12 国网福建省电力有限公司 一种基于数据相似度的工作票生成方法及终端
US12295298B2 (en) 2022-11-30 2025-05-13 Smart Rain Systems, Lcc Devices, systems, and methods for cloud-based irrigation control
US20250307833A1 (en) * 2024-03-28 2025-10-02 Atlassian Pty Ltd Methods, apparatuses and computer program products for generating contextualized user interfaces in an integrated service and asset computing platform

Also Published As

Publication number Publication date
IN2011CH01189A (enExample) 2012-10-19
US9785897B2 (en) 2017-10-10
US20150302346A1 (en) 2015-10-22

Similar Documents

Publication Publication Date Title
US20120259540A1 (en) Methods and systems for workforce management
Balcik et al. Last mile distribution in humanitarian relief
US20230342708A1 (en) Integrated multi-location scheduling, routing, and task management
Abdelmagid et al. A comprehensive review of the truck appointment scheduling models and directions for future research
US8612276B1 (en) Methods, apparatus, and systems for dispatching service technicians
US20230153936A1 (en) Systems and methods for transportation staffing
US20120239452A1 (en) Fleet Management Systems and Processes
US20140278652A1 (en) Hybrid system and method for selecting and deploying field technicians in a facilities management hybrid workforce
US20230088950A1 (en) Method and system for intelligent load optimization for vehicles
US10181111B1 (en) Electronic device communications for item handoffs
JP5961848B2 (ja) 計画管理システム及び計画管理方法
US20190220785A1 (en) Delivery route management and optimization
US20180314998A1 (en) Resource Allocation in a Network System
Butler et al. Integrating information technology and operational research in the management of milk collection
Hill et al. A decision support system for improved resource planning and truck routing at logistic nodes
US20140122164A1 (en) System and method for analyzing commuting metrics
Antonio et al. An advanced planner for urban freight delivering
CA3053089A1 (en) Dynamic selection of geo-based service options in a network system
US20150120353A1 (en) User interface elements and computer method for a team leader homepage
US11982537B2 (en) Systems and methods for generating dynamic transit routes
US11808589B1 (en) Dynamic allocation of resources used in delivery
WO2020185442A1 (en) Computerized vehicle delivery coordination
CN106201154A (zh) 基于hmi的三维可视化服务引擎及其运行方法
US20220237639A1 (en) System and method for data prediction using heat maps
Iordache et al. Project management expert system with advanced document management for public institutions

Legal Events

Date Code Title Description
AS Assignment

Owner name: INFOSYS TECHNOLOGIES LIMITED, INDIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KISHORE, PRADEEP;NARAYAN, VISVANATHAN LAKSHMI;REEL/FRAME:026846/0039

Effective date: 20110628

AS Assignment

Owner name: INFOSYS LIMITED, INDIA

Free format text: CHANGE OF NAME;ASSIGNOR:INFOSYS TECHNOLOGIES LIMITED;REEL/FRAME:027056/0826

Effective date: 20110616

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION