Introduction Last updated: 2020-06-24

EEforce is a Windows based PCB Design version management software that specifically designed for Mentor Graphics PADS and Xpedition PCB. The software has two parts of main components, Server and Client...

Server keeps all project files in a secure and isolated folder as versioned objects and allows authorized users to access and update those files while keeping original files unchanged.

Client software is a simplistic but powerful user interface that gives ability of working with designs in a reliable and simple way.

EEforce Client Software

EEforce Client is a Windows based software which has a simplistic user interface. This software specifically designed for addressing PCB Designers needs. Its interface inspired from various similar softwares like Mentor EDM.

Key Benefits
  • Xpedition and PADS projects can be stored and used at the same time
  • All design parts are kept in same container, not splitted to Schematic, Layout, etc.
  • Designs are edited using Check-In/Check-Out cycle
  • Designers can see a preview of PCB, Schematic and BOM without opening it
  • Every Project can have any number of Boards
  • Every Board can have any number of Versions
  • Versions can be locked, tagged and pruned
  • Uses Windows Authentication (NTLM) and does not requires user-name/password login

EEforce Server Software

EEforce Server Software is headless HTTP server process that accesses projects files in its vault folder and provides a REST API for Client software to access, modify and remove the data that stored in vault.

Server uses Microsoft IIS web server as Proxy and Authentication system.

Key Benefits comparing similar systems
  • Minimalistic Resource Usage, (~40MB of RAM on Idle, Maximum 4GB at Peak)
  • Simple deployment
  • Simple management
  • Need no perodic maintains
  • All-File-System storage
  • Can be used with Windows' Shadow Backup or any other file backup systems

Server Installation

There's some prerequisites that must be fullfilled before the installation.

Prerequisites
  • Supported Operating Systems: Windows Server 2012 R2 x64, Windows Server 2019 x64, Windows 7 x64, Windows 10 x64
  • .NET Framework 4.7.2. (Windows 10 and Windows Server 2019 has built-in. It must be installed manually for other OSs)
  • Server and Clients must be part of same Windows Domain (AD).
    This is required to establish secure connection between server and client computers.
    Can be ignored for testing environments.
  • Empty folder that will used for Vault, preferably in local disk, but mapped network location can be usable. The capacity of this folder must be determined by customer needs. At least 20GB of space allocation is recommended for start. This folder should be backed up by Windows Volume Shadow Copy service or similar 3rd party backup softwares.
  • Decent LAN connection between Server and Client Machines. Gigabit network is recommended.
    This system can be used with VPN or Proxy but download and upload times will be increased.
  • Valid License File that prepared for specifically the Server Machine
    Installation cannot be started without valid license file presented.

Using Installer

Server Installer has been developed to provide roboust step-by-step installation experience.
You can follow instructions on the software or listed down below.

Before beginning

Please check your system meets prerequsites listed above.
Also note that the Installer will require valid License file.

