Model and equipment package
Present body, powertrain, range or capacity choices through package rules.
AUTOMOTIVE AND VEHICLE EQUIPMENT
Bring vehicle choices into one 3D experience
Manage model, package, wheel, paint, upholstery and accessory decisions with the real rules of the vehicle. We develop experiences for products ranging from passenger cars to commercial vehicle equipment.
Decisions a vehicle configurator can manage
The experience does more than change colour: it manages available equipment, visual components and commercial outputs for the chosen model and package.
Exterior
Compare paint, wheels, roof, lighting and exterior accessories on the vehicle.
Interior
Connect upholstery, trim, seat layouts, displays and comfort equipment to the cabin view.
Accessories and price
Manage compatible accessories, package differences and a quote summary based on the selection.
Example: compact electric city vehicle
The customer chooses the vehicle version, then compares wheels, paint, cabin and charging options available for that version.
| Customer choice | 3D response | Rule or output |
|---|---|---|
| Vehicle version | Body and equipment set | Limits subsequent options |
| Wheels and paint | Component and material change | Package and availability fit |
| Upholstery and trim | Cabin materials | Coordinated interior package |
| Charging and accessories | Additional components | Price and quote lines |
The visual and scenario illustrate Viscore’s approach to automotive applications; they do not represent a published customer project.
From product data to sales
We plan the scope around the vehicle family, option codes and source of pricing.
Product and option data
Model years, packages, component relationships and invalid combinations are defined.
3D and material preparation
Vehicle geometry is optimised for the web; paint, upholstery and trim surfaces are prepared.
Quote and system connection
Configuration code, price and enquiry data are passed to CRM, dealer or quote workflows.
About automotive configurators
Common questions when defining scope.
Does every vehicle model need a separate experience?
No. Shared components, materials and option structures can be reused in one data model, while rules manage differences between model families.
Can option codes and package dependencies be applied?
Yes. A choice can require, remove or reprice another option through product rules.
Can it connect to dealer or CRM systems?
Yes. Choices, vehicle codes, visual previews and customer data can be transferred according to the existing system’s API or data capabilities.
Can existing CAD files be used?
We review geometry, component separation and materials, then plan the optimisation and material work required for web delivery.
Let’s explore your vehicle family
Share your models, packages and option structure. We’ll define the right vehicle and choices for an initial release.