Our organization has enthusiastically adopted the 3DEXPERIENCE Works portfolio and has recently expanded to incorporate 3DEXPERIENCE Industries Solutions, such as Requirements Manager. We're keen to implement a wide array of roles including XWB-OC, XWC-OC, XEN-OC, MFN-OC, and MGA-OC.
However, we face a significant challenge: the current named user license model is not optimal for our needs. We are interested in exploring options for shared, SolidNetwork, or concurrent licensing models that would allow for more flexible and cost-effective usage across our team. Naturally, we would need assurance that such a model could be implemented without compromising security.
While we understand that licenses can be removed after 30 days of assignment, we find this period to be excessively long for our needs. A shorter timeframe for license reassignment would greatly enhance our ability to manage our resources efficiently.
Furthermore, we are very interested in adopting additional solutions like SIMULIA and wiring tools. The only factor preventing us from integrating these valuable resources into our workflow is the current licensing costs.
Given these circumstances, we would like to know if Dassault Systèmes is considering or open to developing more user-friendly licensing policies. Such policies could potentially include:
- Shared or concurrent licensing options for cloud-based solutions
- More flexible pricing tiers for growing businesses
- Bundle deals that make it more affordable to adopt a wider range of Dassault Systèmes solutions
We greatly appreciate the high-quality solutions that Dassault Systèmes provides and are eager to expand our usage. However, the current licensing structure is becoming a significant barrier to our ability to fully leverage these tools.
We would be grateful for any insights into potential future licensing options or any recommendations you might have for organizations in our position.
While we recognize that setting up a network license for SOLIDWORKS and attaching a connector could be a potential workaround, we believe this approach may not be the most straightforward or officially recommended solution. We're looking for a more direct and sanctioned method to address our licensing needs.
