Q:

Is there a way for them to activate different modules of SACS Offshore and SACS Fatigue within the OpenWindPower Fixed Foundation? Please share if there is any workflow.

R:

OpenWindPower Fixed Foundation (formerly SACS Wind Turbine) is not a single module that contains other modules, but rather an integrated capability or workflow within the SACS package that uses various SACS modules, including SACS Offshore and SACS Fatigue modules, to perform the complete analysis of offshore wind turbine structures.

The activation of these specific modules occurs as part of the execution of the OpenWindPower workflow. The automated process within OpenWindPower generates the input files and runs the SACS modules required for the full analysis (dynamic, strength, fatigue).

It is important to note that the ability to use these modules within the OpenWindPower workflow is associated with the appropriate SACS licenses. OpenWindPower Fixed Foundation requires its specific license, and fatigue analysis (which is part of the workflow) requires the Fatigue Ultimate license.

In summary, the OpenWindPower Fixed Foundation is a workflow that orchestrates the use of various SACS modules, including those traditionally associated with Offshore SACS (such as Dynpac, Wave Response, Post, Combine) and Fatigue SACS, to carry out the analysis of offshore wind turbines. The “activation” of these modules is integrated and automated by the OpenWindPower process, rather than being a separate manual activation within a single OpenWindPower interface.

The workflow involves activating the OpenWindPower Fixed Foundation license through the Bentley Licensing Tool. This single activation unlocks the various SACS Offshore and SACS Fatigue modules that are part of this comprehensive package within the SACS software. You don't perform separate activations for individual modules within it.

The activation of different modules within the OpenWindPower Fixed Foundation (OWP-FF) workflow in SACS is inherently tied to the execution of the workflow itself, as it orchestrates the use of necessary modules sequentially. Therefore, there isn't a separate, manual "activation" of individual SACS Offshore and SACS Fatigue modules within OWP-FF that you can control to avoid triggering a Term License (TL) invoice.

The triggering of a TL invoice is governed by Bentley's licensing system based on usage. If the OWP-FF workflow utilizes modules that your current license doesn't cover, or if the usage exceeds the terms of your license, it can lead to a TL invoice.

Preventing TL invoices when using OWP-FF involves a combination of understanding your license entitlements, actively managing software usage, implementing internal policies, and maintaining good communication with Bentley Systems. Since OWP-FF's module activation is automated, direct control over individual module activation to avoid TL charges isn't feasible within the workflow itself. The focus should be on managing the overall usage of the SACS environment and ensuring your licenses adequately cover the required functionalities.