Software for creating safe hardware

Catch it in test.
Not in production.

Your requirements become standard tests every supplier runs. You see real results in real time, not at launch.

The later you find it, the more it costs.

Most programs only see the real part at launch, when a fix means line stops, scrap, warranty and recalls.

$0COST TO FIX DESIGNBENCH TESTLAUNCH & FIELD $ $$$ Fusaware finds it here $$$$$$+
Illustrative cost to fix one issue, by when it is found.

Today you discover the issues at launch.
With Fusaware, catch them in real time.

Today
No visibility into supplier testing PDF PDF PDF PDF First real look: launch
With Fusaware
Month 012243648

Messy evidence in. Standard proof out.

Report_v3_FINAL.pdf
test_data (2).xlsx
Lab notebook p.47ran it twice, 2nd time ok??
IMG_2041.jpg
RE: RE: FW: results?
fusaware
One procedure
every supplier
REQ-114 · Part 1
Turn-on time
PASS
REQ-207 · Part 4
Overcurrent shutdown
FAIL
REQ-122 · Part 2
Thermal derating
PASS
REQ-318 · Part 6
Supply voltage range
PASS

Engineers run the test. Everyone sees the data.

Part 3 · Rotor thrust sweep · Run 0412
REQ-122 · Rotor thrust sweepRECORDING
g RMS7.82
Peak21.4 g
Temp23.6 °C
Samples0
PASSREQ-118 Resonance search
PASSREQ-120 Sine sweep, X axis
LIVEREQ-122 Rotor thrust sweep

Running on test benches in 12 countries. And growing.

12Countries
6Continents
24/7Live results
PASSREQ-114 Turn-on timejust now
PASSREQ-301 Supply voltage range2 s ago
FAILREQ-207 Overcurrent shutdown6 s ago
Drag to spin
01DEFINE02RUN03CAPTURE04ADJUST Define REPEAT UNTIL IT PASSES

Iterate in testing, not just in design.

01
Define
02
Run
03
Capture
04
Adjust
For the program ownerSee every part against every requirement, live.
For suppliersA clear definition of done. Keep your design.

Every step has software. Except one.

DesignSchematics, CAD, PLM, simulationServed
Bench testingLab notebooks, Word docs, spreadsheetsFusaware
Automated testHardware in the loop, validation rigsServed
ManufacturingEnd of line testServed

Same problem. Every industry that builds hardware.

Automotive · Software-defined vehicles

Software-defined vehicles still run on hardware.

Every module comes from a different supplier. Each one needs proof before launch.

Live bench data00:00:00
  • 1LightingTurn-on time42 msPASS
  • 2Door modulesAnti-pinch force92 NPASS
  • 3Seat controllersMotor stall current7.8 APASS
  • 4WipersPark position0.4 °PASS
1LightingTurn-on time
2Door modulesAnti-pinch force
3Seat controllersMotor stall current
4WipersPark position

To ship value in software, control moves to the center.

Today · a brain in every part

SDV · one brain the OEM owns

CENTRAL CONTROLLER
SWSWSWSWSWSW

Simple edge hardware: actuators and sensors

Some faults can't wait for software. The hardware has to be right.

100 µs
Time to clear a hard fault
DEADLINE
Central software50 to 500 ms · miss
Local task5 to 10 ms · miss
Hardware path~40 µs · go

You can't ship hardware over the air. Get the requirement wrong and the fix is a recall, not an update.

From buying components to sourcing requirements.

Hardware-delivered valuevalue frozen in the part
Software-delivered valuefeatures over the air
Component sourcingspec, bid, award
Requirement sourcingsell the requirement, not the part
Component engineeringparts tested out of context
System engineeringtest the subsystem
Iterate in designone vehicle at a time
Iterate in testscales to many vehicles
the hardware fault forces the turn

For OEMs

Stop buying components. Start defining systems.

For suppliers

Don't just sell the part. Sell the requirement.

Presented at the DVN US Lighting Workshop: “The Shifting OEM-Supplier Interface: Rebirth of Systems Engineering.”

Make the hardware the easy part.

Tell us what you're building. We'll show you where Fusaware fits.

Or email sales@fusaware.com

AddressNewlab, 2050 15th St
Detroit, MI 48216

Photos and video: NASA and Unsplash contributors