AseptSoft provides a comprehensive set of export and import tools to exchange data between the engineering environment and external formats such as Excel, PDF, Word, and Microsoft Visio.
📂 Export Categories
|
Category |
Description |
Format |
|---|---|---|
|
Export process step sequences with valve states and conditions |
||
|
Export and import all types of Module Data |
Excel, Word, Visio, Templates |
|
|
Core tabular engine powering all structured Excel exports |
Excel (.xlsx) |
🔗 Quick Navigation — Process Exports
|
Export Type |
Page |
|---|---|
|
PDF export |
|
|
Excel — Standard |
|
|
Excel — Tabular |
|
|
Excel — Algorithm |
|
|
Excel — Validations |
|
|
Import/Export Templates |
🔗 Quick Navigation — Module Data Exports
|
Export Type |
Page |
|---|---|
|
Word — Functional Specification |
|
|
Equipment Modules to Excel |
|
|
Parameters & Variables to Excel |
|
|
Dialogs to Excel |
|
|
Dialogs to Visio |
🔄 Cumulative Exports
All AseptSoft exports are cumulative. Once a file has been exported, you can open it, edit it freely (add formatting, notes, charts, etc.), and save it. The next time you export, AseptSoft merges new data into your existing file while preserving your edits.
📋 How It Works
-
First export — AseptSoft creates the file with tables containing your current data
-
You edit — add formatting, colors, extra text, charts, or rearrange columns
-
Data changes — you update your module (rename items, add configurations, etc.)
-
Re-export — AseptSoft updates only the data cells; your formatting and extra content remain intact
This cumulative behavior is powered by the Excel Tabular Export engine, which uses dominant columns and name-based matching to identify existing rows and columns in the file.
🏭 Pharma Example — CIP Qualification Binder
Imagine you are preparing a CIP qualification binder for an IQ/OQ submission. You export your CIP process to Excel, then add custom cover pages, formatting, and inspector notes. A week later the process engineer adds a new rinse step. When you re-export, the new step appears in the workbook while all your custom cover pages, formatting, and notes remain untouched — saving hours of manual rework.
💡 Example
Suppose you export Equipment Modules to Excel. The initial export produces a clean data table. You then add custom formatting, headers, and notes below the table. After adding a new configuration called "Open" in AseptSoft and re-exporting, the new column appears in the table while all your formatting and notes are preserved.
⚙️ Post-Export Behavior
After every export, AseptSoft can automatically:
|
Action |
Description |
|---|---|
|
Open File |
Opens the exported file directly in the default application |
|
Open File Location |
Opens the folder containing the exported file |
|
Do Not Open |
Silently completes the export without opening anything |
📊 Supported Formats Summary
|
Format |
Export |
Import |
Used For |
|---|---|---|---|
|
Excel (.xlsx) |
Yes |
Yes |
Processes, Equipment Modules, Parameters, Variables, Dialogs, Alarms, Control Loops, Interlocks |
|
Word (.docx) |
Yes |
— |
Module functional specification with States, Fluids, Parameters, Variables, Alarms, Interlocks, Control Loops, Dialogs |
|
|
Yes |
— |
Process documentation for IQ/OQ annexes |
|
Visio (.vsdx) |
Yes |
— |
GRAFCET/SFC sequences and Dialog layouts |
|
Templates (.aseptsoftdb) |
Yes |
Yes |
Module Data snapshots for reuse across modules |
🔗 Related Pages
-
Module Ribbon — Export buttons are located in the Export panel
-
Module Data — The data types that can be exported
-
Equipment Module Ribbon — Equipment Module context exports
-
Export Processes — Process-specific export hub
-
Export / Import Module Data — Module data export hub
-
Export Module Data to Word — Word document functional specification
-
Import/Export Templates — Template snapshots for reuse