Installation Steps:
  1. You should have a Zip file named like Server_v1.22_2020_06_21.zip Version numbers can be different than example here.
  2. Extract ZIP file to a convinient folder.
  3. Extracted folder should be seen like this:
  4. Run ServerInstaller. If Windows asks for permission, allow it.
  5. You should be seen a welcome window like this:
  6. Press Start Installation Button
  7. You should see the End User License Agreement. Please take time to read it carefully and press I Agree button.
    Please note approving of this License Agreement is a legally binding document.
  8. After License Agreement window, this form (System Folders) will be presented:
    • License File: License file is a authorization file required by the software to determine whether this computer is allowed to run our softwares. You should obtain valid license file from your local authorized reseller.
    • Software Installation Folder: This folder used for storing software executables. We're strongly recommend to create a folder in your local hard drive for this purpose. Required space is less than 150MB.
    • Vault Folder: This folder used for storing design files. We recommend you to allocate at least 20GB of space for Vault. This folder can be stored in a network path, but the path must be inside a mapped drive. The read and write speeds of this folder is important and lower speeds can impact check-out/check-in performance. You also should setup regular backup for this folder. We recommend to use Windows shadow copy for backups.
    • Trash Folder: When users removes a design file, it is actually not been removed. System moves deleted design files to the Trash folder. We implemented this as a safety feature. Data loss is the worst thing ever can be. We recommend you to allocate at least 5GB of storage for Trash folder, and do manual cleanup regularly.
    • Domain Name: Enter this area the short domain name of your network. This is required for Windows Authentication system.
    • Super Users: There's some actions that requires administrator role. Please enter user names of administrators with commas in between. For example: john,max,jeremy.
      The list of super user priviledges:
      • Access and Manage all designs
      • Drop Licenses that are shown in-use
      • Cancel Check-Outs of any user
    • Normal Users: This list is used to control who can access the system. Therefore, you should name every user, including super users in this list. Note that you should enter exact user names, not first/last names of user.
    You have to present valid informations for every field in this page. After installation, you can change folders and user lists by editing config.json file stored in installation folder.

    When you finish, press Next button.

    If You See License Verification Error Dialog

    Please examine License file, search for SERVER_HWID section. This section shows the MAC address of ethernet port. You can see list of ethernet ports in your computer by typing ipconfig /all in Command Prompt screen.
    See this article for details of finding MAC address on computer.

  9. The next screen is the last checkpoint before installation start. You should check the informations you entered in the previous screen is correct.

    If you're certain the informations you've provided, press Start Installation button.
  10. At this point, installer will create required folders, install some Windows packages and deploy IIS server. Please give installer some time. When installation completed, it will automatically show final page.

    If Installation Fails

    Sometimes installation process may fail while deploying IIS or extracting files. While these situations rarely happens, it can be difficult to determine origin of the problem. Therefore, pleease examine logs that prints on screen and look for errors. Please make sure your system is fullfills the prerequisites.
    If you have pointed network folders for installation, vault or trash, please make sure Local Account IIS_IUSRS has read/write access to those folders. You can set permissions and start over to the installation.

  11. When the installation completed, this completion page will be shown. If you see this page, that means server has been installed and working as expected.

    Please take note for server address presented here. You can now close installation window, and start using server.
    Please take a look following section for deteailed post-install administration.

Deep Dive Configuration

Warning

The procedures explained in this sections should be performed by IT Professionals.
Wrong actions may cause data loss or unexpected behaviors.

  • Changing users and Paths After Installation

    Users and paths are stored in config.json file in the application path. You can see its content below:
    {
    	"Configurations": {
    		"DomainName": "MILBITT",
    		"VaultFolder": "C:\\pdmserver\\vault",
    		"TrashFolder": "C:\\pdmserver\\trash",
    		"SuperUsers": [
    			"admin1"
    			"admin2"
    		],
    		"AllUsers": [
    			"admin1",
    			"admin2",
    			"user1",
    			"user2",
    			"user3"
    		]
    	}
    }
    After saving this file, you must stop and wait for 10 seconds then start it again EEForce Server instance using Internet Information Services(IIS) Manager
  • Relocating Vault

    For relocating Vault, you must first stop EEForce Server instance using Internet Information Services(IIS) Manager. Then, you can move your vault folder to the desired location. After moving the folder, you must follow previous article to modify client.json file.
  • Setup Vault Permissions

    If you're using a network drive for vault, you must grant IIS user (IIS_IUSRS) to write and change to Vault and Trash Folders following this guide:
    1. Right-click the Vault directory, then choose Properties
    2. Go to the Security tab
    3. Find IIS_IUSRS account(If IIS_IUSRS account is not in the list, add it by clicking Edit then clicking Add, and then typing MACHINE_NAME\IIS_IUSRS in the "Enter the object names to select" field)
    4. Highlight the user in the list, click Edit, and grant the account Modify and Write permissions

Client Installation

There's some prerequisites that must be fullfilled before the installation.

