How should legacy controls be treated during retrofits?

• A. Replace all legacy controls with new ones and ignore old logic.
• B. Delete existing sequences and start fresh without mapping.
• C. Document existing sequences, map to new design, implement improved logic where feasible, and test.
• D. Tolerate legacy controls and do not modify.

Answer: (C)

When upgrading controls, you should preserve and improve what the system already does by documenting the current sequences, mapping them to the new design, implementing improvements where feasible, and then testing thoroughly. Start by capturing how the legacy controls currently operate—the sequences of operation, interlocks, alarms, setpoints, and any time schedules. This creates a clear record of intended behavior and actual behavior, which is essential for a smooth retrofit and for verifying that nothing important is lost.

Next, map that documented logic to the new control design. This ensures the new system reproduces the required functions and relationships, even if the hardware or software platform has changed. It also helps identify areas where the design can be aligned with modern standards, improved reliability, or better energy performance without sacrificing safety or function.

Where feasible, implement improved logic. You can optimize sequencing, tighten interlocks, improve fault handling, and enhance energy efficiency or occupant comfort, but only in ways that preserve the essential operations shown in the legacy sequences. This approach leverages the benefits of the new platform while maintaining proven behavior.

Finally, test. Validate that the new control logic matches the documented and mapped intent, verify interlocks and safety functions work, calibrate sensors, and confirm the system meets performance expectations under normal and fault conditions. Robust testing provides evidence that the retrofit delivers the required functionality and avoids surprises after turnover.

Other approaches fall short because they either discard necessary functions, risk introducing unverified behavior, or miss opportunities to improve performance while maintaining proven operation.