System and method for labor scheduling and jobsite management

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are part of this disclosure and are incorporated into the specification. The drawings illustrate example embodiments of the disclosure and, in conjunction with the description and claims, serve to explain various principles, features, or aspects of the disclosure. Certain embodiments of the disclosure are described more fully below with reference to the accompanying drawings. However, various aspects of the disclosure may be implemented in many different forms and should not be construed as being limited to the implementations set forth herein. Like numbers refer to like, but not necessarily the same or identical, elements throughout.

<figref idref="DRAWINGS">FIG. 1</figref> illustrates a first view of a software interface provided on a graphical user interface (GUI), in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates a second view of a software interface provided on a GUI, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 3</figref> illustrates a further view of a software interface provided on a GUI showing information related to operations management, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 4</figref> illustrates a view of a software interface provided on a GUI showing information related to management of job shifts, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 5</figref> illustrates a view of a software interface provided on a GUI showing information related to management of employees, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 6</figref> illustrates a view of a software interface provided on a GUI showing functionality to record a daily log, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 7</figref> illustrates a view of a software interface provided on a GUI showing functionality to specify various job hazards, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 8</figref> illustrates a view of a software interface provided on a GUI showing functionality to specify and manage medical protocols, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 9</figref> illustrates a view of a software interface provided on a GUI showing functionality to specify and modify safety alerts, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 10</figref> illustrates a view of a software interface provided on a GUI showing functionality to schedule drug testing procedures, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 11</figref> illustrates a view of a software interface provided on a GUI showing functionality to specify and manage weld reviews, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 12</figref> illustrates a view of a software interface provided on a GUI showing functionality to manage audits, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 13</figref> illustrates a view of a software interface provided on a GUI showing functionality to specify and manage customer experience surveys, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 14</figref> illustrates a view of a software interface provided on a GUI showing functionality to manage time tracking, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 15</figref> illustrates a view of a software interface provided on a GUI showing functionality to initiate and manage reports and notifications, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 16</figref> is a flow chart illustrating a processor-implemented method of labor scheduling and jobsite management for a dynamically changing workforce, in accordance with one or more embodiments of the disclosure.

<figref idref="DRAWINGS">FIG. 17</figref> is a block diagram of an example computer system, in which disclosed embodiments may be implemented, according to an embodiment of the present disclosure.

DETAILED DESCRIPTION

Disclosed embodiments provide systems and methods of labor scheduling and jobsite management. These embodiments provide functionality to organize and efficiently manage all aspects of a job, including employee onboarding, flexible staffing and workflow management, time entry/payroll support, significant event reporting, medical protocol management, and related capabilities. The disclosed systems and methods may be used to manage the unique challenges posed by jobs requiring teams of craft labor workers. For example, a craft labor job may be a construction site that requires various different teams of workers having different skills working on different aspects of a construction job at different times. Workers needed in the beginning phases of a job may not be needed in middle and end phases of a job. As such, many craft labor jobs have unique scheduling challenges associated with a work force that is dynamically changing as the job progresses.

Disclosed embodiments provide a flexible mechanism to process individual workers through a payroll system to quickly remove and pay one or more workers as needed. In this regard, the system provides a mechanism to quickly “layoff/payoff” temporary workers who have completed their assignments. In contrast, conventional systems only process workers as a batch process and it may be difficult to add and remove workers using such systems. The disclosed systems are flexible in that they are customizable to account for special circumstances (e.g., union rules applying to union workers assigned to craft labor teams). A disclosed software system includes five major components: (1) an operations management platform, (2) a time tracking platform, (3) a self-service portal, (4) an integrated learning management system, and (5) a third-party billing platform. All of these components can feed and/or pull data from a single Enterprise Resource Planning (ERP) system or multiple ERPs or other data sources. This unique combination of system components provide a functionality that is not found in conventional systems.

<figref idref="DRAWINGS">FIG. 1</figref> illustrates a first view <b>100</b> of a software interface provided on a graphical user interface (GUI), in accordance with one or more embodiments of the disclosure. A software interface such as shown in <figref idref="DRAWINGS">FIG. 1</figref> may provide access to all of the system's components and functionality. For example, disclosed systems may include a dashboard <b>102</b> that is displayed on the GUI. The dashboard may provide specific job information, including a targeted task list <b>104</b> customized for each supervisor or superintendent. The dashboard may provide an at-a-glance snapshot of the job <b>106</b>, the jobsite <b>108</b>, work performance <b>110</b> (current project costs, crew rating, etc.), due and overdue tasks, significant event reports, etc. The dashboard may further include a job queue <b>112</b> that provides functionality that allows superintendents to manage a current job and to begin forecasting upcoming jobs. In this regard, the job queue <b>112</b> enhances pre-planning and completion of pre-job tasks. The dashboard may further include a time tracking utility <b>114</b>.

A dashboard screen, such as shown in <figref idref="DRAWINGS">FIG. 1</figref>, provides functionality to help a user see a big picture view of all the information provided by the software interface. Some of the dashboard screens show information specific to the role of the current user, and some display the same information to everyone. According to an embodiment, each user may see similar types of information but some of the information is tailored specifically to the user that is logged in. The list of jobs provided in the job queue <b>112</b> may be sorted by last modified job so the most recently touched jobs will sort to the top. These are typically the jobs that are going to be of most interest to the user logged in. From the jobs queue <b>112</b> it is possible to select an individual job and then use the buttons at the top of the software interface to perform various operations with the selected job as the context.