Prerequisites
  • Mentor Xpedition or PADS Professional must be installed before EEforce Client
  • If you are going to use Xpedition and PADS together, they both must be in same architecture. (x86 or x64)
  • You must install Client software that is built for the same architecture of PADS/Xpedition installation. For example: If you're using PADS Professional x64 version, you must install EEforce x64 version.
  • Server software should be installed and running on the Server machine before installing EEforce Client.
  • Supported Operating Systems: Windows 7 x64, Windows 10 x64
  • .NET Framework 4.7.2. (Windows 10 and Windows Server 2019 has built-in. It must be installed manually for other OSs)
  • Server and Clients must be part of same Windows Domain (AD).
    This is required to establish secure connection between server and client computers.
    Can be ignored for testing environments.
  • Decent LAN connection between Server and Client Machines. Gigabit network is recommended.
    This system can be used with VPN or Proxy but download and upload times will be increased.

Using Installer

Client Installer has been developed to provide roboust step-by-step installation experience.
You can follow instructions on the software or listed down below.

Before beginning

Please check your system meets prerequsites listed above.

Installation Steps:

  1. You should have a Zip file named like Client_v1.22_2020_06_21.zip Version numbers can be different than example here.
  2. Extract ZIP file to a convinient folder.
  3. Extracted folder should be looking like this:
  4. Run ClientInstaller. If Windows asks for permission, allow it.
  5. You should be seen a welcome window like this:
  6. Press Start Installation Button
  7. You should see the End User License Agreement page. Please take time to read the agreement carefully, and press I Agree button to continue.Please note End User License Agreement is a legally binding document. If you're not comfortable with it, you should not agree it. You can read the agreement by opening eula.rtf file which it's in the installation directory.
  8. After License Agreement window, this form (System Folders) will be presented:
    • Software Installation Folder: This folder used for storing software executables. We're recommending to leave it as is. Required space is less than 50MB.
    When you finish, press Next button.
  9. The next screen is the last checkpoint before installation start. You should check the informations you entered in the previous screen is correct.

    If you're certain the informations you've provided, press Start Installation button.
  10. At this point, installer will create required folders, install some Windows packages and deploy IIS server. Please give installer some time. When installation completed, it will automatically show final page.
  11. When the installation completed, this completion page will be shown. If you see this page, which means installation is completed. You can press Finish Installation button to close installer window.

First-Run Configuration

After the installation, some of the configurations, like Server URL, should be edited. Please follow steps below for complete configuration.

First Run Steps:

  1. After the installation finished, EEforce icon should be appeared in your Desktop. Click it to open software.
  2. At the first run, Client Software may not connect to the server due to misconfiguration. If you this error window, dismiss the error dialog and press Setting button at the license selection window which is the window behind.
  3. On the settings window, update Server URL input using your server address. Server address information appears after its installation. If you do not know your server address, please contact with server administrator.

    If you installed the server on your local computer with default settings, you can write this: http://localhost:8000 to the Server URL input.

    After updating Server URL, press Save Configuration button.
  4. After returning the licensing window, if you see an empty list, press Refresh button. Then, if your Server URL configuration is correct, you will see a list of licenses on the window.

    Select an available license that you desire to use and press Use Selected License button.
  5. If the selected license is available, the Main Interface of EEforce Client Software will be shown.

    You're now finished installations and first configuration of the EEforce Client. After this point, you must do some more configurations about the PADS/Xpedition installation locations. Please refer Configuration section for those informations.

All Configurations

Before start to use the Client Software, you should complete the configurations. For this please follow the steps below.

