WO2013049803A1

WO2013049803A1 - Worksite safety, planning and environmental documentation and mapping system and method

Info

Publication number: WO2013049803A1
Application number: PCT/US2012/058276
Authority: WO
Inventors: Bryce WALTER
Original assignee: Ecates, Inc.
Priority date: 2011-09-30
Filing date: 2012-10-01
Publication date: 2013-04-04

Abstract

A worksite planning and mapping system for mapping projects at a worksite includes a central server configured to store a map of the worksite. A display is in communication with the central server and visually presents the map. An approved jobs database is stored at the central server and maintains approved jobs information. A denied jobs database is stored at the central server and maintains first denied job information. The first denied job information includes a first reason for denial and a first denied job location. A pending jobs database is stored at the central server. The first pending job information includes a first pending location, a first pending time period and a first pending identification. The central server is configured to compare the first pending job information to the approved jobs information to create a first recommendation regarding whether to approve the first pending job.

Description

TITLE OF THE INVENTION

[0001 ] WORKSITE SAFETY, PLANNING AND ENVIRONMENTAL DOCUMENTATION AND MAPPING SYSTEM AND METHOD

CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Provisional Patent Application No.

61/541 ,518, filed on September 30, 201 1 and titled "Worksite Safety and Environment

Documentation and Mapping System and Method," the entire contents of which are incorporated herein by reference in its entirety.

BACKGROUND OF THE INVENTION

[0003] Safety is a primary concerns for companies with a plurality of operations and tasks occurring simultaneously and intermittently at a company worksite. The plurality of tasks may be conducted by company employees on a regular basis at predetermined time periods, may be intermittently conducted by company personnel or third party contractors or may be conducted by internal or contractor personnel on an emergency or last-minute basis. The various jobs that are conducted by company and contractor personnel must also be coordinated with various hazards and limited access areas at a worksite or at various worksites where various certifications and/or qualifications are necessary to enter a particular area or to work on a particular machine at the worksite. Planning for the conduct of such jobs and/or tasks, particularly in view of the potential hazardous nature of certain types of jobs can be a difficult endeavor for a company or operation to coordinate. Such planning and organizational difficulties can be pronounced when regular company operations are halted for periodic maintenance of equipment, such as maintenance for power plants, manufacturing assembly lines, steel plants or nearly any company that periodically halts operations to conduct maintenance on equipment. In addition, planning and organizational difficulties can be pronounced when company operations are on-going, but maintenance or specific jobs must be completed at an operating worksite. It is desirable to design and develop a system that permits planning of worksite safety and special organization by documenting and mapping jobs being performed by employees and/or third party contractors at a worksite to minimize safety risks and conflicts between the various tasks or jobs performed at the worksite. This need may be particularly pronounced when multiple maintenance tasks are conducted at a worksite or emergency

maintenance or tasks are required that were not contemplated as standard worksite operations. BRIEF SUMMARY OF THE INVENTION

[0004] Briefly stated, a preferred embodiment of the present invention is directed to a worksite safety, planning and environmental documentation and mapping system for documenting and mapping projects, tasks or jobs conducted at a worksite. The system includes a central server configured to store a map of the worksite. The map includes representations of equipment and facilities at the worksite. A display is in communication with the central server. The display is configured to visually present the map. An approved jobs database is stored at the central server. The approved jobs database maintains approved jobs information including a first approved job. The approved jobs information is related to a plurality of approved jobs at the worksite and includes first approved job information related to the first approved job. The first approved job information includes a first job location associated with a first area on the map. The first job information also includes a first time period and a first job identification. A denied jobs database is stored at the central server. The denied jobs database maintains first denied job information related to a first denied job at the worksite. The first denied job information includes a first reason for denial of the first denied job and a first denied job location. A pending jobs database is stored at the central server. The pending jobs database maintains pending jobs information including a first pending job information. The first pending job information includes a first pending location, a first pending time period and a first pending identification. The central server is configured to compare the first pending job information to the approved jobs information to create a first recommendation regarding whether to approve the first pending job.

[0005] In another aspect, a preferred embodiment of the present invention is directed to a method for utilizing a worksite safety, planning and environmental documentation and mapping system for documenting and mapping projects being conducted at a worksite. The system includes a central server having a pending jobs database, an approved jobs database, a denied jobs database, an approved contractor database and a completed jobs database. The central server is in

communication with a contractor display configured to present a map of the worksite and a controller display. The method includes the steps of receiving, at the central server, a contractor name and a contractor password and comparing the contractor name and the contractor password to a plurality of stored contractor names and stored contractor passwords in the approved contractor database. The central server activates the system if the contractor name matches one of the plurality of stored contractor names and the contractor password matches a corresponding one of the plurality of stored contractor passwords, respectively. The method also includes the steps of receiving, at the central server, first pending job information associated with a first pending job including a first 2012/058276 pending location, a first pending time period and a first pending identification and comparing, with the central server, the first pending time period to a plurality of approved time periods associated with a plurality of approved jobs. The first pending job information being stored in the pending jobs database. The method further includes the steps of comparing, with the central server, the first pending location to a plurality of approved locations associated with the plurality of approved jobs and transmitting, via the central server, one of an approval recommendation if both the first pending time period and the first pending location do not both overlap with the plurality of approved time periods and an associated one of the plurality of approved locations and a denial recommendation to the controller if both the first pending time period and the first pending location overlap with the plurality of approved time periods and an associated one of the plurality of approved locations. The one of the approval and the denial recommendation being transmitted to the controller display. The method also involves receiving, at the central server, one of an approval and a denial of the first pending job.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

[0006] The foregoing summary, as well as the following detailed description of the invention, will be better understood when read in conjunction with the appended drawings. For the purpose of illustrating the invention, there are shown in the drawings embodiments which are presently preferred. It should be understood, however, that the invention is not limited to the precise arrangements and instrumentalities shown. In the drawings:

[0007] Fig. 1 is a block diagram of a worksite safety and environmental documentation and mapping system for documenting and mapping projects being conducted at a worksite in accordance with a preferred embodiment of the present invention;

[0008] Fig. 2 is a depiction of a map in a display screen of the system of Fig. 1 ;

[0009] Fig. 3 is a block diagram of an approved jobs database of the system of Fig. 1 ;

[0010] Fig. 4 is flow diagram of several pages that may be shown on a display of the system of Fig. 1 ;

[0011] Fig. 5 is a flow diagram of client or contractor sign in pages that may be shown on the display of the system of Fig. 1;

[0012] Fig. 6 is a flow diagram of a job planning sheet and related pages that may be shown on the display of the system of Fig. 1 ;

[0013] Fig. 7 is a job denied or approved by the customer or contractor flow diagram that may be shown on the display of the system of Fig. 1 ; P T/US2012/058276

[0014] Fig. 8 is a registration flow diagram including pages that may be shown on the display of the system of Fig. 1 ;

[0015] Fig. 9 is a customer dashboard flow diagram including pages that may be shown on the display of the system of Fig. 1 ;

[0016] Fig. 10 is an incident reporting flow diagram including pages that may be shown on the display of the system of Fig. 1 ;

[0017] Fig. 1 1 is a hazard/safety news flow diagram including pages that may be shown on the display of the system of Fig. 1 ;

[0018] Fig. 12 is a completed jobs flow diagram including pages that may be shown on the display of the system of Fig. 1 ;

[0019] Fig. 13 is a pending jobs/approval process flow diagram including pages that may be shown on the display of the system of Fig. 1 ;

[0020] Fig. 14 is utility impact flow diagram including pages that may be shown on the display of the system of Fig. 1 ;

[0021] Fig. 15 is a lock out/tag out flow diagram including pages that may be shown on the display of the system of Fig. 1 ;

[0022] Fig. 16 is a flow diagram related to the pending jobs/approval process flow diagram of Fig. 13;

[0023] Fig. 17 a jobsite selection page that may be shown on the display of the system of Fig. 1 ;

[0024] Fig. 18 is a safety checklist page that may be shown on the display of the system of Fig. l ;

[0025] Fig. 19 is a customer dashboard page that may be shown on the display of the system of Fig. 1 ;

[0026] Fig. 20 is a request from the system of Fig. 1 to deny or approve a job, which may be shown on the display of the system of Fig. 1 ;

[0027] Fig. 21 is a maps page that may be shown on the display of the system of Fig. 1;

[0028] Fig. 22 is a request from the system of Fig. 1 to select a location or area on the map, which may be shown on the display of the system of Fig. 1 ;

[0029] Fig. 23 is a hazard map page that may be shown on the display of the system of Fig. 1 ;

[0030] Fig. 24 is a job review page that may be shown on the display of the system of Fig. 1 ;

[0031] Fig. 25 is a warning or recommendation from the system of Fig. 1, which may be shown on the display of the system of Fig. 1 ;

[0032] Fig. 26 is a flow diagram of the general operation of the system of Fig. 1 ; [0033] Fig. 27 is a series of symbols that may be utilized for the mapping function of the system of Fig. 1 ;

[0034] Fig. 28 is an alternate depiction of a map in a display screen of the system of Fig. 1 ;

[0035] Fig. 29 is the map of Fig. 28 wherein a job is presented on the alternate map;

[0036] Fig. 30 is the map of Fig. 28 various symbols added to the alternate map; and

[0037] Fig. 31 is the map of Fig. 28, wherein another job that conflicts or overlaps with the job of Fig. 29 is added.

DETAILED DESCRIPTION OF THE INVENTION

[0038] Certain terminology is used in the following description for convenience only and is not limiting. Unless specifically set forth herein, the terms "a", "an" and "the" are not limited to one element but instead should be read as meaning "at least one". The words "right," "left," "lower," and "upper" designate directions in the drawings to which reference is made. The words "inwardly" and "outwardly" refer to directions toward and away from, respectively, the geometric center or orientation of the device or system and related parts thereof. The terminology includes the above- listed words, derivatives thereof and words of similar import.

[0039] Referring to Figs. 1-3, a preferred embodiment of the present invention is directed to a worksite safety, planning and environmental documentation and mapping system, generally designated 10. The safety, planning and environmental documentation and mapping system 10 is preferably used to document and map projects being conducted at a worksite. The preferred system 10 is able to provide real-time information to users of the system 10 regarding numerous activities that are ongoing at the worksite, provide historical information related to the worksite, warn users of hazardous areas at the worksite and otherwise provide worksite information to users in a prompt, simple and convenient manner.

