Novomorphic

Decide what to build before you build it

Partitioning, budgets, interfaces and risk, settled in the first weeks.

What you get
  • Partitioning study
  • Requirements and interface specification
  • Feasibility and risk report
Applied in
GRID-5G
Sectors
Aerospace & Defence, Energy & Critical Infrastructure, Telecoms & Open RAN, Industrial, Robotics & Electrification
First step
Architecture workshopOne to two days. Written opinion within a week.

When to bring us in

The decisions this stage settles

  • You are deciding between an FPGA, an off-the-shelf part and custom silicon, and the business case turns on which.

  • Your system spans analogue, digital, RF and power, and no single supplier owns the boundaries.

  • A previous programme respun and nobody can say which decision caused it.

  • You need a number for a board paper, and “it depends” is not an acceptable answer.

What changes

What you get that you did not have

Integration risk is named before it is expensive.

Partitioning decisions are made against budgets rather than preference. Interfaces get owners.

The programme cost and schedule estimate rests on stated assumptions you can challenge, rather than on an experienced guess. And if the answer is that custom silicon is not justified, you get that answer in weeks rather than after a year of development.

Scope

What is in scope

  • Requirements capture and constraint analysis
  • System partitioning across analogue, digital, RF, power and software
  • Power, thermal, latency, noise and area budgets, with the trade-offs made explicit
  • Interface and data-movement architecture
  • Technology and process selection
  • Build-versus-buy and FPGA-versus-ASIC analysis
  • Programme cost, schedule and risk modelling
  • Verification and validation strategy defined at architecture, not retrofitted

Not included

We do not select your suppliers for you, negotiate foundry commercial terms, or produce a detailed implementation before the architecture is agreed. Where the study concludes that a standard part or an existing platform is the right answer, we say so. That outcome is a successful study, not a failed one.

INTERACTIVE · SYSTEM FIRST

One budget, set once

Four suppliers pad it four times. One team allocates it once.

Over by 4.5 ms

End to end, ms
Sense2.5
Compute5
Connect5
Act2
Joins owned
Supplier padding

Each supplier pads its block. Together they miss.

Illustrative budgets, not measured results.

How we work

Four stages, and a written output

  1. Constraints

    We start from what cannot move: the envelope, the standards, the schedule, the existing platform. Half a day with your engineers, before any design opinion is offered.

  2. Options

    Two or three credible architectures, each costed against the same budgets, with the assumption set exposed.

  3. Trade-off review

    A working session, not a presentation. Your team challenges the assumptions; we change the numbers in the room.

  4. Recommendation

    A written report: the recommended architecture, the interface specification, the risks with owners and mitigations, and a costed route to the next gate.

7 pages, PDF

The partitioning checklist

A printable version of the six questions behind our architecture configurator: reaction time, power source, connectivity, service life, consequence of compromise and volume. What each answer tends to mean for sensing, compute, connectivity and actuation, and space for your own.

What’s inside

  • The six questions we ask before any architecture opinion
  • What each answer tends to mean for the design
  • Space to write your own answers

Read next: System architecture and feasibility: capability brief

5 pages, PDF

System architecture and feasibility: capability brief

Decide what to build before you commit budget to building it. A short brief covering when to bring us in, what is in scope and what is not, how the work runs, and the questions buyers ask first.

What’s inside

  • When to bring us in, and what you have at the end
  • What is in scope, and what is not
  • How the work runs, step by step
  • Straight answers to the questions buyers ask first

Read next: Digital ASIC design, verification and DFT: capability brief

In fifty seconds

From constraints to one recommendation

System Architecture, in 50 seconds.

FAQ

Questions about System Architecture

Who owns the output?

You do. The report, the architecture and the interface specification are yours. Where the work generates something patentable, ownership is agreed in the contract before the work starts, not after.

Will you sign an NDA first?

Yes, before any technical detail is exchanged. Say so in your enquiry and we will send one.

How long does a workshop take?

One or two days on site or remote, with a written output within a week.

What if we already have an architecture?

Then we review it. An independent partitioning review before a design freeze is one of the cheapest risk reductions available to a silicon programme.

What do you need from us?

The constraints, the interfaces to systems you are not changing, and access to the engineer who actually knows why the previous decisions were made.

Talk to an engineer about System Architecture

An engineer reviews every enquiry. We will come back with a technical view, not a brochure.

Everything you send is treated as confidential. We can sign an NDA before any technical detail is exchanged.

What happens next

1

An engineer reads it

Not a form-handler. Whoever owns the relevant discipline.

2

We come back with a technical view

Including if we think you do not need us.

3

If it looks like a fit, a short technical call

Then, if it is useful, a scoped workshop, feasibility study or evaluation.