AseptSoft Core Documentation
AseptSoft Core Documentation
Breadcrumbs

Version Control

AseptSoft includes a built-in version control system that manages your process design work with branches, commits, automatic saving, undo/redo, and collaborative review sessions.

✨ Key Features

Feature

Description

🔄 Undo Redo

Unlimited undo/redo stack for all design operations

💾 AutoSave

Automatic saving synchronized with the host platform

🌿 Commits and Branches

Parallel branches for each collaborator with checkpoint commits

🔀 Merging

Merge data between modules, branches, commits, and templates with conflict resolution

📋 Review Sessions

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, and merged separately.

📌 Workflow Overview

  1. Each user works on their own branch — automatically created with their name

  2. Changes are auto-saved as you work, synchronized with the host platform's save cycle

  3. Create commits (checkpoints) at meaningful milestones to preserve snapshots

  4. Merge work from other branches, commits, or templates when ready to integrate

  5. Review Sessions allow structured collaborative review with validation and conversations

  6. 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)

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

  1. Open your project in the host platform (e.g., AutoCAD Plant 3D)

  2. Check your branch — AseptSoft automatically places you on your personal branch (named after your username)

  3. Design your process — add steps, configure engineering items, set valve states

  4. Save regularly — press Ctrl+S in AutoCAD; AseptSoft auto-saves alongside it

  5. Create a commit when you reach a meaningful milestone (right-click the module → "Create Commit...")

  6. Merge when ready — use "Update from..." to bring in work from other branches or templates

  7. Start a Review Session to get collaborative feedback before finalizing