Product Configurator Reference Architecture#

In this workflow, industry consumers are connected to the developer pipeline using the Omniverse App Streaming API, which streams the Omniverse Viewport. This web-based Viewing Application enables interactive customer experiences across multiple delivery platforms. Using OpenUSD, developers work in a non-destructive workflow, warranting developers to work in their chosen third-party applications and author together using the Kit SDK before deployment. The end-user application uses photoreal 3D models and environments, enabling industry customers to design, create, and validate.

Workflow Diagram#

This diagram shows a configurator workflow and its key contributors such as Platform Developers, Full-Stack Developers and Pipeline Developers, Web Developers, and Look Developers.

Diagram of the roles in the sample workflow for a product configurator

Diagram of the roles in the sample workflow for a product configurator#

Tip

Want or build a configurator? Browse our end to end configurator guide to get started.

Exploring the Sample Workflow#

In this workflow, industry consumers are connected to the developer pipeline using the Omniverse App Streaming API, which streams the Omniverse Viewport. This web-based Viewing Application enables interactive customer experiences across multiple delivery platforms. Using OpenUSD, developers work in a non-destructive workflow, warranting developers to work in their chosen third-party applications and author together using the Kit SDK before deployment. The end-user application uses photoreal 3D models and environments, enabling industry customers to design, create, and validate.

Full Stack Developer#

Establishing the foundation for the rest of the pipeline, the Full Stack Developer starts the development process using Kit SDK to build their custom extensions and the kit-app-template repository to build the custom Kit Applications. The custom Kit Application enables the rest of the developer pipeline to design, iterate, and collaborate efficiently within their authoring application before packaging for the consumer-facing viewing application.

Platform Developer#

Data support and conversion can be efficiently managed using custom tools and connectors for any third-party application. The Platform Developer creates these custom tools that facilitate rapid iteration of data and assets in real-time, allowing the data to be imported customized according to your team’s specific needs and familiarity and ingested into your custom authoring application.

Look Development#

In all areas of the consumer-facing application, the look of the product matters. In the Look Development pipeline, the developer uses the high-quality hero assets imported from the asset database through the custom connector pipeline and builds the scene using various environments, cameras, lighting, and materials. Once the scene is set the Look Developer can then utilize the variant editing capabilities offered by the Kit Application to author and manage the variants of the scene.

Pipeline Support#

Before the scene can be packaged for deployment, the Pipeline Support developer, the Full-Stack developer, or a Technical Artist, iterates on the USD Variant options and works to optimize the scene. Scene optimization includes finalizing the render settings, creating the node-based messaging events to interact with the variants, improving load times by optimizing materials, merging meshes, and more. Once the Pipeline Support developer makes these final adjustments, the scene can be packaged for deployment into the consumer-facing Viewing application.

Deploy to a Cloud Service#

Deploying the consumer-facing viewing application into a cloud service, such as NVIDIA’s Graphic Delivery Network (GDN), gives your industry customer seamless global access to your 3D interactive configurator. GDN is a part of NVIDIA Omniverse Cloud, a service that further enables the full-stack cloud environment for enterprise developers. Once deployed to the cloud service, the title can be streamed into your client webpage using the Omniverse App Streaming API.

Web Developer#

To enhance the industry customer experience, a Web Developer integrates the Omniverse App Streaming API into the client webpage, enabling the client webpage to stream the Omniverse viewport from the cloud-service and connect webpage interactivity to the messaging events in the Kit Application, allowing the end-user to easily manipulate and change the scene.

Delivery Platforms#

Once your webpage is securely hosted and managed by your web server, it becomes easily accessible across various internet-connected platforms. Industry customers can interact, collaborate, and make decisions on their mobile devices, laptops, desktops, virtual machines, and on-premises kiosks.

End User Interactions#

With your content configurator now accessible to industry customers globally, any interactions they have with the viewport, variants, and scene are transmitted through Messaging Events. These events are then fed back into the pipeline, allowing the Viewing application to make live updates in real time.