Review the technical decisions behind your CAD application
Open CASCADE consulting helps an engineering team assess how its application uses geometry, topology, exchange, visualization and document structures. A review can focus on a single operation or the boundaries between those systems.
Typical starting points include an architecture decision, unexpectedly slow processing, excessive memory use or uncertainty about an algorithm’s suitability. Use representative models and observed behavior to keep the investigation tied to the product.
Review the boundaries that affect model correctness
A CAD architecture review can follow one model from import through document storage, processing, meshing and display. At each step, identify who owns the data, how edits invalidate derived results, and where assembly instances and attributes are preserved.
For example, an application may process the same part several times because it treats assembly instances as independent geometry. Another may retain outdated tessellation after a shape changes. The review should connect an observed workload to the application’s data flow before proposing changes.
For a BRepGraph-based design, BRepGraph Advance offers modeling and relation-analysis capabilities to evaluate alongside the application’s ownership and update model. Traditional OCCT and graph-native operations should be selected according to the actual integration requirements.
Application design, ergonomics and solver integration
Consulting can cover open and extensible architectures, OCAF-based parametric engines, and the definition of application objects and operations. It can also address GUI ergonomics: how commands, selection and feedback form an intuitive, consistent workflow for the people using the application.
Other scopes include interoperability with simulation and finite-element solvers, integration of commercial components, and specialist design questions in CAM, coordinate measurement, and engineering pre- or post-processing.
Sessions can be arranged remotely or on site. An early project review can be combined with training so that the team can apply the findings; a milestone review can focus on a specific design or implementation decision. Delivery and preparation are agreed through the selected support engagement.
Prepare an architecture or performance review
- Describe the operation, expected behavior and business impact.
- Identify the OCCT release, compiler, platform and relevant dependencies.
- Provide the architecture or code involved and a reproducible workload where possible.
- Define the decision the review should enable: a design change, integration choice or implementation scope.
For performance work, establish the baseline, measurement method and acceptable result. Separate file reading, geometry processing, meshing and rendering when investigating where time or memory is used.
Turn findings into implementation work
Agree on the review output and priorities before work starts. Follow-on changes can be scoped through custom development or bug corrections and improvements.
For ongoing access to assistance, compare commercial support packages. Start an OCCT consulting enquiry with the decision or problem you need to resolve.