It is possible to generate a lot of data in CATIA. CATIA is much more capable of handling large amounts of 3D and metadata when compared to ENOVIA Web Client.

I am looking at 2 possibilities to improve performance for the Web Client user.

1. Tuning the sever to be more efficient.

2. Apply best practices in the definition of the data created in CATIA.

--------------------------------------------------------------------------------------------

Current practices:

- 100’s of 3dshapes as Skeletons.

There are many cases where no geometry is found in a skeleton at this level

- 100’s of KES objects through out the product structure.

For either case it is possible to avoid this practice.

Q1: if these objects can be eliminated will this improve the performance for ENOVIA web client users?

Q2: where is it best to spend time and resources?  server performance or modelling Best Practices?

Web Client users current experience is very poor.  They see the following messages frequently.