Configuration Steps:

  1. On the EEforce software, go to the Tools menu above of the screen and click Settings
  2. Settings window will be shown:

    In the Settings window, there's 3 sub windows, respectively: Server Settings, Xpedition PCB Settings and PADS Professional Settings. You can click the menu on the left side of the window, and its associated configuration page will be shown on the right side of the window.
  3. On the Server Settings Page, you can edit those settings:

    • Server URL: The URL that used to connect to the Server. You should obtain this information from your System Administrator and should not change unless explicitly requested to.
    • Local Working Directory: Software requires a local folder to download design files and open them. This folder normally stores temporary files, and should be a local folder.
    • Application Language: The language of User Interface can be selected here.
      This option is under development. You can only use English for now. Another languages will be added with software updates.
  4. On the Xpedition PCB Settings Page, you can edit those settings:

    • Xpedition PCB Support: You can Enable or Disable usage of Xpedition PCB altogether. Designs that created by Xpedition PCB could not be opened if you disable this option. Note that Xpedition support is an optional feature. Enabling this option will not give you access unless you're using required License Option.
    • SDD_HOME Path: For Using Xpedition PCB with EEforce software, you must point SDD_HOME folder in your Xpedition PCB Installation path.
    • Central Library File: While opening a PCB Design, software can override Central Library file settings that is written in PRJ file in the design. This is an optional operation. You can use Environment varilables like in the example or point a LMC file directly.
    • Databook File: While opening a PCB Design, software can override Databook file settings that is written in PRJ file in the design. This is an optional operation. You can use Environment varilables like in the example or point a DBC file directly.
    • Borders.ini File: While opening a PCB Design, software can override Borders.ini file settings that is written in PRJ file in the design. This is an optional operation. You can use Environment varilables like in the example or point a INI file directly.
    • Speccomps.ini File: While opening a PCB Design, software can override Speccomps.ini file settings that is written in PRJ file in the design. This is an optional operation. You can use Environment varilables like in the example or point a INI file directly.
    • Busconts.ini File: While opening a PCB Design, software can override Busconts.ini file settings that is written in PRJ file in the design. This is an optional operation. You can use Environment varilables like in the example or point a INI file directly.
    • Part Lister Config Name: While opening a PCB Design, software can override Part Lister Config Name settings that is written in PRJ file in the design. This is an optional operation. Before using this configuration, you must ensure BOM configuration file with same name exists in WDIR or Project folder.
  5. On the PADS Professional Settings Page, you can edit those settings:

    • PADS Professional Support: You can Enable or Disable usage of PADS Professional altogether. Designs that created by PADS Professional could not be opened if you disable this option.
    • SDD_HOME Path: For Using PADS Professional with EEforce software, you must point SDD_HOME folder in your PADS Professional Installation path.
    • Central Library File: While opening a PCB Design, software can override Central Library file settings that is written in PRJ file in the design. This is an optional operation. You can use Environment varilables like in the example or point a LMC file directly.
    • Databook File: While opening a PCB Design, software can override Databook file settings that is written in PRJ file in the design. This is an optional operation. You can use Environment varilables like in the example or point a DBC file directly.
    • Borders.ini File: While opening a PCB Design, software can override Borders.ini file settings that is written in PRJ file in the design. This is an optional operation. You can use Environment varilables like in the example or point a INI file directly.
    • Speccomps.ini File: While opening a PCB Design, software can override Speccomps.ini file settings that is written in PRJ file in the design. This is an optional operation. You can use Environment varilables like in the example or point a INI file directly.
    • Busconts.ini File: While opening a PCB Design, software can override Busconts.ini file settings that is written in PRJ file in the design. This is an optional operation. You can use Environment varilables like in the example or point a INI file directly.
    • Part Lister Config Name: While opening a PCB Design, software can override Part Lister Config Name settings that is written in PRJ file in the design. This is an optional operation. Before using this configuration, you must ensure BOM configuration file with same name exists in WDIR or Project folder.

Project Operations

Project Naming Standard

Project names must be unique and must be in english characters. It cannot contain spaces and special characters except Underscore "_" character. It cannot be shorter than three digits, and longer than 40 digits. We strongly recommending using a consistent naming standard for project names.

Projects are virtual containers that stores Design Files(Boards) inside. One project may have many Boards. Write permisions are configured on project basis, so you can give write permission for a user and this user can edit all boards in the project. Projects are listed in Project Explorer section and all available actions related the projects are available in Right-Click Menu.

Using Project Explorer Section

Project Explorer section contains a list for projects. You have a search option and a filter option. Your filter preferences are stored and after re-opening the software those preferences are restored back.