[0040] The system 10 preferably includes a central server 12 that communicates with other components of the system 10 over a network. The central server 12 is preferably configured to store at least a map 14 of the worksite. The worksite is not limited to any particular variety of worksite and may be comprised of a company facility, a manufacturing plant, a series of roads, a series of rail lines, a company building, a power plant, an airport, several spaced apart worksites operated by a common controller, a hospital and like worksites and/or facilities. The map 14 preferably includes representations of or presents equipment 16 and facilities 18 at the worksite. The map 14 is not limited to presenting or displaying only equipment 16 and facilities 18 and may include additional elements or features, as desired by a user, such as roads 20, railroads, utility lines, bodies of water, elevations, or nearly any other feature that may be desirable to show on the map 14. The central server 12 is preferably in communication with a display, generally designated 22, which may include first, second, third, fourth, fifth and sixth displays 22a, 22b, 22c, 22d, 22e, 22f or additional displays 22. The displays 22 are able to visually show the map with the various features thereon. In addition, the displays 22 may be comprised of touchscreen displays 22 the permit a user, such as a contractor, generally designated 24, or an employee, generally designated 26, to view the map 14 and interact with the system 10. The system 10 is not limited to including touchscreen displays 22 and may include nearly any display 22 that is able to show the map 14 for viewing by the users 24, 26. In the preferred embodiment shown in Fig. 1 , the users include first, second and third contractors 24a, 24b, 24c and first, second and third employees 26a, 26b, 26c. Each of these contractors 24 and employees 26 may have various levels of access to the system 10 and the ability to interact with and manipulate the map 14 and other portions of the system 10.

[0041] The central server 12 may be configured as a cloud computing service or as a stand-alone computing network that is able to carry out the preferred functions of the system 10. The central server 12 is preferably connected to the various displays 22 to provide nearly real-time update information to the map 14 and related information stored by the system 10. The central server 12 is not limited to any particular cloud computing service or configuration and may be comprised of nearly any computing configuration that is able to perform the preferred functions of the system 10, as described herein.

[0042] The central server 12 preferably stores an approved jobs database 28. The approved jobs database 28 maintains approved jobs information including a first approved job 28a. As shown in Fig. 2, the first approved job information of the first approved job 28a includes a first job location 30 associated with a first area 32 on the map 14. The first job location 30 is positioned at a lower right-hand corner of a Facility Z 18 and is denoted by an eCates, Inc. cone symbol. The first area 32 is comprised of a triangle, as shown in Fig. 2 and is associated with a first time period during which work will occur with in the first area 32. In the preferred embodiment, the approved jobs database 28 stores or maintains a plurality of approved jobs 28a, 28b, 28c, 28d for the worksite and may maintain a plurality of approved jobs for multiple worksites that may be accessed by various users 24, 26. For example, in the preferred embodiment shown in Fig. 2, the approved jobs information stored by the approved jobs database 28 also includes a second approved job 28b having a second time period and a second job location 34 associated with a second area 36 on the map 14, a third approved job 28c and a fourth approved job 28d. In the preferred embodiment, the second job location 34 and second area 36 are located in an upper, left-hand portion of the map 14 near a road 20 designated on the map 14. The first time period overlaps with the second time period and the first and second areas 32, 36 are spaced from each other. The third and fourth approved jobs 28c, 28d are also spaced from the first and second approved jobs 28a, 28b in the preferred embodiment. The preferred embodiment of Fig. 2 also includes a third job location 38 and a third area 40 of the third approved job 28c and a fourth job location 42 and a fourth area 44 of the fourth approved job 28d. The approved jobs database 28 is not limited to inclusion of the first, second, third and fourth approved jobs 28a, 28b, 28c, 28d at the displayed worksite and may be comprised of less or more approved jobs or various additional approved jobs at other worksites. In addition, the approved jobs 28 at the worksites are not limited to having the same type of approved job information and may have different information between jobs at the same worksite or different information for each approved job at various worksites.

[0043] In the preferred embodiment, the approved jobs database 28 includes the first approved job 28a having at least the first approved job location 30, the first area 32, the first time period and a first job identification. The first job identification preferably includes a description of the first approved job 28a and may include various details regarding the job, such as who is conducting the job, the equipment being used on the job, photographs related to the first approved job 28a or related information related to the first approved job 28a. The second, third and fourth approved jobs 28b, 28c, 28d are also shown in the preferred embodiment as including second, third and fourth approved job locations 34, 38, 42, second, third and fourth areas 36, 40, 44, second third and fourth time periods and second, third and fourth job identifications. The approved jobs database 28 is not limited to including this specific information or to the inclusion of only four approved jobs 28a, 28b, 28c, 28d. The approved jobs database 28 may include nearly any number of approved jobs 28 with nearly any type of information that is relevant to a particular scenario and is able to be stored using the central server 12.

[0044] The first area 32 in the preferred embodiment is defined by the triangle shown in Fig. 2 and is located proximate a corner of Facility Z 1 8 on the map 14, which is preferably presented by the display 22 to a user 24, 26. The first area 32 is not limited to having a triangular-shape or to the preferred first approved job location 30 of Fig. 2, as the first approved job 28a may be located at any location desired by the user 24, 26 and may have nearly any shape, such as the rectangular shape of the second area 26, the circular or oval shape of the third area 40, the square or rectangular shape of the fourth area 44, an irregular shape chosen by the user 24, 26 or nearly any shape that is able to be provided on the map 14 and presented by the display 22. T U 2012/058276

[0045] By way of non-limiting exampl e, in the preferred embodiment, the first area 32 is defined by at least a first point 32a, a second point 32b, a third point 32c, a first line 33a extending between the first and second points 32a, 32b, a second line 33b extending between the second and third points 32b, 32c and a third line 33c extending between the third and first points 32c, 32a, respectively. The points 32a, 32b, 32c and lines 33a, 33b, 33c preferably define the generally triangular shape of the first approved job 28a to generally define where the work will occur as a result of the first approved job 28a. Other personnel on the worksite during the will know by looking at the map 14 that work is ongoing at the first job location 30 within the first area 32 during the first time period and may be required to or desire to maintain a safe distance from the first area 32 during the first time period. In addition, for planning purposes, a controller 48 is able to plan for the conduct of the first approved job 28a and other approved jobs 28b, 28c, 28d at the worksite by visually comparing and considering the identified approved jobs 28a, 28b, 28c, 28d.

[0046] As part of a job planning process, as is described in greater detail below, a user 24, 26 may define the first area 32 by selecting the first point 32a, the second point 32b and the third point 32c on the map 14 on the display 22. The points 32a, 32b, 32c may be selected using the touchscreen display 22 or the points 32a, 32b, 32c may be otherwise selected, such as by utilizing a global positioning system (GPS) and identifying the points 32a, 32b, 32c on the map 14 as the user 24, 26 physically walks a perimeter of the first area 32, by inputting coordinates into the central server 12 or otherwise selecting the points 32a, 32b, 32c, as would be understood by one having ordinary skill in the art. The central server 12 of the preferred embodiment automatically draws the first line 33a between the first point 32a and the second point 32b, the second line 33b between the second point 32b and the third point 32c and a third line 33c between the third point 32c and the first point 32a, thereby defining the first area 32. The user 24, 26 may then add additional points (not shown) or otherwise manipulate the size and/or shape of the first area 32 to further or more definitively identify the first area 32, as desired. As was described above, the fist area 32 is not limited to triangular shapes, but the triangular shape of the first area 32 is included for illustrative purposes.

[0047] The system 10 of the preferred invention also includes a denied jobs database 46 stored at the central server 12. The denied jobs database 46 maintains first denied job information related to a first denied job 50 at the worksite. The first denied job information includes a first reason for denial of the first denied job 50 and a first denied job location 52. The first denied jobs database 46 preferably includes similar information to the approved jobs database 28, as the denied job information preferably results from a series of pending jobs input into the system 10 by the users 24, 26. The denied jobs and the approved jobs 28a, 28b, 28c, 28d preferably result from pending jobs that are denied by the controller 48 from a pending jobs database 54, as will be described in greater detail below. In the example shown in Fig. 2, the first denied job information of the first denied job 50 also includes a first denied time period and the first denied job location 52. The first time period of the first approved job 28a and the first denied time period over and the first job location 30 overlaps with the first denied job location 52. Accordingly, the controller 48 denies the first denied job 50 because of its overlap in time period and location with the first approved job 28a. As is shown in Fig. 2, the display 22 may show the first job location 30 overlapping with the first denied job location 52 on the map 14. The first denied job 50 may be stored on a denied job layer (not shown) that may be turned off and on selectively by the user 24, 26 and/or the controller 48 to alternatively show or hide the first denied job 50 or any additional denied jobs at the worksite 14.

[0048] The preferred system 10 also includes a pending jobs database 54 stored at the central server 12. The pending jobs database 54 maintains pending jobs information including a first pending job information of a first pending job 54a. The first pending job information includes a first pending location 56, a first pending time period and a first pending identification. In the preferred embodiment, the first pending location 56 of the first pending job 54a is shown on the display 22 on the map 14 of Fig. 2. The central server 12 is preferably configured to compare the first pending job information to the approved jobs information in the approved jobs database 28 to create a first recommendation regarding whether to approve the first pending job 54a. For example, the central server 12 preferably compares at least the fist pending location 56 to the job locations of the approved jobs 28a, 28b, 28c, 28d and the first pending time period to the related approved job time periods to determine if there is any overlap. The first recommendation is preferably based at least partially on whether there is overlap in location and time periods between the approved jobs 28a, 28b, 28c, 28d and the first pending job 54a. Additional factors may also be considered by the central server 12.