Targeted task list <b>104</b> is a list of items that may be relevant to the current user. Items not requiring attention may be displayed with green color indicator <b>116</b>. Items displayed with a red color indicator (not shown in this example) may require the user's attention. A user may then focus on an item indicated in red by selecting the item. For example, an item may be selected using a input received by the GUI through user interaction. A user may use an input device, such as a mouse, to select an item by clicking or double clicking the item using the input device. Selecting an item in this way may cause the GUI to change the appearance of information associated with the selected item. For example, the GUI may present a new screen or new window in the GUI (not shown in this example) that may present more detailed information regarding the selected item.

Time tracking utility <b>114</b> may allow a user to keep track of time associated with a given project. Some users won't have a current project and so an area associated with time tracking utility <b>114</b> may be blank (as shown in view <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref>). For other users with a current project, an area associated with time tracking utility <b>114</b> will display a summary (not shown in this example) for that current project. In such a situation, time tracking utility <b>114</b> may provide user-selectable buttons to allow the user to access various additional pieces of information regarding time tracking of the current project.

Work performance <b>110</b> may be indicated by an overall crew rating. Such a rating gives a quick visual indication of an overall rating for a crew for a current time tracking project. This is a rating that is averaged over all evaluations that have been submitted for the members of the crew over their entire work history. When a project is initiated, the rating may have an initial value of 0.0, as shown. As the project progresses and evaluations for various phases of the project are submitted, the rating may increase to indicate an overall performance of the crew.

Information regarding a current work site may be obtained by selecting a user-selectable option regarding the jobsite <b>108</b>. Selection of the jobsite <b>108</b> option may cause the GUI to modify the content of displayed information. For example, selecting the jobsite <b>108</b> item may cause the GUI to display a new screen or window (not shown) that provides a history of the jobsite that is tied to the current time tracking project. This allows a superintendent to understand what has happened previously at the site where work is currently being performed. A daily logs utility <b>118</b> provides a list of system-supplied messages and may contain information about new updates or new releases of the system software.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates a second view <b>200</b> of a software interface provided on a GUI, in accordance with one or more embodiments of the disclosure. View <b>200</b> is generated by the GUI in response to a user selecting jobsite <b>108</b> that was shown in <figref idref="DRAWINGS">FIG. 1</figref>. View <b>200</b> provides detailed information regarding one or more job sites. View <b>200</b> shows information about the various sites that are defined in the system. A list <b>202</b> of sites is displayed on the right in a searchable list and details for the currently selected site <b>203</b> are shown in the editor <b>204</b> area in the middle of view <b>200</b>. In this example, the editor is configured to only allow read access. As such, there is no way to save any changes that are made in this editor. Editor <b>204</b> may provide search features. When searching the list <b>202</b> of sites, editor <b>204</b> may match a search entry against various search fields including: site name, site code, region name, site main address (e.g., state, zip or postal code, city), etc. In this read-only editor <b>204</b>, the information displayed may be chosen to be the most useful for superintendents and others trying to get a feel for a site before they make a trip out to a job site for a first visit.

<figref idref="DRAWINGS">FIG. 3</figref> illustrates a further view <b>300</b> of a software interface provided on a GUI showing information related to operations management, in accordance with one or more embodiments of the disclosure. View <b>300</b> is generated by the GUI when a user selects the “ops management” tab <b>302</b> and the “jobs” tab <b>304</b>. When a user selects tab <b>302</b>, the GUI closes the listing of dashboard entries shown in <figref idref="DRAWINGS">FIG. 2</figref> and opens the listing of entries pertaining to operations management. Tab <b>302</b> provides a collection of screens and user-selectable options that allow a user to plan, provision, and to track job performance metrics. Tab <b>302</b> provides a single-entry point for the creation of job crew rosters. Once entered, a job roster is available to all other components of the software system. As such, problems that may otherwise arise due to duplicate entries may be avoided.

Selection of tab <b>304</b>, under tab <b>302</b>, invokes a job editor <b>306</b> as shown. Editor <b>306</b> handles maintenance of job records using a standard layout to present a list <b>308</b> of records already in the system. Selection of single record <b>310</b> from list <b>308</b> causes editor <b>308</b> to display information about the single record. List <b>308</b> may be configured as a searchable list. A search may be performed by entering a search field in a search box. List <b>308</b> may be automatically filtered based on a user-specified search criterion.

List <b>308</b> may be edited to add new records and to delete existing records. For example, a user may add a new record by selecting the “new” icon <b>312</b>. Upon selection of icon <b>302</b>, editor <b>306</b> may present a blank form that may be filled with information regarding the new record. An existing record may be deleted when a user selects the “delete” icon <b>314</b>. For some situations, it may be advantageous to create a duplicate record. In this regard, a duplicate record may be created when a user selects the “dup” icon <b>316</b>. For example, a duplicate record may be created having a job name and job number that are the same as an existing job. Such a record may be distinguished from an existing record by the presence of a revision counter (e.g., revision-1, revision-2, etc.). List <b>308</b> may further be searched according to search fields including: job number, job status, line of business, company name, site name, etc.

