Launch faster.Break nothing.Know exactly why.

The engineering platform for launching, maintaining, and evolving complex products fast. AI-native. Built for every team, tool, and agent across the lifecycle.

Get started

Engineering Ontology

5 sources feeding 1 unified ontology — consumed by 5 apps and 4 agents

48,200

Entities

142,800

Connections

207

Entity types

98.2%

Data quality

Mech8.2k

Elec6.4k

SW4.8k

Sig12.4k

Ontology48.2k

Req9.2k

Aftmk7.2k

5 enterprise sources → 1 unified ontology → 5 apps + 4 agents

Live ActivityView all

Teamcenter sync — 340 entities ingested

2m ago

Agent Claude Code queried BMS architecture via MCP

18m ago

Agent DevOps Agent triggered re-sync after ontology update

35m ago

Engineered on SPREAD

FIG.02 — SPECIESSTATUS: NEWSPREAD / CATEGORYv. 2026.1

Category reset

A new species forproduct lifecycle management.

Traditional PLM scatters your engineering data across silos and your teams across disconnected tools. Data drifts out of sync, teams work from different versions of truth, and misalignment shows up as rework. SPREAD adds the intelligence layer: one source of data, aligned teams, and AI doing the reconciliation work in the background.

See how it works

STEP 01 — REQUIREMENTS MANAGER

Run AI at domain-expert level.

Every product starts with intent. SPREAD reads your requirements, checks them against years of your engineering data and prior projects, and flags the conflicts and gaps a senior engineer would have caught, before they reach design.

Explore Requirements Manager

BMS High-Voltage Battery System
Requirements Specification

Document ID: SPEC-BMS-HV-2026-003Revision: 2.1

Date: 2026-03-28Author: Dr. M. Weber

Department: EE ArchitectureStatus: Under Review

3 Electrical Requirements

3.1 General

The Battery Management System (BMS) shall provide comprehensive monitoring, control, and protection for the high-voltage battery system installed in E-Platform Gen3 vehicles. All electrical requirements defined in this section shall be validated against the reference architecture (PLT-EPG-003) and shall comply with applicable EMC standards per LV 124 and CISPR 25.

3.2 Cell Monitoring

3.2.1 The BMS shall monitor individual cell voltages with an accuracy of ±5mV across the full operating temperature range (−40°C to +65°C). Measurement sampling rate shall be ≥10Hz during active vehicle states. Reference: ISO 18300.

3.2.2 Active cell balancing shall maintain voltage delta below 20mV across all series-connected cells during both charge and discharge cycles. The balancing algorithm shall achieve equalization within 4 hours under standard conditions as defined in test procedure TP-BMS-042.

3.3 Safety Requirements

3.3.1 The system shall disconnect the HV battery within 50ms upon detecting a critical isolation fault (resistance < 100Ω/V). This requirement is classified ASIL-C per ISO 26262-3.

3.3.2 All safety-relevant BMS functions shall comply with ISO 26262 ASIL-C requirements. Redundant monitoring paths shall be provided for all critical measurements including cell voltage, pack current, and isolation resistance.

3.4 Communication Interface

3.4.1 Battery state of charge (SoC), state of health (SoH), and fault status shall be transmitted via CAN bus (FlexRay backup) with a maximum cycle time of 100ms during driving states.

Table 3-1: BMS CAN Signal Matrix

Parameter	CAN Signal	Cycle	Resolution
Cell Voltage	BMS_CellV	100ms	1mV
Pack Current	BMS_PackI	50ms	0.1A
Temperature	BMS_Temp	500ms	0.5°C
State of Charge	BMS_SoC	100ms	0.1%

3.5 Environmental Requirements

3.5.1 The battery pack assembly shall maintain full operational capability within an ambient temperature range of −40°C to +65°C without degradation in performance or safety characteristics…

Requirements12 extracted

8 matched

3 new

1 review

Classification Status Confidence

1REQ-BMS-001Performance96%

The BMS shall monitor individual cell voltages with an accuracy of ±5mV across the full operating temperature range.

BMS ECUReviewed

2REQ-BMS-002Functional91%

Active cell balancing shall maintain voltage delta below 20mV across all series-connected cells during both charge and discharge cycles. The balancing algorithm shall achieve equalization within 4 hours under standard conditions.

Cell ModulesNew

AI Analysis

Matched to:Cell ModulesBMS-CM-001

Confidence:91%

3 similar requirements found across 2 past projects (MEB-2024, PPE-2025). Previous realization used passive balancing — this spec requires active.

Source: Page 3, Section 3.2.2

View in Product Explorer

3REQ-BMS-003Safety94%

The system shall disconnect the HV battery within 50ms upon detecting a critical isolation fault (resistance < 100Ω/V).

HV ControllerReviewed

4REQ-BMS-004Safety93%

All safety-relevant BMS functions shall comply with ISO 26262 ASIL-C requirements. Redundant monitoring paths shall be provided.

No match yetReview

5REQ-BMS-005Interface89%

Battery SoC, SoH, and fault status shall be transmitted via CAN bus with a maximum cycle time of 100ms during driving states.

