System architecture and technology selection

Three weeks of decisions set the cost of the next five years. Almost every expensive problem we are called in to fix was designed in before anyone wrote a line of flight code.

How the system divides: the deterministic core and its guaranteed rate on one side of the boundary, perception and mission on the other, with the ground segment and power beneath.

A wrong bus topology is not recoverable

A wrong autopilot can be swapped. A wrong bus topology cannot, and neither can a sensor whose supply dries up in year two. Both surface during integration, when the schedule has no slack left and changing direction costs programme years.

So we are regularly engaged for nothing else — no hardware, no firmware, just the architecture and the selection behind it. The alternative is finding the answer empirically, which is the most expensive way to learn it.

Which commercial parts to build on, and why

Most of an airframe is already on the market: autopilots, receivers, radios, cameras, motors, compute modules. The architecture is the decision about which of them to build on, how they are wired together, and what has to be written to make them behave as one system.

  • Requirements interrogation. What the system must do, separated from what the specification currently says. The two differ more often than not.
  • Trade studies with numbers. Candidate architectures scored against mass, power, thermal envelope and certification route — not against preference.
  • Component and supplier selection, including second sources, end-of-life exposure, and what each part does at the edge of its rating rather than in the middle.
  • Failure analysis before build. What breaks, how it is detected, and what the vehicle does next.
  • A written architecture your team can build from — interfaces, budgets and the reasoning behind each choice, so the decisions survive the people who made them.

We sell the parts, so we know which ones come back

We distribute thousands of commercial components a month, and have done for ten years. That is not a business that happens to sit beside the engineering — it is the evidence underneath it. We see which parts come back, and which second sources are real rather than promised.

We are also the first users of everything we sell. A part we recommend is a part we have flown, instrumented, and in several cases stopped using. Our catalogue is narrower than a distributor's for that reason.

What you get

  • A decision you can defend to a customer, an auditor or a certification body
  • End-of-life exposure known before it becomes a redesign
  • An integration phase with no architectural surprises left in it

Tell us the constraint you cannot get past

The mass budget, the latency, the environment, the certification route. We will tell you honestly whether it is something we should be working on — and if it is not, who should.