Hazardous materials and waste reduction management system

Abstract

A user controlled chemical management system for small-, medium- and large-sized organizations for use with a computer. The chemical inventory management system includes a chemical inventory control system allowing a user to manage chemicals from a central station, the plurality of combined receiving and outpost stations, to allow for the tracking of individual chemical containers throughout its life. In addition, an environmental, health and safety information system as contained in the chemical management system to allow the user create customized chemical storage groups that are color coded for a particular area. Also included is a safety equipment management system to allow accurate records to be kept of all safety equipment. Finally, an international chemical compatibility system is included with a compliance/education design to create compliance/education files for any country in the world.

Claims

What is claimed is:

1. A user controlled hazardous material management system for relatively small, medium and large size organizations comprising:

a computer;

data storage device coupled to said computer;

a display coupled to said computer that provides display screens;

a user input device coupled to said computer; and

hazardous material inventory control data stored in said data storage device enabling user selection of a selected one or a combination of (1) a central control station for a given organization that monitors the in-flow of enclosed hazardous materials to the station by means of unique identification of each hazardous material enclosure, the storage and use of said hazardous materials within the station, and the out-flow of said hazardous material from said central control station as waste; (2) a plurality of individual hazardous material control stations for said given organization, each control station monitoring its in-flow of enclosed hazardous materials by said means of unique identification of each hazardous material enclosure, the storage and use of its hazardous materials and the out-flow of its waste hazardous materials; and (3) a system for said given organization that enables tracking each individual hazardous material enclosure throughout its life by said means of unique identification and a transaction log for each enclosure of said hazardous material, said system including a multi-tier classification of hazardous materials based upon origin and composition.

2. A user-controlled hazardous material management as in claim 1 further including environmental, health, and safety information data stored in said computer representing user-created unique, customized hazardous material capability storage groups, said groups designating storage areas within said organization for hazardous materials and areas within said organization prohibited from being used for storage of said hazardous materials.

3. A system as in claim 2 further including safety equipment management data stored in said computer for generating a maintenance and inspection record of all safety equipment within said organization, including fume/exhaust systems and eye wash and safety showers defined according to government standards and including generic safety equipment that does not fall under the defined safety equipment.

4. A system as in claim 3 further including international hazardous material compatibility data stored in said computer and including multi-tier compliance/education design data for creating compliance/education files within said organization for any country in the world with means for enabling text conversions to the foreign language of a selected country.

5. A system as in claim 4 wherein said international hazardous material compatibility system comprises:

a user created compliance/education file in the language of any selected country in the world;

stored numerical data representing required compliance/education information concerning the hazardous materials in the system; and

said user created compliance/education file including a display in either the foreign language of a selected country or in one or more foreign languages to enable international review of said stored numerical data representing said compliance/education information across predetermined countries of interest.

6. A system as in claim 5 further including a text translator for receiving all text in said system, converting the text to a selected foreign language and storing the converted text.

7. A system as in claim 2 further including:

an unique password for each user having login access to the system;

a preset time after which said password expires; and

user-controlled password disabling means for disabling the password after a predetermined number of invalid login attempts.

8. A system as in claim 7 further including:

a user tracelog record of access to said containers of hazardous material, the record including the personal preference of the user of measurement data, such as gallons versus liters and kilograms versus ounces to be viewed on the user's display; and

said user tracelog record maintaining the use, storage and disposal of said hazardous materials as controlled by the user.

9. A system as in claim 2 wherein said environmental, health, and safety information system storage groups further comprise an unalterable storage group for hazardous material containers that require special storage/handling precautions that are unique to a particular hazardous material because of compatibility with other hazardous materials or environmental/safety/health requirements.

10. A system as in claim 9 wherein any hazardous material designated in said unalterable storage group is provided a record, unique to that hazardous material, of special storage requirements that can be displayed.

11. A system as in claim 9 wherein said group arrangements include:

designated storage and nonstorage areas, including a particular building, a particular floor in a building, a particular room on said particular floor and as general or specific locations in said particular room; and

designated storage/use options for the selected locations, including hazardous material storage only, hazardous material use only, or hazardous material use/storage where both storage and use of the hazardous material may occur.

12. A system as in claim 11 further including:

stored data representing an elevation view of said particular building indicating the floor or floors in which the hazardous materials are located, a plan view of particular floor in said building, and a plan view of the particular room in which the hazardous materials are located illustrating the location of the hazardous materials in said room; and

said user input device enabling display of the desired one of said elevation views and said plan views for use by appropriate personnel in the case of an emergency that might affect said hazardous materials.

13. A system as in claim 3 wherein said safety equipment management system includes:

an inventory of all user-selected system safety equipment items;

stored test data of equipment check procedures that ensure proper safety equipment operation;

stored data representing printed survey forms for inspection of said safety equipment, said survey forms listing equipment elements that require inspection; and

printed compliance labels containing compliance data for each item of safety equipment inspected.

14. A system as in claim 13 wherein said compliance data and said printed compliance labels represents a comparison of sampled data from an item of safety equipment compared to a set of standard criteria for performance of the item.

15. A system as in claim 2 wherein the environmental health safety system further comprises:

first stored data representing icons, training materials, and warnings regarding any particular hazardous material;

second stored data in said memory designating each system user, each user being designated as professional, experienced or a novice in handling hazardous materials; and

an inquiry screen containing icon prompts for selected use by a professional user of hazardous materials, icon prompts and warning materials concerning a selected hazardous material for an experienced user of hazardous materials, and icon prompts and a display of training materials required for a novice to review in the use of hazardous materials, said training materials requiring review of the selected training materials and warnings and requiring specific responses from the novice user before said novice can use said hazardous material in a process.

16. A user controlled hazardous material management system as in claim 1 further comprising hazardous material container classification data stored in said data storage device and including:

first data representing containers storing hazardous materials that are in-use;

second data representing containers storing waste hazardous materials; and

said first and second data representing said containers of the waste group of hazardous materials including four classes of information concerning the hazardous materials in said containers, including pure hazardous material, the trade name of the hazardous material, a preset mixture of hazardous materials, and a variable mixture of hazardous materials so as to enable said system to track said hazardous material in any one of said four classes of information from its beginning as an in-use hazardous material through its disposition as a waste hazardous material.

17. A system as in claim 16 further including:

third data representing containers storing surplus hazardous materials; and

said third data representing said surplus of hazardous materials, including said four classes of information concerning pure hazardous material, the trade name of the hazardous material, preset mixes of the hazardous material, and variable mixes of the hazardous materials so as to allow management of the hazardous materials from the in-flow to the out-flow.

18. A system as in claim 17 wherein:

said term "pure" hazardous material denotes the hazardous material with a recognized scientific name and hazardous material that originates from an outside vendor;

said term "trade name" denotes the designated commercially known name of the hazardous material that originates from an outside vendor;

said term "preset mix" denotes hazardous material originating from a mixture of in-house hazardous materials; and

said term "variable mix" represents a mixture of hazardous materials not normally maintained in stock such that every container of hazardous material is tracked from in-flow to out-flow.

19. A system as in claim 18 further comprising:

a first stored record giving a first unique identification to a first container of a first hazardous material;

a second stored record giving a second unique identification to a second container of hazardous material taken from said first container;

an n.sup.th stored record giving an n.sup.th unique identification to an n.sup.th container of hazardous material taken from the n-1 container; and

a special stored record giving an additional unique identification to a container having a mixture of said first hazardous material from one of said n containers and a second different hazardous material from another container so as to maintain a genealogy of the hazardous material stored in any container such that the unique origin and history of each hazardous material in a given container is known, each of said stored records being identified by a unique code.

