Platform

One thread from requirement to evidence.

A system-level research platform for aerospace and automotive. It orchestrates the solvers you already own, keeps the trace between requirement and result, and generates the certification evidence from that record.

Change impact · one requirement
REQ-2110 → 4 load cases
→ 2 results invalidated
→ 1 test to repeat
→ 3 evidence items reopened
→ 1 compliance row re-generated
The traversal is the product. Everything else is plumbing.
6 OBJECT TYPES4 EDGE TYPES1 TRACE
4SOLVER FAMILIES
7STANDARDS COVERED
2DEPLOYMENT MODES
01

Orchestration — your solvers, one study record

Nastran, Abaqus, ANSYS, LS-DYNA and Simulink stay where they are. The platform prepares the inputs, dispatches the runs, and keeps every case with its version, its solver build and its checksum — on a laptop, a cluster or a cloud node.

BDF / INP / APDLOP2 / ODB / D3PLOTJob schedulingParameter sweeps
02

Traceability — requirement to result, one graph

Requirements, architecture elements, load cases, results, tests and evidence records are nodes with typed edges. A design change is a traversal: the platform lists the cases to re-run, the tests to repeat and the evidence that has just become invalid.

SysML / ReqIFChange impactBaselinesTest linkage
03

Evidence — certification documents, generated

Compliance matrices, verification evidence and work products are produced from the same graph, with each item pointing at the clause it answers. DO-178C objectives, ARP4754B process items, ISO 26262 work products and ASPICE evidence come out of the record, not out of a template exercise.

DO-178C / DO-254ARP4754B / ARP4761AISO 26262 / 21448Automotive SPICER155 / R156

What the platform does not do

Boundaries

It does not model geometry, and it does not replace your PLM. It does not decide whether a clause is satisfied — a named engineer signs that. It does not run physical tests. It connects and it records; the judgement stays with your team.

Why the boundary matters

A tool that claims to certify would have to be qualified itself. Keeping the platform out of the judgement is what lets it sit beside your existing tool chain instead of replacing it.

Deployment

On-premise

Runs inside your network, on your hardware, behind your identity provider. Required where controlled technical data cannot leave the site.

Private cloud

Runs in your own cloud account, in your region, with the same build and the same audit record. Scales a sweep without moving the data.

Design partners,
2027.

The platform is being built with a small number of aerospace and automotive teams. A design partner brings one live programme and one requirement set; we bring the trace, the evidence generation and the engineers who build it.