[0049J The system 10 of the preferred embodiment also includes an approved contractor database 58 stored at the central server 12. The approved contractor database 58 has a plurality of or listing of approved contractors 24 for the worksite. The central server 12 may include different listings of contractors 24 for various worksites or may include a single listing of approved contractors 24 for all worksites associated with the system 12. In addition, the approved contractor database 58 also preferably includes information related to the amount or limit of access the particular contractors 24 may have to different features of the preferred system 12. For example, certain contractors 24 may have read and edit access or access to various layers to depict specific features, facilities 18, equipment 16, roads 20 or other elements of the worksite. A utility contractor 24, for example, may have read and edit capabilities related to jobs associated with the utilities of the worksite, but may have only read capabilities for non-utility related jobs at the worksite. In the preferred embodiment, the various contractors 24 are required to register with the preferred system 12 to gain access and use of the system 12.

[0050] The preferred system 10 also includes an incident database 60 and a completed jobs database 62 stored at the central server 12. The preferred incident database 60 maintains incident information for a plurality of incidents and incident information at the worksite or at various worksites that are associated with the system 10. The incident information for each incident preferably includes incident date, incident location and incident description. The incident database 60 is preferably utilized to depict various incidents on the map 14 using the display 22 to assist in planning and safety remediation. For example, the controller 48 may be able to identify trends in incidents by visually observing and/or tracking incidents utilizing the system 10 or by statistically analyzing incidents with the preferred system 10. The system 10 is not limited to including the incident database 60 or any particular incident information in the incident database 60. The completed jobs database 62 preferably maintains completed jobs information, which is generally comprised of the same or similar information from the approved jobs database 28 after the respective jobs are completed or the time period expires. The completed jobs information of the completed jobs database 62 preferably includes a completion date, a completed job contractor name, a completed job location and a completed job description for a plurality of completed jobs. The completed jobs database 62 may be utilized to track routine maintenance that may be required at the worksite, to depict completed jobs on the map 14 utilizing the display 22, for statistical purposes to analyze completed jobs or for other related or similar reasons that would be apparent to one having ordinary skill in the art upon reviewing the present disclosure.

[0051] The preferred system 10 further includes a worksite map database 54. The worksite map database 54 is designed and configured to store various maps 14 at the central server of different worksites associated with the system 10. The system 10 preferably permits the controller 48 and/or contractors 24 and employees 26 to add and remove maps 14 from the system 10, depending upon whether a particular worksite is active. The central server 12 is preferably able to operate and show several different maps 14 with various layers of information to different contractors 24 and/or employees 26 simultaneously and transmit particular maps 14 to associated contractors 24 and employees 26, depending upon their granted access. For example, the first contractor 24a may only have access to view approved jobs 28a, 28b, 28c, 28d of a map 14 related to a manufacturing facility, while a first employee 26a may have access to the same manufacturing facility map 14 and a map 14 of a mine of the same company. The employee may also have access to review, edit, deny and/or approve pending jobs 54a for one of the worksites, but not for the other. Accordingly, the central server 12 is preferably able to filter the access of information to specific users 24, 26, dependent upon the level of access they are granted to the information stored in the databases 28, 46, 54, 58, 60, 62, 64, 66, 68, 70.

[0052] Although the preferred databases 28, 46, 54, 58, 60, 62, 64, 66, 68, 70 are shown as distinctly separate elements in the central server 12, the databases 28, 46, 54, 58, 60, 62, 64, 66, 68, 70 are not necessarily physically separate and distinct and may be different data sets stored together in a single database in the central server. The databases 28, 46, 54, 58, 60, 62, 64, 66, 68, 70 are meant to be a collection of data that may be stored and/or maintained in the central server 12 in nearly any manner or configuration, as long as the collection of data in the preferred databases 28, 46, 54, 58, 60, 62, 64, 66, 68, 70 can be stored, compared and otherwise manipulated in the normal operating procedures of the described safety, planning and environmental documentation and mapping system 10.

[0053] In operation, the preferred system 10 is preferably restricted for use by pre-approved and authorized users 24, 26. The system 10 may be accessed by entering a contractor name and a contractor password at a first display 22a by a first contractor 24a. The contractor name and password are preferably unique to the first contractor 24a and are received at the central server 12 for verification. The name and password may be submitted by the contractor 24 through the display 22, particularly if the display 22 is a touchscreen display 22, or may be otherwise submitted to the central server 12. The central server 12 compares the received contractor name and the contractor password to a plurality of stored contractor names and stored contractor passwords in the approved contractor database 58. The central server 12 activates the system 12, thereby permitting access to the system 12 by the first contractor 24a, if the contractor name matches one of the plurality of stored contractor names and the contractor password matches the corresponding one of the plurality of stored contractor passwords in the approved contractor database 58. The first contractor 24a is not limited to gaining access to the system 10 using the contractor name and associated contractor password and the system 10 may be restricted in numerous alternative manners, such as by keycard, key, biometric scanner or other access restriction features, which would be known to one having ordinary skill in the art. However, some variety of restriction and/or identification of the contractor 24 is preferred to limit access of the specific contractor 24 to particular features, maps 14, worksites or the like to the specific contractor 24. 6

[0054] The contractor 24, after gaining access to the system 10, preferably submits the first pending job information associated with the first pending job 54a including the first pending location 56, a first pending time period and a first pending identification. The first pending job information is received by the central server 12 and is stored in the pending jobs database 54. The central server 12 compares the first pending time period associated with the first pending job 54a to a plurality of approved time periods associated with a plurality of approved jobs that are stored in the approved jobs database 28. The central server 12 also compares the first pending location 56 to the plurality of job locations 20, 24, 28, 42 associated with the plurality of approved jobs 28a, 28b, 28c, 28d. The central server 12 preferably conducts the comparison to determine if there are conflicts or overlaps between the first pending job 54a and the plurality of approved jobs 28a, 28b, 28c, 28d. Based on the comparison, the central server 12 transmits an approval recommendation if both the first pending time period and the first pending location 56 do not both overlap with the plurality of approved time periods and an associated approved location 30, 34, 38, 42. In contrast, the central server transmits a denial recommendation to the controller 48 if both the first pending time period and the first pending location 56 overlap with the plurality of approved time periods and an associated approved location 30, 34, 38, 42. The approval or denial recommendation is preferably transmitted by the central server 12 to a controller display 49. The controller 48 preferably considers the approval or denial recommendation. The controller 48 may elect to edit the first pending job 54a to eliminate or modify any conflicts, such as by changing the proposed time period and/or first pending location 56, may compare the first pending job 54a to other information stored in the central server, such as information in the incident database 60. The controller 48 may also approve or deny of the first pending job 54a based on the recommendation of the central server 12. Once the first pending job 54a is approved or denied, the contractor 24 preferably receives notification of the approval or denial from the central server 12.

[0055] The preferred system 10 may also be designed and configured such that the central server 12 is in communication with a machine or related equipment 16 at the worksite. Based upon information stored in the databases of the central server 12, the central server may send a signal to the machine or related equipment 16 to disable the machine 16 for a predetermined lockout time period. The central server 12 may lock-out or tag-out the machine 16 during maintenance on the machine 16 that is identified by one of the approved jobs 28a, 28b, 28c, 28d of the approved jobs database 28, as a result of work being conducted at one or more of the job locations 30, 34, 38, 42 that interferes with the operation of the machine 16 or for nearly any reason that a controller 48 may want to lock-out or tag-out a machine 16, as would be apparent to one having ordinary skill in the art. The central server 12 is preferably able to lock-out the machine 16, thereby preventing operation of the machine 16, for a predetermined lockout time period, which may coincide with the approved job that is being avoided or otherwise. At the conclusion of the predetermined lockout time period, the central server 12 preferably sends a signal to the machine 16 to again permit use of the machine 16 and withdraw the lock-out or tag-out instruction. During the lockout time period, the machine 16 is preferably inoperable, at least until the predetermined lockout time period expires or the controller 48 overrides the lock-out.

[0056] In the preferred embodiment, once the controller 48 approves the first pending job 54a, the first pending job 54a and its associated first pending job information is converted by the central server 12 to an approved job 28. The first pending job 54a is converted by moving the first pending job information from the pending jobs database 54 to the approved jobs database 28. Appropriate symbols, areas 32, 36, 40, 44 and related information are also converted on the display 22 and the map 14 such that the users 24, 26 of the system 10 are aware of the conversion and can coordinate and plan accordingly.

[0057] The central server 12 is likewise able to convert the first pending job 54a to the first denied job 50 when the controller 48 denies the first pending job 54a. The first pending job 54a is converted by moving the first pending job information from the pending jobs database 54 to the denied jobs database 46 after the controller 48 denies the job 54a. Appropriate symbols, areas 32, 36, 40, 44 and related information are also converted on the display 22 and the map 14 such that the users 24, 26 of the system 10 are aware of the conversion and can coordinate and plan accordingly. For example, the first pending job 54a may be completely removed from the map 14 upon denial to indicated to the users 24, 26 that a request is no longer pending at the proposed location during the indicated time period and alternative proposals may be implemented for the time period and location.

[0058] The verified contractor 24 or employee 26 may also report incidents for storage at the central server 12 for tracking, remediation, statistical, reporting or other purposes. The user 24, 26 may input a first incident report that is received by the central server 12. The first incident report preferably includes a first incident location for placement of a symbol or other reference on the map 14 and a first incident description. The first incident description may include a text description of the incident, photographs or nearly any variety of description that may be relevant to the incident being reported. The central server preferably stores the first incident report in the incident database 60 and may develop or create a layer for overlay onto the map 14 to visually depict the incident. For example, if a worker slips and falls on a broken staircase at the worksite, the contractor 24 or employee 26 may mark the location on the map 14 and provide a text description of the incident, along with a description. The description may also include a photograph of the broken stair and a remediation plan and timeline to repair the broken staircase. Such information may be

communicated to all of the users 24, 26 of the system 10 to limit subsequent incidents at the incident location. Certain of the information of the incident report may also be transmitted by the central server 12 to a hazard database 66. The incident database 60 of the preferred system 10 includes a plurality of incident reports that the central server 12 may visually show on the displays 22 for safety, tracking and related purposes.

[0059] When a time period of one of the approved jobs 28a, 28b, 28c, 28d expires and/or the controller 28 verifies the particular approved job 28a, 28b, 28c, 28d is completed, the approved job 28a, 28b, 28c, 28d is converted by the central server 12 to a completed job. The approved job 28a, 28b, 28c, 28d is preferably converted to a completed job by moving the approved job information from the approved job database 28 to the completed job database 62. The conversion is preferably visually indicated to the users 24, 26 of the system 10 by removing the associated symbols and markings from the map 14. The users 24, 26 may be able to subsequently again show the completed jobs from the completed job database 62 by requesting such a display from the central server 12. The completed jobs may be utilized by users 24, 26 to develop a subsequent pending job by modifying one of the completed jobs, particularly when a subsequent job has similar features as a previously finished completed job, which is preferably stored in the completed jobs database 62 for later use.

[0060] In use, the preferred central server 12 also compares the first pending job 54a to information stored in the hazards database 66 and an off-limits database 68. The central server 12 may base it approval or denial recommendation at least partially on such comparisons and the controller 48 may also based a final approval or denial of the first pending job 54a on the

comparison of the first pending job information with the information in the hazards database 66 and the off-limits database 68.

[0061] In operation of the preferred system 10, the plurality of approved jobs 28a, 28b, 28c, 28d are each associated with one of a plurality of approved time periods. The central server 12 preferably transmits a signal to at least one of the contractor displays 22a, 22b, 22c to present or show all of the plurality of approved jobs 28a, 28b, 28c, 28d at a current or real time period, when the current time period overlaps with one of the plurality of approved time periods. Accordingly, the contractors 24a, 24b, 24c are able to visually determine location and type of work that is being conducted at the worksite, thereby improving safety for the contractors 24a, 24b, 24c and company U 2012/058276 employees 26a, 26b, 26c at the worksite. The approved jobs 28a, 28b, 28c, 28d are preferably displayed using a symbol on the map 14 that may convey the type of task or job being performed at the particular job location 30, 34, 38, 42. For example, the first and second approved job locations 30, 32 are identified by an orange cone-shaped symbol in Fig. 2.

[0062] The preferred system 10 allows a chronological and spatial planning framework for construction, heavy industry, manufacturing, mining, energy, municipal, governmental and other like worksites and/or application. The framework of the preferred system 10 allows multiple users 24, 26 to plan within a confined workspace while still monitoring and planning their

processes/projects in a chronological fashion. Although the preferred map 14 is shown as a two dimensional map, the map 14 is not so limited and may be comprised of a drawing, a three- dimensional model or any other type of work area that may be visually presented to a user 24, 26.

[0063] The preferred system 10 is designed and configured to have the ability to display historical, current and future projects, processes and data and how these relate to other projects, processes and data within a geographic, 3-dimensional or other type of spatial environment on the map 14. The historical, current, future and related projects or jobs are shown in various

combinations to the users 24, 26 using the displays 22, 49 to facilitate increased job-site or worksite communication (both live and during the planning phase), increased job safety through reduced accidents, incidents and/or near-misses, reduced conflicts or overage charges wherein contractors 24 and/or employees 26 are waiting for crews to exit an area before they are able to enter a particular space in the worksite to conduct their work and better emergency response cycles. Any incidents that do occur at the worksite can also be tracked and logged in the incident database 60 of the preferred central server 12.

[0064] The preferred system 10 utilizes the job locations 30, 34, 38, 42 and associated areas 32, 36, 40, 44 to achieve a spatial planning solution. The areas 32, 36, 40, 44 may be comprised of a point or points, a circle, an oval, a polygon, a square, a rectangle, a cross, a star, irregular shapes, three dimensional spaces, lines or other like shapes and spaces that are able to be depicted on the map 14 to spatially identify the jobs 28a, 28b, 28c, 28d, 54a or other related components, features and elements of the worksite. The spatially planned areas 32, 36, 40, 44 are preferably coordinated by comparing pending jobs 54a with approved jobs 28a, 28b, 28c, 28d, facilities 18, equipment 16, roads 20, hazards, lock-outs, off-limits areas or other features and/or elements that may be positioned or timed to overlap at the worksite. For example, when the various pending jobs 54a conflict with the approved jobs 28a, 28b, 28c, 28d, the preferred system 10 can set off a work flow that denies or approves the pending jobs 54a, alerts proper personnel such as the controller 48 or shows the conflicting areas on the display 22 and the nature of the conflict. These pending jobs 54a can also be used in conjunction with other control systems for machinery or equipment 16, systems, vehicles, facilities 18, roads 20 and other like worksite features to prevent entry/interference in these areas during the planned event. The data collected during the planning process utilizing the preferred system 10 can be used to display a historical, current, or future map 14 showing any and/or all the pending and approved jobs 28a, 28b, 28c, 54a scheduled to occur within the worksite and the display 22 of the map 14 can also be filtered such that only features or elements in a predetermined time period are shown on the display 22. Historical data can also be used to discover what has been done in a particular portion of the worksite in the past by reviewing or depicting information from the completed jobs database 62. All of the data collected during use of the preferred system 10 can be retained in the various databases 28, 46, 54 58, 60, 62, 64, 66, 68, 70 on the central server 12 and utilized at a later date for planning purposes or used for future reporting, planning, and/or scheduling processes.

(0065] Referring to Figs. 1 -13, contractors 24, employees 26 or other personnel of a particular company or organization are able to log into the preferred system 10 (once registered and company profile information is entered into system 10, See Figs. 5 and 8) and plan jobs (See at least Fig. 6). The personnel 24, 26 will preferably pick the location of their jobsite on the map 14, which is preferably pre-loaded with location information, for example, latitude and longitude information in the worksite map database 70 on the central server. The information related to the map 14, such as the map 14 itself, may be pre-loaded onto the central server 12 or entered by one of the users 24, 26. Once this information is completed, the contractor 24 or other personnel may proceed to fill out a basic project information form, which may request basic information, such as type of job, time, date, contractors on-site, etc. and provide title and project info for project mapping purposes (See generally Fig. 6). The contractor 24 is preferably requested by the system 10 to complete an environmental impact questionnaire 72 and submit answers to the questionnaire 72 for filing with the system 10 and storing in one of the databases 28, 46, 54, 58, 60, 62, 64, 66, 68, 70. Certain questions of the questionnaire 72, if appropriately filled out/marked, may alert appropriate personnel, such as the employees 26 of the company or the controller 48, providing the opportunity for project or job oversight, such as editing, denial and/or approval. The contractor 24 other personnel preferably proceeds to customer specific documentation material forms. These forms can include but are not limited to safety checklists, confined space permits 74, electrical hot-work permits 78, excavation permits 76, demolition permits, waste material permits, burning/welding forms 80, building permits 82, street closure permits or planner 84, utility impact planner 86, sewer 6 work planner 88, road service planner 90, lock-out/tag-out planner 92 and other similar forms, planners or information. These documents are preferably linked by the preferred system 10 and all appropriate documents are automatically requested based on safety checklist answers/markings. The contractor 24 may submit documentation to the system 10 for approval, and various jobs and projects can be compared and contrasted with relevant information that is provided to the system 10. Based on the location information, which is generally stored in the pending jobs database 54, the approved jobs database 28, the denied jobs database 46 or the completed jobs database 62, for example, the preferred longitude/latitude data attached to project, and/or job-type information, the project or job is preferably submitted to area/project appropriate employees 26 or personnel for safety, environmental and area manager approvals. Appropriate personnel, such as approved employees 26 and/or the controller 48, will be determined by use of locations on the map 14 and/or drop-down lists available to the contractor 26 in the job-planning processes. The system 10 preferably checks the existing approved jobs databases 28 and alerts or provides a recommendation to appropriate personnel or employees 26 to possible conflicts with other already approved jobs 28a, 28b, 28c, 28d, i.e. within certain radius or distance from a pending job 54a, which is preferably customer determined, on the same date or time as the pending job 54a. Additional parameters within the preferred system 10 can be set to alert proper departments/personnel when work is being done on utilities and then present possible conflicts/service or utility interruption. Personnel, such as employees 26 or the controller 48, can override the system 10 and approve the particular pending job 54a even if a conflict exists, but the system 10 preferably alerts or provides a recommendation to the contractor 24 or other personnel of approved jobs 28a, 28b, 28c, 28d in close proximity to the pending job 54a to afford the contractor 24 and/or employees 26 greater safety and project location awareness of fellow contractors 24 and/or approved jobs 28a, 28b, 28c, 28d. If the relevant project is approved by the controller 48, the pending job 54a is entered into or converted to the approved jobs database 28 that is used for safety and planning purposes. If the pending job 54a is denied, based on conflicts or any other reason so afforded by supervising personnel, such as the controller 48, the pending job 54a is retained in the pending jobs database 54 and the contractor 24 or other personnel is notified as to status and reason for rejection. The contractor 24 can re-submit the pending job 54a, cancel the pending job 54a, change pending job 54a or otherwise address the particular issues with the relevant request and re-submit. Once the pending job 54a is approved, the contractor 24 or other personnel is notified and permit approvals are established as the project information is now entered into the approved jobs database 28. If the particular pending job 54a is finally denied, the pending job 54a is converted to the denied jobs database 46. [0066] Customers, contractors 24, employees 26 or other users can use the preferred system 10 to receive and approve or reject project site requests for contractors 24 as well as for mapping and project supervision purposes. Customer's appropriate personnel, such as company employees 26 and/or the controller 48, will be notified, preferably via email, text or voicemail message, but not so limited, when they have a project in their area or in their field of supervision to log onto the system 10 and approve or deny permission for the pending job 54a. Once the pending job 54a is approved, customers, such as contractors 24, employees 26 and the controller 48, can search the maps 14 based on any number of criteria, such as calendar date, time and type of project/job and/or contractor or nearly any other parameter that is included in the project databases 28, 46, 54, 58, 60, 62, 64, 66, 68, 70. Project or job location searches preferably result in scalable, pan-able maps 14 that contain icons and/or symbols showing project locations, such as the approved job locations 30, 34, 38, 42. With mouse-over or touch screen displays 22, the icons or symbols (Fig. 2) that are included on the maps 14 to identify specific projects or jobs, such as the approved jobs 28a, 28b, 28c, 28d, preferably reveal project location title, but are not so limited and may reveal nearly any information about the specific project or job 28a, 28b, 28c, 28d that is included within the databases 28, 46, 54, 58, 60, 62, 64, 66, 68, 70, such as the presence or absence of potentially hazardous chemicals involved in completion of the project or job 28a, 28b, 28c, 28d. With single click on icon or single touch symbols, a brief description of project or job location 30, 34, 38, 42 and type is preferably displayed on the map 14 along with contact information for the contractor (directly useable on smart-phones) and a link to more in-depth descriptions and photos/documents related to the project or job location 30, 34, 38, 42 are also preferably revealed. For example, Figs. 19, 21 , 23-25 and 27 show the map 14 with a description symbol 91 listing specific details about a job 28a, 28b, 28c, 28d, 54a or a particular area of the map 14. Additional tools for incident reporting, hazard mapping and project planning are preferably made available to customers, employees 26, the controller 48 and/or contractors 24 using similar frame- work and systems as the job-approval process described above.

[0067] Additional parameters available through the preferred planning system 10 may include the utility impact planning process 86, an alarm and safety warning device monitoring module, lockout/tag-out mapping modules in the lock-out/tag-out planner 92, base level operations mapping and databases, live global positioning system ("GPS") monitoring of location of contractors 26, employees 24 and workers in work-site area, off-limits area mapping/databases such as the off- limits database 68 and live camera links available through the preferred system 10 with the use of on-map icons and links as well as listed links in other areas available to web-site users 24, 26, 48. The GPS monitoring may also be utilized to track inventory, equipment 16, employees 26, U 2012/058276 contractors 24, parts or like features on the worksite through communication between a sensor (not show) attached to the item and the central server 12. The sensor is preferably attached to the item and sends a wireless signal to the central server 12, which is able to present the item on the display 22. Examples of the icons and portions of the mapping can be seen at least at Figs. 2, 23, 24 and 27.

[0068] When utilizing the preferred system 12 for utility impact planning (Fig. 14), the contractor 24 or employee 26 may denote a circuit, line, section or system of a utility that they would be working on. This data would preferably be compared to information stored in the central server 12 in a utility use database 94 of the system 10, which is preferably designed and

implemented through cooperation with the customer and/or controller 48, to determine what areas on the worksite or map 14 would be affected by a scheduled service loss/potential service loss to each particular utility. This could be used for any type of utility i.e. electric, telecommunications, gas, water, sewer, computer/data, etc... The location of such scheduled service loss/potential service loss could be marked with an icon or symbol on the map 14, which may include a description of the type of loss/potential service loss, timing and related information, to provide information to site personnel for planning, safety and other jobsite purposes. Such information related to the utility job could also be stored in the approved jobs database 28 so that any potential conflicts could be checked with approved and/or pending jobs 28a, 28b, 28c, 28d, 54a.

[0069] Alarm and safety warning device monitoring may be implemented to allow the preferred system 10 to monitor readings or alarms from various types and locations of safety devices at the worksite. Results of the monitoring could be used to present readings on the displays 22 or to trip limits that would notify proper personnel of such alarms or limits. This would allow the customer, controller 48 and/or employee 26 to set acceptable limits for monitoring devices and/or alert the appropriate personnel of possibly hazardous situations, such as alerting contractors 24 or employees 26 that are scheduled to be working within a predetermined proximity of the alarm area. These alarms and readings could be linked into the map 14 of the preferred system 10 and displayed as links, icons, lists, symbols or other displayed data. These alarms, readings and or resulting data are also preferably available for use in control systems i.e. crane, locomotive, equipment 16 and/or other machinery automated controls, stops, limits or other safety measures implemented to protect workers, workspace, equipment, property etc...

[0070] Lock-out/tag-out mapping and databases (Fig. 15) may be implemented to allow contractors 24, employees 26, the controller 48 and/or customers to mark and map the areas, lines, systems, facilities 18, equipment 16 or controls that have been locked out or tagged out. The information or data stored in the lock-out/tag-out database 64 preferably includes a personnel responsible, approving department or personnel, or any other pertinent data or information. The data can be researched and displayed on the map 14, in lists, on schedules, etc. and may be searchable by contractors 24, employees 26, the controller 48 or other related personnel in conjunction with other job-site information. The preferred system 10 may be used for stand-alone lock-out / tag-out requests. These requests preferably follow the same approval process as described for job/project approval requests.

[0071] Base-level operational mapping with the preferred system 12 is preferably conducted in cooperation with the customer, the controller 48 or the employees 26 to provide a database of standard operations, personnel, processes or related items that take place in normal operating conditions and times. This database could also be linked to or store within additional databases showing work-schedules, personnel schedules, contact data and like information that would allow the preferred system 10 to show possible job-conflicts with work being scheduled, as well as provide contact info for workers, employees 26, contractors 24, the controller 48, departments or areas, as well as automatically notify these areas, departments or workers of projects scheduled or taking place in their area. Certain types of operations could also be marked by the preferred system 10 with priorities such that priority jobs may shift the timing and/or location of lower priority operations. That is, certain of the approved jobs 28a, 28b, 28c, 28d or the pending jobs 54a may be set to have varying levels of priority and a higher priority pending job 54a may displace one or more of the approved jobs 28a, 28b, 28c, 28d. Further, the preferred system 10 may be constructed to have the capability to automatically reject certain pending jobs 54a at a specific location due to conflict or to provide alternate scheduling for such pending jobs 54a. Accordingly, the central server 12 may have rules in place that automatically provide differing priority to particular pending jobs 54a, to automatically reject certain pending jobs 54a if they conflict with a particular area of the worksite or a predetermined time period or any number of predetermined rules that assist in efficient operation of the worksite.

[0072] Live GPS monitoring of the worksite, including monitoring of workers, equipment 16, facilities 18, contractors 24, employees 26, inventory and related items and/or elements may allow greater detail of job-site data as well as providing an opportunity to improve safety of all jobs 28a, 28b, 28c, 28d, 54a being conducted at the specific worksite. This preferably real-time and constant GPS monitoring would provide data and information that could be used in alarm systems that assists in preventing accidents, such as the contractor 24 working outside of permitted/approved areas 32, 36, 40, 44 as well as avoiding collisions with equipment 16 and/or systems on the job-site. The monitoring could also assist in limiting accidents if the contractors 24 or employees 26 enter a 2012/058276 prohibited or restricted area, such as an area stored in the off-limits database 68, the hazard database 66 or other like areas. The various information may be utilized to render different layers for mapping on the map 14, as well as data for lists, schedules and or other related materials. This feature could also be used in asset tracking and monitoring as well as monitoring systems such as trucks, transporters, earth-moving equipment 16, cranes, trains etc allowing the central server 12 to over-see the entire job-site or worksite processes and status of machinery and related equipment 16.

[0073] Off-limits area mapping that is preferably conducted with information stored in the off- limits database 68 may be implemented to allow the controller 48, contractors 24 and/or employees 26 to denote areas on the worksite that are restricted access or off-limits to activity, equipment 16, personnel and nearly any other items. This data and/or information is preferably stored in the off- limits database 68 which is preferably searchable and the data and results are preferably available for presentation on the map 14, in lists, on documents or otherwise with the displays 22. The off- limits database 68 is preferably utilized when searching in the job-approval process as described herein. This off-limits database 68 information and data may also be utilized as an additional layer available for mapping with the central server 12.

[0074] Another feature preferably available through the system 10 is links to live on-site cameras (not shown). Communication between the preferred system 10 and live on-site cameras allows monitoring of the worksite and the various jobs 28a, 28b, 28c, 28d occurring in any particular area that has camera coverage, such as the approved job areas 32, 36, 40, 44. The cameras are preferably in communication with the central server 12 such that the video feed may be displayed on the displays 22, in list format, as links/buttons on web-site pages and or icons with attached links that can be displayed as an additional layer on the maps 14 as well as an additional stand-alone maps 14 available through the web-site. The cameras are not necessarily continuously operating and taking photos or video of a particular location 30, 34, 38, 42, but may be operated as motion sensor- type cameras (not shown) or may take video or photos at predetermined intervals and communicate these videos and/or photos to the central server 12. For example, motion sensor-type cameras may be employed for approved job areas 32, 36, 40, 44 or at locations that are off-limits, as may be stored in the off-limits database 68. These motion sensor type cameras may only operate when motion is detected in an off-limits area, as defined in the off-limits database 68.

[0075] Some of the additional features that may be included in the preferred system 10 include the ability to cancel and reschedule approved jobs 28a, 28b, 28c, 28d and/or pending jobs 54a. This feature preferably allows contractors 24, employees 26, the controller 48, customers and/or system managers to reschedule approved or pending jobs 28a, 28b, 28c, 28d, 54a using already entered data to request a different time, date, location or nearly any other modification. Such rescheduling and/or cancelling of jobs 28a, 28b, 28c, 28d, 54a may be automatically employed by the system 10 or may require intervention or approval by control personnel, such as the controller 48, of the system 10 or may present rescheduling or cancellation proposals to the control personnel, such as the controller 48, of the system 10.

[0076] The preferred system 10 may include login and system 10 use via phone. This feature preferably allows system users and/or approved contractors 24 listed in the approved contractor database 58 to access the approval/denial system from remote locations allowing for smoother job approval processes, even when an approving party is inaccessible by standard system processes. The remote access may be conducted through nearly any medium that permits a user or control personnel to remotely communicate with the system 10.

[0077] The preferred system 10 may also include a start/stop feature. The start/stop feature preferably allows contractors 24, employees 26, the controller 48, customers, workers or like entities to cause projects to "go-live" by using phone, laptop, smart phone, applications or other access to the system 10 to initiate start time and stop time of scheduled project. This feature preferably allows the system 10 to further evolve the ability to handle billing, time cushions, rescheduling, continuation of jobs, and like functions. Utilizing improved billing features, customers, contractors 24, employees 26 and/or the controller 48 will be able to use the system 10 to help monitor time- sheets and billing practices of their contractors 24. This would also sync well with scheduling and other existing corporate systems promoting a fully integrated job-site, worksite or multiple job-sites and worksites.

[0078] The preferred system 10 may further include lock-out/tag-out approval levels that interacts with the lock/tag-out database 64. The lock-out/tag-out approval levels feature preferably requires all lock-out/tag-out's to be approved based information such as location, system being locked out, and related information, which is preferably approved by proper authorities, such as the controller 48. The lock-out/tag-out approval may also be employed automatically by the system 10 itself or by a combination of the system 10 and human intervention, such as interaction with the controller 48.

[0079] The system 10 also preferably includes a superintendent access level(s) feature. The superintendent access level feature preferably allows a user, such as the contractor 24, the employee 26, the controller 48 or other user, to force job approvals (emergency jobs) and gives the ability to start, stop and extend jobs. This feature permits flexibility for the preferred system 10, particularly in emergency project or job situations. [0080] The system 10 also preferably includes a customer operator level feature. The customer operator level feature preferably allows area managers, supervisors and related personnel, the ability to plan jobs with contractors 24, employees 26, in-house maintenance personnel and like individuals to submit approvals on the spot. This feature preferably speeds the approval process, potentially for priority or emergency jobs.

[0081] The system 10 preferably has the ability to cancel and modify jobs 28a, 28b, 28c, 28d, 54a at short-notice for emergency reasons (permits, approvals etc... will require disclaimers notifying contractor/worker of this and preferably requires the application process to procure an emergency # for contacting contractor/worker of these changes).

[0082] An additional feature of the preferred system 10 is a live monitoring of lock-out devices, which preferably interacts with the lock/tag-out database 64. This feature preferably allows for mapping and monitoring the particular location and status of lock-out devices. Such a feature provides notification to personnel, such as the contractor 24, the employee 26, the controller 48, regarding lock-outs of equipment 16 that the personnel may require to limit down time or wasted time for the personnel.

[0083] In another aspect, the system 10 preferably includes safety beacons that alert system users, such as the contractor 24, the employee 26 or the controller 48, and emergency personnel of hazard, incident and other emergencies at specific locations. Such emergency and/or hazard information may be stored in the hazard database 66. The safety beacons may be employed in nearly any manner that provides notification to the users, such as the contractor 24, the employee 26 or the controller 48, and/or emergency personnel, such as indications on the map 14, audible or visual warnings and/or messages sent to communication devices, such as the displays 22, of specific or all personnel who have access to the system 10.

[0084] The preferred system 10 and particularly if the system 10 is adapted specifically for utilization as a municipal access system 10, may also include a feature that allows accident reporting and road-closure/other job-site or worksite information to be communicated to emergency personnel and departments for various reasons. The communication may be nearly any message, as are described above that are transmitted to appropriate personnel.

[0085] The preferred system 10 may also include an alarm system feature that will alert users of jobs nearing pre-set deadlines for project approval/denial. For example, the controller 48 may preset a specific amount of time within which a pending job 54a must be approved or denied are create a rule the is automatically implemented by the central server 12. The preferred system 10 will attempt several notifications by selected area manager/supervisor before potentially passing the project approval along to secondary approval level (each user will select a back-up user that would be requested in this case.) This feature preferably keeps job approval processes moving along even when there are absent employees 26, vacations and other circumstances that delay the processing of pending jobs 54a.

[0086] The system 10 also preferably includes employee/user ability to notify the system 10 of expected absences. The absence notification feature preferably permits the system 10 to notify a user, contractor 24, employee 26 and/or the controller 48 that a particular employee 26 is inaccessible for an expected period of time, allowing for smoother job-approval processes. Such notifications are preferably implemented automatically by the central server 12.

[0087] The entire system 10 is preferably used for mapping using the two-dimensional and three-dimensional maps 14, three-dimensional models and system layout information. This preferred system 10 can be used in projects as varied as steel mills, industrial sites, railroads, municipalities, constructions sites (i.e. single buildings, shopping malls, developments, high-rises), ship-building, and related worksites. The preferred system 10 may also be implemented during the design phase of a project to monitor construction of a facility and subsequently monitor the completed facility.

[0088] Referring to Fig. 4, the preferred system 10 may communicate with user through various web-based graphical interface units ("GU I"). Various components of a preferred main page GUI, which is preferably presented on the displays 22 to users, are shown in Fig. 4. The main page GUI preferably includes general information about the preferred system 10, a contact reference, a sign-in reference and a register reference. The system 10 generally related to an online documentation and mapping system 10 that provides customers with improved safety awareness through online documentation and jobsite mapping. The system 10 also preferably provides disaster recoverability, reduced liability, improved job-site or worksite controls and related benefits. The displays 22 may be comprised of smartphones with touch screens, laptop computers, desktop computers,

workstations or related mechanisms.

[0089] Referring to Fig. 5, the contractor 24, employees 26, controller 48 or nearly any user desiring access to the preferred system is required to sign-in to the system 10. A sign-in GUI may be different for varied users, depending upon the users perceived requirements for the system 10. In addition, once the particular user is logged into the preferred system, the particular user's GUI is preferably different depending upon the user's previous use of the system and the type of user accessing the preferred system 10. For example, a contractor 24 may land on a contractor dashboard GUI following log-in that may present the contractor's pending jobs 54a, statuses of pending job 54a approvals, a new job reference, a job request status reference, a cancel job reference to potentially cancel a pending job 54a, an update profile reference to permit update of the contractor's 24 profile information that is preferably stored in the approved contractor database 58, an emergency job reference that may permit entry of an emergency or priority job for approval and other like references. This initial contractor GUI preferably includes at least the plan new job reference, which preferably leads to interaction with at least the pending jobs database 54. The contractor's 24 initial landing GUI also preferably permits job request status and cancel job options, which typically result in interface with at least the pending jobs database 54.

[0090] Referring to Fig. 6, a basic job planning GUI of the preferred system 10 permits the particular user to input at least a pending job 54a and typically requests pending job information, such as job type, time period, date, duration, environmental impact and other related information. The job planning GUI may also include options for customer planning/emergency job planning or a user may be routed to the job planning GUI to input customer planning and/or emergency job planning information. The job planning GUI preferably prompts the user or provides options to provide information to the central server 12, depending upon the type of pending job 54a, such as interaction with the lock-out/tag-out planner 92, the environmental planner 72, the confined space planner 74, the burning/ welding planner 80, the excavate planner 76, the energized electric planner 78, the building permit planner 82, the street closure planner 84, the utility impact planer 86, the sewer work planner 88, the road services planner 90 and other related planners. Interaction with these planners 92, 72, 74, 80, 76, 78, 82, 84, 86, 88, 90 preferably leads the contractor 24 or other user through a series of steps to ensure that the user has proper licenses, permits, training, permissions and related prerequisites for conducting the desired job. The above-listed planners 92, 72, 74, 80, 76, 78, 82, 84, 86, 88, 90 are not meant to be all-inclusive and additional planners may be implemented by the preferred system 10. The contractor 24 is preferably able to provide and transmit the relevant information to the central server 12 for storage and approval of the pending job 54a. The contractor 24 is also preferably able to print hard copies of the information for their own use. All of the information from the planners 92, 72, 74, 80, 76, 78, 82, 84, 86, 88, 90 is preferably entered into the pending jobs database 54 for review. As part of the planning process, the contractor 24 is also preferably able to select a job location 30, 34, 38, 42 on the map 14, which may be selected on the display 22, user longitude and latitude, with GPS by walking a boundary or otherwise. Certain contractors 24 are allowed area wide access or blanket access to certain areas on the map, such as roads 20 for snot plowing or other road maintenance services. The selection of particular areas may also prompt the central server 12 to require approval from selected or predetermined personnel, such as the controller 48. The information and/or data is preferably automatically sent by the central server 12 to proper approval authorities as a pending job 54a and the central server 12 may automatically send email/text notifications to specific authorization authorities, such as the controller 48. Upon approval, denial, modification or during steps in the approval process, the central server 12 preferably notifies the contractor 24 of the progress of the pending job 54a and also prompts the authorizing authorities to review the pending jobs 54a. For example, the authorizing authorities may be prompted to provide answers related to planning sheet determinations, provide an approval or denial, or related actions.

[0091] Referring to Fig. 7, the preferred system 10 preferably automatically transmits the pending job 54a depending upon whether the pending job 54a is approved or denied by the customer, such as the employee 26 or the controller 48. For example, approval of the pending job 54a preferably generates a message, such as an email, to the appropriate contractor 24, which preferably includes an approval notice and other notifications, such as proximity to safety services, other contractors 24 conducting work in close proximity and related information. The pending job 54a is also preferably converted from the pending jobs database 54 to the approved jobs database 28 and into an approved job 28a, 28b, 28c, 28d. If the authority denies the pending job 54a, the pending job 54a is preferably converted to the denied jobs database 46, a notification is sent to the associated contractor 24 and the contractor 24 is preferably able to make requested changes and resubmit as a new pending job 54a and the pending job 54a re-enters the pending jobs database 54.

[0092] Referring to Fig. 8, the preferred system 10 is also able to register new users, such as contractors 24 and/or controllers 48. The controllers 48 typically register as new customers and customer information is entered into a customer database 96 in the central server 12. Information for the customer database 96 may include, but is not limited to contact information, approval authorizations, rules, approved contractor lists, maps 14 and related information. The registration GUI also preferably includes a contractor registration page for registration of new contractors 24. The information entered by new contractors 24 is preferably stored by the central server 12 in the approved contractor database 58. The registration GUI also preferably indicates the new contractor 24 and/or control ler/customer 48 will be contacted by a company sales representative.

[0093] Referring to Fig. 9, a customer or controller dashboard GUI preferably includes access to references to cancel/extend/reschedule pending jobs 54a, approve or deny pending jobs 54a, information displayed based on access levels, information related to emergency jobs, access to a map page, access to incident reporting, hazard-safety news, completed jobs and other related information. The customer dashboard preferably permits the controller 48 to search the map 14 by 2012/058276 incident, job-type, calendar (and time), date and by contractor 24. Databases that may be search able by the controller 48 include the lock-out/tag-out database 64, the off-limits database 68, the pending jobs database 54, the approved jobs database 28, the completed jobs database 62, the incident database 60, the hazard database 66 and any additional databases. Results of the searching is preferably presented on the controller display 49 on the map 14 with symbols to denote various jobs and other items. The controller display 49 preferably includes a feature to present pop-ups when moused-over of touched by the controller 48. Double-click on the symbols or identifiers also preferably provides a full description of the particular job. Live cameral links may also be available, as well as the ability to view and print results.

[0094] Referring to Fig. 10, an incident reporting GUI preferably permits reporting of an incident at an existing job 54a, 28a, 28b, 28c, 28d or to create an incident from scratch. Entry of notes, information, photos, documents, locations, time periods and other information are permitted for attachment to the created incident report. The collected information and data is preferably entered into and stored in the incident database 60 in the central server 12.

[0095] Referring to Fig. 11 , the preferred system includes a hazard/safety news GUI that permits creation of hazards, off-limits areas, planning for off-limits areas, news/safety bulletin board and related functions. The hazard/safety GUI preferably permits completion of appropriate

documentation, attachment of photos and selection of locations on the map 14 for creation of a hazard or safety area that may be stored in a current hazard/safety map database 98 in the central server 12. The hazard/safety GUI also preferably permits creation of off-limits areas/systems and planning for these areas by filling out forms and selecting areas on the map 14. These off-limits areas/systems and related information are preferably stored in the off-limits database 68 in the central server 12. The hazard/safety GUI also preferably provides news/safety bulletin boards that may include information related to first-aid, eye-wash stations, medical assistance, evacuation meeting places and related hazard and safety information and provide capabilities to present these features of the worksite on the map 14. The central server 12 may provide a safety/hazard layer that may be presented on the map 14 when desired by the contractor 24, the employee 26, the controller 48 or nearly any user. The hazard/safety information is preferably stored in a safety services map database 100 in the central server 12. The information in the safety services map database 10 may be utilized to transmit messages to contractors 24 upon approval of a pending job 54a notifying the contractor 24 of proximity to the safety and/or hazard items of their approved job 28a, 28b, 28c, 28d. [0096] Referring to Fig. 12, the preferred system 10 also includes a completed jobs GUI that permits searching and receipt of approved jobs 28a, 28b, 28c, 28d that have been completed. The completed jobs may be shown on the map 14 using specific logos and/or symbols and completed jobs may also be searched for planning, documentation and/or incident reports. Completed jobs information may be grouped into a layer for overlay onto the map 14 and may be printed by appropriate users. The completed jobs information is preferably stored in the completed jobs database 62 on the central server 12.

[0097] Referring to Fig. 13, customer and/or controller 48 may construct the preferred system 10 to have nearly any rules, flow and/or protocol for a pending jobs approval process. The approval process preferably includes sending pending jobs 54a to proper authorities, such as the controller 48 and/or employees 28, for approval or denial of the pending jobs 54a. The customer representatives can preferably receive notices of the pending jobs 54a via email, text, voicemail or nearly any form of communication/notification or may not receive any communication, thereby resulting in the proper authority having to actively check for pending jobs 54a. Approvals can be given through link in emails or proper authorities can log-in to the system 10 to review and approve or deny pending jobs 54a. The preferred system 10 can also be utilized for stand-alone lock-out/tag-out requests and these requests could follow the same or a similar process. Pending jobs 54a may be pending for approval from any users in the system, including contractors 24, employees 26, the controller 48, authorized personnel or others and may require multiple approvals prior to converting to an approved job 28a, 28b, 28c, 28d. Pending jobs 54a may be accessed by different personnel depending upon the user's access level and responsibility. The system 10 may actively prompt various users to urge them to act on approvals for specific pending jobs 54a after a predetermined amount of time has passed without activity. The information of the pending job 54a is preferably compared to information in existing databases, such as the hazards database 66, the pending jobs database 54, the approved jobs database 28, the off-limits database 68 and other database to identify overlaps. Whether overlaps are identified or not, the system 10 preferably produces a

recommendation to approve or deny the pending job 54a and the authorized personnel are preferably provided with the recommendation prior to making a decision regarding whether to approve or deny the pending job 54a. Alternatively, the system 10 may automatically approve the pending job 54a if no conflicts or overlaps are identified. Once approved, the pending job 54a may be returned to the pending jobs database 54 or may be sent to a rejected or denied jobs database 46 when denies. If conflicts or overlaps in information are identified, the system 10 preferably identifies the conflicts or overlaps to the approving authority and provides the opportunity to either override the conflict or P T/US2012/058276 overlap or deny the pending job 54a based upon the automatic recommendation to deny the pending job 54a. Whether the job is approved or denies, the associated contractor 24 is preferably notified of the approval or denial.

10098] Referring to Fig. 14, the preferred system 10 includes a utility impact GUI that permits interaction with the utility impact planner 86 that permits identification of the type of utility system impacted, system identification, date, time period and additional information that may be selected via drop-down menus. The utility impact information is preferably compared to information in other databases of the preferred system to determine the impact of the utility system job. The utility system information is preferably maintained in the utility database 94 in the central server 12. The utility information, once the utility job is approved, if preferably used to notify users of the system 10 and/or the controller 48 of potential conflicts or overlaps that could impact approved jobs 28a, 28b, 28c, 28d or pending jobs 54a that may rely on the impacted utility. Notifications, preferably via email, are sent to impacted users to notify them of the utility/service interruption. Impacted personnel or users preferably have the ability to deny the service interruption or recommend denial or cancellation of the service interruption. Subsequent denial and/or cancellation of the interruption results in the requested utility interruption being converted to the denied or rejected jobs database 46 and approval of the utility interruption job results in conversion of the interruption to the approved jobs database 28.

[0099] Referring to Fig. 15, the lock-out/tag-out GUI preferably permits attachment of a lock- out/tag-out of a particular piece of equipment 16 to a pending job 54a, an approved job 28a, 28b, 28c, 28d or otherwise or creation of a stand-alone lock-out/tag-out job. Either lock-out/tag-out job preferably permits identification on the map 14, potentially using a lock-out/tag-out symbol. The lock-out/tag-out information may be stored in the approved jobs database 28 and/or the lock-out/tag- out database 64, wherein the information is searchable and may be added to a layer with other lock- out/tag-out jobs for display on the map 14.

[00100] Referring to Fig. 16, the preferred system 10 also preferably includes a base level database 102 that includes information related to all normal operating practices uploaded to the system using forms and maps. Information in the base level database 102 may include contact data and other related data that can be searched and mapped to the map 14 in the preferred system for mapping and/or job planning purposes.

[00101] Referring to Fig. 17, the preferred system 10 includes a jobsite selection GUI that permits a user to select a location of a requested jobsite, location or area on the map 14. The selection is preferably made directly on the map 14, but is not so limited and may be made using coordinates, walking a perimeter of the job area or otherwise.

[00102] Referring to Fig. 18, a GUI for various forms may be provided by the preferred system 10 with checklists, save options, email or transmit options, submit options, print options, entry options or otherwise. The form GUI's are preferred for commonly utilized forms so that consistent information can be gathered and all appropriate information is in place for conduct of the work.

[00103] Referring to Fig. 19, a customer dashboard GUI that may be a landing spot for a contractor 24, employee 26 and/or controller 48 provides information to the users related to pending jobs, projects currently working or approved jobs 28a, 28b, 28c, 28d and a visual representation of planned or ongoing jobs. The customer dashboard GUI may include a description pop-up when relevant symbols on the map 14 are touched or identified. The customer dashboard GUI preferably includes access to maps, incidents, hazards, pending jobs, approved jobs, completed jobs and related information and layers.

[00104] Referring to Fig. 20, the customer dashboard GUI may also display recommendations from the preferred system 10 to the user to approve, deny and/or modify a pending job 54a.

[00105] Referring to Fig. 21, the preferred system 10 also includes a maps page GUI that permits searching of the map 14 and various limits for searching purposes. The maps page GUI also preferably includes access to hazards, incidents, current maps and the map 14.

[00106] Referring to Fig. 22-24, hazard map, incident map and job review GUI's are shown with various searching capabilities, information requests and maps 14.

[00107] Referring to Fig. 25, a preferred system 10 warning indicating that the associated pending job 54a conflicts or overlaps in some manner with an approved job 28a, 28b, 28c, 28d and the system 10 recommends denying the pending job 54a. Options are provided to view the job conflicts, deny the pending job 54a and/or approve the pending job 54a.

[00108] In the preferred system 10, registration information for a new user may include company name, first name, middle name, last name, username, address, password, password confirm, phone, email, confirm email, notify request preference (email, text or otherwise), type of registration (manufacturing, utility, mining, transportation, municipality, contracting company) and other related registration information that may be relatively standard or variable depending upon answers to initial inquiries or the type of registration requested. The preferred system 10 preferably supports forms that may be required for conducting various tasks at a typical worksite, such as an

environmental impact review, a confined space permit request, a confined space entry permit, an energized electrical work permit, a hot work permit request form, an excavation/concrete cutting permit request, a track closure/blue-flag permit request, a useful information form, a safety, health and environment handbook, a request to borrow equipment form, a job permit and other related forms and reference information that may be useful for the preferred system 10.

[00109] Referring to Fig. 26, the preferred system 10 of the present invention includes multiple users, including contractors 24, employees 26 and controllers 48, with various levels of access and authority to manipulate the system 10. Each individual user may have a different level of access and authority or the system 10 may include several or only a single level of access and authority, depending upon how the customer or controller 48 configures the system 10. The pending job information preferably includes location, worksite, storage, meeting area, spatial information, chronological information, critical path planning information, miscellaneous event specific data and other related information. The preferred system 10 is able to locate and present jobs on the map 14 utilizing a spatial management application that includes database, interfacing language code, user interface and related components.

[00110] In order to limit conflicts and/or overlap in the jobs 54a, 28a, 28b, 28c, 28d, a comparison is made during the approval process utilizing the central server 12. The jobs 54a, 28a, 28b, 28c, 28d are preferably not only compared to each other, but also to other events or jobs occurring at the worksite, such as hazards, utility shutdowns, repairs and related events that may result in stoppages in jobs 54a, 28a, 28b, 28c, 28d, thereby damaging efficiency and interrupting schedules. Such comparisons, which are made simple and efficient with the preferred system 10, can be used to plan the worksite by permitting users to see existing data and plan accordingly to open time and space, approve requests by submitting requests to a specific time and/or location for approval, mitigate ongoing conflicts and manipulate or edit potential conflicts or overlaps based on data observed in the preferred system 10 and other advantages.

[00111] Utilizing the preferred system 10, conflicts and overlaps can be used to set off workflows or jobs within the system 10 using special management solution to notify parties responsible for planning the event and/or location. Those responsible may alternatively edit or manipulate a requested job in time, location or otherwise to prevent conflicts and overlaps with existing approved jobs 28a, 28b, 28c, 28d. The approval process submits event data to proper personnel or to the system 10 itself to approve, deny and/or edit or manipulate the date to reduce or eliminate conflicts or overlaps or to generally permit the jobs to flow in an efficient manner. Any denial of the proposed job 54a preferably results in the requestor being notified and resubmittal is permitted. Authorized personnel, such as the controller 48 may also permit overlaps or conflicts to exist in the preferred system 10 for editing and/or cancellation at a later date during continuing planning and T U 2012/058276 management of the worksite or some overlap may be permitted if overlaps can coexist in certain locations.

[00112] The various databases and information collected utilizing the preferred system 10 permits production of reports, charts, chronological maps 14 and related results on the display 22 for users or in other varieties of documents, permits, plans or related items to show historical, current or future event location, data, conflicts, overlaps and other such information. As conditions at the worksite change, the historical collected data can be used within the preferred system's 10 spatial management solution to continually mitigate conflicts or overlaps and assist with event altering decisions based on critical path planning information.

[00113] Referring to Fig. 27, various symbols can be used to present specific events and/or locations on the map 14 in a relatively quick visual manner. Preferred symbols for the system 10 include a contractor job symbol 1 10, a union contractor job symbol 1 11 , a lock-out/tag-out symbol 1 12, a blue flag symbol 1 13, a red flag symbol 1 14, a hazard symbol 1 15, an incident symbol 116, a restroom symbol 1 17, a shower symbol 118, a confined space entry symbol 1 19, a broken machinery symbol 120, a safety meeting symbol 121 and an evacuation meeting place symbol 122. The listed symbols are not meant to be limiting and nearly any symbol may be utilized with the preferred system 10 to depict various jobs, items, elements or events on the map 14.

[0011 ] Referring to Figs. 28-31 , a second preferred embodiment of the map 14' of an alternative worksite for presentation and/or manipulation on the displays 22 includes several facilities 18' and roads 20'. The alternative map 14' will be described using the same reference numerals utilized with the first preferred map 14 and with the prime symbol (') do distinguish the elements of the second preferred embodiment of the map 14'. The second preferred map 14' is preferably stored in the central server 12 in the worksite map database 70 and may be utilized in parallel with the first preferred map 14 for planning, safety and special management of the first and second worksites. The second preferred map 14' is shown in Fig. 28 generally without jobs 28a, 28b, 28c, 28d, 54a or other elements added or as a basic layout example. The preferred maps 14, 14' could be nearly any variety of map 14, 14', construction drawing, aerial photograph or other depiction that is able to represent a worksite for presenting relevant worksite data and to spatially plan events and items at the worksite.

[00115] Utilizing the second preferred map 14', the user, such as the contractor 24, inputs information for the first pending job 54a, which is approved and results in the first approved job 28a'. The first approved job 28a' is represented on the second preferred map 14' by a four-sided shape bounded by first, second, third and fourth lines 33a', 33b', 33c', 33d' and includes the contractor job symbol 10 therein, visually indicating that the first approved job 28a' is a contractor job. The first preferred job 28a' is not limited to the shape represented on the second preferred map 14' and may have nearly any shape that is able to bound the first area 32' of the first approved job 28a', for example, a polygon, a point, a radius, an irregular area, an octagon or nearly any shape that is able to bound an area and/or a volume. The pop-up box at a right-hand side of the display 22 shown in Fig. 29 preferably shows additional data and approved job information related to the first job 28a', including details and chronological information about the job for future reference/planning purposes such as critical path planning. The pop-up box will appear when scrolling over the first area 32' and the contractor job symbol 1 10 is able to provide visual information about the first preferred job 28a' without scrolling over the first area 32'.

[00116] As is shown in Fig. 30, additional features and/or elements may be added to the second preferred map 14' for special planning and information purposes. For example, the log-out/tag-out symbol 1 12 is associated with the first approved job 28a', the hazard symbol 1 15 is associated with Garage #1 , two blue flag symbols 1 13 are positioned proximate Building #1, the confined space symbol 1 19 is positioned in Building #2 18' and the restroom symbol 1 17 is positioned in Office #1 18'. The user has also scrolled over the contractor job symbol 1 10 of the first approved job 28a', thereby prompting the description symbol/pop-up 91 ' associated therewith to activate and present additional information related to the first approved job 28a'. The right-hand side pop-up is also presented indicating the user is adding a safety meeting symbol 121 , which is requesting various information from the user to entry. The users can interact with the job or event markers or symbols to learn additional information about the job, event or location, to contact event or job planners or participants, plan other related or unrelated events or jobs in the same or a similar area or location and at a similar or same time, use historical information for reporting and meetings to discuss the event or job, to consider the proximity of the event or job to other events, jobs and/or site features.

[00117] Referring to Fig. 31, a user added the first pending job 54a' to the map 14 Of the second preferred embodiment and the central server 12 automatically compared the first pending job 54a' to the first approved job 28a', which already existed on the map 14' of the second preferred

embodiment. The central server 12 identified a conflict or overlap in the locations of the first pending and approved jobs 54a', 28a' and transmitted a recommendation or warning pop-up 130 to the appropriate display 22 alerting the user of the conflict or overlap. The recommendation pop-up 130 provides options for the user including "ignore," "cancel" and "edit," which permit the user to react to the conflict or overlap as desired. The recommendation pop-up 130 may automatically appear on the appropriate display 22 once the central server 12 identifies the overlap or conflict, may not appear for the user, but only for authorized personnel, such as the controller 48, who are in charge of approvals or may otherwise, may take a form other than a pop-up on the display 22, may immediately deny the pending job 54a' as a result of the conflict or overlap or may otherwise react to conflicts or overlaps depending upon predetermined rules set up by the controller 48 or other authorized personnel. The preferred system 10 can be used to solely submit information to the proper personnel for approval or denial, without including rules for reaction by the central server 12, but the rules and reactions by the central server 12 are preferred to improve efficiency of the worksite. The system 12 preferably provides a recommendation and/or warning to the approving personnel of conflicts, overlaps or lack of conflict or overlap and permits the authorizing personnel to approve, edit, deny, request new information, request a new pending job 54a', ignore the conflict or overlap or otherwise consider the pending job 54a'. The system 12 can monitor, update, notify users of conflicts and/or overlaps as jobs, circumstances and time unfolds , allowing users to continually monitor and update throughout the lifecycle of the worksite. The preferred system 12 may also transmit warnings or updates to contractors 24 and/or employees 26 who are in charge of approved jobs 28a', 28b, 28c, 28d if a pending job 54a' having a high priority is received that conflicts with their approved jobs 28a', 28b, 28c, 28d, if a hazard, utility interruption, off-limits event, lock-out/tag-out or other events could potentially disrupt their approved job 28a', 28b, 28c, 28d. Further, the preferred system 12 may be designed and configured to transmit information to contractors 24 and/or employees 26 in charge of approved job 28a', 28b, 28c, 28d related to features and items proximate to their approved job 28a', 28b, 28c, 28d, such as showers, restrooms, evacuation meeting places, broken machinery and numerous additional features and or items related to the worksite.

[00118] The drawings provide additional details related to the preferred system 10 and method not explicitly described in the above text and operation of the preferred system 10 and method will be apparent to one having ordinary skill in the art following a review of the present application, including the appended drawings. It will be appreciated by those skilled in the art that changes could be made to the embodiments described above without departing from the broad inventive concept thereof. For example, the modules, databases and features of the preferred system 10 are generally interchangeable and may be utilized in nearly any combination, as would be apparent to one having ordinary skill in the art. It is understood, therefore, that this invention is not limited to the particular embodiments, configurations, arrangements and method steps disclosed, but it is intended to cover modifications within the spirit and scope of the present invention as defined by the appended claims.

Claims

CLAIMS I claim:

1. A worksite safety, planning and environmental documentation and mapping system for documenting and mapping projects being conducted at a worksite, the system comprising:

a central server configured to store a map of the worksite, the map including representations of equipment and facilities at the worksite;

a display in communication with the central server, the display configured to visually present the map;

an approved jobs database stored at the central server, the approved jobs database maintains approved jobs information including a first approved job, the approved jobs information related to a plurality of approved jobs at the worksite and includes first approved job information related to the first approved job, the first approved job information including a first job location associated with a first area on the map, the first job information also including a first time period and a first job identification;

a denied jobs database stored at the central server, the denied jobs database maintains first denied job information related to a first denied job at the worksite, the first denied job information including a first reason for denial of the first denied job and a first denied job location; and

a pending jobs database stored at the central server, the pending jobs database maintains pending jobs information including a first pending job information, the first pending job information including a first pending location, a first pending time period and a first pending identification, the central server configured to compare the first pending job information to the approved jobs information to create a first recommendation regarding whether to approve the first pending job.

2. The worksite safety, planning and environmental documentation and mapping system of claim 1 wherein the first area is defined by a triangle, the first area presented on the map on the display.

3. The worksite safety, planning and environmental documentation and mapping system of claim 1 , wherein the first area is defined by at least a first point, a second point, a third point, a first line extending between the first and second points, a second line extending between the second and third points and a third line extending between the third and first points.

4. The worksite safety, planning and environmental documentation and mapping system of claim 1 , further comprising:

an approved contractor database stored at the central server, the approved contractor database having a plurality of approved contractors for the worksite.

5. The worksite safety, planning and environmental documentation and mapping system of claim 1 , wherein the approved jobs information includes a second approved job having a second time period and a second job location associated with a second area on the map, the first time period overlapping with the second time period and the first and second areas spaced from each other.

6. The worksite safety, planning and environmental documentation and mapping system of claim 1, wherein the first denied job information also includes a first denied time period, the first time period and the first time period overlapping and the first denied job location overlapping with the first job location.

7. The worksite safety, planning and environmental documentation and mapping system of claim 1, wherein the first area is defined by a user selecting a first point, a second point and a third point on the map on the display, the central server automatically drawing a first line between the first point and the second point, a second line between the second point and the third point and a third line between the third point and the first point, thereby defining the first area.

8. The worksite safety, planning and environmental documentation and mapping system of claim 1 , further comprising:

an incident database stored at the central server, the incident database maintains incident information for a plurality of incidents, the incident information including incident date, incident location and incident description.

9. The worksite safety, planning and environmental documentation and mapping system of claim 1, further comprising:

a completed jobs database stored at the central server, the completed jobs database maintains completed jobs information, the completed jobs information including a completion date, a completed job contractor name, a completed job location and a completed job description for a plurality of completed jobs.

10. A method for utilizing a worksite safety, planning and environmental documentation and mapping system for documenting and mapping projects being conducted at a worksite, the system including a central server having a pending jobs database, an approved jobs database, a denied jobs database, an approved contractor database and a completed jobs database and being in

communication with a contractor display configured to present a map of the worksite and a controller display, the method comprising:

(a) receiving, at the central server, a contractor name and a contractor password;

(b) comparing the contractor name and the contractor password to a plurality of stored contractor names and stored contractor passwords in the approved contractor database, the central server activating the system if the contractor name matches one of the plurality of stored contractor names and the contractor password matches a corresponding one of the plurality of stored contractor passwords, respectively;

(c) receiving, at the central server, first pending job information associated with a first pending job including a first pending location, a first pending time period and a first pending identification, the first pending job information being stored in the pending jobs database;

(d) comparing, with the central server, the first pending time period to a plurality of approved time periods associated with a plurality of approved jobs;

(e) comparing, with the central server, the first pending location to a plurality of approved locations associated with the plurality of approved jobs;

(f) transmitting, via the central server, one of an approval recommendation if both the first pending time period and the first pending location do not both overlap with the plurality of approved time periods and an associated one of the plurality of approved locations and a denial

recommendation to the controller if both the first pending time period and the first pending location overlap with the plurality of approved time periods and an associated one of the plurality of approved locations, the one of the approval and the denial recommendation being transmitted to the controller display; and

(g) receiving, at the central server, one of an approval and a denial of the first pending job.

1 1. The method of claim 10, wherein the contractor display is a touchscreen display, the first pending location defined by receiving an area input via the contractor display, the area including at least a first point, a second point, a third point, a first line, a second line and a third line.

12. The method of claim 10, wherein the central server is in communication with a machine at the worksite and further comprising: (h) sending a signal, via the central server, to the machine to disable the machine for a predetermined lockout time period.

13. The method of claim 10, further comprising:

(h) converting, via the central server, the first pending job to a first approved job when receiving the approval in step (g) by moving the first pending job from the pending jobs database to the approved jobs database.

14. The method of claim 10, further comprising:

(h) converting, via the central server, the first pending job to a first denied job when receiving the denial in step (g) by moving the first pending job from the pending jobs database to the denied jobs database.

15. The method of claim 10, further comprising:

(h) receiving, at the central server, a first incident report, the first incident report including a first incident location and a first incident description; and

(i) storing, at the central server, the first incident report in an incident database.

1 6. The method of claim 15, wherein the incident database includes a plurality of incident reports including the first incident report and further comprising:

(j) transmitting, via the central server, a signal to the controller display to present the plurality of incident reports.

17. The method of claim 10, further comprising:

(h) receiving, at the central server, a first completed job, the first completed job including a first completion date and being associated with one of the plurality of approved jobs.

18. The method of claim 10, wherein the central server also stores a hazards database and an off-limits database and further comprising:

(h) comparing, via the central server, the first pending job information to the hazards database and the off-limits database prior to step (f).

19. The method of claim 10, wherein the worksite is selected from the group consisting of a company facility, a series of roads, a series of rail lines, a manufacturing facility, a company building, an assembly line and an airport.

20. The method of claim 10, wherein the plurality of approved jobs are each associated with one of a plurality of approved time periods and further comprising:

(h) transmitting, via the central server, a signal to the contractor display to present all of the plurality of approved jobs wherein a current time period overlaps with one of the plurality of approved time periods utilizing at least a symbol on the map.