20. A system as in claim 17 wherein said data representing surplus hazardous materials is available for display to every user of the system to reduce unnecessary purchasing of hazardous materials already in surplus.

21. A system as in claim 17 further including:

icons appearing on any selected display screen representing in-use, surplus, or waste hazardous materials; and

each of said icons giving a visual representation of a warning relating to each particular hazardous material.

22. A system as in claim 21 further including:

training material data stored in said computer pertaining to at least one of said hazardous materials; and

a particular icon on said display screen that enables the user to select said training materials relating to said hazardous materials for display.

23. A system as in claim 1 further including:

at least one enclosure having multiple individual containers of hazardous material;

a stored data record identifying each hazardous material enclosure that has multiple individual containers of hazardous material inside thereof; and

an inventory data record of an individual container of hazardous material created by entering into said computer said identifying data when any one of said containers is removed from said enclosure.

24. A system as in claim 1 further including:

data representing containers storing surplus hazardous materials; and

said data representing said surplus hazardous materials including pure hazardous material, the trade name of the hazardous material, preset mixes of the hazardous material, and variable mixes of the hazardous materials so as to allow for cradle to the grave management of the hazardous materials.

25. A system as in claim 1 wherein said monitoring of said use of said hazardous materials further includes:

a stored designation for each particular container of hazardous material at least some of which is to be taken out of said container for use in a process; and

a display screen for monitoring said hazardous material taken from said designated particular container and used in said process, said display screen having a first area for entering consumption data including data representing a percentage of said hazardous material consumed in said process, a second area for entering data representing a percentage of said hazardous material transferred to the atmosphere during the process, a third area for entering data representing a percentage of the hazardous material that is disposed on-site essentially as a liquid during the process, and a fourth area for entering data representing a percentage of the hazardous material that is retained as residual waste from the process so that a complete cradle to the grave tracking of each container of hazardous material is possible.

26. A system as in claim 25 wherein said screen includes a fifth area for entering data representing a particular container in which said residual waste is disposed.

27. A system as in claim 25 further including a preprocessing display screen for use with repetitive processes, said preprocessing screen enabling automatic recording of said consumption percentage data by said computer for hazardous materials used in said repetitive process.

28. A system as in claim 25 further including:

multiple containers of different hazardous materials to be used in a process; and

a display screen that allows a user of the process to enter by-products of said process on said screen and link an appropriate portion of each of said by-products to each of said hazardous materials used in the process.

29. A system as in claim 28 further including a preprocessing display screen for use with repetitive processes using multiple containers, said preprocessing display screen enabling automatic recording of consumption percentage data by said computer for hazardous materials used in said repetitive process.

30. A system as in claim 1 wherein the hazardous material management system further includes:

said data storage device storing data representing in-flow and out-flow of said hazardous materials;

a plurality of host platforms, each at a plurality of different locations within said organization; and

a program format in said computer enabling any one of the host platforms at any one of the plurality of different locations within said organization to connect to said storage device and to display data monitoring said in-flow and out-flow of said hazardous materials.

31. A system as in claim 1 further comprising:

a plurality of groups of identical hazardous materials, each group of hazardous materials having different manufacturers and/or international designations;

a synonym representing each of said groups of identified hazardous materials; and

means for displaying all of a group of hazardous materials and inventory without reference to said particular designation by selecting said synonym for said selected group.

32. A user-controlled hazardous material management system for relatively small, medium and a large size organizations comprising:

a computer;

a data storage device coupled to the computer;

a display device coupled to the computer;

a user input device coupled to said computer; and

a hazardous material container classification system stored in said data storage device for access by said user through said input device and including:

first data representing containers storing hazardous materials that are in-use;

second data representing containers storing hazardous materials that are classified as waste hazardous materials; and

said first and second data representing said containers of in-use hazardous materials and waste hazardous materials being designated as pure hazardous materials, as the trade names of the hazardous material, as a preset mixture of hazardous materials, or as a variable mix of hazardous materials so as to enable such system to track each container of hazardous material in any one of said designations from its beginning as an in-use hazardous material through its disposal as a waste hazardous material.

33. A system as in claim 32 wherein:

said term "pure" hazardous material denotes a hazardous material with a recognized scientific name that originates from an outside vendor;

said term "trade name" denotes the designated commercially known name of the hazardous material that originates from an outside vendor;

said term "preset mix" denotes hazardous material originating from a mixture of in-house hazardous materials; and

said term "variable mix" represents a container with a mixture of hazardous materials not normally maintained in stock such that every container of hazardous material is tracked from the in-flow to the out-flow.

34. A system as in claim 33 further comprising:

a first stored record giving a first unique identification to a first container of a first hazardous material;

a second stored record giving a second unique identification to a second container of hazardous material taken from said first container;

an n.sup.th stored record giving an n.sup.th unique identification to an n.sup.th container of hazardous material taken from the n-1 container; and

a special stored record giving an additional unique identification to a container having a mixture of said first hazardous material from one of said n containers and a second different hazardous material from another container so as to maintain a genealogy of the hazardous material stored in any container such that the unique origin and history of each hazardous material in a given container is known, each of said stored records being identified by a unique code.

35. A system as in claim 34 further including:

a display screen having an icon representing any particular container;

a scale displayed along side said icon representing a predetermined original level of hazardous material in said container; and

pointing means movable by the user to said scale for causing said icon to visually represent the level of hazardous material actually in said particular container as determined visually by said user to approximate the amount of hazardous material in said container at any given time when compared to the predetermined original amount of hazardous material in the container.

36. A system as in claim 34 further comprising:

a printer coupled to said computer; and

said computer automatically printing labels with all government requirements for said hazardous material in all individual containers created in said genealogy.

37. A system as in claim 36 wherein, if said label for any container is damaged, a replacement label is generated by said computer when said name of said hazardous material or the container unique code is entered into said computer.

38. A management system as in claim 32 further comprising a three-tier hierarchy user function access that supports a different restriction of user function access in each function tier.

39. A management system as in claim 38 wherein the three-tier hierarchy function access comprises:

a division with predetermined users designated as the top level of access;

a department that is a part of a division and having users designated as the mid-level of access;

a user who is in a division or department and who is designated as the bottom level of access; and

said administrator function allowing an administrator to restrict access at each level to predetermined users.

Description

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to materials management systems and more particularly to systems for the management of hazardous and toxic materials especially chemicals.

2. Description of Related Art

The regulation and control of chemicals, hazardous materials, and hazardous wastes by the government is becoming more and more restrictive to the point where institutions such as chemical labs, doctors' offices, and businesses, corporations with a need to handle chemicals, hazardous materials, and hazardous wastes cannot easily stay up to date on the current laws. As used herein the term "chemical" or "chemicals" is defined as hazardous materials, hazardous wastes, or in select cases nonhazardous materials that are but a portion of an inventory containing hazardous materials or wastes. From this point forward and in all documentation pertaining to this invention, the terms "chemical(s), hazardous material(s), hazardous waste(s)" are used interchangeably.

A typical example of problems encountered in the management of hazardous material can be seen from the perspective of an educational institution such as a college or university. Historically there has not been sufficient budgetary and management priority given to developing waste management programs at those type of institutions. Most problems in hazardous material management arise from an institution's lack of awareness about hazardous waste and applicable regulations, the lack of proper training of the employees, highly variable waste streams which contain multiple materials combined together, the high cost and location of off-site treatments, storage and disposal facilities, and the difficulties in complying with the vast and varied hazardous material regulations.

Many different systems exist for retrieving chemical inventories, transmitting chemical records electronically to other facilities, evaluating compliance with environmental and other regulations, or monitor emergency response activities. However, prior art solutions have targeted specific solutions for a specific user which makes it very expensive and difficult for many businesses and institutions to meet the comprehensive requirements involved with using toxic and hazardous materials.