Filter Options:
  • Active Designs: This options will show only those project which has a checked-out design inside. Check-Outs may be performed by anybody in the system.
  • Recent Designs: This option will show only recently checked-out projects by you.
  • All Designs: This option will show all projects in the system.

In the Project Explorer section, projects may have different icons. All icons has different meanings:


  • Read-Only Projects: Lock icon means that you do not have edit permissions on the project. You can open design content Read-Only.

  • Available Projects: This is the default look of the projects that you have rights to edit. This icon also show there's no actively working user on the project.

  • Actively Used Projects: This icon also means that you have rights to edit on the project, but there's some other user who is working some of the designs in the project.

  • Active Projects: This icon also means that you have rights to edit on the project, and you have checked-out one or more designs in this project.

Creating New Project

For creating a new project, follow the steps explained below. Please note that the creating new project will only allow you and the super users to edit project information.

  1. Right-click anywhere in Project Explorer section,
  2. Press New Project button in the popup menu.
  3. A dialog will be opened, enter name of the new project and press OK
  4. New project should be visible in Project Explorer section.

Changing Project Name

There should be no check-outs in the project and you should have editing permissions. For changing project name, follow the steps explained below.

  1. Right-click project name in the Project Explorer section.
  2. Press Properties button in the popup menu.
  3. Properties dialog will be opened:
  4. Type new name of the project into Project Name input box.
  5. Press Save Properties button.

Changing Project Users

There should be no check-outs in the project and you should have editing permissions. For changing project users, follow the steps explained below.

  1. Right-click project name in the Project Explorer section.
  2. Press Properties button in the popup menu.
  3. Properties dialog will be opened:
  4. For adding new user: Select user from the drop-down box beneigh the Authorized Users list, press Add button.
  5. For removing an existed user: Select user in Authorized Users List, press Remove Selected button.
  6. Press Save Properties button.

Cloning Project

There should be no check-outs in the project and you should have editing permissions. Cloning a project will copy all design files as a new Project. Please follow the steps explained below.

  1. Right-click project name in the Project Explorer section.
  2. Press Clone Project button in the popup menu.
  3. A dialog will be opened, enter the name of the new project and press OK
  4. Cloned project should be visible in Project Explorer section.

Removing Project

There should be no check-outs in the project and you should have editing permissions. Removing a project will also remove all containing designs. If you're sure to remove it, follow the steps explained below.

  1. Right-click project name in the Project Explorer section.
  2. Press Delete Project button in the popup menu.
  3. A confirmation dialog will be opened. If you're sure to remove the design, press OK
  4. Design should be removed from the Project Explorer list.

Board Operations

Board Naming Standard

Board names must be unique and must be in english characters. It cannot contain spaces and special characters except Underscore "_" character. It cannot be shorter than three digits, and longer than 40 digits. We strongly recommending using a consistent naming standard for board names.

Boards are actual design files which stored in the vault as ZIP files. Every version of a board represents a zip file in the vault.

When user checks-out a board, the server automatically finds latest or desired version of this board and sends it to the user's computer.

When user checks-in a design, all design files in the local computer is packed as Zip file and sent to the server. Then, server puts this file into project folder and updates its metadata information.

Board operations are accesible via Right Click Menu in Boards Section.

Importing Board Into Project

For importing an external design into the project, please follow these steps.

  1. Select target project in the Project Explorer section. If you do not have project yet, follow Creating New Project section.
  2. After selecting target project, In Boards section, right click an empty area. A small menu will be shown.
  3. Click Import Local Board button.
  4. Locate the root folder of your design in opened folder browser dialog.

    Note that you should pick the folder where the project (Schematic) file stored in your design.
  5. Wait couple seconds for the process completed, follow the operation status from Operation Logs section.

Renaming Board

Note: Renaming is only possible if board is in Checked-In state.

  1. Right Click the board
  2. In the popup menu, go to Board Info then press Rename button.
  3. A dialog will be shown for typing new name, type new board name there, then press OK.

Cloning Board

