Opens in a new tab

Product Development Delays That Start in the Control Spec

November 18, 2026
Avnan Team
Please share this

Most delays get blamed on the phase where they show up. A board fails a test, firmware misses a milestone, or a part arrives later than the schedule allows, and the team treats it as a problem with that phase. Trace a few of these back and many started earlier, in the control spec. Something was left open, assumed, or never written down, and every task after it inherited the problem. Here are four places that happens, and what you can do about each.

What the control spec has to settle

Your control spec fixes what the controller reads, what it drives, how it communicates, what environment it works in, and which standards it has to meet. Schematic, firmware, layout, test plan, and sourcing all start from it. When a line is vague, each team fills it in a different way, and you find out when the pieces come together.

1. Compliance and security rules that arrive late

Rules change while you’re designing. The first obligations under the EU Cyber Resilience Act took effect on September 11, 2026. Manufacturers of connected products must now report actively exploited vulnerabilities and severe incidents, with an early warning within 24 hours and a full notification within 72 hours. Most of the other requirements apply from December 11, 2027. If your control uses Wi-Fi, BLE, or BACnet/IP and you sell in the EU, vulnerability handling and software updates are worth writing into the spec now. We cover this in our post on the EU Cyber Resilience Act and building controls.

2. Control logic described loosely

“Stage the compressor based on demand” can mean three different things to the hardware engineer, the firmware engineer, and the tester. Fault handling is the usual trouble spot: what counts as a fault, what the controller does about it, how it recovers, and what gets logged. Have firmware in the room before it’s frozen, and write behaviors as statements a test can pass or fail.

3. Parts chosen without sourcing input

A control spec that names a microcontroller or programmable device without a supply check is a schedule risk. Avnet Silica’s Q3 2026 outlook reports rising lead times on microcontrollers and lead times approaching 52 weeks for many programmable logic devices. It suggests flagging the parts that put the most schedule at risk, such as a device with few alternatives, before the design is fixed. PTC’s October post shows the cost of finding out late: when a supplier ends a part’s life, the fix touches the BOM, the approved manufacturer list, requalification, test procedures, and manufacturing documentation. Ask sourcing to review the spec before freeze.

Tightening the control spec before freeze

Hold one review with engineering, firmware, sourcing, and manufacturing before the spec is frozen. Give every open item an owner and a date instead of leaving it as TBD. Bring in DFX early, so manufacturability, testability, reliability, and cost are on the table while changes are still easy to make. Then set a change rule: after freeze, any change gets a quick check on parts, firmware, tests, and certification. At Avnan, DFX means considering those four things during engineering instead of waiting until a design is ready for production.

Key Takeaways

  • Have sourcing check parts before freeze, and set a change rule for after it.
  • Trace a late problem back to the control spec before blaming the phase where it appeared.
  • Write down each interface’s limits, timing, and recovery behavior, with an owner and a test, including what the pins do before firmware starts.
  • Put compliance and security requirements in the spec, including the Cyber Resilience Act if you sell connected controls in the EU.
  • Write control behavior as statements a test can pass or fail, and get firmware into the review.
  • Have sourcing check parts before freeze, and set a change rule for after it.

Looking For A Partner?

If you’re looking for a partner to help you build your electronic controls solution, contact us.

Related Posts