Manage Tekla PowerFab remote work

Presented here are the four main scenarios for setting up work from outside the office network, ranked in the order of effectiveness. These scenarios also apply to cloud installations.

It is assumed that you run Tekla PowerFab on a computer that is outside your office network or that the server installation is not on the network that the user will be on.

Scenario 1: Work with a terminal server connection

Companies that have deployed and configured a terminal server have an excellent way of working remotely with Tekla PowerFab. User's local computer connects to the terminal server and acts as a “thin client.”

Terminal servers allow for multiple remote desktop sessions for each user connected. Running the application on the same network as the server provides the optimal remote working experience.

Things to consider:

This can be a costly and labor-intensive setup.
Terminal servers or services are not hosted by Tekla PowerFab.
The support for setting up and maintaining the terminal servers is outside the Tekla PowerFab scope.

Scenario 2: Connect using remote desktop software

Various remote desktop solutions are available. These may allow you to connect to and control a computer on the same network as the Tekla PowerFab server installation.

Things to consider:

Remote desktop solutions are not set up or supported by Tekla PowerFab.
Set up the remote desktop at the office. You may need to reconfigure firewalls and other security software to allow these connections.
The computer at the office must be running for you to connect to it, but many computers can be set up to start automatically when you try to connect.
Since the computer running Tekla PowerFab is on the same network as the Tekla PowerFab server installation, standard performance and file access is maintained.
This setup requires a reliable internet connection so that all features or integrations function properly. This may not be a workable solution for all users.

Scenario 3: Connect through a VPN and work as if you were at the office

If your company has a VPN set up for remote workers, this is an option for Tekla PowerFab as well.

To use VPN solutions with Tekla PowerFab, connect to the office network from the computer that runs Tekla PowerFab.

Things to consider:

VPN solutions are not set up or maintained by Tekla PowerFab.
The connection is set up and access permitted to the network usually through your IT.
Licensing likely requires a split VPN connection.
Latency in the remote connection is greater than in your office network. Therefore, most processes requiring calls to the server take longer to run.
This is the least recommended option due to performance levels.

Scenario 4: Install a local database - For use with the Estimating module only

If Tekla PowerFab is installed as a server installation, the database is local to the user’s machine. You need to restore a database from the user’s company server and restore it to their local machine. This ensures that all the current company settings and jobs are available.

The estimator can then perform estimates from the local machine, and when finished, use the Job Maintenance option to export the estimate. The export can then be imported into the main database.

Things to consider:

This workflow has the potential for inaccuracy if the settings in the databases do not match. If there are changes, they need to be made to both databases.
This scenario is also only practical for the Estimating module. Other Tekla PowerFab modules are dependent on links to other records that are not included in the export.