ARROW Andon highlights the errors
machines connected to Machine Track
ARROW customer since
The production of an assembly line, for instance, is usually kept continuous. In the Andon philosophy, when an error occurs, the line is stopped and the reason for the problem is investigated. When the downtime is recorded into the information system, it is possible to systematically deal with the causes.
The Wärtsilä factories in Vaasa manufacture big diesel engines for ships and power plants. During the years 2006 – 2007, a new assembly plant was built in Vaasa to manufacture W32/34 engines. It was built on the principle of an assembly line where the engine moves forward as the assembling proceeds. Earlier, large engines were assembled in immovable production cells.
An engine that weighs tens of tons cannot be placed on an assembly line, so the arrangement is that the engine proceeds on the line with steps that can be measured in days. The morning and evening shifts install components into engine blocks and the night shift moves the parts forward to the next assembly area.
The new philosophy
The production control applies the Andon production philosophy that originates in Japan and the Toyota car factory. The principle is not to keep the production going no matter what but to systematically investigate the occurring errors.
The role of the assembler has changed from how it was earlier when the assembler tried to solve the problems inside the assembly cell. Nowadays, the assembler simply sends a report and it is someone else’s job to worry about finding the cause and a solution to the error. Problems are not swept under the carpet but instead, they are brought to the daylight and their causes are rooted out.
“In each assembly cell, there is an error button that activates further measures. The error message is sent as a text message to three units: production, logistics and quality control. Each department sends to the assembly area a representative that has been assigned to this ‘fire brigade’ ”, says development manager of production planning, Mikko Ketonen.
When the group is together, the message is signed for and the cause of the problem is determined. The reasons are various: sometimes a wrong component has found its way to the assembly area or then the component is missing altogether. The cause can also be found in the quality of the components, in which case changing the material will be considered.
Ultimately, when both the cause and the solution to prevent such an error in the future have been determined, the incident is recorded into the system. This information is collected into the database and summed up basically by applying methods familiar from Machine Track.
Read more about our success stories
“The implementation was a multi-stage project, and of the six operational groups, water management was the first to adopt it. The system also includes collection point images and equipment maintenance instructions, so that when maintenance or repair is needed, people know to take the correct spare parts and tools with them”
Read success story
“Clear objectives were set for the maintenance system. The system should enable efficient and systematic control of own resources and projects. In distributed maintenance, it is indispensable that the directors have a tool to enable this.”
Read success story
“When selecting maintenance software, the most important criteria for us were that it should have a clear, internet-based user interface, be easy to start using, have a fairly simple machine hierarchy and low total costs. The total costs were lower because we didn’t have to hire external help to create the system and our share of the labour was only moderate as well”
Read success story