Field programmability offers a way to adapt electronic functions after a device has been manufactured, rather than fixing every detail during production. In a 2000 keynote to the Field Programmable Logic (FPL) Conference, semiconductor technologist Tsugio Makimoto connected the growing use of programmable devices to a broader industry pattern: a recurring swing between standardization and customization. For automation engineers and technical decision-makers, that framework helps explain the design choices behind reconfigurable hardware and updateable embedded systems.
Makimoto’s Wave: a cycle between standardization and customization
Makimoto’s Wave describes an observed tendency for the semiconductor industry to alternate, roughly over decade-long periods, between standardized products and custom-designed solutions. It is a way to interpret industry direction, not a precise timetable for predicting what a particular technology or market will do.
The historical sequence presented in the keynote illustrates the idea. The period from 1967 to 1977 was associated with IC and LSI, including custom LSI design. From 1977 to 1987, microprocessors and memory represented a more standard-oriented phase. ASICs came to characterize the custom-oriented period from 1987 to 1997. The following decade was identified as an era of field-programmable devices, including FPGAs.
These shifts reflect changing priorities. Design automation, manufacturing, and testing tools can make custom solutions more practical, encouraging differentiation. But customization can also bring higher development effort and cost. Standard products can help address time-to-market and operational-efficiency pressures, while an overly standardized approach may limit opportunities to tailor a product or add value. In Makimoto’s analogy, the semiconductor “pendulum” moves as these competing pressures change.
Why field-programmable devices gained momentum
Field-programmable devices offer a middle ground between fixed standard components and fully custom hardware. A system can use a standard device while allowing some of its behavior to be configured through programming. The keynote described FPGAs and programmable microcontrollers as examples of this approach. It also discussed combining programmable logic with processor functions, bringing hardware and software flexibility together on a chip.
The attraction is adaptability. A design based on programmable hardware may be adjusted without creating a wholly new custom circuit for every change. The degree and method of flexibility vary by device: the keynote, for example, identified FPGA technologies based on SRAM, EEPROM, anti-fuse, and EPROM cells, each with its own characteristics. Device selection therefore depends on the application rather than on programmability alone.
For automation teams, the underlying design question is whether requirements are stable enough to justify a fixed implementation, or likely to change enough that configurability is valuable. Potential changes may concern product variants, application behavior, or maintenance needs. The source’s examples are drawn from electronics rather than industrial control projects, so they should be read as illustrations of the design principle, not as claims about a particular automation product.
Updates can extend flexibility beyond manufacturing
Programmability can shift where and when software is written. The keynote traced a microcontroller progression from mask ROM to EPROM-based Z-TAT, flash-based F-ZTAT, and EEPROM-based E-ZTAT versions. In the mask-ROM model described, programming took place at the LSI factory. With programmable versions, programming could instead occur later in the supply chain or at a service location.
The practical distinction is that configuration or software changes need not always be completed at the semiconductor factory. In examples presented at the conference, an F-ZTAT microcontroller could be programmed with regional specifications by a drive manufacturer. The presentation also described writing new applications after a drive had shipped and updating software for an automotive application at a service station. These examples show how field programmability can support product variation and post-shipment maintenance.
Such flexibility does not eliminate engineering decisions; it changes where they occur. Teams still need to decide what should be configurable, when updates are appropriate, and which device technology fits the application. The keynote emphasizes the option to make changes later, rather than providing a universal prescription for how updates should be managed.
Shorter product lifecycles raise the value of adaptability
A second theme in the keynote was the shortening lifecycle of electronic products. It compared the maturation periods of products such as phones, televisions, mainframes, and PCs, and showed how successive generations of CD-ROM drives moved through their lifecycles more quickly. The presentation contrasted older products with digital consumer products that could ramp up rapidly, experience demand fluctuations, and reach end of life on a much shorter timescale.
That kind of market change puts pressure on development and operations. A design may need to accommodate revisions or product variants within a compressed lifecycle. Field-programmable components can provide one route to changing functions without treating every revision as an entirely new hardware design. However, the source does not suggest that programmability alone solves lifecycle, production, or supply challenges. It presents adaptability as one response to changing requirements.
The same balancing act appears in custom-chip economics. As the keynote noted, increasing chip complexity can raise mask costs, while lifetime production volumes may decline. That combination can make the cost of customization per chip more difficult to justify. Programmable approaches and products that combine standard components with configurable logic offer alternatives to consider when full customization is impractical.
Applying the lesson to automation decisions
Makimoto’s Wave is most useful as a strategic lens. It encourages engineering and operations teams to assess both the stability of requirements and the cost of preserving flexibility. When evaluating a programmable device or architecture, consider:
- How likely are requirements to change? A stable, well-defined function may not need the same flexibility as a product expected to support variants or revisions.
- Where should changes be made? The keynote’s examples span programming at a manufacturer, after shipment, and at a service location.
- What type of programmability fits? FPGA and programmable-microcontroller approaches have different underlying technologies and should be selected according to the application.
- How does the product lifecycle affect the decision? Shorter development and market cycles can increase the value of adaptability, while customization and device choices still carry trade-offs.
Conclusion
The rise of field-programmable devices illustrates how semiconductor design responds to shifting demands for flexibility, cost control, and speed. Makimoto’s Wave frames those demands as an ongoing movement between customization and standardization. For industrial automation decision-makers, the practical takeaway is to treat programmability as an architectural option: assess where requirements may change, when updates may be needed, and whether configurable hardware offers a better fit than either a fixed standard device or a fully custom design.