FIELD OF THE DISCLOSURE

[0001] The present disclosure generally relates to systems and methods for worksite optimization. More particularly, the present disclosure relates to worksite optimization using a graphical user interface to access and communicate a weekly target objective, weekly planned activities, completed weekly planned activities and work package data by and between different project supervisors. The weekly planned activities and completed weekly planned activities are hourly based and may be easily compared to the hourly based weekly target objective to determine if the weekly target objective is met in planning and completion of the weekly activities.

BACKGROUND

[0002] Conventional systems and methods for worksite optimization rely heavily on manual processes with very little consistency, transparency and accountability. For example, work packages, each of which represents a scope of work and includes a written description of materials, assembly/installation instructions, drawings and required hours to complete, are printed, manually assembled into respective binders and assigned to respective superintendents. Each superintendent assigns a general foreman who retrieves and reviews the assigned work package(s). Weekly target objectives established at the superintendent level are communicated to the general foreman, however, are rarely communicated in detail to the foremen under the general foreman. In addition, multiple foremen may also work on the same work package without knowing their collective responsibilities for completing the work package. The lack of communication in this conventional worksite approach leads to a lack of accountability between foremen. More importantly, weekly target objectives are typically communicated in the quantity (e.g. linear feet) of product to assemble and install rather than the number of work hours available in a week. The disadvantage is that the same quantity of various products often requires a different number of w ^r ork hours. Also, planning weekly activities is often relegated to a single supervisor without communication to others. A comparison of the weekly planned activities and the weekly target objective is thus, either overlooked or highly isolated and manual, which makes planning the weekly activities to meet the weekly target objective much more difficult. The current worksite approach therefore, often results in multiple project inefficiencies.

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] The present disclosure is described with reference to the accompanying drawings, in which like elements are referenced with like reference numbers, and in which:

[0004] FIGS. I A- I B are a flow diagram illustrating one embodiment of a method for implementing the present disclosure.

[0005] FIGS. 2A-2C are displays illustrating one embodiment of a graphical user interface (GUI) for performing steps 106, 108, 110, 114 and 116 in FIGS. 1A-1B.

[0006] FIG. 3 is a block diagram illustrating one embodiment of a computer system for implementing the present disclosure.

DETAILED DESCRIPTION OF THE ILLUSTRATIVE EMBODIMENTS [0007] The subject matter of the present disclosure is described with specificity, however, the description itself is not intended to limit the scope of the disclosure. The subject matter thus, might also be embodied in other ways, to include different structures, steps and/or combinations similar to and/or fewer than those described herein, in conjunction with other present or future technologies. Although the term "step" may be used herein to describe different elements of methods employed, the term should not be interpreted as implying any particular order among or between various steps herein disclosed unless otherwise expressly limited by the description to a particular order. Other features and advantages of the disclosed embodiments will be or will become apparent to one of ordinary skill in the art up examination of the following figures and detailed description. It is intended that all such additional features and advantages be included within the scope of the disclosed embodiments. Further, the illustrated figures are only exemplary and are not intended to assert or imply any limitation with regard to the environment, architecture, design, or process in which different embodiments may be implemented.

[0008] The systems and methods of the present disclosure overcome one or more of the prior art disadvantages by using a graphical user interface to access and communicate a weekly target objective, weekly planned activities, completed weekly planned activities and work package data by and between different project supervisors. The weekly planned activities and completed weekly planned activities are hourly based and may be easily compared to the hourly based weekly target objective to determine if the weekly target objective is met in planning and completion of the weekly activities.

