Stay up to date with the latest improvements to AseptSoft. This page highlights recent changes, with links to the full documentation for each feature.
🗓️ April 2026
🧩 Interactive Create Equipment Module
Previously, the Create Equipment Module command was a one-shot flow: select some valves, type a name, and the module was created immediately with a 1:1 valve-to-item template. There was no review step, no way to add a second module without restarting, no conflict checking against existing modules, and no way to adjust the template or item names before committing.
Now, the command opens the same rich review window used for Excel imports, letting you configure and confirm multiple Equipment Modules in a single interactive session.
|
Capability |
What It Does |
|---|---|
|
✏️ Editable names |
Each Equipment Module's name is a text box focused automatically on open, with all text selected. Just type to rename; press Enter to accept. |
|
➕ Add another EM |
A dedicated button closes the window, prompts for a fresh drawing selection, and reopens the window with the new module added — your edits on the first module are preserved. Repeat as many times as needed. |
|
🛡️ Valve exclusivity |
Valves already belonging to an existing Equipment Module — or to another module being created in the same session — are detected automatically. A dialog lists the conflicts and lets you proceed with the remaining valves only. |
|
🧠 Smart defaults |
A new Configuration Template is auto-proposed with one item per selected valve, item names matching valve names — so the old one-click behavior still works: select, Enter, done. |
|
🎨 Template picker |
Want to attach the selection to an existing template instead? Pick from the dropdown. Or switch suggestion modes (reuse new templates across EMs, one per EM, etc.). |
|
🔄 Gallery refresh |
New modules appear in the Equipment Modules ribbon gallery immediately after creation — no restart or manual refresh needed. |
The Excel import window gained the same editable-name behavior: worksheet names are now editable before committing, and press-Enter-to-import works anywhere.
Valve exclusivity is now enforced project-wide and across all entry points — Create from Selection, Add another EM, and Excel Import all refuse to assign a valve that already belongs to another module, with a clear dialog explaining which module owns which valve.
👉 Full documentation: Equipment Module · Import Equipment Modules from Excel
☁️ Environment Updates with Backup, Rollback & Cloud Push
Previously, when you opened a project, AseptSoft silently overwrote your local environment files if newer versions were found — either in the project's portability folder or (in a recent change) from the cloud. You had no control, no notification, and no rollback path. Environment push to the cloud required FTP credentials and manual file management.
Now, the Environment Update Options window gives you full control over both update sources and the complete history of every environment on your machine. Every overwrite is backed up. Every cloud push goes through secure, role-based authentication — no FTP credentials required.
|
Capability |
What It Does |
|---|---|
|
⚙️ Per-source update policies |
Choose Auto Update / Always Ask / Manual Only independently for Project source and Cloud source |
|
🔔 Rich notifications |
Non-blocking success cards when auto-updates complete; modal prompts in Always Ask mode with Update Now / Skip This Version / Not Now choices |
|
📊 Full environment table |
See local, project, and cloud versions side by side for every environment, with reveal-in-explorer and copy-link icons |
|
🕒 Complete backup history |
Every overwrite is backed up with version, timestamp, reason, and source — click Activate on any historical version to roll back |
|
🏷️ Detach & reattach |
Running a historical version is a first-class state — automatic updates pause, and you get a daily reminder to reattach if a newer version is available |
|
☁️ One-click cloud push |
Upload environments to the cloud directly from the UI — no FTP, no credentials. Authorization is automatic via your 10Duke organization role. |
|
📥 Missing environment bootstrap |
Environments present in the cloud but absent locally are downloaded automatically on project open, regardless of your update policy — ensuring new team members receive the full set without intervention |
|
🔐 Role-based push empowerment |
The push icon appears only if you have OrgAdmin or EnvironmentAdmin in your organization. Missing EnvironmentAdmin roles are auto-created on first attempt — your admin just has to assign them. |
|
🗂️ Server-side history |
Each cloud push backs up the previous cloud version under |
Prepare for Portability now integrates fully with cloud push: in one command, it bumps every used environment, backs up each, copies to the portability folder, and pushes to the cloud — guaranteeing local, project, and cloud all end at the same version number. The AutoCAD command line reports each step with ✅/⚠/❌ status.
👉 Full documentation: Environment Updates
🤖 AI Assistant (Beta)
AseptSoft now includes an AI-powered copilot that lets you work through natural language conversation. Instead of navigating ribbons and dialogs, you can ask the assistant to create processes, configure equipment, manage automation data, export documents, and more — all from a chat window.
|
What You Can Do |
Examples |
|---|---|
|
📋 Process & algorithm design |
"Create a CIP process with 5 steps", "Add a transition condition to Step 3" |
|
⚙️ States & data management |
"Set the inlet valve to Open in Pre-Rinse", "Create a high-pressure alarm" |
|
🏭 Equipment modules |
"Create an EM from valves V-101 through V-105", "Apply the CIP configuration" |
|
📤 Export & navigation |
"Export to Word", "Navigate to the Drain step" |
|
💧 Fluid simulation |
"Enable fluid flow", "Highlight upstream from V-201" |
The assistant shows each action as a collapsible tool card with human-readable descriptions (valve names, step names — not database IDs). Read operations execute automatically; delete operations require confirmation. Choose between multiple AI models from the header dropdown.
⚠️ Beta — The AI Assistant is actively being expanded. Further capabilities will be added in future updates.
👉 Full documentation: AI Assistant
🔒 Valve Interlocks with Conditional Rules
Previously, interlocks were defined as ISA-88 cause-and-effect logic (cause condition → protective effect → safe actions). This approach focused on runtime behavior but did not capture which physical valve combinations are permitted or forbidden.
Now, valve interlocks define which combinations of valve positions are allowed or forbidden in the plant — directly from the P&ID. Two rule types are available:
|
Rule Type |
Meaning |
Icon |
|---|---|---|
|
🔴 Forbidden |
These specific valve combinations must never occur. Everything else is allowed. |
Red ban icon |
|
🟢 Only Allowed |
Only these specific combinations are permitted. Everything else is forbidden. |
Green check icon |
Creating interlocks is straightforward: select 2 or more valves in the drawing, choose Forbidden or OnlyAllowed, set each valve's state — done. The Module Data window provides a full master-detail panel for managing all interlock sets, with valve filtering, grouping, and inline editing.
Conditional interlocks let you attach reusable conditions (e.g., "CIP Active", "Temperature > 70°C") to individual configurations — so a rule is only enforced when its condition is true. Conditions are created with syntax-highlighted expressions, shared across configurations, and editable from multiple places.
Additional capabilities include:
-
🔍 Interlock overlay — visualize interlocked valves on the drawing with colored circles and connecting lines
-
🧭 Configuration path finder — find the shortest step-by-step transition between two valve configurations, never passing through a forbidden state
-
⚠️ Reachability analysis — detect disconnected configuration "islands" and process violations
-
🔧 Mechanical interlock designer — generate physical key/lock/hub specifications
-
📤 Export — four modes (Raw, All Forbidden, All Allowed, Mechanical Design) to Excel and Word
👉 Full documentation: Valve Interlocks
🎨 Header Block Designer
Previously, displaying project data in the drawing title block required placing individual Targeted Trackers one by one, with no way to track algorithm conditions or store custom per-step annotations.
Now, the Header Block Designer lets you build a complete, auto-updating title block as a single AutoCAD block — with a visual designer, live preview, and reusable presets. The block automatically populates with project data and updates as you navigate between steps and conditions.
|
Feature |
What It Does |
|---|---|
|
📝 Data fields |
Drag-and-drop configurable: Process, Step, User, Date, Version, Page Number, and more |
|
🧮 Algorithm tracking |
Compact GRAFCET notation showing condition types, expressions, actions, and transitions |
|
✏️ Custom per-phase fields |
User-editable text that stores different values per step (e.g., batch numbers, equipment status, operator comments) |
|
🔢 Aggregations |
Count, join, filter, min/max across conditions — active condition, all in phase, all in process, or cross-process |
|
🎨 Block appearance |
Text height, color, spacing, justification, border style, corner radius, label layout |
|
👁️ Live preview |
See exactly how the block will look as you configure it |
|
💾 Presets |
Save, clone, rename configurations — shared across modules |
The block uses a two-zone layout: a main zone for project information (process, step, user, date, custom fields) and a separate algorithm zone below for dynamic condition tracking with GRAFCET symbols.
👉 Full documentation: Header Block
📤 Export Enhancements
Word Export: Process Matrix, Equipment Modules & Algorithm
Previously, the Word export included module-level data (States, Fluids, Parameters, Variables, Alarms, Interlocks, Control Loops, Dialogs). Process-specific data like the valve phase matrix or algorithm conditions required separate Excel exports.
Now, the Word export dialog includes three additional data types for a more complete Functional Design Specification (FDS):
|
Data Type |
What It Exports |
|---|---|
|
📋 Processes |
Valve-vs-phase matrix showing which control modules have which states in each step — with Equipment Module grouping, valve type filtering, state nicknaming, and skip-empty option |
|
🏭 Equipment Module Configurations |
Overview table (all EMs with their templates, control modules, linked valves) plus per-EM detail tables showing item states across configurations |
|
🧮 Algorithm |
Compact mode: two-column table with GRAFCET notation. Full mode: detailed per-field condition table. Choose via radio buttons. |
A shared left sidebar centralizes process and PID selection — choose once, and all relevant data types follow those selections.
👉 Full documentation: Export Module Data to Word
PDF Export: Cover Pages
Previously, adding cover pages or appendices to exported PDFs required manual post-processing in an external PDF editor.
Now, the PDF Export dialog includes a Cover Pages section where you can attach a prefix PDF (prepended before the export) and a suffix PDF (appended after). Page counts are displayed, and an option lets page number trackers account for prefix pages in their numbering.
👉 Full documentation: Export Processes to PDF
🗓️ March 2026
Export Module Data to Word (.docx)
Previously, module data (States, Fluids, Parameters, Variables, Alarms, Interlocks, Control Loops, Dialogs) could only be exported to Excel or shared via templates. To create a formatted functional specification document, you had to manually copy data from Excel into Word.
Now, AseptSoft includes a dedicated Word export that generates a professional, ready-to-share .docx document directly from the Module Ribbon. The export dialog lets you:
-
Choose which data types to include or exclude
-
Reorder and filter individual fields per table by dragging them
-
Transpose tables (swap rows and columns)
-
Group data by category (e.g., group Parameters by Phenomenon)
-
Add an export comment embedded in the document properties
The exported document includes a title page, document metadata, and one formatted table per data type — with blue headers, clean borders, and actual color previews in color columns. Like all AseptSoft exports, it is cumulative — re-exporting updates the data while preserving your manual edits and formatting.
👉 Full documentation: Export Module Data to Word
🖱️ Valve Hover Inspector
Previously, inspecting a valve's state required selecting it and opening the Status Editor or Live Edit panel. Checking how a valve behaves across multiple process steps meant navigating step by step.
Now, simply hover your mouse over any valve on the P&ID drawing to see a rich, interactive popup showing:
|
What You See |
What You Can Do |
|---|---|
|
Current state name, color, and percentage |
Instantly understand the valve's current configuration |
|
FLOW / BLOCK badge |
Know immediately whether fluid passes through |
|
States gallery (all compatible states) |
Click any state to apply it in one click |
|
Percentage slider (for modulating valves) |
Drag to set exact opening percentage |
|
Steps timeline across the entire process |
See how the valve behaves in every step at a glance |
|
Equipment module memberships |
Apply a module configuration to all grouped valves at once |
The feature supports three modes: Auto (always on), Ctrl+Hover (shows only when holding Ctrl/Alt), or Disabled. Colored bullet overlays appear at each valve position, giving a bird's-eye view of all valve states across the drawing.
👉 Full documentation: Valve Hover Inspector
🔀 Off-Page Connector Hover and Connectivity Bullets
Previously, checking whether Off-Page Connectors were correctly paired required running a simulation or manually comparing Tag/Bind values across drawings. There was no visual indicator of connection status.
Now, AseptSoft displays colored connectivity bullets at each OPC's position:
|
Bullet |
Meaning |
|---|---|
|
🟢 Green |
OPC is connected — has a valid pair |
|
🔴 Red |
OPC is unconnected — no matching pair found |
Hovering over any OPC bullet shows a popup with full connectivity details — the current OPC's Tag, Bind, and PID, plus the partner's information if connected. For connected OPCs, a Navigate to Pair button lets you jump directly to the paired connector on the destination P&ID in one click.
For unconnected OPCs, the popup lists all other unconnected OPCs across open PIDs, helping you identify potential matches or spot misspelled Tag/Bind values.
The feature uses the same three modes as the Valve Hover Inspector: Auto, Ctrl+Hover, or Disabled.
👉 Full documentation: Off-Page Connector