01

Who gets to keep the project record?

Teams need their records long after a project closes.

An engineer works at a desk with folders from three projects.

02

A copy of a drawing reaches a second file tray while its approval slip stays behind.

The handoff is where context gets lost

The receiving team needs to know which version it can use.

03

Each organization keeps control of its data

The project agrees who can issue, accept, and keep each release.

Separate archives hold the engineer’s working files and the owner’s retained release.

04

Connect the systems teams already use

Use OCI as the common way to exchange issued versions.

  1. Existing CDE

    Review and issue

  2. OCI exchange

    Exact version and approval record

  3. Owner’s systems

    Retain the release and use the data

05

Prove it on one model

Show that the project can control what gets issued and recover an earlier release.

  1. Draft

    The author submits the model.

  2. First release

    The designated people authorize and accept it.

  3. Next revision

    The owner can still verify the first approval.

Block unauthorized releases in the CDE and registry API.

06

Bring one real handoff

Two organizations, one model, and the project’s approval rules.

One person hands an issued model folder and its approval slip to another.

Presenting this deck

← → or Page Up / Down
Previous or next slide
Space / Shift + Space
Next or previous slide
Home / End
First or last slide
N
Toggle speaker notes
F
Toggle fullscreen