[0009] In one embodiment, the present disclosure includes a method for worksite optimization, which comprises, a) receiving at least one of a weekly target objective and one or more newly assigned work packages into an electronic database, wherein the weekly target objective represents a predetermined number of hours available for work in a current week; b) selecting one or more work packages from the one or more newly assigned work packages using a graphical user interface, wherein each work package represents a predetermined scope of work and a predetermined number of hours required to complete the scope of work; c) planning one or more weekly activities for completing the scope of work represented by the selected work package(s) using the graphical user interface, wherein each weekly planned activity includes a predetermined number of hours required to complete a respective weekly planned activity and a total number of predetermined hours for the one or more weekly planned activities is at least equal to the predetermined number of hours available for work in the current week represented by the weekly target objective; d) initiating the one or more weekly planned activities by performing one or more of the weekly planned activities in the current week; e) identifying one or more of the one or more w ^r eekly planned activities that are completed within the current week using the graphical user interface; and f) repeating steps (a) - (e) for another current week until each newly assigned work package is complete based upon the one or more completed weekly planned activities.

[0010] In another embodiment, the present disclosure includes a non- transitory program carrier device tangibly carrying computer-executable instructions for worksite optimization, the instructions being executable to implement: a) receiving at least one of a weekly target objective and one or more newly assigned work packages into an electronic database, wherein the weekly target objective represents a predetermined number of hours available for work in a current week; b) selecting one or more work packages from the one or more newly assigned work packages using a graphical user interface, wherein each work package represents a predetermined scope of work and a predetermined number of hours required to complete the scope of work; c) planning one or more weekly activities for completing the scope of work represented by the selected work package(s) using the graphical user interface, wherein each weekly planned activity includes a predetermined number of hours required to complete a respective weekly planned activity and a total number of predetermined hours for the one or more weekly planned activities is at least equal to the predetermined number of hours available for work in the current week represented by the weekly target objective: d) initiating the one or more weekly planned activities by performing one or more of the weekly planned activities in the current week; e) identifying one or more of the one or more weekly planned activities that are completed within the current week using the graphical user interface; and f) repeating steps (a) - (e) for another current week until each newly assigned work package is complete based upon the one or more completed weekly planned activities.

[001 1] In yet another embodiment, the present disclosure includes a method for displaying worksite information on a graphical user interface for a project supervisor, which comprises: i) dynamically displaying a weekly target objective and a total number of newly assigned work packages in a work packages tab, wherein the weekly target objective represents a predetermined number of hours available for work in a current week and each work package represents a predetermined scope of work and a predetermined number of hours required to complete the scope of work; ii) interactively linking the work packages tab to a work packages field that identifies each new ^r ly assigned work package; iii) dynamically displaying a total number of hours planned for completing one or more weekly planned activities in the current week, wherein each weekly planned activity includes a predetermined number of hours required to complete a respective weekly planned activity and the total number of hours planned is based on the weekly target objective and one or more work packages selected from the total number of newly assigned work packages; and iv) dynamically displaying a total number of hours earned for completing one or more of the one or more weekly planned activities.

[0012] Referring now to FIGS. 1A-1B, a flow diagram illustrates one embodiment of a method 100 for implementing the present disclosure. The method 100 may be used on various and different worksites where worksite optimization is based on direct hours, which may include concrete and civil work, installation of structural steel and piping, electrical raceway/cable and mechanical equipment.

[0013] In step 102, a weekly target objective and/or one or more newly assigned work packages for a project supervisor are received as input to the method 100. Each work package represents a scope of work and includes the number of hours required to complete the scope of work. The weekly target objective represents the number of man-hours available for work in a week for the project workers under the control of the project supervisor, which are referred to as the supervisor's crew. The weekly target objective may be calculated as the number of project workers under the control of the pro ject supervisor multiplied times the number of project work hours in a week (e.g. 56, which may vary) multiplied times a pooled resource uplift percentage. The pooled resource uplift percentage is greater than 100% and represents pooled specialty workers that may be needed across different work packages. The weekly target objective may change week to week depending on the number of project workers under the control of the project supervisor. Thus, with each weekly iteration of this step, the weekly target objective may be the same or different. Likewise, there may be no more newly assigned work packages for a project supervisor after the first iteration of this step. The first iteration of this step however, will always include a weekly target objective and one or more newly assigned work packages for a project supervisor.

[0014] In step 104, the method 100 determines if all newly assigned work packages received in step 102 are complete based on the completion of weekly planned activities identified in step 114 after the first iteration of the method 100. If all newly assigned work packages received in step 102 are complete, then the method 100 ends. Otherwise, the method 100 proceeds to step 106.

