Setting up Vulcan Software

Accessing Vulcan

Vulcan can be accessed from https://usevulcan.app/launch.

Vulcan works with files stored locally on your device. For the full local workspace workflow, use a Chromium-based browser such as Chrome or Edge. The workspace picker depends on browser folder-access support, so browsers without that support cannot run the normal local workspace workflow. Vulcan can be used on Windows or Mac.

You will be asked to choose a local workspace folder. This is where Vulcan stores modelling inputs, output files, overlays, SAP files, and related supporting files.

On-device storage gives you direct access to your work, but also means you should take care when storing files. We recommend using a secure device, enabling multi-factor authentication where available, and regularly backing up your workspace.

Logging in to Vulcan

You can log in to Vulcan either from the website (https://usevulcan.app/auth) or directly from the web app (https://usevulcan.app/launch).

We recommend using your email and password to log in to Vulcan at this time, and using a secure password manager so you can set a strong password. If required, you can also reset your password or use a "magic link" that only requires your email and access to your email account.

Getting help and support

Use the in-app support chat when you need help with setup, modelling, calculations, evidence, or account questions. The support chat is available across the app, not only from one section.

Saved models or draft submissions can be attached to support conversations where the app offers that option. Attachments are based on saved files, so save the model or draft before asking for review or support on the latest version.

If the support conversation has just been created, send the first message before attaching a saved model or draft.

When attaching a model or draft to a support conversation:

• Attach uploads the latest saved snapshot and links it to the conversation.
• Update refreshes the attachment after you have saved more changes.
• Detach removes the attachment from the conversation and withdraws the linked review request.

Unsaved Geometry edits are not included in the attached draft. Save the model first, then use Update so the reviewed version matches the latest saved files.

The attached draft is based on the saved files and evidence available to Vulcan, including the HEM input, geometry CSV, defaults file, and linked evidence where available.

Reviews can only be requested for draft submissions. Reviews are evidence-based, so missing evidence may limit what can be checked. If a review is urgent, contact Vulcan directly.

User workspace and input/output files

Vulcan stores files locally. After every login, you will have the option to choose the workspace where the files are stored. If you close the Workspace menu, or want to change the workspace, open the top-right app menu and choose the workspace option. The same menu also contains Customise, integrations, licensing information, and your profile page (also accessible at https://usevulcan.app/profile).

Use Customise to change how Vulcan is displayed on your device and how automatic element names are formatted. The Customise modal has two tabs: Theme and Naming.

The Theme tab lets you choose a theme preset or adjust custom colours. It includes colour groups for the app surface, accent colour, text, borders, status colours, charts, Canvas 2D, and Canvas 3D. Vulcan will show contrast warnings where custom colour choices may make text or controls harder to read.

The Naming tab lets you control automatic names for Geometry elements. You can reorder name tokens such as floor, name, orientation, and number; turn optional floor or orientation tokens on or off; choose the floor label style; set a separator; and edit the default labels used for different object types. The preview column shows the resulting format before you apply the changes.

Naming changes apply to eligible auto-generated element names. Elements that you have manually renamed keep their manual name until you select the element and use Reset to auto.

In your workspace, the most important folders are:

• input/base_models: geometry CSV files created from the Geometry section
• input/batch_parameters/base_json: complete HEM input files created when geometry is merged with defaults
• input/batch_configs: scenario configurations created in the Scenarios section
• input/batch_parameters: the parameter library and any parameter snippets you create or edit
• input/analytics: metric definitions used in the Results section
• input/tariff_data_structured: tariff files used for cost metrics in Results
• input/sap: uploaded SAP PDF/XML files and extracted data used for comparison
• input/overlays: uploaded floorplan overlays
• output: simulation outputs from the Scenarios section
• logs: temporary logs created during local modelling workflows

You do not normally need to create these folders manually. If you are unsure, open or refresh the workspace from inside Vulcan.

Sample Parameter Library

The Sample Parameter Library installs the example and reference files used by Geometry, Scenarios, and Results. It writes files into:

• input/batch_parameters for model wrappers, weather, fabric, system, output, and other scenario snippets
• input/defaults for the defaults file used when a geometry CSV is merged into a complete HEM input
• input/base_models for example geometry models
• input/tariff_data_structured for example tariffs used by Results cost metrics
• input/assembly_library for reference assemblies, materials, and related Geometry Builder data

Install or restore the library from the workspace menu. Vulcan checks the library version and manifest in the workspace, and may ask you to restore the library when it is missing or out of date. Restoring the sample library refreshes the sample/reference files it manages, but existing files under input/base_models are preserved so your own saved geometry models are not overwritten.

If the library is missing or out of date, Vulcan may not be able to run normal scenario workflows correctly, because Scenarios and Results depend on the snippets, wrappers, weather files, defaults, and metrics support files installed with the library.