
Open Download on the Production Assist website or go directly to the Download page. You do not need an account to download the desktop app. You can create an account afterward to sign in and work with online projects.
On the Download page, choose the installer for your operating system. The desktop app is available for Windows, macOS, and Linux. The same page also has downloads for integrations such as the Vectorworks plug-in.
For a tablet or smartphone, choose the appropriate store link in the Production Assist for Tablet / Smartphone card. App Store and Google Play open the relevant store in a new tab.

On Windows, you can choose between the installed and portable desktop apps.
On the Download page, select Desktop App and download the EXE file. It is saved automatically in the Downloads folder. Double-click it to start the installation. You can choose the installation folder during setup.
After installation, you can start Production Assist from the Windows Start menu. The program files are in the folder you chose during installation.
By default, the installed desktop app stores user data in %APPDATA%\ProductionAssist.
The portable desktop app is available only for Windows. It does not require installation and can be started, for example, from a USB drive or a custom program folder.
ProductionAssist-VERSION-portable.zip completely into a folder where you have write permission.ProductionAssist.exe in the extracted folder to start it. Keep the other files and the .productionassist-portable marker in this folder.On first launch, the ProductionAssist-data folder is created automatically next to ProductionAssist.exe. This keeps the user data of the installed and portable desktop apps separate. The portable folder structure includes, among other things:
ProductionAssist.exe
.productionassist-portable
resources/ other program files
ProductionAssist-data/
├── session/ session and browser data
├── logs/ log files
├── local-resources/ local resources
├── temp/ temporary files
├── mesh/ temporary geometry data
└── Resource/ cached resources
Important: Move or back up the entire extracted program folder together with
ProductionAssist-data. Without.productionassist-portablenext to the program file, Production Assist does not recognize this as a portable launch. If Production Assist cannot create folders or files in the data directory, the portable app will not start; it does not fall back to the normal AppData directory.
The following special conditions apply to the portable desktop app:
ProductionAssist-data folder.productionassist: URL protocol is not registered in Windows.ProductionAssist-data folder. See Configure the plug-in AppData directory.
Note: If macOS reports on first launch that ProductionAssist was downloaded from the internet, confirm the prompt by clicking Open.

Production Assist is provided for Linux as an AppImage file. Download it from the Download page. The app is tested on the current Ubuntu LTS release and on Manjaro. You can integrate the AppImage into your applications menu with AppImageLauncher or run it directly.
AppImageLauncher is an additional application. If you use it, you can integrate the downloaded Production Assist AppImage into the applications menu the first time you open it.
.deb package from the AppImageLauncher releases page and install it with the package manager. For Arch and Manjaro, find the current installation methods in the AppImageLauncher guide. The previously used Ubuntu PPA is no longer offered.If you do not want to use AppImageLauncher, make the downloaded AppImage file executable. To do this, right-click the file and, on Ubuntu, open Properties → Permissions. Enable Allow executing file as program, then double-click the AppImage file. It starts from its current location.

On KDE (Manjaro), find the option under Properties → Permissions → Executable.
To install the plug-in, you must also have the installed or portable desktop app and run it at least once. If you use the portable desktop app, you must also configure the plug-in's AppData directory.
There are two ways to install the plug-in: with the Production Assist app or manually. For a manual installation, you need to find the Vectorworks user folder for the desired version. The Production Assist app detects installed Vectorworks versions automatically.
If Production Assist reports Version conflict detected, the loaded plug-in version does not match the user interface version. Update the desktop app and reinstall the matching Vectorworks plug-in. The dialog shows the detected versions and paths.
Before installation, Production Assist checks whether Vectorworks is already running. While Vectorworks is open, you cannot select Vectorworks plug-ins. Quit Vectorworks and click Check again in the dialog so Production Assist can update the status.
Before installation, Production Assist checks whether Vectorworks is already running. While Vectorworks is open, you cannot select Vectorworks plug-ins. Quit Vectorworks and click Check again in the dialog so Production Assist can update the status.
When extracting files, Production Assist checks the package size information. Each file can be at most 256 MiB compressed and 512 MiB uncompressed. Each selected package folder can contain at most 2 GiB compressed and 2 GiB uncompressed in total. If an entry exceeds these limits or its size information does not match, installation is cancelled. Contact support about such a package.
The ZIP file contains only the plug-in for the selected Vectorworks version and the shared Production Assist files it needs. For manual installation, you need the Plug-ins folder for your Vectorworks version. If you want to use the folder in the program directory and do not know its location in Windows, search for Vectorworks in the Start menu, right-click the program entry, and use Open file location to open the path to the application.
The image shows an older package as an example. In the current archive, always choose the folder for the Vectorworks version you actually have installed.
Copy the ProductionAssistWeb folder and ProductionAssist.vlb and ProductionAssist.vwr from the folder for your Vectorworks version into its Plug-ins folder. For your user account, this folder is at %APPDATA%\Nemetschek\Vectorworks\<Year>\Plug-ins; replace <Year> with the version number. Alternatively, you can use the Plug-ins folder in the Vectorworks installation folder.
You can now start Vectorworks.
CAUTION: Apple adds a quarantine attribute to downloads from outside the App Store. Temporarily remove it before installing the plug-in. Open Terminal and enter
xattr -d com.apple.quarantine. Add a space, then drag the downloaded ZIP file into the Terminal window. Check that there is a space between the command and the file path, then press Enter.

