If combustibles are not relocated, wet down, or protected with welding curtains or blankets, the hot sparks and slag from welding can easily lead to ignition. Summary of Experiences, Specific Tasks and Activities Performed. While designated hot work areas should have a 35-foot clear radius of combustibles typically maintained, there are very few areas in the average facility that are always clear of combustible material 35 feet in all directions from a given point. These sparks and slag are typically at a temperature above 1,000 degrees F when thrown from the hot work operations-a temperature which can easily ignite paper, wood, flammable liquids, vapors, and many other combustibles if they are allowed to come into contact. The log sheet template will provide information about what the problem is, where, and when it happened.
#WORK HOURS LOGSHEET PROFESSIONAL#
This professional activity becomes essential for checking purposes when problems occur.
Sparks and molten material from hot work can be scattered more than 35 feet during welding, cutting, and grinding. Most businesses use a log sheet to keep track of chronological notes or incidents that happen in the place of work. Hot work is often synonymous with welding and cutting but also includes any work activity with potential to produce ignition sources or excess heat, such as burning, brazing, grinding, soldering, thermal resistance heating, or torch applied roofing. Hot work continues to be a leading cause of industrial fires, consistently in the top five across all industries, and it has been responsible for many of industry's most severe fire losses. Using a daily work log is a helpful productivity tool to track an employee’s activities and his accomplishments during the day.
As such, it serves two purposesas a to-do list that the employee plans to accomplish and a work log after the task is complete. It's highly advisable to use a hot work permit system for all hot work operations outside the designated area A plan for the next day may also go in the daily work log.
0 kommentar(er)