Furthermore, in many organizations chemical inventory management needs vary across the organization. However, the prior art does not provide system design that can alter the inventory design structure to meet the individual needs of the divisions and departments within a multifaceted organization. The inflexibility of present system design forces organizations to do either of the following: 1) purchase, maintain, and update more than one system, which increases the overall costs and makes it more difficult to oversee, coordinate, and manage the chemical inventory management needs of the entire organization; or 2) purchase, maintain, and update one system that forces conformity, which does not address the individual needs within the organization and can cost an organization in regard to time, money, and increased legal jeopardy.

The areas addressed by the prior art are streamlined in the present system regarding specific aspects of hazardous material/chemical management. Present off-the-shelf software packages typically address only one of the following areas of hazardous material/chemical management: 1) hazardous substance information, 2) legislative and regulatory information, 3) hazardous substance inventory management, 4) risk and hazard assessment, 5) training and testing modules, and 6) integrated emergency management. A few software packages address two or at most three of the above areas. In addition, the packages that include hazardous substance inventory management can only accommodate centralized and decentralized inventory methods. None of the prior art systems do the following: 1) true unique inventory tracking methodology, 2) support both bar code and non-bar code tracking, 3) provide comprehensive hazardous/material label printing capabilities that address regulatory compliance issues, 4) incorporate an international design element (important today with the increase in international trade and transfer of information in the everevolving global community), or 5) provide a communication network for users. Furthermore, prior art systems have limited cross platform capabilities and the designs are typically not user friendly.

Therefore, there is a need to provide a comprehensive system to allow institutions the ability to address the full range of hazardous material/chemical management essential today and in the future. Providing this capability helps minimize the amount of hazardous material produced, improves management practices, provides an additional layer of protection to emergency response personnel, provides an international component needed by present institutions working in the international arena, helps train the people to use the system, and educates the individual users regarding safe handling and storage procedures that meet or exceed present regulatory standards.

Therefore there is a need for providing a system to allow institutions to minimize the amount of hazardous waste materials produced, improve the management practices, and to help train the people using the system. Further, it would be desirable to provide a system that provides information for evaluating chemical reactions, toxicity of chemicals, chemical storage and handling procedures, and chemical disposal guidelines.

In addition, the ever-increasing sensitivity to environmental and health issues and the inherent dangers of handling, storing, and disposing of chemicals are of major concern. The sheer number of chemicals readily available at a typical laboratory makes the adequate training of employees in the proper handling of these chemicals nearly impossible without some form of assistance. Also, increasing federal, state, and local environmental/health regulations pose an overwhelming information management problem which, if not addressed, could result in debilitating fines and possible crippling financial liability to the institution.

Therefore, it would be desirable to provide an information and compliance database system that provides the user with a wide variety of critical information including handling, storage, and emergency response methods and guidelines for a cradle-to-grave management of hazardous chemicals and waste.

SUMMARY OF THE INVENTION

The present invention meets the shortcomings of the prior art and provides a comprehensive chemical management system. The chemical management system of the present invention comprises a computer having an input device, a display, and a chemical inventory control system coupled to the computer. The chemical inventory control system includes user selection of the following:

1) a central control station that monitors and places a unique identification on the inflow of chemical containers to the station, monitors the storage of chemicals, monitors and places a unique identification on the new chemical containers created by transfer from an original container(s) or by the mixing of chemicals from various stored chemical containers into a new container(s), and monitors the outflow of chemicals from a central station as waste or surplus;

2) a plurality of combined chemical receiving and outflow stations wherein each station monitors and places a unique identification on the inflow of chemical containers to the stations, monitors the storage of chemicals, monitors and places a unique identification on the new chemical containers created by transfer from an original container(s), or by the mixing of chemicals from various stored chemical containers into new container(s), and the outflow of surplus and waste chemicals;

3) a plurality of combined chemical receiving and outflow stations wherein each station monitors and places a unique identification on the inflow of chemical containers to the stations, monitors the storage of chemicals, monitors and places a unique identification on the new chemical containers created by transfer from an original container(s) or by the mixing of chemicals from various stored chemical containers into a new container(s), monitors, and uniquely tracks by use of the unique identification the creation/maintaining of a transaction file for each individual chemical container throughout the container's life from inflow to outflow, and monitors the outflow of surplus and waste chemicals; and

4) a plurality of mixtures of any of the above three defined systems.

The chemical management system further includes a unique inventory classification design structure that allows an organization to disable at the division or department level function rights for all users having access rights to the division(s) and department(s). This unique and powerful design tool will allow the organization to set different chemical inventory parameters. This will allow the organization at the highest level to alter the chemical inventory group and class structure, within the chemical inventory design, and to address the individual requirements of divisions and departments throughout the organization. For example, the chemical inventory design structure in its entirety includes the following three primary groups:

1) In-use,

2) Surplus, and

3) Waste.

Under each primary group the following four classifications:

1) Pure,

2) Trade name,

3) Preset Mix, and

4) Variable Mix.

This internal design tool will allow an organization to set up 35 different chemical inventory design structures by disabling different combinations of the above three groups and four classes, always leaving at least one group and one class operational. However, there are literally hundreds of other various combinations regarding the overall chemical management system that could be created by using the function access rights option for divisions and departments.

Furthermore, regarding chemical management, a unique password is provided for each user and the viewing of measurement data for chemical containers can be set for the user's personal preference. For example, a user's personal view preference regarding dry measurement data can be set for pounds, ounces, kilograms, or grams, and wet measurement data set for liters, milliliters, gallons, or fluid ounces. A default is set for each user's personal measurement preference but can be easily altered, by the user, when the need arises.

An environmental, safety, and health (ESH) information system is also coupled to the computer and includes user-created, unique, and customized chemical compatibility storage groups that always include one unalterable storage group. Each chemical group is preferably color-coded for a particular chemical storage area. The groups designate storage areas and nonchemical storage areas within facilities corresponding to the system. Designated chemical storage areas can be classified for the following uses: 1) hazardous material storage only, 2) hazardous material use only, or 3) a combination of hazardous material use and storage. Designated chemical storage areas, nonchemical storage areas, safety equipment placement, etc., can be viewed within the unique mapping design of the system. This design allows for the following views within a building: 1) elevation view indicating the floor(s), 2) plan view of particular floor, 3) plan view of a particular room, and 4) a plan view, or example, of shelving, cabinet, or other object where chemicals are stored. The system mapping design supports the import of numerous drawings, PICT files, scanned images, etc. In addition, various buttons can be placed in the views and be set when activated to do the following: 1) search and list chemicals located within a particular building, floor, room, general location, or specific location, and 2) indicate on the various maps, locations of chemical storage groups, designated storage areas, nonstorage areas, safety equipment, etc.

The system also includes a compliance/education file into which once pertinent information is inserted, allows the printing of compliance labels to meet government environment and health regulations for both new containers generated on site and for old containers that need replacement labels. The compliance/education file also links to ESH icons that display visual representation of hazard warning relating to each particular hazardous material. Training and education data can be created by the user or downloaded/accessed from other systems and linked to each icon and information displayed by clicking on said icon. Users can be designated as one of the following within the system and are prompted regarding ESH: 1) professional: icon prompts, 2) experienced: icon prompts and warning material review required, and 3) novice: icon prompts warning material review is required, and specific responses documenting that material review and understanding has occurred.

A safety equipment management system is coupled to the computer and generates an accurate record according to government standards. Safety equipment covered under the system includes exhaust systems and eyewash and safety showers, as well as generic safety equipment that does not fall under required or defined safety equipment.

