SAP Visual Enterprise is sunset. Your VDS library doesn't have to be.

The asset nobody wants to talk about

You spent years building it. Hundreds of engineer-hours went into those VDS files. Assembly sequences, part callouts, role-specific steps, all of it carefully authored to reflect how your products actually get built.

Then SAP announced the sunset. And now that library, which lives at the heart of how your floor operates, is frozen.

No new authoring. No supported migration path. Just a slowly drifting set of instructions that no longer quite matches the BOM, and a growing gap between what engineering designed and what operators are actually doing.

The re-authoring trap

The advice you'll hear most often is to start over. Pick a new work instruction tool, export what you can, and rebuild from scratch.

For a mid-sized VDS library, that's not a project. It's a programme. We're talking hundreds of engineer-hours at minimum, a long runway before anything reaches the floor, and a near-certain outcome where the new instructions are already slightly out of date by the time they're published.

Most teams don't have that time. And honestly, the underlying problem isn't the authoring tool. It's that the content became disconnected from the product data it was supposed to reflect.

There's a different starting point

RealFusion, the flagship product from Virtualspace, takes a different approach. Instead of asking you to re-author, it parses your existing VDS and VZXML files directly. The full assembly hierarchy, transforms, and metadata land on RealFusion's connected data thread in minutes.

From there, your work instruction authors publish role-aware instructions over the imported scenes. Not a static export, a living document that stays connected to your engineering BOM, your manufacturing BOM, and your order BOM.

When a BOM changes upstream, the instruction knows. When a specific order calls for a variant configuration, the operator sees the instruction for that variant, not a generic approximation from six months ago.

What this looks like for your team

For Marcus, the manufacturing engineer who owns the work instruction library, it means his existing content isn't wasted. He's not starting from zero.

For Sophie, the SAP solutions architect, it means the integration story is real. RealFusion speaks the same data language SAP Visual Enterprise users already know and connects natively to ECC and S4.

For Omar, the operations manager, it means operators on the floor are working from instructions that reflect the actual product being built today, not the one that was designed 18 months ago.

The tagline we keep coming back to

We describe RealFusion with a simple line: Your SAP Visual Enterprise content, alive again.

That's not a marketing promise. It's a description of the technical outcome. Your VDS library, parsed without a VEG round-trip, reconnected to your product data, and delivered to every operator who needs it.

If your team is sitting on a frozen VDS library right now, wondering what comes next, that's exactly who we built this for.