Job records may be edited using various user-selectable items. A save button <b>318</b>, for example, allows any unsaved changes to be saved. In an embodiment, save button <b>318</b> may be displayed with a color status indicator. For example, “save” button <b>318</b> may be displayed having a red color (not shown) to indicate a presence of un-saved changes. Upon selecting save button <b>318</b>, changes may be saved and a color indicator change (e.g., from red to green) may provide a visual indication (not shown) that the changes have been saved. Selection of a “reload” button <b>320</b> may cause the GUI to pull a most recent record from the system and load it into editor <b>306</b>. A “copy job” button or icon <b>322</b> allows a user to make a copy of the job with a new job number. A “view pdf” button or icon <b>324</b> allows a user to view a summary of job details in standard PDF format. A “view MTP” button or icon <b>326</b> allows a user to view a medical treatment protocol that is associated with a job. A “create job log” button or icon <b>328</b> allows a user to create a daily log for a job. A “SER” button or icon <b>330</b> allows a user to create a Significant Event Report (“SER”) for the job.

Various aspects of job creation and management are provided by the various screens that may be invoked in response to selection of various user-selectable menu items. For example, the above-described features of <figref idref="DRAWINGS">FIG. 3</figref> are provided through selection of the “details” menu item <b>332</b>. A further screen providing contact information may be obtained by selecting the “contacts” <b>334</b> menu item. As described in greater detail below with reference to <figref idref="DRAWINGS">FIG. 4</figref>, details of the various job shifts may be managed by invoking a job shifts screen by selecting a “shifts” button <b>336</b>.

<figref idref="DRAWINGS">FIG. 4</figref> illustrates a view <b>400</b> of a software interface provided on a GUI showing information related to management of job shifts, in accordance with one or more embodiments of the disclosure. As described above, view <b>400</b> may be generated by the GUI when a user selects “shifts” button <b>336</b>. The shifts view <b>400</b> allows superintendents to identify jobsite resource needs (e.g., craft labor type, quantity, etc.), even without assigning individual craftsmen to positions. A list <b>401</b> of job shifts may be edited by an editor <b>402</b>, which may provide similar functionality to that provided by job editor <b>306</b>, described above with reference to <figref idref="DRAWINGS">FIG. 3</figref>. In this regard, a shifts <b>406</b> portion of editor <b>402</b> may allow creation of job shift records. For example, “add” button <b>408</b> allows creation of a new shift record, while “edit” button <b>410</b> allows modification of an existing job shift record. A “remove” button <b>412</b> allows a selected record to be deleted. As shown, a record may be created that specifies a number of required days <b>414</b>, start day/date <b>416</b>, end day/date <b>418</b>, start time <b>420</b>, hours per shift <b>422</b>, days per week <b>424</b>, a shift percentage <b>426</b>, a shift pay rate <b>428</b>, etc. In other embodiments, additional fields may be defined by a user.

Editor <b>402</b> may further include a resource portion <b>430</b> of editor <b>402</b> that may allow available manpower resources to be searched and to be assigned. Resource attributes may include specification of a number of required days <b>432</b>, a quantity <b>434</b> of a specific type of worker, a skill set <b>436</b> or type of craft worker <b>438</b>, a union designation <b>440</b>, a class designation <b>442</b>, etc. As with shift portion <b>406</b>, resource portion <b>430</b> of editor <b>402</b> may further allow a user to define additional fields to designate needed resources. As described in greater detail below with reference to <figref idref="DRAWINGS">FIG. 5</figref>, details of the various employees that may be assigned to job shifts may be managed by invoking an employee's screen by selecting an “employees” button <b>446</b>.

<figref idref="DRAWINGS">FIG. 5</figref> illustrates a view <b>500</b> of a software interface provided on a GUI showing information related to management of employees, in accordance with one or more embodiments of the disclosure. As described above, view <b>500</b> may be generated by the GUI when a user selects “employees” button <b>446</b>. Functionality provided by view <b>500</b> may be used by a superintendent in identifying correct resources for a specific job. According to an embodiment, the system may be configured to cross reference site requirements, training requirements, employee requirements, and other pertinent information to create an ideal team for a job. Such cross-referenced information may be provided from various other screens that may be displayed by the GUI in response to various user-selections. The resource planning capability of the system also provides overall visibility of craft availability and scheduling to all levels of the business, including resource managers, general managers, and corporate personnel. One major benefit is a systematic overview of all assigned and available craftsmen for a given time period, simplifying management of the entire pool of craftsmen.

Each employee may be categorized according to their individual skills and training. In some embodiments, the GUI may be configured to provide visual indicators that provide information regarding an employee's skills/training. For example, the system may provide a red/green visual indicator (not shown) indicating a breakdown of an employee's qualifications. For example, desirable skills for a particular job may be highlighted in green (not shown) while deficits may be highlighted in red (not shown). Such visual indicators may give a superintendent a graphical overview of how well a selected crew meets jobsite requirements. Any shortfalls that need to be addressed before the job starts may be highlighted using a visual indicator (e.g., a text box highlighted in red), as described above. Granular control of this functionality allows a superintendent to tailor the overview of job qualifications to the needs of a particular job.

