Thoughts on failures caused by one operation procedure

Thoughts on failures caused by one operation procedure

 

In the morning, I joined the staff of the Department to operate the analytical instruments. The staff knew nothing about the instruments, so I wrote the operational procedures to guide her.

 

although the procedure I have compiled is already very detailed, there are still some loopholes that cannot be used by a layman to operate the instrument, this led to the feasibility and operability of my work instruction book for the entire environment of the company. I think most of the technicians are similar to me, and there must be something that the work instruction book cannot detail a job, this is what the company knows. I think about this as follows:

Due to the differences in people's cognitive and expressive abilities, different people have different descriptions of the same thing. Similarly, one thing is that the descriptive language generated by different technologists is also different.
In addition, people will always make some mistakes. for documents with strict requirements such as work instruction books, the craftsman will always have these or some omissions, resulting in the failure of work instruction books to complete their functions, sometimes it even plays a negative role.

In view of the above two points, it is recommended that the company establish a mechanism, or prepare a work instruction book to compile general rules, which stipulate and describe some common terms, and define common operation methods. The advantages of making such a file are:
1 New employees can be trained in a unified manner. They only need to be trained to familiarize themselves with these commonly used terms and methods, which reduces the huge changes caused by the flow of personnel.
2 Communication between the craftsman and the operator at the bottom is easier.
  3 The work instruction book prepared by the craftsman does not need to be lengthy, but does not need to explain some frequently-used terms (the operator may not know these terms due to knowledge ), you only need to explain some remote locations, reduce the length of the work instruction book, and reduce the form of mistakes.

This is also a suggestion from my superiors.

Many management books often say that the process should be well done. Most of our management systems are introduced from advanced companies such as the United States. Most people only see the huge benefits of Process Reengineering, but ignore the premise and foundation of process reengineering. Many managers of the company often say that the process should be clear at meetings. It is true that a clear process will bring very good product quality and quantity. This also led to a majority of management activities targeting the process, with few management operations hitting the technical level. Even with the management of related technologies, it was also intended to spread the data storage and so on, instead of further managing technology management.

Third-stream enterprises make products and first-class enterprises make standards. Why can't I set a standard for my company?

Define repetitive technical terms, concepts, and operation methods in a standard or provision to form a management document, this will inevitably make technical exchanges within the company easier, thus reducing the chance of technical errors. For example, when the development of computer languages has reached a certain stageCLanguageISO,C ++Language standards. In this way, people who use these technologies will save repetitive work and make it easier to reuse them!