HIVECH

The technical route and rendering principle of IRIS 3D and IRIS 2D are different. IRIS 2D is based on the superposition rendering of pre-rendered layers, while IRIS 3D is based on real-time rendering of 3D engines. IRIS 2D has faster rendering speed and can support clearer and sharper image rendering, while IRIS 3D has slower rendering speed but can support more complex scenes and more realistic rendering effects, and lower cost.

Of course. IRIS 2D engine has been providing high-speed and stable service for our customers for many years, and IRIS 2D engine provides a very friendly image customization tool. You can use this tool to customize the vehicle images you need, without having to understand the meaning of system parameters.

The upgrade from IRIS 2D to IRIS 3D is downward compatible, only requiring backend deployment upgrade to complete seamless migration.

Generally, the IRIS-based solution includes the following items, billed separately. Specific pricing information please contact sales representatives.

• IRIS 3D software usage authorization
• Vehicle 3D modeling
• Deployment and integration fees
• Operation and maintenance services

Non-IRIS solution pricing is quoted based on the implementation plan and scope, please contact sales representatives

Since customers own vehicle metadata, these metadata and CAD model files must be provided to create a 3D model. Usually, only the following materials are needed, and we can start creating models:

• Vehicle metadata, such as vehicle name and unique code
• Configuration items set with classification and unique code
• CAD/3DS Max/Unity/Unreal model files for 3D modeling
• Configuration item model files consistent with the above materials
• Configuration rules, such as configuration conflicts and associations
• Type of IRIS product, 2D or 3D

Yes. Both enterprise-owned servers and cloud deployment are supported, but cloud deployment is faster and more economical.

We provide standardized web components. On this basis, customers can customize styles and layouts according to the CI requirements of the enterprise. Of course, if the existing components cannot meet your business needs, you can also develop them yourself, and we will provide necessary technical support to integrate the IRIS system.

IRIS usually completes the rendering of 1000+ layers in less than 500 milliseconds, so we dare to call it real-time rendering.

The system performance will not slow down even when there are many concurrent access requests, because IRIS has a feature called dynamic caching. Once the image rendering is completed, it will be cached by CDN.

Customers need to bear the cost of CDN, because we believe this is the fairest for customers. Customers need to prepare a domain name with a parsing permission (usually a subdomain of the official website is sufficient) so that the domain name can point to the IRIS service domain name. If you have any questions about configuration, we are willing to provide technical support at any time.

For general enterprise websites, we recommend using Magnolia CMS, which is based on the Java technology stack, cost-effective, and uses a WYSIWYG editor to quickly create and maintain websites.

For large multinational enterprise websites, we recommend using Adobe Experience Manager, which has a good digital marketing ecosystem and can seamlessly integrate with Adobe's marketing tools, providing powerful functionality.

For large e-commerce platforms, we recommend using Magento, which has a good e-commerce ecosystem and also joins the Adobe ecosystem, allowing seamless integration with Adobe's marketing tools.

For small businesses, we recommend using WordPress, which is open source and free, easy to use, and can quickly create and maintain websites.