View <b>500</b> shows a job roster page that may be displayed by the GUI in response to a user selection of the “job roster” button <b>502</b>. A roster <b>504</b> for a given job may be created by selecting employees from a list <b>506</b> of employee candidates. In this example, an employee <b>508</b> has been selected from list <b>506</b>. The selected employee <b>508</b> may be added to roster <b>540</b> when a user selects a transfer button <b>510</b> that transfers the selected employee <b>508</b> from the list <b>506</b> of potential employees to roster <b>504</b>. As described in greater detail below with reference to <figref idref="DRAWINGS">FIG. 6</figref>, a daily log screen may be invoked when a user selects a “daily logs” button <b>512</b>.

<figref idref="DRAWINGS">FIG. 6</figref> illustrates a view <b>600</b> of a software interface provided on a GUI showing functionality to record a daily log that is invoked when a user selects a “daily logs” button <b>512</b>, in accordance with one or more embodiments of the disclosure. In this regard, the system incorporates user-defined selection capabilities for sharing daily logs. Superintendents can select which portions of logs are shared with specific groups such as third-party contractors, customers, field engineers, or corporate leadership. View <b>600</b> includes a list <b>602</b> of daily logs and a daily log editor <b>604</b>. Selection of a specific log <b>606</b> by a user causes the GUI to load information about log <b>606</b> into editor <b>604</b>. Editor <b>604</b> may then be used to update or correct information associated with log <b>606</b>. A “new” button <b>608</b> may be selected to create a new log. As shown, editor <b>604</b> includes forms that allow information to be recorded regarding a job site <b>610</b>, a specific job <b>612</b>, a superintendent <b>614</b>, details <b>616</b> of the log, dates <b>618</b>, etc. Some embodiments allow creation of user-defined categories of information to be included in daily logs.

<figref idref="DRAWINGS">FIG. 7</figref> illustrates a view <b>700</b> of a software interface provided on a GUI showing functionality to specify various job hazards, in accordance with one or more embodiments of the disclosure. The system may be configured so that the GUI presents view <b>700</b> in response to a user selecting the “hazard hunts” button <b>702</b>. The functionality provided by view <b>700</b> is similar to that presented in other examples above. In this regard, view <b>700</b> includes a list <b>704</b> of selectable records and an editor <b>706</b>. Records may be created, edited, and deleted as described in previous examples. In this example, editor <b>706</b> provides forms allowing entry of information regarding a particular site <b>708</b>, a particular job <b>710</b>, a superintendent <b>712</b> for the job <b>710</b>, and various details <b>714</b> regarding potential hazards that may be encountered with job site <b>708</b> that is associated with job <b>710</b>. Editor <b>706</b> further provides functionality to include one or more images <b>716</b>. The functionality provided by view <b>700</b> allows “hazard hunt” guidelines to be defined and requirements to be pushed to superintendents in the field. Further, the “hazard hunt” page (i.e., view <b>700</b>) provides management oversight of the program and ensures safety is always the top priority.

<figref idref="DRAWINGS">FIG. 8</figref> illustrates a view <b>800</b> of a software interface provided on a GUI showing functionality to specify and manage medical protocols, in accordance with one or more embodiments of the disclosure. The system may be configured so that the GUI presents view <b>800</b> in response to a user selecting the “medical protocols” button <b>802</b>. View <b>800</b> provides a comprehensive, step-by-step guide to company medical protocols and procedures including information regarding hospitals and clinics associated with each job site (e.g., closest facilities, maps, contact information, emergency services, etc.). View <b>800</b> includes a records list <b>804</b> and an editor <b>806</b>. Editor <b>806</b> includes various forms that allow creation and management of information for medical treatment protocols <b>808</b>, contact information <b>810</b>, information regarding a general manager <b>812</b>, a director <b>814</b>, etc. Records list <b>804</b> allows records to be searched, new records to be created using the “new” button <b>816</b>, and records to be deleted using the delete button <b>818</b>. Selecting a particular record <b>820</b> causes the various forms <b>808</b>, <b>810</b>, <b>812</b>, and <b>814</b> of editor <b>806</b> to be populated with information regarding record <b>820</b>. Editor <b>806</b> may then be used to edit the information associated with record <b>820</b>. Similarly, when a new record is created using “new” button <b>816</b>, blank forms <b>808</b>, <b>810</b>, <b>812</b>, and <b>814</b> may be presented that allow new information to be entered into the newly created record.

