AseptSoft Core Documentation
AseptSoft Core Documentation
Breadcrumbs

AseptSoft Project Structure

Understanding the relationship between your CAD environment and AseptSoft is essential for effective process design work. This page explains the three-level hierarchy: Host Project, AseptSoft Project, and AseptSoft Module.

📐 Hierarchy Overview

Level

What It Is

What It Contains

Host Project

Your AutoCAD / Plant 3D project

P&ID drawings, symbols, layers

AseptSoft Project

The AseptSoft organizational layer (1 per Host Project)

Users, Branches, Commits, Modules

AseptSoft Module

A complete unit of process design work

Processes, Steps, Conditions, Module Data, Exports

Key relationship: Each Host Project has exactly one AseptSoft Project, which contains multiple Modules.

🏗️ Host Project

The Host Project is the project created in your CAD platform (AutoCAD or Plant 3D). It exists independently of AseptSoft and contains:

  • P&ID drawings (.dwg files)

  • Symbol libraries and block definitions

  • Layer configurations

  • Plant 3D project database (if applicable)

Platform-specific behavior:

Platform

Project Support

AutoCAD Plant 3D

Full native project support — AseptSoft integrates with the Plant 3D project structure

AutoCAD Standard

No native project support — AseptSoft creates a virtual project to group your drawings

For an in-depth look at how the Host Project works on both platforms, see the Host Project Definition page, which covers both platforms in depth.

The AseptSoft Project opens and closes automatically with the Host Project, and its data is stored in a nearby folder.

📦 AseptSoft Project

The AseptSoft Project is the organizational layer that sits on top of the Host Project. It manages:

Feature

Description

👥 Users

Team members who can access and work on the project

🌿 Branches

Separate lines of development for parallel work

💾 Commits

Saved snapshots of module states (version history)

📦 Modules

The individual units of process design work

One AseptSoft Project is automatically created for each Host Project. You do not need to create it manually — it appears as soon as you start using AseptSoft in a Host Project.

🧩 AseptSoft Module

An AseptSoft Module is the core working unit of AseptSoft. It contains everything needed for a complete process design deliverable.

What a Module Contains

Category

Contents

Learn More

🔄 Process Design

Processes with their Steps (e.g., CIP, SIP, Production)

Process Design

⚙️ Algorithm Design

Conditions defining transitions between steps

Algorithm Design

📊 Module Data

States, Fluids, Parameters, Variables, Dialogs, Equipment Modules

Module Data

✅ Review Sessions

Conversations, Validation, and approval workflows

Review Sessions

📤 Exports

PDF, Excel, and other output formats

Export / Import

Module Independence

Each module is fully independent of other modules in the same project. This means:

  • Different modules can have completely different States, Parameters, and Variables

  • Each module has its own Process Design and Algorithm Design

  • Think of each module as a separate, self-contained deliverable

📑 Multi-P&ID Support

A single module can span across multiple P&IDs. This allows:

  • Sharing the same Processes and Steps across multiple drawings

  • Unified Algorithm Design across P&IDs

  • Consolidated exports covering all included P&IDs

  • Fluidstream simulations that flow between drawings via Off-Page Connectors

Why Multiple Modules?

While a single-user team could deliver an entire project using just one module, multiple modules are common because of:

Scenario

How Modules Help

🤝 Team collaboration

Each team member works on their own module on separate branches

📜 Version control

Each Commit creates a snapshot module

🔀 Work merging

Modules serve as buffers when merging work between colleagues

🔁 Parallel development

Different Branches each contain their own modules

💊 Pharma Example: Biotech Facility Project

Here is how a typical pharmaceutical / biotech facility project might be structured in AseptSoft:

Host Project: PharmaCorp Biotech Facility — Building 5

Module

Description

P&IDs Included

CIP Skid

Clean-In-Place system for automated vessel and pipe cleaning

PID-101 (CIP Supply), PID-102 (CIP Return)

SIP System

Steam-In-Place sterilization for product-contact surfaces

PID-201 (Steam Generation), PID-202 (SIP Distribution)

Product Processing

Main bioreactor fermentation and downstream purification

PID-301 (Fermentation), PID-302 (Filtration), PID-303 (Chromatography)

Utilities

WFI generation, clean steam, compressed air, and nitrogen supply

PID-401 (WFI Loop), PID-402 (Clean Steam), PID-403 (Gases)

Each module is independently designed — the CIP Skid team defines their own States ("Rinse", "Wash", "Drain"), Fluids ("WFI", "NaOH 0.5M", "HNO3"), and Processes, without affecting the Product Processing team's work. When ready, modules can be reviewed via Review Sessions and exported together for the facility's complete documentation package.

📖 Terminology Quick Reference

To avoid confusion between the host CAD software's project and AseptSoft's project, the documentation follows this convention:

Term in Documentation

Refers To

Example

Host Project

The AutoCAD / Plant 3D project

The .dwg files and project database

Project

The AseptSoft Project

Users, branches, commits, modules

Module

An AseptSoft Module

Process design, algorithm design, exports

🖥️ Supported Platforms

Platform

Status

Autodesk AutoCAD Plant 3D

✅ Fully supported

Autodesk AutoCAD

✅ Fully supported