Note: Cloning is only possible if board is in Checked-In state.

  1. Right Click the board
  2. In the popup menu, go to Board Info then press Clone button.
  3. A dialog will be shown for typing a name for new board, type new board name there, then press OK.

Deleting Board

Note: Deleting is only possible if board is in Checked-In state.

  1. Right Click the board
  2. In the popup menu, go to Board Info then press Delete button.
  3. A confirmation dialog will be shown, If you sure to delete the project, press OK.

Moving Board Into Another Project

Note: Moving is only possible if board is in Checked-In state.

  1. Right Click the board
  2. In the popup menu, go to Board Info then press Move/Copy to Another Project button.
  3. A dialog will be shown.
  4. Select the Move Board option under the Operation section
  5. Select the target project in the list below
  6. Type a new name for the project, leave it as is if you do not want to change its name.
  7. Press OK

Copying Board Into Another Project

Note: Copying is only possible if board is in Checked-In state.

  1. Right Click the board
  2. In the popup menu, go to Board Info then press Move/Copy to Another Project button.
  3. A dialog will be shown.
  4. Select the Copy Board option under the Operation section
  5. Select the target project in the list below
  6. Type a new name for the project, leave it as is if you do not want to change its name.
  7. Press OK

Design Operations

This section is the continuation of the Board Operations section. In this section interactions with design files are explained. Design files are managed with a State Machine system. Which means is that designs has States and every state only accepts certain actions.

Design States

  • Checked In: In this state, design is stored in the server vault and there's no one editing it at the moment. So you can check-out if you have required permission.
  • Checked Out: In this state, while design is stored in the server vault, a copy of the design has been opened for editing by a user. Only the user who is checked it out can edit the design.
Design State Flow

Operations

  • Check Out (Start Editing Mode): This operation is available if design is in Checked-In State. It will download desired version of the design into local computer and change design state to Checked-Out. In this state, only the user who checked out the design has editing capabilities.
  • Check In (Finish Editing): This operation is available if you checked-out a design. After editing the design, you should call this procedure to upload the changes you made to the server. This procedure will increase design version and unlock the design for editing.
  • Cancel Check-Out (Discard Editing): This operation is available if you checked out a design. When you checked-out a design and did no changes on it, you can undo your check-out by running this procedure. This procedure should be used with caution, because local copy of the design will be removed.

Opening Design Read-Only

While you can check-out the design for editing, most of users would only open the design with no desires of editing. For this neeed, there's an option to open the design without calling check-out procedure. With this operation, a copy of design files will be downloaded into local computer, and you would able to open it with available tools. But you will not be able to update the files. The procedure:

  1. Right click board or desired version of it
  2. Run desired actions in under View (Open Read-Only Mode) menu.

Opening Design Editable (Check-Out)

As explained above, you can open design as editable by calling Check Out procedure:

  1. Right click board or desired version of it
  2. Run desired actions in under Check Out (Start Editing Mode) menu.

Finishing Editing of Design (Check-In)

As explained above, you can upload local copy of the design as a new version by calling Check In procedure:

  1. Right click the board that is already Checked-Out by you.
  2. Press Check In (Finish Editing) button.
  3. A dialog will be shown:
    Design State Flow
  4. Lock Status: If you see design as LOCKED, that means a program still running in your computer that locks some of the design files. Check if any editor window still open, close them and press Check Again button.
  5. Check-In Comment: You can write short comments about the reason of this check-in. It will be shown in the versions section.
  6. Remove 3D Files Option: 3D files can consume significant disk space. If you do not have any 3D work, there's still can be leftover files. Check this option if you want to remove all 3D information stored in the design.
  7. Remove Unnecessary Files: There's some files that is not needed to store in the design, like log and old CCZ files. You can check this option to remove those files.
  8. After completing the steps above, press Check-In button to complete process. Give it some time to upload the design to the server and track the status that shown in the Operation Logs section.

Cancelling Editing of Design (Cancel-Checkout)

