Specialist assistance for an OCCT development team
Technical assistance helps a team work through a specific implementation question, integration problem or maintenance task. Examples include selecting a geometry operation, investigating visualization behavior, preparing a platform build or reviewing an application change.
This page describes the work that can be scoped. For support-unit quantities, published package terms and purchasing options, use the OCCT3D commercial support page.
Technical questions that lead to useful work
| Starting problem | Investigation focus | Useful result to agree on |
|---|---|---|
| An imported assembly displays without expected names or colors | Reader configuration, XDE document structure and presentation code | A working document-to-viewer sequence and checks for the required attributes |
| A distance or collision result changes with mesh settings | Representation, deflection and query tolerance | A documented choice of geometry representation and accuracy settings |
| A CAD operation fails only on some models | Reproducer, topology, tolerances and operation parameters | An explanation of the failure and a bounded correction or workaround scope |
| A wrapped application fails to load its native libraries | Runtime identifier, architecture and dependency packaging | A reproducible deployment configuration for the selected target |
These are examples of investigation scope, not fixed-price promises. A support request can begin with a technical finding; code changes and release work can be scoped once the cause is understood.
Algorithm development, visualization and porting
Technical support can extend beyond answering a helpdesk question. An engagement may develop an algorithm or class to an agreed specification, customize an existing operation, or produce an analysis report with implementation recommendations.
Examples include surface morphing and reconstruction, shape healing, custom graphical presentations, selection filters and handling large sets of displayed objects. Platform work can address another operating system, compiler or deployment environment. Performance work can combine measurement with a proposed implementation change.
The request is reviewed with the relevant specialists and translated into a technical proposal and effort estimate, including technical-support days where applicable. Implementation begins once the scope and estimate are agreed. The support package and the proposal define how this work is delivered.
Make an investigation actionable
Describe the task, current behavior and desired result. Identify the OCCT version, platform and relevant code or model. If the problem is intermittent or performance-related, include the conditions and measurements needed to reproduce it.
Agree on a bounded outcome such as an implementation recommendation, investigation finding or scoped correction. Implementation effort and delivery arrangements depend on the problem and the agreed engagement.
Select the appropriate service
For reproducible failures or slow operations, see bug corrections and improvements. For architectural decisions, see expert consulting. For a team’s learning needs, explore OCCT and SALOME training.
Describe your technical support requirement to establish the scope and the information needed to begin.