<figref idref="DRAWINGS">FIG. 9</figref> illustrates a view <b>900</b> of a software interface provided on a GUI showing functionality to specify and modify safety alerts, in accordance with one or more embodiments of the disclosure. The system may be configured so that the GUI presents view <b>900</b> in response to a user selecting the “safety alerts” button <b>902</b>. Disclosed embodiments may be configured so that safety alerts are mapped to applicable technologies and work scopes. Such a mapping ensures that safety alerts for a specific system or line of business are targeted to job sites and work scopes that employ those systems. View <b>900</b> allows management and safety professionals to push critical alerts using granular selection criteria (e.g., push to all superintendents, push specific job types, push based on specific work scopes, push to specific superintendents, etc.). View <b>900</b> includes a list <b>904</b> of safety alerts and an editor <b>906</b>. New alerts may be created using the “new” button <b>908</b> and existing records may be deleted using the “delete” button <b>910</b>. Existing records in list <b>904</b> may be searched using various search fields relating to the safety alert name and safety alert summary. Other embodiments may include other search criteria. Selecting a specific record <b>912</b> populates editor <b>906</b> with information regarding selected record <b>912</b>. Editor <b>906</b> also allows information regarding the selected record <b>912</b> to be edited. Editor <b>906</b> may allow information for a newly created record to be entered.

<figref idref="DRAWINGS">FIG. 10</figref> illustrates a view <b>1000</b> of a software interface provided on a GUI showing functionality to schedule drug testing procedures, in accordance with one or more embodiments of the disclosure. The system may be configured so that the GUI presents view <b>1000</b> in response to a user selecting the “drug testing request” button <b>1002</b>. Many jobs require workers to submit to a drug test in order to be qualified for the job. View <b>1000</b> leverages the job roster (described above) and billing capabilities to simplify and expedite drug tests for craftsmen on-site or during pre-job planning. View <b>1000</b> includes a list <b>1004</b> of scheduled tests and an editor <b>1006</b>. New requests may be initiated when a user selects the “new” button <b>1008</b>, and existing requests may be deleted using the “delete” button <b>1010</b>. Editor <b>1006</b> allows information to be entered for a new requested test and allows information for a selected existing test <b>1012</b> to be edited. Editor <b>1006</b> includes forms that allow specification of details regarding the job <b>1014</b>, the job site <b>1016</b>, and whether the test is billable <b>1018</b> or non-billable <b>1020</b>. Editor <b>1006</b> further allows test details <b>1022</b> and details regarding the work shift <b>1024</b> to be entered. Further embodiments may allow further information to be specified.

<figref idref="DRAWINGS">FIG. 11</figref> illustrates a view <b>1100</b> of a software interface provided on a GUI showing functionality to specify and manage weld reviews, in accordance with one or more embodiments of the disclosure. The system may be configured so that the GUI presents view <b>1100</b> in response to a user selecting the “weld reviews” button <b>1102</b>. View <b>1100</b> centralizes and digitizes a process that was previously a tedious paper process. The functionality provided by view <b>1100</b> further generates State documents and reports required for weld certification. View <b>1100</b> includes a list <b>1104</b> of weld reviews and a weld review editor <b>1106</b>. Editor <b>1106</b> handles the maintenance of a portion of the current time tracking project that deals with weld review records. Various time tracking editors (described in greater detail below) work on a specific portion of the current time tracking project and work in conjunction with each other to track everything that goes on during execution of the project. When working with a weld review record <b>1108</b>, required fields may be marked with a visual indicator (e.g., a red asterisk; not shown), and field validation may be applied prior to saving the record. According to this example, invalid data may be entered into editor <b>1106</b>, but the data will be checked when the “save” button <b>1110</b> is invoked. As such, the system may be configured to prompt a user to fix invalid data prior to the data being saved to the system. Editor <b>1106</b> may include forms that allow specification of information regarding job site <b>1112</b>, job <b>1114</b>, and information regarding QA leads <b>1118</b> and <b>1120</b>.

<figref idref="DRAWINGS">FIG. 12</figref> illustrates a view <b>1200</b> of a software interface provided on a GUI showing functionality to manage audits, in accordance with one or more embodiments of the disclosure. The system may be configured so that the GUI presents view <b>1200</b> in response to a user selecting the “leadership audits” button <b>1202</b>. View <b>1200</b> is part of a centralized, standardized audit system. Other examples of audits provided by the system include “monitor audits” <b>120</b> (e.g., see <figref idref="DRAWINGS">FIG. 1</figref>). The system further provides functionality to generate and share user-defined custom audits. View <b>1200</b> includes a list <b>1204</b> and an editor <b>1206</b>.

A new audit may be generated when a user selects the “new” button <b>1208</b> and existing audits may be deleted using the “delete” button <b>1210</b>. Existing audits may be searched using various criteria such as job number, template title, site name, superintendent name (e.g., first name . . . starts with, last name . . . starts with, etc.). Selecting a specific existing audit <b>1214</b> populates editor <b>1206</b> with information regarding the selected record <b>1214</b>. Editor <b>1206</b> also allows information regarding the selected record <b>1214</b> to be edited. Editor <b>1206</b> may allow information for a newly created record to be entered. For example, editor <b>1206</b> provides forms for entry of a title <b>1216</b>, information regarding a specific job <b>1218</b>, report details <b>1220</b>, report dates <b>1222</b>, etc.

