When you visit a manufacturing site, the path to improvement is often right in front of you. You can see where the bottlenecks are, where rework occurs, and what needs to change. Those who have worked on the floor for years usually understand these issues with remarkable accuracy. Yet, even after years pass, the same problems remain in the exact same places.
This gap is commonly attributed to a lack of investment, outdated equipment, or labor shortages. These explanations are not entirely wrong. However, when the same issues continuously reappear even at facilities that have invested in new equipment and advanced systems it becomes clear that these factors are not the whole story.
In this series of articles, we want to share how we define and address problems on the manufacturing floor. Our core message is simple: manufacturing problems do not exist solely because the necessary technology is lacking. More often, the problem itself has not yet been defined in a form that technology can interpret and solve.
Three Disconnects That Keep Problems from Reaching Technology
First, the language of the shop floor and the language of engineering do not meet.
Problems on the manufacturing floor often
exist in statements such as, “Material variations have become greater lately,”
or “That angle can only be handled manually.” These statements are not
inaccurate. They are condensed observations built over years of experience. The
problem is that they often remain untranslated into variables that can be
observed, measured, and verified from an engineering perspective, such as heat
input, restraint conditions, work sequence, and tolerance accumulation. A
problem that has not been translated cannot become a target for improvement.
Individual experience continues to accumulate, but it does not remain as data
that the company can use.
Second, people make judgments, but systems
record only the results.
Most important decisions made on the
manufacturing floor are never recorded. The reasons behind a particular
sequence of work or the decision to avoid certain conditions may be reflected
in the final result, but they are not preserved as data. Meanwhile, systems
accumulate only the results, without the reasoning behind them. In this
situation, no matter how much data is collected, it becomes difficult to define
what should be learned from it. Automation is often limited not because there
is no data, but because the reasoning behind human decisions was never captured
as data.
Third, improvement ends as a project, while
operations return to routine.
Improvement is usually carried out as a
project with a defined timeframe. Once the project ends, responsibilities
change, exceptions gradually accumulate, and eventually the process returns to
its previous way of operating. If an improvement does not change the operating
procedure itself, its results remain in reports rather than on the
manufacturing floor.
That is why we start by looking at the essence of the problem.
Whether to apply AI, introduce automated
equipment, or develop software is decided only after identifying the cause of
the problem and the conditions under which a solution can be applied. Even when
the means are predetermined by the nature of a business or project, we maintain
one principle: we do not force problems on the manufacturing floor to fit
the solution.
Many technologies and machines have already
been introduced into manufacturing environments. However, more important than
the number of technologies available is the ability to define a problem on the
shop floor in a form that technology can understand and address.
1. Record
the situation and the decisions made at the time without interpretation.
2. Form
hypotheses about the cause and verify them under actual operating conditions.
3. Select
the appropriate solution based on the verified cause and application
conditions.
4. Validate
performance and identify application limits in the actual production process.
5. Integrate
the findings into work standards, systems, and data structures, then verify
them again through ongoing operations.
JL
Heavy Industries operates real manufacturing facilities and has directly
addressed challenges in cutting and machining processes. At the same time, we
develop drawing data solutions, NC code, CAM, and automation software. This
does not mean that we have solved every problem. Rather, it means that we have
a structure in which observations from the manufacturing floor can be carried
through to process engineering and software development, and the results of
that development can be verified again in actual production. That is the
foundation for why we are beginning this conversation.
We begin with cutting, machining, welding processes, and production data. We do not assume that what we learn can be applied directly across all areas of manufacturing. However, we will examine these questions one by one: where data becomes disconnected in actual production environments, how the lack of standardization in the tools required for production, including software and hardware, affects manufacturing operations, and how automation software changes the way workers make decisions.
A record of the conditions for application and their limitations,
failed attempts, and problems that remain unsolved.
That is how JL Heavy Industries approaches
manufacturing problems through technology.
댓글 쓰기