AseptSoft Core Documentation
AseptSoft Core Documentation
Breadcrumbs

Import/Export Templates

Templates allow you to save and restore Module Data snapshots for reuse across modules and projects. This speeds up module initialization and enables standardized configurations.

Import and export template buttons are located at the bottom of the Module Data window.

:clipboard: Overview

In pharmaceutical facilities, consistency is critical. When multiple CIP skids, WFI loops, or SIP stations share the same basic configuration — the same states, processes, parameters, and variables — templates let you define that configuration once and apply it everywhere. Instead of manually recreating module data for each new skid, you export a proven configuration as a template and import it into new modules.

This is especially valuable when rolling out standardized CIP procedures across multiple production lines or facilities, ensuring every module starts from the same validated baseline.

:package: What Templates Contain

A template is a .aseptsoftdb file that captures:

Data Type

Included

States

Yes

Processes

Yes

Parameters

Yes

Variables

Yes

:outbox_tray: Export Data (Create Template)

Creates a template based on the current Module. The template captures all States, Processes, Parameters, and Variables.

Storage location: %appdata%\AseptSoft\ModuleDataTemplates (see File System)

Steps

  1. Open the Module Data window

  2. Click the Export button at the bottom

  3. The template is saved to the templates directory

:inbox_tray: Import Data (Load Template)

Data can be imported from two sources:

Source

Description

Templates

Previously exported template files from the templates directory

Module files

Any .aseptsoftdb module file, including from older commits or different branches

Import Steps

  1. Click the Import button in the Module Data window

  2. Choose a source:

    • Select a template from the list of saved templates

    • Browse... to locate any .aseptsoftdb file (from another module, older commit, or different branch)

  3. Select data to import — choose which data types to include:

  4. Click Import

:shield: Conflict Resolution

During import, naming conflicts are resolved as follows:

Scenario

Behavior

Item with same name exists locally

Overwritten by the imported version

Attribute with same name exists locally

Local attribute preserved, imported version ignored

State attributes

Always imported (mandatory)

No name conflict

Item is created normally

Tip: Attributes are never overwritten during import. If you need to update an attribute, delete the local one first, then import.

:test_tube: Pharma Use Cases

Use Case

How

Example

Standardize CIP across facilities

Export a validated CIP template from the reference facility, share the file, and import into each new facility's modules

A proven CIP sequence with alkaline wash, acid wash, and WFI rinse steps is rolled out to 5 production lines

Copy data between modules

Export from source module, import into target module

Transfer a SIP configuration from Tank-01 to Tank-02

Restore from history

Browse to a .aseptsoftdb from an older commit or branch

Roll back to last week's parameter set after an accidental edit

Share with team

Export template, share file, teammate imports

Send your validated WFI loop configuration to the commissioning team at a remote site