Safety codes, rules and procedures

The whole purpose of safety codes, rales and procedures is to provide the information on which to build routinely safe behaviom. On this basis, failure to implement the reqnirements of safety codes, rules and procedures is unquestionably a violation and is often seen as the root canse of an accident/incident and an imequivocal indication that the person who breached the rules is responsible for the ensuing accident/incident. However, this conclnsion assumes that the code, rale or procedure is appropriate, practical, well written, well communicated (whether by formal training or otherwise) and appropriately supervised/reinfoiced. Unfortunately, this is often far from the truth as the examples below show quite clearly. 

Despite these particular difficulties miiung operations generally rely heavily on written safety codes, rules and procedures. 

It is impossible to underestimate the very real culmral, ethnic, language and educational difficulties which are evident in many mines and the difficulties that these create for the effective development and implementation of good qnality safety codes, rules and procedures. 

The nature and extent of the dangers. .. the source of such dangers and how best to avoid them is a very succinct description of the purpose and objectives of safety codes, rules and procedures. 

Codes, rules and procedures (including, for example, method statements, safety instractions, permits to work, safe working practices etc.) are, in effect, the instruction mannals of the Safety Management System. Like instraction manuals in everyday life they range from totally invaluable to completely useless. 

All of the information provided in Section 5.2 in relation to improving the training provision for codes, rules and procedures applies equally in relation to the wider aspects of safety training considered in this chapter. 

Finally, in this outline of the crucial elements for an effective safety management, the Safety Management System must be comprehensive. As well as covering the obvious elements such as defined responsibilities, codes, rules and procedures, training etc. it must encompass those aspects... 

If the application software is written in a FVL, the developer should follow the requirements and guidelines in lEC 61508-3. If the application software is written in LVL or FPL, the developer may follow the lEC 61511-1 ANSI/ISA-84.00.01-2004 Part 1 (lEC 61511-1 Mod) requirements and guidelines. The developer should follow the restrictions and procedures provided by the logic solver vendor in the safety manual. Programming guidelines and coding/configuration rules should also be developed and used if needed. 

Rules of procedure designed to secure uniformity and protection of life and property having the force of law in certain jurisdictions. Examples include Occupational Safety and Health Administration (OSHA) Standards (29 CFR 1910) and the National Fire Protection Association (NFPA) Codes. See also General Industry Safety Standards. 

In the world of occupational safety, the ever-present requirement to achieve 100% compliance with written codes, rules, regulations, or established operating procedures is a challenge in and of itself. However, in the practice of system safety, it must be... 

Positive measure refers to the positive safety action taken to control or mitigate hazards. Measures include design features, safety equipment, procedures, safety rules, or other controls including physical security and coded control systems, used collectively or individually, to enhance safety and to reduce the... 

---