3.2.7: Case Study - The Factory of the Future
- Page ID
- 66025
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\( \newcommand{\dsum}{\displaystyle\sum\limits} \)
\( \newcommand{\dint}{\displaystyle\int\limits} \)
\( \newcommand{\dlim}{\displaystyle\lim\limits} \)
\( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)
( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\id}{\mathrm{id}}\)
\( \newcommand{\Span}{\mathrm{span}}\)
\( \newcommand{\kernel}{\mathrm{null}\,}\)
\( \newcommand{\range}{\mathrm{range}\,}\)
\( \newcommand{\RealPart}{\mathrm{Re}}\)
\( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)
\( \newcommand{\Argument}{\mathrm{Arg}}\)
\( \newcommand{\norm}[1]{\| #1 \|}\)
\( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)
\( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)
\( \newcommand{\vectorA}[1]{\vec{#1}} % arrow\)
\( \newcommand{\vectorAt}[1]{\vec{\text{#1}}} % arrow\)
\( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\( \newcommand{\vectorC}[1]{\textbf{#1}} \)
\( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)
\( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)
\( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)
\( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)
\(\newcommand{\longvect}{\overrightarrow}\)
\( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)
\(\newcommand{\ket}[1]{\left| #1 \right>}\)
\(\newcommand{\bra}[1]{\left< #1 \right|}\)
\(\newcommand{\braket}[2]{\left< #1 \vphantom{#2} \right| \left. #2 \vphantom{#1} \right>}\)
\(\newcommand{\braopket}[3]{\left< #1 \vphantom{#2}\vphantom{#3} \right| #2 \vphantom{#1}\vphantom{#3} \left| #3 \vphantom{#1}\vphantom{#2} \right>}\)
\(\newcommand{\qmvec}[1]{\mathbf{\vec{#1}}}\)
\(\newcommand{\op}[1]{\hat{\mathbf{#1}}}\)
\(\newcommand{\expect}[1]{\langle #1 \rangle}\)
\(\newcommand{\dfn}[1]{\emph{\textbf{#1}}}\)
Chuo Motor Corporation: The Gate That Wasn't Supposed to Ask Questions
Chuo Motor Corporation was eighteen months into a multi-year transition to next-generation robotic automation at its new smart factory outside Nagoya, a project run on a strict stage gate structure where every phase needed formal governance board approval before the next tranche of funding released and construction moved to the next stage of the factory floor. The plan had been solid when the board approved it, built around a specific generation of robotic arms specified down to the model number and locked into the original 3.2 billion yen equipment budget.
Yuki Tanaka, the robotics engineering lead, brought something to the Phase 3 gate review that wasn't on anyone's agenda. A new generation of manufacturing robots, faster and more precise than the ones written into the original stage gate documents, had come onto the market at a price only about 10 percent above the original spec. "If we lock in the old generation now," she told the board, "we'll be running equipment that's already a step behind before full production even starts. These new arms would cost us roughly 3.6 billion yen instead of 3.2 billion, but they're rated for a longer service life and tighter tolerances, which should cut scrap rates on the precision welds significantly."
Hiroshi Sato, the finance director, wasn't persuaded that this was the moment to reopen a plan the board had already signed off on. "Redesigning part of the factory floor at Phase 3 means renegotiating our contract with the original equipment supplier, and their penalty clause alone runs close to 400 million yen if we walk away from committed units at this stage," he said. "That's before we even count the four-month schedule slip Yuki's own estimate assumes." Yuki didn't back down. "That 400 million yen is real," she said, "but it's a fraction of what we'll spend replacing the old generation early once it's obsolete mid-lifecycle. My team's model puts the ten-year total cost of ownership at roughly 900 million yen lower with the new robots, mostly from fewer replacement cycles and less energy waste per unit produced." Neither number was wrong. They just weren't measuring the same thing, and the board didn't have an obvious way to weigh a guaranteed near-term cost against a projected long-term saving that depended on assumptions nobody in the room could fully verify yet.
Board member Masaru Endo, who'd sat through every gate review since the project's approval, argued for treating this one like all the others. "The stage gate exists to confirm we're on track and release the next tranche," he said. "It's not the place to relitigate equipment decisions we already made." Kenji Watanabe, chairing the board, pushed back on that framing directly. "If a stage gate only ever exists to wave a project forward," he said, "then it isn't actually protecting anything, it's just a scheduling formality with a signature attached. The whole reason we built these gates into a high-risk capital program was so a moment like this one had somewhere to land instead of getting steamrolled by momentum." The room didn't settle the disagreement so much as sit with it, because both readings of what a stage gate was for had a real claim behind them.
After two additional weeks of analysis the board hadn't originally scheduled, Kenji brought the group to a decision that satisfied the letter of both arguments without fully resolving either one. The board authorized a hybrid approach: the new robotics generation would go into the factory's precision welding line, the section where Yuki's tolerance argument mattered most, while the remaining lines would proceed with the originally specified equipment as planned, preserving most of the existing supplier contract and avoiding the full 400 million yen penalty. Hiroshi called it a reasonable hedge against Yuki's unproven long-term projections. Yuki called it a partial win that left most of the factory running equipment she still believed would be obsolete before the plant reached full production.
What the decision didn't settle was what happened at the next stage gate, when the precision welding line's new robots would have been running long enough to generate real performance data against Yuki's model, while the rest of the factory would already be further along with the older equipment and harder to retrofit without repeating the same cost and delay argument all over again. It also left Chuo Motor running two different robotics standards inside a single factory indefinitely, doubling the spare parts inventory and the technician training required to service both systems, a complexity the board's decision memo mentioned in a single sentence without assigning anyone responsibility for managing it. Kenji closed the gate review without a firm answer on whether the hybrid approach was a genuine compromise or simply a way of deferring the actual decision to whichever future gate happened to have better data and worse options.
- The board's hybrid decision put the new robotics generation on the precision welding line while leaving the rest of the factory on the original spec. Was this a legitimate use of the stage gate's authority to pivot, or did it avoid the harder either-or decision the gate was actually designed to force?
- Weigh Hiroshi's 400 million yen near-term penalty and schedule cost against Yuki's projected 900 million yen in ten-year savings. Whose argument is stronger given only the numbers presented at this gate, and what additional evidence would the board need before treating either estimate as reliable enough to act on?
- The decision left Chuo Motor running two robotics standards in one factory, with the resulting spare parts and training complexity acknowledged but not assigned to anyone. Should the board have resolved that operational question before approving the hybrid path, or is it reasonable to defer it to a later gate once real performance data exists?

