US2011314066A1PendingUtilityA1

System and method of managing safety information

Assignee: RICHARDSON DALEPriority: Sep 7, 2007Filed: Aug 31, 2011Published: Dec 22, 2011
Est. expirySep 7, 2027(~1.1 yrs left)· nominal 20-yr term from priority
G06Q 10/06
50
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

A safety management system for use in industry, such as the oil and gas industry, is disclosed. The system comprises a database component for storing safety information including project information comprising at least one project entry. Each project entry has a unique project identifier and project data. The database component further includes safety card information comprising at least one safety card entry, and a unique safety card identifier, a project identifier selected from the unique project identifiers of the at least one project entries and safety card data. The database component further comprising notification information comprising at least one notification entry. Each notification entry comprising a unique notification identifier, a project identifier selected from the unique project identifier of the at least one project entries and notification card data. The safety management system further comprises a control component for generating notifications and providing notification information to the database component.

Claims

exact text as granted — not AI-modified
1 . A safety management system for use in industry comprising:
 a database component for storing safety information including:
 project information comprising at least one project entry, each project entry comprising:
 a unique project identifier; and project data; 
 
 safety card information comprising at least one safety card entry, each safety card entry comprising:
 a unique safety card identifier; 
 a project identifier selected from the unique project identifiers of the at least one project entry; and 
 safety card data; and 
 
 notification information comprising at least one notification entry, each notification entry comprising:
 a unique notification identifier; 
 a project identifier selected from the unique project identifier of the at least one project entry; and 
 notification card data; and 
 
 a control component for generating notifications and providing notification information to the database component. 
   
     
     
         2 . The system as claimed in  claim 1 , further comprising a user interface component for receiving project information and safety card information, and for sending the notifications. 
     
     
         3 . The system as claimed in  claim 1  wherein the control component comprises:
 a notification component for calculating a project safety performance index (SPI) based on at least the safety card data of at least one of the safety card entries with the project identifier corresponding to the project identifier of the received safety card information. 
 
     
     
         4 . The system as claimed in  claim 3 , wherein the control component generates notifications if the calculated project SPI is above an SPI threshold. 
     
     
         5 . The system as claimed in  claim 2 , wherein the safety information further comprises:
 user information comprising at least one user entry comprising:
 a unique user identifier; 
 a username; and 
 a password. 
   
     
     
         6 . The system as claimed in  claim 5 , wherein the control component further comprises a security component for determining an access privilege for a user based on a received username and password. 
     
     
         7 . The system as claimed in  claim 6 , wherein each of the at least one user entries further comprises the access privilege, and wherein the security component determines the access privilege for the user by comparing the received username and password with the username and password of user entries. 
     
     
         8 . The system as claimed in  claim 6 , wherein the user interface component comprises a web server for serving a web page to the user based on at least the determined access privilege. 
     
     
         9 . The system as claimed in  claim 1 , wherein the generated notification is at least one of an email message, a short message service (SMS) text message or a phone message. 
     
     
         10 . The system as claimed in  claim 1 , wherein the safety card information further comprises action information comprising at least one action entry, the action entry comprising:
 a unique action identifier;   a project identifier selected from the unique project identifier of the at least one project entries; and   action data.   
     
     
         11 . The system as claimed in  claim 1 , wherein the control component generates the notification based on the number of safety cards received. 
     
     
         12 . The system as claimed in  claim 1 , wherein:
 the project information is stored in a project table with each project entry stored as a record of the project table;   the safety card information is stored in a safety card table with each safety card entry stored as a record of the safety card table; and   the notification information is stored in a notification table with each notification entry stored as a record of the notification table.   
     
     
         13 . The system as claimed in  claim 1 , wherein the project information, safety card information and notification information is stored in a single table. 
     
     
         14 . A method of managing the safety of projects comprising:
 receiving project data;   storing in a database project information comprising the received project data and an associated unique project identifier;   receiving safety card data;   storing in the database safety card information comprising the received safety card data, an associated unique safety card identifier and a project identifier of the at least one unique project identifier associated with each project data; and   generating a notification and associated notification information if a project safety performance index (SPI) is above an SPI threshold.   
     
     
         15 . The method as claimed in  claim 14 , further comprising:
 storing in the database the notification information comprising notification data, an associated unique notification identifier and a project identifier of the at least one unique project identifiers associated with each project data; and   sending the generated notification.   
     
     
         16 . The method as claimed in  claim 15  wherein the stored safety card information further comprises an SPI rating associated with the safety card data. 
     
     
         17 . The method as claimed in  claim 16 , further comprising calculating a project SPI based on at least the SPI rating associated with at least one safety card data with the unique project identifier corresponding to the project identifier of the received safety card data. 
     
     
         18 . The method as claimed in  claim 15 , wherein sending the generated notification comprises at least one of:
 sending the notification in an email message;   sending the notification in a short message service (SMS) text message; or   sending the notification in a phone message.   
     
     
         19 . A computer-readable medium storing instructions or statements for use in the execution in a computer of a method of managing the safety of projects, the method comprising:
 receiving project data;   storing in a database project information comprising the received project data and an associated unique project identifier;   receiving safety card data;   storing in the database safety card information comprising the received safety card data, an associated unique safety card identifier and a project identifier of the at least one unique project identifier associated with each project data; and   generating a notification and associated notification information if a project safety performance index (SPI) is above an SPI threshold.

Join the waitlist — get patent alerts

Track US2011314066A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.