An international chemical compatibility system is coupled to the computer system to include a multi-tiered compliance and education design. This includes a system to create compliance/education files for any country in the world with means for enabling text conversions to the foreign language of a selected country.

An integrated emergency response system is coupled to the computer system to include an ability for emergency organizations such as the fire departments, hazardous waste teams, emergency medical services, and the like to access pertinent data regarding ESH, fire ingress and egress, and integrated emergency management. The outside emergency organization, once provided both access and linkage by a computer to the chemical management system of an organization, has both view and report printing function rights in all but sensitive areas. The option to search, view, and print various chemical lists and various maps, for example, that pinpoint dangerous chemical storage areas, nonstorage areas, and fire ingress and egress routes provide both powerful and invaluable tools for integrated emergency planning and support of emergency operations that occur at the organization's site.

Finally, the overall system is designed to operate on a plurality of host platforms, each at a plurality of different locations within an organization. These platforms include, but are not limited to, Macintosh, Microsoft Windows, OS/2, Windows NT, and the like.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features of the present invention will be more fully disclosed in the following DESCRIPTION OF THE PREFERRED EMBODIMENT in which like numerals represent like elements and in which:

FIG. 1 is an overview of the system according to the present invention;

FIG. 2A is a general block diagram of one mode of operating the present system;

FIG. 2B is a general block diagram of an alternative method of using the present system;

FIG. 2C is yet another alternative method of using the present system;

FIG. 3 is a flow chart of a single stand alone version of the present system;

FIG. 4 is a flow chart of a centralized version of the present system;

FIG. 5A is a block diagram representing an example of using a central database server;

FIG. 5B is another example of using a central database server;

FIG. 6 is a window or screen for the administrative set-up of the present invention;

FIG. 7 is an example of a user window according to the present invention;

FIG. 8 is an example of a user preferences window;

FIGS. 9A,B, and C are examples of function rights windows;

FIG. 10 is an example of a department rights window;

FIG. 11 is an example of a logon window;

FIG. 12 is an example of a trace log for the a user;

FIG. 13 is an example of a window indicating all logged on users;

FIG. 14 is a block diagram of the system division/department hierarchy;

FIG. 15 is an example of a division records window;

FIG. 16 is an example of a department records window;

FIG. 17 is a example of a department access list window;

FIG. 18A is a block diagram of an example of a simple small institution;

FIG. 18B is another block diagram of a small institution;

FIG. 19A is an example of a large institution using the hierarchy of FIG. 14;

FIG. 19B is another example of a large industry using the hierarchy of FIG. 14;

FIG. 20A is still another block diagram representing the use of the system in a large university atmosphere;

FIG. 20B is a block diagram of a large corporation using the present system;

FIG. 21A is an example of an in-use inquiry window for multiple departments;

FIG. 21B is an example of an in-use inquiry window for a particular department;

FIG. 22 is an example of a send e-mail window;

FIG. 23 is an example of a read e-mail window;

FIGS. 24A, B, and C are block diagrams representing three of the possible many categorizations of chemical containers in the present system;

FIG. 25A is an example of an in-use inquiry window for multiple departments indicating the availability of surplus;

FIG. 25B is an example of an in-use inquiry window for multiple departments for a specific preset mix substance;

FIG. 25C is an in-use inquiry window for multiple departments for a specific trade name product;

FIG. 25D is an example of an in-use inquiry window for a variable mix product;

FIG. 26 is an example of a components window;

FIG. 27 is a graphical representation of various levels of chemical containers;

FIG. 28A is an example of a surplus inquiry window for a trade name;

FIG. 28B is an example of a surplus inquiry window for a preset mix substance;

FIG. 28C is an example of a surplus inquiry window for a pure substance;

FIG. 28D is an example of a surplus inquiry window for a variable mix substance;

FIG. 29A is an example of a waste inquiry window for a pure substance;

FIG. 29B is an example of a waste inquiry window for a preset mix substance;

FIG. 29C is an example of a waste inquiry window for a trade name substance;

FIG. 29D is an example of a waste inquiry window for a variable mix substance;

FIG. 30 is a block diagram of the pure chemical structure of the present system;

FIG. 31 is a block diagram of the chemical structure for trade name, preset mix, and variable mix chemicals;

FIG. 32 is an example of a main chemical records window;

FIG. 33 is an example of a list of synonyms window;

FIG. 34 is an example of a groupings window;

FIG. 35 is an example of a main chemical records window showing the grouping field expanded;

FIG. 36 is an example of the molecular structure window;

FIG. 37 is an example of the minimum and maximum amounts window;

FIG. 38 is an example of an in-use inquiry window;

FIG. 39 is an example of a chemical type/vendor records window for a pure chemical;

FIG. 40 is an example of grade codes window;

FIG. 41 is an example of a description codes window;

FIG. 42 is an example of a chemical type/vendor records window for a trade name chemical;

FIG. 43 is an example of a in-use container records window;

FIG. 44 is an example of a in-use container records window with the departments field expanded;

FIG. 45 is an example of an in-use container records window with the container type field expanded;

FIG. 46 is an example of a container types window;

FIG. 47 is an example of a open multicontainer window;

FIGS. 48A, 48B, and 48C are examples of windows showing the insertion of a substance amount into a container using a visual graphical image to insert the amount;

FIG. 49 is an example of an in-use inquiry window showing the weight and volumes in grams and milliliters;

FIG. 50 is an example of an in-use inquiry window showing the weight and volume in pounds and gallons;

FIG. 51 is an example of a conversions window;

FIG. 52 is an example of an in-use containers record window showing the manufacturer field expanded;

FIG. 53 is an example of an in-use container records window showing the retailer field expanded;

FIG. 54 is an example of a building records window;

FIG. 55 is an example of an in-use container records window showing the building field expanded;

FIG. 56 is an example of a building plans window illustrating an elevation view of a building storing chemicals;

FIG. 57 is an example of in-use container records window showing the floor field expanded;

FIG. 58 is an example of a floor plan set-up window illustrating a plan view of a building storing chemicals;

FIG. 59 is an example of an in-use container records window showing the room field expanded;

FIG. 60 is an example of a room set-up window;

FIG. 61 is an example of in-use container records window showing the location field expanded;

FIG. 62 is an example of a location set-up window;

FIG. 63 is an example of in-use container records window showing the specific location field expanded;

FIG. 64A is a partial view of the window of FIG. 64C;

FIG. 64B is a partial view of the window of FIG. 64C;

FIG. 64C is an example of in-use inquiry window;

FIG. 64D is an example of an in-use container records window;

FIG. 65 is an example of an in-use inquiry window;

FIG. 66 is an example of an in-use inquiry window;

FIG. 67 is an example of a report window;

FIG. 68 is an example of a user define report window;

FIG. 69 is an example of a screen report window;

FIG. 70 is an example of a bar code reader program editor window;

FIG. 71 is an example of a bar code interface window;

FIG. 72 is a modified block diagram with a procedure for using a bar code reader;

FIG. 72' is an example of a transfer to other department window;

FIG. 73 is a modified block diagram of an alternative method of using a bar code reader;

FIG. 73' is an example of a transfer to new container window;

FIG. 74 is an example of a transfer to existing container window;

FIG. 75 is an example of a transfer to new location window;

FIG. 76 is an example of a transactions window for a particular container;

FIG. 77 is an example of a single process for container window;

FIG. 78 is an example of a processes window;

FIG. 79 is an example of a multiple consumption process components window;

FIG. 80 is an example of a multiple consumption processes window;

FIG. 81 is an example of a personal contacts window;

FIG. 82 is a graphical representation of a portion of a manual method of using the present system;

FIG. 83 is a representation of a sign to be used in connection with the method of FIG. 82;

