WEBVTT

1
00:00:00.500 --> 00:00:04.925
Theseus found his way out of the labyrinth because Ariadne's thread lay at
every junction.

2
00:00:05.025 --> 00:00:13.284
Modern digital life needs that thread: product data lives in CAD, PLM, ERP,
quality and service systems, and loses its way between them.

3
00:00:14.534 --> 00:00:17.722
A file arrives: converted, delivered, and quietly changed.

4
00:00:17.822 --> 00:00:19.255
Attributes drop out.

5
00:00:19.355 --> 00:00:20.776
Relationships break.

6
00:00:20.876 --> 00:00:22.192
A tolerance shifts.

7
00:00:22.292 --> 00:00:24.195
The next decision takes the wrong turn.

8
00:00:25.445 --> 00:00:29.198
Every organisation has its own labyrinth and its own conversion risks.

9
00:00:29.298 --> 00:00:32.135
Secure delivery gets information across the boundary.

10
00:00:32.235 --> 00:00:34.458
Teams still need to know how it belongs together.

11
00:00:35.708 --> 00:00:42.191
The thread is the meaning: requirements, functions, geometry and verification,
connected through shared engineering concepts.

12
00:00:42.291 --> 00:00:46.141
CASCaRA builds on existing standards; every partner keeps its own models.

13
00:00:47.391 --> 00:00:56.615
A semantic layer gives the thread a common language: ontologies define
meaning, RDF states relationships, a knowledge graph connects requirement,
component and test.

14
00:00:56.715 --> 00:01:04.253
It does not replace PLM; it makes product data connectable and AI-ready, for
impact analysis, traceability and compliance checks.

15
00:01:05.503 --> 00:01:12.830
INOMIC ProductMesh makes that context workable: versioned Digital Data
Packages with files, entities, relationships and decisions.

16
00:01:12.930 --> 00:01:15.815
Inspect the model, follow its connections, keep the reasoning.

17
00:01:17.065 --> 00:01:27.218
ProductMesh speaks your formats: seventeen import formats, from STEP AP242 and
ReqIF to SysML and JSON-LD, eight export formats, plus ontology transfer.

18
00:01:27.318 --> 00:01:30.899
Onshape, SAP IPD and S/4HANA feed the package.

19
00:01:30.999 --> 00:01:37.312
Governed handovers reach S/4HANA, IPD, SAP Build Process Automation and the
public API.

20
00:01:38.562 --> 00:01:45.024
A future vision: selected DDP content, streamed on demand with its
relationships and agreed version context.

21
00:01:45.124 --> 00:01:47.779
Not another copy, but the context a partner needs.

22
00:01:49.029 --> 00:01:53.049
Close the loop: verification and feedback return to the original requirement.

23
00:01:53.149 --> 00:01:55.167
Review, agree, create the next version.

24
00:01:55.267 --> 00:01:57.836
From idea to service, the thread stays in your hand.

25
00:01:57.936 --> 00:01:59.397
INOMIC ProductMesh.

26
00:01:59.497 --> 00:02:01.484
Keep engineering context connected.