Brownfield Integration: Making New Automation Talk to Legacy Equipment
Elsner Engineering Works | Hanover, PA — Purpose-Built Precision Since 1934
Most automation does not get installed in a gleaming new facility. It lands in a working plant full of equipment of every age—a thirty-year-old press next to a five-year-old CNC next to a machine whose controller is no longer manufactured. This is brownfield reality, and it is where many automation projects quietly run into trouble. A new automated cell that performs flawlessly in isolation is worthless if it cannot exchange signals with the machines upstream and downstream of it. Integration, not the machine itself, is often the hardest engineering problem in an automation project.
The challenge is widespread because modern automation is still far from universal. U.S. Census Bureau research on advanced technology adoption found that the use of robotics and advanced automation remains relatively low and concentrated among larger firms, which means most manufacturers are integrating new capability into facilities built around older equipment rather than starting fresh. For these plants, the question is never just “what machine do we need” but “how will it communicate with what we already run.”
The Protocol Problem
The core difficulty is that machines of different eras speak different languages. A modern cell might use an industrial Ethernet protocol; an older machine might offer only a serial connection, a set of discrete hardwired signals, or a proprietary interface with no documentation. Getting them to coordinate—so the new cell knows when the upstream machine has finished a part and the downstream machine knows when to expect one—requires bridging those differences deliberately rather than hoping they connect.
Interoperability standards are what make this tractable. NIST’s testing of manufacturing communication standards demonstrates how protocols like MTConnect and OPC-UA can provide a common, non-proprietary vocabulary for equipment to exchange structured data across different systems. Where a machine supports a modern standard, integration is comparatively clean. Where it does not, the integrator’s job is to build the translation layer—adapters, gateways, and added sensing—that lets old and new equipment share a common understanding of what is happening on the line.
Reading the Existing Equipment First
Successful brownfield integration begins with documentation, not design. Before anything is engineered, the existing machines have to be assessed: what control systems they run, what communication options they expose, what signals are actually available, and how reliable those signals are. Older equipment often hides surprises—undocumented modifications, partial failures masked by operator workarounds, or controls that were never designed to talk to anything outside the machine. Discovering these during design is inexpensive; discovering them during installation is not.
For equipment that lacks modern connectivity entirely, the path is usually to add it. Sensors, modern controllers, and communication interfaces can be retrofitted onto an older machine to give it a voice on the network—a process closely tied to [PLACEHOLDER: Machine Safeguarding and Risk Assessment — Designing Automation to OSHA, ANSI/RIA, and ISO 13849], since opening up a legacy machine to modernize its controls is also the moment to bring its safeguarding up to current standards. The assessment that precedes integration frequently reveals that a machine needs both a connectivity upgrade and a safety upgrade, and doing them together is far more efficient than revisiting the machine twice.
Integration Is an Engineering Discipline, Not a Cable
The biggest misconception about integration is that it is a matter of connecting wires. In reality it is a multidisciplinary design problem spanning controls, electrical, mechanical, and software, and it has to be validated before the integrated system reaches the floor. The communication between new and existing equipment is verified as part of Factory Acceptance Testing wherever possible, the discipline described in [PLACEHOLDER: Factory Acceptance Testing — What to Expect Before a Custom Machine Ships], so that integration faults are caught at the builder rather than during a live changeover.
This is also why integration rewards experience with both new and old equipment. An integrator that understands legacy controls, modern protocols, and the realities of a working production floor can design connection points that are robust rather than brittle—handling the timing, fault conditions, and edge cases that a simple signal swap ignores. Done well, brownfield integration lets a manufacturer add modern capability without replacing functional equipment, protecting both the existing investment and the production schedule. Done poorly, it produces a sophisticated new cell stranded on an island, unable to coordinate with the plant around it.
Planning a Brownfield Project Around Production
The defining constraint of a brownfield project is that the plant has to keep running while the integration happens. Unlike a greenfield build, where equipment is installed in an empty space, brownfield integration unfolds around active production schedules, limited floor space, and the reality that the machines being connected may be running orders that cannot stop. Planning the installation and tie-in sequence around production windows—and designing the new system so it can be connected in stages rather than all at once—is often as important as the technical integration itself.
Phasing is the tool that makes this manageable. A well-planned brownfield project identifies which connections can be made and tested during normal operation, which require a brief planned stoppage, and which can be staged so the line returns to production at the end of each shift even if the full system is not yet complete. This sequencing is worked out during engineering, in collaboration with the plant’s production team, because only they know which lines can be released when. An integrator who ignores the production calendar can deliver a technically sound system while causing more disruption than the automation is worth.
Commissioning a brownfield system also benefits from a fallback plan. Because the new automation depends on existing equipment behaving as documented, a prudent project keeps the ability to revert to the prior method of operation until the integrated system has proven itself under real production load. This safety net lets a plant adopt new capability without betting a shift’s output on everything working perfectly the first time. The combination of careful phasing, production-aware scheduling, and a reversion plan is what separates a brownfield integration that strengthens a plant from one that holds it hostage during startup.
Elsner Engineering: Custom Automation Built and Tested in Hanover, PA
Elsner Engineering specializes in integrating new automation with the equipment manufacturers already run, designing control systems that communicate with older machines through modern protocols, hardwired signals, or added sensing—so new capability strengthens an existing line instead of stranding it.
Our Automation Capabilities Include:
- Custom Automation Machinery — Turnkey automated cells and full production lines, designed and built in-house
- Machine Retrofit & Upgrades — Modern controls, vision, and connectivity added to existing equipment
- Contract Engineering — Multi-disciplinary mechanical, electrical, and controls design for complex projects
Planning an automation project? Contact Elsner Engineering to discuss your application with an engineering team that has built machinery in Hanover, PA since 1934.
Frequently Asked Questions
What is brownfield integration?
Brownfield integration is adding new automation into an existing facility that already contains equipment of varying ages, rather than building a new line from scratch (a greenfield project). The central challenge is making the new equipment communicate and coordinate with older machines upstream and downstream, which often use different—or no—modern communication protocols.
Can new automation communicate with machines that have no modern controls?
Yes, though it takes engineering. Where a machine offers only serial connections, hardwired discrete signals, or a proprietary interface, an integrator builds a translation layer—adapters, gateways, or added sensors and controllers—so the machine can exchange the signals the new automation needs. For equipment with no connectivity at all, modern controls and sensing can often be retrofitted to give it a presence on the network.
Why is assessing existing equipment important before integration?
Because older equipment frequently hides issues—undocumented modifications, intermittent faults, or controls never designed to communicate externally. Documenting each machine’s control system, available signals, and reliability before design means those realities shape the solution. Discovering them during installation instead causes delays and rework, often while a production line sits idle.
Should integration and safety upgrades be done together?
Usually, yes. Opening up a legacy machine to add modern controls and connectivity is the natural moment to bring its safeguarding up to current standards as well. The pre-integration assessment often shows a machine needs both, and combining the connectivity and safety upgrades into one project is far more efficient than engineering, scheduling, and revisiting the machine twice.
Works Cited
Fisher, Ryan, and Guodong Shao. “Testing of the MTConnect – OPC-UA Companion Specification.” National Institute of Standards and Technology, www.nist.gov/publications/testing-mtconnect-opc-ua-companion-specification. Accessed 15 June 2026.
Beede, David, and Emin Dinlersoz. “Three Results From Recent Research on Advanced Technology Use and Automation.” U.S. Census Bureau, 11 Sept. 2023, www.census.gov/newsroom/blogs/research-matters/2023/09/advanced-technology-use-and-automation-results.html. Accessed 15 June 2026.