<img height="1" width="1" style="display:none;" alt="" src="https://px.ads.linkedin.com/collect/?pid=5292226&amp;fmt=gif">
Skip to content

Design architectures with system dependencies in mind

Define and refine requirements, specify function realizations, and design and optimize components across variants.

Design architectures with system dependencies in mind

What can you achieve with this use case?

Up to
40%
faster function definition
Up to
30%
less time designing components
Up to
70%
faster validation prep

Trusted by

 

Create signals and functions

Define and create signals and functions to represent system behaviors and interactions, forming the foundation of your system architecture.

Design architectures with system dependencies in mind
Design architectures with system dependencies in mind

Assign functions to components

Map functions to specific components, ECUs, and their associated software modules, ensuring a clear definition of how the system is realized.

Design architectures with system dependencies in mind

Understand system relations

Visualize and establish precise relationships between signals, functions, components, and software modules, creating a fully traceable and structured system network.

Design architectures with system dependencies in mind

What types of data does SPREAD connect and analyze?

SPREAD integrates critical R&D data from multiple engineering systems and unstructured sources to provide complete traceability from issues to root cause. It connects and contextualizes:

Data Type Description Typical sources File Formats needed
Function Data Mappings between logical functions, software modules, and hardware components (including function hierarchy and realizations) Company specific system
.json .xml
Signal Data Sender-receiver mappings, communication buses, signal properties, variants Signal databases (e.g. DBC, ARXML)
.dbc .arxml
Vehicle Architecture Logical and physical structure: components, ECUs, buses, gateways, topologies Company specific system
.json .xml
Variant Configuration Mapping of feature/function/component presence across vehicle variants Company specific system
.json .xml
Issue Tickets Description, criticality, affected car, software release, affected function incl. linked parts & software, … Company specific system
Data definition As-is-state of signals, sender-/receiver-ECUs as well as the defined bits Company specific system
.arxml

How to

get started

1

Jointly scope
use cases

We bring practical expertise to understand your challenges and scope the right solutions  with you.

2

Deploy solutions
rapidly

Within weeks we deploy our platform, integrate the required product data and configure the defined solutions.

3

Rollout across
the company

We train users across teams, scale company-wide, and support you continuously on the way.