<figref idref="DRAWINGS">FIG. 13</figref> illustrates a view <b>1300</b> of a software interface provided on a GUI showing functionality to specify and manage customer experience surveys, in accordance with one or more embodiments of the disclosure. The system may be configured so that the GUI presents view <b>1300</b> in response to a user selecting the “customer experience” button <b>1302</b>. View <b>1300</b> provides functionality for a user to collect system performance data via customer experience surveys. In this regard, based on user input, the system may generate and send invitations to targeted individuals (e.g., customer representatives, plant owners, field engineers, etc.). The invitations may provide a request to the recipient to share feedback regarding their experience in using the system. Surveys also request recipients to share feedback on craft labor performance on the jobsite. These customer surveys may help to ensure company performance of assigned jobs/tasks exceed standards. Targeted surveys may ensure that performance feedback is provided by appropriate entities. View <b>1300</b> includes a list <b>1304</b> of surveys and an editor <b>1306</b>. Selecting a specific existing survey <b>1318</b> populates editor <b>1306</b> with information regarding the selected survey <b>1318</b>, and editor <b>1306</b> allows information regarding the selected survey <b>1318</b> to be edited. A new survey request may be generated when a user selects the “new” button <b>1308</b> and enters information regarding the new survey using editor <b>1306</b>. Editor <b>1306</b> allows information to be entered including a survey title <b>1310</b>, a job <b>1312</b> to which the survey refers, a status <b>1314</b> of the survey, and dates <b>1316</b> associated with collection of survey data.

<figref idref="DRAWINGS">FIG. 14</figref> illustrates a view <b>1400</b> of a software interface provided on a GUI showing functionality to manage time tracking, in accordance with one or more embodiments of the disclosure. The system may be configured so that the GUI presents view <b>1400</b> in response to a user selecting the “time tracking” tab <b>1402</b> and the “project setup” button <b>1404</b>. The system provides a collection of screens that are designed to allow a job superintendent or job site clerk to track activities of all of the manpower involved in a specific job or job shift. This includes functionality to define crews, to track hiring and layoff paperwork, to enter and track expenses, to enter and track hours, and to prepare reports that may be submitted to a payroll department to drive paycheck creation.

View <b>1400</b> includes an editor <b>1406</b> that allows specification of project information <b>1408</b>, payroll information <b>1410</b>, superintendent information <b>1412</b>, as well as information regarding the job site <b>1416</b>, the site address <b>1418</b>, etc. Various other screens may be accessed to allow additional time tracking functionality. For example, an employee roster page, an employee skills matrix page, etc., may be accessed by selecting respective buttons <b>1420</b>, <b>1422</b>, etc.

The system may further provide a “layoff is payoff” functionality. In this regard, union agreements require craft employees to be paid a final paycheck before they can be laid-off from a jobsite and returned to the union hall for re-assignment. Disclosed embodiments allow individual employees to be selectively pulled from the jobsite payroll batch and have their pay and union benefits dispersed immediately. No other time tracking system is known to have this capability. Disclosed embodiments further provide functionality to make payroll corrections, even to previously executed payroll actions. According to this functionality, a superintendent may simply correct the error to “what it should have been” and the backend system is configured to take care of correcting pay and benefits.

Additional embodiments provide functionality for third-party time tracking. This functionality provides significant flexibility that is not found in conventional time tracking systems. In this regard, the system may be configured to allow third-party contractors to enter time for the purpose of cost tracking and, as such, the entered third-party time is not processed as a payroll action. This unique feature creates a single repository of information regarding all jobsite costs. The ability to track and manage all costs for a given jobsite permits actual cost reporting and forecasting via a percent-complete value by activity. This functionality also permits tracking of sub-contracted personnel, third-party equipment, site material costs, etc. The system may further be configured to keep track of separate costs incurred by the primary user vs. those incurred by third-party contractors.

Additional functionality may allow reporting third-party timecards back to a third-party contractor for payroll processing. In this way, the system may be configured to natively track and to supply all aspects of customer financial reporting, including a pass-through capability to track third-party work hours and to either allow internal payroll processing, or to directly submit third-party work hours to a third-party payroll system. Further, the primary user may generate and submit bills to the end customer on behalf of the third-party contractor. As such, the system may provide a full centralized billing functionality for an entire job and may provide output that includes activity and progress reporting, as well as direct invoicing for end customers.

<figref idref="DRAWINGS">FIG. 15</figref> illustrates a view <b>1500</b> of a software interface provided on a GUI showing functionality to initiate and manage reports and notifications, in accordance with one or more embodiments of the disclosure. The system may be configured so that the GUI presents view <b>1500</b> in response to a user selecting the “reports” tab <b>1502</b> and the “daily timesheet” button <b>1504</b>. The system may be configured to allow customizable reporting and notification, including the ability to set groups for specific types of notifications. For example, a user may specify “significant event reports” (SER) to go to all senior leaders, termination notifications to go to payroll and operations leaders, etc.

Selection of various icons allows a user to generate various types of reports. For example, a user may select cost reports <b>1506</b>, employee reports <b>1508</b>, customer reports <b>1510</b>, etc. View <b>1500</b> shows a screen associated with a “daily timesheet” <b>1504</b> report. As shown, the “daily timesheet” <b>1504</b> report includes an editor that allows entry of various pieces of information including a project ID <b>1512</b>, a company name <b>1514</b>, a customer name <b>1516</b>, a plant location/site name <b>1518</b>, and a description <b>1520</b>. In this example, limits <b>1522</b> may be set by timesheet, by job/date, by task/date, etc., and various timesheets may be selected <b>1524</b> using a timesheet selection form. Various other reports may be generated using editors that provide similar functionality.

