Module Code Management
Creating a New Module Based on an Option Expression
You can create a new module based on an option expression that is currently listed under a different module. This action splits the wiring with that option expression into a separate module.
Procedure
Click the Configuration Setting Browser Window (Configuration tab) on the left of the application window and choose Module from the drop-down Mode list; the browser window on the tab lists the harnesses in the design.
Select the harness(es) for which you want to edit modules and click the Manage module codes for selected harnesses () button; the browser tree expands below each selected harness to display the modules that you have created for the wires in them. It also displays the wires in those modules. See the Browser Window (Module) section of Configuration Setting Browser Window (Configuration Tab) for full details of its contents.
Right-click the option expression and choose create new module.
Results
The option expression sub-folder and its wires are moved under a new module named after the option expression.
If a module already exists with that name, a suffix is added to the new module.
Examples
You can see one module A-RJ. There are wires with the option expression A-CDC and A-RJ that are in that module.
Figure 168: Create a Module Example: Before
If you right-click the A-CDC option expression and choose Create New Module, you get the following:
Figure 169: Create a Module Example: After
You now have two modules A-CDC and A-RJ, each of which contain wires with matching option expressions.
Parent Topic:
Module Code Management
Related Topics
Module Code Management
Viewing the Modules in a Capital Systems Integrator Design
Setting Wiring in Particular Modules to Active in the Design
Renaming a Module
Merging Modules
Moving Wiring Between Modules
Sharing Wires Between Modules
Capital Systems Integrator User Guide, 2512.2606
Unpublished work. © 2026 Siemens
Source: https://docs.sw.siemens.com/en-US/doc/861057055/202511026.capital_si_user/id193f9d17-45f8-4ce1-ace0-355d48c64f0c · retrieved 2026-07-18