Now double-click the ZIP file in your Downloads folder to extract it. In the extracted archive, open the folder for your Vectorworks version and copy ProductionAssist.vwlibrary.
The image shows the VW21 folder as an example. In the current archive, choose the folder for the Vectorworks version you have installed.
Go to your Vectorworks user folder at ~/Library/Application Support/Vectorworks. Select your Vectorworks version and place ProductionAssist.vwlibrary in the Plug-ins folder.
The image shows an older package as an example. In the current archive, always choose the folder for the Vectorworks version you actually have installed.
You can now start Vectorworks.
In addition to the Production Assist desktop app, you need the SketchUp extension. Install the extension separately from the SketchUp download package; it does not appear in the desktop app's plug-in installation dialog. The component library is downloaded separately and can then also be opened as a local collection.
ProductionAssist.rbz file in the folder for your SketchUp version. The folders and supported versions may vary between download packages, so check the compatibility information for the current package.The extension adds a Production Assist toolbar and palette to SketchUp. For more information about synchronization, components, and creating your first model, see the SketchUp extension guide.
First install the Production Assist desktop app and start it at least once. An internet connection is required to install through the app. Close AutoCAD or BricsCAD during installation.
APPLOAD, select ProductionAssist.arx in the ARXYY folder for your AutoCAD version, and load the module. Also add it to the Startup Suite. If the Ribbon tab is missing, you may also need to load the included productionassist.cuix.ProductionAssist.bundle. The loading and Ribbon procedure is not verified in this guide; do not apply the Windows steps unchanged.APPLOAD, select the appropriate BRX or MRX module in the BRXYY folder, and enable Autoload.Use manual installation if your AutoCAD version is missing from the dialog or you want to provide the plug-in yourself. First install the Production Assist desktop app. Close AutoCAD before extracting or replacing the plug-in files.
ARXYY folder for your installed AutoCAD major version. Check in the archive that your version and operating system are supported.ProductionAssist.arx together with all DLLs, libraries, and support files in the extracted folder structure. Do not move only the ARX file. Put the folder in a local location your user account can access; network drives and synchronized cloud folders can slow down or prevent loading.APPLOAD in the command line.ARXYY folder, select ProductionAssist.arx, and click Load. If AutoCAD asks for approval, allow the plug-in permanently. Add the folder to the trusted locations if needed.ProductionAssist.arx to the Startup Suite so AutoCAD loads the plug-in again the next time it starts.productionassist.cuix on Windows using the AutoCAD CUI command; instructions are in the AutoCAD and BricsCAD installation quick start.Then install the DWG library using Install Library on the Production Assist tab. The installation downloads the latest library for the app version and release channel in use; its build number does not have to match the app's build number. Production Assist checks the files. For more information about choosing a folder and replacing existing files, see the installation quick start.
These manual steps are documented for AutoCAD on Windows. For supported macOS versions, the package includes ProductionAssist.bundle; loading and Ribbon setup on macOS are not verified here. Do not use the Windows steps unchanged on macOS. For a manual installation, check yourself whether a new plug-in package is available, and replace the complete plug-in folder when updating.
The AutoCAD and BricsCAD versions currently offered in the dialog, as well as manual installation for both CAD applications, are described in the AutoCAD and BricsCAD installation quick start. For the portable desktop app, you must also configure the plug-in AppData directory.
The native Production Assist plug-ins for Vectorworks, AutoCAD, BricsCAD, and ZWCAD, as well as SDK integrations, store settings, login data, resources, and the production_assist_config.json file created by the desktop app in the following directory by default:
| Operating system | Default plug-in directory |
|---|---|
| Windows | %APPDATA%\productionassist |
| macOS | ~/Library/Application Support/productionassist |
On Windows and macOS, you can specify a different AppData directory for each of these plug-in modules. This is especially useful for the portable desktop app, separate work environments, or multiple independently configured plug-in installations. This configuration does not apply to the SketchUp and grandMA3 plug-ins.
Create a UTF-8-encoded JSON file named exactly productionassist-plugin.json next to the loaded plug-in module or plug-in bundle, depending on the plug-in type. The plug-in reads the file when it starts.
Typical locations are:
ProductionAssist.vlb, ProductionAssist.arx, libProductionAssistBRXYY.brx, or ProductionAssistZRX.zrx.libProductionAssistBRXYY.mrx.productionassist-plugin.json next to ProductionAssist.vwlibrary or ProductionAssist.bundle, not inside the bundle under Contents/MacOS.Note for macOS: Because the configuration file is outside the plug-in bundle, you can add or change it without modifying the bundle's code signature. For compatibility, the previous location under
Contents/MacOSis still used if there is no configuration file next to the bundle.
Currently, you can define exactly the following override:
| Key | Type | Effect |
|---|---|---|
appDataFolder | String | Sets this plug-in's AppData directory. Relative paths are resolved below the operating system's general AppData directory; absolute paths are used unchanged. |
Other keys are ignored. The configuration file affects only the plug-in's product-specific AppData directory. It does not change the operating system's general AppData root directory or the desktop app's Downloads, program, or home directory.
A relative path creates a separate directory within the general AppData directory:
{
"appDataFolder": "productionassist-vectorworks-2026"
}
The example resolves to:
%APPDATA%\productionassist-vectorworks-2026~/Library/Application Support/productionassist-vectorworks-2026On Windows, absolute paths with drive letters and UNC network paths are supported. Forward slashes avoid the need to escape backslashes in JSON:
{
"appDataFolder": "D:/ProductionAssist/Daten"
}
{
"appDataFolder": "//Dateiserver/ProductionAssist/Daten"
}
On macOS, an absolute path begins with /:
{
"appDataFolder": "/Volumes/ProductionAssist/Daten"
}
To use a plug-in with the portable Windows app, enter the full path to its data folder:
{
"appDataFolder": "D:/Programme/ProductionAssist/ProductionAssist-data"
}
First start the portable desktop app at least once, then close the desktop app and CAD application. Place the configuration file next to each plug-in module you use. After the next start, the plug-in uses the production_assist_config.json file from this folder, among other data.
The plug-in uses its default directory if:
productionassist-plugin.json is missing or is not a valid JSON object,appDataFolder is missing or is not a string,appDataFolder is empty or contains only spaces.Environment variables such as %APPDATA% and shortcuts such as ~ are not resolved in the value. Use either a relative path or a fully absolute path. The target directory must be writable by the signed-in user. When changing the directory, existing data is not moved automatically. If necessary, copy it manually to the new directory while the desktop app is closed and the CAD application is not running.
We're sorry that you want to leave us. If you have encountered any problems, you can always contact us here.
If you installed the plug-in manually, delete ProductionAssist.vwlibrary from the Plug-ins folder for your Vectorworks version under ~/Library/Application Support/Vectorworks. If you installed it through the desktop app, remove the ProductionAssist link there instead.
If you installed the plug-in manually, open the Plug-ins folder where you copied it and delete these Production Assist files:
ProductionAssistWeb folderProductionAssist.vlbProductionAssist.vwrIf you installed it through the desktop app, remove the ProductionAssist.lnk shortcut instead from the Plug-ins folder for your Vectorworks version under %APPDATA%\Nemetschek\Vectorworks\<Year>.