For innovation, R&T and concept design leads

The discipline: deciding between futures, defensibly

The practice in this role is real and mostly manual: horizon scanning, stage gates, portfolio reviews, technology roadmapping, the concept studies that precede any programme commitment. What makes it hard is not the frameworks; it is that the load-bearing questions are cross-boundary. Which pathway to back depends on infrastructure that is not yours, regulators who move on their own clock, supply chains and shared resources that every other sector is also claiming. That is systems-of-systems territory, whether or not anyone calls it that, and doing it by intuition and committee, then feeding the result into a rigorous engineering process, builds a precise structure on an unexamined foundation.

There is a boundary worth drawing precisely, because it is where you operate. MBSE governs the system you control; systems-of-systems thinking governs the questions where success depends on systems nobody in the programme controls. Concept design is the high ground between them: the stage where the ecosystem decides what the requirements should be, before the toolchain takes over.

What SOSX does about it

The plain question is: which pathway do we back — and will the reasoning survive review, not just the recommendation? SOSX operationalises exactly the systemic work the standards name and leave unspecified. The ecosystem becomes a typed, parameterised network, actors, infrastructure, regulators, resource pools, with every connection saying what it carries. Candidate pathways are worked as comparative and feasibility studies from the same model, on the same scope, so the options are structurally comparable rather than separate decks. Every claim cites a catalogued source; every value carries its units, provenance and confidence; and a committed decision carries its rationale chain (the analyses, parameters, assumptions and sources behind it) and is re-tested when those parameters move materially. The reasoning survives review, not just the recommendation.

And this is where SOSX has its deepest exposure: its live MBSE trials with a large global aerospace manufacturer sit with the organisation's innovation and research-and-technology function, the people whose job is innovation management, in the context of long-horizon technology-pathway decisions. Live enterprise trials, not production deployments, and we say that plainly.

It lands in your toolchain, and your evidence base

Concept-stage evidence is only useful if it flows into the engineering process rather than standing beside it: SOSX exports into nine MBSE tools and formats, so derived requirement values and pathway evidence arrive where your systems engineers already work. And because every AI interaction is audit-logged and the stages that decide the model pass a human approval gate, the practice leaves evidence as a by-product of doing the work: the honest answer to the known failure mode of management standards, the certificate maintained while the practice decays. To be plain in the way we prefer: SOSX aligns with and produces evidence for the frameworks on our compliance page; nobody certifies you but your assessor.

The research behind the design

This page's argument is not only marketing. A paper on the SOSX design has been submitted to a peer-reviewed journal (submission is not acceptance, and we claim nothing more until review has run its course) and the design it reports was built under the same discipline it describes: verified citations, documented searches, adversarial review. The book series behind the platform teaches the whole practice in the open, starting with The Concept Design Advantage, written for exactly this role.