[0015] In step 106, a work package is selected from the newly assigned work packages received in step 102 using a GUI and the client interface/video interface described further in reference to FIG. 3. More than one work package may be required for selection when a single work package does not have enough scope of work (hours) to meet the weekly target objective received in step 102. The work package(s) may be selected from the same newly assigned work packages received in the first iteration of step 102 (to the extent they are not completed) or from newly assigned work packages received in subsequent iterations of step 102. hi FIGS. 2A-2C, three displays illustrate one embodiment of a GUI for performing this step. The GUI in FIGS. 2A-2B refers to a dashboard and provides general details for the worksite project. The GUI in FIG. 2C provides more detail for newly assigned work package(s) for the worksite project. The GUI only includes data for a particular project supervisor (e.g. George Polanco). The data displayed for the GUI in FIGS. 2A-2B includes a crew ^r tab 202, a w ^r ork packages tab 204 a blocks tab 206, an hours planned tab 208, an hours earned tab 210, a cost PF tab 212, a current hour's tab 214 and an ideal hours tab 216. The crew tab 202 identifies the number of crew members (8) under the supervision of the project supervisor, which is linked to a crew field 218 that identifies each crew member by name picture and title. The work packages tab 204 identifies the total number of newly assigned work packages (36) received in step 102 and the total hours (31205) required to complete the scope of work represented by the total number of newly assigned work packages. The work packages tab 204 is linked to a work packages field 220 that identifies each assigned work package by number and its completion percentage, current performance factor (PF), date range (for weekly planned activities), materials status and block status. The current PF represents the actual hours worked on the work package divided by the hours earned for the work package. A current PF greater than 1 represents more hours worked than hours earned, which flags inefficiency. The blocks tab 206 identifies the total work stoppages for newly assigned work packages. The hours earned tab 210 identifies the hours earned each work w ^r eek (e.g. Monday-Sunday) and the total hours (461) required to meet the weekly target objective received in step 102. Thus, one or more work packages may be selected from the work packages tab 204 using the work packages field 220 to identify the work package(s) with enough scope of work (hours) to meet or exceed the weekly target objective. The current hours tab 214 identifies the total hours (31205) required to complete the scope of work represented by the total number of newly assigned work packages. The ideal hours tab 216 identifies the hours (461) required to meet the weekly target objective, the maximum hours (692) for weekly planned activities that may exceed the weekly target objective and the preferred hours (1383) assigned. The maximum hours for weekly planned activities should exceed the weekly target objective and is preferably no more than 1.5 times the weekly target objective. And, the preferred hours assigned is approximately no more than 3 times the weekly target objective. The cost PF tab 212 identifies the cost performance factor for the newly assigned work packages and represents actual hours worked divided by hours earned.

[0016] In step 108, one or more weekly activities are planned for completing the scope of work represented by the work package(s) selected in step 106 using the GUI and the client interface/video interface described further in reference to FIG. 3. Each weekly planned activity includes the number of hours required to complete the respective weekly planned activity. The weekly planned activities for any given week, should therefore, include enough hours (hours planned) to meet the weekly target objective received in step 102. The hours planned tab 208 for the GUI in FIGS. 2A-2B identifies the hours planned (501) for the current weekly planned activities. The GUI in FIG. 2C may be used to plan the weekly activities by linking from a selected work package in another work package field 222 to the scope of work represented by the selected work package. In this manner, the scope of work may be used to include enough hours (hours planned) to meet the weekly target objective. The scope of work represented by the selected work package includes another crew field 224 that identifies each crew member by name picture and title for the selected work package, a status field 226 for the selected work package, a work package notification field 228, a drawings field 230 for the selected work package and a burn chart field 232 for the selected work package. The status field 226 includes data for the selected work package, which may include the blocks (work stoppages), the materials on site, the material withdrawal requests (MWR), the hours planned, the completion percentage, the hours earned out of the total hours assigned to the selected work package and the current PF for the selected work package. The burn chart field 232 graphically illustrates the current PF for the selected work package over time.