FIG. 84 is an example of labels containing bar codes for use on the present system;

FIG. 85 is a flow chart of the requisition request;

FIG. 86 is an example of a personal notes window;

FIG. 87 is an example of a chemical vendors window;

FIGS. 88A and 88B are block diagrams representing examples of storage groups within the institution divisions;

FIG. 89A is an example of a storage group records window;

FIGS. 89B and 89C are block diagrams setting forth examples of various storage groups and departments;

FIG. 90 is an example of a floor plan designating particular types of storage areas throughout the floor;

FIG. 91 is an example of trace log window for a particular user;

FIG. 92 is an example of an in-use inquiry window;

FIG. 93 is an example of the safety and information window;

FIG. 94 is a block diagram showing the system receiving data from regulatory agency data bases;

FIG. 95 is a block diagram representing the entry of data into the system from compliance data books;

FIG. 96 sets forth the various environmental, health, and safety icons used in the present system;

FIG. 97 is an example of a user educational window;

FIG. 98 is an example of a training session window;

FIG. 99 is an example of a MSDS location records window;

FIG. 100 is an example of a chemical compliance label;

FIG. 101 is an example of a hood certification label;

FIG. 102 is an example of a partial view of an inspection form;

FIG. 103 is a systems functional operations chart;

FIG. 104 is an administrator's menu;

FIG. 105 relates commands to icons;

FIG. 106 is a File menu;

FIG. 107 is a Bar Code menu;

FIG. 108 illustrates the relationship of the system with the archive interface;

FIG. 109 illustrates an SQL Searcher window;

FIG. 110 is a diagram illustrating how the Integrated Emergency Response Design Element is integrated within the system;

FIG. 111 is a flow chart illustrating the use of the Integrated Emergency Response Design Element;

FIG. 112 is a flow chart setting forth the system main event processing loop;

FIG. 113 is a flow chart for the logon ICP;

FIG. 114 is a flow chart for the logon to the SQL host;

FIG. 115 is a flow chart for the name and password scripting;

FIG. 116 is a flow chart for updating the user logon and logoff record;

FIG. 117 is a flow chart for storing user data in library variables;

FIG. 118 is a flow chart for verifying logon;

FIG. 119 is a flow chart for logging on to the system host;

FIG. 120 is a flow chart for obtaining the user conversion preferences;

FIG. 121 is a flow chart for building lists in random access memory;

FIG. 122 is a flow chart for setting the user default department;

FIG. 123 is a flow chart for the logon WCP;

FIG. 124 is a flow chart for a user trace log ICP;

FIG. 125 is a flow chart for the user trace log clear routine;

FIG. 126 is the user trace log WCP;

FIG. 127 is the user window ICP;

FIG. 128 is a flow chart for opening the user trace log window from the users window;

FIG. 129 is a flow chart for copying of present user record to create a new user record;

FIG. 130 is a flow chart for creating a weight conversion list;

FIG. 131 is a flow chart for creating a volume conversion list;

FIG. 132 is a flow chart for deleting a user record;

FIG. 133 is a flow chart for window clean up for the user window;

FIG. 134 is a flow chart for deleting the user access rights to the system;

FIG. 135 is a flow chart for building weight and volume conversion lists in the user window;

FIG. 136 is a flow chart for selecting lines in the list of FIG. 135;

FIG. 137 is a flow chart for copying the current user department access record when creating a new record;

FIG. 138 is a flow chart for copying a current user function access record when creating a new user record;

FIG. 139 is WCP for the user window;

FIG. 140 is the flow chart for the read mail ICP window;

FIG. 141 is a flow chart for the send mail procedure of the read mail window;

FIG. 142 is a flow chart for obtaining a list of all unread and undeleted mail;

FIG. 143 is a flow chart for responding to receive mail;

FIG. 144 is a flow chart for setting the receipt acknowledged button;

FIG. 145 is a flow chart for deleting mail;

FIG. 146 is the department window ICP;

FIG. 147 is the flow chart for the department access list for a particular user;

FIG. 148 is the flow chart for creating a SQL search string for containers;

FIG. 149 is flow chart for building a department view list;

FIG. 150 is a flow chart for setting the default department for a particular user;

FIG. 151 is a flow chart for removing the default department;

FIG. 152 is a WCP for the department list window;

FIG. 153 is a flow chart for the ICP for the send mail window;

FIG. 154 is a flow chart for the WCP as a send mail window;

FIG. 155 is the flow chart for the ICP for the users rights window;

FIG. 156 is a flow chart for creating a list of all departments within the system;

FIG. 157 is a flow chart for building a list of all the departments within the system;

FIG. 158 is a flow chart for checking the user accessible departments;

FIG. 159 is a flow chart for deleting a users access to departments;

FIG. 160 is a flow chart for a WCP of the user rights window;

FIG. 161 is the flow chart for the ICP of the user preference window;

FIG. 162 is the flow chart for bringing up the weight conversion list;

FIG. 163 is a flow chart for bringing up the volume conversion list;

FIG. 164 is a flow chart for building weight and volume conversion list;

FIG. 165 is a flow chart for selecting preferences in the weight and volume conversion list;

FIG. 166 is a flow chart for the WCP of the user preference window;

FIG. 167 is the flow chart for the ICP of the users rights function window;

FIG. 168 is a flow chart for the menu list for the rights function window;

FIG. 169 is a flow chart for creating a list of menu functions;

FIG. 170 is a flow chart for creating a list of windows for users right function;

FIG. 171 is a flow chart for creating a list of window functions;

FIG. 172 is a flow chart for building a function list;

FIG. 173 is a flow chart for removing embedded titles in menus;

FIG. 174 is a flow chart for building a menu procedure list;

FIG. 175 is a flow chart for creating a format menu procedure list;

FIG. 176 is a flow chart for building a menus list;

FIG. 177 is a flow chart for checking the users accessible functions;

FIG. 178 is a flow chart for giving access to a user;

FIG. 179 is a flow chart for removing embedded titles in windows;

FIG. 180 is a flow chart for building a window procedure list;

FIG. 181 is a flow chart for creating a format window procedure list;

FIG. 182 is a flow chart for building a windows list;

FIG. 183 is a flow chart for checking accessible window functions;

FIG. 184 is a flow chart for the WCP of the rights function window;

FIG. 185 is a flow chart for the ICP of the administrator window;

FIG. 186 is a flow chart for the administrator edit function;

FIG. 187 is a flow chart for the WCP of the administrator window;

FIG. 188 is a flow chart for the ICP of the present users window;

FIG. 189 is a flow chart for logging off a present user;

FIG. 190 is a flow chart for building list of present user;

FIG. 191 is the flow chart for the WCP of the present user window;

FIG. 192 is the flow chart for the procedure to disable and enable menu commands;

FIG. 193 is the flow chart for checking disabled commands;

FIG. 194 is a flow chart for checking for window commands;

FIG. 195 is the flow chart for the procedure to insert a log entry into the trace log of a user;

FIG. 196 is the flow chart for logging off and quitting a system session;

FIG. 197 is the flow chart for locking a record;

FIG. 198 is a flow chart for unlocking and updating a record;

FIG. 199 is the flow chart for unlocking a record;

FIG. 200 is a flow chart for obtaining a block of container ID numbers;

FIG. 201 is a flow chart for obtaining the next sequential ID number;

FIG. 202 is a flow chart for obtaining the next unused ID number;

FIG. 203 is a flow chart for obtaining the next unique ID number;

FIG. 204 is a flow chart for checking the SQL statement for errors;

FIG. 205 is a flow chart for building a list;

FIG. 206 is a flow chart for selecting a line in a list;

FIG. 207 is a flow chart for selecting the first line in a list;

FIG. 208 is a flow chart for looking up a list;