BMS ECUReviewed

6REQ-BMS-006Environmental97%

The battery pack assembly shall maintain full operational capability within −40°C to +65°C ambient temperature range.

Battery PackNew

FIG.03STATUS: LIVESPREAD / REQUIREMENTSv. 2026.1

STEP 02 — PRODUCT EXPLORER

Understand the product inside out. Decide faster.

Once it’s built, the product lives across a dozen systems nobody can hold in their head. Ask Explorer a question in plain language; its AI traces the answer across parts, requirements, tests, and suppliers in seconds.

Explore Product Explorer

Systems

Components

Functions

Signal

100%

FIG.04STATUS: LIVESPREAD / EXPLORERv. 2026.1

STEP 03 — ERROR INSPECTOR

Try the extraordinary, knowing you will surface and solve issues fast and forever.

Every product line runs into problems: in pilot, in series, in the field. Whether it’s a failed pilot test, a defect flagged on the line, or a warranty ticket from the field, Error Inspector’s AI traces it back to the components or requirements that caused it in minutes, not weeks of war rooms.

Explore Error Inspector

340 ticketsTraction Power Loss·Cluster detected 3 days ago · Production weeks W48–W03 · 12,400 vehicles

87% confidence

Step 1 · Symptom

340 tickets clustered semantically

Step 2 · Function

94% map to Torque Control

Step 3 · Signal

PowerAvail drops 40% at >32°C

Step 4 · Root Cause

BMS ECU FW v2.14.1 threshold

Symptom

Traced path

Ruled out

100%

Selected node

BMS ECU

Firmware v2.14.1 · Battery Supplier B

Root Cause

Signal Data

History

AI Root Cause Analysis

Thermal derating threshold in BMS firmware v2.14.1 is set to 32°C (should be 40°C). BMS under-reports available power to the inverter under normal operating temperatures, causing torque limitation experienced as intermittent power loss.

Confidence:87%

Impact Radius

12,400

Vehicles affected

€4.2M

Warranty exposure

W48–W03

Production weeks

OTA

Recommended fix

Supporting Evidence

%94% of tickets correlate with Supplier B batteries and FW v2.14.1

SPowerAvail_CAN drops from 180kW to 110kW when cell temp exceeds 32°C

HSimilar derating defect on MEB platform (2024) resolved via OTA in 3 days

✓Supplier A batteries (6% of fleet) show no anomaly — confirms supplier-specific issue

Paths Ruled Out

×Power Limiting — signal within normal range

×Cell Balancing — delta within 15mV tolerance

×ThermalState — within operating range

×DerateFactor — no anomaly detected

×Inverter ECU — no signal anomaly detected

×Battery Pack HW — cell health within spec

FIG.05STATUS: LIVESPREAD / INSPECTORv. 2026.1

FIG.06 — FOUNDATIONSTATUS: CONNECTEDSPREAD / ONTOLOGYv. 2026.1

Under the hood

One ontology.Seven years.Fits your world.

Connecting tools is easy. Making them agree is the hard part. SPREAD’s engineering ontology has been refined for seven years, spanning every function that touches your product: requirements in engineering, pilot and series production, tickets in the field. Plug in Teamcenter, Windchill, 3DEXPERIENCE, SAP, and the answers finally agree.

7YRS

of ontology work

40+SYS

connectors ready

0MIG

migration required

Talk to an engineer

Case Studies

Automotive OEM / CS.01

Mitigating €2B SOP risk at a leading Automotive OEM.

Defense OEM / CS.02

Saving >€600k yearly with one MBSE model at a Defense OEM.

Automotive OEM / CS.03

Boosting production rework efficiency at an Automotive OEM.

Testimonials

“Even in a fully regulated, on-premise environment, we’ve gained control over complex engineering data, detecting errors earlier and accelerating development with confidence.”

Dr. Ulrich NudingEngineering Director Germany

01/06

FIG.04 — FAQSTATUS: OPENSPREAD / SUPPORTv. 2026.1

FAQ

Common questions.

Integrations, setup, pricing, and security, answered.

Still have questions?

Talk to an engineer

What systems does SPREAD integrate with?

SPREAD connects to PLM, CAD, ERP, simulation, and test management systems out of the box — including Teamcenter, Windchill, 3DEXPERIENCE, SAP, and more. SPREAD maps your data in place without migration, so your teams keep working in the tools they already use.

How long does setup take?

Does SPREAD replace our existing tools?

How is SPREAD priced?

Is my data secure?

Get started

Launch faster.See how.

20-minute walkthrough. No slides, just your systems live.

Get started

Launch faster.Break nothing.Know exactly why.

A new species forproduct lifecycle management.

Stop guessing what breaks at launch.

Run AI at domain-expert level.

Understand the product inside out. Decide faster.

Try the extraordinary, knowing you will surface and solve issues fast and forever.

One ontology.Seven years.Fits your world.

What our customers achieve.

Mitigating €2B SOP risk at a leading Automotive OEM.

Saving >€600k yearly with one MBSE model at a Defense OEM.

Boosting production rework efficiency at an Automotive OEM.

Common questions.

Launch faster.See how.