As explained above, you can undo check-out if you do not want to upload local copy to the server. Please note that this operation will remove all local files related the design.

  1. Right click the board that is already Checked-Out by you.
  2. Press Cancel Check-Out (Discard Editing)
  3. A confirmation dialog will be shown.
    Design State Flow
  4. Lock Status: If you see design as LOCKED, that means a program still running in your computer that locks some of the design files. Check if any editor window still open, close them and press Check Again button.
  5. After completing the steps above, press Cancel Check-Out button to complete process.

Remote Working

This features are developed for users who requesting to work outside the system (For example: Remote workers) and still wanting to be able to import their update to the system.

Exporting Board For Remote Working

Exporting a design for remote working will give you a ZIP file which stores all design files, and you can work on it outside the system.

  1. Select project from Project Explorer section.
  2. Select the board you want to work remotely in the Boards section.
  3. Right click to the board, go to Remote Working menu
  4. Choose Export Package
  5. A File dialog will be opened. Choose a convinient folder and a name.
  6. Press Save
  7. You can work with the ZIP file now.

Importing Remotely Updated Board

When you worked outside the system and want to import local files As a new version of a board you can follow this procedure.

  1. Select project from Project Explorer section.
  2. Select the board you want to import new version in the Boards section.
  3. Right click to the board, go to Remote Working menu
  4. Choose Import Package
  5. A folder selection dialog will be opened. Find the design you wish to import and choose it.
  6. Give some time to the process, and track its status in Operation Logs section.

Licensing

License is an authorization information in form of XML file issued by us per costomer. License file may contain different kind and quantity of licenses. License file is stored in the server and served to the client machines. When one user tries to open Client Software, server checks if there's any suitable licenses for this user and give him a list of licenses. User can pick any license from avaliable ones and locks it as long as his Client Software is running. When the user closes the Client Software, license became back available for any other user.

License Types

  • License Period: Perpetual vs Term

    A Perpetual License is a permanent license that gives licensee to use it lifetime. On the other hand, Term license is a rental kind of license that gives licensee to use it for a period of time, usually for one year.
  • License Kind: Floating vs Nodelocked

    A Nodelocked license can only work on a dedicated users' machine. On the other hand, Floating license can work any machine in the network without limitation.
  • License Option: for PADS Pro vs for Xpedition + PADS Pro

    You have two options, if you will use the software only with PADS Professional, you can choose PADS Pro option which is cheaper. On the other hand, if you are using Xpedition, or Xpedition and PADS Professional same time, you need Xpedition + PADS Pro option.
  • License Upgrade Options

    If you choose to purchase a Perpetual license, it would give you lifetime usage, but this kind of licenses comes with only 1-year Upgrade/Support. When this period ends, you can still run latest version published in this period, but you cannot run newest version that published after your upgrade period ends. With License Upgrade package, you can purchase one more year of upgrade and support.

Frequently Asked Questions

  • Question: What versions of PADS is supported?
    Answer: We support all versions of PADS Professional
  • Question: What versions of Xpedition is supported?
    Answer: We support all VX versions. If you're using older version, please let us know, we can check it.
  • Question: Can I import old PADS Design (Not PADS Professional)?
    Answer: At the moment unfortunately not. Please let us know this request. We can add it into our development plans.
  • Question: How many users can use same system?
    Answer: We run stress tests similar to real-world environment. It depends on your hardware, design size and network speed. In general speaking, we say at least 50 users can work simultaneously. If you have more than 50 users, we can provide a custom scaling solution that uses advanced structure like multiple nodes and load balancers.
  • Question: Where is my data stored?
    Answer: All data stored inside Vault folder.
  • Question: Can I access my server via Internet
    Answer: If you're using VPN to connect your work network, we support this solution. But if you're going to expose server to internet access, it will bring security risks. Therefore, we do not officially support internet access but there's some success stories out there. Please contact us for detailed info.
  • Question: How can I revert a design to an older version
    Answer: You have two choices, first is checking out the version you wish to revert and check back in. Second choice is pruning newer versions until the version bacame latest one.