FIG. 209 is a flow chart for assigning icons to library variables;

FIG. 210 is a flow chart for converting a parameter value to grams;

FIG. 211 is a flow chart for converting a parameter value to milligrams;

FIG. 212 is a flow chart for disabling certain function accesses depending on the user ID;

FIG. 213 is a flow chart for checking access for a particular user in displaying a message;

FIG. 214 is a flow chart for checking access for a particular user in sending an audible alarm;

FIG. 215 is a flow chart for a user to send electronic mail to the systems administrator;

FIG. 216 is a flow chart for checking electronic mail;

FIG. 217 is a flow chart for sending a confirmation of receipt of electronic mail;

FIG. 218 is a flow chart for updating a departments records for container ID numbers;

FIG. 219 is a flow chart for the administrator menu;

FIG. 220 is a flow chart for the ICP as a start up of the system;

FIG. 221 is a flow chart of the library control procedure for the start up of the system;

FIG. 222 is a flow chart for the timer control procedure idle timer;

FIG. 223 is a flow chart of the ICP for setting up a new transaction record;

FIG. 224 is a flow chart for inserting a transaction;

FIG. 225 is a flow chart for the initial transaction of a container;

FIG. 226 is a flow chart of a department transfer transaction;

FIG. 227 is a flow chart of a local transfer transaction;

FIG. 228 is a flow chart of a transfer to an existing container transaction;

FIG. 229 is a transfer to a new container transaction;

FIG. 230 is the flow chart of adding a substance to a container;

FIG. 231 is a flow chart of a consumption transaction;

FIG. 232 is a flow chart of a multiconsumption transaction;

FIG. 233 is a flow chart of bringing up the context windows for the current division;

FIG. 234 is a flow chart of the context for the default department;

FIG. 235 is a flow chart for personal contacts window for the present user;

FIG. 236 is a flow chart for setting port parameters for the bar code unit;

FIG. 237 is a flow chart for the bar code program editor;

FIG. 238 is the flow chart for the bar code interface;

FIG. 239 is a flow chart for loading the bar code unit with the necessary system information;

FIG. 240 is the flow chart for the ICP for the contacts window;

FIG. 241 is the flow chart to set the contact type for the contacts window;

FIG. 242 is the flow chart for rebuilding contact list;

FIG. 243 is a flow chart for the WCP of the contacts window;

FIG. 244 is a flow chart of the ICP of the consumption window;

FIG. 245 is a flow chart to building a residual container list;

FIG. 246 is a flow chart to build a process list;

FIG. 247 is a flow chart to do a consumption transaction;

FIG. 248 is a flow chart for the WCP of the consumption window;

FIG. 249 is the flow chart for the ICP for the multiconsumption window;

FIG. 250 is the flow chart for adding to a multiconsumption list;

FIG. 251 is a flow chart for replacing a line in a multiconsumption list;

FIG. 252 is a flow chart for removing a line from the multiconsumption list;

FIG. 253 is a flow chart for adding a by product;

FIG. 254 is a flow chart for replacing a by product;

FIG. 255 is a flow chart for removing a by product;

FIGS. 256 and 257 are flow chart for the procedure run after the multiconsumption process is done;

FIG. 258 is a flow chart for building a type list;

FIG. 259 is a flow chart for building a container list;

FIG. 260 is a flow chart for setting up lists for the multiconsumption window;

FIG. 261 is a flow chart for refiguring amounts;

FIG. 262 is a flow chart for building a component list;

FIG. 263 is a flow chart for checking the inserted percentages;

FIG. 264 is a flow chart for checking edited percentages;

FIG. 265 is a flow chart for obtaining MCP components;

FIG. 266 is a flow chart for inserting a MCPC record;

FIG. 267 is a flow chart for copying MCP components to the transaction file;

FIG. 268 is a flow chart for updating container record;

FIG. 269 is a flow chart for inserting a by product record;

FIG. 270 is a flow chart for updating a by product container record;

FIG. 271 is a flow chart for inserting a by product link;

FIG. 272 is a flow chart for building a by product list;

FIG. 273 is a flow chart for inserting by product link;

FIG. 274 is a flow chart for inserting a by product;

FIG. 275 is a flow chart for building a residual container list;

FIG. 276 is a flow chart for the WCP of the multiconsumption window;

FIG. 277 is a flow chart for the ICP of the MCP window;

FIG. 278 is a flow chart for the MCP components button;

FIG. 279 is a flow chart to build the MCP list;

FIG. 280 is a flow chart for the ICP of the open case window;

FIG. 281 is a flow chart for the current container ID of the open case window;

FIG. 282 is a flow chart for selecting the parent container;

FIG. 283 is a flow chart for designating a default location;

FIG. 284 is a flow chart for establishing a new location;

FIG. 285 is a flow chart for setting a default location;

FIG. 286 is a flow chart for building a case list;

FIG. 287 is a flow chart for validating a list;

FIG. 288 is a flow chart for opening a multicontainer case;

FIG. 289 is a flow chart for the WCP of the open case window;

FIG. 290 is the ICP of the processes window;

FIG. 291 is the flow chart to build a process list;

FIG. 292 is the WCP of the processes window;

FIG. 293 is the flow chart for the ICP of the transactions window;

FIG. 294 is a flow chart of a build transaction list;

FIG. 295 is a flow chart of the WCP of the transactions window;

FIG. 296 is a flow chart of the ICP of the transfers window;

FIG. 297 is a flow chart to select a transfer type;

FIG. 298 is a flow chart containing a list of all departments user has access rights to;

FIG. 299 is a flow chart of the buildings for the division to which the user has access;

FIG. 300 is a flow chart of a list of all rooms to which the user has access;

FIG. 301 is a flow chart of the location list to which the user has access;

FIG. 302 is a flow chart of the specific location to which the user has access;

FIG. 303 is a flow chart of a list containing containers that may receive residual materials for the current container;

FIG. 304 is a flow chart for the transfer to another department;

FIG. 305 is a flow chart for a transfer to a new location;

FIG. 306 is a flow chart for a transfer to an existing container;

FIG. 307 is a flow chart for a transfer to a new container;

FIG. 308 is flow chart for adding a new container to the system;

FIG. 309 is the WCP for the transfers window;

FIG. 310 is a flow chart for the ICP of the notes window;

FIG. 311 is a flow chart for the list of notes for particular user;

FIG. 312 is a flow chart for building a notes list;

FIG. 313 is a flow chart for the WCP of the notes window;

FIG. 314 is a flow chart for designating a special chemical storage group;

FIG. 315 is a flow chart for a general description window;

FIG. 316 is a flow chart for assigning storage and nonstorage areas within buildings;

FIG. 317 is a flow chart for the compliance/education file;

FIG. 318 is a flow chart for tracking MSDS;

FIG. 319 is a flow chart for designating a user with a given rank;

FIG. 320 is a flow chart for printing labels; and

FIG. 321 is a block diagram representing the safety equipment management.

DESCRIPTION OF THE PREFERRED EMBODIMENT

The present invention is a system 10, as shown in FIG. 1, which incorporates five basic design elements into one comprehensive application 12. The five elements of application 12 are a chemical inventory control system 14, an environmental/health/safety information system 16, a safety equipment management system 18, an international compatibility system 20 and an integrated emergency response system 21. The application 12 is coupled to the user interface 22 such as a personal computer that contains a processor 24 and a data input device 26 (such as a keyboard) and a display 28 for displaying the inputted data and/or the information supplied by application 12 to the user. Preferably, a server 30 is coupled to application 12 to allow multiple stations 32 to be monitored from a central location.

Each aspect of the invention shall be discussed in detail below under the following section headings:

Section 1--Chemical Inventory Control System

Section 2--Environmental/Health/Safety Information System

Section 3--Safety Equipment Management System

Section 4--International Compatibility System

Section 5--Integrated Emergency Response System

Listed below is an outline of the Chemical Management System of the present invention. Each of the structures outlined below will be discussed in detail in various sections as indicated. Multiple structures are used for each of the five sections indicated above and specific reference will be made to the discussion appropriate for each section. It is noted that all headings in the following description follow the outline to allow for easy reference to a particular aspect of the system.

The portions of the outline that specifically concern the five design structures of the system have been set forth separately under the corresponding headings. However, these portions also maintain the outline headings to make it easy to see where each structure fits within the overall system. In addition, when reviewing the system outline below, it is essential to note that all portions of the outline are covered under section 1 unless noted "in italics" to be covered under either section 2, 3, 4, or 5.

SYSTEM OUTLINE

I. Administrative

A. Host set-up

B. User set-up

C. Function access

D. Department/Division access

E. System Electronic Mail

II. Table/Set-up Maintenance (administrator access only)

III. Chemical Management

A. Inventory classification

1. In-use

a. Pure

b. Trade name

c. Preset Mix

d. Variable Mix

2. Surplus

3. Waste

B. Inventory File Structure

1. Main

a. ID/CAS (or NO CAS)

b. Prefix

c. Name and Synonym

d. Grouping

e. Density

f. Type

g. Chemical Molecular Formula

h. Chemical Structural Formula

i. Molecular Structure Drawing

j. Molecular Weight

k. Physical State

l. Minimum & Maximum Volumes

m. Storage Group covered under section 2

i. Special covered under section 2

ii. General Description Window covered under section 2

iii. Designated Area covered under section 2

(a) Designated Storage Area and Designated Nonstorage Area covered under section 2

(b) Storage/Use Designation covered under section 2

n. Color Code covered under section 2

2. Type

a. Pure

i. Purity

ii. Grade

iii. Description

b. Trade name

c. Preset Mix

d. Variable Mix

3. Container

a. Container ID

b. Division/Department

c. Chemical Amount

i. Weight (Dry)

(a) Left

(b) Original

ii. Volume (Wet)

(a) Left

(b) Original

iii. Container Size

iv. Container Traits

(a) Container Type

(b) Single or Multiple Container

v. Visual Container Depiction

vi. Measurement Setting

d. Received (Date Received)

e. Inventory (Last Inventory Date)

f. Expiration (Expiration Date)

g. Waste (Date Converted to Waste)

h. Manufacturer

i. Product Number

ii. Lot Number

i. Retailer

i. Product Number

j. PO Number

k. Project

i. Controller

1. Mapping

i. Building

ii. Floor

iii. Room

iv. Location

v. Specific location

C. Lists

1. Consolidated Lists

2. Data Defined Entry Lists

a. Synonym--Alterable

b. Type--Alterable

c. Physical State--Nonalterable

d. Grade--Alterable

e. Description--Alterable

f. Container Type--Alterable

g. Manufacturer--Alterable

h. Retailer'Alterable

i. Building--Alterable

j. Room--Alterable

k. Location--Alterable

l. Specific Location--Alterable

m. Deterioration Category--Alterable

D. Searches & Reports

1. Searches

a. Preset searches

i. Type Lists

(a) Purity, Grade, and Description for Pure Chemicals

(b) Vendors for Trade name Chemicals

ii. Individual Container Lists

(a) Pure Chemicals

(b) Trade name Chemicals

(c) Preset Mix Chemicals

(d) Variable Mix Chemicals

b. User Defined Searches

i. Components of a Preset Mix

ii. Multiple Consumption Process

iii. SQL Searcher

2. Reporting

a. Ad Hoc Reporting

b. Preset Reports

E. Inventory

1. Division specific

a. Bar code

i. Method One

ii. Method Two

b. Nonbar Code

2. Department Specific

3. Site Specific

F. Transactions

1. Container

a. Single Consumption Process (SCP)

b. Multiple Consumption Process (MCP)

2. MSDS covered under section 2

IV. Safety Equipment Management all of IV covered under section 3

A. Fume/Exhaust Systems

B. Chemical Eyewash and Safety Showers

C. Generic Category

V. Compliance and Education all of V covered under section 2

A. Compliance/Education File

1. Boolean Check Boxes

2. Data Defined Entry Lists

3. Inserting Text

4. Insertion of Information

5. Automatic Threshold Analysis

B. Environmental/Safety/Health Awareness Icons

C. Interactive Educational Multimedia

1. Development Tools Provided for On Site Development of Systems

2. Professionally Developed Multimedia Modules

D. Information Gathering

E. MSDS Scan and Text Import

1. Cataloging

2. Scan and Text Import

VI. Archiving

A. Transactions

1. Users

a. Normal System Functions

b. Compliance/Education Functions covered under section 2

i. Education Rank covered under section 2

(a) Professional covered under section 2

(b) Experienced covered under section 2

(c) Novice covered under section 2

(d) Automatically Updating of the Rank from Novice to Experienced covered under section 2

2. Containers

B. MSDS covered under section 2

C. Users

VII. Labels

A. Hazardous Materials

1. Tracking

a. Bar Code

b. Nonbar Code

i. Hand Written

ii. Printer Generated

2. Chemical Name/Compliance covered under section 2

a. Secondary Containers covered under section 2

b. Mixed Containers covered under section 2

c. Surplus Containers covered under section 2

d. Waste Containers covered under section 2

e. Replacement for Labels for the Original Containers covered under section 2

B. Fume Hoods covered under section 3

C. Eyewash and Safety Showers covered under section 3

VIII. Requisition System

IX. Contact Manager

A. Vendors

B. Department Personnel

C. Division Personnel

D. Personal Contacts

E. Government Agencies

F. Professional Support

G. Hazardous Waste Companies

H. Emergency Phone Contacts and Numbers

X. International Design Elements all of X covered under section 4

A. Multi-tiered Compliance/Education File

B. Text Translator

XI. Integrated Emergency Response all of XI. covered under section 5

Section 1--Chemical Inventory Control System

Chemical inventory management is increasingly mandated and controlled by local, state and federal regulations. These regulations have increasingly become more stringent in order to minimize the use of chemicals and develop suitable cradle-to-grave management systems for tracking hazardous materials. There are three essential ways of managing the chemical inventories and they are centralized, decentralized, and uniquely identified methods. Shown in FIGS. 2A-2C are three chemical management methods that can be used with the present system.

FIG. 2A discloses the centralized method 200, which is the least complicated design. A central receiving station 202 is used to record all incoming chemicals 204-210 and categorize pertinent information for each of the chemicals. Centralized method 200 requires the close monitoring of the inflow of chemicals 204-210 at the central station 202 and the subsequent non-monitored outflow of chemicals at users sites 221, and either one of the following: 1) non-monitored movement of chemicals to and from multiple storage areas 212, 2) a non-monitored movement of chemicals to and from a central storage station 212, or 3) a monitored movement of chemicals from a centralized storage station 212 leading to the eventual close monitored disposal of waste chemicals at a centralized disposal station 220. In addition, the central storage receiving station 202, central storage station 212, and the central disposal station 220 can either be: 1) singular/separate units; 2) two combined units and one separate unit; or 3) one combined unit. Furthermore, a periodic inventory of the volume of each container holding chemicals can be performed, depending on the centralized inventory approach, at the centralized stations 202, 212, or 220. As can be seen in FIG. 2A, all chemicals received at stations 202 are labeled as indicated at 219. If chemicals 203 and 205 are combined to form a new chemical 207, the new chemical 207 is recorded in computer memory and labeled at the central receiving station 202. In like manner, if a part of chemical 203 is placed in a separate container 208, part of chemical 205 is placed in separate containers 209-213 or part of chemical 211 is further placed in containers 215 and 217, at user sites 221, all of the new containers are recorded in computer memory and are labeled individually at the central receiving station 202.

