CELUS puts a reviewable plan in front of component research

CELUS has added a beta workflow in which its Design Assistant proposes a plan, waits for engineering approval and then researches a system architecture and components. The change moves more of the early planning into the software, while giving the engineer a document to inspect before that work starts.

Called the Intent Document, it records requirements gathered through questions about interfaces, power, cost and compliance. CELUS says the assistant then builds a block diagram, links component recommendations to datasheets or specifications and checks the result against the recorded requirements. It can also rank alternatives and export design material into established EDA tools.

A plausible block diagram can leave supply sequencing unresolved or say nothing about how a circuit behaves when an external connection is missing. Recording those assumptions early makes them easier to challenge before they become embedded in component choices.

Approval depends on what the plan contains

Take a hypothetical battery-powered instrument with a sensor interface, a processor and a wireless connection. A plan might allocate a power budget and select devices whose typical consumption fits it. The design can still miss its operating target if the budget omits radio current peaks or the time spent waiting for a measurement to settle. In this hypothetical example, the budget can only be checked properly if those operating conditions have been recorded. It is not a reported CELUS failure.

The approval step becomes useful when an engineer can inspect those conditions and see how they lead to the proposed parts and power budget.

The same applies to alternatives. A cheaper regulator can change the output-capacitor requirements; a similar interface device can alter the permitted power-up sequence. Ranking by price or lead time helps narrow a search, but the constraints that made the first part acceptable still have to accompany the substitution.

Checking the conditions behind a recommendation

Linking a recommendation to original documentation gives a reviewer somewhere to check it, provided the recommendation also preserves the relevant operating conditions. A datasheet may contain several current ratings, each referring to a different operating mode, or place an important condition in a footnote far from the headline specification.

Those conditions have to survive the move into component choice and exported design. If a requirement changes, the decisions that depend on it also need to be identifiable. A recommendation can retain a valid citation while becoming unsuitable for the revised circuit.

“The decision stays with the person who has to stand behind the design,” says founder and chief executive Tobias Pohl.

CELUS says the more involved workflow takes longer than a single prompt. Its claim of fewer revision rounds is not accompanied by a controlled benchmark in the announcement.

NXP already offers CELUS technology through its Block Diagram Designer. The new beta is available on the CELUS Design Platform, although the release does not confirm whether it is also available through NXP’s existing implementation.

Sources

• CELUS-issued announcement: workflow, beta availability and attributed statements
• NXP: existing Block Diagram Designer, separate from the newly announced CELUS beta
• CELUS: existing Design Assistant architecture and design-block documentation

Image: Two people inspecting a circuit board. Illustrative photograph, not CELUS software, its output or its staff. Photo: Bulat843 / Pexels. Image source. Licence.