According to an embodiment, the system may provide a “self-service portal” to allow contractors and other third-parties to access the system. The self-service portal may be configured as an external system that allows workers to update personal information managed by the system. For example, a worker may use the self-service portal to provide information including name, address, basic contact information, I-9 and W-4 forms, and other information needed prior to the start of a job. The system may further allow workers to identify upcoming work opportunities and manage their job schedule. The self-service portal may further be configured to allow third-party contractors to push data such as hazard hunt results (e.g., see <figref idref="DRAWINGS">FIG. 7</figref>) to the system. This functionality may also allow the system to share appropriate information with third-party contractors.

The self-service portal may further include user-selectable pages that provide an “open calls” utility, an “onboarding” utility, a “pay and benefits” utility, and a “reporting” utility. The open calls utility is a labor forecasting tool for individual craftsmen. This tool may be configured to allow craftsmen from union halls across North America to view and volunteer for upcoming job opportunities, coordinate with site superintendents, and to plan/forecast follow-on work opportunities. The onboarding utility may be configured to be a web-based portal that permits craftsmen to complete pre-job tasks, including general and site-specific safety training, to update personal information (contact info, tax withholding, etc.), and to review company policies. The pay and benefits utility may be configured as an employee portal that allows craftsmen to view/download pay statements and other personal documents. The reporting utility may be configured to enable superintendents to proactively manage pre-job requirements by submitting crew preparation data to the system for completion and compliance reporting.

Further embodiments may include an integrated learning management system which is a comprehensive system that incorporates training courses for all required jobsite, safety, and annual training requirements. Functionality of this system allows integration of training requirements with pre job planning operations. This integration allows a superintendent to view status of crew training on a single, integrated dashboard which greatly improves informed decision-making.

<figref idref="DRAWINGS">FIG. 16</figref> is a flow chart illustrating a processor-implemented method <b>1600</b> of labor scheduling and jobsite management for a dynamically changing workforce, in accordance with one or more embodiments of the disclosure. In a first stage <b>1602</b>, the method includes controlling, by a processor-circuit, a GUI to present a user interface that includes a plurality of user-selectable input screens that are configured to receive user input regarding employee onboarding, flexible staffing and workflow management, time entry/payroll support, significant event reporting, and medical protocol management. In stage <b>1604</b>, the method includes receiving user input from one or more of the user-selectable input screens. In stage <b>1606</b>, the method includes generating and dynamically updating a plurality of work schedules for a respective plurality of workers having different skills working on different aspects of a job at different times as the job progresses. Further, at stage <b>1608</b>, the method includes managing time keeping, payroll, benefits, and medical protocols for workers beginning and ending work at different times as the job progresses.

Disclosed embodiments may be implemented in hardware, firmware, software, or any combination thereof. Embodiments may also be implemented as instructions stored on a non-transitory machine-readable medium, which may be read and executed by one or more processor circuits (i.e., “processors”). A machine-readable medium may include any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computing device). For example, a machine-readable medium may include read only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; electrical optical, acoustical or other forms of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.), and others. Firmware, software routines, and computer program instructions may be described herein as performing certain actions or operations. However, such descriptions are merely for convenience of description. Such actions or operations, in fact, result from computing devices, processors, controllers, or other devices executing the firmware, software, routines, instructions, etc.

<figref idref="DRAWINGS">FIG. 17</figref> is a block diagram of an example computer system <b>1700</b> in which disclosed embodiments of, or portions thereof, may be implemented as computer-readable code (i.e., machine-readable computer program instructions), which is executed by one or more processors causing the one or more processors to perform operations of the disclosed embodiments.

Disclosed systems may include components implemented on computer system <b>1700</b> using hardware, software, firmware, tangible computer-readable (i.e., machine-readable) media having computer program instructions stored thereon, or a combination thereof, and may be implemented in one or more computer systems or other processing system.

If programmable logic is used, such logic may be executed on a commercially available processing platform or a on a special purpose device. One of ordinary skill in the art may appreciate that embodiments of the disclosed subject matter may be practiced with various computer system configurations, including multi-core multiprocessor systems, minicomputers, mainframe computers, computers linked or clustered with distributed functions, as well as pervasive or miniature computers that may be embedded into virtually any device.

Various disclosed embodiments are described in terms of this example computer system <b>1700</b>. After reading this description, persons of ordinary skill in the relevant art will know how to implement disclosed embodiments using other computer systems and/or computer architectures. Although operations may be described as a sequential process, some of the operations may in fact be performed in parallel, concurrently, and/or in a distributed environment, and with program code stored locally or remotely for access by single or multi-processor machines. In addition, in some embodiments the order of operations may be rearranged without departing from the spirit of the disclosed subject matter.

As persons of ordinary skill in the relevant art will understand, a computing device for implementing disclosed embodiments has at least one processor, such as processor <b>1702</b>, wherein the processor may be a single processor, a plurality of processors, a processor in a multi-core/multiprocessor system, such system operating alone, or in a cluster of computing devices operating in a cluster or server farm. Processor <b>1702</b> may be connected to a communication infrastructure <b>1704</b>, for example, a bus, message queue, network, or multi-core message-passing scheme.

