Privacy statement: Your privacy is very important to Us. Our company promises not to disclose your personal information to any external company with out your explicit permission.
At AIPCon 10, Jordan Edwards and Sean Koh, CFA spotlighted how Jordan is using Palantir Foundry to operate Mixology Clothing Company with his sister, Gabby Edwards, proving that you don’t need to be an engineer to build powerful software and agentic workflows. By taking the “Forward Deployed CEO” approach, he shows how the person closest to the problem can directly create tools that scale team capabilities and drive real operational impact. Jordan also thanked Palantir for selecting Mixology as one of 11 companies to demo live and one of just three featured in the Backstage Pass films, while praising the team behind the platform. His takeaway was simple: early movers compound, and those who adopt and build first can unlock outsized results.
I keep seeing the same problem in foundries: orders rise, but output stays flat. The shop floor feels busy, yet molds wait, metal cools too long, and rework eats the day. I have watched teams blame the furnace, the crew, or the schedule. Most of the time, the real issue is simpler. Work is not flowing. Small delays stack up, and each delay cuts output.
When I help a foundry lift production, I start with the bottleneck. I look at the point where parts wait the longest. In one mid-size iron foundry, the pouring area kept stopping because molds were not ready when metal arrived. The fix was not a new machine. The team changed mold prep timing, set a clear handoff between molding and pouring, and cut idle waiting. Output climbed because the line stopped stalling.
I also focus on setup work. A lot of foundries lose hours to changeovers, tool swaps, and small checks that happen in a loose way. I ask the team to group similar jobs, stage tools before the shift starts, and keep the most used items close to the work area. I saw one plant cut changeover waste by using a simple shadow board and a short checklist. The crew spent less energy searching, and more energy making sound castings.
Maintenance matters as much as pace. A machine that runs poorly may still run, but it drags the whole shop down. I prefer short, regular checks on mixers, conveyors, furnaces, and cooling systems. I like clear signs on what must be inspected and who owns each task. At one aluminum foundry, a worn part on a sand system caused hidden slowdowns for weeks. After the team set a daily check and replaced the part early, the line moved more smoothly.
Data helps me keep the plan honest. I do not ask for a pile of reports. I ask for a few numbers that show where output leaks away: pieces poured, scrap rate, rework count, downtime minutes, and waiting points between steps. When a supervisor can see those numbers on one sheet, the next move gets easier. I like to review them at the end of the shift, not as a blame game, but as a map for the next run.
People need clear habits too. A trained crew can spot problems before they grow. I have seen simple coaching work better than long meetings. One worker learns how to catch a sand defect early. Another learns the right way to handle a hot mold without slowing the line. When each person knows the next step, the shop feels calmer, and output grows without extra noise.
I also pay attention to scrap. Every bad casting uses labor, power, metal, and patience. I tell foundry teams to study the top three defect types, not every small issue at once. A steel foundry I worked with kept finding the same edge crack. The answer was not more pressure on the crew. The team adjusted cooling practice and checked one step in the shakeout area. Scrap dropped, and good parts moved out faster.
My view is simple: bigger output does not need a dramatic move. It comes from cleaner flow, tighter handoffs, regular upkeep, and a team that knows what to watch. When I see a foundry grow faster, I rarely see chaos. I see fewer pauses, clearer roles, and less waste. That is the pattern I trust, and it holds up on busy floors.
I keep hearing the same concern from foundry teams.
The line stays busy. The furnace keeps running. The day still ends with fewer good castings than expected.
That gap usually does not come from one big failure. I see it come from small stops, slow handoffs, uneven mold quality, and scrap that grows quietly through the shift. One delay turns into three. Then the whole line feels heavier.
What helps is not a flashy promise. I look for changes that a crew can repeat on a normal day.
I always watch where work stops moving.
A team may blame the furnace, yet the slow point can sit at shakeout, mold prep, or pouring transfer. I once saw a mid-size gray iron foundry in the Midwest miss output goals for months. The crew thought they needed more heat capacity. The real issue was a long walk between molding and pour area. Parts waited too long, molds cooled unevenly, and rework kept climbing.
They moved staging closer, set clear handoff rules, and kept the path open. The line felt smoother the same week.
I trust stable input more than fast recovery.
When sand moisture drifts, mold strength shifts too. Then the team starts chasing defects instead of running the line. I like to see one person own the start-of-shift check. That person can confirm moisture, temperature, and mix before the first mold goes down the line.
One plant I worked with cut repeated breakage this way. They did not add extra steps. They removed confusion.
Small batches can hurt output when changeovers drag.
I have seen crews lose a lot of time by switching patterns too often, moving tools back and forth, and searching for the next job. A cleaner job sequence helps. I prefer grouping similar castings, staging the next pattern early, and keeping the tools near the station that uses them most.
This sounds basic. It works.
Scrap is expensive when the whole batch is already done.
I like simple checks at the start of the line, not after problems spread. A quick look at mold fill, gating, temperature, and surface finish can stop repeat defects before they turn into a pile of rejects. One ductile iron shop I supported used to catch issues after cooling. After they moved one quality check closer to pour time, they stopped losing good hours to late fixes.
I have learned that output rises when the crew knows the same rule set.
People do better when each station has a clear job. Who checks the sand. Who watches the pour. Who clears the next pallet. Who calls a stop. When these roles stay clear, the shift runs with less noise. New workers also settle in faster, since they do not need to guess what comes next.
I also like visual boards. A simple board with targets, scrap notes, and delayed jobs gives the team a quick view of the day. No extra talk. No long search through old reports.
A foundry does not need a dramatic fix to lift output.
I have seen better results come from basic discipline: tighter handoffs, steadier input, faster checks, and less motion that does not help the part move forward. That is why many foundry managers keep talking about the same kind of gain. They want more good castings from the same day, the same crew, and the same floor space.
When I look at a shop that keeps improving, I rarely see magic. I see fewer pauses. I see cleaner steps. I see a team that knows where loss begins and deals with it before the whole line feels it.
I have seen a lot of foundries chase output by buying more machines, adding more labor, or pushing people to work faster.
That is not the move I would make first.
The real pain usually sits somewhere smaller and easier to miss. A line stops for a few minutes. A mold waits for a crane. A core arrives late. Sand quality drifts. One delay turns into five more. By the end of the shift, the team feels busy, yet the tonnage does not move the way it should.
The simple shift behind a major output jump is often this:
I stop treating output as a casting problem alone, and I start treating it as a flow problem.
That change sounds basic. It is basic. It also changes a plant fast.
I once looked at a mid-sized foundry that blamed low output on aging equipment. The team wanted more automation. The manager wanted overtime. Yet the real bottleneck sat in plain sight. Parts were moving in batches, not in a clean sequence. One area worked ahead, another area waited, and the shop floor kept paying for those gaps.
When I helped the team map the day, one fact stood out. The line was not slow everywhere. It was slow at handoff points.
That is where I began.
I asked one question:
What keeps the next step from starting on time?
That question led to a simple set of changes.
I made the start of each shift more disciplined.
The team used to begin with a mix of talk, guesswork, and quick fixes. Some people went straight to their own tasks. Others waited for a supervisor to assign work. Small issues hid inside that loose start.
We changed that.
I asked for a short pre-shift review at the same spot every day. The team checked mold availability, core readiness, sand condition, melt plan, crane use, and repair needs. Nothing fancy. No long meeting. Just a clear look at what could block the line.
That small habit cut a lot of wasted motion.
I also pushed for visual staging near the point of use.
Before that, workers spent too much time walking parts across the floor. Patterns sat far from where they were needed. Consumables were stored in different corners. The line lost minutes here and there, then lost real output.
We moved key items closer to the work area. We marked locations on the floor. We made the “ready now” items easy to see.
The team did not need more effort. It needed less searching.
I paid attention to one bottleneck at a time.
That matters more than people think.
Many plants try to fix everything at once. They touch the furnace, the molding line, the finishing area, the maintenance plan, and the schedule all in the same week. That creates noise. No one can tell what helped.
I prefer one clear target.
In this case, the bottleneck was waiting. Waiting for material. Waiting for approval. Waiting for the next step to clear.
We tracked each wait and asked a simple follow-up:
Can I remove this delay, shorten it, or move the task earlier?
Some delays disappeared after a small change in order. Some needed a tighter handoff. Some needed a spare tool kept at the station.
The line improved because the team kept solving the same kind of problem the same way.
I also found that clear ownership mattered more than people admit.
If a task belongs to everyone, it often belongs to no one.
So I gave each step one name. One person checked readiness. One person confirmed movement. One person handled escalation if a delay showed up. That did not mean one person did all the work. It meant one person watched the handoff.
That single change reduced the “I thought someone else had it” problem.
A real example makes this easier to see.
A plant I worked with had a pattern of good mornings and poor afternoons. Early output looked fine. Then the line slowed, and the last part of the shift felt rushed. The team thought the furnace or the mold line was the issue. After a few days of tracking, I saw the real pattern: the lunch break reset the rhythm, and the team returned without a clear queue or a clear next job.
We fixed that by setting the next two jobs before the break ended. Workers came back to a ready plan. They did not have to ask what was next. Output steadied. Stress dropped. The floor felt calmer.
That is the part I like most about a simple shift.
It does not just raise numbers. It makes the work feel more controlled.
If I were improving a foundry today, I would follow this path:
I would map the delays that happen every day.
I would mark the one step that blocks the rest.
I would build a short pre-shift check around that step.
I would keep key materials close to the point of use.
I would assign one owner for every handoff.
I would track the same few signals each day, not fifty of them.
Those steps do not need a big budget. They need attention and consistency.
The lesson I keep coming back to is simple.
When output jumps in a foundry, the gain is not always hiding in a new machine or a large project. Sometimes it comes from a cleaner start, a tighter handoff, and a line that moves without extra waiting.
That is the shift I trust.
It is small on paper.
It can change the whole day on the shop floor.
I keep hearing the same concern from foundry teams.
Scrap keeps creeping up.
Rework eats into the day.
Orders move, but margins stay tight.
Small problems build into bigger ones, and the floor starts to feel harder to control.
That is usually the moment I step back and ask a simple question: where is the real loss happening?
I do not start with a sales pitch. I start with the process.
In one foundry I worked with, the team thought the main issue was casting quality alone. After I walked the line with them, I saw a different picture. The melt data was not being checked the same way across shifts. Sand readings were being recorded, but not used in a steady way. A few operators had good habits, yet the process depended too much on memory and guesswork.
That kind of setup is common.
I have seen it in plants that run well on good days and struggle on busy ones. I have seen it in places where the team works hard, yet the numbers still drift. The issue is not effort. The issue is control.
When I look at a foundry that wants better results, I focus on three things.
I check the points where variation starts.
Pouring temperature, sand condition, melt consistency, and inspection steps all matter. If one of them shifts without notice, the whole line feels it later. A small change at the front can turn into a reject at the end.
I look at how the team handles each shift.
A process that works only when one senior operator is present is not stable enough. I want clear steps, simple checks, and records that the whole team can follow. When the work is easy to repeat, the floor gets calmer.
I watch how problems are closed.
Some plants find the same issue again and again. The notes are there, but the fix never becomes part of the routine. That is where loss stays hidden. Once the team tracks the cause, sets one owner, and reviews the result, the problem stops coming back as often.
Here is the kind of change I prefer to see.
A foundry starts with a basic review of scrap points.
The team separates defects by pattern, not just by count.
Operators get a short checklist that fits the shift flow.
Supervisors review the same data every day.
The plant makes one adjustment, then watches the result before moving to the next.
That pace may feel slow at first. It is not glamorous. It does work better than chasing ten fixes at once.
I remember one shop that had repeated surface defect issues on a product line. The team had already tried quick corrections, and each one gave only a short break. We sat down with the records, checked the sand test logs, and compared them with the defect notes. A clear pattern showed up. The problem was not one single point. It was a mix of uneven checking and weak handoff between shifts.
After they tightened the check routine and made the shift handoff more direct, the defect trend became easier to manage. The plant did not turn into a perfect site overnight. That never happens. Yet the team had a clearer grip on the line, and the work became less reactive.
That is what I mean when I talk about better results.
I do not mean a loud promise.
I mean cleaner control.
Fewer surprises.
Better use of the people already on site.
If your foundry feels stuck in the same cycle, I would start with the same questions I ask every time:
Where does the variation begin?
Which check is too easy to miss?
What keeps repeating across shifts?
What one step would make the floor easier to run?
Once those answers are clear, the path gets easier to follow.
I have learned this after many plant visits: the foundries that move forward are not always the ones with the biggest spend. They are often the ones that make the process simpler, track the right points, and keep the team aligned.
That is where real progress starts.
Contact us today to learn more Hu: dgliheng168@163.com/WhatsApp +8613509684273.
Womack, J P 1990 Lean Thinking
Shingo, S 1985 A Revolution in Manufacturing The SMED System
Liker, J K 2004 The Toyota Way 14 Management Principles from the Worlds Greatest Manufacturer
Nakajima, S 1988 Introduction to TPM Total Productive Maintenance
Imai, M 1986 Kaizen The Key to Japans Competitive Success
Harrington, H J 1991 Business Process Improvement The Breakthrough Strategy for Total Quality Productivity and Competitiveness
Why pay for a fixed line when a mobile low pressure machine can cut installation costs by up to 40%? For businesses that need flexibility, speed, and lower overhead, mobile solutions offer a smarte
One machine can do a lot, but can it do it all? Speed, accuracy, and portability are the three benefits that matter most when choosing the right computer for work, study, and everyday tasks. A trul
We were drowning in rework until we switched to this mobile low pressure system. By delivering consistent pressure exactly where it’s needed, it helped reduce errors, improve application quality,
What if you could produce complex metal parts in far less time without sacrificing quality? A mobile low-pressure
Email to this supplier
Contact


Send Inquiry
PRODUCT CATEGORIES
Privacy statement: Your privacy is very important to Us. Our company promises not to disclose your personal information to any external company with out your explicit permission.
Fill in more information so that we can get in touch with you faster
Privacy statement: Your privacy is very important to Us. Our company promises not to disclose your personal information to any external company with out your explicit permission.