CM4D Peruse System Requirements

CM4D Peruse System Requirements

This topicdocument includes the hardware and software minimum requirements and recommendations for the basic configurations of CM4D Peruse. The specifications outlined are intended to be used as a generic starting point in the planning of your CM4D Peruse implementation.

Windows System Updates should be kept up to date to ensure the computer has any Root Certificate updates that might be required by digitally signed software.

CM4D Peruse Host Server

 

Hardware

CM4D Peruse Installation

HOOPS Communicator Server

Database

OS

RAM

HDD

 

Software

 

CM4D Peruse Client Systems

CM4D Peruse runs as a web application accessed via the network/internet, so clients only need a web browser to access the software installed on a network server or host machine via the internet. 3D models are rendered in the client systems' web browser by the HOOPS Web Viewer component in CM4D Peruse. 

 

The HOOPS Web Viewer works on the following browsers:

Platform	Browser
Windows	Chrome, Firefox, MS Edge
Linux	Chrome, Firefox
Mac	Chrome, Firefox, Safari 8
Android 5+	Chrome
iOS 11+	Chrome, Safari

 

HOOPS 3D Engine

HOOPS Communicator is a third-party graphics engine with requirements outside of ATS. See here for information on the HOOPS Communicator supported platforms and hardware recommendations.

 

Supported 3D File Formats

Which list of supported formats do we use? There are different lists for Communicator, Exchange and Web Viewer - which license(s) does ATS have?

For a list of supported CAD file formats, refer to the CM4D documentation HERE.

https://docs.techsoft3d.com/communicator/latest/build/overview/supported-formats.html

 

Client-Side 3D Rendering and Performance

3D CAD models associated to a Routine in CM4D are converted to a stream cache format. The model information is stored in the database and the model stream cache files are stored in a Model Directory on the HOOPS Communicator server. The models are then streamed from the HOOPS server to clients and rendered by the HOOPS Web Viewer on the client-side in CM4D Peruse. This requires the end client, the machine running CM4D Peruse in a web browser, to do the actual rendering the 3D model when it is loaded into the web viewer in CM4D Peruse.

Because the rendering of the image is done when the client loads the stream cache image from the database, the speed of the network or internet between the database and the client system directly impacts the loading performance for the end user.

Server-side rendering is not available; it would require a very expensive hardware for a server to support this rendering method.