Computer system <b>1700</b> may also include a main memory <b>1706</b>, for example, random access memory (RAM), and may also include a secondary memory <b>1708</b>. Secondary memory <b>1708</b> may include, for example, a hard disk drive <b>1710</b>, removable storage drive <b>1712</b>. Removable storage drive <b>1712</b> may include a floppy disk drive, a magnetic tape drive, an optical disk drive, a flash memory, or the like. The removable storage drive <b>1712</b> may be configured to read and/or write data to a removable storage unit <b>1714</b> in a well-known manner. Removable storage unit <b>1714</b> may include a floppy disk, magnetic tape, optical disk, etc., which is read by and written to, a removable storage drive <b>1712</b>. As will be appreciated by persons of ordinary skill in the relevant art, removable storage unit <b>1714</b> may include a computer readable storage medium having computer software (i.e., computer program instructions) and/or data stored thereon.

In alternative implementations, secondary memory <b>1708</b> may include other similar devices configured to allow computer programs or other instructions to be loaded into computer system <b>1700</b>. Such devices may include, for example, a removable storage unit <b>1716</b> and an interface <b>1718</b>. Examples of such devices may include a program cartridge and cartridge interface (such as that found in video game devices), a removable memory chip (such as EPROM or PROM) and associated socket, and other removable storage units <b>1716</b> and interfaces <b>1718</b> which allow software and data to be transferred from the removable storage unit <b>1716</b> to computer system <b>1700</b>.

Computer system <b>1700</b> may also include a communications interface <b>1720</b>. Communications interface <b>1720</b> allows software and data to be transferred between computer system <b>1700</b> and external devices. Communications interfaces <b>1720</b> may include a modem, a network interface (such as an Ethernet card), a communications port, a PCMCIA slot and card, or the like. Software and data transferred via communications interface <b>1720</b> may be in the form of signals <b>1722</b>, which may be electronic, electromagnetic, optical, or other signals capable of being received by communications interface <b>1720</b>. These signals may be provided to communications interface <b>1720</b> via a communications path <b>1724</b>.

In this document, the terms “computer program storage medium” and “computer usable storage medium” are used to generally refer to storage media such as removable storage unit <b>1714</b>, removable storage unit <b>1716</b>, and a hard disk installed in hard disk drive <b>1710</b>. Computer program storage medium and computer usable storage medium may also refer to memories, such as main memory <b>1706</b> and secondary memory <b>1708</b>, which may be semiconductor memories (e.g., DRAMS, etc.). Computer system <b>1700</b> may further include a display unit <b>1726</b> that interacts with communication infrastructure <b>1704</b> via a display interface <b>1728</b>. Computer system <b>1700</b> may further include a user input device <b>1730</b> that interacts with communication infrastructure <b>1704</b> via an input interface <b>1732</b>. A user input device <b>1730</b> may include a mouse, trackball, touch screen, or the like.

Computer programs (also called computer control logic or computer program instructions) are stored in main memory <b>1706</b> and/or secondary memory <b>1708</b>. Computer programs may also be received via communications interface <b>1720</b>. Such computer programs, when executed, enable computer system <b>1700</b> to implement embodiments as disclosed herein. In particular, the computer programs, when executed, enable processor <b>1702</b> to implement the processes of disclosed embodiments, such as various stages in disclosed methods, as described in greater detail above. Accordingly, such computer programs represent controllers of the computer system <b>1700</b>. When an embodiment is implemented using software, the software may be stored in a computer program product and loaded into computer system <b>1700</b> using removable storage drive <b>1712</b>, interface <b>1718</b>, and hard disk drive <b>1710</b>, or communications interface <b>1720</b>. A computer program product may include any suitable non-transitory machine-readable (i.e., computer-readable) storage device having computer program instructions stored thereon.

Embodiments may be implemented using software, hardware, and/or operating system implementations other than those described herein. Any software, hardware, and operating system implementations suitable for performing the functions described herein may be utilized. Embodiments are applicable to both a client and to a server or a combination of both.

The disclosure sets forth example embodiments and, as such, is not intended to limit the scope of embodiments of the disclosure and the appended claims in any way. Embodiments have been described above with the aid of functional building blocks illustrating the implementation of specified functions and relationships thereof. The boundaries of these functional building blocks have been arbitrarily defined herein for the convenience of the description. Alternate boundaries can be defined to the extent that the specified functions and relationships thereof are appropriately performed.

The foregoing description of specific embodiments will so fully reveal the general nature of embodiments of the disclosure that others can, by applying knowledge of those of ordinary skill in the art, readily modify and/or adapt for various applications such specific embodiments, without undue experimentation, without departing from the general concept of embodiments of the disclosure. Therefore, such adaptation and modifications are intended to be within the meaning and range of equivalents of the disclosed embodiments, based on the teaching and guidance presented herein. The phraseology or terminology herein is for the purpose of description and not of limitation, such that the terminology or phraseology of the specification is to be interpreted by persons of ordinary skill in the relevant art in light of the teachings and guidance presented herein.

The breadth and scope of embodiments of the disclosure should not be limited by any of the above-described example embodiments, but should be defined only in accordance with the following claims and their equivalents.