AseptSoft includes a built-in version control system that manages your process design work with branches, commits, a browsable history, automatic saving, undo/redo, and collaborative review sessions.
✨ Key Features
|
Feature |
Description |
|---|---|
|
Unlimited undo/redo stack for all design operations |
|
|
Automatic saving synchronized with the host platform |
|
|
Parallel branches for each collaborator, with a real commit timeline per module |
|
|
Browse a module's full history, see what each commit changed, compare any two versions, and restore |
|
|
Merge data between modules, branches, commits, and templates with visual conflict review |
|
|
Collaborative validation and conversation workflow for process approval |
⚙️ How It Works
AseptSoft's version control operates at the module level. Each module is an independent unit of work that can be committed, branched, compared, and merged separately, and each module keeps its own complete commit timeline.
📌 Workflow Overview
-
Each user works on their own branch — automatically created with their name
-
Changes are auto-saved as you work, synchronized with the host platform's save cycle
-
Create commits (checkpoints) at meaningful milestones to preserve named, time-stamped snapshots
-
Browse the history to see what changed in any commit, compare any two versions, and restore an earlier state safely
-
Merge work from other branches, commits, or templates when ready to integrate
-
Review Sessions allow structured collaborative review with validation and conversations
-
Undo/Redo provides an unlimited stack for reversing individual design operations
🌳 Branch Structure
Project
├── main (shared branch for merged work)
├── user1 (personal branch)
│ ├── Module A
│ │ ├── Commit 1
│ │ └── Commit 2
│ └── Module B
├── user2 (personal branch)
│ └── Module C
└── custom (additional branches)
🏭 Pharma Example: Tracking CIP Process Changes Across Engineering Milestones
Imagine your team is engineering a CIP (Clean-in-Place) skid for a biopharmaceutical facility. The project moves through several engineering milestones — Conceptual Design, Basic Engineering, and Detailed Engineering — and multiple engineers contribute simultaneously.
Here is how AseptSoft's version control supports this workflow:
|
Milestone |
What Happens |
Version Control Feature |
|---|---|---|
|
Conceptual Design |
Lead engineer sets up the initial CIP process with wash steps, rinse steps, and drain sequences |
Work happens on the engineer's personal branch; a commit named "Conceptual Baseline" is created |
|
Basic Engineering |
A second engineer branches off to optimize chemical dosing while the lead refines valve sequences |
Each engineer works on their own branch independently (Commits and Branches) |
|
Change review |
The team compares the latest checkpoint against the conceptual baseline to see exactly what moved |
Version History & Comparison shows every change as a readable card |
|
Peer Review |
The team opens a Review Session to validate the optimized dosing against GMP requirements |
Review Sessions capture validation conversations |
|
Integration |
The dosing optimization is merged into the main branch for Detailed Engineering |
Merging detects conflicts and lets the team resolve them |
|
Accidental change |
An engineer mistakenly changes a valve state — they immediately undo the operation |
Undo Redo reverses the mistake instantly |
|
Continuous protection |
Throughout the process, every save in AutoCAD automatically persists AseptSoft data |
AutoSave keeps everything safe |
This ensures full traceability from concept through to detailed design — a key requirement for pharma validation and regulatory compliance.
📖 How To: Get Started with Version Control
-
Open your project in the host platform (e.g., AutoCAD Plant 3D)
-
Check your branch — AseptSoft automatically places you on your personal branch (named after your username)
-
Design your process — add steps, configure engineering items, set valve states
-
Save regularly — press Ctrl+S in AutoCAD; AseptSoft auto-saves alongside it
-
Create a commit when you reach a meaningful milestone (right-click the module → "Create Commit…")
-
Browse the history — open "Version History…" to compare versions or restore an earlier state
-
Merge when ready — use "Update from…" to bring in work from other branches or templates
-
Start a Review Session to get collaborative feedback before finalizing
🔗 Related Pages
-
Home Ribbon — Branch management from the Folders panel
-
File System — Where version control data is stored on disk
-
Review Session Ribbon — The ribbon for review sessions
-
Import/Export Templates — Template management for module data
