Your EBOM Changes on Monday. Your MBOM Updates Itself.

No. During the pilot and in standard deployment, Virtualspace connects to SAP VE in read-only mode. Your production systems are never modified. Virtualspace reads your EBOM data, processes it in the Virtualspace environment, and outputs MBOM structures and work instructions as separate artefacts that your team reviews before approving for use.

Virtualspace imports your existing variant configuration rules from SAP VE and builds them into the digital twin model. During the pilot, your manufacturing engineers review and validate the rule capture, and can add edge cases through the Variant Rule Editor. Most standard variant configurations are captured accurately within the first two weeks of the pilot.

Yes — this is exactly what the pilot is designed to discover. Your team's institutional knowledge (what Rex calls "the 47-tab Excel") is captured through a structured exception mapping process in weeks 2-3 of the pilot. Virtualspace's digital twin learns your environment, not the other way around.

Nothing — they stay exactly as they are. Virtualspace generates new outputs alongside your existing records, allowing your team to compare and validate before any transition. Most customers run Virtualspace in parallel for 30 days before migrating new change workflows to the platform.

The Virtualspace pilot is designed for zero production disruption. A read-only SAP VE connection is established in days 1-3 (typically 4-8 hours of your IT team's time). The platform then runs in your environment with Virtualspace providing onboarding engineering support. Most customers are generating validated MBOM outputs by week 2.

Yes. We run all demos against real discrete manufacturing scenarios — variant-rich assemblies, multi-level BOM structures, and SAP VE integration examples. Book a 45-minute session and tell us your product type and primary planning pain point. We will demonstrate the most relevant capability for your environment.