[0017] In step 110, the method 100 determines if the weekly planned activities (hours planned) for the current week in step 108 are greater than or equal to the weekly target objective received in step 102 using the GUI and the client interface/video interface described further in reference to FIG. 3. If the weekly planned activities for the current week are not greater than or equal to the weekly target objective, then the method 100 returns to step 108 to plan additional weekly activities for the current week. Otherwise, the method 100 proceeds to step 112. The GUI in FIGS. 2A-2B may be used to compare the weekly planned activities (hours planned) for the current week identified in the hours planned tab 208 and the weekly target objective identified in the hours earned tab 210. Because the weekly planned activities (hours planned) for the current week (501) identified in the hours planned tab 208 are greater than the weekly target objective (461) identified in the hours earned tab 210, the method 100 would proceed to step 112.

[0018] hi step 112, the w ^r eekly planned activities in step 108 are initiated for the current week. The weekly planned activities are initiated by performing one or more of the weekly planned activities in a work week such as, for example, assembly and installation of structural steel and piping at a worksite.

[0019] In step 114, the weekly planned activities in step 108 that are completed after step 112 within the work week (hours earned) are identified using the GUI and the client interface/video interface described further in reference to FIG. 3. The GUI in FIGS. 2A-2B may be used to identify the weekly planned activities that are completed within the work week (hours earned) in the hours earned tab 210. This tab may be used to input completion of each weekly planned activity that represents the hours earned and not the actual hours worked. Tims, the actual hours worked in any given work week may be more or less than the hours earned. A timesheet tab in the GUI may be used to input the actual hours worked, which impacts the current PF.

[0020] In step 116, the method 100 determines if the weekly planned activities identified in step 114 as completed (hours earned) are greater than or equal to the weekly target objective received in step 102 using the GUI and the client interface/video interface described further in reference to FIG. 3. This step is therefore, typically performed at the end of a work week. If the completed weekly planned activities are not greater than or equal to the weekly target objective, then the method 100 returns to step 102. Otherwise, the method 100 proceeds to step 118. The GUI in FIGS. 2A-2B may be used to quickly determine if the completed weekly planned activities (hours earned) in the hours earned tab 210 are greater than or equal to the weekly target objective also identified in the hours earned tab 210.

[0021] In step 118, a score is determined that represents the cumulative number of current work weeks the weekly target objective is achieved (met or exceeded) by the completed weekly planned activities. The method 100 then returns to step 102.

[0022] The GUI in FIGS 2A-2B also includes a notifications field 234, a safety cross field 236 and a schedule field 238. The notifications field 234 may be used to provide weekly updates on any of the work package data in the GUI. The safety cross field 236 may be used to compile a daily record of events impacting crew safety during any work week and rank the safety impact of the event. And, the schedule field 238 may be used as a guide to planning the weekly activities in step 108. The schedule field 238 includes newly assigned work packages and their start/stop dates scheduled in advance by a supervisor. Thus, weekly planned activities preferably take into account the scheduled start/stop dates for the work packages they cover.

[0023] The method 100 may be used on various and different worksites where worksite optimization is based on direct hours, which may include concrete and civil work, installation of structural steel and piping, electrical raceway/cable and mechanical equipment. The method 100 may also be used for engineering production management, assignment of missions, planning of activities and completing objectives.

[0024] The present disclosure may be implemented through a computer-executable program of instructions, such as program modules, generally referred to as software applications or application programs executed by a computer. The software may include, for example, routines, programs, objects, components and data structures that perform particular tasks or implement particular abstract data types. The software forms an interface to allow a computer to react according to a source of input. A worksite database may be used as an interface application to implement the present disclosure. The software may also cooperate with other code segments to initiate a variety of tasks in response to data received in conjunction with the source of the received data. The software may be stored and/or carried on any variety of memory such as CD- ROM, magnetic disk, bubble memory and semiconductor memory (e.g. various types of RAM or ROM). Furthermore, the software and its results may be transmitted over a variety of carrier media such as optical fiber, metallic wire and/or through any of a variety of networks, such as the Internet.