FIG. 2B discloses a decentralized method 222 that incorporates several combined receiving and disposal stations 224 strategically located throughout an academic institution, a corporation, or a small business. Each station 224 is responsible for maintaining an up-to-date chemical inventory at its respective place. The maintenance of chemical inventories is accomplished by recording the inflow of chemicals 226, 228, and 229 and labeling them as indicated at 225 and the subsequent non-monitored outflow of chemicals at users sites 240, and the monitored or non-monitored movement of chemicals to and from multiple storage areas 230 leading to the eventual close monitored disposal of waste chemicals at multiple disposal stations 238. In addition, the multiple receiving stations 224, multiple storage stations 230, and multiple disposal stations 238 can be: 1) singular/separate units or 2) various combinations of receiving, storage, and/or disposal stations. However, both receiving and disposal stations closely monitor chemicals while storage stations may or may not monitor storage depending on the decentralized inventory approach followed. Furthermore, this inventory control method supports the periodic inventory of the volume of each container holding chemicals at the multiple stations 224, 230, and 238.

Next, FIG. 2C discloses the third approach to chemical inventory management, the uniquely identified method 246. This method requires that each individual chemical container 248, 249, and 250 be uniquely identified, preferably by use of a bar code 259 and tracked throughout the container's useful life, i.e., until all the chemical within a given container is used or finally disposed of as a waste. This is accomplished by maintaining a transaction file, or T file, 257 of the particular container. This methods incorporates a real time approach to chemical management and can provide the ability to update information daily regarding quantity, location, container volume, container transfer, container consumption, and eventual container disposal. This is done by uniquely marking chemicals 248, 249, and 250 at a receiving station 254 and continuously tracking the containers during the following operations: 1) use at user sites 268, 2) movement of chemicals to and from multiple storage areas 256, and 3) eventual disposal of containers at multiple disposal stations 258. This system is the most thorough and rigorous form of chemical inventory management and enables one to know how much of a chemical went down the drain (into the waste water or sewage system), up a stack (into the atmosphere), was transferred to another container, was transformed into a by-product, or became waste.

The present invention incorporates the ability to easily accommodate any of the three chemical management methods or any combination of these management systems. This is accomplished through the following design structures within a system as set forth in the outline above.

I. ADMINISTRATIVE

The administrative set-up of the present invention has structure allowing it to operate in very dissimilar environments such as a small business with one computer, a large university with disparate environments, or a large industry with multiple plants remotely located from each other. As those skilled in the art will realize it is preferable that the cross-platform capabilities of such a system to work in various environments such as Microsoft Windows.TM., Unix.TM., OS-2.TM., or Macintosh.TM. relies heavily on a programming language such as Omnis 7.TM..sup.3 to support such a system design.

A. Host Set-Up

Preferably the host set-up uses the same format to create a connection from the present invention to a host such as those available from Oracle.TM., Sybase.TM., or Ingres.TM.. This allows the present invention to operate in different host and cross-platform environments. Three examples of such environments are shown in FIGS. 3, 4, 5A, and 5B.

FIG. 3 illustrates a standard computer platform 300 such as Macintosh.TM., Windows.TM., Unix.TM., etc. in a stand alone set-up. In this configuration a standard computer platform 300 has the application 302 installed within the computer and the application 302 connects to a sequel query language ("SQL") data file 304 via an SQL connect routine 306.

FIG. 4 illustrates an array of SQL servers 400 access through various platforms 402, 404, and 406 that all could be different native platforms. The SQL server or data file 400 is accessed by the platforms 402-406 via similar application and connect routines 410, 414, and 418 as described above in FIG. 3.

The third example of the system operating in host and cross-platform environments is shown in FIGS. 5A and 5B. In FIGS. 5A and 5B the central SQL database server 500 is accessed through various platforms 502-514 as shown. It is possible to connect a large number of SQL servers to various platforms simply by using the proper connects provided for in the programming language used in the present invention such as the preferred Omnis 7.TM..sup.3. Each connect routine 306, 410, 414, and 418 enables the present invention to interact with the SQL server 304, 400, or 500. Once the host set-up is completed it is likely that it will not be used again unless the data is moved to a different host. The host set-up creates the ability to communicate to the present inventive system the host type, location, which particular connect to use, and sets up password protection for each user.

Password protection includes unique passwords for each user, expiration of passwords after a preset time, and disabling passwords after a preset number of invalid log-in attempts. A typical set-up window 600 is shown in FIG. 6 which allows the system administrator to set up the defaults and supply the necessary information as indicated in FIG. 6.

Specific, detailed flow charts of preferred procedures within the present system that correspond to the last set-up are set forth at FIGS. 114-119, 185-187, 196, and 220

B. User Set-Up

The novel user set-up of the present invention allows every individual, including the administrator, to have their own user record 700 that is displayed to the administrator such as in FIG. 7. The user record defines the extent of access that a particular user has to the inventive system and includes an automatic logoff field 702. For example, the record defines personal user preferences, which were set by the user as seen in FIG. 8 at window 800. Window 800 includes allowing the user to establish a desired weight conversion 802 and a desired volume conversion 804 into a preferred set of units. In addition, the system allows the user to check a series of boxes 806 to set-up the various default conditions for displaying vendors, check E-Mail, or initially displaying the first type of a found main chemical record. The user record also defines the access level of a particular user. This access level is set by the system administrator and includes function access and division, department and user access as explained below at headings C and D, in connection with windows 900 and 1000 shown in FIGS. 9A, B, and C and 10, respectively.

Also, the user set-up portion of the system preferably tracks certain defined functions allowed by each user's access level and places these functions in a user's trace log. For example, when a user logs on, such as shown in FIG. 11, by entering his name at numeral 1100 and his password at 1102, logs out, inserts, edits, deletes data, or if the user makes an ID block request, etc., the system hereof preferably automatically places this information in the individual user's trace log such as shown in FIG. 12 at window 1200. In order to eliminate the problem with users logging on to the system but not actively using the system, which can tie up and significantly slow down the effectiveness of the system, the present system preferably allows the administrator to preset an auto logoff time for each individual user, such as shown in FIG. 7 at 702. In addition, the administrator preferably has the ability to check to see which users are logged-0n to the system at any given time such as shown in the example of FIG. 13 at window 1300.

The flow charts that specifically concern the user set-up portion of the present system are set forth at FIGS. 124, and 127-139.

C. Function Access

As used herein the term "function" is defined as any button, menu, menu item, list, field, or any object the user can click or double-click on to make an action occur. Preferably, the system hereof is set to default to a state such as when a user record is initially created the user has access to all functions within the system except for administrative functions. The administrative function then preferably allows the administrator to restrict at the top level the division access of all users within the division, at the mid level the department access of all users in the department, and finally at the bottom level the individual user access to any of the functions within the system. The present system incorporates a three-tier hierarchy function access design that supports different restriction of function access from the top (division level) to the mid (department level) to the bottom (user level). Further stated, the restriction of function access at the division level restricts the function access of all the departments under the division and all users with access to any department within the division. Next, the further restriction of function access at the individual department level (within the above division) will further restrict the function access of all users within the department. Finally, the administrator can further restrict function access at the individual user level.

Function access is controlled by building the L.sub.-- ACCESS.sub.-- LIST shown in TABLE I LOGON. This list will contain a record for every function to which a user, department, or division does not have access.

                  TABLE I
    ______________________________________
     ##STR1##
    ______________________________________