On this page
The announcement described a proposed technical connection
In June 2022, Siemens and U.S.-based NVIDIA announced a first step to connect their Xcelerator and Omniverse platforms. They described combining industrial models and software with simulation and computing capabilities.
That is a historical partnership announcement with expected benefits. It does not prove that a particular customer’s systems, data or permissions were ready, or disclose how the companies would allocate every support obligation.
Describe the customer’s job in ordinary language
A digital twin is a computer representation of an asset or process. For a buyer, the useful question is what decision that representation can support and what evidence shows it is suitable. A convincing visual display does not settle the quality or completeness of the input.
Use this ELN acceptance sheet for your own proposed integration. It is not a technical specification for either platform or a claim about their current functions.
| Part of the workflow | Question before a customer promise | Evidence to request |
|---|---|---|
| Input | Which data, version, format and permissions are needed? | A supported input example and the limits of what it represents |
| Connection | Who converts, validates and transfers the information? | A demonstrated end-to-end path, including errors and changed inputs |
| Output | What must the customer be able to decide or do? | An agreed output and acceptance question, not only a presentation |
| Ongoing support | Who investigates a fault spanning both products? | A named lead, escalation route and proposed change responsibilities |
A demonstration may leave most of the delivery work unanswered
Fictional example: one supplier can show a model on prepared data, but the customer’s actual data still needs conversion and validation. Calling the service integrated would hide that work unless the scope, cost and responsible team are explicit.
Ask for the smallest demonstration that includes the real handoffs and a realistic exception. Keep missing evidence visible. There is no need to manufacture a success score when a necessary input or decision is still undefined.
Approve the evidence needed for the first customer
Request a shared statement of scope from the proposed partners: inputs, output, responsibilities, limits, cost and who can change the arrangement. Price the work that remains with your own team as well as the purchased technology.
Use Partner evidence to record what has actually been demonstrated and what is only asserted or planned. A named partnership is useful context; your customer promise still needs its own evidence.
Scope
- Company-reported historical facts are attributed. The public record does not establish private contract terms, U.S. net profit or a result another business can expect.
- ELN’s tables and decision exercises are original planning suggestions. Actual product, people, contract and operating requirements need their own checks.
Next step
In Partner evidence, record the demonstrated workflow, input limits, support lead and unresolved integration tasks before making the first customer commitment.
Sources & review notes
Siemens AG
Passage, dates and research notes
company-announcement · 29June2022release: proposed first connection of Xcelerator and Omniverse and described complementary roles
Read complete partnership announcement. Proposed integration, customer benefits, product capabilities and performance expectations are not treated as current verified outcomes, a ready customer deployment or disclosed private support terms.
Bookmark this guide or mark it as read.
Progress privacy
Saving is off by default. Without it, progress lasts only on this page. If you turn it on, this browser profile stores public content IDs and the progress you record. Anyone sharing the profile could see them. No plan inputs or contact details are included. Reset or export in learning settings.
This is a reading aid, not evidence of disclosure delivery, expertise or legal approval.