[0025] Moreover, those skilled in the art will appreciate that the disclosure may be practiced with a variety of computer-system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable-consumer electronics, minicomputers, mainframe computers, and the like. Any number of computer-systems and computer networks are acceptable for use with the present disclosure. The disclosure may be practiced in distributed-computing environments where tasks are performed by remote- processing devices that are linked through a communications network, hi a distributed- computing environment, program modules may be located in both local and remote computer- storage media including memory storage devices. The present disclosure may therefore, be implemented in connection with various hardware, software or a combination thereof, in a computer system or other processing system.

[0026] Referring now to FIG. 3, a block diagram illustrates one embodiment of a system for implementing the present disclosure on a computer. The system includes a computing unit, sometimes referred to as a computing system, which contains memory, application programs, a client interface, a video interface, and a processing unit. The computing unit is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the disclosure.

[0027] The memory primarily stores the application programs, which may also be described as program modules containing computer-executable instructions, executed by the computing unit for implementing the present disclosure described herein and illustrated in FIGS. lA-lB and 2A-2C. The memory therefore, includes a worksite optimization module, which enables steps 102-118 described in reference to FIGS. 1A-1B. The worksite optimization module may integrate functionality from the remaining application programs illustrated in FIG. 3. In particular, the worksite database may be used as an interface application to provide the weekly target objective and/or one or more newly assigned work packages received in step 102. Although the worksite database may be used as interface application, other interface applications may be used, instead, or the worksite optimization module may be used as a stand-alone application.

[0028] Although the computing unit is shown as having a generalized memory, the computing unit typically includes a variety of computer readable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. The computing system memory may include computer storage media in the form of volatile and/or nonvolatile memory such as a read only memory (ROM) and random access memory (RAM). A basic input output system (BIOS), containing the basic routines that help to transfer information between elements within the computing unit, such as during start-up, is typically stored in ROM. The RAM typically contains data and/or program modules that are immediately accessible to, and/or presently being operated on, the processing unit. By way of example, and not limitation, the computing unit includes an operating system, application programs, other program modules, and program data.

[0029] The components shown in the memory may also be included in other removable/nonremovable, volatile/nonvolatile computer storage media or they may be implemented in the computing unit through an application program interface ("API") or cloud computing, which may reside on a separate computing unit connected through a computer system or network. For example only, a hard disk drive may read from or write to nonremovable, nonvolatile magnetic media, a magnetic disk drive may read from or write to a removable, nonvolatile magnetic disk, and an optical disk drive may read from or w ^r rite to a removable, nonvolatile optical disk such as a CD ROM or other optical media. Other removable/nonremovable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment may include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The drives and their associated computer storage media discussed above provide storage of computer readable instructions, data structures, program modules and other data for the computing unit.

[0030] A client may enter commands and information into the computing unit through the client interface, which may be input devices such as a keyboard and pointing device, commonly referred to as a mouse, trackball or touch pad. Input devices may include a microphone, joystick, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit through the client interface that is coupled to a system bus, but may be connected by other interface and bus structures, such as a parallel port or a universal serial bus (USB).

[0031] A monitor or other type of display device may be connected to the system bus via an interface, such as a video interface. A GUI may also be used with the video interface to receive instructions from the client interface and transmit instructions to the processing unit. In addition to the monitor, computers may also include other peripheral output devices such as speakers and printer, which may be connected through an output peripheral interface.

[0032] Although many other internal components of the computing unit are not shown, those of ordinary skill in the art will appreciate that such components and their interconnection are well-known. [0033] While the present disclosure has been described in connection with presently preferred embodiments, it will be understood by those skilled in the art that it is not intended to limit the disclosure to those embodiments. It is therefore, contemplated that various alternative embodiments and modifications may be made to the disclosed embodiments without departing from the spirit and scope of the disclosure defined by the appended claims and equivalents thereof.