Capital Design Tools - Common Functions User Guide

SIEMENS
Capital Design Tools -

Common Functions User
Guide
Incorporating Capital E/E
Insight User Guide
Release 2207
December 2023
Unpublished work. © 2023 Siemens
This Documentation contains trade secrets or otherwise confidential information owned by Siemens Industry
Software Inc. or its affiliates (collectively, “Siemens”), or its licensors. Access to and use of this Documentation is
strictly limited as set forth in Customer’s applicable agreement(s) with Siemens. This Documentation may not be
copied, distributed, or otherwise disclosed by Customer without the express written permission of Siemens, and may
not be used in any way not expressly authorized by Siemens.
This Documentation is for information and instruction purposes. Siemens reserves the right to make changes in
specifications and other information contained in this Documentation without prior notice, and the reader should, in
all cases, consult Siemens to determine whether any changes have been made.
No representation or other affirmation of fact contained in this Documentation shall be deemed to be a warranty or
give rise to any liability of Siemens whatsoever.
If you have a signed license agreement with Siemens for the product with which this Documentation will be used,
your use of this Documentation is subject to the scope of license and the software protection and security provisions
of that agreement. If you do not have such a signed license agreement, your use is subject to the Siemens Universal
Customer Agreement, which may be viewed at https://www.sw.siemens.com/en-US/sw-terms/base/uca/, as
supplemented by the product specific terms which may be viewed at https://www.sw.siemens.com/en-US/sw-
terms/supplements/.
SIEMENS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS DOCUMENTATION INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE, AND NON-INFRINGEMENT OF INTELLECTUAL PROPERTY. SIEMENS SHALL NOT BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL OR PUNITIVE DAMAGES, LOST DATA OR
PROFITS, EVEN IF SUCH DAMAGES WERE FORESEEABLE, ARISING OUT OF OR RELATED TO THIS
DOCUMENTATION OR THE INFORMATION CONTAINED IN IT, EVEN IF SIEMENS HAS BEEN ADVISED OF
THE POSSIBILITY OF SUCH DAMAGES.
TRADEMARKS: The trademarks, logos, and service marks (collectively, "Marks") used herein are the property of
Siemens or other parties. No one is permitted to use these Marks without the prior written consent of Siemens or the
owner of the Marks, as applicable. The use herein of third party Marks is not an attempt to indicate Siemens as a
source of a product, but is intended to indicate a product from, or associated with, a particular third party. A list of
Siemens' Marks may be viewed at: www.plm.automation.siemens.com/global/en/legal/trademarks.html. The
registered trademark Linux® is used pursuant to a sublicense from LMI, the exclusive licensee of Linus Torvalds,
owner of the mark on a world-wide basis.
About Siemens Digital Industries Software
Siemens Digital Industries Software is a global leader in the growing field of product lifecycle management (PLM),
manufacturing operations management (MOM), and electronic design automation (EDA) software, hardware, and
services. Siemens works with more than 100,000 customers, leading the digitalization of their planning and
manufacturing processes. At Siemens Digital Industries Software, we blur the boundaries between industry domains
by integrating the virtual and physical, hardware and software, design and manufacturing worlds. With the rapid
pace of innovation, digitalization is no longer tomorrow’s idea. We take what the future promises tomorrow and make
it real for our customers today. Where today meets tomorrow. Our culture encourages creativity, welcomes fresh
thinking and focuses on growth, so our people, our business, and our customers can achieve their full potential.
Support Center: support.sw.siemens.com

Send Feedback on Documentation: support.sw.siemens.com/doc_feedback_form
Table of Contents
Chapter 1
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Refreshing External Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Viewing the Details of Installed Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Reloading Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Design Inspectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Custom Action Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Object Attribute Descriptions for Use in Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . 34
Usage Example - Loading an Extensibility Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Product Excellence Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
API, Plugin, and Web Service Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Location of Application Log Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Log File Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Capital Application Launcher and Application Command Line Options . . . . . . . . . . . . . . . 43
Specifying the Memory Allocation of Capital Applications . . . . . . . . . . . . . . . . . . . . . . . . . 49
Displaying a String in the Window Banner of Applications . . . . . . . . . . . . . . . . . . . . . . . . . 50
Capital Stop Services - Command Line Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Encrypting Text Strings for Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Feature Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Automatic Update of Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Multi Factor Authentication Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Enablement of Multi Factor Authentication Using OIDC . . . . . . . . . . . . . . . . . . . . . . . . . 56
Creating Additional Icons in the Capital Application Launcher . . . . . . . . . . . . . . . . . . . . . . 58
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Using the Report Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
User Interface Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
User Interface Toggle View Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Embedded Library Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Enabling The Embedded Library Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Using The Embedded Library Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Configuring Internal Part Numbers on Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Multiple Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Embedded Integration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Adding a Library Part from EDM Collaborate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Launching Capital Component Manager from this Application . . . . . . . . . . . . . . . . . . . . . . 78
Launching Capital Symbol Designer from this Application . . . . . . . . . . . . . . . . . . . . . . . . . 79
Diagram Language Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Language Dictionary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Active Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Translatable Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Chinese and Japanese Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Capital Design Tools - Common Functions User Guide, 2207 3

December 2023
Table of Contents
Editing the Language Dictionary CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Saving a Language Dictionary CSV File with UTF-8 or Non-Ascii Characters . . . . . . . . 84
Importing a Language Dictionary CSV File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Exporting a Language Dictionary CSV File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Refreshing Language Dictionary Data in a Design Application . . . . . . . . . . . . . . . . . . . . 87
Adding a Translation of an Existing Translatable Term for the Currently Active Language 88
Adding a Translation of a New Translatable Term for the Currently Active Language . . 89
Converting Text Strings into Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Running Capital Tasks in the Background (Flexible Execution Model). . . . . . . . . . . . . . . . 91
Running Harness Processing in Capital Harness Designer (or Capital Harness Designer
Modular) in the Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Running SBOM Generation and Costing in Capital Harness Process Designer in the
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Running FMEA Scenarios in Capital Analysis in the Background . . . . . . . . . . . . . . . . . . 94
Creating Audit Reports When Capital Analysis Operations are Run in the Background . 95
Running ICD Publication from Capital Logic Designer in the Background . . . . . . . . . . . 96
Tasks tab in Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Running Documentation Package Generation in Capital E/E Publisher in the Background. 99
Searching for an Action on the Ribbon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Configurable Ribbon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Filtering Out Ribbon Actions Based on Design Type and Abstraction . . . . . . . . . . . . . . . 102
Searching for an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Reordering Browser Tabs on the Bottom Left of a Design Application . . . . . . . . . . . . . . . . 108
Undocking Browser Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Creating and Using Quick Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Launch Pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Sort Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Call Home Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Specifying Preferences for Call Home Error Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Manually Creating a Filtered Call Home Error Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Capturing Performance Profiling Data and Heap Dump Data. . . . . . . . . . . . . . . . . . . . . . . . 118
Chapter 2
Projects and Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Project Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Opening a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Deleting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Importing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Exporting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Closing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Saving Changes to Projects and Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Project Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Project Preferences for Capital Analysis Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Project Preferences for Manufacturing Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Project Preferences for Capital Device Modeler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
4 Capital Design Tools - Common Functions User Guide, 2207

December 2023
Table of Contents
Project Preferences for Capital Harness Designer and Capital Harness Designer Modular
Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Project Preferences for Capital Systems Integrator Designs . . . . . . . . . . . . . . . . . . . . . . 158
Project Preferences for Capital Logic Designer Designs . . . . . . . . . . . . . . . . . . . . . . . . . 169
Project Preferences for Capital Project Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Project Preferences for Capital Wiring Integrator Designs . . . . . . . . . . . . . . . . . . . . . . . 202
Project Preferences for Capital Systems Modeler Designs . . . . . . . . . . . . . . . . . . . . . . . 210
Project Preferences for Design Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
General Project Preferences Applicable to all Applications . . . . . . . . . . . . . . . . . . . . . . 217
Project Preferences - Checks Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Capital Compressed Format for Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Exporting a Project in Capital Compressed Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Importing a Project in Capital Compressed Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Designs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Importing Designs into a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Copying Designs From One Project to Another . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Migrating a Design from Capital Harness Classic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Editing the Information for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Editing a Property for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
Comparing Objects and Their Properties in Design Revisions or Build Lists . . . . . . . . . . 241
Mass Design Revision and Effectivity Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Using ECOs for Mass Revision and Effectivity Changes . . . . . . . . . . . . . . . . . . . . . . . . 243
Using Build Lists for Mass Revision and Effectivity Changes . . . . . . . . . . . . . . . . . . . . 244
Selecting Specific Designs for Mass Revision and Effectivity Changes . . . . . . . . . . . . . 245
Design Rule Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Running Design Rule Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Running Design Rule Checks in Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Design Rule Checks Output Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Design Browser Tree Expansion Limitations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Running Modes for DRCs in Capital Systems Integrator . . . . . . . . . . . . . . . . . . . . . . . . 251
Enforcing Design Rule Checks During Release Level Transitions . . . . . . . . . . . . . . . . . 253
Track and Override Design Rule Check Failures Using Issues . . . . . . . . . . . . . . . . . . . . 256
Design Rule Check Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Design Rule Checks Applicable to Capital Systems Integrator Designs . . . . . . . . . . . . . 262
Design Rule Checks Applicable to Capital Logic Designer Designs. . . . . . . . . . . . . . . . 307
Design Rule Checks Applicable to Capital Harness Designer and Capital Harness Designer
Modular Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Design Rule Checks Applicable to Manufacturing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Design Rule Checks Applicable to Capital Wiring Integrator Designs . . . . . . . . . . . . . . 404
Searching for a Design across all Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Design Folder. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Editing Design Folders in Design Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Build List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Setting an Active Build List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Selecting an Alternative Build List. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Applying Scopes to a Project or Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Options and Option Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Creating an Option at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Defining Option Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 430

December 2023
Table of Contents
Defining Inclusive and Exclusive Relationships for an Option . . . . . . . . . . . . . . . . . . . . . 430

Creating an Option Folder at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Option Combinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Creating an Option Combination at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Adding a Valid Selection to an Option Combination. . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Deleting a Valid Selection from an Option Combination . . . . . . . . . . . . . . . . . . . . . . . . 436
Deleting an Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Engineering Change Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Working with an ECO Created in Capital . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Creating an Engineering Change Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Deleting an Engineering Change Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Viewing Engineering Change Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Assigning an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Capture and Apply a Change Within an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
ECO Impacted Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Start and Stop Capturing an ECO Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Capturing a Change with an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Applying a Stored Change from an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Identification of Topology Changes with Hotspots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Harness Object Behavior on Applying ECO Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
ECO Support for Bundles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
ECO Support for Splices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
ECO Support for Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
ECO Support for Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
ECO Support for Modular Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
ECO Support for Fixings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
ECO Support for Insulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
ECO Support for Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
ECO Support for Multicores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
ECO Support for Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
ECO Import and Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Exporting an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
Importing an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Exporting an ECO Design Change Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Importing an ECO Design Change Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Chapter 3
Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Common Edit Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Changing the Cursor to Crosshair Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Copying and Pasting an Object in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Deleting an Object in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Filtering the Objects Displayed in a Capital Systems Integrator or Capital Wiring Systems
Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Finding and Selecting Objects by Attribute or Property. . . . . . . . . . . . . . . . . . . . . . . . . . . 475
Finding and Selecting Objects by Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Keyboard Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Moving Objects from a Diagram to Another Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 485

December 2023
Table of Contents
Moving Objects on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487

Redoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Repeating an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Selecting All Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Selecting Specific Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Specifying the Handle Color and Width of Selected Objects. . . . . . . . . . . . . . . . . . . . . . . 490
Specifying the Highlight Color and Width of Selected Objects . . . . . . . . . . . . . . . . . . . . . 490
Undoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Using the Stroke Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Window Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Arranging Diagram Windows for Viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Changing the Background Color of a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Panning Across a Diagram Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Using Tearable Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Zooming In and Out of Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Chapter 4
3D Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Opening the 3D Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Adding Harness Objects to the 3D Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Removing Harness Objects from the 3D Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Viewing a Skin in the 3D Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Changing the View in the 3D Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Separation Categories and Distances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Creating a File of Separation Categories and Distances. . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Setting Separation Categories and Distances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
3D Viewer Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Chapter 5
Graphics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Borders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Adding a Border to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Removing a Border from a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Replacing a Border on a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Graphic Drawing Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Adding an Image to a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Adding Properties to a Graphical Shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Adding Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Adding a Comment Symbol to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Adding a Symbol to a Diagram as Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Editing a Symbol Added as Graphics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Resizing a Comment Symbol in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
Adding a Text Frame to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
Changing the Image in an Image Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Controlling the Layering Order (Z-Order) of Graphical Shapes and Graphical Objects . . 527
Deleting a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
Drawing a Circle in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Drawing a Curved Line in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528

December 2023
Table of Contents
Drawing a Fillet in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

Drawing a Line in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
Drawing an Arc in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Drawing an Offset in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Drawing a Polygon in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Drawing a Rectangle in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Drawing a Tangent in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Editing a Property Value of a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Editing the Graphical Properties of a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Grouping Graphical Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Link or Embed Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Moving a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Stretching a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Transform Graphics on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Translate Graphics on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Trimming Graphics in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Ungrouping Graphical Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 550
Graphics Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Adding a Graphics Point to a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Deleting a Graphics Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Grip Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Adding a Grip Point to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Deleting a Grip Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
Chapter 6
Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Grouping Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Creating a Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Ungrouping Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Aligning Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Distributing Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Flipping Objects in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Rotating Objects in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Rotating Objects Around a Specified Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Defining Rotation Increments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Free Rotating Text Decorations, Comment and RED Symbols or Graphical Objects . . . . 565
Example of Applying Styling on Rotated or Flipped Objects . . . . . . . . . . . . . . . . . . . . . . 566
Pivoting Text About its Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Setting Snap To Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Setting Grid Defaults for a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Splitting Tables Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Using Japanese Text on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Chapter 7
Rules and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573
Overview of Rules and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576

December 2023
Table of Contents
Object Rule Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576

Editable Elements in Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Regular Expressions in Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Defining Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
Assigning a Rule or Constraint to an Object or Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Usage Example - Using a Null Value in a Constraint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Rule Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584
Chapter 8
Modifying Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Object Attributes and Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Assigning a New Library Part to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
Assigning/Editing an Object's Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Bulk Editing the Properties of Design Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Defining Specification Attributes for a Conductor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Editing an Object's General Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Editing the Graphical Attributes of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Editing the User-Defined Properties of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
Foreground, Background and Manual Color Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
Freezing and Unfreezing Shared Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
Simultaneous Editing of Multiple Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Specifying a Wire Color with a Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
Specifying Connector Cavity Component Drivers in Capital Logic Designer and Capital
Systems Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Specifying Option-Specific Values for Net Attributes and Properties . . . . . . . . . . . . . . . . 606
Specifying the Name Attribute of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607
Unassigning a Library Part from an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Updating Library Parts Assigned to Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Viewing the Library Part Details for an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
Converting a Symbol to a Parameterized Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Adding Assemblies Containing Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
Adding Associated Comment Graphics or Comment Symbols to an Assembly . . . . . . . . 615
Adding Objects Within the Associated Comment Graphic Boundary to an Assembly . . . 617
Creating an Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
Creating an Assembly from the Part Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Deleting an Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Editing an Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621
Extending the Selection of Objects for an Assembly Comment Graphic or Symbol. . . . . 621
Removing an Object from an Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Removing Objects No Longer Within the Associated Comment Graphic Boundary from an
Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Renaming an Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Updating Assembly Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Updating Assembly Supplements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Physical Line Thickness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Setting the Default Physical Line Thickness for Comment Graphics . . . . . . . . . . . . . . . . 626
Setting the Physical Line Thickness for Graphics in Diagrams . . . . . . . . . . . . . . . . . . . . . 627

December 2023
Table of Contents
Using a Plugin Interface to Control Physical Line Thickness . . . . . . . . . . . . . . . . . . . . . . 628

Finding and Replacing Property Values, Attribute Values and Symbols . . . . . . . . . . . . . . . 629
Advanced Naming Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
Generating Names for all Objects in a Build List, Design or Diagram . . . . . . . . . . . . . . . 634
Generating Names for Selected Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Selecting a Component Part Number in the Part Selection Dialog Box . . . . . . . . . . . . . . . . 636
Performing a Batch Update of Library Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
Slicing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
Navigating Between Sliced Object Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
Reconnecting a Sliced Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Slice and Move To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Slicing a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Slicing a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Slicing Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Slicing Conductors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Slicing Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Slicing Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Slicing to Trim Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Design Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Opening Design Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Parameterized Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
Viewing Design Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
Chapter 9
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
Print to a Printer or Plotter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
Printing a Single Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662
Printing Selected Diagrams in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Printing All Diagrams in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
Printing All Diagrams in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665
Printing Selected Print Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
Print Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
Adding a Print Region to a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
Resizing a Print Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Moving a Print Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
Editing a Print Region. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
Locking a Print Region in Position. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Deleting a Print Region. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
Print to a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Printing To File - All Diagrams in a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Printing To File - All Diagrams in a Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
Printing To File - Single Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Printing To File - Selected Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676
Printing To File - Print Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
SVG Page Settings Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Line Thickness Scale Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Minimum Line Width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
Display Width and Display Height . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682

December 2023
Table of Contents
Line Pattern Scale Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683

Fill Pattern Scale Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
Chapter 10
Collaborate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
Introduction to Collaborate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
Notifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
Enabling Collaborate Notify Me Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
Modifying Collaborate Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695
Viewing Comments, Notes and Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
Creating a Comment, Note or Checklist Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
Modifying a Comment, Note, or Checklist Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
Replying to a Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
Managing Collaborate Data in a Project or Design Action . . . . . . . . . . . . . . . . . . . . . . . . . . 702
Chapter 11
Trace and Navigate, Compare and Propagate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
Trace and Navigate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
Tagging Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
Working Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
Adding Designs to a Working Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
Tracing an Object across Designs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Trace Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
Trace Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
Configuring Tagging Tasks to Run in the Background . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
Configuring Stale Tag Cleanup Tasks to Run in the Background . . . . . . . . . . . . . . . . . . . 715
Compare and Propagate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
Viewing the To Do List for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Applying To Do List Attribute and Property Changes Between Capital Logic Designer Designs
723
Usage Example - Traversing Internal Device Links When Using Compare and Propagate
Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
To Do List Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Troubleshooting Tagging Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
ANSTagGenerationTask or ANSStaleTagCleanupTask Fails . . . . . . . . . . . . . . . . . . . . . . 733
ANSTagGeneration Task Cannot Run after Superuser Password Change. . . . . . . . . . . . . 733
ANSTagGenerationTask or ANSStaleTagCleanupTask Runs for a Long Time . . . . . . . . 734
CapitalRunner Log File Indicates Out-of-Memory Issues . . . . . . . . . . . . . . . . . . . . . . . . . 735
Tagging Tasks Have Not Started After Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
First Tagging Task Takes a Long Time After Data Migration. . . . . . . . . . . . . . . . . . . . . . 735
Chapter 12
Dialog and Field Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737
Project-related Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
Choose Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744

December 2023
Table of Contents
Copy Design Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745

Create New Design Revision Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Edit Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Edit Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
Import Designs to Project - Copying to Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . 750
Import Designs to Project Wizard - Copying to Project Wizard Dialog Box. . . . . . . . . . . 754
New Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
Open Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
Project Folders Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
Project Preferences Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776
Select Designs to Copy Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
Select Project Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
Editing Action Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
Applicable Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
Connections Tab (Properties Dialog Box) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783
Cross-references Tab (Properties Dialog Box) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
Compare Designs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
Design Revision - Build List Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 794
Design Rule Checks Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
Edit Assemblies Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
Edit Assembly Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
Edit Breakout/Spot Tape Details Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
Edit Design Properties Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
Edit Effectivity Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Edit Graphical Attributes Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
Edit Name Text Attributes Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Edit Objects Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Edit Option Expression Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
Filter Popup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
General Tab (Properties Dialog Box) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
Generate Advanced Names Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827
Handle Graphics Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
Highlight Graphics Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
Manage Designs & Effectivity Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
Map Equivalent Devices Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833
Map Pins Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
Name Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
New/Edit Assembly Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
Part Selection Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
Properties Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
Properties Tab (Properties Dialog Box) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
Select by Attribute/Property Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
Select By Name Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
Select Color Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
Select Details Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852
Where Used In Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
Graphics Related Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854

December 2023
Table of Contents
Add Text Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855

Drafting Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
Edit Border Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
Fill Pattern Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860
Image Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
Propertied Graphic Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
Save as Function or Device Symbol Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
Symbol Selection Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
Update Symbol - Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
Layout Related Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
Set Grid Defaults Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
Split Table Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
Miscellaneous Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
Applicable Changes Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
Apply Change Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
Assign ECOs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
Batch Translate Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Browser Tab and Dialog Box Filters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Capital Systems Integrator or Topology Design Filter Dialog Box . . . . . . . . . . . . . . . . . . 884
Change Manager Apply ECO Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886
Change Manager Preview ECO Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
Configure Import Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
Edit Capital Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
Edit Diagram Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
Engineering Change Orders Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
Engineering Change Orders Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
Export ECOs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
Manage Designs & Effectivity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909
New Folder or Rename Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
New Property Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
Options (Apply ECO) Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 912
Plugins Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
Plugin Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915
Query Criteria Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
Release Designs Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Report Builder Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
Set separation distances Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
Simulate Change Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Printing Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
CGM Page Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 924
DXF Page Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925
Edit File Name Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
Edit Print Region Groups Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927
PDF Page Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 929
Print Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
Print to File Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
Project Diagram Settings Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
SVG Page Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
Rules and Constraints Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937

December 2023
Table of Contents
Condition Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938

Constraint Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941
Define Rules Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942
Rule Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
Rules Tab in Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
Collaborate Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946
Associated Objects Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 947
Checklist Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
Collaborate Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950
Comments Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
Edit Collaborate Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
Manage Notifications Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956
Notes Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957
Warning Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959
Undoable Operation Confirmation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 960
Design Log Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
Design Log Event Filter Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962
Design Log Filter Options Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
Design Log Viewer Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
View Design Logs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
Help Button Landing Pages for Dialog Boxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968
Add Shared Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
Add Shared Pins/Ports Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
Add Text Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
Applicable Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
Assemblies Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
Batch Translate Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
Build Lists Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
Capital Systems Integrator or Topology Design Filter Help . . . . . . . . . . . . . . . . . . . . . . . 973
CGM Page Settings Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
Change Manager Apply ECO Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
Change Manager Preview ECO Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
Choose Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
Collaborate Checklists Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
Collaborate Comments Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
Collaborate Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
Collaborate Manage Notifications Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
Collaborate Notes Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
Compare Designs Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
Condition Dialog Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
Convert to Ring Terminal Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Copy Design Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Create New Design Revision Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Design Assistant Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Design Effectivity Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Design Log Event Filter Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Design Log Filter Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Design Log Viewer Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Design Revision/Build List Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979

December 2023
Table of Contents
Design Rule Checks Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979

Define Rules Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Details Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
DXF Page Settings Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
Edit Border Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
Edit Breakout/Spot Tape Details Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
Edit Build List Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
Edit Capital Configuration Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
Edit Design Properties Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
Edit Effectivity Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Edit File Name Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Edit Multicore or Overbraid Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Edit Objects Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Edit Option Expression Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
Edit Print Region Groups Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
Edit Project Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
Edit Properties Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
Edit Shared Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
Embedded Library Portal Import Configuration Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
Engineering Change Orders Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
Fill Pattern Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
Freeze / Unfreeze Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
Generate Advanced Names Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
Image Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
Import Designs to Project/Copying to Project Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
Import Designs to Project Wizard/Copying to Project Wizard Help . . . . . . . . . . . . . . . . . 986
Manage Designs & Effectivity Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
Managing Collaborate Data Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
Map Equivalent Devices Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
Map Pins/Ports Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
Merge Into Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
New Folder or Rename Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
New Project Dialog Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
New Property Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
Open Project Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
Options (Apply ECO) Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
Part Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
PDF Page Settings Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
Plugin Details Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
Plugins Dialog Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
Print Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
Print to File Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
Project Diagram Settings Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
Project Folders Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
Project Preferences Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991
Project Usages Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992
Properties and Attributes Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992
Query Criteria Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993

December 2023
Table of Contents
Release Designs Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994

Replacing Composite Symbols for Shared Objects Help . . . . . . . . . . . . . . . . . . . . . . . . . . 994
Rules and Constraints Selection Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994
Rule Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
Rules Tab in Properties Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
Save as Function or Device Symbol Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
Select by Attribute/Property Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
Select By Name Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
Select Designs to Copy Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
Set Grid Defaults Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
Select Project Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
Set separation distances Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
Share Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
Split Table Dialog Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
SVG Page Settings Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
Symbol Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
Undoable Operation Confirmation Dialog Box Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
Update Symbol - Options Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
View Design Logs Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
Chapter 13
Capital E/E Insight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 999
Enabling Capital E/E Insight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001
Overview of Studies and Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
Studies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
Creating a Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
Editing a Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
Deleting a Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
Creating a Scenario (and Study) from the Insight Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
Opening a Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1005
Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
Default Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
Creating a Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009
Creating a Metric Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1010
Deleting a Metric Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011
Editing a Metric Element Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011
Deleting a Metric Element Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
Specifying the Architectural Cost of a Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
Viewing Metric Results for the Open Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013
Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015
Taking a Snapshot of Metric Results for Current Design Data . . . . . . . . . . . . . . . . . . . . . 1015
Editing a Snapshot Name and Display Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
Opening a Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
Opening a Snapshot in the Insight Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017
Comparing Snapshots from One Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017
Comparing Snapshots from Different Studies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
Comparing Snapshots from One or More Studies in the Insight Tab. . . . . . . . . . . . . . . . . 1019

December 2023
Table of Contents
Capital E/E Insight Dialog and Field Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020

Calculation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
Compare Snapshots Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
Compare Snapshot With Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1023
Edit Metrics Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026
Edit Scenario Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1029
Edit Snapshot Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1030
Edit Study Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031
Edit Study/Scenario Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
Metrics/Insight Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
Metrics Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
New Scenario Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038
New Study Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039
Snapshot Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
Take Snapshot Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044
Usage Example - Study of Alternative Harness Routing Paths. . . . . . . . . . . . . . . . . . . . . . . 1044
Help Button Landing Pages for Capital E/E Insight Dialog Boxes . . . . . . . . . . . . . . . . . . . . 1047
Calculation Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047
Compare Snapshots Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1047
Compare Snapshot With Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
Edit Metrics Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
Edit Scenario Properties Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
Edit Snapshot Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
Edit Study Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
Edit Study Properties Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
New Scenario Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
New Study Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
Snapshot Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
Take Snapshot Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
Index
Third-Party Information

December 2023
Table of Contents

December 2023
List of Figures
Figure 1-1. String in Client Application Window Banners . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Figure 1-2. Client Auto Update Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Figure 1-3. Example Communication for a Client Application - User Authentication Using OIDC
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Figure 1-4. Example Communication for a Web Application - User Authentication Using OIDC
56
Figure 1-5. Enabled Embedded Library Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Figure 1-6. Enabled Embedded Library Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Figure 1-7. 3Dfindit.com Search Results - Part Number Entered . . . . . . . . . . . . . . . . . . . . . 68
Figure 1-8. 3Dfindit.com Default Home Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 1-9. Example Rendered Part Information Imported from EDM Collaborate. . . . . . . 78
Figure 1-10. A filteredaction secton . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 1-11. Name and Target Values for a Ribbon Action . . . . . . . . . . . . . . . . . . . . . . . . . 103
Figure 1-12. Default Ribbon Before Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Figure 1-13. Ribbon with Plug/Jack/Inline Actions Column Filtered Out . . . . . . . . . . . . . . 104
Figure 1-14. Ribbon with Pin/Inline/Assembly Actions Row Filtered Out . . . . . . . . . . . . . 104
Figure 1-15. Search Tab in Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Figure 1-16. Blue Line Indicating Target Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Figure 1-17. Call Home Package Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Figure 1-18. Call Home Context Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Figure 1-19. Call Home Error Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Figure 2-1. DRC Failures and Issues Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Figure 2-2. Name Ellipsis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Figure 2-3. Name Sub Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Figure 2-4. ECO Cost Only Change Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Figure 2-5. Status Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Figure 2-6. ECO Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Figure 2-7. ECO Console. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Figure 2-8. Hotspot Visualization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Figure 2-9. Hotspot Issue Highlighting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Figure 3-1. Crosshair Mode Cursor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Figure 3-2. Crosshair Mode Cursor with Action Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Figure 4-1. 3D Ribbon Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Figure 4-2. Different Bundle Thicknesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Figure 4-3. separationCategory Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Figure 4-4. Example Separation CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Figure 5-1. Example Maximum Permitted Fillet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Figure 5-2. Dynamic Graphics and Tooltip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Figure 5-3. Set Radius for Fillet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
Figure 5-4. Dynamic Graphics with Reversed Fillet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

December 2023
List of Figures
Figure 5-5. Example with Trimmed and Extended Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . 532

Figure 5-6. Angle between new position and original position . . . . . . . . . . . . . . . . . . . . . . . 533
Figure 5-7. Angle of intersection with another straight line . . . . . . . . . . . . . . . . . . . . . . . . . 533
Figure 5-8. Dynamic Graphics and Tooltip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Figure 5-9. Dynamic Graphics with Fillet Deselected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Figure 5-10. Example of Self-Intersecting Shape Producing Multiple Offset Profiles . . . . . 537
Figure 5-11. Snap point for tangent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Figure 5-12. Extending line at tangent. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Figure 5-13. Line at tangent to curve. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Figure 5-14. Preview of Transform Graphics Action With Tooltip . . . . . . . . . . . . . . . . . . . 544
Figure 5-15. Set Transform Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Figure 5-16. Result of Transform Graphics Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Figure 5-17. Preview of Translate Graphics Action With Tooltip . . . . . . . . . . . . . . . . . . . . 546
Figure 5-18. Preview of Translate Graphics Action With Graphic Segments Deselected . . 546
Figure 5-19. Set Translation Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Figure 5-20. Result of Translate Graphics Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Figure 5-21. Example Segments and Intersections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Figure 5-22. Selecting Multiple Graphic Segments for Trimming . . . . . . . . . . . . . . . . . . . . 549
Figure 5-23. Result of Trimming Multiple Selected Graphic Segments . . . . . . . . . . . . . . . . 549
Figure 6-1. Text Before Flip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562
Figure 6-2. Text After Flip . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563
Figure 8-1. Color Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
Figure 8-2. Color Attribute with Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Figure 8-3. Example Assembly Graphic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616
Figure 8-4. Starting Point. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
Figure 8-5. Make the Slice. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
Figure 8-6. Slice Made . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Figure 8-7. Select Move To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Figure 8-8. Objects Removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Figure 8-9. Selected Objects on New Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644
Figure 8-10. Slot Before Slice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Figure 8-11. Slot After Split . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Figure 8-12. Slice Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Figure 8-13. Block Slice Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Figure 8-14. Separate Blocks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Figure 8-15. Slice Conductors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
Figure 8-16. Slice Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
Figure 8-17. Slicing a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Figure 8-18. Connector Slice Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
Figure 8-19. Separate Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651
Figure 8-20. Slicing a Mated Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Figure 8-21. Sliced Mated Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 652
Figure 8-22. Slice Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Figure 8-23. Device Slice Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Figure 8-24. Separate Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654

December 2023
List of Figures
Figure 8-25. Make the Slice Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655

Figure 8-26. Trimmed Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655
Figure 9-1. Before Factor Increase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
Figure 9-2. After Factor Increase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
Figure 9-3. Source Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
Figure 9-4. First Minimum Width Increase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
Figure 9-5. Second Minimum Width Increase. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 681
Figure 9-6. Insufficient Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
Figure 9-7. More Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683
Figure 9-8. Source Diagram Linestyle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
Figure 9-9. Inconsistent Linestyle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
Figure 9-10. Correctly Rendered Linestyle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 684
Figure 9-11. Source Diagram Fill Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
Figure 9-12. Inconsistent Fill Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 685
Figure 9-13. Correctly Rendered Fill Pattern . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 686
Figure 10-1. An Example Collaborate Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689
Figure 10-2. Example Collaborate Note . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
Figure 10-3. Example Collaborate Checklist Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Figure 11-1. Supported and Unsupported Design Comparisons - Capital Logic Designer. . 720
Figure 11-2. Supported and Unsupported Design Comparisons - Other Applications . . . . . 721
Figure 11-3. Selected To Do Task (Delta). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
Figure 11-4. Applied Change in To Do List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Figure 11-5. To Do Tab in the Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Figure 11-6. Simple Logical Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
Figure 11-7. Related Wiring Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
Figure 11-8. Deltas Without TRAVERSE_INTERNAL_LINKS Property . . . . . . . . . . . . . 727
Figure 11-9. TRAVERSE_INTERNAL_LINKS with Value of yes . . . . . . . . . . . . . . . . . . . 727
Figure 11-10. Deltas with TRAVERSE_INTERNAL_LINKS Property . . . . . . . . . . . . . . . 727
Figure 12-1. Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
Figure 12-2. MLC2 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 789
Figure 12-3. Comparison ExampleA v ExampleB Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
Figure 12-4. Comparison ExampleA v ExampleB Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 791
Figure 12-5. Comparison ExampleB v ExampleA Part 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 792
Figure 12-6. Comparison ExampleB v ExampleA Part 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
Figure 12-7. Edit Effectivity Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Figure 12-8. Edit Objects Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Figure 12-9. Properties Error Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Figure 12-10. Example Name Column Filter Popup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
Figure 12-11. Object Type Filter Toolbar Capital Harness Designer and Capital Harness
Designer Modular . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818
Figure 12-12. Object Type Filter Toolbar Capital Logic Designer . . . . . . . . . . . . . . . . . . . . 819
Figure 12-13. Clip 2 Deleted Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
Figure 12-14. Drag Copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
Figure 12-15. Example Popup Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821
Figure 12-16. Hidden Column . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821

December 2023
List of Figures
Figure 12-17. Map Pins Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834

Figure 12-18. Drafting Settings Dialog Box Showing Mouse Move Increments . . . . . . . . . 857
Figure 12-19. Drafting Settings Dialog Box Showing Line Stretch Locking Keys . . . . . . . 857
Figure 12-20. Symbol Selection Dialog Box Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
Figure 12-21. Symbol on the Symbols Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
Figure 12-22. Symbol on the Cursor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
Figure 12-23. Black Node with Circle on Top . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
Figure 12-24. Moving the Symbol. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
Figure 12-25. Original Node Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
Figure 12-26. Moved Node Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
Figure 12-27. Sample Dialog Box Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Figure 12-28. Simulate Change Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Figure 12-29. Condition Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
Figure 12-30. Operators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 939
Figure 12-31. Manage Associate Objects Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 947
Figure 12-32. Checklist Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
Figure 12-33. Collaborate Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950
Figure 12-34. Comments Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
Figure 12-35. Example Dialog Box: Edit Collaborate Design Export Options Dialog Box . 954
Figure 12-36. Notes Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957

December 2023
List of Tables
Table 1-1. API, Plugin, and Web Service Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Table 1-2. Capital Application Launcher Command Line Options . . . . . . . . . . . . . . . . . . . 43
Table 1-3. Remote Capital Manager Argument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Table 1-4. Services Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Table 1-5. Example Combinations of Arguments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Table 1-6. Tasks Tab Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Table 1-7. Example filteredaction Sections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Table 1-8. Search Scope Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Table 1-9. Additional Search Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Table 1-10. Launch Pane Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Table 1-11. Profiling Data and Heap Dump Zip Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Table 2-1. Project Preferences for Capital Analysis Designs . . . . . . . . . . . . . . . . . . . . . . . . 132
Table 2-2. Project Preferences for Capital Harness Process Designer, Capital Work Instruction
Publisher, and Capital Harness Costing Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Table 2-3. Project Preferences for Capital Device Modeler . . . . . . . . . . . . . . . . . . . . . . . . . 133
Table 2-4. Project Preferences for Capital Harness Designer and Capital Harness Designer
Modular Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Table 2-5. Project Preferences for Capital Systems Integrator Designs . . . . . . . . . . . . . . . . 159
Table 2-6. Project Preferences for Capital Logic Designer Designs . . . . . . . . . . . . . . . . . . 169
Table 2-7. Project Preferences for Capital Project Manager Designs . . . . . . . . . . . . . . . . . 201
Table 2-8. Project Preferences for Capital Wiring Integrator Designs . . . . . . . . . . . . . . . . . 202
Table 2-9. Project Preferences for Capital Systems Modeler Designs . . . . . . . . . . . . . . . . . 210
Table 2-10. Project Preferences for Design Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Table 2-11. General Project Preferences Applicable to all Applications . . . . . . . . . . . . . . . 217
Table 2-12. Project Preferences - Checks Node Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Table 2-13. Release Level Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Table 2-14. Design Rule Checks Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Table 2-15. DRC Running Modes for Capital Systems Integrator . . . . . . . . . . . . . . . . . . . . 251
Table 2-16. Invalid wire path - Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384
Table 3-1. Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Table 3-2. Stroke Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Table 4-1. Cross-highlighting of Selected Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Table 4-2. Objects Added to 3D Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Table 11-1. Trace Tab Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
Table 11-2. Trace Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 710
Table 11-3. To Do List Tab Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
Table 12-1. Choose Options Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
Table 12-2. Edit Project Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Table 12-3. Edit Properties Dialog Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749
Table 12-4. Import Designs to Project/Copying to Project Dialog Box Contents . . . . . . . . 750

December 2023
List of Tables
Table 12-5. Import Designs to Project Wizard/Copying to Project Wizard Dialog Box Contents
754
Table 12-6. New Project Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
Table 12-7. Open Project Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
Table 12-8. Options Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 769
Table 12-9. Project Folders Dialog Box Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
Table 12-10. Fields in the Project Preferences Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . 776
Table 12-11. Select Designs to Copy Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . 777
Table 12-12. Applicable Options Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
Table 12-13. Connections Tab (Properties Dialog Box) Contents . . . . . . . . . . . . . . . . . . . . 783
Table 12-14. Cross-references Tab (Properties Dialog Box) Contents . . . . . . . . . . . . . . . . 785
Table 12-15. Compare Designs Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
Table 12-16. Design Revision/Build List Selection Dialog Contents . . . . . . . . . . . . . . . . . 794
Table 12-17. Design Rule Checks Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
Table 12-18. Edit Assemblies Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
Table 12-19. Edit Assembly Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
Table 12-20. Edit Breakout/Spot Tape Details Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
Table 12-21. Properties Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
Table 12-22. Rules Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
Table 12-23. Scopes Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
Table 12-24. ECO Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 804
Table 12-25. Edit Effectivity Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
Table 12-26. Edit Graphical Attributes Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . 808
Table 12-27. Edit Name Text Attributes Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . 811
Table 12-28. Edit Option Expression Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . 820
Table 12-29. General Tab (Properties Dialog Box) Contents . . . . . . . . . . . . . . . . . . . . . . . . 823
Table 12-30. Generate Advanced Names Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . 827
Table 12-31. Map Equivalent Devices Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . 833
Table 12-32. Map Pins Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
Table 12-33. Name Selection Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
Table 12-34. New/Edit Assemblies Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 839
Table 12-35. Part Selection Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
Table 12-36. Effects of Override Symbol Styling and Master Setting Combinations . . . . . 848
Table 12-37. Select by Attribute/Property Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . 849
Table 12-38. Select by Name Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
Table 12-39. Project Usages Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 853
Table 12-40. Add Text Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
Table 12-41. Edit Border Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
Table 12-42. Fill Pattern Selection Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 860
Table 12-43. Image Selection Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
Table 12-44. Edit Properties - Propertied Graphic Dialog Box Contents . . . . . . . . . . . . . . 862
Table 12-45. Symbol Selection Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
Table 12-46. Update Symbol - Options Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . 870
Table 12-47. Set Grid Defaults Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 872
Table 12-48. Split Table Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873

December 2023
List of Tables
Table 12-49. Applicable Changes Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 876

Table 12-50. Apply Change Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
Table 12-51. Batch Translate Dialog Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880
Table 12-52. Capital Systems Integrator Design Filter Dialog Box Contents . . . . . . . . . . . 884
Table 12-53. Change Manager Apply ECO Dialog Box Contents . . . . . . . . . . . . . . . . . . . . 886
Table 12-54. Change Manager Preview ECO Dialog Box Contents . . . . . . . . . . . . . . . . . . 892
Table 12-55. Configure Import Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
Table 12-56. Edit Capital Configuration Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . 898
Table 12-57. Engineering Change Orders Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . 901
Table 12-58. Engineering Change Orders Output Window . . . . . . . . . . . . . . . . . . . . . . . . . 906
Table 12-59. New Property Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
Table 12-60. Options (Apply ECO) Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 912
Table 12-61. Plugins Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
Table 12-62. Plugin Details Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915
Table 12-63. Query Criteria Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916
Table 12-64. Release Designs Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Table 12-65. Report Builder Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
Table 12-66. CGM Page Settings Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 924
Table 12-67. DXF Page Settings Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925
Table 12-68. Edit File Name Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
Table 12-69. Edit Print Region Groups Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . 927
Table 12-70. PDF Page Settings Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 929
Table 12-71. Print Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
Table 12-72. Print to File Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
Table 12-73. Project Diagram Settings Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . 935
Table 12-74. SVG Page Settings Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
Table 12-75. Condition Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
Table 12-76. Constraint Selection Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 941
Table 12-77. Define Rules Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942
Table 12-78. Rule Selection Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
Table 12-79. Rules Tab in Properties Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . 944
Table 12-80. Undoable Operation Confirmation Dialog Box Contents . . . . . . . . . . . . . . . . 960
Table 12-81. Design Log Event Filter Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . 962
Table 12-82. Design Log Filter Options Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . 963
Table 12-83. Design Log Viewer Dialog Box (Non-Connector Logs) Contents . . . . . . . . . 964
Table 12-84. Design Log Viewer Dialog Box (Capita Connector Logs) Contents . . . . . . . 964
Table 12-85. View Design Logs Dialog Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
Table 13-1. Calculation Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
Table 13-2. Compare Snapshots Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1022
Table 13-3. Compare Snapshot With Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . 1023
Table 13-4. Edit Metrics Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1026
Table 13-5. Edit Scenario Properties Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . 1029
Table 13-6. Edit Study/Scenario Property Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . 1032
Table 13-7. Metrics/Insight Tab Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
Table 13-8. New Scenario Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038

December 2023
List of Tables
Table 13-9. New Study Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039

Table 13-10. Snapshot Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
Table 13-11. Take Snapshot Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044

December 2023
Chapter 1
Introduction
This user guide contains information on the functions that are common between the Capital™
design applications. These functions include the handling of projects and designs, the layout of
design objects, the ability to add comment graphics to a diagram, Capital Team Collaborator,
Capital Change Validator, and Capital E/E Insight.
Refreshing External Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Viewing the Details of Installed Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Design Inspectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Object Attribute Descriptions for Use in Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . 34
Usage Example - Loading an Extensibility Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Product Excellence Program. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
API, Plugin, and Web Service Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Location of Application Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Capital Application Launcher and Application Command Line Options . . . . . . . . . . . 43
Specifying the Memory Allocation of Capital Applications. . . . . . . . . . . . . . . . . . . . . . . 49
Displaying a String in the Window Banner of Applications . . . . . . . . . . . . . . . . . . . . . . 50
Capital Stop Services - Command Line Arguments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Encrypting Text Strings for Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Feature Licensing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Automatic Update of Clients. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Multi Factor Authentication Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Enablement of Multi Factor Authentication Using OIDC . . . . . . . . . . . . . . . . . . . . . . . . . 56
Creating Additional Icons in the Capital Application Launcher . . . . . . . . . . . . . . . . . . 58
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
User Interface Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
User Interface Toggle View Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Embedded Library Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Enabling The Embedded Library Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Using The Embedded Library Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Configuring Internal Part Numbers on Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

December 2023
Note - Viewing PDF files within a web browser causes some links not to function. Use HTML for full navigation.
Introduction

Embedded Integration Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Adding a Library Part from EDM Collaborate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Launching Capital Component Manager from this Application . . . . . . . . . . . . . . . . . . 78
Launching Capital Symbol Designer from this Application . . . . . . . . . . . . . . . . . . . . . . 79
Diagram Language Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Language Dictionary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Active Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Chinese and Japanese Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Saving a Language Dictionary CSV File with UTF-8 or Non-Ascii Characters . . . . . . . . 84
Importing a Language Dictionary CSV File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Exporting a Language Dictionary CSV File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Refreshing Language Dictionary Data in a Design Application . . . . . . . . . . . . . . . . . . . . 87
Adding a Translation of an Existing Translatable Term for the Currently Active Language 88
Adding a Translation of a New Translatable Term for the Currently Active Language . . 89
Converting Text Strings into Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Running Capital Tasks in the Background (Flexible Execution Model) . . . . . . . . . . . . 91
Modular) in the Background. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Running FMEA Scenarios in Capital Analysis in the Background . . . . . . . . . . . . . . . . . . 94
Creating Audit Reports When Capital Analysis Operations are Run in the Background . 95
Running ICD Publication from Capital Logic Designer in the Background . . . . . . . . . . . 96
Running Documentation Package Generation in Capital E/E Publisher in the Background
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Searching for an Action on the Ribbon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Configurable Ribbon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
Filtering Out Ribbon Actions Based on Design Type and Abstraction . . . . . . . . . . . . . . . 102
Searching for an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Reordering Browser Tabs on the Bottom Left of a Design Application. . . . . . . . . . . . . 108
Undocking Browser Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Creating and Using Quick Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Launch Pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Sort Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Call Home Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Specifying Preferences for Call Home Error Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Manually Creating a Filtered Call Home Error Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

December 2023
Introduction
Refreshing External Data
Capturing Performance Profiling Data and Heap Dump Data. . . . . . . . . . . . . . . . . . . . 118

You can refresh data that has been updated outside of the open design in which are you
working. Press Space Bar and enter Refresh, then in the Search Ribbon dropdown list select one
of the items in the list below.
Note
The items in the list below are only available in applications that they are relevant to.
• Everything
Refreshes all the items in this list that are relevant to the application you are working in.
• Symbol Libraries
Refreshes symbol library data when it has been modified in Capital Symbol Designer.
• Options
Refreshes option and variant data for a design when they have been modified in other
Capital applications.
• Functional Module Codes
Refreshes Functional Module Code data when it has been modified in other Capital
applications.
• Production Module Codes
Refreshes Production Module Code data when it has been modified in other Capital
applications.
• Shared Objects
Refreshes shared object data for a design when it has been modified in other Capital
applications.
• Designs
Refreshes design data for the design in which you are working when it has been
modified in other Capital applications.
• Library Parts
Refreshes cached library part data when it has been modified in Capital Component
Manager.
• Patterns

December 2023
Introduction
Refreshes SBOM Pattern data when it has been modified in Capital Project Manager. It
does not refresh the SBOM pattern based on changes to the design. You should close
and reopen the SBOM to see any changes.
• Design Connectivity
This item is applicable when multi-user access is enabled within Capital Logic
Designer. When multiple users are working within the same design, you can select this
option to refresh the design connectivity in your session. Objects which have been
modified in other sessions and are visible in the current session will be updated. For
example, a design-wide device may have been renamed in another session. Refreshing
design connectivity will update the device’s name in the current session.
• Cross References
Refreshes cross-reference data when it has been modified in other Capital applications.
• Language Dictionary
Refreshes any Diagram Language Translation changes made in other Capital
applications.
• ICDs
Refreshes ICD data when it has been modified in Capital Device Modeler.
• Change Policies
Refreshes change policy data for the design in which you are working when it has been
modified in Capital Project Manager.
• Synchronize Logical Changes
Refreshes design data relating to associated Capital Logic Designer designs when it has
been modified in Capital Logic Designer.
• Synchronize Functional Changes
Refreshes design data relating to associated Functional designs when it has been
modified in other applications.

December 2023
Introduction
Extensibility Plugins
Compiled plugins - written in Java or JavaScript - provide custom actions and are placed into
the \plugins sub-directory of the Capital installation location.
These plugins are loaded when an application is started, and can be inspected from within an
application.
Note
For more information about developing and using extensibility plugins, see the
PluginDevelopment.pdf file that is located in the doc\plugin folder of your Capital
installation.
The function of a custom action is entirely dependent upon the plugin design; refer to the user
documentation supplied with the plugin for information on using the action.
Viewing the Details of Installed Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Design Inspectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Object Attribute Descriptions for Use in Extensibility Plugins. . . . . . . . . . . . . . . . . . . . 34
Usage Example - Loading an Extensibility Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Product Excellence Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Viewing the Details of Installed Extensibility

Plugins
You can view the details of the extensibility plugins that you have installed. Compiled plugins -
written in Java or JavaScript - provide custom actions and are placed into the \plugins sub-
directory of the Capital installation location.
Procedure
1. Press Space Bar and enter Plugins.
The Plugins Dialog Box is displayed.
2. Select a plugin in the Available Plugins table and click Details.
Results
The Plugin Details Dialog Box is displayed, allowing you to view the details of the selected
plugin.

December 2023
Introduction
Reloading Extensibility Plugins
Related Topics
Design Inspectors
Custom Action Plugins
Usage Example - Loading an Extensibility Plugin

You can reload extensibility plugins, or load new plugins, when they have been modified in
your Capital installation and you do not want to restart the application.
Procedure
1. Press Space Bar and enter Plugins.
2. Click Reload All on the Plugins Dialog Box.
3. Alternatively, click System > Reload Plugins from the Capital ribbon.
Results
• The Available Plugins table is updated and any new or modified plugins are available to
use in your Capital applications.
Related Topics
Viewing the Details of Installed Extensibility Plugins
Design Inspectors
Design Inspectors
The Design Inspector is available as an interface to expose the functionality of custom plugins
that you may want to create to extend the Capital applications. Once a plugin has been loaded, a
new tab will be added to the inspector, from where all of the plugin functions can be accessed.
Note
If there are multiple tabs, you can drag and drop the tabs to reorder them. When you close
and reopen the Design Inspector it remembers the order of the tabs and which tab was last
active.
You access the Design Inspector by pressing Space Bar and entering Show Design Inspector.

December 2023
Introduction
The creation and application of plugins is detailed in a separate document called

CustomDesignInspectorDevelopment.pdf, which can be found in the \doc\plugin folder of your
Capital home directory.
Once the plugin has been placed in the correct location, check it has been loaded and refresh the
installed plugins list if necessary. Open the required Capital application, press Space Bar and
enter Plugins. If the custom plugin is not displayed in the Available Plugins list, click the
Reload All button to refresh the list. Once you have verified that the plugin is present, close the
dialog box.
Related Topics

Custom actions are customer-delivered functions that are exposed in the Capital user interface.
Implemented using the plugin architecture, these actions allow the extensibility of the Capital
functionality on a client-by-client basis. Custom actions are delivered as a compiled plugin -
written in Java or JavaScript - which is placed into the \plugins sub-directory of the Capital
installation location.
These plugins are loaded when the application is started, and can be inspected from within the
Capital tools; see “Viewing the Details of Installed Extensibility Plugins” on page 31 for more
information.
Note
A reference document describing the construction and deployment of custom actions is
available. Refer to the document CustomActionDevelopment.pdf in the \doc\plugin sub-
directory of your Capital installation location.
Custom actions are exposed in the user interface in three ways:
• On the ribbon. Press Space Bar and enter Custom. The name of the action - as coded in
the plugin - is displayed as a selectable option.
• In the context-menu, accessed by right-clicking an object in the design browser. Any
installed custom actions available are offered beneath a Custom > menu option.
• In the context-menu, accessed by right-clicking on an object on the diagram. Any
installed custom actions available are offered beneath a Custom > menu option.

December 2023
Introduction
Object Attribute Descriptions for Use in Extensibility Plugins
The function of a custom action is entirely dependent upon the plugin design; refer to the user
documentation supplied with the plugin for information on using the action.
Tip
If you have a large number of custom actions defined via plugins in your plugins folder you
can organize custom actions into a menu structure under the Custom menu in either the
ribbon or contextual menu, using groups, sub-groups and separators. The Override Plugin Path
User Permission must be enabled in order to categorize your plugins. For further information
see Override Plugin Path User Permission in the Capital Access Manager User Guide.
Related Topics
Design Inspectors
Object Attribute Descriptions for Use in

If you are using extensibility plugins, you can use object attributes when creating the plugins.
For a full list of available attributes, see the AttributeList.html file located in the /doc/plugin/api
directory of your installation.

This usage example demonstrates how to load an extensibility plugin into your Capital
installation and how to use a custom constraint from a plugin.
The plugin in this example is for Capital Systems Integrator and utilizes a custom “ Wiring by
Attribute/Property” constraint to every signal, except those that are selected in the Topological
Plane Browser Window during batch operations, such as Composite Wiring Synthesis.
This effectively provides the ability to run these actions only on selected signals. This makes it
very easy to synthesize different subsets of signals without even changing the constraint - you
just have to select a different set of signals.
The normal scenario for using this plugin is when CWS has already run for all signals, some
signals have been edited and you want to run CWS again only for those edited signals.

December 2023
Introduction
Prerequisites
• The plugin must have been developed and compiled. For more information about
developing extensibility plugins, see the PluginDevelopment.pdf file that is located in
the doc\plugin folder of your Capital installation.
• This example uses a Quick Start - Automotive Generative project.
Procedure
1. Obtain the compiled plugin and add it to your Capital installation:
a. In this example, you download a UnselectedSignals.zip file that contains the plugin
b. Open the UnselectedSignals.zip file and copy the UnselectedSignals.jar file into the
\plugins sub-directory of the Capital installation location.
2. Check that the plugin is available in the Capital Systems Integrator application:
a. Open the Capital Systems Integrator application
b. Press Space Bar and enter Plugins: the Plugins Dialog Box is displayed. The
UnselectedSignals plugin is listed in the table of plugins that have been loaded in the
software.
Note
The plugin might not be listed if Capital Systems Integrator was already running
when you added it to your installation. In this case, click Reload All on the
Plugins dialog box. This will load the plugin.
3. Use the functionality that has been added by the plugin.
Note
The steps from this point onwards depend on the plugin that you are using. In this
example, you will apply the custom constraint from the plugin to a topological plane
and run Composite Wiring Synthesis (CWS) for selected signals.
a. Open the Quick Start - Automotive Generative project in Capital Systems

Integrator.

December 2023
Introduction
b. Open the Vehicle Topology design.
c. In the Topological Plane Browser Window, right-click the Vehicle Topology plane
and select Properties.
The Plane: Vehicle Topology dialog box is displayed where you edit properties and
attributes for it.
d. On the Rules tab, click Add Constraint; the Constraint Selection dialog box is
displayed.
e. Select the Wiring by Attribute/Property constraint and click OK; the standard
template for the constraint is added to the Rules tab.
f. Click the icon; a dropdown list is displayed from which you select
UnselectedSignals.

December 2023
Introduction
Product Excellence Program
g. The “ Wiring by Attribute/Property” constraint template is replaced with the

following:
h. Click OK to exit the Plane: Vehicle Topology dialog box.

i. In the Topological Plane Browser Window, select the signals for which you want to
run CWS, press Space Bar and enter CWS; the Abstract & Composite Wire
Synthesis dialog box is displayed.
j. You do not want to update harness options or generate harness levels again so select
Finish Synthesis and click Go; CWS re-generates the wiring for those selected
signals only.
Related Topics
Design Inspectors
Product Excellence Program

The Product Excellence Program collects information about how you use your software. This
information helps us to improve our product features and functionality. Participation in the
program is voluntary and can be turned on or off in System Preferences.
For further information about how this works, see the “Product Excellence Program” topic in
the Capital Project Manager User Guide.
API, Plugin, and Web Service Documentation

The doc folder in your Capital installation contains various documents related to API, plugin
and web service development.

December 2023
Introduction
Table 1-1. API, Plugin, and Web Service Documents

Document or Folder Description
bridges/Harness X2ML This document describes the various elements and
Schema.pdf attributes as defined in the Capital 3D Harness XML (or
HX2ML) schema.
HX2ML is a simplified version of the Capital Project
Manager XML which is used to store design data (and
related project data). This format is described by its XML
schema which can be found in %CAPITAL_HOME%\
dtd\bridgesharness.xsd.
Capital applications always directly interact with the
HX2ML format through Capital Connectors. For
interaction between any data format and Capital,
HX2ML always acts as the intermediary data format.
bridges/api This folder contains descriptions of the classes available
in the Capital Connectors SDK.
plugin/ Capital has a feature to attach auxiliary custom data to a
AttachedDataAccessGuide Capital design of any type, using the Extensibility API or
.pdf REST API. Multiple types of data may be attached to a
single Capital design. Once created and attached, such
data can be read, updated or deleted using these APIs.
This document describes these API with examples.
plugin/ This document contains process, description, and
CapitalConnectAndConver examples on how to use API to query ANS tables, to
geAPIGuide.pdf write Custom Taggers, to write custom comparators for
To-Do, to write custom relationships for Trace.
plugin/ This document describes the process and interfaces for
CustomActionDevelopme developing plugins that are available as actions in the
nt.pdf Capital applications like Capital Logic Designer, Capital
Wiring Integrator, Capital Systems Integrator, Capital
Harness Designer, and so on.
plugin/ This document describes how to develop a custom auto
CustomAutoLinkDevelop link plugin
ment.pdf
plugin/ This document describes with examples, the three
CustomBridgeProcessorDe Extensibility interfaces used to manipulate the data
velopment.pdf during Bridge Out and Bridge In operations from design
applications.
CustomBuildListContentU This document describes the process of developing a
pdaterDevelopment.pdf custom plugin for dynamicallypopulating/updating the
Build List designs list.

December 2023
Introduction
Table 1-1. API, Plugin, and Web Service Documents (cont.)

CustomChangePolicySelec developing a plugin to select a change policy based on
torDevelopment.pdf the current application context (current project, design,
and so on). This change policy is then used by the
application to restrict certain edits.
plugin/ This document describes how to develop a custom
CustomCollaborationLink Collaboration Link plugin. Collaboration capabilities
Development.pdf have capabilities like Comments, Notes, and Checklists.
There are requirements to store links to external systems
like Teamcenter and Polarion. This document discusses
plugin development for another Collaboration capability
called Link. This Capability can be used to link Capital
objects to external objects, for example, Teamcenter
Requirements, Polarion Requirements, Polarion
Testcases, and so on.
CustomConstraintDevelop developing plugins that are available as custom
ment.pdf constraints in the Capital applications like Capital Logic
Designer, Capital Wiring Integrator, Capital Systems
Integrator, Capital Harness Designer, and so on.
plugin/ This document describes how to develop Custom Design
CustomDesignInspectorDe Inspectors for the Capital design applications like Capital
velopment.pdf Systems Integrator. The inspector allows to create
custom views of the design (and selected parts of that
design) to inspect design data in a suitable format.
CustomDRCDevelopment. developing plugins that are available as DRCs in the
pdf Capital applications like Capital Logic Designer, Capital
Wiring Integrator, Capital Systems Integrator, Capital
Harness Designer, and so on.
CustomHarnessProcessor developing custom harness processors. Such processors
Development.pdf can replace or supplement existing engineering
processors (for example, bundle size calculation) in
Capital Harness Designer or Capital Harness Designer
Modular.
plugin/ This document covers the details of how to write custom
CustomLibraryExportImp filters to exclude parts during export or import of Library
ortFiltersForCEADevelope Parts using Capital Library Synchronizer.
ment.pdf

December 2023
Introduction

plugin/ This document describes ways of developing custom
CustomReportDevelopme reports for Design tools and Capital E/E Reporter.
nt.pdf
CustomSBOMCostResult developing custom cost result exporters in Capital
ExporterDevelopment.pdf Harness Process Designer or Capital Work Instruction
Publisher.
CustomSBOMOperationD developing custom SBOM operations in Capital Harness
evelopment.pdf Process Designer or Capital Work Instruction Publisher.
It contains a detailed description of the SBOM
generation engine, which invokes those custom
operations.
plugin/ This document describes the process and interface for
CustomScopingDevelopm developing custom scoping plugins which are used in
ent.pdf Capital applications for the selection of Library
components.
plugin/ This document describes how to develop a custom
CustomSecurityPluginDev security plugin for delegated authentication or ticket
elopment.pdf based authentication.
plugin/ This document describes the interfaces available for
CustomTableDevelopment developing plugins tables that are used across Capital
.pdf applications.
CustomTaskDevelopment. developing plugins that are available as tasks which can
pdf be executed by Capital Integration Server in the
background.
plugin/ Capital can publish data to ENOVIA. Sometimes there is
CustomValidatorAndProce a need to validate the data being published and to provide
ssorDevelopmentForPublis additional documents to be attached to the data being
hToENOVIA.pdf published. Hence there is a need for plugins which users
can write, to perform above operations at runtime.
plugin/ Capital can publish data to Teamcenter as well as import
CustomValidatorAndProce the previously published data from Teamcenter.
ssorDevelopmentForPublis Sometimes there is a need to provide item details where
htoTeamcenter.pdf data will be published, additional attributes, and datasets
to be attached to the data being published. This document
provides details of the API to achieve this, using
examples.

December 2023
Introduction

CustomWorkbookProvider developing custom workbook providers, which are
Development.pdf invoked by the workbook generation engine to extract
the data to be displayed from the input SBOMs.
plugin/ This document describes the process for developing
LibraryCustomActionDev Custom Action plugins for Capital Component Manager.
elopment.pdf
plugin/ This document describes the general plugin framework
PluginDevelopment.pdf for Capital applications and how the plugins should be
developed and deployed.
webservice/ This document describes the REST resources exposed in
RestServiceDevelopment. Capital that can be leveraged by externalapplications to
pdf integrate with Capital.
webservice/ This document describes the process for integrating
WebServiceDevelopment. external applications with Capital, using various web
pdf services, with an example for each. It also provides
details about how external web services may be invoked
by Capital through configured hooks.

December 2023
Introduction
Location of Application Log Files
Location of Application Log Files

Whenever you run a Capital application, an application specific LOG file is created. Log files
contain information related to the running application instance only. The next time the
application is run, the previous log file is overwritten (default), removed, or retained depending
on configuration settings.
Where are the log files?
Capital writes application log files to a temporary folder. By default, these files are placed
within the %TEMP% folder on your computer.
On many computers, there are two TEMP variables; one for the system and one for the user.
Log files for services (Capital Manager, Capital Integration Server, and so on) are placed in the
system variable TEMP location. Application log files are placed in the user variable TEMP
location.
Note
In a two or three tier installation there are log files on the Capital Manager server computer
and log files on the client computers.
If you are gathering the log files for Capital customer support, zip the entire TEMP folder and
indicate whether it from a client computer or server computer.
If you are running Windows 7, Windows 8.1, or Windows 10, the %TEMP% folder is under the
user’s directory by default. However, if you have started Capital server applications that are
registered as Windows services, log files are written to C:/Windows/Temp.
If you are running Windows Server 2008, Windows Server 2012, or Windows Server 2016,
these log files will be automatically removed if the machine is restarted or if the user logs off,
therefore any required log files should be copied to a safe location prior to restarting or logging
off.
Log File Configuration

Capital allows you to configure what happens to existing application log files each time an
application is run. Existing log files can be overwritten, retained, or removed based on
configuration settings. By default, existing log files are overwritten.
How your file system interacts and maintains application log files is defined in the
loggingprops.xml configuration file, located in the <install_location>/config directory. Each
installation of Capital has its own loggingprops.xml file, so client and server installations can
use different settings to retain log files.

December 2023
Introduction
Capital Application Launcher and Application Command Line Options
Within this config file, when the element uniquelogname is enabled, log files will be created
with the current date and time appended to their names to make them unique. As a unique log
file will be created each time an application is started, a log file cleanup mechanism is required
to avoid over-accumulation of log files. So if uniquelogname is enabled, a log file cleanup
mechanism is also enabled by default.
Comments within the loggingprops.xml file explain the different log file cleanup configuration
options available, and how to use them.
Note
Only log files matching the following criteria will be deleted in the cleanup mechanism:
• Log file was created by the application that is running, for example,
CapitalHarnessDesigner will only delete CapitalHarnessDesigner logs.
• Log file was created for the current user.
• Log file matches the generated file name pattern.
If the loggingprops.xml file does not exist, or if it does not contain a valid entry, log files will be
deleted after 7 days to avoid over-accumulation of files.
Capital Application Launcher and Application

Command Line Options
When starting the Capital Application Launcher or an application, you can use a command line
with additional options (arguments). You can use these command line options to create a
shortcut for running the Capital Application Launcher or applications in different environments
(for example, a production sever or a development server).
The following command line options are available.
Table 1-2. Capital Application Launcher Command Line Options
Argument Options Description
nosplash true/false Specifies whether a splash screen is displayed
before the application starts.
For example, to prevent the splash screen
displaying:
C:\Program Files\Siemens\Capital\bin\
CapitalSystemsIntegrator.exe -nosplash=true

December 2023
Introduction
Table 1-2. Capital Application Launcher Command Line Options (cont.)

logname name Specifies the username that is added to the name
of log files created by the applications.
For example, to add the name user1:
CapitalApplicationLauncher.exe -
logname=user1
A log file for Capital Application Launcher will
then have the name
CapitalApplicationLauncher_user1.log.
username username Specifies the username with which you are
starting the Capital Application Launcher or
application. This takes an encrypted value.
For example, to start the Capital Application
Launcher with username system and password
manager:
username=L+eGP3hQcLm1O4dUmfMLnA== -
password=5RgPALm7odU94TcXZCWQ==
password password Specifies the password with which you are
starting the Capital Application Launcher or
application. This takes an encrypted value.
For example, to start the Capital Application
Launcher with username system and password
manager:
username=L+eGP3hQcLm1O4dUmfMLnA== -
password=5RgPALm7odU94TcXZCWQ==

December 2023
Introduction

cisconfig path to Specifies the path to the
capitalintegrationserver capitalintegrationserverconfiguration.xml
configuration.xml configuration file to use for starting the Capital
relative to installation Integration Server. The path must be relative to
directory your installation directory.
For example, to use a
production_capitalintegrationserverconfiguratio
n.xml file in the config directory of your
installation:
cisconfig=config\
production_capitalintegrationserverconfiguratio
n.xml
clientprops path to clientprops.xml Specifies the path to the clientprops.xml
relative to installation configuration file to use for running the Capital
directory Application Launcher or application.
For example, to use a
production_clientprops.xml file in the config
directory of your installation:
clientprops=config\production_clientprops.xml

December 2023
Introduction

adaptorconfigfile absolute path to adaptor Specifies the path to the adaptors.xml
configuration file configuration file to use with applications. The
path must be absolute.
For example, to use an adaptors.xml file in a \
adaptors\production_environment\ sub-directory
of your installation:
adaptorconfigfile=C:\Program Files\Siemens\
Capital\adaptors\production_environment\
adaptors.xml
If a file path contains a space, the entire
argument must be encased within double quotes.
For example:
CapitalApplicationLauncher.exe “-
adaptorconfigfile=C:\Program Files\Siemens\
Capital\adaptors\production_environment\
adaptors.xml”
Note: The bridge.properties file is picked up
from the resources folder of the folder
containing the adaptors.xml configuration file.
Additionally, in the adaptors.xml file, the
properties file path for each adaptor is relative to
the folder containing the adaptors.xml.

December 2023
Introduction

pluginfolder absolute path to plugin Specifies the path to the plugin folder to use with
folder applications. The path must be absolute.
For example, to use a \plugins\
production_plugins sub-directory in your
installation:
<install dir>\Capital\bin\
pluginfolder=<install dir>Capital\plugins\
production_plugins
If a file path contains a space, the entire
argument must be encased within double quotes.
For example:
<install dir>\Capital\bin\
CapitalApplicationLauncher.exe “-
pluginfolder=<install dir>\Capital\plugins\
production_plugins”
Note: This replaces the default plugin folder.
It does not add an additional plugin folder
alongside the default.
To use this argument your user account must
have the Override Plugin Path permission (set in
Capital Access Manager). See “Permissions” in
the Capital Access Manager User Guide.

December 2023
Introduction

title title Can be used only with the Capital Application
Launcher, not with individual applications.
Specifies a title that is displayed on the Capital
Application Launcher and on applications started
from the Capital Application Launcher.
For example, if you want to display “Production
Environment” on the Capital Application
Launcher and applications:
<Installation_directory>\bin\
CapitalApplicationLauncher.exe "-
title=Production Environment"
Note the use of "" around the entire argument.
This is required because of the space between the
words Production and Environment.
Xmx<value> value Can be used with the Capital Application

Launcher or individual applications.
Specifies the maximum amount of memory that
Capital Application Launcher or the application
being started can use.
For full details and examples, see “Changing the
Application Memory Allocation Using
Command Line Parameters” in the Capital
Project Manager User Guide.

December 2023
Introduction
Specifying the Memory Allocation of Capital Applications

appmx value Can be used with the Capital Application
Launcher or individual applications.
Specifies the maximum amount of memory that
an application started from the Capital
Application Launcher or from within the
application being started can use can use.
Note: Examples of secondary applications
launched from within another application are
Capital Symbol Designer and Capital
Component Manager, which can be started from
the ribbon in design applications like Capital
Logic Designer.
For full details and examples, see “Changing the
Application Memory Allocation Using
Command Line Parameters” in the Capital
disabletopology Not applicable Specifies that you are launching Capital Logic
Designer without Capital Wiring Integrator.
For example:
CapitalLogic.exe -disabletopology
If you do not use Capital Wiring Integrator, you
should start Capital Logic Designer without it so
that you do not check out a Capital Wiring
Integrator license.
Specifying the Memory Allocation of Capital

Applications
You can use the Capital Configuration Editor to specify the maximum amount of physical
memory (on a client computer) that each Capital application is permitted to use.
Procedure
1. On the Capital Application Launcher, click the Configuration option in the Support
section.
The Edit Capital Configuration Dialog Box is displayed.
2. In the Memory Allocation (MB) column for an application, select the maximum amount
of memory that the application can use. By default, this is 512 MB. Alternatively,
manually enter another amount.

December 2023
Introduction
Displaying a String in the Window Banner of Applications
3. Click Apply to save the change, or OK to save the change and exit.
4. Start an amended application from the Capital Application Launcher.
Results
The Capital application starts, using the amended memory allocation.
The memory allocation is recorded in the application log file, where “xxx” is the set memory
allocation:
“Allocated Maximum Heap Size = xxxMb”
Note
Memory allocation for each application is retained for 2021.1 applications but not for
MR2207.
Displaying a String in the Window Banner of

Applications
You can display a string in the window banner of an application by running the application with
a –title parameter. This can be useful if you deploy multiple Capital environments (such as
Training, Development, Production) and switch between active client application windows that
connect to different environments but run in parallel.
Procedure
Start an application from a command line with the –title parameter. For example:
CapitalApplicationLauncher.exe –title=PRODUCTION
Note
If you are running different environments with clientprops.xml files that point to
different Managers and databases, you can add a –clientprops parameter that points
the application to a specific clientprops files. For example:
CapitalApplicationLauncher.exe -clientprops=config\production_clientprops.xml -
title=PRODUCTION
Results
The specified string displays in the window banner of the application.

December 2023
Introduction
Capital Stop Services - Command Line Arguments
Figure 1-1. String in Client Application Window Banners
If you also used the –clientprops parameter, the application uses the specified clientprops.xml
file and therefore connects to the Manager and database specified in that file.
Capital Stop Services - Command Line

Arguments
The CapitalStopServices.exe shuts down services for Capital Manager, Capital Integration
Server, Capital E/E Reporter, and the Capital Update Server. It works by connecting to Capital
Manager and then finding the other applications. You can run it with various command line
arguments.
The executable looks for a locally-installed Capital Manager by default, but you can use the
following argument to make it look for a remote Capital Manager.
Table 1-3. Remote Capital Manager Argument
Command Line Description
Argument
-allowremote=true Specifies that the executable connects to a remote Capital
Manager to find the other services.
Without this argument, the executable connects to a locally-
installed Capital Manager.
The executable shuts down all of the services mentioned above by default, but you can use a
combination of the following arguments to restrict which services it shuts down.
Table 1-4. Services Arguments
Argument
-cis Specifies that it shuts down Capital Integration Sever.
-cer Specifies that it shuts down Capital E/E Reporter.
-manager Specifies that it shuts down Capital Manager.
-cus Specifies that it shuts down Capital Update Server.

December 2023
Introduction
Encrypting Text Strings for Configuration Files
Table 1-5. Example Combinations of Arguments

CapitalStopServices.exe This stops Capital Integration Server, Capital E/E
(No additional arguments) Reporter, Capital Manager, and Capital Update Server.
CapitalStopServices.exe –cer – This stops just Capital E/E Reporter and Capital Update
cus Server. It will not stop Capital Integration Server or
Capital Manager.
CapitalStopServices.exe -cer - This stops just Capital E/E Reporter but connects to a
allowRemote=true remote Capital Manager to find the Capital E/E Reporter
service. This would be useful in a situation where Capital
E/E Reporter is installed alone on a machine (with
Capital Manager running remotely).
Note
When using the CapitalStopServices.exe file to stop Capital Manager in a Capital Server
Manager environment, you can use various command line arguments to control when it
shuts down, and whether you want a report on current users connected to it. See “Auto
Shutdown of Capital Manager” in the Capital Enterprise Manager User Guide.
Encrypting Text Strings for Configuration Files

Configuration files (such as config/managerprops.xml and config/clientprops.xml) include
sensitive information, such as usernames and passwords. System default usernames and
passwords are encrypted (with the exception of dbconnection details in the config/
managerprops.xml. You can use a utility to generate encrypted credentials for user-specific
values, which you can use to replace the system default credentials, and to replace the
dbconnection clear text strings.
Procedure
1. On a Capital Manager server or a services only installation (not a client), run the bin/
CapitalUtility.exe file.
An Encrypt text dialog box displays.
2. Enter the text to encrypt, confirm it, and click Encrypt (enabled only when the text
entered in each field matches).
Note
You can click Clear to clear all fields on the dialog box.
The Encrypted text field displays the encrypted version (read-only).

December 2023
Introduction
Feature Licensing
3. Click Copy to copy the text. You can then paste it over the original text in any
configuration file. The software can read the encrypted version.
Feature Licensing
You enable add-on functionality (licenses) by using license policies and user groups in Capital
Access Manager.
See “License Policy” in the Capital Access Manager User Guide.
Automatic Update of Clients

Each new version of Capital contains key stability and functionality improvements. With auto-
update functionality you can distribute these improvements from your Capital Manager
computer to all client computers seamlessly, thereby reducing the burden on IT support. Auto-
update functionality also allows you to push out other environment updates, such as plugin and
configuration changes, with the same speed and ease.
Figure 1-2. Client Auto Update Overview

December 2023
Introduction
Automatic Update of Clients
For full details of this, see the chapter Automatic Update of Clients in the Capital Installation
and Upgrade - Additional Information guide (available with your release documents and from
Support Center).
That chapter includes such information as:
• Installation Types Supported for Automatic Update Services

• Updating Client Computers Automatically
• Configuring Excluded Files for Update
• Example Scenarios for Automatic Update of Clients
o Updating Client Version
o Updating Plugins
o Including clientprops.xml in the Updates
o Excluding adaptors.xml from the Updates
o Removing CapitalProjectManager.exe from a Client installation
• Enabling or Disabling Automatic Update, and Configuring Port Number
• Renaming the Windows Services

December 2023
Introduction
Multi Factor Authentication Support
Multi Factor Authentication Support

Capital supports delegated multi factor authentication using OpenID Connect (OIDC). OIDC is
an inter-operable authentication protocol based on the OAuth 2.0 family of specifications for
enabling multi factor authentication.
In a default installation, Capital internally maintains the authentication of all user accounts for
controlled access to Capital applications. For multi factor authentication, login is delegated to
an external and trusted authentication server using OIDC.
Note
To be able to log into Capital applications using OIDC, every user must have their own,
currently active, unique user account, containing an appropriate username created in Capital
Access Manager. This account should have the 'Delegated Sign-On' property enabled. See
“User Accounts” in the Capital Access Manager User Guide.
Example communication with an authentication server for client applications, such as Capital
Logic Designer or Capital Harness Designer, and for web based applications such as Capital
Device Modeler, is shown on the below sequence diagrams:
Figure 1-3. Example Communication for a Client Application - User

Authentication Using OIDC

December 2023
Introduction
Enablement of Multi Factor Authentication Using OIDC
Figure 1-4. Example Communication for a Web Application - User

Authentication Using OIDC
Note
For FEM Tasks, only standard Capital authentication can be used for web service
submission of tasks or system tasks.
Enablement of Multi Factor Authentication Using OIDC. . . . . . . . . . . . . . . . . . . . . . . . 56
Enablement of Multi Factor Authentication Using

OIDC
You can enable Capital clients and web applications to use Multi factor authentication. The
authentication of the user is then delegated to an external and trusted authentication server using
OpenID Connect (OIDC).
Note
A Capital user account should have the 'Delegated Sign-On' property enabled to use that
account with multi factor authentication. See “User Accounts” in the Capital Access
Manager User Guide.

December 2023
Introduction
Enablement of Multi Factor Authentication Using OIDC
Configuration for using OIDC authentication - Client Applications

To delegate client application login authentication to a third party server you must modify the
following elements in the config/clientprops.xml file:
• Configure the userauthenticationtype element to use OIDC:

<userauthenticationtype value=”OIDC”/>
• Enable/modify the oidcauthentication element:

<oidcauthentication serverhost="localhost" mode="normal"
port="49901"/>
Where:
o serverhost – This is the hostname where the Capital Integration Server is running. In
a case where multiple Capital Integration Server instances are configured, this
should be set to the Capital Integration Server Controller.
o mode - Define this parameter to specify if the communication should happen in
secure or non-secure mode.
Note
If you intend to communicate with Capital Integration Server only in secure
mode, then set the value to "secure", otherwise set the value to "normal".
o port – The port number used to communicate with Capital Integration Server.
Note
If you intend to communicate with Capital Integration Server only in secure
mode, then specify the secure port value, otherwise use the non-secure port
value. The default secure port value is 49932.
Configuration for using OIDC authentication - Web Applications

To delegate web application authentication to a third party server, in the Capital_home/
webclient/configuration/common/generalpreferences.json file, modify the authenticationType
element as follows:
"authenticationType": "oidc"
To revert to the Capital Integration Server credentials:
"authenticationType": "internal"

December 2023
Introduction
Creating Additional Icons in the Capital Application Launcher
Configuration to connect Capital Integration Server to Authentication Server

To delegate authentication to a third party server, a properties file is used to connect the Capital
Integration Server to the Authentication Server (OP). This must be configured before the user
login can be delegated for either client or web applications.
In the Capital_home/config/oidc.properties file follow the instructions given to configure the

connection.
Creating Additional Icons in the Capital

Application Launcher
The Capital Application Launcher is used to start the Capital applications. You can extend the
Capital Application Launcher with custom icons for starting additional applications.
Custom icons include:
• Starting an internet browser with the Capital E/E Reporter start page displayed.
• Launching Capital-related, external applications.
• Launching Capital applications with different memory settings.
• Launching Capital applications with an explicit Login dialog box if Delegated Sign-on
is standard.
Procedure
1. Edit the launcherprops.xml file in the config directory of your Capital installation.
2. Within the <launcher> tags, create a new <launcherentry> tag with the following
attributes:
• name="Name"
Where Name is the name text that will be displayed next to the icon in the Capital
Application Launcher.
• exec="path to executable"
Where “path to executable” is the path to the executable for the application.
• section="Section title"
Where Section title is the title of the Capital Application Launcher section in which
you want the icon to be displayed. It must be either Design, Harness, Analysis,
Manager or Custom.
• icon="path to icon"

December 2023
Introduction
Where “path to icon” is the path to the icon graphic to use in the Capital Application
Launcher. If you leave this attribute blank (that is, icon=""), a default icon is used.
• launcherentrydescription text="description of the icon"
Where “description of the icon” is the descriptive text that is displayed below the
icon name in the Capital Application Launcher.
3. When you have finished editing the file, save and close it.
4. From the Capital folder within the Start Menu, select Capital Application Launcher, to
start the Capital Application Launcher.
Results
Capital Application Launcher is displayed with your custom icons.
Examples
• Custom icon for starting Capital Harness Classic
<launcher>
<launcherentry name="Capital Harness Classic"

exec="<install dir>\CAPH\caph.bat"
section="Custom" icon="<install dir>\CAPH\IMAGES\
img_capitalmanufacture_32x32.gif">
<launcherentrydescription text="Harness Design and detailing" />
</launcherentry>
</launcher>
• Custom icon for opening Capital E/E Reporter in Firefox Browser

<launcher>
<launcherentry name="Capital E/E Reporter"

exec="C:\ProgramFiles(x86)\MozillaFirefox\firefox.exehttp://
localhost:49912/reporter/Login.jsp"
section="Custom" icon="">
<launcherentrydescription text="Enterprise wide Reporting" />
</launcherentry>
</launcher>
• Custom icon for starting Capital Project Manager with Login dialog even when
Delegated sign-on is active

December 2023
Introduction
<launcher>
<launcherentry name="Capital Project Manager with Login"

exec="<install dir>\Capital\bin\CapitalProjectManager.exe -login"
section="Manager" icon="">
<launcherentrydescription text="Manage Designs and Projects" />
</launcherentry>
</launcher>
• Custom icon for starting Capital Logic Designer with parameter -Xmx1400m for bigger
heap space
<launcher>
<launcherentry name="Capital Logic Designer 1400m" exec="<install

dir>\Capital\bin\CapitalLogicDesigner.exe -Xmx1400m"
section="Design" icon="">
<launcherentrydescription text="CLogic with more Memory allocation"

/>
</launcherentry>
</launcher>
• Custom icon for starting Capital Logic Designer with parameter -Xmx1400m (to
increase the default memory allocation)
<launcher>
<launcherentry name="Capital Logic Designer 1400m" exec="<install

dir>\Capital\bin\CapitalLogicDesigner.exe -Xmx1400m"
section="Design" icon="">
<launcherentrydescription text="CLogic with more Memory allocation"

/>
</launcherentry>
</launcher>

December 2023
Introduction
Reports
Reports
In the design applications, you can run various reports on designs, and objects in designs.
If you are using Capital Logic Designer, see the Capital Logic Designer User Guide for more
information.
If you are using Capital Harness Designer or Capital Harness Designer Modular, see the Capital
Harness Designer User Guide for more information.
If you are using Capital Harness Process Designer, see the Capital Harness Process Designer
User Guide for more information.
If you are using Capital E/E Publisher, see the Capital E/E Publisher User Guide for more
information.
If you are using Capital Systems Modeler, see the Capital Systems Modeler User Guide for
more information.
If you are creating platform designs in Capital Systems Architect, see the Capital Systems
Architect User Guide for more information.
The following topic provides details about how you can configure reports:
Using the Report Builder

Capital provides a dynamic report generator enabling you to quickly and easily specify, create
and modify customized reports. The functionality is available in Capital Logic Designer,
Capital Systems Integrator, Capital Wiring Integrator, Capital Harness Designer, Capital
Systems Modeler, and Capital Systems Architect.
The Report Builder interface is intuitive and user-friendly, offering control using icons and drag
and drop functionality, enabling the simple creation and management of reports. The scope of
the report is only based on the current design.
The reports are generated as plugins and can be made available, depending on your
requirements, as tables on diagrams, in Design Inspectors, for internal reports, and in Capital E/
E Reporter.
Tip
You can change the location that reports are saved to a local folder by following the
instructions given in Technote MG595661 - How Can I Set My Capital Client to Access
Specific Plugins. You will need a Support Center login to access this information.

December 2023
Introduction
Prerequisites
A design must be open in the browser.
Procedure
1. Press Space Bar and enter Build.
2. Either:
• Click the icon to create a new report.
• Click the icon to load an existing report (as a plugin) and edit as required.
3. Choose the relevant icon to report the Tool or Tools:.

• Select for Capital Logic Designer
• Select for Capital Systems Integrator and Capital Wiring Integrator
• Select for Capital Systems Modeler
• Select for Capital Systems Architect
• Select for Capital Harness Designer
You can report on one, or a combination of tools. The objects that can be reported on
changes according to the tool(s) selected and are displayed for selection in the
Include: section at the bottom of the window.
Objects available for the tools include, for example, Device and Connectors for
Capital Logic Designer; Slots and Holes for Capital Systems Integrator; Clips and
Grommets for Capital Harness Designer; Functions and Signals for Capital Systems
Modeler and Gateways and Carriers for Capital Systems Architect. This list is
illustrative only. Refer to the icon tooltips for a full list of available objects for each
tool.
Click the selected icons to include in, or remove from the report.
Note
Only applicable object types are available for each of the design types.
Combining design types narrows the scope of possible objects for selection, as
only common objects are shown. as available.
4. Choose the type of report, or reports to generate:

• Select to generate output as an embedded report.
• Select to generate output as a table to be used in a style set. (Not available for
Capital Systems Modeler and Capital Systems Architect).

December 2023
Introduction
• Select to generate a design inspector report.
• Select to generate a report accessible in Capital E/E Reporter. (Not available for
Capital Systems Modeler and Capital Systems Architect).
5. Enter a unique name, version, and description for your report by typing in the free text
entry boxes.
6. Click the icon to add columns to the report. Once there is at least one column in the
report click the icon to specify the contents of the column.
Tip
Double-click the heading of the column to change or edit its name.
• Columns may be reordered by dragging or dropping into the required configuration.
• When two different attributes having the same column names (for example
Function -> Type and Signal -> Type) need to be added in a custom report, you
should give a custom name to the first column before adding the second.
• Select a column and click the icon to delete it.
• By default the report will be sorted in ascending order from the first column.
However, you can set a sort order on any column that will subsequently be used in
your generated report. Click the column heading tag to sort in ascending order, click
again to sort in descending order or click a third time to remove the sort order.
7. After clicking the icon the Edit Contents of Column dialog box opens:

December 2023
Introduction
8. Drag and drop available elements, including attributes, queries and plugin queries, to
construct the desired content of the report. You can also insert your own text by typing
in between the elements. A preview of how the elements will appear in the report
column is shown at the bottom of the dialog box.
Where there are a number of different options available under an element a dropdown
list is accessible by clicking the down arrow.
When selecting the Attribute element a list of specific attributes are displayed for
conductors, devices, connectors and splices, along with common attributes for all
objects. In addition, you can add a "User specified" attribute to include attributes not
listed in the above sections.
Tip
The Special > Design Name setting on the Attribute element returns the Design
attribute on the object. To obtain the name of the design the object belongs to, use
the name setting in the Design element.
Plugins not created by Capital cannot be opened, or used as the basis for report content.
The “From” and “To” elements are available only if Wires are selected. Selecting any
other object will remove the “From” and “To” fields.
Likewise, the “Ends” element (not shown) is available only if “Nets” or “Signals” are
selected. This element is used to retrieve details of the terminations of the selected net or
signal. It displays a list separated by the “|” character in editing mode, but in actual
output it is rendered as a multi-line report.
Note
If you have previously created Net reports using the “From” and “To” elements, it is
recommended you recreate the report by removing the previous From/To columns
and instead use the “Ends” element as this provides greater report clarity.
If you add a calculation element then its dropdown list allows access to a further list of
options enabling you to construct your required calculation. You can also format the
calculation, including specifying the number of decimal places shown by clicking the
Format option from the calculation dropdown menu.
9. Click the icon compile and save your report, ensuring you have specified a name and
description, if required, in the Plugin Name and Plugin Description fields.
Reports automatically become available in the Capital tool suite, negating any need to
restart the Capital E/E Reporter server.
Results
The report is available as a plugin, and depending on the choice of output, can be viewed as an
embedded report in the tool, as a plugin table in Styling, using the design inspector, or in Capital
E/E Reporter.

December 2023
Introduction
User Interface Language
Note
If Capital E/E Reporter is not installed on the same machine on which you have generated
your report, you must copy the report output file to the plugins directory on the machine
where it is running, to view the report in Capital E/E Reporter.
Related Topics
Report Builder Dialog Box
User Interface Language

Capital provides the user interface in four languages: English, German, Chinese, and Japanese.
You set the language in the clientprops.xml file located in the config subdirectory of your
Capital installation directory. See the Capital Configuration Files Reference Guide.
User Interface Toggle View Options

You can use the Toggle Layout options to toggle the viewing of the browser area, the output
window, and the status bar between visible and hidden. Specific information for each tool is
contained within that tools user guide, if applicable.
Note
For each of the options, press Space Bar and enter Toggle Browser Area / Output Window /
Status Bar. If the option is highlighted, the option is visible; if not, the option is hidden.
Project Browser Window

The Project Browser Window is located on the upper left side of the application window. It
contains a browser tree that displays the designs and diagrams that exist for the project that is
open.
Output Window
The Output Window is located at the bottom of the screen. It displays the tool output during
operation. Information sent to the window is not lost while the window is hidden.
Status Bar
The Status Bar is located at the bottom of the Application window and contains various
elements related to whichever design tool is open.

December 2023
Introduction
Embedded Library Portal
Embedded Library Portal

The embedded library portal integration provides instant access to the CADENAS 3Dfindit.com
online component library. 3Dfindit.com offers a multitude of ready-to-import parts, from
various prominent vendors, and is available from the parts tab within the design applications.
While working on designs, engineers can research and compare parts they may wish to use, and
then seamlessly load them into their component and symbol libraries, ready for immediate use
in the active design tool.
This reduces the time and effort required to create and maintain library parts and their symbols.
The embedded library portal also provides easy-to-edit configuration files to customize the
import of parts and symbols to adhere to your organization’s standards and requirements. These
enable you to specify settings such as attribute, type, color, material code mapping, as well as
specifying internal part numbers and revisions.
You can also configure the language used in the embedded library portal, even if this overrides
that specified by your operating system or the locale designated in the system configuration
files. Please note only languages supported by Capital and 3Dfindit.com are supported.
Note
The embedded library portal integration is turned off by default at this release. To enable its
functionality see “Enabling The Embedded Library Portal” on page 66.
Caution
Siemens Industry Software Inc., provides integrated access to the CADENAS 3Dfindit.com
online component library in good faith and cannot be held accountable for the credibility of
parts available there. Component libraries are provided directly by suppliers and manufacturers
of components. Refer to the 3Dfindit.com Terms of Service for more information.
Enabling The Embedded Library Portal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Using The Embedded Library Portal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Configuring Internal Part Numbers on Import . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Embedded Integration Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Enabling The Embedded Library Portal

Access to the 3Dfindit.com embedded library portal is turned off by default, and is not available
on the Parts tab of the design tools until explicitly enabled.
To enable access to the 3DfindIT.com embedded library portal navigate to the
<your_installation>/config/libraryportal/ExternalLibraryImport.properties file, locate the
setting Enable_Embedded_Portal=true and remove the “comment out” marker before it in
order to make the 3Dfind IT.com button available.

December 2023
Introduction
Using The Embedded Library Portal
Once enabled the 3Dfindit.com button is available on the design tools Parts tab as
shown in Figure 1-5.
Figure 1-5. Enabled Embedded Library Portal

The embedded library portal integration provides instant access to the CADENAS 3Dfindit.com
online component library. It enables you to search and compare a multitude of parts in the
embedded 3Dfindit.com parts library browser. These can then be imported from 3Dfindit.com,
and saved into component and symbol libraries, ready for immediate use in the active design
tool.
Note
Only connectors, devices, terminals, cavity plugs, cavity seals, multicores and “other”
component groups are supported in this release.
Prerequisites
• The embedded functionality must be enabled before use. See “Enabling The Embedded
Library Portal” on page 66. Once enabled the 3Dfindit.com button is available
on the Parts tab of the design tools, as shown in Figure 1-6.
• Downloading parts from the 3Dfindit.com online component library requires a
3Dfindit.com account login, available through a free registration.
Procedure
1. Type a search term in the Search field of the Parts tab and click the 3Dfindit.com button
, the value is transferred automatically to 3Dfindit.com. Alternatively leave the

search field blank and click the button to open the 3Dfindit.com home page, see step 2.

December 2023
Introduction
Figure 1-6. Enabled Embedded Library Portal
Search results are displayed in the embedded 3Dfindit.com browser window, see
Figure 1-7.
Figure 1-7. 3Dfindit.com Search Results - Part Number Entered
Note
Information on the integration with 3Dfindit.com is available by clicking the Learn
more... link at the top left of the browser window.
2. If you left the Parts tab search field blank the 3Dfindit.com home page is displayed. By
default the embedded library portal integration launches catalogs that contain
electrically enriched relevant parts. The filter “CNSDATAQUALITY_ELECTRO” is
automatically set in the search field to aid the work of the ECAD engineer.

December 2023
Introduction
Figure 1-8. 3Dfindit.com Default Home Page
Tip
This filter can also be applied by clicking on the checkbox "Electro enhanced" in the
tab on the left of the screen.
3. Selecting a part from the 3Dfindit.com library displays its details and available symbol
graphics. Available information includes all the attributes of the selected part displayed
in a table, as well as 3D images and electrical properties of cavities, if applicable. You
can also browse and compare a list of similar parts to the one selected by clicking
.
4. Clicking the button from within the 3Dfindit.com browser

imports the part into Capital Component Manager, as well as loading it into the design
browser. After clicking the button, a bell notification at the top right corner of your
screen indicates the part is getting downloaded. Once the part is downloaded a progress
bar is displayed indicating the import progress. The details section of the progress bar
displays relevant information, warnings and error messages for each processing action
that is performed on the incoming data.
Note
If you wish to configure a new internal part number, or manage part revision prior to
importing the part see “Configuring Internal Part Numbers on Import” on page 72.

December 2023
Introduction
5. If a symbol is also being imported, the Import DXF Dialog Box appears where you can
configure the target symbol details such as a symbol name, destination library and
dimensions. For further information see Importing a Symbol or Border from a DXF File
into a Library in the Capital Symbol Designer User Guide.
The imported part gets created and added to the Capital Component Manager. Its
accompanying symbol is also created in the specified symbol library and automatically
associated to the part. It automatically appears, without refreshing, in the Parts list of the
Design Browser and is available for immediate use.
Results
Following a successful part import from 3Dfindit.com:
• The incoming parts important attributes, such as description and number of cavities are
filled in correctly with the information derived from 3Dfindit.com. To ensure it is
immediately available for use its Status is set to current.
Tip
The Status setting is configurable. You can change the default value in the
ExternalLibraryImport.properties file.
• You can provide custom mapping between the details of incoming part and type codes,
color codes and material codes already used in your library. These can be specified in
the <your_installation>/config/libraryportal/ExternalLibraryImport.properties (for
Type Codes), ColorCodeMapping.txt and MaterialCodeMapping.txt configuration files.
If you do not provide a mapping, the integration creates or associates the most suitable
codes automatically based on the Embedded Integration Process.
• Multicores are imported with structures provided by the parts manufacturer. Wire
specifications (specs) of inner cores are set based on the CSA value present on
individual inner cores.
Color and material information for the outer sheath and the inner cores is derived from
the information provided by the part manufacturer.
If suitable wire specs are not present in the database, a wire spec is created using default
material and specification values. These can be configured in the <your_installation>/
config/libraryportal/ExternalLibraryImport.properties file as follows:
o Default_multicore_wire_CSA=0.000001
o Default_multicore_wire_specification= -
These are the default CSA and default specification that need to be set on an inner
core wire when there is no wire size in the database similar to the incoming CSA.
o Default_multicore_shield_CSA=0.000001
o Default_multicore_shield_specification=SHIELD

December 2023
Introduction
These are the default CSA and default specification that need to be set on an inner
core shield.
o Default_multicore_sheath_specification=SHEATH
This is the default specification that needs to be set on a sheath type element.
• Connector views will be created as comment symbols in symbol libraries and are
associated to the part automatically. The configuration file located at
<your_installation>/config/libraryportal/ExternalLibraryImport.properties contains
further information on these settings.
The embedded library portal functionality also allows the automatic addition of RED
datum elements at each cavity present on the connector end view comment symbol.
Available RED datums are:
o A connector pin datum as a related entity on a connector.
o A wire datum as a related entity on each connector pin datum.
By default, on each cavity of the connector comment symbol, a connector pin datum
(connector and wire datums) is automatically added at exact cavity locations. The
visibility of these datum element names is set to false to ensure the connector comment
symbol looks correct.
The default value for these datum properties is set to true so they are automatically
created when cavity details are provided by 3Dfindit.com. Both properties can be set to
false to prevent automatic datum element creation. You can configure the settings to
create connector pin datums only, but the creation of wire datums alone is not allowed.
Automatic creation is controlled by the configuration file located at
<your_installation>/config/libraryportal/ExternalLibraryImport.properties. The
properties are:
o Create_connector_pin_datum=true
o Create_wire_datum=true
• For details required in the Single Wire Fits Cavity and Single Terminations tabs, the
system processor examines the minimum suitable wire CSA and maximum wire CSA
values of the arriving part, and for Cavity Seals, the maximum and minimum cable
diameters. Suitable wire sizes among the available ones in the Capital Component
Manager are added to the Single Wire Fits Cavity tab for connectors, and the Single
Terminations tab for terminal and cavity seals automatically.
• For details required by the Housing tab, relevant housing parts are created and added in
the Housing tab of connectors and devices automatically. You can further configure the
types of housing parts that need to be added in the ExternalLibraryImport.properties
file.
• Information, such as strip lengths are set for terminals and devices.

December 2023
Introduction
Configuring Internal Part Numbers on Import
Configuring Internal Part Numbers on Import

Newly imported parts from 3Dfindit.com are assigned the supplier provided part number by
default. Embedded Library Portal functionality enables you to create and edit internal part
numbers on these new parts prior to import into Capital. The functionality also provides a clear
indication of the existence of the part in the Component Library together with the ability to
revise existing parts in conjunction with controlling the import mode.
Prerequisites
• Downloading parts from the 3Dfindit.com online component library requires a
3Dfindit.com account login, available through a free registration.
Procedure
1. Type a search term in the Search field of the Parts tab and click the 3Dfindit.com button
, the value is transferred automatically to 3Dfindit.com. Alternatively leave the

search field blank and click the button to open the 3Dfindit.com home page.
2. Once you have located your required part click the button from
within the 3Dfindit.com browser to import it into Capital Component Manager, as well
as loading it into the design browser.
If this is the first time you have imported this part then the New Component tab is
displayed on the Configure Import Dialog Box. If you have previously imported the part
then the Existing Component tab is displayed - proceed to step 6 below.
Note
Even if you have not previously imported the part earlier, but it has any housing
components that are already there in the Capital library, the Existing Components
tab is also displayed showing those housing components.
3. For new components the Internal Part Number field is pre-populated with the part
number supplied by the manufacturer. You can overwrite this with an appropriate
internal part number according to your organization’s requirements.
4. You can also optionally set a revision value that should be assigned to the part when it is
created in your component library.
5. Once you have updated the internal part number click Proceed to import the part. A
progress bar is displayed indicating the import progress. The details section of the
progress bar displays relevant information, warnings and error messages for each
background processing action that is performed on the incoming data.
6. If the supplier part number of the incoming component matches with a supplier part
number already present on any component in your library then the incoming component
is considered an existing component and the Existing Component tab is displayed on the
Configure Import Dialog Box.

December 2023
Introduction
Multiple Language Support
7. Click the View Part button to view all existing details for the selected part as held in
your component library. See the relevant Component Dialog Box and Field Reference
section in the Capital Component Manager User Guide for further information on the
fields displayed.
8. Click the Revise check box to revise the existing component with the new incoming
details. Enter an appropriate value in the New Revision field.
9. Specify the required import mode prior to importing the part.
Note
The available options are only applicable for existing revisions of a part.
Available options are:

• Replace - Specifies that the data for an existing component in the library is truncated
and overwritten with the data from the component with the same supplier part
number in the import file.
• Merge - Specifies that the component data for a supplier part number in the import
file is merged with the component data for an existing component with that supplier
part number in the library.
• Ignore - Components from the import file that already exist, or with supplier part
numbers matching components already in the library are not imported.
Tip
If you create a new component revision while Ignore mode is selected it cannot
automatically be set as the latest revision in the component library. If you need to set
it as the latest revision then you should verify the part in Component Manager tool and
manually set the part as the latest part in the History tab of Component Details section.
10. As with new components, once you have completed your updates click Proceed to
import the part. A progress bar is displayed indicating the import progress. The details
section of the progress bar displays relevant information, warnings and error messages
for each processing action that is performed on the incoming data.
Multiple Language Support

By default, the embedded library portal is launched in the language corresponding to the locale
specified by your operating system, or the one configured in the config/clientprops.xml file. The
embedded library portal functionality enables you to configure the language used in the portal
user interface, even if this overrides that specified by your operating system or the system
configuration files.
This enables you to obtain localized content from the portal. Descriptions of parts downloaded
from the portal will be in the language corresponding to the locale in which Capital is seen,

December 2023
Introduction
Embedded Integration Process
(irrespective of the override language set in the portal), provided the part description is available
in that language. For example, when Capital is in a German locale, the descriptions of the parts
downloaded will also be in German, if a parts description is available in that language.
Note
Only languages supported by both Capital and 3Dfindit.com are available. Additionally the
flag setting below is applicable only to the Description attribute of a part.
To use part description translations based on the locale configured, ensure the flag
Set_the_data_as_per_locale=true located in the <your_installation>/config/libraryportal/
ExternalLibraryImport.properties file is set to true.
Set the flag to false to set part descriptions in the default language (this will be English for the
majority of catalogs).

There are a set of integration steps that use the configuration files to transform the incoming
parts to the target environment.
Configuration and Property Files

The following configuration and property files are available to control and manage the import of
parts from 3Dfindit.com. They are located in <your_installation>/config/libraryportal/
• ColorCodeMapping.txt
• ExternalLibraryImport.properties
• MaterialCodeMapping.txt
Embedded Library Portal Transformation Process

• Filter Unnecessary Housing Definition - This removes any housing sub-components on
a part which are superfluous for electrical engineering.
o For a connector main part, with the exception of terminals, cavity plugs and cavity
seals, sub-components of any other group are removed from the incoming data.
o For a device main part, with the exception of terminals, sub-components of any other
group are removed from the incoming data.
o For an other group main part, all subcomponents are removed from the incoming
data.
o This behavior is configurable and you can specify any sub-components that need to
be retained during the processing.

December 2023
Introduction
• Import of Unsupported Groups into Other Group
Note
Only parts of the groups connectors, devices, terminals, cavity plugs, cavity seals,
multicores and “other” are supported for import from 3Dfindit.com in this release.
o If you try to import a part whose group is currently unsupported for import from
3Dfindit.com this identifies and reports the issue. You are then given the option to
cancel the import, or import the part into the other group, for manual update in the
future.
o For parts where a component group can be defined but does not yet belong to the list
of supported groups at this release, for example Assemblies, the import is cancelled
and a message is displayed.
• Import of Zero Pin/Cavity Devices and Connectors - In the 3Dfindit.com portal, there
can be basic parts for which cavity or pin information might not be available. If you
attempt to import such a part the system identifies and reports the issue. You are given
the option to cancel the import, or to import the part with zero pin/cavity count.
• Import of Existing Part - If you attempt to import an existing part (this can be the
component or a housing sub-component of the main part or both), the system identifies
and reports the issue and asks you to select an appropriate import mode.
o When the main part itself is an existing part, (irrespective of sub-components status)
you have two options:
• Import the data in merge mode (incoming changes shall be merged with existing
data).
• Cancel the import.
o When the sub-component is an existing part (and the main component doesn't exist
in library), you have three options, provided there are new updates from the part
manufacturer for these sub-components:
• Import the data in merge mode (incoming changes shall be merged with existing
data).
• Import the data in ignore mode (incoming changes shall be ignored).
• Cancel the import.
• Unit Conversion - Converts the values of different external data elements, that are going
to be processed, into your organization’s required unit system, as specified in the
ExternalLibraryImport.properties configuration file.
• Type Code - The IEC Class code of the incoming part (if present) can be mapped to the
type code attribute of the part. Multiple IEC Class codes can be mapped to a single type

December 2023
Introduction
code in Capital. This can be controlled in the ExternalLibraryImport.properties

configuration file.
• Material Code - The material information of the incoming part (if present in the form of
ECLASS material code) can be mapped to the material code attribute of the part. This
can be controlled in the MaterialCodeMapping.txt configuration file.
• Color Code - The color information of the incoming part (if present in the form of RGB
value or IEC 60757 color code) can be mapped to the color code attribute of the
part.This can be controlled in the ColorCodeMapping.txt configuration file.
• Strip Length - Different pins of a device may have different strip length values. Strip
length information is only stored at part level. The system identifies the largest strip
length value, from all the available strip length values at different pin levels, and sets it
as the strip length of the part.
• Attribute and Property Mapping - External data elements from 3Dfindit.com can be
mapped to attributes or user properties. These are controlled by the mappings defined in
the ExternalLibraryImport.properties properties file.
• Connector Wire Specs. - Based on the incoming min. and max. connectable wire CSA,
suitable wire specs need to be added to the single wire fit cavity tab.
o The integration reads the minimum and maximum CSA of a connector and locates
the wire specs in the database that satisfies this CSA range. It then adds them as
single wire fits cavity tab entries of the connector.
o The configuration files allow you to set material codes that should be considered
while selecting the wire specs to be added. The default value is empty which means
it adds wire specs of all the available material codes provided they are satisfying the
range.
• Terminal Wire Specs. - Based on the incoming min. and max. connectable wire CSA,
suitable wire specs need to be added to the single terminations tab.
o The integration reads the minimum and maximum CSA of a terminal and locates the
wire specs in the database that satisfies this CSA range. It then adds them as single
termination tab entries of the terminal.
range.
• Cavity Seal Wire Specs. - Based on the incoming minimum and maximum cable
diameters, suitable wire specs need to be added to the single terminations tab.
o The integration reads the minimum and maximum cable diameters of a cavity seal
and locates the wire specs in the database that satisfies this CSA range. It then adds
them as single terminations tab entries of the cavity seal.

December 2023
Introduction
Adding a Library Part from EDM Collaborate
range.
• DXF Importer - Enables you to import the DXF symbol of the connector with regard to
the configuration you have set in the DXF Import dialog, and then assign the symbol to
the part.
Adding a Library Part from EDM Collaborate

This topic explains how to add a library part from EDM Collaborate for use in all Capital
applications.
You can drag and drop library parts managed within EDM Collaborate from the EDM Web
Browser directly into either the Part Selection dialog box, a Properties dialog box, or the Design
Browser in Capital.
Procedure
1. Search for the required part in the DSM/EDM Collaborate Web Browser interface.
2. On locating the part, drag and drop it from the browser into either the part selection field
of the properties dialog box of a part, or into the part field of the design browser.
3. Part information is passed from EDM Collaborate to Capital in the form of a JSON file.
Data for an example part “YTU-001” is shown below:
{
"PartNumber": "YTU-001",
"CustomerPartNumber": "C-YTU-001",
"SupplierPartNumber": "S-YTU-001",
"Revision": "3.0"
}
4. Depending on the search by setting (Internal part number, Customer part number or
Supplier part number) the appropriate value is added to the field as seen below in the
design browser parts tab (Figure 1-9.) The incoming part is now available for use across
all Capital applications.

December 2023
Introduction
Launching Capital Component Manager from this Application
Figure 1-9. Example Rendered Part Information Imported from EDM Collaborate
Related Topics
Part Selection Dialog Box
Properties and Attributes Help
Launching Capital Component Manager from

this Application
Capital Component Manager provides component management services for the Capital product
suite and defines the part library data used by other Capital applications, such as Capital Logic
Designer, Capital Systems Integrator and Capital Harness Designer. You can launch Capital
Component Manager from this application.
Procedure
Press Space Bar and enter Capital Component Manager.
Results
Capital Component Manager launches in a separate window.

December 2023
Introduction
Launching Capital Symbol Designer from this Application
Launching Capital Symbol Designer from this

Application
Capital Symbol Designer enables the construction of electrical symbols for use on designs. It
also enables the construction of borders for user on diagrams in other applications. You can
launch Capital Symbol Designer from this application.
Procedure
Press Space Bar and enter Capital Symbol Designer.
Results
Capital Symbol Designer launches in a separate window.

December 2023
Introduction
Diagram Language Translation

You can display, print and publish diagrams as well as generate workbooks with text rendered
in any given language using a language database stored as part of your system data. This
enables you to generate multi-language service documentation.
Language Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Active Language. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Chinese and Japanese Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Saving a Language Dictionary CSV File with UTF-8 or Non-Ascii Characters . . . . . . 84
Importing a Language Dictionary CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Exporting a Language Dictionary CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Refreshing Language Dictionary Data in a Design Application . . . . . . . . . . . . . . . . . . . 87
Adding a Translation of an Existing Translatable Term for the Currently Active Language
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Adding a Translation of a New Translatable Term for the Currently Active Language 89
Converting Text Strings into Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Language Dictionary
To start using diagram language translation, you must edit and import a comma separated
variable (CSV) file, that acts as a language dictionary of translatable terms. This is the starting
point for the language database.
See “Editing the Language Dictionary CSV File” on page 82 and “Importing a Language
Dictionary CSV File” on page 85.
Any updates made in the applications will only be included in the database, the CSV file is not
updated automatically but you can export an updated CSV file. See “Exporting a Language
Dictionary CSV File” on page 86.
The CSV file lists the available translation languages and any translations that already exist for
specific translated words or terms. Each translation entry has a quick code and a list of
translations for the available languages. The quick code links each translatable string within the
design tools, or library data, with the translation entry in the language dictionary.
An example CSV file, dictionary.csv, is included in the starter data supplied with the software
see capital_home\data\xml\Language Dictionary. You can take a copy of that and edit it or
create a new CSV file.

December 2023
Introduction
Active Language
Active Language
Within Capital Project Manager or a design application, you control which translation language
is active by selecting a language code in the box that is at the bottom right of the application
window. By default, the language is EN. In Capital Component Manager, you control it from
the Actions > Switch Language menu.
The default EN language is used:
• When you bridge data in or out of the applications.

• When design rule checks and design compare functionality interpret results.
• When the Analysis functionality interprets properties and names. It is not recommended
to use translatable strings in analysis models.
When you export a DXF, PDF, CGM, or SVG file, the currently active language is used.
Translatable Terms
When you enter property, attribute, or comment text into a dialog box, predictive text displays a
list of translated terms in the active language, enabling you to select an existing translated term.
You can enter free, non-translated text as normal, including text that exists within the language
database.
Wherever a translatable term is used, that translation is displayed against a gray background
( ). When the active language is changed, the displayed text will change to the one for
the now active language.
If a translatable term was entered for a previously active language and the currently active
language does not have a translation for that term, the quick code will be displayed.
If a translatable term does not have a translation for the active language, you can enter one using
the context menu for that highlighted term. See “Adding a Translation of an Existing
Translatable Term for the Currently Active Language” on page 88).
You can enter a new translatable term and add it to the dictionary. See “Adding a Translation of
a New Translatable Term for the Currently Active Language” on page 89).
A design rule check “No translation for text” is also available to identify:
• where a translatable term has been used but no translation exists for the active language
so the quick code is displayed.
• where a translatable term has been entered as free text and has no link to the language
database.
See “Running Design Rule Checks” on page 247.

December 2023
Introduction
Chinese and Japanese Characters
In dialog boxes using query expressions, the query expression will work with values from the
currently active language. However, if you change the active language, the query expression has
to be modified to match the now active language.
In the Part Selection Dialog Box, the filter for a property value will only work with a quick code
as the value for translatable entries.
Capital Work Instruction Publisher

You can configure translations for all non-component specific areas of workbook provider
output including table headers, operation names, task names, page headers and footers as well
as any diagram attribute, property or comment text. See Workbook Translation.
Chinese and Japanese Characters

To see Chinese and Japanese characters in dialog boxes, you must have East Asian characters
available on your computer.
Editing the file in Microsoft Office Excel removes UTF-8 encoding. See “Saving a Language
Dictionary CSV File with UTF-8 or Non-Ascii Characters” on page 84 for a workaround.
Font settings for comment text on diagrams are taken from the Project Preferences for each
application (Applicaton Name > Property > Text). By default, they use the Lucida Sans font
which does not support East Asian characters. To use East Asian characters, you must change
the font in these preferences. See “Project Preferences” on page 131.
Related Topics
Editing the Language Dictionary CSV File
Saving a Language Dictionary CSV File with UTF-8 or Non-Ascii Characters
Importing a Language Dictionary CSV File
Exporting a Language Dictionary CSV File
Refreshing Language Dictionary Data in a Design Application
Adding a Translation of a New Translatable Term for the Currently Active Language
Converting Text Strings into Translations

An example CSV file is included in the starter data supplied with the software. You can take a
copy of that and edit it or create a new CSV file.

December 2023
Introduction
You must use a unicode-supporting text editor capable of creating UTF-8 encoded files (for
example, OpenOffice, Windows Notepad) to edit the CSV file that acts as the language
dictionary of translatable terms.
Note
Editing the file in Microsoft Office Excel removes UTF-8 encoding. See “Saving a
Language Dictionary CSV File with UTF-8 or Non-Ascii Characters” on page 84 for a
workaround.
The first line of the file lists the available languages. For example:
QuickCode,EN_UK:ENGLISH:UK:BRITISH,DE:GERMAN:GERMANY:GERMAN
Note that QuickCode is mandatory, this code is not necessarily in any particular language but
links a translation with a particular translatable term. All other listed languages are optional.
In this example, QuickCode is followed by the languages UK English

(EN_UK:ENGLISH:UK:BRITISH) and German (DE:GERMAN:GERMANY:GERMAN).
Each language is separated by a comma (,). Each language entry consists of the language code
(which is the code that appears within the design tools, in the lower right corner of the
application), language name, country code and remarks separated by a colon (:). Only the
language code is mandatory information.
You can add any languages to this row. For example, if you wanted to add French to the
available languages, you would add FR:FRENCH:FRANCE:FRENCH. For example:
QuickCode,EN_UK:ENGLISH:UK:BRITISH,DE:GERMAN:GERMANY:GERMAN,FR:FRE
NCH:FRANCE:FRENCH
The remaining lines within the CSV file describe each translated entry. Each row consists of a
unique quick code followed by the translations. The QuickCode that you use for a language can
be anything. The translations must follow the same order as the language list in the first row.
In this example, PWR is the quick code, Leistung is the German translation and power circuit is
the English translation.
PWR,Leistung,power
PWRC,Leistungsteil,power circuit
SUP,Lieferant,supplier
YES,möglich,possible
SWPOS,Positionsschalter,position switch
AUTOCUT,Automatisches Schneiden und Terminieren beider Enden,Auto Cut and
Terminate both ends

December 2023
Introduction
Note
Multiple words that form a phrase, as one translatable term, must be entered in the same
row, in the example above “Auto Cut and Terminate both ends” is the English translation
for the German phrase “Automatisches Schneiden und Terminieren beider Enden,”
Each translatable term must have a quick code as this is used to identify which term is being
translated when you enter a translation from an application.
Each translatable term should have one translation for each available language defined in the
first line. However, if no translation exists for a particular language, the entry for that language
is placed as an empty string.
Using the above example, if there was an English translation for PWR but no German
translation, its row would be:
PWR,Leistung,,
Note
If a translation string contains an explicit comma (,), you must enter a backslash before it (\
,).
Related Topics
Saving a Language Dictionary CSV File with UTF-8

or Non-Ascii Characters
Editing a language dictionary CSV file in Microsoft Office Excel removes UTF-8 encoding.
However, there is a workaround for this.
Procedure
1. Open the CSV file in Microsoft Office Excel.

December 2023
Introduction
2. In Microsoft Office Excel, save the file as a CSV (Comma delimited) (*.csv) file.
3. Close Microsoft Office Excel.
4. Open the CSV file in Notepad (found under All Programs > Accessories in the
Windows Start menu).
5. In Notepad, select File > Save As from the menu; the Save As dialog box is displayed.
6. From the Encoding dropdown list at the bottom of the dialog box, select UTF-8.
Note
Do not select ANSI or you will lose any accents.
7. Save the file with a different name from the original.

Results
This file is in UTF-8 and retains all characters and accents. It can be imported into databases
supported by Capital.
Related Topics

You can import a comma-separated variable (CSV) file that acts as a language dictionary of
translatable terms into your database.
Note
When importing and exporting system data, any language dictionary data will be included in
your system data and as such will be imported and exported. You do not need to import and
export language dictionary data separately, although you may want to just import language
dictionary data from a separate CSV file.
Caution
In European locales (for example France), the separator used in the CSV file should be
changed to a semi-colon ";" rather than a comma ",". Comma, in such locales, is used as a
decimal point instead.

December 2023
Introduction
Prerequisites
• The CSV file must contain the languages that you want available. See “Editing the
Language Dictionary CSV File” on page 82.
• Your user account must have the Import Language Dictionary permission.
Procedure
1. In Capital Project Manager, select File > Import Language Dictionary; the Import
Language Dictionary dialog is displayed.
2. Navigate to the language dictionary CSV file and select it. If your database already
contains language dictionary data, you must specify one of the following:
• Overwrite
Completely overwrites the contents of the existing language dictionary in the
database and removes existing translations that are not in the imported CSV file.
• Merge
Merges the contents of the CSV file with the existing language dictionary in the
database. Existing strings that are not included in the CSV file remain in the
database. New strings are added and existing strings are updated with any new
translation strings in the file.
3. Click Import Dictionary.
Results
The contents of the language dictionary CSV file are stored as part of your system data.
Related Topics

You can export a comma-separated variable (CSV) file that acts as a language dictionary of
translatable terms from your database.

December 2023
Introduction
Note
When importing and exporting system data, any language dictionary data included in your
system data will also be imported and exported. You do not need to import and export
language dictionary data separately, although you may want to just export language dictionary
data in a separate CSV file.
Caution
In European locales (for example France), the separator used in the CSV file should be
changed to a semi-colon ";" rather than a comma ",". Comma, in such locales, is used as a
decimal point instead.
Prerequisites
• Your user account must have the Export Language Dictionary permission.
Procedure
1. In Capital Project Manager, select File > Export Dictionary; the Export Language
Dictionary dialog is displayed.
2. Navigate to the location where you want to save the file, specify a name and click
Export Dictionary.
Results
The contents of your language dictionary are saved in the CSV file.
Related Topics
Refreshing Language Dictionary Data in a Design

Application
You can refresh the language dictionary data that is being used in a design application. This is
useful if the language dictionary has been updated while your application session has been
open.

December 2023
Introduction
Procedure
Press Space Bar and enter Language Dictionary; the language dictionary accessed by the
application is updated.
Results
• Any amendments are now:
o Visible in the application.
o Available for Workbook Translation.
Related Topics
Adding a Translation of an Existing Translatable

Term for the Currently Active Language
You can add (enter) a translation for a term that does exist in the language dictionary but does
not yet have a translation for the currently active language. You can do this while entering
property, attribute or comment text into a dialog box.
Prerequisites
• The translatable term must have been entered in the language dictionary but without a
translation for the currently active language.
• You must know the quick code for the translatable term.
• Your user account must have the Add to Language Dictionary permission.
Procedure
1. Enter the new translation in the field where you want to use it.
2. Select the translation, right-click it and select Add To Dictionary; the Add To
Dictionary dialog box is displayed.
3. Specify the Entry Value and click OK.

December 2023
Introduction
Results
• The translation is added to the language dictionary.
• The translation is displayed against a gray background in the field ( ).
Related Topics
Adding a Translation of a New Translatable Term

for the Currently Active Language
You can add (enter) a translation for a term that does not exist in the language dictionary. You
can do this while entering property, attribute, or comment text into a dialog box.
Prerequisites
• Your user account must have the Add to Language Dictionary permission.
Procedure
1. Enter the translation in the field where you want to use it.
2. Select the translation, right-click it and select Add To Dictionary; the Add To
Dictionary dialog box is displayed.
3. Specify a unique Entry Code (the quick code for the term) and click OK.
Results
• The translatable term and translation are added to the language dictionary.
• The translation is displayed against a gray background in the field ( ).
Related Topics

December 2023
Introduction


You can perform a batch conversion of text strings, that exactly match existing translations for
the currently active language, into translation strings.
You run this conversion in any of the design applications. It updates all texts in fields where
translation is supported. You specify whether you want to perform this for an entire project, a
design or a diagram.
Note
The process also updates any diagram attribute, property or comment text translations that
may be used in translated workbooks.
Translation Strings are text strings with a gray background, ( ), that change when the
active language changes).
Procedure
1. Press Space Bar and enter Translation; the Batch Translate Dialog Box is displayed.
2. In the Scope tree, select the designs and diagrams in which you want to perform the
action and click Translate; a progress bar indicates that the action is being performed.
Results
• A Batch Translate tab in the Output Window at the bottom of the application reports on
the results of the action.
• If multiple entries are found for a particular text in the language dictionary, the first one
whose quick code appears alphabetically is used.
Related Topics

December 2023
Introduction
Running Capital Tasks in the Background (Flexible Execution Model)
Running Capital Tasks in the Background

(Flexible Execution Model)
Capital can use a Flexible Execution Model (FEM) to process long running and recurring tasks,
such as Harness Processing, Design Rule Checks (DRCs), running FMEA scenarios, Tagging,
Costing, or Global Library tasks, in the background. These tasks can be distributed across one
or more task servers for efficient execution. In this way, engineers avoid waiting for tasks to
complete and reduce design cycle times. In addition, FEM allows any Capital task to be started
by a third-party web-service using the same infrastructure as Capital’s own integrated
functionality. Please note, it is mandatory to run at least one Capital Integration Server (Capital
Integration Server Controller) in your Capital environment to ensure all base functionality is
available.
Note
For information about setting up and configuring Capital to use FEM tasks see the “Flexible
Execution Model (FEM)” chapter in the Capital Installation and Upgrade - Additional
Information guide (available with the release documents).
Modular) in the Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Running FMEA Scenarios in Capital Analysis in the Background . . . . . . . . . . . . . . . . 94
Creating Audit Reports When Capital Analysis Operations are Run in the Background 95
Running ICD Publication from Capital Logic Designer in the Background . . . . . . . . . 96
Running Harness Processing in Capital Harness

Designer (or Capital Harness Designer Modular) in
the Background
You can use the flexible execution model to run harness processing in Capital Harness Designer
(or Capital Harness Designer Modular) as a task in the background.
See also “Processing a Harness Design” in the Capital Harness Designer User Guide.
Prerequisites
• You must have configured the Capital Integration Server that is running as the Capital
Integration Server Controller. See “Configuring a Capital Integration Server as the
Capital Integration Server Controller” in the Capital Installation and Upgrade -
Additional Information guide (available with the release documents).

December 2023
Introduction
Running SBOM Generation and Costing in Capital Harness Process Designer in the Background
• You must have configured the Capital Integration Servers that are running as the Capital
Integration Server Workers. See “Configuring a Capital Integration Server as a Capital
Integration Server Worker” in the Capital Installation and Upgrade - Additional
Information guide.
• The Capital Integration Servers must be running. On the Capital Integration Server
Controller computer, you must have logged in to the Capital Integration Server with a
user name and password.
• The client from which you are running harness processing must have been configured to
connect to the Capital Integration Server Controller. See “Configuring a Client to
Connect to the Capital Integration Server Controller” in the Capital Installation and
Upgrade - Additional Information guide.
Note
In order for design logs to be created when background harness processing is running, the
local system where the Capital Integration Server instance is running must have access to
the design log repository. See “Server Setup for FEM Tasks” in the Capital Installation and
Upgrade - Additional Information guide for details on Capital Integration Server configuration.
Procedure
Run harness processing as detailed in the “Processing a Harness Design” topic in the Capital
Harness Designer User Guide but ensure that you select the Background Run box at the
bottom of the Harness Processing dialog box.
Note
If you want to use scheduling when running harness processing in the background,
you can use web services to schedule it. See the WebServiceDevelopment.pdf
document located in the doc folder of your Capital installation for more information
about web services.
Results
When the harness processing starts, the task will be viewable in the Tasks tab.
Related Topics
Tasks tab in Output Window
Running SBOM Generation and Costing in Capital

Harness Process Designer in the Background
You can use flexible execution model tasks to run SBOM generation and costing in Capital
Harness Process Designer as a task in the background.

December 2023
Introduction
Running SBOM Generation and Costing in Capital Harness Process Designer in the Background
See also “Generating an SBOM” in the Capital Manufacturing Systems Solutions User Guide.
Prerequisites
Information guide.
• The client from which you are running SBOM generation and costing must have been
configured to connect to the Capital Integration Server Controller. See “Configuring a
Client to Connect to the Capital Integration Server Controller” in the Capital
Installation and Upgrade - Additional Information guide.
• Capital Harness Process Designer are installed, with the appropriate licenses, on your
remote machines.
Procedure
Run SBOM generation and costing as detailed in the “Generating an SBOM” topic in the
Capital Manufacturing Systems Solutions User Guide but ensure that you select the
Background Run box at the bottom of the SBOM Processing Wizard dialog box.
Note
If you want to use scheduling when running SBOM generation and costing in the
background, you can use web services to schedule it. See the
WebServiceDevelopment.pdf document located in the doc folder of your Capital
installation for more information about web services.
Results
SBOM generation and costing runs, the task will be viewable in the Tasks tab of the Output
window.
Related Topics

December 2023
Introduction
Running FMEA Scenarios in Capital Analysis in the Background
Running FMEA Scenarios in Capital Analysis in the

Background
You can use flexible execution model tasks to run FMEA analysis scenarios in Capital Analysis
as a task in the background.
Prerequisites
Information guide.
• The client from which you are running the FMEA task must have been configured to
Procedure
Use the FMEA Wizard to run an analysis scenario as detailed in the “Creating FMEA
Scenarios” topic in the Capital Analysis User Guide, but ensure that you select the Background
Run box at the bottom of the Run Scenario dialog box.
Note
If you want to use scheduling when running FMEA analysis in the background, you
can use web services to schedule it. See the WebServiceDevelopment.pdf document
located in the doc folder of your Capital installation for more information about web
services.
Results
When the FMEA starts, the task will be viewable in the Tasks tab in Output Window.
Related Topics

December 2023
Introduction
Creating Audit Reports When Capital Analysis Operations are Run in the Background
Creating Audit Reports When Capital Analysis

Operations are Run in the Background
You can create audit reports for Capital Functional Verifier, Capital Component Sizer, and
Capital Analysis Scripter in Capital Analysis as a task in the background (using the flexible
execution model).
See also the “Creating a SCA Report”, the “Stress Analysis Wizard”, and the “Using a Script
File” topics in the Capital Analysis User Guide, for more information on creating the required
audit report.
Prerequisites
Information guide.
• The client from which you are running the “Create audit report” task must have been
configured to connect to the Capital Integration Server Controller. See “Configuring a
Client to Connect to the Capital Integration Server Controller” in the Capital
Installation and Upgrade - Additional Information guide.
Procedure
Use either the SCA Wizard, the Stress Analysis Wizard or the simulation tool, Capital Analysis
Scripter tab to create the required audit report as detailed in the “Creating a SCA Report”, the
“Stress Analysis Wizard”, and the “Using a Script File” topics in the Capital Analysis User
Guide, but ensure that you select the Run in background box at the bottom of the appropriate
dialog box.
Note
If you want to use scheduling to create audit reports when running analysis
operations in the background, you can use web services to schedule it. See the

December 2023
Introduction
Running ICD Publication from Capital Logic Designer in the Background
Results
When the audit reports are created, the task will be viewable in the Tasks tab of the Output
window.
Running ICD Publication from Capital Logic

Designer in the Background
You can use the flexible execution model (FEM) to run ICD publication from Capital Logic
Designer as a task in the background.
See also the Background ICD Publication From Capital Logic Designer topic in the Capital
Logic Designer User Guide.
Prerequisites
Information guide.
• The client from which you are running ICD publication must have been configured to
Procedure
Create and update ICDs as detailed in the “Creating ICDs from Capital Logic Designer” topic in
the Capital Logic Designer User Guide, ensuring that your web service triggers, such as Build
List Release Level Change and (Design) Release Level Change, are enabled.
Note
If you want to use scheduling for background ICD publication you can also use web
services or an external program to run the background task regularly. See the

December 2023
Introduction
Running ICD Publication from Capital Logic Designer in the Background
Results
When the ICD publication is triggered, the task will be viewable in the Tasks Tab.

December 2023
Introduction

To access: Press Space Bar and enter Tasks in a design tool.
Use this tab to view the status of tasks that have been submitted to run in the background.
Objects
Table 1-6. Tasks Tab Contents
Field Description
Delete If the selected task in the Tasks Table has not been executed yet,
this deletes the selected task.
If the selected task in the Tasks Table is a recurring task or is a
failed task scheduled for a rerun, this stops the selected task but
does not delete it.
Only the user who submitted the task or a superuser can use this.
Refresh Refreshes the tasks listed in the Tasks Table.
View Logs Allows you to view the log files for the tasks listed in the Tasks
Table.
Tasks Table Lists the tasks that have been performed in the background or are
scheduled to be performed in the background. Also details the name
of the design on which the task has been performed. The user id of
the person who initiated the task. The start and end time of the task
performance, the machine it was run on and its current status -
whether it is running, stopped, failed, completed, and so on. Results
can be filtered by typing in the task tab field, for example to filter
by user. Clicking the dropdown in the corner of the fields toggles
the display between ascending and descending filter results.
Tip: If user names contain the domain name as well, for
example abc\john.doe, it is recommended to filter with just the
name, excluding the domain name. For example, search/filter string
could be john.doe. This is to avoid the search string being treated as
an escape sequence. If domain name must be included in the
filtering, use \\ instead of \. For example, abc\\john.doe.
Today / Yesterday / Past Specifies the time period for which tasks are displayed in the Tasks
Week / Table.
Future

December 2023
Introduction
Running Documentation Package Generation in Capital E/E Publisher in the Background
Related Topics
Background
Running Documentation Package Generation

in Capital E/E Publisher in the Background
You can use the flexible execution model to run documentation package generation in Capital
E/E Publisher as a task in the background.
Publication using background tasks can be used to produce large packages, or ones that need to
be frequently produced, saving precious time and resources. It also enables packaging
automation using scheduled tasks and trigger events. See the “Generating Documentation” topic
in the Capital E/E Publisher User Guide for more information.
Prerequisites
• You must have configured the Capital Integration Server that is running as the task
execution controllers. See “Configuring a Capital Integration Server as the Capital
Integration Server Controller” in the Capital Installation and Upgrade - Additional
Information guide (available with the release documents).
• You must have configured the Capital Integration Servers that are running as the task
execution workers. See “Configuring a Capital Integration Server as a Capital
Information guide.
• The Capital Integration Servers must be running. On the task execution controller
computer, you must have logged in to the Capital Integration Server with a user name
and password.
• The client from which you are running package generation must have been configured to
connect to the task execution controller. See “Configuring a Client to Connect to the
Additional Information guide.
Procedure
Generate a Capital E/E Publisher documentation package as detailed in the “Generating
Documentation” topic in the Capital E/E Publisher User Guide but ensure that you select the
Background Run check box at the bottom of the Generate Documentation dialog box.

December 2023
Introduction
Searching for an Action on the Ribbon
Note
If you want to use scheduling when running documentation generation in the
background, you can use a web services to schedule it. See the
Results
When the documentation package generation starts, the task will be viewable in the Tasks Tab.

The ribbon at the top of an application contains tabs with menu items and buttons for various
actions. You can use the Ribbon Helper to find a particular action.
Procedure
1. Press Space Bar or click the Capital tab on the ribbon and click the Ribbon Helper
button, a Search Ribbon dialog box displays.
2. Start typing the name of the action in the box; the Ribbon Helper searches for actions
matching the string.
Note
If your installation is using a non-English locale language, you can type text in the
locale language, the English language, or a mixture of the two.
For example, if you are using a Japanese locale, you could enter “Add” (just English
text), “ ” (just Japanese), or “ ” (a mixture of Japanese and English).
When using a mixture, you must have a space between the different language strings,
such as “ ”. “ ” would not match any actions.
Results
If only one actions matches the string, the ribbon jumps to the appropriate tab and the action is
highlighted.
If multiple actions match the string, the dialog box lists the matches. Click the action you want
and the ribbon jumps to that action.
If your installation is using a non-English locale language, the matching actions are displayed in
the locale language (even if you entered English text).

December 2023
Introduction
Note
Matching actions may be displayed in the Search Ribbon list because their tooltip contains
the string typed in the text box. For example, when searching for the term “Translation” a
result of Language Dictionary is returned as its tooltip references its translation role.
To activate an action, do one of the following:

• Select it in the search results and press Enter
• Double-click it in the search results
• Click it on the ribbon

December 2023
Introduction
Configurable Ribbon
Configurable Ribbon
You can configure which actions are displayed on the ribbon based on design type and
abstraction.
Filtering Out Ribbon Actions Based on Design Type and Abstraction . . . . . . . . . . . . . 102
Filtering Out Ribbon Actions Based on Design Type

and Abstraction
By default, the ribbon at the top of a design application provides all available actions for the
currently active design type. A system administrator can adjust the available actions based on
design type and abstraction. That is, the administrator can filter out actions that are not
applicable for a given abstraction or design type.
Note
Filtering out a ribbon action also filters out menu items and buttons for that action elsewhere
on the application interface.
Restrictions and Limitations

You cannot filter out the following actions in the design tools:
• Quick Links
• Custom actons
• Extensions actions
• Auto-route actions
• Save message dialog box when closing a diagram, project, or application
Procedure
1. Navigate to the <installation_directory>/config/ActionFilter.xml file.
2. Open it in an editor.
3. For each action that you want to filter out, you need to add a filteredaction section. The
file contains some example sections.

December 2023
Introduction
Filtering Out Ribbon Actions Based on Design Type and Abstraction
Figure 1-10. A filteredaction secton
See “Example filteredaction Sections” on page 104 in the Examples section below.
a. Ensure that any sections you want to apply are not commented out with .
b. For each filteredaction section, specify the name and target values. To identify the
name and target values, you press CTRL-SHIFT-<click_the_action> in a design
application. The values are displayed in a Main tab in the Output Window at the
bottom of the application.
Figure 1-11. Name and Target Values for a Ribbon Action
c. Specify application names and design abstractions for which that ribbon action will
be filtered out.
For the application name, remove the word Capital. You can use lowercase,
uppercase, or camel case characters. For example, ‘systems integrator’ for Capital
Systems Integrator.
4. Save the file in an accessible location.
Note
The file must be called ActionFilter.xml. You can save it in any accessible location
but you must specify that path in the Action Filter system preference. In the example
below, the ActionFilter.xml file is saved in a directory C:\Program Files\Siemens\
ActionFilter. If you do not specify a path in the preference, or if the system cannot find
the file in the specified path, it reads the <installation_directory>/config/
ActionFilter.xml file.
Results
When you next open the impacted applications, the actions are filtered out as specified.

December 2023
Introduction
Filtering Out Ribbon Actions Based on Design Type and Abstraction
If an entire column or row of actions are filtered out in a section of the ribbon, the available
actions are re-aligned.
Figure 1-12. Default Ribbon Before Filtering
Figure 1-13. Ribbon with Plug/Jack/Inline Actions Column Filtered Out
Figure 1-14. Ribbon with Pin/Inline/Assembly Actions Row Filtered Out
Examples
Table 1-7. Example filteredaction Sections
Example filteredaction Section Impact on Ribbon
<filteredaction name="Add Device Without Pins" The Add Device Without Pins
target="chs.caplets.logic.actions.CreateNoPinDevic action will not appear on the
eActionUI">
<applicability>
ribbon in Capital Logic
<application name="logic designer"> Designer when you open a
<designabstraction name="System Design"/> design with the abstraction
</applicability > ‘System Design’. It will appear
</filteredaction > for designs with other
abstractions.
filteredaction name="Add Block " The Add Block action will not
target="chs.caplets.logic.actions.CreateBlockDevic appear in the Capital Logic
eActionUI">
<applicability>
Designer and Capital Systems
<application name="logic designer|platform Architect applications for any
designer"/> designs regardless of their
</applicability > abstraction.
</filteredaction >
Note: The | character is
used to separate the
application names.

December 2023
Introduction
Searching for an Object
Table 1-7. Example filteredaction Sections (cont.)

Example filteredaction Section Impact on Ribbon
<filteredaction name="Add Highway" The Add Highway action will
target="chs.caplets.logic.actions.CreateHighwayAct not appear in any application
ionUI">
<applicability>
for any designs with an
<designabstraction name="System Design"/> abstraction of ‘System Design’
<designabstraction name="Platform Design"/> or ‘Platform Design’. It will
</applicability > appear for designs with other
</filteredaction > abstractions.
<filteredaction name="Slice objects" The Slice objects action is not
target="chs.caplets.logic.actions.SliceActionUI"> available in any applications
</filteredaction >
for any designs regardless of
their abstraction.

In design applications, you can search for an object by name in the currently open project and
navigate to the identified object instances from the search results. You set a search scope when
doing this so that you search in the currently open design, in the currently active build list, in the
currently active working set, or in the whole project.
Caution
You cannot search for signal and wiring objects in Capital Wiring Integrator designs
because they are not saved, they are synchronized from associated logical designs.
This search functionality is aware of domain restrictions. For example, if a design has a domain
restriction and a user performing this search does not have access to that domain, the search
results will not include objects from that design.
Prerequisites
• The project must be open.
Procedure
1. Either press Space Bar and enter Search Objects, or press Shift-Space Bar.
A Search Objects dialog box displays.

December 2023
Introduction
2. Click the Scope dropdown ( ) to set the search scope.
Table 1-8. Search Scope Selection

Scope Description
Searches in the currently open design.
Active Design
Enabled only when a design
is open.
Searches in the designs in the currently active build
list.
Active Build List
Enabled only when you have
an active build list.
Searches in the designs in the currently active working
set.
Active Working Set
Enabled only when you have
an active working set.
Searches in all the designs in the project.
Project
Note
The dialog box remembers what you selected when you last accessed it.
3. Enter a string contained in the name of the object to be found.

If you enter a string without a wildcard, the search looks for objects whose name
contains the string anywhere. For example, if you enter dev, the search results include
objects with names such as 2N-DEV, DEV-123, 3N-DEV-456, and so on.
You can use additional wildcards (*) or search options in the string.
Table 1-9. Additional Search Options

Search Option Description
Case Sensitive The search treats uppercase and lowercase letters as
distinct characters.
Starts With The search compares the string from the beginning of
the object name.

December 2023
Introduction
For example:
• If you enter dev and select Starts With, this specifies a STARTS WITH dev search
and the results include objects such as dev, dev1, dev100, dev1000, and so on. The
results do not include an object such as sh_dev.
• If you enter dev*batt, this specifies a STARTS WITH dev AND ENDS WITH batt
search. The results include objects such as devbatt, dev1batt, devengine_batt, but do
not include devbattery or sh_dev_batt.
o Extending this example, if you also select Case Sensitive, the results include
objects such as devbatt, dev1batt, devengine_batt, but do not include DEV1batt.
4. Press Enter.
Results
The results display in a Search tab in the Output Window at the bottom of the application
interface.
Figure 1-15. Search Tab in Output Window
Each result includes the following information:

• Abstraction
The abstraction of the design in which the object instance is located. If no design
abstraction is set, this displays the design type.
• Name
The name of the object and an icon indicating what sort of object it is. The name is a
hyperlink. You can click the name to navigate to that object in a diagram in the
appropriate application (which will open automatically).
• Design
The name of the design in which the object instance is located.

December 2023
Introduction
Reordering Browser Tabs on the Bottom Left of a Design Application
• Build List
The name of the build list in which the object instance is located.
Note
The columns are sortable by clicking the column header name. The columns are filterable
by clicking the dropdown in the header or by typing in the header.
Reordering Browser Tabs on the Bottom Left

of a Design Application
You can change the order of the tabs for browser windows on the bottom left of a design
application interface by dragging and dropping them.
Procedure
Drag and drop a tab to the new location among the tabs. A blue line indicates the target location.
Figure 1-16. Blue Line Indicating Target Location
Results
• If you drop the tab among the other tabs, that tab docks in the new location.
• If you drop the tab away from the other tabs, that tab undocks and displays as a separate
window.
Note
To return an undocked tab to the bottom left of the main application interface, close
the separate window. It returns to its previous position among the tabs.
• The new order is retained when you close and open the design, project, or application.
Undocking Browser Windows

You can undock and move any browser windows and tabs displayed at the bottom left of the
application window.
Procedure
1. Click the tab of the browser window and drag it to the location where you want to
display it.
2. Resize the browser window as required.

December 2023
Introduction
Creating and Using Quick Links
Note
To return the browser window to the bottom left of the main application window,
close the separate window. It returns to its original position automatically.
Creating and Using Quick Links

You can configure quick links entries to access an external weblink, network directory, or file
from within Capital. Quick links entries are launchable URL locations that are displayed as
menu items under the ribbon ‘Quick Links’ icon.
Prerequisites
• To create new Quick Links entries you should be a system administrator.
Procedure
Choose an action:
If you want to... Do the following:

Create a new Quick 1. Navigate to the config/clientprops.xml file in your
Links entry installation, and open the file in an XML editor.
2. Within the < quicklinks > tags section, create a new <
definition > tag with the following attributes:
• displaytext = “<text>”
Where <text> is the text to be shown as a clickable option
under the Quick Links ribbon menu.
Note: If displaytext is left empty (displaytext = “ ”),
but the url field is defined, then the url value as
display text will be shown in the Quick Links dropdown
menu.
• url = “<path>”
Where <path> is a link or path to a desired location, either
to an external weblink, network directory, or to a file in
the system.
3. When you have finished editing the file, save and close it.
Note: You will need to relaunch your Capital application
for any new Quick Links to appear.

December 2023
Introduction
Launch Pane

Launch a Quick Links 1. On the ribbon, click the down arrow on the Quick Links
entry
icon to display the available quick links

Note: If you click the icon itself the default quick link
will launch. The first defined quick link is considered
the default.
2. From the displayed menu items, select the quick link you
want to launch.
Note: : If your quick link fails to launch, check the
console window for any issues.
Examples
• Quick links clientprops.xml definition to open the Siemens Capital homepage
<quicklinks>
<definition displaytext="Siemens Capital" url="https://

www.plm.automation.siemens.com/global/en/products/capital/"/>
</quicklinks>
• Quick links clientprops.xml definition to open a network location:

<quicklinks>
<definition displaytext="Network Directory" url="file://inh/dfs/"/>
</quicklinks>
Launch Pane
The Launch Pane is displayed in a design application when no diagram is open.
The top panels on it change each release and provide links to information on such things as new
functionality.

December 2023
Introduction
Sort Order
At the bottom of the launch pane, the following icons link to the following sources of
information:
Table 1-10. Launch Pane Icons
Launch Pane Icon Links to:
InfoHub Locally-installed user guides with links to SupportNet.
Communities Discussions with other Capital users around the world,

where you can get the latest guidance and advice.
IDEAS A facility where you can suggest ideas for enhancements

to the Capital software.
On Demand Training Siemens Learning Services where you can enroll on

courses about Capital software.
Support Center Siemens customer support site.
Sort Order
When you apply a sort order to a list of objects in Capital (for example, library parts listed in the
Component Maintenance dialog box in Capital Component Manager), the system applies the
sort order in a particular way.

December 2023
Introduction
Sort Order
The sort order is:
• Strings starting with special characters

• Numeric strings
• Alphabetical strings
For example:
!Terminal
123
124
255
366
AB-1
AIR
C-1
Coax
For alphanumeric strings, the sorter compares only the numeric portion.
For example, if you have two strings, 0A123 and 1211A, it compares only the starting numerals
first and pads them with 0 to make numeric strings of equal length to decide which goes first.
In this example, 0A123 starts with 0. 1211A starts with four numerical characters 1211 and then
the alphabetical character A. As the system compares only the starting numerals to decide
which goes first, it pads the numeric value 0 (from 0A123) with a further three characters of 0 to
make the numeric values for comparison of equal length. Therefore:
0000 (from 0A123)
1211 (from 1211A)
If the numeric portion is the same, it includes the alphabetical characters for comparison.
If a 0 is followed by a number, the 0 is ignored and the number is sorted. If the 0 is followed by
a letter, the zero is not ignored.

December 2023
Introduction
Sort Order
So 01111, 1112, A12345, 0A12346 sort like this:
0A12346
01111
1112
A12345
In this case, the numeric portion of 0A12346 is compared with the rest of the values and it
displays first.

December 2023
Introduction
Call Home Packages
Call Home Packages

Call home packages are information that the system saves and forwards to Siemens or your own
internal support automatically when an error occurs. The package contains the context and
action history that led to the error. These packages provide additional information that a user
may not be able to capture and remember. This information helps in understanding the cause of
errors. Based on the criticality and frequency of these errors, these issues are analyzed and fixed
in future releases.
The call home package is a zip file containing several folders and files. The zip file name
contains the application name, the user name, and the date (for example,
Data_CapitalLogic_user1_2017-11-06T16-01-06.zip).
The call home package typically contains the following structure:
Figure 1-17. Call Home Package Folders
The Configuration folder contains all the configuration files used by Capital, for example,
clientprops.xml, launcherprops.xml, and so on.
The Context folder contains the data.
Figure 1-18. Call Home Context Folder

December 2023
Introduction
Call Home Packages
Note
There is a system preference to enable the inclusion of design data (Include Design and
Project Data). If you enable this option, design data and project data (XML) are also
included in a separate folder called Data. That folder may contain project data, design data,
system data, image dictionary, symbol dictionary, snippet of data loaded from Capital Manager,
open diagram screenshot, and so on. Many users clear this option so that their design data is not
shared.
If you remove some files from the package (for example, files that include server names), the
package is still useful for analyzing errors.
• Action History
Contains the details about the action that was performed by the user which potentially
led to the call home. It can contain information like the project name, design name, and
so on.
• Jar File Manifests
Contains lists of all jar files in the lib folder and adaptors/lib folder of your Capital
installation. Also contains details about those jar files.
• Open Diagrams
Contains a list of the names of any diagrams that were open at the time of the crash.
• Plugin Information
Contains details about any plugins being used. Does not contain the plugin jar files.
• Scrub On The Fly
Contains details of any data inconsistency fixes from this session.
• Selection
Contains ids of any objects selected by the user at the time of the crash.
• System Environment
Contains all environment variables.
• Undo Queue
Contains ids of objects that were modified as part of the last few actions. Some actions
can be undone.
• Working Set
Contains a list of all designs that were part of a working set in Capital.

December 2023
Introduction
Specifying Preferences for Call Home Error Reporting
The Error folder contains all the application logs, exception stack trace, thread state of the
application, Manager logs.
Figure 1-19. Call Home Error Folder
Note
The Error folder is the most useful folder because it shows the code where the exception
occurred. For some types of error (such as a validation error), the stack trace may contain
parts of your data (for example, names of project, design, diagram, and object).
Specifying Preferences for Call Home Error Reporting . . . . . . . . . . . . . . . . . . . . . . . . . 116

Manually Creating a Filtered Call Home Error Report . . . . . . . . . . . . . . . . . . . . . . . . . 117
Specifying Preferences for Call Home Error

Reporting
System preferences enable you to specify various settings for the creation of call home packages
when an error occurs (for example, whether design and project data is included, where the data
package is sent).
Procedure
1. In Capital Project Manager, expand the System node of the Project Browser Tree and
double-click the Preferences node; a Preferences dialog box displays.
2. Click the Error Reporting and Recovery node on the left of the dialog box; preferences
for call home packages appear on the right. See the System Preferences for Error
Reporting and Recovery (Call Home) table in System Preferences Dialog Box in the
Capital Project Manager User Guide for descriptions of each setting.
Note
In order for Siemens to correctly track any reported issues, ensure you supply your
Site ID and Name in the preferences.

December 2023
Introduction
Manually Creating a Filtered Call Home Error Report
Manually Creating a Filtered Call Home Error

Report
You may have an existing error report that contains sensitive design information that you do not
want to send to support services. You can create a filtered version of the full error report.
Prerequisites
Use the following files in the config directory of your installation to configure what information
is filtered out of the report:
• FilterErrorReportDefaultAllowList.txt
Use this to specify an allow list of folders and files (such as log files) that you do want
included in a filtered error report data package.
• FilterErrorReportDefaultRules.json
Use this to specify error report data package files in which you want to hash or remove
certain values. For each data package file you specify which values are to be hashed or
removed.
Instructions for editing FilterErrorReportDefaultRules.json are located in a config/
FilterErrorReportDefaultRules.json.example file. Instructions for editing
FilterErrorReportDefaultAllowList.txt can be found in the same file.
Note
You can use this procedure to test (debug) the FilterErrorReportDefaultAllowList.txt and
FilterErrorReportDefaultRules.json files that the system references when creating filtered
error reports. See the System Preferences for Error Reporting and Recovery (Call Home) table
in “System Preferences Dialog Box” in the Capital Project Manager User Guide for further
information about specifying the settings for error reporting.
Procedure
From a command line, navigate to your installation/bin directory, and run
FilterErrorReport.bat (on Windows) or FilterErrorReport.sh (on Linux) using the following
command line arguments as needed:
Switch Description
-h Displays a list of supported switches and application usage information.
-i Specifies the location of the call home error reports to be filtered. The
procedure will filter all call home error reports in that location. By default,
this is: ./input/
-o Specifies the location where you want to save the filtered versions of the
error reports. By default, this is: ./output/

December 2023
Introduction
Capturing Performance Profiling Data and Heap Dump Data
Switch Description
-r Specifies the path and name of the rules file you want to use. By default,
this is: ./FilterErrorReportDefaultRules.json
-w Specifies the path and name of the allow list file you want to use. By
default, this is: ./FilterErrorReportDefaultAllowList.txt
-x If used, this specifies that you want to overwrite zips in the output
directory if they have the same name. This is useful if repeatedly running
the program against the same input and output.
Results
• The filtered error reports are saved in the output location.
• If there is an issue with the allow list or rules file, the program displays a detailed
message stating that there is an error in the configuration files and that the filtered error
report was not created.
Capturing Performance Profiling Data and

Heap Dump Data
Profiling data and heap dumps allow Siemens support and engineering teams to identify the
cause of application slowdown or unusual memory consumption. An analysis of the profiled
data can pinpoint the amount of time taken by a particular function to execute.
Profiling data can be captured without having to restart the client application and with little to
no assistance required from an IT administrator. A user can start capturing profiling data
whenever they experience slow application response. Among the details captured are client and
database interactions, as well as information such as ping times, upload and download speeds,
and application log files.
Once profiling is stopped, all the captured data is compressed into a single zip file and saved.
This data can be shared with the Siemens development or services team for further analysis.
This functionality is available in both design applications and non-design applications.
Procedure
Follow the appropriate procedure for a design or non-design application.

December 2023
Introduction
Note
If you stop an application before completing the capture of profiling or heap dump
data, the capture action also stops and no data is saved.

Capture performance profiling 1. Select the Help > Start Profiling action on the
data in a design application ribbon at the top of the application.
An icon ( ) on the status bar at the bottom of the
application indicates that profiling is in progress.
2. Perform the actions that you have identified as
running slowly.
3. Click the profiling icon on the status bar or select the
Help > Stop Profiling action on the ribbon.
The profiling icon on the status bar disappears and
the Main tab of the output window at the bottom of
the application informs you that a zip file is saved in
the temp folder defined for the software suite.
Capture performance profiling 1. Select the Help > Start Profiling menu option at the
data in a non-design application top of the application.
2. Perform the actions that you have identified as
running slowly.
3. Select the Help > Stop Profiling menu option at the
top of the application.
A window informs you that a zip file is saved in the
temp folder defined for the software suite.
4. Click OK.
Capture heap dump data in a Select the Help > Capture Heap Dump action on the
design application ribbon at the top of the application.
A progress bar displays and then the Main tab of the
output window at the bottom of the application informs
you that a zip file is saved in the temp folder defined for
the software suite.
Capture heap dump data in a 1. Select the Help > Capture Heap Dump menu
non-design application option at the top of the application.
A progress bar displays and then a window informs
you that a zip file is saved in the temp folder defined
for the software suite.
2. Click OK.

December 2023
Introduction
Results
The zip file contains files with the captured data that you can send to Siemens support and
engineering for analysis.
Table 1-11. Profiling Data and Heap Dump Zip Files
Zip File Included Files
Profiling data • .jfr file
A file that can be opened in VisualVM and contains all of the details
for analyzing the performance issue. You can send this to Siemens
support.
• .log file
A log file that contains the Manager interaction details, such as ping
response time between client application and Manager, upload and
download speed between client application and Manager, ping
response times between Manager and database, and the call statistics
for the Manager API calls made from the client application.
You can view this file as well as send it to Siemens support.
Heap dump .hprof file
data A file that contains the heap dump data. You can send this to Siemens
support.

December 2023
Chapter 2
Projects and Designs
This chapter contains details about how to perform various generic management and editing
actions on projects and designs.
Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Project Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Deleting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Capital Compressed Format for Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Exporting a Project in Capital Compressed Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Importing a Project in Capital Compressed Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Copying Designs From One Project to Another . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Migrating a Design from Capital Harness Classic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Comparing Objects and Their Properties in Design Revisions or Build Lists . . . . . . . . . . 241
Mass Design Revision and Effectivity Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Design Rule Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Design Rule Check Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Searching for a Design across all Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Design Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Build List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Applying Scopes to a Project or Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Options and Option Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Creating an Option at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Defining Inclusive and Exclusive Relationships for an Option . . . . . . . . . . . . . . . . . . . . . 430
Creating an Option Folder at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431

December 2023

Deleting an Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Engineering Change Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438
Working with an ECO Created in Capital . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Creating an Engineering Change Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Deleting an Engineering Change Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Viewing Engineering Change Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Assigning an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Capture and Apply a Change Within an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Identification of Topology Changes with Hotspots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Harness Object Behavior on Applying ECO Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452

December 2023
Projects
Projects
The information that is contained within a project is arranged into distinct sub-containers called
designs. Designs are versionable data containers that can have their contents copied as required.
A design is usually created for each sub-system of a product line and contains diagrams created
in one of the design applications (for example, system or wiring diagrams from Capital Logic
Designer, harness diagrams from Capital Harness Designer or topological diagrams from
Capital Systems Integrator).
Project Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Deleting a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Capital Compressed Format for Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Exporting a Project in Capital Compressed Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226
Importing a Project in Capital Compressed Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Project Browser
The Project Browser is located on the upper left side of the application window. It allows you to
view and access the designs and diagrams in a project, and allows you to perform various
actions.
It contains the following:
• Close Project ( ) button
Closes the currently viewed project.

• Project Dropdown List
Lists the current open projects to select the one that you want to view.
• Project Browser Tree
Lists the designs and diagrams that have been created for the project. To expand a
section of the browser tree, click . To collapse a section of the browser tree, click .
• Enter Filter String ( ) / Clear Filter String ( )

December 2023
Opening a Project
In the field next to the Enter Filter String icon ( ), enter a series of characters. A filter
is applied to the Project Browser Tree so that only designs with names containing that
series of characters are listed.
The behavior of the filter varies depending on such things as whether you use wildcards
and the case (upper or lower) of the specified characters. See “Browser Tab and Dialog
Box Filters” on page 880 for further information.
Click the Clear Filter String icon ( ) to clear the filter and view all designs in the
project.
• Design Filter ( )
Click the dropdown list to filter the designs displayed in the Project Browser Tree
window to those of a particular type, all designs in the project or all designs in the
currently active build list.
Related Topics
Opening a Project
Creating a Project
Deleting a Project
Importing a Project
Exporting a Project
Closing a Project
Project Preferences
Opening a Project
You can open an existing project in a design tool so that it displays in the project browser and
you can edit it.
Procedure
1. Press Space Bar and enter Open.
The Open Project Dialog Box is displayed.
2. Click the project that you want to open and click OK.
Note
You can filter which projects display by entering a string in the field where the
Enter Filter String icon ( ) displays. Filtering is based on project name only.

December 2023
Creating a Project
Results
The project opens and is added to the Project Browser.
Related Topics
Creating a Project
Deleting a Project
Importing a Project
Exporting a Project
Closing a Project
Project Preferences
Creating a Project
You can create a project from within a design application and use it as a container for the
designs required for a vehicle.
Once a project has been created, all project-level data can be managed within Capital Project
Manager. Refer to the Capital Project Manager User Guide for more information.
Procedure
1. Press Space Bar and enter New Project. The New Project Dialog Box is displayed.
2. Enter a Name for the project.
3. Click OK.
Results
The project is created and added to the Project Browser.
Related Topics
Opening a Project
Deleting a Project
Importing a Project
Exporting a Project
Closing a Project
Project Preferences
Deleting a Project
You can delete a project from the database when you no longer want to use it.

December 2023
Importing a Project
Caution
The deletion of a project can only be undone from a database backup.
Procedure
1. Open the project you want to delete.
2. Press Space Bar and enter Delete Project.
3. A message is displayed asking you to confirm the deletion. Click Yes to proceed and
delete the project.
Results
The project is removed from the database.
Related Topics
Opening a Project
Creating a Project
Importing a Project
Exporting a Project
Closing a Project
Project Preferences
Importing a Project
You can import a project (from a Project XML file) that has been exported from another
instance of Capital.
Procedure
1. Press Space Bar and enter Import Project. A generic file browser is displayed.
2. Navigate to the Project XML (*.xml) file to import.
3. Click Import Project. A progress bar monitors the status of the import and disappears
once complete.
Note
An imported project is not opened by default and must be opened manually.
Related Topics
Opening a Project
Creating a Project

December 2023
Exporting a Project
Deleting a Project
Exporting a Project
Closing a Project
Project Preferences
Exporting a Project
Projects may be exported from, and imported into, the Capital design databases (as XML files).
The use of XML files as the data-transfer medium enables the exchange of project data between
other data systems and also increases the portability of Capital project data. The data stored in
XML files is readily manipulated manually.
An exported project's XML file contains all of the information (options, object names, designs,
diagrams, and so on.) that are contained in its original database record.
Note
You must have the Analysis permission assigned to your user account in Capital Access
Manager if you want to import and export projects that have Analysis project models
attached to them.
Procedure
1. If you want to export the currently open project, press Space Bar and enter Export
Current Project, or right-click the project and select Export.
If you want to export a project that is not open, press Space Bar and enter Select Project
to Export; the Select Project dialog box is displayed. Select the project to export and
click OK.
The Export Project dialog box is displayed.
2. Specify the folder location and file name for the project's exported XML file.
3. Choose the following as required:
• As Copy
Select if you want the project to be exported with anonymous unique identifiers
(UIDs). This option replaces all of the exported project's database UIDs (within the
exported XML file) with anonymous UIDs so that the project can be imported back
into Capital in the future. A project exported with anonymous UIDs are
automatically assigned new UIDs when it is imported back into Capital.

December 2023
Closing a Project
Note
When a project is exported from Capital, its original record remains in the
database with its original UIDs. Therefore, if the project is exported without
anonymous UIDs, it cannot be imported back into Capital unless its UIDs have been
changed, as its original UIDs are already present in the original project in the
database and are not allowed to be overwritten.
4. Click Export Project; the selected project is exported from the database.
Note
When a project export is started, a complete snapshot of the current state of the
project and all its associated data is taken, it is this project snapshot that is then
exported. This is to prevent inconsistencies in data due to project modifications being
made by other users during an export.
Related Topics
Opening a Project
Creating a Project
Deleting a Project
Importing a Project
Closing a Project
Project Preferences
Closing a Project
You close a project in a design application when you have finished your current session of
working on it.
Procedure
1. Click the project in the Project Browser and either:
• Press Space Bar and enter Close Project
• Right-click the project and select Close Project
2. A warning prompts you to save any modified designs in the project. Click Yes to save
them and close the project. Click No to discard any changes you have made and close
the project.
Related Topics
Opening a Project
Creating a Project

December 2023
Saving Changes to Projects and Designs
Deleting a Project
Importing a Project
Exporting a Project
Project Preferences

As you edit diagrams in the design applications, you can save your changes.
Procedure
Decide the extent of the designs that you want to save:

Save the changes in the Press Space Bar and enter Save or click the Save action on the Home
currently active design ribbon.
(that is, the design for The system saves the changes in all open diagrams of the currently
which you are editing a active design. It does not save changes in diagrams that are open from
diagram). other designs.
Note: When you modify one or more diagrams for a design in a
session, the system asks you whether you want to save the
modifications only when you close the last diagram for that design.
A diagram with unsaved changes has a * character on the diagram
window tab showing its name:
The video shows an example of the save behavior when modifying

multiple diagrams for a design in a session.

December 2023

Save all designs in the 1. Close the project by clicking the project in the Project Browser at
project. the top left of the application window and either:
• Press Space Bar and enter Close Project
• Right-click the project and choose Close Project
2. A warning prompts you to save any modified designs in the
project. Click Yes to save them and close the project.
3. If you want to continue editing the designs in the project, open the
project and designs again in the appropriate design application.

December 2023
Project Preferences
Project Preferences
Project preferences are default settings that you specify for the designs and diagrams in a
project.
You specify them in the Project Preferences Dialog Box, accessed in the design applications by
pressing Space Bar and entering Project Preferences.
You can also edit them in Capital Project Manager by opening a project, expanding the Project
Browser Tree for that project and double-clicking the Preferences node.
Note
Some preferences work alongside Capital styling to control the appearance of designs. See
the Capital Diagram Styling User Guide for more information about all aspects of Capital
styling.
If a preference (for example, bundle thickness) is specified for an object type, whenever a new
instance of that object type is inserted into a design, it will automatically assume this pre-set
preference setting.
All new and existing designs within a project automatically inherit their project's preferences.
Note
Preferences can also be specified at the system level.
Project Preferences for Capital Analysis Designs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Project Preferences for Manufacturing Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Project Preferences for Capital Device Modeler. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Project Preferences for Capital Harness Designer and Capital Harness Designer Modular
Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
Project Preferences for Capital Systems Integrator Designs. . . . . . . . . . . . . . . . . . . . . . 158
Project Preferences for Capital Logic Designer Designs . . . . . . . . . . . . . . . . . . . . . . . . . 169
Project Preferences for Capital Project Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Project Preferences for Capital Wiring Integrator Designs . . . . . . . . . . . . . . . . . . . . . . 202
Project Preferences for Capital Systems Modeler Designs . . . . . . . . . . . . . . . . . . . . . . . 210
Project Preferences for Design Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
General Project Preferences Applicable to all Applications . . . . . . . . . . . . . . . . . . . . . . 217
Project Preferences - Checks Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

December 2023
Project Preferences
Project Preferences for Capital Analysis Designs

Certain project preferences are available specifically for designs and diagrams in Capital
Analysis. They are not applicable for any other Capital tool.
Table 2-1. Project Preferences for Capital Analysis Designs

Field Description
Default wire model The default wire model is available specifically for designs and
diagrams to have custom wire model if necessary.
Note: Wire model settings found in project preferences take the
highest precedence, followed by system preference settings.
Project Preferences for Manufacturing Tools

Harness Process Designer, Capital Work Instruction Publisher, and Capital Harness Costing.
They are not applicable for any other Capital tool.
Table 2-2. Project Preferences for Capital Harness Process Designer, Capital
Work Instruction Publisher, and Capital Harness Costing Designs
Field Description
Manufacturing Node Displayed in the Project Preferences browser.
Displays project preferences for Capital Harness Process Designer,
Capital Work Instruction Publisher and Capital Harness Costing
designs.
Sub-assembly name Displayed in the Project Preferences pane when you select the
prefix Manufacturing node in the Project Preferences browser.
Setting used to specify a prefix for sub-assemblies such as project or
design name. This is combined with a system generated suffix to
identify where a particular sub-assembly fits in the SBOM structure.
Sub-assembly part Displayed in the Project Preferences pane when you select the
number prefix Manufacturing node in the Project Preferences browser.
Setting used to specify a prefix for sub-assembly part number. This is
combined with a system generated suffix to help identify common
cross-harness sub-assemblies for maximum reuse and optimization.

December 2023
Project Preferences
Table 2-2. Project Preferences for Capital Harness Process Designer, Capital
Work Instruction Publisher, and Capital Harness Costing Designs (cont.)
Field Description
Part Number Displayed under the Manufacturing node in the Project Preferences
Rationalization browser.
Tolerance Used by the Set Master Part Numbers Dialog Box to filter the display
of similar sub-assembly part numbers whose wire/multicore length
differences are greater than but within the defined tolerance value
when configuring sub-assembly part number rationalization.
Mandatory.
Override Library Non- This project preference only displays if the system preference
BOM SBOM System “Include Library non-BOM objects in SBOM generation” is selected.
Preference This project preference allows you to override that system preference
on individual projects. See System Preferences Dialog Box topic in
Capital Project Manager User Guide for full information on the
system preference.
Checks Node See “Project Preferences - Checks Node” on page 220.
Project Preferences for Capital Device Modeler

Certain project preferences are available specifically when working with part number and
footprint details in Capital Device Modeler. They are not applicable for any other Capital tool.
Table 2-3. Project Preferences for Capital Device Modeler

Field Description
Capital Device Modeler Displayed in the Project Preferences browser.
Node Displays project preferences for Capital Device Modeler.
Do not automatically Select to place ICDs as non-shared objects, as the default action,
share ICD on placement irrespective of its applicability definition. Clear to place ICDs as
shared objects. Default is cleared.
See also “Placing ICDs” in the Capital Logic Designer User Guide.

December 2023
Project Preferences
Table 2-3. Project Preferences for Capital Device Modeler (cont.)

Field Description
Do not propagate part With this project preference set to on, the system will not add library
and footprint details part number and footprint details to the Device in Capital Logic
Designer, during placement or when running the “Update from ICD”
action. The design rule checks ICD part number mismatch, ICD
backshell inconsistency and ICD device connector inconsistency are
also ignored in this scenario.
Note: This is applicable for devices in the generative flow. The
part number and footprint allocation is delayed until the platform
allocation stage in Capital Systems Integrator, where an Assign
Footprint constraint can read these details from Capital Device
Modeler.
Note: If a variant ICD (one Logic device referencing multiple
ICDs) is placed then irrespective of this setting no part or
footprint will be assigned to the ICD.
Propagate Option This preference has three settings for propagating option expressions
Expressions from ICD from ICDs to the following Capital Logic Designer objects:
to Logic for: • Device
• Pin
• Net
It enables you to determine whether the device, pin, or net option
expression attribute is ‘mastered’ in the ICD or in Capital Logic
Designer. Each option can be selected individually from the others.
With the project preference selected for a device, pin, or net, the
option expression evaluated on the ICD will always overwrite any the
option expression held on that particular object in Capital Logic
Designer.
If the project preference is cleared, the ICD’s option will never
overwrite that specified in Capital Logic Designer.

December 2023
Project Preferences
Table 2-3. Project Preferences for Capital Device Modeler (cont.)

Field Description
Create ICDs This preference has three settings that activate or deactivate the
creation of ICDs:
• Disabled
• Enabled on released designs only
• Enabled on all designs
Selecting either of the Enable preferences allows you to define ICDs,
including pin and device attributes/properties, device connectors, and
signals connected to device pins from within Capital Logic Designer,
and transfer them using an action on the context menu of the design
or build list to Capital Device Modeler.
You can restrict ICD creation to Released Designs only by selecting
that preference.
If the third preference is selected, the ICD in Capital Device Modeler
inherits its release level from the source Capital Logic Designer
design, provided that the release level can be found at system level,
regardless of whether it is creating a new, or updating an existing,
ICD.
Automatically create With this preference set to on, the system will create a library part and
part number on ICD assign it to the ICD.
creation
Default part number This preference works in conjunction with the Automatically create
status part number on ICD creation preference. With that preference set to
on this allows you to set the default part number status to either
current or new.
Project Preferences for Capital Harness Designer and

Capital Harness Designer Modular Designs
Harness Designer and Capital Harness Designer Modular. They are not applicable for any other
Capital tool.
Table 2-4. Project Preferences for Capital Harness Designer and Capital
Harness Designer Modular Designs
Field Description
Applicable Options Displays project preferences for Applicable Options on Capital
Harness Designer and Capital Harness Designer Modular designs.

December 2023
Project Preferences
Harness Designer Modular Designs (cont.)
Field Description
Mandate Applicable Select to edit object expressions on design objects only when
Options applicable options are specified for the design.
Clear to edit object expressions on design objects regardless of
whether any applicable options are specified for the design.
Assembly Select the check boxes to include the following components inside
their owner’s assembly by default.
Selected - Updating assembly content updates the components in the
assembly.
• Additional Components
• Modular Connector Children
• Connector Backshells
• Backshell Plugs
• Backshell Seals
• Cavity Terminals
• Cavity Seals
• Cavity Plugs
• Extra Cavity Components
• Wire End Components
• Multicore End Components
• Any multicore end component, of a multicore that is part of an
existing assembly, is automatically added to the assembly.

December 2023
Project Preferences
Field Description
BOM ID Naming The BOM ID is a unique nomenclature displayed against a
component in the Bill of Materials table, the Composite BOM Table,
and in Bill of Material reports generated from Capital E/E Reporter.
The BOM IDs are created individually on each design, so parts used
in different designs may have different BOM IDs. They can be
represented in the diagram using Leader Line and Ballooning. The
Bill of Materials is sorted alphanumerically by the BOM ID.
BOM ID Naming contains sub-nodes for object types. Select the
sub-nodes to display settings for creating unique BOM IDs for library
parts used in a design. The unique ID is created when a component is
added to a design and is a component attribute that is displayed in the
BOM.
You can create BOM IDs for the following component types:
• Assembly (bought-in only)
• Backshell
• Cavity Plug
• Cavity Seal
• Clip
• Connector
• Device
• Grommet
• IDC Connector
• Multicore (non in-house only)
• Other
• Overbraid
• Splice (not including Ultrasonic Welds)
• Tape
• Terminal
• Tube
• Wire
Prefix The prefix added to the start of the BOM ID for library parts of this
object type.
Start The number used for the first BOM ID generated for this object type.
Increment The increment applied to the number in the BOM ID each time a new
BOM ID is generated for this object type.
Checks See “Project Preferences - Checks Node” on page 220.

December 2023
Project Preferences
Field Description
Composite BOM Configures the display of objects on the Composite BOM Table.
See also “Composite BOM” in the Capital Harness Designer User
Guide.
Object Type Lists all the objects you can display in a Composite BOM Table.
Show Total? Select to display a “Total number of...” row in the Composite BOM
Table for this object type.
Include Objects? Select to display a total row for individual component part numbers
of the object type.
Total Rows Position Select Top or Bottom to display the total rows at the top or bottom of
the Composite BOM Table.
Default Processing Use to predefine processing wizard configurations for Composite
Configuration Breakdown, Modular Breakdown, Harness Engineering, and Harness
Checks.
The settings configured here will be the default settings displayed on
the Harness Processing Dialog Box Wizard dialog box.
Selected Process Dropdown selector to choose the process to configure.
• Composite Breakdown
• Modular Breakdown
• Harness Engineering
• Harness Checks
Process Option • Use the following selection
Selected - the Process Configuration panel is enabled. The
settings configured there will be the default settings displayed on
the Harness Processing Dialog Box Wizard.
• Use last used settings
Default selection.
Selected - the Process Configuration panel is disabled. All options
in the Harness Processing Dialog Box Wizard are populated with
the selections used in the previous user session. Users are able to
make any selection on the processing wizard.

December 2023
Project Preferences
Field Description
Process Configuration Displays all the configurable options for the selected process.
Predefine the options as required.
Right-click an option to further refine the configuration:
• Unlocked
Users can modify this option setting in the Harness Processing
Dialog Box Wizard.
• Locked
Users can not modify this option setting in the Harness Processing
Dialog Box Wizard.
• Hidden
This option will not be displayed in the Harness Processing
Dialog Box Wizard.
The option displays cleared and dimmed in this dialog box.
Diagram Specifies the default physical scale and grid space unit and value
settings of designs and diagrams.
Physical Scale Specifies the real-world distance represented by the separation of two
points on the drawing grid. Click the Units dropdown list to specify
the units to use.
Grid Space Specifies the distance between two points of the drawing grid as
represented when printed. Click the Units dropdown list to specify
the units to use.
Major Grid Interval Specifies at which interval larger grid points are displayed. For
example, a value of 5 displays a larger grid point for every 5th grid
point.
Default = 5.
Use the composite When you run composite or modular breakdown, the default behavior
border for child creates derivative or module diagrams with the border that is
diagrams created during specified in the applicable style set. Select to override that behavior,
breakdown and create derivative diagrams with the same border that is currently
used on the composite parent diagram.
You can also set this preference at the system level, to automatically
apply the setting to all new projects.
Default = cleared.

December 2023
Project Preferences
Field Description
Lock component In full scale diagrams, this functionality is unavailable if
symbol to node for Manipulation Handles are enabled.
moving Symbols and decorations can only be locked to nodes if styling is
applied to anchor the objects to each other. To anchor symbols and
decorations to parent objects, see also “Nominal Origin” in the
Capital Diagram Styling User Guide.
Select to lock component symbols to mid-bundle and bundle end
component nodes, to enable the symbols and nodes to be moved
together. You can also move decorations that are anchored to
symbols, to automatically move symbols and nodes with the
decoration.
Note: To maintain the tangents at arc and bundle ends, you
cannot manipulate bundles connected to arcs using symbols
anchored to nodes.
Clear to move symbols and nodes independently of each other. If the
option is cleared, the icon is available on the Status Bar to toggle
between symbol lock to node On or Off.
If the option is selected, the “lock” behavior is mandatory and the
icon is unavailable.
Optional.
Allow independent Select to use the Ctrl key to cancel the “lock” behavior and move the
move with CTRL + symbols and nodes independently of each other.
move symbol Clear to use the “lock” behavior at all times.
Optional.
Always create Select to create all dimensions placed on the diagram as Critical
dimensions as critical Dimensions. If you delete a Critical dimension, created while the
project preference is selected, the Critical dimension is deleted across
all the diagrams in the design.
Note: Contiguous and Internode dimensions cannot be set as
Critical dimensions.
Default = cleared.
Optional.
Apply to auto placed Only available if the “Always create dimensions as critical”
dimensions preference is selected.
Select to set all dimensions placed on the diagram, using the Auto
Place Standard Dimensions action, as Critical dimensions.

December 2023
Project Preferences
Field Description
Protect symbol property Select to lock the visibility of text properties (including comment
text symbols) on the diagram. Deactivates the Delete action on the context
menu and the keyboard when text properties are selected.
Clear to enable text properties added to symbols to be deleted.
You cannot use the style set to lock the Visibility of text properties
added to symbols.
Optional.
Retain decoration Select to preserve the current style set and its overrides when you
overrides on paste to copy and paste the harness or section of the harness.
diagram Clear to apply the style set associated with the target design when you
copy and paste the harness or section of the harness.
See also “Copy and Paste a Harness Section” in the Capital Harness
Designer User Guide.
Allow proportional Select to enable the option to proportionally distribute any length
distribution for changes arising from internode dimension edits which affect nodes
internode dimensions with hidden internode dimensions.
edits Clear to disable the option.
See also “Internode Dimensions Behavior” in the Capital Harness
Style Settings - Do not Select to prevent decorations under the Design node of the style set
refresh design level being refreshed. Use to improve the performance of actions such as
decorations on Add Connector or Add Clip, as these actions refresh any design-level
interactive edits decorations by default.
If selected, you can perform an Update Border action to manually
force an update to the design-level decoration information, or by
performing a save.
Note: Some operations, such as Delete, Edit Overbraids, Edit
Multicores, and Edit Wires, will force a refresh of the
design-level decorations to preserve data integrity.
Harness Engineering Configures the engineering parameters used during harness
processing.
Note: If you amend any of these parameters, you must refresh or
close and re-open the project, to apply the new parameters
correctly.
Add-On Per Junction Calculates and adds the specified value onto wire lengths, per
junction that the wire passes through. Default = 3.0.

December 2023
Project Preferences
Field Description
Percentage Add-On The percentage add-on value is calculated for and added to each wire
in the harness. Default = 0. The limits of the resulting add-on are
controlled by the Minimum and Maximum percentage value.
Minimum Percentage If a percentage add-on is calculated for a wire and is less than this
Value value, the minimum percentage value is used as the add-on instead of
the percentage add-on calculated. Default = 0.0.
Maximum Percentage If a percentage add-on is calculated for a wire and is greater than this
Value value, the maximum percentage value is used as the add-on instead of
the percentage add-on calculated. Default = 0.0.
Wire Length Rounding You must select one of the following methods to round wire lengths:
Method • None — Wire lengths are not rounded.
• Nearest — Rounds the calculated wire length to the nearest unit
specified in the Wire Length Rounding Value field. The length
will be rounded up or down.
• Up — Rounds the calculated wire length Up to the nearest unit
specified in the Wire Length Rounding Value field.
Wire Length Rounding Specifies the value to round the calculated wire lengths together with
Value the selected Rounding method. Default = 1.0.
Default Link Lead Specifies the length value for looped wires that have the same start
Length and end node and where the calculated length is zero. Applies to
single wires. Default = 100. Add-on and knock-off values are applied
as normal. If the link lead has a through node set, the default value is
ignored and the base length of the wire is calculated as twice the
distance to the through node.
Looped Splice Add-On Each looped splice wire can have an add-on value. Specifies an
Value amount to add when a wire is forced to enter a center strip splice from
the opposite side.
The add-on value is only used when the system has moved a wire
from one side to another as a consequence of running splice
balancing, forcing common entry direction.
The following prerequisites are required for the system to move a
wire and apply the add-on value:
• Center strip splice
• Run splice balancing

December 2023
Project Preferences
Field Description
Default Multicore Specifies a default multicore untwisted value that the system uses
Untwisted Value during the following actions:
• Wire/Multicore Length calculations from the Automate >
Calculate ribbon.
or
• Harness Engineering calculations.
You can manually override this preference on individual multicores
using the “Untwisted Change Value” on the Ends tab of the Edit
Multicore Dialog Box.
Default Splice Strip Each wire end can have a strip length applied (amount of insulation to
Length be removed to facilitate crimping / splicing of the conductor).
The system applies the required strip length to each end (or window
strip) of a wire as defined at the instance of the terminating object.
Where the splice also supports a separate definition for multi-strip,
a default value field is available for this attribute.
Default Solder Sleeve Each wire end can have a strip length applied (amount of insulation to
Strip Length be removed to facilitate crimping / splicing of the conductor).
Default Ultrasonic Weld Each wire end can have a strip length applied (amount of insulation to
Strip Length be removed to facilitate crimping / splicing of the conductor).
Default Center Strip Each wire can have a center strip or window strip length specified
Length (amount of insulation to be removed to facilitate crimping / splicing
of the conductor).
Bundle CSA Specifies a CSA Multiplication Factor to apply to the calculated
Multiplication Factor bundle diameter results, to accommodate inaccuracies in the bundle
calculation because of assembly variances.
Mandatory Spot Tape Specifies the branch insulation layer assigned to spot tape that is
Layer automatically added to the harness because it is a mandatory
component. Default = 1000.
Replacement Splice Specifies the prefix used for any wires created when running
Wire Prefix Composite Breakdown with Remove Splices With 2 Identical
Wires? and Generate Replacement Wire Names? selected.
Default = SPL.

December 2023
Project Preferences
Field Description
Tube Mandatory Specifies the positions for mandatory components when added on a
Component Positions tube:
• Start / End
• Start / Middle / End
• None
• Middle
Default = None.
Overlap/Spiral Tape Specifies how the calculated lengths for Overlap and Spiral tape are
Calculation Method derived during Harness Engineering calculations.
Select Nodes to use the node diameter (which can be greater than the
bundle diameter ending because of extra wires passing through the
node in other bundles) when calculating the length added because of
multiple turns of tape at the bundle end. Default = Nodes.
Select Bundles to use the bundle diameter before it reaches the node.
Housing Definition Specifies the nesting limit when adding mandatory items in nested
Nesting Level housing definitions. Default = 0.
Tape Usage Percentage This value is calculated as a percentage of each length of tape to
Add-On overestimate tape usage. The result is then added to the tape length.
Cannot be overridden as it is used by the Engineering Calculations
routine. Default = 0.0, Min = 0.000000, Max = 100.000000.
Default Grease Specifies how grease part numbers are applied.
Application Method Select Node to add the grease part number once as an extra
component at the node.
Select Cavity to add the part number once for each cavity of the
component.
Default Grease Specifies the part number added to the greased node, if Node is
Component selected as the Default Grease Application Method. Type = Internal
Part Number.
Default Grease Packing Specifies the part number that is also added to the node, if Node is
Component selected as the Default Grease Application Method. However, it is
only added once per node. Type = Internal Part Number.

December 2023
Project Preferences
Field Description
Tube Selection Specifies how much shorter a tube can be when selected by the Tube
Tolerance Selection process during Engineering Calculations. Used in
conjunction with shorter length tube selection. The tolerance is
always applied to the length of tube required. In all cases, the system
is asked to choose a tube of a certain length, which is usually the
combined bundle lengths that the tubes span, apart from when
cut-back is applied. In that case, it is still a specific length of tube that
is selected. The tolerance must always act on the required tube length
and not the bundle. Default = 0.0, Min = 0.000000, Max =
999999.999999
Tube Selection Order Specifies the order in which logic is applied by the Tube Selection
process when selecting tubes during Engineering Calculations. Used
if the system is unable to match a tube with the exact length required.
Click the ellipsis (...) button to open the Tube Selection Order dialog
box.
• CutShorter — The system chooses a shorter or exact length tube
which matches the Standard Selection Criteria and whose unit of
measure is Each, Per Roll / Reel. Components cannot be selected
for CutShorter.
• CutExact — The system chooses an exact match length tube
which matches the Standard Selection Criteria and whose unit of
measure is Each, Per Roll / Reel. Components cannot be selected
for CutExact.
• FromReel — The system chooses a tube component which
matches the Standard Selection Criteria and whose unit of
measure is Each, Per Roll / Reel. Components that match exact
length cannot be selected for FromReel.
At least one order must be selected and each value can occur only
once.
Distance from Specifies how placement of component insulation is determined.
Connector Calculation • Instance at Connector — Any component insulation instance is
Method placed at the node where the connector exists, when the Distance
From Connector value is 0.
• Even Distribution — Any component insulation instance is not
placed at the node where the connector exists (even if the
Distance From Connector value is 0).
• Instance at Connector — Default.
• See “Add or Edit Insulation Layer Dialog Box” for more
information about setting Distance From Connector values.

December 2023
Project Preferences
Field Description
Backshell Termination Specifies how Add On or Knock Off attribute values used during
Wire Length Harness Processing wire length calculations, are applied for wires
Calculation that terminate at a backshell.
• Use Connector Attributes — Values are applied to the
connector.
• Use Backshell Attributes — Values are applied to the backshell.
Default = Use Connector Attributes.
By default, the Add on and Knock off fields may not display on the
Capital Component Manager Component Maintenance Backshell
dialog box Base tab. You can enable the fields using the Configurable
User Interface functionality in Capital Component Manager.
Use Break-Out Tape Specifies whether Break-Out tape thickness is included in bundle
Thickness for Tape thickness calculations.
Calculation Select Yes to include. Select No to exclude.
Check Properties and Specifies whether bundles that have properties defined against them,
Values when Merging are merged when Composite Breakdown or Modular Breakdown is
Bundles run with the option Merge Bundles and Identical Insulation?
selected.
Default = No.
Select Yes to merge bundles with properties defined against them
only where all the following conditions are satisfied:
• The number of properties is the same.
• The property names are all the same.
• The property values are all the same.
All properties are retained on any merged bundle.

December 2023
Project Preferences
Field Description
Properties Excluded Only enabled if you have set the preference “Check Properties and
from Bundle Merge Values when Merging Bundles” to Yes.
Property Check Specifies names of properties to exclude from the “Check Properties
and Values when Merging Bundles” function when you run
Composite or Modular Breakdown with the option “Merge Bundles
and Identical Insulation?” selected.
You can specify multiple properties by separating them with a
semicolon for example, “Property1;Property2;Property3”.
Where you merge two bundles that have the same excluded property
name, but with differing values, you can specify a “conflict value”.
The breakdown process sets this value on the property that is assigned
to the newly merged bundle.
Specify the conflict value in the following format (where ValueXX is
the conflict value), Property1=ValueXX.
You can specify multiple property conflict values separated by a
semicolon, for example,
Property1=ValueXX1;Property2=ValueXX2.
Note: If you define the same property with two different conflict
values, the last value is assigned. For example, where
Property1=ValueXX1;Property1=ValueXX2, the ValueXX2 is used
as the conflict value for Property1.
See also “Properties Excluded from Bundle Merge Property Check
Examples” in the Capital Harness Designer User Guide for examples
of how this preference works.
Properties that Block Only enabled if you have set the preference “Check Properties and
Bundle Merge Values when Merging Bundles” to Yes.
Specifies names of properties that, if present on potential bundles for
merging, will prevent those bundles from being merged when you run
Composite or Modular Breakdown with the option “Merge Bundles
and Identical Insulation?” selected.
Specify the properties in the following format,
Property1;Property2;Property3.
See also “Properties That Block Bundle Merge Examples” in the
Capital Harness Designer User Guide for examples of how this
preference works.

December 2023
Project Preferences
Field Description
Check Properties and Specifies whether insulation runs and layers, that have properties
Values on Insulation defined against them, are considered for merging when Composite
Runs and Layers when Breakdown or Modular Breakdown is run with the option Merge
Merging Insulation Bundles and Identical Insulation? selected.
Runs Default = Yes.
Select Yes to merge insulation runs and layers with properties defined
against them, only where all the following conditions are satisfied for
all runs and layers that are being considered:
• The number of properties is the same.
• The property names are all the same.
• The property values are all the same.
All properties are retained on any merged insulation runs and layers.
Properties Excluded Only enabled if you have set the preference “Check Properties and
from Insulation Run Values on Insulation Runs and Layers when Merging Insulation
Merge Property Check Runs” to Yes.
Specifies names of properties to exclude from the “Check Properties
and Values on Insulation Runs and Layers when Merging Insulation
Runs” function when you run Composite or Modular Breakdown
with the option “Merge Bundles and Identical Insulation?” selected.
You can specify multiple properties by separating them with a
semicolon for example, “Property1;Property2;Property3”.
Where you merge two insulation runs / layers that have the same
excluded property name, but with differing values, you can specify a
“conflict value”. The breakdown process sets this value on the
property that is assigned to the newly merged insulation run / layer.
Specify the conflict value in the following format (where ValueXX is
the conflict value), Property1=ValueXX.
You can specify multiple property conflict values separated by a
semicolon, for example,
Property1=ValueXX1;Property2=ValueXX2.
Note: If you define the same property with two different conflict
values, the last value is assigned. For example, where
Property1=ValueXX1;Property1=ValueXX2, the ValueXX2 is used
as the conflict value for Property1.
See also “Properties Excluded from Bundle Merge Property Check

December 2023
Project Preferences
Field Description
Properties that Block Only enabled if you have set the preference “Check Properties and
Insulation Run Merge Values on Insulation Runs and Layers when Merging Insulation
Runs” to Yes.
Specifies names of properties that, if present on potential insulation
runs / layers for merging, will prevent the insulation runs from being
merged when you run Composite or Modular Breakdown with the
option “Merge Bundles and Identical Insulation?” selected.
Specify the properties in the following format,
Property1;Property2;Property3.
See also “Properties That Block Bundle Merge Examples” in the
Capital Harness Designer User Guide for examples of how this
preference works.
Merge Bundles and Specifies how bundles and insulation runs are merged when you run
Insulation Runs if Composite or Modular Breakdown with the option “Merge Bundles
Dimension Exists at and Identical Insulation?” selected, where a dimension start or end
Optional Node point exists at a node that could potentially be removed.
Select Yes to merge the bundles or insulation runs / layers and delete
such nodes.
Select No to preserve such nodes and to not merge the bundles or
insulation runs / laters.
Default = Yes.
See also “Merge Bundles if Dimension Exists at Optional Node
Merge insulation run Used by the “Merge Bundles and Identical Insulations” Composite
within specified Breakdown action.
distance from junction Specifies a distance from the end of an insulation run to the
corresponding junction node, within which, insulation runs are
considered for merging.
Default = 0.0
Delete spot tapes within Used by the “Merge Bundles and Identical Insulations” Composite
a certain distance from Breakdown action.
junctions of merged Specifies a distance from the junction node, within which, any placed
insulation spot tapes are automatically deleted when insulation runs are merged.
Default = 0.0

December 2023
Project Preferences
Field Description
Bundle Size Calculation Specifies the method used to calculate bundle diameters during
Method Harness Engineering:
• Worst Case - Basic (Default)
• Worst Case - Enhanced
• Navy Table
• Summed CSA x Factor
See “Bundle Size Calculations” for a full description of the methods
and calculations for bundles with overbraids.
Parent/Composite Specifies whether diagram and design-level properties on a parent
properties values harness (composite harness or modular parent) are inherited by child
overwrite modules/ harnesses (derivatives or modules), if a property exists on both parent
derivatives upon and child with a different value.
breakdown • Any property present on a parent is always inherited by the
children.
• If the property only exists on a child, it is preserved regardless of
the parent not having this property.
Select Yes to inherit the parent properties and overwrite the
properties on the child design.
Select No to preserve the properties on the child design.
Default = Yes.
See also “Extra Information” on page 158.
Use Multicore Outer Specifies an alternate CSA selection method, used by the solder
dia. for Solder Sleeve sleeve part selection process, where the shield of a multicore
Selection terminates in a solder sleeve.
Select Yes to use the CSA of the multicore to select a matching solder
sleeve part instead of using the CSA of the sum of the connected
multicore wires.
Select No to use the default CSA selection method.
Default = No.
See also “Part Selection” in the Capital Harness Designer User
Guide.

December 2023
Project Preferences
Field Description
Allow Breakdown Specifies whether to run Composite Breakdown or Modular
without all part numbers Breakdown if there are any bundle or node insulations (spot tape), or
selected multi-location node components on the design that do not have
library part numbers assigned.
Select Yes to bypass this design consistency error and enable
composite breakdown or modular breakdown to run on designs where
not all components have library part numbers assigned.
Select No to not run composite breakdown or modular breakdown.
A design consistency error message is displayed giving details of the
affected components.
Default = No.
Auto component Specifies a property name that is added to all components that are
creation property name created by the Auto Create Components constraints. The property
value is set to True.
Tape quantity Specifies whether to display a detailed report of the nodes and values
calculation verbose log used to calculate the insulation quantities for all overlap and spiral
tape on the harness design. Use with the Calculate Insulation Totals
action.
Select Yes to display the report in the Design Log and on the
Insulation Calculations tab in the Output Window.
Default = No.
Optional.
Process insulation for Specifies whether insulation is processed on splices when the
splice with insulation insulation type is None on the Edit Splice or Add Splice Dialog Box.
type="None" Select Yes to process all insulation on splices when the system selects
parts.
Select No to ignore insulation on splices when the system selects
parts.
Default = Yes.
Note: Any manually applied insulation is retained on the
diagram.

December 2023
Project Preferences
Field Description
Consider non-wired Possible values Yes / No. Default is No.
objects during Used by harness processing during wire-driven Composite
breakdown Breakdown.
Controls the availability on derivative designs of components that are
not directly connected (non-wired) to the harness.
Select No to use the default wire-driven composite breakdown, and
populate derivative designs with wires and connected components
only.
Select Yes to consider the option expressions on all components in a
composite design, and populate derivative designs with non-wired
components, in addition to wires and connected components.
Optional.
Delete single wire Specifies whether splices that contain only a single center-stripped
center-strip splice wire are deleted during composite breakdown.
during breakdown Yes - the Composite Breakdown process automatically removes
splices that only have a single center-stripped wire.
See Composite Breakdown for full information on using this
preference in conjunction with the “Retain center-strip splice with
property name” preference.
Default is No.
Retain center-strip Specify the property name you have added to single wire center-strip
splice with property splices that you do not want to be deleted by composite breakdown.
name Specify multiple properties with (;) as a delimiter.
See Composite Breakdown for full information on using this
preference in conjunction with the “Delete single wire center-strip
splice during breakdown” preference.
In-house twisted The method the system uses to calculate in-house twisted multicore
multicore length lengths.
calculation method • Longest wire length
This is the default setting.
Length of multicore = the length of its longest wire.
• Maximum length between wire ends
Length of multicore = longest wire at End A + common multicore
length + longest wire at End B.
See Multicore End Identification for further information.

December 2023
Project Preferences
Field Description
Harness Applies to Capital Harness Designer and Capital Harness Designer
Synchronization Modular.
Consider Capital Select to preserve any existing modular connector parent child
Harness Designer as the hierarchy defined in Capital Harness Designer during harness
primary author for synchronization.
modular connectors
Allow synchronization Select to run Harness Synchronization in Capital Harness Designer
without build lists without using build lists or change management.
Capital Systems Capital Systems Integrator options are considered master when
Integrator Mastered Synchronizing from a Capital Systems Integrator Design. Select to
Options remove all existing options from the composite and any associated
derivative design. Options on the composite are then set by the
harness from which it is being synchronized.
Options for existing derivatives are set from their associated levels
options, if they have been previously mapped. Option information for
derivatives and levels that are not mapped will not be synchronized.
See also “Mapping Harness Levels to Derivative Designs”.
Allow splice Select to enable the Synchronization process from Capital Systems
repositioning during Integrator / Wiring Integrator, to move splices on the target design
Capital Systems when their positions have changed on the source design. Default =
Integrator/Wiring cleared.
Integrator Note: This preference is used in conjunction with the Change
synchronization Policy “Splice (Bridge In / Synchronization) Update” setting,
which must be selected, to enable splice position changes. See also
“Synchronization Rules”.
Design Access Control Applies to Capital Harness Designer and Capital Harness Designer
Modular.
Inherit domain of child Select for all derivative, functional module, and production module
design from composite designs to inherit the domain set against their parent design
design automatically. Access to them is controlled by any configured
Domain Access settings.
Clear for the domain settings of a parent design to not affect the
access and editing of its derivative, functional module, and
production module designs. Default = cleared.
See also “Child Design Domain Inheritance” in the Capital Harness
Design Content Control Used to configure various editing restrictions on harness designs.
Panel

December 2023
Project Preferences
Field Description
None Select to not apply any specified restrictions to harness designs in the
open project.
Default.
Only allow Capital Select to only permit wires and multicores authored in Capital
Harness Designer- Harness Designer to be edited or deleted.
authored wires & A message is displayed on opening the Edit Wires and Edit
multicores to be edited Multicores dialog boxes to warn that this editing restriction is set.
and deleted
See Wire and Multicore Authoring Controls in the Capital Harness
Use change policy for See Design Content Control Overview in the Capital Harness
objects authored in Designer User Guide for details on how to use this preference.
Selected - the editing and deletion of harness objects, that were
originally authored in the listed tools, is controlled by the selected
Change Policies.
The system uses the Origin Attribute of each object to determine its
authoring tool.
The dropdown lists display all the change policies configured against
the open project.
If there are no change policies defined for a project, system-level
change policies are listed.
The dropdown lists are blank if there are no project or system-level
change polices defined.
• Capital Harness Designer
• Capital Logic Designer
• Capital Wiring Integrator
• Capital Systems Integrator
• External System
Entries in red denote an invalid selection:
• A change policy that has been deleted or renamed since being
selected.
• A system-level policy, selected before any project-level policies
existed, but project-level policies have since been created.
• The OK button on the dialog box is dimmed until you make a
valid selection.
• The Design Access Control tree view name displays in red.
• You can not make modifications to any harness design object
authored in this tool.

December 2023
Project Preferences
Field Description
Module Codes, Applies to Capital Harness Designer Modular only.
Options, Levels Displays project preferences to override the exclusive module code
checks in certain circumstances, and also to pre-define which “tag
fields”, such as option expressions, harness levels, and module code
fields are available on the Edit Object dialog boxes of Capital
Harness Designer Modular designs and diagrams, for any given
project.
Allow Exclusive In a typical flow, a module child design represents the data associated
Module Codes On with a single buildable module design and as such the system by
Module Child Designs default stops you making mutually exclusive codes applicable to a
module design.
However, you might need to allow mutually exclusive content to exist
in the same module design, for example, when the design is used to
generate a diagram for a formboard that supports mutually exclusive
content. Select to allow mutually exclusive codes to be applied to
module child designs. Default = cleared.
A tooltip indicates that there are exclusive module codes on the
design and a design rule check reports the fact; however, with this
preference selected, you are still able to proceed and generate the
design.

December 2023
Project Preferences
Field Description
Enable and Display The default for all options is selected.
Select or clear the check boxes to display or suppress the following
options:
• Option Expressions
Use to add object expressions to objects. Additionally, enables the
New Derivative menu for harness designs in the Project window,
and the Applicable Options menu in the New/Edit Harness dialog
box. See also the Capital Harness Designer Modular help.
• Harness Levels
Specifies whether harness levels are synchronized from a Capital
Systems Integrator design with derivative modular harness
designs created in Capital Harness Designer Modular.
Additionally, enables the automatic creation of child harness
designs based on the level configurations synchronized into the
parent harness.
• Functional Module Codes
Use to add Functional Module codes to objects. Additionally,
enables the Functional Module menu for harness designs in the
Project window, and the Applicable Functional Module Codes
menu in the New/Edit Harness dialog box. See also the Capital
Harness Designer Modular help.
• Production Module Codes
Use to add Production Module codes to objects. Additionally,
enables the Production Module menu for harness designs in the
Project window, and the Applicable Production Module Codes
menu in the New/Edit Harness dialog box. See also the Capital
Harness Designer Modular help.
Composite Behavior - Use to configure the automatic creation of child design diagrams
Populate child designs during the copy or revision of a parent design.
by default during Select to select the Populate column automatically when you select
Revise/Copy of a the Revise or Copy check box on the Select Child Designs Dialog
composite (applies to Box.
derivatives and
modules) Clear the Populate check box to override this behavior manually.
Default = selected.

December 2023
Project Preferences
Field Description
Technical Module Applies to Capital Harness Designer Modular only.
Code Assignation Displays project preferences to define how combinations are used for
technical module code assignation, and if codes are reused or created.
Assignation Order can also be specified.
Technical module codes can be automatically generated for each of
the following objects types:
• Breakout Tape
• Clip
• Connector
• Device
• Grommet
• Insulation Run
• Multi-Location Component
• Multi Crimp
• Other
• Overbraid
• Splice
• Spot Tape
Assignation Order Applies to Capital Harness Designer Modular only.
Displays project preferences to determine the assignation order for
splices and multi-crimps, where there are connections from a splice
into a multi-crimp that could be assigned to either the splice technical
module code, or the multi-crimp technical module code. You can
specify the order in which assignation occurs, based on
manufacturing preferences or equipment availability.
Assign Splices before Technical Module Code assignation analyzes and assigns codes to
Multi-crimps splices before multi-crimps.
Assign Multi-crimps Technical Module Code assignation analyzes and assigns codes to
before Splices multi-crimps before splices.
Only use pre-defined Technical Module Code assignation only uses the user pre-defined
combinations combinations in the module code manager.
Try the pre-defined Technical Module Code assignation first tries to use the user pre-
combinations, otherwise defined combinations in the module code manager. If none match, a
generate a combination generated combination is created. You can specify a combination
limit.

December 2023
Project Preferences
Field Description
Max number of If the Create a Combination option is selected, this setting stipulates
combinations before the maximum number of combinations that are created for the current
failure object being evaluated. This does not limit the total number of
combinations generated for the design.
Reuse existing code If the code is assigned to the matching combination row, that is the
code used.
Create new code If the code is assigned to the matching combination row, a new code
for the object is also created.
Production Variation Applies to Capital Harness Designer Modular only.
node Select to configure technical variation combinations.
Max Number of Specifies a maximum number of technical variations to be created per
combinations before combination when running Variant Module Generation. Default = 12.
failure
Extra Information
Using the “Parent/Composite properties values overwrite modules/derivatives upon
breakdown” preference
Where the preference is set to Yes, and you are using OTI properties, and you have edited the
default OTI values on the parent, the values are applied depending on how you create a new
derivative in the New Derivative/Module dialog box:
• If you select the Properties tab before clicking OK for the creation of the child design,
the values are immediately inherited from the parent and displayed.
• If you click OK, without selecting the Properties tab, the default OTI properties values
are allocated to the child design.
In both cases, the child design properties are overwritten with the current parent design values
upon breakdown.
If the preference is set to No, the default design property values as configured in the OTI will be
assigned to the child designs.
If no default values are defined in the OTI, the properties will be created without a value.
Project Preferences for Capital Systems Integrator

Designs
Systems Integrator. They are not applicable for any other Capital tool.

December 2023
Project Preferences
Table 2-5. Project Preferences for Capital Systems Integrator Designs

Field Description
Bundle calculation Displayed under Capital Systems Integrator in the Project Preferences
node browser.
Displays project preferences for calculating a bundle diameter for a
bundle width report.

December 2023
Project Preferences
Table 2-5. Project Preferences for Capital Systems Integrator Designs (cont.)
Field Description
Wire Gap Coefficient Displayed in the Project Preferences pane when you select Capital
Systems Integrator > Bundle Calculation in the Project Preferences
browser.
Specifies the coefficient that is used to represent the air gap between
adjacent wires when calculating a bundle diameter. The value must be
a float (decimal number) of 1 or higher. By default, this is 1.154.
A value of 1 indicates that there is no air gap.
If a multicore has an OutsideDiameter attribute, it is treated as one
wire by these calculations. Otherwise, its constituent wires are
processed.
Bundle diameter (DBundle) is calculated in the following ways
(given a number of wires of diameter DWire):
• If the bundle contains one wire:
DBundle = DWire
• If the bundle contains two wires:
DBundle =
• If the bundle contains three or more wires:
DBundle =
where is calculated from DWire
The cross-sectional area of a wire ( ) is calculated in a

variety of ways (depending on what data exists):
• If the OutsideDiameter attribute exists on a wire, this is used as-is.
This also applies if a multicore has an OutsideDiameter attribute.
In this case, the wires within the multicore are ignored.
• If a wire has no OutsideDiameter attribute but has both a
WireMaterial attribute and a WireCSA attribute defined, the
WireCSA attribute is used to calculate the copper diameter and an
insulation thickness determined from Capital Component
Manager (from the Wire Insulation Thickness Dialog) is added to
calculate DWire.
• If the OutsideDiameter attribute does not exist on a wire, the
WireCSA attribute is used to calculate the copper diameter and
the value specified for the “Default Insulation Thickness” project
preference is added to calculate DWire. If a multicore does not
have an OutsideDiameter attribute, its constituent wires are
processed individually in this way.
In all these cases, this value of DWire is used to calculate the overall
CSA of copper plus insulation.

December 2023
Project Preferences
Field Description
Default Insulation Displayed in the Project Preferences pane when you select Capital
Thickness Systems Integrator > Bundle Calculation in the Project Preferences
browser.
Specifies the insulation thickness that is used by default when
calculating the bundle diameter. The value must be a float (decimal
number). By default, this is 0.0.
Running Mode Displayed in the Project Preferences pane when you select Capital
Systems Integrator > Checks in the Project Preferences browser.
Located at the top of the dialog box, this enables you to select a
running mode for design rule checks from a dropdown list.
Select a running mode and a Design Abstraction to specify a scenario
for running design rule checks (that is, running checks in a particular
mode on a design with a particular abstraction). You can then use the
Design Rule Checks browser to select the design rule checks that are
run automatically and their severity for this particular scenario.
For a list of DRC running modes in Capital Systems Integrator (with
descriptions), see “Running Modes for DRCs in Capital Systems
Integrator” on page 251.
Design Abstraction Displayed in the Project Preferences pane when you select Capital
Systems Integrator > Checks in the Project Preferences browser.
Located at the top of the dialog box, enables you to select a design
abstraction from a dropdown list.
Select a Running Mode and a design abstraction to specify a scenario
The list of design abstractions depends on those available in the
project. You can select an empty row from the dropdown list that
represents designs without a design abstraction. Designs which
reference an abstraction which no longer exists also default to the
empty abstraction rule check configuration.

December 2023
Project Preferences
Field Description
Design Rule Checks Lists the available design rule checks, grouped into categories, in a
browser tree to set preferences for each check. See “Design Rule Check
Displayed in the Project Descriptions” on page 261 for a detailed explanation of each
Preferences pane when available Design Rule Check.
you select Capital The preferences for each check apply only to the selected
Systems Integrator > combination of Running Mode and Design Abstraction. When you
Checks in the Project change the preferences for a particular combination, ensure that you
Preferences browser. click Apply at the bottom of the dialog box before selecting a new
running mode or design abstraction.
Select a design rule check in the tree if you want it to run
automatically. Clear it to not run automatically. If you select or clear
a design rule check category (for example, Connectivity), all of the
checks under that category are selected or cleared.
Right-click the symbol next to a design rule check to specify whether
a failure for that check generates an error, a warning or a notification
(information).
Note: A single custom DRC can have multiple violations defined
in it. While writing a custom DRC, you can define different
severities for each violation using the report() method as well as a
default severity. In case no severity is defined for a violation (that is,
it is assigned a NULL severity), it uses the default severity. The
default severity of a custom DRC is visible in the project preferences,
and any changes made to it will persist even after opening, closing,
exporting or importing the project. Changing the severity of the
preference does not change the original custom code. When a custom
DRC is run, the severity for each violation is decided in the following
order:
• 1. System uses severity for a particular violation as defined in the
custom DRC code using the report() method in the
IXDRCViolationReporter API (violation reporter class).
• 2. Only if report() method passes NULL for that violation, the
system uses the default severity of the custom DRC as updated
explicitly in the project preferences.
• 3. In the case that the default severity has not been updated in the
preferences, the system uses the default severity from the custom
DRC code.
In addition, right-click the symbol and select or clear Show to specify
whether the check is (selected) or is not (cleared) listed in the Design
Rule Checks dialog box (used for manually running checks) in the
design application. If Show is cleared, the check is dimmed in the
tree, although you can still right-click it to edit its preferences. In
addition to not being listed for selection, a check with Show cleared
will not run.

December 2023
Project Preferences
Field Description
Comment node Displayed under Capital Systems Integrator in the Project
Preferences browser.
Expands to display further nodes of project preferences for comment
graphics created by drawing tools.
Graphic node Displayed under Capital Systems Integrator > Comment in the
Project Preferences browser.
Displays project preferences for graphics created by drawing tools.
Style Displayed in the Project Preferences pane when you select Capital
Systems Integrator > Comment > Graphic in the Project Preferences
browser.
Specifies the line style used for comment graphics created by drawing
tools in a diagram.
Thickness Displayed in the Project Preferences pane when you select Capital
Systems Integrator > Comment > Graphic in the Project Preferences
browser.
Specifies the line thickness used for comment graphics created by
drawing tools in a diagram.
Select the type of thickness from the second dropdown list:
• Logical
These thicknesses do not have a physical unit of measurement.
They provide a logical progression of thickness with a default of
1. A line with thickness 2 is displayed twice as thick as a line with
thickness 1, and so on. When you zoom in or out of a diagram, the
line thickness does not appear any different.
You select the thickness from the first dropdown list.
• Physical (unit of measurement)
These are physical units of measurement. The line thickness is
displayed in relation to the grid size of a diagram. When you
zoom in or out of a diagram, the line grows or shrinks to stay in
scale with the grid.
When you select a unit, the first dropdown list changes to a free
text field to specify the thickness. The value can be any floating-
point number up to three decimal places.
See “Physical Line Thickness” in the Capital Design Tools -
Common Functions User Guide for a definition and links to
related task flows.
Text node Displayed under Capital Systems Integrator > Comment in the
Project Preferences browser.
Displays project preferences for text created by drawing tools.

December 2023
Project Preferences
Field Description
Name Displayed in the Project Preferences pane when you select Capital
Systems Integrator > Comment > Text in the Project Preferences
browser.
Specifies the type of font used for text in a text frame and whether it
is bold and/or italic. Select the values from the dropdown lists.
Height Displayed in the Project Preferences pane when you select Capital
browser.
Specifies the height of text in a text frame and the units of
measurement for this height. Select the values from the dropdown
lists.
Justification Displayed in the Project Preferences pane when you select Capital
browser.
Specifies where text is placed in a text frame. The Preview window
shows you how the justification will look.
Connector node Displayed under Capital Systems Integrator in the Project
Displays project preferences for connector graphics.
Connector Width Displayed in the Project Preferences pane when you select Capital
Systems Integrator > Connector in the Project Preferences browser.
Specifies the width of a connector graphic in pin grids. Select the
value from the dropdown list.
Connector View Displayed in the Project Preferences pane when you select Capital
Libraries Systems Integrator > Connector in the Project Preferences browser.
When editing a signal map in Capital Systems Integrator, you can
display a Connector Faceview Panel for a connector.
If the connector has a library part with associated faceview symbols
in Capital Component Manager, the panel offers these symbols for
selection.
Note: A faceview symbol is created as a comment symbol with
pins in Capital Symbol Designer.
If the library part does not have associated faceview symbols in
Capital Component Manager, the panel searches for symbols (with
the same name as the connector part number) in the symbol libraries
specified in this preference.
General node Displayed under Capital Systems Integrator in the Project

December 2023
Project Preferences
Field Description
Automatically delete Displayed under Capital Systems Integrator > General in the Project
obsolete wiring after Preferences browser.
unplace or uncombine If this is selected, the system deletes any obsolete wires after you
unplace or uncombine a device. The number of deleted wires will be
reported in the Place tab in the Output Window at the bottom of the
Capital Systems Integrator application.
You may choose to not select this preference if you want to keep
these obsolete wires in order to move them to other connections or
routes in the design.
By default, this is selected in a new project. It is not selected by
default in an existing project that has been migrated from a previous
release where this preference did not exist.
Note: For an example of uncombining devices, and the impact of
the project preference, see “Example of Uncombining Devices” in
the Capital Systems Integrator User Guide.
Name node Displayed under Capital Systems Integrator in the Project
Expands to display nodes of project preferences for object name text
in Capital Systems Integrator diagrams.
Text node Displayed under Capital Systems Integrator > Name in the Project
Displays project preferences for object name text in Capital Systems
Integrator diagrams.
Systems Integrator > Name > Text in the Project Preferences
browser.
Specifies the type of font used for the object name text and whether it
browser.
Specifies the height of the object name text and the units of
lists.
browser.
Specifies the justification of the text. The Preview window shows you
how the justification will look.

December 2023
Project Preferences
Field Description
Diagram node Displayed under Capital Systems Integrator in the Project
Displays project preferences for the grid spacing on a plane diagram
in Capital Systems Integrator.
Grid Spacing Displayed in the Project Preferences pane when you select Capital
Systems Integrator > Diagram in the Project Preferences browser.
Defines the size represented by the visible grid on a diagram. Specify
a decimal number and select the unit of measurement from the
dropdown list. This setting will effect the size of objects (such as
devices and connectors) when a diagram is printed. The position of
electrical objects are constrained by this grid (purely graphical
objects are constrained by the drawing grid).
You can specify how this grid is displayed using the Set Grid
Defaults dialog box in Capital Systems Integrator.
You can use the Edit Physical Scale dialog box in Capital Systems
Integrator to specify the physical scale of objects in a design.
Drawing Grid Displayed in the Project Preferences pane when you select Capital
In addition to the visible grid on a diagram, there is the drawing grid
that is invisible. When you place a drawing object that does not have
any pins nor connects to any pins on the diagram, the object will snap
to the drawing grid. You can specify how many points of the drawing
grid are between the points of the visible grid using a percentage of
the print scale. For example, if you specify 50, there will be one
invisible drawing point halfway between each point on the visible
grid.
Major Grid Interval Displayed in the Project Preferences pane when you select Capital
Specifies at which interval larger grid points are displayed. For
example, a value of 5 would display a larger grid point for every 5th
grid point.
Default = 5.
Maximum Drawn Points Displayed in the Project Preferences pane when you select Capital
Specifies the maximum number of grid points that can be displayed in
any one row or column when you zoom out of the diagram. When the
specified number of grid points is exceeded, the grid is no longer
displayed.

December 2023
Project Preferences
Field Description
Property node Displayed under Capital Systems Integrator in the Project
Expands to display nodes of project preferences for object property
text in Capital Systems Integrator diagrams.
Text node Displayed under Capital Systems Integrator > Property in the Project
Displays project preferences for object property text in Capital
Systems Integrator diagrams.
Systems Integrator > Property > Text in the Project Preferences
browser.
Specifies the type of font used for the object property text and
whether it is bold and/or italic. Select the values from the dropdown
lists.
browser.
Specifies the height of the object property text and the units of
lists.
browser.
Specifies the justification of the object property text. The Preview
window shows you how the justification will look.
Synthesis node Displayed under Capital Systems Integrator in the Project
Displays project preferences related to wiring synthesis.

December 2023
Project Preferences
Field Description
Mandatory options must Displayed in the Project Preferences pane when you select Capital
be explicitly specified as Systems Integrator > Synthesis in the Project Preferences browser.
supported in harness During wiring synthesis, the system may promote an option in a
levels mandatory option folder to a harness. This preference controls
whether the system automatically promotes other impacted options in
that folder to the harness.
If cleared (the default setting for a project created before release
2018.1), the system does not promote other options from the
mandatory option folder.
If selected (the default for a new project), the system will promote
other options from the mandatory option folder if it determines they
impact the harness wiring.
See Promotion of Options in Mandatory Option Folders for detailed
information about how the system behaves in both cases.
Simplify option Displayed in the Project Preferences pane when you select Capital
expressions by vehicle Systems Integrator > Synthesis in the Project Preferences browser.
model If selected, the system simplifies option expressions generated on
wires that were created during wiring synthesis. It simplifies them by
removing any terms that are not supported by any vehicle model. This
removal of unnecessary terms can shorten the generated option
expressions and makes them easier to understand. For example, if the
vehicle models are defined such that AWD is only available with the
2.0D engine, an option expression such as (AWD && 1.4 || AWD
&& 1.6 || AWD && 2.0D) would be simplified to (AWD && 2.0D).
Selected by default for newly created projects. It is cleared by default
for projects created in Capital v2012.1 or earlier.
Sort harness levels Displayed in the Project Preferences pane when you select Capital
alphanumerically Systems Integrator > Synthesis in the Project Preferences browser.
The system stores harness levels so that abstract harness levels are
always at the top of the list. When you import harness levels, this
preference controls the sort order of the imported physical harness
levels that follow those abstract levels.
If selected (the default), the systems sorts the physical harness levels
alphanumerically by name.
If cleared, the system stores the most complex physical harness levels
at the top of the list. This produces better wiring synthesis results. The
most complex harness level is the one that supports the most options
(and variants).

December 2023
Project Preferences
Field Description
Visualize Wiring node Displayed under Capital Systems Integrator in the Project
Displays project preferences related to visualize wiring functionality.
For more information about that functionality, see “Generating a
Wiring View of a Synthesized Signal or Multicore” in the Capital
Systems Integrator User Guide.
Use Logic Diagram Displayed in the Project Preferences pane when you select Capital
Grid Spacing Systems Integrator > Visualize Wiring in the Project Preferences
browser.
By default, this is cleared and visualized wiring diagrams use a
calculated grid spacing which may vary.
When this is selected, visualized wiring diagrams use the same grid
spacing as specified in the project preferences for Capital Logic
Designer diagrams.
Project Preferences for Capital Logic Designer Designs

Certain project preferences are available specifically for designs and diagrams in Capital Logic
Designer. They are not applicable for any other Capital tool.
Table 2-6. Project Preferences for Capital Logic Designer Designs

Field Description
Capital Logic Designer Displayed in the Project Preferences browser.
node Expands to display nodes of project preferences for Capital Logic
Designer designs.
Enable multi-user Displayed in the Project Preferences browser at the Capital Logic
editing of designs Designer base node.
Select this preference if you want to use the multi-user access to
Capital Logic Designer designs functionality in this project, to
facilitate more than one user working concurrently in a single design.
Default is cleared meaning the project is using single-user mode.
Note: To enable multi-user access, in addition to selecting this
project preference, the logicdesign_multiuser_access setting in
the clientprops.xml configuration file must be set to “yes”. See
“Multi-user Access to Capital Logic Designer Designs” in the Capital

December 2023
Project Preferences
Table 2-6. Project Preferences for Capital Logic Designer Designs (cont.)
Field Description
Applicable Options Displayed in the Project Preferences browser under the Capital Logic
node Designer node.
Displays project preferences for Applicable Options on Capital Logic
Designer designs.
Mandate Applicable Displayed in the Project Preferences pane when you select Capital
Options Logic Designer > Applicable Options in the Project Preferences
browser.
Specifies:
• whether you can edit object expressions on an object in a Capital
Logic Designer design only when that design has applicable
options specified for it (selected)
or
Logic Designer design regardless of whether any applicable
options are specified for the design (cleared).
Assembly node Displayed in the Project Preferences browser under the Capital Logic
Designer node.
Click Assembly and select the check box(es) in the Project
Preferences pane to include the following components, by default,
inside their owner’s assembly:
• Connector Backshells
• Modular Connector Children
Attribute node Displayed under Capital Logic Designer in the Project Preferences
browser.
Expands to display nodes of project preferences for object attribute
text in Capital Logic Designer diagrams.
Text node Displayed under Capital Logic Designer > Attribute in the Project
Displays project preferences for object attribute text in Capital Logic
Designer diagrams.
Logic Designer > Attribute > Text in the Project Preferences browser.
Specifies the type of font used for the object attribute text and
lists.

December 2023
Project Preferences
Field Description
Specifies the height of the object attribute text and the units of
lists.
Specifies the justification of the object attribute text. The Preview
Auto-route node Displayed under Capital Logic Designer in the Project Preferences
browser.
Expands to display the project preferences for user defined auto-
routing in Capital Logic Designer diagrams, enabling the routing of
full signals, even across splices and single pin-pair inline connector
junctions.
Diagram Flow Displayed in the Project Preferences pane when you select Capital
Logic Designer > Auto-route in the Project Preferences browser.
Specifies the layout direction of the diagram flow. You can accept the
current default flow, or either select Horizontal or Vertical from the
dropdown list.
Wire/Net Spacing Displayed in the Project Preferences pane when you select Capital
Logic Designer > Auto-route in the Project Preferences browser.
Defines the spacing size between wires/nets represented by the
visible grid on a diagram when the auto-routing action is applied.
Specify a positive integer value.
Minimum Wire/Net Displayed in the Project Preferences pane when you select Capital
Length Logic Designer > Auto-route in the Project Preferences browser.
Specifies the minimum wires/net length represented by the visible
grid on a diagram when the auto-routing action is applied. Specify a
positive integer value.
Batch Share Node Displayed under Capital Logic Designer in the Project Preferences
browser.
Expands to display nodes of project preferences for batch sharing
logical objects according to attributes, properties or connectivity.

December 2023
Project Preferences
Field Description
Pin reservation status Select the pin reservation status you want to apply to pins of shared
panel objects newly created using the batch share action action.
• Automatic (Default)
• Reserved
• Unrestricted
See also the Pin Reservation Status topic in the Capital Project
Manager User Guide.
Device node Displayed under Capital Logic Designer > Batch Share in the Project
Ground node Preferences browser.
Highway node The Project Preferences pane displays the batch share criteria for the
selected object type.
Inline node
Jack node
Multicore node
Net node
Overbraid node
Plug node
Ring Terminal node
Splice node
Wire node

December 2023
Project Preferences
Field Description
Batch Share Criteria Displayed in the Project Preferences pane when you select Capital
Logic Designer > Batch Share in the Project Preferences browser.
Specifies the criteria used to match objects when batch sharing
logical objects.
• Match using connectivity
Only displayed when the Wire node is selected in the Project
Specifies that connectivity should be used to match wires.
• Attributes
Lists the matching criteria attributes of the object type selected in
the Project Preferences browser. Select one or more attributes and
click Add to add them to the “Match using” list.
Unavailable when the Wire node is selected in the Project
Preferences browser and “Match using connectivity” is selected.
• Property Name
The dropdown list shows the properties defined in the Object
Type Information in Capital Project Manager for the object type
selected in the Project Preferences browser. Either select a
property from the list, or type the property name in the field, then
click Add to add it to the “Match using” list.
• Match using
Lists the attributes and properties that will be used to match
objects of the type selected in the Project Preferences browser
when batch sharing objects. To remove criteria from the list,
select them and click Remove.

December 2023
Project Preferences
Field Description
Batch Share Criteria Note: When specifying matching criteria note the following:
(continued) • You cannot add an attribute or property to the “Match using” list
more than once.
• You must specify at least one matching criteria for each object
type. If you remove all the criteria from the “Match using” list for
an object type, the type's node in the Project Preferences browser
will display in red, the border of the “Match using” list for that
object type will be red, and the OK and Apply buttons will be
unavailable.
• The order in which the match criteria are specified in the “Match
using” list is not important. When matching performed during
batch sharing, the criteria are combined using logical AND
operators to create the overall matching criterion. That is, an
object must match all the criteria specified in order to be
considered a match.
Checks node See “Project Preferences - Checks Node” on page 220.
Uniqueness Displayed in the Project Preferences pane when you select Capital
Logic Designer > Checks > Uniqueness in the Project Preferences
browser.
Lists selection criteria that work in conjunction with each other and
also design rule name checks enabling you to inspect, and report on,
where there are duplicate names across object types within a single
design or all designs in a build list, including variants in option
expressions and/or harness attributes.
The Across Object Types and Option Expressions preferences are
selected by default. Selecting the preferences individually, or in
combination enables you to scale the depth of your checks.
For example, selecting only the Across Object Types preference
means the system will report instances where, a Splice and a
Connector may have the same name.
However, if both the Across Object types and the Option expression
preferences are checked, and the same Splice and Connector have
differing option expressions of RHD and LHD, they will not be
highlighted in the report.
Select the Location and Function preferences to comply with IEC-
81346 naming standards. Under these standards the uniqueness of a
component is derived from its name, location and function.
Tick the check box to include the required criteria when running
name checks.

December 2023
Project Preferences
Field Description
Uniqueness (cont’d) The available criteria for checking if names are unique are:
• Across Object Type (for example, device, connector.)
Object types checked include:
• Devices
• Wires
• Nets
• Overbraids
• Multicores
• Ring Terminals
• Splice
• Plugs / Inline Plugs
• Receptacles / Inline Receptacles
• Shield Terminations
• Location
• Function
• Option Expression
• Harness Attribute
Note: Highways are not included in these checks.
Comment node Displayed under Capital Logic Designer in the Project Preferences
browser.
Graphic node Displayed under Capital Logic Designer > Comment in the Project
Logic Designer > Comment > Graphic in the Project Preferences
browser.
tools in a diagram.

December 2023
Project Preferences
Field Description
Logic Designer > Comment > Graphic in the Project Preferences
browser.
• Logical
text field where you specify the thickness. The value can be any
floating-point number up to three decimal places.
See Physical Line Thickness in the Capital Design Tools -
related task flows.
Text node Displayed under Capital Logic Designer > Comment in the Project
Logic Designer > Comment > Text in the Project Preferences
browser.
browser.
lists.

December 2023
Project Preferences
Field Description
browser.
Conductor node Displayed under Capital Logic Designer in the Project Preferences
browser.
Expands to display nodes of project preferences for conductor cross-
references in Capital Logic Designer diagrams.
Allow slicing of Displayed in the Project Preferences pane when you select Capital
conductors Logic Designer > Conductor in the Project Preferences browser.
Specifies whether conductors can be sliced when a slice action is
performed:
• Selected: conductors can be sliced.
• Cleared: conductors are excluded from any slice action.
Cross-reference node Displayed under Capital Logic Designer > Conductor in the Project
Displays project preferences for conductor cross-references in Capital
Logic Designer diagrams.
These settings are used for cross-references if the Diagram node
preference “Use Style Set Cross-reference” is cleared.
Show Displayed in the Project Preferences pane when you select Capital
Logic Designer > Conductor > Cross-reference in the Project
Specify to display cross-references for conductors in diagrams
(selected) or not (cleared).
Limit references per line Displayed in the Project Preferences pane when you select Capital
Specify the maximum number of cross-references that can be
displayed on one line when there are multiple cross-references for an
object. By default, this is 1. Select the box to enable the field and
specify the number.

December 2023
Project Preferences
Field Description
Limit lines per block Displayed in the Project Preferences pane when you select Capital
Specify the maximum number of lines that can be in a block of cross-
references in a diagram. If the number of cross-references for an
instance of a shared object is greater than this value, the cross-
references are displayed in multiple blocks. If you move a cross-
reference in a block to another location in a diagram, all of the cross-
references in that block move with it. Cross-references in other blocks
for that instance do not move. By default, there is no limit. Select the
box to enable the field and specify the number.
Template Displayed in the Project Preferences pane when you select Capital
Specify the format of the cross-references.
Specify a string that combines text with references to variables. The
system interprets text in braces as a variable. This will be replaced by
the appropriate value in a cross-reference. Valid variables are as
follows:
• DESIGN.* where * is the name of a design attribute
• DIAGRAM.* where * is the name of a diagram attribute
• ZONE.* -where * is the name of a zone attribute
• EQUIV.* - if a shared net conductor is part of an equivalence set
and you specify this variable in the format, the cross-reference
text will also include the name of the other shared net conductor
from the equivalence set.
• PIN.NAME - the name(s) of the pins and pinlists that the
conductor is connected to. This variable is only available for use
in the template field of the form for conductors, pins and pinlists.
For example, you could have the format:
/{DESIGN.NAME}:{DIAGRAM.NAME} {ZONE.X}:{EQUIV.X}
If a shared net conductor, Net-2, is in the same equivalence set as the
shared net conductor by which the cross-reference is displayed, and if
Net-2 is in the zone with an X coordinate of 3, in the diagram
Audio_1, of the design Audio, the cross-reference would be:
/Audio:Audio_1 3:Net-2
If a variable is undefined in the cross-reference, the variable name is
replaced with an empty string.

December 2023
Project Preferences
Field Description
Delimiter Displayed in the Project Preferences pane when you select Capital
If the “Limit References per line” setting is greater than 1, specify a
text string to place between cross-references on the same line.
Text node Displayed under Capital Logic Designer > Conductor > Cross-
reference in the Project Preferences browser.
Displays project preferences for conductor cross-reference text.
Logic Designer > Conductor > Cross-reference > Text in the Project
Specifies the type of font used for conductor cross-reference text and
lists.
Specifies the height of conductor cross-reference text and the units of
lists.
Specifies where conductor cross-reference text is placed in a text
frame. The Preview window shows you how the justification will
look.
Connectivity node Displayed under Capital Logic Designer in the Project Preferences
browser.
Expands to display the project preferences for Connectivity Match.
Connectivity Match Displayed in the Project Preferences pane when you select Capital
Logic Designer > Connectivity in the Project Preferences browser.
Displays the match criteria options used to generate connectivity
between matching device pins and connector cavities when Auto-
Connecting Pins by Match Criteria.

December 2023
Project Preferences
Field Description
For a mated device pin Displayed in the Project Preferences pane when you select Capital
and connector cavity, Logic Designer > Connectivity > Connectivity Match in the Project
choose which to match: Preferences browser.
Device Pin
Select to generate the connectivity by matched device pins. Default.
Connector Cavity
Select to generate the connectivity by matched wire end component
pins.
See “Match Criteria” in the Capital Logic Designer User Guide for
examples of differences between generated connectivity for device
pins or connector cavities.
Define Match Criteria Displayed in the Project Preferences pane when you select Capital
Logic Designer > Connectivity > Connectivity Match in the Project
Displays a table to specify the criteria to use to match device pins or
connector cavities when the Connect By <Conductor> action is
invoked. See “Define Match Criteria Table” in the Capital Logic
Connector node Displayed under Capital Logic Designer in the Project Preferences
browser.
Displays project preferences for connector graphics in a Capital
Logic Designer diagram.
Logic Designer > Connector in the Project Preferences browser.
The width of a connector graphic in pin grids. Select the value from
the dropdown list.
Libraries Logic Designer > Connector in the Project Preferences browser.
Displays additional libraries where an associated symbol for the
connector could be found. Listed symbol libraries are searched in a
top to bottom priority sequence.
Device node Displayed under Capital Logic Designer in the Project Preferences
browser.
Displays project preferences for devices in Capital Logic Designer
diagrams.

December 2023
Project Preferences
Field Description
Display - Device Pin Displayed in the Project Preferences pane when you select Capital
Name Logic Designer > Device in the Project Preferences browser.
Specifies whether device pin names are displayed on diagrams
(selected) or not (cleared).
Display - Device Displayed in the Project Preferences pane when you select Capital
Connector Cavity Name Logic Designer > Device in the Project Preferences browser.
Specifies whether device connector cavity names are displayed on
diagrams (selected) or not (cleared).
Device Connector Displayed in the Project Preferences pane when you select Capital
Width Logic Designer > Device in the Project Preferences browser.
Specifies the width of device connectors in pin grids. Select the value
from the dropdown list.

December 2023
Project Preferences
Field Description
Freeze Symbol Select to ensure the orientation of a device connector symbol is
Orientation retained, even when the device is flipped. See the following images
for flip scenarios.
Note: If a device is rotated, its associated device receptacle

connector symbol will also rotate. Use the apply style action on a
device connector to get the initial orientation. See the following
images for an example rotation scenario.

December 2023
Project Preferences
Field Description
Merge Matching Device Displayed in the Project Preferences pane when you select Capital
Connectors Logic Designer > Device in the Project Preferences browser.
When unchecked, the device connectors are not merged during
“Share into” or “Merge into” actions on devices (Default).
When checked, the device connectors are merged based on the
following rule criteria:
• Device connectors must have the same name.
• Device connectors must have the same part number assigned (or
no part number assigned).
• Different device pins must be mapped to different cavities of
device connector.
Diagram node Displayed under Capital Logic Designer in the Project Preferences
browser.
Displays project preferences for grid spacing in Capital Logic
Designer diagrams.
Logic Designer > Diagram in the Project Preferences browser.
grid.
grid point.
Default = 5.

December 2023
Project Preferences
Field Description
displayed.
Use Style Set Cross- Displayed in the Project Preferences pane when you select Capital
reference Logic Designer > Diagram in the Project Preferences browser.
Specifies whether you use the project preferences settings for cross-
references (cleared) or you use cross-reference settings from style
sets (selected).
If you toggle this setting from cleared to selected, all existing cross-
reference blocks on open diagrams are deleted and re-created based
on applied style sets. This creates cross-reference blocks at default
locations. To position them relative to other decorations, you must
use the Apply Style functionality on the diagrams.
If you toggle this setting from selected to cleared, all existing cross-
reference blocks are deleted and re-created based on project
preferences.
Update Cross-reference Displayed in the Project Preferences pane when you select Capital
On Read Only Diagram Logic Designer > Diagram in the Project Preferences browser.
Specifies whether Read-only diagrams should have their cross-
references updated.
Highway node Displayed under Capital Logic Designer in the Project Preferences
browser.
Expands to display nodes of project preferences for highway cross-
Cross-reference node Displayed under Capital Logic Designer > Highway in the Project
Displays project preferences for highway cross-references in Capital
These settings are used for cross- references if the Diagram node
Logic Designer > Highway > Cross-reference in the Project
Specify whether you want to display cross-references for highways in

December 2023
Project Preferences
Field Description
specify the number.

December 2023
Project Preferences
Field Description
follows:
Text node Displayed under Capital Logic Designer > Highway > Cross-
Displays project preferences for highway cross-reference text.

December 2023
Project Preferences
Field Description
Logic Designer > Highway > Cross-reference > Text in the Project
Specifies the type of font used for highway cross-reference text and
lists.
Specifies the height of highway cross-reference text and the units of
lists.
Specifies where highway cross-reference text is placed in a text
frame. The Preview window shows you how the justification will
look.
Module Codes, Options Displayed under Capital Logic Designer in the Project Preferences
node browser.
Displays project preferences to pre-define which 'tag fields' such as
option expressions and module code fields are available on the Edit
Object dialog boxes of Capital Logic Designer designs and diagrams,
for any given project.

December 2023
Project Preferences
Field Description
Enable and Display Displayed in the Project Preferences pane when you select Capital
Logic Designer > Module Codes, Options in the Project Preferences
browser.
Select the required option to display or suppress the following. The
default for all settings is On.
• Option
Allows you to add object expressions to objects and designs.
When selected, the Applicable Options and Option fields display
on the Capital Logic Designer Edit Designs dialog box, and the
Options field displays on the Capital Logic Designer Edit Object
Properties dialog box. The default setting is On. (See the Capital
Logic Designer help system for more information).
• Modules
Allows you to add Module Codes to objects and designs. When
selected, the Applicable Modules field displays on the Capital
Logic Designer Edit Designs dialog box, and the Modules field
displays on the Capital Logic Designer Edit Object Properties
dialog box. The default setting is Off. (See the Capital Logic
Designer help system for more information).
• Show Legacy Module Code
Allows you to control the display of the Module Code attribute on
Capital Logic Designer objects. When selected, the Module Code
attribute displays on any relevant Capital Logic Designer object
properties dialog box. The default setting is Off. (See the Capital
Logic Designer help system for more information).
The Show Legacy Module Code check box is set to Off when
importing and opening any project created prior to Capital version
2012.1.
Multicore node Displayed under Capital Logic Designer in the Project Preferences
browser.
Displays project preferences for multicores in Capital Logic Designer
diagrams.

December 2023
Project Preferences
Field Description
Default Conductor Type Displayed in the Project Preferences pane when you select Capital
(when no abstraction Logic Designer > Multicore in the Project Preferences browser.
assigned) Specifies how the system converts uninstantiated cores into
conductors when sharing a library multicore.
When design has a Design Abstraction assigned, the system converts
all conductors based on the assigned abstraction (for example, Wiring
abstraction will have wires created, and System abstraction will have
nets created).
When the design does not have an abstraction assigned, the system
uses these settings:
• Wires
The system converts library inner cores into wires while sharing a
library multicore.
• Nets
The system converts library inner cores into nets while sharing a
library multicore.
Split Indicators Displayed in the Project Preferences pane when you select Capital
Logic Designer > Multicore in the Project Preferences browser.
Specifies whether multicore indicators are split where the conductors
in the multicore connect to different pin lists (selected) or whether the
indicators stretch across all of the conductors in the multicore
(cleared).
Indicator node Displayed under Capital Logic Designer > Multicore in the Project
Displays project preferences for multicore indicators in Capital Logic
Designer diagrams.
Indicator Width Displayed in the Project Preferences pane when you select Capital
Logic Designer > Multicore > Indicator in the Project Preferences
browser.
Specifies the width of multicore indicators in pin grids. Select the

December 2023
Project Preferences
Field Description
Separate Hookups at Displayed in the Project Preferences pane when you select Capital
different levels Logic Designer > Multicore > Indicator in the Project Preferences
browser.
For nested multicores, this specifies whether indicator hookups on
different multicore levels are displayed at unique grid positions or
not.
If cleared, hookups for different multicore levels are displayed at the
same position.
If selected, hookups corresponding to an inner multicore indicator are
placed next to the indicator and hookups belonging to the next level
indicator are placed further away. The space between the hookups is
specified by “Number of grids to separate hookups”.
For example:
Number of grids to Displayed in the Project Preferences pane when you select Capital
separate hookups Logic Designer > Multicore > Indicator in the Project Preferences
browser.
Specifies the number of grid spaces that separate hookups from the
indicator and from each other if “Separate Hookups at different
levels” is selected.

December 2023
Project Preferences
Field Description
Preserve Indicator Displayed in the Project Preferences pane when you select Capital
Widths Logic Designer > Multicore > Indicator in the Project Preferences
browser.
If you have a nested multicore (that is, a parent multicore that
contains a child multicore), the multicore indicators for the parent and
child overlap each other.
With this option cleared, the indicators for the multicores are different
widths (the parent multicore’s indicator is wider).

With this option selected, the indicators for the multicores are the
same width.

December 2023
Project Preferences
Field Description
Max Grid Distance for Displayed in the Project Preferences pane when you select Capital
Toggle Indicator Logic Designer > Multicore > Indicator in the Project Preferences
browser.
This enables you to specify the maximum distance (in terms of the
Pin Grid) between the bottom left extent of the conductors of a
multicore which will be evaluated by the Toggle/Add indicator action
for tying together with single indicator.
If the toggle action is performed with a default setting of 3, specified
in the pin grid field, the indicator would not stretch, as shown
below.
.
If the pin grid preference is changed, for example to 6, and the toggle
action is performed, the indicator would stretch as shown below and
both these wires are grouped, as the distance between the bottom left
extent of these wires (a setting of 5 in the pin grid field) is still within
the project preference specified (a setting of 6 in the pin grid
field).

December 2023
Project Preferences
Field Description
Connect hookups Displayed in the Project Preferences pane when you select Capital
directly onto indicator Logic Designer > Multicore > Indicator in the Project Preferences
browser.
This option allows you to decide whether to connect the indicator
directly on to the shield hookup, or not. With the option selected the
connection snaps directly to the edge of shield boundary (that is, its
radius), thereby displaying a straight line between shields and no
visible line beyond the radius providing a clear and clean diagram
layout. With the option cleared the connection will snap to the grid
and a graphical hookup arm will be drawn from the grid to the
indicator. For indicators created with this setting enabled the option is
retained and reused whenever that indicator is redrawn.
Note: If this preference is used in conjunction with the ‘Separate
Hookups at different levels’ preference it will assume primacy
and shields will still connect directly on to the indicator. For wired
connections, splices will still be added at separate grid points. This
option provides a clear layout when creating daisy-chain connections
between different multi-cores placed one grid apart.
Quick Add node Displayed under Capital Logic Designer > Multicore in the Project
Displays the shortcut key preferences when quickly adding
multicores in Capital Logic Designer diagrams.
Default Twisted Displayed in the Project Preferences pane when you select Capital
Multicore Logic Designer > Multicore > Quick Add in the Project Preferences
browser.
Specifies the type of twisted multicore to add by default when you
invoke the Quick Add ribbon action or press Shift+T.
Default Shielded Displayed in the Project Preferences pane when you select Capital
browser.
Specifies the type of shielded multicore to add by default when you
invoke the Quick Add ribbon action or press Shift+H.
Default Sheathed Displayed in the Project Preferences pane when you select Capital
browser.
Specifies the type of sheathed multicore to add by default when you
invoke the Quick Add ribbon action or press Shift+S.

December 2023
Project Preferences
Field Description
Name node Displayed under Capital Logic Designer in the Project Preferences
browser.
in Capital Logic Designer diagrams.
Text node Displayed under Capital Logic Designer > Name in the Project
Displays project preferences for object name text in Capital Logic
Designer diagrams.
Logic Designer > Name > Text in the Project Preferences browser.
lists.
Net node Displayed under Capital Logic Designer in the Project Preferences
browser.
Displays project preferences for net conductors in Capital Logic
Designer diagrams.
Net Join Display Type Displayed in the Project Preferences pane when you select Capital
Logic Designer > Net in the Project Preferences browser.
Specifies how a pin is displayed when a net is connected to it. Select
either Square or Circle.
Net Join Display Size Displayed in the Project Preferences pane when you select Capital
Logic Designer > Net in the Project Preferences browser.
Specifies the size (in grid spaces) of the square or circle that is
displayed where nets join in a diagram. By default, this is 0.25 grid
spaces.
Overbraid node Displayed under Capital Logic Designer in the Project Preferences
browser.
Displays project preferences for overbraids in Capital Logic Designer
diagrams.

December 2023
Project Preferences
Field Description
Indicator node Displayed under Capital Logic Designer > Overbraid in the Project
Displays project preferences for overbraid indicators in Capital Logic
Designer diagrams.
Indicator Width Displayed in the Project Preferences pane when you select Capital
Logic Designer > Overbraid > Indicator in the Project Preferences
browser.
Specifies the width of overbraid indicators in pin grids. Select the
Connect hookups Displayed in the Project Preferences pane when you select Capital
directly onto indicator Logic Designer > Overbraid > Indicator in the Project Preferences
browser.
This option allows you decide whether to connect the indicator
directly on to the shield hookup, or not. With the option selected the
connection snaps directly to the edge of shield boundary (that is, its
radius), thereby displaying a straight line between shields and no
visible line beyond the radius providing a clear and clean diagram
layout. With the option cleared the connection will snap to the grid
and a graphical hookup arm will be drawn from the grid to the
indicator. For indicators created with this setting enabled the option is
retained and reused whenever that indicator is redrawn.
Note: If this preference is used in conjunction with the ‘Separate
Hookups at different levels’ preference it will assume primacy
and shields will still connect directly on to the indicator. For wired
connections, splices will still be added at separate grid points. This
option provides a clear layout when creating daisy-chain connections
between different multi-cores placed one grid apart.
Quick Add node Displayed under Capital Logic Designer > Overbraid in the Project
Displays the shortcut key preferences when quickly adding
overbraids in Capital Logic Designer diagrams.
Default Overbraid Displayed in the Project Preferences pane when you select Capital
Logic Designer > Overbraid > Quick Add in the Project Preferences
browser.
Specifies the type of overbraid to add by default when you invoke the
Quick Add ribbon action or press Shift+O.
Pin node Displayed under Capital Logic Designer in the Project Preferences
browser.
Expands to display nodes of project preferences for pin cross-

December 2023
Project Preferences
Field Description
Cross-reference node Displayed under Capital Logic Designer > Pin in the Project
Displays project preferences for pin cross-references in Capital Logic
Designer diagrams.
preference Use Style Set Cross-reference is cleared.
Logic Designer > Pin > Cross-reference in the Project Preferences
browser.
Specify whether you want to display cross-references for pins in
browser.
specify the number.
browser.

December 2023
Project Preferences
Field Description
browser.
follows:
browser.
Text node Displayed under Capital Logic Designer > Pin > Cross-reference in
the Project Preferences browser.
Displays project preferences for pin cross-reference text.

December 2023
Project Preferences
Field Description
Logic Designer > Pin > Cross-reference > Text in the Project
Specifies the type of font used for pin cross-reference text and
lists.
Specifies the height of pin cross-reference text and the units of
lists.
Specifies where pin cross-reference text is placed in a text frame. The
Preview window shows you how the justification will look.
Pin List node Displayed under Capital Logic Designer in the Project Preferences
browser.
Expands to display nodes of project preferences for pin list cross-
Cross-reference node Displayed under Capital Logic Designer > Pin List in the Project
Displays project preferences for pin list cross-references in Capital
Logic Designer > Pin List > Cross-reference in the Project
Specify whether you want to display cross-references for pin lists in
specify the number.

December 2023
Project Preferences
Field Description
follows:

December 2023
Project Preferences
Field Description
Text node Displayed under Capital Logic Designer > Pin List > Cross-
Displays project preferences for pin list cross-reference text.
Logic Designer > Pin List > Cross-reference > Text in the Project
Specifies the type of font used for pin list cross-reference text and
lists.
Specifies the height of pin list cross-reference text and the units of
lists.
Specifies where pin list cross-reference text is placed in a text frame.
The Preview window shows you how the justification will look.
Property node Displayed under Capital Logic Designer in the Project Preferences
browser.
text in Capital Logic Designer diagrams.
Text node Displayed under Capital Logic Designer > Property in the Project
Displays project preferences for object property text in Capital Logic
Designer diagrams.
Logic Designer > Property > Text in the Project Preferences browser.
lists.

December 2023
Project Preferences
Field Description
lists.
Wire node Displayed under Capital Logic Designer in the Project Preferences
browser.
Displays project preferences for wires in Capital Logic Designer
diagrams.
Poke Home Arrow Style Displayed in the Project Preferences pane when you select Capital
Logic Designer > Wire in the Project Preferences browser.
The arrow style used to represent poke homes. Select from the
dropdown list.
Treat Wires Displayed in the Project Preferences pane when you select Capital
Terminating On A Logic Designer > Wire in the Project Preferences browser.
Different Harness As Ensure that this is selected if you are working with poke home wires
Poke Home in Capital Logic Designer.
Project Preferences for Capital Project Manager

Certain project preferences are available specifically for designs and diagrams in Capital Project
Manager. They are not applicable for any other Capital tool.
Table 2-7. Project Preferences for Capital Project Manager Designs

Field Description
Capital Project Manager Displayed in the Project Preferences browser.
node Expands to display nodes of project preferences for Capital Project
Manager designs.

December 2023
Project Preferences
Table 2-7. Project Preferences for Capital Project Manager Designs (cont.)
Field Description
Preselect the option Displayed in the Project Preferences browser at the Capital Project
expression propagation Manager base node.
preference in the Edit When this preference is selected, it preselects the user preference on
Shared Multicore dialog the Edit Shared Multicore dialog box in Capital Project Manager.
Once selected it propagates the options defined on the parent shared
multicore to its inner cores and nested multicores. By default, this
project preference is not selected.
Project Preferences for Capital Wiring Integrator Designs

Certain project preferences are available specifically for designs and diagrams in Capital Wiring
Integrator. They are not applicable for any other Capital tool.
Table 2-8. Project Preferences for Capital Wiring Integrator Designs

Field Description
Bundle Calculation Displayed in the Project Preferences browser under the Capital
Wiring Integrator node.
Displays project preferences used when calculating a bundle diameter
for a bundle width report.

December 2023
Project Preferences
Table 2-8. Project Preferences for Capital Wiring Integrator Designs (cont.)
Field Description
Wire Gap Coefficient Displayed in the Project Preferences pane when you select Capital
Wiring Integrator > Bundle Calculation in the Project Preferences
browser.
Specifies the coefficient that is used to represent the air gap between
adjacent wires when calculating a bundle diameter. The value must be
a float (decimal number) of 1 or higher. By default, this is 1.154.
A value of 1 indicates that there is no air gap.
If a multicore has an OutsideDiameter attribute, it is treated as one
wire by these calculations. Otherwise, its constituent wires are
processed.
Bundle diameter (DBundle) is calculated in the following ways
(given a number of wires of diameter DWire):
• If the bundle contains one wire:
DBundle = DWire
• If the bundle contains two wires:
DBundle =
• If the bundle contains three or more wires:
DBundle =
where is calculated from DWire
The cross-sectional area of a wire ( ) is calculated in a

variety of ways (depending on what data exists):
• If the OutsideDiameter attribute exists on a wire, this is used as-is.
This also applies if a multicore has an OutsideDiameter attribute.
In this case, the wires within the multicore are ignored.
• If a wire has no OutsideDiameter attribute but has both a
WireMaterial attribute and a WireCSA attribute defined, the
WireCSA attribute is used to calculate the copper diameter and an
insulation thickness determined from Capital Component
Manager (from the Wire Insulation Thickness Dialog) is added to
calculate DWire.
• If the OutsideDiameter attribute does not exist on a wire, the
WireCSA attribute is used to calculate the copper diameter and
the value specified for the Default Insulation Thickness project
preference is added to calculate DWire. If a multicore does not
have an OutsideDiameter attribute, its constituent wires are
processed individually in this way.
In all these cases, this value of DWire is used to calculate the overall
CSA of copper plus insulation.

December 2023
Project Preferences
Field Description
Default Insulation Displayed in the Project Preferences pane when you select Capital
Thickness Wiring Integrator > Bundle Calculation in the Project Preferences
browser.
Specifies the insulation thickness that is used by default when
calculating the bundle diameter. The value must be a float (decimal
number). By default, this is 0.0.
Comment node Displayed under Capital Wiring Integrator in the Project Preferences
browser.
Graphic node Displayed under Capital Wiring Integrator > Comment in the Project
Wiring Integrator > Comment > Graphic in the Project Preferences
browser.
tools in a diagram.

December 2023
Project Preferences
Field Description
Wiring Integrator > Comment > Graphic in the Project Preferences
browser.
• Logical
See Physical Line Thickness in the Capital Design Tools -
related task flows.
Text node Displayed under Capital Wiring Integrator > Comment in the Project
Wiring Integrator > Comment > Text in the Project Preferences
browser.
browser.
lists.

December 2023
Project Preferences
Field Description
browser.
Connector node Displayed under Capital Wiring Integrator in the Project Preferences
browser.
Displays project preferences for connector graphics in a Capital
Wiring Integrator diagram.
Wiring Integrator > Connector in the Project Preferences browser.
The width of a connector graphic in pin grids. Select the value from
the dropdown list.
Render back-face Displayed in the Project Preferences pane when you select Capital
Wiring Integrator > Connector in the Project Preferences browser.
Specifies how virtual connectors are drawn in Capital Wiring
If selected, the connector has a line that runs along the extent of the
slot. For example:
Here you can see there is a bright green line drawn for the part of P1
that is flush with the slot. The line for the slot is then drawn over that
bright green line.
If cleared, no connector line is drawn flush with the slot.

December 2023
Project Preferences
Field Description
Retain topology By default, this is not selected. That means, when a Capital Logic
properties not defined Designer (logical) object, such as a connector, is associated with a
on associated connector Capital Wiring Integrator (topological) object, all properties on the
topological object are overwritten with values from the logical object.
Note that this means that properties which exist on the topological
object but not on the logical object are removed from the topological
object.
If this is selected, when a logical object is associated with a
topological object, properties on the topological object are
overwritten with values from the logical object, only if they exist on
the logical object. Note that this means that properties which exist on
the topological object but not on the logical object are not modified or
deleted.
See “Associating Logical Designs with the Topological Design” in
the Capital Wiring Integrator chapter of the Capital Logic Designer
User Guide for information about the action.
Libraries Wiring Integrator > Connector in the Project Preferences browser.
When editing a signal map in Capital Systems Integrator/Topology,
you can display a Connector Faceview Panel for a connector.
If the connector has a library part with associated faceview symbols
in Capital Component Manager, the panel offers these symbols for
selection.
Note: A faceview symbol is created as a comment symbol with
pins in Capital Symbol Designer.
If the library part does not have associated faceview symbols in
Capital Component Manager, the panel searches for symbols (with
the same name as the connector part number) in the symbol libraries
specified in this preference.
Name node Displayed under Capital Wiring Integrator in the Project Preferences
browser.
in Capital Wiring Integrator diagrams.
Text node Displayed under Capital Wiring Integrator > Name in the Project
Displays project preferences for object name text in Capital Wiring

December 2023
Project Preferences
Field Description
Wiring Integrator > Name > Text in the Project Preferences browser.
lists.
Plane node Displayed under Capital Wiring Integrator in the Project Preferences
browser.
Displays project preferences for the grid spacing on a plane diagram
in Capital Wiring Integrator.
Wiring Integrator > Plane in the Project Preferences browser.
You can specify how this grid is displayed using the Set Grid
Defaults dialog in Capital Systems Integrator.
You can use the Modify Physical Scale dialog in Capital Wiring
Integrator to specify the physical scale of objects in a design.
grid.

December 2023
Project Preferences
Field Description
grid point.
Default = 5.
displayed.
Property node Displayed under Capital Wiring Integrator in the Project Preferences
browser.
text in Capital Wiring Integrator diagrams.
Text node Displayed under Capital Wiring Integrator > Property in the Project
Wiring Integrator diagrams.
Wiring Integrator > Property > Text in the Project Preferences
browser.
lists.
browser.
lists.
browser.

December 2023
Project Preferences
Project Preferences for Capital Systems Modeler Designs

Systems Modeler.
Table 2-9. Project Preferences for Capital Systems Modeler Designs

Field Description
Capital Systems Displayed in the Project Preferences browser.
Modeler node Expands to display nodes of project preferences for Capital Systems
Modeler designs.
Applicable Options Displayed in the Project Preferences browser under the Capital
node Systems Modeler node.
Displays project preferences for Applicable Options on Capital
Systems Modeler designs.
Mandate Applicable Displayed in the Project Preferences pane when you select Capital
Options Systems Modeler > Applicable Options in the Project Preferences
browser.
Specifies:
Systems Modeler design only when that design has applicable
options specified for it (selected)
or
Systems Modeler design regardless of whether any applicable
options are specified for the design (cleared).
Auto-route node Displayed under Capital Systems Modeler in the Project Preferences
browser.
Expands to display the project preferences for user defined auto-
routing in Capital Systems Modeler diagrams, enabling the routing of
signals and messages.
Diagram Flow Displayed in the Project Preferences pane when you select Capital
Systems Modeler > Auto-route in the Project Preferences browser.
Specifies the layout direction of the diagram flow. You can accept the
current default flow, or either select Horizontal or Vertical from the
dropdown list.
Minimum Signal/ Displayed in the Project Preferences pane when you select Capital
Message Spacing Systems Modeler > Auto-route in the Project Preferences browser.
Defines the minimum spacing size between signals/messages
represented by the visible grid on a diagram when the auto-routing
action is applied. Specify a positive integer value.

December 2023
Project Preferences
Table 2-9. Project Preferences for Capital Systems Modeler Designs (cont.)
Field Description
Minimum Signal/ Displayed in the Project Preferences pane when you select Capital
Message Length Systems Modeler > Auto-route in the Project Preferences browser.
Specifies the minimum signal/message length represented by the
visible grid on a diagram when the auto-routing action is applied.
Specify a positive integer value.
Uniqueness Displayed in the Project Preferences pane when you select Capital
Systems Modeler > Checks > Uniqueness in the Project Preferences
browser.
Lists selection criteria that work in conjunction with each other and
also design rule name checks enabling you to inspect, and report on,
where there are duplicate names across object types within a single
design or all designs in a build list, including variants in option
expressions and/or harness attributes.
The Across Object Types and Option Expressions preferences are
selected by default. Selecting the preferences individually, or in
combination enables you to scale the depth of your checks.
For example, selecting only the Across Object Types preference
means the system will report instances where, a Splice and a
Connector may have the same name.
However, if both the Across Object types and the Option expression
preferences are checked and the same Splice and Connector have
differing option expressions of RHD and LHD, then they will not be
highlighted in the report.
Tick the check box to include the required criteria when running
name checks.
The available criteria for checking if names are unique are:
Comment node Displayed under Capital Systems Modeler in the Project Preferences
browser.
Graphic node Displayed under Capital Systems Modeler > Comment in the Project

December 2023
Project Preferences
Field Description
Systems Modeler > Comment > Graphic in the Project Preferences
browser.
tools in a diagram.
Systems Modeler > Comment > Graphic in the Project Preferences
browser.
• Logical
See “Physical Line Thickness” on page 626 for a definition and
links to related task flows.
Text node Displayed under Capital Systems Modeler > Comment in the Project
Systems Modeler > Comment > Text in the Project Preferences
browser.

December 2023
Project Preferences
Field Description
browser.
lists.
browser.
Diagram node Displayed under Capital Systems Modeler in the Project Preferences
browser.
Displays project preferences for grid spacing in Capital Systems
Modeler diagrams.
Systems Modeler > Diagram in the Project Preferences browser.
to the drawing grid. This setting enables you to specify how many
points of the drawing grid are between the points of the visible grid
using a percentage of the print scale. For example, if you specify 50,
there will be one invisible drawing point halfway between each point
on the visible grid.
grid point. Mandatory.

December 2023
Project Preferences
Field Description
displayed. Mandatory.
Property node Displayed under Capital Systems Modeler in the Project Preferences
browser.
text in Capital Systems Modeler diagrams.
Text node Displayed under Capital Systems Modeler > Property in the Project
Systems Modeler diagrams.
Systems Modeler > Property > Text in the Project Preferences
browser.
lists.
browser.
lists.
browser.
Project Preferences for Design Release

You can use certain project preferences to configure actions when you release a design. They
are applicable across all relevant Capital tools.

December 2023
Project Preferences
Table 2-10. Project Preferences for Design Release

Field Description
Check node Displayed in the Project Preferences browser.
Displays project preferences that the system references when
running design rule checks during design release.
Annotate by Default Displayed in the Project Preferences pane when you select Check in
If selected, the Annotate results field on the Release Designs Dialog
Box is selected by default and cannot be cleared.
If cleared, a user can choose whether to select the Annotate results
field.
Annotation of the design will only occur if the design contains a
border with a [CHECK_RESULTS] property (assigned to the
border using Capital Symbol Designer).
Annotation Template Displayed in the Project Preferences pane when you select Check in
Enables the specification of the information and text that is to be
automatically inserted into the design when design rule checks are
run during design release.
By default, the annotation is “Verified by {User} on {DATE}”.
The system will evaluate the placeholders and update them
accordingly with the date and time the checks were run and the
name of the user who ran them.
For example: Verified by Smith on 19 Jan, 2017 2:24:34 PM
You can add other default text by typing into the box but the system
will not evaluate any other placeholders. It simply strips the
brackets from the placeholder.
For example, if you entered Verified {design.name} by {USER} on
{DATE}, the resulting text will be:
Verified design.name by Smith on 19 Jan, 2017 2:24:34 PM
Use Design Rule Checks If cleared, the Design Rule Checks dialog box opens with the
settings from previous run design rule checks selected as specified in project preferences.
That is, it selects the design rule checks that are selected to run in
the current running mode and design abstraction (if specified).
If you modified the checks on the previous run, in the current mode
and abstraction, the selections are not preserved.
If selected, the Design Rule Checks dialog box preserves the checks
from the previous run in the current mode and abstraction.

December 2023
Project Preferences
Table 2-10. Project Preferences for Design Release (cont.)

Field Description
Issues Used to specify which DRC failures to track using Issues and
configure the automatic creation and overridden Issues preferences.
You must ensure that the following behaviors are present in at least
one release level:
• Issue Opened
• Issue Closed
• Issue Overridden
See also “Issues” under “Release Level Behaviors” in the Capital
Auto-create Issues for Specify which of the following DRC failure types to create Issues
DRC messages: for automatically:
• Errors (default)
• Warnings
• Information
Auto-create Issues only Select to only auto-create Issues for violations of DRCs that you
for DRCs marked “Issue have specified as “Issue Status Editable” in the project preferences
Status Editable” in project “Checks node”. See also “Project Preferences - Checks Node” on
preferences page 220. If “Issue Status Editable” is cleared on all the DRCs, no
Issues are created for any of the DRC failures. Default.
Clear to auto-create Issues for all DRC failures.
Auto-create Issues for the Specify which of the following DRC design types to create Issues
following DRCs for automatically.
• Functional
• Platform
• Logic
• Integrator
• Topology
• Harness/SBOM
Ignore DRCs with “Overridden Issues” are Issues in a release level status that is
overridden Issues when: specified with the “Issue Overridden” behavior.
Specify to ignore DRC failures with associated overridden Issues
when either saving a design, transitioning a design between release
levels, or both.
Default is cleared.

December 2023
Project Preferences
General Project Preferences Applicable to all

Applications
Certain project preferences are applicable across all relevant applications.
Table 2-11. General Project Preferences Applicable to all Applications

Field Description
General node Displays project preferences applied to all applications.
Purge unplaced objects Select to delete any design-wide objects, listed as connectivity objects
on Save in the Unplaced folders in the Design Browser, when you save the
design. Clear to preserve the objects in the Unplaced folders to
continue creating the connectivity on the diagram.
When you use Capital Schematic Generator for Logic Designer to
generate diagrams using a prototype design, unconnected stacked
pins that do not match any stacked pins in the prototype design are
ignored (selected) or listed (cleared) in the Unplaced folders in the
Design Browser as individual pins.
Caution: If selected, you may want to set your project
preferences for design rule checks to run the “Unplaced object”
check when you save a design. The check identifies non-shared
objects that are not placed on a diagram and enables you to verify and
distribute the connectivity before you save and purge the objects in
the Unplaced folders.
Effectivity Specifies whether you want to use the effectivity functionality with
the project (selected) or not (cleared).
Apply table styling to If selected, content in a Collaborate note table will be rendered based
Collaborate notes on table styling settings.
content If cleared, content in a Collaborate note table will be rendered using
the HTML formatting available on the note content.
Disallow pin duplication If cleared (the default behavior), you can add multiple instances of
within a design shared or unshared pins within a design.
If selected, you can not add further instances of pins unless you make
shared pins Unrestricted or you add the pins as Reference Pins.
Note: Stud pins are specifically excluded from the check, as they
can be placed a number of times to facilitate the mating of
multiple ring terminals
Show non-optioned Specifies whether you want to include objects that do not have
objects options assigned to them when you generate an evaluated design
(selected) or not (cleared). If cleared, any evaluated designs that are
generated will include only those objects with options assigned to
them.

December 2023
Project Preferences
Table 2-11. General Project Preferences Applicable to all Applications (cont.)

Field Description
Update Symbol on When running Library Part Update in Capital Logic Designer, this
Library Part Update preference enables you to simultaneously update the diagram with
any symbol changes that may have occurred (selected), or not.
If cleared and library parts with associated symbols are assigned to a
parameterized device, the device will remain parameterized.
However, if the option is selected, the associated symbol will replace
the existing parameterized symbol.
Show generated shared When you copy Capital Logic Designer designs with shared pin lists
pinlist for mapping in to another project, by default the system does not list generated
Advance Copy shared pin lists for mapping. Select to map source shared pin lists to
generated shared pin lists manually. With this preference selected, a
Shared Pin Lists tab lists all shared pin lists for mapping (when you
click the Advanced button on the Copying to Project dialog box).
Copy Advance/Import When this preference is selected, Copy Advanced and Import Design
Designs to use incoming actions will use the timestamps and author details available on the
timestamps and author source designs when added to the target project. By default, this
details project preference is not selected.
Copy Advance/Import This preference applies when importing designs into a project or
Designs to use incoming copying designs between projects.
Options & Module With this preference cleared (default), the system does not copy
relations and folders inclusive/exclusive relationships for options and module codes to the
target project. In addition, it does not copy any folder structure for
options and module codes.
With this selected in the preferences for the target project, the system
does copy those things to the target project.
Disable Create, Edit and When this preference is selected you will not be able to create, edit, or
Delete actions for delete Collaborate notes, even if the user has the permission to
Collaborate Notes perform the actions. All UI elements and shortcuts for these tasks will
be hidden or disabled.
Display blank lines Used to control the rendering of blank lines while displaying property
while showing property text on diagrams for all designs, including released designs.
text Select to display blank lines in the text when you enter two line
breaks in the Value field, or clear to ignore the line breaks.
Note: Blank lines are not preserved if you open the diagram in
Capital E/E Reporter.
Poke home prefix Specifies a prefix that is added to wires that are poke homes when a
report is generated for the project.
Part Selection - Current Specifies to use only Capital Component Manager components that
components only have the Status of Current on designs (selected) or not (cleared).

December 2023
Project Preferences

Field Description
Part Selection - Specifies to use only preferred Capital Component Manager
Preferred components components (selected) or not (cleared).
only
Allowed Domains for Restricts access to objects from within designs to those belonging to
Parts, Symbol libraries, domains flagged as allowed for the project, or those that do not
ICDs and Shared belong to a domain.
Objects The Available list displays all domains to which the currently
logged-in user has access (read-only or read-write).
• To specify a domain for a project, select the domain in the
Available list, and then click the Add button to move it into the
Selected list.
• To restrict a domain from a project, select the domain in the
Selected list, and then click Remove.
The Add All and Remove All buttons are available to speed up
selection.
Customer Specifies the default Customer that will be used when creating
Harness Designs. Select the name from the dropdown list.
Manufacturing site Specifies the default Manufacturing Site that will be used when
creating Harness Designs. Select the name from the dropdown list.
PLM Preferences - When checked prevents the management of PDM linked properties
Disable management of for a design being updated in the database when storing a time stamp,
PDM linked properties if the design or build list is read only.
on read-only designs/
build lists
PLM Preferences - When checked prevents the storing of a time stamp on a design
Disable management of during an update or publish action if the design is read only.
time stamp properties on
data transfer

December 2023
Project Preferences

Field Description
PLM Preferences - Restricts the action of creating new designs or revisions, on a per
Create/Revise Designs design type basis, to the established PLM system only. Selected
from PLM Only design types will have these actions disabled in the Capital design
application User Interface.
The Available list displays all design types to which the currently
logged-in user has access.
• To specify a design type for PLM creation/revision only, select it
in the Available list, and then click the Add button to move it into
the Selected list.
• To specify a design type for Capital design application based
creation/revision only, return it to the Available list by selecting it
in the Selected list before clicking Remove.
The Add All and Remove All buttons are available to speed up
selection.
Project Preferences - Checks Node

You can use the preferences on the Checks node to configure which Design Rule Checks
(DRCs) to run automatically in the Running modes when using the Capital design tools.
Caution
To avoid losing modifications to a DRC configuration, you must click Apply or OK to save
the changes before you switch to a different configuration, Running mode, or preference.
Table 2-12. Project Preferences - Checks Node Designs

Field Description
Checks node Displayed under the following nodes in the Project Preferences
browser.
• Capital Harness Designer
• Capital Systems Integrator
• Capital Wiring Integrator
• Manufacturing
• Capital Systems Architect
• Capital Systems Modeler
Displays the design rule checks running mode configuration options.
See “Design Rule Check Descriptions” on page 261 for full details of
available checks for each tool.
Running Mode

December 2023
Project Preferences
Table 2-12. Project Preferences - Checks Node Designs (cont.)

Field Description
Displayed in the Project Preferences pane when you select a Checks
node in the Project Preferences browser.
Located at the top of the dialog box, this enables you to select a
running mode for design rule checks from a drop-down list.
As there can be a number of different manually configurable release
levels, these have been grouped under release level type. They are:
Draft Release Levels, Pending Release Levels, Obsolete Release
Levels, and Released Release Levels. If you select one of these, a new
dropdown menu is available where you specify its actual release
level.
Select a running mode and a Design Abstraction to specify a scenario
You can specify DRC settings as a combination of Release Level and
abstraction. This is fully supported in the API for writing custom
DRCs.
Note: You require the appropriate user permission to edit project
preferences to setup the DRCs to be run for each release level.
Manual When you run design rule checks manually in a design application by
pressing Space Bar and entering DRCs and selecting the checks to
run. The Check tab of the output window displays the results.
Background Design rule checks are run automatically in the background in a
design application. Background runs occur when the background
mode has been activated and after changes have been made to objects
in the design to which the currently active diagram belongs. The
Check tab of the output window displays the results.
On Save Design rule checks are run automatically on saving a diagram in a
design application. If there are any failures of severity Error, the save
is canceled and the Check tab of the Output Window displays the
failures, prompting for manual intervention. By default, no design
rule checks are run for the On Save mode. If you want checks to run
when you save, you must specify preferences for this mode.
Draft Release Levels Design rule checks are run automatically on transitioning a design to
a draft release level. The Check tab of the output window displays the
results.
Pending Release Levels Design rule checks are run automatically on transitioning a design to
a pending release level. The Check tab of the output window displays
the results.

December 2023
Project Preferences

Field Description
Obsolete Release Levels Design rule checks are run automatically on transitioning a design to
an obsolete release level. The Check tab of the output window
displays the results.
Released Release Levels Design rule checks are run automatically on releasing a design. The
Release Level Template Each Release Level type for the Running mode groups has an
associated template, available for selection using the drop-down
menu.
Set the required DRC selection by clicking the checkbox from the list
displayed for each release level in the template before creating the
actual release level.
This is to save time when creating new release levels for your
designs. For example, each release level of the type Pending
automatically copies the DRCs specified on the Pending Release
Levels template.
Once the DRC settings have copied you can manually adjust the
DRCs required for individual release levels without making changes
to the templates.
Note: The use of templates is optional. On the initial use of this
functionality the default templates for Draft, Pending and
Obsolete Release Levels are blank. The Released template contains
settings that were used for Released type Release Levels prior to the
2207 software release, when these DRC settings were hard-coded and
not editable.
On Processing Design rule checks (including custom checks) are run automatically
on launching the Harness Processing wizard in Capital Harness
Designer / Modular.
No checks are selected by default. You must select at least one check
to trigger the automatic running of the checks.
See also “Harness Processing Configuration” in the Capital Harness
Designer User Guide

December 2023
Project Preferences

Field Description
Design Abstraction Displayed in the Project Preferences pane when you select a Checks
node in the Project Preferences browser.
Located at the top of the dialog box, enables you to select a design
abstraction from a dropdown list.
Select a Running Mode and a design abstraction to specify a scenario
The list of design abstractions depends on those available in the
project. You can select an empty row from the dropdown list that
represents designs without a design abstraction. Designs which
reference an abstraction which no longer exists also default to the
empty abstraction rule check configuration.

December 2023
Project Preferences

Field Description
Design Rule Checks Lists the available design rule checks, grouped into categories, in a
browser tree to set preferences for each check. See “Design Rule Check
Displayed in the Project Descriptions” on page 261 for a detailed explanation of each
Preferences pane when available Design Rule Check.
you select a Checks The preferences for each check apply only to the selected
node in the Project combination of Running Mode and Design Abstraction. When you
Preferences browser. change the preferences for a particular combination, ensure that you
click Apply at the bottom of the dialog box before selecting a new
running mode or design abstraction.
Select a design rule check in the tree to run it automatically. Clear the
check to run it manually. If click a design rule check category (for
example, Connectivity), all of the checks under that category are
selected or cleared.
Right-click Actions
• Right-click a DRC to specify whether a failure generates an Error,
Warning, or Information (notification). You can right-click the
parent DRC node to apply the failure type to all the DRCs in the
group.
Note: A single custom DRC can have multiple violations
defined in it. While writing a custom DRC, you can define
different severities for each violation using the report() method as
well as a default severity. If no severity is defined for a violation
(that is, it is assigned a NULL severity), it uses the default
severity. The default severity of a custom DRC is visible in the
project preferences, and any changes made to it will persist even
after opening, closing, exporting, or importing the project.
Changing the severity of the preference does not change the
original custom code. When a custom DRC is run, the severity for
each violation is decided in the following order:
• 1. System uses severity for a particular violation as defined in
the custom DRC code using the report() method in the
IXDRCViolationReporter API (violation reporter class).
• 2. Only if report() method passes NULL for that violation, the
system uses the default severity of the custom DRC as updated
explicitly in the project preferences.
• 3. If the default severity is not updated in the preferences, the
system uses the default severity from the custom DRC code.

December 2023
Capital Compressed Format for Projects

Field Description
(cont...) • Allowed to Run
Select to enable the check in the Design Rule Checks dialog box
(used to run checks manually) in the design application.
Clear to deactivate the check in the tree. The check will not run;
however, you can still right-click it to edit its preferences.
Allowed to Run is not available for the running modes “On
Processing”, “On Save”, or “Background”.
• Issue Status Editable
Select to enable the “Issue Status” of an Issue associated with a
DRC failure to be edited in the design application or in Capital
Teamwork. Only enabled if you have the Set Release Levels user
permission.
Clear by default for all DRCs.
If selected, the DRC failure icons in the Design Rule Checks
Output Window display with a “pencil” overlay .
See also “Track and Override Design Rule Check Failures Using
Issues” on page 256.
Tip: If you multi-select checks (Shift+click / Ctrl+click) and
right-click to bulk change the Allowed to Run and Issue Status
Editable preferences, the current active status is determined by the
first check you select.

You can export and import projects in a Capital Compressed Format (CCF). This extends
Capital’s project transfer capabilities for extremely large projects by reducing the file size
required for the data and accelerating the export and import actions.
This format provides direct export and import of data without using Capital’s established XML
data formats.
When you import a project in Capital Compressed Format, the system does not perform design
validation checks automatically. However, it runs those checks when you open an imported
design in any Capital application.

December 2023
Exporting a Project in Capital Compressed Format
Note
To validate the data you can run the Submitted Index Validation Task using
CapitalDataMigrate.exe -submitindexingtasks flag. The process will validate all of the data
that was imported by the CCF. Use the - symbolsdeduplicated flag to compact any of the
symbols.
See the Capital Upgrade Guide for further information.
In addition, you can use Capital compressed format to export a corrupted project from the
database. The project data is exported in a .ccf file that can be sent directly to Siemens support
or to your own in-house support, who should forward it to Siemens support.
For instructions about exporting a project as a raw data dump, see “Exporting a Project in
Capital Compressed Format” on page 226.
Related Topics
Importing a Project in Capital Compressed Format

You can export a project from the database in Capital Compressed Format. This format
provides direct export and import of data without using Capital’s established XML data
formats.
Procedure
Choose an action:

Export the currently open 1. Press Space Bar and enter Export Current Project; the
project Export Project dialog box is displayed.
2. In the Files of Type field, select Capital Compressed Format
files (*.ccf).
3. Specify a location and name for the exported file.
4. Click the Export Project button; a progress bar displays
and disappears when the export is complete.

December 2023

Export a project that is 1. Press Space Bar and enter Select Project to Export; the
not open Select Project dialog box is displayed.
2. Select the project to export and click OK; the Export Project
dialog box is displayed.
3. In the Files of Type field, select Capital Compressed Format
files (*.ccf).
4. Specify a location and name for the exported file.
5. Click the Export Project button; a progress bar displays
and disappears when the export is complete.
Note
When a project export is started, a complete snapshot of the current state of the
project and all its associated data is taken, it is this project snapshot that is then
exported. This is to prevent inconsistencies in data due to project modifications being
made by other users during an export.
Results
The system saves the .ccf file at the specified location.

You can import a project that was exported in Capital Compressed Format from another
installation. This format provides direct export and import of data without using Capital’s
established XML data formats.
Prerequisites
• You must import any symbols required by the project into Capital Symbol Designer.
• You must import library components required by the project into Capital Component
Manager.
Procedure
1. Press Space Bar and enter Import; the Import dialog box is displayed.
2. Browse to the project's .ccf file to import.
3. Click the Import button.
Results
• If a project with the same name does not exist in the database already, the specified
project is imported into the database and now appears in the Project Browser Tree.

December 2023
• See the Capital Compressed Format for Projects topic for information about how the
system validates the data in these imported files.
Related Topics

December 2023
Designs
Designs
Any number of designs may be created within a project. As each design is created, it is listed in
the project's Designs folder in the Project Browser Tree.
Copying Designs From One Project to Another . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Migrating a Design from Capital Harness Classic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Comparing Objects and Their Properties in Design Revisions or Build Lists. . . . . . . . 241
Mass Design Revision and Effectivity Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Design Rule Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Design Rule Check Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Searching for a Design across all Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Importing Designs into a Project

You can import one or more designs in XML format from outside of your database into a
project.
You can do this either by specifying only the basic details for the imported designs using the
Import Designs to Project - Copying to Project Dialog Box or using the Import Designs to
Project Wizard - Copying to Project Wizard Dialog Box to specify advanced details.
Note
Style sets are not included in the export and import of designs so you must ensure that the
required style sets are available in your Capital installation. See “Importing Style Sets” in
This video shows how to use constraints when importing child harness designs.

December 2023
Prerequisites
• Design XML file is available for import.
Procedure
1. To access the Import dialog box:.
• In design applications, press Space Bar and enter Import Designs.
• In Capital Project Manager, click File > Import.
2. Locate and select the XML files containing the designs, and then click Import.
The Import Designs to Project - Copying to Project Dialog Box is displayed with the
designs listed.
3. Select the Target Project into which you are importing the designs.
4. To specify advanced details for the designs that will be created in the target project,
click the Advanced.
The Import Designs to Project Wizard - Copying to Project Wizard Dialog Box is
displayed. Skip to step 7.
5. To specify only basic details for the designs that will be created in the target project, edit
the following as required:
a. If you have configured the current project with rules containing Design Attributes
and Properties Constraints, you can automatically bulk update child harness Name,
Part Number, Revision and other attributes and properties.
i. Select the required rule from the Design Attribute Constraint dropdown list.
ii. Click Apply.
The constraint changes are applied to the selected child harnesses and are updated in
the table.
b. Otherwise, check and manually update the child harness details.
o Name
o Short Description
o Description
o Revision
o Release Level
o Abstraction
o Effectivity — Displayed only if Effectivity is enabled in the target project.
o Overwrite

December 2023
o Copy As Revision
o Copy Effectivity — Displayed only if Effectivity is enabled in the target project.
6. Click OK and skip to step 7.
7. On the Design Abstractions tab, map the design abstractions from the source designs
(designs being imported) to the design abstractions in the target project.
8. On the Design Details tab, specify the basic details for the designs that will be created in
the target project:
• Name
• Part Number (if importing a Capital Harness Designer design)
• Revision
• Short Description
• Description
• Release Level
• Design Abstraction
• Location
• Function
• Copy Associated Logic Designs (if importing a Capital Systems Integrator design)
• Copy Generated Wiring (if importing a Capital Systems Integrator design)
• Overwrite Revision
• Copy As Revision
9. If the imported designs contain any shared conductors, click the Shared Conductors
tab and specify the following options:
• Project Shared Conductor
• Copy Shared Conductor
10. If the imported designs contain shared pin lists, click the Shared Pin Association
Defaults tab to set the defaults for automatic shared pin association:
• Merge Restricted Pins
• Merge Reserved Pins
11. To manually associate source shared pin lists with shared pin lists in the target project,
click the Shared Pin Lists tab and specify the following settings:
• Associate Pin Lists

December 2023
Copying Designs From One Project to Another
• Associate Pins
• Pin Reservations
12. If you need to translate component codes (for example, color codes) and component part
numbers to match codes and components in your database, click the Translation tab
and specify the following options:
• Translate Codes (for example, color codes) in the imported data.
• Translate Parts in the imported data. Converts internal part numbers to customer or
supplier part numbers.
13. The Summary tab displays a summary of the options that you have selected in the
wizard. You can return to any of the tabs to edit settings.
14. Click Back to return to the Import Designs to Project/Copying to Project dialog box.
15. Click OK.
Results
• The target project is opened in the Browser tree and the imported designs are added
under the Designs node for that project.
• The system does not perform component library part assignment automatically during
the import so you must run a batch update of library parts on the imported designs. See
“Performing a Batch Update of Library Parts” on page 636 to ensure that the attributes
of the library parts used in the imported data match the attributes of the library parts in
your Capital component library.
Related Topics
Import Designs to Project Wizard - Copying to Project Wizard Dialog Box
Import Designs to Project - Copying to Project Dialog Box

You can use Copy Advanced functionality (in Capital Project Manager or design tools) to copy
one or more designs from one project to another. This saves time as you do not have to recreate
the design again.
See “Overview of Copying Designs Between Projects” in the Capital Project Manager User
Guide for more information about how the copied designs are treated in the database.

December 2023
This video shows how to use constraints when copying child harness designs.
Procedure
1. Depending on which application you are working in, access the Copy Advanced
functionality using one of the following methods:

Do this in Capital Project Either:
Manager • Right-click the Designs node for the source project in the
Project Browser Tree on the left of the Capital Project
Manager window and choose Copy Advanced.
• Right-click a design folder or selected designs under the
Designs node in the Project Browser Tree and choose Copy
> Advanced.
Do this in a design Press Space Bar and enter Copy Advanced.
application Note: You can select a design folder or specific designs in
the Project Browser Window at the top left of the application
window when doing this but do not have to.
The Select Designs to Copy Dialog Box displays. The Designs to Copy field displays
the designs that are currently selected to be copied. See the Designs to Copy field
description for details of how these designs are selected.
2. Specify the Target Project to which you want to copy the designs and click OK; the
Import Designs to Project - Copying to Project Dialog Box displays.
3. If you want to specify advanced details for the design that is created in the target project,
click the Advanced button; the Import Designs to Project Wizard - Copying to Project
Wizard Dialog Box displays. Skip to step 4.
If you want to specify only basic details for the design that is created in the target
project, edit the following as required:
• Name
• Short Description

December 2023
• Description
• Effectivity (only displayed if Effectivity is enabled in the target project.)
• Revision
• Release Level
• Abstraction
• Overwrite
• Copy As Revision
• Unfreeze new Shared Object
Note
If the source design has shared objects frozen, and target project has same shared
objects in unfrozen state, this option is disabled.
• Copy Effectivity (if copying the designs to a project that uses effectivity)
Note
If a design displays in red, this indicates that there is an issue to be resolved
before you can copy it to the target project. Hover over the design row in the
table and a tool tip displays the issue.
If you have specified only basic details, continue to Step 11.

4. If you have clicked the Advanced button and displayed the “Import Designs to Project
Wizard/Copying to Project Wizard” dialog box, map the design abstractions from the
source designs (designs being copied) to the design abstractions in the target project on
the Design Abstractions tab.
5. On the Design Details tab, specify the basic details for the designs that are created in the
target project:
a. If you have configured the current project with rules containing Design Attributes
and Properties Constraints, you can automatically bulk update child harness Name,
Part Number, Revision and other attributes and properties.
i. Select the required rule from the Design Attribute Constraint dropdown list.
ii. Click Apply.
The constraint changes are applied to the selected child harnesses and are updated in
the table.
b. Otherwise, check and manually update the child harness details.
o Name

December 2023
o Part Number (if copying a Capital Harness Designer design)

o Revision
o Short Description
o Description
o Release Level
o Design Abstraction
o Copy Associated Logic Designs (if copying a Capital Systems Integrator design)
o Copy Generated Wiring (if copying a Capital Systems Integrator design)
o Overwrite Revision
o Copy As Revision
6. If the copied design contains any shared conductors, specify the following for them on
the Shared Conductors tab:
• Project Shared Conductor
• Copy Shared Conductor
7. If the design being copied contains any shared pin lists, set the defaults for automatic
shared pin association on the Shared Pin Associations Defaults tab by specifying:
• Automatic Association Configuration Mode (either Merge Unrestricted Pins, or
Merge Reserved Pins)
8. If you want to manually associate source shared pin lists with shared pin lists in the
target project, specify the following on the Shared Pin Lists tab:
• Associate Pin Lists
• Associate Pins
• Pin Reservations
9. On the Summary tab, check that the listed import settings are correct. You can click any
tab to return to it and edit settings.
10. Click Back; the “Import Designs to Project Wizard/Copying to Project Wizard” dialog
box is closed.
11. Click OK on the “Import Designs to Project/Copying to Project” dialog box; a progress
bar displays. When the copy is complete:
• In Capital Project Manager: the target project is opened in the Project Browser Tree
on the left of the Capital Project Manager window. The copied designs are added
under the Designs node for that project.

December 2023
Migrating a Design from Capital Harness Classic
• In design applications: the target project does not open automatically but the copied
designs will be displayed in it when you next open it in an application and view the
Project Browser Window.
Migrating a Design from Capital Harness Classic

You can migrate, (import / transfer), designs from Progress or Oracle installations of Capital
Harness Classic into Oracle or Postgres installations of Capital, retaining all design content and
branch layout details.
Procedure
Full details can be found in the Migration of Designs from Capital Harness Classic topic in the
Capital Harness Designer User Guide.
Editing the Information for a Design

If the necessary permissions have been set for your user account in Capital Access Manager,
you can edit the information (such as design name, revision, abstraction) for a design in the
Capital Design Tools.
If you use advanced naming functionality, design properties may be included in the naming
compositions that are set up in Capital Project Manager. This means that the values that you
specify for design properties in this dialog box may influence the names that are generated. See
the Capital Project Manager help system for more information about setting up naming
compositions and see “Advanced Naming Functionality” on page 633 for more information
about applying advanced naming to objects in Capital Logic Designer.
Procedure
1. Right-click the name of the design in the Project Browser Window on the upper left of
the application window and select Edit from the pop-up menu that is displayed.
2. The Edit Design dialog box is displayed. You can edit the following attributes for the
design:
Note
The available attributes vary depending on the type of design.
• Name - the name of the design. If valid names for the object type have been created
in Capital Project Manager, you can select a name by clicking the ellipsis (...) button
to display the Name Selection dialog box.
Note
You can click the Properties button to display the Edit Design Properties Dialog
Box that allows you to add or delete properties for the design.

December 2023
• Part Number (displayed for Capital Harness Designer designs only, read-only in
Capital E/E Publisher) - a unique part number for the design.
• Revision - the revision for the design.
• Short Description - the short description for the design.
• Description - the long description for the design.
• Plan (displayed for Capital Systems Integrator designs only) - the Basic Plan or Pro
Product Plan associated with a Capital Systems Integrator design. See “Associating
a Basic Plan with a Design” or “Associating a Pro Product Plan with a Design” in the
Capital Systems Integrator User Guide.
• Release Level - the release level for the design. Select the release level from the
dropdown list and click the Change Release Levels of Designs icon ( ) to
transition to the next specified release level.
Note
Capital enforces the running of specific design rule checks during each transition
in the release cycle of a design. This is to ensure design content is correct and
verified, and to prevent the build up of multiple DRC failures towards the end of the
design process. You are prevented from transitioning to the next level in your release
cycle until the specified DRCs for that release level are passed. For further
information see “Enforcing Design Rule Checks During Release Level Transitions”
on page 253.
The release levels that you can assign to the design also depend on the permissions
that have been set for your user account in Capital Access Manager. See the Capital
Access Manager help system for more information about setting permissions for a
user account.
If the release level of a design is changed and saved in Capital Harness Designer, the
release level will be automatically be transferred when the design is opened in
Capital Harness Classic.
The release levels will be mapped between Capital Harness Classic and Capital
Harness Designer as follows:
Table 2-13. Release Level Mapping
Capital Harness Classic Capital Harness Designer
Draft Draft
Pending Checking
Released Released
Obsolete Obsolete

December 2023
• Abstraction (not displayed for Capital Harness Designer designs in Capital E/E
Publisher) - the abstraction level for the design.
• Domain - the domain level editing access for the design.
Note
Domain level access is enabled on a release level basis by the inclusion of the
‘Design Domain Changes’ behavior, for more information see “Release Level
Behaviors” in the Capital Project Manager User Guide.
For an overview of creating and using domains, see “Domains” in the Capital
Access Manager User Guide.
For information about assigning a project to a domain, see “Domain” in the Capital
For information about assigning designs to domains, see “Domains for Designs” in
• Applicable Derivatives. Only displays for Derivative Group Designs. Click the
ellipsis (...) button to the right of the field to open the “Select the derivatives to be
grouped” dialog box, to choose the subset of derivatives you want to include in
Derivative Group.
• Applicable Options (read-only for Capital Harness Designer designs in Capital E/E
Publisher) - the options that can be assigned to the design. Click the ellipsis (...)
button by the Applicable Options field to display the Applicable Options Dialog
Box.
• Applicable Modules (displayed for Capital Logic Designer designs only) -
functional Module Codes that are available to objects in the design can be assigned,
amended or removed. Click the ellipsis (...) button, next to the Applicable Modules
field, to display the Applicable Modules dialog box and select the required
Functional Module code(s).
Note
The Applicable Modules field will only display if you have selected the Modules
project preference. See “Project Preferences for Capital Logic Designer
Designs” on page 169.
• Applicable FM Codes (displayed in Capital Harness Designer Modular only) -

displays the Functional Module codes that have been assigned to this design. Click
the ellipsis (...) button to the right of the field, to open the Applicable Functional
Module Codes dialog box and edit the selection.
• Applicable Variant FM Codes (displayed in Capital Harness Designer Modular
only) - specify any Applicable Variant FM codes to be assigned to the design. Click

December 2023
the ellipsis (...) button next to the field, to display the Applicable Variant FM Codes
Dialog Box and select the required Variant Functional Module code(s). Optional.
These codes are used to control bundle length and object position variance. See
Variant Length Bundles and Component Positions. Optional.
• Applicable PM Codes (displayed in Capital Harness Designer Modular only) -
displays the Production Module codes that have been assigned to this design. Click
the ellipsis (...) button to the right of the field, to open the Applicable Production
Module Codes Dialog and edit the selection.
• Applicable Variant PM Codes (displayed in Capital Harness Designer Modular
only) - specify any Applicable Variant PM codes to be assigned to the design. Click
the ellipsis (...) button next to the field, to display the Applicable Variant PM Codes
Dialog Box and select the required Variant Functional Module code(s). Optional.
These codes are used to control bundle length and object position variance. See
Variant Length Bundles and Component Positions. Optional.
• Option (not displayed for Capital Harness Designer designs) - the option or option
expression to apply to the whole design. Click the ellipsis (...) button to display the
Edit Option Expression Dialog Box.
• Effectivity (read-only for Capital Harness Designer designs in Capital E/E
Publisher) - if using effectivity, click the ellipsis (...) button to the right of the field,
to open the Edit Effectivity Dialog Box and specify the effectivity ranges that apply
to the design. See “Effectivity” in the Capital Project Manager User Guide for an
overview of using effectivity.
• Harness Group - (displayed for Capital Harness Designer and Capital Harness
Designer Modular designs only) - use of Harness Groups allows auto-mapping of
valid objects when Synchronizing from a Capital Logic Designer Build List.
Harness Group names can be manually added or removed here. To select multiple
Harness Groups, click the ellipsis (...) button to the right of the field, to open the
Name Selection dialog box and select predefined names.
• Select Derivatives (displayed for Capital Harness Designer and Capital Harness
Designer Modular designs with derivatives only) - if the Release Level of the
Composite design has been changed, click the ellipsis (...) button to open the Change
Release Level of Child Designs dialog box, to select, or clear, any derivative designs
to which the Release Level change should also be applied.
• Select Functional Modules (displayed for Capital Harness Designer Modular
designs only) - if the Release Level of the Parent design has been changed, click the
ellipsis (...) button to open the Change Release Level of Child Designs dialog box, to
select, or clear, any child designs to which the Release Level change should also be
applied.

December 2023
Editing a Property for a Design
• Sealing Requirements (displayed in Capital Harness Designer and Capital Harness

Designer Modular only) - select the sealing options for specific component types on
the design:
o Seal Harness - check this box if you want to apply all of the below seal type
options to the connectors and splices when they are inserted into the design.
Optional.
o Seal Connectors - check this box if you want all of the connectors inserted into
the design to be sealed by default. Optional.
o Plug Connectors - check this box if you want all of the connectors inserted into
the design to be plugged by default. Optional.
o Insulate Splices - check this box if you want all of the splices inserted into the
design to be insulated by default. Optional.
• Modify Harness Details (displayed in Capital Harness Designer and Capital
Harness Designer Modular only) - click to open the Edit Harness Details dialog box
and enter additional manufacturing information for both internal and customer
consumption.
• Location (displayed for Capital Logic Designer and Capital Systems Modeler
functional designs only) - denotes the physical location in the product where the
design content resides.
• Function (displayed for Capital Logic Designer designs only) - denotes the function
that should be achieved in the product through the design.
3. Click the OK button to confirm the changes and to exit the dialog box.
Note
If you move a design to release level with “Frozen Shared Objects” behavior, all
shared objects in a design must be frozen. If any shared objects are not frozen, the
Freeze/Unfreeze Shared Objects dialog box is displayed automatically when you click
OK, to freeze them. See “Release Level” in the Capital Project Manager User Guide for
more information on Release Level behaviors.
Editing a Property for a Design

You can add, edit, and delete user-defined properties for a design when creating it or editing the
information for it.

December 2023
Comparing Objects and Their Properties in Design Revisions or Build Lists
Procedure
On a dialog box for editing or creating a design, click Properties to display the Edit Design
Properties Dialog Box.

Add a property 1. Click New to display the New Property Dialog
Box. Enter a name for the property and click OK.
The property is added to the Edit Design
Properties Dialog Box.
2. Specify the Value and Type for the property and
click OK.
Edit a property value Edit the Value and click OK.
Delete a property Click the property and click Delete.
Comparing Objects and Their Properties in Design

Revisions or Build Lists
You can compare a revision of a design with any revision of any design in a project. The
comparison looks at what objects appear on the design revisions and, optionally, at what
properties and attributes are on those objects. The results can be exported and saved as an
HTML file.
When you compare two build lists, design revisions are compared individually by mapping each
design revision from the first build list to one in the second build list based on Name.
Procedure
1. In a design application (such as Capital Logic Designer or Capital Harness Designer):
Open the diagram or plane for one of the design revisions to compare, press Space Bar
and enter Compare.
In Capital Project Manager:
In the Project Browser Tree, right-click one of the design revisions to compare and
select Compare.
The Design Revision - Build List Selection Dialog Box is displayed.
2. Select the project that contains the build lists or design to compare from the Projects
window.
3. Either:
• Select the two build lists to compare from the Build Lists window.

December 2023
• Select the other design revision to compare from the Design Revisions window.
4. Click OK.
The Compare Designs Dialog Box is displayed.
5. Configure the Comparison Type, Traverse, and Compare parameters to perform.
6. Click Compare.
Results
• The Differences window lists the results of the design comparison in a tree. The tree
displays each design revision and the objects being compared in each design. If an
object appears on a design revision or build list, the field in the column for that design
revision or build list is selected.
• If you are comparing properties and attributes on objects, these are listed under the
appropriate objects. If the property or attribute is set for the object in a design revision or
build list, the field in the column for that design revision or build list is selected.
Note
You can export and save the comparison results in an HTML file by clicking
Export.

December 2023
Mass Design Revision and Effectivity Changes

When managing change requirements, you may want to change the revision and effectivity of
multiple designs at one time. To do this you can use a flow using an engineering change order
(ECO), a flow using a build list, or a flow using designs that you select.
When making design changes in aerospace in particular, you commonly create an ECO to
describe the required changes, the impacted set of designs, and the target effectivity of the new
set of design revisions.
Alternatively, if you do not want to use an engineering change order, you can use a build list to
define a set of designs for which you want to create new revisions with specific effectivity. If
you do not want to use a build list, you can select specific designs yourself.
Using ECOs for Mass Revision and Effectivity Changes . . . . . . . . . . . . . . . . . . . . . . . . . 243

Using Build Lists for Mass Revision and Effectivity Changes. . . . . . . . . . . . . . . . . . . . . 244
Selecting Specific Designs for Mass Revision and Effectivity Changes . . . . . . . . . . . . . 245
Using ECOs for Mass Revision and Effectivity Changes

When making design changes in aerospace in particular, you commonly create an engineering
change order (ECO) to describe the required changes, the impacted set of designs, and the target
effectivity of the new set of design revisions.
Typically, you start with a set of released designs with a specific effectivity. These are the
designs that you want to change. At the end of the procedure you have a set of new design
revisions that implement a different effectivity.
Procedure
Create an engineering change order as instructed in “Creating an Engineering Change Order” on
page 439. When doing this, ensure that you perform the following steps.
a. On the Engineering Change Orders Dialog Box, specify the existing impacted
designs that require changes.
b. On the same dialog box, specify the effectivity that you want the new design
revisions to have. The system will propagate this automatically when it creates the
new revisions.
Caution
The system propagates effectivity to any new revisions only for Capital Logic
Designer and Capital Harness Designer designs.
c. The starting point designs typically have a released status, so you must create new
design revisions. Click the Manage Designs & Effectivity ( ) button above the
Impacted Designs table; the Manage Designs & Effectivity Dialog Box displays.

December 2023
Specify the revision and short description for each new design revision. For a
harness design, you can also edit the Part Number of a harness design if required.
d. On the Manage Designs & Effectivity dialog box, ensure the “Update ECO design
references” option is selected. When you click OK, the system will propagate the
new design revisions back to the Impacted Designs table on the Engineering Change
Orders dialog box.
Results
You have a new set of design revisions that implement a specific effectivity, and an engineering
change order that describes this.
Note
If you revise a composite design, the new design revision maintains a link to existing child
designs under the original composite.
Using Build Lists for Mass Revision and Effectivity

Changes
As an alternative to using an engineering change order, you can use a build list to define a set of
designs for which you want to create new revisions with specific effectivity.
Typically, you start with a set of released designs with a specific effectivity. These are the
designs that you want to change. At the end of the procedure you have a set of new design
revisions that implement a different effectivity.
Prerequisites
• You must have a build list that includes the designs that you want to update. See “Build
List” in the Capital Project Manager User Guide.
Procedure
1. Right-click a build list in the project browser window (in design applications) or in the
project browser tree (in Capital Project Manager), and choose Manage Designs &
Effectivity.
The Manage Designs & Effectivity Dialog Box displays. It lists the designs from the
build list.
2. In the Revise column, select the designs for which you want to create new revisions.
3. Specify the Revision and Short Description for each new design revision. For a harness
design, you can also edit the Part Number of a harness design if required.
4. Specify the effectivity that you want the new design revisions to have.

December 2023
Caution
5. Click OK.
A progress dialog box displays. This can take a couple of minutes.
Results
• Design revisions are created as specified with the effectivity entered.
Note
If you revise a composite design, the new design revision maintains a link to existing
child designs under the original composite.
• A Manage Designs & Effectivity Report displays. In design applications, this displays as
a tab in the output window at the bottom right of a design application window. In Capital
Project Manager this displays as a dialog box. It reports information regarding any
changes made to designs while the system created design revisions.
• The audit trail records such actions as Design created, Design revised, Logical
Effectivity added, and Harness Effectivity added.
Selecting Specific Designs for Mass Revision and

Effectivity Changes
As an alternative to using an engineering change order or a build list, you can select specific
designs for which you want to create new revisions with specific effectivity.
Typically, you start with a set of designs with a specific effectivity. These are the designs that
you want to change. At the end of the procedure you have a set of new design revisions that
implement a different effectivity.
Tip
When using this procedure, you do not have to create new design revisions. You can just
define new effectivity on the existing design revisions.
Procedure
1. In the project browser window in a design application, select the design revisions to edit,
right-click and select Manage Designs & Effectivity.
Note
You can select only design revisions of one design type to invoke this action. You
cannot select design folders and you cannot select designs of different types.

December 2023
2. The Manage Designs & Effectivity Dialog Box displays. It lists the designs that you
selected.
Note
You can add or remove designs by using the buttons above the table: and . At
this point you can add designs of different types.
Note
This is optional, and is not required if you want to change effectivity only. Skip to
step 5 if you want to change effectivity only.
5. Specify the effectivity that you want the new design revisions to have.
Caution
6. Click OK.
A progress dialog box displays. This can take a couple of minutes.
Results
• Design revisions are created as specified with the effectivity entered.
Note
If you revise a composite design, the new design revision maintains a link to existing
child designs under the original composite.
• A Manage Designs & Effectivity Report displays. In design applications, this displays as
a tab in the output window at the bottom right of a design application window. In Capital
Project Manager this displays as a dialog box. It reports information regarding any
changes made to designs while the system created design revisions.
• The audit trail records such actions as Design created, Design revised, Logical
Effectivity added, and Harness Effectivity added.

December 2023
Design Rule Checks
Design Rule Checks

You can use Design Rule Checks (DRCs) to check for problems with you designs.
Running Design Rule Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Running Design Rule Checks in Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Design Rule Checks Output Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
Design Browser Tree Expansion Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Running Modes for DRCs in Capital Systems Integrator . . . . . . . . . . . . . . . . . . . . . . . . 251
Enforcing Design Rule Checks During Release Level Transitions . . . . . . . . . . . . . . . . . 253
Track and Override Design Rule Check Failures Using Issues. . . . . . . . . . . . . . . . . . . . 256
Running Design Rule Checks

You can run design rule checks manually to identify errors in designs. You can check a single
design or, in the case of Capital Logic Designer, all designs in a build list.
Procedure
1. Press Space Bar and enter DRCs.
The Design Rule Checks Dialog Box is displayed.
2. Choose the design, build list, or SBOM to check.
3. (Optional) Enter a text string in the Filter field to refine the list of checks in the Design
Rule Check browser.
4. Choose the required checks.
5. (Optional) Click Reset to revert to the selections determined by the “Use Design Rule
Checks settings from previous run” project preference. See also “Project Preferences for
Design Release” on page 214.
6. Click Run.
Results
The identified errors, warnings, and information messages are displayed in a tabular form on the
Check tab in the Design Rule Checks Output Window.
Related Topics
Running Design Rule Checks in Background
Design Rule Check Descriptions

December 2023
Design Rule Checks
Running Design Rule Checks in Background

You can run design rule checks automatically in the background. When doing this, you cannot
select checks at the time of running them. The checks that are run are controlled by project
preferences.
See “Design Rule Check Descriptions” on page 261 for an explanation of the checks that can
run.
Procedure
Click the Design Rule Checks Toggle on the Status Bar at the bottom of the application:
Results
• The system runs the design rule checks that have been specified to run in background
mode in Project Preferences.
• The results of the design rule checks are listed on the Check tab of the Design Rule
Checks Output Window.
• The Design Rule Checks Toggle changes to show a square (stop icon) and also indicates
whether the checks have currently found failures or not:
• The checks run whenever changes are made to the design to which the currently active
diagram belongs; the Check tab of the Design Rule Checks Output Window and Design
Rule Checks Toggle update dynamically to reflect the latest results.
Related Topics
Running Design Rule Checks
Design Rule Checks Output Window

The Output Window is displayed at the bottom of the application and displays various tabs
depending on the actions performed in a design. When you run design rule checks, the Check
tab displays the results in a tabular form.

December 2023
Design Rule Checks
The table includes columns in which you can filter the contents by selecting an item from the
dropdown list at the top. You can sort the contents of a column by clicking the column header.
The columns are:
Table 2-14. Design Rule Checks Output Window
Field Description
Opens the Design Rule Checks Dialog Box without accessing the project
preferences.
Saves the contents of the table as a comma-separated values (CSV) file.
Manually creates an issue for the selected rows.
Refreshes the Issues associated with DRC failures if the Issues are updated
in Capital Teamwork.
Opens help information.
Severity Whether the result is an error ( ), a warning ( ), or information message

( ).
Issue ID Unique identifier of the Issue created to manage DRC failures if you have
configured the project to track and override DRC failures.
Click the issue ID hyperlink to open the Issue in Capital Teamwork.
See also “Issues Overview” in the Capital Teamwork User Guide.
You can click the Create Issue icon ( ) to manually create an issue for
DRC failures that are not configured to create an Issue automatically.
Issue Status One of the Release Level names defined on the Issues tab in the Edit
Release Levels dialog box in Capital Project Manager, which can be
configured with the "Issue Opened", "Issue Closed", or "Issue Overridden"
release level behaviors. See also “Release Level Behaviors” in the Capital
If the DRC is configured as editable (“Issue Status Editable” specified in
the project preferences Checks node) its icon displays with a pencil
graphic overlay . Otherwise, the Issue Status dropdown list is
inactive.
You can click the Issue Status dropdown lists to change the release level of
the DRC to a status permitted by the configured Release Level
Transitions.
Note: To bulk change the issue status, multi-select the required rows
(Shift+click / Ctrl+click), and then right-click to open the “Set Issue
Status To” popup. If you have selected multiple rows with a different
current issue status, the system offers a choice of common statuses only.
Issues are automatically assigned the Release Level name which includes
the “Issue Opened” behavior.

December 2023
Design Rule Checks
Table 2-14. Design Rule Checks Output Window (cont.)

Field Description
Message Detailed message about what the check has identified. You can click an
object in the message to jump to that object in the diagram.
Note: When you jump to an object, the Design Browser Tree
displayed on a tab at the bottom left of the application also expands to
display and highlight that object. See “Design Browser Tree Expansion
Limitations” on page 250 for limitations with regards to the expansion and
highlighting of the Design Browser Tree.
Category The category of design rule check to which the particular design rule
check belongs (for example Connectivity or Naming).
Check The specific design rule check that has identified something in the design.
Design/Build The design or build list in which the check has identified something.
List
Object The specific object for which the check has identified something.
Usage Notes
You can click the column header dropdown lists to filter the list of DRC failures.
Related Topics
Track and Override Design Rule Check Failures Using Issues
Design Browser Tree Expansion Limitations

You can click an object in a message for a check in the Design Rule Checks Output Window
(Check tab in Output Window) or Design Assistant to jump to that object in the diagram. When
you jump to an object, the Design Browser Tree displayed on a tab at the bottom left of the
application also expands to display and highlight that object. There are limitations with regard
to this expansion and highlighting.
• In Capital Systems Integrator, you must:
o Set all design levels active.
o Perform the Expand All action on the Design Browser Tree.
o Switch the Toggle Splice Visibility mode to ON.

December 2023
Design Rule Checks
Note
These actions are necessary so that:
• Toggle Splice Visibility works and a splice can be highlighted in the tree when
selected from a check hyperlink.
• All the objects are present in the tree and the system can scroll to any object.
• In Capital Harness Designer, if you click a cavity in a message the system highlights the
connector in the tree.
• In Capital Logic Designer, if you click a plug, multicore, or wire object, the system
highlights all the objects under it (pins, wires, and so on) in the tree.
• If you click a wire or net that is part of a highway, the system highlights the highway in
the tree.
• If you click an object placed on the diagram, the system highlights it the tree. Ensure
objects are placed before trying to highlight them.
• In Capital Harness Designer and Capital Harness Designer Modular, the system can
highlight only full scale bundles in the tree.
• In the Design Assistant, if you click a Group1 or Group2 object the system highlights
the wires and signals that are part of that group.
• The system cannot highlight fixtures in the tree.
Running Modes for DRCs in Capital Systems Integrator

There are various running modes for design rule checks (DRCs) in Capital Systems Integrator.
Table 2-15. DRC Running Modes for Capital Systems Integrator

Running Mode Description
Name
Manual When you run design rule checks manually in a design application by
pressing Space Bar and entering DRCs, and selecting the checks to
run. The Check tab of the output window displays the results.
Background When design rule checks are run automatically in the background in a
design application. Background runs occur when the background
mode has been activated and after changes have been made to objects
in the design to which the currently active diagram belongs. The
You should set as small a number as possible of checks to run in the
background as they will use memory.

December 2023
Design Rule Checks
Table 2-15. DRC Running Modes for Capital Systems Integrator (cont.)
Running Mode Description
Name
On Save When design rule checks are run automatically on saving a diagram
in a design application. If there are any failures of severity Error, the
save is canceled and the Check tab of the Output Window displays
the failures. By default, no design rule checks are run for the On Save
mode. If you want checks to run when you save, you must specify
preferences for this mode.
You should set as small a number as possible of checks to run in the
background as they will use memory.
On Release When design rule checks are run automatically on releasing a
diagram. The Check tab of the output window displays the results.
For further details of this action, see ““Enforcing Design Rule Checks
During Release Level Transitions” on page 253” for further details of
this action.
Design Assistant When design rule checks are run from the Design Assistant. If there
are any failures, the Design Assistant displays them.
For further details of this action from the Design Assistant, see
“Running Design Rule Checks in the Design Assistant” in the Capital
Systems Integrator User Guide.
Harness Transfer When a harness is imported into a design using Capital Systems
Integrator Harness Exchange functionality.
For further details of this functionality, see “Capital Systems
Integrator Harness Exchange” in the Capital Systems Integrator User
Guide.
Level Assignment When design rule checks are run automatically during the assignment
of wires from abstract harness levels to physical harness levels
(Assign Levels action). By default, this running mode contains only
the “Redundant wires” DRC but you can add others.
For a description of the “Redundant wires” DRC and others, see
“Design Rule Checks Applicable to Capital Systems Integrator
Designs” on page 262.
For a description of the Assign Levels action, see “Assigning Wires
from Abstract Harness Levels to Physical Harness Levels” in the

December 2023
Design Rule Checks
Enforcing Design Rule Checks During Release Level

Transitions
Capital enforces the running of specific design rule checks (DRCs) during each transition in the
release cycle of a design. This is to ensure design content is correct and verified, and to prevent
the build up of multiple DRC failures towards the end of the design process.
Separate specific sets of design rule checks can be enforced at each release level. For example,
if you have release levels set for your designs of New, In-Work1, In-Work 2 and Released, your
design must pass one set of DRCs to transition from New to In-Work 1. It must then pass a
different set of DRCs to transition from In-Work 1 to In-Work 2 and so on. In essence, you are
prevented from transitioning to the next level in your release cycle until the specified DRCs for
that release level are passed.
The DRCs that are to be applied to each release level are specified using the Project Preferences
for the design application you are using. The appropriate preferences are displayed when you
select the Checks node for an application in the Project Preferences Dialog Box.
Tip
To save time when creating new release levels for your designs you can use the Release
Level Template field (also available on the Checks node) to set up the DRCs that must be
passed for each of your designated release levels. For example, each release level of the type
Pending automatically copies the DRCs specified on the Pending Release Levels template.
Release levels created this way are still manually configurable. Additionally, the use of the
template is optional.
This action is available across the Capital toolset, including Capital Logic Designer, Capital
Wiring Integrator, Capital Systems Integrator, Capital Systems Modeler, Capital Systems
Architect, Capital Electrical Publisher, Capital Harness Designer, Capital Harness Designer
Modular, Capital Harness Process Designer, Capital Work Instruction Publisher, and Capital
Harness Costing.
Note
Existing and legacy projects that previously relied on the Enforce Design Rule Checks on
release of designs project preference are automatically updated to use the new enforcing
DRC transitions behavior.
The type of design that you can release is dependent upon the application that you use (that is,
only Capital Systems Integrator designs can be released in the Capital Systems Integrator
application, and so on).
You can run the release action on:
• a single design

December 2023
Design Rule Checks
• a set of selected designs (including complete design families in composite/derivative or

modular parent/child scenarios)
If you are using Web Services, you can release designs and send an automatic notification to the
Web Services component. The Web Services mechanism automatically uses the enforcing DRC
transitions behavior.
Prerequisites
• In the appropriate design application, open the project that contains the designs.
• The designs to be released must have a current release level setting that can be
transitioned to the next available release level type.
• The design rule checks for the release level transition to be run on the designs must have
been set in the Project Preferences for the design application (the appropriate
preferences are displayed when you select the Checks node for an application in the
Project Preferences Dialog Box).
Procedure
1. In the appropriate design application for the type of design that you want to transition,
press Space Bar and enter Release, or click the button on the Workflow tab
of the ribbon. The Release Designs Dialog Box is displayed.
Tip
In cases where no transition is defined for a Release Level, the Change Release
Level button still allows you to open the Release Designs Dialog Box and transition
other designs if required.
2. Select the designs to transition to the next release level.
Note
If you have a design open in the diagram window, it is selected automatically. If you
have selected designs in the Project Browser Window on the top left of the
application window before initiating this action, those designs are selected
automatically.
3. Specify the Release Level to apply to the designs.

4. Specify whether you want to “Annotate results” and “Treat warnings as errors” for the
design rule checks.

December 2023
Design Rule Checks
Note
When you select to annotate results, the release process is slower if the diagrams
involved are not open in the design application. This is because the application must
open and close each diagram. Project preferences can also be used to set whether the
Annotate results box is selected by default (Annotate by Default) and to customize the
wording of the annotation that is added to the diagram (Annotation Template).
5. Click OK; a progress bar is displayed while the design rule checks run.
Results
• If there are no failures, the release level for the designs is changed and they are saved,
including any modifications such as annotations.
• If the release level transition fails a message is displayed. You must ensure the affected
design can pass all specified DRCs before you can transition it to the another release
level.
A summary of the release transition process is displayed in the Output Window at the
bottom of the application. This indicates whether any design rule checks failed for
designs. The Check tab of the Output Window gives details of the design rule checks
that have failed.
• For a Capital Logic Designer design, the summary also lists any shared objects that are
frozen during the release process.
Related Topics
Designs

December 2023
Design Rule Checks
Track and Override Design Rule Check Failures Using

Issues
Design Rule Checks (DRCs) are used to identify violations in the integrity of the design;
however, in certain scenarios where DRC failures are manually checked and passed but not
fixed in the design, the messages will continue to be reported with each DRC run.
To avoid displaying these violations in the Design Rule Checks Output Window without fixing
the design, you can use Issues to choose which violations to “override” while tracking the
current and overridden DRC failures.
Note
The Capital Team Collaborator license must be assigned to your user account in the Capital
software to access the Issues workflow. See Licensing Options in the Capital Teamwork
User Guide.
Issues Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Configuring the Project to Track and Override DRCs Using Issues . . . . . . . . . . . . . . . 257
Using Issues in the Design Rule Checks Output Window . . . . . . . . . . . . . . . . . . . . . . . . 258
Issues Overview
The system uses an Issues container associated with the DRC failures, which you can configure
to track and override specific DRC failures to understand the quantity and status of violations in
the design.
Figure 2-1. DRC Failures and Issues Flow

December 2023
Design Rule Checks
You can override an Issue on a DRC failure in the Design Rule Checks Output Window to
ignore the violation and prevent it from displaying again in the next DRC run.
You can also manage Issues in the Capital Teamwork web application to assign Issues to other
users and track the Issues to verify which DRC failures have been fixed or overridden using the
Issues workflow.
Configuring the Project to Track and Override DRCs Using Issues

Before you can use Issues to understand the validity of the design and override Design Rule
Check (DRC) failures, the project must be configured.
System Administrators must use this procedure to configure the following preferences and
permissions:
• Configure the Issue statuses to model the life cycle of Issues associated with designs.
• Specify which DRCs can be overridden if the DRC fails.
• Configure the Issue auto-create options.
• Specify the Issues user permissions for each user.
Procedure
1. From Capital Project Manager, open a project.
2. Double-click Release Levels to open the Edit Release Levels dialog box.
3. Click the Issues tab.
The release level “Open” is created for Issues by default.
4. Click New to create the following release levels:
• Overridden
• Closed
5. Configure the following options to define the status of the Issue in the life cycle of the
design:
• Type
• Behaviors
• Transitions
See also “Creating a Release Level for a Project” in the Capital Project Manager User
Guide.

December 2023
Design Rule Checks
6. Double-click Preferences to open the Preferences dialog box.

7. Expand the product name of the required Capital design tool.
8. Click the Checks node.
9. Select one or more DRCs, and then right-click and select Issue Status Editable to
enable the DRC failure to be manually overridden in the Design Rule Checks Output
Window.
See also “Design Rule Checks browser” in the “Project Preferences - Checks Node” on
page 220.
10. Click the Check node and configure the automatic creation and overridden Issues
preferences to control which DRC failures to track.
See also “Issues” in the “Project Preferences for Design Release” on page 214.
11. From Capital Access Manager, edit each user account.
The Edit User Account Dialog Box is displayed.
12. Click the Permissions tab.
13. Specify the following Edit Project > Issues permissions to control the level of access
for each user:
• Create
• Delete
• Edit
• Set Release Levels
See also “Edit Project User Permissions” in the Capital Access Manager User Guide.
Using Issues in the Design Rule Checks Output Window

You can manually change the release levels of Issues to close or override (ignore) Design Rule
Check (DRC) failures without fixing the violation in the design.
Note
The status changes of Issues associated with DRCs in the project are logged in the Audit
Trail and can be filtered and viewed using the Audit Trail Events for Issues.

• You cannot change the release levels of DRC failures manually if the “Issue Status
Editable” option on the DRC is not selected in the Project Preferences - Checks Node.

December 2023
Design Rule Checks
Prerequisites
• An Issue has been created either automatically or manually for the DRC failure. If
automatically, the “Auto-create Issues for DRC messages” project preference is selected
for at least one of the DRC failure types. See also “Project Preferences for Design
Release” on page 214.
• The “Issue Status Editable” option on the DRCs you want to override is enabled.
See also “Design Rule Checks browser” in the “Project Preferences - Checks Node” on
page 220.
• You have the user permissions to “Set Release Levels” for DRC failures. See also “Edit
Project User Permissions” in the Capital Access Manager User Guide.
Procedure
1. From the Workflow ribbon, click the DRCs action ( ) to open the Design Rule
Checks Dialog Box and run the DRCs on the design.
The following objects are displayed in the Design Rule Checks Output Window:
• Issues are created automatically for all the DRC failures.
Tip
You can select the “Auto-create Issues only for DRCs marked Issue Status
Editable” project preference to create Issues for editable DRCs only and reduce
the quantity of Issues to manage.
• The editable DRC failures are displayed with a pencil graphic overlay .
• The release levels of the Issues are listed in the Issue Status column.
• The Issue ID hyperlinks are listed in the Issue ID column.
2. To close or override a DRC failure:
• Click the Issue Status dropdown list for the editable DRC failure and choose a
release level.
• Right-click one or more DRC failure rows and choose a release level to set the Issue
Status to.

December 2023
Design Rule Checks
Tip
You can click the Issue Status header dropdown list and filter out Overridden Issues.
This way if you override the Issue, the DRC failure is hidden the next time you run
the DRCs. To show the DRC failures specified as overridden, you can click the Issue
Status header dropdown and filter to show Overridden Issues. After rerunning the
DRCs, you can click the Issue Status header dropdown list and select Overridden to
show the DRC failures that are specified as overridden.
You can also configure the Project Preferences for Design Release to ignore DRC
failures that have Overridden Issues when you save or release the design.
3. Click the Issue ID hyperlink to open and manage an Issue in Capital Teamwork.
4. Select one or more DRC failure rows and click the Create Issue icon ( ) to create
Issues manually for DRC failure types that are not configured to create an Issue
automatically.
5. Click the Open DRCs dialog icon ( ) to rerun the DRCs if you fix or override the
DRC failures in the design.
6. Click the Refresh Issues icon ( ) to refresh the Issues associated with DRC failures if
the Issues are updated in Capital Teamwork.

December 2023

You can use Design Rule Checks to check for specific errors in designs in each design
application. Descriptions of the checks are available.
If you are using web services with your Capital applications, design and send an automatic
notification to the web services component. When you release a design this way, it is
automatically checked for design errors using the Design Rule Checks functionality.
This guide contains lists of available design rule checks for various applications. However,
some specific design application guides also contain relevant sections. For Capital Systems
Architect, see Design Rule Checks for Platform Designs in the Capital Systems Architect User
Guide. For Capital Systems Modeler, see Design Rule Check Descriptions in the Capital
Systems Modeler User Guide.
Design Rule Checks Applicable to Capital Systems Integrator Designs . . . . . . . . . . . . 262

Design Rule Checks Applicable to Capital Logic Designer Designs . . . . . . . . . . . . . . . . 307
Design Rule Checks Applicable to Capital Harness Designer and Capital Harness Designer
Modular Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Design Rule Checks Applicable to Manufacturing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Design Rule Checks Applicable to Capital Wiring Integrator Designs . . . . . . . . . . . . . 404

December 2023
Design Rule Checks Applicable to Capital Systems

Integrator Designs
There are specific design rule checks that you run while editing a design in Capital Systems
Integrator design.
See the following topics for descriptions of the available checks.
Capital Systems Integrator - Appearance DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Capital Systems Integrator - Connectivity DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Capital Systems Integrator - Consistency DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Capital Systems Integrator - Design Assistant DRCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Capital Systems Integrator - Integrator Rules DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . 281
Capital Systems Integrator - Library Consistency DRCs . . . . . . . . . . . . . . . . . . . . . . . . 295
Capital Systems Integrator - Naming DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305
Capital Systems Integrator - Appearance DRCs

There are particular design rule checks related to appearance that you can run for a Capital
Systems Integrator design.
No translation for text

Identifies where a translatable term has been used but no translation exists for the active
language so the quick code is displayed or where a translatable term has been entered as free
text and has no link to the language database.
Messages Variables
Unable to render border text ''''{0}'''' in current {0} - Text
language. Please update the language {1} - Language code
dictionary database for language ''''{1}''''
Unable to render text at ''''{0}'''' in current {0} - Text
Text cannot be shown or printed in chosen font

Identifies diagram text that cannot be rendered in the font applied to it. For example, Chinese
text must have a font that supports UNICODE so this check identifies Chinese text entered in a
non-UNICODE font.

December 2023
Messages Variables
Unable to render/print border text ''''{0}'''' {0} - Text
using Font ''''{1}'''' {1} - Font type
Unable to render/print text ''''{0}'''' at {1} using {0} - Text
Font ''''{2}'''' {1} - Co-ordinate points
{2} - Font type
Unlocked print regions

Identifies and reports on print regions on the diagram that are not locked in position.
Messages Variables
Print Region {1} is in an unlocked state {0} - Print region name
Capital Systems Integrator - Connectivity DRCs

There are particular design rule checks related to connectivity that you can run for a Capital
Empty physical multicore

Identifies multicores that do not contain any wires (all harness levels checked).
Messages Variables
Multicore {1} in Harness {2} does not contain {1} - Multicore name
any Wires on any Harness Level {2} - Harness name
Incomplete wiring in vehicle configuration

Checks that all wiring connectivity is complete in the selected vehicle configuration and reports
instances that are not.
Messages Variables
Wiring connectivity in {0} is not complete {0} - Vehicle configuration
Inline cavity signal mismatch

Identifies mismatched and unmated signals in inline pairs. If connector refinement has been
used, this check identifies whether the signals mapped to mated pins on the specialized
connectors are different.

December 2023
Messages Variables
Inline cavity {0} on Connector {1} has a {0} - Inline cavity name
mismatched signal {2} with the mated cavity {1} - Connector name
{3} on connector {4} which is mapped to {5}.
{2} - Signal name
{3} - Cavity name
{4} - Connector name
{5} - Signal name for the mated cavity
Inline cavity {0} on Connector {1} has no {0} - Inline cavity name
mated cavity. {1} - Connector name
Inline half {0} has no mate {0} - Inline half name
Multicore wires follow different paths

Identifies wires in a multicore that follow different paths.
Messages Variables
The wires in multicore {0} do not follow the {0} - Multicore name
same bundle path, eg {1} {1} - List of wires in the multicore which
follow different paths
Signal wire mismatch at cavity

Identifies virtual connector cavities that have a wire from the wrong signal connected. If a wire
terminates at a cavity from a signal that is not mapped to the cavity, this is an error. The signal
of the wire must share a common ancestor with at least one of the signals mapped to the cavity.
Messages Variables
Signal of {1} ({2}) does not match the mapped {1} - Wire name
signals of connected cavity : {3}:{0} {2} - Signal name
{3}:{0} - Connector and cavity
Signal of {1} ({2}) does not match the mapped {1} - Wire name
signals of connected Backshell Termination : {2} - Signal name
{3}:{4}:{0}
{3}:{4}:{0} - Connector, backshell and
termination
There were {0} Cavities with mismatched {0} - Number
Wires and Signal

December 2023
Unconnected wire
Identifies wires that are unconnected at one or both ends. Also reports the signal name carried
by the wire.
Messages Variables
Wire {1} in Signal {2} is not connected at {1} - Wire name
both ends {2} - Signal name
Unterminated bundle
Identifies bundles that are unconnected at one or both ends.
Messages Variables
Bundle {0} on Harness {2} has the same start {0} - Bundle name
and end node at {3} {2} - Harness name
{3} - X,Y coordinate.
Bundle {0} on Harness {2} has an {0} - Bundle name
unconnected end at {3} {2} - Harness name
{3} - X,Y coordinate.
Wiring with no harness level

Identifies wires and splices that have no harness level assigned.
Messages Variables
Wire {1} has no Harness Levels {1} - Wire name
Wire {1} has no Base Harness {1} - Wire name
Wire {0} has no associated Signal {0} - Wire name
Empty bundle
Identifies bundles that do not contain wires (all harness levels checked).
Messages Variables
Bundle {1} in Harness {2} does not contain {1} - Bundle name
Wires on any Harness Level {2} - Harness name
Sections of Bundle {1} in Harness {2} do not {1} - Bundle name
contain Wires on any Harness Level {2} - Harness name

December 2023
Inline wiring option expression

Detects incorrect option expressions at inline cavities having multiple wires, and reports
violations if the resultant option expression on multiple wires (which is an “OR'ed” expression
on individual wires) terminating at mated cavities of both sides of the inline connector does not
match.
Multiple signals mapped to cavity

Identifies slot connector or interface connector cavities to which incompatible signals are
mapped (that is, they do not share a common ancestor or parent signal).
Messages Variables
There were {0} Cavities mapped to multiple {0} - Number
Signals
Signals {1} and {2} are mapped to the same {1} and {2} - Signal names
interface connector cavity {3}:{0} {3}:{0} - Interface connector and cavity
connector cavity {3}:{0} {3}:{0} - Connector and cavity
cavity {3}:{0} {3}:{0} - Connector and cavity
Backshell Termination {3}:{0} {3}:{0} - Backshell and backshell termination
Obsolete wires
Identifies obsolete wiring that can occur as a result of unplacing or uncombining devices. You
can delete this obsolete wiring by running the Delete Obsolete Wiring action.
Messages Variables
Signal {0} is not required at slot {1}, {0} - Signal name
connector {2} cavity {3} {1} - Slot name
{3} - Cavity name
Signal {0} is not required at slot {1}, {0} - Signal name
connector {2} {1} - Slot name
Signal {0} is not required at connector {1}, {0} - Signal name
cavity {2} {1} - Connector name
{2} - Cavity name

December 2023
Messages Variables
Signal {0} is not required at hole {1} {1} - Signal name
{2} - Hole name
The following wires on signal {0} are {0} - Signal name
obsolete: {1} {1} - Wire names
Redundant abstract wires

Identifies duplicate paths between any two pins or cavities in the abstract wiring for a signal.
This DRC checks the paths of wiring by considering option expressions on bundles and device
pins. It ignores:
• All harness levels and option expressions on the wiring.

• Paths that have bundle or device pin option expressions that cannot co-exist.
Messages Variables
Wiring in signal {0} between pins {1}:{2} and {0} - Signal name
{1}:{2} is redundant: Path1 {3} {1} - Object name
{2} - Pin name
{3} - Wire name. There can be multiple paths.
Redundant wires
Identifies where more than one wiring path exists between two pins or cavities and both paths
are active on the same physical harness level. The DRC only processes physical harness levels
and ignores abstract harness levels. Each path might consist of a single wire, or multiple wires
and splices (including center-strip splices). The cavities could be on a slot connector, ring
terminal, inline, or interface connector. The pins could be on a splice, or a device connected
directly by a hole.
This DRC ignores:
• Harnesses with no physical harness levels. An information message reports this when
the DRC is run.
• Harnesses with no wiring (such as a dummy harness for an unconnected slot connector).
No message displays for this.
• Shields and pigtails. This is because they are likely to form loops on a single level (for
example, with a multi-termination or combined pigtail at each end). It identifies issues
with multicores by processing the innercores.

December 2023
Messages Variables
Wiring in signal {0} between pins {1} and {2} {0} - Signal name
is redundant in level {3} Path1: {4} {1} and {2} - Pin names
{3} - A single harness level
{4} - A list of wires and splices. There can be
multiple paths.
Wiring in signal {0} between pins {1} and {2} {0} - Signal name
is redundant in levels {3} Path1: {4} {1} and {2} - Pin names
{3} - A list of harness levels
{4} - A list of wires and splices. There can be
multiple paths.
Some harnesses have no physical harness {0} - List of harness names
levels, so the DRC was not run on the
following:{0}
Two-wire splice
Identifies splices that connect just two wires in one or more harness levels. This issue will only
be reported if a bypass wire could be created during synthesis.
Messages Variables
Splice {0} can be bypassed in level {1} by {0} - Splice name
replacing wires {2} and {3} with a single wire {1}- Harness level
{2} and {3} - Wire names
Splice {0} is connected to only one wire {1} in {0} - Splice name
level {2} {1}- Wire name
{2} - Harness level
Wires with negated options

Identifies wires with negated options (!option). Reports such statements as 'Wire WIRE25 has
negated options A'. This check is relevant to functionality for ensuring the giveaway of negated
options. See “Option Expressions for Negated Options” in the Capital Systems Integrator User
Guide.
Messages Variables
Wire {0} has negated options {0} - Wire name

December 2023
Capital Systems Integrator - Consistency DRCs

There are particular design rule checks related to consistency that you can run for a Capital
Constraint that breaks rule hierarchy

Identifies constraints which have been added to an object to which the constraint does not have
any affect. For example, a placement constraint added to a bundle.
Messages Variables
{0} {1} contains inapplicable constraint ''{2}'' {0}- Object type (for example, slot, bundle)
{1} - Object name
{2} - Name of a constraint template
{0} slot {2} contains ground constraint ''{3}'' {0} - Slot type - equipment or junction box
{2} - Slot name
{0} slot {2} contains junctionbox constraint {0} - Slot type - equipment or ground
''{3}'' {2} - Slot name
Slot connector {1} on {2} slot {4} contains {1} - Slot connector name
ground constraint ''{5}'' {2} - Slot type - equipment or junction box
{4} - Slot name
Device pin not connected to a device connector

Performs the same checks as the “Mismatched device footprint” design rule check.
Messages Variables
Functional Device {0} in Slot {1} has Pins not {0} - Functional device name
connected to any Device Connector Pin {1} - Slot name
Inconsistent module code

Identifies wires with a module code which is different from other wires with the same option
expression in the same harness.

December 2023
Messages Variables
Wire {1} with Option Expression {2} has a {1} - Wire name
Module Code {3} inconsistent with Wire {5} {2} - Option expression
in harness {6}
{3} - Module code
{5} - Wire name
{6} - Harness name
Wire {1} with Option Expression {2} has a {1} - Wire name
Module Code {3} inconsistent with Wire {5} {2} - Option expression
and {6} other objects in harness {7}
{3} - Module code
{5} - Wire name
{6} - Number
{7} - Harness name
Wire {1} and {2} other objects with Option {1} - Wire name
Expression {3} have a Module Code {4} {2} - Number
inconsistent with Wire {6} and {7} other
objects in harness {8} {3} - Option expression
{4} - Module code
{6} - Wire name
{7} - Number
{8} - Harness name
Inconsistent option-based variance

Identifies wires (from composite wiring synthesis or modular wiring synthesis) whose attributes
do not match the option-specific values defined for their source net as displayed on the Variance
tab of the Edit Properties facilities for signals.
Messages Variables
Cannot evaluate option variance because there
are no configurations defined.
Merged signal {0} resulted in a merged {0} - Signal name
Variance table with conflicting values for {2} - Attibute or property name
attribute/property {2}. Default value will be
used.
Error in Variance table of net {1} for attribute/ {1} - Net name
property {3} parsing option expression ''{4}'' {3} - Attibute or property name
{4} - Option expression

December 2023
Messages Variables
Ambiguous result from Variance table of net {1} - Net name
{1} for attribute/property {3}. Option {3} - Attibute or property name
expressions ''{4}'' and ''{5}'' are both active in
Harness Level {6}. Default value will be used. {4} and {5} - Option expression
{6} - Harness level name
Variance table with conflicting values for {2} - Attibute or property name
attribute/property {2} for Harness Level {3}.
Default value will be used. {3} - Harness level name
No result from Variance table of net {1} for {1} - Net name
attribute/property {3}. No option expression {3} - Attibute or property name
match for Harness Level {4}. Default value
will be used. {4} - Harness level name
No result from merged Variance table on {0} - Signal name
signal {0} for attribute/property {2}. No {2} - Attibute or property name
option expression match for Harness Level
{3}. Default value will be used. {3} - Harness level name
variance table with conflicting values for {4} - Attibute or property name
attribute/property {4} in abstract configuration
{1}. Default value will be used. {1} - Configuration name
Error in variance table of net {3} for attribute/ {3} - Net name
property {5} parsing option expression "{6}" {5} - Attibute or property name
in abstract configuration {1}
{6} and {7} - Option expression
{1} - Configuration name
Ambiguous result from variance table of net {3} - Net name
{3} for attribute/property {5}. Option {5} - Attibute or property name
expressions "{6}" and "{7}" are both active in
abstract configuration {1}. Default value will {6} and {7} - Option expression
be used. {1} - Configuration name
variance table with conflicting values for {3} - Attibute or property name
attribute/property {3} in abstract configuration
No result from variance table of net {3} for {3} - Net name
attribute/property {5}. No option expressions {5} - Attibute or property name
match in abstract configuration {1}. Default
value will be used. {1} - Configuration name

December 2023
Messages Variables
No result from merged variance table on signal {2} - Signal name
{2} for attribute/property {4}. No option {4} - Attibute or property name
expression match in abstract configuration
Inconsistent options between plan and build list

A design can be associated with both a Capital Logic Designer build list and a pro product plan.
This check identifies when options in the associated build list and pro product plan do not
match. See “Creating a Logic Build List from a Pro Product Plan” in the Capital Systems
Integrator User Guide for further information about the related process. This check works only
on the build list and the plan that are associated with the Capital Systems Integrator design from
which it is launched.
Messages Variables
Plan {0} references option {1}, which is not {0} - Plan name
used in build list {2} {1} - Option name
{2} - Build list name
Build list {0} references option {1}, which is {0} - Build list name
not used in plan {2} {1} - Option name
{2} - Plan name
Inconsistent refined connector signal mapping

Identifies wires that have been incorrectly mapped to a refined connector so that a wire has
more than two active connections. This may be because:
• Multiple specialized pins have been mapped with the same expression and the same
signal to the same generalized cavity.
• One of the mappings is not a variant mapping.
You must fix the mappings in the signal map for the refined connector.
Messages Variables
Wire {0} of signal {1} is incorrectly mapped {0} - Wire name
at connector {2} creating a wire with more {1} - Signal name
than two active connections

December 2023
Mismatched physical and logical multicore

Identifies physical multicores that are of a different type to that of their corresponding
functional multicore and identifies functional multicores that do not have a corresponding
physical multicore (because of conductor/shield mismatches).
Messages Variables
Functional multicore {0} does not have a {0} - Multicore name
corresponding physical multicore for wire {1} {1} - Wire name
in harness {2}
{2} - Harness name
Physical multicore {0} in harness {1} has a {0} - Multicore name
different type than its corresponding functional {1} - Harness name
multicore {2}
{2} - Multicore name
Signal {0} is a member of two functional {0} - Signal name
multicores which cannot be combined: {1} {1}- 'Reason' which can be one of the
following (where {2} and {3} are functional
multicores):
• Not all nets of {2} and {3} are logically
equal.
• Shields of {2} and {3} are not logically
equal.
• {2} and {3} have a different number of
cores.
• {2} and {3} inner multicores have different
structures.
• {2} and {3} have a different number of
inner multicores.
• {2} and {3} have a shield mismatch.
• {2} and {3} have different shield body
types.
• {2} and {3} have different sheath types.
Physical multicore {0} in harness {1} has {0} - Multicore name
different number of cores than its {1} - Harness name
corresponding functional multicore {2}
Physical multicore {0} in harness {1} has {0} - Multicore name
different structure than its corresponding {1} - Harness name
functional multicore {2}

December 2023
Messages Variables
parent multicore, but its corresponding {1} - Harness name
functional multicore {2} does not
Physical multicore {0} in harness {1} does not {0} - Multicore name
have a parent multicore, but its corresponding {1} - Harness name
functional multicore {2} does
Physical multicore {0} in harness {1} does not {0} - Multicore name
have a shield, but its corresponding functional {1} - Harness name
multicore {2} does
shield, but its corresponding functional {1} - Harness name
multicore {2} does not
Mismatched wire option expression and harness level

Identifies wires whose option expression is not active on one or more of the harness levels to
which it is assigned. For example, a wire with option expression ABS should not appear on a
harness level which does not support the ABS feature.
Note
This check is applicable only to physical harness levels and not abstract harness levels.
Messages Variables
Wire {0} in signal {1} has an option {0} - Wire name
expression which is not active in some of its {1} - Signal name
harness levels: {2}.
{2} - List of level names
Wire {0} in signal {1} is not present on some {0} - Wire name
levels when its expression is active: {2}. {1} - Signal name
{2} - List of level names
Pending checklist items

Identifies Collaborate checklist items that have not been resolved.
Messages Variables
There is {0} pending checklist item {0} - Number

December 2023
Messages Variables
There are {0} pending checklist items {0} - Number
Refined connector cavity mismatch

If a connector has been refined, all the cavities that carry wiring should be referenced by the
refinement. This check confirms that each wire attached to a refined connector is assigned to a
refined pin with a matching signal, and identifies where this is not the case. A matching signal
can be the same signal, or a child/parent signal.
Messages Variables
Cavity {0}, Signal {3} on connector {2} is {0} - Cavity name
missing a specialized pin for bundle fanout {3} - Signal name
Cavity {0} (unconnected) on connector {2} is {0} - Cavity name
missing a specialized pin for bundle fanout {2} - Connector name
Unresolved comments
Identifies Collaborate comments that have not been resolved.
Messages Variables
There is {0} unresolved comment {0} - Number
There are {0} unresolved comments {0} - Number
Comment symbol requires update

Identifies any comment symbol that has changed since it was assigned to a library part.
Messages Variables
Symbol {0} is out of date for comment graphic {0} - Symbol name
at {2} in {1} {2} - X,Y coordinate
{1} - Design name.
Symbol was not found for comment graphic at {1} - X,Y coordinate
{1} in {0} {0} - Design name.

December 2023
Inconsistent harness level

This check does the following:
• If vehicle models are defined, identifies levels that are not associated with any vehicle
model.
• If vehicle models are defined, identifies levels which do not support options defined as
STD in an associated vehicle model.
• If vehicle models are defined, identifies levels which support an option which is
unavailable in an associated vehicle model.
• Identifies levels that support exclusive options.
• Identifies levels which have identical supported vehicle models and options.
Messages Variables
Level {0} of harness {1} does not match any {0} - Harness level name
Valid Selection of Option Combination {2} {1} - Harness name
permitted for Vehicle Model {3}
{2} - Option combination
{3} - Vehicle model name
Level {0} of harness {1} is not associated with {0} - Harness level name
any Vehicle Models {1} - Harness name
Level {0} of harness {1} has Option {2} set {0} - Harness level name
but the Option is omitted from all associated {1} - Harness name
Vehicle Models
{2} - Option name
Level {0} of harness {1} has Option {2} {0} - Harness level name
cleared but the Option is standard in associated {1} - Harness name
Vehicle Model {3}
{2} - Option name
{3} - Vehicle model name
Level {0} of harness {1} has Option {2} set {0} - Harness level name
but inclusive Option {3} unset {1} - Harness name
{2} and {3} - Option names
Levels {0} and {1} of Harness {2} reference {0} and {1} - Harness level names
the same Options and Vehicle Models {2} - Harness name
Obsolete option
Identifies any obsolete options used on design objects and in prototype constraints.

December 2023
Messages Variables
Harness {0} level {1} uses obsolete option {2} {0} - Harness name
{2} - Option name
Harness {0} level {1} uses obsolete options {0} - Harness name
{2} {1} - Harness level name
{2} - Option names
Signal {1} mapped to {2}:{3} uses obsolete {1} - Signal name
option {4} {2}:{3} - Connector and cavity
{4} - Option name
Signal {1} mapped to {2}:{3} uses obsolete {1} - Signal name
options {4} {2}:{3} - Connector and cavity
{4} - Option names
Obsolete options {1} are present in the option {1} - Option names
expression of functional device {2} in slot {0} {2} - Device name
{0} - Slot name
Obsolete option {1} is present in the option {1} - Option name
expression of functional device {2} in slot {0} {2} - Device name
{0} - Slot name
Obsolete options {1} are present in the option {1} - Option names
expression of functional source {2} of signal {2} - Object name
{0}
{0} - Signal name
Obsolete option {1} is present in the option {1} - Option name
expression of functional source {2} of signal {2} - Object name
{0}
{0} - Signal name
Vehicle model {0} uses obsolete option {1} {0} - Vehicle model name
{1} - Option name
Vehicle model {0} uses obsolete options {1} {0} - Vehicle model name
{1} - Option names
Obsolete options {1} are present in the variant {1} - Option names
placement option expression of device {2} in {2} - Device name
slot {0}
{0} - Slot name

December 2023
Messages Variables
Obsolete option {1} is present in the variant {1} - Option name
placement option expression of device {2} in {2} - Device name
slot {0}
{0} - Slot name
Prototype constraint using design {0} defined {0} - Design name
with obsolete option {1} {1} - Option name
Prototype constraint using design {0} defined {0} - Design name
with obsolete options {1} {1} - List of option names
Variantly placed device with an invalid option expression

Identifies devices that have been variantly placed either with no option expression or with the
same option expression in multiple slots. For further information about variant placement, see
“Variant Placement of a Device” in the Capital Systems Integrator User Guide.
Messages Variables
Device {0} is variantly placed with no option {0} - Device name
expression in the following slot(s):
Device {0} is variantly placed with the same {0} - Device name
option expression in the following slot(s):
There are {0} variantly placed device(s) with {0} - Number
an invalid option expression
Wiring breaks separation rules

Reads all the wires in the design that have a separation category, finds all the bundles that those
wires pass through, and then checks that the distances between those bundles in 3D space
conform to the minimum separation defined between the various categories. If you have not set
any separation categories and distances, the check reports “No separation categories/distances
have been defined for this design. See “Setting Separation Categories and Distances” on
page 511 for how to set separation rules.
Messages Variables
No separation categories/distances have been
defined for this design. Please set separation
distances using the action in the 3D tab.
Wire {0} in bundle {1} breaks separation rules {0} - Wire name
with wire {2} in bundle {3}. {1} - Bundle name
{2} - Wire name
{3} - Bundle name

December 2023
Messages Variables
Failed to run Wiring breaks separation rules
DRC as no license is available.
Capital Systems Integrator - Design Assistant DRCs

There are particular design rule checks related to design assistant that you can run for a Capital
Inconsistent harness option

Identifies options that are either missing from a harness and needed by synthesis to route a
signal, or are present on a harness and are no longer required or are missing from the project.
Messages Variables
Option {0} on a Device placed in Slot {1} is {0} - Option name
not present on Harness {2} {1} - Slot name
{2} - Harness name
Option {0} on a Device placed in Slot {1} is {0} - Option name
not defined in the Project {1} - Slot name
Options {0} on a Device placed in Slot {1} are {0} - Option names
not present on Harness {2} {1} - Slot name
{2} - Harness name
Options {0} on a Device placed in Slot {1} are {0} - Option names
not defined in the Project {1} - Slot name
Option {0} is redundant on Harness {1} {0} - Option name
{1} - Harness name
Options {0} are redundant on Harness {1} {0} - Option names
{1} - Harness name
Option {0} on wire {1} is not present on {0} - Option name
Harness {2} {1} - Wire name
{2} - Harness name
Option {0} on wire object {1} is not defined in {0} - Option name
the Project {1} - Wire name
Options {0} on wire {1} are not present on {0} - Option names
Harness {2} {1} - Wire name
{2} - Harness name

December 2023
Messages Variables
Options {0} on wire {1} are not defined in the {0} - Option names
Project {1} - Wire name
Option {1} is not referenced in any levels of {1} - Option name
Harness {0}. {0} - Harness name
Options {1} are not referenced in any levels of {1} - Option names
Harness {0}. {0} - Harness name
There are no levels defined for Harness {0}. {0} - Harness name
Level {0} of Harness {1} does not reference a {0} - Harness level name
vehicle model. {1} - Harness name
Levels {0} of Harness {1} do not reference a {0} - Harness level names
vehicle model. {1} - Harness name
Invalid prototype constraint

Identifies prototype constraints that cannot be applied because of an invalid definition. Invalid
definitions can result from invalid signal names (no signals match the specified name), invalid
option expressions (options may have changed or been deleted), or invalid design names
(design may have been renamed or deleted).
Note
Prototype wiring cannot be applied to a signal inside a multicore if the prototype constraint
applies to a signal rather than a multicore. The check also reports cases where a constraint
attempts to do this.
Messages Variables
Prototype constraint references design {0} that {0} - Design name
does not exist with the project
Prototype constraint using design {0} {0} - Design name
references invalid configuration {1} {1} - Configuration name
Prototype constraint using design {0} will {0} - Design name
match condition Signal Name = {1} cannot be {1} - Signal name
applied as signal {2} is part of the multicore
{3} {2} - Signal name
Prototype constraint using design {0} with {0} - Design name
match condition Signal Name = {1} does not {1} - Signal name
match any signal in the design

December 2023
Empty slot
Identifies slots with no placed devices.
Messages Variables
Slot {0} has no content {0} - Slot name
There are {0} Slot(s) with no content {0} - Number
Placement conflict
If slots have both “Option place by Attribute/Property” and “Place by Attribute/Property”
constraints that match a device, only “Option place by Attribute/Property” constraints influence
the placement of ground devices in slots. This check reports any related conflicts. For example:
Slot1 and Slot2 both contain conflicting placement constraints for GND1. This will result in the
placement of GND1 being placed in Slot1.
Messages Variables
Slots {0} contain valid placement constraints {0} - List of slots
for {1}. This will result in the placement of {1} - Functional device name
{1} being determined on a first come first
served basis.
Slots {0} contain conflicting placement {0} - List of slots
constraints for {1}. This will result in the {1} - Functional device name
placement of {1} being placed in {2}.
{2} - Slot name
There are {0} Placement conflicts {0} - Number
Unplaced device
Identifies unplaced devices in the current plane.
Messages Variables
Functional Device {0} is not placed {0} - Functional device name
There are {0} unplaced Functional Device(s) {0} - Number
Shared Functional Device {0} is not placed {0} - Functional device name
There are {0} unplaced Shared Functional {0} - Number
Device(s)
Capital Systems Integrator - Integrator Rules DRCs

There are particular design rule checks related to integrator rules that you can run for a Capital

December 2023
Assign connector rule violation

Identifies mappings between device connectors and virtual connectors that violate any “Assign
Connector by Attribute/Property” constraints (rules).
Messages Variables
Mapping footprint Connector {0} to {1} {0} - Device or footprint connector name
violates connector assignment constraint on {1} - Slot connector
Slot {2}
{2} - Slot name
Daisy-chained network wiring that breaks specified limit

Checks the overall length of daisy-chained networks (between terminator devices) in each
configuration and reports if the maximum length specified in a Daisy-chained network
specification constraint has been exceeded.
Messages Variables
The overall length of the daisy-chained {3}:{4} and {5}:{6} - Connector and cavity
network from {3}:{4} to {5}:{6} of signal {2} {2} - Signal name
exceeds the maximum length in {0} {1}
{0} - Vehicle configuration or abstract
configuration
Not all conductors in multicore {0} match a {0} - Multicore name
daisy-chained network specification constraint
Unable to determine daisy-chained network {2} - Signal name
path for signal {2} in {0} {1} {0} - Vehicle configuration or abstract
configuration
Ground placement constraint violation

Identifies combined ground devices and multiple terminations of ground signals that violate
constraints applied to ground slots.
Messages Variables
Maximum cavities exceeded on Connector {0} - Connector name
{0}, Ground Slot {1}. Found {2}, limit is {3} {1} - Ground slot name
{2} and {3} - Numbers

December 2023
Messages Variables
Maximum ground signals exceeded on Cavity {0} - Cavity name
{0}, Connector {1}, Slot {2}. Found {3}, limit {1} - Connector name
is {4}
{2} - Slot name
{3} and {4} - Numbers
Map same cavity by signal rule violation

Identifies any signals and pins that violate any “Map to Same Cavity by Signal Attribute/
Property” constraint (rules).
Messages Variables
Cavity {0} of Slot {1} is shared by pins {2} {0} - Cavity name
violating the Don't Map To Same Connector {1} - Slot name
Cavity constraint
{2} - List of Logic device pins
Signal {0} is mapped to Cavities {1} of Slot {0} - Signal name
{2} violating the Do Map To Same Connector {1} - List of cavities
Cavity constraint
{2} - Slot name
Map signal to inline cavity rule violation

Identifies wires that violate any “Map To Inline Cavity by Signal Attribute/Property” constraint
(rules). Also reports the signal, cavity and connector on which the violation exists.
Messages Variables
Signal {0} is mapped incorrectly to Cavity {1} {0} - Signal name
on inline {2} in Harness {3} {1} - Cavity name
{2} - Inline connector name
{3} - Harness name
Minimum splice separation rule violation

Identifies splices that violate any applicable minimum separation constraints (rules). Also
reports the bundle and harness on which the violation exists.

December 2023
Messages Variables
Splice {0} in Signal {1} violates separation {0} - Splice name
constraint from {2} connector {3} on Bundle {1} - Signal name
{4}, Harness {5}
{2} - Type of connector ('slot', 'inline',
'interface', and so on)
{4} - Bundle name
{5} - Harness name
constraint from {2} connector {3} on Bundle {1} - Signal name
Region {4}, Bundle {5}, Harness {6}
{2} - Type of connector ('slot', 'inline',
'interface', and so on)
{4} - Bundle region name
{5} - Bundle name
{6} - Harness name
constraint from splice {3} on Bundle {4}, {1} - Signal name
Harness {5}
{3} - Splice name
{4} - Bundle name
{5} - Harness name
constraint from splice {3} on Bundle Region {1} - Signal name
{4}, Bundle {5}, Harness {6}
{3} - Splice name
{5} - Bundle name
{6} - Harness name
constraint from Take Out {2} on Bundle {3}, {1} - Signal name
Harness {4}
{2} - Takeout name
{3} - Bundle name
{4} - Harness name

December 2023
Messages Variables
constraint from Take Out {2} on Bundle {1} - Signal name
Region {3}, Bundle {4}, Harness {5}
{2} - Takeout name
{4} - Bundle name
{5} - Harness name
Missing custom constraint

Identifies any custom constraints that have been defined for an object, but are no longer loaded
in Capital Systems Integrator.
Messages Variables
Custom Constraint {0} on {1} {2} is missing {0} - Custom constraint name
from plugin {1}- Object type
{2} Object name
Custom constraint {0} on design {1} is {0} - Custom constraint name
missing from plugin {1}- Design name
Multicore that breaks specification rule

Identifies multicores that violate any applicable multicore specification constraints (rules). Also
reports the signal and harness on which the violation exists and any conflicting multicore
specification constraints (rules) that apply to the design.
Messages Variables
Multicore {0} in Harness {1} violates {0} - Multicore name
specification constraint; {2} not {3} {1} - Harness name
{2} - Attribute or property name
{3} - Expected value
Multicore {0} in Harness {1} violates {0} - Multicore name
specification constraint; {2} missing {1} - Harness name
Cannot validate {0} rule on Multicore {1} {0} - Attribute or property name
because conflicting constraints were found on {1} - Multicore name
{2} and {3}.
{2} and {3} - Object names

December 2023
Multiterm that breaks number of wires rule

Identifies synthesized (CWS or MWS) multiple wire terminations that contain more wires than
the maximum specified (for a particular signal) in a constraint (rule).
Messages Variables
Multiterm violates max number of wires {3} - Signal name
constraint for signal {3} on cavity {2}, {2} - Cavity name
connector {4}, slot {5} in abstract
configuration {1} {4} - Connector name
{5} - Slot name
{1} - Abstract configuraiton name
constraint for signal {2} on pin {3}, device {3} - Pin name
{4}, slot {5} in abstract configuration {1}
{4} - Device name
{5} - Slot name
constraint for signal {3} on cavity {2}, {2} - Cavity name
connector {4} in abstract configuration {1}
Multiterm violates max number of wires {0} - Cavity name
constraint on Cavity {0}, Connector {1}, Slot {1} - Connector name
{2}
{2} - Slot name
Multiterm violates max number of wires {0} - Pin name
constraint on pin {0}, device {1}, Slot {2} {1} - Device name
{2} - Slot name
Multiterm violates max number of wires {0} - Cavity name
constraint on Cavity {0}, Connector {1} {1} - Connector name
Network wiring that breaks specified limit

Identifies network wiring that does not conform to the limits specified using a Network
Specification constraint. The wiring does not conform if:
• Not all stubs are connected to the main line using splices.
• The maximum length between the terminated devices is greater than the length specified
in the constraint.

December 2023
• The minimum and maximum stub lengths do not conform to the values specified in the
constraint.
• The minimum distance between stubs does not conform to the distance specified in the
constraint.
Note
Your design must have at least one configuration if you want to run this check.
Messages Variables
Stub {3} of signal {2} violates constraint for {3} - Slot connector name
maximum stub length in {0} {1} {2} - Signal name
configuration
Stub {3} of signal {2} violates constraint for {3} - Slot connector name
minimum stub length in {0} {1} {2} - Signal name
configuration
The overall length of the bus from {3} to {4} {3} and {4} - Slot connector names
of signal {2} exceeds the maximum length in {2} - Signal name
{0} {1}
configuration
Stub {3} of signal {2} does not connect to {3} - Slot connector name
backbone with a splice in {0} {1} {2} - Signal name
configuration
Not all conductors in multicore {0} match a {0} - Multicore name
network specification constraint
Splice {2} in signal {3} violates network stub {2} - Splice name
separation constraint from splice {5} in {0} {3} - Signal name
{1}
{5} - Splice name
configuration

December 2023
Object that breaks attribute/property rule

Identifies any objects that violate any “Set Integrator Attribute/Property on Object” constraints.
These constraints define, for specific objects, which value an attribute/property should have
when another attribute/property has another specific value.
Messages Variables
{0} {1} violates Attribute/Property constraint; {0} - Object type
{2} should be {3} {1} - Object name
{3} - Expected value.
{2} is missing {1} - Object name
Pin {0} on {1} {2} violates Attribute/Property {0} - Pin name
constraint; {3} should be {4} {1} - Object type
{2} - Object name
Pin {0} on {1} {2} violates Attribute/Property {0} - Pin name
constraint; {3} is missing {1} - Object type
{2} - Object name
Cannot validate {0} rule on {1} {2} because {0} - Attribute or property name
conflicting constraints were found on {3} and {1} - Object type
{4}
{2} - Object name
conflicting constraints were found on {3} {1} - Object type
{2} - Object name
{3} - Object names
Cannot validate {0} rule on {1} {2} {0} - Attribute or property name
{1} - Object type
{2} - Object name

December 2023
Signal that breaks backshell usage rule

Identifies backshell terminations where a cavity should be used according to assigned rules and
constraints.
Messages Variables
No backshell used for {2} at connector {1}, {2} - Signal name
uses cavity {0}. {1} - Connector name
{0} - Cavity name
Unable to use backshell for signal {0} at {0} - Signal name
connector {1} as connector is ring terminal. {1} - Connector name
Should not use backshell {0} for signal {2} at {0} - Backshell name
connector {1}. {2} - Signal name
Signal that breaks pigtail usage rule

Identifies signals that connect using a pigtail where no pigtail should be used according to
assigned rules and constraints. Signals that connect without a pigtail where a pigtail should be
used according to assigned rules and constraints.
Messages Variables
Cavity {0} on connector {1} for Signal {2} {0} - Cavity name
requires direct connection but uses a pigtail. {1} - Connector name
{2} - Signal name
Cavity {0} on connector {1} for Signal {2} {0} - Cavity name
requires a pigtail but uses a direct connection. {1} - Connector name
{2} - Signal name
Slot that breaks placement rule

Identifies devices that violate any applicable slot placement constraints (rules) and regular
devices that have been placed into ground slots. Also reports the slot in which the violation
exists.
Messages Variables
Device {0} violates placement constraint on {0} - Device name
Slot {1} {1} - Slot name
Standard Device {0} is placed in Ground Slot {0} - Device name
{1} {1} - Ground slot name

December 2023
Splice that breaks number of wires rule

Identifies splices that violate any applicable maximum number of wires per splice constraints
(rules). Also reports the bundle and harness on which the violation exists.
Messages Variables
Splice {2} in signal {3} violates max number {2} - Splice name
of wires constraint on bundle {4}, harness {5} {3} - Signal name
in abstract configuration {1}
{4} - Bundle name
{5} - Harness name
Splice {2} in signal {3} violates max number {2} - Splice name
of wires constraint on bundle region {4}, {3} - Signal name
bundle {5}, harness {6} in abstract
configuration {1} {4} - Bundle region name
{5} - Bundle name
{6} - Harness name
Splice {0} in Signal {1} violates max number {0} - Splice name
of wires constraint on Bundle {2}, Harness {1} - Signal name
{3}, Level {4}
{2} - Bundle name
{3} - Harness name
Splice {0} in Signal {1} violates max number {0} - Splice name
of wires constraint on Bundle Region {2}, {1} - Signal name
Bundle {3}, Harness {4}, Level {5}
{3} - Bundle name
{4} - Harness name
Splice that breaks specification rule

Identifies splices (from composite wiring synthesis or modular wiring synthesis) that violate
any applicable splice specification constraints (rules). Also reports the signal and harness on
which the violation exists and any conflicting splice specification constraints (rules) that apply
to the design.

December 2023
Messages Variables
Splice {0} in Signal {1}, Harness {2} violates {0} - Splice name
specification constraint; {3} not {4} {1} - Signal name
{2} - Harness name
Splice {0} in Signal {1}, Harness {2} violates {0} - Splice name
specification constraint; {3} missing {1} - Signal name
{2} - Harness name
Cannot validate {0} rule on Splice {1} {0} - Attribute or property name
because conflicting constraints were found on {1} - Splice name
{2} and {3}.
Wire that breaks length change rule

Identifies wires with “Length Change Type” or “Length Change Value” attribute values that
violate any “Length Change for Jumper” or “Length Change for Wire” constraints. Wire are
considered to be violating the constraints if:
• They have values for the Change Length attributes that vary from the matching
constraint values.
• The wire length varies from the length calculated using the matching constraint.
• The wire length calculation using the constraint produces a negative value.
Messages Variables
{1} {0} in Signal {2}, Harness {3} violates {1} - Wire or jumper wire
length change constraint; {4} not {5} {0} - Wire name
{2} - Signal name
{3} - Harness name
{4} - Length change attribute

December 2023
Messages Variables
{1} {0} in Signal {2}, Harness {3} violates {1} - Wire or jumper wire
length change constraint; {4} missing {0} - Wire name
{2} - Signal name
{3} - Harness name
{4} - Length change attribute
Cannot validate {2} rule on {1} {0} because {2} - Length change attribute
conflicting constraints were found on {3} and {1} - Wire or jumper wire
{4}.
{0} - Wire name
{1} {0} in Signal {2}, Harness {3} does not {1} - Wire or jumper wire
have correct wire length; WireLength not {5}. {0} - Wire name
{2} - Signal name
{3} - Harness name
Wire length calculation using constraint shows {4} - Negative value
negative value {4} for {1} {0} in Signal {2}, {1} - Wire or jumper wire
Harness {3}.
{0} - Wire name
{2} - Signal name
{3} - Harness name
Wire that breaks routing rule

Identifies wires that violate any applicable signal routing constraints (rules). Also reports the
signal, bundle and harness on which the violation exists.
Messages Variables
Wire {0} in Signal {1} violates routing {0} - Wire name
constraint on Bundle {2}, Harness {3} {1} - Signal name
{2} - Bundle name
{3} - Harness name
constraint on Bundle Region {2}, Bundle {3}, {1} - Signal name
Harness {4}
{3} - Bundle name
{4} - Harness name

December 2023
Messages Variables
constraint on Connector {2}, Harness {3} {1} - Signal name
{3} - Harness name
constraint on Junction Box {2}, Harness {3} {1} - Signal name
{2} - Junction box name
{3} - Harness name
Wire that breaks specification rule

Identifies wires that violate any applicable wire specification constraints (rules). Also reports
the signal and harness on which the violation exists and any conflicting wire specification
constraints (rules) that apply to the design and conflicts in the option-specific values as
displayed on the Variance tab of the Edit Properties dialog boxes for signals.
Messages Variables
Wire {0} in Signal {1}, Harness {2} violates {0} - Wire name
specification constraint; {3} not {4} {1} - Signal name
{2} - Harness name
specification constraint; {3} missing {1} - Signal name
{2} - Harness name
Cannot validate {0} rule on Wire {1} because {0} - Attribute or property name
conflicting constraints were found on {2} and {1} - Wire name
{3}.
Wire that breaks terminal specification rule

Identifies wires that violate any applicable terminal specification constraints (rules). Also
reports the signal and harness on which the violation exists.

December 2023
Messages Variables
terminal specification constraint; {3} attribute {1} - Signal name
not {4}
{2} - Harness name
terminal specification constraint; {3} attribute {1} - Signal name
missing
{2} - Harness name
Cannot validate Terminal Specification rule on {0} - Connector name
Connector {0}, Cavity {1} because conflicting {1} - Cavity name
constraints were found on {2} and {3}.
Ground device that breaks placement rule

Identifies issues with the placement of ground devices in slots. For each placed ground device,
this determines whether it should be uniquely placed in a single slot, variant place or placed
according to optimized ground placement. In each case, this check reports warnings as follows:
• If the ground device has one or more matching variant placement constraints, the check
reports if the ground is not placed in these slots, or is not placed with the appropriate
variant option expression, or is placed in additional slots.
• If the ground device has a single matching slot, the check reports if the ground is not
placed in this slot, or is variantly placed in this slot, or is placed in additional slots.
• If the ground device has multiple matching slots (that is, it needs to be optimally placed),
the check determines whether the ground device is placed once and only once for every
placement context that has at least one active connected device. The placement context
will be based on the options on the connected devices and on the ground slots only.
Messages Variables
{0} does not match its variant placement {0} - Ground device name
constraints. It is not placed in slots: {1}. {1} - List of slots
constraints. There is no matching placement {1} - List of slots
constraint on slots: {1}.

December 2023
Messages Variables
constraints. It placement option expression {1} - List of slots
does not match the constraint on slots: {1}.
{0} does not match its placement constraint. It {0} - Ground device name
is not placed in slot {1}. {1} - Slot name
{0} does not match its placement constraint. It {0} - Ground device name
is placed in slot {1} with option expression {1} - Slot name
{2}.
{2} - Option expression
{0} does not match its multiple placement {0} - Ground device name
constraints. It is not placed in any slot for the Followed by list of contexts each of which is a
following contexts: list of options
{0} does not match its multiple placement {0} - Ground device name
constraints. It is placed in more than one slot Followed by list of contexts each of which is a
for the following contexts: list of slots and an option expression
Cannot check Ground placement due to This is followed by a list of issues in the form
Vehicle Models having conflicts between of the following message.
options:
Vehicle Model {0} has conflicting options {1} {0} - Vehicle model name
{1} - List of options
{0} has redundant placement expressions. {0} - Ground device name
This could have an adverse effect on ground
refinement and synthesis. Please remove the
expressions from the device.
Capital Systems Integrator - Library Consistency DRCs

There are particular design rule checks related to library consistency that you can run for a
Capital Systems Integrator design.
Inline mate part mismatch

Identifies mated inline pair halves that have library parts that are not valid mates. If connector
refinement has been used, this check examines the mated specialized connectors.
Messages Variables
Inline {0} has a library part with mating {0} -Inline name
restrictions that conflicts with Connector {1}. {1} - Connector name

December 2023
Messages Variables
Inline {0} has incorrect cavity mating. Library {0} -Inline name
part {1} defines that cavity {2} should be {1} - Library part number
mated to cavity {3}.
{2}and {3} - Cavity names
Inline {0} references library part that can not {0} -Inline name
be found.
Inline {0} has a library part with mating {0} - Inline name
restrictions but no mate.
Library connector cavity count mismatch

Identifies virtual/device/inline/refined (specialized) connectors having a cavity count that
differs to that of their corresponding library part.
Messages Variables
Connector {0} has conflicting Cavity count {0} - Connector name
from its library part {1} {1} - Library part number
Device Connector {3} on slot connector {1} {3} - Device connector name
has conflicting Cavity count from its library {1} - Slot connector name
part {2}
{2} - Library part number
Connector {0} has part number {1} but no {0} - Connector name
Cavity count is specified {1} - Library part number
Device Connector {3} defined on slot {3} - Device connector name
connector {1} has part number {2} but no {1} - Slot connector name
Cavity count is specified
Library multicore mismatch

Identifies multicores with mismatches between the number of conductors in their library
association and that specified on the design.
Messages Variables
Multicore {1} is missing conductor {2} {1} - Multicore name
required for library part {0}. {2} - Specification of the missing conductor as
defined in Library

December 2023
Messages Variables
Multicore {0} contains {1} {2} not accounted {0} - Multicore name
for in library part {3} {1} - Wire or shield
{2} - Wire or shield name
Multicore {0} refers to a library part that does {0} - Multicore name
not exist
Attributes of multicore "{1}" does not match {1} - Multicore name
with its library part "{2}" {2} - Library part number
Attributes of innercore {0} {1} of "{2}" does {0} - Wire or shield
not match with its library part "{3}" {1} - Wire or shield name
Innercore {0} {1} of multicore "{2}" does not {0} - Wire or shield
match with its conductor role in library part {1} - Wire or shield name
"{3}"
Library part not latest revision

Identifies any library part that is not the latest revision.
Messages Variables
{0} {1} has P/N={2} assigned to it, but that is {0} - Object type
not the latest {1} - Object name
Mismatched device footprint

Identifies mismatches and conflicts in device connector or harness footprint pin mappings once
they have been placed into slots.
Messages Variables
Slot {0} has Connector(s) not referencing the {0} - Slot name
corresponding Footprint Connector(s) for the {1} - Device name
placed Device {1}

December 2023
Messages Variables
Slot {0} has Direct To Device connection to {0} - Slot name
connector {1} that does not match the {1} - Connector name
corresponding Footprint for the placed Device
{2} {2} - Device name
Slot {0} has a different number of Connectors {0} - Slot name
than defined in Footprint for the placed Device {1} - Device name
{1}
Slot {0} has Connector(s) with different Pin {0} - Slot name
names than the corresponding Footprint {1} - Device name
connector(s) for the placed Device {1}
Slot {0} has Connector(s) with a different {0} - Slot name
number of Pins than the corresponding {1} - Device name
Footprint Connector(s) for the placed Device
{1}
Slot {0} has a different Pin mapping than the {0} - Slot name
Library Footprint for the placed Device {1} {1} - Device name
Slot {0} has Footprint but the placed Device {0} - Slot name
{1} does not {1} - Device name
Slot {0} has a different Pin mapping than {0} - Slot name
defined by pin attribute(s) on the placed {1} - Device name
Device {1}
In Slot {0}: Device {1} needs to Update its {0} - Slot name
Footprint reference {1} - Device name
Not all the pins in slot {1} could be matched to {1} - Slot name
the pins defined for library part {2} {2} - Library part number
Not all the pins on device {0} in slot {1} could {0} - Device name
be matched to the pins defined for library part {1} - Device name
{2}
Slot {0} has a placed Device {1} that has {0} - Slot name
Device Connector(s) that do not reference the {1} - Device name
correct Footprint connector(s)
Device Connector names inconsistent with the {1} - Device name
Footprint Connector names
Slot {0} has a placed Device {1} that has a {0} - Slot name
different number of Device Connectors than {1} - Device name
that in Footprint

December 2023
Messages Variables
Device Connector(s) with different Pin names {1} - Device name
than the Footprint Connector(s)
Device Connector(s) with a different number {1} - Device name
of Pins than the Footprint Connector(s)
different number of Device Pins than required {1} - Device name
by the Footprint
Slot {0} has a placed Device {1} that has a Pin {0} - Slot name
mapping inconsistent with the Footprint {1} - Device name
Slot {0} has a placed Device {1} that has a {0} - Slot name
Footprint type conflicting with Library {1} - Device name
definition
Slot {0} has a placed Device {1} that has no {0} - Slot name
pins placed on design {1} - Device name
Device Pins unmapped in Footprint definition {1} - Device name
Slot {0} has a placed Device {1} that {0} - Slot name
references a Footprint that no longer exists {1} - Device name
Slot {0} has a placed Device {1} that has no {0} - Slot name
referenced Footprint Pinmaps in Library {1} - Device name
Slot {0} and the placed Device {1} have {0} - Slot name
corresponding Device Connector(s) not {1} - Device name
referencing the same Library Part
mismatched Device Connector names {1} - Device name
Slot {0} and the placed Device {1} have a {0} - Slot name
different number of Device Connectors {1} - Device name
corresponding Device Connector(s) with {1} - Device name
different Pin names
corresponding Device Connector(s) with {1} - Device name
different numbers of Pins

December 2023
Messages Variables
Slot {0} and the placed Device {1} do not {0} - Slot name
have the same Footprint ID {1} - Device name
Slot {0} and the placed Device {1} do not {0} - Slot name
have the same Footprint ID {1} - Device name
different Device to Device Connector Pin {1} - Device name
mapping
Reference to non-existent library object

Identifies devices, wires, connectors, device connectors, refined (specialized) connectors,
multicores, shields, splices that possess a library reference or part number property, but where a
corresponding library object does not exist.
Messages Variables
{0} {1} has a library reference and Part {0} - Object type
Number {2} but library object does not exist {1} - Object name
Connector {0} in refinement definition of {0} - Connector name
Connector {1} has a library reference and Part {1} - Connector name
Number {2} but library object does not exist
{0} {1} has a library reference, but no Part {0} - Object type
Number and library object does not exist {1} - Object name
Connector {0} in refinement definition of {0} - Connector name
Connector {1} has a library reference, but no {1} - Connector name
Part Number and library object does not exist
Status of library part is not current

Identifies any library part used in a design or build list that has a status other than Current (that
is, have an Obsolete or New status).
Messages Variables
Status of library part for {0} {1} is ''{2}'', not {0} - Object type
current {1} - Object name
{2} - Library part status

December 2023
Wire fits cavity mismatch

At every harness level, examines the cavities of connector and ring terminals with a library part,
and considers all combinations of each cavity with its connected conductors (wires, nets, and
shields), and identifies the following:
• Mismatch between the material and CSA specified for the connected conductors and the
cavity.
• When the cavity and its connected conductors are not accepted by any defined terminals
on the cavity.
• For connectors, the check reads the configuration of the library part number on the
following tabs in the Component Maintenance Dialog Box:
o Single Wire Fits Cavity and Multiple Wire Fits Cavity tabs — Reports errors
related to terminals associated with the cavities defined on the Housing tab.
o Pin Names tab — Reports errors related to terminal and seal violations for each
cavity only if the Requires Terminal/Seal option is selected.
• For ring terminals, the check reads the Single Termination and Multiple Termination
tabs and verifies any terminals associated with the cavity defined on the Housing tab.
If connector refinement is specified, this check examines the specialized connectors.
Where a wire terminates at multiple cavities (variance), all cavities are checked.
Messages Variables
In harness {0} level {1}, wire {4} does not fit {0} - Harness name
cavity {3} on {5} {2} {1} - Harness level
Mismatch between the Spec, Material, and {4} - Wire name
CSA values of the single wire connected to the
cavity and the values defined on the Single {3} - Cavity number
Wire Fits Cavity tab. {5} - <connector or ring terminal>
{2} - <connector or ring terminal> name
In harness {0} level {1}, wires {4} do not fit {0} - Harness name
Mismatch between the Spec, Material, and {4} - Wire names
CSA values of multiple wires connected to the
cavity and the values defined on the Multiple {3} - Cavity number

December 2023
Messages Variables
In harness {0} level {1}, no terminal on {0} - Harness name
connector {2} fits cavity {3} and accepts wire {1} - Harness level
{4}
Terminal material on the wire does not match
the wire fit profile of the library terminal. {3} - Connector cavity
{4} - Wire name
connector {2} fits cavity {3} and accepts wires {1} - Harness level
{4}
Terminal material on the wires does not match
the wire fit profiles of the library terminals. {3} - Connector cavity
{4} - Wire names
In harness {0} level {1}, ring terminal {2} {0} - Harness name
does not fit wire {4} {1} - Harness level
Ring terminal has a library terminal assigned {2} - Ring terminal name
but the part has no wire fit profiles. No
terminal part on wire (Single wire). {4} - Wire name
does not fit wires {4} {1} - Harness level
terminal part on wires (Multiple wires). {4} - Wire names
Wire cavity component mismatch

Examines the terminals and seals defined on the conductors on the Connections tab with the
terminals and seals defined in the housing definition of the library part and identifies the
following:
• Mismatch between the terminal part or material between the ones defined on connected
conductors (Connection tab) and library cavities (Housing definition).
• Mismatch between the seal part between the ones defined on connected conductors
(Connection tab) and library cavities (Housing definition).
• Identifies if the terminal / seal defined on the conductor (Connection tab) does not
accept wires.

December 2023
Messages Variables
In harness {0} level {1}, terminal {6} in {0} - Harness name
cavity {3} of connector {2} does not accept {1} - Harness level
wire(s) {4}
{6} - Terminal part number
Same terminal part exists on both the wire and
in the housing definition, but no wire fit {3} - Connector cavity
profiles exist on the terminal part in the {2} - Connector name
library.
{4} - Wire names
In harness {1} level {2}, terminal {3} on {1} - Harness name
wire(s) {6} is not defined for cavity {4} in {2} - Harness level
connector library part {5} on {0}
Terminal part on the wires is not defined in the
housing definition of the library part. {6} - Wire names
{4} - Cavity number
{5} - Connector library part number
In harness {1} level {2}, seal {3} on wire(s) {1} - Harness name
{6} is not defined for cavity {4} in connector {2} - Harness level
library part {5} on {0}
{3} - Seal part number
Seal part on the wires is not defined in the
{4} - Cavity number
In harness {0} level {1}, seal {6} in cavity {3} {0} - Harness name
of connector {2} does not accept wire(s) {4} {1} - Harness level
Seal part on the wires matches the housing {6} - Seal part number
definition, but it has no wire fit.
{3} - Cavity number
{4} - Wire names
In harness {0} level {1}, the following wires {0} - Harness name
have different values for attribute terminal part {1} - Harness level
at connector {2} cavity {3}:{4}
The terminal part numbers on the connected
wires are different. {3} - Connector cavity
{4} - Wire names

December 2023
Messages Variables
have different values for attribute seal part at {1} - Harness level
connector {2} cavity {3}:{4}
The seal part numbers on the connected wires
are different. {3} - Connector cavity
{4} - Wire names
have different values for attribute terminal {1} - Harness level
material at connector {2} cavity {3}:{4}
The terminal materials on the connected wires
{4} - Wire names
No wire fit defined in terminal {3} for cavity {3} - Terminal part number
{1} in connector library part {2} on {0} {1} - Cavity number
Same terminal part is present on the wire and {2} - Connector library part number
in the housing definition, but no wire fit
library.
No wire fit defined in seal {3} for cavity {1} {3} - Seal part number
in connector library part {2} on {0} {1} - Cavity number
Same seal part is present on the wire and in the {2} - Connector library part number
housing definition, but no wire fit profiles
exist on the seal part in the library. {0} - Connector name
Include-on-BOM status changed

Identifies a connector or conductor whose component library definition has changed so that the
On BOM status is now different.
Messages Variables
{0} {1} 's Include On Bom status is different {0} - Object type
to its library part. {1} - Object name
Library part required for connector

Identifies inline and virtual connectors that have no library part assigned.
Messages Variables
{0} {1} has no library part {0} - Inline, Slot Connector or Interface
Connector

December 2023
Library part required for slot

Identifies slots containing devices that have no library part assigned.
Messages Variables
Slot {0} has no library part {0} - Slot name
No conductor library part available

Identifies conductors for which the combination of specification attribute values (specified on
the General tab of the Edit Properties facility) does not exist in any library wire size definition.
Messages Variables
Specification attributes combination for {0} {0} - Wire name
does not exist in Library wire size definitions
Out of scope component

Identifies components whose scope is not within the scope of the project or design.
Messages Variables
Library part {0} of {1} {2} has invalid {0} - Library part number
scoping. Component Scoping: {3}. {4} {1} - Object type
Scoping: {5}
{2} - Object name
{3} - Scope applied to library component
{4}- Design or project
{5} - Scoping applied to the design or project
Library part {0} of backshell {2}:{3} has {0} - Library part number
invalid scoping. Component Scoping: {4}. {5} {2} - Owning connector of backshell
Scoping: {6}
{3} - Backshell name
{4} - Scope applied to library component
{5}- Design or project
Capital Systems Integrator - Naming DRCs

There are particular design rule checks related to naming that you can run for a Capital Systems
Integrator design.

December 2023
Duplicate names in the design

Identifies objects having a name that is identical to that of another object of the same kind on the
same design or a shared object of the same kind but having different option expressions.
If connector refinement has been used, this check examines both the specialized connectors and
generalized connectors. If a generalized connector has the same name as one of its specialized
connectors, this will not be identified as an issue.
Messages Variables
There were {0} pairs of objects with duplicate {0} - Number of pairs of objects with duplicate
names names
Duplicate names in a harness

Identifies object names that are not unique on a harness. This check compares objects against
those of the same object type only.
If connector refinement has been used, this check examines both the specialized connectors and
generalized connectors. If a generalized connector has the same name as one of its specialized
connectors, this will not be identified as an issue.
Messages Variables
There were {0} groups of objects whose {0} - Number of groups of objects with
names clash within a harness duplicate names

December 2023
Design Rule Checks Applicable to Capital Logic Designer

Designs
There are specific design rule checks that you run while editing a design in Capital Logic
Designer.
Capital Logic Designer - Logic Build List Connectivity DRCs . . . . . . . . . . . . . . . . . . . . 307

Capital Logic Designer - Logic Build List Consistency DRCs. . . . . . . . . . . . . . . . . . . . . 308
Capital Logic Designer - Logic Build List Library Consistency DRCs . . . . . . . . . . . . . 308
Capital Logic Designer - Logic Build List Naming DRCs . . . . . . . . . . . . . . . . . . . . . . . . 312
Capital Logic Designer - Appearance DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Capital Logic Designer - Connectivity DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Capital Logic Designer - Consistency DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Capital Logic Designer - Exclusion DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Capital Logic Designer - ICD Consistency DRCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Capital Logic Designer - Inclusion DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Capital Logic Designer - Library Consistency DRCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Capital Logic Designer - Logic Rules DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Capital Logic Designer - Naming DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Capital Logic Designer - Logic Build List Connectivity DRCs

There are particular design rule checks related to build list connectivity that you can run for a
Capital Logic Designer design.
Shared wire terminating at more than two pins

Identifies shared wires that are terminated at more than two pins. It is only possible to have two
ends to a wire within the context of a build list. You should make sure that a single wire
connects to only two pins within the designs of any build list.
Messages Variables
Shared wire {0} terminating at more than two {0} - Shared Wire name
pins {1} {1} - Pinlist name : Pin name
Shared connectors mated to multiple devices

Identifies shared connectors mated to multiple devices. Signal trace data for the identified
connectors can be incorrect if proper options are not applied to the mating devices.

December 2023
Messages Variables
Shared connector {0} mated to multiple {0} - Shared Plug Connector name
devices {1} {1} - name of Devices
Capital Logic Designer - Logic Build List Consistency DRCs

There are particular design rule checks related to build list consistency that you can run for a
Inconsistent shared pin connections across designs

Identifies inconsistencies in the connection of shared pins where the same pin in multiple
designs is mated to different connectors or the same pin has no mate in one design but does have
a mate in another design. This check also considers ring terminals.
Messages Variables
Shared Pin {0}.{1} is connected to {2}.{3} {0} - Shared Pinlist name
{4}.{5} {1} - Shared Pin name
{2} - Pinlist name
{3} - Pin name
{4} - Pinlist name
{5} - Pin name
Inconsistent mating of connectors on blocks across designs

Identifies unassociated pins and invalid associations by checking each block on a design for un-
mated receptacle pins, or unconnected device pins. A warning is issued along with a link to the
highlighted block.
Messages Variables
{0} - Pin mated with different connectors {0} - Pin name with its design and parent name
in:{1} {1} - Design, Pinlist and pins name
Capital Logic Designer - Logic Build List Library Consistency

DRCs
There are particular design rule checks related to build list library consistency that you can run
for a Capital Logic Designer design.

December 2023
Wires fit shared cavity mismatch

Examines the shared cavities of connectors and ring terminals with a library part, and considers
all combinations of each shared cavity with its connected conductors (wires, nets, and shields),
and identifies the following:
shared cavity.
• When the shared cavity and its connected conductors are not accepted by any defined
terminals on the cavity.
• For connectors, the check reads the configuration of the part number on the following
tabs in the Component Maintenance Dialog Box:
related to terminals associated with the shared cavities defined on the Housing tab.
shared cavity only if the Requires Terminal/Seal option is selected.
tabs and verifies any terminals associated with the shared cavity defined on the
Housing tab.
The design rule check is not applied to non-shared connectors and ring terminals. See the
equivalent “Wire fits cavity mismatch” check for non-shared components on the Logic Design
tab.
Messages Variables
Wire {3} does not fit cavity {2} on connector {3} - Wire name
{1} {2} - Cavity name
Mismatch between the Spec, Material, and {1} - Connector name
cavity and the values defined on the Single
Wire Fits Cavity tab.
Wires {3} do not fit cavity {2} on connector {3} - Wire names
Mismatch between the Spec, Material, and {1} - Connector name
cavity and the values defined on the Multiple

December 2023
Messages Variables
No terminal on connector {1} fits cavity {2} {1} - Connector name
and accepts wires {3} {2} - Cavity name
No terminal part on the wire, the terminal part {3} - Wire names
exists in the housing definition, but there are
no wire fit profiles on the terminal part in the
library (Multiple wires).
and accepts wire {3} {2} - Cavity name
library (Single wire).
Ring terminal {1} does not fit wire {3} {1} - Ring terminal name
Ring terminal has a library terminal assigned {3} - Wire name
terminal part on wire (Single wire).
Ring terminal {1} does not fit wires {3} {1} - Ring terminal name
Ring terminal has a library terminal assigned {3} - Wire names
terminal part on wires (Multiple wires).
Wire shared cavity component mismatch

following:
accept wires.
The design rule check is not applied to non-shared connectors and shared ring terminals. See the
equivalent “Wire fits cavity mismatch” check for non-shared components on the Logic Design
tab.

December 2023
Messages Variables
Shared wire {0} has different values for wire {0} - Wire name
end attributes
The wire end attributes are different in
different designs.
Following wires have different values for {1} - Connector name
attribute terminal part at connector {1} cavity {2} - Cavity name
{2}:{3}
{3} - Wire names
wires are different.
attribute terminal material at connector {1} {2} - Cavity name
cavity {2}:{3}
{3} - Wire names
are different.
Terminal {2} on wire(s) {5} is not defined for {2} - Terminal part
cavity {3} in connector library part {4} on {0} {5} - Wire names
Terminal part on the wire is not present in the {3} - Cavity name
housing definition of the library part.
{4} - Connector part
Terminal {5} in cavity {2} of connector {1} {5} - Terminal part
does not accept wire(s) {3} {2} - Cavity part
Same terminal part exists on both the wire and {1} - Connector name
profiles exist on Terminal Part in the library. {3} - Wire names
attribute seal part at connector {1} cavity {2} - Cavity name
{2}:{3}
{3} - Wire names
are different.
Seal {2} on wire(s) {5} is not defined for {2} - Seal part
Seal part on the wire is not present in the {3} - Cavity name
housing definition.

December 2023
Messages Variables
Seal {5} in cavity {2} of connector {1} does {5} - Seal part
not accept wire(s) {3} {2} - Cavity part
Seal part on the wire and in the housing {1} - Connector name
definition match, but the seal part has no wire
fit profiles. {3} - Wire names
Capital Logic Designer - Logic Build List Naming DRCs

There are particular design rule checks related to build list naming that you can run for a Capital
Logic Designer design.
Duplicate Names across Designs

Identifies objects (devices, connectors, wires, nets, splices, multicores, and so on) having a
name that is identical to that of an object on another design in the build list. The default status
for this check is true, and its default severity setting is error. The check works in conjunction
with the Uniqueness project preference and so, for example, the name can be checked for
uniqueness within an object group such as connectors or across object types. In addition the
option expression and the harness attribute can also be included in the name composition. See
the Uniqueness project preference for more information.
Note
This check is only available if a build list has been defined in the project.
Messages Variables
{1} {0} in {2} and {4} {3} in {5} have {0} and {3} - any Logic Object(Other than
duplicate names. Highways)
{1} and {4} - are Object Types in Logic
{2} and {5} - are Design Name
Invalid name for shared object

Identifies, within the selected build list, shared objects with names that do not appear in the list
of valid names for that project's shared object type.
Note
This check is only available if a build list has been defined in the project.

December 2023
Messages Variables
Invalid name: {0} is not in the list of valid {0} - Any Shared Object
shared {1} names {1} - Any Shared Object Type
Capital Logic Designer - Appearance DRCs

Sector overlap
Identifies any overlapping sectors on a design. When this condition occurs then the inheritance
logic cannot resolve and must be manually corrected.
Messages Variables
Sectors {0}, {1} are overlapping. Attributes/ {0} {1} - are name of the Sectors
properties cannot be propagated
Sector {2}, {1} {0} are overlapping. {0} - Pinlist name
Attributes/properties cannot be propagated {1} - Pinlist Type
{2} - Sector name
Incorrect number of indicators on a multicore

Identifies multicores in the design that either have no indicators on the diagram or not enough
indicators on the diagram.
Messages Variables
{1} {0} belonging to {2} {3} having {4} {0} - Conductor name
terminations, but only {5} crossing indicator {1} - Conductor Type
{2} - Multicore or Overbraid Object Type
{3} - Multicore or Overbraid name
{4} - Number of conductor terminations
{5} - Number of indicators
{1} {0} belonging to {2} {3} having {4} {0} - Conductor name
terminations, does not have any crossing {1} - Conductor Type
indicators
{2} - Multicore or Overbraid Object Type
{3} - Multicore or Overbraid name
{4} - Number of conductor terminations

December 2023

Identifies:
so the quick code is displayed
database
See “Diagram Language Translation” on page 80.
Messages Variables
Overlapped device pins not connected

Identifies device pins on the diagram that overlap but are not connected. To fix this, right-click
a pin or pinlist and select Connect > by wire, by net, or by pin. Note: This DRC is not
applicable for connector pins.
Messages Variables
Pins {0}.{1} and {2}.{3}are overlapped but {0} and {2} - Device name
not connected. {1},{3} - Pin name
Overlapping conductors
Identifies conductors in which any portion of their segment overlaps another conductor
segment.
Messages Variables
{1} {0} overlaps with {3} {2} between {4} {0} and {2} - Any Conductor (Other than zero
and {5} length shields)
{1} and {3}- Conductor Type
{4} and {5} - Coordinate points

December 2023
Messages Variables
1} {0} overlaps with {2} between {4} and {5} {0} - Any Conductor (Other than zero length
shields)
{1}- Conductor Type
{2} - Daisy Chain
{4}, {5} - Coordinate points
{0} overlaps with {3} {2} at {4} {0} - Daisy Chain
{2} - Any Conductor (Other than zero length
shields)
{3}- Conductor Type
{4} - Coordinate points
{0} overlaps with {3} {2} between {4} and {0} - Daisy Chain
{5} {2} - Any Conductor (Other than zero length
shields)
{3}- Conductor Type
{4} and {5} - Coordinate points
{1} {0} overlaps with {2} at {4} {0} - Any Conductor (Other than zero length
shields)
{1} - Conductor Type
{2} - Daisy Chain
{1} {0} overlaps with {3} {2} at {4} {0} and {2} - Any Conductor (Other than zero
length shields)
{1} and {3} - Conductor Type
{0} overlaps with {2} at {4} {0} and {2} - Daisy Chain
{0} overlaps with {2} between {4} and {5} {0} and {2} - Daisy Chain
{4}, {5} - Coordinate points
Pin not on the grid

Identifies electrical pins on the diagram that are not positioned on grid points.
Messages Variables
Pin {1} of {0} is Not On The Grid {0} - Pinlist
{1} - Pin of Pinlist

December 2023

Messages Variables

non-UNICODE font.
Messages Variables
{2} - Font type
Text overlaps object

Identifies text, within a Capital Logic Designer design, that overlaps with component graphics
on the diagram. The check considers a number of scenarios when considering if text is
overlapped. These include:
• Text with styling options including ‘wrap’, ‘clip’, ‘shrink’, ‘overflow’

• Multi-line texts
• Text inside Comment symbols
• Text inside Device Signals
• Cross reference texts
• Opaque text in an enclosing boundary box
Depending on the scenario, the system either uses the tight boundary box of the text, or its
paragraph width and height to determine if overlapping has occurred. Any violations are
reported and a link is provided to the diagram to enable manual correction.

December 2023
Note
Text in tables is not considered when checking for overlapping text.
Where there is multi-line text or where paragraph width and height is used, the design rule
check accuracy is such that it may show return false positives when the other text is close by -
manually inspect the diagram to confirm issues.
Messages Variables
Text ''''{0}'''' overlaps with {1} ''''{2}'''' {0} - Text
{1} - Logic Object Type
{2} - Logic Object
Text overlaps text

Identifies text, within a Capital Logic Designer design, that overlaps with other text on the
diagram. The check considers a number of scenarios when considering if text is overlapped.
These include:
• Text with styling options including ‘wrap’, ‘clip’, ‘shrink’, ‘overflow’

• Multi-line texts
• Text inside Comment symbols
• Text inside Device Signals
• Cross reference texts
• Opaque text in an enclosing boundary box
Depending on the scenario, the system either uses the tight boundary box of the text, or its
paragraph width and height to determine if overlapping has occurred. Any violations are
reported and a link is provided to the diagram to enable manual correction.
Note
Text in tables is not considered when checking for overlapping text.
Where there is multi-line text or where paragraph width and height is used, the design rule
check accuracy is such that it may show return false positives when the other text is close by -
manually inspect the diagram to confirm issues.
Messages Variables
Text ''''{0}'''' overlaps with Text ''''{1}'''' {0} - Text
{1} - Text

December 2023
Capital Logic Designer - Connectivity DRCs

Invalid Device Terminations

Identifies jumper pins that are connected to a conductor.
Messages Variables
Jumper pin {0} of device {1} has conductors {0} - Pin name
connected to it {1} - Device name
Pin {0} of device {1} has both a device pin {0} - Pin name
and a conductor connected to it {1} - Device name
Net not terminating at a pin

Identifies net conductors that are not terminated at one or more ends.
Messages Variables
{1} {0} has not been terminated at both ends {0} - Net Conductor
{1} - Net
Shield termination not terminating at a pin

Identifies shields that are not terminated at one or both ends.
Messages Variables
{1} {0} has not been terminated at both ends {0} - Shield Conductor
{1} - Shield Termination
Unconnected connector
Identifies plug connectors or receptacle connectors that are not connected to any conductors on
the design.
Messages Variables
{1} {0} is unconnected {1} - Connector type
{0} - name

December 2023
Unconnected device
Identifies parameterized devices (with or without pins), library devices or symbol devices that
are not connected to any conductors on the design.
Messages Variables
{1} {0} is unconnected {1} - Device
{0} - Name
Unconnected splice
Identifies splices that are not connected to any conductors on the design.
Messages Variables
{1} {0} is unconnected {1} - Splice
{0} - Name
Wire not terminating at a pin

Identifies wires that are not terminated at one or both ends.
Messages Variables
{1} {0} has not been terminated at both ends {0} - Wire Conductor
{1} - Wire
Design that breaks module code relationships

Examines the module codes applied to a design and checks the explicit inclusive/exclusive
relationships and the implicit relationships (such as mutually exclusive folders). Any violations
are reported. (Only available if the Enable and Display Modules is set in the Module Codes
Project Preference.)
Messages Variables
{0} has a module code expression that violates {0} - Design name
module code relationships, {1} and {2} are {1} and {2} - Module codes
exclusive
Object that breaks module code relationships

Examines the module codes on each object and checks the explicit inclusive/exclusive
relationships and the implicit relationships (such as mutually exclusive folders). Any violations
are reported. (Only available if the Enable and Display Modules is set in the Module Codes
Project Preference.)

December 2023
Messages Variables
{0} has a module code expression that violates {0} - Object name
module code relationships, {1} and {2} are not {1} and {2} - Module codes
exclusive
Shield terminating at more than two pins

Identifies shields that are terminated at more than two pins.
Messages Variables
Shield Termination {0} of multicore {1} {0} - Shield name
terminating at more than two pins {1} - Multicore name
Connectors mated to multiple pinlists

This DRC identifies connectors mated to multiple pinlists - connectors or devices within a
single design. This is useful in scenarios where an inline is connected to multiple jacks.
Identified connectors can prevent generation of signal trace data in SmartClient packets.
Messages Variables
Failed to generate click and sprout data - {0} - Connector name
Connector {0} mated to multiple pinlists: {1}, {1} and {2} - Pinlists name
{2} Please check the design data.
Hierarchical block connectivity does not match with associated design

Identifies where block connectivity, including numbers of pins, differs from the connectivity
specified in the associated design.
Messages Variables
One or more conductors between block {0} {0} and {1} - Block names
and block {1} have no route. Please add the
missing highway interface.
Highways connected between block {0} and {0} and {1} - Block names
block {1} do not route any conductors. Please
ensure the target designs use some common
shared conductors.
Incompatible mates on hierarchical block

Identifies when mated blocks have different numbers of pins.

December 2023
Messages Variables
Plug {0} is mated to different types of objects {0} - Plug connector name
on block {1} {1} - Block name
Plug {0} is mated to multiple devices on block {0} - Plug connector name
{1} {1} - Block name
Capital Logic Designer - Consistency DRCs

Design assembly does not match the library assembly

Identifies assemblies with a part number that have child components in the design that are not
defined in the component library. The DRC also checks if the connectivity associated with
design assembly has an older last modified date than its library definition and reports
accordingly.
Messages Variables
Assembly {0} has {1} {2} for which no part {0} - Assembly
assigned {1} - Logic Object Type
{2} - Logic Object
Assembly {0} has {1} Components with part {0} - Assembly
number {2} but it is defined with quantity {3} {1} - Quantity for Assembly Element part
in library assembly details of {4} number in design
{2} - Library Part Number of Assembly
Element
{3} - Library object Quantity for Assembly
element part number in Library
{4} - Assembly Part Number
Assembly {0} has the following components {0} - Assembly
missing from its part number {1} {2} {1} - Assembly Part
Element with Count in brackets
Connectivity associated with assembly {0} has {0} - Assembly
an older last modified date than its library {1} - Assembly Part
definition ''{1}''

December 2023
Hierarchical block pins does not match with associated design pins
Identifies that conductors between blocks do not have a valid route and must be added. Also
identifies instances where multiple blocks either lack shared conductors or have not been
associated to a design that uses shared conductors.
Messages Variables
There are pins in the target design {0} not {0} - Design With Revision
shown on block {1} {1} - Block Device
There are pins on block {0} not available in {0} - Block Device
target design {1}. Pins are {2} {1} - Design With Revision
{2} - BlockDevice pins
Included on BOM with no part number

Identifies objects on the design (connectors or conductors) that have the On BOM flag set for
them but have no part number.
Messages Variables
{0} {1} is on BOM, but no part assigned {0} - Bom Object Type
{1} - BOM Object

Messages Variables
There is {0} pending checklist item {0} - Number for single checklist item
There are {0} pending checklist items {0} - Number of checklist items
Unresolved comments
Messages Variables
There is {0} unresolved comment {0} - Number for single unresolved comment
There are {0} unresolved comments {0} - Number for unresolved comments

December 2023
Assembly item not in a boundary

You can have associated comment graphics for an assembly that can be used to create a
graphical boundary for the assembly on the diagram. This check identifies any diagram objects
that belong to an assembly but do not fall within the bounding box of its associated graphics.
Messages Variables
Assembly {0} contains items not completely {0} - Assembly name
bound inside the associated graphics
Assembly library definition not used in design

Identifies assemblies with a part number but having missing child components (that is, child
components defined in the component library but missing from the assembly in the design).
Messages Variables
Design Assembly {0} has the following {0} - Assembly
components unused from its part number {1}: {1} - Assembly Part
{2}
Design Assembly {0} have {1} components {0} - Assembly
with part number {2} but {3} is defined with {1} - Design Assembly quantity
quantity {4} in assembly details of library part
{5} {2} - Library Element Part number
{3} - Library Element Part Number
{4} - Library assembly Quantity
{5} - Assembly part number

Messages Variables
Symbol {0} is out of date for comment graphic {0} - Symbol
at {2} in {1} {1} - Diagram
{2} - comment Symbol Coordinates
Symbol was not found for comment graphic at {0} - Diagram
{1} in {0} {1} - Comment Symbol Coordinates

December 2023
Electrical symbol requires update

Identifies any symbol that has changed since it was assigned to a library part (causing a
graphical/electrical mismatch between the library part symbol and its corresponding symbol in
the symbol library).
Messages Variables
Symbol for {0} is out of date {0} - Device name
Symbol for {0} was not found {0} - Device name
Mismatch between assembly content and project preference

Identifies assemblies, contained on the design, that comprise of objects that do not match the
default Assembly settings in project preferences.
Messages Variables
Assembly {0} structure is inconsistent with {0} - Assembly
project preferences. The following {1} - Connector or Backshell with count in
components violate the preferences: {1} brackets
Missing or conflicting harness attribute

Identifies objects in a connectivity set that do not have a harness attribute value, and objects
with different values that you might want to preserve, such as harness attribute values on poke
home wires or variant connectors. See also “Propagating Harness Attributes by Connectivity” in
the Capital Logic Designer User Guide.
Note
Devices that are not connected directly (that is, without a connector) to a conductor will not
display DRC errors for missing harness attribute values.
Messages Variables
{0} {1} has an empty harness attribute {0} - Object Type
{1} - Object name hyperlink
{0} {1} has a harness attribute {2} which {0} - Object Type
conflicts with {0} {1} having a harness {1} - Object name hyperlink
attribute {2}
{2} - Harness Attribute Value
Obsolete option
Identifies any obsolete options used on design objects.

December 2023
Messages Variables
{2} {0} uses obsolete option {1} {0} - Any Logic Object
{1} - Option
{2} - Object Type
{3} {0}:{1} uses obsolete options {2} {0} - Pinlist
{1} - Pin
{2} - Options name
{3} - Pin Type (Pin or Backshell Termination)
{1} - Pin
{2} - Options name
{2} {0} uses obsolete options {1} {0} - Any Logic Object
{1} - Options name
{2} - Object Type
Unplaced object
Identifies non-shared objects that are not placed on any diagram. These are displayed in a folder
called Unplaced and there is a project preference to delete all unplaced objects when you save
the design.
Messages Variables
Unplaced{0} {1} {2} {0} - Shared (If its shared object) else empty
{1} - Object Type
{2} - Any logic object (other than Assembly,
Modular Connector, and Shield Conductor Part
of multicore)
Unplaced{0} {1} {2} {0} - Shared (If its shared object) else empty
{1} - Object Type
{2} - Pin Owner : Pin (Pins on Pinlist)
Child overriding parent's attributes/properties

Identifies any objects on the design that have had their Function or Location attributes or
properties manually updated, leading to a mismatch with their parent, whether it is the sector or
diagram (it checks the nearest parent).

December 2023
Messages Variables
{0} {1} is overriding {2}, {3} and {4} from {0} - Pinlist Object Type
parent {5} {6} {1} - Pinlist (Home Object)
{2} - Location
{3} - Function
{4} - Properties
{5} - Parent Type (Sector or Diagram)
{6} - Sector or Diagram
{0} {1} is overriding {2} and {3} from parent {0} - Pinlist Object Type
{4} {5} {1} - Pinlist (Home Object)
{2} - Location or Function or Properties
{0} {1} is overriding {2} from parent {3} {4} {0} - Pinlist Object Type
{1} - Pinlist (Home Object)
Invalid design association on hierarchical block

Identifies that the block is either missing an association to a design, or does not have a valid
association within the active build list.
Messages Variables
Block {0} is not associated to any design. {0} - Block Device name
Please associate this block to a design within
the active build list.
Block {0} does not have a valid association. {0} - Block Device name
Please associate this block to a design within
the active build list.
Multiple instances of pin within the design

Identifies any pins on a design with duplicate names, where project preference “Disallow pin
duplication within a design” is set and prohibits this.

December 2023
Messages Variables
Multiple instances of pin {0} of {1} {2} found {0} - Pin
within design {3} {1} - Pinlist Type
{2} - Pinlist
{3} - Design
Capital Logic Designer - Exclusion DRCs

There are particular design rule checks related to exclusion that you can run for a Capital Logic
Designer design.
Harness connector not defined in device library footprint

Identifies any plug or receptacle connector that is present on the design and not part of a
device's library description.
Messages Variables
{1} {0} is not a device connector {0} - Connector (Other than Device
Connector)
{1} - Connector Type
Wire not allowed

Identifies any wires present on a design in which wires are not permitted (for example, on net
type designs for use with Capital Systems Integrator). The default status for this check is Not
shown.
Messages Variables
Disallowed Wire {0} detected {0} - Wire name
Capital Logic Designer - ICD Consistency DRCs

There are particular design rule checks related to ICD consistency that you can run for a Capital
ICD backshell inconsistency

Identifies inconsistencies between the backshell as placed in Capital Logic Designer, using the
Xpedition flow and its original Capital Device Modeler definition. If the DRC fails, right-click
the device and run the Update From ICD action from the context menu.

December 2023
Messages Variables
ICD defined backshell {0} missing from {0} - Backshell name
harness connector {1} {1} - Connector name
ICD does not define backshell {1}:{0} {0} - Backshell name
ICD defined backshell termination(s) {0} {0} - Backshell termination name
missing from backshell {1} {1} - Connector and Backshell name
ICD does not define backshell termination(s) {0} - Backshell termination name
{0} on backshell {1} {1} - Connector and Backshell name
ICD defined footprint for icd connector {0} {0} - ICD Connector name
does not match against harness connector(s) {1} - Harness connector names
{1}
ICD defined name {0} does not match for {0} - ICD name
backshell {1} {1} - Connector and Backshell name
ICD defined part {0} does not match with part {0} - ICD part name
{1} on backshell {2} {1} - Part name
{2} - Connector and Backshell name
ICD device connector inconsistency

Identifies inconsistencies between the device connector as placed in Capital Logic Designer and
its original Capital Device Modeler definition. If the DRC fails, right-click the device and run
the Update From ICD action from the context menu.
Messages Variables
ICD defined footprint for icd connector {0} {0} - ICD Connector name
does not match against device connector(s) {1} - Device connector names
{1}
ICD defined device connector pin missing for {0} - Pin names
device pin(s) {0}
ICD defined device connector pin name(s) do {0} - Pin names
not match against device pin(s) {0}
ICD does not define device connector against {0} - Pin names
device pin(s) {0}
ICD defined name {0} does not match for {0} - ICD name
device connector {1} {1} - Device connector name

December 2023
Messages Variables
ICD defined part {0} does not match with part {0} - ICD part name
{1} on device connector {2} {1} - Part name
{2} - Device connector name
ICD multicore inconsistency

Identifies inconsistencies between the multicore as placed in Capital Logic Designer and its
original Capital Device Modeler definition. If the DRC fails, right-click the device and run the
Update From ICD action from the context menu.
Note
Prior to SP2012, this DRC would fail if the name of the multicore as placed in Capital Logic
Designer was different to the name in the original Capital Device Modeler definition. From
SP2012 onwards, if the multicore type, structure and inner cores are the same in Capital Logic
Designer and in the Capital Device Modeler definition, the multicore name being different will
not cause this DRC to fail.
Messages Variables
ICD defined net(s) contained within {0} {1} {0} - Multicore
should be in different multicores as defined in {1} - Multicore name
the ICD
Multiple ICD defined multicores {0} match {0} - Comma separated multicores with type in
against {1} {2} brackets
{1} - Multicore
Structure of {0} {1} does not match the ICD {0} - Multicore
definition {2} {1} - Multicore name
{2} - Multicore with Type
The indicator type(s) for {0} {1} do not match {0} - Multicore
the ICD definition {2} {1} - Multicore name
{2} - Multicore with Type
The {0}(s) {1} should not be contained within {0} - Multicore(s)
the same parent {2} {3} as defined in the ICD {1} - Multicore name
{2} and {3} - Multicore names
ICD defined multicores {0} contained within {0} - Multicore with type
{1} {2} should be in different multicores {1} - Multicore with type

December 2023
Messages Variables
Some of ICD defined multicore {0}(s) {1} are {0} - Multicore(s)
missing at {2} {3} {1} - Multicore name
{2} and {3} - Pinlist with pins
ICD defined {0}{1} missing at {2} {3} {0} - Multicore net(s)
{1} - Multicore net name
ICD defined multicore {0}(s) {1} missing at {0} - Multicore(s)
{2} {3} {1} - Multicore name
{0} implementing ICD {1}(s) {2} should be in {0} - Conductors names
separate multicores {1} - ICD Signal(s)
{2} - Signal name
ICD part number mismatch

Identifies that the part number assigned to an ICD does not match with the ICD placed in the
Messages Variables
Part number mismatch for ICD {0} in design {0} - ICD name
{1} {1} - Design name
Supplier part number mismatch for ICD {0} in {0} - ICD name
design {1} {1} - Design name
Customer part number mismatch for ICD {0} {0} - ICD name
in design {1} {1} - Design name
Footprint mismatch for ICD {0} in design {1} {0} - ICD name
{1} - Design name
The type code of device {0} in design {1} {0} - ICD name
does not match the ICD definition {1} - Design name
The type description of device {0} in design {0} - ICD name
{1} does not match the ICD definition {1} - Design name

December 2023
ICD pin signal connectivity inconsistency

Identifies if an ICD is placed and any of its pins have an associated signal that are either not
connected or connected to the wrong signal. It also checks connectivity mismatches with
traversal through splitters such as inlines connectors or devices with internal connectivity.
Note
This DRC can also be set to run in Background mode.
Messages Variables
ICD defined signal(s){0}missing at pin{1} {0} - Signals name
{1} - Pin name
{3} {4} defined on ICD ''{2}'' {5} missing at {0} - Device name
device ''{0}'' in design ''{1}'' {1} - Design name
{2} - ICD name
{3} - Pin
{4} - Pin name
{5} - ICD pin name
{3} {4} defined on ICD ''{2}'' {5} missing at {0} - Device name
device ''{0}'' in design ''{1}'' {1} - Design name
{2} - ICD name
{3} - Pins
{4} - Comma separated Pin names
{5} - ICD pin name
ICD defined connectivity is missing between {0} - List of Devices with Pins names
{0}
Invalid release level on ICD

Identifies if the release level behavior of a placed ICD in Capital Logic Designer does not
support ‘ICD Design Association.’
Messages Variables
Release level on ICD {0} used in design {1} {0} - ICD name
does not allow design association {1} - Design name
Multiple ICD definitions exist

Identifies if more than one definition of an ICD exist.

December 2023
Messages Variables
For the current context multiple ICDs:{0} with {0} - List of ICDs name
role {1} are applicable {1} - Role of ICD
For the current context multiple devices are {0} - Role of ICD
placed for an ICD with role {0}
ICD not associated

When you place/update an ICD, the system stores the current references to ICD(s) in a property
“ASSOCIATED ICD(s)” on the device.
This DRC identifies and reports when the property, refers to one or more ICDs which either do
not exist in the system, are not applicable to the design, have a release level not containing the
'ICD Design Association' behavior, refers to a Role of ICD that no longer matches the Device
Name, has a mismatch in Effectivity.
See Eligibility Criteria, in the Capital Logic Designer User Guide.

Messages Variables
Device {0} has property “Associated ICD(s)” {0} - Device name
referring to ICD(s) {1} which do not exist in {1} - ICD name
the system
referring to ICD(s) {1} which are not {1} - ICD name
applicable to the design
referring to ICD(s) {1} which do have a {1} - ICD name
release level not containing the “ICD Design
Association” behavior
referring to ICD(s) {1} whose role is different {1} - ICD name
than the name of device
referring to ICD(s) {1} which have different {1} - ICD name
effectivity than the design
ICD option expression and property mismatch

Identifies where option expressions and properties differ from those specified in Capital Device
Modeler suggesting that the ICD should be updated to reflect the latest version.

December 2023
Messages Variables
Option Expression of {0}:{1} in design:{2} {0} - Conductor Type (Wire or Net)
does not match the option expression defined {1} - Conductor
in ICD:{3},Pin:{4},Signal:{5}
{2} - Design
{3} - ICD
{4} - ICD Pin
{5} - Signal
Option expression on {0}:{1} in design:{2} is {0} - Conductor Type (Wire or Net)
not applicable to design {1} - Conductor
{2} - Design
Value ''{7}'' of property:''{6}'' of {0}:{1} in {0} - Conductor Type (Wire or Net)
design:{2} does not match the value ''{8}'' {1} - Conductor
defined in ICD:{3},Pin:{4},Signal:{5}
{2} - Design
{3} - ICD
{4} - ICD Pin
{5} - Signal
{6} - Property Name
{7} - Property Value
{8} - ICD Property Value
Property ''{6}'' defined on {0} - Conductor Type (Wire or Net)
ICD:{3},Pin:{4},Signal:{5} is missing on {1} - Conductor
{0}:{1} of design:{2}
{2} - Design
{3} - ICD
{4} - ICD Pin
{5} - Signal
{6} - Property Name
Value ''{5}'' of property:''{4}'' of {2}:{0} in {0} - Conductor
design:{1} does not match the value ''{6}'' {1} - Design
defined on Signal:''{3}'' in dictionary
{2} - Conductor Type (Wire or Net)
{3} - Signal
{4} - Property Name

December 2023
Messages Variables
Property ''{4}'' defined on Signal:''{3}'' in {0} - Conductor
dictionary is missing on {2}:{0} of design:{1} {1} - Design
{2} - Conductor Type (Wire or Net)
{3} - Signal
{4} - Property Name
Option expression of device:{0} in design:{1} {0} - Device
does not match the option expression defined {1} - Design
in ICD:{2}
{2} - ICD
Option expression of device:{0} in design:{1} {0} - Device
is not applicable to design {1} - Design
Property ''{0}'' is not required on device ''{1}'' {0} - Propety Name
in design ''{2}'' as there is no ICD associated {1} - Device
with this device
{2} - Design
The property ''{0}'' and its ICD value(s) is {0} - Propety Name
missing on device ''{1}'' in design ''{2}'', {1} - Device
perform ''Update from ICD'' to rectify
{2} - Design
Property ''{0}'' defined with value ''{1}'' on {0} - Propety Name
device ''{2}'' in design ''{3}'' does not match {1} - Property Value
with its associated ICD(s) ''{4}'', perform
''Update from ICD'' to rectify {2} - Device
{3} - Design
{4} - ICD's
Value ''{4}'' of property:''{3}'' of device:{0} in {0} - Device
defined in ICD:{2}
{2} - ICD
{3} - Property Name
Property ''{3}'' defined on ICD:{2} is missing {0} - Device
on device:{0} of design:{1} {1} - Design
{2} - ICD
{3} - Property Name

December 2023
Messages Variables
defined in 'library part':{2}
{2} - Library Part
{3} - Property Name
{5} - Library Property Value
Property ''{3}'' defined on 'library part':{2} is {0} - Device
missing on device:{0} of design:{1} {1} - Design
{2} - Library Part
{3} - Property Name
defined in dictionary
{2} - Property Name
Property ''{2}'' defined in dictionary is missing {0} - Device
on device:{0} of design:{1} {1} - Design
{2} - Property Name
Option expression of device:{0},pin:{1} in {0} - Device
design:{2} does not match the option {1} - Pin
expression on ICD:{3},Pin:{4}
{2} - Design
{3} - ICD
{4} - ICD Pin
Option expression of device:{0},pin:{1} in {0} - Device
design:{2} is not applicable to design {1} - Pin
{2} - Design
Value ''{6}'' of property:''{5}'' of {0} - Device
device:{0},pin:{1} in design:{2} does not {1} - Device Pin
match the value ''{7}'' defined in ''library
part'':''{3}'',pin:''{4}'' {2} - Design
{3} - Library Part
{4} - Library Pin
{5} - Property Name
{7} - Library Property Value

December 2023
Messages Variables
Property ''{5}'' defined on ''library {0} - Device
part'':''{3}'',pin:''{4}'' is missing on {1} - Device Pin
device:{0},pin:{1} of design:{2}
{2} - Design
{3} - Library Part
{4} - Library Pin
{5} - Property Name
Value ''{6}'' of property:''{5}'' of {0} - Device
device:{0},pin:{1} in design:{2} does not {1} - Device Pin
match the value ''{7}'' defined in ICD:{3}
pin:{4} {2} - Design
{3} - ICD
{4} - ICD Pin
{5} - Property Name
Property ''{5}'' defined on ICD:{3},Pin:{4} is {0} - Device
missing on device:{0},pin:{1} of design:{2} {1} - Device Pin
{2} - Design
{3} - ICD
{4} - ICD Pin
{5} - Property Name
Unplaced ICD
Identifies if ICDs are applicable for the design and are not placed.
Messages Variables
ICD {0} is applicable but not placed in design {0} - ICD
{1} {1} - Design
ICD {0} is applicable but not placed in designs {0} - ICD
{1} {1} - Designs
ICD {0} is applicable but not placed in {0} - ICD
buildlist

December 2023
Capital Logic Designer - Inclusion DRCs

There are particular design rule checks related to inclusion that you can run for a Capital Logic
Designer design.
Missing symbol for device

Identifies devices on the design that do not possess a symbol.
Messages Variables
Device {0} has no symbol {0} - Device name
Capital Logic Designer - Library Consistency DRCs

Incompatible mated connector

Identifies:
• When mated connectors have different numbers of pins.

• When the library parts assigned to mated connectors have different numbers of pins.
• When a mated connector does not have a library part assigned.
Messages Variables
Mated connectors {0} and {1} have {0} and {1} - Connectors
incompatible number of pins
Library parts for mated connectors {0} and {0} and {2} - Connectors
{2} have incompatible number of cavities ({1} {1} and {3} - Respective Library Part
and {3}) Numbers
{1} {0} refers to a library part that does not {0} - Connector
exist {1} - Connector Type
{0} and {1} are mated in design but their {0} and {1} - Connectors
library parts are not mated

December 2023
Invalid library footprint

Identifies devices that have library parts with footprints where the footprint data on the device is
out-of-sync with the footprint definition in Capital Component Manager, and where not all pins
of the device have been assigned to a footprint cavity. In addition the DRC also:
• Checks that all the device/harness connectors defined in the footprint are available on
device.
• The footprintconnectorname attribute on harness connector is also checked.
• The cavity versus pins match for each harness/device connector.
• The part-number on these connectors.
• The device-pin and device-connector-pin mating is also checked.
• For footprints of device-connector type the mated connectors (as defined on the
footprint connector) part number mismatch is also checked.
Messages Variables
Attribute "Footprint Connector Name" of {0} - Connector name
connector {0} does not match library
definition
Part number "{0}" on connector "{1}" does {0} - Part number
not match with the library footprint definition {1} - Connector name
Device {0} has no pins placed on design {0} - Device name
Device {0} has Device Pins unmapped in {0} - Device name
Footprint definition
Device {0} references a Footprint that no {0} - Device name
longer exists
Device {0} has no referenced Footprint {0} - Device name
Pinmaps in Library
Device {0} has a Footprint type conflicting {0} - Device name
with Library definition
Device {0} has different number of Device {0} - Device name
Pins than required by the Footprint
Device {0} has a different number of Device {0} - Device name
Connectors than that in Footprint
Device {0} has Device Connector names {0} - Device name
inconsistent with the Footprint Connector
names

December 2023
Messages Variables
Device {0} has Device Connector(s) that do {0} - Device name
not reference the correct Footprint
connector(s)
Device {0} has Device Connector(s) with a {0} - Device name
different number of Pins than the Footprint
Connector(s)
Device {0} has Device Connector(s) with {0} - Device name
different Pin names than the Footprint
Connector(s)
Device {0} has a Pin mapping inconsistent {0} - Device name
with the Footprint
Invalid library pin mapping

Identifies invalid mappings between library part cavities and object pins in a design.
Messages Variables
{1} {0} references library part {2} that conflicts with {0} - Pinlist (Other than connector
its symbol assembly)
If a library part and symbol are identified on a device, {1} - Pinlist Type
the check reports a mismatch between the number of {2} - Library Part Number
pins on the symbol and the number of cavities on the
library part.
{1} {0} has no symbol, references library part {2} that {0} - Pinlist (Other than connector
has a symbol assembly)
Device on the diagram has no symbol but the assigned {1} - Pinlist Type
library device part number has a symbol. {2} - Library Part Number
Library referenced {1} {0} has one or more cavities {0} - Pinlist (Other than connector
({2}) not present in library part assembly)
Device pins on the diagram include a pin name that is {1} - Pinlist Type
not specified on the assigned library device part {2} - Pins
number.
Library referenced {1} {0} has one or more unplaced {0} - Pinlist (Other than connector
cavities ({2}) assembly)
For each pin on the library device part number {1} - Pinlist Type
assigned to a device, there must be a cavity with a {2} - Pins
matching name on the diagram.
If the device is shared and there are pins reserved for
this design, the check is limited to the reserved pins
only.

December 2023
Messages Variables
{1} {0} has pin {2} with attribute "{3}" that does not {0} - Pinlist (Other than connector
match referenced library part "{4}" assembly)
For each pin attribute value on a device, there must be {1} - Pinlist Type
an assigned library connector with a matching cavity {2} - Pin
attribute value on the diagram.
{3} - Attribute
{4} - Library Part
Pin {0}:{1} mated with {2}:{3} does not match {0} - Plug Connector
mapping in library for {4} {1} - Plug Connector Pin
If the following are identified: {2} - Connector
• Library connector part numbers are assigned to {3} - Connector Pin
both a mated plug and jack connector on the
diagram. {4} - Library Part
• Library connector mating is defined in the library
between the two library connector part numbers.
The check reports a mismatch between the mated pin
name pairs on the diagram and the mated cavity name
pairs in the library mating.
Invalid library reference

Identifies objects (devices, connectors, wires, nets, splices, multicores, shields, and so on.) on
the design that reference library parts that do not exist in the library databases (for example, as a
result of an imported project).
Messages Variables
{1} {0} refers to a library part that does not {0} - Logic Object
exist {1} - Object Type
{1} {0} has part number \"{2}\" that does not {0} - Logic Object
exist in your library {1} - Object Type
{2} - Library Part Number
Invalid library symbol

Identifies objects (devices, connectors, wires, nets, splices, multicores, shields, and so on.) on
the design that reference symbols that do not exist in the symbol library (for example, as a result
of a deleted symbol) or that reference a symbol that is not associated with the assigned library
part.

December 2023
Messages Variables
{1} {0} symbol conflicts with part number {2} {0} - Pinlist
symbol {1} - Pinlist Type
{1} {0} refers to a library part that does not {0} - Pinlist
exist {1} - Pinlist Type

Identifies pin count mismatches between connectors (plugs or receptacles) on the design and
their corresponding library part.
Messages Variables
{1} {0} pin count conflicts with part number {0} - Connector
{2} cavity count {1} - Connector Type
{1} {0} refers to a library part that does not {0} - Connector
exist {1} - Connector Type
Library multicore mismatch

Identifies multicores with mismatches between the number of conductors in their library
association and that specified on the design.
Messages Variables
Multicore {1} is missing {2} required for {0} - Multicore Library Part
library part {0}. {1} - Multicore
{2} - Conductor or Multcore based on sheath
type With Attributes (Material,Spec,Color)
Multicore {0} contains {1} {2} not accounted {0} - Multicore
for in library part {3} {1} - Inner Core type (Multicore or Conductor)
{2} - Inner core (Multicore or Conductor)
{3} - Library Part
Multicore {0} refers to a library part that does {0} - Multicore
not exist
Attributes of {0} "{1}" does not match with its {0} - Multicore Type
library part "{2}" {1} - Multicore
{2} - Library Part

December 2023
Messages Variables
Attributes of innercore {0} {1} of "{2}" does {0} - Inner Core type (Multicore or Conductor)
not match with its library part "{3}" {1} - Inner core (Multicore or Conductor)
{2} - Multicore
{3} - Library Part
Innercore {0} {1} of multicore "{2}" does not {0} - Inner Core Conductor type
match with its conductor role in library part {1} - Inner core Conductor
"{3}"
{2} - Multicore
{3} - Library Part

Messages Variables
{0} {1} has P/N={2} assigned to it, but that is {0} - Object Type
not the latest {1} - Any Logic Library Object
{2} - Part Number

Messages Variables
Status of library part for {0} {1} is ''{2}'', not {0} - Object Type
current {1} - Any Logic Library Object
{2} - Part Status

Examines the cavities of connectors and ring terminals with a library part, and considers all
combinations of each cavity with its connected conductors (wires, nets, and shields), and
identifies the following:
cavity.or
on the cavity.

December 2023
The design rule check is not applied to shared connectors and ring terminals. See the equivalent
“Wires fit shared cavity mismatch” check for shared components on the Build List tab.
Messages Variables
Wire {3} does not fit cavity {2} on connector {1} - Connector name
cavity and the values defined on the Single
Wires {3} do not fit cavity {2} on connector {1} - Connector name
cavity and the values defined on the Multiple
and accepts wires {3} {2} - Cavity name
library (Multiple wires).
and accepts wire {3} {2} - Cavity name
library (Single wire).

December 2023
Messages Variables
Ring terminal {1} does not fit wire {3} {1} - Ring terminal name
Ring terminal has a library terminal assigned {3} - Wire name
terminal part on wire (Single wire).
Ring terminal {1} does not fit wires {3} {1} - Ring terminal name
Ring terminal has a library terminal assigned {3} - Wire names
terminal part on wires (Multiple wires).
Notes on Options and Design Rule Checks in Capital Logic Designer

The relationship of option expressions assigned to objects is not considered in Capital Logic
Designer designs while running the Design Rule Checks (DRCs) because a single design can
contain data for multiple configurations. For example, a single wiring design can represent the
wiring for both a Left Hand Drive (LHD) and Right Hand Drive (RHD) configuration.
An object that is present in Capital Logic Designer is always considered as available in the
logical design, and actual simplification happens in the downstream applications on certain
actions, for example, during Harness processing, Capital Systems Integrator synthesis, or Auto
view assist functionality.
You can filter objects or generate wiring designs that support a particular configuration before
running certain actions, but DRCs are run on the set of objects that are present in the design to
check the final design state before it can be used. In certain scenarios, such as the “Wire fits
cavity mismatch” DRC, an error is returned even though wires are marked for two different
configurations; are mutually exclusive; and will never be in the cavity at the same time. In this
situation you can ignore the error.

following:
accept wires.

December 2023
The design rule check is not applied to shared connectors and ring terminals. See the equivalent
“Wires fit shared cavity mismatch” check for shared components on the Build List tab.
Messages Variables
attribute terminal part at connector {1} cavity {2} - Cavity name
{2}:{3}
{3} - Wire names
wires are different.
attribute terminal material at connector {1} {2} - Cavity name
cavity {2}:{3}
{3} - Wire names
are different.
Terminal {2} on wire(s) {5} is not defined for {2} - Terminal part
Terminal part on the wire is not present in the {3} - Cavity name
housing definition of the library part.
Terminal {5} in cavity {2} of connector {1} {5} - Terminal part
does not accept wire(s) {3} {2} - Cavity part
Same terminal part exists on both the wire and {1} - Connector name
profiles exist on terminal part in the library. {3} - Wire names
attribute seal part at connector {1} cavity {2} - Cavity name
{2}:{3}
{3} - Wire names
are different.
Seal {2} on wire(s) {5} is not defined for {2} - Seal part
Seal part on the wire is not present in the {3} - Cavity name
housing definition.
Seal {5} in cavity {2} of connector {1} does {5} - Seal part
not accept wire(s) {3} {2} - Cavity part
Seal part on the wire and in the housing {1} - Connector name
definition match, but the seal part has no wire
fit profiles. {3} - Wires names

December 2023
Notes on Options and Design Rule Checks in Capital Logic Designer

The relationship of option expressions assigned to objects is not considered in Capital Logic
Designer designs while running the Design Rule Checks (DRCs) because a single design can
contain data for multiple configurations. For example, a single wiring design can represent the
wiring for both a Left Hand Drive (LHD) and Right Hand Drive (RHD) configuration.
An object that is present in Capital Logic Designer is always considered as available in the
logical design, and actual simplification happens in the downstream applications on certain
actions, for example, during Harness processing, Capital Systems Integrator synthesis, or Auto
view assist functionality.
You can filter objects or generate wiring designs that support a particular configuration before
running certain actions, but DRCs are run on the set of objects that are present in the design to
check the final design state before it can be used. In certain scenarios, such as the “Wire cavity
component mismatch” DRC, an error is returned even though wires are marked for two
different configurations; are mutually exclusive; and will never be in the cavity at the same
time. In this situation you can ignore the error.
Device Housing Definition mismatch

Identifies jumper devices that not configured in the housing definition of the device that they are
mated with.
Messages Variables
Device {0} cannot be found in device {1} {0} and {1} - Device name
housing definition

Identifies connectors or conductors whose component library definitions have changed so that
the On BOM status is now different.
Messages Variables
{0} {1} 's Include On Bom status is different {0} - Logic Object Type
to its library part. {1} - Any Logic Library Object
Invalid ring terminal on stud pin

Checks the validity of library parts on ring terminals connected to stud pins. The check
examines the stud pin and reads the valid ring terminal associated from the ring terminal group
to ensure that any mated ring terminals are in that group. It reports an error if:
• If the stud pin has a housing definition defined in the library, but its mated ring terminal
does not have a library part.

December 2023
• If the stud pin has a housing definition defined in the library, but the library part of its
mated ring terminal does not match any of the parts defined in the housing.
• If the device has a stud pin for which no library housing definition is defined in the
library.
Messages Variables
Part Number "{0}" on "{1}" mated to stud pin {0} - Part number
"{2}:{3}" is inconsistent with library housing {1} - Ring terminal name
definition
{2} - Device name
{3} - Stud pin name
Incorrect connector type mated to stud pin {0} - Device name
"{0}:{1}" {1} - Stud pin name
Stud pin "{0}:{1}" does not have library {0} - Device name
housing definition {1} - Stud pin name
Library part required for device

Identifies devices on the design that do not possess a library part.
Messages Variables
Device {0} has no library part {0} - Device name
Modular connector structure does not match library definition

Identifies instances with blocked cavities that do not match the Library definition for the
component. To update the library part, on the General tab of the Properties Dialog Box, click
Update to the right of the Library Part field. You can observe the change to the number in
parentheses in the Position list on the Modular tab.
Messages Variables
Position "{0}" of purchased connector {1} is {0} - Position
empty {1} - Connector name
Component "{0}" occupies position "{1}" {0} - Component part
which is not defined in the housing definition {1} - Position
of "{2}"

December 2023
Messages Variables
Connector {0} at {1}:{2} is not blocking any {0} - Connector name
cavity of its parent, but in Library it blocks {1} - Connector name
cavity "{3}"
{2} - Pin name
{3} - Cavity
Connector {0} at {1}:{2} is blocking cavity {0} - Connector name
"{3}" of its parent, but in Library it blocks {1} - Connector name
cavity "{4}"
{2} - Pin name
{3} and {4} - Cavity
Connector {0} at {1}:{2} is blocking cavity {0} - Connector name
"{3}" of its parent, but in Library it does not {1} - Connector name
block any cavity
{2} - Pin name
{3} - Cavity
No conductor library part available

Identifies conductors for which the combination of specification attribute values (specified on
the General tab of the Edit Properties facility) does not exist in any library wire size definitions.
Messages Variables
Specification attributes combination for {0} {0} - Conductor
does not exist in Library wire size definitions

Messages Variables
Library part {0} of {1} {2} has invalid {0} - Library Part Full Name
scoping. Component Scoping: {3}.{4} {1} - Object Type
Scoping: {5}
{2} - Logic Object (Library Object)
{3} - Component Scopes
{4} - Design or Project
{5} - Design or Project scopes

December 2023
Messages Variables
Library part {0} of {1} {2}:{3} has invalid {0} - Library Part Full Name
scoping. Component Scoping:{4}. {5} {1} - Object Type (BackShell)
Scoping: {6}
{2} - Connector
{3} - Backshell
Library part {0} of {1} {2}:{3} has invalid {0} - Library Part Full Name
scoping. Component Scoping: {4}.{5} {1} - Object Type (BackShell)
Scoping: {6}
{2} - Connector
{3} - Backshell
Ring terminal with connector part number

Issues a warning where ring terminal objects exist with connector part numbers assigned.
Messages Variables
Ring terminal {0} has a connector library part {0} - Ring Terminal
{1} attached {1} - Library Part Full name
Capital Logic Designer - Logic Rules DRCs

There are particular design rule checks related to logic rules that you can run for a Capital Logic
Designer design.

Identifies any objects that violate any “Set Logic Attribute/Property on Object” constraints.

December 2023
Messages Variables
{0} {1} violates Attribute/Property constraint; {0} - Object Type
{2} should be {3} {1} - Logic Object
{2} - Attribute or Property Name
{3} - Attribute or Property Value
{0} {1} violates Attribute/Property constraint; {0} - Object Type
{2} is missing {1} - Logic Object
Pin {0} on {1} {2} violates Attribute/Property {0} - Pin
constraint; {3} should be {4} {1} - Pinlist Type
{2} - Pinlist
{4} - Attribute or Property Value
Pin {0} on {1} {2} violates Attribute/Property {0} - Pin
constraint; {3} is missing {1} - Pinlist Type
{2} - Pinlist
Capital Logic Designer - Naming DRCs

There are particular design rule checks related to naming that you can run for a Capital Logic
Designer design.
Invalid name for component

Identifies objects with names that do not appear in the list of valid names for the project's object
type.
Messages Variables
Invalid name: {0} is not on the list of valid {1} {0} - Non-Shared Logic Object
names {1} - Object Type
Duplicate Names for Shared Objects in Project

Identifies shared objects (devices, connectors, wires, nets, splices, multicores, and so on.)
having a name that is identical to that of another shared object of the same kind in the project
but having different option expressions. The default status for this check is true, and its default

December 2023
severity setting is error. The check works in conjunction with the Uniqueness project
preference.
Messages Variables
{0}{1} and {2}{3} have duplicate names. {0} and {3} - Any Shared Object(Other than
Highways)
{1} and {4} - Object Type
{2} and {5} - Design Name
Duplicate Names in Design

Identifies objects (devices, connectors, wires, nets, splices, multicores, and so on.) having a
name that is identical to that of another object of the same kind on the same design or a shared
object of the same kind but having different option expressions. The default status for this check
is true, and its default severity setting is error. The check works in conjunction with the
Uniqueness project preference.
Messages Variables
{0}{1} and {2}{3} have duplicate names. {0} and {3} - Any Logic Object (Other than
Highways)
{1} and {4} - Object Type
{2} and {5} - Design Name
Invalid name for shared object

Identifies, within the selected design, shared objects with names that do not appear in the list of
valid names for that project's shared object type. Note: If a shared net is connected to more than
one device with a Usage definition and these devices are split across multiple designs, it is
possible that this check will give incorrect results. In this case, the “Invalid name for shared
object” check, listed under Build List checks will give a more accurate result.
Messages Variables
Invalid name: {0} is not on the list of valid {1} {0} - Shared Object
Invalid short description

Identifies any object for which the short description has been changed in the object type
information in Capital Project Manager but this change has not been applied in Capital Logic
Designer.

December 2023
Messages Variables
The short description of {1} {0} is invalid {0} - Logic Object (Any logic Object with
Short Description)
{1} - Object Type
The short description of object {0} is invalid {0} - General logic Object

December 2023
Design Rule Checks Applicable to Capital Harness

Designer and Capital Harness Designer Modular Designs
There are specific design rule checks that you can run while editing a design in Capital Harness
Designer and Capital Harness Designer Modular.
Capital Harness Designer and Capital Harness Designer Modular - Appearance DRCs
353
Capital Harness Designer and Capital Harness Designer Modular - Connectivity DRCs
354
Capital Harness Designer and Capital Harness Designer Modular - Consistency DRCs
356
Capital Harness Designer and Capital Harness Designer Modular - General DRCs . . 384
Capital Harness Designer and Capital Harness Designer Modular - Harness Designer
Rules DRCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Capital Harness Designer and Capital Harness Designer Modular - Inclusion DRCs . 386
Capital Harness Designer and Capital Harness Designer Modular - Library Consistency
DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391
Capital Harness Designer and Capital Harness Designer Modular - Naming DRCs . . 400
Capital Harness Designer and Capital Harness Designer Modular

- Appearance DRCs
Harness Designer / Modular design.

Identifies:
• Where a translatable term has been used but no translation exists for the active language
so the quick code is displayed.
• Where a translatable term has been entered as free text and has no link to the language
database.
Messages Variables

December 2023
Messages Variables

non-UNICODE font.
Messages Variables
{2} - Font type

Messages Variables

- Connectivity DRCs
Empty multicore
Identifies multicores exist that do not contain any wires.
Messages Variables
{0} {1} does not contain any Wires {0} - Context of object - Multicore
{1} - Multicore name hyperlink
Unconnected wire
Identifies wires are unconnected at one or both ends.

December 2023
Messages Variables
{0} {1} is not connected at both ends {0} - Context of object - Wire
{1} - Wire name hyperlink
{0} {1} is not connected at one end. {0} - Context of object - Wire
Unterminated bundle
Identifies bundles are unconnected at one or both ends.
Messages Variables
{1} {0} has the same start and end node at {2} {1} - Context of object - Bundle
{0} - Bundle name hyperlink
{2} - Node name hyperlink
{1} {0} has an unconnected end at {2} {1} - Context of object - Bundle
Unterminated wire end

Checks single and multiple wire CSA, with regard to cavity terminal and single / multi
terminations. There must be a termination for each wire.
Messages Variables
{0} {1} belongs to a combination with no {0} - Context of object - Wire
terminal at {2} {3} {1} - Wire name hyperlink
{2} - Type of owning object of cavity
{3} - Owning object name hyperlink
{0} {1} has no terminal at {2} {3} {0} - Context of object - Wire
Wire with zero strip length

Checks if the wire instance has zero strip length following harness processing.

December 2023
Messages Variables
{0} {1} has no strip length at {2} {3} {0} - Context of object - Wire
{0} {1} has no strip length at Splice {2} {0} - Context of object - Wire
{2} - Splice name hyperlink
{0} {1} has no strip length at wire end {2} {0} - Context of object - Wire
{2} - Wire end number
Empty bundle
The system checks the routes of all bundles and lists those without wires or multicores.
Messages Variables
{0} {1} does not contain any wires {0} - Context of Object - Bundle

- Consistency DRCs
Blank terminal material driver

Identifies any connector, backshell, device, or ring terminal with no Terminal Material Driver
specified.
Messages Variables
Cavity {1} has a blank terminal material at {0} {1} - Type of parent Connector, Device, Ring
"{2}" Terminal
{0} - Cavity name hyperlink
{2} - Name of parent

December 2023
Bundle arc below minimum bend radius

Identifies bundles that contain an arc with a bend radius lower than that specified in its
minimum bend radius value.
Messages Variables
Bundle {0} has an arc segment with radius less {0} - Bundle name hyperlink
than minimum bend radius of the bundle
Centerstrip splice not on wire route

Checks the route of all wires with center strip. The corresponding splice node should fall on the
route.
Messages Variables
Centre Strip {0} "{1}" is not on the route of {0} - Context of object - "Splice"
Wire "{2}" {1} - Splice name hyperlink
{0} "{1}" route is not available {0} - Wire name hyperlink
{1} - Wire route
Component not located on any bundle

Checks if there is any component that exists on a node which is not on any bundle.
Messages Variables
{0} {1} at {2} {3} is not on any branch {0} - Type of MLC, Node Multi-Location
Component
{1} - Multiple Location name hyperlink
{2} - Location, Node
{3} - Hyperlink to location
{0} {1} is not on any branch {0} - Type of component, Connector
{1} - Component name Hyperlink
Connector route does not exist in library definition

Identifies if routes assigned to a connector on the design do not match the routes defined in
Capital Component Manager.

December 2023
Messages Variables
{0} {1} route is not consistent with connector {0} - Context of object - "Wire"
{2} library part {1} - Wire name hyperlink
{2} - Connector name hyperlink
Critical dimension has a graphical representation

Compares the Critical Dimensions listed in the Design browser with the Critical dimensions
shown across all the diagrams in the design. If a Critical dimension is not displayed on a
diagram, a message reports the diagram name and the end nodes for the missing critical
dimension.
Note
You can ignore the DRC error messages if all the Critical dimensions you require are
displayed on the diagram.
Messages Variables
Missing critical dimension between {0} and {0} - Node name hyperlink
{1} on diagram {2} {1} - Node name hyperlink
{2} - Diagram name hyperlink
Design assembly does not match the library assembly

Detects if a main node component is present in the design assembly, but not present in assembly
details.
Messages Variables
Assembly {0} has {1} {2} for which no part {0} - Assembly
assigned {1} - Logic Object Type
{2} - Logic Object
Assembly {0} has {1} Components with part {0} - Assembly
number {2} but it is defined with quantity {3} {1} - Quantity for Assembly Element part
in library assembly details of {4} number in design
Element
{3} - Library object Quantity for Assembly
element part number in Library
{4} - Assembly Part Number

December 2023
Messages Variables
Assembly {0} has the following components {0} - Assembly
missing from its part number {1} {2} {1} - Assembly Part
Connectivity associated with assembly {0} has {0} - Assembly
an older last modified date than its library {1} - Assembly Part
definition ''{1}''
Different graphical and physical bundle lengths

On a full scale diagram, if the bundle is made flexible and it is stretched, this DRC will identify
the difference between the physical and graphical length.
Messages Variables
{0} {1} has different physical ({2}) and {0} - Context of object - "Bundle"
graphical length ({3}) in {4} {1} - Bundle name hyperlink
{2} - Bundle physical length
{3} - Bundle graphical length
{4} - Diagram name hyperlink
Included on BOM with no part number

Identifies any objects that are marked as include on BOM but have no part assigned
Messages Variables
{0} {1} is on BOM, but no part assigned {0} - Context of object - "Wire"
Insulation run associated bundle validity

Identifies Associated Bundles that are shorter than the insulation run, irrespective of the
position of Associated bundle nodes or intersections with the main insulation graphic.
Messages Variables
Associated bundle {0} length is shorter than {0} - Bundle name hyperlink
parent Insulation Run {1}. Associated Bundle {1} - Insulation run name hyperlink
length: {2} Parent Insulation Run length: {3}
{2} - Bundle Length value
{3} - Insulated Length value

December 2023
Invalid variant position

Evaluates all object’s variant positions against the derivative options and validates all object
positions on a bundle is within the bundle length limit for each derivative.
Messages Variables
Cyclic variant positions are detected for {1} - Bundle name hyperlink
bundle {1} on the child {0} {0} - Design name + ":" + Design Part number
+ ":" + Design Revision
Can not validate the node position of {1} as {1} - Object name hyperlink
cyclic variant positions are detected for bundle {2} - Bundle name hyperlink
{2} in the child {0}
{0} - Design name + ":" + Design Part number
{1} will be placed outside of bundle {2} on the {1} - Object name hyperlink
child {0} {2} - Bundle name hyperlink
{0} - Design name + ":" + Design Part number
Invalid wire attributes versus library definition

Checks that the specified color, material and specification of the wire exist and are consistent
with the applicable component library codes.
Messages Variables
{0} {1} has invalid definition {0} - Context of object - "Wire"
Invalid wire route

Checks the route on the wire.
Messages Variables
{0} {1} route is not consistent with {2} {3} {0} - Context of object - "Wire"
library part at Cavity {4} {1} - Wire name hyperlink
{2} - Context of parent object, "Connector"
{3} - Parent Object name hyperlink
{0} {1} does not terminate at both ends {0} - Context of object - "Wire"

December 2023
Mid-bundle component with multiple locations in the same child

Evaluates all object’s variant positions against the derivatives to find those having multiple
positions for the same derivative.
Messages Variables
{0}: {2} has multiple variant positions {0} - Context of Object, "Grommet"
applicable on the child {1} {2} - Object name hyperlink
{1} - Design Name + ":" + Design Part
Number + ":" + Design Revision
Multiple components at position

Checks if there is more than one additional component occupying the same position.
Messages Variables
There are multiple positioned components. {0} - Derivative name text
Derivative: {0}, Position: {1}, {2}: {3}, {1} - Position text
Positioned Components: {4}
{2} - Context of Object, "Connector"
{3} - Object name text
{4} - Positioned Component Part Numbers
(list)
There are multiple positioned components. {0} - Position text
Position: {0}, {1}: {2}, Positioned {1} - Context of Object, "Connector"
Components: {3}
{3} - Positioned Component Part Numbers
(list)
Multiple instances for variant position object on a derivative

Identifies if a variant position connector or splice exists at more than one position within the
same derivative.

December 2023
Messages Variables
Derivative {0} contains multiple VPXs: {2} {0} - Derivative Name text
{3} {4} {5} {6} {7} {8} {9} {10} {11} for {2} - Primary Position Object Name hyperlink
primary position object: {1}
{3} - Variant Position Object Name hyperlink
(1 of 10)
(2 of 10)
(3 of 10)
(4 of 10)
(5 of 10)
(6 of 10)
(7 of 10)
(8 of 10)
(9 of 10)
(10 of 10)
Multiple variant bundles

Identifies if more than one variant length exists for the same bundle within a derivative.
Messages Variables
Child {0} has more than one instance of {0} - Design Name + ":" + Design Part
Variant bundle {1} Number + ":" + Design Revision
Non-modular connector is connected to more than one bundle

Checks the presence of a non modular connector at a node which is connected to more than one
bundle (such as, a modular connector with inserts placed and connected with zero-length
bundles; the modular connector part is removed and a normal connector is added in its place).

December 2023
Messages Variables
{0} {1} is not modular connector but {0} - Context of Object - "Connector"
associated with more than one bundle {1} - Object name hyperlink
Option on object not applicable to design

Checks that the options used for the object match the option expression on the design.
Messages Variables
{0} "{1}" bundle has variant with invalid {0} - Context of Object - "Bundle"
functional variant code "{2}" {1} - Object name hyperlink
{2} - Function Variant Expression text
{0} "{1}" bundle has variant with invalid {0} - Context of Object, "Bundle"
option expression "{2}" {1} - Object name hyperlink
{2} - Option Expression text
{0} "{1}" bundle has variant with invalid {0} - Context of Object - "Bundle"
production variant code "{2}" {1} - Object name hyperlink
{2} - Production Variant Expression text
{0} "{1}" has an invalid option expression {0} - Context of Object, "Bundle"
"{2}" {1} - Object name hyperlink

Messages Variables
There is {0} pending checklist item {0} - Number for single checklist item
There are {0} pending checklist items {0} - Number of checklist items
Unresolved comments
Messages Variables
There is {0} unresolved comment {0} - Number for single unresolved comment
There are {0} unresolved comments {0} - Number for unresolved comments

December 2023
Unrouted wire to multi-entry connector

Checks if a wire end is terminated at a multi-entry connector but no route has been picked for
this end.
Messages Variables
{0} {1} is not routed at end {2} {0} - Context of object - "Wire"
{2} - Wire End location Object name hyperlink
Validate node component graphics layering

Checks that component graphics stacked at multi-location component nodes respect the order
matching, where the components have a “Layer” attribute value and the graphics include at least
one polygon associated to one of the component nodes.
Note
The Layer attribute value must be higher than the default “0” value.
See “Component Graphic and Layer Order Matching” in the Capital Harness Designer User
Guide.
The order matching is valid when the order of the physical size of the component graphics
match the order of their layer numbers on both sides of an intersecting bundle.
Where the order matching cannot be verified, the Design Rule Checks Output window reports
the following:
• Name of the object graphic that cannot be found or matched to the layer order.
• Name of the node where the error is present.
• Explanation of the error.
The default severity is “Error”.
Note
The DRC is not available in Background mode.
Messages Variables
Multiple Multi-location components are {0} - Node name hyperlink
placed at node {0}. Layer ordering cannot be
verified

December 2023
Messages Variables
Diagram appearance at node {0} does not {0} - Node name hyperlink
match the components layer number order
Graphics intersections for {1} {2} at node {0} {1} - Context of Object, "Node Component"
cannot be determined. Layer ordering cannot {2} - Object name hyperlink
be verified
Multiple bundles exist at node {0}. Layer {0} - Node name hyperlink
ordering cannot be verified
Node {0} is outside of the polygon for {1} {0} - Node name hyperlink
{2}. Layer ordering cannot be verified {1} - Context of Object, "Node Component"
{1} {2} at node {0} has no layer number or a {1} - Context of Object, "Node Component"
duplicate layer number defined. Layer {2} - Object name hyperlink
ordering cannot be verified
Cannot find polygon for {1} {2} at node {0}. {1} - Context of Object, "Node Component"
Layer ordering cannot be verified {2} - Object name hyperlink
Assembly insulation/wire length in design does not match library definition

Reports on assemblies where there is a mismatch in the length of wires and insulations used on
the design versus the definition in Assembly Details in Capital Component Manager.
Messages Variables
Design assembly {0} has {1} {2} with part {0} - Assembly Object name hyperlink
number {3} and length {4} but length defined {1} - Context of Object, "Wire"
in library assembly {5} is {6}
{3} - Part Number text
{4} - Length on Design Object
{5} - Context of Assembly - "Assembly"
{6} - Length on Assembly Object
Assembly library definition not used in design

Detects assembly components from an assembly library part which have not been added to the
assembly on the design.

December 2023
Messages Variables
Design Assembly {0} has the following {0} - Assembly
components unused from its part number {1}: {1} - Assembly Part
{2}
Design Assembly {0} have {1} components {0} - Assembly
with part number {2} but {3} is defined with {1} - Design Assembly quantity
quantity {4} in assembly details of library part
{5} {2} - Library Element Part number
{3} - Library Element Part Number
{4} - Library assembly Quantity
{5} - Assembly part number
Assembly splits in derivative design

Indicates if the options assigned to assembly components would lead to them being on different
derivatives.

December 2023
Messages Variables
Assembly {0} will split in derivative {1} {0} - Assembly Object name hyperlink
components: {2} {3} {4} {5} {6} {7} {8} {9} {1} - Derivative Design name text
{10} {11} of Assembly {12} will get
orphaned in Derivative {13} as Assembly does {2} - Assembly Component name hyperlink (1
not have matching option expression of 10)
{3} - Assembly Component name hyperlink (2
of 10)
of 10)
of 10)
of 10)
of 10)
of 10)
of 10)
{10} - Assembly Component name hyperlink
(9 of 10)
{11} - Assembly Component name hyperlink
(10 of 10)
{12} - Assembly name hyperlink
{13} - Derivative Design name text
Assembly {0} will split in design {1} as the {0} - Assembly Object name hyperlink
following components from the assembly do {1} - Derivative Design name text
not match the design\u2019s applicable
options: {2} {2} - Assembly Components - names with
Option Expression
Calculated bundle width exceeds max bundle width

Checks that the width of a bundle does not exceed the maximum bundle width specified.
Messages Variables
Max Bundle Width attribute value is less than {0} - Bundle name hyperlink
the calculated width for bundle {0}

December 2023
Cavity component does not fit wire

Checks single / multiple wire csa in relation to cavity seal and single and multi terminals.
Messages Variables
Seal at {4} "{1}" cavity "{2}" does not fit {4} - Parent Object name hyperlink
wires "{3}" {1} - Cavity name text
{2} - Wire names hyperlink, comma separated
{3} - Context of parent, Connector
Terminal at {4} "{1}" cavity "{2}" does not fit {4} - Parent Object name hyperlink
wires "{3}" {1} - Cavity name text
Ring terminal "{1}" does not fit wires "{3}" {1} - Ring Terminal name hyperlink
Ring terminal "{1}" does not fit wire "{3}" {1} - Ring Terminal name hyperlink
Seal at {4} "{1}" cavity "{2}" does not fit wire {4} - Parent Object name hyperlink
"{3}" {1} - Cavity name text
Terminal at {4} "{1}" cavity "{2}" does not fit {4} - Parent Object name hyperlink
wire "{3}" {1} - Cavity name text
Cavity multi-location components without cavities

Reports cases where a cavity MLC (multiple location component) is pointing to cavities that no
longer exist (for example, deleted connector cavities after MLC creation).
Messages Variables
{0} {1} does not contain any cavities {0} - Context of Object - "Cavity Multi-
Location Component"
{1} - MLC Object name hyperlink
Cavity with seal but no wire

Checks that the cavity has a seal defined, but there is no connectivity at the cavity.

December 2023
Messages Variables
Cavity {0} has a seal defined, but no {0} - Cavity name hyperlink
connectivity at {1} {2} {1} - Context of parent, Connector
{2} - Parent Object name text
Cavity with terminal but no wire

Checks that the cavity has a terminal defined, but there is no connectivity at the cavity.
Messages Variables
Cavity {0} has a terminal defined, but no {0} - Cavity name hyperlink
connectivity at {1} {2} {1} - Context of parent, Ring Terminal
Child module design references module code not on composite

(Applicable for Capital Harness Designer Modular only) Checks whether a child design uses
module codes that are no longer applicable to its parent composite design, this can result from
manual or bridged-in changes to the codes applicable to the composite. Any violations are
reported.
Messages Variables
{0} has module codes {1} which are not {0} - Object name hyperlink
applicable on parent {2} {1} - Module Code name(s) (comma delimited
if more than 1)
{2} - Parent Design Name + ":" + Parent
Design Part Number + ":" + Parent Design
Revision
Design has applicable module code that is not assigned to any object
(Applicable for Capital Harness Designer Modular only) Reports if objects exist on a design for
which no module codes are assigned.
Messages Variables
Modular design has applicable module codes {0} - Module Code name(s) (comma delimited
{0} that are not assigned to any objects if more than 1)
Design has child designs using mutually exclusive codes

Checks if the set of options / module codes applicable to a child design is valid.

December 2023
Run this check on a parent design to identify any derivative or modular child designs, that have
a set of options or functional / production module codes which have exclusive or mutually
exclusive relationships with each other.
Where the check identifies such relationship violations, the Design Rule Checks Output
Window reports the following:
• The name of the child design.

• The names of the identified codes.
The default severity is “Warning”.
Messages Variables
Child design {0} uses mutually exclusive {0} - Design Name + ":" + Design Part
functional module codes {1} Number + ":" + Design Revision
{1} - Module Code name(s) (comma delimited
if more than 1)
production module codes {1} Number + ":" + Design Revision
if more than 1)
options {1} Number + ":" + Design Revision
if more than 1)
Design that breaks module code relationships

(Applicable for Capital Harness Designer Modular only) Examines the module codes applied to
a design and checks the explicit inclusive / exclusive relationships and the implicit relationships
(such as mutually exclusive folders). Any violations are reported. Run this check only on child
designs.
Messages Variables
{0} has a module code expression that violates {0} - Design Name + ":" + Design Part
module code relationships, {1} and {2} are Number + ":" + Design Revision
exclusive {1} - Module Code name hyperlink
{2} - Module Code name hyperlink

December 2023
Empty modular design

(Applicable for Capital Harness Designer Modular only) If the design is a module parent, this
checks the module code on each object. If a child exists where applicable module codes do not
contain at least one of the module codes used in the parent then a report is issued.
Messages Variables
Child design {0} has applicable options {1} {0} - Design Name + ":" + Design Part
which are not present on any objects in its Number + ":" + Design Revision
parent {1} - Child design applicable options
Inconsistent assembly module code

(Applicable for Capital Harness Designer Modular only) Checks whether an assembly and its
constituent parts have matching module code assignation and reports any inconsistencies.
Messages Variables
Assembly {0} has inconsistent functional {0} - Assembly name hyperlink
module code assignation to child objects
Assembly {0} has inconsistent production {0} - Assembly name hyperlink
module code assignation to child objects
Inconsistent bundle sequence at junction

For all diagrams in the design - identifies mismatches at junction nodes between the current
order of bundles and any stored Bundle Junction Sequence.
Bundle junction sequences that are in a different order or reversed are reported by the DRC.
Note
The system can interpret the sequence as being reversed if you have flipped a section or the
whole harness, see Sequence Direction.
Messages Variables
On diagram {0}, order of bundles at junction {0} - Diagram name hyperlink
{1} does not match the defined sequence: {2} {1} - Junction name hyperlink
{2} - Bundle names (list)
On diagram {0}, at junction {1}, the order of {0} - Diagram name hyperlink
bundles "{2}" is reversed from the diagram {1} - Junction name hyperlink
specific counting order
{2} - Bundle names (list)

December 2023
Inconsistent insulation code

Identifies whether the contents of an insulation code have been edited and no longer match the
contents of the same code in use within the design, or whether an insulation code in use no
longer exists within the design.
Messages Variables
{0} "{1}" has insulation code {2} which {0} - Context of object - "Insulation Run"
differs from the project defined insulation code {1} - Insulation run name hyperlink
in {3}
{2} - Insulation Code text
{3} - Context of code "insulation layer
sequence" or "insulation layer attribute"
{0} "{1}" has insulation code {2} which no {0} - Context of object - "Insulation Run"
longer exists {1} - Insulation run name hyperlink
{2} - Insulation Code text
Inconsistent multicore inner core module code

(Applicable for Capital Harness Designer Modular only) Checks whether all inner cores of a
multicore have matching code assignations.
Messages Variables
Multicore {0} has inner cores with {0} - Multicore name hyperlink
inconsistent functional module code
assignations
Multicore {0} has inner cores with {0} - Multicore name hyperlink
inconsistent production module code
assignations
Inconsistent variant position object

Identifies if one or more variant positions for an object (connector or splice) have been
modified, and are now out of synchronization with the primary position object.
Messages Variables
{0} {1} has an attribute "{2}" with a different {0} - Context of Object, "Connector"
value to {3} {1} - Object name hyperlink
{2} - Attribute Text

December 2023
Messages Variables
{0} {1} at {2} {3} has an attribute "{4}" with {0} - Context of Object, "Connector"
a different value at {5} {1} - Object name hyperlink
{2} - Source Parent Object Type
{3} - Source Parent Object name hyperlink
{5} - Target Parent Object name hyperlink
{0} {1} Option: {2} at {3} {4} has an attribute {0} - Context of Object, "Connector"
"{5}" with a different value at {6} {1} - Object name hyperlink
{3} - Source Parent Object Type
{4} - Source Parent Object name hyperlink
{0} {1} has component "{2}" that is not on {0} - Context of Object, "Connector"
{3} {1} - Object name hyperlink
{2} - Part number text
{3} - Target Object name hyperlink
{0} {1} has a property "{2}" that is not on {3} {0} - Context of Object, "Connector"
{2} - Property name text
{0} {1} has component "{2}" with a different {0} - Context of Object, "Connector"
quantity to {3} {1} - Object name hyperlink
{0} {1} has a property "{2}" with a different {0} - Context of Object, "Connector"
value to {3} {1} - Object name hyperlink
{2} - Property name text
Inconsistent variant position reference node

Evaluates all object’s variant positions against the derivative options and validates if the order
of the reference nodes on a bundle in each derivative will be the same as the default order
specified on the composite bundle. See also “Variant Position Connectors” in the Capital
Harness Designer User Guide.

December 2023
Messages Variables
{0} {1} has different physical and graphical {0} - Context of Object - "Bundle"
reference node order in {2} {1} - Bundle name hyperlink
{2} - Physical Order **Node List** Diagram
Order **Node List**
On the child {0} the reference node order {0} - Design Name + ":" + Design Part
changed for bundle {1} {2} Number + ":" + Design Revision
{2} - Node Order on Composite **Node List**
Node Order on Child **Node List**
Inconsistent variant position wiring

Identifies if one or more variant positions for a wire have been modified, and are now out of
synchronization with the primary position wire.
Messages Variables
{0} {1} has wire {2} that is not in {3} {0} - Context of Object, "Connector"
{0} {1} has wire {2} terminating at a different {0} - Context of Object, "Connector"
cavity in {3} {1} - Object name hyperlink
{0} {1} - Option Expression {2} has different {0} - Context of Object - "Wire"
wire markers to {3} {4} - Option Expression {1} - Wire name hyperlink
{5}
{3} - Context of Object - "Wire"
{4} - Wire name hyperlink on other wire
variant
{5} - Option Expression text for wire variant

December 2023
Messages Variables
{0} {1} at {2} {3} has component {4} with {0} - Context of Object - "Wire"
different quantity to {5} {6} at {7} {8} {1} - Wire name hyperlink
{2} - Location of Object, "Connector"
{3} - Location of Object name hyperlink
variant
{7} - Location of Wire Variant Object,
"Connector"
{8} - Location of Wire Variant Object name
hyperlink
{0} {1} at {2} {3} has component {4} not on {0} - Context of Object - "Wire"
{5} {6} at {7} {8} {1} - Wire name hyperlink
{2} - Location of Object, "Connector"
{3} - Location of Object name hyperlink
variant
{7} - Location of Wire Variant Object,
"Connector"
{8} - Location of Wire Variant Object name
hyperlink
Incorrect associated bundle graphic

Evaluates if Associated Bundles intersect with the start and ends of the main insulation graphic
on the diagram, to ensure that the main insulation graphics cover all Associated bundles.
Messages Variables
Diagram appearance for insulation {0} on {0} - Insulation Layer name hyperlink
diagram {1} does not include associated {1} - Diagram name hyperlink
bundle(s) {2}
{2} - Bundle name hyperlink(s) (comma
delimited if more than 1)

December 2023
Incorrect graphical node position

Identifies where a graphical offset has been applied which results in the node being repositioned
on a different bundle.
This can occur if you have updated graphical offset positions using a plugin. See “Graphical
Offsets” in the Capital Harness Designer User Guide.
Messages Variables
Node position and its graphical offset puts the None
node outside of the bundle
Invalid overbraid end termination

Identifies if a termination has been specified for an overbraid that does not exist on the routes of
any of the wires contained within it.
Messages Variables
{0} {1} has end termination at {2} {3}, Cavity {0} - Context of Object - "Overbraid"
{4} that does not exist on the route of any of {1} - Overbraid name hyperlink
its wires.
{2} - Context of Object Terminated at,
"Connector"
{3} - Object name Terminated at hyperlink
{4} - Cavity name Terminated at hyperlink
{0} {1} has end termination at {2} {3}, {4} {0} - Context of Object - "Overbraid"
{5}, termination {6} that does not exist on the {1} - Overbraid name hyperlink
route of any of its wires.
{2} - Context of Parent Object terminated at,
"Connector"
{3} - Parent Object name Terminated at
hyperlink
{4} - Context of Object Terminated at -
"Backshell"
{5} - Backshell name hyperlink
{6} - Backshell Termination name hyperlink
Mismatch between assembly content and project preference

Checks the content of assemblies on the design and highlights any that do not conform with the
project preference “Assembly”.

December 2023
Messages Variables
Assembly {0} structure is inconsistent with {0} - Assembly
project preferences. The following {1} - Connector or Backshell with count in
components violate the preferences: {1} brackets
Missing association for bundle overlapping insulation run

Identifies bundles that intersect with the main insulation graphic but are not associated with the
insulation run. See also “Associated Bundles” in the Capital Harness Designer User Guide.
Messages Variables
Insulation run {0} on diagram {1} has {0} - Insulation run name hyperlink
overlapping non associated bundle(s) {2} {1} - Diagram name hyperlink
{2} - Bundle name hyperlink(s) (comma
delimited if more than 1)
Modular expression too long to be costed in CapH Costing

(Applicable for Capital Harness Designer Modular only) Checks if the length of the Module
Code Expression is longer than 1024 characters. If true, it reports that the harness cannot be
accurately costed in Capital Harness Classic because of the number of characters.
Messages Variables
Object {0} has a module code expression over {0} - Object name hyperlink
1024 characters
Modular Objects with No Functional Module Codes

(Applicable for Capital Harness Designer Modular only) Identifies any objects that do not have
any Functional Module codes assigned.
Messages Variables
{0} {1} has no {2} Module Codes {0} - Context of object - "Connector"
{2} - Type of Module Code - "Functional"
Modular Objects with No Production Module Codes

(Applicable for Capital Harness Designer Modular only) Identifies any objects that do not have
any Production Module codes assigned.

December 2023
Messages Variables
{0} {1} has no {2} Module Codes {0} - Context of object - "Wire"
{2} - Type of Module Code - "Production"
Module code used on composite but not consumed by child module

(Applicable for Capital Harness Designer Modular only) Reports if module codes exist in the
design that are not consumed by a buildable module, indicating that a child module has not been
created to use this module.
Messages Variables
{0} has module codes {1} which are not {0} - Object Name hyperlink
appliable to any child modules (and therefore {1} - Module Code name(s) (comma delimited
unbuildable) if more than 1)
Multi-location component without a wire end

Reports cases where a wire multi-location component is pointing to wire ends that no longer
exist (for example, specified wire end from/to details unchecked on Edit Multi-Location Wire
End Component Dialog Box, after MLC creation).
Messages Variables
{0} {1} does not contain any wire ends {0} - Context of object - "Wire Multi-Location
Component"
Multi-location component without node

Reports cases where a node multi-location component is pointing to nodes that no longer exist
(for example, deleted connector after MLC creation).
Messages Variables
{0} {1} does not contain any nodes {0} - Context of object - "Node Multi-Location
Component"
Nested assembly contains in-house assembly/multicore

Indicates when a standard or connector assembly contains an in-house assembly.

December 2023
Messages Variables
Standard/Connector Assembly {0} contains an {0} - Assembly name hyperlink
In-House-Assembly {1} {1} - In House Assembly Object name text
Standard/Connector Assembly {0} contains an {0} - Assembly name hyperlink
In-House-Twisted-Pair-Multicore {1} {1} - In House Twisted Pair Multicore Object
name text
Object assigned a technical module code that has no associated

combinations
(Applicable for Capital Harness Designer Modular only) Examines module codes on each
object. If the module code is a technical module code and is not associated with a combination a
report is issued.
Messages Variables
Object {0} has technical module code {1} {0} - Object name hyperlink
assigned that has no combinations {1} - Module Code name(s) (comma delimited
if more than 1)
Object that breaks module code relationships

(Applicable for Capital Harness Designer Modular only) Examines the module codes on each
object and checks the explicit inclusive / exclusive relationships and the implicit relationships
(such as mutually exclusive folders). Any violations are reported.
Messages Variables
{0} has a module code expression that violates {0} - Object name hyperlink
module code relationships, {1} and {2} are not {1} - Module Codes in exclusive relationship
exclusive
{2} - Module Codes in exclusive relationship
Obsolete option
Messages Variables
{2} {0} uses obsolete option {1} {0} - Any Logic Object
{1} - Option
{2} - Object Type

December 2023
Messages Variables
{1} - Pin
{2} - Options name
{1} - Pin
{2} - Options name
{2} {0} uses obsolete options {1} {0} - Any Logic Object
{1} - Options name
{2} - Object Type
Overlapping insulation layers with same layer number

Identifies where layer orders cannot be determined because of overlapping insulation layers
with the same layer number. The check runs on single derivative, FM, and PM designs only, and
not on composite designs.
Messages Variables
Overlapping insulation layers {0}, {1} have {0} - Insulation Layer name hyperlink
the same layer number {2} {1} - Insulation Layer name hyperlink
{2} - Insulation Layer, Layer Number text
Reference nodes overlap graphically

Identifies where a graphical offset has been applied which results in the node crossing another
reference node on the same bundle.
This can occur if you have updated graphical offset positions using a plugin. See “Graphical
Offsets” in the Capital Harness Designer User Guide.

December 2023
Messages Variables
Reference node {0} should be between {1} {0} - Node name text + [Object name text] (if
and {2}, but found to be between {3} and {4} object present)
{1} - Node name text + [Object name text] (if
object present)
object present)
object present)
object present)
Related objects assigned different module codes

(Applicable for Capital Harness Designer Modular only) Checks the validity of codes
assignments and reports when related objects, for example connectors and cavity seals, have
been assigned different module codes.
Messages Variables
{0} is assigned functional module codes {0} - Object name hyperlink
different from {1}{0} is assigned production {1} - Related Object Type (optional) + Related
module codes different from {1}Wire end Object Name Text
components of {0}
{0} is assigned production module codes {0} - Object name hyperlink
different from {1} {1} - Related Object Type (optional) + Related
Object Name Text
Wire end components of {0} {0} - Related Object Name Text
Required terminal and cavity seal consistency

Checks each wire combination in each cavity detail and reports any mismatch in the required
terminal / seal parts. For example, if different terminal / seal part numbers are available on
multiple wire ends terminating at the same cavity.
Messages Variables
Required {0} in {1} cavity {2} has multiple {0} - Context of Object, "Cavity Seal"
parts {3} on wires {4} {1} - Parent Object name hyperlink
{3} - Part names text, comma separated
{4} - Wire names text, comma separated

December 2023
Terminal and cavity seal selected part validity

Checks and reports any mismatch between the terminal / seal part numbers specified in the
source design and the actual terminal / seal parts in the target harness design. For example, if the
required terminal / seal parts change in the source design but have not been updated in the target
harness design using Cavity Component Management.
Messages Variables
Wire end in {0} cavity {1} has required {0} - Parent Object name hyperlink
{2}:{3}. Cavity contains:{4} {1} - Cavity name hyperlink
{2} - Cavity Part Type - "Terminal" or "Seal
{3} - Required Terminal or Seal Part Number
text
{4} - Actual Terminal or Seal Part Number text
Tube does not fit bundle

Identifies any tubes that are too small for the bundle to which they have been applied. For tubes
that are shrinkable (see “Tubes” in the Capital Component Manager User Guide), the check
fails if the following rules are not satisfied:
• The bundle width covering the tube must be greater than the Min. Allowed Diameter
attribute of the tube.
• The bundle width covering the tube must be less than the Bore Size attribute of the tube.
If the heat shrink tube also covers another insulation, Rule 1 and Rule 2 are applied.
For all types of tubes, the check fails if the following rules are not satisfied:
• For a bundle covered by a Tube that has a part number with Min. Allowed Diameter and
Max. Allowed Diameter attribute defined:
o The bundle width must be less than the Max. Allowed Diameter attribute.
o The bundle width must be greater than the Min. Allowed Diameter attribute.
Any error message displayed reports either the Min. Allowed Diameter or Max. Allowed
Diameter that has been violated as well as the bundle diameter.
Note
Insulated bundle diameter (“Width with Insulations” bundle attribute) is calculated as
follows: (Tube Factor adjustments do not apply to shrinkable tubes):
• For shrinkable tubes - Wire bundle diameter + (2 x shrink tube thickness).

• For non-shrinkable tubes - Bore size + (2 x tube thickness)

December 2023
Messages Variables
Tube {0} belonging to insulation run {1} {0} - Insulation Layer name hyperlink
running from Node {2} to Node {3} does not {1} - Insulation run name hyperlink
fit bundle. Tube diameter is {4}, bundle
diameter is {5} at Node {6} {2} - Insulation Start Node name hyperlink
{3} - Insulation End Node name hyperlink
{4} - Tube Diameter attribute value
{5} - Bundle max Diameter attribute value
{6} - The node with the max Diameter
fit bundle. Max. allowed bundle diameter is
{4}, bundle diameter is {5} at Node {6} {2} - Insulation Start Node name hyperlink
{4} - Max Allowed Bundle Diameter from
Library Part
fit bundle. Min. allowed bundle diameter is
{4}, bundle diameter is {5} at Node {6} {2} - Insulation Start Node name hyperlink
{4} - Min Allowed Bundle Diameter from
Library Part
Tube is longer than bundle

Identifies any tubes that are longer than the bundle to which they have been applied.
Only applicable to tubes where you have manually overridden the system calculated tube length
on the Add or Edit Insulation Layer Dialog Box or the Quick Tube Creator Dialog Box.
Messages Variables
Defined length for Tube {0}: {1} exceeds the {0} - Context of object - "Tube"
length of covered bundles: {2} {1} - Tube Length
{2} - Length of covered bundles

December 2023
Assembly component not in library

Checks if an extra component is present in the design assembly, but not present in library.
Messages Variables
Assembly {0} has the following extra {0} - Assembly name hyperlink
components missing from its part number {1} {1} - Assembly Part Number text
<BR> {2}
{2} - Assembly Component Part Number text
(on separate line)
Assembly {0} has {1} extra components with {0} - Assembly Name hyperlink
part number {2} but {3} is defined with {1} - Quantity of Assembly Component in
quantity {4} in assembly details of library part Assembly
{5}
{4} - Quantity of Assembly Component in
Library
{5} - Assembly Part Number text
Insufficient distance between items

Identifies insulation runs for which the “Distance between items” attribute has a value of 0.
Messages Variables
Insulation {0} does not have distance between {0} - Insulation Layer name hyperlink
items set

- General DRCs
There are particular general design rule checks related that you can run for a Capital Harness
Designer / Modular design.
Invalid wire path

Checks if Wire End2 is reachable from Wire End1 through the bundles and honoring the thru /
not-thru nodes constraints.
Table 2-16. Invalid wire path - Messages
Messages Variables
No valid path found for {0} {1} {0} - Context of object - Wire

December 2023
Table 2-16. Invalid wire path - Messages (cont.)

Messages Variables
{0} {1} does not terminate at both ends {0} - Context of object - Wire

- Harness Designer Rules DRCs
There are particular design rule checks related to Harness Designer rules that you can run for a
Capital Harness Designer / Modular design.
Violated attribute/property rule

Identifies any objects that violate any “Set Attribute/ Property on Object” constraints. These
constraints define, for specific objects, which value an attribute/property should have when
another attribute / property has another specific value.
Messages Variables
conflicting constraints were found on {3} and {1} - Object type
{4}
{2} - Object name
conflicting constraints were found on {3} {1} - Object type
{2} - Object name
{3} - Object names
Cannot validate {0} rule on {1} {2} {0} - Attribute or property name
{1} - Object type
{2} - Object name

Identifies wires that violate any “Route by Attribute/ Property” constraints (rules). Also reports
the signal, bundle, inline connector and harness on which the violation exists.
Messages Variables
Wire {0} violates routing constraint on Bundle {0} - Wire name hyperlink
{1}, HarnessDesign {2} {1} - Bundle name hyperlink
{2} - Design name + ":" + Design Part Number

December 2023

- Inclusion DRCs
There are particular design rule checks related to inclusion that you can run for a Capital
Wire does not fit cavity

Checks against cavity attributes whether a wire fits or not. Use on child modules and derivatives
only.
Messages Variables
Wires "{3}" does not fit cavity "{2}" on {4} {3} - Context of Cavity location name
"{1}" hyperlink
{2} - Cavity name text
{4} - Wire name hyperlinks, comma separated
{1} - Context of Cavity location, "Connector"
Wire "{3}" does not fit cavity "{2}" on {4} {3} - Context of Cavity location name
"{1}" hyperlink
{1} - Context of Cavity location, "Connector"
Alternative cavity plug available

The system has selected a cavity plug where there are two or more identical plugs to choose
from. This check prompts you to check the selection was correct.
Messages Variables
{0} {1} {2} {3} has alternative Plugs {0} - Context of object - "Connector"
{2} - Cavity type, "Connector Cavity"
{4} - List of alternative Plugs (hardcoded
concatenation, not a parameter)
Alternative cavity seal available

The system has selected a cavity seal where there are two or more identical seals to choose
from. This check prompts you to verify the selection was correct

December 2023
Messages Variables
{0} {1} {2} {3} {4} {5} has alternative Seals {0} - Context of object - "Wire"
{2} - Context of owning object, "Connector"
{3} - Owning Object name hyperlink
{4} - Cavity Type, "Connector Cavity"
Alternative terminal available

The system has selected a cavity terminal where there are two or more identical terminals to
choose from. This check prompts you to verify the selection was correct
Messages Variables
{0} {1} {2} {3} {4} {5} has alternative {0} - Context of object - "Wire"
Terminals {1} - Wire name hyperlink
Cavity with plug or seal marked as "none"

Identifies where the use of plug / seals has been specified but the corresponding library part
does not have it assigned.
Messages Variables
Non-Plugged {0} "{1}" has a plug part "{2}" {0} - Context of object - "Connector"
{2} - Cavity Plug part number
Non-Sealed {0} "{1}" has a seal part "{2}" {0} - Context of object - "Connector"
{2} - Cavity Seal part number
Inappropriate terminal material or type for wire

Identifies where the terminal material or type does not match the selected wire terminal or type
defined in Cavity Component Management.

December 2023
Messages Variables
{0} {1} {2} {3} {4} {5} Inappropriate {0} - Context of object - "Wire"
Terminal Material for wire {1} - Wire name hyperlink
{0} {1} {2} {3} {4} {5} Inappropriate {0} - Context of object - "Wire"
Terminal Type for wire {1} - Wire name hyperlink
Invalid mandatory item selection

Checks if a mandatory item defined in a library component's housing definition exists on the
node with a matching quantity. For cavity components, check that they exist in the matching
cavity in correct quantity. When checking for additional components, the Include-on- BOM
status of the parent object is important:
• If the parent component is “instance” Non-BOM (Include-on-BOM is not set on the

instantiated parent but it is set on the parent’s Capital Component Manager part number)
it is a “reference” object, and the object is not considered / reported by this DRC.
Similarly, any of its mandatory components that are not present are not reported.
• However, if the parent object is Library Non-BOM (Include-on-BOM is not set in
Capital Component Manager), this DRC reports any non-present mandatory additional
components that are Library Include-on-BOM (Include- on-BOM is set in Capital
Component Manager). Such components are not reported if they are Library Non-BOM
(Include-on- BOM is not set in Capital Component Manager).
Messages Variables
{0} "{1}": library part has a mandatory {0} - Context of object, "Connector"
housing definition "{2}" which is not present {1} - Object name hyperlink
on the node
{2} - Component part number
{0} "{1}": library part has a mandatory {0} - Context of object, "Grommet"
housing definition "{2}" which is not present {1} - Object name hyperlink
on the node in right quantity

December 2023
Messages Variables
No default grease packing component "{0}" {0} - Default Grease Packing Component part
number
No default grease component "{0}" {0} - Default Grease Component part number
{0} of {1} cavities have no default grease {0} - Number of cavities without grease
component "{2}" component
{1} - Number of Cavities attribute of
Connector
{2} - Default Grease Component part number
All cavities have no default grease component {0} - Default Grease Component part number
"{0}"
Mismatched mated connectors and terminal material

Checks that all selected terminals in a connector or backshell have the same material. If not, it
reports the cavity name and terminal part number / material for the cavities which have different
terminal materials.
Messages Variables
{0} {1} has different terminal materials {0} - Context of object - "Connector" or
"Backshell"
Cavity {0} Terminal Part Number {1} {0} - Cavity name text
Terminal Material {2} {1} - Terminal part number text
{2} - Terminal Material Code text
Mismatched wire and cavity terminal material

Identifies where the terminal material of the selected terminal does not match the wire terminal
material defined in Cavity Component Management.
Messages Variables
{0} {1} {2} {3} {4} {5} wire and cavity {0} - Context of object - "Wire"
terminal material mismatch {1} - Wire name hyperlink

December 2023
Plug and wire at the same cavity

Checks if a cavity has a plug as well as a wire. If you are running this on a Parent Design (after
you have run Composite Breakdown) the check only reports an error if the wire and the plug in
the cavity belong to at least one common child design.
Messages Variables
{0} {1} has a wire and a plug on cavity {2} {0} - Context of object - "Connector"
Terminal material code mismatch at double termination

Identifies where the terminal selected on a derivative in a multiple termination does not match
the terminal material assigned to the wires in Cavity Component Management.
Messages Variables
{0} {1} {2} {3} {4} {5} True wire double {0} - Context of object - "Wire"
termination Material Code mismatch {1} - Wire name hyperlink
Sealed and unsealed components exist

Checks the sealed / unsealed status on each connector, device, or ring terminal and lists them.
Messages Variables
{0} at {1} "{2}" int. part no. "{3}" sealed? {0} - Context of object - "Connector"
Yes {1} - Location of object, "Node"
{2} - Location name hyperlink
{0} "{1}" at {2} "{3}" sealed? Yes {0} - Context of object - "Connector"
{1} - Location of object, "Node"
{0} int. part no. "{1}" sealed? Yes {0} - Context of object - "Connector"

December 2023
Messages Variables
{0} "{1}" sealed? Yes {0} - Context of object - "Connector"
{0} int. part no. "{1}" sealed? No {0} - Context of object - "Connector"
{0} "{1}" is marked as unsealed but contains {0} - Context of object - "Connector"
seals in the component library. {1} - Object name hyperlink
{0} "{1}" sealed? No {0} - Context of object - "Connector"
{0} at {1} "{2}" int. part no. "{3}" sealed? No {0} - Context of object - "Connector"
{0} "{1}" at {2} "{3}" is marked as unsealed {0} - Context of object - "Connector"
but contains seals in the component library. {1} - Object name hyperlink
{0} "{1}" at {2} "{3}" sealed? No {0} - Context of object - "Connector"

- Library Consistency DRCs
Capital Harness Designer / Modular design.
Component does not exist in housing definition

Identifies where an additional node or cavity component is not defined in the first level of a
components housing definition.
Note
When a backshell is present on a connector, the check searches the first level housing
definition of both the connector and the backshell. If an additional component is not in the
connector housing definition but is in the backshell, the check does not report an error.

December 2023
Messages Variables
Additional component "{2}" at {0} "{1}" not {2} - Context of component parent,
in Housing Definition "Connector"
{0} - Parent Component Name hyperlink
Cavity component "{2}" in Cavity "{3}" of {2} - Text "Connector" from resource
{0} "{1}" not in Housing Definition {3} - Connector Name hyperlink
{1} - Cavity Name hyperlink
Terminal "{0}" in Cavity "{3}" of {1} "{2}" {0} - Terminal part number
not in Housing Definition {3} - Text "Connector" from resource
{1} - Connector Name hyperlink
Seal "{0}" in Cavity "{3}" of {1} "{2}" not in {0} - Seal part number
Housing Definition {3} - Text "Connector" from resource
{0} {1} part number {2} does not exist in {0} - Text "Backshell" from resource
housing definition for {3} {4} part number {1} - Backshell Name hyperlink
{5}
{2} - Backshell part number
{3} - Text "Connector" from resource
{5} - Connector part number

Messages Variables
{0} {1} has P/N={2} assigned to it, but that is {0} - Object Type
not the latest {1} - Any Logic Library Object
{2} - Part Number
Obsolete or invalid part number

Identifies where a part number exists but the corresponding part is either not available or
obsolete in Library.

December 2023
Messages Variables
{0} "{1}" has an invalid part "{2}" on its {0} - Context of object, "Connector"
cavity {1} - Component Name hyperlink
{0} "{1}" uses an obsolete library part "{2}" {0} - Context of object, "Connector"
on its cavity, please change the part to one that {1} - Component Name hyperlink
is current.
{0} "{1}" at {2} "{3}" has an invalid part {0} - Context of object, "Backshell"
"{4}" {1} - Component Name hyperlink
{0} "{1}" at {2} "{3}" has an obsolete library {0} - Context of object, "Backshell"
part "{4}", please change the part to one that is {1} - Component Name hyperlink
current.
{0} "{1}" has an invalid extra component part {0} - Context of parent object, "Grommet"
"{2}" {1} - Parent Component Name hyperlink
{0} "{1}" uses an obsolete extra component {0} - Context of parent object, "Grommet"
part "{2}", please change the part to one that is {1} - Parent Component Name hyperlink
current.
Attributes of {0} "{1}" not match with its {0} - Context of object, "Wire"
library part "{2}" {1} - Component Name hyperlink
{0} "{1}" has an invalid part "{2}" {0} - Context of object, "Connector"
{1} - Component Name hyperlink
{0} "{1}" uses an obsolete library part "{2}", {0} - Context of object, "Connector"
please change the part to one that is current. {1} - Component Name hyperlink

December 2023
Messages Variables
Additional component at {0} "{1}" has an {0} - Context of object - "Node Multi-Location
invalid part "{2}" Component" or "Cavity Multi-Location
Component" or "Wire Multi-Location
Component"
{1} - Multi-Location Component name
hyperlink
Additional component at {0} "{1}" has an {0} - Context of object - "Node Multi-Location
obsolete library part "{2}", please change the Component" or "Cavity Multi-Location
part to one that is current Component" or "Wire Multi-Location
Component"
hyperlink
{0} has an invalid part "{1}" at {2} "{3}" {0} - Context of object, "Clip"
{2} - Text "Node" from resource
{3} - Node Name hyperlink
{0} uses an obsolete library part "{1}" at {2} {0} - Context of object, "Clip"
"{3}", please change the part to one that is {1} - Component part number
current.
{2} - Text "Node" from resource
{3} - Node Name hyperlink
{0} "{1}" has no library part {0} - Context of insulation object, "Bundle
Insulation"
{1} - Insulation Layer Name hyperlink
{0} at {1} "{2}" has an invalid part "{3}" {0} - Text "Additional Component" from
resource
{1} - Text "Wire" from resource
{2} - Wire Name hyperlink
{0} at {1} "{2}" has an obsolete library part {0} - Text "Additional Component" from
"{3}", please change the part to one that is resource
current. {1} - Text "Wire" from resource
{2} - Wire Name hyperlink

December 2023
Messages Variables
Inner cores or conductors of {0} "{1}" not {0} - Context of object - "Multicore"
match with its library part "{2}" {1} - Multicore Name hyperlink
{2} - Multicore Part Number text
Fixture part number validity

Validates the assigned part numbers for all fixtures on all diagrams in the design using the
fixture. See “Automatic Part Number Selection Rules” in the Capital Harness Designer User
Guide.
Note
The “Auto-Selectable” rule is not considered in this check.
Messages Variables
{0} {1} has invalid part number: {2} {0} - Context of object - "Fixture"
{1} - Fixture name hyperlink
{2} - Diagram name

Identifies where an object has a “Not-On-BOM” attribute a value different to its library setting.
Messages Variables
{0} {1} 's Include On Bom status is different {0} - Logic Object Type
to its library part. {1} - Any Logic Library Object
Library part required for bundle insulation

Identifies where an insulation exists that has no library part assigned.
Messages Variables
{0} {1} has no library part {0} - Context of object - "Bundle Insulation"
{1} - Insulation name hyperlink
Library part required for clip

Identifies where a clip exists that has no library part assigned.

December 2023
Messages Variables
{0} {1} has no library part {0} - Context of object - "Clip"
{1} - Clip name hyperlink

Identifies where a connector exists that has no library part assigned.
Messages Variables
{0} {1} has no library part {0} - Context of object - "Device"
{1} - Device name hyperlink
Library part required for device

Identifies where a device exists that has no library part assigned.
Messages Variables
{0} {1} has no library part {0} - Context of object - "Connector"
Library part required for grommet

Identifies where a grommet exists that has no library part assigned.
Messages Variables
{0} {1} has no library part {0} - Context of object - "Grommet"
{1} - Grommet name hyperlink
Library part required for multi-location component

Identifies where a multi-location component exists that has no library part assigned.
Messages Variables
{0} {1} has no library part {0} - Context of object - "Node Multi-Location
Component" or "Cavity Multi-Location
Component" or "Wire Multi-Location
Component"
hyperlink

December 2023
Library part required for multicore

Identifies where a multicore exists that has no library part assigned.
Messages Variables
{0} {1} has no library part {0} - Context of object - "Multicore"
{1} - Multicore name hyperlink
Library part required for node insulation

Identifies where a node insulation exists that has no library part assigned.
Messages Variables
{0} {1} has no library part {0} - Context of object - "Spot Tape" or
"Breakout Tape"
{1} - Tape name hyperlink
Library part required for splice

Identifies where a splice exists that has no library part assigned.
Messages Variables
{0} {1} has no library part {0} - Context of object - "Splice"
{1} - Splice name hyperlink
Library part required for wire

Identifies where a wire exists that has no library part assigned.
Messages Variables
{0} {1} has no library part {0} - Context of object - "Wire"
Library part without supplier number

Checks the components that have no supplier part number listed in Library.
Messages Variables
{2} "{3}" at {0} "{1}" has no supplier part {2} - Text "Insulation Run" from resource
number {3} - Insulation run name hyperlink
{0} - Context of object - "Bundle Insulation"
{1} - Insulation name hyperlink

December 2023
Messages Variables
{0} "{1}" has a cavity part "{2}" which has no {0} - Context of object - "Connector"
supplier part number {1} - Connector name hyperlink
{2} - Cavity component part number
{0} "{1}" at {2} "{3}" has no supplier part {0} - Text "Backshell" from resource
number {1} - Backshell name hyperlink
{2} - Text "Connector" from resource
Extra component with part number "{2}" at {2} - Conext of parent object - "Connector"
{0} "{1}" has no supplier part number {0} - Component name hyperlink
{1} - Extra component part number
{0} "{1}" has no supplier part number {0} - Context of object - "Connector"
Additional component with part number "{0}" {0} - Component internal part number
at {1} "{2}" has no supplier part number {1} - Context of parent - "Node Multi-Location
Component"
{2} - Multi-Location name hyperlink
{0} with part number "{1}" at {2} "{3}" has {0} - Context of object - "Clip", "Grommet",
no supplier part number "Other Component"
{1} - Component internal part number
{2} - Location, Node
{0} with part number "{1}" at {2} "{3}" has {0} - Context of object - "Additional
no supplier part number Component"
{1} - Component internal part number
{2} - Location - "Wire"
Modular connector structure does not match library definition

Checks if a housing component is made applicable to one position but is placed in a different
one. For example, if a fuse is present in an incompatible position on a fuse box connector.
Also captures case where a purchased part is instantiated on design, but its child inserts are not
present on the design.
Identifies mismatches between library definition and design instance of modular connectors.
For example, the library definition position configuration blocks a cavity but the design instance
does not have this information (or the reverse).

December 2023
Also captures cases where a purchased part is instantiated on design, but its child inserts are not
present on the design.
See “Modular Connectors Overview” in the Capital Harness Designer User Guide.
Messages Variables
Component "{0}" occupies position "{1}" {0} - Object name text
which is not defined in the housing definition {1} - Position text
of "{2}"
Connector {0} at {1}:{2} is blocking cavity {0} - Connector name hyperlink
"{3}" of its parent, but in Library it blocks {1} - Position Container Object hyperlink + ":"
cavity "{4}" + Position text
{3} - Library Blocked Cavity name(s) text
Connector {0} at {1}:{2} is not blocking any {0} - Connector name hyperlink
cavity of its parent, but in Library it blocks {1} - Position Container Object hyperlink + ":"
cavity "{3}" + Position text
{3} - Library Blocked Cavity name(s) text
Connector {0} at {1}:{2} is blocking cavity {0} - Connector name hyperlink
"{3}" of its parent, but in Library it does not {1} - Position Container Object hyperlink + ":"
block any cavity + Position text
Position "{0}" of purchased connector {1} is {0} - Position text
empty {1} - Connector name hyperlink


December 2023
Messages Variables
{0} {1} on {2} {3} has invalid scoping. {4} {0} - Context of Object, "Cavity Seal"
{5} {6} {7} {1} - Object Name text
{3} - Parent Object Name hyperlink
{4} - Project Scoping text
{5} - Project Scoping value
{6} - Housing Scoping text
{7} - Housing Scoping value
Ring terminal with connector part number

Issues a warning where ring terminal objects exist with connector part numbers assigned.
Messages Variables
Ring terminal {0} has a connector library part {0} - Ring Terminal
{1} attached {1} - Library Part Full name
Undefined route for dressed connector

Identifies where available routes in Capital Component Manager have not been applied to
connectors in the design.
Messages Variables
Connector {0} has no route defined {0} - Connector Name hyperlink

- Naming DRCs
There are particular design rule checks related to naming that you can run for a Capital Harness
Designer / Modular design.
Invalid name for component

Identifies objects with names that do not appear in the list of valid names for the project's object
type.
Messages Variables
Invalid name: {0} is not on the list of valid {1} {0} - Non-Shared Logic Object

December 2023
Multiple components with same name

Checks for objects with the same name on a harness design. For example, when synchronizing
device connectors of a device that has two device footprint connectors with the same part
number.
Messages Variables
{0} {1} with same name already exists {0} - Object context, text - any object
Missing BOM ID
Checks that all objects that can be assigned a BOM ID have a valid BOM ID.
Messages Variables
{0} {1} has no BOMID value {0} - Object context, text - any object
{1} - Object Name hyperlink
{0} {1} {2} {3} {4} {5} {6} has no BOMID {0} - Object context, cavity component
value {1} - Part number
{2} - Text "at" from resource
{3} - Location, "Connector"
{4} - Location Name hyperlink
{5} - Text "Cavity" from resource
{0} {1} {2} {3} {4} has no BOMID value {0} - Object context
{1} - Part number
{2} - Text "at" from resource
{3} - Location Context - "Node"
{4} - Location Name hyperlink

December 2023
Design Rule Checks Applicable to Manufacturing

There are specific design rule checks that you run while editing a design in Capital Harness
Process Designer and Capital Harness Costing.
Manufacturing - Costing DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402

Manufacturing - Part Number Management DRCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Manufacturing - Sub-assembly Structure DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Manufacturing - Costing DRCs

There are particular design rule checks related to costing that you can run in Capital Harness
Process Designer and Capital Harness Costing.
Sub-assembly not costed

Identifies sub-assemblies not costed due to a problem during cost calculation.
Messages Variables
{0} {1} has no cost associated {0} - Context of Object - "Sub-assembly"
{1} - Sub Assembly Name hyperlink (non-
existent)
Manufacturing - Part Number Management DRCs

There are particular design rule checks related to part number management that you can run in
Capital Harness Process Designer.
Note
These are not applicable to Capital Harness Costing.
Sub-assembly with no part assigned

Identifies sub-assemblies on the SBOM that have no part number assigned.
Messages Variables
{0} {1} has no part number assigned {0} - Context of Object - "Sub-assembly"
{1} - Sub Assembly Name hyperlink (non-
existent)

December 2023
Manufacturing - Sub-assembly Structure DRCs

There are particular design rule checks related to sub-assembly structures that you can run in
Capital Harness Process Designer.
Note
These are not applicable to Capital Harness Costing.
Incomplete insulation
Identifies sub-assemblies which contain an insulation but which do not include all wire sub-
assemblies which run through the insulation.
Messages Variables
Insulation sub-assembly {0} does not contain {0} - Sub Assembly Name hyperlink
all its covered wires
Incomplete overbraid
Identifies sub-assemblies which contain an overbraid but which do not include all wire sub-
assemblies which run through the overbraid.
Messages Variables
Overbraid sub-assembly {0} does not contain {0} - Sub Assembly Name hyperlink
all its covered wires
Incomplete splice
Checks that all connected wire sub-assemblies are also included in a sub-assembly which
contains a splice.
Messages Variables
Splice sub-assembly {0} does not contain all {0} - Sub Assembly Name hyperlink
its connected wires
Orphaned strip
Identifies sub-assemblies which contain a wire strip object but which do not contain the wire
that owns the wire strip object.
Messages Variables
Wire strip sub-assembly {0} does not contain {0} - Sub Assembly Name hyperlink
its owner wire

December 2023
Design Rule Checks Applicable to Capital Wiring

Integrator Designs
There are specific design rule checks that you run while editing a design in Capital Wiring
Integrator.
Capital Wiring Integrator - Appearance DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404

Capital Wiring Integrator - Connectivity DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405
Capital Wiring Integrator - Consistency DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Capital Wiring Integrator - Design Assistant DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407
Capital Wiring Integrator - Library Consistency DRCs . . . . . . . . . . . . . . . . . . . . . . . . . 410
Capital Wiring Integrator - Naming DRCs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Capital Wiring Integrator - Topology Rules DRCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Capital Wiring Integrator - Appearance DRCs

Wiring Integrator design.

Identifies:
so the quick code is displayed
database
Messages Variables

December 2023

non-UNICODE font.
Messages Variables
{2} - Font type
Capital Wiring Integrator - Connectivity DRCs

Multicore wires follow different paths

Identifies wires in a multicore that follow different paths.
Messages Variables
The wires in multicore {0} do not follow the {0} - Multicore name
same bundle path, eg {1} {1} - List of wires in the multicore which
follow different paths
Unterminated bundle
Identifies bundles that do not terminate on connectors or a device.
Messages Variables
Bundle {0} on Harness {2} has an {0} - Bundle
unconnected end at {3} {2} - Harness
{3} - x,y coordinate
Empty bundle
Identifies bundles that do not contain any conductors.

December 2023
Messages Variables
Bundle {1} in Harness {2} does not contain {1} - Bundle
Wires {2} - Harness
Sections of bundle {1} in Harness {2} do not {1} - Bundle
contain Wires {2} - Harness
Capital Wiring Integrator - Consistency DRCs


Messages Variables
There is {0} pending checklist item {0} - Number
There are {0} pending checklist items {0} - Number
Unresolved comments
Messages Variables
There is {0} unresolved comment {0} - Number
There are {0} unresolved comments {0} - Number

Messages Variables
Symbol {0} is out of date for comment graphic {0} - Symbol name
at {2} in {1} {2} - X,Y coordinate
{1} - Design name
Symbol was not found for comment graphic at {1} - X,Y coordinate
{1} in {0} {0} - Design name

December 2023
Obsolete option
Messages Variables
{0} uses obsolete option {1} {0} - Object type and object name
{1} - Option name
{0} uses obsolete options {1} {0} - Object type and object name
{1} - Option names
Wiring breaks separation rules

Reads all the wires in the design that have a separation category, finds all the bundles that those
wires pass through, and then checks that the distances between those bundles in 3D space
conform to the minimum separation defined between the various categories.
If you have not set any separation categories and distances, the check reports “No separation
categories/distances have been defined for this design.”
See “Setting Separation Categories and Distances” on page 511 for how to set separation rules.
Messages Variables
No separation categories/distances have been
defined for this design. Please set separation
distances using the action in the 3D tab.
Wire {0} in bundle {1} breaks separation rules {0} - Wire name
with wire {2} in bundle {3}. {1} - Bundle name
{2} - Wire name
{3} - Bundle name
Failed to run Wiring breaks separation rules
DRC as no license is available.
Capital Wiring Integrator - Design Assistant DRCs

There are particular design rule checks related to design assistant that you can run for a Capital
Attribute/property mismatch with wiring design

Identifies attributes and properties that have been set on connectors in the Capital Wiring
Integrator design but do not match with the attributes and properties on the associated connector
in the Capital Logic Designer design. If a connector has a part number assigned in the Capital

December 2023
Logic Designer or Capital Wiring Integrator design, attributes and properties are not compared
against the associated connector.
Messages Variables
Attributes mismatch found for object {0} {0} - Object name
Properties mismatch found for object {0} {0} - Object name
{0} ({1}) - ({2}) in Logic Design {0} - Index of the mismatch
{1} - Value of the attribute or property in the
Topology design
{2} - Value of the attribute or property in the
Logic design
Unplaced harness connector

Identifies harness connectors that exist in the associated Capital Logic Designer designs but
have not been placed in the Capital Wiring Integrator design.
Messages Variables
Connector {0} from Design {1} is not placed {0} - Connector name
{1} - Design name
There are {0} unplaced Harness Connectors {0} - Number of unplaced harness connectors
in the design
Unplaced inline connector

Identifies inline connectors that exist in the associated Capital Logic Designer designs but have
not been placed in the Capital Wiring Integrator design.
Messages Variables
Connector {0} from Design {1} is not placed {0} - Connector name
{1} - Design name
There are {0} unplaced Inline halves {0} - Number of unplaced inline halves in the
design
Empty slot
Identifies slots with no placed devices.
Messages Variables
Slot {0} has no content {0} - Slot
There are {0} Slot(s) with no content {0} - Number of slots with no placed devices

December 2023
Placement conflict
Identifies placement conflicts caused by multiple constraints influencing placement.
Messages Variables
Slots {0} contain valid placement constraints {0} - Slot names
for {1}. This will result in the placement of {1} - Functional device name
{1} being determined on a first come first
served basis.
Slots {0} contain conflicting placement {0} - Slot names
constraints for {1}. This will result in the {1} - Functional device name
placement of {1} being placed in {2}.
{2} - Slot name
There are {0} Placement conflicts {0} - Number
Unassociated harness connector

Identifies harness connectors in the Capital Wiring Integrator design that have no association
with a connector in the Capital Logic Designer designs.
Messages Variables
Connector {0} from Design {1} has no {0} - Connector name
physical association {1} - Design name
There are {0} unassociated Harness {0} - Number of unassociated harness
Connectors connectors in the design
Unplaced device
Identifies unplaced devices in the current plane.
Messages Variables
Functional Device {0} is not placed {0} - Device name
There are {0} unplaced Functional Device(s) {0} - Number of unplaced devices in the design
Shared Functional Device {0} is not placed {0} - Device name
There are {0} unplaced Shared Functional {0} - Number of unplaced shared devices in the
Device(s) design
Unrouted wires
Identifies wires that have not been routed in the Capital Wiring Integrator design.

December 2023
Messages Variables
Conductor {0} from Design {1} is unrouted {0} - Wire name
{1} - Design name
There are {0} unrouted Conductors {0} - Number of unrouted wires in the design
Capital Wiring Integrator - Library Consistency DRCs

Capital Wiring Integrator design.
Inline mate part mismatch

Identifies mated inline pair halves that have library parts that are not valid mates.
Messages Variables
Inline {0} has a library part with mating {0} and {1} - Inline half names
restrictions that conflicts with Connector {1}.
Inline {0} has incorrect cavity mating. Library {0} - Inline half name
part {1} defines that cavity {2} should be {1} - Library part number
mated to cavity {3}.
{2} and {3} - Connector cavity names
Inline {0} references library part that can not {0} - Inline half name
be found.
Inline {0} has a library part with mating {0} - Inline half name
restrictions but no mate.

Identifies virtual/device/inline connectors having a cavity count that differs to that of their
corresponding library part.
Messages Variables
Connector {0} has conflicting Cavity count {0} - Connector name
from its library part {1} {1} - Library part number
Device Connector {3} on Slot Connector {1} {3} - Device connector
has conflicting Cavity count from its library {1} - Slot connector
part {2}
Connector {0} has part number {1} but no {0} - Connector name
Cavity count is specified {1} - Library part number

December 2023
Messages Variables
Device Connector {3} defined on Slot {3}- Device connector name
Connector {1} has part number {2} but no {1} - Slot connector name
Cavity count is specified

Messages Variables
{0} {1} has P/N={2} assigned to it, but that is {0} - Object type
not the latest {1} - Object name
Reference to non-existent library object

Identifies devices, wires, connectors, device connectors, multicores, shields, splices that possess
a library reference or part number property, but where a corresponding library object does not
exist.
Messages Variables
{0} {1} has a library reference and Part {0} - Object type
Number {2} but library object does not exist {1} - Object name
{0} {1} has a library reference, but no Part {0} - Object type
Number and library object does not exist {1} - Object name
Connector {0} in refinement definition of {0} and {1} - Connector names
Connector {1} has a library reference and Part {2} - Library part number
Number {2} but library object does not exist
Connector {0} in refinement definition of {0} and {1} - Connector names
Connector {1} has a library reference, but no
Part Number and library object does not exist


December 2023
Messages Variables
Status of library part for {0} {1} is ''{2}'', not {0} - Object type
current {1} - Object name
{2} - Library part status
Status of library part for {0} is ''{1}'', not {0} - Object name
current {1} - Library part status

At every harness level, examines the cavities of connectors and ring terminals with a library
part, and considers all combinations of each cavity with its connected conductors (wires, nets,
and shields), and identifies the following:
cavity.
on the cavity.
Messages Variables
In harness {0} level {1}, wire {4} does not fit {0} - Harness name
cavity and the values defined on the Single {3} - Cavity number

December 2023
Messages Variables
In harness {0} level {1}, wires {4} do not fit {0} - Harness name
cavity and the values defined on the Multiple {3} - Cavity number
connector {2} fits cavity {3} and accepts wire {1} - Harness level
{4}
Terminal material on the wire does not match
the wire fit profile of the library terminal. {3} - Connector cavity
{4} - Wire name
connector {2} fits cavity {3} and accepts wires {1} - Harness level
{4}
Terminal material on the wires does not match
the wire fit profiles of the library terminals. {3} - Connector cavity
{4} - Wire names
does not fit wire {4} {1} - Harness level
terminal part on wire (Single wire). {4} - Wire name
does not fit wires {4} {1} - Harness level
terminal part on wires (Multiple wires). {4} - Wire names

following:

December 2023
accept wires.
Messages Variables
In harness {0} level {1}, terminal {6} in {0} - Harness name
cavity {3} of connector {2} does not accept {1} - Harness level
wire(s) {4}
Same terminal part exists on both the wire and
in the housing definition, but no wire fit {3} - Connector cavity
library.
{4} - Wire names
In harness {1} level {2}, terminal {3} on {1} - Harness name
wire(s) {6} is not defined for cavity {4} in {2} - Harness level
connector library part {5} on {0}
Terminal part on the wires is not defined in the
{4} - Cavity number
In harness {1} level {2}, seal {3} on wire(s) {1} - Harness name
{6} is not defined for cavity {4} in connector {2} - Harness level
library part {5} on {0}
{3} - Seal part number
Seal part on the wires is not defined in the
{4} - Cavity number
In harness {0} level {1}, seal {6} in cavity {3} {0} - Harness name
of {5} {2} does not accept wire(s) {4} {1} - Harness level
Seal part on the wires matches the housing {6} - Seal part number
definition, but it has no wire fit.
{3} - Cavity number
{5} - <connector or ring terminal>
{4} - Wire names

December 2023
Messages Variables
have different values for attribute terminal part {1} - Harness level
at connector {2} cavity {3}:{4}
wires are different. {3} - Connector cavity
{4} - Wire names
have different values for attribute terminal {1} - Harness level
material at connector {2} cavity {3}:{4}
{4} - Wire names
have different values for attribute seal part at {1} - Harness level
connector {2} cavity {3}:{4}
{4} - Wire names
No wire fit defined in terminal {3} for cavity {3} - Terminal part number
{1} in connector library part {2} on {0} {1} - Cavity number
Same terminal part is present on the wire and {2} - Connector library part number
library.
No wire fit defined in seal {3} for cavity {1} {3} - Seal part number
in connector library part {2} on {0} {1} - Cavity number
Same seal part is present on the wire and in the {2} - Connector library part number
housing definition, but no wire fit profiles
exist on the seal part in the library. {0} - Connector name

Identifies objects that have a “Not-On-BOM” attribute with a value different to its library
setting.
Messages Variables
{0} {1} 's Include On Bom status is different {0} - Object type
to its library part. {1} - Object name

December 2023

Identifies inline and virtual connectors that have no library part assigned.
Messages Variables
{0} {1} has no library part {0} - Object type
{1} - Object name
Library part required for slot

Identifies slots containing devices that have no library part assigned.
Messages Variables
Slot {0} has no library part {0} - Slot name

Messages Variables
Library part {0} of {1} {2} has invalid {0} - Library part number
scoping. Component Scoping: {3}. {4} {1} - Object type
Scoping: {5}
{2} - Object name
{3} - Scope applied to the library component
{4} - "Design" or "Project"
Library part {0} of Backshell {2}:{3} has {0} - Library part number
invalid scoping. Component Scoping: {4}. {2}- Owning connector of the backshell
{3} - Backshell name
{4} - Scope applied to the library component
and the scope applied to the design or project
Capital Wiring Integrator - Naming DRCs

There are particular design rule checks related to naming that you can run for a Capital Wiring
Integrator design.
Duplicate names in the design

Identifies objects having a name that is identical to that of another object of the same kind on the
same design.

December 2023
Messages Variables
There were {0} pairs of objects with duplicate {0} - Number of pairs of objects with duplicate
names names
Duplicate names in a harness

Identifies object names that are not unique on a harness. This check compares objects against
those of the same object type only.
Messages Variables
There were {0} groups of objects whose {0} - Number of groups of objects with
names clash within a harness duplicate names
Capital Wiring Integrator - Topology Rules DRCs

There are particular design rule checks related to topology rules that you can run for a Capital
Assign connector rule violation

Identifies mappings between device connectors and virtual connectors that violate any “Assign
by Attribute/Property” constraints (rules).
Messages Variables
Mapping footprint Connector {0} to {1} {0} and {1} - Connector names
violates connector assignment constraint on {2} - Slot name
Slot {2}
Minimum splice separation rule violation

Identifies splices that violate any “Minimum Splice Separation” constraints (rules). Also reports
the bundle and harness on which the violation exists.
Messages Variables
Splice {0} violates separation constraint from {0} - Splice name
Connector {2} on Bundle {3}, Harness {4} {2} - Connector name
{3} - Bundle name
{4} - Harness name

December 2023
Messages Variables
{1} {2} on Bundle Region {3}, Bundle {4}, {1} - Object type
Harness {5}
{2} - Object name
{3} - Bundle region
{4} - Bundle name
{5} - Harness name
Take Out {1} on Bundle {2}, Harness {3} {1} - Takeout name
{2} - Bundle name
{3} - Harness name
Take Out {1} on Bundle Region {2}, Bundle {1} - Takeout name
{3}, Harness {4}
{2} - Bundle region
{3} - Bundle name
{4} - Harness name
Splice {2} on Bundle {3}, Harness {4} {2} - Splice name
{2} - Bundle name
{4} - Harness name
Bundle Device {2} on Bundle {3}, Harness {2} - Bundle device name
{4}
{3} - Bundle name
{4} - Harness name
Missing custom constraint

Identifies any custom constraints that have been defined for an object but are not loaded in
Capital Wiring Integrator any longer.
Messages Variables
Custom Constraint {0} on {1} {2} is missing {0} - Custom constraint name
from plugin {1}- Object type
{2}- Object name
Custom constraint {0} on design {1} is {0} - Custom constraint name
missing from plugin {1}- Design name

December 2023

Identifies any objects that violate any “Set Topology Attribute/Property on Object” constraints.
Messages Variables
{2} should be {3} {1} - Object name
{2} - "Attribute" or "Property" and the
attribute/property name
{3} - Value specified by the constraint
{2} is missing {1} - Object name
{2} - "Attribute" or "Property" and the
attribute/property name
Cannot validate {0} rule on {1} {2} because {0} - Name of the attribute or property
conflicting constraints were found on {3} and controlled by the constraint
{4} {1} - Object type
{2} - Object Name
{3} and {4} - Objects to which both conflicting
constriants are applied
Cannot validate {0} rule on {1} {2} because {0} - Name of the attribute or property
conflicting constraints were found on {3} controlled by the constraint
{1} - Object type
{2} - Object Name
{3} - Object to which both conflicting
constriants are applied
Cannot validate {0} rule on {1} {2} {0} - Name of the attribute or property
controlled by the constraint
{1} - Object type
{2} - Object Name
Slot that breaks placement rule

Identifies devices that violate any “Place by Attribute/Property” constraints (rules). Also reports
the slot in which the violation exists.

December 2023
Searching for a Design across all Projects
Messages Variables
Device {0} violates placement constraint on {0} - Device name
Slot {1} {1}- Slot name
Standard Device {0} is placed in Ground Slot {0} - Device name
{1} {1}- Slot name

Identifies wires that violate any “Route by Attribute/Property” constraints (rules). Also reports
the signal, bundle, inline connector and harness on which the violation exists.
Messages Variables
constraint on Bundle {2}, Harness {3} {1} - Signal name
{2} - Bundle name
{3} - Harness name
constraint on Bundle Region {2}, Bundle {3}, {1} - Signal name
Harness {4}
{3} - Bundle name
{4} - Harness name
constraint on Connector {2}, Harness {3} {1} - Signal name
{3} - Harness name

In design applications, you can search for a design across all the projects in your database and
navigate to the design from the search results.
Caution
This search functionality is aware of domain restrictions. For example, if a project has a
domain restriction and a user performing this search does not have access to that domain,
the search results will not include designs from that project.

December 2023
Procedure
1. Press Space Bar and enter Search Designs.
A Design Search tab displays in the Output Window at the bottom of the application
window.
2. Enter the Name, Part Number (applicable to harness designs), Revision, Short
Description, or a combination of these for the design and click the button.
By default, the search looks for designs whose attributes start with the strings you have
entered. For example, if you enter a Name of 2-Aud, the search results include designs
with names such as 2-Audio, 2-Audio-Basic, and so on. When you enter values in
multiple fields, the search results are designs that match all the specified criteria.
You can use additional wildcards (*) in the strings. For example, if you enter a Name of
*Aud, the search results include designs with names such as 2-Audio, 4-Audio-Basic,
and so on.
Note
The Part Number field offers automatic completion of the string that you enter.
Results
The table in the Design Search tab lists details for the designs matching your search criteria:
• Project
The project in which the design is located.
• Design
The name, revision, and short description of the design. This is a hyperlink. You can
click it to navigate to that design in the appropriate application (which will open
automatically). When you do this, the system opens the project and highlights the design
in the Project Browser Window at the top left of the application window.
• Abstraction
The abstraction assigned to the design.

December 2023
• Type
The type of design, such as logical, harness, and so on.
Note
The columns are sortable by clicking in the column header name. The columns are filterable
by clicking the dropdown in the header or by typing in the header.
You can save the search results to a comma separated variable (CSV) file by clicking the Save
To CSV ( ) button at the top right of the table.

December 2023
Design Folder
Design Folder
To aid the management of designs and their design revisions, you can create user-defined
design folders in which you can group and organize your various designs. This is how they
appear in the Project Browser Window.
All of the Capital applications display the user-defined design folder structure, and you can edit
the structure in Capital Project Manager as well as the design applications.
The following 3 folder types may exist in a design folder structure:
• Design Folder- folders containing a design's specific design revisions and/or any other
normal folders (see below) that you have created. All design revisions under this folder
must belong to the same design. You cannot create a design folder, they are created by
the application when a design is created.
• Normal Folder- user-defined folders that can have any name and can contain design
folders, other normal folders and/or revision nodes (see below).
• Revision Node - represent a particular design revision and can have a design folder or a
normal folder as an immediate parent. Revision nodes cannot have sub-folders and must
have a design folder somewhere in their folder structure.
The following rules apply to the usage of user-defined design folders:
• If a revision is copied to a normal folder, a check is performed to verify that the normal
folder has a parent design folder for that revision.
• A revision cannot be moved into a revision node if a design folder is found that is not the
revision's true parent. If there is no design folder, the revision's design folder is created
first and is added to the parent normal folder and the revision added to the newly created
design folder.
• You cannot add a revision to a design folder that does not represent that revision’s
design.
Editing Design Folders in Design Applications

You can edit the design folder structure of a project in the design applications (that is, create,
delete, rename, and move design folders). You can do this when users are working concurrently
in a project. The system propagates any changes to the other users.
If you want to do this in Capital Project Manager, see Creating Design Folders in Capital
Project Manager in the Capital Project Manager User Guide.

December 2023
This video shows examples of tool behavior when you edit design folders (create, delete,
rename, move).
Procedure
In a design tool, decide how you want to edit the design folders in the Project Browser Window:

Create a new design folder at 1. Right-click on the project name folder and choose
the root level of the project. New Folder; the New Folder dialog box displays.
2. Specify the folder name and click Create; the
system adds the folder to the Project Browser
Window.
Note: You can right-click the new folder to access
menus for creating new designs.
Create a child design folder 1. Right-click on the existing design folder and
underneath an existing choose New Folder; the New Folder dialog box
design folder. displays.
2. Specify the folder name and click Create; the
system adds the child folder under the existing
folder in the Project Browser Window.
Note: You cannot create a new design folder under
a design, design revision, or build list. You can
right-click the new folder to access menus for creating
new designs.
Rename a design folder. 1. Right-click on the folder and choose Rename; the
Rename dialog box displays.
2. Specify the new name and click Rename; the
system renames the folder in the Project Browser
Window.
Delete a design folder. 1. Right-click on the folder and choose Delete; the
system asks you to confirm the deletion.
2. Click Delete; the system deletes the folder
including any child folders and designs in it.

December 2023

Move a design folder. Drag and drop the design folder on to the project folder
or another design folder in the Project Browser
Window; the system moves the design folder and
anything in it under the target folder.
Move a design. Drag and drop the design on to the project folder or
another design folder in the Project Browser Window;
the system moves the design under the target folder. It
also moves any design revisions listed below the
design.
Move a design revision. Drag and drop the design revision on to the project
folder, another design folder, or a node for the design
to which the revision belongs; the system moves the
design revision under the target folder or design node.
If you move it under the project folder or a design
folder, the system creates a design node above the
revision.
Note
When dragging a folder over an unexpanded folder containing child folders, the
system expands the tree to see the child folders. The mouse cursor indicates
locations where you cannot drag a folder ( ).
Results
The system propagates the changes to any other uses when they next invoke an action from the
Project Browser Window.
Related Topics
New Folder or Rename Dialog Box

December 2023
Build List
Build List
A build list is a container for designs, representing a subset of a vehicle’s connectivity and
topology at a single point in the design lifecycle. Any number and configuration of build lists
may be created for a project.
See Build List in the Capital Project Manager User Guide for full details of this concept and
links to related tasks.

Setting an Active Build List

You can set an active build list in Capital Logic Designer, Capital Wiring Integrator, Capital
Platform Designer, or Capital Systems Integrator. When a build list is active, any cross-
references in the designs in the build list will list only those instances in designs on the active
build list.
If you have set an active build list and close the project, the build list will not be active when
you next open the project.
When a build list is active and you open a diagram that is not on that build list, the system asks
you to set an alternative build list as active. See “Selecting an Alternative Build List” on
page 427.
Note
Setting an active build list within a Capital Logic Designer design does not set the analysis
scope to that build list. See “Scoping”in the Capital Analysis User Guide for more
information.
Procedure
1. Press Space Bar and enter Set Active.
2. The Set Active Build List facility is displayed. Select the build list to set as active. If it
has a description, it is displayed in the Description box. The designs in the build list are
displayed in the Contents box. The Integrator Design field displays the source topology
design from where the Logic build list was generated. This is useful when Capital
Schematic Generator for Systems Integrator is used to create diagrams from a Capital
Logic Designer build list containing multiple logic designs.
Click the OK button.
3. In the Project Browser Window, the designs from the active build list have an orange
indicator next to them.

December 2023
Selecting an Alternative Build List
Selecting an Alternative Build List

This topic describes how to select an alternative build list.
Procedure
1. When you open a diagram for a design that is not in the build list that is currently active,
the Select an Alternative Build List dialog is displayed. It lists the build lists to which
the design belongs.
2. Select the build list that you want to set as active. If it has a description, it is displayed in
the Description box. The designs in the build list are displayed in the Contents box.
3. In the Project Browser Window, the designs from the active build list have an orange
indicator next to them.
Applying Scopes to a Project or Design

You can apply scopes to a project or design. Component Scoping is a code based method for
controlling access to component data across Capital. Scope codes can be applied to any type of
component, sub-component, design or project. They restrict the use of components within
projects and designs. Whenever the system or a user selects a component, only those
components within the scopes applied to the project or design are available.
If scopes are defined at project level and there are no design-level scope definitions, the project-
level scopes are used for the designs. If scopes are defined both at project and design level, the
design-level scopes are used within a design.
Only one customer or manufacturing site scope code is allowed per design or project.
For a usage example detailing how to use component scoping, including applying it to projects
or designs, see “Usage Example - How To Use Component Scoping” in the Capital Component
Manager User Guide.
Note
You can use Extensibility Plugins to manage component scoping. If a plugin is available
then it will override the default part selection rules. For more information about developing
and using extensibility plugins, see the PluginDevelopment.pdf file that is located in the
<install_directory>\doc\plugin folder.
Prerequisites
• The required scopes must have been created in Capital Component Manager.
Procedure
1. Right-click the project name or design in the Project Browser and select Edit.

December 2023
The Edit Project Dialog Box or Edit Design dialog box displays.
2. Click Properties.
The Edit Properties dialog box or Edit Design Properties Dialog Box displays.
3. Select the Scopes tab.
The scope codes that have been created in Capital Component Manager are displayed in
the Available list.
4. Select the scopes that you want to apply to the project or design and click Add.
The selected scopes are added to the Selected list.
Note
You can also remove scopes, that you have applied, by selecting them in the
Selected list and clicking Remove. To empty the selected list, click Remove All.
5. Click OK.
Results
• The selected scopes are applied to the project or design.
• If a library component has had scopes applied to it, these dictate whether it is available
for selection within the project or design.
• For a design, if you hold your mouse cursor over the design name in the Project
Browser, the applied scopes are displayed.

December 2023
Options and Option Relationships
Options and Option Relationships

Options and variant options can be created at project level in the design applications. An option
is a code representing a feature or capability in a vehicle. Options are used in expressions to
convey the conditional inclusion of an object in a particular vehicle configuration.
Creating an Option at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Defining Inclusive and Exclusive Relationships for an Option . . . . . . . . . . . . . . . . . . . . 430
Creating an Option Folder at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431
Deleting an Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Creating an Option at Project Level

You can create options (including variant options) at a project level. You can specify inclusive
and exclusive relationships for the option.
Procedure
1. With the project open, press Space Bar and enter Data - Options.
The Options Dialog Box is displayed.
2. Select the folder of the Options Browser in which you want to create the option:
3. Click Create anew Option ( ); a new option is added to the Options Browser.
4. Specify the Name and Description for the option. In addition, specify whether it is an
Electrical option and whether it is a Variant option.
5. Define any Inclusive or Exclusive relationships for the option.
6. Click OK.
Related Topics
Creating an Option Folder at Project Level
Defining Inclusive and Exclusive Relationships for an Option
Creating an Option Combination at Project Level
Adding a Valid Selection to an Option Combination
Deleting a Valid Selection from an Option Combination
Deleting an Option

December 2023
Defining Option Relationships
Defining Option Relationships

Once created for a project, an option may be applied to any of the designs created within that
project. The options applied to designs are known as “applicable options”. There are three ways
to define relationships between options at project level:
1. Define inclusive and exclusive relationships for individual options. See “Defining
Inclusive and Exclusive Relationships for an Option” on page 430.
2. Group options within an option folder and specify whether they are mutually exclusive
(that is, none of the options within the folder can be selected together in a vehicle) or
mandatory (that is, at least one of the options within the folder must be selected in a
vehicle). See “Creating an Option Folder at Project Level” on page 431. Also available
at system level (in Capital Project Manager).
3. Create option combinations that enable you to specify valid selections of options. See
“Option Combinations” on page 433.
Related Topics
Deleting an Option
Defining Inclusive and Exclusive Relationships for

an Option
You can define inclusive and exclusive relationships between options at a project level.
Inclusive options are ones that you must include together in a vehicle. You cannot include
exclusive options together.
Procedure
2. Select the option in the Options Browser.
The fields on the right of the dialog display the values for that option.

December 2023
3. Add any Inclusive or Exclusive relationships for the option - click the button above
either the Inclusive or Exclusive panes to open the Choose Options Dialog Box.
4. Click OK.
Tip
You can repeat steps 2 to 3 and define inclusive and exclusive relationships for
multiple options before clicking OK.
Related Topics
Deleting an Option

You can create an option folder at a project level from a design application. You can specify
whether the options in the folder are mutually exclusive or mandatory.
Procedure
2. Select the folder of the Options Browser in which you want to create the option folder.
3. Click Create a new folder ( ).
A new option folder is added to the Options Browser.

4. Specify the Name of the folder and whether it will contain options that are Mutually
Exclusive or Mandatory.
5. Click OK.
Caution
If an option in a mutually exclusive or mandatory folder is changed to be a non-
electrical option it is removed from the folder when you click OK in the Options
dialog box.

December 2023
Related Topics
Deleting an Option

December 2023
Option Combinations
Option Combinations
An option combination is a collection of options that have been arranged into specific, valid
selections.
Option combinations and valid selections allow the representation of complex relationships
between a group of otherwise unrelated options by specifying their allowed combinations.
Option combinations reduce the allowable combinations of a set of options, which in turn helps
to limit the potentially large number of harness levels that can be generated by the Composite
Wiring Synthesis procedure in Capital Systems Integrator.
For example, if no inclusive or exclusive relationships exist between the six options A, B, C, D,
E, F, and they are all optional in a particular vehicle model, there are 64 possible combinations.
To lower the complexity (or for other design reasons), the six options can be added to an option
combination and arranged to permit only the following “valid selections”:
• (A, B, C, D, E, F)
• (B, F)
• (A)
• (F)
The following considerations apply to option combinations and valid selections:
• Once an option has been added to an option combination it can then not be added to any
other option combinations. That is, an option cannot be added to multiple option
combinations. (Note that an option does not have to be added to any option
combination).
• An option combination does not have to include a valid selection that has all the options
selected.
• The only limitation on an option combination’s valid selections is that they must
conform to any normal inclusive/exclusive relationships between the options.
• If it is permitted for none of the options in an option combination to apply to a vehicle,
an explicit, empty valid selection must be created for that option combination.
Creating an Option Combination at Project Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Adding a Valid Selection to an Option Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Deleting a Valid Selection from an Option Combination . . . . . . . . . . . . . . . . . . . . . . . . 436

In design applications you can create an option combination and its valid selections at project
level. Option combinations and valid selections allow the representation of complex

December 2023
Option Combinations
relationships between a group of otherwise unrelated options by specifying their allowed

combinations. Option combinations reduce the allowable combinations of a set of options,
which in turn helps to limit the potentially large number of harness levels that can be generated
by the Composite Wiring Synthesis procedure in Capital Systems Integrator.
Procedure
1. Press Space Bar and enter Data - Options.
2. Select the Combinations folder in the Options Browser and click Create a new
Combination ( ).
A new option combination is added to the Combinations folder in the Options Browser.
3. Specify the Name for the option combination.
4. Drag and drop an option to be included in the option combination from its location in the
Options Browser tree to the option combination node in the tree.
The option is listed under the option combination as well as in its original location in the
tree.
Note
You cannot add non-electrical or variant options to an option combination.
5. Repeat step 4 for each option that you want to add to the option combination.
6. Select the option combination in the Options Browser.
The options are displayed as columns in the Valid Selections table.
7. Click Insert a row ( ) to add a valid selection row to the table.
The row is added to the table.

8. Specify a unique identifier for the valid selection in the Name column.
9. In the row, select the options that are included in the valid selection.
10. Repeat steps 7 to 9 for each valid selection in the option combination.
11. Click OK.
Caution
If an option in an option combination is changed to be a non-electrical option it is
removed from the option combination when you click OK in the Options dialog box.

December 2023
Option Combinations
Tip
You can repeat steps 2 to 10 and create multiple option combinations before clicking
OK.
Related Topics
Deleting an Option

You can add a valid selection row to the Valid Selections table for an option combination in the
Options Dialog Box. Option combinations and valid selections allow the representation of
complex relationships between a group of otherwise unrelated options by specifying their
allowed combinations.
Procedure
1. Press Space Bar and enter Data - Options.
The Valid Selections table displays the existing valid selections for the option
combination.
3. Click Insert a row ( ) to add a valid selection row to the table.
The row is added to the table.

4. Specify a unique identifier for the valid selection in the Name column.
5. In the row, select the options that are included in the valid selection.
6. Click OK.
Caution
If an option in an option combination is changed to be a non-electrical option it is
removed from the option combination when you click OK in the Options dialog box.

December 2023
Option Combinations
Tip
You can repeat steps 3 to 5 and create multiple valid selections before clicking OK.
Related Topics
Deleting an Option

You can delete (remove) a valid selection row from the Valid Selections table for an option
combination in the Options Dialog Box. The system will no longer apply that valid selection.
Procedure
The Valid Selections table displays the existing valid selections for the option
combination.
3. Select the row that you want to delete.
Note
You can multi-select rows and delete multiple rows simultaneously.
4. Click Remove the selected rows ( ).
The row is deleted from the table and the valid selection is deleted from the option
combination.
5. Click OK.
Tip
You can repeat steps 3 to 4 and delete multiple valid selections before clicking OK.
Related Topics

December 2023
Deleting an Option

Deleting an Option
Deleting an Option
In design applications, you can delete a project-level option from the Options Dialog Box when
you no longer want to use it.
Procedure
1. Select the option in the Options Browser.
2. Click Delete selected objects ( ).
Results
• If the option is used in a combination an error message is displayed giving details of the
combination that is using the option, and the option is not deleted.
• If the option has been specified as an applicable option for a design an error message is
displayed giving details of the design that is using the option, and the option is not
deleted.
• If the option is not used in a combination and has not been specified as an applicable
option for a design it is removed from the Options Browser.
Related Topics

December 2023
Engineering Change Orders

An engineering change order (ECO) is an instruction to make a change to one or more designs
(for example, an instruction to change the backshells on connectors from straight to right-angle
backshells). Once the change has been made, the ECO can be set as completed.
In the Capital design tools, you can capture and store design changes against an ECO. In Capital
Harness Designer and Capital Harness Designer Modular only, you can automatically re-apply
the ECO onto a different design revision at a later date.
Image files can be added to the ECO and opened in the Image Viewer, to illustrate and explain
the before and after details of the changes required.
Since the scope of an ECO can span many designs within Capital, each design within an ECO
has a Completion Status (Not Started, In Progress, or Completed), and only when the
completion status for each design is set to Completed, can the release level of the ECO be
changed to Released. However, the release level assigned to an ECO does not have to be the
same release level assigned to the impacted design revisions.
Note
An ECO can transition between Draft, Obsolete, Released - these levels can be configured
within Capital Project Manager.
You can perform the following ECO procedures:
• Manually create ECOs within the Capital design applications.

• Transfer ECOs between projects and databases.
• Assign existing ECOs to designs.
• Import and export ECO impacted design changes using the Capital applications.
When you export and import project data (as a copy or dataset), all ECO data is included.
However, if you export the project as a template, no ECO data is included.
Working with an ECO Created in Capital . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439

Creating an Engineering Change Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Deleting an Engineering Change Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Viewing Engineering Change Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Assigning an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444
Capture and Apply a Change Within an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445
Identification of Topology Changes with Hotspots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Harness Object Behavior on Applying ECO Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . 452

December 2023
Working with an ECO Created in Capital

There is a basic flow for working with engineering change orders across multiple applications in
Capital.
Procedure
1. In Capital Project Manager or within any design tool, use the Engineering Change
Orders Dialog Box to create an ECO for a required change, and then associate the ECO
with the impacted design revisions. See “Creating an Engineering Change Order” on
page 439. The Release Level for the ECO (not necessarily for the associated design
revisions) is Draft and the Completion Status value for each associated design is Not
Started.
2. In the design tools, make the required change to the designs.
3. For each design, open the Edit Design Properties Dialog Box and click the ECO tab.
In the Design Status column for the ECO, change the value to Completed.
Note
You can also change the status on the Engineering Change Orders tab, see “Start and
Stop Capturing an ECO Change” on page 446.
4. In Capital Project Manager or a design tool, open the Engineering Change Orders
Dialog Box; note that the Completion value for each design associated with the ECO has
changed to Completed. Change the ECO Release Level to Released.
Related Topics
Creating an Engineering Change Order
Deleting an Engineering Change Order
Viewing Engineering Change Orders
Engineering Change Orders Dialog Box

You can create an engineering change order (ECO) for use in Capital. Engineering change
orders (ECO) enable you to track the implementation of any instructions to make a change to
one or more designs. Once the change has been made, the ECO can be set as “Completed”.
Prerequisites
• Your user account must have the “Engineering Change Order Creation” permission set.

December 2023
Procedure
1. Either:
In Capital Project Manager: In the browser tree on the left of the application, navigate to
and double-click, or right-click, the Engineering Change Orders node and select Edit;
the Engineering Change Orders Dialog Box is displayed.
or
In a design application: Press Space Bar and enter Engineering Change Order; the
Engineering Change Orders dialog box is displayed.
2. If the ECO category to which the ECO belongs does not yet exist, create it:
a. Click above the Category Window; a new category is added to the window.
b. Click the new category and edit its name.

3. Click next to the category name; a new ECO is added under the category.
4. Click the new ECO and edit its name.

5. Ensure that the ECO is selected in the Category Window and specify its Short
Description, Release Level, Description and Properties. If required, also specify the
effectivity for any design revisions that will be created.
6. Specify the designs impacted by the ECO:
a. In the Impacted Designs panel, click ; the Design Revision Selection dialog box is
displayed.
b. Select one or more impacted designs and click OK; the designs are added to the list.
7. If required, add an image(s) to illustrate the change. Use the Images panel buttons to
paste from the clipboard, take a screenshot of the currently visible diagram canvas area,
or add an image from a file. Once added, you can double-click a file to open it in the
Image Viewer.
8. If you do not want to create new design revisions for this ECO, click OK and you have
finished.
If you want to create new design revisions, click the Manage Designs & Effectivty ( )
button above the Impacted Designs table; the Manage Designs & Effectivity Dialog Box
displays. The system saves any edited ECOs at this point.

December 2023
Note
Select “Update ECO design references” to propagate the new design revisions back
to the Impacted Designs table on the Engineering Change Orders dialog box.
11. Click OK.

If you are creating new design revisions, a progress dialog box displays. This can take a
couple of minutes.
Results
• An association is created between the ECO and the impacted designs and any image
files added.
• Design revisions are created as specified with the effectivity entered on the Engineering
Change Orders dialog box.
• If you created new design revisions, a Manage Designs & Effectivity Report displays. In
design applications, this displays as a tab in the output window at the bottom right of a
design application window. In Capital Project Manager this displays as a dialog box. It
reports information regarding any changes made to engineering change orders and
designs while the system created design revisions.
• The audit trail records such actions as Engineering Change Order modified, Engineering
Change Order Effectivity added, Design created, Design revised, Logical Effectivity
added, and Harness Effectivity added.
Related Topics

You can delete an engineering change order (ECO) from the system when you no longer want to
use it.
Prerequisites
• Your user account must have the “Engineering Change Order Deletion” permission set.

December 2023
Procedure
1. Either:
In Capital Project Manager: In the browser tree on the left of the application, navigate to
and double-click, or right-click, the Engineering Change Orders node and select Edit;
the Engineering Change Orders Dialog Box is displayed.
or
In a design application: Press Space Bar and enter Engineering Change Order; the
Engineering Change Orders dialog box is displayed.
2. Select the ECO in the Category Window and click next to the category name to which
it belongs.
3. The selected ECO is deleted.
4. Click OK.
Results
• The association between the ECO and the impacted designs is removed.
• The ECO is removed from the project
Related Topics

You can view the details of an engineering change order (ECO) in any of the Capital design
applications. You can view the ECOs applicable to the active design or all ECOs for the project.
The columns displayed can be configured in the almintegration.xml file which is located in the
capital_home\config folder.
Prerequisites
• ECOs have been created for the relevant design.
• The relevant designs have been associated to the ECOs.
Procedure
1. Open the diagram in the relevant Capital design application.

December 2023
2. Select the Layout > ECOs action on the Capital ribbon. Alternatively press Space Bar
and enter ECOs.
Results
• ECOs applicable to the current project are displayed in the Engineering Change Orders
Tab, below the diagram. Click the ( ) button to toggle the display to show ECOs
applicable to the current open design.
Note
If no diagram is open, all ECOs applicable to the current project are displayed.
• If the diagram is currently open and the filter for current diagram is toggled on, an
ellipsis displays in the Name row as inFigure 2-2 .
Figure 2-2. Name Ellipsis
Click the ellipsis to display a sub menu as in Figure 2-3. See the “Engineering Change
Orders Tab” topic for full details about these menu items.
Figure 2-3. Name Sub Menu
Related Topics
Engineering Change Orders Tab

December 2023
Assigning an ECO
Assigning an ECO
This topic describes how to assign one or more ECOs, to one or more designs.
Procedure
1. In the Project Browser Tree, choose one or more designs that you want to assign ECOs
to.
2. To open the Assign ECOs Dialog Box either:
In Capital Project Manager: Right-click the selected design(s) and select Assign ECOs.
or
In a design application: Press Space Bar and enter Assign ECO, click the
Capital > Data > Assign ECOs ribbon action, or right-click the selected design(s) and
select Assign ECOs.
3. Within the Assign ECOs dialog box, choose one or more ECOs listed in the Category
Window.
Note
If you want to see the details of an ECO at any time, select it and click the icon; a
read-only window showing the ECO details opens. Click the same icon to close the ECO
details tab.
4. Click Assign.
Results
The system adds the selected designs to each of the selected ECOs.
Related Topics

December 2023
Capture and Apply a Change Within an ECO

You can capture and store design edits within an ECO impacted design for automatic
implementation onto another design at a later date. This functionality is available in Capital
Harness Designer and Capital Harness Designer Modular only.
A common example is the application of a “cost only” design change, illustrated in Figure 2-4
below, where there is a requirement to process and report the cost impact of a change based on a
given version of a design, but implement it on the live design at a later date, when approval for
the change is given.
Figure 2-4. ECO Cost Only Change Flow
• In step 1, ECO(s) are created with the change details.

• In step 2, a copy of the design is made and associated with the ECO. The changes
detailed in the ECO are made and captured. The harness is engineered and costing
reports for the changes are created and sent for approval.
• In step 3, approval is received and a revision of the design is created as a target for
selected captured changes to be applied onto.
• In step 4, the selected changes captured in step 2 are automatically applied onto the
target design.
Capturing a Change with an ECO
ECO Impacted Design
Start and Stop Capturing an ECO Change
ECO Import and Export
Applying a Stored Change from an ECO
Identification of Topology Changes with Hotspots

December 2023
Harness Object Behavior on Applying ECO Changes

ECO Impacted Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Start and Stop Capturing an ECO Change. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Capturing a Change with an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448
Applying a Stored Change from an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
ECO Impacted Design

An ECO can have one or more associated impacted designs. The system can store the particular
data against each impacted design
• Captured ECO data. See “Capturing a Change with an ECO” on page 448.
• Images. You can add PNG, JPG, or JPEG files to help illustrate details of the ECO.
You can export and import ECO impacted designs between ECOs in the same or different
projects or databases. See “ECO Import and Export” on page 464.
Related Topics
Start and Stop Capturing an ECO Change

You can change the completion status against an ECO Impacted Design to start and stop the
capture of ECO changes.
Figure 2-5 shows the completion status changes.
Figure 2-5. Status Changes

December 2023
Note
If you change the completion status from Completed to In Progress, any captured changes
are deleted from the ECO impacted design. If you change the completion status from In
Progress to Not Started, the baseline point where the capture started is deleted from the ECO
impacted design.
You can change the completion status:
• From the ECO tab on the Edit Design Properties dialog box.
Figure 2-6. ECO Tab
• From the Engineering Change Orders Tab.
Note
The ellipsis in the Name row only displays if the diagram attached to the ECO is
currently open, and the filter for current diagram is toggled on, see Viewing
Engineering Change Orders for more details.
Figure 2-7. ECO Console

December 2023
Related Topics

When an ECO is received, you can make and capture the changes on a copy of the design and
implement them at a later date on a revision of the design.
The procedure in this topic relates to step two of the “ECO Cost Only Change” flow, capturing
the change, see Figure 2-4 on page 445.
Prerequisites
• The required Impacted Design is associated to the ECO. See “Creating an Engineering
Change Order”.
• The Completion Status of the Impacted Design on the ECO is set to Not Started.
Procedure
1. Open the required design diagram.
2. Press Space Bar and enter ECOs.
The Engineering Change Orders Tab opens in the output window below the diagram.
3. Click the ellipsis button in the Name cell of the relevant ECO and choose Completion
Status > In Progress.
Note
The ellipsis in the Name row only displays if the diagram attached to the ECO is
currently open, and the filter for current diagram is toggled on, see “Viewing
Engineering Change Orders” for more details.
Alternatively, open the Edit Design Properties Dialog Box for the required design and
click the ECO tab. In the Design Status column for the ECO, change the value to In
Progress and click OK.
The Create Baseline message box is displayed.
4. Click the Create Baseline button.
The system creates a baseline and starts capturing the ECO changes you make from this
point. This is indicated by the Completion Status of the impacted design changing to “In
Progress (Capturing Changes)” on the Engineering Change Orders Dialog Box.
Alternatively, click the Do not Create Baseline button, to not capture the ECO changes.
5. Make the appropriate changes as documented in the ECO description and illustrated by
any associated image files.

December 2023
6. Optionally, add images to confirm that the changes have been made.
7. Save the design.
8. In the Engineering Change Orders Tab, click the ellipsis button in the Name cell and
choose Completion Status > Completed.
Results
• The system stops capturing. All the changes you have made are captured and stored
against the ECO impacted design. This is indicated by the Completion Status of the
impacted design changing to “Completed (Changes Captured)” on the Engineering
Change Orders dialog box.
Related Topics

When an ECO is received, you can make and capture the changes on a copy of the design and
implement them at a later date on a revision of the design.
The procedure in this topic relates to step 4 of the “ECO Cost Only Change” flow, applying the
change, see Figure 2-4 on page 445.
Prerequisites
• The steps in the “Capturing a Change with an ECO” topic have been completed.
• A target design which is a revision or copy of the source design used in the “Capturing a
Change with an ECO” topic is open.
• The target design has been added as an impacted design of the ECO and has a
Completion Status of In Progress. See “Creating an Engineering Change Order” on
page 439.
Procedure
1. Press Space Bar and enter Apply.
2. The Applicable Changes Dialog Box displays. Select the required ECO impacted design
and click the Apply Change button.
3. The Change Manager Apply ECO Dialog Box and/or the Change Manager Preview
ECO Dialog Box are displayed, depending on which was displayed at the end of the

December 2023
previous session. (You can use the View ( )Toolbar button to toggle between the two
dialog boxes.
Note
The Simulate Change Output Window displays automatically. It reports all the
identified changes that will be applied on processing the ECO, without the design
changes being committed.
4. On the Change Manager Apply ECO Dialog Box, choose File > Options.
The Options (Apply ECO) Dialog Box displays.
5. Configure any ECO apply change settings on the Change Policy and Setup tabs. These
settings are persisted from the last time the dialog box was used.
6. Any topology changes are highlighted in the Change Manager Preview ECO Dialog Box
as hotspots. See “Identification of Topology Changes with Hotspots” on page 450 for
more information.
7. Click the Process button. The ECO changes are applied to the target design. See
“Harness Object Behavior on Applying ECO Changes” on page 452 for information
about how the changes are applied to different harness objects.
Results
• The captured changes are all applied to the target design revision.
• The Apply Change Output Window displays. It reports the changes that have been
applied on processing the ECO. Any changes that could not be made because of conflict
in the target design state are also reported for manual intervention.
Related Topics

The ECO change manager contains functionality that enables the quick identification of harness
topology changes by means of hotspots.

December 2023
Objects in the Change Manager Preview ECO Dialog Box (where possible connectivity issues
exist) are highlighted as shown in Figure 2-8. Hotspots are shown if all connected objects in the
preview are linked but there are still connectivity issues. These issues include:
• Connected bundles at a node in the source data are left unlinked to the same node in the
target design.
• Connected bundles at a node in the target design are left unlinked to the same node in the
source data.
• There is a connector mismatch at a node.
Figure 2-8. Hotspot Visualization
Clicking a hotspot automatically highlights the bundles and connectors which are causing the
issue, as shown in Figure 2-9, where Bundle 8 has switched nodes. These can then be
investigated.
Figure 2-9. Hotspot Issue Highlighting

December 2023
Harness Object Behavior on Applying ECO

Changes
ECO design changes are applied to target designs in different ways depending on the object type
being processed.
ECO Support for Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
ECO Support for Splices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
ECO Support for Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453
ECO Support for Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
ECO Support for Modular Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
ECO Support for Fixings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
ECO Support for Insulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
ECO Support for Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
ECO Support for Multicores . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
ECO Support for Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
ECO Support for Bundles

The Change Manager Apply ECO process offers the following support for bundles.
• Place - Appropriate bundles are created as specified.
If multiple objects are selected for placement, all selected bundles are placed first, this is
because placement of splices, fixings and protections, mandates that underlying bundles
are already placed.
• Link - Creates a permanent association between the target object and its counterpart in
the source.
• Unlink - Clears the value in the selected Capital object’s External ID attribute, breaking
the link with the Source object.
• Autolink - Only Name and Length are applicable to bundles.
• Synchronize - Updates the linked object with the source data. The following attributes
are synchronized in accordance with any defined Change Policy:
o MaxBundleWidth
o MinBendRadius
o Option Expression
o The Source ID of a linked bundle is displayed in the Edit Bundle dialog box as an
attribute of the bundle.

December 2023
ECO Support for Splices

The Change Manager Apply ECO process offers the following support for splices.
• Place - If the source data has a part number specified and the part is available in the
library, it is assigned to the splice created in the design. If the part is not found, the splice
is still created as per the source data, and a warning related to the missing part is
displayed in the Status field. The splice is created even if the source data does not have a
part number specified.
If the underlying bundle is not linked, the splice is not be placed and an error is
displayed in the Status field.
All splice cavity names (default L, R, X or any other user defined name) are preserved.
the source.
• Autolink - Only Name, Offset, ElecId and PartNumber are applicable to splices
• Synchronize - Updates the linked object with the source data.
o The part number specified in the source data is searched for in the library and if
found, is assigned to the splice in the design (accordance with any defined Change
Policy) irrespective of whether it is already part assigned or not. If the part is not
found, the existing part assigned to the splice in the design will remain.
o The Source ID of a linked splice is displayed in the Capital Harness Designer Edit
Splice dialog box as an attribute of the splice.
ECO Support for Devices

The Change Manager Apply ECO process offers the following support for devices.
• Place - A device is placed at the bundle end node if the connected bundle is already
placed. Otherwise it is placed at the node coordinates. New incoming devices, without a
node, are automatically placed on existing structure nodes in the design with the same
name, and without any node component.
If the source data has a part number specified, and the part is available in the library, it is
assigned to the device created in the design. If the part is not found, the device is still
created as per the source data, and a warning related to the missing part is displayed in
the Status field. The device is created even if the source data does not have a part
number specified.

December 2023
Cavities are created as specified in the source data. Additional components are created
only as part of the housing of the device part, so the Place function only needs to select
appropriate additional components after assigning the device part.
the source.
• Autolink - Only Name, ElecId and PartNumber are applicable to devices.
• Synchronize - The linked device is updated with the source data.
found, is assigned to the device in the design (accordance with any defined Change
found, the existing part assigned to the device in the design will remain.
o If an associated additional component part (or its quantity) are different, a Property
Mismatch is shown. If the additional component part specified in the source data is
different from the selected additional components, and if the new additional
component exists in the library as an available additional component, that one is
selected.
o If the number of cavities differs between the source data and the harness device, a
Property Mismatch is shown. If the number of cavities is greater in the source device
than the target device, remaining non-linked cavities are created.
Note
Creation of cavities is performed only if there is no part assigned. User-defined
properties of cavities are not considered as this is not supported in Capital
Harness Designer.
• Changes to cavities are managed based on a one-to-one mapping between the cavities in
the source data and those in the target design, using the cavity name.
• The Option Expression and Module Expression fields are also synchronized.
• The Source ID of a linked device is displayed in the Capital Harness Designer Edit
Device dialog box as an attribute of the device.
ECO Support for Connectors

The Change Manager Apply ECO process offers the following support for connectors.
• Place - A connector is placed at the bundle end node if the connected bundle is already
placed. Otherwise it is placed at the node coordinates. New incoming connectors,

December 2023
without a node, are automatically placed on existing structure nodes in the design with
the same name, and without any node component.
If the source data has a part number specified, and the part is available in the library, it is
assigned to the connector created in the design. If the part is not found, the connector is
still created as per the source data, and a warning related to the missing part is displayed
in the Status field. The connector is created even if the source data does not have a part
number specified.
Cavities are created as specified in the source data. Backshells and any other additional
components are created only as part of the housing of the connector part, so the Place
function only needs to select an appropriate backshell and other components as
additional components after assigning the connector part.
the source.
• Autolink - Only Name, ElecId and PartNumber are applicable to connectors.
• Synchronize - The linked connector is updated with the source data.
found, is assigned to the connector in the design (accordance with any defined
Change Policy) irrespective of whether it is already part assigned or not. If the part is
not found, the existing part assigned to the connector in the design will remain.
o If an associated backshell part or additional component part (or its quantity) are
different, a Property Mismatch is shown. If the backshell part or additional
component part specified in the source data are different from the selected additional
components, and if the new backshell/additional component exists in the library as
an available additional component, that one is selected. User-defined properties of a
backshell are not considered as this is not supported in Capital Harness Designer.
The length of backshell is also not synchronized.
o If the number of cavities differs between the source data and the harness connector, a
Property Mismatch is shown. If the number of cavities is greater in the source
connector than the target connector, remaining non-linked cavities are created.
Note
Creation of cavities is performed only if there is no part assigned. User-defined
properties of cavities are not considered as this is not supported in Capital
Harness Designer.
• Changes to cavities are managed based on a one-to-one mapping between the cavities in
the source data and those in the target design, using the cavity name. Changes to plugs,
seals and terminals are synchronized.

December 2023
• Cavity wire combinations, including “autoselect” attributes for plugs and seals are
supported, enabling multiple cavity details to be correctly handled.
• The Plugged and Sealed flags of connectors are also synchronized. These flags are
recursively applied to cavities.
• The Option Expression and Module Expression fields are also synchronized.
• The Source ID of a linked connector is displayed in the Capital Harness Designer Edit
Connector dialog box as an attribute of the connector.
ECO Support for Modular Connectors

The Change Manager Apply ECO process offers the following support for modular connectors.
Note
This section details only that functionality that is specific to modular connectors. Refer to
the ECO Support for Connectors section, above, for a full description of connector
functionality.
• Place - If the modular connector shell is not yet placed, it is placed at the bundle end
node if the connected bundle is already placed, else it is placed at the node coordinates.
Sub-connectors are placed at reference nodes, connected to the connector shell by zero-
length bundles.
o If none, or some, of the sub-connectors of the shell have been previously linked, the
connector shell is placed and a Topology Mismatch warning is displayed in the
connector shell’s Status field. The Apply Change Output Window displays a
message advising remedial action is taken to ensure that all internal objects are
linked.
o If the sub-connectors are already linked, the connector shell is placed and all sub-
connectors, along with the connector shell, are grouped to be a single modular
connector. The grouping information is obtained from the connector shell object of
the source data and the shellid attribute of the sub-connector objects.
• Link - The connector shell object can be linked to any parent connector using the Source
ID.
o If any of the component connectors are not linked, a Topology Mismatch is
displayed in the Status field for the connector shell.
o In cases where the connector shell is not linked, a Topology Mismatch is displayed
in the Status field on each of the linked sub-connectors.
• Unlink - Unlink the modular connector by clearing the Source ID from the connector
shell and all sub-connectors.

December 2023
• Autolink - Only Name, ElecId, PartNumber and shellid are applicable to modular
connectors
• Synchronize - The grouping information of the modular connector is synchronized as in
the source data.
ECO Support for Fixings

The Change Manager Apply ECO process offers the following support for fixings.
• Place - Appropriate fixings are created as specified by the type (a grommet is placed for
type Grommet, a clip for type Clip, and so on).
o If the fixing type is not specified, but the part number can be found in the library,
that part’s fixing type is used.
o If a matching part is found in the library, but the fixing type assigned to it differs
from that assigned to the source fixing, the type assigned to the library part is used.
o If a fixing type is not specified and no matching part number is found in the library,
a clip is placed as default, and Fixing is displayed in the Change Manager.
Note
If a subsequent source file is imported for the same harness, for those fixings
whose type has previously been determined, the correct type will still be
displayed.
o If the source data has a part number specified, and the part is available in the library,
it is assigned to the fixing created in the design. If the part is not found, the fixing is
still created as per the source data, and a warning related to the missing part is
displayed in the Status field. The fixing is created even if the source data does not
have a part number specified.
If the underlying bundle is not linked, the fixing will not be placed and an error is shown
in the Status field.
If the fixing has multiple locations then Unsupported Action is displayed for Place.
• Link - Links the objects by assigning the Source ID. If the fixing has multiple locations
then Unsupported Action is displayed. Also, if the fixing type is specified, only that type
is linkable. (a clip can only be linked to a clip, a grommet can only be linked to a
grommet). However, if the type is not specified, a fixing is linkable to any of the types.
• Unlink - Unlink the objects by clearing the Source ID. If the fixing has multiple
locations then Unsupported Action is displayed.
• Autolink - Only Name, Offset and PartNumber are applicable to fixings.
• Synchronize - Updates the fixing with the source data.

December 2023
o A Property Mismatch is displayed if Offset, PartNumber, Option Expression or user-

defined properties are different.
o A Topology Mismatch is displayed if the underlying bundle is not linked.
o If the fixing has multiple locations then Unsupported Action is displayed.
o The fixing is moved according to the Offset supplied in the source data. If the fixing
happens to be in a different linked bundle, the fixing is moved across the bundle.
found, is assigned to the fixing in the design (accordance with any defined Change
found, the existing part assigned to the fixing in the design will remain.
o The Option Expression field is also synchronized.
o The Source ID is displayed in the Edit dialog box for Clips, Grommets and Other
components.
ECO Support for Insulations

The Change Manager Apply ECO process offers the following support for insulations.
• Place - Appropriate insulations are created as specified by the insulation type.
o Insulations with the same start and end nodes (after offset conversion and
approximation to multiples of bundle precision, as dictated by the source data) are
created in the same Capital Harness Designer insulation run.
o Insulation type is set as Untaped, Overlap Tape, Spiral Tape, Space Tape, Fixed
Tube, Fixed Cut-back Tube, Fixed Pulled-back Tube, Selected Tube, Selected Cut-
back Tube or Selected Pulled-back Tube as given by the subtype field.
• If the subtype field is not present, but the part number can be found in the library,
that part’s insulation type is used.
• If a matching part is found in the library, but the subtype assigned to it differs
from that assigned to the source insulation, the subtype assigned to the library
part is used.
• If the subtype field is not present and no matching part number is found in the
library, the insulation type is set as FixedTube for source insulation type Tube, as
OverlapTape for source insulation type Tape, and as SpotTape for source
insulation type SpotTape.
Note
If a subsequent source file is imported for the same harness, for those
insulations whose subtype has previously been determined, the correct
subtype will still be displayed.

December 2023
o Insulations are placed into layers dictated according to the layer values in the source
data. Once placed, all source supplied insulation layer numbers are compared with
their Capital counterparts; a Property Mismatch is displayed if found to be different.
o If the part number is included in the source data, Place will search in the library for
the exact part (using a Tape or Tube filter) and if the part is found, it is assigned to
the object. If the part is not found, a warning is displayed in the Status field and the
insulation is created as specified in the source data but without the library part
number.
o If the underlying bundles are not linked, the insulation will not be placed and an
error is displayed in the Status field.
o Spot Tape is placed at a location defined as the mid-point between the startLocation
and endLocation positions.
o If the incoming insulation has an insulation code assigned, and a matching code
exists within the current project, insulation layers are created as dictated by the code.
• Link - Links the objects by assigning the Source ID. If the insulation type is specified,
linking is possible only with same type. For example, a spot tape can only be linked to a
spot tape.
• Autolink - Only Name, Offset, Length and PartNumber are applicable to insulations.
o An insulation is moved according to the start or end offset supplied in the source
data. This is done by repositioning the reference nodes. Rounding rules in Capital
Harness Designer are honored while updating offset values. If the end node is a
structure node, offset synchronization fails and an error message is displayed. If the
insulation ends happen to be in different linked bundle, they will not be moved
across the bundle.
found, is assigned to the insulation in the design (accordance with any defined
Change Policy) irrespective of whether it is already part assigned or not. If the part is
not found, the existing part assigned to the insulation in the design will remain.
o If an insulation has been placed into a layer of an insulation run containing other
insulations, but has moved in a later iteration of the source data, the updated
insulation is removed from the insulation run and added to a new insulation run,
which is created if required.
o The Convoluted flag, Slit Tube flag, innerDiameter, numberTurns, wallThickness,
tapeThickness, overlap, insulationNote, optionExpression, colorCode and

December 2023
materialCode fields are synchronized with the corresponding fields in the Capital
Harness Designer insulation.
o The innerDiameter value is mapped to the Width attribute in Capital Harness
Designer.
o The wallThickness and tapeThickness fields are mapped to the Thickness value
depending on whether the insulation type is Tube or Tape.
o A Property Mismatch is returned if the offset, length, part number, user-defined
properties, innerDiameter, thickness, option expression, insulation note, overlap,
color or material are different.
o A Topology Mismatch is returned if all underlying bundles are not one-to-one
linked.
o The Source ID is displayed in the Edit Insulation dialog box attributes.
o If either the source insulation does not have an insulation code associated, or the
code does not exist in the current project, and the linked insulation run in the design
has an associated insulation code, a connectivity mismatch is reported, and the run
will need to be synchronized manually.
o Assuming the source protection has an insulation code associated, which also exists
within the current project:
• If the linked insulation run in the design has a different insulation code
associated, a connectivity mismatch is reported, and all existing insulation layers
(associated with the existing insulation code) are deleted, and recreated using the
source insulation code. The Update change policy assigned to the TypeCode
attribute is honored.
• If the linked insulation run in the design has the same insulation code, no other
attributes of the source protection are synchronized and no mismatches are
reported.
• If the linked insulation run has no insulation code associated, the source code is
applied to the run. No other attributes of the source protection are synchronized.
ECO Support for Wires

The Change Manager Apply ECO process offers the following support for wires.
• Place - Appropriate wires are created.
it is assigned to the wire created in the design. If the part is not found, the wire is still
created as per the source data, and a warning related to the missing part is displayed
in the Status field. The wire is created even if the source data does not have a part
number specified.

December 2023
o Route is set according to the source data.

o Center-strip splices are associated if the associated splices in the source data are
already placed or linked in Capital Harness Designer. For multiple object
placements, bundles, connectors and splices are placed before wires.
o If all the underlying bundles are not linked, the wire is placed with appropriate
report.
o If all connecting cavities are not resolved, the wire is placed and error message
displayed.
the source.
• Autolink - Only Name, Electrical ID, and PartNumber are applicable to wires.
o A Property Mismatch is returned if center-strip splices associated with the wire are
different in the source data and target design.
o A Topology Mismatch is returned if routes and connected cavities are different.
found, is assigned to the wire in the design (accordance with any defined Change
found, the existing part assigned to the wire in the design will remain.
o Wirematerial, Wirecolor, Wirespec, Wirelength, Wirecsa, WireNote,
OptionExpression, Material Code at Wire End, and so on, are set with the values in
the source data. Change Manager also ensures that attributes are not modified if a
library attribute and part are assigned.
o The Source ID is displayed as a wire attribute in the Edit Wires dialog box.
ECO Support for Multicores

The Change Manager Apply ECO process offers the following support for multicores.
• Place - Appropriate twisted or sheath multicore is created according to the multicore
type in the source data. Internal wires, shields and multicores are also placed. Shields are
placed as wires in Capital Harness Designer.
it is assigned to the multicore created in the design. If the part is not found, the
multicore is still created as per the source data, and a warning related to the missing

December 2023
part is displayed in the Status field. The multicore is created even if the source data
does not have a part number specified.
o Route and wire ends are set on wires according to the source data.
o If all the underlying bundles are not linked, or wire pins are not resolved, wires are
placed and a report message displayed in the Status field.
• Link - Links the multicores by assigning the Source ID. This is also set for internal
wires and multicores. Internal objects are linked after an alphanumeric sort on members
is performed.
• Unlink - Unlink the multicores by clearing the Source ID. This is also cleared for
internal wires and multicores.
• Autolink - Only Name, Electrical Id and PartNumber are applicable to multicores.
o A Topology Mismatch is returned if member wires or multicores are different in the
source data and target design.
o If a part is not assigned and there is an incoming part, that part is searched in the
library and, if found, assigned to the object.
o If the target object’s part number is different from the source part number, the new
part is assigned if there is a Change Policy that allows for part number change. If no
Change Policy is assigned, a warning is displayed in the Status field and the
incoming part is not assigned.
o If enabled in Capital Harness Designer, user-defined properties can be synchronized.
o Cablelength, cablecoverthickness, cablematerial, cablecolor, cablespec, and so on,
are set with the values in the source data. ECO Change Manager also ensures that
attributes are not modified if a library attribute and part are assigned.
o A wire’s attributes and library part are synchronized as specified in the wire section.
o The Source ID is displayed as a multicore attribute in the Edit Multicores dialog box.
ECO Support for Options

Source options are synchronized with project options.
• Options are not listed in the Change Manager Apply ECO Dialog Box or Change
Manager Preview ECO Dialog Box.
• If any of the incoming options are not available in the project, a “Missing Options”
message is displayed on the selected harness Status field, if linked and selected. You can
then perform the Synchronize action on the harness to import the new options into the
project.

December 2023
• If you have the Option Maintenance permission, the new options are imported to the
project, otherwise an error report is displayed.
Related Topics
Change Manager Preview ECO Dialog Box
Change Manager Apply ECO Dialog Box
Harness Shape Parameters [Capital Diagram Styling User Guide]

December 2023

ECOs can be transferred between projects and databases through the use of import and export
functionality.
When an ECO is exported, an xml based data file is created. The file contains all the attached
data present on an ECO, including any associated images and design name information.
On an ECO import, the system checks a unique identifier (UID) and performs design name
matching to associate an imported ECO to local designs.
ECO Design Change Records can also be imported and exported between ECOs on the same or
different databases. As detailed in the “cost only” design change example in Figure 2-4, once
you have created an ECO impacted design with captured changes, it can be exported and sent to
another site to be applied to a target design on another system.
Note
Import and export of ECOs can also be conducted with web services. See the
WebServiceDevelopment.pdf document located in the doc folder of your Capital installation
for more information about web services.
Exporting an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464

Importing an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Exporting an ECO Design Change Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
Importing an ECO Design Change Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 467
Exporting an ECO
This topic describes how to export one or more ECOs for transfer between projects and
databases.
Procedure
1. To open the Export ECOs Dialog Box either:
In Capital Project Manager: From the Project Browser Tree, expand the project, and
then right-click the Engineering Change Orders node and select Export ECOs.
or
In a design application: Press Space Bar and enter Export ECO, or click the
Capital > File > Export ECOs ribbon action.
2. Within the Export ECOs dialog box, choose one or more ECOs listed in the Category
Window.

December 2023
Note
If you want to see the details of an ECO at any time, select it and click the icon; a
read-only window showing the ECO details opens. Click the same icon to close the ECO
details tab.
3. Click Export.
4. Select a file location to export the ECO data to, and then click Export.
Results
An ECO data file <Project Name> - ECOs.xml, containing all the attached data present on the
selected ECO(s), including any associated images and design name information, is created at
the specified export file location.
Related Topics
Importing an ECO
This topic describes how to import an ECO data file.
Prerequisites
• You must have a valid, previously exported, ECO data file to import. Invalid files will
not import, you will receive a warning dialog detailing any issues if a file fails to import.
Procedure
1. To open a file browser and locate the ECO data file to import, either:
In Capital Project Manager: From the Project Browser Tree, expand the project, and
then right-click the Engineering Change Orders node, and select Import ECOs.
or
In a design application: Press Space Bar and enter Import ECO, or click the
Capital > File > Import ECOs ribbon action.
2. Select an ECO data file and click Import.
Results
The chosen ECO data file <Project Name> - ECOs.xml, containing details of the required
ECOs, is imported and any unique ECOs are added to the project.

December 2023
Related Topics
Exporting an ECO Design Change Record

You can export ECO Impacted Designs for transfer between ECOs on the same or different
databases.
• Only ECO impacted designs with a Completion Status of “Completed - Changes
Captured” can be exported.
Prerequisites
• An ECO exists with a valid ECO impacted design which (optionally) has attached
images.
• The Engineering Change Orders Dialog Box is open.
Procedure
1. Select the required Impacted Design.
2. Click the Export ( ) button on the Impacted Designs toolbar.
The Export file chooser dialog box displays with a default file type of Engineering
Change Order.eco. Enter the required name for the export file and navigate to the
required location.
3. Click the Export button.
Results
• The Engineering Change Order.eco file is created at the specified location.
• The ECO impacted design (including and any associated captured change data) is saved
to the .eco export file.
• All images associated with the ECO impacted design are saved to the .eco export file.
Related Topics
Importing an ECO Design Change Record

December 2023
Importing an ECO Design Change Record

You can import Engineering Change Order.eco files to transfer ECO Design Change Records
between ECOs on the same or different databases.
Prerequisites
• An .eco file has been created.
• The Engineering Change Orders Dialog Box is open.
Procedure
1. Select the required ECO in the Category panel.
2. Click the Import ( ) button on the Impacted Designs toolbar. A file chooser dialog
box displays.
3. Navigate to the required .eco file and click Import.
Results
• The ECO impacted designs (including and any associated captured change data) are
imported.
• All images associated with the ECO Design Change Record are imported and displayed
in the images panel.
• The Impacted Design’s table entry for the imported ECO Design Change Record:
o Displays in italic.
o Does not display a “Release Level” or “Latest” entry as the target project does not
have that information.
Related Topics
Exporting an ECO Design Change Record

December 2023

December 2023
Chapter 3
Diagrams
This chapter contains the following topics which explain how to perform various generic editing
actions on diagrams.
Common Edit Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Changing the Cursor to Crosshair Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Copying and Pasting an Object in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Finding and Selecting Objects by Attribute or Property. . . . . . . . . . . . . . . . . . . . . . . . . . . 475
Finding and Selecting Objects by Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Keyboard Shortcuts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Moving Objects from a Diagram to Another Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Redoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Repeating an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Specifying the Handle Color and Width of Selected Objects. . . . . . . . . . . . . . . . . . . . . . . 490
Specifying the Highlight Color and Width of Selected Objects . . . . . . . . . . . . . . . . . . . . . 490
Undoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Window Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Changing the Background Color of a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Panning Across a Diagram Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Zooming In and Out of Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497

December 2023
Diagrams
Common Edit Actions
Common Edit Actions

This section contains details of how to perform common editing actions on objects in a diagram.
Changing the Cursor to Crosshair Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
Copying and Pasting an Object in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Finding and Selecting Objects by Attribute or Property . . . . . . . . . . . . . . . . . . . . . . . . . 475
Finding and Selecting Objects by Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Moving Objects from a Diagram to Another Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Redoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Repeating an Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Specifying the Handle Color and Width of Selected Objects . . . . . . . . . . . . . . . . . . . . . 490
Specifying the Highlight Color and Width of Selected Objects. . . . . . . . . . . . . . . . . . . . 490
Undoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Changing the Cursor to Crosshair Mode

In the design applications, you can change the mouse cursor to a crosshair mode. Crosshairs
make it easier to align design objects when drawing them.
Procedure
On the status bar at the bottom of the application window, click the Enable crosshairs ( )
icon.
Results
The cursor changes to crosshair mode.
Figure 3-1. Crosshair Mode Cursor
For some actions, the action-specific cursor is displayed with the crosshairs.

December 2023
Diagrams
Copying and Pasting an Object in a Diagram
Figure 3-2. Crosshair Mode Cursor with Action Icon
To change the cursor back, click the Disable crosshairs ( ) icon on the status bar.

You can copy an object on a diagram and paste a copy or a new instance of the object to a new
location on the same diagram or another diagram of the same type.
• The Cut ( ) action is available in Capital Logic Designer only, see “Cutting and
Pasting an Object in a Diagram” in the Capital Logic Designer User Guide.
To cut and paste objects in other design applications, use the Copy and Paste actions,
and then delete the objects in the original location.
• In Capital Logic Designer, you can paste a new instance of a non-shared object
(regardless of whether it is a design-wide object) or paste a new instance of a shared
object. See also “Design-wide Objects” and “Shared Objects” in the Capital Logic
If you paste a new instance onto a diagram in another design revision, the pasted object
will not be an instance of the object you copied but will instead be a new non-shared,
non-design-wide object, with the same name as the object you copied.
• If the “Disallow pin/port duplication within a design” project preference is selected, a
message is displayed if you paste a new instance of an object that would create duplicate
instances of pins. See also “Preventing Pin Duplication Within a Design” in the Capital
• If you copy objects to another diagram in Capital Systems Architect, connections or
relationships between two objects are only copied if both objects are selected and copied
(for example, a pin and a wire). No relationships are created between new and old
objects when objects are pasted. An object's constraints and referenced rules are copied
with the object. Directly added constraints (static or dynamic) are copied, but references
to project-wide rules are lost when copying to another project.
• You cannot re-paste objects after undoing a paste, as the Undo action clears the data in
the clipboard.

December 2023
Diagrams
• If you copy an object and then make a change on the diagram, the data in the clipboard is
cleared and you cannot paste the object.
Procedure
1. To copy a selected the object:
• Right-click and select Copy.
• Press Ctrl+C.
• Press Space Bar and enter Copy.
• Select the Home > Copy-Cut > Copy ribbon action.
The object is saved to the clipboard.
2. To paste the object, move the cursor to where you want to paste the object:

Paste the copy as an unrelated • Right-click the diagram and select Paste.
object. • Press Ctrl+V.
• Press Space Bar and enter Paste, and then
select Paste.
• Select the Home > Paste > Paste ribbon
action.
Paste the copy as a new instance of • Right-click the diagram and select Paste
the same object. Special.
• Press Ctrl+Shift+V.
• Press Space Bar and enter Paste, and then
select Paste Special.
• Select the Home > Paste > Paste Special
ribbon action.
Tip
You can repeat the Paste and Paste Special actions to add additional copies or
instances of the object.
Results
• The copy or instance of the object is pasted and selected on the diagram at the current
cursor location.
• If the object that you copied was a non-shared, non-design-wide object, it becomes a
design-wide object.

December 2023
Diagrams
Deleting an Object in a Diagram
Related Topics
Using Nested Production Modules [Capital Harness Designer User Guide]

You can delete (remove) an object from a diagram if you no longer want to use it.
Procedure
Do one of the following:
• Select the object then either:

o Press Space Bar and enter Delete, and then select Home > Delete from the
Search Ribbon dropdown list.
o Press the Delete key on your keyboard.
• Right-click the object and select Delete.
Results
The object is deleted.
Note
If a diagram contains design-level tables, and you select all objects before performing the
delete action, the system does not delete the design-level tables. Only Apply Style or Update
Border actions can delete those tables.
Filtering the Objects Displayed in a Capital

Systems Integrator or Capital Wiring Systems
Diagram
The Capital Systems Integrator or Topology Design Filter dialog box enables you to filter the
graphical topology in a diagram. This can make it easier to view and understand the wiring for
particular harnesses or configurations.
You can filter it to display:
• Only the design elements included in active harness levels

• Only design elements with active wiring
• Only the design elements assigned particular options

December 2023
Diagrams
Filtering the Objects Displayed in a Capital Systems Integrator or Capital Wiring Systems Diagram
This video shows the impact of the different filters.
This functionality is available for single composite harnesses (where a single harness has some
optional bundles).
Option filter settings apply only to individual open diagrams and they are not saved when you
close a diagram. When it is opened again, it reverts to the default setting of no filtering.
Filtering does not change design data. If you want to create a separate, editable version of a
filtered design, you must create an evaluated design in Capital Project Manager. The effect of
filtering an object out of the diagram is limited to the following:
• It is not displayed in the diagram.

• It is not selectable.
• Stretches and manipulations of visible objects never result in a connection to the
invisible object.
• Cross-references to invisible objects are still displayed and following the cross-reference
opens the other diagram but the invisible object is not selected.
Note
The visibility of an object depends on the visibility of its containing object. For
example, if a slot is invisible, its slot connector and name text is invisible:
• The visibility of inline halves and interface connectors is dependent on the visibility
of the connected bundle.
• The visibility of a bundle region is dependent on the visibility of the bundle to which
it belongs.
Procedure
1. Open the Capital Systems Integrator or Capital Wiring Integrator diagram.
2. Press Space Bar and enter Filter platform design.
The Capital Systems Integrator or Topology Design Filter Dialog Box displays.
3. Select one of the Filter options and click OK.

December 2023
Diagrams
Finding and Selecting Objects by Attribute or Property
Results
• The filtering is applied to the diagram.
• The filtering icon on the Status Bar at the bottom of the application window displays the
icon for the filtering that you have selected.
Related Topics
Capital Systems Integrator or Topology Design Filter Dialog Box
Finding and Selecting Objects by Attribute or

Property
You can search for an object on a diagram by using a value for a particular attribute or property.
The system selects any matching objects so that you can perform an action on them.
This video, recorded in Capital Logic Designer, demonstrates how to find and select objects by
attribute or property.
Procedure
1. With the diagram open, press Space Bar and enter Select By Attribute/Property.
The Select by Attribute/Property Dialog Box is displayed.
2. Specify the following:
• In the Attribute/Property field, enter the property or attribute name.
• In the Value field, specify the value for which you are searching.
• Use the Regular Expression option to specify whether the Value string you entered
contains Regular Expression wildcard search characters. Leave cleared if the string
is an exact value that must be matched.

December 2023
Diagrams
Finding and Selecting Objects by Name
Note
Common Regular Expression search wildcards are:
.* searches for any character (.), zero or more times (*), $ matches at the end of a
string (for example, searchme$), ^ matches at the beginning of a string (for example,
^searchme).
3. Click OK.
Results
Any objects with matching values for the specified attribute or property are selected on the
diagram and in any browser trees where they appear.
Related Topics
Undoing an Action
Redoing an Action
Repeating an Action
Selecting All Objects in a Diagram
Specifying the Highlight Color and Width of Selected Objects
Using the Stroke Tool

You can search for an object on a diagram by using its name. The system selects the matching
objects so that you can perform an action on them.
This video, recorded in Capital Logic Designer, demonstrates how to find and select objects by
name.

December 2023
Diagrams
Keyboard Shortcuts
Procedure
1. With the diagram open, press Space Bar and enter Select by Name.
The Select By Name Dialog Box is displayed.
2. In the Name field, enter the name for which you are searching.
3. Use the Regular Expression option to specify whether the Name string you entered
contains Regular Expression wildcard search characters. Leave cleared if the string is an
exact value that must be matched.
Note
Common Regular Expression search wildcards are:
.* searches for any character (.), zero or more times (*), $ matches at the end of a string
(for example, searchme$), ^ matches at the beginning of a string (for example,
^searchme).
4. Click OK.
Results
Any objects with matching names are selected on the diagram and in any browser trees where
they appear.
Related Topics
Undoing an Action
Redoing an Action
Repeating an Action
Keyboard Shortcuts
Various keyboard shortcuts are available in Capital. Many are common to all design
applications, while others are specific to particular applications.

December 2023
Diagrams
Keyboard Shortcuts
Table 3-1. Keyboard Shortcuts

Keyboard Shortcut Action
All Applications
General
Ctrl+Alt+K Reload Plugins
Ctrl+Shift+O Add Option Folder
Ctrl+Y Repeat action
Space Ribbon search
Ctrl+T Trace
Shift+Space Object Search
Ctrl+S Save
Ctrl+P Print
Ctrl+Alt+A Add Print Region
Ctrl+Alt+E Print Region Settings
Ctrl+O Open Project
Ctrl+N New Project
Ctrl+S Save
F1 Help
Esc Cancel
Enter Commit
Editing
Ctrl+X Cut
Ctrl+C Copy
Ctrl+V Paste
Delete Delete
Ctrl+Z Undo
Ctrl+Y Redo
Ctrl+A Select All
Ctrl+E Extend Selection
Ctrl+D Edit Rules
Ctrl+Shift+{Select} Select from a list of overlapping objects
Ctrl+Shift+O Edit Options

December 2023
Diagrams
Keyboard Shortcuts
Table 3-1. Keyboard Shortcuts (cont.)

Ctrl+Shift+F Edit Functional Module codes
Ctrl+Shift+P Edit Production Module codes
Ctrl+Alt+R Pivot Text
Alt+Enter Properties
Double click Properties
Ctrl+Shift+Up Bring Forward
Ctrl+Shift+Down Send Backward
Shift+Toolbar Repeat Selected Action
Shift+{Select} Multi-select sequence of rows
Drag+{Select} Area select objects on diagram
Ctrl+{Select} Multi-select objects
F Flip while placing symbols
R Rotate while placing symbols
H Hide repeat columns
Ctrl+Shift+G Move to grid
Styling
Shift+A Apply Style
Ctrl+Shift+A Apply Style to All
Shift+U Fix decoration
Shift+P Fix Position
Alt+Shift+F Force Apply Style
Alt+Shift+S Update Style
Shift+E Edit Style
Ctrl+Shift+I Split table
Graphics
L Add Line
R Add Rectangle
Y Add Polygon
C Add Circle
A Add Arc

December 2023
Diagrams
Keyboard Shortcuts

K Add Curve
T Add Text
Ctrl+Shift+J Toggle Snap to Object
Ctrl+Up Graphics push action
Navigation
Alt+Numpad++ Zoom In
Ctrl+= Spring-loaded zoom in
Ctrl+NumPad+
Alt+NumPad- Zoom out
Ctrl+Zoom / Pan Spring-loaded zoom out
Z Zoom selected
A Zoom area
Q Zoom all
NumPad* Expand All Tree nodes
NumPad+ Expand Tree Node
NumPad- Collapse Tree Node
Shift+Z Zoom Selected Red (specific)
Capital Logic Designer
Editing
Ctrl+Shift+V Paste extended
Ctrl+M Move To
Ctrl+R Route Selected
Ctrl+Shift+R Toggle Auto-route Net
Ctrl+Shift+S Slice
O Add/Edit Overbraid
V Add/Edit Shared Overbraid
X View Related Items
D Disconnect Selected
Shift+W Connect by Wire (overlapping pins)
Shift+C Connect by Net (overlapping pins)

December 2023
Diagrams
Keyboard Shortcuts

Shift+NumPad+ Connect by Pin (overlapping pins)
Ctrl+B Add backshell termination
Shift+S Create co-axial sheath multicore
Shift+T Create twisted sheath multicore
J Join selected instances of a design-wide
or shared object
Shift+M Manage connectors
Ctrl+H Route into highway
Shift+O Create overbraid sheath
Ctrl+G Generate Selected Names
Adding
P Add Pin
I Add Internal Pin
N Add Net
G Add Highway
W Add Wire
S Add Shield Termination
M Add/Edit Multicore
CTRL+Shift+T Add Ring Terminal
V Add/edit Shared Overbraid
CTRL+L Add Device from Library
Capital Wiring Integrator
Editing
X Show Functional Source
Shift+X View Related Items
Adding
I Add Inline Pair
] Add Inline Receptacle
[ Add Inline Plug

December 2023
Diagrams
Keyboard Shortcuts

V Add Slot Connector
H Add Hole
B Add Bundle
Capital Systems Integrator
Editing
Ctrl+F5 Vehicle Models
Ctrl+F8 Vehicle Configurations
Alt+F8 Configuration Builder
Ctrl+F7 Harness Levels
X Show Functional Source
Shift+X View Related Items
M Edit Multicore
Ctrl+I Import wiring
Ctrl+F5 Product planner
Adding
I Add Inline Pair
] Add Inline Receptacle
[ Add Inline Plug
V Add Slot Connector
H Add Hole
B Add Bundle
Capital Harness Designer
Styling
Ctrl+H Hide decoration
Ctrl+I Un-hide decoration
Ctrl+F Edit Font Style
Ctrl+E Edit Graphic Style
Ctrl+W Edit Width Graphic Style
Ctrl+Shift+H Edit Graphic Height

December 2023
Diagrams
Keyboard Shortcuts

Ctrl+Shift+E Edit Symbol Graphic Style
Editing
Alt+P Bundle Palette
Ctrl+Shift+R Proportional Bundle Stretch
Ctrl+R Edit Insulation Run
Adding
Ctrl+B Add Bundle (Dynamic)
Shift+B Add Bundle (Static)
Ctrl+Shift+B Add Bundle (Define)
O Add Connector
Ctrl+Shift+T Add Ring Terminal
S Add Splice
Shift+V Add Device
W Add Wires
M Add Multicores
V Add Overbraids
P Add Clip
F Add Fixture
G Add Grommet
I Add Insulation run (Bundle)
Shift+I Add Insulation run (Start & End)
Shift+D Add Dimension (Reference)
D Add Dimension (Standard)
Ctrl+D Add Dimension (Contiguous)
Shift+F Add Dimension (External)
Rules
Ctrl+Shift+C Apply Constraints
Ctrl+Shift+L Route Wires
Ctrl+Alt+Shift+L Clear Wire Route
Ctrl+Alt+Shift+C Define Fixture Constraint

December 2023
Diagrams
Keyboard Shortcuts

Ctrl+Alt+X Place Fixtures
Ctrl+G Degenerate insulation run
Shift+P Fix position
Ctrl+U Regenerate breakout tape
Ctrl+L Regenerate spot tape
Alt+T Tabular edit
Processing
Ctrl+Alt+L Calculate Wire/Multicore Lengths
Ctrl+Alt+B Calculate Node/Bundle Sizes
Ctrl+Shift+U Calculate Insulation Totals
Ctrl+Alt+D Calculate Center Strip Distances
Ctrl+Alt+G Calculate Harness Weight
Ctrl+Alt+N Balance Splices
Ctrl+Alt+F Balance Splices (Force Entry Direction)
Ctrl+Shift+Z Optimize Splice Position
Alt+R De-populate redundant objects
Actions
Ctrl+Alt+Shift+F Assign Functional Module Codes
Ctrl+Alt+Shift+R Assign Production Module Codes
Process Part Selection
Ctrl+Alt+P Select All Part Numbers
Ctrl+Alt+W Select Wire Part Numbers
Ctrl+Alt+M Select Multicore Part Numbers
Ctrl+Alt+C Select Customer Part Numbers
Ctrl+Alt+S Select Supplier Part Numbers
Ctrl+Alt+Y Select Mandatory Component
Ctrl+Alt+I Select Splice Part Numbers
Ctrl+Shift+W Select Ultrasonic Weld P/N
Ctrl+Shift+V Select Solder Sleeve P/N
Ctrl+Alt+H Select Heat Shrink Sleeves

December 2023
Diagrams
Moving Objects from a Diagram to Another Diagram

Ctrl+Alt+O Select Spot Tapes
Ctrl+Alt+U Select Tubes
Ctrl+Alt+T Select Cavity Components
Harness Processing
Ctrl+Alt+Shift+P Harness Processing
Capital Harness Process Designer
Actions
Ctrl+Alt+Shift+B SBOM Processing
Ctrl+Alt+Shift+W Part Number Where Used
Ctrl+Alt+Shift+M Set Masters
Ctrl+E Debug SBOM pattern editor
Ctrl+W Edit cost result workstation
Ctrl+F / Alt+F Merge Formboard
Capital Systems Modeler
Shift+S Manage signals
M Add message
P Add function port
S Add signal
Capital Systems Architect
B Add break pair
E Edit interface map
O Add component
P Add pathway
Alt+Del Unassign signals from carriers
Shift+X Connect by interconnects
Moving Objects from a Diagram to Another

Diagram
You can move objects from one diagram to another diagram within a design.

December 2023
Diagrams
Moving Objects from a Diagram to Another Diagram
Note
The Move To action cannot be undone.
The following restrictions apply to moving objects in Capital Logic Designer:
• Individual pins cannot be not moved without the parent object moving.
• Device connectors cannot be moved without their parent device.
• Inline connectors cannot be split.
• To move a multicore you need to select the multicore indicators and all the inner cores.
• Aerospace modular connectors cannot be moved.
The video demonstrates how to move a device from one diagram to another diagram.
Procedure
1. Select the objects to move on the diagram or in the Design Browser, and then either:
• Press Space Bar and enter Move To.
• Right-click the selected objects and select Move To.
The Diagram Selection dialog box displays.
2. Select which diagram to move the objects to, and then click OK.
Results
• The selected diagram is opened and the objects are moved to it and placed in the same
position that they occupied on the original diagram. You can then move and resize the
objects as required.
• In Capital Logic Designer, if the selected objects are connected to other objects that are
not selected to be moved, the connections are broken when the objects are moved. No
connectivity is created automatically in the new diagram. However, you can move
objects as normal to create connectivity.
• In Capital Systems Integrator and Capital Wiring Integrator, any objects graphically
connected to the selected objects are moved with them.

December 2023
Diagrams
Moving Objects on a Diagram
Moving Objects on a Diagram

You can move non-intelligent graphical shapes and objects, and objects with electrical
connectivity freely on the diagram, or use Shift and Ctrl and the arrow keys on your keyboard to
move objects with more control.
Prerequisites
• See “Set Grid Defaults Dialog Box” for grid point descriptions, such as Drawing Grid
and Major Grid Interval.
Procedure
1. Select one or more objects and drag the objects using the mouse.
2. (Optional) Hold down Shift or Ctrl and use the arrow keys to move non-intelligent
graphical shapes and objects:
• Shift — Moves by one drawing grid point (percentage of the grid point distance),
see the “Set Grid Defaults Dialog Box” topic.
• Ctrl — Moves by a percentage of five grid points (Major Grid Interval default), as
specified by the Drawing Grid percentage.
Note
If the Drawing Grid percentage is 20%, the objects will move by 20% of two grid
points when you hold down Ctrl.
3. (Optional) Hold down Shift or Ctrl and use the arrow keys to move electrically
connected objects:
• Shift — Moves by one grid point.
• Ctrl — Moves by one major grid point.
Redoing an Action
You can re-perform the last actions that were reversed using the undo facility.
Note
If there are no more actions to redo, the Redo option changes to Repeat.
Related Topics
Undoing an Action
Repeating an Action

December 2023
Diagrams
Repeating an Action

Repeating an Action
If there are no undone actions that can be redone, you can repeat the last action that you
performed.
Procedure
1. Press Space Bar and enter Repeat.
2. The application is put in the correct mode to repeat the last action performed.
Tip
A number of the component placement functions can be locked to enable the
continuous placement of the same component type until the tool is unlocked. For
example, in Capital Harness Designer, you can lock the Static Bundle function (press
Space Bar and enter Static Bundle), allowing you to keep drawing bundles (and
confirming the entered length) without having to reselect the Static Bundle action.
To lock a function, press the Shift key while selecting it from the ribbon or from the
Search Ribbon dropdown list. To unlock a tool, press the Esc key.
Related Topics
Undoing an Action
Redoing an Action

December 2023
Diagrams

You can select all objects in a diagram to perform an action on all of them at once.
Video
This video demonstrates how to select all objects in a diagram:
Procedure
1. Press Space Bar and enter Select All.
All of the objects on the diagram are highlighted.
2. Perform the required action.
Note
If a diagram contains design-level tables, and you select all objects before
performing the delete action, the system does not delete the design-level tables. Only
Apply Style or Update Border actions can delete those tables.
Related Topics
Undoing an Action
Redoing an Action
Repeating an Action

December 2023
Diagrams
Selecting Specific Objects in a Diagram
Selecting Specific Objects in a Diagram

You can select specific objects that you want to edit in a diagram window.
Procedure
1. Press Space Bar and enter Select.
2. Either click the single object you want to select or drag a box around a group of multiple
objects.
Specifying the Handle Color and Width of Selected

Objects
You can specify the color and width of the handles used to modify the size and shape of objects
in a diagrams in functional and logical designs in the design applications and used to modify the
size and shape of symbol graphics in Capital Symbol Designer.
Procedure
1. Press Space Bar and enter Handle Graphics.
The Handle Graphics Dialog Box displays.
2. Select the color and width that you require.
3. Click OK.
Results
• The handle color and width specified are used in the current application, in the other
design applications (when editing a diagram in a functional design or logical design),
and in Capital Symbol Designer.
Note
You cannot resize a symbol in a logical or functional design. If you want to resize a symbol
graphic, you must use Capital Symbol Designer and then update the symbol graphic in the
diagram. See Updating Symbols in the Capital Logic Designer User Guide or Updating
Symbols in the Function Design in Capital Systems Modeler User Guide.
Specifying the Highlight Color and Width of

Selected Objects
You can specify the color used to highlight the selected objects in a diagram in the design
applications and used to highlight the selected symbol graphics in Capital Symbol Designer.
For functional designs and logical designs you can specify different colors to be used depending
on whether an object is selected by clicking it in the diagram or by clicking its name either in the

December 2023
Diagrams
Design Browser or the Design Rule Checks Output Window, and can also specify the width of
highlighting to be used when an object is selected by clicking its name in the Design Browser or
Design Rule Checks Output Window.
In Capital Symbol Designer you can specify different colors to be used depending on whether a
symbol graphic is selected by clicking it in the diagram or by clicking its name in the Symbol
Contents Browser Window, and can also specify the width of highlighting to be used when a
symbol graphic is selected by clicking its name in the Symbol Contents Browser Window.
Procedure
1. Either:
• When editing a diagram in a platform design, Capital Wiring Systems design,
Capital Systems Integrator design or harness design, press Space Bar and enter
Selection Color.
• When editing a diagram in a functional design or logical design:
o To specify the highlight color for an object when it is selected by clicking it in a
diagram, press Space Bar and enter Selection Graphics.
o To specify the highlight color or width for an object when it is selected by
clicking it in the Design Browser or Design Rule Checks Output Window, press
Space Bar and enter Highlight Graphics.
• In Capital Symbol Designer:
o To specify the highlight color for a symbol graphic when it is selected by
clicking it in a diagram, press Space Bar and enter Selection Graphics.
o To specify the highlight color or width for a symbol graphic when it is selected
by clicking it in the Symbol Contents Browser Window, press Space Bar and
enter Highlight Graphics.
The Select Color Dialog Box or Highlight Graphics Dialog Box displays.
2. Either:
• In the Select Color Dialog Box, select the color that you require.
• In the Highlight Graphics Dialog Box, select the color and width that you require.
3. Click OK.
Results
• The highlight color and width specified are used in the current application.
• If you specified a highlight color and width in the Highlight Graphics Dialog Box, they
are used in the other design applications (when editing a diagram in a functional design
or logical design), and in Capital Symbol Designer, immediately.

December 2023
Diagrams
Undoing an Action
• If you specified a highlight color in the Select Color Dialog Box, it is used in the other
design applications and in Capital Symbol Designer the next time you launch one of
those applications.
Related Topics
Undoing an Action
Redoing an Action
Repeating an Action
Undoing an Action
You can use the undo facility to reverse up to the last 20 actions that have been performed.
Procedure
1. Press Space Bar and enter Undo.
2. The previous action is undone and is added to the stored list of undone actions.
Note
If you perform a new action after you have undone one or more actions, this empties
the stored list of undone actions.
Related Topics
Redoing an Action
Repeating an Action

December 2023
Diagrams

The stroke tool enables you to perform various actions by moving the mouse in a pre-defined
way. If you do not have a middle mouse button, you cannot use the stroke tool.
Procedure
Follow these steps:
• Each stroke action maps to a pattern on the following nine part grid:
• A stroke is identified by the path of the mouse through the grid. For example, the
following stroke that is a counter-clockwise C pattern is named 3214789 because of
the grid squares that it passes through.
• The following stroke actions are available:
Table 3-2. Stroke Actions

Stroke Action Grid Path
Zoom Area 159
Zoom All 951
Zoom in by 20% 357
Zoom out by 20% 753
Delete 741236987

December 2023
Diagrams
Table 3-2. Stroke Actions (cont.)

Stroke Action Grid Path
Analysis Toggle Interface property 14789
Undo 1478963
Redo 7412369
Add net (in Capital Logic Designer), Add 258
bundle (in Capital Systems Integrator)
Route selected (in Capital Logic Designer 96321
only)

December 2023
Diagrams
Window Controls
Window Controls
This section contains details about how to arrange open diagram windows and browser
windows for viewing and how to use the zoom and pan controls to change what you are viewing
in a window.
Changing the Background Color of a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Panning Across a Diagram Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Zooming In and Out of Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Arranging Diagram Windows for Viewing

You can use the New View and Mode ribbon actions on the Window tab to arrange open
diagrams for viewing purposes.
Procedure
Choose one of the following options:
• New View
Creates a copy of the active diagram. Any changes made in the copy are also made
in the original. This is useful for viewing smaller sections of large diagrams.
• Mode
Click the Mode ribbon action button then click the Mode ribbon action dropdown
list and select one of the following:
o Tabbed Mode: Resizes each diagram to occupy the entire display area and adds
a row of tabs at the bottom of for switching between open diagrams.
o Cascade: Rearranges and resizes the open diagrams in a staggered fashion,
allowing selection and viewing of a diagram by clicking it once.
o Tile Horizontal: Rearranges and resizes the open diagrams so that they are
aligned horizontally.
o Tile Vertical: Rearranges and resizes the open diagram windows so that they are
aligned vertically.
Tip
With Cascade, Tile Horizontal or Tile Vertical selected clicking the Mode ribbon
action button changes the mode to Tabbed Mode.

December 2023
Diagrams
Changing the Background Color of a Diagram
Related Topics
Using Tearable Tabs
Zooming In and Out of Diagrams
Panning Across a Diagram Window
Changing the Background Color of a Diagram

You can toggle the background color in the Diagram window between black and white.
Procedure
To select either white or black backgrounds for diagrams:
• Press Space Bar and enter Invert Colors.

• Click the Window > Invert Colors ribbon action.
If you apply a default, background, or foreground color to objects on the diagram, the
color of the objects inverts when the background color is toggled. See “Foreground,
Background and Manual Color Options” on page 601.
Note
The background color change only affects on-screen viewing. Printing a diagram is
always executed with a white background.

You can pan across a diagram window to change the area that you are viewing.
Procedure
1. Either:
• Press Space Bar and enter Pan.
• Right-click the diagram and select Pan.
The cursor changes to .
2. Click and hold, and then move the cursor to pan.
Note
You can also activate the panning tool by click and holding the left mouse button for
at least a second. Once the tool is activated, keep the mouse button held down and
move the cursor to pan.

December 2023
Diagrams
Using Tearable Tabs
Related Topics
Using Tearable Tabs
Using Tearable Tabs

You can display browser tabs in separate windows that you can move around your screen.
Any browser tabs that are located on the lower left side of an application window are tearable
and can be dragged away from that position so that they are displayed in their own separate
windows.
Procedure
1. Click the tab of the browser and drag it to the location where you want to display it.
2. Resize the browser window as required.
Note
To return the browser window to the lower left side of the main application window,
close the separate window. The tab returns to its original position automatically.
Related Topics

You can use the zoom controls to zoom in and out of diagrams to change the diagram area that
you are viewing.
Procedure
Choose one of the following options:
• Zoom In
Increases the scale of the diagram so that objects appear larger.

December 2023
Diagrams
Note
See “Zooming Insulation” in the Capital Harness Designer User Guide for
information about zooming insulation layers in Capital Harness Designer and
Capital Harness Designer Modular.
Either:
o Press Space Bar and enter Zoom In
o Press =
o Press Alt+NumPad+
o Roll the mouse wheel forward
• Spring-loaded Zoom In
Increases the scale of the diagram so that objects appear larger, and then returns the
diagram to the previous scale once you release the Ctrl key.
Either:
o Press Ctrl+=
o Press Ctrl+NumPad+
o Press Ctrl and roll the mouse wheel forward
• Zoom Out
Decreases the scale of the diagram so that objects appear smaller.
Either:
o Press Space Bar and enter Zoom Out
o Press -
o Press Alt+NumPad-
o Roll the mouse wheel backward
• Spring-loaded Zoom Out
Decreases the scale of the diagram so that objects appear smaller, and then returns
the diagram to the previous scale once you release the Ctrl key.
Either:
o Press Ctrl+-
o Press Ctrl+NumPad-
o Press Ctrl and roll the mouse wheel backward

December 2023
Diagrams
• Zoom Selected
Zooms in on the object(s) that you have selected in the diagram or in the design
browser.
Select the object(s) and either:
o Press Space Bar and enter Zoom Selected
o Press Z
o Right-click and select Zoom Selected
In Capital Harness Designer, Capital Harness Designer Modular, Capital Formboard
Designer, and Capital Harness Process Designer, the zoom level extents include the
selected object(s) and all their related decorations. The following zoom functionality
is also available in these tools:
o Where the diagram includes objects with related entity decorations (REDs) or
secondary representations displayed on separate sheets, you can press Shift+Z to
zoom to the selected object(s) on the additional sheets. The zoom displays
multiple objects located in close proximity of each other all together.
This video shows the zoom selected functionality.
• Zoom Area
Zooms in on a specified area of a diagram.
Either:
o Press Space Bar and enter Zoom Area
o Press A
The cursor changes to . Click the diagram to specify the first corner of the area
and click again to specify the opposite corner of the area.
• Zoom All
Zooms out to display all objects in the diagram.

December 2023
Diagrams
Either:
o Press Space Bar and enter Zoom All
o Press Q
o Right-click the diagram and select Zoom All
• Zoom
Zooms in or out by moving your mouse.
Either:
o Press Space Bar and enter Zoom
o Right-click on the diagram and select Zoom
Click and hold, and then move your mouse forward or to the left to zoom out, or
backward or to the right to zoom in. To exit zoom mode, right-click and select
Cancel or press the Esc key.

December 2023
Chapter 4
3D Viewer
If harness data has 3D coordinates (3D data points), you can open a 3D Viewer in Capital
Systems Integrator and Capital Wiring Integrator to view the data in a 3D skin.
The 3D Viewer functionality is accessed from a 3D ribbon tab at the top of the application when
you have a Capital Systems Integrator or Capital Wiring Integrator design open.
Figure 4-1. 3D Ribbon Tab
Opening the 3D Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501

Adding Harness Objects to the 3D Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Removing Harness Objects from the 3D Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Viewing a Skin in the 3D Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Changing the View in the 3D Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Separation Categories and Distances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Creating a File of Separation Categories and Distances. . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Setting Separation Categories and Distances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
3D Viewer Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Opening the 3D Viewer

If harness data has 3D coordinates (3D data points) from CATIA V5 or NX, you can open a 3D
Viewer in Capital Systems Integrator and Capital Wiring Integrator to view the data in 3D. You
can add a 3D skin to the view to provide the context within a vehicle.
Prerequisites
• You must have the latest version of the Visual C++ Redistributable Package for Visual
Studio 2013 and 2015 installed.
• A Capital Systems Integrator or Capital Wiring Integrator diagram must be open.
• The harness data for the open design must have 3D coordinates (3D data points). This
data is imported using Capital Connectors functionality for CATIA V5 or NX. See the
Capital Connectors User Guide for more information.

December 2023
3D Viewer
Procedure
Use one of the following flows:

Open the 3D Viewer so that it is Press Space Bar and enter Visualize; select
empty. the Visualize action from the 3D ribbon
tab.
Open the 3D Viewer to display 1. Select the desired objects in the Design
particular harness objects. Browser (Design Tab) on the bottom
left of the application or in the diagram
window:
• One or more harnesses to view all
bundles in them.
• One or more signals that have wiring
to view all of the bundles that those
wires pass through.
• One or more wires to view all
bundles that those wires pass
through.
• One or more systems to view all
bundles in them.
• One or more bundles to view those
bundles.
Note: In Capital Wiring Integrator,
you can select wires on the Wiring
Browser at the bottom left of the
application window to view all bundles
that those wires pass through.
2. Press Space Bar and enter Add
Selected; select the Add Selected
action from the 3D ribbon tab.

December 2023
3D Viewer
Results
• The 3D Viewer window opens either empty or with the selected harness objects
displayed in 3D. In the case of large data, the 3D Viewer has the text Loading Model at
the top until it has loaded the data in 3D format.
Caution
If you have opened the 3D Viewer before and did not remove all objects from it,
those objects are still visible in it.
If you are working with a design that has two diagrams and you switch between
diagrams, the content of the 3D Viewer does not change because it is using data from the
same design. If you switch between designs, the 3D Viewer is forced to close and its
content is removed because it must reference different design data.
• If the selected objects include half of an inline connector and it is connected to another
inline half (not included in the selected objects), both halves are displayed in the 3D
Viewer.
• Bundles in the 3D Viewer have different thicknesses depending on bundle width. If a
bundle has a width of 0, it will still be visible.
Figure 4-2. Different Bundle Thicknesses
• You can use your mouse to change the camera angle of the view (by dragging), or zoom
in and out (using the mouse wheel).
• You can change the view in the 3D Viewer. See “Changing the View in the 3D Viewer”
on page 507.
• You can add or remove objects from the 3D Viewer window. See “Adding Harness
Objects to the 3D Viewer” on page 504 or “Removing Harness Objects from the 3D
Viewer” on page 505.
• You can add a skin to the 3D Viewer. See “Viewing a Skin in the 3D Viewer” on
page 506.
• If the harness data had no 3D coordinates, an error displays in a 3D View tab in the
Output Window at the bottom of the application.

December 2023
3D Viewer
Adding Harness Objects to the 3D Viewer
• Selected objects will cross-highlight across the 3D Viewer, diagram window, and
Design Browser:
Table 4-1. Cross-highlighting of Selected Objects
If you select... Also selected:
Bundle in the 3D Viewer Equivalent bundle in Design Browser and diagram
window
Bundle in Design Browser or Equivalent bundle in 3D Viewer
diagram window
Signal (with wires passing Bundles carrying signal wires in 3D Viewer
through harness) in Design
Browser
Harness (that carries one or Harness bundles carrying those signal (harness
more signals) in Design bundles not carrying any signals are not selected) in
Browser 3D Viewer
Individual objects, such as Equivalent objects
slots, inlines
Adding Harness Objects to the 3D Viewer

When you have the 3D Viewer open, you can add further harness objects to it.
Procedure
1. Select the desired objects in the Design Browser (Design Tab) on the bottom left of the
application or in the diagram window:
2. Press Space Bar and enter Add Selected; select the Add Selected ribbon action from the
3D ribbon tab.
Table 4-2. Objects Added to 3D Viewer

Selected Objects Objects Added to 3D Viewer
One or more harnesses All bundles in those harnesses
One or more signals that All of the bundles that those wires pass through
have wiring
One or more wires All bundles that those wires pass through
One or more systems All bundles that carry wires associated with the
selected systems

December 2023
3D Viewer
Removing Harness Objects from the 3D Viewer
Table 4-2. Objects Added to 3D Viewer (cont.)

Selected Objects Objects Added to 3D Viewer
One or more bundles Those bundles
Note
In Capital Wiring Integrator, you can select wires on the Wiring Browser at the
bottom left of the application window to view all bundles that those wires pass
through.
Results
The appropriate bundles are added to the 3D Viewer.
Removing Harness Objects from the 3D

Viewer
You can remove objects from the 3D Viewer with or without it open.
Procedure

Remove specific harness 1. Select the desired objects in the Design Browser
objects. (Design Tab) on the bottom left of the application or
in the diagram window:
• One or more harnesses
• One or more signals
• One or more wires
• One or more bundles
• One or more systems
2. Press Space Bar, enter Remove Selected, and select
the Remove Selected action from the 3D ribbon tab.
Remove all objects. Press Space Bar, enter Remove All, and select the
Remove All action from the 3D ribbon tab.

December 2023
3D Viewer
Viewing a Skin in the 3D Viewer
Results
The corresponding bundles are removed from the 3D Viewer. They will not be visible when you
next open the 3D Viewer.
Note
If you added one harness (for example H1) to the 3D Viewer, and then added another (H2)
that is connected to it by an inline connector, the inline connector is removed if you remove
H1, even though it is connected to the still visible H2.
Viewing a Skin in the 3D Viewer

A 3D skin provides context for where bundles are situated in a vehicle. You can add a skin in JT
format to the 3D Viewer. You can also change the skin, or change its rendering mode. The skin
is added for the design that you are viewing. It is not added for the entire project.
Prerequisites
• A 3D skin must have been created in an external tool and saved as a single (monolithic)
file in JT format. The skin must be the correct scale for your design (that is, your 2D
design must have the same scale as your 3D model).
Note
You can convert OBJ files to JT format using a third party converter.
• The skin files must be in an accessible location.

• The 3D Viewer must be open.
Procedure

Add a skin to the 3D Viewer 1. Click the Set Skin action on the 3D ribbon.
A Select a 3D skin dialog box displays.

2. Navigate to the skin file, select it and click the
Select skin button.
The skin is displayed in the 3D Viewer.
Note: You cannot remove a skin once you have
added it. You can only replace it with a different
skin.

December 2023
3D Viewer
Changing the View in the 3D Viewer

Replace the skin 1. Click the Set Skin action on the 3D ribbon.
A Select a 3D skin dialog box displays.
2. Navigate to the skin file, select it and click the
Select skin button.
The selected skin replaces the old skin in the 3D
Viewer.
Change the rendering mode Select one of the following: either Wireframe,
of the skin Silhouette, or Solid on the 3D ribbon tab.

You can display bundles in the 3D Viewer in the following views: plan, elevation, front. You
can switch between these.
Procedure
You can switch between these.

Change the view of the data. Select either Plan, Elevation, or Front on the 3D
ribbon tab.

December 2023
3D Viewer

Reset the view to the elevation Click the Reset View action on the 3D ribbon tab.
view.
The view returns to the elevation view and zooms

out so that all objects are visible.
The video illustrates what happens when you reset
the view.
Drag the view of the data. Click and hold the middle mouse button and drag
your mouse.
The video illustrates what happens when you drag,
zoom, or rotate the view.
Zoom in and out of the view. Scroll your mouse wheel forwards to zoom out and
backwards to zoom in.
Rotate the view. Click and hold the right mouse button and drag the
mouse

December 2023
3D Viewer
Separation Categories and Distances
Separation Categories and Distances

EWIS regulations require that there are adequate separation distances between wires to prevent
adverse effects from current, heat, and so on. You can specify EWIS separation categories and
distances, set them for the 3D data in a design, and then run a design rule check that identifies
any wires in bundles that break any of the separation categories and distances.
During a design process that involves 3D data, a “separationCategory” property should be
added to wires in Capital. The property name must be “separationCategory”. In the below
screenshot, WIRE10 has been given a separation category value of B.
Figure 4-3. separationCategory Property
Note
There are various ways of doing this. For example, manually editing the properties dialog
box for a wire, using “Set Integrator/Topology Attribute/Property on Object” constraints in
Capital Systems Integrator, or developing a custom action in Capital Logic Designer.
The separationCategory value must match a separation category that has been set against the
design. You set separation categories and distances against a design by doing the following:
1. Create a comma-separated values (CSV) file of separation categories and distances. See
“Creating a File of Separation Categories and Distances”.
Note
When you create this file, you specify the minimum separation distance allowed
between two wires of particular separation categories. For example, a wire with
category B must be separated by a distance of 159 from a wire with category C.
2. Reference the file from the design in Capital.

After you have set the categories and distances, you run a design rule check “Wiring breaks
separation rules” against a design to check for wires in bundles that break any of the categories
and distances. See “Running Design Rule Checks” on page 247.
The check will read all the wires in the design that have a separation category, find all the
bundles that those wires pass through, and then check that the distances between those bundles
in 3D space conform to the minimum separation defined between the various categories.
Creating a File of Separation Categories and Distances . . . . . . . . . . . . . . . . . . . . . . . . . 510

December 2023
3D Viewer
Creating a File of Separation Categories and Distances
Setting Separation Categories and Distances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 511
Creating a File of Separation Categories and

Distances
You can create a comma-separated values (CSV) file of separation categories and distances that
you want to apply to the 3D data in a design.
Note
For an overview of how to use separation categories and distances in Capital, see
“Separation Categories and Distances” on page 509.
When creating this file, you are specifying the minimum separation distance allowed between
two wires of particular separation categories. For example, a wire with category B must be
separated by a distance of 159 from a wire with category C.
The CSV file must have the following format:
Figure 4-4. Example Separation CSV File
Tip
If you open the file in a spreadsheet, it is automatically formatted so that it is easier to read
and edit.
Procedure
1. Enter a first row that defines the separation categories.
In the example above, the first row defines four separation categories: A, B, C, and D.
Note
The string “separationCategory,” is not mandatory but you may want to include it to
provide context.

December 2023
3D Viewer
Setting Separation Categories and Distances
2. For each category, you can enter a row that defines the minimum separation distance
allowed between it and other categories (including itself).
Note
There is no default unit of measurement for a separation distance. It is an arbitrary
unit that matches the Capital 3D wiring space.
In the example, the second row defines that 100 is the minimum separation distance
between category A and A. “-” indicates no minimum is specified between A and B, A
and C, or A and D.
Note
A and B, A and C, and A and D do have separation distances but they are specified
on the following rows in this example.
The third row defines the minimum separation distance allowed between category B and
other categories. In this case, 200 between B and A, 10000 between B and B, no
minimum between B and C, or B and D.
Note
You should define minimum separation distances for all valid pairs of categories.
The system reads them row by row. In the example matrix above, the system reads
the A row, followed by the B row, and so on.
Because of the nature of this matrix, you can define two different distances for the same
pair of categories. That is, A,B is technically the same pair as B,A. In this scenario, the
system uses the distance value for the first pair it reads, and it ignores any subsequent
distance value defined for this pair (in the same order or reversed).
3. Save the file.

Results
You can now set these categories and distances against a design. See “Setting Separation
Categories and Distances” on page 511.

You can set EWIS separation categories and distances that are applied to the 3D data in a design
by referencing a comma-separated values (CSV) file.
Note
For an overview of how to use separation categories and distances in Capital, see
“Separation Categories and Distances” on page 509.

December 2023
3D Viewer
3D Viewer Help
Prerequisites
• You must have created a CSV file that contains the separation categories and distances.
See “Creating a File of Separation Categories and Distances” on page 510.
Procedure
1. Click the Set Separation action on the 3D ribbon tab at the top of the application.
The Set separation distances Dialog Box displays.

2. Click the Browse button.
An Open dialog box displays.
3. Navigate to the CSV file, select it, and click Open.
The categories and minimum separation distances between them display in the “Set
separation distances” dialog box.
4. Click Save.
Results
The system saves the categories and distances against the design.
Note
You can run a design rule check “Wiring breaks separation rules” against a design to check
for wires in bundles that break any of the separation categories and distances that you have
set. See “Running Design Rule Checks” on page 247.
The check will read all the wires in the design that have a separation category, find all the
bundles that those wires pass through, and then check that the distances between those bundles
in 3D space conform to the minimum separation defined between the various categories.
3D Viewer Help
What do you need help with?
• The 3D Viewer concept
• Opening the 3D Viewer
• Adding Harness Objects to the 3D Viewer
• Removing Harness Objects from the 3D Viewer

December 2023
3D Viewer
3D Viewer Help
• Viewing a Skin in the 3D Viewer

• Changing the View in the 3D Viewer
• Understanding how to work with Separation Categories and Distances
• Setting Separation Categories and Distances

December 2023
3D Viewer
3D Viewer Help

December 2023
Chapter 5
Graphics
This following sections explain how to add and edit borders, graphical shapes and graphical
objects, and how to add grip points to design objects and symbols.
Borders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Replacing a Border on a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Graphic Drawing Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Adding an Image to a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Adding Properties to a Graphical Shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Adding Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Changing the Image in an Image Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Controlling the Layering Order (Z-Order) of Graphical Shapes and Graphical Objects . . 527
Drawing a Circle in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Drawing a Curved Line in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Drawing an Arc in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Drawing an Offset in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Drawing a Rectangle in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Editing a Property Value of a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Editing the Graphical Properties of a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Transform Graphics on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Translate Graphics on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Trimming Graphics in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Graphics Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Adding a Graphics Point to a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Grip Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553

December 2023
Graphics
Adding a Grip Point to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553

Deleting a Grip Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554

December 2023
Graphics
Borders
Borders
You create borders for diagrams in Capital Symbol Designer. This section explains how to add
and edit a border in a diagram.
Replacing a Border on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 518
Adding a Border to a Diagram

You can add a border that has been created in Capital Symbol Designer to a diagram.
Procedure
1. Press Space Bar and enter Border, and then select Drawing > Border from the Search
Ribbon dropdown list.
The Edit Border Dialog Box is displayed.
2. Browse through the border libraries in the Border Selection tree and select the border to
add to the diagram.
3. Click OK. The border is added to the diagram.
Related Topics
Replacing a Border on a Diagram
Removing a Border from a Diagram

You can remove a border that has been added to a diagram at any time.
Procedure
2. Select [ No Border ] in the Border Selection tree.
3. Click OK. The border is removed from the diagram.
Related Topics

December 2023
Graphics

You can replace a border that has been added to a diagram at any time.
Procedure
2. Browse through the border libraries in the Border Selection tree and select the new
border to add to the diagram.
3. Click OK. The new border is added to the diagram.
Related Topics

December 2023
Graphics
Graphic Drawing Tools
Graphic Drawing Tools

This section explains how to add and edit non-intelligent, graphical shapes (such as lines and
rectangles) and graphical objects (images, text, glyphs and symbols) on a diagram. These are
considered as comments and do not represent any electrical connectivity.
Adding an Image to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 520
Adding Properties to a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Adding Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Adding a Comment Symbol to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Adding a Symbol to a Diagram as Graphics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Editing a Symbol Added as Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Resizing a Comment Symbol in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
Changing the Image in an Image Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Controlling the Layering Order (Z-Order) of Graphical Shapes and Graphical Objects
527
Drawing a Circle in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Drawing a Curved Line in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528
Drawing an Arc in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Drawing an Offset in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Drawing a Rectangle in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537
Editing a Property Value of a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Editing the Graphical Properties of a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . 541
Transform Graphics on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 543
Translate Graphics on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Trimming Graphics in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547

December 2023
Graphics
Adding an Image to a Diagram

You can add an image file (of type JPG, JPEG, PNG, GIF, or SVG) to a diagram. The system
considers the image to be a comment and it does not represent any electrical connectivity.
Note
SVG files are placed onto the diagram as high-resolution images, and cannot be edited as
imported vector graphics.
Prerequisites
• For linked images, the required image file must be saved in the images folder that has
been specified in the system preferences for Paths in Capital Project Manager. You
cannot navigate to any other folder.
Procedure
1. Press Space Bar and enter Image.
2. Click the diagram to place the first corner of the image frame that will contain the
image.
3. Click the diagram to place the opposite corner of the image frame. The Image Selection
Dialog Box is displayed.
4. Select the required radio button to either link or embed the image (see “Link or Embed
Images”). If you are adding an image to a non-comment symbol in Capital Symbol
Designer, these options do not display and the image will be added using the “Link to
Image” method by default.
5. Select the image file that you want to add.
For linked images, only files and sub-folders from the images folder area available for
selection. You cannot navigate to another folder location. For embedded images, you
can navigate to any location on your file system.
6. Click Select.
The image frame and image are added to the diagram. The image is scaled to fit the
image frame.
Note
In Capital Logic Designer, if you select a pin, connector, or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).

December 2023
Graphics
Adding Properties to a Graphical Shape
Related Topics
Changing the Image in an Image Frame
Link or Embed Images
Adding Properties to a Graphical Shape

You can add a property to a graphical shape, that you created with the drawing tools, so that the
property value displays on the diagram.
Procedure
1. Either:
• Select the graphical shape. Press Space Bar and enter Properties.
• Right-click the graphical shape and select Properties.
• Double-click the graphical shape.
2. The Propertied Graphic Dialog Box is displayed.
3. On the General tab, click the New button. The New Property Dialog is displayed.
4. Enter the name of the property and click OK. The property is added to the Properties
table on the General tab.
5. In the Value field, enter the value of the property and specify whether the value can be a
string, integer, or float in the Type field.
6. Click OK.
7. The value is displayed next to the graphical shape on the diagram.

December 2023
Graphics
Adding Symbols
Adding Symbols
This section describes how to add and edit comment symbols and symbols added as graphics.
Adding a Comment Symbol to a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Adding a Symbol to a Diagram as Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Editing a Symbol Added as Graphics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Resizing a Comment Symbol in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
Adding a Comment Symbol to a Diagram

You can add a comment symbol, created in Capital Symbol Designer, to a diagram and
associate the comment symbol with another object. If the associated object is moved, the
comment symbol moves to maintain its orientation to the object. Comment symbols can be used
to add a build note to a diagram.
Procedure
1. Press Space Bar and enter Comment Symbol.
The Symbol Selection Dialog Box is displayed.
2. In the Symbol Selection tree, select the comment symbol.
3. Click OK.
The comment symbol is displayed next to the cursor.
4. Move the cursor to position the symbol. Either:
• Click in free space so that the comment symbol is not associated with another object.
• Select an object to create an association and click once where you want to position
the symbol in relation to the associated object.
Note
Once a comment symbol has been placed, you can right-click it and select
Update Symbol to refresh it with the latest version of the symbol (reflecting any
changes that may have been made).
Related Topics
Resizing a Comment Symbol in a Diagram
Adding a Symbol to a Diagram as Graphics

You can add a symbol as non-intelligent graphical shapes and text to a diagram, which can be
edited independently of the symbol library.

December 2023
Graphics
Adding Symbols

• You cannot associate a symbol to a connector node.
Procedure
1. To add a symbol as graphics:
If you want to... Do the following...

Add a symbol as graphics 1. Choose a symbol name, right-click and select Place
from the Symbols tab. Symbol As Graphics ( ).
Add a symbol as graphics 1. From the Home ribbon, click the Add Line ( )
from the Symbol Selection dropdown list and select Place Symbol As Graphics.
Dialog Box. 2. Alternatively, from the Drawing ribbon, click the Add
Comment Symbol ( ) dropdown list and select Place
Symbol As Graphics.
Note: In Capital Harness Designer and Capital
Harness Designer Modular, you can click the Select
A Library Set dropdown list to choose a library.
3. Choose a name in the Symbol browser, and then click
OK.
4. Alternatively, double-click the symbol name in the
Symbol browser.
The symbol graphic is visible near the mouse cursor.

2. Move the mouse cursor over the Diagram window to the required location.
Note
Before placing a symbol graphic on a diagram, you can rotate the graphic using the
R key, and flip it using the F key.
3. To place the symbol graphic:

Place the symbol graphic in Click the required location on the diagram.
free space on the diagram.
Associate a symbol graphic Double-click the object.
directly on an object.
Associate a symbol graphic 1. Select the object.
at a distance from an object. 2. Click where you want to position the symbol in relation
to the associated object.

December 2023
Graphics
Adding Symbols
Note
If you associate the symbol graphic with an object, the symbol will move with the
object. If the object is deleted, its associated symbol is also deleted from the
diagram.
Results
The graphical shapes comprising the symbol are placed as grouped graphics that can be
ungrouped and edited, if required. See “Editing a Symbol Added as Graphics” on page 524.
Related Topics
Editing a Symbol Added as Graphics
Editing a Symbol Added as Graphics

You can edit a symbol added as graphics, independently of the symbol library.
• You cannot rotate symbols added as graphics.
Prerequisites
• The symbol must be created as graphical shapes in Capital Symbol Designer if you want
to ungroup and edit the symbol.
• The symbol must have been added to the diagram as a graphic using the Place Symbol
As Graphics ( ) action.
Procedure
1. Select the symbol graphic to edit.
2. Right-click and select Ungroup ( ).
Note
If the symbol is associated to an object, all the ungrouped graphical shapes remain
associated to the object.
3. Modify the graphical shapes in the symbol, as required.
Note
You can use a variety of tools to edit and add graphical shapes in symbols. See
“Graphic Drawing Tools” on page 519.
4. Select all the graphical shapes, right-click and select Group ( ).

December 2023
Graphics
Adding a Text Frame to a Diagram
Examples
In Capital Harness Designer and Capital Harness Designer Modular, you can edit symbols
placed as graphics to represent multi-location components (MLCs) and clips. See “Component
Graphic and Layer Order Matching” to determine the layer order of component graphics at a
node.
Related Topics
Adding a Symbol to a Diagram as Graphics
Resizing a Comment Symbol in a Diagram

You can resize (scale) an instance of a comment symbol in a diagram at any time.
Note
When resizing a comment symbol as described in this topic, datums and their text may not
scale correctly. In this case, use Capital Symbol Designer to redraw the symbol at the
required scales.
Procedure
1. Move the mouse cursor over the symbol; a bounding box is displayed.
2. Move the mouse cursor over a corner of the bounding box so that the stretch icon ( ) is
displayed, click and hold, and then drag the corner to resize the symbol.
The symbol is scaled proportionally along both the X-axis and Y-axis.
Related Topics
Adding a Comment Symbol to a Diagram
Adding a Text Frame to a Diagram

You can use the drawing tools to add a text frame to a diagram. The system considers the text
frame to be a comment and it does not represent any electrical connectivity.
Procedure
1. Press Space Bar and enter Text.
2. Click the diagram to place the first corner of the text frame.
3. Click the diagram to place the opposite corner of the text frame. The Add Text Dialog
Box is displayed.
4. Enter the text to display in the box at the top of the Add Text dialog box.

December 2023
Graphics
5. Click OK. The text frame and text is added to the diagram.
Note
If the text is not displayed, the text frame is not large enough for the text. To increase
the size of the text frame, place the mouse cursor over a corner of the frame so that
the stretch icon is displayed, click and hold, and then drag the corner.
start drawing the graphic, the graphic is automatically associated with the object (that
means, if the object is moved, the graphic moves with it).

You can change the image in an image frame that you added to a diagram.
• This procedure applies to linked images only. For embedded images you must add a new
image. See “Link or Embed Images” on page 541.
Procedure
1. Either:
• Select the image frame. Press Space Bar and enter Properties.
• Right-click the image frame and select Properties.
• Double-click the image frame.
3. On the General tab, click the ellipsis (...) button next to the Image File field.
The Image Selection Dialog Box is displayed.
4. Select the image file that you want add.
5. Click Select. The new image is displayed in the image frame. The image is scaled to fit
the image frame.
Related Topics

December 2023
Graphics
Controlling the Layering Order (Z-Order) of

Graphical Shapes and Graphical Objects
You can control the layering order (z-order) of overlapping graphical shapes (such as lines and
rectangles) and graphical objects (images, text, glyphs and symbols).
The following actions are available:
• Bring To Front
Brings the selected shapes to the front of the overlapping shapes.
• Send To Back
Sends the selected shapes to the back of the overlapping shapes.
• Bring Forward
Brings the selected shapes one layer forward in the overlapping shapes.
• Send Backward
Sends the selected shapes one layer backward in the overlapping shapes.
Prerequisites
• The graphical shapes must have been added to the diagram and are overlapping each
other.
Procedure
In the diagram window, select one or more graphical shapes and either:
• right-click a selected object and select Order > Bring To Front / Send To Back /
Bring Forward / Send Backward
• Press Space Bar and enter Bring To Front, Send To Back, Bring Forward or Send
Backward
Results
The selected shapes and objects change layer accordingly.
Deleting a Graphical Shape

You can remove a graphical shape, that you created with the drawing tools, from a diagram at
any time.

December 2023
Graphics
Drawing a Circle in a Diagram
Procedure
Either:
• Select the graphical shape, and then either:

o Press Space Bar and enter Delete, and then select Home > Delete from the
o Press the Delete key.
• Right-click the graphical shape and select Delete.
Results
The graphical shape is removed from the diagram.
Drawing a Circle in a Diagram

You can use the drawing tools to add a circle to a diagram. The system considers the circle to be
a comment and it does not represent any electrical connectivity.
Procedure
1. Press Space Bar and enter Circle.
2. Click the diagram to place the center of the circle.
3. Drag the cursor away from the center and click the diagram to place the edge of the
circle.
Note
Drawing a Curved Line in a Diagram

You can use the drawing tools to add a curved line to a diagram. The system considers the
curved line to be a comment and it does not represent any electrical connectivity.
Procedure
1. Press Space Bar and enter Curve.

December 2023
Graphics
Drawing a Fillet in a Diagram
2. Click the diagram to place the first end of the curved line.
3. Click the diagram to place further points along the curve and double-click on the
diagram or press the Enter key to place the second end of the curved line.
Note

You can use the Fillet tool to round the corners of graphics or create a bi-tangent arc between
two intersecting or non-intersecting lines.
• Lines will automatically be trimmed or extended to complete the fillet on the concave
side of the arc only.
In the following example the lines are on the convex side of the arc, and the line will not
be extended beyond its maximum point A.
Figure 5-1. Example Maximum Permitted Fillet
Prerequisites
• Object snapping must be enabled. Object snapping will be automatically enabled when
Fillet Graphics is invoked.

December 2023
Graphics
Procedure
1. To create a fillet:
• Press the space bar and enter Fillet.
• Click the Fillet Graphics icon ( ). You can Shift-click the Fillet Graphics icon to
continue drawing fillets without needing to invoke the action again.
• Right-click and select Drafting > Fillet.
The cursor changes to
2. Select the first line of the corner or one of the non-intersecting lines where the fillet
starts.
3. Select the second line where the fillet ends.
Dynamic graphics display the fillet between the two lines at an initial radius relative to
the position of the cursor.
A tooltip displays the current radius value in the units of measure specified in the Set
Grid Defaults Dialog Box.
Figure 5-2. Dynamic Graphics and Tooltip
4. You can modify the fillet by:

• Moving the cursor to change the radius size with each increment of the mouse to the
required value.
See Drafting Settings Dialog Box to specify the “Move mouse increments” values
for the Fillet Graphics action.
• Press Ctrl to open the Set Radius dialog box and specify a precise radius value. The
fillet is automatically applied when you click OK.

December 2023
Graphics
Figure 5-3. Set Radius for Fillet
5. You can click the diagram to flip the dynamic graphics and reverse the curvature of the
fillet.
Figure 5-4. Dynamic Graphics with Reversed Fillet
6. Double-click or press Enter to apply the fillet.

Results
The fillet is created, and the lines are trimmed or extended to close the ends to the fillet.

December 2023
Graphics
Drawing a Line in a Diagram
Figure 5-5. Example with Trimmed and Extended Lines
The graphic attributes (except arrow heads) and properties of the first line are applied to the
created arc.
If the two lines are part of a rectangle, for example, if you are adding rounded corners to a
rectangle, then the rectangle is converted to a polyline.

You can use the drawing tools to add a line to a diagram. The system considers the line to be a
comment and it does not represent any electrical connectivity.
Procedure
1. Press Space Bar and enter Line.
2. Click the diagram to place the first end of the line.
3. Move your mouse to where the second end of the line should be.
As you draw the line, a tooltip displays the following information:
• Length — The length of the line in the units of measure defined in the “Set Grid
Defaults Dialog Box” on page 872.
• Slope — The angle of the line measured to the horizontal plane oriented left to right,
between -180 degrees to +180 degrees. Negative values apply to lines with a
downward direction when oriented left to right.
• Angle — If you are moving the end of an existing line, or the line intersects with
another line, then the angle and its complement to 180 degrees is shown, otherwise it
is not shown.

December 2023
Graphics
If the line intersects several other lines, only the angle at the intersection closest to
the cursor location is shown.
If you are moving the end of an existing line, it shows the angle between the original
position and the new position.
Figure 5-6. Angle between new position and original position
If the line intersects with another straight line, it shows the angle of intersection.
Figure 5-7. Angle of intersection with another straight line
4. When you are drawing the line, you can lock either the length or the slope of the line to
prevent unwanted changes. While drawing the line, press and hold the appropriate line
stretch locking key as configured in the “Drafting Settings Dialog Box” on page 857.
5. To insert a waypoint into the line, click once again on the diagram, otherwise, place the
second end of the line by double-clicking or by pressing the Enter key.
Note

December 2023
Graphics
Drawing an Arc in a Diagram
Drawing an Arc in a Diagram

You can use the drawing tools to add an arc to a diagram. The system considers the arc to be a
comment and it does not represent any electrical connectivity.
Procedure
1. Press Space Bar and enter Arc.
2. Click the diagram to place the first end of the arc.
3. Click the diagram to place the second end of the arc.

4. Drag the cursor away from the ends and click the diagram or press the Enter key to place
the curve of the arc.
Note
Drawing an Offset in a Diagram

You can use the Offset Graphics tool to create a parallel profile of graphics at a precise offset
distance.
• Curves are not supported by the Offset Graphics tool. Circles and arcs are supported.
Prerequisites
• You have previously drawn a line or shape on the diagram.
• Object snapping must be enabled. Object snapping is automatically enabled when Offset
Graphics is invoked.
Procedure
1. To create an offset:
• Press the space bar and enter Offset.
• Click the Offset Graphics icon ( ). You can Shift-click the Offset Graphics icon
to create multiple parallel profiles without needing to invoke the action again.
• Right-click and select Drafting > Offset.

December 2023
Graphics
2. Select the graphic to offset.

Alternatively, you can select the graphic before invoking the action.
Dynamic graphics display the parallel profiles at an initial default offset distance or the
value of the previously applied offset.
A tooltip displays the current offset value in the units of measure specified in the Set
Grid Defaults Dialog Box.
Figure 5-8. Dynamic Graphics and Tooltip
3. Select which side of the graphic you want the offset to appear by moving the cursor to
the appropriate side. The dynamic graphics will move and adjust to the other side.
4. The offset distance that was used previously is retained, allowing you to create multiple
equidistant offsets. You can change the offset distance by:
• Clicking free space on the diagram and moving the cursor to change the offset
distance with each increment of the mouse to the required value.
See Drafting Settings Dialog Box to specify the “Move mouse increments” values
for the Offset Graphics action.
You can click free space again to lock the new offset value and visualize the offset
using the dynamic graphics.

December 2023
Graphics
• Pressing Ctrl to open the Set Offset dialog box and specifying a precise offset value.
The offset is automatically applied when you click OK.
5. If required, you can select segments of the graphic to exclude or include the segments
when you apply the offset.
Figure 5-9. Dynamic Graphics with Fillet Deselected
Results
The parallel profile is created at the specified offset distance from the graphic.
Each offset graphic retains its graphic attributes, including arrow heads, and properties.
The parallel profile is selected automatically ready to apply another offset if required.
Graphics that intersect themselves, for example the shape shown below, will produce multiple
offset profiles.

December 2023
Graphics
Drawing a Polygon in a Diagram
Figure 5-10. Example of Self-Intersecting Shape Producing Multiple Offset

Profiles
Drawing a Polygon in a Diagram

You can use the drawing tools to add a polygon to a diagram. The system considers the polygon
to be a comment and it does not represent any electrical connectivity.
Procedure
1. Press Space Bar and enter Polygon.
2. Click the diagram to place the first corner of the polygon.

3. Click the diagram to place further corners and double-click the diagram or press the
Enter key to place the last corner.
Note
Drawing a Rectangle in a Diagram

You can use the drawing tools to add a rectangle to a diagram. The system considers the
rectangle to be a comment and it does not represent any electrical connectivity.
Procedure
1. Press Space Bar and enter Rectangle.
2. Click the diagram to place the first corner of the rectangle.

3. Click the diagram to place the opposite corner of the rectangle.

December 2023
Graphics
Drawing a Tangent in a Diagram
Note

You can draw a line at a tangent to a circle or arc.
• Drawing a tangent to a curve is not supported. You can draw lines tangential to circles
and arcs.
Prerequisites
• You must have Object Snapping enabled.
• The circle or arc to which you want to draw a tangent must be present on the diagram.
Procedure
1. Create a new line, or click the end of an existing line to enter stretch mode. See
“Drawing a Line in a Diagram” on page 532.
2. Move the cursor to the circle or arc.
Several grip points appear on the circle or arc to which the line can snap, including one
where the line is tangent.
The line can be terminated here if required.
Figure 5-11. Snap point for tangent

December 2023
Graphics
3. The tangent line can be extended by pressing and holding the slope locking key as
configured in the Drafting Settings Dialog Box.
Figure 5-12. Extending line at tangent
Results
The line is placed at a tangent to the circle or arc.

December 2023
Graphics
Editing a Property Value of a Graphical Shape
Figure 5-13. Line at tangent to curve
Editing a Property Value of a Graphical Shape

You can edit a property value of a graphical shape, that you created with the drawing tools, at
any time.
Procedure
1. Either:
3. On the General tab, edit the Value field for the property and click OK.
Results
If the Visible check box for the property is selected in the dialog box the new value is displayed
next to the graphical shape on the diagram.

December 2023
Graphics
Editing the Graphical Properties of a Graphical Shape
Editing the Graphical Properties of a Graphical

Shape
You can edit the appearance (color, thickness, line style and fill pattern) of the lines of a
graphical shape, that you created with the drawing tools.
Procedure
1. Either:
3. On the Graphical tab, edit the values as required and click OK.
Results
The appearance of the graphical shape on the diagram changes accordingly.
Grouping Graphical Shapes

You can group together graphical shapes to edit and move them like they are one object.
Procedure
1. Press Ctrl and select the required graphical shapes in the diagram.
2. Either:
• Press Space Bar and enter Group.
• Right-click one of the selected shapes and select Group.
Results
A frame is displayed around the shapes and you can edit them as one object.
Related Topics
Ungrouping Graphical Shapes

When you are adding images to a diagram, there are two choices on the Image Selection Dialog
box which allow you to either Link to Image or Embed Image.

December 2023
Graphics
Moving a Graphical Shape
Link to Image
If you choose this option, the selected image displays in the diagram using a link to the image
file in the Images folder (as specified in the system preferences for Paths in Capital Project
Manager).
Only the path to the image file is saved with the diagram and not the image file itself. Once
saved, the diagram will not display the image if, for example, the file is moved or you export the
design to another database where the exact file and path are not present on the target system.
All diagrams that link to an image file are automatically updated if the image file is changed.
Embed Image
If you choose this option, the selected image is embedded in the diagram. This removes the need
to maintain a link to the path of the inserted image, as is the case with a linked image, because
the image data is stored with the diagram itself.
This option is available in Capital Harness Designer, Capital Harness Designer Modular,
Capital Logic Designer, Capital Systems Integrator, Capital Wiring Integrator, Capital E/E
Publisher, and Capital Symbol Designer (where images can be embedded in comment symbols).
Related Topics
Image Selection Dialog Box
Moving a Graphical Shape

You can move a graphical shape, that you created with the drawing tools, at any time.
Procedure
1. Position the cursor over the graphical shape.
The graphical shape is highlighted and the cursor changes to .
2. Click and hold, and then drag the shape.
Stretching a Graphical Shape

You can stretch a graphical shape, that you created with the drawing tools, at any time.

December 2023
Graphics
Transform Graphics on a Diagram
Procedure
1. Position the cursor over a graphics point ( ) on the graphical shape.
The graphical shape is highlighted and the cursor changes to .
2. Click and hold, and then drag the graphics point to stretch the shape to its new
dimensions.

You can rotate and scale individual graphics, multiple selected graphics, or grouped graphics on
the diagram.
Procedure
1. Select the graphics that you want to transform. You can select individual graphics,
multiple graphics or graphics that have been grouped together. If you attempt to invoke
Transform Graphics without a valid selection, a message will be displayed informing
you that graphics must be selected before invoking the action.
2. To begin the transform:
• Press the space bar and enter Transform
• Click the Transform Graphics icon ( )).
• Right-click and select Drafting > Transform.

A bounding box shown as dynamic graphics previews the position of the graphics. An
arrow shown on the source graphics and on the dynamic graphics represents the angle of
rotation.
A tooltip shows the scale factor that will be applied and the rotation from the original
graphic.

December 2023
Graphics
Figure 5-14. Preview of Transform Graphics Action With Tooltip
3. You can modify the transform by:

• Moving the cursor to change the rotation and scale factor.
• Press Ctrl to open the Set Transform dialog box. You can configure the width,
height, scale factor, rotation from the original, and angle from the horizontal. If you
change a value, the other values will be automatically updated. The transform is
applied when you click OK.
Figure 5-15. Set Transform Dialog

December 2023
Graphics
Translate Graphics on a Diagram
4. Double-click or press Enter to apply the transform.

Results
The graphics are rotated and scaled.
Figure 5-16. Result of Transform Graphics Action

You can create a copy of individual graphics, multiple selected graphics, or grouped graphics on
the diagram at a specified distance and angle from the original.
Procedure
1. To begin the translation:
• Press the space bar and enter Translate.
• Click the Translate Graphics icon ( ). You can shift-click the Translate
Graphics icon to continue copying the selected graphics without needing to invoke
the action again.
• Right-click and select Drafting > Translate.
Dynamic graphics preview the position of the graphics. An arrow shows the direction
and angle of translation.

December 2023
Graphics
A tooltip shows the angle and distance of the translation.

Figure 5-17. Preview of Translate Graphics Action With Tooltip
2. You can add or remove graphics or segments of graphics from the selection by clicking
on them.
Figure 5-18. Preview of Translate Graphics Action With Graphic Segments
Deselected
3. If you have previously performed a translation then the same angle and distance will be
applied to subsequent translations. You can modify the translation by:
• Click once to change the angle and distance of translation using the cursor.
• Press Ctrl to open the Set Translation dialog box. You can configure the distance
from the original, and angle from the horizontal. The translation is applied when you
click OK.

December 2023
Graphics
Trimming Graphics in a Diagram
Figure 5-19. Set Translation Dialog Box
4. Double-click or press Enter to apply the translation.

Results
• The graphics are copied to the location.
Figure 5-20. Result of Translate Graphics Action
• If you invoked the Translate Graphics action in continuous mode then you will be
prompted to apply the same translation again, which you can modify (see Step3).
• Graphic attributes, including arrow heads, and properties are copied

You can use the Trim Graphics tool to delete lines and segments of graphical shapes, and trim
sections of graphics up to and between graphical intersections.
• Curves are not supported by the Trim Graphics tool. Circles and arcs are supported.
Prerequisites
• Object snapping must be enabled. Object snapping is automatically enabled when Trim
Graphics is invoked.

December 2023
Graphics
Procedure
1. To trim graphics:
• Press the space bar and enter Trim.
• Click the Trim Graphics icon ( ). You can Shift-click the Trim Graphics icon to
continue trimming without needing to invoke the action again.
• Right-click on the diagram and select Drafting > Trim.
2. To trim a single graphic:

Hover the cursor over the graphic to be trimmed.
The graphic is highlighted depending on the number of intersecting graphics:
• No intersection — Segment of the graphic.
• 1 intersection — Section of the segment up to the intersection.
• 2 intersections — Section of the segment between the intersections.
Figure 5-21. Example Segments and Intersections
3. When the correct section of the graphic is highlighted, click to complete the trim.
4. To trim multiple graphics:
Click and drag the cursor to draw a trace line on the diagram. Wherever this trace line
intersects a graphic, it is selected (or deselected if it was all ready selected).

December 2023
Graphics
Figure 5-22. Selecting Multiple Graphic Segments for Trimming
Release the mouse button and draw a new trace to select additional graphics.
Double-click or press Enter to complete the trim.
Results
• The selected segments or sections of the graphics are removed.
Figure 5-23. Result of Trimming Multiple Selected Graphic Segments
• Rectangles that have a section removed are converted to polylines.

December 2023
Graphics
• Circles that have a section removed are converted to arcs.

• Graphic attributes, including arrow heads, are preserved.

You can ungroup graphical shapes, that you grouped together previously, so that you can edit
and move them as separate objects.
Procedure
Either:
• Click one of the shapes in the group to select the group. Press Space Bar and enter
Ungroup.
• Right-click one of the shapes in the group and select Ungroup.
Results
The frame around the shapes is deleted and you can edit them separately.
Related Topics
Grouping Graphical Shapes

December 2023
Graphics
Graphics Points
Graphics Points
A graphics point is a point you can stretch a graphical shape to resize or reshape it.
The following topics explain how to add graphics points to graphical shapes in a diagram and
how to delete them.
Adding a Graphics Point to a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551

Adding a Graphics Point to a Graphical Shape

You can add a graphics point to a line, polygon, or curved line, that you created with the
drawing tools. A graphics point is a point at which you can stretch a graphical shape to resize or
reshape it.
Procedure
1. Either:
• Select the graphical shape. Press Space Bar and enter Add Graphic Point.
• Right-click the graphical shape and select Add.
2. Click the graphical shape where you want to add the graphics point.
Results
The graphics point is added to the graphical shape.
Related Topics
Deleting a Graphics Point

You can delete a graphics point on a graphical shape in a diagram at any time.
Note
If you delete a graphics point that forces a line to form a corner, the line straightens to
follow the shortest route between the graphics points on either side of the deleted graphics
point.

December 2023
Graphics
Procedure
1. Either:
• Select the graphical shape. Press Space Bar and enter Delete Graphics Point.
• Right-click the graphical shape and select Delete.
2. Click the graphics point you want to delete.

Results
The graphics point is deleted.
Related Topics
Adding a Graphics Point to a Graphical Shape

December 2023
Graphics
Grip Points
Grip Points
A grip point is point that you add to a wire, net, shield termination or highway in Capital Logic
Designer, a bundle in Capital Systems Integrator, a bundle in Capital Harness Designer or an
internal link in Capital Symbol Designer. It divides the object into graphical sections that can be
resized and reshaped.
The following topics explain how to add a grip point to an object and how to delete it.
Adding a Grip Point to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553

Deleting a Grip Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
Adding a Grip Point to an Object

You can add a grip point to a wire, net, shield termination, or highway in Capital Logic
Designer, a bundle in Capital Systems Integrator, a bundle in Capital Harness Designer, or an
internal link in Capital Symbol Designer to divide the object into graphical sections that you can
resize and reshape.
Procedure
1. Either:
• Select the object. In Capital Logic Designer or Capital Systems Integrator, press
Space Bar and enter Add Grip Point. In Capital Harness Designer or Capital Symbol
Designer, press Space Bar and enter Add, and then select Home > Add from the
• In Capital Logic Designer, Capital Systems Integrator or Capital Harness Designer,
right-click the object and select Grip Point > Add. In Capital Symbol Designer,
right-click the object and select Add.
In Capital Logic Designer, Capital Systems Integrator, or Capital Harness Designer, the
cursor changes to if it is positioned over the object or to otherwise. In Capital
Symbol Designer the cursor changes to .
2. Click the object where you want to add the grip point.
Results
The grip point is added to the object.
Related Topics
Deleting a Grip Point

December 2023
Graphics

You can delete a grip point on an object in a diagram.
Note
If you delete a grip point that forces an object to form a corner, the corner straightens so that
the line follows the shortest route between the grip points on either side of the deleted grip
point.
Procedure
1. Either:
• Select the object. In Capital Logic Designer or Capital Systems Integrator, press
Space Bar and enter Delete Grip Point. In Capital Harness Designer, press Space Bar
and enter Delete, and then select Home > Delete from the Search Ribbon
dropdown list. In Capital Symbol Designer, press Space Bar and enter Delete, and
then select Home > Delete from the Search Ribbon dropdown list.
• In Capital Logic Designer, Capital Systems Integrator or Capital Harness Designer,

right-click the object and select Grip Point > Delete. In Capital Symbol Designer,
right-click the object and select Delete.
In Capital Logic Designer, Capital Systems Integrator or Capital Harness Designer the
cursor changes to if it positioned over a grip point or to otherwise. In Capital
Symbol Designer the cursor changes to
2. Click the grip point you want to delete.

Results
The grip point is deleted.
Related Topics
Adding a Grip Point to an Object

December 2023
Chapter 6
Layout
This section contains information about how to perform layout-related actions.

Grouping Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Creating a Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Ungrouping Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Aligning Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Distributing Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Flipping Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 561
Rotating Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Rotating Objects Around a Specified Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564
Free Rotating Text Decorations, Comment and RED Symbols or Graphical Objects . . . . 565
Example of Applying Styling on Rotated or Flipped Objects . . . . . . . . . . . . . . . . . . . . . . 566
Pivoting Text About its Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Setting Snap To Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Setting Grid Defaults for a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Splitting Tables Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571
Using Japanese Text on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571

December 2023
Layout
Grouping Objects in a Diagram
Grouping Objects in a Diagram

This section contains details about how to group and ungroup graphical objects so that they can
be selected, and moved, aligned or distributed, as a single entity.
Creating a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556
Ungrouping Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 557
Creating a Group
You can group graphical objects so that they can be selected, moved, aligned, and distributed as
a single entity.
Procedure
1. Select the objects. Either:
• Press Ctrl and select the objects.
• Click and hold at one corner of the area that encloses the objects, and then drag the
cursor to define an enclosing window selection.
2. Either;
• Press Space Bar and enter Group
• Right-click and select Group
Note
If the Group action is dimmed, a tooltip on that action displays a message “Selection
contains objects that cannot be grouped”. Objects that cannot be grouped include:
print regions, objects created by styling, border zone area objects, leader lines, and
datum representations. The action is also dimmed if only one graphical object is selected
or if the selected objects have different parent objects.
The Group action availability for a set of objects depends on how those objects have
been selected. If there is electrical information, such as datums, in a comment symbol
that you have selected with other graphics in an enclosing window, the Group action is
dimmed. However, if you select those same objects individually using the Ctrl key and
clicking, the Group action is enabled.
A new highlight is applied to all of the selected objects, showing the outside limit of the
group.
Results
Grouped objects can be dragged to a new position on the canvas as a single entity. Clicking to
select any object in the group results in the whole group being selected, which can then be
moved by clicking and dragging the outside border.

December 2023
Layout
Ungrouping Objects
Ungrouping Objects
It is not possible to remove a single object from a group. Instead, the collection of objects must
be ungrouped, and then create a new group minus the unwanted object.
Procedure
1. Select the group by clicking on any object within it.
2. Either:
• Press Space Bar and enter Ungroup
• Right-click and select Ungroup
The group highlight disappears, leaving each object independently selectable.
Related Topics
Aligning Objects in a Diagram
Distributing Objects in a Diagram

You can align all objects apart from tables, pins, and indicators in a diagram window.
Note
If an object has pins, they move with the object. If a device and connector are connected,
they move together but the alignment depends on which of those objects has been selected.
If conductors are connected to an object, they move to maintain the connectivity.
Procedure
1. Select the objects.
2. Either:
• Press Ctrl and select the objects.
or
3. Press Space Bar and enter Align, and then select the appropriate action:
• Align Left ( )
Objects align with the left-most object

December 2023
Layout
Before:
After:
• Align Right ( )
Objects align with the right-most object

Before:
After:
• Align Top ( )
Objects align with the top-most object

Before:

December 2023
Layout
After:
• Align Bottom ( )
Objects align with the bottom-most object

Before:
After:
• Align Vertically ( )
Object center points align along the vertical plane

Before:
After:
• Align Horizontally ( )
Object center points align along the horizontal plane

December 2023
Layout
Before:
After:
4. The objects are aligned accordingly.

You can distribute all objects apart from pins and indicators in a diagram window so that there
is an equal distance between them.
Note
If an object has pins, they move with the object. If a device and connector are connected,
they move together but the alignment depends on which of those objects has been selected.
If conductors are connected to an object, they move to maintain the connectivity.
Procedure
1. Select the objects. Either:
• Press the Ctrl and select the objects.
or
2. Press Space Bar and enter Distribute, and then select the appropriate action:
• Distribute Horizontally ( )
The left-most and right-most objects do not move. If there is enough space, the other
selected objects move so that there is an equal horizontal distance between each of
them. Otherwise, the objects move so that there is an equal horizontal distance
between their center points. No objects move vertically.

December 2023
Layout
Flipping Objects in a Diagram
Before:
After:
• Distribute Vertically ( )
The top and bottom objects do not move. If there is enough space, the other selected
objects move so that there is an equal vertical distance between each of them.
Otherwise, the objects move so that there is an equal vertical distance between their
center points. No objects move horizontally.
Before:
After:
3. The objects are distributed accordingly.

You can flip objects about a specified axis in a diagram.

December 2023
Layout
Note
When an object is rotated and has styling applied again, the created decorations/shape
respect the rotation. See “Example of Applying Styling on Rotated or Flipped Objects” on
page 566.
Procedure
1. Select one or more objects that you want to flip.
Note
If you select multiple objects, they are flipped as a group around one axis.
2. Do one of the following:

• Press Space Bar and enter Flip
• Right-click one of the selected objects and select Flip from the menu
The cursor changes to and a dashed axis line is displayed along the sides of the
object or object group as you move the cursor around the selected objects.
3. Move the cursor to the side of the objects where you want to flip them and click once.
Results
The objects flip over the axis line.
If text is included in a graphic group (such as a symbol), when you flip the graphic group the
text is rendered in such a way that it maintains the same gap from the horizontal (flip) axis
afterwards.
Figure 6-1. Text Before Flip

December 2023
Layout
Figure 6-2. Text After Flip

December 2023
Layout
Rotating Objects in a Diagram

You can rotate objects about a specified point in a diagram and freely rotate primitive graphical
objects and comment symbols around their center point.
The following topics are available.
Rotating Objects Around a Specified Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 564

Free Rotating Text Decorations, Comment and RED Symbols or Graphical Objects . 565
Example of Applying Styling on Rotated or Flipped Objects . . . . . . . . . . . . . . . . . . . . . 566
Rotating Objects Around a Specified Point

You can rotate objects about a specified point in a diagram to change their layout at any time.
Note
When an object is rotated and has styling applied again, the created decorations/shape
respect the rotation. See “Example of Applying Styling on Rotated or Flipped Objects” on
page 566.
Procedure
1. Select one or more objects that you want to rotate.
Note
If you select multiple objects, they are rotated as a group around one point.
2. Press Space Bar and enter Rotate.

3. Click the point around which you want to rotate the objects.
4. The objects rotate at a 90 degree increment around the point.
Note
All text labels are orientated as part of the flip process to ensure that they can be read
correctly.
Defining Rotation Increments

You can specify the major and minor rotation increments that the system uses in the free
rotation of primitive graphical objects and comment symbols around their center point.

December 2023
Layout
Free Rotating Text Decorations, Comment and RED Symbols or Graphical Objects
Procedure
1. Press Space Bar and enter Set Rotation Degrees.
2. Set the Minor Rotation Increment used for finer grained rotational control. Default value
is 1 degree.
3. Set the Major Rotation Increment used for coarser grained rotational control. Default
value is 5 degrees.
4. Click OK to confirm your settings.
Free Rotating Text Decorations, Comment and RED

Symbols or Graphical Objects
You can freely rotate various objects around their center points by a pre-defined major or minor
rotation increment: style set text decorations, comment symbols, symbols styled within REDs
(Related Entity Decorations), and primitive graphical objects.
See also “Rotating a Table” in the Capital Harness Designer User Guide.

• Electrical Connectivity Objects and Electrical Symbols do not have free rotation
enabled.
• For RED symbols, to select only the symbol you want to rotate, and exclude all other
decorations that are styled as part of the decoration set, press Ctrl and then select the
required symbol.
• Running Apply Style resets any rotated text decorations to their default rotation, unless
they are configured to be excluded from apply style or have their styling fixed.
• Text decorations configured in the style set to auto flip, will never display upside down
when rotated.
Procedure
1. Select one object that you want to rotate.
2. Either:
• Press Ctrl + > to rotate the object clockwise by a major increment. Press Ctrl + < to
rotate counterclockwise. For finer grained control, press Ctrl + Shift + > or Ctrl +
Shift + < to rotate the object.
or
• Press Ctrl and use the middle mouse button to scroll forwards or backwards to rotate
the object clockwise or counterclockwise by a major increment. For finer grained
control, press Ctrl + Shift and then use the middle mouse button to scroll.

December 2023
Layout
Example of Applying Styling on Rotated or Flipped Objects
Results
• The object rotates at the pre-defined degree increment around its center point.
Related Topics
Defining Rotation Increments
Example of Applying Styling on Rotated or Flipped

Objects
This example demonstrates what happens when styling (as defined in a style set) is re-applied to
an object that has been rotated or flipped.

December 2023
Layout
Prerequisites
In this example, styling has been defined for a device as follows:
Procedure
1. Define styling for a device as follows:

December 2023
Layout
2. When a new device is created, styling is applied as below:
• If that device is rotated by 90 degrees and styling is applied to it again, all

decorations rotate as per the rotation angle:

December 2023
Layout
Pivoting Text About its Axis
• If that device is flipped about the horizontal axis and styling is applied to it again, all
decorations respect the flip as in this example:
Related Topics
Pivoting Text About its Axis

You can pivot text about its axis from 0 degrees to 270 degrees, and the other way around.
Procedure
1. Select one or more text strings that you want to pivot.
2. Press Space Bar and enter Pivot Text.
3. If the text is at 0 degrees on its axis, it pivots to 270 degrees. If the text is at 270 degrees
on its axis, it pivots to 0 degrees.
Setting Snap To Object

When adding or modifying a comment graphic, you can position it to automatically “Snap To”
alignment with another graphic on a diagram.
Note
Snap To Object is always enabled by default. You can clear the setting to position objects
close together, but not touching. The Snap To Object setting only affects comment graphics.
Procedure
1. With the diagram open, press Space Bar and enter Snap to Object.
2. Comment graphics are aligned accordingly on the diagram.

December 2023
Layout
Setting Grid Defaults for a Diagram
3. The following objects may be snapped to:

• Rectangle — markers for center, corner mid-point of edge, also snaps to any other
point on edge.
• Circle — marker for center, top, bottom, left and right, also snaps to any point on
circumference.
• Line — markers for start, end or mid-point of segment, also snaps to any point on
edge.
• Polygon — markers for start, end or mid-point of segment, also snaps to any point
on edge.
• Arc — markers for start, end of mid-point, also snaps to any point on arc.
• Curve — markers for the grip points, no snapping to the curve itself.
Note
Snap to Object overrides Snap to Grid except for electrical objects. In this case
Snap to Grid settings are also retained.
Setting Grid Defaults for a Diagram

You can specify how grid points are displayed on a diagram (number of points and spacing),
and the percentage of a grid point to use as the distance between the invisible drawing grid
points.
Procedure
1. With the diagram open, press Space Bar and enter Set Grid Defaults.
The Set Grid Defaults Dialog Box is displayed.
2. Specify the following values:
• Major Grid Interval
• Maximum Drawn Points
• Drawing Grid
3. Click OK.
The grid changes accordingly on the diagram.

December 2023
Layout
Splitting Tables Manually
Caution
When new and existing designs are opened, the Diagram Project Preferences
override any associated values you specify in the Set Grid Defaults dialog box. If
you wish to permanently use the same grid settings for all diagrams you should specify
the required values here.

You can control the way in which large tables are broken down into smaller numbers of
columns or rows, allowing more flexible placement of the table content.
Procedure
1. With the diagram open, select Override Styling > Split Table from the context menu of
the selected table.
The Split Table Dialog Box is displayed.
2. Specify the required table splitting settings.
3. Click Apply. The table changes accordingly on the diagram.
Note
See the Diagram Styling User Guide for more information about all aspects of table
styling.
Using Japanese Text on a Diagram

There are prerequisites for displaying Japanese fonts and characters in diagrams.
Procedure
Follow these guidelines:
• You must use a Japanese operating system

• You must set your Oracle installation to support Japanese. See the documentation
supplied by Oracle for information.
• The Font for the text must be set to a Japanese font.

December 2023
Layout
Using Japanese Text on a Diagram
Caution
You can export a file with Japanese text and import it into a non-Japanese
operating system. However, you cannot make changes to that data and re-import
it into the Japanese operating system. In this case, the Japanese text remains intact
but some things, such as the diagram name, are no longer readable in the Japanese
operating system.

December 2023
Chapter 7
Rules and Constraints
This section contains details of how to apply rules and constraints to designs and design objects.
Overview of Rules and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Editable Elements in Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Regular Expressions in Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Defining Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
Assigning a Rule or Constraint to an Object or Design . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Usage Example - Using a Null Value in a Constraint . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Rule Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 584

December 2023
Overview of Rules and Constraints

You can set rules and constraints on designs and design objects to control certain actions, and to
control how objects behave in certain situations.
For example:
• In Capital Systems Integrator, you can set rules and constraints to control how the
system places devices in slots, synthesizes wiring and sets properties/attributes for
objects.
• In Capital Logic Designer, you can use one constraint to set properties and attributes on
objects.
• In Capital Harness Designer, you can set rules and constraints to control wire paths on a
harness diagram and to enable harness processing to optimize a harness design based on
preset criteria.
• In Capital Wiring Integrator, you can set rules and constraints to control how the system
places devices in slots and routes conductors.
• In Capital Formboard Designer, you can set rules and constraints to control how
formboard fixtures are populated into a diagram.
• In Capital Harness Designer Modular, you can set rules and constraints to control how
module codes are assigned to objects.
Note
If you are using rules and constraints in Capital Systems Integrator, see the Rules
and Constraints section of the Capital Systems Integrator User Guide for more
detailed information and usage examples.
The generative flow (and wiring synthesis in particular) rely on user-configured constraints to
control the results of the automated process.
This overview examines the following concepts:
Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 574
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Constraints
A constraint is a statement that can be applied to a whole design, or to individual objects within
a design. It can be applied as an individual constraint or as part of a rule. For example (in
Capital Systems Integrator): Don't place devices with property matching Name=Battery here.

December 2023
Constraints
If this example constraint were set for a slot, the system would not place a device with a Name
property of Battery in that slot.
You use constraint templates to define a constraint. For full lists of the standard constraint
templates available for specific design applications, see the following:
• Capital Harness Designer constraint descriptions

o Routing
o Splice Repositioning
o Auto Create Components
o Fixture Constraints
o Markers
• Capital Formboard Designer constraint descriptions
• Capital Modular Harness constraint descriptions
o Module Assignation Constraints
o Set Cavity Details Generation Method Constraint
• Capital Systems Integrator constraint descriptions
• Capital Logic Designer constraint descriptions
• Standard Constraints for Capital Wiring Integrator
• The Constraint Selection Dialog Box fields
You can write your own custom constraints in Java and load them into the design applications.
For more information about writing and loading custom constraints, see the
PluginDevelopment.pdf document that is located in the doc\plugin folder of your Capital
installation. Once custom constraints are loaded into the applications, you use them in the same
way as standard constraints. An object can have both standard and custom constraints defined
for it.
The design rule check “Missing Custom Constraint Check” can be run to report on any custom
constraints that have been defined for an object, but are no longer loaded.
Related Topics
Creating a Strategy for Constraint Definition in Capital Integrator [Capital Systems Integrator
User Guide]
Assigning a Rule or Constraint to an Object or Design

December 2023
Rules
Rules
A rule can consist of one constraint or a groups of constraints and can be applied to a whole
design or to individual objects within a design. You can define rules from within the design
applications or from within Capital Project Manager. In Capital Project Manager, you can
define rules either at a project level or you can define rule libraries at a system level. A rule
library can be added to a project. See the Capital Project Manager help system for more
information about defining rule libraries.
Note
In Capital Logic Designer a rule can be applied to a whole design only.
A rule can contain (reference) other rules and therefore include their constraints.
You can create rules at a system level and import the required rules into a project when
necessary. All rules are available to every project created within Capital Project Manager.
Related Topics
Defining Rules
Object Rule Hierarchies

Rules can be set for different objects in a design and this means that there can be conflicts
between the rules and constraints that have been set. For this reason, rule hierarchies determine
which rule/constraint is used on each object. The rules/constraints on an object lower down a
hierarchy override the rules/constraints on objects higher up a hierarchy.
For example (in Capital Systems Integrator):
A rule/constraint on a cavity overrides a rule/constraint on a connector. A rule/constraint on a

connector overrides a rule/constraint on a slot. A rule/constraint on a slot overrides a rule/
constraint on a diagram.
Note
For more detailed information about object rule hierarchies and hierarchical object rule
resolvers in Capital Systems Integrator, see Object Rule Hierarchies in Capital Systems
Integrator in the Capital Systems Integrator User Guide.
Related Topics
Editable Elements in Constraints
Defining Rules

December 2023

Editable elements in constraints are displayed in green and red. These elements allow you to
tailor the constraint to meet your specific requirements.
Note
Constraints include match clauses. A match clause is a value that follows an operator such
as =. When creating a match clause, you must use a regular expression (regex). You can use
wildcards in the regular expression. See “Regular Expressions in Constraints” on page 580 for
further details.
The following elements may be displayed:
• Only/Don't
Select Only or Don't from the dropdown list.
• Do
Select Do or Don't from the dropdown list.
• Expression
Click to display a dialog box to define an option expression. You can type the
expression manually or you can click the ellipsis (...) to open the Edit Option Expression
facility.
• Name
By default, this refers to the Name attribute of an object. Click to display a dialog box.
You can select to reference either an attribute or property and you select the specific
attribute or property from the dropdown list.
• Slot Name
Click to display a dialog box. If the Use Slot Name box is selected, the Name attribute of
a slot is used. If you clear the box, you can enter another string.
• ObjectName
Click to display a dialog box. If the Use Object Name box is selected, the Object Name
property is used. If you clear the box, you can enter another property name.
• Ruled Object Name
Click to display a dialog box. If the Use Ruled Object Name box is selected, the value
for the Object Name property is used. If you clear the box, you can enter another
property value.
• Value

December 2023
This is used typically when you want to use rules to add properties and attributes to
wires, splices, and multicores.
Select one of the following:
o Literal
This means it is a literal value. Enter the value string in the box. You can use
wildcards in this string. Click the OK button to exit the dialog box.
o Attribute
This means the value is derived from the value of an attribute on the functional
signal or multicore. Select the attribute from the dropdown list in the box. Click the
OK button to exit the dialog box.
o Property
This means the value is derived from the value of a property on the functional signal
or multicore. Enter the property name in the box. Click the OK button to exit the
dialog box.
• Num
Enter an integer.
• Object
Select an object type from the dropdown list.
• Object Type
Select an object type from the list that is displayed when you click this.
• Spec
Enter a specification string.
• .*
This is the same as a literal value string but is a wildcard by default.
• Wire Part Specification
Select WireMaterialCode, WireColor or WireSpec from the dropdown list.
• AttrOrProp
Select either Attribute or Property. For an attribute, select the attribute name from the
dropdown list. For a property, enter the property name in the box or select from the list
of pre-defined property names in the dropdown list. Click the OK button to exit the
dialog box.

December 2023
If a constraint contains a clause for matching it to particular objects (for example, Object
Name = PropValue), you can also edit the match operator that is = by default. The
available operators are:
= Equal to
!= Not equal to
< Less than
> Greater than
<= Less than or equal to
>= Greater than or equal to
For example:
Only route signals with property matching Object Name != Signal01
In this example, only signals that do not have a value of Signal01 for the Object Name
property will be routed.
Do place devices with property matching Rating >= 7.5 here
In this example, only devices that have a value greater than or equal to 7.5 for the Rating
property will be placed.
When specifying a property value string in a constraint, you can use wildcards.
For example:
.* is all possible strings
si.* is any string starting with si.
If you are using Wire Part Specification constraints and Terminal Type Specification
constraints and you are using wildcards when defining property value strings, prioritized
pattern matching is used if there are two constraints of the same type on an object. This
means that if two constraints of the same type can both apply to one signal, the
constraint most specific to that signal will be used.
There are three levels of match quality:
o Level 1 - a broad default. For example: ObjectName = .*
o Level 2 - a refined wildcard. For example: ObjectName = sig.*
o Level 3 - a specific match. For example: ObjectName = signal
Level 3 overrides level 2 and level 2 overrides level 1.

December 2023
Regular Expressions in Constraints
If there is a situation where the wildcards in constraints of the same type match, an error
will be generated. For example, the following situations would generate an error:
o ObjectName = .* in one Wire Part Specification constraint on an object and
ObjectName = .* in another Wire Part Specification constraint on the same object.
o ObjectName = si.* in one Terminal Type Specification constraint on an object and
ObjectName = sig.* in another Terminal Type Specification constraint on the same
object.
o ObjectName = signal in one Wire Part Specification constraint on an object and
ObjectName = signal in another Wire Part Specification constraint on the same
object.
Related Topics
Defining Rules
Regular Expressions in Constraints

Constraints include match clauses. A match clause is a value that follows an operator such as =.
When creating a match clause, you must use a regular expression (regex). You can use wild
cards in the regular expression.
For example:
• Wire Spec: Wire Color is BK where Signal matches Name = [0-9][0-9]0

• Wire Spec: Wire Color is BK where Signal matches Name = \d\d0
[0-9][0-9]0 and \d\d0 are match clauses written as regular expressions. These examples both
mean the same because [0-9] is equivalent to \d. The color BK is assigned to any signal whose
name consists of exactly three digits, the last of which is 0. They therefore match 340 for
example, but not 341, 20, or 6540, and so on.
The following are examples of regular expression wild cards:
• . matches any single character.

• * matches the preceding character zero or more times (this is why .* matches any string
of characters).
• ? matches the preceding character once or not at all.

December 2023
Defining Rules
You can also do things like match any one of a number of characters by putting them in square
brackets:
• [abc] will match either a or b or c.

• [a-z] will match any character in the range a to z.
• [0-9] will match any digit in the range 0 to 9. This is the same as \d.
So for example: [a-z][0-9][0-9] would match k26 or z97, and so on.
Another useful example is putting ^ at the beginning of a group of characters: [^abc] will match
any character except for a ,or b, or c.
You can use | between regular expressions to mean OR. For example, you could have the
following: Name = Sig1.*|SpecialSig
This matches any signals whose names start with Sig1 and also matches a signal with the name
SpecialSig.
If you want to include a special character in a match clause, you must escape it with a backslash.
For example, if you wanted to match against a device called DEV|200, your match clause
should be the following: DEV\|200
For complete details of regular expressions, perform an Internet search for "java regex pattern".
Defining Rules
You can define a rule at project-level to assign it to appropriate objects in the project.
Note
If you are using rules and constraints in Capital Systems Integrator, see “Rules and
Constraints” in the Capital Systems Integrator User Guide for more detailed information
and usage examples.
Procedure
1. In a design application, press Space Bar and enter Rules; the Define Rules Dialog Box is
displayed.
2. Click New; the Rule Name dialog box is displayed.
3. Specify the name of the rule and click OK; the rule name is added to the Rules window.
4. Specify the constraints that you want the rule to include:
• To add constraints, click the Add Constraint ( ) button; the Constraint Selection
Dialog Box is displayed. Select the constraints and click OK.

December 2023
• To reference another rule (and therefore add its constraints), click the Add Rule
Reference ( ) button; the Rule Selection Dialog Box is displayed. Select the rule
and click OK.
The constraints are added to the Constraints window.
5. Edit the green and red elements in the constraints to contain the required values. See
“Editable Elements in Constraints” on page 577 for a list of editable elements.
Note
If you have added a rule reference, the rule name is displayed. Select it to display the
constraints included in it. You cannot edit them here.
6. Click OK to exit the dialog box.

Results
The rule can be assigned to objects within the project.
Related Topics
Assigning a Rule or Constraint to an Object or

Design
You can assign a rule or constraint to a specific object or design in a design application.
Note
If you are using rules and constraints in Capital Systems Integrator, see the “Rules and
Constraints” section of the Capital Systems Integrator User Guide for more detailed
information and usage examples.
Procedure
1. Open the Properties dialog box for the object or design and click the Rules tab; the
Rules Tab in Properties Dialog Box displays the rules and constraints that have been
assigned to the object already.
Note
It also displays the rules and constraints that have been assigned to any objects to
which the current object belongs (for example, a slot belongs to a harness, a harness
belongs to a design).

December 2023
Usage Example - Using a Null Value in a Constraint
2. Specify the rules and constraints to assign to the object:

• To add constraints, click the Add Constraint ( ) button; the Constraint Selection
Dialog Box is displayed. Select the constraints and click OK.
• To assign a rule (and therefore assign its constraints), click the Add Rule Reference
( ) button; the Rule Selection Dialog Box is displayed. Select the rule and click
OK.
The constraints are added to the Constraints window.
3. Edit the green and red elements in the constraints so that they contain the required
values. See “Editable Elements in Constraints” on page 577 for a list of editable
elements.
Note
If you have added a rule, the rule name is displayed. Select it to display the
constraints included in it. You cannot edit them here.
If you want to use a customized version of a constraint (if any have been made available
using Extensibility Plugins), click the ( ) icon next to it and select the customized
version from the dropdown list.
4. Click OK to exit the Properties dialog box.

Results
The constraints will be taken into account when any related actions are performed.
Related Topics
Defining Rules
Usage Example - Using a Null Value in a

Constraint
In this example, you add a Wire Specification constraint to a Capital Systems Integrator
diagram. The constraint tells the system to assign a wire specification of 0.35 to wires
synthesized from signals that have a wire specification value of null (that is, a blank value).
In this case, you also want the system to copy the wire specification from signals that have one
to the wires synthesized for them. To enforce this, you add a second Wire Specification
constraint to the diagram.

December 2023
Rule Libraries
Procedure
1. In Capital Systems Integrator, right-click on the diagram name in the Design Browser
(Plane tab) at the bottom left of the application window and select Properties; the Plane:
<Plane Name> dialog box is displayed.
2. Click the Rules tab; the tab displays any rules or constraints that have been applied to
the diagram already.
3. Click the Add Constraint ( ) button; the Constraint Selection dialog box is displayed.
4. Under Attributes and Properties, double-click Wire Specification; a default Wire

Specification constraint is added to the Rules tab:
Wire Spec: AttrOrProp is Value where Signal matches Name = .*
5. Edit the constraint so that it looks like this:
Wire Spec: Wire Specification is 0.35 where Signal matches Wire Specification = ^$
^$ is a regular expression that represents a value of null.
6. Repeat steps 3 and 4; another default Wire Specification constraint is added to the Rules
tab.
7. Edit the constraint so that it looks like this:
Wire Spec: Wire Specification is ValueOf(WireSpec) where Signal matches Name = .*
8. ClickOK; the Plane: <Plane Name> dialog box closes.
Results
When you use the Set Attribute/Property action from the ribbon:
• The system assigns a wire specification of 0.35 to wires synthesized from signals that
have a wire specification value of null.
• The system copies the wire specification from signals that have one to the wires
synthesized for them.
Related Topics
Defining Rules
Rule Libraries
A Rule Library is a collection of rules which are defined by the user at the system-level, to
enable a number of rules to be grouped together. Once you have defined system rules, you can

December 2023
Rule Libraries
assign them to specific projects. You can access these rules from design applications to add
them to designs or objects within designs.
See also “Rule Libraries” in the Capital Project Manager User Guide.

December 2023
Rule Libraries

December 2023
Chapter 8
Modifying Objects
This chapter contains procedures related to modifying objects on a diagram.

Object Attributes and Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Assigning a New Library Part to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590
Assigning/Editing an Object's Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Bulk Editing the Properties of Design Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Defining Specification Attributes for a Conductor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Editing an Object's General Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Editing the Graphical Attributes of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Editing the User-Defined Properties of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
Foreground, Background and Manual Color Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
Freezing and Unfreezing Shared Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
Simultaneous Editing of Multiple Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Specifying a Wire Color with a Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
Systems Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Specifying Option-Specific Values for Net Attributes and Properties . . . . . . . . . . . . . . . . 606
Unassigning a Library Part from an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Updating Library Parts Assigned to Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Viewing the Library Part Details for an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
Converting a Symbol to a Parameterized Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
Assemblies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Adding Assemblies Containing Connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
Adding Associated Comment Graphics or Comment Symbols to an Assembly . . . . . . . . 615
Adding Objects Within the Associated Comment Graphic Boundary to an Assembly . . . 617
Creating an Assembly from the Part Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Deleting an Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Extending the Selection of Objects for an Assembly Comment Graphic or Symbol. . . . . 621
Removing an Object from an Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Renaming an Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Physical Line Thickness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626

December 2023
Modifying Objects
Setting the Default Physical Line Thickness for Comment Graphics . . . . . . . . . . . . . . . . 626
Setting the Physical Line Thickness for Graphics in Diagrams . . . . . . . . . . . . . . . . . . . . . 627
Using a Plugin Interface to Control Physical Line Thickness . . . . . . . . . . . . . . . . . . . . . . 628
Finding and Replacing Property Values, Attribute Values and Symbols . . . . . . . . . . . 629
Advanced Naming Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 633
Generating Names for all Objects in a Build List, Design or Diagram . . . . . . . . . . . . . . . 634
Generating Names for Selected Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Selecting a Component Part Number in the Part Selection Dialog Box . . . . . . . . . . . . . 636
Performing a Batch Update of Library Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636
Slicing Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
Navigating Between Sliced Object Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
Reconnecting a Sliced Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Slice and Move To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Slicing a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Slicing a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646
Slicing Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647
Slicing Conductors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Slicing Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Slicing Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Slicing to Trim Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Design Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Opening Design Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Viewing Design Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658

December 2023
Modifying Objects
Object Attributes and Properties

In Capital, attributes and properties are distinctly different. An attribute is a quality or
characteristic of an object within Capital. Object attributes are built-in to Capital and particular
tool behavior is inferred by their presence and value. A property is a user-defined name/value
pair assigned to an object. You can display and report properties, as well as use them in rules
and analysis functionality.
In design applications, you use the Properties Dialog Box to edit the attributes and properties of
objects. You can select individual or multiple objects for which you want to edit attributes and
properties.
Note
The Pin Type attribute enables you to specify the type of pin. If a net is connected to more
than one device with a usage definition, the list of net names displayed depends on the pin
types to which it is connected. The pin types can be IN, OUT, IxO, IxO Terminated, NC, PWR,
and GND. These are defined in Capital Component Manager. See the Capital Component
Manager help system for more information about defining pin types. In Capital Symbol
Designer and Capital Logic Designer, you can specify the pin type “U” that means that no pin
type is specified. This can be overwritten when you assign the symbol to a library part in Capital
Component Manager.
Assigning a New Library Part to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590

Assigning/Editing an Object's Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Bulk Editing the Properties of Design Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Defining Specification Attributes for a Conductor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 596
Editing an Object's General Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597
Editing the Graphical Attributes of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598
Editing the User-Defined Properties of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
Foreground, Background and Manual Color Options. . . . . . . . . . . . . . . . . . . . . . . . . . . 601
Freezing and Unfreezing Shared Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602
Simultaneous Editing of Multiple Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603
Specifying a Wire Color with a Comment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604
Systems Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 605
Specifying Option-Specific Values for Net Attributes and Properties . . . . . . . . . . . . . . 606
Unassigning a Library Part from an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Updating Library Parts Assigned to Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609
Viewing the Library Part Details for an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 611

December 2023
Modifying Objects
Assigning a New Library Part to an Object

You can assigning a library part to an object in a design. The object inherits the attributes and
properties of the library part. This is not available in Capital Symbol Designer.
Prerequisites
• Footprint Library Parts
A library part with a footprint may, or may not have a symbol associated with it in
Capital Component Manager. In either case, you can assign the library part to existing
devices (including shared devices) in a Capital Logic Designer diagram.
If the library part has device connectors, device connectors are added to the device in
Capital Logic Designer. In the case of a shared device, the device connectors are added
to the shared instances.
If a library part has a symbol associated with it, the graphical representation of the
device in Capital Logic Designer does not change to the symbol when you assign that
library part to it.
• Library Part Usage on Shared Objects in Capital Logic Designer
When a library part is assigned to a shared object, if the number of pins/cavities on the
library part is greater than the number of pins on the shared object, the number of pins
necessary to account for difference is added to the shared object.
When a library part is assigned to a shared device, if you have selected a symbol for the
library part, that symbol is added to the shared device and you are presented with a
dialog to map shared pins to the symbol pins.
• Library Part Usage in Capital Systems Integrator
Library parts on slots that are included with a harness. If a slot has been included with a
harness, a library part can be assigned to the underlying physical connector. To do this,
continue as though assigning a library part to the slot but the library part is really
assigned to the connector.
o Footprint Library Parts
In Capital Logic Designer designs, devices can have a library part associated with
them. If the library part has a footprint associated with it, this affects what you can
do in Capital Systems Integrator.
When the device with the footprint is placed in a slot in Capital Systems Integrator,
the physical connectors are defined by this information. This means that you cannot
delete related virtual connectors in a slot that has such a library part assigned.
o Parts on Slots

December 2023
Modifying Objects
A slot is treated like a 'room' and the physical device of the slot is the equipment that
may contain multiple devices. A library part assigned to the slot is for the equipment,
not for the device or devices placed inside the slot.
o Parts on Specialized Connectors and Generalized Connectors
You can assign a library part to a virtual connector or inline connector half
(generalized connectors). If you do this, you cannot use the Refine
Connector facility to define specialized connectors.
If you have defined specialized connectors for a generalized connector, you cannot
use the Edit Properties facility to assign a library part to the generalized connector. If
you want to do this, you must delete any bundle fanouts that you have created for it.
If you have defined specialized connectors, you can use the Refine Connector
facility (see “Refining Connectors” in the Capital Systems Integrator User Guide) to
assign library parts to the individual specialized connectors. If a specialized
connector has been defined by a footprint in Capital Logic Designer, you cannot
assign a library part to it in Capital Systems Integrator.
When adding or changing a library part for a device that has already been added to a
design, the list of devices from Capital Component Manager is filtered to show only
those with an equal or greater number of cavities to the device in the design.
• Editing Multiple Objects Simultaneously
If you have selected multiple objects with different library parts, Multiple Part Numbers
is displayed at the top of the Library Part section. You can only remove the library part
associations in this scenario.
If you are adding a library part to multiple objects, you will have to associate pins with
each object. In addition, the information passed to the library part selector will be about
the lowest common denominator aspects of the objects. This means, if you have selected
a 4-pin device and a 6-pin device, you can select only library parts with a minimum of 6
pins.
You cannot edit library parts if the selected objects are of different object types. If you
have selected multiple multicores, library part selection is only possible if the multicore
structure is the same for all selected objects.
Procedure
1. Right-click the object and select Properties; the Edit Properties dialog box is displayed.
2. Click the Add (...) button in the Library Part section of the General tab; the Part
Selection Dialog Box is displayed.
3. Search for the library part, select it and click Insert.

December 2023
Modifying Objects
Assigning/Editing an Object's Options
4. If you are assigning a library part to a device, connector or backshell, the Map Pins
Dialog Box is displayed. Associate the pins from the library part with the pins on the
object, then click OK.
If you are assigning a library description to a multicore, the Assign Library Multicore
Dialog Box prompts you to assign the innercores from the library multicore to the
multicore wires in the design. When you have associated the multicore wires, click OK.
Results
The library part number is displayed at the top of the Library Part section of the General tab.
Note
If the details for a library description are changed in Capital Component Manager, they are
not updated automatically in Capital Logic Designer or Capital Systems Integrator, you
must update them manually. See the “To update an object's library part” section below.
Related Topics

You can specify the variant harness options (as an option expression) that are applicable to a
design object. This controls when an object is included on a harness.
The options specified for a design object in Capital Logic Designer or Capital Systems
Integrator are used to distinguish the individual variant harness designs when applying the
Evaluated Designs facility in Capital Project Manager. See “Evaluated Design” in the Capital
Project Manager User Guide for further information about evaluated designs. Options are not
applicable to Capital Symbol Designer.
Procedure
1. Either:
• Select the object to you want assign or edit the option expression for. Press Space
Bar and enter Properties.
• Right-click the object to you want assign or edit the option expression for and select
Properties.
The Properties Dialog Box displays.
2. In the Configuration section, enter the option expression in the Option field. You can
either enter the expression manually or click the ellipsis button (...) next to the Option
field to display the Edit Option Expression Dialog Box.

December 2023
Modifying Objects
Bulk Editing the Properties of Design Objects
After a device has been placed using variant-based placement, the General tab of the
properties dialog box for a device displays the Expression field under the heading
Placement to distinguish the option expression from regular option tagging.
Note
The options that are available for assignment to the object in the Edit Option
Expression dialog box are initially created for the object's project and then assigned
to the object's design using the Applicable Options facility in the Capital Project
Manager application. See the Capital Project Manager help system for more information
on creating and assigning options and evaluated designs.
If no options have been assigned specifically to the design, the system displays all of the
options that have been created for the project.If you attempt to enter an invalid option
expression in the Option field, the text is displayed in red and the OK button is dimmed.
If you attempt to enter an invalid expression in the Expression field in the Edit Option
Expression dialog box, the text is displayed in red and that dialog box’s OK button is
dimmed.
3. Select the Visible box if you want the option expression to be displayed next to the
object on the diagram. You can set the graphical attributes for the text that is displayed
by clicking the Edit Attributes button to display the Edit Name Text Attributes Dialog
Box. Click OK to exit the Edit Attributes dialog box.
4. Click OK to exit the properties dialog box.

In Capital Harness Designer, Capital Harness Designer Modular and Capital Logic Designer,
you can bulk edit the properties for single and multiple selected objects. You can also select
multiple objects and view their shared attributes.

December 2023
Modifying Objects
Note
These two videos demonstrate how to use the Edit Objects Dialog Box,
• Part 1 covers ways to access the dialog box, cross highlighting and zooming, filtering on
objects or columns, and moving columns.
• Part 2 looks at editing the table and using OTI properties on the table.

December 2023
Modifying Objects
Procedure
Decide the action you want to perform:

Edit the properties and view 1. Select the object, or one of its entities on the diagram,
the attributes of a single alternatively select the object in the browser tree.
selected object using Capital 2. Use one of the following methods:
Harness Designer or Capital
Harness Designer Modular. • Click the ribbon action.
• Right-click on the selected object and select “Edit
xxx” (where xxx is the name of the object type).
• Double-click on one of the related entities belonging
to the object.
• Press the Alt + Enter keys.
• Press Space Bar and enter Edit Object.
The Edit xxx dialog box is displayed.
Note: Depending on behavior settings specified at
Project level, you may be prohibited from creating
or modifying certain object attributes and properties.
These are displayed as read-only. In general it is only
Capital Logic Designer, topographical and electrical
attributes and properties that are protected and these
should be modified prior to import into Capital Harness
Designer. Other harness design attributes and
relationships, for example, plugging / sealing a
connector may still be modified as required.
3. Make any changes required to the attributes and/or
properties.
4. Click OK to save any changes.
Edit the properties and You can follow the steps in the next row below. You can
attributes of a single selected also use the methods described in the Object Attributes and
object using Capital Logic Properties topics.
Designer.

December 2023
Modifying Objects
Defining Specification Attributes for a Conductor

Bulk edit the properties and 1. Select multiple objects on the diagram or in the browser
view the attributes of tree.
multiple objects. 2. Use one of the following methods:
In Capital Harness Designer and Capital Harness
Designer Modular:
• Click the ribbon action.

• Right-click and choose Table Editor.
• Press the Alt + Enter keys.
• Press Space Bar and enter Edit Object.
In Capital Logic Designer:
• Click the ribbon action.
• Right-click and choose Table Editor.
• Press Space Bar and enter Table Editor.
The Edit Objects Dialog Box displays.
Note: Depending on behavior settings specified at
Project level, you may be prohibited from creating
or modifying certain object properties. These are
displayed as read-only.
3. Make any (bulk) changes required to the properties.
Attributes can be viewed in this dialog box but not
edited.
4. Click OK to save any changes.

You can define the color, material, spec and CSA in the Edit Properties dialog for a conductor in
a design.
Note
When you assign a library part to the conductor, the Part Selection Dialog uses these
attributes to restrict the search for a library part.
Procedure
1. Right-click the object and select Properties; the Edit Properties dialog is displayed.
2. In the Specification section of the General tab, specify the Color, Material, Spec, and
CSA as required. If you want to display any of these attribute values next to the
conductor in the diagram, select the box next to the field and click the button to
display the Edit Graphical Attributes dialog where you specify how it is displayed.

December 2023
Modifying Objects
Editing an Object's General Attributes
3. Click OK to apply the specified values and exit the facility.

You can edit the general attributes (such as name, short description, option) of an object in a
design tool. Object attributes are built-in to Capital and particular tool behavior is inferred by
their presence and value.
Note
Please see the Bulk Editing the Properties of Design Objects topic for alternative ways to
edit object properties and attributes in Capital Logic Designer, Capital Harness Designer
and Capital Harness Designer Modular.
Procedure
1. Right-click the appropriate design object, select the Properties option.
2. Click the General tab in the Properties Dialog Box.
Note
To edit the general properties of a border in Capital Symbol Designer, you must
right-click to the side of the border in the diagram window to access the Edit
Properties facility.
3. Edit the attributes as required, and click OK.
Note
When you use a function symbol in a functional diagram, attributes specified for it in
Capital Symbol Designer carry over to the object in the diagram.
Related Topics
Specifying the Name Attribute of an Object
Updating Library Parts Assigned to Components
Unassigning a Library Part from an Object
Viewing the Library Part Details for an Object
Assignation of Module Codes to Capital Logic Designer Components [Capital Logic Designer
User Guide]

December 2023
Modifying Objects
Editing the Graphical Attributes of an Object

In diagrams, an object assumes the application’s default graphical attribute values when you
create it. However, you can edit these attributes (primary and secondary colors, line thickness,
line style, fill pattern, line end style and fill color).
Procedure
1. Right-click the object, choose Properties, and then click the Graphical tab.
2. Edit the graphical attributes as required.
If you want to ... Do the following:

Change the primary or • Primary Color
secondary color Choose the primary color from the dropdown list; the
preview box previews the selected color.
• Secondary Color
Only displayed for wires, nets, highways, shield terminations
and daisy chains in Capital Logic Designer/Capital E/E
Publisher and for bundles in Capital Systems Integrator.
Only available if a broken line style is selected in the Line
Style field.
The secondary color is the color of the gaps in a broken line.
Choose the secondary color from the dropdown list; the
preview box previews the selected color.
As well as color names, the list contains the following options.
See “Foreground, Background and Manual Color Options” on
page 601.

December 2023
Modifying Objects

Change the line 1. Select Override in the first dropdown list.
thickness 2. Choose the type of thickness in the third dropdown list.
• Logical
These thicknesses do not have a physical unit of
measurement. They provide a logical progression of
thickness with a default of 1. A line with thickness 2 is
displayed twice as thick as a line with thickness 1, and so
on. When you zoom in or out of a diagram, the line
thickness does not appear any different.
The physical unit of measurement that has been specified
as the Unit in the style set applied to the diagram. The line
thickness is displayed in relation to the grid size of a
diagram. When you zoom in or out of a diagram, the line
grows or shrinks to stay in scale with the grid.
When you select a unit, the middle dropdown list changes
to a free text field where you specify the thickness. The
value can be any floating-point number up to three decimal
places.
3. Specify the numerical value of the thickness in the middle
dropdown list or free text field.
Change the line style 1. Select Override in the first dropdown list.
2. Choose the required line style from the second dropdown list.
The line style will display with the color currently selected in the
Primary Color setting.
If the object is a wire, net, highway, shield termination or daisy
chain in Capital Logic Designer/Capital E/E Publisher or a
bundle in Capital Systems Integrator and the line style selected is
broken, the color of the gaps in a broken line can be set in the
Secondary Color field.
Change the fill pattern 1. Select Override in the first dropdown list.
2. Click Default box or Change box.
The Fill Pattern Selection Dialog Box displays.
3. Click the required pattern, and specify the foreground and
background colors.
4. Click OK on the Fill Pattern Selection dialog box.
Note: If you add a fill pattern to grouped objects, the fill
pattern is lost when you ungroup them.
Tip: Fill pattern can be used, for example, to highlight the
function of a connectivity object when producing service
documentation.

December 2023
Modifying Objects
Editing the User-Defined Properties of an Object

Change the line end 1. In the Line End Style section at the bottom of the facility,
style of a conductor click the Left dropdown list and select the style of arrow to
display at the left end of the conductor. When you select an
arrow style, it is previewed in the window below the
dropdown list. If you do not want an arrow at the end of the
conductor, select the blank line from the dropdown list.
2. Click the Right dropdown list and select the style of arrow to
display at the right end of the conductor.
The style is applied to every end-segment of the conductor. An
end-segment is a segment where at least one end point is not
connected to another segment from the same conductor.
Change the fill color Choose the color from the dropdown list; the preview box
previews the selected color.
It is available for parameterized objects (not symbols) in Capital
Logic Designer.
The fill color for an object type can also be controlled by the
style set applied to the diagram. See the “Fill Color” option in
the Styling Options - Graphics section of the Capital Diagram
Styling User Guide.
Tip: Fill color can be used, for example, to highlight the
function of a connectivity object when producing service
documentation.
3. Click OK.
Results
The system applies your changes to the object in the diagram.

You can add, edit, and delete your own properties for a graphical object or symbol.
Note
See “Bulk Editing the Properties of Design Objects” for alternative ways to edit object
properties and attributes in Capital Logic Designer, Capital Harness Designer and Capital
Harness Designer Modular.

• In Capital Harness Designer / Capital Harness Designer Modular, you cannot use the
style set to lock the Visibility of text properties added to symbols. See the “Protect
symbol property text” Project Preference, to avoid deleting text properties on the
diagram.

December 2023
Modifying Objects
Foreground, Background and Manual Color Options
Procedure
1. Right-click the appropriate design object and select Properties, to open the Propertied
Graphic Dialog Box.
2. Perform one of the following actions:

Add a property 1. Click New, to open the New Property dialog box.
2. Specify the property name and click OK. The property
row is displayed in the table.
3. Specify the value, type, and display settings for the
property as required, and then click OK.
Edit the value of an existing Type the value in the Value column, and then click OK.
property
Delete a property Select the property row in the table and click Delete. The
system deletes the property from the object.
Foreground, Background and Manual Color

Options
Wherever you can select a color, as well as color names, the list contains various options.
You can toggle the background color in the Diagram window between black and white.
See “Changing the Background Color of a Diagram” on page 496.
If you apply a default, background, or foreground color to objects on the diagram, the color of
the objects inverts when the background color is toggled.
Note
The background color change only affects on-screen viewing. Printing a diagram is always
executed with a white background.
• Default
The default color used for the object by the system.
• Query
You can use a query expression to specify the conditions required to select the color.
If a suitable Query Expression is not available, click the Edit Queries button, to create a
new query expression, or copy and modify an existing expression in the Edit Query
Expressions dialog box.

December 2023
Modifying Objects
Freezing and Unfreezing Shared Objects
If you have developed extensibility plugins to select the color, click the Plugin button to
select a plugin.
• Background
The same color (black or white) used for the background of the diagram.
• Foreground
If the diagram background is white, the foreground is black, and the other way around.
• Manual
The Choose Object Color dialog box is displayed, to select a color.
Caution
When you define a color manually, the software only uses the RGB value and
ignores the following values:
• Any Transparency value on the HSV or HSL tabs.
• Any Alpha value on the RGB or CMYK tabs.
Freezing and Unfreezing Shared Objects

You can freeze a shared signal, message, or function to prevent changes being made to its
attributes or properties. Freezing a shared function also prevents changes being made to its
shared object definition (its ports, port reservations, and associated symbols).
When a shared object is frozen, you can still add new instances of the shared object to diagrams,
change the appearance of instances of the shared object on diagrams, place ports that exist in the
shared object definition onto instances of the shared object, and remove ports from instances of
the shared object. In Capital Project Manager, you can change the reservation status of ports on
shared functions.
Tip
If you have the necessary permission set in Capital Access Manager, you can unfreeze a
shared object after it has been frozen. The unfreezing of a shared object is an administrative
operation and can be done on any frozen shared objects. This might not be possible if a design is
read-only.
If your user account has the “Frozen Shared Object Port Attributes/Properties” permission, you
can edit the attributes / properties for frozen shared object ports.

• If you revise a design that contains frozen objects, you can make only connectivity
changes to those shared objects. You cannot edit attributes, properties, or part numbers.
To make such changes, you must create a revision of the shared object.

December 2023
Modifying Objects
Simultaneous Editing of Multiple Objects
See also “Creating a Revision of a Shared Object” in the appropriate documentation:

o Capital Logic Designer User Guide
o Capital Project Manager User Guide
o Capital Systems Modeler User Guide
Procedure
1. To freeze a single shared object, right-click the object in the Shared Object Browser
window and select Freeze Shared Object.
A blue snowflake is displayed on the shared object icon ( ) in the browser window.
2. To unfreeze a single shared object, right-click the object in the Shared Object Browser
window and select Unfreeze Shared Object.
3. To freeze or unfreeze multiple shared objects:
a. In the Shared Objects Browser window, click the Freeze/Unfreeze Shared Objects
icon ( ).
The Freeze/Unfreeze dialog box is displayed.

b. Select or clear the shared objects to freeze / unfreeze, and then click OK.

You can select multiple objects to edit properties and attributes that apply to all of those objects.
Note
Please see the Bulk Editing the Properties of Design Objects topic for alternative ways to
edit object properties and attributes in Capital Logic Designer, Capital Harness Designer
and Capital Harness Designer Modular.
If you select multiple objects of different object types, the selection of tabs displayed on the
Properties Dialog Box may be limited. In addition, the properties and attributes that you can edit
may be limited. This is because not all properties and attributes can be applied to all object
types.
For example:
If you select a wire and a device, a Wire Color attribute is listed but you cannot change it
because it cannot be applied to all of the selected objects.
Even if a property is not editable because it does not apply to all selected objects, you can still
change whether it is visible or not.

December 2023
Modifying Objects
Specifying a Wire Color with a Comment
If any of the selected objects are frozen, you can only edit graphical properties.
Note
You cannot edit equipotential nets as part of a multiple selection.
If a property does not currently apply to all of the selected objects, a check box is displayed at
the start of the Value field when you select it. Select if you want the property and its value to
apply to all of the selected objects. You can change the value of the property at any point.
If a property does apply to all of the selected objects but the objects have different values for it,
Multiple Values is displayed in the Value field with a dropdown list of the different values. You
can select one of these values and select the box at the start of the Value field to apply it to all
selected objects, or you can leave the field as Multiple Values so that the objects retain their
different values. Alternatively, you can enter an entirely new value that will apply to all of the
selected objects.
If there is a list of possible values defined for a property, these are listed in the dropdown list
with the used values in the Value field. Any values that are already used on the selected objects
are displayed in bold.
If a property has a different Type value (string, integer or float) on different objects, you cannot
edit it and Different Types is displayed in the Value field.
Specifying a Wire Color with a Comment

When specifying a color attribute (in a Color field) for a wire, you can add a comment to the end
of the color.
Caution
You cannot add a comment to a color code if # has been set as a color separator in the
System Preferences.
Prerequisites
• The required color codes must already exist in your library.
Procedure
1. Enter the color code in the field. In the example below, the wire has a primary color LG,
a secondary color R, and uses a color separator /.
Figure 8-1. Color Attribute

December 2023
Modifying Objects
Specifying Connector Cavity Component Drivers in Capital Logic Designer and Capital Systems
2. At the end of the color value, type # and then the comment. In the example below, the
comment is “Color created by user 1”.
Figure 8-2. Color Attribute with Comment
Specifying Connector Cavity Component Drivers in

Capital Logic Designer and Capital Systems
Integrator
For a wire in Capital Logic Designer or Capital Systems Integrator, you can specify connector
cavity component drivers, that is, the required terminal material for a wire end, terminal part
number, and seal part number.
Note
You can view this information in Capital Wiring Integrator, but not edit it.
This enables you to:
• Specify terminal material for each wire end (including on shared wires in Logic).
• Create an early bill of materials, while still validating all cavity component selections in
the harness domain.
Procedure
1. Right-click a wire and choose Properties, click the Connections tab in the Properties
Dialog Box.
2. For each wire end, specify the required terminal material, terminal part, and seal part as
appropriate. See “Connections Tab (Properties Dialog Box)” on page 783 for details of
editing these fields.
3. Click OK to close the dialog box.
Results
Note
If you move a wire from one connector to another, the attributes do not change. If they need
to be removed or changed, you must edit the Connections tab for the wire again.
• When you synchronize data to Capital Harness Designer, the drivers (material, required
terminal part, require seal part) are transferred and the part numbers are selected in the
Material, Required Terminal, and Required Seal fields of the Edit Wires dialog box if
they are valid.

December 2023
Modifying Objects
Specifying Option-Specific Values for Net Attributes and Properties
• If validation fails in Capital Harness Designer and the system is unable to select a
specified part, Cavity Component Management and a design rule check “Terminal and
cavity seal selected part validity” report the invalid requirements. Both of these report
which part was selected instead.
Specifying Option-Specific Values for Net

Attributes and Properties
In Capital Logic Designer and Capital Systems Integrator, the Variance tab in the Edit
Properties facility for net conductors in Capital Logic Designer enables you to specify option-
specific values for net attributes and properties. For example, a net conductor can have a
WireColor attribute of blue when used in one option and a WireColor attribute of green when
used in another option.
When the Capital Logic Designer design is associated with a Capital Systems Integrator design,
the Variance tab can be viewed (but not edited) in the Edit Properties facility for signals in
Capital Systems Integrator. The option-specific values are taken into account when composite
wiring synthesis is performed.
Note
The Variance tab will not be displayed for an object if there are no options defined in a
project or if the project preference for “Mandate applicable options” has been set and the
design does not have any applicable options.
Any properties specific to the individual net conductor or to the net conductor object type can
have option-specific values.
The attributes that can have option-specific values are:
• WireColor
• WireCSA
• WireMaterial
• WireSpecification
In order for these attributes or net-specific properties to be available on the Variance tab, they
must have a valid value set on the Properties tab or General tab of the Edit Properties facility.
Procedure
1. Right-click the net conductor in the diagram or Logical Design Browser Window and
select the Properties option from the popup menu.

December 2023
Modifying Objects
2. Ensure that the attribute or property has a valid value set on the Properties tab or General
tab of the Edit Properties facility. This value is used as the default value when no option
expression has been applied to the net.
3. Click the Variance tab and click the New button in the Option Variable Attributes or
Option Variable Properties section as appropriate.
4. The Option Selection dialog is displayed. From the dropdown list, select the attribute or
property, and then click the OK button.
5. A row for that attribute or property is added to the appropriate table. In the Options
column, specify the option expression to which the value applies. You can click the
ellipsis (...) button to display the Edit Option Expressions facility that helps you to
define the expression. In the Value field, specify the option-specific value.
You repeat steps 2 to 5 for each option-specific value for that attribute or property.
6. Click the OK button to exit the Edit Properties facility.
Note
There are two design rule checks that can be run in Capital Systems Integrator that
are relevant to these option-specific values, “Wire that breaks specification rule” and
“Option-based variance inconsistency”. See “Design Rule Check Descriptions” on
page 261.
7. To delete an Option-Specific Value, select the row for the option-specific value on the
Variance tab and click the Delete button.

You can specify the format and diagram display characteristics of an object's name. This is not
available in Capital Symbol Designer.
Note
See “Bulk Editing the Properties of Design Objects” on page 593 for alternative ways to edit
object properties and attributes in Capital Logic Designer, Capital Harness Designer, and
Capital Harness Designer Modular.
If an object’s name was assigned using a name from the project’s Object Type Information in
Capital Project Manager then the object’s short description will be taken from that definition
and will be read-only in the Properties Dialog Box. If you select the Visible check box next to
the Short Description field in the properties dialog box, the short description will be displayed
in the diagram and you can specify its diagram display characteristics in the Edit Name Text
Attributes Dialog Box.

December 2023
Modifying Objects
Procedure
The Properties Dialog Box displays.
2. If required, type the new name of the object in the Name box. If valid names for the
object type have been created in Capital Project Manager, you can select a name by
clicking the ellipsis button (...) to display the Name Selection dialog box.
Note
With the exception of pins, you can rename an object to have the same name as
another object in the same diagram. If you do this, the name is displayed in red and a
warning is displayed when you click the OK button.
If you are editing the properties of a multicore indicator, the multicore name is displayed
in the Name field. If you are editing the properties of a signal in Capital Systems
Integrator, you can edit the name only if the signal is not associated with a functional
source net conductor from the associated Capital Logic Designer design. If a shared
object has been frozen, you cannot change its name.
If you have assigned a library part to the object and usage definitions have been created
for the library part in Capital Project Manager, the Name Selection dialog box lists only
the names that are used in the usage definitions by default. You can display all available
names for the object type by clearing the filter on Usage box at the top of the dialog box.
See the Capital Project Manager help system for more information about usage
definitions.
If you are editing the general properties for a net conductor and it connects to a device
that has a usage definition in Capital Project Manager, the Name Selection dialog box
lists only the names that have been added for the corresponding pin in the usage
definition.
If a net conductor is connected to more than one device with a usage definition, the list
of net names displayed depends on the pin types to which it is connected. The pin types
can be IN, OUT, IxO, IxO Terminated, NC, PWR, and GND. These are defined in
Capital Component Manager. See the Capital Component Manager help system for
more information about defining pin types.
In Capital Symbol Designer, you can specify the pin type “U” that means that no pin
type is specified.
3. Select the Visible check box, if you want the specified name to be displayed with the
object in the diagram.
The name is displayed once for each object. However, in the case of conductors, you can
display the name next to more than one segment of the conductor. If name text has been
added to segments previously and has not been deleted, select the Visible check box to
display the name text for each instance of name text that has been added.

December 2023
Modifying Objects
4. Click the Edit Attributes button to display the Edit Name Text Attributes Dialog
Box, and set graphical attributes for the name that is displayed on the diagram:
5. Click the OK button to exit the Edit Name Text Attributes dialog box, and then click
OK on the Properties dialog box.
Results
The name displays accordingly on the diagram.

You can unassign a library part from an object so that the object no longer has the attributes and
properties from it.
Procedure
2. Click the Remove ( ) button in the Library Part section of the General tab.
3. The details for the library description are removed from the Edit Properties facility.

If a library part is assigned to a design component, and the part is edited in the component
library, you can update one or more components to include the library part edits in the
component properties.
If you select multiple components with different library part numbers assigned, the part details
are updated for all the associated library parts.
• If an update cannot be performed because of conflicts between the updated library part
definition and the component definition, a message is displayed.
• If an update of the library part information invalidates the existing connectivity, the
connectivity is disconnected from the component. For example, if a device with harness
connectors defined in the library part footprint is modified so that the harness connectors
are no longer valid, the harness connectors are disconnected from the device when the
update is performed.
• The Update Part action might be unavailable because of a domain restriction on
associated shared components or library parts. If you require access to this action,
contact your system administrator. See also “Domains” in the Capital Access Manager
User Guide.

December 2023
Modifying Objects
• The Update Part action is not available for fixtures, see “Updating Fixtures” in the
Capital Harness Designer User Guide.
• The Update button ( ) is not available in the edit component dialog boxes in Capital
Harness Designer / Capital Harness Designer Modular.
Procedure
1. Select one or more components on the diagram or in the Design browser, and then
perform one of the following steps:
• Right-click and select Update Part.
• From the Automate ribbon, click the Update dropdown list and select Library Part.
• Press Space Bar and enter Library Part.
Note
In Capital Logic Designer, you can also open the Properties Dialog Box, and click
the Update button ( ) in the Library Part section on the General tab, to update the
library part.
2. In Capital Harness Designer / Capital Harness Designer Modular, the Update Part dialog
box opens:
a. Specify the Preserve Include on BOM attribute option.
o Select to maintain the current setting on the component.
o Clear to overwrite the attribute with the library part setting.
b. Specify the Reset parts to preferred Supplier option.
o Select to update all components in the design with a preferred supplier part
number and details.
o Clear to retain existing supplier details on all components in the design.
c. Specify the Preserve Customer Part Number option.
o Select to preserve the customer part number selected in the design, if it is still in
the part number definition in the library. If the customer part number does not
exist in the definition the process replaces it with the first customer part number
available for that component.
o Clear to replace the selected customer part number for that component with the
first customer part number available.
If a component has one customer part number selected in the design, and an
additional customer part number is defined in the part definition in the library
such that the additional customer part number would become the default, with
this option selected the process will not update the selected customer part

December 2023
Modifying Objects
number on the design, because the customer part number selected in the design
still exists in the part definition.
If a component has one customer part number defined, and that customer part
number is changed in the part definition, the process updates the customer part
number in the design even if this option is selected, as the original customer part
number no longer exists in the part definition.
d. Click Update to confirm or Cancel the action.
Results
• The library part details are updated in the properties dialog box of the components.
• Depending on the component and any changes that have been made to the library part in
Capital Component Manager, the Map Pins Dialog Box might display.
• If the symbol associated to the library part has been modified, the symbol in the diagram
is updated or replaced when you update the library part information. When a symbol has
been replaced, the Map Pins dialog box opens.
Note
You can use the “Invalid library pin mapping” Design Rule Check, to identify invalid
library pin mappings.
Related Topics
Design Rule Checks Applicable to Capital Logic Designer Designs
Performing a Batch Update of Library Parts

You can view the library part that you have assigned to an object so that you can see all of the
attributes and properties for that library part. This is not available in Capital Symbol Designer.
Procedure
2. Click the View ( ) button in the Library Part section of the General tab.
3. The View Component facility is displayed. This is like the Part Selection facility but is
read-only. Click the Close button to exit the facility.

December 2023
Modifying Objects
Converting a Symbol to a Parameterized Object
Converting a Symbol to a Parameterized

Object
In a logical diagram, you can convert a symbol to a parameterized object (a device with pins but
no symbol) so that you can adjust its size and re-distribute the pins.
Procedure
Right-click the symbol and choose Convert to Parameterized.
Results
• The symbol changes to a parameterized device.
• If pins are on the edge of the symbol, they remain in the same locations.
• If a device has harness connectors, they remain mated to the pins in the same location
and will combine into a single instance if there are multiple instances of the same
connectors and they are adjacent to each other. The same applies to device side
connectors.
• If the symbol had pins inside its perimeter, they move to the closest edge of the graphics.
• The system may create some devices larger than the original symbol area because of the
position of the pins on those symbols:
o A symbol with a large number of pins inside its graphic or pins that are overlapping.
o A small symbol that has all of its pins collinear on a single line. This is done to move
the pins to their required positions after the conversion.
• Devices and device pins retain their attributes and properties after the conversion.
• The system applies styling to the device and device pins.
• The system persists any “Set or Remove Home Condition” and “Show or Hide Cross
Reference Text” settings.
• If auto-route is enabled, the system routes any affected conductors automatically.

December 2023
Modifying Objects
Assemblies
Assemblies
An assembly is a collection of objects that you can use as a single entity. It is treated as a design
wide object. It can contain wires, shields, nets, devices, connectors, conductor groups, inline
plugs and inline jacks, and other assemblies. Commercially Off the Shelf (COTS) cables are
also treated as assemblies. COTS cables are purchased in their made-up form containing multi-
conductors with one or more pre-connected connectors. For further information on COTS
cables, see the Capital Component Manager User Guide.
Note
This video illustrates how to work with assemblies.
Adding assemblies from Capital Component Manager automatically populates the design
browser with the correct child parts, improving quality and reducing design time. The part
selection dialog assists in assigning the correct assembly and sub-assembly parts. In addition, if
the assembly contains connectivity information then once the assembly is placed on the diagram
the system auto-routes the conductors defined in the assembly.
You can add comment graphics and comment symbols to a diagram so that those graphics and
symbols are associated with the assembly and form a graphical boundary around it.
Note
An assembly cannot contain shared objects.
This functionality can be used, for example, to create the graphical representation of a panel, a
line replaceable unit (LRU) or Commercially Off the Shelf (COTS) cables.
The topics on assemblies in this section apply to both Capital Logic Designer and Capital
Harness Designer applications, except where noted.

December 2023
Modifying Objects
Adding Assemblies Containing Connectivity
Note
Concurrent editing of assemblies utilizing multi-user access is supported, if enabled (see
Multi-user Access to Capital Logic Designer Designs). Multiple users can simultaneously
edit and create assemblies. Conflicts are very rare, but, under certain circumstances it is possible
for User 2 to select conductors which have previously been added to another assembly by User
1. When this happens any changes carried out by User 2 in the Assemblies dialog are reverted
once User 2 selects OK. A message is displayed in the output window providing information on
the conflict and the Assemblies dialog refreshes so User 2 can restart their editing action.
Adding Assemblies Containing Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614

Adding Associated Comment Graphics or Comment Symbols to an Assembly . . . . . . 615
Adding Objects Within the Associated Comment Graphic Boundary to an Assembly 617
Creating an Assembly from the Part Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . 619
Deleting an Assembly. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 620
Extending the Selection of Objects for an Assembly Comment Graphic or Symbol . . 621
Removing an Object from an Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622
Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Renaming an Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Adding Assemblies Containing Connectivity

Adding assemblies such as COTS cables and sub-circuits that contain connectivity speeds up
design time by enabling rapid diagram creation. It also improves quality by reusing approved
circuitry and helps optimize layouts using assisted placement and ghosted connection lines.
Note
This method of editing an assembly is only available in the Capital Logic Designer
application.
Once assemblies, including COTS cables, that can contain connectivity information are stored
within Capital Component Manager they are available for consumption in designs. The facility
also exists to save assemblies that have had child part content and connectivity changes back
into Capital Component Manager once this has been finalized on a design.

December 2023
Modifying Objects
Adding Associated Comment Graphics or Comment Symbols to an Assembly
This video illustrates how to perform this task.
Prerequisites
• The assembly must exist in Capital Component Manager
Procedure
1. Create an assembly following the process detailed in Creating an Assembly. This
populates the design browser with all defined connectivity objects such as devices,
connectors, splices and so on.
Note
If you have read-write domain access permission you can save the design assembly
changes back into the library assembly by selecting Save Design into Assembly on
the ribbon.
2. Once the assembly is added to the diagram its pre-defined connectivity, including any
highway information is shown by ghosted lines. This enables the optimal placing of
objects and connectivity prior to saving the design. For further information see
Preserving Imported Connectivity and Using Assisted Placement.
3. Save your design.
Adding Associated Comment Graphics or

Comment Symbols to an Assembly
This topic details how to add comment graphics and comment symbols to a diagram so that
those graphics and symbols are associated with the assembly and form a graphical boundary
around it.
Note
application.
This functionality can be used, for example, to create the graphical representation of a panel or
line replaceable unit (LRU).

December 2023
Modifying Objects
Figure 8-3. Example Assembly Graphic
In this example, the box surrounding the diagram objects and the text ASSEMBLY1 are
comment graphics associated with an assembly called ASSEMBLY1. WIRE3 and WIRE5 pass
out of the box to connect with other design objects not in the assembly. The inline jack J1 is part
of the assembly whereas the inline plug P1 is not.
The visible graphical boundary can be any shape but the system creates an invisible rectangle
around the extents of the visible shape. This invisible rectangle represents the boundary for any
actions related to the assembly (such as “Add to Bounded Assembly” and “Remove from
Bounded Assembly”).
Prerequisites
• The assembly must exist.
Procedure
1. In the Design Browser Window, select the assembly in the Assemblies folder and either:
• Right-click and select Associate Graphics followed by the graphic drawing tool that
you want to use.

December 2023
Modifying Objects
Adding Objects Within the Associated Comment Graphic Boundary to an Assembly
• Select the graphic drawing tool from the toolbar.

2. Use the selected tool to add the required graphic or symbol. See “Graphic Drawing
Tools” on page 519 for detailed instructions for each tool.
Related Topics
Assemblies
Creating an Assembly
Removing an Object from an Assembly
Renaming an Assembly
Deleting an Assembly
Assembly
Extending the Selection of Objects for an Assembly Comment Graphic or Symbol
Adding Objects Within the Associated Comment

Graphic Boundary to an Assembly
When you associate comment graphics with an assembly to form a visible, graphical boundary
around it, the system creates an invisible rectangle around the extents of the visible shape.
Note
This method of editing an assembly is only available in Capital Logic Designer.
This topic details how to add diagram objects wholly contained within the invisible boundary to
the assembly.
Prerequisites
• The assembly must exist with the associated comment graphic boundary. See “Creating
an Assembly” on page 618 and “Adding Associated Comment Graphics or Comment
Symbols to an Assembly” on page 615.
• The objects to be added to the assembly must have been added to the diagram within the
invisible boundary.

December 2023
Modifying Objects
Procedure
Select the assembly in the Assemblies folder in the Design Browser or select the visible
graphical boundary in the diagram then either:
• Right-click the selected object and select Assemblies > Add to Bounded
Assembly.
• Press Space Bar and enter Add to Bounded Assembly.
Results
Any diagram objects wholly contained within the invisible boundary are added to the assembly
and appear under it in the Design Browser.
Related Topics
Assemblies
Assembly
This topic details how to create an assembly and specify the design objects that are included in
the assembly.
Procedure
1. Press Space Bar and enter Assemblies.
2. The Edit Assemblies facility is displayed. Click the Create button ( ); the New
Assembly dialog is displayed.
3. If you do want to use a default name for the assembly, leave the Default Name box
selected. Otherwise, clear the Default Name box and enter the assembly name in the
Assembly Name box. Click the OK button.
4. Click the assembly in the Selected box. The Available box contains the objects that can
be added to the assembly. Select the objects that you want the assembly to contain and
click the Add ( ) button. You can leave the assembly empty for later use.

December 2023
Modifying Objects
Creating an Assembly from the Part Selection Dialog
5. Any selected objects are added to the Selected box under the assembly. You can double-
click the assembly name to show or hide the objects in it. Click the OK button.
6. The assembly is added to the Assemblies folder in the Design Browser Window.
Note
In Capital Logic Designer you can right-click the assembly in the Design Browser
Window and select the Extend Selection option from the pop-up menu to highlight
all of the objects in the assembly in the diagram window.
Related Topics
Assemblies
Assembly
Creating an Assembly from the Part Selection

Dialog
You can add pre-defined assemblies, including COTS cables, sub-circuits, and assemblies
containing connectivity from Capital Component Manager into designs. This offers the benefit
of standardization to assemblies as they can be defined and controlled by parts librarians rather
than being created on a case by case basis. Quality is further enhanced by additional structure
match checks using a constraint on the selected assembly, ensuring only valid child parts are
available during assembly creation.
Note
application.
Prerequisites
• The assembly must exist in Capital Component Manager.

December 2023
Modifying Objects
Procedure
1. Access the Part Selection Dialog functionality from the Parts tab on the left of the
application and use the search function to identify the required assembly.
2. Right-click the required assembly and select Create Assembly on the context menu.
The selected assembly is added to the Assembly folder in the Design browser, while its
contents are added to the Unplaced folder of the child object.
3. The assembly can now be placed on the diagram using the Place Dialog Box.
Results
The pre-validated assembly is placed on the diagram, system constraints having ensured that
only valid child parts have been used in the construction of the assembly.
• If the assembly has a part number but it's children do not then the Part Selection Dialog
on the children checks the structure of the assembly and only allows valid children.
• If the assembly does not have a part number but its children do then the Part select
Dialog on the assembly only allows assemblies which contain the children.
This topic details how to delete an assembly.
Procedure
1. Press Space Bar and enter Assemblies; the Edit Assemblies dialog is displayed.
2. Select an assembly in the Selected box and click the Delete ( ) button.
3. The assembly name is deleted and any objects under the assembly move from the
Selected box to the Available box. Any comment graphics or comment symbols
associated with the assembly are deleted.
Related Topics
Assemblies
Assembly

December 2023
Modifying Objects
Editing an Assembly
Editing an Assembly
You can edit an assembly on a harness design.
Note
This method of editing an assembly is only available in the Capital Harness Designer
application.
Procedure
1. Select the assembly to be edited.
2. Right-click the selected assembly in the Harness Design Browser and select Edit
Assembly. The Edit Assembly Dialog Box is displayed.
3. Make any changes required to the component attributes and/or properties.
4. Click OK.
Related Topics
Extending the Selection of Objects for an Assembly

Comment Graphic or Symbol
When you select particular objects in the diagram window, you can extend the selection to
include associated objects. The behavior for comment graphics and symbols associated with an
assembly is slightly different to other objects.
Procedure
1. Select a comment graphic or comment symbol associated with an assembly in the
diagram window and either:
• Right-click a selected object and select Extend Selection
• Press CTRL+E
• Press Space Bar and enter Extend Selection
All graphics and symbols associated with the assembly are selected in the diagram
window.

December 2023
Modifying Objects
2. Perform the action a second time to extend the selection to all diagram instances of the
assembly contents (all design wide objects contained in the assembly).
Related Topics
Assemblies
Assembly

This topic details how to remove a design object from an assembly.
Procedure
2. In the Selected window, expand the assembly containing the object and select the object.
3. Click the Remove ( ) button; the object moves from the Selected box to the Available
box.
4. Click OK.
Related Topics
Assemblies
Assembly

December 2023
Modifying Objects
Removing Objects No Longer Within the

Associated Comment Graphic Boundary from an
Assembly
When you associate comment graphics with an assembly to form a visible, graphical boundary
around it, the system creates an invisible rectangle around the extents of the visible shape.
Note
This method of editing an assembly is only available in Capital Logic Designer.
This topic details how to remove diagram objects no longer wholly contained within the
invisible boundary from the assembly.
Prerequisites
• The assembly must exist with the associated comment graphic boundary. See “Creating
an Assembly” on page 618 and “Adding Associated Comment Graphics or Comment
Symbols to an Assembly” on page 615.
• The objects to be removed from the assembly must not be wholly contained within the
invisible boundary.
Procedure
Select the assembly in the Assemblies folder in the Design Browser or select the visible
graphical boundary in the diagram then either:
• Right-click the selected object and select Assemblies > Remove from Bounded
Assembly.
• Press Space Bar and enter Remove from Bounded Assembly, then select
Home > Assembly > Remove from Bounded Assembly from the Search Ribbon
dropdown list.
Results
Any diagram objects no longer wholly contained within the invisible boundary are removed
from the assembly and are no longer displayed under it in the Design Browser.
Related Topics
Assemblies

December 2023
Modifying Objects

This topic details how to rename an assembly.
Procedure
2. Right-click the assembly name in the Selected box and select Rename from the pop-up
menu; the Edit Assembly dialog is displayed.
3. Ensure that the Default Name box is cleared and enter the new name in the Assembly
Name box. Click the OK button.
Related Topics
Assemblies
Assembly
Updating Assembly Contents

If you change the Capital Harness Designer > Assembly project preferences, you can use the
Update Assembly Contents action to bring the contents of existing assemblies in-line with the
new project preference settings.
See “Project Preferences for Capital Harness Designer and Capital Harness Designer Modular
Designs” on page 135 for more information about project preferences.
Procedure
1. In the Design Browser, either:
• To update only specific assemblies, select those assemblies.

December 2023
Modifying Objects
Updating Assembly Supplements
• To update all assemblies in the design, do not select any assemblies.

2. Press Space Bar and enter Update Assembly Content.
A message displays to advise that “Assembly contents will be reset to match the settings
in Project Preferences > Capital Harness Designer > Assembly”.
3. Click Apply to proceed, or click Cancel.
Results
• The contents of either the selected assemblies, or of all assemblies, are updated to match
the current project preference settings.
Updating Assembly Supplements

If you change the Capital Logic Designer > Assembly project preferences, you can use the
Update Assembly Supplements action to bring the contents of existing assemblies in-line with
the new project preference settings.
See “Project Preferences for Capital Logic Designer Designs” on page 169 for more
information about project preferences.
Procedure
1. In the Design Browser, either:
• To update only specific assemblies, select those assemblies.
• To update all assemblies in the design, do not select any assemblies.
2. Press Space Bar and enter Update Assembly Supplements.
A message displays to advise that “Assembly contents will be reset to match the settings
in Project Preferences > Capital Logic Designer > Assembly”.
3. Click Apply to proceed, or click Cancel.
Results
• The contents of either the selected assemblies, or of all assemblies, are updated to match
the current project preference settings.

December 2023
Modifying Objects
Physical Line Thickness

Any line on a diagram or symbol (for example, a wire graphic, a device graphic or a comment
symbol) can be configured to have a thickness that maps to a physical unit (such as inch, cm or
mm).
This thickness is used when displaying the graphics in the diagram window and is displayed
relative to the grid size. It is also translated to all outputs for printing and exporting diagrams.
Note
See the topics”Setting the Physical Line Thickness for an Electrical Symbol or Border” and
“Setting the Physical Line Thickness for a Comment Symbol” in the Capital Symbol
At the 2020.1 release fine rendering has been enabled in Capital Logic Designer and Capital
Symbol Designer applications. As part of this feature, graphical objects that use very thin
graphics (for example thinner than 0.05mm) will visually appear a little light due to a
transparency factor added to them based on their thickness.
Setting the Default Physical Line Thickness for Comment Graphics. . . . . . . . . . . . . . . 626
Setting the Physical Line Thickness for Graphics in Diagrams . . . . . . . . . . . . . . . . . . . 627
Using a Plugin Interface to Control Physical Line Thickness . . . . . . . . . . . . . . . . . . . . . 628
Setting the Default Physical Line Thickness for

Comment Graphics
By editing project preferences, you can set a default physical line thickness for comment
graphics in Capital Logic Designer, Capital Wiring Integrator and Capital Systems Integrator.
Procedure
1. From a design application, press Space Bar and enter Project Preferences; the Project
Preferences Dialog Box is displayed.
2. Navigate to the Application Name > Comment > Graphics node and select it; the
Thickness field is displayed on the right of the dialog box.
3. Select the unit of measurement from the second dropdown list for the Thickness option;
the first dropdown list changes to a free text field.
4. Specify the physical line thickness and click OK.
Results
When you add comment graphics to a diagram in the appropriate application, their line
thickness matches what you have specified. Zooming in or out maintains the line thickness with
respect to the diagram grid size (for example, the lines become thinner if you zoom out).

December 2023
Modifying Objects
Setting the Physical Line Thickness for Graphics in Diagrams
Related Topics
Setting the Physical Line Thickness for Graphics in

Diagrams
The physical line thickness for graphics in diagrams is defined in styling but can be overridden
for individual instances of lines.
Prerequisites
The diagram must be open in the diagram window.
Procedure
1. In the style set that you are using, ensure that the correct unit for your diagrams has been
specified:
a. Press Space Bar and enter Styles; the Style Sets dialog is displayed.
b. In the browser on the left, select the style set that you are using for the diagram and
specify the Unit. This option specifies the unit of measurement upon which all
numerical distances on a design with this style set applied will be based.
2. Within the style set in the browser on the left, navigate to the object type for which you
want to specify a physical line thickness and select the Graphics node; a Thickness field
is displayed on the right of the dialog (among other fields).
3. In the Thickness field, select Override from the first dropdown list and Physical from
the last dropdown list. The unit that you set for the Unit is displayed next to the Physical
option.
4. In the field that now appears between the dropdown lists, specify the value for the line
thickness. The value can be any floating-point number up to three decimal places.
5. Click OK.
6. Apply the style set change to the diagram. See Applying Styles in the Capital Diagram
Styling User Guide.
Results
• The line thickness for objects of that type updates accordingly. Zooming in or out
maintains the line thickness with respect to the diagram grid size (for example, the lines
become thinner if you zoom out).
• You can override the line thickness for a graphic in a diagram by right-clicking it and
selecting Properties. On the Graphical tab, specify the required Thickness.

December 2023
Modifying Objects
Using a Plugin Interface to Control Physical Line Thickness
Related Topics
Using a Plugin Interface to Control Physical Line

Thickness
You can use a plugin interface to control all of the graphical attributes for an object type,
including the attribute Thickness.
Caution
You can use the plugin to control all attributes for an object type or just a subset of those
attributes. When the plugin controls only a subset, you must configure the other attributes
manually before assigning the plugin (as in the procedure below).
Procedure
1. In the Style Sets dialog, navigate to the style set that you are using in the browser tree on
the left.
2. Within the style set in the browser tree, navigate to the Graphics node for the object
type.
3. Specify the Graphics attributes that are not controlled by the plugin.
4. Create the plugin to set the line thickness of the object type. For information about
developing and using extensibility plugins, see the PluginDevelopment.pdf file, located
in the doc\plugin folder of your Capital installation.
5. Assign the plugin in the Style Sets dialog:
a. Within the style set in the browser tree, navigate to the Graphics node for the object
type.
b. From the Plugin Name dropdown list, select the plugin.
c. Click OK.
6. Apply the style set change to the diagram. See Applying Styles in the Capital Diagram
Styling User Guide.
Results
The line thickness for objects of that type updates accordingly (based on the plugin). Zooming
in or out maintains the line thickness with respect to the diagram grid size (for example, the
lines become thinner if you zoom out).
Related Topics

December 2023
Modifying Objects
Finding and Replacing Property Values, Attribute Values and Symbols
Finding and Replacing Property Values,

Attribute Values and Symbols
Within Capital Logic Designer, you can find and replace attribute values, property values and
symbols across multiple designs and/or diagrams, a build list or an entire project.
Procedure
1. Press Space Bar and enter Find and Replace. Alternatively, you can select an object and
then select the menu option.
2. The Find and Replace dialog box is displayed. Specify the following:
• Scope - select the project, build list, designs or diagrams in which you want to
search. If build lists exist, they are listed above the designs.
3. The filter symbol in the Scope section indicates whether a filter has been set or
not .
If a filter has been set and you do not want to use a filter, click the Clear Filter button.
If you want to set a filter for the search, click the Set Filter button to display the Find
and Replace Filters dialog box, and then specify the following;
• Object Types - select the object types to be included in the search. You can clear the
selection at any point by clicking the Clear Selection button.
Note
If you search for pins, the search results include backshell terminations, if you
search for devices, the search results also include ground devices.
• Revision - specify the design revision in which you want to search. Select the Latest
Revision Only box to only ever search across the latest revision.
• Release Level - from the dropdown list, select either no release level (blank) or a
release level across which you want to search.
• Domain - from the dropdown list, select either no domain (blank) or a domain
across which you want to search.
• Effectivity (only visible if effectivity functionality has been enabled for the project
in Capital Project Manager) - specify the effectivity range within which you want to
search.
Click the OK button to exit the Find and Replace Filters dialog box.
4. In the Find section, you specify for what you are searching and potentially want to
replace. Select the Match Case box if you want the search to be case-sensitive with
regard to the specified values.

December 2023
Modifying Objects
Be aware if you define a regular expression string, this is only applicable to the Find
action, not the Replace action.
You can specify the following:
Note
In the following fields, if you want to search for a special character such as $, ensure
that you type a delimiter (\) before it. For example, \$.
• Object Name - if you want to limit the search to objects with particular names, you
can enter a full name or part of a name using wildcards.
• Attribute/Property - specify the attribute or property name. You can either enter
the name manually or select it from the dropdown list in the field.
• Matches - specify the value of the attribute or property.
If Exact Match is selected, every value string found will be fully replaced by the
content in the replace section.
If Exact Match is cleared, each and every occurrence of the string entered will be
replaced by the content in the replace section. For example, find “AB” and replace
with “C”, results in the renaming of Property=ABDAB with Property=CDC.
If nothing is specified here, the entire value strings of the attribute/property
occurrences found will be replaced by the content in the replace section. For
example, find “” and replace with “C”, results in the renaming of Property=ABDAB
with Property=C.
• Symbol - if you want to search on objects that use a particular symbol only, click the
ellipsis (...) button to display the Symbol Selection dialog box, and then browse the
available symbol libraries to select the symbol. If you select a symbol, it is displayed
in a preview window.
You can click the Clear button to clear the symbol selection.
5. In the Replace section, you can specify the following:

• Attribute/Property - the attribute or property name that you want to replace the
attribute or property names found by the search. You can either enter the name
manually or select it from the dropdown list in the field. The properties listed are
those created at the project level and are not those created on the fly for an instance
of an object. The attributes listed are only those applicable to the specified objects.
• Value - the property value that you want to replace the property values found by the
search.
• Symbol - the symbol that you want to replace the symbols found by the search.
Click the ellipsis (...) button to display the Select Symbol dialog box, and then

December 2023
Modifying Objects
browse the available symbol libraries to select the symbol. If you select a symbol, it
is displayed in a preview window.
You can click the Clear button to clear the symbol selection.
• Update Symbol Only - select to replace only the symbols used for the found objects
and not their attributes or properties. You cannot replace comment symbols or
symbols associated to library parts.
• Preserve Pin Positions
Select for the pins on the symbol instances to remain where they are in the diagram
already.
• Remove Properties Not on Symbol
Select to remove any properties from the symbol instances that are not on the symbol
in the symbol library.
• Copy Attribute/Property Values from Symbol
Select to copy any properties and attributes that are on the symbol in the symbol
library to the symbol instances.
• Preserve Attribute Text
The attribute visibility settings on a diagram instance of a symbol may be different to
the attribute visibility settings on that symbol in the symbol library. If selected, the
attribute visibility settings on the symbol instance in the diagram are retained. If
cleared, the attribute visibility settings on the diagram instance are overwritten by
those on the symbol in the library.
• Preserve Diagram Pin Name
In a diagram, you can rename a pin name on a symbol instance. If selected, the pin
names in the diagram are retained. If cleared, the pin names in the diagram are
replaced by the pin names from the symbol in the symbol library.
6. Click one of the following buttons:
• Find - finds the specified attributes and properties but does not replace any values.
The output window at the bottom of the application displays the found objects on the
Find and Replace tab. You can select an object name to view that object in a
diagram.
• Preview - previews the changes that would be made if you did a replace but does not
change the actual designs. The changes are displayed on the Find and Replace tab of
the output window at the bottom of the application but are not made to the actual
design. You can select an object name to view that object in a diagram.
• Replace - finds and replaces the specified values. This works on editable designs
only. If the replace action affects a shared object, the design is saved automatically.

December 2023
Modifying Objects
This button is dimmed if the Replace section does not contain valid data. The objects
with replaced values are listed on the Find and Replace tab of the output window at
the bottom of the application. You can select an object name to view that object in a
diagram. Some replacement values may be invalid for some of the found objects and
the Find and Replace tab lists these as errors.
7. If you are replacing values, a message states that the operation is undoable and you must
confirm whether you want to proceed. You can check a box so that this message is not
displayed again.
If you are replacing symbols and the replacement symbol has a different number of pins
to the symbol instance, the Map Pins Dialog Box is displayed and you map the pins from
the replacement symbol to pins on the symbol instances. You also specify what data on
the symbol instance you want to preserve and what data you want to remove. After
doing this, click OK.

December 2023
Modifying Objects
Advanced Naming Functionality
Advanced Naming Functionality

Advanced Naming enables the names of objects in logical and Capital Systems Integrator
designs to be automatically generated from a wide range of their design attributes, properties,
locations, related objects, and queries.
Note
You cannot use Advanced Naming in Topology designs.
There are three types of object names:
• Default Names
Default names are names that are generated automatically when an object is created.
Default names are generated according to the Default Naming values specified in
Capital Project Manager. See “Default Object Names” in the Capital Project Manager
User Guide.
• Fixed Names
Fixed names are names that have been set as fixed in the Properties Dialog Box. In the
properties dialog box, you can set a name as fixed by doing one of the following, then
clicking OK:
o Manually editing the Name field.
o Clicking the ellipsis (...) button to the right of the Name field and selecting a name
from a list of pre-specified names maintained in the project’s Object Type
Information in Capital Project Manager.
o Selecting the Fixed check box.
• Generated Names
Generated names are names that are generated based on the naming compositions set up
in the Advanced Naming functionality in Capital Project Manager. Each name
composition has a condition that determines the objects which can be used to generated
names. When a name is being generated, each name composition is tested against the
named object in the order the compositions are defined. The first name composition to
match the object is used to generate a name.

December 2023
Modifying Objects
Generating Names for all Objects in a Build List, Design or Diagram
Note
By default, the names of shared objects are treated as fixed names. When you promote an
object to be shared in Capital Logic Designer:
• If the object has a default or fixed name, the name of the shared object is treated as being
fixed.
• If the object’s name was generated using the advanced naming functionality, you can
specify that you want the name of the shared object to be treated as either fixed or
generated. See “Promoting a Device or Connector”, “Promoting a Splice” or “Promoting
a Multicore or Overbraid” in the Capital Logic Designer User Guide.
When you use the advanced naming functionality, in the Generate Advanced Names Dialog
Box you specify which types of names (default, generated or fixed) you want to replace with
newly generated names. You can generate names for specific selected objects, or generate
names for all objects in a build list, design or diagram.
When you generate names using the advanced naming functionality, different types of condition
entries are used to test the named object. Property and attribute value conditions can be used to
match their value to a fixed string. It may be the case that some objects will not be renamed
when you apply advanced naming to them because they do not match any conditions for the
naming compositions. Design properties can also be included in naming compositions so the
values that you have specified for design properties influence the names that are generated. See
Editing the Information for a Design for more information about specifying design properties.
Note
Device connectors whose names are constrained by a footprint or library part cannot be
renamed using advanced naming.
Generating Names for all Objects in a Build List, Design or Diagram . . . . . . . . . . . . . 634
Generating Names for Selected Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . 635
Generating Names for all Objects in a Build List,

Design or Diagram
You can use the Advanced Naming functionality to generate names for all objects in a build list,
design or diagram. Advanced Naming enables the names of objects in logical and Capital
Systems Integrator designs to be automatically generated from a wide range of their design
attributes, properties, locations, related objects and queries.
Procedure
1. With the appropriate project open, press Space Bar and enter Batch Naming; the
Generate Advanced Names Dialog Box is displayed.

December 2023
Modifying Objects
Generating Names for Selected Objects in a Diagram
2. In the Scope tree, select the build list, design or diagram within which you want to
generate all object names.
3. The objects in these containers already have names and you must select which types of
names you want to replace with newly generated names. In the Replace section, select
each type of name to replace.
Note
Selecting Fixed Names replaces the names of shared objects that are either Fixed or
Generated.
If a selected project, build list, or design contains a shared object, the advanced naming
functionality uses the home instance to generate the name. This matters if an advanced
naming rule is written such that it uses the information specific to the design or the
instance (such as, connected wires, and so on). If there is no home instance, the
advanced naming functionality uses the first shared object instance that it finds.
4. Specify whether you want to Reset Object Indices and/or Reset Counters.
5. Click OK; the dialog closes and the new names for the selected objects are generated.
Related Topics
Generating Names for Selected Objects in a

Diagram
You can use the Advanced Naming functionality to generate names for selected objects in a
diagram. Advanced Naming enables the names of objects in logical and Capital Systems
Integrator designs to be automatically generated from a wide range of their design attributes,
properties, locations, related objects and queries.
Procedure
1. Select the objects for which you want to generate names, right-click one of them and
select Generate Selected Names. Alternatively, select the objects, press Space Bar and
enter Update Selected; the Generate Advanced Names Dialog Box is displayed.
2. The objects already have names and you must select which types of names you want to
replace with newly generated names. In the Replace section, select each type of name to
replace.

December 2023
Modifying Objects
Selecting a Component Part Number in the Part Selection Dialog Box
Note
Selecting Fixed Names replaces the names of shared objects that are either Fixed or
Generated.
For shared objects, advanced names are only generated for home instances. If the home
instance of a shared object is in another design, you can reset the instance on the design
you are working on as the home object, run Generate Selected Names, and then revert
the home condition back on to its original location. See Changing the Home Instances of
an Object or Pin.
3. Specify whether you want to Reset Object Indices and/or Reset Counters.
4. Click OK; the dialog closes and the new names for the selected objects are generated.
Related Topics
Selecting a Component Part Number in the

You use the Part Selection Dialog Box to select one or more component part numbers when
editing a field on another dialog box that requires a component part number to be entered.
Procedure
1. In the Part Selection Dialog Box, enter your search criteria as required and click Search
parts using criteria specified ( ).
The search results are returned in the Parts table.

2. Select the part number that you want to use in the table and click Insert.
The Part Selection dialog box closes and the selected component part definitions are
added to the field that you are editing.

You can perform a batch update of library part information for components based on the Part
Number attribute for each component. The action can update library part information for all
components in the currently active design or in a build list to which the design belongs.

December 2023
Modifying Objects
Note
You can use extensibility plugins to assign part numbers to components, and then use the
batch update functionality to update the association of library parts. For more information
about developing and using extensibility plugins, see the PluginDevelopment.pdf file located in
the doc\plugin folder of your Capital installation.

• In Capital Logic Designer, Capital Harness Designer Modular and Capital Harness
Designer, this action does not update connectors that have a library part marked as a
modular parent.
• In Capital Logic Designer, if a multicore or overbraid has a library part number, all inner
cores must be placed.
Procedure
1. Perform one of the following steps:
• From the Automate ribbon, click the Batch Update dropdown list and select
Library Parts.
• Press Space Bar and enter Library Parts.
The Confirm Batch Of Update Library Parts dialog box opens.
2. If prompted, choose to update library parts in the currently active design or in a build list
to which the design belongs.
3. Specify the Preserve Include on BOM attribute option.
• Select to maintain the current setting on the component.
• Clear to overwrite the attribute with the library part setting.
4. Specify the Reset parts to preferred Supplier option.
• Select to update all components in the design with a preferred supplier part number
and details.
• Clear to retain existing supplier details on all components in the design.
Note
If running the batch update in Capital Logic Designer with the option “Reset parts to
preferred Supplier” cleared, on a design that has a design abstraction assigned with
the “Auto create harness connectors” option selected, the supplier part number and
supplier name of footprint harness connectors are reset to the preferred supplier details.
See also “Design Abstraction” in the Capital Project Manager User Guide.

December 2023
Modifying Objects
5. Specify the Preserve Customer Part Number option:

This option controls how the process retains the previously selected customer part
number in the design when multiple customer part numbers are defined for the same
component and customer in the library.
• Select to preserve the customer part number selected in the design, if it is still in the
part number definition in the library. If the customer part number does not exist in
the definition, the process replaces it with the first customer part number available
for that component.
• Clear to replace the selected customer part number for that component with the first
customer part number available.
If a component has one customer part number selected in the design, and an additional
customer part number is defined in the part definition in the library such that the
additional customer part number would become the default, with this option selected the
process will not update the selected customer part number on the design, because the
customer part number selected in the design still exists in the part definition.
If a component has one customer part number defined, and that customer part number is
changed in the part definition, the process updates the customer part number even if this
option is selected, as the original customer part number no longer exists in the part
definition.
6. Click Update to confirm or Cancel the action.
A status bar displays the progress of the update.
Results
• The Update Library Parts tab in the Output window displays information regarding
which components have been updated. This tab also displays messages regarding any
components that could not be updated. You can click a component name to jump to that
component in the Diagram window.
• If a component has a value specified for its Part Number attribute but does not have a
library part associated, an association to a library part is created for that component.
If its Revision attribute has no value, the update action selects the latest revision of that
library part.
• If a component already has an associated library part, the associated part is not changed
but the library part information is updated for that component where appropriate.

December 2023
Modifying Objects
Slicing Objects
Slicing Objects
Certain objects on diagrams can be sliced, simplifying diagram modifications and making
diagrams easier to understand. The Slice functionality allows you to draw an intersection line
across an applicable object and create a new instance of that object, retaining connectivity and
preserving style. You can use this to quickly partition diagram content then move it to a new
diagram, or to trim oversized devices and connectors.
This functionality is available in Capital Logic Designer, Capital E/E Publisher, Capital
Systems Integrator and Capital Wiring Integrator only.
• In Capital Logic Designer and Capital E/E Publisher: Devices, blocks, connectors and
conductors (including multicores, overbraids and highways) can be sliced.
Note
Conductors can only be sliced if the “Allow slicing of conductors” project
preference is selected.
• In Capital Systems Integrator and Capital Wiring Integrator: Slots and bundles can be
sliced.
• Slices can be vertical or horizontal.
• Slices can not be made directly across pins.
• Inline connectors can not be sliced across just one of the inline halves.
• Slices on devices, slots or connectors must leave at least one pin on each side of the slice
and slices on blocks must leave at least one highway each side of the slice, otherwise the
object will be trimmed to the size of the slice.
This video illustrates how to perform this task.
Navigating Between Sliced Object Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640

Reconnecting a Sliced Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Slice and Move To . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641
Slicing a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Slicing a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 646

December 2023
Modifying Objects
Navigating Between Sliced Object Instances
Slicing Blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 647

Slicing Conductors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648
Slicing Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Slicing Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Slicing to Trim Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654
Navigating Between Sliced Object Instances

There are various ways to navigate quickly between instances of sliced objects. This enables
faster editing.
Prerequisites
• The instances must exist.
Procedure
Perform one of the following procedures.

Highlight instances Select the object name in the Design Browser (Design tab).
The instances highlight in the diagram. If you switch to
another diagram with an instance, it is also highlighted.
Note: If you select an instance in the Design Browser,
only that instance is highlighted in the diagram.
Zoom in to instances in the Right-click the instance in the Design Browser (Design tab)
diagram and choose Zoom Selected. The diagram window zooms in
to that instance and highlights it.
Note: If you select the object name rather than an
instance, the diagram windows zooms in to include all
instances.
Jump to another instance Right-click the instance you are viewing and choose View
from the instance you are Related Items. If there is only one other instance, you jump
viewing to it in the diagram window and it is highlighted. If there are
multiple instances available, you select which instance you
want from a dialog box.
Note: In most applications that include this functionality
you can use the keyboard shortcut X.
In Capital Systems Integrator and Capital Wiring Integrator,
you can use the keyboard shortcut Shift+X.

December 2023
Modifying Objects
Reconnecting a Sliced Bundle

You can reconnect instances of a sliced bundle that are on the same diagram in Capital Systems
Integrator and Capital Wiring Integrator.
Procedure
Right-click on the arrow glyph at a sliced end of a bundle and choose Join Sliced Bundle.
Results
The sliced sections of the bundle reconnect.
Slice and Move To

You can slice multiple objects from a section of a diagram to partition them from other sections
and then move them to a new diagram.
• You cannot use the Move To action to move objects to diagrams in different designs.
In Capital Logic Designer, you can use Cut and Paste to move objects into another
design. See “Cutting and Pasting an Object in a Diagram” in the Capital Logic Designer
User Guide.
Prerequisites
• Diagram contains valid objects that can be sliced.
• Second diagram is available for selection to Move To.
Procedure
1. Press Space Bar and enter Slice.
2. (Optional) Select Shift + Slice to retain the Slice action and enable repeated slices. Press
Escape to return to the standard cursor.
3. The cursor changes to the Slice cursor .
In Example 8-4, the action is used to slice and move the six speakers and their associated
connectivity, from the top right of the diagram to a new diagram.

December 2023
Modifying Objects
Slice and Move To
Figure 8-4. Starting Point
4. Click the diagram to place the slice line.

In Example 8-5, the slice line is made vertically across the conductors.
Figure 8-5. Make the Slice
The Slice is made and the six speakers and their conductors have been separated.
See Example 8-6, cross-references are created for the new instances of the nets.

December 2023
Modifying Objects
Slice and Move To
Figure 8-6. Slice Made
5. Select the objects in Example 8-7, press Space Bar and enter Move To. Choose the
required diagram and click OK.
Figure 8-7. Select Move To
Results
• The selected objects are removed from the original diagram.

December 2023
Modifying Objects
Slice and Move To
Figure 8-8. Objects Removed
• The selected objects are displayed on the required diagram.

Figure 8-9. Selected Objects on New Diagram
Related Topics
Slicing Devices
Slicing Blocks
Slicing Connectors
Slicing Conductors
Slicing to Trim Objects

December 2023
Modifying Objects
Slicing a Bundle
Slicing a Bundle
In Capital Systems Integrator or Capital Wiring Integrator, you slice a bundle to create multiple
instances of it. Instances can remain on the same diagram but you may want multiple instances
to separate harness objects that you want to move to another diagram.The separation is purely
graphical, it does not break any connectivity.
Prerequisites
• A valid bundle on an open diagram.
Procedure
The cursor changes appearance ( ).
2. Click the diagram, drag the cursor over where you want to slice the bundle or bundles,
and click the diagram again.
Results
The bundles split but the connectivity does not break.
The Design Browser (Design tab) displays an Instances folder under the harness for the bundle.
It lists the instances of that harness. You can also expand the node for that particular bundle to
view the different instances of it.
The sliced end of the bundles have an arrowed glyph ( ) to indicate the bundles have been
sliced.
You can drag a sliced end to stretch and move a bundle.
You can move objects on either side of the slice to another diagram.
You can use styling to control whether and how cross-reference text is displayed at a sliced end
for a bundle. You apply this styling to the bundle object in your style set. See Adding a Cross-
Reference Text Decoration in the Capital Diagram Styling User Guide.
If you select a harness or bundle instance on one diagram so that it is highlighted, any instance
of the same bundle or harness will be highlighted automatically when you switch to another
diagram.
Related Topics
Slicing Objects

December 2023
Modifying Objects
Slicing a Slot
Slicing a Slot
In Capital Systems Integrator or Capital Wiring Integrator, you slice a slot to separate harness
objects that you want to move to another diagram, or to create an instance with a subset of the
connectors on it. The separation is purely graphical, it does not break any connectivity.
Each instance represents the entire slot (that is, a device placed in the slot is available in all
instances).
Prerequisites
• A valid slot on an open diagram.
Procedure
The cursor changes appearance ( ).
2. Click once on the diagram, drag the cursor over where you want to slice the slot. You
decide this based on which connectors you want on which instance.
Figure 8-10. Slot Before Slice
3. Click the diagram again.

Results
The slot splits so that each instance has a subset of the connectors. The connectors on each
instance depend on where you sliced the slot.
Figure 8-11. Slot After Split

December 2023
Modifying Objects
Slicing Blocks
You can move the instances separately.

The Design Browser (Design tab) displays an Instance folder under the slot. This lists the
instances of the slot on the different diagrams and shows which connectors are on each instance.
Related Topics
Slicing Objects
Slicing Blocks
You can slice blocks. This action creates a new instance of the block which retains connectivity
and preserves any styling that was applied to the original.
Prerequisites
• Valid block on open diagram
Procedure
Note
Selecting Shift & Slice will enable the cursor to retain the Slice action and allow
repeated slices. Press Escape to return to the standard cursor.
2. The cursor changes to the Slice cursor
3. Click the diagram to place the first end of the slice line.
4. Place the second end of the line by clicking at the desired location. In the figure below,
the slice line is made horizontally across device BLOCK200, between highways
HW101 and HW102.
Figure 8-12. Slice Block
Results
• The block is split as in the figure below.

December 2023
Modifying Objects
Slicing Conductors
Figure 8-13. Block Slice Complete
• The blocks can be selected and moved apart as in the figure below.
Figure 8-14. Separate Blocks
Related Topics
Slicing Connectors
Slicing Conductors
Slice and Move To
Slicing Conductors
You can slice conductors. This action creates a new instance of the conductor which retains
connectivity and preserves any styling that was applied to the original.
Note
Conductors can only be sliced if the “Allow slicing of conductors” project preference is
selected. See “Project Preferences for Capital Logic Designer Designs” on page 169.
Prerequisites
• Valid conductors on open diagram

December 2023
Modifying Objects
Slicing Conductors
Procedure
Note
the slice line is made vertically across conductors 001, 002, and 003.
Figure 8-15. Slice Conductors
Results
• The conductors are sliced and display with appropriate cross-references. See the figure
below
Figure 8-16. Slice Complete

December 2023
Modifying Objects
Slicing Connectors
Related Topics
Slicing Devices
Slicing Blocks
Slicing Connectors
Slice and Move To
Slicing Connectors
You can slice connectors. This action creates a new instance of the connector which retains
Prerequisites
• Valid connector on open diagram
Procedure
Note
the slice line is made horizontally across the connector Conn1, between Wire 002 and
Wire 003.
Figure 8-17. Slicing a Connector

December 2023
Modifying Objects
Slicing Connectors
Results
• The connector is split as in the figure below.
Figure 8-18. Connector Slice Complete
• The connectors can be selected and moved apart as in the figure below.
Figure 8-19. Separate Connectors
Examples
You can also slice connectors that are mated to devices, without having to slice the device or
any other mated connectors, as shown in the figures below.

December 2023
Modifying Objects
Slicing Connectors
Figure 8-20. Slicing a Mated Connector
Figure 8-21. Sliced Mated Connector
Related Topics
Slicing Devices
Slicing Blocks
Slicing Conductors
Slice and Move To

December 2023
Modifying Objects
Slicing Devices
Slicing Devices
You can slice devices. This action creates a new instance of the device which retains
Prerequisites
• Valid device on open diagram
Procedure
Note
the slice line is made horizontally across device DEV305, between conductors
COND114 and COND115.
Figure 8-22. Slice Device
Results
• The device is split as in the figure below.

December 2023
Modifying Objects
Figure 8-23. Device Slice Complete
• The devices can be selected and moved apart as in the figure below.
Figure 8-24. Separate Devices
Related Topics
Slicing Blocks
Slicing Connectors
Slicing Conductors
Slice and Move To

You can slice oversized objects, such as connectors and devices, to trim down their size.
Prerequisites
• Valid object to be trimmed exists on the diagram. In this example a device is used.
Procedure

December 2023
Modifying Objects
Note
4. Place the second end of the line by clicking at the desired location. In Example 8-25
below, the slice line is made horizontally across the device below conductor 003.
Figure 8-25. Make the Slice Device
Results
• Because there were no pins on either side of the slice line, the device is trimmed to the
size of the slice. See Example 8-26 below.
Figure 8-26. Trimmed Device
Related Topics
Slicing Devices
Slicing Blocks
Slicing Conductors

December 2023
Modifying Objects
Slicing Connectors
Slice and Move To

December 2023
Modifying Objects
Design Logs
Design Logs
There are multiple processes that generate a design log file, which details the results of the
process, as well as any warnings or errors that may have occurred.
By inspecting these logs, you can investigate the causes of any problems encountered.
• Change Manager Bridge Operations

• Harness Engineering
• Module Breakdown
• Generate SBOM
• SBOM Part Number Generation
• Cost Generation
• Design Rule Checks
• Apply stored ECO Changes
• Workbook Generation
• Tape quantity calculation
Opening Design Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Viewing Design Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
Opening Design Logs

Once a process activity is completed, you can review the design logs generated by opening them
in the Output Window.
Prerequisites
• Valid logs are available. See Design Logs.
Procedure
1. Open the relevant design.
2. Click Workflow > Design Log > Open from the ribbon.
The Open Design Logs dialog box displays (see View Design Logs Dialog Box).
3. In the Log column, double-click the log you want to open, alternatively select the
required log, and click the Preview button.

December 2023
Modifying Objects
Parameterized Object
Note
If you are viewing the logs for a composite harness, you can expand the log structure
(by clicking the plus [+] symbols) until the logs for any derivative, functional
module, or production module child are displayed.
Results
The log opens in the Output Window, this allows you to review the log and interact with the
open design.
Parameterized Object
Parameterized objects are design objects that have no symbols and their graphics are controlled
by a configuration file. Some examples of parameterized objects are devices, connectors,
splices, and slots.
Viewing Design Logs

Once a process activity is completed, you can review the design logs generated by opening them
in the Design Log Viewer dialog box.
Prerequisites
• Valid logs are available. See Design Logs.
Procedure
1. Open the relevant design.
2. Press Space Bar and enter View Design Log.
The View Design Logs Dialog Box is displayed.
3. In the Log column, double-click the log you want to view, alternatively select the
required log, and click the View button.
Note
If you are viewing the logs for a composite harness, you can expand the log structure
(by clicking the plus [+] symbols) until the logs for any derivative, functional
module, or production module child are displayed.
Results
• The Design Log Viewer Dialog Box opens, displaying the contents of the log.
• You can repeat step 3 to open multiple Design Log Viewer Dialog boxes
simultaneously.

December 2023
Modifying Objects
Viewing Design Logs
• All filtering controls on the View Design Logs dialog box remain active when Design
Log Viewer dialog box(es) are open.
• You are able to keep the viewer dialog box open and interact with the design.
o However, if you invoke any action that creates a log file, all open viewers are
automatically closed. See “Design Logs” on page 657 for details of such actions.
Related Topics
View Design Logs Help
Design Log Viewer Help
Design Log Event Filter Options Help
Design Log Filter Options Help

December 2023
Modifying Objects
Viewing Design Logs

December 2023
Chapter 9
Printing
This section details the options available in configuring how diagrams are output to printing
devices, including diagram scaling and the configuration and selection of print regions.
The following topics are available:
Print to a Printer or Plotter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662

Printing Selected Diagrams in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Printing All Diagrams in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
Print Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668
Resizing a Print Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Editing a Print Region. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
Locking a Print Region in Position. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Deleting a Print Region. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
Print to a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Printing To File - All Diagrams in a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673
Printing To File - All Diagrams in a Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
SVG Page Settings Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679
Display Width and Display Height . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682

December 2023
Printing
Print to a Printer or Plotter

This section contains details about how to select one or more diagrams to be sent to a printer or
plotter, either installed on the local machine or available on the network.
Printing Selected Diagrams in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Printing All Diagrams in a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 664
Printing a Single Diagram

You can print the currently open diagram at any time.
Procedure
1. In the menu, with the diagram open, press Space Bar and enter Print. The Print Dialog
Box appears.
2. Select Diagram from the Print dropdown list.
3. Specify the printing device to which the print is to be sent by selecting the device from
the Printer dropdown list.
4. Select one of the following options from the Scaling dropdown list:
• Fit to Paper — This option specifies that the diagram should be printed to fit on a
single sheet of paper, of a size specified in the Page Setup dialog for the selected
printing device. The diagram will be resized as needed to fit.
• Print to Scale — This option specifies that the diagram should be printed at 100%
size, as dictated by the design’s grid spacing value (as specified in the currently
applied style set; see the Diagram Styling User Guide for more information).
Alternatively, the diagram can be printed larger or smaller by specifying a new
percentage value, either by overwriting the value in the field to the right, or by
clicking the up and down arrow buttons.
5. Select the Clip To Border check box to print only the diagram elements falling within
the border outline. Cleared, all harness elements will be printed, including those placed
outside of the border.
6. Select the Black/White Only check box to generate prints using only black lines/text
against a white background, regardless of the specified text/line colors in use in a
diagram. Cleared, prints will be generated in color.
7. Specify a Dash Multiplier setting to stretch or shrink dashes relative to the size of output
page.

December 2023
Printing
Printing Selected Diagrams in a Project
8. Click OK. The diagram is sent to the specified printer.

Related Topics
Printing All Diagrams in a Project
Printing All Diagrams in a Design
Printing Selected Print Regions

You can print the currently selected designs and diagrams or build list in the Project Browser.
Prerequisites
If you want to print all diagrams in a build list (by selecting the build list), set the build list to
active.
Procedure
1. With the designs and diagrams selected in the Project Browser, press Space Bar and
enter Print. The Print Dialog Box is displayed.
Note
If you select a block of diagrams, the diagrams are printed in the order in which they
are listed in the project tree. If you select individual diagrams, the diagrams are
printed in the order in which they were selected.
2. Select Selection from the Print dropdown list.

3. Click the Configure button to the right of the Print field. The Project Diagram Settings
Dialog Box is displayed, to refine the selection of diagrams to print before clicking OK.

December 2023
Printing
page.
9. Click OK. The selection of diagrams are sent to the specified printer.
Related Topics

You can print all diagrams belonging to the currently open project.
Procedure
1. With the project open, press Space Bar and enter Print. The Print Dialog Box is
displayed.
2. Select Project from the Print dropdown list.
3. Click the Configure button to the right of the Print field. The Project Diagram Settings
Dialog Box is displayed, to refine the selection of diagrams to print before clicking OK.

December 2023
Printing
page.
9. Click OK. The diagrams are sent to the specified printer.
Related Topics

You can print all diagrams belonging to the currently open design.
Procedure
1. Open any diagram belonging to the design for which you want to print all diagrams.
2. Press Space Bar and enter Print. The Print Dialog Box is displayed.
3. Select Design from the Print dropdown list.

December 2023
Printing
page.
Related Topics

You can print sections of a design by selecting one or more Print Regions to be printed.
Procedure
1. With the diagram open, press Space Bar and enter Print. The Print Dialog Box is
displayed.
2. Select Print Region from the Print dropdown list.
3. Click the Configure button to the right of the Print field. The Edit Print Region Groups
4. Select the Active option for each print region to be included in the print, and then click
OK.

December 2023
Printing

page.
Related Topics

December 2023
Printing
Print Regions
Print Regions
This section contains information about how to add print regions to a design, with additional
topics on resizing, moving, locking in position and editing print regions once created.
You can create print regions within a border symbol, which is added to a design as the border is
selected.
You can create one or more print regions for comment symbols that contain connector and
splice information on a harness diagram.
Topics detailing the creation and maintenance of border and comment symbol print regions are
available in the Capital Symbol Designer User Guide.
Note
The Update Print Regions action on the Home ribbon is only enabled under certain
configurations. Contact GCSS Support for further details.

Resizing a Print Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Editing a Print Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670
Locking a Print Region in Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Deleting a Print Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
Adding a Print Region to a Design

You can create one or more print regions by drawing directly onto a design.
Procedure
1. Press Space Bar and enter Add print region. The cursor changes to .
2. Click to place the first corner of the print region, and then drag out a rectangle until the
region is of the required size.
3. Click to confirm the placement of the print region.
Note
Multiple print regions can be placed without reselecting the Add Print Region tool.
Once a print region has been placed, single-clicking again will place the first corner
of a new print region.

December 2023
Printing
Resizing a Print Region
4. Double-click or press Enter to finish. The Edit Print Region Groups Dialog Box is
displayed.
5. Either accept the default Print Region Name offered, or enter your own.
6. By default, print regions are set to Active and the Visible setting is cleared; change these
settings if required.
7. Click OK.
Results
The print region is placed onto the design.The following print region entities are displayed:
• The print region outline
• The print region name
Related Topics
Moving a Print Region
Editing a Print Region
Deleting a Print Region

You can increase or decrease the size of a print region on a design at any time.
Note
Print regions configured against the border applied to the design can only be resized by
editing the border symbol in Capital Symbol Designer. See also, Editing a Print Region in
the Capital Symbol Designer User Guide.
Procedure
1. Either:
• Hover the cursor over the print region outline
or
• Click the print region outline to select it
2. The gray boxes identifying the draggable corners are displayed.
3. Click one of the gray boxes and drag until the outline is of the required size.
Related Topics

December 2023
Printing


You can reposition a print region on a design at any time.
Note
Print regions configured against the border applied to the design can only be moved by
editing the border symbol in Capital Symbol Designer. See also, Editing a Print Region in
the Capital Symbol Designer User Guide.
Procedure
1. Click any edge of the print region outline (not on the corners).
2. Drag the print region to the new location and release the mouse button.
Note
Begin dragging as soon as you click the print region outline; if you wait too long
before starting to drag, the Panning Tool will activate.
Related Topics

You can change the name and behavior of a print region on a design.
Procedure
1. Press Space Bar and enter Print Region Settings. The Edit Print Region Groups Dialog
Box is displayed.
2. Make any changes required before clicking OK.

December 2023
Printing
Locking a Print Region in Position
Note
Print regions configured against the border applied to the design can only be
renamed by editing the border symbol in Capital Symbol Designer. See Editing a
Print Region in the Capital Symbol Designer User Guide. However the Active and
Visible status can be amended within the design.
Related Topics
Locking a Print Region in Position

This functionality enables technical authors to lock print regions in position to prevent
unintentional changes when working on diagrams.
Diagrams, whether created manually, or generated by rule-based layout plugins may contain
several print regions, placed side by side to ensure the diagrams are ready for printing. These
print regions can sometimes be inadvertently selected and changed during diagram
manipulation and may get displaced from their position. This can then require manual
intervention by authors to re-position them again to ensure the diagrams can be printed
correctly.
A design rule check is also provided to ensure consistency and adherence to your organization’s
standards regarding print regions.
Prerequisites
• Print regions are created on the diagram.
Procedure
To lock print regions in position, or unlock the setting do one of the following:
• Press Space Bar and enter Lock Print Regions/Unlock All Print Regions.
• Right-click the print region boundary and select Lock or Unlock from the context
menu.
• Use a keyboard shortcut:
o Lock : Alt+Shift+L
o Unlock : Alt+Shift+U

December 2023
Printing
• Access the Edit Print Region Groups Dialog Box and select the print regions you
wish to lock individually, or all at once.
Results
Locked print regions are highlighted by grey dashed lines. When locked the print region cannot
be selected, moved, resized or deleted.
Unlocked print regions are highlighted in green. A design rule check is provided to report on
unlocked print regions. For further information see Capital Logic Designer - Appearance DRCs.
Note
The Lock print regions functionality is applicable only in design applications and print
regions of group "Manual". Print regions placed using style sets or borders cannot be locked
or unlocked.

You can remove a print region from a design when you no longer want to use it.
Note
Print regions configured against the border applied to the design can only be deleted from
the border symbol in Capital Symbol Designer
Procedure
1. Select the print region to be deleted.
2. Either:
• Press Space Bar and enter Delete
• Right-click and select Delete
• Press the Delete key
Results
The print region is removed from the design.
Related Topics

December 2023
Printing
Print to a File
Print to a File
This section contains information about how to export the design data from one or more
diagrams to either PDF, DXF, CGM, or SVG format.
Note
Graphics for device pins, connector pins and so on, are not displayed while exporting wiring
diagrams as PDF, DXF, CGM and SVG. You can indicate the presence of pins using
styleset decorations such as “Pin Name."
Printing To File - All Diagrams in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673

Printing To File - All Diagrams in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
Printing To File - All Diagrams in a Project

You can export all the diagrams in the currently open Project to PDF, DXF, CGM, or SVG
format.
Procedure
1. Press Space Bar and enter Print to File. The Print to File Dialog Box is displayed.
2. From the Export dropdown list, select Project.
3. Click the Configure button to the right of the Export field. The Project Diagram
Settings Dialog Box is displayed, to refine the selection of diagrams to print before
clicking OK.
4. Select the Format in which the data should be exported. Available formats are PDF,
DXF, CGM, or SVG.
Note
If you select PDF, DXF, CGM, or SVG in the Format field, the Configure button to
the right of the field is enabled to open either the PDF Page Settings Dialog Box, the
DXF Page Settings Dialog Box, the CGM Page Settings Dialog Box, or the SVG Page
Settings Dialog Box, to configure a number of PDF, DXF, CGM, or SVG specific
generation parameters.
5. Either:
• Accept the default Filename of {Diagram}, in which case the data files created will
be named based on the diagram name appended with the file extension appropriate
to the selected export Format.

December 2023
Printing
Printing To File - All Diagrams in a Design
• Click the ellipsis (...) button to the right of the Filename field, to display the Edit File
Name Dialog Box and configure a new file name template.
6. Click the ellipsis (...) button to the right of the Location field, and use the file browser
dialog to navigate to the directory in which the exported data file(s) should be placed.
7. Click OK.
Results
The design data is exported and the generated file(s) placed in the specified location.
Note
Graphics for device pins, connector pins and so on are not displayed while exporting wiring
diagrams as SVG, PDF and CGM. You can indicate the presence of pins using styleset
decorations such as “Pin Name."
Related Topics
Printing To File - Single Diagram
Printing To File - Selected Diagrams
Printing To File - Print Regions

You can export all the diagrams in the currently open Design to PDF, DXF, CGM or SVG
format.
Procedure
2. From the Export dropdown list, select Design.
DXF, CGM or SVG.
Note
Settings Dialog Box, to configure the PDF, DXF, CGM, or SVG specific generation
parameters.

December 2023
Printing
4. Either:
6. Click OK.
Results
Related Topics

You can export the design data from a single diagram to PDF, DXF, CGM, or SVG format.
Procedure
2. From the Export dropdown list, select Diagram.
DXF, CGM, or SVG.
Note
Settings Dialog Box, to the PDF, DXF, CGM, or SVG specific generation parameters.
4. Either:

December 2023
Printing
6. Click OK.
Results
Related Topics

You can export the currently selected designs and diagrams or build list in the Project Browser
to PDF, DXF, CGM, or SVG format.
Prerequisites
If you want to print all diagrams in a build list (by selecting the build list), set the build list to
active.
Procedure
1. With the designs and diagrams or build list selected in the Project Browser, press Space
Bar and enter Print to File. The Print to File Dialog Box is displayed.
Note
If you select a block of diagrams, the diagrams are printed in the order in which they
are listed in the project tree. If you select individual diagrams, the diagrams are
printed in the order in which they were selected.
2. From the Export dropdown list, select the Selection option.

3. Click the Configure button to the right of the Export field. The Project Diagram
Settings Dialog Box is displayed, to refine the selection of diagrams to print before
clicking OK.
DXF, CGM, or SVG.

December 2023
Printing
Note
Settings Dialog Box, to configure the PDF, DXF, CGM, or SVG specific generation
parameters.
5. Either:
7. Click OK.
Results
Related Topics

You can export active Print Regions in the diagram currently open to PDF, DXF, CGM format.
Print Regions can not be exported to SVG format.
Procedure
1. With a diagram open that has active print regions, press Space Bar and enter Print to
File. The Print to File Dialog Box is displayed.
2. From the Export dropdown list, select Print Regions.
3. Click the Configure button to the right of the Export field. The Edit Print Region
Groups Dialog Box is displayed.
4. Select the Active check box for each print region to be exported, and then click OK.

December 2023
Printing
DXF or CGM.
Note
If you select PDF, DXF, or CGM in the Format field, the Configure button to the
right of the field is enabled to open either the PDF Page Settings Dialog Box, the
DXF Page Settings Dialog Box, or the CGM Page Settings Dialog Box, to configure the
PDF, DXF, or CGM specific generation parameters.
6. Either:
8. Click OK.
Results
Related Topics

December 2023
Printing
SVG Page Settings Examples
SVG Page Settings Examples

As source diagrams in Capital Design Tools can differ in size, scale, detail and complexity, the
settings used to generate SVG diagrams may need to be adjusted to create accurate rendering.
The SVG Page Settings Dialog Box contains multiple settings to adjust the rendering when
generating SVG files using Print to File.
Note
It may be necessary to adjust a combination of the Page Settings to achieve accurate
rendering.
The following examples detail each of the available settings, explaining why they may be used
and show the effects that changing the settings have on the final output SVG file. Some
examples have used exaggerated settings to emphasize the effects of the changes.

Display Width and Display Height. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682
Line Thickness Scale Factor

The system uses this setting when generating SVG diagrams. It applies a percentage increase or
decrease to the thickness of any lines on the output SVG.
It can be used when the display of lines on an output SVG file is considered too faint or too
bold. See also “Minimum Line Width” on page 680 for other line width controls.
Example 9-1 below shows an SVG that has been created with the Line Thickness Scale Factor
set to 0.7. The lines appear faint.

December 2023
Printing
Minimum Line Width
Figure 9-1. Before Factor Increase
By increasing the Line Thickness Scale Factor to 2.0 and regenerating the SVG from the same
source diagram, the output file displays as in Example 9-2 below.
Figure 9-2. After Factor Increase
Minimum Line Width

The system uses this setting when generating SVG diagrams. Specified in pixel width, it
automatically applies a minimum line width to all lines in generated SVG files. It can be used to
ensure that a minimum line width is applied as a default across any SVG renderings.

December 2023
Printing
Minimum Line Width
See also “Line Thickness Scale Factor” on page 679 on page 255 for other line width controls
Example 9-3 below shows a set of differing width lines drawn in a design tool.
Figure 9-3. Source Design
Example 9-4 below shows a section of an SVG that has been created from the above source
diagram, with the Minimum Line Width set to 30 pixels. All the lines have a line width of 30
pixels or more so the Minimum Line Width has not been applied and the rendering is as in the
source diagram.
Figure 9-4. First Minimum Width Increase
By increasing the Minimum Line Width to 180 pixels and regenerating the SVG from the same
source diagram, the output file displays as in Example 9-5 below. The Minimum Line Width
has been applied and has had the effect of rendering all the lines at a minimum width of 180
pixels.
Figure 9-5. Second Minimum Width Increase

December 2023
Printing
Display Width and Display Height
Display Width and Display Height

As the size of source diagrams can vary, it may be necessary to change the display size of output
SVG to give accurate display detail. You can specify the pixel width / height in the Display
Width and Display Height settings, to modify the display size of any output SVG.
Example 9-6 below shows a section of an SVG, created with Display Width and Display Height
set to 1024 x 768, that is zoomed in to its maximum. The cavity details on the connector symbol
are difficult to read.
Figure 9-6. Insufficient Detail
By increasing the Default Width and Default Height setting to 5000 x 4000, and regenerating
the SVG from the same source diagram, a much larger SVG is created and the maximum zoom
now displays the same object in more detail see Example 9-7 below.

December 2023
Printing
Line Pattern Scale Factor
Figure 9-7. More Detail

The system uses this setting when generating SVG diagrams. As the size of source diagrams can
vary, it may be necessary to amend the way that linestyles (doted or dashed) are rendered on any
generated SVG to ensure than are consistent with the source.

December 2023
Printing
The Line Pattern Scale Factor setting applies a percentage increase/decrease to spacing of any
lines styles on the output SVG to ensure an accurate and consistent rendering.
Example 9-8 below shows a source diagram linestyle.
Figure 9-8. Source Diagram Linestyle
Example 9-9 below, shows the same linestyle, rendered on an SVG that has been created with
the Line Pattern Scale Factor set to 2.0. The linestyle spacing has not been maintained
Figure 9-9. Inconsistent Linestyle
By decreasing the Line Pattern Scale Factor to 0.5 and regenerating the SVG from the same
source diagram, the linestyle renders as a more accurate representation of the original source
diagram. See Example 9-10 below.
Figure 9-10. Correctly Rendered Linestyle
Tip
For advanced users ONLY. If diagrams require further alterations to render correctly, you
can access the <install_directory>\config\cgmprops.xml and change the linePattern setting
value to 0.5 rather than the default which is 1.0, to assist the correct output of dotted lines.

December 2023
Printing
Fill Pattern Scale Factor

The system uses this setting when generating SVG diagrams. As the size of source diagrams can
vary, it may be necessary to amend the way that fill patterns are rendered on any generated SVG
to ensure than are consistent with the source.
The Fill Pattern Scale Factor setting applies a percentage increase/decrease to spacing of any fill
patterns on the output SVG to ensure an accurate and consistent rendering.
Example 9-11 below shows a source diagram fill pattern.
Figure 9-11. Source Diagram Fill Pattern
Example 9-12 below, shows the same fill pattern, rendered on an SVG that has been created
with the Fill Pattern Scale Factor set to 2.0. The linestyle spacing has not been maintained
Figure 9-12. Inconsistent Fill Pattern
By decreasing the Fill Pattern Scale Factor to 0.5 and regenerating the SVG from the same
source diagram, the fill pattern renders as a more accurate representation of the original source
diagram. See Example 9-13 below.

December 2023
Printing
Figure 9-13. Correctly Rendered Fill Pattern
Related Topics

December 2023
Chapter 10
Collaborate
This section contains information about using the Collaborate functionality, including
comments, notes, checklists, and managing notifications.
Introduction to Collaborate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 687
Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 690
Checklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691
Notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694
Viewing Comments, Notes and Checklists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696
Creating a Comment, Note or Checklist Item. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 697
Modifying a Comment, Note, or Checklist Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699
Replying to a Comment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
Managing Collaborate Data in a Project or Design Action . . . . . . . . . . . . . . . . . . . . . . . 702
Introduction to Collaborate
Collaborate is functionality that enables users of Capital design tools to annotate designs and
diagrams. Information in these annotations help users work collaboratively by enabling
designers to communicate within the design tool itself.
Collaborate content takes four main forms:
• Comments
• Notes
• Checklist items
• Requirement Links - for further information see Using Requirements Linking.
In addition to the above content, a notification management system is provided that allows user
accounts to be associated with, or tagged in, Collaborate content. Users receive automated
notification by email about any Collaborate design content they are associated with or are newly
tagged in. A user can set their Collaborate contact email or profile picture in the Capital Access
Manager application, see “Creating and Editing a User Account” in the Capital Access
Manager User Guide.

December 2023
Collaborate
Comments
Collaborate content is found on tabs in the Output Window (below the main Diagram Window).
See “Viewing Comments, Notes and Checklists” on page 696 for topics related to viewing
Collaborate content.
As Collaborate is a collaborative feature, with users often working remotely, refresh content at
any time to ensure the latest comments, notes and checklist items are visible. See “Viewing
Comments, Notes and Checklists” on page 696.
Any Collaborate content you create is associated with the currently active design at the time of
creation. Collaborate data can only be transferred when copying a design, creating a revision, or
exporting a project/design. See the System Preferences for Collaborate section of “System
Preferences Dialog Box” in the Capital Project Manager User Guide for the default settings
related to these actions.
Note
All Collaborate data is available using the Capital Extensibility API and can be used by
extensibility plugins. Examples provided with the Capital installation illustrate the
following topics:
• Creation of all Collaborate objects driven by customer-specific flows.

• Access to Collaborate data, for example, using Export of Checklist to CSV file.
For information about developing and using extensibility plugins, see the
PluginDevelopment.pdf file, located in the doc\plugin folder of your Capital installation, with
examples in doc\plugin\examples\Java\src\com\example\plugin\action\collaboration
Related Topics
Comments
Checklist
Notes
Notifications
Comments
A comment is an annotation used to convey information related to the current design or diagram
during the design phase.
Comments allow designers to communicate at the point of diagram creation to ensure design
requirements and standards are met. For example, a comment could contain a question, answer,
or action that needs to be completed.

December 2023
Collaborate
Comments
Figure 10-1. An Example Collaborate Comment
You create comments with the Collaborate Editor Dialog Box. When created, comments are
associated with the design of the currently active diagram. The Collaborate editor enables
standard HTML formatted content containing text, images, and links to be created. It also
enables you to associate objects placed on any diagram of the active design with the comment.
Associated objects appear as hyperlinks within a comment and bring the object into focus on the
diagram when clicked.
User accounts with domain access to the current design/project can be referenced, or tagged, in
a comment using the Collaborate Editor dialog box. When you tag a user they receive a
notification email about a comment they are tagged in. See “Notifications” on page 694 for
more details.
Any existing comment can be replied to, thereby creating a chain of comments and enabling a
thread of discussion. Replies always appear nested under the parent comment.
Tracking Comments
Comments can be tracked to ensure all content is seen and resolved by design stakeholders.
Once created, a comment must be marked as resolved to ensure the design passes a DRC check.
DRC checking for unresolved comments is found under the consistency check category. See
“Running Design Rule Checks” on page 247 for more details.
You can reopen a comment at any time once it has been resolved. Replies do not have a
resolved status.
Note
The ability to resolve comments is a licensed feature and is only available if you have a
valid Capital Team Collaborator license and the correct user permissions. Details of
Collaborate user account permissions can be found in the “Permissions” section the Capital

December 2023
Collaborate
Notes
Related Topics
Creating a Comment, Note or Checklist Item
Modifying a Comment, Note, or Checklist Item
Viewing Comments, Notes and Checklists
Replying to a Comment
Comments Tab
Notes
A note is an annotation used to capture additional helpful information about a design, and if
required visualize that information on a diagram.
Notes let you associate additional information and manufacturing details with a diagram. For
example, a note could contain and include instructions on design navigation, or why a certain
design decision was made.
Figure 10-2. Example Collaborate Note
Notes are created using the Collaborate Editor Dialog Box and are associated with the active
design. Each note has a unique note name field which can be set in the editor. The editor enables
standard HTML formatted content containing text, images, and links to be created in the note. It
also enables you to associate objects from any diagram in the active design with the note.
Associated objects appear as hyperlinks within a note and bring the object into focus on the
diagram when clicked.
Notes can only be added to a design that is editable, you cannot create notes on read-only
designs.
Notes can be displayed on the diagram using styling capabilities. Any diagram notes appear
within a table displayed on the diagram. To display a note table please see “Adding a Table
Decoration” in the Capital Diagram Styling User Guide.

December 2023
Collaborate
Checklist
Note
On a diagram any object that has an association with a note can have the note name
displayed next to the object using a decoration query result under style sets. See “Using
Query Result Decorations” in the Capital Diagram Styling User Guide, choosing the
CollaborateNoteResult option in the Query Result Name attribute.
Related Topics
Notes Tab
Checklist
A checklist item is an annotation used to capture a task or design check that needs to be
completed.
A checklist lets you manage and track multiple required design actions for a design. For
example, this could include ensuring all devices of the same type are properly aligned, or that all
signals have a required naming standard.

December 2023
Collaborate
Checklist
Figure 10-3. Example Collaborate Checklist Items
Checklist items are created using the Collaborate Editor Dialog Box and are automatically
associated with the active design. The editor enables standard HTML formatted content
containing text, images, and links to be created in the checklist item. Each checklist item has a
visible status button to indicate if the task has been completed ( )
Tracking Checklist Items

Checklist items can be tracked to ensure all items are completed and marked as resolved. Once
created, a checklist item must have its status changed to resolved to ensure the design passes a
DRC check. DRC checking for unresolved checklist items is found under the consistency check
category. Please see “Running Design Rule Checks” on page 247 for more details.
A checklist item can be reopened at any time once it has been resolved.
Note
Checklist is a licensed feature and will only be available if you have a valid Capital Team
Collaborator license. The ability to create, edit, or resolve checklist items is only available
to users with valid Collaborate user account permissions. Details of Collaborate user account
permissions can be found in the “Permissions” section the Capital Access Manager User Guide.
Related Topics

December 2023
Collaborate
Checklist

Checklist Tab

December 2023
Collaborate
Notifications
Notifications
Notifications enable users to be directly associated with Collaborate content. Associated users
are included in an email-based feedback system.
You can receive notification emails from the Collaborate notification management system in
two ways:
• Notify Me
Turning on this mode allows you to receive updates by email about any new Collaborate
content created for a desired design. You also receive a daily activity report email, detailing
all Collaborate content for that design.
• User Tagging
You can tag individual users within comments, notes, or checklist items. To be available to
be tagged, a user must have appropriate domain access for the active design and have a valid
Capital Team Collaborator feature license. If you tag a user, they receive an email within a
fifteen minute window, provided the user has access for the active design (including domain
access defined on underlying shared objects) detailing the content they have been associated
with. Tagged users are included on a watchlist of users for a design. See the Insert User
button of the “Collaborate Editor Dialog Box” on page 950 for details on how to tag users in
Collaborate content.
Note
The frequency of Collaborate notifications can be configured.

Enabling Collaborate Notify Me Updates

You can enable a “Notify Me” notification mode to update you by email about new Collaborate
content for the current design. You also receive a summary email of all Collaborate content for
the design once a day.
Procedure
To toggle the notification setting either:
• Press the Space Bar and enter Notify. Click Workflow > Notify Me.
• On the Workflow tab of the ribbon, click the Notify Me icon .

December 2023
Collaborate
Modifying Collaborate Notifications
Note
You can add further users to the notification feature using the “Manage Notifications
Dialog Box” on page 956.
Results
When Notify Me is enabled, the icon background is green .

By default, a notification of new or updated Collaborate content is sent every 15 minutes, and a
daily activity report summarizing all content is sent every 24 hours. These frequency of these
emails can be modified, see “Modifying Collaborate Notifications” on page 695.

You can modify the Collaborate notifications system. This could include adding or removing
users who receive notifications, or changing the frequency in which notifications are sent out.
Prerequisites
• Open the Manage Notifications dialog box. See “Manage Notifications Dialog Box” on
page 956.
Procedure
In the Manage Notifications dialog box perform one of the following actions:

Add new users to the 1. Click the Add User(s) icon in the top right corner of the
notification list
dialog box. An Add Users dialog box displays.
2. Enter single or multiple user names separated by a semi
colon and click OK.
Note: Only validated system users can be added.
Remove users from the 1. Click on the name of the user you want to remove.
notification list 2. Click the Remove User(s) button in the top right corner of
the dialog box. The user is removed.

December 2023
Collaborate

Change the frequency of the 1. Navigate to the config/Collaborate-configuration.xml file in
Collaborate Changes your Capital installation
notifications emails (user 2. Find the CollaborateChangesNotificationEmailTask
tagging) parameter in the file and locate the cronexpression attribute.
3. Enter a cron expression to schedule how often the
notification task runs.
See “Cron Syntax Usage Example” in the Capital
Component Manager User Guide for information and
examples of how to define cron expressions.
Note: By default, the Collaborate Changes Notification
email task runs every 15 minutes.
Change the frequency of the 1. Navigate to the config/Collaborate-configuration.xml file in
Collaborate Activities Report your Capital installation
emails (daily report) 2. Find the CollaborateActivityReportEmailTask parameter in
the file and locate the cronexpression attribute.
3. Enter a cron expression to schedule how often the
notification task runs.
See “Cron Syntax Usage Example” in the Capital
Component Manager User Guide for information and
examples of how to define cron expressions.
Note: The Collaborate Activity Report email task runs once
every 24 hours at 12am local time.

You can view comments, notes, and checklist items on the Collaborate tabs within the Output
window. Visible content can refreshed, filtered, and searched.
Procedure
Follow the appropriate procedure from the table.

Open the Comment, Note, Either:
or Checklist tab • Press the Space Bar and enter Collaborate. Choose the
appropriate tab to open from the three displayed options.
• Click the Window > Collaborate ribbon action ,

and choose the appropriate tab to open from the three
displayed options.

December 2023
Collaborate

Search for text on the 1. Click in the Search field in the top left corner of the Output
Comment, Note, or window, enter the text for which you are searching.
Checklist tab Any matching text found in the current Collaborate tab is
highlighted yellow, with the number of matching items of
text listed next to the search field.
2. You can cycle through the matching items using the
binocular icons displayed next to the search field. The
currently selected matching item is highlighted orange.
Filter visibility of comments, 1. Click the Filter dropdown list in the top right-hand corner of
notes, or checklist items by the Output window and choose an option.
type For the different filter types available, see the reference
topics for each tab:
• Comments Tab
• Notes Tab
• Checklist Tab
Refresh the visible content Click the Refresh icon on the Collaborate tab. The content of
on the Comments, Notes or the tab page is refreshed.
Checklist tab
Close the Comments, Notes Right-click the name of the Collaborate tab and select Remove
or Checklist tab tab.

You can create new Collaborate content in the form of a comment, note, or checklist item.
You cannot annotate the following design objects in the Capital applications using the
Collaborate functionality:

o Cable marker
o Internal link
o Multicore end component
o Pin
o Terminal bar
o Wire end component

December 2023
Collaborate
• Capital Harness Designer / Capital Harness Designer Modular

o Critical dimensions
• Capital Systems Integrator / Capital Wiring Integrator
o Bundle region
o Signal
• Capital Systems Modeler
o Port
Prerequisites
• A Collaborate content tab is open in the console window. See “Viewing Comments,
Notes and Checklists” for how to open the Comment, Note, or Checklist tabs.
Procedure
1. If you are creating a comment or note, select the objects in the Design Browser or on the
diagram, to be associated items.
Note
To select multiple items, you can click and drag on the diagram to form a box around
the objects you want to select.
2. To open the Collaborate Editor Dialog Box:
• On the Comments, Notes, or Checklist tab, click the Add icon ( ).
• On the Home tab of the ribbon, click the Add Note icon ( ), or the Comment on
design icon ( ).
• Right-click on the diagram and select Collaborate > Comment or

Collaborate > Add Note.
• In the Project Browser Tree, right-click a diagram and select
Collaborate > Comment or Collaborate > Add Note.
3. In the dialog box, enter content to form the body of the item, and then click Save.
Content can be formatted text, images, object links, and user links, see “Collaborate
Editor Dialog Box” on page 950, for full details on available content types.
Note
When creating a note, a property called Note Name is available within the
Collaborate Editor dialog box, to give each note a visible unique identifier.

December 2023
Collaborate
Results
A new comment, note, or checklist item is created and displayed in the respective Collaborate
tab.
Related Topics
Comments
Checklist
Notes

You can modify an existing comment, note, or checklist item. This could include editing
content and associated design objects, or changing the status.
• Only a user with the correct level of Collaborate permissions, or who is the content
creator, can use the Edit and Delete buttons on a comment, note, or checklist item. User
Collaborate permissions can be found in “Permissions” in the Capital Access Manager
User Guide.
• Only a design with Checklist Editing and Comments Editing behaviors included on its
release level will allow content editing. See “Release Level Behaviors” in the Capital
• Only a user with a valid license and user permissions for the Collaborate feature will be
able to use the Resolve button on a comment or checklist item.
Prerequisites
• You have a design open with preexisting Collaborate content in the form of comments,
notes or checklist items.
Procedure
Open the Comments, Notes or Checklist tab

Edit the content of an 1. Click the Edit button beneath the content to be modified. The
existing comment, note, or Collaborate Editor Dialog Box displays.
checklist item 2. Within the dialog box make the required changes and click
Save.

December 2023
Collaborate

Delete an existing comment, 1. Click the Delete button beneath the content to be removed. A
note, or checklist item warning dialog box displays.
2. Within the dialog box click Proceed to delete the content, or
Close to exit the process.
Associate an object with a 1. Click the Associate button beneath the content to be
comment or note modified. The Associated Objects Dialog Box displays.
2. To add objects to the Associated Objects dialog box either:
• Single click objects in the diagram or design browser
windows.
• Click and drag in the diagram window to form a box
around the objects you want to select.
• Select an object in the Design Browser window, and then
Shift+click another listed object to select all the objects in-
between.
3. Click OK to associate all the listed objects with the comment
or note.
The associated objects are listed as hyper-links within the
comment or note. If clicked, an object will be brought in-
focus in the diagram window.
Remove an associated object 1. Click the Associate button beneath the content to be
from a comment or note modified. The Associated Objects Dialog Box displays.
2. To remove objects from the list, highlight the object you
want to remove, or use Ctrl+Shift+click to highlight multiple
objects.
3. Click to remove the selected objects from the list.
4. Click OK.
Resolve a comment or 1. Click the Resolve button beneath the content to be modified.
checklist item The Collaborate Editor Dialog Box displays.
2. In the dialog box add any additional information for this
action and click Resolve.
Reopen a resolved comment 1. Click the Reopen button beneath the content to be modified.
or checklist item The Collaborate Editor Dialog Box displays.
2. In the dialog box add any additional information for this
action and click Reopen.
Note: If your resolved comment or checklist item is not
visible, select the visibility filter for the tab. See the
Results of this task topic for more detail.

December 2023
Collaborate

Toggle a checklist item’s Click the graphic on the left of the checklist item to toggle its
status
status. A green graphic indicates completed, or resolved
status. A red circle graphic indicates a pending, or

unresolved status.
Results
• After resolving a comment, its status is changed and will only now be visible in the
Comments tab when the All or Resolved visibility filter is selected. See “Viewing
Comments, Notes and Checklists” on page 696 for details on visibility filters.
• After resolving a checklist item its status is changed to completed and will only now be
visible in the Checklist tab when the All or Completed visibility filter is selected. See
“Viewing Comments, Notes and Checklists” on page 696 for details on visibility filters.
Related Topics
Comments
Checklist
Notes
This topic describes how to create a reply to an existing Collaborate comment.
Prerequisites
• You have an existing Collaborate comment visible in the Comments tab of the Output
Window. See Creating a Comment, Note or Checklist Item for how to create a
Collaborate comment.
Procedure
1. In the Comments tab, click the Reply button beneath an existing comment. The
Collaborate Editor Dialog Box displays.
Note
A reply is itself a comment, and so in turn can also be replied to. A reply cannot be
resolved or have additional associated objects however.
2. Within the dialog box enter content to form the body of the reply and click Save.
Content can be formatted text, images, object links and user links, see “Collaborate
Editor Dialog Box” on page 950 for full details on available content types.

December 2023
Collaborate
Managing Collaborate Data in a Project or Design Action
Results
A new comment is created and displayed as a reply to the parent comment in the Comments
tab.
Related Topics
Comments
Managing Collaborate Data in a Project or

Design Action
You can include Collaborate data in a project or design action. Such actions might include
exporting or copying a design, or creating a new revision. Individual types of Collaborate data
can be chosen for inclusion in the action, overriding the default settings.
Prerequisites
• The dialog box for your required action is open. For example, the export design or
export project dialog box. See “Exporting a Project” or “Exporting a Design From a
Project” in the Capital Project Manager User Guide.
Procedure
1. In the open dialog box, click the Collaborate Options button. The Edit Collaborate
Options Dialog Box opens.
2. From the options, check which types of Collaborate data you want to include with this
action.
Note
The initial check status of the options is taken from the default export settings. See
the System Preferences for Collaborate section of “System Preferences Dialog
Box” in the Capital Project Manager User Guide for default action settings.
3. Click OK to confirm your changes and continue with the action.

Results
If exporting a design, the completed export includes Collaborate data of the types set in this
process, overriding the default settings in this export instance only.

December 2023
Chapter 11
Trace and Navigate, Compare and Propagate
Trace and navigate functionality (Capital Change Validator) provides you with the ability to
trace related objects across design revisions and abstractions, and to navigate to those objects.
Compare and propagate functionality provides you with the ability to compare objects in
designs, and generate a To Do list to help propagate changes that ensure your designs and build
lists are consistent.
Trace and Navigate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
Tagging Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704
Working Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
Adding Designs to a Working Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
Tracing an Object across Designs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Trace Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
Trace Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
Configuring Tagging Tasks to Run in the Background . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
Configuring Stale Tag Cleanup Tasks to Run in the Background . . . . . . . . . . . . . . . . . . . 715
Compare and Propagate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
To Do List Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Troubleshooting Tagging Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
ANSTagGenerationTask or ANSStaleTagCleanupTask Fails . . . . . . . . . . . . . . . . . . . . . . 733
ANSTagGeneration Task Cannot Run after Superuser Password Change. . . . . . . . . . . . . 733
ANSTagGenerationTask or ANSStaleTagCleanupTask Runs for a Long Time . . . . . . . . 734
CapitalRunner Log File Indicates Out-of-Memory Issues . . . . . . . . . . . . . . . . . . . . . . . . . 735
Tagging Tasks Have Not Started After Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
First Tagging Task Takes a Long Time After Data Migration. . . . . . . . . . . . . . . . . . . . . . 735

December 2023
Trace and Navigate
Trace and Navigate

Trace and navigate (Capital Change Validator) functionality provides you with the ability to
trace related objects across design revisions and abstractions, and to navigate to those objects.
For example, you can see how a signal is implemented by wires.
The scope of this functionality is dictated by a user-defined working set of designs and build
lists. You can trace and navigate to objects in designs in the working set only. The initial object
that you select need not be in a design in the working set but all trace results will be from the
working set.
This video demonstrates how trace and navigate works.
Tagging Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 704

Working Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
Adding Designs to a Working Set. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
Tracing an Object across Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Trace Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
Trace Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
Configuring Tagging Tasks to Run in the Background . . . . . . . . . . . . . . . . . . . . . . . . . . 711
Configuring Stale Tag Cleanup Tasks to Run in the Background . . . . . . . . . . . . . . . . . 715
Tagging Service
The trace functionality refers to tags that the system generates for various containers in the
Capital database (for example, designs, SBOMs). Tags are named pieces of data that the system
generates for an object in a container and stores for querying.
For example, you can have a tag with type “signal” and value “POWER +12V”. That tag
represents the signal of an object in a design. Wires and nets implementing that signal have that
tag.

December 2023
Working Set
Note
It is mandatory to run a Capital Integration Server (Capital Integration Server Controller) in
your Capital environment to ensure all base functionality is available. See the “Flexible
Execution Manager (FEM)” chapter of the Capital Installation and Upgrade - Additional
Information guide and the The capitalintegrationserverconfigurationxml File Formatsection in
the Capital Configuration Files Reference Guide.
The tagging service is triggered by various user actions that run for containers:
• When you edit a container. For example, when you edit and save a design.
• When you delete a container. For example, when you delete a design.
• When you import a project or design.
• When you edit a shared object in a Capital Logic Designer design.
• When you add a design to the working set.
• When you revise or copy a Capital Systems Integrator, Capital Harness Designer, or
Capital Wiring Integrator design.
In addition, you can modify the schedule of the tagging service and its related parameters. See
Configuring Tagging Tasks to Run in the Background.
When containers are deleted from the database, any tags related to them remain. You can
configure the system to check for these stale tags and remove them on a fixed schedule. See
Configuring Stale Tag Cleanup Tasks to Run in the Background.
Related Topics
Trace and Navigate
Working Set
Adding Designs to a Working Set
Configuring Tagging Tasks to Run in the Background
Configuring Stale Tag Cleanup Tasks to Run in the Background
Working Set
Your working set contains designs that are relevant to your work. You can trace and navigate to
objects in designs in your working set only.
You add individual designs of any type or build lists to the working set. Included designs and
build lists are indicated by a green dot ( ) overlaid on top of the icon for the design or build list
in the Project Browser Window.

December 2023
The system saves your working set on your computer. If you close and re-open Capital (and the
project) on that computer, the working set is still available. If you access Capital on a different
computer, the working set is not available.
You can filter the Project Browser Window in any design application to display only the designs
in your working set. Select the Show designs and build lists in Working Set icon ( ) at the
bottom right of the Project Browser Window.
Related Topics

Adding a design, design folder, or build list to a working set means you can trace and navigate
to objects in any of the included designs.
Procedure
In the Project Browser Window at the top left of any design application window, right-click the
design, design folder, or build list and select Add to Working Set.
Note
You can select multiple designs and design folders.
Results
• In the Project Browser Window, a green dot is added to the icon for the design, design
folder, or build list (for example, ).
• Trace and navigate functionality can trace and navigate to objects in that design, design
folder, or build list.
• If multiple revisions of the same design are included in a design folder, the system adds
the latest revision only.
• The working set is saved on the computer on which you are working. If you close and
re-open Capital (and the project) on that computer, the working set is still available. If
you access Capital on another computer, the working set is not available and you will
have to set it up on that computer again.
• You can filter the Project Browser Window in any design application to display only the
designs in your working set. Select the Show designs and build lists in Working Set
icon ( ) at the bottom right of the Project Browser Window.
• You can remove a design, design folder, or build list from a working set by right-
clicking it in the Project Browser Window and selecting Remove from Working Set.

December 2023
Tracing an Object across Designs
To remove everything from a working set, right-click the project name in the Project
Browser Window and select Remove from Working Set.
Related Topics
Trace and Navigate
Working Set

You can select an object in a design and trace (find) related objects in other designs from your
working set, as well as find linked requirements (in external systems). The related objects are
presented as a list to navigate to those objects in the appropriate applications.
Prerequisites
• If you want to trace requirements (in external systems), those requirements must have
been linked to Capital objects. See “Bi-directional Requirements Linking with Polarion”
and “Bi-directional Requirements Linking with Teamcenter” in the Capital Connectors
User Guide.
Procedure
Do one of the following:
• Right-click the object and select Trace.

• Click the object and press Ctrl-T.
• Click the object and click the Trace action ( ) on the Ribbon.
Note
The Trace button ( ) is also available on the Links tab for linked
requirements at the bottom left of the application window. Here you can select a
linked requirement and click that button.
A Trace Tab appears in the Output Window at the bottom of the application window.
Note
If the Trace action is dimmed, the tool tip on it explains why. The most common
reasons are you have multiple objects selected or have an empty working set.
Results
• The Trace tab displays: the related objects.
o All related Capital objects (in the active working set)

December 2023
Trace Tab
o For each listed Capital object, all linked requirements (in external systems)
• Click a related object’s name to navigate to it. The appropriate application and design
opens with the related object highlighted and a Trace tab opens for that object.
Note
If you traced from an object that is not in the working set, the Trace tab displays
only related objects that are in the working set.
Related Topics
Trace and Navigate
Working Set
Trace Relationships
Trace Tab
A Trace tab is displayed in the Output Window at the bottom of a design application window
when you use trace functionality to find related objects to the object currently selected in the
design.
The tab displays a table listing the related objects with the following contents:
Table 11-1. Trace Tab Contents
Field Description
Click to go back in history If you have clicked the icon in the Name column to view
Click to go forward in trace results for related objects, you can navigate backwards
history and forwards through the results for each viewed object. The
viewed objects are listed alongside these buttons. The
dimmed name indicates the object whose results are
displayed currently. You can click a blue object name to
view the results for it. You can click earlier objects that you
viewed to see their results again and the listed objects remain
the same until you click the icon for an object not yet
viewed.
Refresh the contents of the Refreshes the contents of the tab with any related updates
table made for the current object in the other designs.
Abstraction The abstraction assigned to the design containing the related
object. If you have not assigned an abstraction for the design,
the design type displays.

December 2023
Trace Relationships
Table 11-1. Trace Tab Contents (cont.)

Field Description
Name The name of the related object. You can click the name to
navigate to the object. The design opens in the appropriate
application with the object highlighted and a Trace tab opens
for that object.
If you do not want to open the other design, you can hold the
mouse cursor over this field and click the icon to display
the trace results for that related object. That is, what the
Trace tab would display if you had right-clicked the related
object in the other application and selected Trace.
Relationship The relationship between the selected object and the related
object. Hold your mouse cursor over the relationship to view
a tool tip that explains what the relationship means. See also
“Trace Relationships” on page 709 for descriptions of
relationships.
Design The name of the design in which the related object is located.
Build List The name of the build list containing the design with the
related object. “None” displays if the design is not part of
any build list.
Usage Notes
To tear this tab from the interface so that it is a free-floating, re-sizable dialog box, click the tab
name and drag it. If you do not tear the tab from the interface, the results are replaced when you
use the trace function for another object. If you tear off the tab, it remains unchanged when you
use the trace function for another object and a separate tab is created. To return the tab to the
Output Window, close the dialog box.
When free-floating, the name of the tab also includes the selected object. For example,
Trace:BUN387.
Related Topics
Trace Relationships
Trace Relationships
The Trace functionality identifies various relationships between objects.
The Trace tab results can include the following relationships between objects.

December 2023
Trace Relationships
Table 11-2. Trace Relationships

Relationship Description
Same Name This object in the list has the same name as the
traced object regardless of the object kind.
For example: When you create a revision or a copy
of a Capital Logic Designer design, the same pins
across revisions appear in trace results. Note that
the ‘same name for pins’ trace looks only within a
single device. It does not trace all pins with the
same name across all devices.
Same Signal This object in the list has the same value for the
signal attribute or property as the traced object
regardless of the object kind.
For example: When you create a revision of a
Capital Logic Designer design and convert nets to
wires in it, the trace results for a wire show the nets
corresponding to it in the original revision.
Same Connectivity This object in the list has the same end point
connectivity as the traced object. Must be an exact
match.
Same Ancestry This object in the list has the same ancestry as the
traced object. Through the various types of data
management activities, these two objects are
related. It is not necessary that one be a direct
descendant of the other. Note that copying a design
will not retain any ancestry relationships.
source Capital Logic Designer design, a revised
wire in the revision has the same base ID as an
original wire in the source. This means, when you
trace one of them, the other appears in the trace
results as sharing the same ancestry.
Direct Descendant This object in the list was derived from the traced
object through a data management task such as
revisioning the design, or harness synchronization.
device in the revision has a parent ID equal to the
ID of an original device in the source. This means,
when you trace the original device, the revised
device appears in the trace results as direct
descendant.

December 2023
Table 11-2. Trace Relationships (cont.)

Relationship Description
Direct Ancestor This object in the list was sourced from the traced
object through a data management task such as
revisioning the design, or harness synchronization.
For example, when you create a revision of a
device in the revision has a parent ID equal to the
ID of an original device in the source. This means,
when you trace the revised device, the original
device appears in the trace results as direct
ancestor.
Linked A related object has a link to a requirement (in an
<EXTERNAL_SYSTEM> external system).
requirement
For example, Linked
Teamcenter requirement
Platform Implementation This object in the list is the representation (Capital
Systems Integrator/Topology): signal(s), slot(s),
splice(s), connector(s), wire(s) in the topology of
the traced object.
That means, the trace result is showing the
implementation object in a Capital Systems
Integrator design for an object in an associated
Platform Source This object in the list is the source (in Capital Logic
Designer) of the traced topology object.
That means, the trace result is showing the object in
an associated Capital Logic Designer design when
an object in a Capital Systems Integrator design is
traced.
Related Topics
Trace Tab
Configuring Tagging Tasks to Run in the

Background
In order for you to use the trace functionality, the system must tag design data. You can modify
the schedule of the task that does this and its related parameters.

December 2023
The tagging task runs mainly for data that has been edited since the last time it was tagged.
See Tagging Service for further information about tagging.
Prerequisites
• You should be a system administrator.
• You must have configured Capital Integration Server in the
capitalintegrationserverconfiguration.xml file in the config directory of your
installation. The specified user must have access to all domains that require tagging. See
the The capitalintegrationserverconfigurationxml File Format section in the Capital
Configuration Files Reference Guide for further information.
• You can configure the Capital Integration Server to perform tagging tasks on a dedicated
machine. See the “Flexible Execution Model (FEM)” chapter of the Capital Installation
and Upgrade - Additional Information guide for further information.
Procedure
1. Navigate to the config directory of your Capital installation where you run Capital
Integration Server and open the indexing-configuration.xml file for editing.
2. Find the ANSTagGenerationTask line and edit the parameters:
• autoschedule
Set to true to enable the background indexing and tagging. The scheduling specified
by the cronexpression runs from when the Capital Integration Server starts.
• cronexpression
Enter a cron expression to schedule how often the indexing and tagging task runs.
See Cron Syntax Usage Example for information and examples of how to define
cron expressions.
• store_logs_per_execution
Defines whether you want to store all execution logs. Default is set to false which
means the log for only the latest execution run is stored.
For example:
<ANSTagGenerationTask autoschedule="true" cronexpression="0 0 0/1 * * ?"
store_logs_per_execution="false"/>
3. Find the TaskParameters line and edit the parameters:
• batchsize
The indexing and tagging task processes batches of design containers. Specify how
many design containers are included in each batch.

December 2023
• waittime
Specify how much time (in milliseconds) the system waits between finishing one
batch of design containers and starting on the next batch. This frees up the system
for any other scheduled tasks.
• cleanupfiles
As the ANSTagGeneration task (and related ANSStaleTagCleanup task) run
frequently, they accumulate task parameter files and log files quickly. Specify true
if you want the system to clean up (delete) these files automatically.
Specify “false” if you do not want to run clean-up functionality. If you want to
archive the files rather than delete them, you can implement your own OS batch
script.
• cleanuptype
If you have set cleanupfiles to “true”, this specifies how the files are cleaned up.
Specify one of the following values:
o simple
Deletes all the parameter files and log files for the task, excluding the files for
the current task run.
o retainbytime
Deletes all the files that are older than a specified retention time (retentiontime
parameter).
o retainbycount
Deletes all the files, excluding those for the specified number of last task
executions (retentioncount parameter).
• retentiontime
Relates to the cleanuptype parameter with value retainbytime. Specify the maximum
age (in milliseconds) of the parameter files and log files that are not deleted.
• retentioncount
Relates to the cleanuptype parameter with value retainbycount. Specify the number
of last executions for which the parameter files and log files are not deleted.
Default parameters:
With the following default parameters, the system indexes and tags 100 design
containers, and then leaves 15000 milliseconds before indexing and tagging the next 100
design containers, and so on. It deletes parameter and log files but retains those with an
age up to 604800000 milliseconds. Recommended during tagging on larger databases
(as this can take days and you do not want to lose log files that are generated early).

December 2023
<TaskParameters batchsize="100" waittime="15000" cleanupfiles="true"

cleanuptype="retainbytime" retentiontime="604800000"/>
For example:
In the following example, the system indexes and tags 100 design containers, and then
leaves 15000 milliseconds before indexing and tagging the next 100 design containers,
and so on. It deletes parameter and log files but retains those with an age up to 14400000
milliseconds.
In the next example, it deletes the parameter and log files, but retains those from last
four execution runs of the task.
cleanuptype="retainbycount" retentioncount="4"/>
Caution
The TaskParameters are shared with any Stale Tag Cleanup tasks configured in the
indexing-configuration.xml file.
4. Save and close the indexing-configuration.xml file.

Results
• When Capital Integration Server starts, the system follows the scheduling specified by
the cronexpressions to run the indexing and tagging tasks.
• For each execution of the task, the system creates two files in the temp directory for your
Capital installation:
o An XML task parameter file whose name starts with “ANSTagGenerationTask”
followed by a unique identifier.
o An execution log file whose name starts with “CapitalRunner” followed by the same
unique identifier.
• You can use the trace functionality after the system has run tagging at least once.
• You can monitor the tasks in the Tasks tab in Output Window, from which you can also
access log files. You can also access the log files in your temp directory.
Note
If you need to kill a tagging task, for example, when you need to reboot the system
while it is running. You can kill it from your Task Manager. However, check that the
status of the task on the Tasks tab changes to FAILED. If the status is still RUNNING,
see “ANSTagGenerationTask or ANSStaleTagCleanupTask Runs for a Long Time” on
page 734 for instructions on how to reset it.

December 2023
Related Topics
Tagging Service
Troubleshooting Tagging Tasks
Configuring Stale Tag Cleanup Tasks to Run in the

Background
When you use the trace functionality, the system runs indexing and tagging tasks in the
background. The tags are stored in the Capital database. However, when design containers are
deleted from the database, any tags related to them remain. You can configure the system to
check for these stale tags and remove them on a fixed schedule.
Prerequisites
• You should be a system administrator.
• You must have configured Capital Integration Server in the
capitalintegrationserverconfiguration.xml file in the config directory of your
installation. The specified user must have access to all domains that require tagging. See
the The capitalintegrationserverconfigurationxml File Formatsection in the Capital
Configuration Files Reference Guide for further information.
• You can configure the Capital Integration Server to perform tagging tasks on a dedicated
machine. See the “Flexible Execution Model (FEM)” chapter of the Capital Installation
and Upgrade - Additional Information guide for further information.
Procedure
1. Navigate to the config directory of your Capital installation where you run Capital
Integration Server and open the indexing-configuration.xml file for editing.
2. Find the ANSStaleTagCleanupTask line and edit the parameters:
• autoschedule
Set to true to enable the background cleanup of tags. The scheduling specified by the
cronexpression runs from when the Capital Integration Server starts.
• cronexpression
Enter a cron expression to schedule how often the cleanup task runs. See Cron
Syntax Usage Example for information and examples of how to define cron
expressions.
• store_logs_per_execution

December 2023
Defines whether you want to store all execution logs. Default is set to false which
means the log for only the latest execution run is stored.
For example:
<ANSStaleTagCleanupTask autoschedule="true" cronexpression="0 0 0/1 * * ?"
store_logs_per_execution="false"/>
3. Find the TaskParameters line and edit the parameters:
• batchsize
The cleanup task processes batches of design containers. Specify how many design
containers are included in each batch.
• waittime
Specify how much time (in milliseconds) the system waits between finishing one
batch of design containers and starting on the next batch. This frees up the system
for any other scheduled tasks.
• cleanupfiles
As the ANSStaleTagCleanup task (and related ANSTagGeneration task) run
frequently, they accumulate task parameter files and log files quickly. Specify “true”
if you want the system to clean up (delete) these files automatically.
Specify “false” if you do not want to run clean-up functionality. If you want to
archive the files rather than delete them, you can implement your own OS batch
script.
• cleanuptype
If you have set cleanupfiles to “true”, this specifies how the files are cleaned up.
Specify one of the following values:
o simple
Deletes all the parameter files and log files for the task, excluding the files for
the current task run.
o retainbytime
Deletes all the files that are older than a specified retention time (retentiontime
parameter).
o retainbycount
Deletes all the files, excluding those for the specified number of last task
executions (retentioncount parameter).
o retentiontime

December 2023
Relates to the cleanuptype parameter with value retainbytime. Specify the

maximum age (in milliseconds) of the parameter files and log files that are not
deleted.
o retentioncount
Relates to the cleanuptype parameter with value retainbycount. Specify the
number of last executions for which the parameter files and log files are not
deleted.
Default parameters:
With the following default parameters, the system indexes and tags 100 design
containers, and then leaves 15000 milliseconds before indexing and tagging the next 100
design containers, and so on. It deletes parameter and log files but retains those with an
age up to 604800000 milliseconds.
For example:
In the following example, the system indexes and tags 100 design containers, and then
leaves 15000 milliseconds before indexing and tagging the next 100 design containers,
and so on. It deletes parameter and log files but retains those with an age up to 14400000
milliseconds.
In the next example, it deletes the parameter and log files, but retains those from last
four execution runs of the task.
cleanuptype="retainbycount" retentioncount="4"/>
Caution
The TaskParameters are shared with any Indexing and Tagging tasks configured in
the indexing-configuration.xml file.
4. Save and close the indexing-configuration.xml file.

Results
• When Capital Integration Server starts, the system follows the scheduling specified by
the cronexpressions to run the cleanup task.

December 2023
• For each execution of the task, the system creates two files in the temp directory for your
Capital installation:
o An XML task parameter file whose name starts with “ANSStaleTagCleanupTask”
followed by a unique identifier.
o An execution log file whose name starts with “CapitalRunner” followed by the same
unique identifier.
• You can monitor the tasks in the Tasks tab in Output Window, from which you can also
access log files. You can also access the log files in your temp directory.
Note
If you need to kill a tagging task, for example, when you need to reboot the system
while it is running. You can kill it from your Task Manager. However, check that the
status of the task on the Tasks tab changes to FAILED. If the status is still RUNNING,
see “ANSTagGenerationTask or ANSStaleTagCleanupTask Runs for a Long Time” on
page 734 for instructions on how to reset it.
Related Topics
Tagging Service

December 2023
Compare and Propagate

You can compare objects in designs and use a To Do List to propagate changes that ensure your
designs and build lists are consistent. For example, you have added a device to a system design
but you have not yet added it to an associated wiring design.
The To Do List displays all differences between the designs and enables you to navigate to the
objects that require a change.
This video demonstrates how compare and propagate works.
Note
In addition to the functionality shown in the video, you can automatically propagate
attribute and property changes (non-connectivity changes) between Capital Logic Designer
designs and abstractions.

December 2023
Figure 11-1. Supported and Unsupported Design Comparisons - Capital Logic

Designer

December 2023
Viewing the To Do List for a Design
Figure 11-2. Supported and Unsupported Design Comparisons - Other

Applications

Applying To Do List Attribute and Property Changes Between Capital Logic Designer
Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
To Do List Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727

When using compare and propagate functionality, you can use the To Do list to view which
objects require updating in a related design and which tasks (deltas) should be performed for
them. For example, you have added a device to a system design but you have not yet added it to
an associated wiring design.

December 2023
Note
On a wiring diagram, you can use internal connectivity to model devices like terminal bars
that implement splices, either by using symbols with internal links or by adding nets directly
between pins of a device.
When you compare logical designs with wiring designs, the To Do list does not recognize this
internal connectivity and reports such devices, and the signals they propagate, as being an
incorrect implementation of a net (signal). You can add a property
TRAVERSE_INTERNAL_LINKS with a value of yes to a device in a wiring design so that the
To Do list recognizes the internal connectivity and does not report it as a difference. See also
“Usage Example - Traversing Internal Device Links When Using Compare and Propagate
Functionality” on page 726.

• When source and target designs belong to different abstractions, attribute tasks (deltas)
are only reported if the attribute values are different from the default values in both the
source and target designs.
If an attribute is specified with the default value in at least one abstraction, the
comparison ignores the attribute value across all designs.
Procedure
1. From the Project Browser window, navigate to and select a design in which you want to
identify objects that need updating:
• Click To Do on the Workflow tab.
• Right-click and select To Do List.
The To Do List Tab displays on the bottom left of the application. The design is selected
in the “to Update” dropdown list.
2. Click the Use dropdown list and select the design that has been updated and requires
changes to be reflected in the “to Update” design.
3. Click the Refresh icon ( ).
The To Do list displays on the tab. The gray header rows list objects that have been
added, changed, or deleted in the “Use” design.
4. Click the arrow at the start of these rows to view the tasks (deltas) that need to be
completed in the “to Update” design.
Where possible, objects are hyperlinks that you can click to locate them in the Diagram
window (other applications open when required). If multiple instances of the object
exist, the system opens the target instance from the hyperlink but also opens a Trace tab
for the object that lists the other instances.

December 2023
Note
The hyperlinks navigate to the source (Use) or the target (to Update) designs based
on the following criteria:
• By default, the link opens the target design and object.
• If the object does not exist yet in the target design, the link opens the source design
and object.
5. Update the objects in the “to Update” design as required.
Note
You can automatically propagate attribute and property changes (non-connectivity
changes) between Capital Logic designs and abstractions. See “Applying To Do List
Attribute and Property Changes Between Capital Logic Designer Designs” on page 723.
Results
When you complete one or more tasks and click the Refresh icon ( ), the system strikes the
completed tasks off the list but does not remove them. If you complete all tasks for an object,
the entire group of tasks are struck off and the group moves to the bottom of the list. To remove
all completed tasks from the list, click the dropdown arrow by the Refresh icon and select
Restart.
Note
The dropdown arrow displays various actions that you can perform, including swapping the
designs in the Use and “to Update” fields, and exporting the listed tasks (deltas) as a CSV
file. You can also use filters at the bottom of the To Do List tab to control which tasks (deltas)
are displayed in the To Do list. See “To Do List Tab” on page 727 for details of both the
dropdown arrow actions and the filters.
Related Topics
To Do List Tab
Applying To Do List Attribute and Property

Changes Between Capital Logic Designer Designs
When viewing a To Do list for Capital Logic Designer designs, you can automatically
propagate attribute and property changes (non-connectivity changes) between designs and
abstractions.

December 2023
Note
You can only automatically propagate changes from Capital Logic Designer designs or
build lists to Capital Logic Designer designs or build lists.
You cannot apply attribute and property changes automatically when using a custom
configuration for the comparison.
This enables you to apply a change once and propagate it to multiple designs for consistency.
For example, if you change a maximum current property in a system design, you can propagate
that to your wiring designs.
For a list of the Capital Logic Designer object attributes that are supported or not supported by
this automatic propagation, see the <installation_directory>/docs/supportingdocs/
Change_Selected_Supported_Attributes.pdf file.

• You cannot propagate changes automatically in cases where you normally would not be
able to make such a change. This includes scenarios where the design is read-only, you
do not have domain permissions to write, shared objects are frozen, or a design is not in
single-user mode. Also, you cannot propagate changes automatically if you are using a
custom configuration for the comparison.
• Attributes and properties that are changed because of a change to the library part will not
display in the To Do list. Only the library part change is displayed. Once the library part
is changed, you must update the library part in the Edit Properties dialog box for an
impacted object or run a batch update of library parts to apply all of the attribute or
property changes.
Prerequisites
• You must have generated a To Do list for Capital Logic Designer designs. See “Viewing
the To Do List for a Design” on page 721.
Procedure
1. In the To Do list, select the non-connectivity tasks (deltas) for which you want to
propagate the attribute or property changes.
Figure 11-3. Selected To Do Task (Delta)

December 2023
Note
If you select the check box in a gray header row, the system selects all non-
connectivity tasks grouped below it.
The selection box for a connectivity change is not enabled.
2. Click the Change selected button.
Caution
You cannot undo any changes once they are applied because the system saves them.
However, the system displays a progress bar while making the changes. You can
click Stop to stop the process; however, stopping does not undo any changes that are
already applied.
Results
• The system saves the applied changes.
• The system strikes the completed tasks off the list but does not remove them.
Figure 11-4. Applied Change in To Do List
• The system displays the To Do tab in the Output window at the bottom of the application
to indicate whether the changes have been applied successfully or not.
Figure 11-5. To Do Tab in the Output Window
Note
The messages contain hyperlinks to the relevant objects.

December 2023
Usage Example - Traversing Internal Device Links

When Using Compare and Propagate Functionality
On a wiring diagram you may use internal connectivity to model devices like terminal bars that
implement splices, either by using symbols with internal links or by adding nets directly
between pins of a device. When you compare logical designs with wiring designs, the To Do list
does not recognize such internal connectivity and reports such devices, and the signals they
propagate, as being an incorrect implementation of a net (signal). You can add a property
TRAVERSE_INTERNAL_LINKS with a value of yes to a device in a wiring design so that the
To Do list recognizes the internal connectivity and does not report it as a difference.
In this example, you have a simple logical design:
Figure 11-6. Simple Logical Design
You have a related wiring design:
Figure 11-7. Related Wiring Design
DIODE is a symbol with an internal link between the pins.

December 2023
To Do List Tab
If you use the To Do list to compare the logical and wiring diagram, you get the following
deltas:
Figure 11-8. Deltas Without TRAVERSE_INTERNAL_LINKS Property
This is because the To Do list does not trace through the internal connectivity of DIODE and
treats it as a connectivity break.
You can add the property TRAVERSE_INTERNAL_LINKS with a value of yes to DIODE.
Figure 11-9. TRAVERSE_INTERNAL_LINKS with Value of yes
When you use the To Do list to compare the designs again, it now traces through the internal
connectivity of DIODE and no longer treats it as a connectivity break.
Figure 11-10. Deltas with TRAVERSE_INTERNAL_LINKS Property
Note
If you want the To Do list to treat a device with internal connectivity as a connectivity break
again, you can either remove the TRAVERSE_INTERNAL_LINKS property or set it to no.
To Do List Tab
A To Do List tab is displayed at the bottom left of a design application window when you click
the To Do action on the Workflow tab of the ribbon or when you right-click a design in the

December 2023
To Do List Tab
Project Browser Window and select To Do List. You can hide the tab by right-clicking it and
choosing Close.
For example, you have added a device to a system design (“Use” design) but you have not yet
added it to an associated wiring design (“to Update” design).
Table 11-3. To Do List Tab Contents
Field Description
With Select the custom configuration that you want to use.
Displayed only if you have a config/changevalidator.xml file
that contains details of custom comparators.
This field is used by trace and compare functionality for
block designs (as well as other types of design). See Trace
and Compare for Block Designs in the Capital Logic
Use Select the design or build list that has been updated and
whose changes need to be reflected in other related designs
(“to Update” designs). You can swap the designs or build
lists in the Use and “to Update” fields by clicking the
Refresh ( ) dropdown and choosing Swap. That action
swaps the values in the fields and updates the To Do list.
to Update Select the design or build list that you need to update to make
it consistent with changes already made in the “Use” design
or build list.
By default, the design or build list that you right-clicked in
the Project Browser Window is selected.
If you have defined a Working Set, the designs in that set are
listed for selection.
Select Choose if you want to select a design outside of the
working set, using the Design Revision - Build List Selection
Dialog Box.

December 2023
To Do List Tab
Table 11-3. To Do List Tab Contents (cont.)

Field Description
Refresh dropdown Having selected a “Use” design and “to Update” design,
click the icon ( ) to display the To Do list on this tab.
When you have changed all “to Update” objects for a “Use”
Note: When the Refresh
object and click the icon, a line appears through the name of
dropdown is grayed out
the “Use” object. If you complete all tasks for an object, the
it means that the selected
entire group of tasks (deltas) are struck off and the group
designs are not supported. It
moves to the bottom of the list.
is enabled for:
The dropdown arrow displays various actions:
• any two supported
designs in any • Restart
application Refreshes the tasks displayed in the To Do list and
• any two designs if you removes all completed tasks.
use a complete custom • Swap
comparison profile (that
is, a profile where all Swaps the “Use” design and “To Update” design and
comparators and updates the To Do list accordingly.
relationships are • Export all deltas or Export filtered deltas
custom) Exports all or just the filtered tasks as a CSV file for
reporting or detailed analysis. The CSV file contains the
following:
• Header
The header row from the To Do list
• Complete
Whether you have completed the task
• Object
The kind of object
• Delta
The type of action
• Description
The description of the action
<Number> shown and Displayed for Capital Logic Designer designs only.
<Number> selected of Indicates the number of To Do tasks (deltas) currently
<Number> total displayed (not filtered out), alongside the number currently
selected, and the total number of deltas.
Note: If you have selected an action and it is now filtered
out, it is still selected and will be applied when you click
Change selected.

December 2023
To Do List Tab

Field Description
Change selected Enabled for Capital Logic Designer designs only.
Click this to propagate attribute and property changes across
designs and abstractions for the To Do tasks (deltas)
currently selected in this tab.
See “Applying To Do List Attribute and Property Changes
Between Capital Logic Designer Designs” on page 723.

December 2023
To Do List Tab

Field Description
To Do list The gray header rows list objects that have been added,
deleted, or changed in the "Use" design and that need you to
perform a corresponding task in the "to Update" design.
Click the arrow at the start of these rows to view those
corresponding tasks (deltas) that you need to perform in the
"to Update" design.
Where possible, objects are hyperlinks that you click to
navigate to the object in the diagram window (other
applications open when required). If multiple instances of
the object exist, the system opens the target instance from the
hyperlink but also opens a Trace tab for that object that lists
the other instances.
Note: The hyperlinks navigate to the source (Use) or the
target (to Update) designs based on the following
criteria:
• By default, the link takes the user to the target design and
object.
• If the object does not exist yet in the target design, the
link takes the user to the source design and object.
For Capital Logic Designer designs only, you can select
tasks related to attribute and property changes (non-
connectivity changes). If you click the Change Selected
button, the system propagates these changes across the
designs and abstractions for the selected tasks. If you select a
gray header row, the system selects all non-connectivity
tasks grouped below it.
Note: The selection box for a connectivity change is not

enabled.
You can right-mouse click the list and choose Expand all or
Collapse all to expand or collapse all listed deltas.
For Capital Logic Designer designs only, you can right-click
the list and choose Select All or Unselect All to change the
current selection of tasks.

December 2023
To Do List Tab

Field Description
Text Filter You can filter the tasks (deltas) to display only those that
contain a particular text string (for example, CAN). The text
filter supports wildcards (see “Browser Tab and Dialog Box
Filters” on page 880)
The text filter field is displayed always and you can click
to clear it.
Add a new filter You can filter the tasks (deltas) displayed in the To Do list by
adding the following filters:
• Kind
Note: You can have
only one Kind filter, one This filter display deltas for one or more specific kinds of
Type filter, and one Nature objects (nets, wires, devices, and so on). The available
filter. This button is objects are limited to only those that are included in the
disabled when you have listed deltas.
each of these. • Type
You click to remove a This filter displays deltas for one or more specific types
filter. of design modification in the “to Update” design:
• Add
You should add an object.
• Delete
You should delete an object.
• Change
You should modify an object (for example, you need
to change an attribute or property).
• Nature
You can apply a filter to display deltas based on the
nature of the required task in the “to Update” design:
• Property
The task requires a change to property values.
• Attribute
The task requires a change to attribute values.
• Connectivity
The task requires a change to connectivity (such as,
moving a net from one pin to another or deleting a
wire).
Related Topics

December 2023

You can encounter the following scenarios when tagging tasks are running.
ANSTagGenerationTask or ANSStaleTagCleanupTask Fails . . . . . . . . . . . . . . . . . . . . 733
ANSTagGeneration Task Cannot Run after Superuser Password Change. . . . . . . . . . 733
ANSTagGenerationTask or ANSStaleTagCleanupTask Runs for a Long Time . . . . . 734
CapitalRunner Log File Indicates Out-of-Memory Issues . . . . . . . . . . . . . . . . . . . . . . . 735
Tagging Tasks Have Not Started After Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . 735
First Tagging Task Takes a Long Time After Data Migration . . . . . . . . . . . . . . . . . . . . 735
ANSTagGenerationTask or
ANSStaleTagCleanupTask Fails
ANSTagGenerationTask or ANSStaleTagCleanupTask has a FAILED status in the Tasks tab
displayed in the Output Window of your Capital application.
Solution
Look at the corresponding XML task parameter file and execution log file for this task
execution to view the reason for the failure. The files are located in the temp directory for your
Capital installation on the computer where the task is or was being executed. The Machine
column on the Tasks tab indicates which computer this is.
ANSTagGeneration Task Cannot Run after

Superuser Password Change
Capital Integration Server cannot run a ANSTagGeneration task after the password of the
superuser has been changed.
Causes
This is expected because the system stores the username and password for a task with the task
details in the database.
Capital Integration Server creates the ANSTagGeneration task with superuser credentials so the
problem occurs when the superuser password is changed.
Solution
1. Delete the currently running and future instances of the ANSTagGenerationTask in the
Tasks tab in Output Window.
2. Restart Capital Integration Server so that it re-creates the ANSTagGeneration task using
the new superuser credentials.

December 2023
ANSTagGenerationTask or ANSStaleTagCleanupTask Runs for a Long Time
ANSTagGenerationTask or
ANSStaleTagCleanupTask Runs for a Long Time
ANSTagGenerationTask or ANSStaleTagCleanupTask has a RUNNING status for a long time
in the Tasks tab displayed in the Output Window of your Capital application.
Solution
Check your Task Manager to see whether a CapitalRunner is visible in the processes.
If CapitalRunner is not visible in Task Manager:
This means the status of the task is stuck in RUNNING, when actually it is not running. For
example, this can occur if Capital Manager shut down during a forced computer restart. Reset
the task so that it starts running as per schedule again.
1. Select the task in the Tasks tab.

2. Click the cross icon at the top right of the tab.
3. Choose one of the following options:
o Deleting the Task
Deletes all records of the task.
o Marking it as Stopped
Marks the task as stopped but does not delete records of it.
4. Restart Capital Integration Server; the tasks run as per schedule again.
If Capital Runner is visible in Task Manager:
Look at the corresponding XML task parameter file and execution log file for this task
execution. The files are located in the temp directory for your Capital installation on the
computer where the task is or was being executed. The Machine column on the Tasks tab
indicates which computer this is.
If the log file reports that the task execution is complete, the status on the Tasks tab has not
updated. Reset the task as described above.
If the log file does not report that the task execution is complete, it will report any exceptions
that have occurred.

December 2023
CapitalRunner Log File Indicates Out-of-Memory Issues
CapitalRunner Log File Indicates Out-of-Memory

Issues
The CapitalRunner log file generated for a tagging task indicates that there is not sufficient
memory to complete the task.
Solution
Allocate more memory to the task. Do this in the capitalintegrationserverconfiguration.xml file
in the config directory of your installation. In the ciscontroller node, increase the value for
application_memory_alloc.
For full details of how to configure the ciscontroller node, see the “Flexible Execution Manager
(FEM)” chapter in the Capital Installation and Upgrade - Additional Information guide. The
guide is available from Support Center and with the release documents.
Tagging Tasks Have Not Started After Data

Migration
When you start Capital Integration Server for the first time after migrating your data, the
tagging tasks have not started.
Solution
Immediately after migration, Capital executes indexing tasks. All other tasks are suspended
during this time. Once the indexing tasks are complete, the tagging tasks will start executing as
per schedule.
First Tagging Task Takes a Long Time After Data

Migration
There is a reason why the first tagging task execution after a data migration may take a long
time.
Solution
This is because it is tagging all containers (designs, SBOMs, and so on). You can monitor the
progress by viewing the log messages in the corresponding CapitalRunner log file. Note that the
scheduled tagging task never runs simultaneously with this first execution. If the schedule is, for
example, every hour and the current execution is still running when the next hour arrives, it will
skip that next hour.

December 2023
First Tagging Task Takes a Long Time After Data Migration

December 2023
Chapter 12
Dialog and Field Reference
This section offers a description of the dialog boxes available in multiple Capital applications.
For each dialog box, all fields are listed, along with a full description of the field’s function.
Project-related Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
Choose Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
Copy Design Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
Create New Design Revision Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Edit Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Import Designs to Project - Copying to Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . 750
Import Designs to Project Wizard - Copying to Project Wizard Dialog Box. . . . . . . . . . . 754
New Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
Open Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
Project Folders Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
Select Designs to Copy Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
Select Project Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779
Editing Action Dialogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780
Applicable Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
Cross-references Tab (Properties Dialog Box) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
Compare Designs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
Design Rule Checks Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
Edit Assemblies Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
Edit Assembly Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
Edit Breakout/Spot Tape Details Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
Edit Design Properties Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
Edit Effectivity Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Filter Popup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
General Tab (Properties Dialog Box) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823

December 2023
Highlight Graphics Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830

Manage Designs & Effectivity Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
Map Pins Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
Name Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
New/Edit Assembly Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
Part Selection Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
Properties Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
Properties Tab (Properties Dialog Box) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
Select By Name Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
Select Color Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
Select Details Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852
Graphics Related Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 854
Add Text Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
Edit Border Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
Image Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
Symbol Selection Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
Layout Related Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
Split Table Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873
Miscellaneous Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
Applicable Changes Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
Assign ECOs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
Capital Systems Integrator or Topology Design Filter Dialog Box . . . . . . . . . . . . . . . . . . 884
Configure Import Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
Engineering Change Orders Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906

December 2023
New Property Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911

Plugins Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
Plugin Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915
Release Designs Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Printing Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
DXF Page Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925
Edit File Name Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
Print Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
Print to File Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
SVG Page Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
Rules and Constraints Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
Condition Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
Constraint Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941
Define Rules Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942
Rule Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
Collaborate Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 946
Associated Objects Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 947
Checklist Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
Comments Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
Edit Collaborate Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
Manage Notifications Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956
Notes Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957
Warning Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959
Undoable Operation Confirmation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 960
Design Log Dialogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961
Design Log Filter Options Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
Design Log Viewer Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
View Design Logs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966
Help Button Landing Pages for Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 968
Add Shared Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970

December 2023
Add Text Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971

Applicable Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
Assemblies Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
Batch Translate Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
Build Lists Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
Capital Systems Integrator or Topology Design Filter Help . . . . . . . . . . . . . . . . . . . . . . . 973
CGM Page Settings Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
Change Manager Preview ECO Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
Choose Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
Collaborate Manage Notifications Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
Collaborate Notes Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
Condition Dialog Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
Copy Design Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Design Assistant Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Design Effectivity Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Design Log Viewer Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Design Revision/Build List Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Define Rules Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Details Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
Edit Border Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
Edit Breakout/Spot Tape Details Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
Edit Build List Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
Edit Capital Configuration Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
Edit Design Properties Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
Edit Multicore or Overbraid Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Edit Objects Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Edit Print Region Groups Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
Edit Project Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
Edit Shared Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
Embedded Library Portal Import Configuration Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984

December 2023
Engineering Change Orders Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984

Freeze / Unfreeze Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
Image Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
Import Designs to Project/Copying to Project Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
Import Designs to Project Wizard/Copying to Project Wizard Help . . . . . . . . . . . . . . . . . 986
Manage Designs & Effectivity Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
Managing Collaborate Data Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
Map Equivalent Devices Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
Merge Into Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
New Folder or Rename Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
New Project Dialog Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
Open Project Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
Options (Apply ECO) Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
PDF Page Settings Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
Plugins Dialog Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
Print Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
Print to File Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
Project Usages Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992
Properties and Attributes Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992
Query Criteria Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
Release Designs Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994
Replacing Composite Symbols for Shared Objects Help . . . . . . . . . . . . . . . . . . . . . . . . . . 994
Rules and Constraints Selection Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994
Rule Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
Select by Attribute/Property Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
Select By Name Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
Select Designs to Copy Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
Select Project Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
Share Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
Split Table Dialog Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997

December 2023
Symbol Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998

Undoable Operation Confirmation Dialog Box Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
Update Symbol - Options Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
View Design Logs Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998

December 2023
Project-related Dialogs
Project-related Dialogs
This section offers a description of all dialog boxes used to open and create projects. For each
dialog box, all fields are listed, along with a full description of the field’s function.
Choose Options Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
Copy Design Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745
Create New Design Revision Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Edit Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Import Designs to Project - Copying to Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . 750
Import Designs to Project Wizard - Copying to Project Wizard Dialog Box . . . . . . . . 754
New Project Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766
Open Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767
Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 768
Project Folders Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 775
Select Designs to Copy Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777
Select Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779

December 2023
Choose Options Dialog Box
Choose Options Dialog Box

To access: Click next to a field on the Options Dialog Box.
Used to select options.
Objects
Table 12-1. Choose Options Dialog Box Contents
Field Description
Available Lists the options that are available for selection. Select the options and
click Add to move them to the Selected list. Click Add All to move all
available options to the Selected list.
Selected Lists the options that have been selected. To remove options from the
list, select them and click Remove to move them to the Available list.
To empty the list, click Remove All.
Filters Located below the Available and Selected lists.
Enter alpha/numeric text to dynamically filter the list of options to
display only options with names containing your search text.
Options in folders (and sub-folders) are included in the filtering. You
must open any non-expanded folder to see the filtered option.
The behavior of the filter varies depending on such things as whether
you use wildcards and the case (upper or lower) of the specified
characters. See “Browser Tab and Dialog Box Filters” on page 880.
Note
An option cannot have both an inclusive and exclusive relationship with another option:
• If the options in the Selected list are displayed in red it indicates that an invalid selection
has been made. If two options already have an inclusive (or exclusive) relationship you
cannot define an exclusive (inclusive) relationship for them. If an option is in a folder
that has the Mutually Exclusive check box selected you cannot add another option from
the same folder to the option’s Inclusive list.
• When you specify an inclusive relationship for two options in the same folder the
folder’s Mutually Exclusive check box becomes unavailable.
Related Topics

December 2023
Copy Design Dialog Box

To access: In a design application, right-click a design revision in the Project Browser and
select Copy. The dialog box is titled “Copy Merged Formboard Design” when accessed for
merged or combined Capital Formboard Designer designs.
Used to copy an existing design revision.
Objects
Object Description
Standard design fields This dialog box contains the standard fields used
when creating a new design.
For a Capital Harness Designer, Capital Harness
Designer Modular, or a merged Capital Formboard
Designer design, see “New Harness Design Dialog
Box” in the Capital Harness Designer User Guide.
For a Capital Systems Integrator design, see “New
Integrator Design Dialog Box” in the Capital Systems
Integrator User Guide.
For a logical design, see “New Logical Design Dialog
Box” in the Capital Logic Designer User Guide.
For a functional design, see “Creating a New Capital
Systems Modeler Design” in the Function Design in
Capital Systems Modeler User Guide.
For a Capital Wiring Integrator design, see “New
Topology Design Dialog” in the Capital Logic
Select Derivatives / Functional Modules Displayed only if you are creating a copy of a
/ Production Modules composite or modular design.
Displays the derivative or module designs that will be
included as derivatives or modules of the new design
copy.
To edit the list, click the ellipsis (...) button next to the
field; the Select Child Designs Dialog Box displays
where you can.
• Select which derivatives or modules to include.
• Configure whether the original or a new copy of
the derivative / module will be associated to the
copy of the parent.

December 2023
Object Description
Retain Generated Names Does not display if you are copying a merged or
combined formboard design.
Specifies whether object names that have been
generated using Advanced Naming are retained in the
copy (selected) or whether object names return to
Default Object Names in the copy (cleared).
Collaborate Options Opens the Edit Collaborate Design Copy Options
Dialog Box, to choose which Collaborate Data to
include in the copy of the design.

December 2023
Create New Design Revision Dialog Box
Create New Design Revision Dialog Box

To access: Right-click a design in the Project Browser window and select Create Revision.
Used to create a new design revision for a design. The dialog box is titled “Create New Merged
Formboard Design Revision” when accessed for merged or combined Capital Formboard
Designer designs.
Objects
Object Description
Standard design fields This dialog box contains the standard fields listed
when creating a design.
For a Capital Harness Designer, Capital Harness
Designer Modular, or merged Capital Formboard
Designer design, see “New Harness Design Dialog
Box” in the Capital Harness Designer User Guide.
For a Capital Systems Integrator design, see “New
Integrator Design Dialog Box” in the Capital Systems
Integrator User Guide.
For a logical design, see “New Logical Design Dialog
Box” in the Capital Logic Designer User Guide.
For a functional design, see “Creating a New Capital
Systems Modeler Design” in the Function Design in
Capital Systems Modeler User Guide.
For a Capital Wiring Integrator design, see New
Topology Design Dialog in the Capital Logic
Collaborate Options Opens the Edit Collaborate Design Copy Options
Dialog Box, to choose which Collaborate Data to
include in the copy of the design.
Select Derivatives / Functional Displayed only if you are creating a design revision
Modules / Production Modules for a composite or modular design.
Displays the derivative or module designs that are
included as derivatives or modules of the new design
revision. To edit the list, click the ellipsis (...) button
next to the field; the Select Child Designs Dialog Box
displays to select the derivatives and specify whether
new revisions are created of the derivative designs.
Usage Notes
You cannot enter a new Name but you must enter a new Revision number.

December 2023
Edit Project Dialog Box

To access: Right-click the project name in the Project Browser and select Edit.
Used to specify attributes and properties for a project.
Objects
Table 12-2. Edit Project Dialog Box Contents
Field Description
Name The unique name of the project.
Properties Click to display the Edit Properties Dialog Box where you can specify
properties for the project.
Description A description of the project.
Domain The domain for the project.
For an overview of creating and using domains, see “Domains” in the
Capital Access Manager User Guide.
For information about assigning a project to a domain, see “Domain” in
For information about assigning designs to domains, see “Domains for
Designs” in the Capital Project Manager User Guide.
Folder Enables you to specify a folder structure in which this project will be
listed in any dialog where you select a project from a tree (for example,
the Open Project dialog). You use \ as a separator between the folders
in the structure. For example, if you enter New Projects\October, the
projects tree will contain a folder New Projects with a sub-folder
October. The project that you are editing will be listed under the sub-
folder. Maximum path length is 512 characters. You can click the
ellipsis (...) button next to the field to display the Project Folders
Dialog Box where you can select an existing project folder in which
you want to list the project. You can click the red cross next to the field
to clear it. Optional.
Related Topics
Edit Properties Dialog Box

December 2023

To access: Click the Properties button on the Edit Project Dialog Box.
Used to specify properties and scopes for a project.
Objects
Table 12-3. Edit Properties Dialog Contents
Field Description
Properties Tab
Name A unique identifier for the property. Read-only.
Value The value assigned to the property. Optional.
Type The data type of the value. Mandatory. If you enter a Value that is not
supported by the selected Type, the Value is displayed in red text and the
OK button is dimmed. The following types are available:
• String - a mix of letters, number or special characters
• Integer - a whole number
• Float - a number including a decimal (floating) point
Scopes Tab This tab is used to configure the Scope Codes that apply to the project.
Available Displays a list of available scope codes that can be applied to the design.
You can select scopes in this list.
Add Moves the selected scopes in the Available window to the Selected
window.
Add All Moves all scopes in the Available window to the Selected window.
Remove Moves the selected scopes in the Selected window to the Available
window.
Remove All Moves all scopes in the Selected window to the Available window.
Selected Displays the names of the scopes applied to the project.
Usage Notes
To add a property to the project, click the New button, enter a Property Name in the New
Property Dialog Box, and then click OK. The new property is added to the list. To delete a
property from the list, select it and click the Delete button, and then click OK to confirm the
deletion.
Related Topics

December 2023
Import Designs to Project - Copying to Project

Dialog Box
To access: Click File > Import from the menu and select a design XML file to import.
Alternatively, in Capital Project Manager right-click a design folder or specific designs in
the Project Browser Tree and select Copy Advanced or Copy > Advanced. In a design
tool, select a design folder or specific designs in the Project Browser Window at the top left
of the application window, press Space Bar and enter Copy Advanced.
Used to specify details for designs when importing them into a project in the database or when
copying them from one project to another within the database.
Objects
Table 12-4. Import Designs to Project/Copying to Project Dialog Box Contents
Field Description
Target Project Displayed only when you are importing a design using File >
Import from the menu.
Displays the name of the project into which you are importing
designs. To import the designs into a project other than the one
that is open, click the ellipsis (...) next to the field to display
the Select Project Dialog Box, and select a different project.
Mandatory.
Source Project The name of the project from which the design was exported.
Read-only.
Source Design The name of the design in the source project. Read-only.
Name A unique label to identify the design in the target project.
Enter a new name. The contents of this field display in red if
they are not unique within the project. Mandatory.
Short Description Enter a line of descriptive text to provide more information
about the design. Optional.
Description This is a free-text field used to enter additional comments or
notes relevant to this design. Optional.
Revision Specifies the design revision, allowing multiple updated
versions of the same design to exist in the database. When
creating a new design, the initial version number or letter
should be entered. Subsequent revisions receive a new
revision number as part of their creation. Mandatory.
Release Level Specifies the Release Level of the design. Mandatory.
Abstraction If you are using Design Abstractions, select the abstraction to
which the design belongs, from the dropdown list. Optional.

December 2023

Field Description
Effectivity Displayed only if Effectivity is enabled in the target project
and if Copy Effectivity is selected.
Displays the effectivity range that is applied to the design.
Part Number Enabled only for a Capital Harness Designer design.
Specify a unique identifier for the harness in the database. The
combination of this field and the revision must be unique
within the database; if the combination already exists, the
contents of both fields display in red. Mandatory.
There are two ways to ensure uniqueness for the part number
of the new design:
• Overwrite the part number with a new, unique number.
• Enter a new code in the Revision field. Note that entering a
new revision code does not result in the copied design
being created as a revision of the existing design; to create
the copy as a revision, you must select the Copy As
Revision option.
Overwrite If a design revision with the name exists in the target project
already, specify whether you want to overwrite the existing
design revision (selected) or not (cleared). An import of a
design with an existing name is possible only when this is
selected. Mandatory if a design with the same name exists.
Location Denotes the physical location in the product where the
design’s content resides.
Function Denotes the function that should be achieved in the product
through the design.
Folder Specify the design folder path to locate the design in the target
project.

December 2023

Field Description
Copy As Revision Select to create a copy of the design with the same name, as a
revision of the source design in the target project.
You can edit the short description, but you must edit the
revision level to ensure that a new revision is created in the
target project. The system records the number of revisions that
are created to retain a revision hierarchy. If a revision of the
design already exists in any project, you must specify the next
available revision level.
If cleared, the design is created as a new design in the target
project and any relationship with the source design and the
revision hierarchy is lost. You can specify a new name, but it
must not conflict with an existing design name in the target
project.
This option also affects the copying of shared conductors and
pin lists on the diagram. If selected, all copied shared objects
retain their parent-child revision relationships. If cleared, any
revision relationships are lost, and the copied objects are
created as new shared objects in the target project, with a
default revision of 1.
Optional.
Unfreeze New Shared Objects Select if you want all new shared objects (created by the Copy
Advance or Import Design process) to be in an unfrozen state.
If cleared, new shared objects are created in the same frozen or
unfrozen state as the source objects. That is, if the source
shared object is frozen so is the new shared object.
Note: If the source design has shared objects frozen, and
target project has same shared objects in an unfrozen state,
this option is disabled. It is also disabled if the source design is
a released design with the release level behavior "Frozen
Shared Objects" selected.
This setting does not impact any pre-existing shared objects.
Copy Effectivity Displayed only if Effectivity is enabled in the target project.
If selected, any effectivity ranges assigned to the designs are
copied with them.
Collaborate Options Opens the Import Designs to Project - Copying to Project
Dialog Box that lets you select which types of Collaborate
data are included in the import.

December 2023

Field Description
Advanced Opens the Import Designs to Project Wizard - Copying to
Project Wizard Dialog Box that offers you advanced options
when importing designs into a project (either from outside of
the database or from another project in the database).
Optional.
Related Topics
Select Project Dialog Box

December 2023
Import Designs to Project Wizard - Copying to

Project Wizard Dialog Box
To access: Click the Advanced button on the Import Designs to Project/Copying to Project
dialog box.
Used to specify advanced options when importing designs into a project or when copying
designs from one project to another, or to the same project. This also helps support copy/paste
modify flows when working with Capital Systems Architect and Capital Systems Integrator
diagrams.
Objects
Table 12-5. Import Designs to Project Wizard/Copying to Project Wizard Dialog
Box Contents
Field Description
Design Abstractions Tab Displayed only if you accessed this dialog box by clicking the
Advanced button on the Import Designs to Project - Copying
to Project Dialog Box.
Used to map design abstractions from the source designs
(designs being copied or imported) to the design abstractions
in the target project. Mandatory.
Source Design Abstractions Design Abstraction column lists the Design Abstractions from
the source designs (designs being copied).
Mapped column indicates the design abstraction (in the Target
Project Design Abstractions) to which the source design
abstraction is mapped. If blank, this means the design
abstraction is not mapped.
If a design abstraction exists in both the source designs and the
target project, it is mapped automatically.
If a design abstraction exists just in the source designs, it is
created automatically in the Target Project Design
Abstractions and the abstraction from the source designs is
mapped to it.
Note that you can map two design abstractions from the source
designs to one design abstraction in the target project.
Associate Creates a mapping between the currently-selected design
abstractions in the Source Design Abstractions and Target
Project Design Abstractions fields.
Dis-Associate Clears the currently-selected mapping in the Source Design
Abstractions and Target Project Design Abstractions fields.

December 2023

Box Contents (cont.)
Field Description
Auto Associate Maps any unmapped design abstractions in the Source Design
Abstractions to design abstractions with matching names in
the Target Project Design Abstractions.
Auto Create Creates Target Project Design Abstractions for unmapped
Source Design Abstractions and maps them to each other.
Clear Associations Clears all mappings in the Source Design Abstractions and
Target Project Design Abstractions fields.
Target Project Design Design Abstraction column lists the design abstractions in the
Abstractions target project (to which the designs are being copied or
imported).
Mapped column indicates the design abstraction (in the Source
Design Abstractions) to which the target design abstraction is
mapped. If blank, this means the design abstraction is not
mapped.
If a design abstraction exists in both the source designs and the
target project, it is mapped automatically.
If a design abstraction exists just in the source designs, it is
created automatically in this table and the abstraction from the
source designs is mapped to it.
Note that you can map two design abstractions from the source
designs to one design abstraction in the target project.
Design Details Tab
Design Details Table Lists the source projects and source designs along with the
details for the new designs that are created in the target
project. Click a row to select a source design and the details of
its target design; the fields below the table are updated to
display the existing values.
New Not enabled in this dialog box.
Update Updates the selected row in the Design Details table with the
contents of the fields below it.
Reset Returns the cells in the Design Details table to their previous
state. This means that:
• If you are editing an existing row for a design, the fields
are returned to their previous values.
Delete Not enabled in this dialog box.

December 2023

Field Description
Name A unique label to identify the design in the target project.
Enter a new name or click the ellipsis (...) button to the right of
the field to select from a list of pre-specified design names
maintained in the project’s Object Type Information. The
contents of this field display in red if they are not unique
within the current project. Mandatory.
Part Number Enabled only if a Capital Harness Designer design is selected
in the Design Details table.
Specify a unique identifier for the harness in the database. The
combination of this field and the revision must be unique
within the database; if the combination already exists, the
contents of both fields display in red. Mandatory.
There are two ways to ensure uniqueness for the part number
of the new design:
• Overwrite the part number with a new, unique number.
• Enter a new code in the Revision field. Note that entering a
new revision code does not result in the copied or imported
design being created as a revision of the existing design; to
create the copy as a revision, you must select the Copy As
Revision option.
Revision Specifies the design revision, enabling multiple updated
versions of the same design (and, therefore, the same part
number) to exist in the database. When creating a new design,
the initial version number or letter should be entered.
Subsequent revisions receive a new revision number as part of
their creation.
The combination of this field and the part number must be
unique within the database; if the combination already exists,
the contents of both fields display in red. Mandatory.
about the derivative design. Optional.
Release Level The Release Level for the design. Mandatory.
Location Denotes the physical location in the product where the
design’s content resides.
Function Denotes the function that should be achieved in the product
through the design.

December 2023

Field Description
Design Abstraction If you are using Design Abstractions, select the abstraction to
which the design belongs, from the dropdown list. Maintained
in Capital Project Manager, abstractions enable you to group
related harnesses together for reporting purposes, providing a
“view” of a subset of a vehicle’s wiring. Optional.
Folder Specify the Design Folder path under which you want the
design to be located in the target project.
Design Attribute Constraint See the Design Attributes and Properties Constraints
Overview topic in the Capital Harness Designer User Guide
Apply
This video shows how to use constraints when importing child
harness designs.
Copy Associated Logic A design can have one or more associated Capital Logic
Designs Designer designs. This check box specifies whether these
(Visibility of this field depends associated designs are copied with this design (selected) or not
on which product you are (cleared). Mandatory.
using)
Copy Associated Function A platform design can have one or more associated function
Designs designs. This check box specifies whether these associated
(Visibility of this field depends designs are copied with this design (selected) or not (cleared).
on which product you are Mandatory.
using)
Effectivity Displayed only if Effectivity is enabled in the target project.
Displays the effectivity range that is applied to the design.
Copy Generated Wiring A Capital Systems Integrator design may have had wiring
generated for it. This check box specifies whether you want to
copy the generated wiring with the design (selected) or not
(cleared). Mandatory.
Overwrite Revision If a design revision with the name exists in the target project
already, specify whether you want to overwrite the existing
design revision (selected) or not (cleared). An import of a
design with an existing name is possible only when this is
selected. Mandatory if a design with the same name exists.

December 2023

Field Description
Copy As Revision Select to create a copy of the design with the same name, as a
revision of the source design in the target project.
You can edit the short description, but you must edit the
revision level to ensure that a new revision is created in the
target project. The system records the number of revisions that
are created to retain a revision hierarchy. If a revision of the
design already exists in any project, you must specify the next
available revision level.
If cleared, the design is created as a new design in the target
project and any relationship with the source design and the
revision hierarchy is lost. You can specify a new name, but it
must not conflict with an existing design name in the target
project. Any subsequent revision of this design from source
will not be created as revision in the target project.
This option also affects the copying of shared conductors and
pin lists on the diagram. If selected, all copied shared objects
retain their parent-child revision relationships. If cleared, any
revision relationships are lost, and the copied objects are
created as new shared objects in the target project, with a
default revision of 1.
Note: It is recommended to keep this option selected.
Optional.
Shared Conductors Tab Used to configure the shared conductors used by the selected
designs.

December 2023

Field Description
Shared Conductors Table Lists the shared conductors in the source designs.
If the designs being copied or imported contain any shared
conductors, but the target project does not possess any shared
conductors, the shared conductors are copied automatically to
the target project and are listed for reference only in this table.
If the designs being copied or imported contain any shared
conductors, and the target project contains shared conductors,
you can select to:
• Copy a source shared conductor to the target project
without associating it with a target shared conductor.
Select the source shared conductor in the table, select
Copy Shared Conductor, and then click Update. The
Copy Shared Conductor column displays Yes.
• Choose to not copy a source shared conductor to the target
project, but instead associate it with one in the target
project.
Select the source shared conductor in the table, clear Copy
Shared Conductor, specify a Project Shared Conductor
and then click Update. The Copy Shared Conductor
column displays No. Note that you can only associate
shared conductors of the same type (for example, net with
net, wire with wire).
New Not used.
Update Updates the selected row in the Shared Conductors table with
the contents of the fields below it.
Reset Returns the cells in the Shared Conductors table to their
previous state.
Delete Not used.
Shared Conductor The name and revision of the shared conductor from the
source designs. Read-only.
Project Shared Conductor The name and revision of the shared conductor (from the
target project) that is associated with the shared conductor.
Select the target shared conductor from the dropdown list.
Mandatory only if Copy Shared Conductor is cleared.

December 2023

Field Description
Copy Shared Conductor Specifies whether the source shared conductor that is selected
in the Shared Conductors table is copied to the target project
(selected) or whether it is not copied but is associated with a
shared conductor in the target project (cleared). If not copied,
the target shared conductor is specified by Project Shared
Conductor. Mandatory.
Shared Pin Association
Defaults Tab
Automatic Association If the designs being copied or imported contain any shared pin
Configuration Mode lists, this option specifies the method of association between
the pins on the source designs and the pins in the target
project:
• Merge Unrestricted pins - reuse existing pins where there
is a match between names. Unrestricted pins remain
unrestricted. If a reserved pin is used in more than one
design being copied or imported, it becomes unrestricted.
• Merge Reserved pins - always reuse existing pins where
there is a match between names. Unrestricted pins remain
unrestricted. Manually reserved pins remain manually
reserved to designs where used. Automatic reservation
pins remain as reserved pins and their usages are updated
with all copied or imported designs.
By default, ‘Merge Reserved Pins’ option is selected.
Shared Pin Lists Tab Enables you to associate shared pin lists and their pins from
the source designs with shared pin lists in the target project.
Associate Pin Lists Used to associate shared pin lists in the source designs with
shared pin lists in the target project.

December 2023

Field Description
Source Design Table Source Design column lists the shared pin lists from the source
designs (designs being copied).
Mapped to column indicates the shared pin list (in the Target
Project table) to which the source shared pin list is mapped. If
blank, this means the shared pin list is not mapped.
The following rules apply to the mapping of pin lists:
• You can map a pin list on the source design only to one of
the same type on the target project (that is, device to
device, plug to plug, and so on).
• You can map a shared inline pin list to only a target inline
pin list that possesses the same, or a greater number of
pins.
• Any target pin lists that are not permitted to be mapped to
the selected source pin list, are unavailable for selection
(dimmed).
• Before you can proceed to the next tab, you must have
mapped all of the pin lists (and their pins) on the source
design, with pin lists on the target project.
See “Rules for Shared Objects When Copying, Importing or
Exporting Designs” in the Capital Project Manager User
Guide for further information about rules that apply to shared
objects.
Associate Maps the selected shared pin list in the Source Design table to
the selected shared pin list in the Target Project table.
Disassociate Clears the currently-selected mapping in the Source Design
table and Target Project table fields.
Disassociate All Clears all mappings in the Source Design table and Target
Project table fields.
Associate All Creates mappings for all shared pin lists in the Source Design
table.

December 2023

Field Description
Target Project Table Target Project column lists the shared pin lists in the target
project (to which the designs are being copied or imported).
Mapped from column indicates the shared pin list (in the
Source Design table) to which the target shared pin list is
mapped. If blank, this means the shared pin list is not mapped.
The following rules apply to the mapping of pin lists:
• If you have selected Automatically Associate on the
Shared Pin Association Defaults tab, pins are
automatically associated when pin lists are associated.
• You can map a pin list on the source design only to one of
the same type on the target project (that is, device to
device, plug to plug, and so on).
• You can map a shared inline pin list to only a target inline
pin list that possesses the same, or a greater number of
pins.
• Any target pin lists that are not permitted to be mapped to
the selected source pin list, are unavailable for selection
(dimmed).
• Before you can proceed to the next tab, you must have
mapped all of the pin lists (and their pins) on the source
design, with pin lists on the target project.
See “Rules for Shared Objects When Copying, Importing or
Exporting Designs” in the Capital Project Manager User
Guide for further information about rules that apply to shared
objects.
Add Adds a new shared pin list to the Target Project table and
maps the selected shared pin list in the Source Design table to
it. The new shared pin list is named using the Source Object
Names for the target project.
Remove Removes the selected shared pin list from the Target Project
table.
Associate Pins Used to associate pins from the selected shared pin list in the
Source Design table with pins from the associated shared pin
list in the Target Project table.

December 2023

Field Description
Source Pins Table Once you have associated a source shared pin list (Source
Design table) with a target shared pin list (Target Project
table), you can associate their pins.
Source Pins column lists the shared pins from the source pin
list selected in the Source Design table.
Mapped to column indicates the shared pin (in the Target Pins
table) to which the source shared pin is mapped. If blank, this
means the shared pin is not mapped.
If there are duplicate pin names in a pin list, you can double-
click a pin in a table to display the attributes for the pin.
Associate Maps the selected shared pin in the Source Pins table to the
selected shared pin in the Target Pins table.
Disassociate Clears the currently-selected mapping in the Source Pins table
and Target Pins table fields.
Disassociate All Clears all mappings in the Source Pins table and Target Pins
table fields.
Associate All Creates mappings for all shared pins in the Source Pins table.
Target Pins Table Once you have associated a source shared pin list (Source
Design table) with a target shared pin list (Target Project
table), you can associate their pins.
Target Pins column lists the shared pins in the target pin list
selected in the Target Project table.
Mapped from column indicates the shared pin (in the Source
Pins table) to which the target shared pin list is mapped. If
blank, this means the shared pin list is not mapped.
If there are duplicate pin names in a pin list, you can double-
click a pin in a table to display the attributes for the pin.
Add Adds a new shared pin to the Target Pins table and maps the
selected shared pin in the Source Pins table to it. The new
shared pin is named using the source object naming protocol
for the target project.
Remove Removes the selected shared pin from the Target Pins table.
Pin Reservations Enables you to specify whether the pins listed in the Target
Pins table are automatic reservation or unrestricted.
Automatic Reservations Table List any automatic reservation pins from the Target Pins table.

December 2023

Field Description
Add Converts the selected automatic reservation pin in the
Automatic Reservations table to an unrestricted pin and moves
it to the Unrestricted Pins table. You can select multiple pins
by using the Shift or Ctrl keys with your mouse.
Add All Converts all automatic reservation pins in the Automatic
Reservations table to unrestricted pins and moves them to the
Unrestricted Pins table.
Remove Converts the selected unrestricted pin in the Unrestricted Pins
table to an automatic reservation pin and moves it to the
Automatic Reservations table. You can select multiple pins by
using the Shift or Ctrl keys with your mouse.
Remove All Converts all unrestricted pins in the Unrestricted Pins table to
automatic reservation pins and moves them to the Automatic
Reservations table.
Unrestricted Pins Table List any unrestricted pins from the Target Pins table.
Translation Tab Used to specify whether you want to translate component
codes (for example, color codes) and component part numbers
during the import. You must have created Code Translations
before the import.
Translate Codes Select to apply the code translations defined for the target
project to the imported component data.
Translate Parts Select to translate component part numbers in the imported
data to supplier or customer part numbers. Note that this only
updates the string in the Library Part attribute of the
component in the design. It does not create an association
between the component in the design and the matching library
part in your component library. To create an association, you
must run a batch update of library parts on the imported
designs after the import. See “Performing a Batch Update of
Library Parts” on page 636.
Summary Tab Displays a summary of the options that you have selected in
the wizard.
Back Displayed at the bottom of the dialog box.
Click to return to the Import Designs to Project - Copying to
Project Dialog Box.
Related Topics

December 2023


December 2023
New Project Dialog Box
New Project Dialog Box

To access: Press Space Bar and enter New Project.
Used to specify the name for a project.
Objects
Table 12-6. New Project Dialog Box Contents
Field Description
Name Enter a unique identifier for the project. If you enter a name already in
use by a project in the database, upon clicking OK, a message is
displayed to warn you and you are prevented from proceeding.
Create Select to create a design in the new project. In the dropdown list, select
the type of design. If selected, a New Design dialog is displayed when
you click OK. Optional.

December 2023
Open Project Dialog Box
Open Project Dialog Box

To access: Press Space Bar and enter Open. Otherwise opened automatically when starting the
application for the first time when On Startup is set to Display Open Project dialog box.
Used to select a project to open.
Objects
Table 12-7. Open Project Dialog Box Contents
Field Description
Create New Project Select to create a new project. Optional, displayed only when starting
application for the first time when On Startup is set to Display Open
Project dialog box.
Create Select to create a design in the new project. In the dropdown list, select
the type of design. If selected, a New Design dialog box is displayed
when you click OK. Optional, enabled only if Create New Project is
selected.
Open Existing Project Select to open an existing project. Select the project in the window.
Optional.
On Startup Specifies whether a project opens by default the next time that you start
the application. Mandatory.
You can select the following:
• Always open last project
The last project that you opened in the application opens
automatically.
• Display Open Project Dialog
The Open Project dialog box is opened automatically.
• Do nothing
No project opens and the Open Project dialog box is not opened
automatically.
You can filter which projects display by entering a string in the field
where the Enter Filter String icon ( ) displays. Only projects whose
name contain that string display. To display all projects again, click the
Clear Filter String icon ( ).
Note: Wildcards can be used when filtering projects, see “Browser
Tab and Dialog Box Filters” on page 880.

December 2023
Options Dialog Box
Options Dialog Box

To access: In a design application, with a project open press Space Bar and enter Data - Options.
In Capital Project Manager, expand the Option Maintenance folder (either in the System
tree or in a project tree) and double-click the Options node.
Used to define option relationships within a project or at system level.
Figure 12-1. Options Dialog Box

December 2023
Options Dialog Box
Objects
Table 12-8. Options Dialog Box Contents
Field Description
Options Browser Located at the left of the dialog box. Blank when no options exist.
Displays a tree of options ( ), variant options ( ), non-electrical
options ( ) and obsolete options ( ) grouped within option folders
( ). Folders whose options have mutually exclusive ( ) or
mandatory ( ) relationships are indicated with green and red check
marks respectively. When you edit options at project level, option
combinations ( ) are listed too.
When you select an option folder, option combination or option in
the tree, details for the selected item are displayed in fields on the
right of the dialog box.
You can drag and drop items in the tree to:
• Change their order. Dragging an option or folder to a space
between two other items moves it there. Dropping an option or
folder over a folder adds it as the last child node of that folder.
• Add an option to an option combination. In this case, the option
is copied in the tree.
The order that options and option folders are listed in the Options
Browser is used when they are listed in other dialog boxes in Capital
applications.
Filter
Located below the Options browser.

Enter alpha/numeric text to dynamically filter the list of options to
display only options with names containing your search text.
Options in folders (and sub-folders) are included in the filtering. You
must open any non-expanded folder to see the filtered option.
characters. See “Browser Tab and Dialog Box Filters” in the Capital
Design Tools - Common Functions User Guide.
Note: When you enter text into the filter, all editing functionality
on the right-hand side of the dialog box is automatically
unavailable. You must clear the filter text ( ) to re-enable editing
functionality.

December 2023
Options Dialog Box
Table 12-8. Options Dialog Box Contents (cont.)

Field Description
Delete selected objects Keyboard shortcut: Delete
• Deletes option folders and option combinations that are selected
in the Options Browser.
• Deletes options that are selected in the Options folder of the
Options Browser.
• Removes options that are selected in the Combinations folder of
the Options Browser from the option combination that they are
in.
Create a new Option Keyboard shortcut: Ctrl+O
Creates a new option in the Options Browser. If a folder is selected
in the tree the new option is added to the folder; if an option is
selected in the tree the new option is added below it.
Unavailable when the Combinations folder or a combination is
selected.
Create a new Folder Keyboard shortcut: Ctrl+F
Creates a new option folder in the Options Browser. If a folder is
selected in the tree the new folder is added as a sub-folder of the
selected folder; if an option is selected in the tree the new folder is
added below it.
Unavailable when a folder whose options have mutually exclusive
and/or mandatory relationships is selected. Unavailable when the
Combinations folder or a combination is selected.
Create a new Creates a new option combination node he Options Browser. If a
Combination combination is selected in the tree, the new combination is added
below it.
Only available when the Combinations folder or an existing
combination is selected. Unavailable at system level in Capital
Project Manager.

December 2023
Options Dialog Box

Field Description
Sort options by name /
Sort options by
description / Sort
selected folders by name Keyboard shortcut: Ctrl+S
/ Sort selected folders by
description Sorts the contents of the selected folders alphanumerically. Sorting
with multiple folders selected sorts the contents of each selected
folder; sorting with the Options folder selected sorts all the option
folders and options in the tree.
There are three ways of sorting:
• By name: click the button dropdown and select Sort options by
name or Sort selected folders by name. Options and option
folders are sorted by name. Clicking the button reverses the sort
order.
• By description: click the button dropdown and select Sort
options by description or Sort selected folders by description.
Options are sorted by description and option folders are sorted by
name. Clicking the button reverses the sort order.
• Using the keyboard shortcut Ctrl+S: if option descriptions are
displayed options are sorted by description, otherwise options are
sorted by name; option folders are sorted by name.
Tip: You can toggle the display of option descriptions by
pressing Space Bar and entering Show Option/Module
Description in a design application or by toggling the
View > Show Option/Module Description option in Capital
Project Manager.
The sorting action behaves as follows:
• All options (including variant options, non-electrical options and
obsolete options) are considered equivalent for the purpose of
sorting.
• Each selected folder (including the root Options folder) is sorted
recursively, that is, sub-folders in selected folders are also sorted.
• If no folder is selected, the sorting behaves as though the root
Options folder is selected.
• Folders and options are sorted as two groups whereby folders
always appear above options.
• When content is already sorted, clicking the button without
selecting an option from the dropdown reverses the sort order.
Note: The sort order of the options is retained when you close the
dialog box by clicking OK, even when the Product Planner
application has been enabled in Capital Systems Integrator. The
order that options and option folders are listed in this dialog box is
used when they are listed in other dialog boxes in Capital
applications.
Unavailable
Capital Design Tools - Common Functions when2207
User Guide, an option, empty folder, a combination or the 771
December 2023 Combinations folder is selected.
Options Dialog Box

Field Description
Name Specifies the identifier for the selected option folder, option
combination or option in the Options Browser. Mandatory.
Description Specifies a descriptive string for the option selected in the Options
Browser. Optional, enabled only for an option.
Group Specifies particular relationships between the options in the folder
selected in the Options Browser. Optional, displayed only for an
option folder and available only for option folders that do not have
sub-folders.
The following options are available:
• Mutually Exclusive
Indicates that none of the options within this folder can be
selected together in a vehicle. Unavailable if an inclusive
relationship has already been specified for two or more options
in the folder.
• Mandatory
Indicates that at least one of the options within this folder must be
selected in a vehicle.
Electrical Specifies whether the option selected in the Options Browser is
electrical (in other words, it impacts the electrical connectivity of the
vehicle). Some options (for example, seat coverings) do not involve
any electronic components.
Non-electrical options are only of interest in vehicle configurations
in Capital Configuration Optimizer. They are not displayed
elsewhere in the applications.
New options are created as electrical as default. Migrated, legacy
options are electrical by default.
Electrical options have the icon .
Non-electrical options have the icon .
Displayed only for an option.
Caution: If an option in an option combination is changed to be
a non-electrical option it is removed from the option combination
when you click OK.
Caution: If an option in a mutually exclusive or mandatory
folder is changed to be a non-electrical option it is removed from
the folder when you click OK.
Obsolete Specifies whether the option selected in the Options Browser is
obsolete, and can not be used. Displayed only for an option.

December 2023
Options Dialog Box

Field Description
Variant Specifies whether the option selected in the Options Browser is a
variant option (selected) or not (cleared). Mandatory, displayed only
for an option.
Inclusive Lists the options that are required with the option selected in the
Options Browser. Optional, displayed only for options at project
level in applications. Unavailable at system level in Capital Project
Manager.
Click to display the Choose Options Dialog Box where you select
the inclusive options.
To remove an option from the Inclusive list, select it and click .
Exclusive Lists the options that cannot be used with the option selected in the
Options Browser. Optional, displayed only for options at project
level in applications. Unavailable at system level in Capital Project
Manager.
Click to display the Choose Options Dialog Box where you select
the exclusive options.
To remove an option from the Exclusive list, select it and click .
Valid Selections Lists the options in the option combination selected in the Options
Browser; each option is a column in the table. A row represents a
valid selection of the options. Click Insert a row( ) to add a row to
the table. Click Remove the selected rows( ) to delete a row from
the table. Within a row select the options to be included in that valid
selection. The Name column specifies unique identifiers for the valid
selections. Available only for option combinations at project level in
applications. Unavailable at system level in Capital Project
Manager.
Usage Notes
When you add an option to another option’s Exclusive list, the corresponding exclusive
relationship is automatically created in the first option’s Exclusive list. For example, if Option
A cannot be selected with Option B, it follows that Option B cannot be selected with Option A,
so when Option A is added to Option B’s Exclusive list Option B is automatically added to
Option A’s exclusive list.
However, if two options both have an inclusive relationship with each other you need to
manually add each option the other option’s Inclusive list. This is because it is possible for one
option to have an inclusive relationship with another option without the other option necessarily
having an inclusive relationship with the first option. For example, Option B may only be
available if Option A has also been selected, but Option A may be available without selecting
Option B.

December 2023
Options Dialog Box
Related Topics

December 2023
Project Folders Dialog Box
Project Folders Dialog Box

To access: Click the ellipsis (...) button next to the Folder field on the Edit Project Dialog Box.
Used to select a project folder in which you want a project to be listed in any dialog where you
select a project from a tree (for example, the Open Project dialog). Also, used to create, delete,
or rename project folders.
Objects
Table 12-9. Project Folders Dialog Box Help
Field Description
Project Tree Select the one in which you want the project to be listed and click OK.
New To create a new folder, right-click a folder node in the project tree and
select New; a new sub-folder is created below the selected folder.
Rename To rename a folder, right-click a folder and select Rename.
Delete To delete a folder, right-click a folder and select Delete.
Usage Notes
You cannot rename or delete a project folder that contains a project. If you want to place a
project in a differently named folder, create that folder and select it. Any unused folders do not
display when you next open this dialog box.
Related Topics

December 2023
Project Preferences Dialog Box
Project Preferences Dialog Box

To access: In the design applications, press Space Bar and enter Project Preferences. In Capital
Project Manager, open a project, expand the Project Browser Tree for that project and
double-click the Preferences node.
Used to specify the Project Preferences for the currently open project.
Objects
Table 12-10. Fields in the Project Preferences Dialog Box
Field Description
Project Preferences Located on the left of the dialog box, use to select the type of project
browser preferences to edit. The corresponding project preferences are
displayed in Project Preferences pane on the right of the dialog box.
Project Preferences Located on the right of the dialog box, this displays the project
pane preferences for the type selected in the Project Preferences browser.
For full descriptions of the preferences see:
• Project Preferences for Capital Analysis Designs
• Project Preferences for Manufacturing Tools
• “Project Preferences for Capital Device Modeler” on page 133
• Project Preferences for Capital Harness Designer and Capital
Harness Designer Modular Designs
• Project Preferences for Capital Systems Integrator Designs
• Project Preferences for Capital Logic Designer Designs
• Project Preferences for Capital Wiring Integrator Designs
• Project Preferences for Capital Systems Modeler Designs
• Project Preferences for Platform Designs in Capital Systems
Architect
• Project Preferences for Design Release
• General Project Preferences Applicable to all Applications
• Project Preferences - Checks Node

December 2023
Select Designs to Copy Dialog Box

To access: In Capital Project Manager: Right-click a design folder or specific designs in the
Project Browser Tree and select Copy Advanced or Copy > Advanced. In a design tool:
Press Space Bar and enter Copy Advanced. Note that you can select a design folder or
specific designs in the Project Browser Window at the top left of the application window
when doing this but do not have to.
Used to select designs that you want to copy into a particular target project.
Objects
Table 12-11. Select Designs to Copy Dialog Box Contents
Field Description
Available Designs Lists the build lists and designs that are available to copy.
Select a design or a design folder and click Add to move the design or
the designs within the folder to the Designs to Copy window.
Any designs that you have selected for copy already are dimmed.
Designs to Copy Lists the designs that are currently selected to be copied.
When this dialog box opens, the designs listed depend on the designs
or design folders that were selected when you started the Copy
Advanced action:
• If you selected a Capital Systems Integrator design to be copied,
any associated Capital Logic Designer designs are also listed.
• If you selected a build list, all designs from the build list are listed.
• If you selected a design folder containing multiple designs, all of
those designs are listed.
• If you selected a Capital Harness Designer composite design, all
derivatives are listed.
Select a design or a design folder and click Remove to move the
design or the designs within the folder to the Available Designs
window.
Target Project Click the ellipsis (...) button to the right of this field to display the
Select Project Dialog Box where you select the target project to which
you are copying the designs.
Enter Filter String In the field next to the Enter Filter String icon, enter a series of
characters. A filter is applied to the Available Designs windows so
Clear Filter String that only designs with names containing that series of characters are
listed.
characters. See “Browser Tab and Dialog Box Filters” on page 880 for
further information.

December 2023
Table 12-11. Select Designs to Copy Dialog Box Contents (cont.)

Field Description
Keep Release Level Check to include any release level data associated with the selected
Settings design(s) in the copy.
Design Filter Click the dropdown list to filter the designs displayed in the Available
Designs window to those of a particular type.
Related Topics

December 2023

To access: Click the ellipsis (...) button next to the Target Project field in the Import Designs to
Project/Copying to Project dialog box. Alternatively, in Capital Project Manager choose
File > Export > Select Project from the menu. In design applications, press Space Bar and
enter Select Project to Export.
Used to select a project.
Objects
Select the project from the tree.
Related Topics
Exporting a Project

December 2023
Editing Action Dialogs

This section offers a description of various dialog boxes used for editing designs and objects.
For each dialog box, all fields are listed, along with a full description of the field’s function.
Applicable Options Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782
Cross-references Tab (Properties Dialog Box) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785
Compare Designs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 786
Design Rule Checks Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795
Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798
Edit Assemblies Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 799
Edit Assembly Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 800
Edit Breakout/Spot Tape Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 802
Edit Design Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
Edit Effectivity Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Filter Popup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
General Tab (Properties Dialog Box). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
Highlight Graphics Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 830
Manage Designs & Effectivity Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831
Map Pins Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
Name Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
New/Edit Assembly Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
Part Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840
Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
Properties Tab (Properties Dialog Box). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
Select By Name Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
Select Color Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851

December 2023
Select Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 852


December 2023
Applicable Options Dialog Box
Applicable Options Dialog Box

To access: Click the Applicable Options ellipsis button (...) in the following dialog boxes:
• Edit Design Dialog Box
• New Harness Design Dialog Box
• New Derivative Harness Design Dialog Box
• Design tab in the Generate Wiring Diagram Dialog Box
• Design tab in the Autoview Query and Generate Design dialog boxes
Used to select the options that you can assign to an object.
Objects
Table 12-12. Applicable Options Dialog Box Contents
Field Description
Applicable Options • Available
Lists the options that are available. Select the options that can be
assigned to the object that you are editing and click Add to move
them to the Selected list. Click Add All to move all available
options to the Selected list.
• Selected
Lists the options that can be assigned to the object that you are
editing. To remove options from the list, select them and click
Remove to move them to the Available list. To empty the list, click
Remove All.
Filter Located below the Available and Selected lists. Enter a series of
characters. A filter is applied to the list so that only codes with names
containing that series of characters are listed. For a description of how
to use wildcards when filtering see “Browser Tab and Dialog Box
Filters” on page 880.

December 2023
Connections Tab (Properties Dialog Box)

To access: In Capital Logic Designer, Capital Systems Integrator, or Capital Wiring Integrator,
double-click a wire in the diagram window. Alternatively, select a wire, then press Space
Bar and enter Properties or right-click an object and choose Properties. Click the
Connections tab.
Used to edit and view the connector cavity part drivers for a wire (terminal material, terminal
part, seal part) in Capital Logic Designer and Capital Systems Integrator.
Note
You can view this tab in Capital Wiring Integrator, but not edit it.
Objects
Table 12-13. Connections Tab (Properties Dialog Box) Contents
Object Description
End 1 / End 2 Indicates the wire end represented by the column.
Note: For a shared wire in a Capital Logic Designer design where
only one end of the wire is connected, only one column is enabled.
A message displays at the bottom of the tab: Connections from other
designs are not shown
Terminal Details Displays details of the termination, such as: slot, connector, cavity.
Note: For variant wires in Capital Systems Integrator, these details
can include multiple, refined connectors.
Terminal Material Unavailable if the end is at a splice. If you select a terminal part, this
field is filled automatically and cannot be edited.
Select the material required for the terminal from the dropdown list.
Terminal Part Unavailable if the end is at a splice.
The library part for the terminal. Either type the part name or click the
Add (...) button to display the Part Selection dialog box. The part
number displays in red if it does not yet exist in your library.
You can unassign the part by clicking the Delete ( ) button.
You can view the library part details by clicking the View ( ) button.
Seal Part Unavailable if the end is at a splice.
The library part for the seal. Either type the part name or click the Add
(...) button to display the Part Selection dialog box. The part number
displays in red if it does not yet exist in your library.
You can unassign the part by clicking the Delete ( ) button.

December 2023
Related Topics
Systems Integrator

December 2023
Cross-references Tab (Properties Dialog Box)
Cross-references Tab (Properties Dialog Box)

To access: Double-click an object in the Diagram window. Alternatively, select an object then
press Space Bar and enter Properties or right-click an object and select Properties. Click the
Cross-references tab.
Used to override the style set or project preference settings related to the display of cross-
reference text for an instance of a shared device, plug, jack, inline, ring terminal, splice or
function, or of a pin or port on an instance of a shared object.
Objects
See “Edit Graphical Attributes Dialog Box” on page 808 for a description of the fields not
described in the table below.
Table 12-14. Cross-references Tab (Properties Dialog Box) Contents
Field Description
Visible Specifies whether the cross-reference text for the object instance is
displayed in the diagram (selected) or not displayed in the diagram
(cleared).
References per line Specifies the maximum number of cross-references that are
displayed on each line for the instance of the object. Select the
Override check box to override the value set in the project
preferences or in the applied style set. To set a limit, select the Set
limit check box and specify the limit in the spin control.
Note: If you select the Override check box and leave the Set
limit check box cleared, all cross-references for the object
instance will be displayed on the same line.
Lines per block Specifies the maximum number of lines that are displayed in each
block of cross-references for the instance of the object. Select the
Override check box to override the value set in the project
preferences or in the applied style set. To set a limit, select the Set
limit check box and specify the limit in the spin control. If you
select this option and the number of cross-references for an object
instance divided by the number of cross-references allowed per line
exceeds the value you have specified for this setting, the cross-
references are displayed in multiple blocks.
Note: If you select the Override check box and leave the Set
limit check box cleared, all cross-references for the object
instance will be displayed in a single block. If you move a cross-
reference in a block to another location in a diagram, all of the
cross-references in that block move with it, but cross-references in
other blocks do not move.

December 2023
Compare Designs Dialog Box

To access: In a design application or in Capital E/E Publisher, with diagrams from two different
design revisions open press Space Bar and enter Compare. Alternatively, in a design
application, in Capital E/E Publisher or in Capital Project Manager, click OK on the Design
Revision - Build List Selection Dialog Box.
Used to specify settings for a design revision or build list comparison.
Objects
Table 12-15. Compare Designs Dialog Box Contents
Field Description
Comparison Type Specifies how objects are treated in the comparison. Only displayed
when comparing Capital Logic Designer, Capital Systems Integrator
and Capital Wiring Integrator design revisions and when comparing
build lists. Mandatory.
• Topology Only
Only topological data is considered. None of the connectivity
items on the selected designs appear in the comparison results.
Only available when comparing Capital Systems Integrator or
Capital Wiring Integrator design revisions.
• Exact
Nets and wires are treated as different types of object, and all
objects are treated as equivalent if they have the same base UID
(when comparing revisions of the same design) or if they have the
same name (when comparing designs that are unrelated).
• Conductor Equivalent
Nets and wires are treated as the same type of object. Devices are
treated as equivalent if they have the same name. Only available
when comparing Capital Logic Designer, Capital Systems
Integrator and Capital Wiring Integrator design revisions.
If there is a net between two pins on one design revision and two
wires separated by a splice between the same pins on a second
design revision, these are treated as the same.
• Device and Conductor Equivalent
Functions like the Conductor Equivalent comparison type.
However, device names are not used to determine whether devices
in design revisions are equivalent. You must click Map
Equivalent Devices to display the Map Equivalent Devices
Dialog Box, and designate devices from the first design as
equivalent to specific devices in the second design revision. Only
available when comparing Capital Logic Designer, Capital
Systems Integrator and Capital Wiring Integrator design
revisions.

December 2023
Table 12-15. Compare Designs Dialog Box Contents (cont.)

Field Description
Traverse Only displayed when comparing Capital Logic Designer, Capital
Wiring Integrator and Capital Systems Integrator design revisions
and only available when comparison type is Conductor Equivalent or
comparison type is Device and Conductor Equivalent.
• Connectors
Specifies whether connectors are considered in the comparison
(cleared) or are ignored in the comparison (selected). Mandatory.
• Splices
Specifies whether splices are considered in the comparison
(cleared) or are ignored in the comparison (selected). Mandatory.
Compare • Attributes and Properties
Specifies whether to compare the attributes and properties of
objects in the design revisions (selected) or to ignore the attributes
and properties of objects (cleared). Mandatory.
• Exclude
Simplifies the Differences report by excluding the entered
attribute and property names. The list of attributes and
properties should be comma-separated.
Excludes all entered names during the comparison (selected) or
compares all attributes and properties of objects (cleared).
Entered attribute and property names are remembered by the
software.
Available only when comparing Capital Harness Designer
design revisions with Attributes and Properties selected.
Optional.
• Internal Connectivity
Specifies whether the internal connectivity of devices is
considered in the comparison (cleared) or is ignored in the
comparison (selected). Available only when comparing two
Capital Logic Designer design revisions. Mandatory.
Design 1 [D1] The first design being compared. By default, this is the currently open
design revision. You can click the ellipsis (...) to display the Design
Revision - Build List Selection Dialog Box again, and select a
different design revision. Displayed only if you are comparing design
revisions. Optional.
Design 2 [D2] The second design being compared. You can click the ellipsis (...) to
display the “Design Revision - Build List Selection” dialog box again,
and select a different design revision. Displayed only if you are
comparing design revisions. Optional.

December 2023

Field Description
BuildList 1 [BL1] The first build list being compared. You can click the ellipsis (...) to
display the “Design Revision - Build List Selection” again, and select
a different build list. Displayed only if you are comparing build lists.
Optional.
BuildList [BL2] The first build list being compared. You can click the ellipsis (...) to
display the “Design Revision - Build List Selection” again, and select
a different build list. Displayed only if you are comparing build lists.
Optional.
Compare Runs the comparison. The results for which, are displayed in the
Differences window. Mandatory.
Export Enables you to export and save the comparison results in an HTML
file. Click to display the Design Compare Report dialog box, and
select a location to save the file and specify the file name. Optional.
Differences Lists the results of the design comparison in a tree. The tree displays
each design revision and the objects being compared in each design. If
an object appears on a design revision or build list, the field in the
column for that design revision or build list is selected.
If you are comparing properties and option expressions on objects,
these are listed under the appropriate objects. If the property or option
expression is set for the object in a design revision or build list, the
field in the column for that design revision or build list is selected.
If filtering has been applied to the diagram windows for the designs,
(Filter Active) is displayed in the head for the Differences column.
Note: If you select an object in the Differences window, the diagram
or plane containing that object is opened and the object is highlighted.
Show Differences Displays the differences between the design revisions graphically by
fading (filtering out) objects that are common in the diagram
windows. You move the slider control up and down to control how
much the common objects are faded. Objects that are different
between the design revisions are displayed normally. When clicked
this button changes to Hide Differences. Optional, not available when
comparing build lists.
Note: If filtering has been applied to the diagram windows for the
design revisions, (Filter Active) is displayed in the head for the
Differences column. This means, some objects may have been faded
in the diagram window as a result of the filtering and not as a result of
showing differences. If harnesses have been faded on the basis of their
lock status, this fading is undone when you click Show Differences
and any fading is a result of the design comparison.

December 2023

Field Description
Hide Differences Displays all objects in the diagram windows normally, regardless of
whether they are common to the design revisions or not. When clicked
this button changes to Show Differences. Optional, not available
when comparing build lists.
Slider Control Move the slider up and down to control how much common objects
are faded out (filtered) when Show Differences has been clicked.
Optional, not available when comparing build lists.
Usage Notes
Example Results Interpretation Capital Harness Designer
This example compares two designs, ExampleA and ExampleB, that both have Multi Location
Node Component, MLC2, configured as in Figure 12-2.
Figure 12-2. MLC2 Configuration
Figure 12-3 and Figure 12-4 show the results of comparing the designs where ExampleA is the
main design, D1, and ExampleB is D2.
The highlighted section in Figure 12-3 shows that MLC2 is present in both designs (see D1 and
D2 check boxes). The bracketed entries [N341,N329,N303,N330] are the nodes that are
configured for MLC2 in the D1 main design (ExampleA).

December 2023
Figure 12-3. Comparison ExampleA v ExampleB Part 1
The highlighted section in Figure 12-4, shows differences that have been identified for MLC2.
• ILC2A [N329] is listed because it is part of MLC2 in the main design D1 (ExampleA)
but not part of MLC2 in comparison design D2 (ExampleB).
o The check boxes for D1 and D2 are both selected because node N329 itself, is
present in both designs.
• N330 is listed because it is part of MLC2 in the main design D1 (ExampleA) but not part
of MLC2 in comparison design D2 (ExampleB).
o Note that only the check box for D1 is selected, because this node is not present at all
on design D2 (ExampleB).

December 2023
Figure 12-4. Comparison ExampleA v ExampleB Part 2
Figure 12-5 and Figure 12-6 show the results of reversing the selection of the designs, in this
case ExampleB is the main design, D1, and ExampleA is D2.
In Figure 12-5, the highlighted section shows that MLC2 is present in both designs (see D1 and
D2 check boxes). The bracketed entries [N341, N303] are the nodes that are configured for
MLC2 in the D1 main design (ExampleB).

December 2023
Figure 12-5. Comparison ExampleB v ExampleA Part 1
In Figure 12-6, the highlighted section shows differences that have been identified for MLC2.
• ILC2A [N329] is listed because it is not part of MLC2 in the D1 design (ExampleB) but
it is part of MLC2 in the comparison D2 design (ExampleA).
o The check boxes for D1 and D2 are both selected because node N329 itself is present
in both designs.
• N330 is listed because it is not part of MLC2 in the main design D1 (ExampleB) but it is
part of MLC2 in comparison design D2 (ExampleA). Note that only the check box for
D2 is selected, because this node is not present on design D1 (ExampleB).

December 2023
Figure 12-6. Comparison ExampleB v ExampleA Part 2
Related Topics

December 2023
Design Revision - Build List Selection Dialog Box
Design Revision - Build List Selection Dialog Box

To access: Press Space Bar and enter Compare Design with a diagram or plane open, or click
the Add button on the Edit Build List Dialog Box. The dialog box is also displayed when
you click the Design ellipsis button on the Export Line Balancing dialog box.
Used to select build lists or designs.
Objects
Table 12-16. Design Revision/Build List Selection Dialog Contents
Field Description
Projects Displays the projects to select designs or build lists. Click the project.
Build Lists Displays the available build lists that you can compare. Select the two
build lists to compare or do not select any to compare individual
design revisions.
Design Revisions Displays the design revisions contained in the selected project in a
browser tree. If you want to compare individual design revisions, click
the design revision to compare with the currently open design
revision. If you are comparing build lists, do not select a design
revision.
Enter Filter String ( ) / In the field next to the Enter Filter String icon ( ), enter a series of
Clear Filter String ( ) characters. A filter is applied to the Design Revisions window so that
only designs with names containing that series of characters are listed.
characters. See also “Browser Tab and Dialog Box Filters” on
page 880.
Click the Clear Filter String icon ( ) to clear the filter and view all
designs in the project.
Design Filter ( ) Click the dropdown list to filter the designs displayed in the Design
Revisions window to those of a particular type, all designs in the
project or all designs in the currently active build list.
Related Topics

December 2023
Design Rule Checks Dialog Box
To access: From the Workflow ribbon, click the DRCs button ( ). Alternatively, press
Space Bar and enter DRCs.
Used to choose which design rule checks to run against designs, all the designs in a build list, or
the structure of an SBOM, to display messages and identify the severity levels of issues in the
design data.
Objects
Table 12-17. Design Rule Checks Dialog Box Contents
Field Description
Transition To Select a release level to transition designs to.
Note: For a release level to appear you must have the appropriate
user permission for its type. See Set Release Levels User
Permissions in the Capital Access Manager User Guide.
Filter Release Levels Click the Filter dropdown menu to filter by Release Level type. The
default state is No Filter. Available options are Draft, Pending,
Released and Obsolete.
Harness Design Select to run checks against Capital Harness Designer designs. Choose
designs from the Design browser tree. Displayed only in Capital
Harness Designer / Modular, Capital Harness Process Designer,
Capital Harness Costing, and Capital E/E Publisher. Optional.
Integrator Design Select to run checks against Capital Systems Integrator designs.
Choosedesigns from the Design browser tree. Displayed only in
Capital Systems Integrator and Capital Platform Designer. Optional.
Logic Design Select to run checks against Capital Logic Designer designs. Choose
designs from the Design browser tree. Displayed only in Capital Logic
Designer, Capital Platform Designer, Capital Systems Architect, and
Capital E/E Publisher. Optional.
Logic Build List Select to run checks against logical build lists. Choose a build list from
the list. Displayed only in Capital Logic Designer, Capital Platform
Designer, Capital Systems Architect, and Capital E/E Publisher.
Optional.
Topology Design Select to run checks against Capital Wiring Integrator designs. Choose
designs from the Design browser tree. Displayed only if Capital Wiring
Integrator is enabled in Capital Logic Designer. Optional.
SBOM Select to run checks against SBOMs. Choose an SBOM from the list.
Displayed only in Capital Harness Process Designer and Capital
Harness Costing. Optional.

December 2023
Table 12-17. Design Rule Checks Dialog Box Contents (cont.)

Field Description
Function Design Select to run checks against Capital Systems Modeler designs. Choose
designs from the Design browser tree. Displayed only in Capital
Systems Modeler and Capital Systems Architect. Optional.
Function Build List Select to run checks against function design build lists. Choose a build
list from the list. Displayed only in Capital Systems Modeler and
Capital Systems Architect. Optional.
Platform Design Select to run checks against platform designs in Capital Systems
Architect. Choose designs from the Design browser tree. Displayed
only in Capital Systems Architect. Optional.
Enter Filter String () / In the field next to the Enter Filter String icon (), enter a series of
Clear Filter String () characters. A filter is applied to the Design browser tree or the Design
Rule Checks browser to display designs or checks with names
containing that series of characters only.
The behavior of the filter varies depending on whether you use
wildcards or the case (upper or lower) of the specified characters.
See also “Browser Tab and Dialog Box Filters” on page 880.
Click the Clear Filter String icon () to clear the filter and view all the
available designs.
Design Rule Checks Displays the checks that you can run and whether a check generates an
browser error ( ), a warning ( ), or an information message ( ) when it
identifies a conflict. See “Design Rule Check Descriptions” on
page 261 for descriptions of checks.
Click the plus icon (+) and minus icon (-) to expand and collapse a
section of the browser.
Select the checks to run, and then click OK. Mandatory.
Reset Resets the check selections to the settings that are currently specified in
project preferences for the current running mode (and abstraction).
Not displayed if the “Use Design Rule Checks settings from previous
run” is cleared in project preferences. See “Project Preferences for
Design Release” on page 214 for a description of the preference.
Only available if the selections in the Design Rule Checks browser
conflict with the project preference checks chosen to run under specific
conditions. That is, those checks selected to run in the current running
mode, and design abstraction (if specified). See “Project Preferences -
Checks Node” on page 220 for a description of those settings.
Run Runs the selected checks and saves any modified check selection
configuration.

December 2023
Table 12-17. Design Rule Checks Dialog Box Contents (cont.)

Field Description
Cancel Closes the dialog box without running the checks. Any changes you
have made to the check selections are not saved.
Usage Notes
The “Use Design Rule Checks settings from previous run” project preferences controls the
behavior of this dialog box with regard to the selected checks when it opens:
• If the preference is cleared, the dialog box opens with the design rule checks selected as
specified in project preferences. That is, it selects the design rule checks that are
specified to run in the current running mode and design abstraction (if specified).
See “Project Preferences - Checks Node” on page 220 for a description of those settings.
If you modified the checks on the previous run, in the current mode and abstraction, the
selections are not preserved.
• If the preference is selected, the dialog box preserves the checks from the previous run
in the current mode and abstraction.
Note
Any changes you make to the check selections do not change the settings on the Project
Preferences dialog box.

December 2023
Details Dialog Box
Details Dialog Box

To access: Select a component in the Part Selection Dialog Box or the Parts Browser and click
View part details ( ).
Used to display the component details tabs for a library part.
Objects
See the Component Details Section in “Component Maintenance Dialog Box” in the Capital
Component Manager User Guide for more information about the fields on the tabs.

December 2023
Edit Assemblies Dialog Box
Edit Assemblies Dialog Box

To access: Press Space Bar and enter Assemblies.
Used to create assemblies.
Objects
Table 12-18. Edit Assemblies Dialog Box Contents
Field Description
Available Lists the components that are available for incorporation into your
assembly. Select the components to use, and then click the ( ) icon to
them to the Assemblies window.
Assemblies Lists the components that comprise your assembly. Select any
components to remove, and then click the ( ) icon to move them to
the Available window.

December 2023
Edit Assembly Dialog Box

To access: Right-click the assembly selected in the Harness Design Browser and select Edit
Assembly from the context menu.
Used to configure assemblies.
Objects
Table 12-19. Edit Assembly Dialog Box Contents
Field Description
Name A unique label for the assembly (within this design). Type a name, or
click the ellipsis (...) button to the right of the field to select from a list
of pre-specified assemblies names maintained in the project’s Object
Type Information in Capital Project Manager. If this field is left blank,
the assembly is named according to any default names configured for
the project in Capital Project Manager. Optional.
Short Description Automatically displays the Short Description field of the assembly if it
is already defined in Capital Project Manager. If no predefined
information exists then it allows you to enter and edit the Short
Description. This attribute is then made available for use in styling and
for search queries. Optional.
Library Part Specifies an association with an assembly in the library. Select the
required library part number type (Internal, Customer, or Supplier)
and click the ellipsis (...) button. The Part Selection Dialog Box is
displayed allowing you to search for and insert an assembly from the
library. You can view details for the associated part by clicking the
button. The associated part can be removed by clicking the button.
Optional.
If a library part is selected, all attributes for which values can be
specified against the library part are completed and set to read-only.
BOM ID Specifies a unique identifier to be displayed against the component in
the Bill of Materials table, the Composite BOM table and in Bill of
Material reports generated from Capital E/E Reporter. This attribute is
only available when a library part is assigned. Optional.
BOM IDs can be automatically prefixed in tables and reports based on
preferences configured for the project. See “Project Preferences for
Designs” on page 135 for more information.

December 2023
Table 12-19. Edit Assembly Dialog Box Contents (cont.)

Field Description
Included on BOM Specifies whether the assembly should be ignored when generating a
bill of materials during engineering calculations (cleared) or whether it
should be included (selected)
Also applies to any components associated with this one, see Included
On BOM Setting.
Optional.
Show All Attributes The Show All Attributes option is selected by default. Clear to display
only the editable attributes on this tab. When you have edited the
attributes, click OK to exit the Edit Assemblies facility and to commit
your changes.
Option Expression Specifies the derivatives in which the assembly exists. To create or edit
an option expression, click the ellipsis (...) button to the right of the
field, and use the Edit Option Expression Dialog Box expression
directly within the field. Optional.
Properties Tab See Properties Tab Dialog Box

December 2023
Edit Breakout/Spot Tape Details Dialog Box
Edit Breakout/Spot Tape Details Dialog Box

To access: Click the Edit ellipsis (...) button underneath the Edit tab of the Edit Insulation
Codes window.
Used to create and edit the short cut code and attributes of breakout and spot tape from a list of
codes created for the object type in Capital Project Manager. For further information see the
Capital Project Manager User Guide.
Objects
Table 12-20. Edit Breakout/Spot Tape Details Contents
Field Description
Library Part Select the appropriate insulation library part number by clicking the
ellipsis (...) button. Optional.
Color Code Specifies the color of the breakout tape. Select a code from the
dropdown list of values available. Optional.
Material Code Specifies the material from which the breakout tape is made. Select a
code from the dropdown list of values available. Optional.
Number Of Turns (Spot Specifies the number of times the tape should be wrapped around the
Tape Only) center of the junction. Optional.
Thickness Specifies the thickness of the tape. This value is used when
calculating the extra diameter added to a bundle by the application of
a spot tape. Optional.
Turns At Breakout Specifies the number of times the tape should be wrapped around the
(Breakout Tape Only) center of the junction. Optional.
Turns On Branch Specifies the number of times the tape should be wrapped around
(Breakout Tape Only) each bundle leaving the junction. Optional.
Type Code Offers a list of component type codes, as maintained in Capital
Component Manager, which can be used to filter the selection of
components displayed when searching for a tape using the Part
Selection dialog box. Optional.
Unmodified Length The unmodified length of the tape. Optional.
Width Specifies the width of the tape. Optional.
Usage Notes
Click the OK button to save the breakout code information to the object type and close the
dialog box.

December 2023
Edit Design Properties Dialog Box

To access: On a On a dialog box for editing a design, creating a design or creating a revision of
a design, click Properties.
Used to modify design properties, scopes and rules. Also used to view the engineering change
orders that impact a design and to set the Design Status for an ECO.
Note
The Rules and ECO tabs are not displayed when creating a new revision of a design. See
“Engineering Change Orders” on page 438 for further information about ECOs.
Objects
Table 12-21. Properties Tab
Field Description
Properties To add a property to the design, click the New button, enter a Property
Name in the New Property Dialog Box, and then click OK. The new
property is added to the list. A property consists of the following fields:
• Name
A unique identifier for the property. Read-only.
• Value
The value assigned to the property. Optional.
• Type
The data type of the value. Mandatory. If you enter a Value that is
not supported by the selected Type, the Value is displayed in red
text and the OK button is unavailable. The following types are
available:
To delete a property from the list, select it and click Delete.
Table 12-22. Rules Tab

Field Description
Add Rule/ Allows you to set rules and constraints on the design. See “Assigning a
Constraint Rule or Constraint to an Object or Design” on page 582. Optional.
Table 12-23. Scopes Tab

Field Description
Available Displays a list of available scope codes that can be applied to the
design. You can select scopes in this list.

December 2023
Table 12-23. Scopes Tab (cont.)

Field Description
Add Moves the selected scopes in the Available list to the Selected list.
Add All Moves all scopes in the Available list to the Selected list.
Remove Moves the selected scopes in the Selected list to the Available list.
Remove All Moves all scopes in the Selected list to the Available list.
Selected Displays the names of the scopes applied to the design.
Table 12-24. ECO Tab

Field Description
Category Displays the category of the engineering change order. Read-only.
Name Displays the name of the engineering change order. Read-only.
Short Description Displays the short description for the engineering change order. Read-
only.
Date Created Displays the date on which the engineering change order was created.
Read-only.
Date Updated Displays the date on which the engineering change order was last
updated. Read-only.
Release Level Displays the release level for the engineering change order. Read-only.
Design Status Indicates the implementation status of the ECO on the impacted
design(s). Select the status from the dropdown list.
If you are using Capital Harness Designer and Capital Harness
Designer Modular, you use this status as part of the Capture and Apply
a Change Within an ECO process.
If an ECO is associated with multiple designs, the Completion value of
the ECO only changes to Completed when the Design Status of all
associated designs has been changed to Completed. Mandatory.
Details Click to opens the Engineering Change Orders Dialog Box in read-only
mode.
Related Topics

December 2023
Edit Effectivity Dialog Box

To access: Click the ellipsis (...) button next to an Effectivity field on a create or edit a Design
dialog box, Manage Designs & Effectivity Dialog Box, or Engineering Change Orders
Dialog Box.
Used to create and manage effectivity ranges for design revisions.
Note
See Managing Effectivity in the Capital Project Manager User Guide for an overview of
using effectivity.
Description
Figure 12-7. Edit Effectivity Dialog Box
The top table (Effectivity Ranges table) in this dialog box displays available effectivity ranges.
The second table (Effectivity Details table) displays the available revisions of the design, and
the effectivity ranges that have been specified for them. Either table can be maximized or
minimized using the dialog box splitter button . If the dialog box is resized, the changes will
be retained for the next time the dialog box is opened.

December 2023
Note
When this dialog box is accessed from the Engineering Change Orders Dialog Box, or
Manage Designs & Effectivity Dialog Box, it will only display the Effectivity Ranges table,
and not the Effectivity Details table.
You can click any table column header to sort the rows according to the content of that column.
Each columns in a table has a filter button. You can click the filter button and enter a series of
characters to apply a filter to the table, only objects with values containing your series of
characters are now listed.
Note
Any table text shown in red indicates that an effectivity range overlaps with another range,
and must be changed. Any text shown in yellow indicates there are overlapping effectivity
ranges in the current design revisions.
Objects
Table 12-25. Edit Effectivity Dialog Box Contents
Field Description
Effectivity Ranges Displays effectivity ranges in a table format.
Start The start value for the effectivity range. See “Valid Start and
End Values for Effectivity Ranges” in the Capital Project
Manager User Guide for guidance on valid values.
Mandatory.
End The end value for the effectivity range. See Valid Start and
End Values for Effectivity Ranges in the Capital Project
Manager User Guide for guidance on valid values.
Mandatory.
Create new Effectivity range Adds a row to the table for a new effectivity range to be
defined.
Delete selected Effectivity ranges Deletes the selected rows in the Effectivity Ranges table.
Duplicate selected Effectivity Copies and duplicates the selected effectivity ranges within
ranges the Effectivity Ranges table.
Note: Newly duplicated rows will display ranges in red
text until they are modified to no longer overlap with an
existing range.
Dialog Splitter Maximize or minimize either table.

December 2023
Table 12-25. Edit Effectivity Dialog Box Contents (cont.)

Field Description
Effectivity Details Not displayed when this dialog is accessed from the
Engineering Change Orders dialog box, Manage Designs &
Effectivity dialog box
Lists the existing revisions of the design and the effectivity
ranges that have been specified for those revisions. Read
only.
Revision Details A combination of the Revision and Short Description values
for the design revision. A harness design revision will also
combine in the Part Number value.
Note: A revision will display in yellow text if its
associated effectivity range overlaps with another
preexisting effectivity range.
Start The start value for the effectivity range.
End The end value for the effectivity range.
Copy and create selected Copies the effectivity range from the selected row in the
Effectivity ranges Effectivity Details table, and places it in the above
Effectivity Ranges table.
Related Topics

December 2023
Edit Graphical Attributes Dialog Box

To access: In a Properties Dialog Box, click the Edit Attributes ( ) button to the right of an
attribute or property.
Used to specify the graphical attributes of an attribute or property value when it is displayed in a
diagram.
Objects
Table 12-26. Edit Graphical Attributes Dialog Box Contents
Field Description
Font Specifies the font used for the text.
Plain / Bold / Italic / Specifies whether the text is displayed bold and/or italic.
Bold/Italic
Number and unit of Specifies the size of the text.
measurement
Default / Foreground / Specifies the color of the text. The selected color is previewed in the
Background / Colors block next to the dropdown list.
Note the following:
• Background
The same color used for the background of the diagram. The color
changes when the background color is toggled.
• Foreground
If the diagram background is white, the text is black, and the other
way around.
Opaque When the text and objects overlap in the diagram:
• If selected, object lines are not visible behind the text.
• If cleared, object lines are visible behind the text.
Rotation Rotates the text to change the angle at which it is displayed. By default
this is 0 which displays the text running left to right following the
horizontal axis: . Enter a different value manually or select a value
from the dropdown list, for example, 270 .

Auto flip If selected, the text flips automatically so that it is never displayed
upside down when it is rotated or flipped.
If cleared, a flip or rotation can result in the text being displayed upside
down.
Justification Where you want the text to be displayed in relation to the object.

December 2023
Table 12-26. Edit Graphical Attributes Dialog Box Contents (cont.)

Field Description
Layout Specifies the layout of the text in relation to its bounding box in the
diagram:
• Clip text to bounding box
If selected, specifies that the text is clipped at the edge of its
bounding box.
• Shrink to fit
If selected, specifies that the font of the text reduces as necessary so
that the text fits in its bounding box.
• Allow text to overflow
If selected, specifies that the text ignores the edge of its bounding
box and flows out of it.
• Wrap text
Specifies whether the text wraps onto multiple lines when it reaches
the edge of the text bounding box (selected) or whether the text
ignores the bounding box and continues on one line (cleared).
When this is selected, if a word is too long to fit on a single line, it
is wrapped by character.
Note: Fonts used in exported DXF files may not display
properly if that font is not installed in the operating system fonts
folder used by Capital or your DXF viewer. This includes viewing
Lucida Sans, as DXF exports use a Java specific version which is
not installed on operating systems.
The Preview shows the behavior that you have selected.

December 2023
Table 12-26. Edit Graphical Attributes Dialog Box Contents (cont.)

Field Description
Number Format If the text is a numerical value, this specifies how the value is
formatted:
• Preview
Displays a preview of how numerical values will be represented on
the diagram according to the value entered in the Decimal Places
field. Read-only.
• Rounding
Specify the method the system uses for rounding the numerical
value. Available settings are:
• Default - the setting specified in Design Settings of your style set
is used.
• Nearest - the system will round up or down to the nearest
multiple of the rounding value.
• None (if selected all other number formatting options are
dimmed).
• Up - the system will round up to the nearest multiple of the
rounding value.
• Decimal Places
Specify the number of decimal places from 0 to 6. This value will
be displayed in the Preview field. If you specify Default, the
number of places value is inherited from the Design Settings of
your style set.
• Delimiter
Specify the delimiter to be used in place of a decimal point, if
required. This can either be Default (a decimal point) or From
Locale, where it is derived from the parameter set at the Design
Settings of your style set.

December 2023
Edit Name Text Attributes Dialog Box

To access: In a Properties Dialog Box box, click the Edit Attributes ( ) button to the right of
a Name field or Short Description field.
Used to specify the graphical attributes of an object name or short description when it is
displayed in a diagram.
Objects
Table 12-27. Edit Name Text Attributes Dialog Box Contents
Field Description
Font Specifies the font used for the text.
Plain / Bold / Italic / Specifies whether the text is displayed bold and/or italic.
Bold/Italic
Number and unit of Specifies the size of the text.
measurement
Default / Foreground / Specifies the color of the text. The selected color is previewed in the
Background / Colors block next to the dropdown list.
Note the following:
• Background
• Foreground
way around.
Opaque When the text and objects overlap in the diagram:
• If selected, object lines are not visible behind the text.
• If cleared, object lines are visible behind the text.
Rotation Rotates the text to change the angle at which it is displayed. By default
this is 0 which displays the text running left to right following the
horizontal axis: . Enter a different value manually or select a value
from the dropdown list, for example, 270 .

Auto flip If selected, the text flips automatically so that it is never displayed
upside down when it is rotated or flipped.
If cleared, a flip or rotation can result in the text being displayed upside
down.

December 2023
Table 12-27. Edit Name Text Attributes Dialog Box Contents (cont.)
Field Description
Balloon Shape Specify the balloon shape that will enclose text on a diagram. The
thickness of the encasing balloon is controlled by setting the
BalloonLineThickness parameter in Design Settings. The color of the
balloon automatically matches the color setting for the text within it.
Select available balloon styles from the dropdown list.
Adding a balloon shape to a diagram automatically dims the Layout
options “Clip Text to Bounding Box” and “Shrink to Fit”.
Justification Where you want the text to be displayed in relation to the object.
Layout Specifies the layout of the text in relation to its bounding box in the
diagram:
• Clip text to bounding box
bounding box.
• Shrink to fit
• Allow text to overflow
• Wrap text
is wrapped by character.
The Preview shows the behavior that you have selected.
Related Topics

December 2023
Edit Objects Dialog Box

To access: Use one of the following methods:
• In Capital Harness Designer or Capital Harness Designer Modular, with more than one
object selected:
o Click the Ribbon action.
o Right-click and select Table Editor.

o Press the Alt + Enter keys.
o Press the Space Bar and enter Edit Objects.
• In Capital Logic Designer with one or more objects selected:
o Click the Ribbon action.
o Right-click and select Table Editor.

o Press the Space Bar and enter Table Editor.
Used to bulk edit the properties and view the attributes of multiple selected objects.
Note
These videos demonstrate how to use the Edit Objects dialog box.

December 2023
Figure 12-8. Edit Objects Dialog Box
Note
The dialog box can display a maximum of 500 properties. If the objects you have selected
contain more than 500 properties, a message as in Figure 12-9 is displayed.
Figure 12-9. Properties Error Message

December 2023
Objects
Field Description
Select Object By default, all the objects that you selected are displayed in the table,
Filter sorted on the Name column in alpha/numeric order. Click the Filter button
to open the Object Type Filter Toolbar which you can use to:
• Display or hide all the selected object types (Select All / Clear All).
• Toggle the display of object types using the individual object buttons.
Note: If you have chosen Clear All, clicking an individual object
button displays all rows for that object type.
If you have chosen Select All, clicking an individual object button hides all
rows for that object type.
The system remembers any filter changes you make to the table display and
re-applies them if you re-open the dialog box within the same session.
Search You can use the Search box to filter the table display based on your input.
All rows containing matches in the name column and also attributes and
property value cells are displayed.
Attributes/ Toggle the control to display either the all the common attributes or all the
Properties Radio properties of the selected objects in the table. Attribute values are display
Set only.
Add Property Only displays when you have selected the Properties radio button.
Click to open a popup to specify the property name and type (String, Float,
or Integer). Click Add to display the property in the table.
Note: If you add a new property, but do not assign it a value for any of
the currently displayed objects, the property is not saved and does not
re-display when you close and re-open the dialog box.
All properties and values that you add are automatically updated to the
selected object(s) when you save the dialog box. You can use the
Properties tab of the individual object to view and edit such object
properties.
Remove Property Only displays when the you have selected the Properties radio button.
Click to remove the currently selected property (and value) from the
selected object(s) in the table. See Remove a Property below.
Any property that you remove is automatically removed from the
individual object when you save the dialog box. Properties that are
removed do not display in the Properties tab for the individual object.
Note: If you delete all the values for a property column, the column is
automatically removed when you click OK.

December 2023
Field Description
Toggle Zoom With this button toggled off, when you select one or more cells in the table,
Selected the object(s) are cross-highlighted in the current diagram view.
If you toggle this button on:
• When you select one or more cells in the table, the diagram view
extents zooms to include all objects you selected.
• In Capital Logic Designer, if you have selected a single object which
appears on different diagrams, you can press the N key to toggle the
zoom to each diagram.
• In Capital Logic Designer, if you have selected multiple objects that
appear on different diagrams, the zoom functionality is unavailable.
Table Use to add, delete, and modify properties and property values for multiple
design objects at once. Bulk editing, cross highlighting, search
functionality, and several filter functions enable you to reduce your data
entry and adjustment time.
Use the table to:
• Add, edit, and delete properties and values, including Object Type
Information properties.
• View attributes and values for the selected objects.
• Bulk edit property values.
• Copy and paste property values within the dialog box and to external
tools.
• Copy attribute values and paste into external tools.
• Filter the displayed object types.
• Filter and sort column values.
• Cross highlight and zoom selected objects.
• Search objects and values across the whole table.
• Hide and show columns.
Name Displays the names of the selected objects in alpha-numeric order. A
corresponding symbol displays in a column to the left.
Click the header cell to display a ( ) symbol. Click to reverse the current
column sort.
Hover over the header cell to display a ( ) symbol. Click to open the
Name Column Filter Popup. Use this popup to configure filtering on the
column.
Note: The symbol remains pinned to the column header if you

have applied a filter on a column.

December 2023
Field Description
Attributes / Displays the names and values of the properties or attributes belonging to
Properties the currently selected objects.
Where only a single object type is currently displayed, all properties and
attributes for that object type are displayed.
Where multiple different object types are displayed:
• All properties on all objects are displayed.
• Only the attributes that are common to all displayed objects are
displayed.
Click the header cell to display a ( ) symbol. Click to reverse the current
column sort.
Hover over the header cell to display a ( ) symbol. Click to open the
Filter Popup. Use this popup to configure filtering on the column.
Diagram Language Translation functionality is not supported for data
entries in the property cells.
Note: The symbol remains pinned to the column header if you

have applied a filter on a column.
Usage Notes
Name Column Filter Popup
• Use this popup to refine filtering of objects in the table Name column.

December 2023
Figure 12-10. Example Name Column Filter Popup
o Select Column - Closes the popup and selects all the cells in the column on the table.
o Filter - Enter a search criteria to dynamically filter the names in the panel below.
o Individual Row Names Panel - Configure the rows you want to display by selecting
or clearing rows in this panel.
o Select All - Selects all the rows in the above panel.
o Clear All - Clears all the rows in the above panel.
Object Type Filter Toolbar
Figure 12-11. Object Type Filter Toolbar Capital Harness Designer and Capital
Harness Designer Modular

December 2023
Figure 12-12. Object Type Filter Toolbar Capital Logic Designer
Remove a Property
Cells are highlighted in a darker gray where you have removed a property. In Figure 12-13, Clip
2 has had the property “Position” removed.
Figure 12-13. Clip 2 Deleted Property
Copy and Paste

You can select cells and use CTRL + C / CTRL + V to copy and paste values to other cells.
You can also copy the contents of selected cells by clicking and dragging the thick cell edge of
a selection as circled in Figure 12-14. The cursor changes to a cross-hair as you drag.
Figure 12-14. Drag Copy

December 2023
Edit Option Expression Dialog Box
Edit Option Expression Dialog Box

To access: Click the ellipsis (...) button next to an Option or Option Expression field.
Used to assign one or more options to an object by creating an option expression.
Objects
Table 12-28. Edit Option Expression Dialog Box Contents
Field Description
Options Lists all applicable options assigned to the design. To add an option to
the Expression field, double-click the option name. Mandatory.
Operators Lists the mathematical symbols available to construct an option
expression. Optional.
To add an operator to the Expression field, double-click the operator.
The operators available are:
• && [and]
The component to which the option expression is assigned appears
on only those derivatives with both options assigned.
• || [or]
on those derivatives with either option assigned.
• ! [not]
on only those derivatives without the option assigned.
• ( and )
An opening and closing parenthesis. Enclosing a subset of an
option expression in parentheses, enables you to construct more
complex option expressions that include precedence (the part of the
expression in parentheses must be evaluated separately before
being evaluated as part of the complete expression).
Expression Contains the complete expression constructed from the options and
operators available. You can also type an expression into this field
instead of selecting from the lists above. Mandatory.
Related Topics
Composite Breakdown [Capital Harness Designer User Guide]
Filter Popup
The filter popup is available on multiple dialog boxes. You can use it to filter various objects in
tables. The filter displays when you right-click a header.

December 2023
Filter Popup
Property or Attribute Column Filter

Figure 12-15. Example Popup Filter
• Hide Column - Hides the currently selected column. When you have hidden a column,
the header row displays a thicker line to separate column headers. Figure 12-16 shows
that a column is hidden between the “_No._of_Matings” and the “_Shell_Style”
columns. To unhide a hidden column, right-click one of the headers on either side and
select Unhide adjacent.
Figure 12-16. Hidden Column
• Select Column - Closes the popup and selects all the cells in the column on the table.
• Filter - Enter a search criteria to dynamically filter the names in the panel below.
• Individual Row Names Panel - Configure the rows you want to display by selecting or
clearing rows in this panel.

December 2023
Filter Popup
• Select All - Selects all the rows in the above panel.

• Clear All - Clears all the rows in the above panel.

December 2023
General Tab (Properties Dialog Box)

To access: In design applications, double-click an object in the diagram window. Alternatively,
select an object then press Space Bar and enter Properties or right-click an object and select
Properties. Click the General tab.
Used to edit the general attributes of an object (for example, name, library part, option
expression) in design applications.
Note
If editing the general attributes of a block in a logical design, see “General Tab (Properties
Dialog Box) [Blocks]” in the Capital Logic Designer User Guide.
Objects
Table 12-29. General Tab (Properties Dialog Box) Contents
Object Description
Name Specify a name for the object. Enter a new name or click the ellipsis
(...) button to the right of the field to select from a list of pre-specified
logical diagram names maintained in the project’s Object Type
Information in Capital Project Manager.
With the exception of pins, you can rename an object to have the same
name of another object in the same design revision. If you do this, the
name is displayed in red and a warning is displayed when you click
OK. If you are editing a multicore indicator, the multicore name is
displayed in the Name field. If you are editing a signal, you can edit
the name only if the signal is not associated with a functional source
net conductor from an associated design.
Select Fixed if you want the name to be fixed. Select the Visible check
box next to the Name field if you want the name to display on the
diagram.
Click the Edit Attributes ( ) button to display the Edit Name Text
Attributes Dialog Box where you can specify how the name is
Short Description Read-only if an object’s name was assigned using a name from the
project’s Object Type Information in Capital Project Manager.
A brief description of the object to provide some detail about it.
Select the Visible check box next to the Short Description field if you
want the name to display on the diagram.
Click the Edit Attributes ( ) button to display the Edit Name Text
Attributes Dialog Box where you can specify how the short
description is displayed on the diagram.

December 2023
Table 12-29. General Tab (Properties Dialog Box) Contents (cont.)

Object Description
Bundle Name - Bundle Only displayed for bundle regions.
Start/Bundle End Specifies the offset between bundle region nodes and the bundle start
or end nodes.
See Editing the Offsets of a Bundle Region from the Bundle Ends in
the Capital Systems Integrator User Guide.
Slot Type Only displayed for slots.
Specifies the type of slot.
• Equipment
The slot contains normal devices.
• Ground
The slot contains ground devices.
• Junction Box
You can route signals through this slot.
Length Only displayed for bundles.
The physical length of a bundle is initially determined by the length of
the bundle in the diagram. You can select Override to change the
physical length.
The bundle length is used when calculating the cost of any synthesized
wiring. Overriding the length can therefore change the result of routing
logical signals because the system selects the cheapest route.
Click the Edit Attributes button , to display the Edit Name Text
Attributes dialog box and set graphical attributes for the short
description that is displayed on the diagram.
Specification Only displayed for conductors.
Allows you to enter the color, material, specification and CSA for the
conductor.
Library Part Specify the library part to assign to the object. Either type the part
name or click the Add (...) button to display the Part Selection dialog
box.
You can click the Update ( ) button if the part has been edited in the
component library. This action updates the design object with the
library edits.
You can unassign the part by clicking Remove ( ) button.

December 2023

Object Description
Configuration - Option Specifies the variant harness options that apply to the object. This
controls when the object is included on the harness. Either enter the
option expression manually or click the ellipsis (...) button to display
the Edit Option Expression dialog box.
See “Assigning/Editing an Object's Options” on page 592.
For more information about options, see “Option” in the Capital
Select the Visible check box next to the Option field if you want the
option expression to display on the diagram.
Click the Edit Attributes button to display the Edit Attributes
dialog box and set graphical attributes if the option expression is
Configuration - Specifies the module codes that apply to the object. Either enter the
Modules module codes manually or click the ellipsis (...) button to display the
Modules dialog box.
For more information about module codes, see “Capital Harness
Designer Modular” in the Capital Harness Designer User Guide.
Select the Visible check box next to the Modules field if you want the
module codes to display on the diagram.
Click the Edit Attributes button to display the Edit Graphical
Attributes dialog box and set graphical attributes if the module codes
are displayed on the diagram.
Configuration - Level Only displayed for wires.
Specifies the harness levels on which the wire exists.
See Specifying the Harness Levels on which a Wire Exists in the
Attributes table Displays attributes specific to the object type.
If an attribute is editable for the object, its name and value are
displayed in black in the Name and Value column, otherwise they are
dimmed. If you enter an invalid value, it changes to red.
The attributes that are displayed vary depending on the type of object
and on the application you are running. For example, the bypass
attribute is only used in Capital Systems Integrator, it should be
ignored if viewed in Capital Logic Designer.
Show All Attributes Selected by default. Clear this option to display only the editable
attributes on this tab.

December 2023

Object Description
Properties table Displays only if the object has no attributes specific to the object type.
Contains user-defined properties for the object. You can create and
delete properties from this table.
Related Topics

December 2023
Generate Advanced Names Dialog Box

To access: When generating names for selected objects: Select the objects for which you want
to generate names, right-click one of them and select Generate Selected Names.
Alternatively, select the objects, press Space Bar and enter Update Selected.
When generating names for all objects in a build list, design or diagram: With the appropriate
project open, press Space Bar and enter Update Selected.
Use this dialog box to generate names for selected objects or all objects in a build list/design/
diagram.
Objects
Table 12-30. Generate Advanced Names Dialog Box Contents
Field Description
Scope tree Displayed only when generating names for all objects in a build list,
design or diagram.
Select the build list, design or diagram in which you want to generate
object names.
Enter Filter String In the field next to the Enter Filter String icon ( ), enter a series of
characters. A filter is applied to the Scope tree so that only designs
with names containing that series of characters are listed.
Click the Clear Filter String icon ( ) to clear the filter and view all
designs in the project.
Show all designs Filter Click the dropdown list to filter the designs displayed in the Scope tree
to those of a particular type, all designs in the project or all designs in
the currently active build list.
Replace Specify the types of existing object names that you want to replace
with newly generated names:
• Default Names - the names generated automatically when an object
is created.
• Generated Names - names that have been generated previously
using the advanced naming functionality. You may want to select
this if naming compositions and conditions have been updated in
Capital Project Manager.
• Fixed Names - these have been defined in the Edit Properties dialog
for objects and have been set as fixed.
Note: Selecting Fixed Names replaces the names of shared objects
that are either Fixed or Generated.

December 2023
Table 12-30. Generate Advanced Names Dialog Box Contents (cont.)

Field Description
Reset Object Indices Select to replace the indices for the counters on the objects. New
indices start at the next number after the counters last value.
For example:
If you replace the indices for three objects with the indices 1, 2 and 3,
the new indices will be 4, 5 and 6. If you replace the indices again, they
become 7, 8 and 9.
See the “Usage Notes” below about selecting both this and Reset
Counters.
Reset Counters Check this box if you want to reset the indices for the counters on the
objects to begin counting from 1.
For example:
If you reset a counter for three objects that currently have the indices 7,
8 and 9, the indices become 1, 2 and 3.
See the “Usage Notes” below about selecting both this and Reset
Object Indices.
Usage Notes
If you check both the Replace Object Indices box and the Reset Counters box, the indices on
the objects will start from 1.
If the Reset Counters box is selected and the Replace Object Indices box is cleared, the
indices on the selected objects do not change but the counter will start from 1 again when you
create new objects.
For example:
If you have three objects with the indices 4, 5 and 6, those indices will remain 4, 5 and 6.
However, when you create a new object that uses that counter, it will have the index value 1.
The next new object created after that will have the index value 2, and so on.
Related Topics

December 2023
Handle Graphics Dialog Box

To access: When editing a functional design or logical design in a design application or when
editing a symbol in Capital Symbol Designer, press Space Bar and enter Handle Graphics.
Used to specify the color and width of the handles used to modify the size and shape of objects
in a diagrams in functional and logical designs in the design applications. Used to specify the
color and width of the handles used to modify the size and shape of symbol graphics in Capital
Symbol Designer.
Note
You cannot resize a symbol in a logical or functional design. If you want to resize a symbol
graphic, you must use Capital Symbol Designer and then update the symbol graphic in the
diagram. See Updating Symbols in the Capital Logic Designer User Guide or Updating
Symbols in the Function Design in Capital Systems Modeler User Guide.
Objects
Field Description
Color selection methods Select the color you require on either the Swatches, HSV, HSL,
RGB or CMYK tab.
Preview Displays a preview of the selected color and also displays the
current color.
Handle width Use the slider or spin control to select the width you require.
Reset Click to reset the selection to the default color and width.
Related Topics
Select Color Dialog Box
Highlight Graphics Dialog Box

December 2023

To access: When editing a functional design or logical design in a design application or when
editing a symbol in Capital Symbol Designer, press Space Bar and enter Highlight Graphics.
Used to specify the highlight color for an object in a functional design or logical design when it
is selected in the Design Browser or the Design Rule Checks Output Window. Used to specify
the highlight color for a symbol graphic when it is selected in the Symbol Contents Browser
Window in Capital Symbol Designer.
Objects
Field Description
Color selection methods Select the color you require on either the HSV, CMYK, HSL, RGB
or Swatches tab.
current color.
Highlight width Use the slider or spin control to select the width you require.
Reset Click to reset the selection to the default color and width.
Related Topics

December 2023
Manage Designs & Effectivity Dialog Box

To access: Click the Manage Designs & Effectivity ( ) button above the Impacted Designs
table on the Engineering Change Orders dialog box. Alternatively, right-click a build list in
the project browser window (in design applications) or in the project browser tree (in
Capital Project Manager), and select Manage Designs & Effectivity. You can also select
specific design revisions in the project browser tree of a design application, right-click them,
and choose the menu item.
Used to specify the design revisions that the system will create with the engineering change
order.
Caution
If effectivity is not enabled in project preferences, this dialog box is called Manage Designs.
Objects
Object Description
You can add designs to this action by clicking this button and
selecting the designs in a Design Revision Selection dialog box.
Add designs
You can remove designs from this action by selecting them in
the table and clicking this button.
Remove selected designs
Design Lists the starting point design revisions for the engineering
change order. Read-only.
Revise Select to create a new revision for the engineering change order.
Revision Specify the identifier for the new revision.
Part Number Allows you to edit the part number for a harness design. Not
editable for other design types.
Short Description Allows you to edit the short description for the design revision.
The revision, part number, and short description display in red
if they are not a unique combination.
Current Effectivity Shows the effectivity value assigned to the existing design
revisions.

December 2023
Object Description
Effectivity Displays the effectivity for the target design revisions that the
system will create.
If you accessed this dialog box from the Engineering Change
Order dialog box, the value is pre-populated with the value
from the effectivity field on that. You can change it here.
If you access this dialog box from a build list, you can edit this
field by clicking the ellipsis button to launch the Edit
Effectivity Dialog Box.
Caution: The system propagates effectivity to any new
revisions only for Capital Logic Designer and Capital
Harness Designer designs.
Update ECO design Not displayed if you access this dialog box from a build list.
references Select to propagate the new design revisions back to the
Impacted Designs table on the Engineering Change Orders
dialog box.
OK Dimmed if multiple revisions of the same design are listed in
this dialog box.
Click to perform the action and close the dialog box.

December 2023
Map Equivalent Devices Dialog Box
Map Equivalent Devices Dialog Box

To access: Click the ellipsis (...) button next to the Device and Conductor Equivalent option
on the Compare Designs Dialog Box.
If you have selected the Device and Conductor Equivalent comparison type when comparing
designs, you must map devices in the first design to equivalent devices in the second design.
Objects
Table 12-31. Map Equivalent Devices Dialog Box Contents
Field Description
Tables List the devices from the two design being compared. Click the title
of any column to sort the table according to the contents of that
column.
The second design must contain equivalent devices for all of the
devices in the first design for mapping to occur. The second design
can contain devices that do not have equivalents in the first design
but not the other way around.
Associate Enabled only when valid devices for mapping are selected in each
table.
To map a device from one design to a device in the other, select
them in the tables and click Associate.
Assist Attempts to map devices automatically. It may be the case that it
cannot map all devices and you need to map some manually. When
you click the Assist button, the Suggestions field displays any
suggested mappings that the system has identified.
Disassociate Enabled only when devices mapped to each other are selected.
To unmap one device association, select the mapped device in each
table and click Disassociate.
Clear Clears all mappings.
Suggestions When you click the Assist button, this window displays any
suggested mappings that the system has identified.
Related Topics

December 2023
Map Pins Dialog Box
Map Pins Dialog Box

To access:
• Click Insert in the Part Selection Dialog Box when associating a library part with an
object that has pins.
• Click OK in the Select Symbol dialog box when replacing a symbol with a symbol that
has a different number of pins.
• In Capital Logic Designer, right-click a device and select Update From ICD, after an
Interface Control Document (ICD) is modified in Capital Device Modeler.
Used to map pins in a library part definition to pins on a diagram object, and to map pins on a
symbol to pins on a device based on a symbol.
Figure 12-17. Map Pins Dialog Box
Objects
Table 12-32. Map Pins Dialog Box Contents
Field Description
Library part list / Symbol Lists the pins on the library part or on the replacement symbol.
pins list Unassociated pins are shown in bold font; associated pins are
shown in plain text.
Instance pins Lists the pins on the instance in the diagram. Unassociated pins are
shown in bold font; associated pins are shown in plain text.

December 2023
Map Pins Dialog Box
Table 12-32. Map Pins Dialog Box Contents (cont.)

Field Description
Associate, Associate All, Either click Associate All to associate the pins in the order they
Disassociate, Disassociate appear in the lists, or select a pin in the Library part list / Symbol
All pins list and a pin in the Instance list then click Associate.
Select two associated pins and click Disassociate to disassociate
them. Click Disassociate All to clear all pin associations.
Changes Lists the changes that will be made when you click OK, or, if the
OK button is unavailable, displays an explanation of why it is
unavailable.
Preserve Diagram Pin Not displayed when creating a library part association with a
Position library part that does not have a symbol.
Select if you want the pins on the instance in the diagram to remain
where they are.
Remove Properties not on Not displayed when creating a library part association with a
Symbol library part that does not have a symbol.
Select to remove any properties from the diagram instance that are
not on the symbol in the symbol library.
This option is not applicable if the same property also exists in
Library. In this scenario Library is the master.
Copy Attribute/Property Not displayed when creating a library part association with a
Values from Symbol library part that does not have a symbol.
Select to copy any properties that are on the symbol in the symbol
library to the diagram instance.
This option is not applicable if the same property also exists in
Library. In this scenario Library is the master.
Preserve Attribute/ Not displayed when creating a library part association with a
Property Text library part that does not have a symbol.
Select to maintain the visibility of the object attributes and
properties on the diagram. If you do not select this, they will no
longer be displayed.
Preserve Pin Names Only displayed when replacing a symbol.
Select this if you want the names of the pins on the instance in the
diagram to remain unchanged. If not selected, the pins on the
instance in the diagram will be renamed to match those in the
library part / symbol.

December 2023
Map Pins Dialog Box
Table 12-32. Map Pins Dialog Box Contents (cont.)

Field Description
OK Unavailable if any pins on the object instance have not been
associated with a pin in the library part / symbol.
Click to apply changes and close the dialog box.
If the OK button is unavailable, the Changes pane displays an
explanation of why it is unavailable.

December 2023
Name Selection Dialog Box

To access: From the Details panel in Component Maintenance dialog boxes: click the ellipsis
(...) button to the right of a Name field. Alternatively, in Capital Logic Designer, click the
ellipsis (...) button to the right of the Harness field in the Edit Harness Attribute dialog box.
Used to select the name of an object from a list of names created for the object type in Capital
Project Manager. The dialog box includes a filter on the first row of each column. This enables
you to filter the list of Object Type Information details based on the content of any of the
columns. See “Usage Notes” below for further information.
Caution
This dialog box behaves differently in some circumstances. If you work with Capital
Networks and are editing a function signal in Capital Systems Modeler, see “Name
Selection Dialog Box (for Signal)” in the Function Design in Capital Systems Modeler User
Guide for further information.
If you work with Capital Systems Modeler and are mapping a functional message to a network
message, see also “Name Selection Dialog Box (for Message)” in the Function Design in
Capital Systems Modeler User Guide for further information.
Objects
Table 12-33. Name Selection Dialog Box Contents
Field Description
Filtering The first row is a filter relating to the content of that column. Selecting
in the desired filter row will present you with a list of the values within
that column.
Alternately enter a string in any of the filter columns to limit the listed
names to those containing that string.
Note: Regular expressions are also supported.
Optional
Filter on Usage If you have assigned a library part to the object and usage definitions
have been created for the library part, this specifies whether the dialog
displays all available names for the object type (cleared) or just those
names used in the usage definitions by default (selected). Optional.
Name The name created in Capital Project Manager. To select a name for an
object, click it and click OK. Read-only.
Description The description that is applied to the object with the name. Read-only.
Short Description The description that is applied to the object with the name. Read-only.

December 2023
Usage Notes
• You can filter the list of Object Type Information details based on any of the column
contents, such as Name, Description or Short Description.When selecting in any of the
columns you are presented with the list of values from that column. Selecting the desired
value in that column will filter the contents of the table and just display that row.
Wildcard and regular expressions are also supported. For example typing 'A' into the
Name filter cell will show all rows where an 'A' is present.

December 2023
New/Edit Assembly Dialog Box
New/Edit Assembly Dialog Box

To access: Click the New ( ) button in the Edit Assemblies Dialog Box, or right-click the
assembly name in the Assemblies field and select Rename.
Used to enter the name of the new assembly you are creating or edit an existing name.
Objects
Table 12-34. New/Edit Assemblies Dialog Box Contents
Field Description
Assembly Name Enter the required name for your assembly. (Not available if the
Default Name box is selected).
Check this box to use a default system name for your assembly. Select
to remove access to the Assembly Name field.
Default Name Lists the components that comprise your assembly. Select any
component(s) which you wish to remove. Click the ( ) icon to move
it/them back to the Available window.

December 2023

To access: Click the ellipsis (...) button next to the Library Part field on a dialog box for
adding or editing an object that can have a library part associated with it. Alternatively, in
Capital Logic Designer press Space Bar and enter Add Device From Library, Add Splice
From Library or Add Library Multicore.
You can also access Part Selection functionality from the Parts Browser. See the “Parts
Browser” topic in the User Guide for the application that you are using.
• Capital Harness Designer Parts Browser
• Capital Systems Integrator Parts Browser
• Capital Logic Designer Parts Browser
Used to select a library part and assign its definition to an object in a design.

December 2023
Objects
Table 12-35. Part Selection Dialog Box Contents
Field Description
Search By Use the dropdown list to specify whether you want to search for an
internal, customer or supplier part number and enter a partial or full
part number in the field next to that dropdown list. Mandatory.
As you type a part number, a dropdown list suggests part numbers that
match the entered string. If ... is displayed at the bottom of the list, this
indicates that more matching part numbers are available. When the
entry ... is selected, a component search with the currently entered part
number string combined with other defined search criteria is
performed.
You can use the following characters to restrict the part numbers
returned in the search results:
• * (star symbol)
Represents any number of characters when used in a string. For
example, entering C-00*E represents values that start C-00,
followed at any position by an E. Example results are C-002-
BLUE, C-003-GREEN, C-004-GREY, C-005-RED.
• ? (question mark character)
Represents any single character when used in a string. For example,
entering A??X (an A, two question marks and an X) into a field
represents only 4-character values that have an A as their first
character and an X as their fourth character. Example results are
ABCX, A11X, ABCXAB.
• Single letter
Entering a single letter into the field, returns only part numbers that
begin with that letter. For example, typing the character C into a
box will list only that box's records that begin with C - regardless of
their length.
Search parts using Displays parts matching the criteria entered in the Search By fields and
criteria specified Filter table in the Parts Table.

December 2023
Table 12-35. Part Selection Dialog Box Contents (cont.)

Field Description
Filter table Enables you to enter advanced search criteria. To enter a criteria, click
Add restriction ( ) to add a new row to the table. For that row, select
an Attribute Name, an Operator and a Value from the dropdown lists
in the columns. To remove a criteria, select that row and click Remove
restriction(s) ( ). To remove all criteria, click Revert to initial
criteria ( ). These criteria are applied when you click Search parts
using criteria specified.
If you are using the Parts Browser, the table is not displayed until you
add a criteria.
Depending on what type of object you are editing, and whether it
currently has a library part assigned, certain filter criteria are
automatically added to the table. Editable criteria are displayed in blue;
non-editable criteria are displayed in black.
Preferred Appears only if you have defined a list of preferred components to be
used in the project. This is done in Capital Project Manager. Preferred
in this case means that you only want to see the list of components that
have been defined on the preferred components list in Capital Project
Manager (selected), otherwise the system lists all appropriate
components (cleared).
Latest With this option selected, any parts belonging to a revision history in
which they are not the latest revision will not be returned by a search.
Mandatory.

December 2023
Table 12-35. Part Selection Dialog Box Contents (cont.)

Field Description
Parts table Displays the results of a search for part numbers when you click
Search parts using criteria specified. To select a part number for
assigning to an object, select the library part in the table and click
Insert.
To view the details for the part, click View part details ( ) to display
the Details Dialog Box. Alternatively, when using the Parts Browser,
you can right-click the part in the table and select View Details.
If the selected part has details that require you to make a choice, the Set
details to be selected ( ) button is enabled. Click to display the Select
Details Dialog Box then select the details that you want to apply.
Alternatively, when using the Parts Browser, you can right-click the
part in the table and select Select Details.
When using the Parts Browser, you can:
• View where the selected part has been used in elsewhere. Click the
View Project Usages ( ) button to display the Where Used In
Project Dialog Box that lists the projects and designs where the part
has been used.
• When using the Parts Browser, you can right-click on part numbers
for certain component types and add a component with that part
number to a design.
See “Parts Browser” in the User Guide for the application that you are
using.
Insert Click to assign the part number that is selected in the Parts table to the
object that you are adding/editing.

December 2023
Properties Dialog Box

To access: In design applications, double-click an object in the diagram window. Alternatively,
right-click an object and select Properties, or choose an object, press Space Bar, and then
enter Properties.
Used to edit the attributes and properties of an object in a design application.
Objects
Object Description
General tab Displays for all objects (excluding object name text).
Used to edit the general attributes of an object (for example,
name, library part, option expression).
See “General Tab (Properties Dialog Box)” on page 823 or,
for blocks (in Capital Logic Designer), see “General Tab
(Properties Dialog Box) [Blocks]” in the Capital Logic
Designer User Guide for further details of the fields on this
tab.
Properties tab Displays for all objects (excluding object name text).
Used to add, edit, and delete user-defined properties for the
object.
See “Properties Tab (Properties Dialog Box)” on page 846 for
further details of the fields on this tab.
Graphical tab Displays for all objects (excluding object name text).
See “Editing the Graphical Attributes of an Object” on
page 598.
Modular tab See “Modular Tab (Properties Dialog Box)” in the Capital
(Displays for modular Logic Designer User Guide.
connectors)
Cross-references tab See “Cross-references Tab (Properties Dialog Box)” on
page 785.
Parameters tab This section enables you to alter the instance shape of an
object by manipulating its parameters. See “Adding / Editing
Object Parameters” in the Capital Logic Designer User
Guide.
Rules tab See “Assigning a Rule or Constraint to an Object or Design”
on page 582.
Scopes tab See “Applying Scopes to a Project or Design” on page 427.

December 2023
Object Description
Symbol tab Displays information detailing if the selected symbol instance
is up-to-date by showing its UID, modification timestamp and
time, as well as which library it originated from.
Paper Layout tab See “Editing the Paper Layout Properties of a Border” in the
Capital Symbol Designer User Guide. This provides
information about the paper size and usable area within the
border.
Variance tab Enables you to specify option-specific values for net attributes
and properties. See “Specifying Option-Specific Values for
Net Attributes and Properties” on page 606.
Related Topics
Specifying Option-Specific Values for Net Attributes and Properties

December 2023
Properties Tab (Properties Dialog Box)

To access: In design applications, double-click an object on the diagram. Alternatively, right-
click an object and select Properties, or select an object, press Space Bar and enter
Properties. Click the Properties tab.
Used to edit the user-defined properties of an object in design applications.
Objects
Object Description
Property table Lists the properties that you have defined for the object.
Name The name of the property. You cannot edit this field.
Value The value of the property. This is the value that displays with the
object in the design if you select Visible.
Type The type of value that the property can have. You can select from
the following options:
• String
A mixture of letters, numbers, and special symbols.
• Integer
A whole number.
• Float
A decimal number.
Editable (visible only in Select if you want the Value and Type fields to be editable in other
Capital Symbol Designer) applications.

December 2023
Object Description
Master (visible only in If the visibility of this property on the symbol is defined both here
Capital Symbol Designer) (using the Visible and Attributes settings) and as a property
decoration in a style set, this specifies whether the settings here or
the settings in the style set take priority when the symbol is placed
in a diagram.
• symbol
If the Override Symbol Styling setting is selected in the style
set applied to a diagram, symbol specifies that only the
visibility of the property (that is, whether it is displayed on the
diagram) is dictated by the style set. The font of the property
value is dictated by the settings here and the position of the
property value is dictated by where you position the property
value on the symbol.
If the Override Symbol Styling setting is cleared, the visibility
and font of the property value are dictated by the settings here
and the position of the property value is dictated by where you
position the property value on the symbol.
• style
If the Override Symbol Styling setting is selected in the style
set applied to a diagram, style specifies that:
• Where a property is defined on a symbol and it is also styled
in the style set, the style set dictates the visibility, font and
position of the property value in the diagram.
• Where a property is defined on a symbol but is not styled in
the style set, it is not displayed in the diagram.
• See also “Override Symbol Styling” in the Capital Diagram
Styling User Guide for further information about that setting.
The effect of that setting combined with the Master setting
for a property on a symbol is summarized in the “Usage
Notes” below.
Visible Select to display the specified Value with the object on the design.
If style set options have been defined for the property, those
options are used to define the appearance of the value. Otherwise,
the Attributes defined in this table define the appearance.
Attributes Click Edit Attributes, to display the Edit Graphical Attributes
facility and set the graphical attributes for the value text that is
displayed for this property on the diagram.
New Enables you to add a property to the object. This displays a New
Property dialog box to specify the name.
Delete Deletes the property that you have selected in the table.

December 2023
Usage Notes
Table 12-36. Effects of Override Symbol Styling and Master Setting
Combinations
Override Symbol Property defined on Property has Master Property has Master
Styling Selected in symbol only or also setting of Style in setting of Symbol in
Style Set? as property symbol symbol
decoration in style
set?
Selected Defined both on Property value Property value
symbol and as a style visibility in diagram, visibility in diagram
set decoration font and position dictated by style set
dictated by style set Font and position
dictated by symbol
Defined on symbol Property value not Property value
only used in diagram visibility in diagram,
font and position
dictated by symbol
Not selected Defined both on Property value Property value
symbol and as a style visibility in diagram, visibility in diagram,
set decoration font and position font and position
dictated by style set dictated by symbol
Defined on symbol Property value Property value
only visibility in diagram, visibility in diagram,
font and position font and position
dictated by symbol dictated by symbol
Related Topics

December 2023
Select by Attribute/Property Dialog Box
Select by Attribute/Property Dialog Box

To access: Press Space Bar and enter Select By Attribute/Property.
Used to search for an object in a diagram by using a value for an attribute or property.
Objects
Table 12-37. Select by Attribute/Property Dialog Box Contents
Field Description
Attribute/Property Enter the name of the attribute or property
Value Enter the value to search for. Regular Expression wildcard search
characters can be used if the Regular Expression check-box is
selected.
Regular Expression Select if the string in the Value field contains Regular Expression
wildcard search characters. Leave cleared if the string is an exact
value that must be matched. See “Finding and Selecting Objects by
Attribute or Property” on page 475 for examples of common
Regular Expression wildcards.

December 2023
Select By Name Dialog Box
Select By Name Dialog Box

To access: Press Space Bar and enter Select By Name.
Used to search for an object in a diagram by using its name.
Objects
Table 12-38. Select by Name Dialog Box Contents
Field Description
Name Enter the name for which you want to search. The Regular Expression
option specifies whether the value in this field is treated as a complete
name that must be matched or as a partial string. Mandatory.
Regular Expression Select if the string in the Name field contains Regular Expression
wildcard search characters. Leave cleared if the string is an exact value
that must be matched. See “Finding and Selecting Objects by Name”
on page 476 for examples of common Regular Expression wildcards.

December 2023

To access:
• When editing a platform design, Capital Wiring Integrator design, Capital Systems
Integrator design or harness design in a design application, press Space Bar and enter
Selection Color.
• When editing a functional design or logical design in a design application, or when
editing a symbol in Capital Symbol Designer, press Space Bar and enter Selection
Graphics.
Used to specify the highlight color for an object in a platform design, Capital Wiring Integrator
design, Capital Systems Integrator design or harness design when it is selected. Used to specify
the highlight color for an object in a functional design or logical design when it is selected by
clicking it in a diagram. Used to specify the highlight color for a symbol graphic in Capital
Symbol Designer when it is selected by clicking it in a diagram.
Objects
Field Description
Color selection methods Select the color you require on either the Swatches, HSV, HSL,
RGB or CMYK tab.
current color.
Reset Click to reset the selection to the default color.
Related Topics

December 2023
Select Details Dialog Box
Select Details Dialog Box

To access: Select a component in the Part Selection Dialog Box or the Parts Browser and click
Set details to be selected ( ).
Used to choose what details you want to apply to the instance of the part currently selected in
the Part Selection Dialog Box or Parts Browser, where the part has multiple choices to choose
from such as multiple customer or supplier part numbers.
Objects
The details to be chosen are displayed in tables, select the rows for the settings that you want to
apply.

December 2023
Where Used In Project Dialog Box
Where Used In Project Dialog Box

To access: Click the View Project Usages ( ) button on the Part Selection Dialog Box or on
the Parts Browser with a part selected.
Used to view where a component part has been used in projects. This dialog box contains a table
with columns that can be filtered by selecting an item from the dropdown list below the column
header.
Objects
Table 12-39. Project Usages Dialog Box Contents
Field Description
Project The project in which the component is used.
Design The design in which the component is used.
Design Type The type of design in which the component is used.
Release Level The release level of the design in which the component is used.
Object Name The name of the object instance where the component is used.
Object Type The type of object where the component is used.

December 2023
Graphics Related Dialogs
Graphics Related Dialogs

This section offers a description of various dialog boxes used for editing graphics. For each
dialog box, all fields are listed, along with a full description of the field’s function.
Add Text Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
Edit Border Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
Image Selection Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
Symbol Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866

December 2023
Add Text Dialog Box
Add Text Dialog Box

To access: Press Space Bar and enter Text, and then create a text frame boundary box on the
diagram. See “Adding a Text Frame to a Diagram” on page 525
Used to specify text and its format in a text frame.
Objects
Table 12-40. Add Text Dialog Box Contents
Field Description
Large text box at top Enter the text. Mandatory.
of dialog box
Font Select the font type for the text and whether the text is plain, bold,
italic, or bold/italic. Mandatory.
Height Specify the height of the text and select the unit of measurement from
the dropdown list. Mandatory.
Color To specify the color of the text, select a color from the dropdown list; it
is previewed in the window to the right of the field. Mandatory.
As well as color names, the list contains the following options:
• Default
The default color used for text by the system.
• Background
• Foreground
way around.
• Manual
The Choose Text Color dialog is displayed, to select a color.
Opaque Select whether object lines are visible behind the text frame boundary
box, (cleared), or are not visible behind the text frame boundary box,
(selected). Mandatory.
Rotation By default this is 0 for the text to run horizontally (left to right). Enter a
different value manually or select a value from the dropdown list, for
example, 270 for the text to run vertically (bottom to top). Mandatory.
Auto Flip If selected, the text flips automatically so that it is never displayed
upside down when it is rotated or flipped. If cleared, a flip or rotation
can result in the text being displayed upside down.
Justification Specify the position of the text within the text frame. Mandatory.

December 2023
Add Text Dialog Box
Table 12-40. Add Text Dialog Box Contents (cont.)

Field Description
Layout The following set of options are available to control the layout of the
text within its frame.
• Clip Text to Bounding Box
bounding box.
• Shrink to Fit
• Allow Text to Overflow
• Wrap text
is wrapped by character. Mandatory.
Preview Displays an preview of an example text string formatted using the
currently selected Layout settings. Mandatory.

December 2023
Drafting Settings Dialog Box

To access: From the Home ribbon, click the Drafting Settings icon ( ).
Used to specify the distance to move with each increment of the mouse when using the drawing
tools, and configure the modifier keys to lock the stretch line action.
Figure 12-18. Drafting Settings Dialog Box Showing Mouse Move Increments
Figure 12-19. Drafting Settings Dialog Box Showing Line Stretch Locking Keys

December 2023
Objects
Tab Description
Mouse move Click to display the radius, offset, line length, and angle values
increments used with the following drawing tools:
• Fillet
• Offset
• Add Line
• Stretch
Specify the distance or angle to move with each increment of the
mouse.
Line stretch locking Click to display the keys to press to lock the slope and length
keys when stretching a line.
Specify the following keys:
• Slope locking key — Locks the angle of the line, meaning the
line can only be stretched.
• Length locking key — Locks the length of the line, meaning
the line can only be rotated.

December 2023
Edit Border Dialog Box
Edit Border Dialog Box

To access: Press Space Bar and enter Border, and then select Drawing > Border from the
Used to select a border created in Capital Symbol Designer that you want to add to a diagram.
Objects
Table 12-41. Edit Border Dialog Box Contents
Field Description
Border Selection Browse through the border libraries in the tree and select the border to
add to the diagram. Mandatory.
Properties Displays the properties that have been specified for the selected border
in Capital Symbol Designer. If a property is editable, you can edit its
value in the Value column. Optional.
Usage Notes
If a placeholder was used as the value for a property in Capital Symbol Designer, you cannot
edit it here. See “Adding Information Placeholders to a Border” in the Capital Symbol Designer
User Guide for more information.

December 2023
Fill Pattern Selection Dialog Box
Fill Pattern Selection Dialog Box

To access: Click Default or Change when overriding the Fill Pattern Selection in the Propertied
Graphic Dialog Box.
Used to select a fill pattern for a graphical shape on a diagram.
Objects
Table 12-42. Fill Pattern Selection Dialog Box Contents
Field Description
Fill Patterns Select the fill pattern.
Foreground Color Specify the foreground color for the pattern. As well as color names,
the list contains the following options:
• Default
• Background
The same color used for the background of the diagram. The
color changes when the background color is toggled.
• Foreground
If the diagram background is white, the object is black, and the
other way around.
• Manual
The Choose Object Color dialog is displayed to select a color.
Background Color Specify the background color for the pattern. As well as color names,
the list contains the following options:
• Default
• Background
The same color used for the background of the diagram. The
color changes when the background color is toggled.
• Foreground
other way around.
• Manual
The Choose Object Color dialog is displayed, to select a color.

December 2023

To access: Press Space Bar and enter Image, and then create an image frame boundary box on
the diagram. See “Adding an Image to a Diagram” on page 520.
Used to navigate to and select an image to be added to a diagram.
Objects
Table 12-43. Image Selection Dialog Box Contents
Field Description
Look in Defaults to your central image repository folder. Mandatory.
Window listing files Displays the image files in your Images folder (as specified in the
system preferences for Paths in Capital Project Manager). Select the
image file to be added to the diagram. The image is previewed to the
right of this window. Only files and sub-folders from the Images folder
area available for selection. You cannot navigate to another folder
location. Mandatory.
Link to Image / Specify how the image is added. See “Link or Embed Images” on
Embed Image page 541. These options do not display if you are adding an image to
non-comment symbols in Capital Symbol Designer. In that case, the
image is added by default using the Link to Image method. These
options also do not display if you are changing the linked image in an
image frame. Mandatory.
File name Displays the name of the selected image file.
Files of type Specify what types of file you want to display in the window listing
files. Mandatory.
Related Topics

December 2023
Propertied Graphic Dialog Box

To access: Select the graphical shape, press Space Bar and enter Properties, and then select
Home > from the Search Ribbon dropdown list. Alternatively, right-click the graphical
shape and select Properties or double-click the graphical shape.
Used to add and edit graphical shape properties, edit the appearance of a graphical shape, and
change the picture displayed in an image frame.
Objects
Table 12-44. Edit Properties - Propertied Graphic Dialog Box Contents
Field Description
General
Properties To add a property to the graphical shape, click the New button, enter a
Property Name in the New Property Dialog Box, and then click OK.
The new property is added to the list. A property consists of the
following fields:
• Name
• Value
• Type
The data type of the value. Mandatory. If you enter a Value that is
not supported by the selected Type, the Value is displayed in red
text and the OK button is dimmed. The following types are
available:
To delete a property from the list, select it and click the Delete button,
and then click OK to confirm the deletion.
Image File Click the ellipsis (...) button to display the Image Selection Dialog Box,
and select the image to display in the image frame. Displayed only for a
linked image. See “Link or Embed Images” on page 541. Mandatory.
Graphical

December 2023
Table 12-44. Edit Properties - Propertied Graphic Dialog Box Contents (cont.)
Field Description
Primary Color Select a color from the dropdown list; it is previewed in the box to the
right of the field. As well as color names, the list contains the following
options:
• Default
• Background
• Foreground
other way around.
• Manual
The Choose Object Color dialog is displayed, to select a color.
Thickness Specify the thickness of the lines of the graphical shape. Mandatory.
To use the default thickness, select Default from the first dropdown
list.
To use a different thickness, select Override from the first dropdown
list and select the type of thickness from the second dropdown list:
• Logical
They provide a logical progression of thickness with a default of 1.
A line with thickness 2 is displayed twice as thick as a line with
You select the thickness from the middle dropdown list.
The physical unit of measurement that has been specified as the
Unit in the style set applied to the diagram. The line thickness is
displayed in relation to the grid size of a diagram. When you zoom
in or out of a diagram, the line grows or shrinks to stay in scale with
the grid.
When you select a unit, the middle dropdown list changes to a free
text field to specify the thickness. The value can be any floating-
point number up to three decimal places.
See “Physical Line Thickness” on page 626 for a definition and
links to related task flows.

December 2023
Table 12-44. Edit Properties - Propertied Graphic Dialog Box Contents (cont.)
Field Description
Line Style Specify the style of the lines of the graphical shape. Mandatory. To use
the default style, select Default from the first dropdown list.
To use a different style, select Override from the first dropdown list
and select the style from the second dropdown list.
Fill Pattern Selection Specify the fill pattern of the graphical shape. To use the default fill
pattern, select Default from the dropdown list. To use a different fill
pattern, select Override from the dropdown list and click Default or
Change to display the Fill Pattern Selection Dialog Box and select a
fill pattern. Mandatory
Line End Style Specify the line end styles by selecting styles in the dropdown lists.
Options include various combinations of line end shape, size and
direction.
Usage Notes
Displayed only for a graphical shape that encloses space.

December 2023
Save as Function or Device Symbol Dialog Box
Save as Function or Device Symbol Dialog Box

To access: In the diagram window, select the objects and comment graphics that you want to be
included in a symbol, press Space Bar and enter Save as Device Symbol (in Capital Logic
Designer) or Save as Function Symbol (in Capital Systems Modeler).
Used to save selected, connected electrical objects and comment graphics in a diagram as a
function symbol (in Capital Systems Modeler) or device symbol (in Capital Logic Designer).
Note
For the task flows, see “Saving Diagram Objects as a Device Symbol” in the Capital Logic
Designer User Guide or “Saving Diagram Objects as a Function Symbol” in the Function
Design in Capital Systems Modeler User Guide.
Objects
Object Description
Create New Select to create the symbol in a new symbol library.
Library - Name Specify the name of the new symbol library.
Library - Domain Click the dropdown list to assign the new library to a
domain.
Select Existing Library Select to save the symbol in an existing library.
Library Select the existing library in which you want to save
the symbol.
Folder Select to save the symbol in a specific sub-folder of
the existing symbol library.

December 2023
Symbol Selection Dialog Box

To access: With no symbol selected in the Symbol Browser, press Space Bar and enter
Comment Symbol or in Capital Systems Architect, Capital Systems Modeler, Capital Logic
Designer or Capital E/E Publisher press Space Bar and enter Place Symbol As Graphics.
Alternatively, click the ellipsis(...) button to the right of any Symbol field.
Used to browse and select symbols from a symbol library.
Figure 12-20. Symbol Selection Dialog Box Example
Objects
Table 12-45. Symbol Selection Dialog Box Contents
Field Description
Select A Library Set A dropdown list displays available Library sets. A library set is a group
of symbols available to a particular design, see Library Sets in the
Capital Styling User Guide for information on creating library sets.
Symbol Selection In the tree, browse to and select a symbol. The selected symbol is
displayed in the pane to the right of the tree.
Show Origin Specifies whether the symbol origin should be indicated in the symbol
pane (selected) or not indicated in the symbol pane (cleared).
Usage Notes
Associating a Symbol to an Empty Node
1. Open the Symbol Selection Dialog Box or click the Symbols tab on the lower-left side
of the application window, and browse to the required symbol.

December 2023
Figure 12-21. Symbol on the Symbols Tab
2. To place the symbol on the diagram, select the symbol name and click OK, or double-
click the symbol name in the browser tree.
The symbol is displayed on your cursor for you to position on the diagram.
Figure 12-22. Symbol on the Cursor
3. If you move the cursor over a node, a circle is displayed on top of the node indicating
that you can associate the symbol to the node.

December 2023
Figure 12-23. Black Node with Circle on Top
4. Double-click the required node when you see the circle.

Results
The symbol is placed on the diagram and associated to the node.
If you move the symbol, it will not break the association.
Figure 12-24. Moving the Symbol
If you move the node, the symbol will follow the node.
Figure 12-25. Original Node Position

December 2023
Figure 12-26. Moved Node Position
You can apply option expressions to symbols to manage the presence of symbols on child
designs following Composite Breakdown in Capital Harness Designer/ Capital Harness
Designer Modular.
Tip
You must associate symbols to an empty node or free space to add an option expression to
the symbol for evaluation during composite breakdown. If you associate a symbol to a node
occupied by a harness component, you cannot add an option expression to the symbol and it will
appear on any child designs containing the parent component.

December 2023
Update Symbol - Options Dialog Box
Update Symbol - Options Dialog Box

To access: Right-click on a symbol on the diagram and select Update Symbol.
Used to control the source of symbol properties and/or attributes when updating a symbol.
Objects
Table 12-46. Update Symbol - Options Dialog Box Contents
Field Description
Preserve Diagram Pin Select if you want the pins on the symbol instance to remain where
Position they are in the diagram already. Optional. Not available in Capital
Harness Designer.
Remove Properties not With this option selected, any properties applied to the comment
on Symbol symbol on the design are removed during the update if they do not exist
in the original symbol definition. Optional.
Copy Attribute/ With this option selected, where properties with matching names, but
Property Values from different values, exist on both the symbol instance and the original
Symbol symbol definition, the instance values are updated with the values from
the original symbol. Optional.
Preserve Attribute Select to maintain the visibility of the object attributes on the diagram.
Text If cleared, they will no longer be displayed. Optional. Not available in
Capital Harness Designer.
Preserve Pin Names Select to maintain any pin names that have been changed manually on
the diagram. If cleared, they will be replaced with pin names from the
symbol library. Optional. Not available in Capital Harness Designer.
Update all xx instances This check box displays if the system has identified other instances of
of this symbol on the the selected comment symbol on the diagram. xx denotes the number of
diagram. instances found. Select the check box to update all instances at the
same time. Optional.

December 2023
Layout Related Dialogs
Layout Related Dialogs

This section details various dialog boxes used for editing designs and objects. For each dialog
box, all fields are listed, along with a full description of the field’s function.
Split Table Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873

December 2023
Set Grid Defaults Dialog Box
Set Grid Defaults Dialog Box

To access: Press Space Bar and enter Set Grid Defaults.
Used to specify how grid points are displayed on a diagram.
Objects
Table 12-47. Set Grid Defaults Dialog Box Contents
Field Description
Show Grid Specifies whether grid points are displayed on the diagram. Even if you
clear this box so that the grid points are not displayed, they still exist and
objects with pins snap to them. Optional.
Major Grid Specifies at which interval larger grid points are displayed. For example, a
Interval value of “5” would display a larger grid point for every 5th grid point.
Mandatory.
Maximum Drawn Specifies the maximum number of grid points that can be displayed in any
Points one row or column when you zoom out of the diagram. When the specified
number of grid points is exceeded, the grid is no longer displayed.
Mandatory.
Drawing Grid Non-electrical objects on a design, such as symbols or text, snap to a
secondary invisible drawing grid that can provide finer-scale positioning
than the visible grid. This option specifies the distance between the points
of this secondary drawing grid as a percentage of the visible grid. For
example, a value of “10” results in ten secondary grid points being
available between two points on the visible grid; a value of 50 results in a
single point, halfway between two grid points. Enter a percentage value
between 10 and 100, in ten-percent increments. Mandatory.
Non-resizable Specifies whether the symbol can (cleared) or cannot (selected) be resized
when placed in a diagram. Mandatory, displayed only when editing a
comment symbol in Capital Symbol Designer.
Use Physical Scale Specifies whether you want to use a physical scale as specified by Grid
Size for a comment symbol when placing it in diagrams. If cleared, a
comment symbol will be scaled based on pin grid points. Mandatory,
displayed only when editing a comment symbol in Capital Symbol
Designer.
Grid Size Specifies the physical distance between the visible grid points. A comment
symbol uses this physical scale and retains its physical size when placed in
a diagram regardless of the diagram’s pin grid settings. Displayed only
when editing a comment symbol in Capital Symbol Designer, unavailable if
Use Physical Scale is cleared.
Usage Notes
The coordinates displayed at the bottom right of the Capital Symbol Designer application use
the units specified for Grid Size.

December 2023
Split Table Dialog Box

To access: Select Override Styling > Split Table from the context menu of the selected table.
Used to control the way in which large tables are broken down into smaller number of columns
or rows, allowing more flexible placement of the table content.
Objects
Table 12-48. Split Table Dialog Box Contents
Field Description
Single Instance Select the check box to clear splitting and force the table to remain as a
single instance. All options are cleared. Clear the check box to enable
the splitting of tables to which this style is applied, and the options for
configuring splitting. Choose from the following:
Split After • Rows
Selecting this option will result in the table being split beneath the
number of rows specified in the Count field.
• Columns
Selecting this option will result in the table being split to the right
of the number of columns specified in the Count field.
• Count
Specifies the number of rows or columns (as selected, above) after
which the table will be split. Mandatory.
Layout These options control how each subset of split table rows or columns
will be placed relative to the initial table block. The following options
are available:
• Fused
Only available when a table is split by Rows, this option results in
subsequent blocks of rows being abutted to the right of the previous
table block.
• Horizontal
This option places subsequent table blocks to the right of the
previous block, separated by the distance specified in the Offset
field, below.
• Vertical
This option places subsequent table blocks beneath the previous
block, separated by the distance specified in the Offset field, below.
• Offset
Specifies the distance at which subsequent table blocks should be
placed relative to the previous block. The units in which this value
is specified are set using the Unit option, and are displayed to the
right of the field. Mandatory.

December 2023
Related Topics

December 2023
Miscellaneous Dialogs
Miscellaneous Dialogs
This section offers a description of various miscellaneous dialog boxes. For each dialog box, all
fields are listed, along with a full description of the field’s function.
Applicable Changes Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
Assign ECOs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
Capital Systems Integrator or Topology Design Filter Dialog Box. . . . . . . . . . . . . . . . . 884
Configure Import Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896
Engineering Change Orders Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
New Property Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
Plugins Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
Plugin Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915
Release Designs Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918

December 2023
Applicable Changes Dialog Box

To access: Press Space Bar and enter Apply Change.
Used to select an ECO design change record to be replayed on a design.
Note
Applies to Capital Harness Designer and Capital Harness Designer Modular only.
Objects
Table 12-49. Applicable Changes Dialog Box Contents
Field Description
Hide Applied Changes Select to hide any ECOs that you have already applied to the current
design in the Applicable Changes list.
The setting is remembered when you re-open the dialog box.
Note: If you update the captured change of a hidden ECO, it
re-displays in the list.
Applicable Changes Lists ECOs with captured changes that are applicable to the currently
List open design.
Entries display in italics if they have already been applied to the
currently open design and the Hide Applied Changes check box is
cleared.
Partially applied ECOs do not display.
Apply Change Click to open the Change Manager Apply ECO dialog box.
Related Topics
Apply Change Output Window
Simulate Change Output Window

December 2023

To access: Click Process in the Applicable Changes Dialog Box. The Apply Change tab
displays in the Output window below the diagram.
The Apply Change tab is an automatically created report that summarizes the top-level design
details and object content in the ECO design change being applied. Any validation errors or
warnings identified are listed in the report.
Note
Objects
Table 12-50. Apply Change Output Window
Field Description
Severity Whether the result is an error ( ), a warning ( ) or an
information message ( ).
Operation The particular type of activity that has been run.
Object Type The specific object type on which the activity has been run.
To make the list more manageable, it can be filtered to show only
the required object types.
Action The specific object on which the activity has been run (Deleted,
Updated, and so on).
Message Detailed message about the activity that has occurred.
Source The name of the object in the Source harness.
Target The name of the object in the Target harness.
Usage Notes
• Click any hyperlinked object in the report to jump to that object in the diagram window.
• Click in the column header to sort the columns. Click in the first cell of each column to
filter the columns.
• Click the icon at the top right of the tab to display a popup menu:
o Clear
Clears the Apply Change output window.
o Show All
Displays the complete report generated during the current design session.
o Save to CSV

December 2023
If required for future reference, save the report save as a comma separated variable
(CSV) file. A dialog box is displayed to specify the filename and location for the
file.
Related Topics

December 2023
Assign ECOs Dialog Box
Assign ECOs Dialog Box

To access: In a design application, press Space Bar and enter Assign ECO, or click the Capital
> Data > Assign ECOs ribbon action.
Use this dialog box to select one or more ECOs to be assigned to one or more selected designs.
Objects
Object Description
Category Window Lists the ECO categories and the individual ECOs that belong to
those categories.
Expand/Shrink Eco Displays or minimizes the details of a selected ECO. The ECO
Detail details are displayed in a read-only format.
See “Engineering Change Orders Dialog Box” for details on the
ECO field displayed.
Assign Assigns the selected ECOs to any currently selected designs.
Related Topics

December 2023
Batch Translate Dialog Box
Batch Translate Dialog Box

To access: In a design application, press Space Bar and enter Translation.
Use this dialog to perform a batch conversion of free text strings that exactly match existing
translations for the currently active language into translation strings. For example, text strings
with a gray background that change when the active language changes.
Objects
Table 12-51. Batch Translate Dialog Contents
Field Description
Scope tree Displays all of the designs and diagrams in the currently open
project. Select the designs and diagrams in which you want to
perform the Batch Translate action.
Enter Filter String In the field next to the Enter Filter String icon ( ), enter a
series of characters. A filter is applied to the Scope tree so that
only designs with names containing that series of characters
are listed.
The behavior of the filter varies depending on such things as
whether you use wildcards and the case (upper or lower) of
the specified characters. See “Browser Tab and Dialog Box
Filters” on page 880 for further information.
Click the Clear Filter String icon ( ) to clear the filter and
view all designs in the project.
Show all designs Filter Click the dropdown list to filter the designs displayed in the
Scope tree window to those of a particular type, all designs in
the project or all designs in the currently active build list.
Related Topics
Browser Tab and Dialog Box Filters

On various browser tabs and dialog boxes, you can filter listed objects. The behavior of these
filters varies depending on whether you use wildcards and the case (upper or lower) of the
specified characters.
Figure 12-27. Sample Dialog Box Filter
Filter wildcards are distinct from full regular expressions used elsewhere in the applications.

December 2023
Wildcard Behavior
The wildcard syntax supports three wildcard characters:
• *
The ‘*’ wildcard is used in place of zero or more instances of any character.
• ?
The ‘?’ wildcard is used in place of a single instance of any character.
• |
The ‘|’ wildcard is used to combine filter searches. Its function is equivalent to a logical
OR operation.
When no wildcards are used in a filter (or if wildcard mode is disabled), the filter text will be
used to find any objects that contain that text.
Wildcard Mode Toggle

The use of wildcards can be toggled by clicking the wildcard toggle in the filter text field.
By default, the use of wildcards in the filter string is enabled. This is indicated by the icon.
You can click that icon to turn off the use of wildcards so that the filter will use exact match
strings. The icon changes to , which you can click to enable the use of wildcards again.
When disabled, the filter treats the wildcard characters as any other character. This is useful in
the case that object names contain one or more wildcard characters.
For example:
• If is visible, a filter string of p*r will show objects with names including the string
'power' or 'player' (any strings with p followed by an r later).
• If is visible, a filter string of p*r will not return those objects because it is looking for
objects with names that include the exact string p*r.
Click the Clear filter icon ( ) to clear the filter and view all objects.
When you switch between using and not using wildcards in a filter that currently does not
contain characters, this change is applied to other filters across the software as a user preference.
If another filter contains characters already, the change is not applied to that particular filter
until you clear it.
If you switch between using and not using wildcards in a filter that does currently contain
characters, the current user preference is not changed and the change of wildcard use is not
applied to other filters.

December 2023
See the following video for an example of the tool behavior when turning the use of wildcards
on and off.
Case Sensitivity
When using a single case, either upper or lower, the filter is not case sensitive. When using a
mixed case, the filter becomes case sensitive and will only match to the exact case used in the
filter text.
For example:
• ‘Device’ is case-sensitive.
• ‘device’ is not case-senstive.
Filter Text and Wildcard Examples
Filter Text Result Example Results

conn Any data that contains the substring • CONN100
“conn”, in either uppercase, lowercase, • Junction_Connector
or mixed case. • conn101
CONN Any data that contains the substring • CONN100
“conn”, in either uppercase, lowercase, • Junction_Connector
or mixed case. • conn101
Conn Any data that contains the substring • Junction_Connector
“Conn”, matching the case of each • Conn123
character exactly.
conn* Any data that starts with the substring • CONN100
“conn”, followed by zero or more • conn101
instances of any character. • Conn
*conn Any data that ends with the substring • Junction_Conn
“conn”, preceded by zero or more • NEWCONN
instances of any character. • conn

December 2023
Filter Text Result Example Results

conn? Any data that starts with the substring • Conn1
“conn”, followed by a single instance of • CONN2
any character. • conn3
?conn Any data that ends with the substring • AConn
“conn”, preceded by a single instance of • 1conn
any character. • _CONN
conn*123 Any data beginning with “conn” and • CONN123
ending with “123”, with zero or more • Conn_123
instances of any character in between. • connector123
conn?123 Any data beginning with “conn” and • CONN_123
ending with “123”, with a single • Conn0123
instance of any character in between. • connA123
*conn*|*123 Data containing “conn” and data • Junction_Connector
containing “123”. • SIGNAL123
• conn123
conn*|?123 Data starting with “conn”, followed by • Connector
zero or more instances of any character • J123
and data ending with “123” preceded by • Conn123
a single instance of any character.

December 2023
Capital Systems Integrator or Topology Design

Filter Dialog Box
To access: Either press Space Bar and enter Filter platform design, or click the filtering icon
( ) on the Status Bar.
Use this dialog box to filter the graphical topology in a diagram.
Objects
Table 12-52. Capital Systems Integrator Design Filter Dialog Box Contents
Field Description
Filter Select a filtering option from the dropdown list.
No Filtering Displays all objects from the worst-case scenario harness. Worst-
case means all of the objects for every possible configuration of a
vehicle.
Graphics by Active Displays only objects from the configuration that is currently active.
Harness Levels See “Setting an Active Vehicle Configuration” in the Capital
Systems Integrator User Guide for more information about setting
active vehicle configurations. Inlines and interface connectors not
connected to a bundle are filtered (hidden). Otherwise, their
visibility depends on the visibility of the attached bundle.
Note: Select Show Harnesses with no Levels to display harnesses
that have no harness levels at all.
Graphics by Active Displays bundles, slots, inlines and interface connectors only if they
Wiring have active wiring content. The visibility of interface connectors
and inlines depends on the visibility of the connected bundle. The
visibility of a slot portal depends on the visibility of the slot and the
connected bundle(s). Any unconnected inline connectors and
interface connectors are filtered (hidden) because they have no
active wiring content. Inlines and interface connectors connected to
inactive bundles are filtered and hidden. Slot portals on the active
slot are filtered if they are not connected to any bundle or if the
connected bundle does not contain any active wiring.
Graphics by Custom Allows you to select a custom filter that you have developed in Java.
Filter. For more information about writing and loading custom filters, see
the PluginDevelopment.pdf document that is located in the doc\
plugin folder of your Capital Installation.

December 2023
Table 12-52. Capital Systems Integrator Design Filter Dialog Box Contents
Field Description
Graphics by Option Displays only objects to which you have assigned particular options.
Ensure that you are showing the filter options (Show Filter Options)
and add the options to the Selected window. To display objects with
no assigned option expressions, select Show Non-Optioned
Objects.
Inlines and interface connectors not connected to a bundle are
filtered (hidden). Otherwise, their visibility depends on the visibility
of the attached bundle. The visibility of slot portals depends on the
visibility of the slot.
Note: If no options are in the Included column, only objects with no
option expression display in the diagram.
Show Filter Options Enabled only when Graphics by Option is selected.
Hide Filter Options Shows or hides the Options window where you select which options
are used in the filter.
Show Non-Optioned Enabled only when Graphics by Option is selected.
Objects See Graphics by Option for an explanation of this field.
Show Harnesses with no Enabled only when Graphics by Active Harness Levels is selected.
Levels See Graphics by Active Harness Levels for an explanation of this
field.
Options Enabled only when Graphics by Option is selected.
Shows or hides the Options window where you select which options
are used in the filter. See Graphics by Option for an explanation.
Related Topics
Diagram

December 2023

To access: Click the Apply Change button on the Applicable Changes Dialog Box.
Used to control how the changes are applied to the harness design. Source: The changes in the
selected ECO-impacted design that are to be applied. Target: The currently open harness design.
Note
Objects
Table 12-53. Change Manager Apply ECO Dialog Box Contents
Field Description
File
Options Opens the Options (Apply ECO) Dialog Box where you configure
the settings used when applying the ECO.
Actions
Place Creates a new object (subject to any change policy specified in the
Options (Apply ECO) dialog box) in the target harness using the
attributes belonging to the object selected in the Harness Objects
Grid or in the Change Manager Preview ECO Dialog Box.
The placement behavior varies depending on the object type.
See also “Harness Object Behavior on Applying ECO Changes” on
page 452.
Any module code expressions are assigned to the object.
Upon placing a selected object, the Link and Synchronize Object
actions are invoked automatically. If the object is created without
issues, the Status field for that object in the Harness Objects Grid
grid is updated and the Origin field displays “Linked”.
Auto Link All objects for which a match can be found will have their source
ids synchronized when a Synchronize Object action is performed.
This enables you to compare changes on the object after linking or
auto-linking. The Status field for those objects in the Harness
Objects Grid displays “Successful” and the Origin field displays
“Linked”.
See the “Link” action below, for a description of the behavior of
linked objects.

December 2023
Table 12-53. Change Manager Apply ECO Dialog Box Contents (cont.)
Field Description
Link Creates a permanent association between the target object and its
counterpart in the source. This link is maintained by updating the
Target object with the Source ID of the Source object. If required
the appropriate module code expressions are also assigned to the
object.
To link an object, select it in the Harness Objects Grid or in the
Change Manager Preview ECO Dialog Box, press Space Bar and
enter Link, and then click the object in the open harness diagram to
which the object should be linked. The Status field for the object
displays “Successful” and the Origin field displays “Linked”.
Note: You can cancel the linking process without selecting an
object by pressing Space Bar and entering Cancel.
Upon linking an object, its source id is synchronized whenever a
Synchronize Object action is performed. See the “Synchronize
Object” action, below, for more information.
Once linked, selecting an object in either the Change Manager
Apply ECO Dialog Box, Change Manager Preview ECO dialog
box or the open diagram for the current harness, results in the same
object being selected in the other two views.
Synchronize Object Updates the attributes and properties of the Target object with the
values belonging to the linked object in the Source, subject to any
change policy specified in the Options (Apply ECO) Dialog Box.
User-defined properties are also synchronized. Filters declared in
adaptors.xml (found in your capital_home/adaptors folder) are also
taken into account. See also “Filters” in the Capital Connectors
User Guide.
Where applicable, Length rounding rules are honored (see “Harness
Shape Parameters” in the Capital Diagram Styling User Guide).
The effects of synchronization vary for different objects; see also
“Harness Object Behavior on Applying ECO Changes” on
page 452.
Unlink Clears the value in the selected Capital object’s External ID
attribute, breaking the link with the Source object.
Report Generates a list of all supported object attributes and the values
contained within the Target and Source objects. All applied
changes are reported. Where a mismatch between the two is found,
the issue is reported as a warning. The report is displayed on the
Apply Change Output Window tab.

December 2023
Field Description
Map Derivatives This option opens the Derivative Mapping dialog box which
performs the following action (subject to any change policy
specified in the Options (Apply ECO) Dialog Box).
• If any derivatives exist in the Source harness that are not
currently mapped to Target derivative designs, the dialog box is
displayed enabling you to either map to an existing derivative,
or create a new one using the derivative details in the Source
data.
Map Modules This option opens the Module Mapping dialog box which performs
the following action (subject to any change policy specified in the
Options (Apply ECO) Dialog Box).
• If any modules exist in the Source data, the Module Mapping
dialog box is displayed enabling you to either map to an existing
module design, or create a new one using the module details in
the Source data.
Auto Link Harness Performs an auto-linking on all Source harness objects. Objects for
Objects which a match can be found based on the autolink criteria will have
their source ids synchronized when a Synchronize Object action is
performed. This enables you to compare changes on the object after
linking or auto-linking. The Status field for those objects in the
Harness Objects Grid displays “Successful” and the Origin field
displays “Linked”.
See the “Link” action, for a description of the behavior of linked
objects.
Process This single action is a combination of Place, Auto Link, and
Synchronize Object. Once the action is selected a progress bar
appears indicating the current status of the action.
This option also performs the following actions (subject to any
change policy specified in the Options (Apply ECO) Dialog Box):
• Updates and synchronizes the attributes and properties of the
objects in the Target harness. If, for any reason, some of the
links were broken, the Auto-Link Criteria will be applied to re-
establish the link.
• Creates new options in the current project if any found in the
changed harness data do not already exist.
• Updates the applicable options on the Target harness with those
in the Source harness (if different).
View

December 2023
Field Description
Display Report With this option selected:
• The Apply Change Output Window displays when the ECO is
processed.
• When the harness is validated - either automatically or manually
- a report is generated.
With this option cleared, no report is generated, and a warning
message is issued only if an error is encountered during validation.
Detailed Reporting Toggles the Change Manager report content between full, detailed
reports or condensed, short reports.
With Detailed Reporting selected (on) all Warning, Error, and
Information message are displayed.
If Detailed Reporting is unselected (off) then the following filtering
is applied:
• Information Messages that are filtered out
• All Status Messages except exclusive attribute value reports
of Capital or External Values, Bundle reconnections and
deletions
• All Updated Messages (Attribute Value Set messages)
• Warning Messages that are filtered out
• Change Policy restrictions
• Already linked messages
• Mismatch in the number of child objects
• No error messages are filtered out
View Toggles the display of the Change Manager Preview ECO Dialog
Box.
Filter Filters the items displayed in the Harness Objects grid of the
Change Manager Apply ECO Dialog Box.
Refresh Refreshes the Harness Objects grid.
Zoom Selected (Design) Select, or press Z, to immediately locate and highlight the selected
object on the harness diagram.
Zoom Selected (Preview) Select, or press P, to immediately locate and highlight the selected
harness object in the Preview window.
Harness Objects Grid This grid lists all supported objects found in the ECO change.
Certain actions in the Harness Objects grid are available by right-
clicking and accessing the context menu.
Type The component type, such as Bundle, Clip, Tube, and so on.

December 2023
Field Description
Origin Specifies whether the object exists only in the source data or, the
Target harness design, or whether it has been linked and is therefore
present in both.
Status Provides feedback on the results of the last linking action
performed for the object. If the linking was not successful, an
appropriate warning is displayed. Where an issue is encountered,
further information on the problem is provided on the Change
Manager tab in the Output Window.
Target The design-level name assigned to the object in the Target harness.
Source The name assigned to the object in the Source.
User FM The user generated functional modules codes assigned to the object
in the Source. To filter, type the filter string in the text field of the
column header. Capital Harness Designer Modular only.
Generated FM The system generated functional modules codes assigned to the
object in the Source. To filter, type the filter string in the text field
of the column header. Capital Harness Designer Modular only.
User PM The user generated production modules codes assigned to the object
in the Source. To filter, type the filter string in the text field of the
column header. Capital Harness Designer Modular only.
Generated PM The system generated production modules codes assigned to the
object in the Source. To filter, type the filter string in the text field
of the column header. Capital Harness Designer Modular only.
Source ID The unique identifier given to the object in the Source. It is this
value that is inserted into the target object’s ID field, creating the
link between the two.
Toolbar The Change Manager toolbar provides quick access to certain
commands on the Actions and View menus. Results of operations
executed from the toolbar are immediately applied to the Change
Manager Preview ECO Dialog Box.
Auto Link Performs an auto-linking on Source harness objects. See “Auto
Link”.
View Toggles the display of the Change Manager Preview ECO dialog
box.
Filter Used to filter the items displayed in the Harness Objects grid of the
Change Manager Preview ECO dialog box.
Refresh Refreshes the Harness Objects Grid.

December 2023
Field Description
Process Initiates the Process action, which is a single action that performs
all required steps automatically to apply changes, while adhering to
defined policies.
The Source data applied to the Target harness.
• Objects are Auto-Linked.
• Existing linked objects are synchronized (updated).
• Obsolete objects are deleted.
• New objects are added.
Note: Existing bundles with topology changes are re-connected
using the incoming structure.
Related Topics
Options (Apply ECO) Dialog Box

December 2023

To access: On the Change Manager Apply ECO Dialog Box, choose View > View from the
main menu or click the View ( ) button on the toolbar.
Used to display a graphical representation of the target harness with the ECO changes applied.
Note
Objects
Table 12-54. Change Manager Preview ECO Dialog Box Contents
Field Description
Preview Menu Items The dialog box menu - and the icon shortcuts on the toolbar - offer
a number of options for controlling the display of the harness, as
well as mirroring the placement and linking options available
within the “Change Manager Apply ECO” dialog box.
File
Exit Closes the Change Manager Preview ECO dialog box (and the
“Change Manager Apply ECO” dialog box if it is also open).
You can also click the icon to exit.
The system stores the status of the two dialog boxes on exit, and if
both were open, reopens both when the Change Manager Apply
ECO dialog box is opened again.
Actions See the Actions section in the topic “Change Manager Apply ECO
Dialog Box” on page 886

December 2023
Table 12-54. Change Manager Preview ECO Dialog Box Contents (cont.)
Field Description
View The following options control the way in which the harness is
displayed in the preview window, but do not affect the harness
topology in any way.
• Zoom In
Increases the size at which the preview is displayed. Can also
be accessed by clicking the icon on the toolbar.
• Zoom Out
Decreases the size at which the preview is displayed. Can also
be accessed by clicking the icon on the toolbar.
• Zoom All
Sets the size of the preview such that it comfortably fills the
window. Can also be accessed by clicking the icon on the
toolbar.
• Zoom Synchronized
Sets the zoom level of the preview to match that defined for the
active diagram window. Can also be accessed by clicking the
icon on the toolbar.
• Show Labels
Toggles the display of component names in the preview
window. Can also be accessed by clicking the icon on the
toolbar.
• Show Splices
Toggles the display of splices (indicated by the symbol).

Can also be accessed by clicking the icon on the toolbar.
• Show Fixings
Toggles the display of fixings (indicated by the symbol).


December 2023
Table 12-54. Change Manager Preview ECO Dialog Box Contents (cont.)
Field Description
View (continued) • Show Protections
Toggles the display of protections (indicated by a thicker
linestyle than an unprotected bundle). Can also be accessed by
clicking the icon on the toolbar.
• Show Connectors
Toggles the display of connectors (indicated by the

symbol). Can also be accessed by clicking the icon on the
toolbar.
• Show Devices
Toggles the display of devices (indicated by the symbol).

• Text and Symbol Size
Displays the Adjusting Text and Symbol Sizes dialog box, to
scale the display and visibility of graphics and text objects. Can
also be accessed by clicking the icon on the toolbar.
• Display Report
Toggles the display of the Harness Validation report during
Harness Validation. Select the option to enable reporting (the
option will be ticked to indicate selection); select the option
again to clear it.
Note: With this option cleared, Harness Validation will result
in the generation of an error dialog box if an error was
detected, instead of the full report.
• Change Manager - Apply ECO
Toggles the display of the Change Manager Apply ECO
Dialog Box. Can also be accessed by clicking the icon on
the toolbar.
Tools • Validate
Triggers an automatic validation process to run on the
incoming source data. The process is described fully in the
“Harness Validation” topic in the Capital Connectors User
Guide.

December 2023
Usage Notes
The following actions are supported in the preview window:
• Bundles are represented as lines, nodes as the intersections between them. Text labels
can also be displayed, together with splices, connectors, protections and fixings. A
color-coding scheme is used to represent different preview objects as follows:
o Green denotes an unlinked bundle, connector, or device.
o Blue denotes an unlinked splice, fixing or protection.
o Grey denotes a linked bundle or device.
o Red denotes a selected item.
• Object Selection
The preview includes a representation of all of the objects in the captured change that
can be illustrated graphically. Selecting an object in the preview pane results in the same
object being selected in both the Change Manager Apply ECO Dialog Box and in the
diagram window.
o Select a single object by clicking it.
o Select multiple objects by clicking and dragging out a rectangular selection; upon
releasing the mouse button, all objects falling wholly or partly within the rectangle
are selected.
o Clear all objects by clicking an empty area of the window.
• Panning
Middle-click within the preview window and drag to move the window contents.
Note
Middle click is also referred to as mouse button 3, and is activated by pressing down
on the mouse scroll wheel, where available.
• Zooming
If your mouse has a scroll wheel, you can use it to zoom into/out of the preview.

December 2023
Configure Import Dialog Box

To access: Select a part you wish to import in the 3Dfindit.com Embedded Library Portal and
click the button.
Use this dialog to create and edit internal part numbers on new parts during the import process
into Capital. It also offers the ability to revise existing parts and control the import mode action.
The dialog displays either a New Components tab or an Existing Components tab depending on
the prior existence of the incoming parts in your component library. The available fields display
accordingly.
Note
In certain scenarios the dialog can display both tabs as well if the incoming component
contains new, as well as existing parts. For example, the housing components of a new
connector part may already exist in your component library. In such a case, the connector will
be in New Components tab but housing components will be in Existing Components tab.
Objects
Table 12-55. Configure Import Dialog Box
Fields Description
Supplier The name of the parts manufacturer. Read-only.
(Both New and Existing
Components tab)
Type The component type that is being imported. Read-only.
(Both New and Existing
Components tab)
Group The component group to which the component belongs.
(Both New and Existing See Component Groups in the Capital Component
Components tab) Manager User Guide for more information. Read-only.
Supplier Part Number The part number as supplied by the parts manufacturer.
(Both New and Existing Read-only.
Components tab)
Internal Part Number The Internal Part Number of the component. This is pre-
(Both New and Existing populated with the part number supplied by the
Components tab) manufacturer. You can overwrite this with an appropriate
internal part number according to your organization’s
requirements. This value should be unique and non-empty.
You should not use the part number of any existing part.
Revision Enter a revision value that is assigned to the new part when
( New Components tab only ) it is created in your component library. Optional.

December 2023
Table 12-55. Configure Import Dialog Box (cont.)

Fields Description
View Part Click to view all the details for the selected part as held in
your component library. See the relevant Component
(Existing Components tab Dialog Box and Field Reference section in the Capital
only) Component Manager User Guide for further information
on the fields displayed.
Revise Click the check box to revise the existing component with
(Existing Components tab the new incoming details.
only)
New Revision Enter a valid new revision value for the incoming part.
(Existing Components tab Editable only when Revise check box is selected.
only)
Import mode for existing Specifies how the system resolves conflicts between
revisions internal part numbers in the newly imported data and in the
(Existing Components tab existing library. Please note, this mode affects only those
only) parts in the Existing Tab that are NOT selected for
Revision. Mandatory.
• Replace
Specifies that the data for an existing component in the
library is truncated and overwritten with the data from
the component with the same supplier part number in
the import file.
• Merge
Specifies that the component data for a supplier part
number in the import file is merged with the
component data for an existing component with that
supplier part number in the library. For further
information and usage examples for Library Data
Merging see Usage Examples for Library Data
Merging in the Capital Component Manager User
Guide.
• Ignore
Components from the import file with supplier part
numbers matching components already in the library
are not imported.
Proceed / Cancel Click Proceed to import the selected part into your
component library. Click Cancel to abort the import of the
part.

December 2023
Edit Capital Configuration Dialog Box

To access: Click the Configuration option from the Support section of the Capital Application
Launcher.
Used to specify the maximum amount of physical memory (on a client computer) that each
Capital application is permitted to use during their operation. Also used to enable some
applications as detailed below.
Objects
Table 12-56. Edit Capital Configuration Dialog Box Contents
Field Description
Application Name The name of the Capital application. Read-only.
Memory Allocation Specifies the maximum amount of physical memory (in megabytes)
(MB) that the application can use. Select either 128, 256, 512, 768, 1024,
1280 or 1536 from the dropdown menu. By default, this is 512 MB.
Alternatively, manually enter another value. Mandatory.
Note: If you use the appmx command line argument with the
launcher, the Memory Allocation (MB) column in the Edit Capital
Configuration dialog box is unavailable.
Enable Insight If this is selected, Capital Systems Integrator, Capital Wiring
Integrator, Capital Harness Designer, and Capital Harness Designer
Modular will start with the add-on Capital E/E Insight functionality
enabled.
Caution: Your user account must have a license policy that
includes Capital E/E Insight in order to use it.
If this is not selected, you have access to default metrics that can be run
against designs to measure and assess them.
For information about both, see “Capital E/E Insight” on page 999.
Enable Capital Where your license policy includes Capital Formboard Designer:
Formboard Designer • If this is selected, Capital Harness Designer and Capital Harness
Designer Modular will start with the Capital Formboard Designer
functionality enabled and consume a formboard license where one
is available. This mode is selected by default.
• If this is un-selected, Capital Harness Designer and Capital Harness
Designer Modular will start with Capital Formboard Designer
functionality not enabled and not consume a formboard license
where one is available.
For more information, see Capital Formboard Designer in the Capital
Harness Designer User Guide.

December 2023
Note
In earlier releases, you could use this dialog box to enable other add-on functionality
(licenses). You now do this through the use of license policies. See “License Policy” in the
Capital Access Manager User Guide.

December 2023
Edit Diagram Properties Dialog Box
Edit Diagram Properties Dialog Box

To access: Click the Properties button next to the Diagram Details - Name field on a New
Design dialog box.
Used to specify user-defined properties for a new diagram.
Objects
Object Description
Properties To add a property to the design, click the New button, enter a
property name in the New Property dialog box, and then click
OK. The new property is added to the list. A property consists
of the following fields:
• Name
• Value
• Type
The data type of the value. Mandatory. If you enter a
Value that is not supported by the selected Type, the Value
is displayed in red text and the OK button is dimmed. The
following types are available:

December 2023

To access: In a design application, press Space Bar and enter Engineering Change Order, or
select More from the popup menu displayed from the Name column in the Engineering
Change Orders tab. In Capital Project Manager, in the browser tree on the left of the
application, navigate to the Engineering Change Orders node for the project. Double-click it
or right-click it and choose Edit.
The dialog box displays in read-only mode when accessed by:
• Clicking the button on the Assigned ECOs panel of The Build lists Dialog Box
• Clicking the “Details” button on ECO Tab of the Edit Design Properties Dialog Box
Use this dialog box to create, edit, import/export, and delete Engineering Change Orders
(ECOs).
Objects
Table 12-57. Engineering Change Orders Dialog Box Contents
Field Description
Category Window Lists the ECO categories and the individual ECOs that belong
to those categories. Click the Add New Engineering Change
Order Category ( ) button to create a new category.
To add a new ECO under a category, click by that category
name.
To delete an ECO from a category, select it and click .
To edit a category or ECO name, double-click it. An ECO
name must be unique within a project.
Empty categories are deleted from the list when the dialog box
is closed.
You can drag and drop an ECO from one category to another.
If you hold your mouse cursor over an ECO name, a tooltip
displays information about who created it, when it was created
and who has modified it.
<ECO name> panel This section displays the details for the ECO selected in the
Category window.
about the ECO. Optional.

December 2023
Table 12-57. Engineering Change Orders Dialog Box Contents (cont.)

Field Description
Release Level The release level for the ECO. Note that this does not refer to
the design release level assigned to the impacted designs.
Select the release level for the ECO from the dropdown list.
The release levels that you can assign depend on the
permissions that have been set for your user account in Capital
Access Manager. See the Capital Access Manager help system
for more information about setting permissions for a user
account.
If an ECO is associated with multiple designs, this Release
Level value of the ECO can only be changed to Released when
the Completion Status of all associated designs in the ECO
have been changed to Completed. Mandatory.
Effectivity Click the ellipsis (...) button, to open the Edit Effectivity
Dialog Box and specify the effectivity of the target designs
that are created with the engineering change order.
Caution: The system propagates effectivity to any new
revisions only for Capital Logic Designer and Capital
Harness Designer designs.
Properties Enables you to add properties to the ECO.
To add a property, click to display the New Property dialog
box, and specify a name for it. For the property, specify the
value and the data type of the value. If you enter a value that is
not supported by the selected Type, the Value is displayed in
red text and the OK button is dimmed. The following types are
available:
To remove a property, select it and click .
Notes Notes about what changed during this ECO. Editable only if
the Release Level is set to Released.

December 2023

Field Description
Impacted Designs This table lists the ECO impacted designs (design revisions)
associated with the ECO.
A row in italics indicates that it has been imported (see “ECO
Import and Export” on page 464).
• ( ) - Manage Designs & Effectivity. Click to open the
Manage Designs & Effectivity Dialog Box, and specify the
design revisions to create with the engineering change
order.
• ( ) - Click to open the Design Revision - Build List
Selection Dialog Box, and select a design revision to
associate with the ECO.
• ( ) - Click to dis-associate the selected design revision
and any images from the ECO.
• ( ) Click to update the selected impacted design to its
latest revision. Enabled only when the selected design is
not the latest revision.
• - Click to import an ECO impacted design.
• - Click to export the currently selected ECO impacted
design. Enabled only where the selected has a Completion
Status of “Completed - Changes Captured”.
• - Click to delete all ECO captured information and any
images associated with selected row.
Latest A tick ( ) in this column indicates that this is the latest
revision of the design.
Full Name The full name of the associated design.
Release Level The release level of the associated design.
Abstraction The abstraction value of the associated design.

December 2023

Field Description
Completion Status Indicates the implementation status of the ECO on the
impacted design(s). Read-only.
For Capital Harness Designer and Capital Harness Designer
Modular only:
• Not Started - Action has not started implementing the
ECO.
• In Progress - Action has started to implement the ECO but
you have chosen not to create a capture baseline.
• In Progress (Capturing Changes) - Action has started to
record the ECO and the system has created a baseline.
• Completed - ECO implementation action has finished.
• Completed (Changes Captured) - Action has finished
implementing the ECO and the changes have been
captured.
For all tools:
• Not Started - Action has not started implementing the
ECO.
• In Progress - Action has started implementing the ECO.
• Completed - Action has finished implementing the ECO.
The status values are changed in:
• The Design Status column on the ECO Tab of the Edit
Design Properties Dialog Box.
• The Completion menu setting in the Name column of the
Engineering Change Orders Tab.

December 2023

Field Description
Images This panel displays any image files you have added to help
illustrate the ECO.
Image files are added using the following buttons:
• - Paste image from Clipboard. Adds an image file to
the panel, created from the current content of the clipboard.
The button is dimmed when the clipboard is empty.
• - Take a screenshot of visible diagram area. This takes
a screenshot of current visible area of the active diagram
canvas and adds it as an image file to the panel. The button
is dimmed if a diagram is not open.
• - Add image(s) from file(s). Opens a file browser to
select a valid PNG, JPG, or JPEG file to add to the panel.
• - Remove selected image(s). Select an image file from
the panel and click this button to remove it.
The buttons are dimmed when nothing is selected in the
Impacted Designs panel and when the dialog box displays in
read-only mode.
Image Viewer Double-click a file in the Images panel to open it in the Image
Viewer.
- Click this button to open a file browser and select a
location to save the currently open image in PNG format.
- Click this button to copy the currently open image to the
clipboard.
Related Topics

December 2023

To access: Press Space Bar and enter ECOs in any of the design tools.
The Engineering Change Orders tab displays in the output window at the bottom right-hand side
of the design tool application.
Objects
Table 12-58. Engineering Change Orders Output Window
Field Description
Name The name of the relevant ECOs.
If there is no diagram currently open, or the filter for current
diagram is toggled off, the output window displays all the ECOs
that are associated with the project. The Name ellipsis button is not
enabled.
If there is a diagram currently open and the filter for current
diagram is toggled on, the output window displays only the ECOs
that are associated with the diagram. The Name ellipsis button is
enabled. Click to display the following popup menu items:
• Take a Screenshot
Select to take a screenshot of current visible area of the active
diagram canvas. The screenshot is automatically added to the
Images panel of the selected ECO for this design.
• Completion Status
Enables you to change the status of the ECO on the impacted
design. Select from Not Started, In Progress, Completed.
For Capital Harness Designer and Capital Harness Designer
Modular only, change the status to start and stop capturing the
change. See “Capture and Apply a Change Within an ECO” on
page 445
• More
Select to open the Engineering Change Orders Dialog Box in
full edit mode for the selected ECO.
Short Description Descriptive text about the ECO. Read-only.
Category Lists the ECO categories for the individual ECOs that belong to
those categories. Read-only.
Release Level The release level for the ECO. Note that this is not the same
release level assigned to the impacted design revisions. Read-only.
Design Status The completion status of the ECO in the currently open design.
Read-only.
Created By The name of the user who created the selected ECO. Read-only.

December 2023
Table 12-58. Engineering Change Orders Output Window (cont.)

Field Description
Modified By The name of the last user to modify the selected ECO. Read-only.
Refresh Click to refresh the displayed list.
Filter If there is a diagram open, click to toggle the list of displayed
ECOs between those that are applicable to the currently open
design (the default when you open this tab) and those that are
applicable to any designs in the currently open project.
If no diagram is open, the table lists all ECOs that are applicable to
any designs in the currently open project.
Filter by Release Level Select to filter the list of available ECOs by their Release
Level, select from Draft, Pending, Released.
Usage Notes
• The columns are sortable by clicking in the column header. The columns are filterable
by clicking in the first cell of each column.
Related Topics

December 2023
Export ECOs Dialog Box
Export ECOs Dialog Box

To access: In a design application, press Space Bar and enter Export ECO, or click the Capital
> File > Export ECOs ribbon action.
Use this dialog box to select one or more ECOs to be exported.
Objects
Object Description
Category Window Lists the ECO categories and the individual ECOs that belong to
those categories.
Expand/Shrink Eco Displays or minimizes the details of a selected ECO. The ECO
Detail details are displayed in a read-only format.
See “Engineering Change Orders Dialog Box” for details on the
ECO field displayed.
Export Exports the selected ECOs. Opens a file browser to choose a
destination for the exported data.
Related Topics

December 2023
Manage Designs & Effectivity Report
Manage Designs & Effectivity Report

To access: Displays after you have used the Manage Designs & Effectivity dialog box to create
new design revisions with a specific effectivity. In design applications, this displays as a tab
in the output window at the bottom right of a design application window. In Capital Project
Manager this displays as a dialog box.
Reports information regarding any changes made to engineering change orders and designs
while the system created design revisions.
Objects
Object Description
Displays a Save dialog box and enables you to save the
report to a CSV file.
Save to CSV
Severity Indicates whether this row is an error ( ), a warning
( ) or an information message ( ).
An error or warning displays if the system could not
revise a design. This may occur if a user does not have
necessary permissions or does not have access to
necessary domains.
Design/Engineering Change The name of the design or engineering change order
Order that the system has changed.
Message Informs you of the change to the design (that is, created
revision, updated effectivity) or to the engineering
change order (that is, updated design revisions).

December 2023

To access: In the Project Browser Window of a design application, right-click the project name
folder or a design folder and select New Folder. Alternatively, right-click a design folder
and select Rename.
Used to specify the name of a design folder when creating or renaming it.
Objects
Object Description
Name field Specify a name for the design folder. The name must be
unique within the parent folder. For example, if the folder
structure is A > B > C and A > B > D, you cannot create a
folder with name C or D under B. However, you could
create a folder C or D directly under A. The name displays
red if it is a duplicate of an existing folder name or a
design name.
Create or Rename Click to create or rename the design folder.
Related Topics

December 2023
New Property Dialog Box
New Property Dialog Box

To access: Click the New button on the Properties tab of a dialog box for editing an object or
design.
Used to specify the name of a new property on an object or design.
Objects
Table 12-59. New Property Dialog Box Contents
Field Description
Property Name Enter the name for the property. If you are adding a property to an
object type for which properties have been defined in the Object Type
Information in Capital Project Manager, you can, alternatively, select a
property name from the list.

December 2023

To access: Click File > Options from the main menu on the Change Manager Apply ECO
Dialog Box.
Used to control a number of different options including translation settings, change policies, and
setup.
Note
Description
These are used when applying changes from an ECO impacted design using the “Change
Manager Apply ECO” dialog box. The different options are organized on separate tab pages to
ease accessibility.
Objects
Table 12-60. Options (Apply ECO) Dialog Box Contents
Field Description
Change Policy Tab This tab is used to specify the change policies that may be applied
during the apply ECO process. Change policies, configured by
project in Capital Project Manager, allow you to define a set of
rules to govern the update of harness components with incoming
source information. Refer to “Creating a Change Policy” in the
Capital Project Manager User Guide for more information on
creating and maintaining Change Policies.
Change Policy This option to allows you to select a Change Policy to apply to the
ECO processing.
Synchronize Cavity If selected, performing a synchronize action on a connector will
Components also synchronize all its cavity components. If cleared, cavity
components are not synchronized.
Setup Tab This tab enables the selection of custom plugin processors. These
processors modify the data prior to, or after, the application of the
selected bridge adaptor during import or export operations. See
Extensibility Plugins for more information on deploying plugins.
Bridge Processor This option allows you to specify the processor plugin. There can
be multiple plugins for the same application and this enables the
switching between them depending on the adaptor or customer.
Related Topics

December 2023


December 2023
Plugins Dialog Box
Plugins Dialog Box

To access: Press Space Bar and enter Plugins.
Used to view the details of any extensibility plugins that you have installed, to reload
extensibility plugins and to select an extensibility plugin when specifying one in a field.
Objects
Table 12-61. Plugins Dialog Box Contents
Field Description
Available Plugins Lists the details for the extensibility plugins that you have installed.
• Name
The name of the plugin. Read-only.
• Version
The version of the plugin. Read-only.
• Type
The type of plugin (for example, Constraint or DRC). Read-only.
• Language
The language of the plugin, either Java or Script. Read-only.
• Path
The absolute path of the parent folder for the script plug-in or the
absolute path of the JAR file for a Java plugin). Read-only.
• File
The file name for a script or the class name for Java plugin. Read-
only.
Details Click to open the Plugin Details Dialog Box, where you can view the
plugin details, description and the implemented plugin interfaces for
the currently selected plugin. Optional.
Reload All Click to reload the installed extensibility plugins if you have changed a
plugin and do not want to restart the application in which you are
working. Optional.
OK Click to exit the dialog after selecting an extensibility plugin. Optional.

December 2023
Plugin Details Dialog Box
Plugin Details Dialog Box

To access: Select a plugin and click Details on the Plugins dialog box.
Used to view the details of any extensibility plugins that you have installed and to reload
extensibility plugins.
Objects
Table 12-62. Plugin Details Dialog Box Contents
Field Description
Name The name of the plugin. Read-only.
Version The version of the plugin. Read-only.
Type The type of plugin (for example, Constraint or DRC). Read-only.
Language The language of the plugin, either Java or Script. Read-only.
Path The absolute path of the parent folder for the script plug-in or the
absolute path of the JAR file for a Java plugin). Read-only.
File The file name for a script or the class name for Java plugin. Read-
only.
URL Either the URL value for the Script plug-in, or the Java plugin. Read-
only.
Description A description of the plugin. Read-only.
Classpath The absolute paths to the Java plugin classes. Read-only.
Implemented plugin A list of the plugin interfaces. Read-only.
interfaces

December 2023
Query Criteria Dialog Box

To access: Click View > Filter from the main menu on the Change Manager Apply ECO
Dialog Box. Alternatively click the Filter button.
Used to filter the items displayed in the Harness Objects grid of the Change Manager Apply
ECO dialog box.
Note
Objects
Table 12-63. Query Criteria Dialog Box Contents
Field Description
Show Insulation Run Specifies whether insulations included in an insulation run are
Content displayed as objects. Default is selected.
Origin Specifies the harness objects to display in the grid, based on their
origin:
• Source
With this option selected, the grid lists all supported objects
found in the ECO change record.
• Target
With this option selected, the grid lists all supported objects
found in the open target harness design.
Unlinked Objects Specifies whether harness objects that are not linked should be
listed in the grid (selected) or not (cleared).
No Longer Linked Objects This option is only available when the Origin is set to Target. With
this option selected, objects in the open harness design that retain
an source id attribute, from an object in the source data that has
since been deleted, are displayed.

December 2023
Table 12-63. Query Criteria Dialog Box Contents (cont.)

Field Description
Linked Objects Specifies whether linked objects should be displayed (selected) or
not (cleared). Upon selecting this option, the following options are
all selected by default:
• Connectivity Mismatch
Specifies whether linked objects, for which connectivity (the
number of cavities, wire terminations, and so on) is different,
are displayed (selected) or not displayed (cleared).
• Attr\Prop Mismatch
Specifies whether linked objects for which one or more
attributes or properties are different are displayed (selected) or
not (cleared).
• Synchronized
Specifies whether objects that have been synchronized
(connectivity and properties match in both linked objects)
should be displayed (selected) or not (cleared).
Related Topics

December 2023
Release Designs Dialog Box

To access: In a design application, press Space Bar and enter Release, then click the
button on the ribbon.

Used to select designs that you want to release and to specify settings for the release process.
Objects
Table 12-64. Release Designs Dialog Box Contents
Field Description
Designs browser Displays the designs available for editing from the open project
in the design application that you are using. Select the designs to
release.
In Capital Harness Designer, you can right-click a composite
design and select Select Child Designs to select all of its
derivative designs.
In Capital Harness Designer Modular, you can right-click a
parent design and select Select Child Designs to select all of its
child designs.
Transition To Lists the release levels that are available to transition to. Select
the release level with which you want to transition the release
level of the designs.
Release Levels Filter Click the release levels filter icon ( ) to only show release
levels of a particular type.
Enter Filter String ( ) / Clear In the field next to the Enter Filter String icon ( ), enter a
Filter String ( ) series of characters. A filter is applied to the Designs browser so
that only designs with names containing that series of characters
are listed, or that have the same release level.
Note: The release level name is appended to the Design
name and revision.
The behavior of the filter varies depending on such things as
whether you use wildcards and the case (upper or lower) of the
specified characters. See also “Browser Tab and Dialog Box
Filters” on page 880.
Click the Clear Filter String icon ( ) to clear the filter and
view all available designs again.

December 2023
Table 12-64. Release Designs Dialog Box Contents (cont.)

Field Description
Show designs in active build Displayed only in Capital Logic Designer when Capital Wiring
list / Show only Logic Integrator is enabled or when a build list is active.
Designs / Show only Filters the Designs browser so that only designs in the active
Topology Designs build list, only Capital Logic Designer designs or only Capital
Wiring Integrator designs are displayed.
Design rule checks browser Displays the design rule checks that will be run on the designs
when you click OK.
These are specified in the Project Preferences for an application
(the appropriate preferences are displayed when you select the
Checks node for an application in the Project Preferences
Dialog Box).
Annotate results If a diagram has a border with the property CHECK_RESULTS
and you check this box, the diagram will be annotated to show
that the design has been verified after a successful run of the
design rule checks. The annotation includes the date and the ID
of the user who ran the checks. See Creating a Border in the
Capital Symbol Designer User Guide for further information
about creating a border to add to diagrams.
If the checks find an error and are therefore unsuccessful, the
diagram will not be annotated and any pre-existing annotation
in the value of the border's CHECK_RESULTS property is reset
to the value from the border.
Treat warnings as errors If cleared, the system considers a design rule check
unsuccessful, if it has a severity level of error and finds a
problem.
If you check this box, the system treats any checks with a
severity level of warning like checks with a severity level of
error. That means, a design rule check is unsuccessful if it has a
severity level of error or warning and finds a problem.
Related Topics
Enforcing Design Rule Checks During Release Level Transitions

December 2023

To access: Press Space Bar and enter Build.
Use this dialog box to specify, create and modify customized reports for viewing as tables on
diagrams, in Design Inspectors, for internal reports, and in Capital E/E Reporter.
Objects
Table 12-65. Report Builder Dialog Box Contents
Field Description
Enables the creation of a new report
Loads an existing report (as a plugin). Opens the Plugins folder
allowing you to select the required file.
Compiles and saves the report.
Makes the report available in Capital Logic Designer. The objects
available for inclusion in the report depend on the tool selected.
Makes the report available in Capital Systems Integrator and
Capital Wiring Integrator. The objects available for inclusion in
the report depend on the tool selected.
Makes the report available in Capital Harness Designer. The
objects available for inclusion in the report depend on the tool
selected.
Click to generate output as an embedded report.
Click to generate output as a table to be used in a style set.
Click to generate a design inspector report.
Click to add columns to the report.
Click to remove the selected column from the report.
Click to specify the contents of the column.
Displays the objects that can be reported according to the tool(s)
selected. Click the icons to include in, or remove from the report.
Related Topics
Design Inspectors

December 2023
Set separation distances Dialog Box
Set separation distances Dialog Box

To access: Click the Set Separation action on the 3D ribbon tab at the top of the application.
Used to import and set separation categories and distances for the 3D data in a design.
Objects
Object Description
Current file Indicates the name of the comma-separated value (CSV) file
used to set the current categories and distances.
Browse Opens a dialog box to locate and select the CSV file to use
to set the categories and distances.
First category and second Specifies the two categories for which a minimum
category separation distance is specified in this row.
For an explanation of what separation categories and
distances are, see “Creating a File of Separation Categories
and Distances” on page 510.
Minimum separation The minimum separation distance allowed between wires of
distance the separation categories in this row. For example, a wire
with category B must be separated by a distance of 10 from
a wire with category C.
Save Saves the categories and distances against the currently
active design.
Related Topics
Creating a File of Separation Categories and Distances

December 2023

To access: Click Apply Change on the Applicable Changes Dialog Box.
The Simulate Change Output tab displays in the output window below the open diagram. It
reports the results of applying the ECO, without the design changes being committed.
You can click the hyperlinked object names in the tab to jump to them on the target design.
Note
Objects
• An example is shown below.
Usage Notes
Figure 12-28. Simulate Change Tab
Related Topics

December 2023
Printing Dialogs
Printing Dialogs
This section offers a description of dialog boxes related to printing functions. For each dialog
DXF Page Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925
Edit File Name Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
Print Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
Print to File Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
SVG Page Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936

December 2023
CGM Page Settings Dialog Box

To access: Click the Configure button to the right of the Format field on the Print to File Dialog
Box, with a format of CGM selected.
Used to configure the creation of a CGM file format document from exported design data.
Note
The default values displayed in this dialog box, font mapping choices and diagnostics can be
amended in the file cgmprops.xml located in your Capital_home/config installation folder.
Amendments will have a system wide effect and should only be made by your CGM expert
System Administrator.
Objects
Table 12-66. CGM Page Settings Dialog Box Contents
Field Description
Line Thickness Scale Use to specify a factor by which line thickness will be adjusted to
Factor maintain the display rendering accuracy between the Capital data and
the CGM format. Default value is 1.0.
Line Pattern Scale Use to specify a factor by which line patterns, such as dotted lines and
Factor dot and dash size, will be adjusted to maintain the display rendering
accuracy between the Capital data and the CGM format. Default value
is 1.0.
Hatching Pattern Scale Use to specify a factor by which hatching patterns will be adjusted to
the CGM format. Default value is 1.0.
Resolution Select a resolution of either Standard or High from the dropdown list.
Standard resolution creates CGM files using 16-bit coordinates,
suitable for most standard paper sizes.
High resolution creates CGM files using 32-bit coordinates. Select if
the paper size exceeds 15 meters.
Note: The created file size will be larger when using High
resolution.
Related Topics
Print to a File
DXF Page Settings Dialog Box
PDF Page Settings Dialog Box
SVG Page Settings Dialog Box
Print to File Dialog Box

December 2023

Box, with a format of DXF selected.
Used to configure the creation of a DXF file format document from exported design data.
Objects
Table 12-67. DXF Page Settings Dialog Box Contents
Field Description
Write Extended Font Select to write out the full font name in the DXF file, to aid any
Information future mapping that is required.
Related Topics
Print to a File

December 2023
Edit File Name Dialog Box
Edit File Name Dialog Box

To access: Click the ellipsis (...) button to the right of the Filename field in the Print to File
Dialog Box.
Used to specify the way in which the file names of exported design data are created.
Objects
Table 12-68. Edit File Name Dialog Box Contents
Field Description
Keyword This field offers a list of all diagram attributes that can be included in a
filename. To select an attribute, click it and then click the Add button
to move it into the Entries list. When the data is exported and the
filename generated, the value of the selected attribute is extracted and
inserted into the filename.
Text This field allows the entry of a string of alphanumeric characters for
insertion into the filename. Enter the characters to be used, and then
click the Add button to move the string into the Entries field. When the
filename is generated, any text entries will be inserted as entered here.
Entries This field displays all attributes and text inserts (in quotation marks) in
the order they will be used when constructing filenames for exported
design data, with the entry at the top of the list being used first. To
change the order of items in the list, select an item to move, and then
click the Up or Down button as appropriate. To delete an item from the
list, select the item, and then click the Remove button.
Preview This field displays a preview of how the filename, constructed from the
Entries and Text entered above, will look.
Related Topics
Print to a File

December 2023
Edit Print Region Groups Dialog Box

To access: Press Space Bar and enter Print Region Settings, or opened automatically when
placing a print region in a design or border symbol. Also accessed by clicking the ellipsis
(...) button at the top of the Print Dialog Box when a Print type of Print Region is selected.
Used to configure print regions on a design, whether created within the design or imported as
part of a border symbol. Also used to select print regions for printing.
Objects
Table 12-69. Edit Print Region Groups Dialog Box Contents
Field Description
Print Region Name A unique label used to identify the print region, both within this dialog
box on the design, where it is displayed in the bottom-left corner of the
print region outline. Print regions are given a default name of Print
Region followed by an incrementing number, but this can be
overridden as long as the new name is unique within the design.
Mandatory.
If opened from within a tool other than Capital Symbol Designer, this
column also lists any print regions configured within the border symbol
in use. These print regions will be displayed with the border name
appended to the Print Region Name, and a icon is displayed at the
beginning of the row, indicating that this print region cannot be
renamed. Print regions created within the current design are preceded
by a icon, indicating that they can be renamed.
Active Specifies whether the print region is available for selection in the Print
dialog box (selected) or whether it is unavailable for selection
(cleared). Mandatory.
When accessed from the Print dialog box, this setting indicates whether
the print region should be included in the print.
Visible Specifies whether the print region is displayed on the design (selected)
or whether it is hidden (cleared). Mandatory.
This option is not available when the dialog box is opened from the
Print dialog box.
Locked Specifies whether the print region is locked in position on the design
(selected) or whether it is unlocked (cleared). You can lock or unlock
print regions individually or all at once. Mandatory.

December 2023
Table 12-69. Edit Print Region Groups Dialog Box Contents (cont.)
Field Description
Order The order in which print regions appear in the dialog box defines the
order in which they are printed. If a number of print regions exist they
are grouped together by type. You may rearrange the order of print
regions within their group, or push a whole group up or down. You
cannot move a print region outside of its group. The print order is
maintained when the design is saved.
This option is not available when the dialog box is opened from the
Print dialog box.
Usage Notes
To move a print region within the list, select it, and then click one of the following:
• to move the selected print region or group to the top of the list.
• to move the selected print region or group up one position in the list.
• to move the selected print region or group down one position in the list.
• to move the selected print region or group to the bottom of the list.

December 2023

To access: Click the Configure button to the right of the Format field in the Print to File Dialog
Box, with a format of PDF selected.
Used to configure the creation of a PDF document from exported design data.
Objects
Table 12-70. PDF Page Settings Dialog Box Contents
Field Description
Page Size Dropdown list of supported page sizes and their dimensions. Select
Custom to enable the Width, Height, and Units fields below.
Mandatory.
Width Displays the width relevant to the page size selected in the Page Size
field above. If Custom is selected as the Page Size, this field is enabled
and a manual width can be entered. Otherwise this field is read-only.
Mandatory.
Height Displays the height relevant to the page size selected in the Page Size
field above. If Custom is selected as the Page Size, this field is enabled
and a manual height can be entered. Otherwise this field is read-only.
Mandatory.
Units Displays the dimension units, in mm, cm or inches, relevant to the page
size selected in the Page Size field above. If Custom is selected as the
Page Size, this field is enabled and a manual selection can be made.
Otherwise this field is read-only. Mandatory.
Orientation Specifies whether the PDF file should be generated with the page(s) in
Landscape (horizontal) or Portrait (vertical) layout. Mandatory.
Color Specifies whether the PDF file should be generated in Color or Black
& White. Mandatory.
Printable Area Specifies the parts of the diagram that will be included in the export.
Mandatory. Select from:
Fit To Page
Everything on the diagram is added to the export and the output is sized
to fit on the Page Size selected.
Fit To Border
The output is sized so that the border reaches the edges of the Page Size
selected. Any design elements placed outside the border are not
included in the export.

December 2023
Table 12-70. PDF Page Settings Dialog Box Contents (cont.)

Field Description
Output File When multiple diagrams have been selected for export, this setting
specifies whether the diagrams should be exported as a Single File, in
which each diagram is printed to a single page, or as Multiple Files, in
which case each diagram is exported as a single file with a unique file
name. Mandatory.
Line Pattern Scale Allows you to set a dash multiplier figure that stretches or shrinks
Factor dashes relative to the size of output page. This allows for greater
control over the rendering of dashed lines. Optional.
Related Topics
Print to a File

December 2023
Print Dialog Box
Print Dialog Box

To access: Press Space Bar and enter Print.
Used to configure one or more diagrams for printing.
Objects
Table 12-71. Print Dialog Box Contents
Field Description
Print Specifies the diagrams or print regions to be included in the print. Mandatory.
Select one of the following options from the dropdown list:
• Project
All diagrams belonging to the open project are included in the print. With
this option selected, clicking Configure to the right of the field displays
the Project Diagram Settings Dialog Box, from where you can refine the
selection of diagrams to be printed.
• Design
All diagrams belonging to the current design are included in the print.
• Diagram
Only the currently open diagram is printed.
• Selection
Only the designs and diagrams selected in the Project Browser are printed.
• Print Region
Only the content within the specified print regions (belonging to the
currently open diagram) is included in the print. With this option selection,
clicking the ellipsis (...) button to the right of the field displays the Edit
Print Region Groups Dialog Box, from where you can specify the print
regions to be printed.
Configure This button has a function dictated by the setting of the Print option:
If Project or Selection are selected, clicking this button displays the Project
Diagram Settings Dialog Box, allowing you to specify whether to print all or
only the latest design revisions, and whether to include derivative designs in
the print.
If Print Regions is selected, clicking this button displays the Edit Print Region
Groups Dialog Box, allowing you to specify the regions to be included in the
print.
Printer Displays the name of the currently selected print device. Mandatory.
Printer Setup Displays a generic Print dialog box, allowing you to select and configure any
printer or print device that is available to you. Optional.
Plotter Select when sending a print to a plotter. This ensures that the device’s
continuous paper feed is handled correctly. Optional.

December 2023
Print Dialog Box
Table 12-71. Print Dialog Box Contents (cont.)

Field Description
Scaling Specifies the size at which the selected diagram(s) are printed. Mandatory.
Select one of the following options:
• Fit to Paper
This option specifies that each diagram should be printed to fit on a single
sheet of paper, of a size specified in the Page Setup dialog box for the
selected printing device. Diagrams are resized as needed to fit.
• Print to Scale
This option specifies that each diagram should be printed at 100% size, as
dictated by the design’s grid spacing value (as specified in the currently
applied style set; see the Diagram Styling User Guide for more
information). Alternatively, diagrams can be printed larger or smaller by
specifying a new percentage value, either by overwriting the value in the
field to the right, or by clicking the up- and down-arrow buttons.
Clip To Border With this option selected, only those diagram elements falling within the
border outline are printed; any harness elements falling outside of the border
will be ignored. With this option cleared, all harness elements are printed,
even those placed outside of the border. Mandatory.
Black/White With this option selected, printed output is generated using only black lines/
Only text against a white background, regardless of the specified text/line colors in
use in a diagram. Optional.
Line Pattern Allows you to set a dash multiplier figure that stretches or shrinks dashes
Scale Factor relative to the size of output page. This allows for greater control over the
rendering of dashed lines. Optional.
Usage Notes
• The option to create multiple diagrams is a licensed operation; if you do not have the
required license, yet are attempting to print a diagram from a design with multiple
diagrams, no printed output is generated.
• If a diagram has an associated border, the “Clip To Border” option will be selected by
default. If the “Clip To Border” option is selected for a diagram without an associated
border, the setting will be ignored when the diagram is printed.
Related Topics

December 2023

To access: Press Space Bar and enter Print to File.
Used to configure the export of one or more diagrams to either PDF, DXF, CGM, or SVG
format.
Objects
Table 12-72. Print to File Dialog Box Contents
Field Description
Export Specifies the diagrams to be included in the export. Mandatory. Select
one of the following options from the dropdown list:
• Project
All diagrams belonging to the open project are included in the
export. With this option selected, click the Configure button to the
right of the field, to display the Project Diagram Settings Dialog
Box and refine the selection of diagrams to be exported.
• Design
All diagrams belonging to the current design are included in the
export.
• Diagram
Only the currently open diagram is exported.
• Selection
Only the designs and diagrams selected in the Project Browser are
printed. With this option selected, click the Configure button to the
right of the field, to display the Project Diagram Settings dialog box
and refine the selection of diagrams to be exported.
• Print Regions
Only the content within the specified print regions (belonging to the
currently open diagram) is included in the print. With this option
selection, click the Configure button to the right of the field, to
display the Edit Print Region Groups Dialog Box and specify the
print regions to be printed.
Configure This button has a function dictated by the setting of the Export option:
If Project or Selection are selected, click to display the Project Diagram
Settings Dialog Box, and specify whether to print all or only the latest
design revisions, and whether to include derivative designs in the print.
If Design or Diagram is selected, this button is not enabled.
If Print Regions is selected, click to display the Edit Print Region
Groups Dialog Box, and specify the regions to be included in the print.

December 2023
Table 12-72. Print to File Dialog Box Contents (cont.)

Field Description
Format Specifies the target format to which the diagram is exported.
Mandatory. Select from:
• PDF
Exports the design data in Adobe’s Portable Document Format
(.pdf). With this option selected, click the Configure button to the
right of the field, to display the PDF Page Settings Dialog Box and
configure the export.
• DXF
Exports the design data in AutoCAD DXF (Drawing Interchange
Format, or Drawing Exchange Format) format. With this option
selected, click the Configure button to the right of the field, to
display the DXF Page Settings Dialog Box and configure the
export.
• CGM
Exports the design data in the W3C group WebCGM format
(.cgm). With this option selected, click the Configure button to the
right of the field, to display the CGM Page Settings Dialog Box and
configure the export.
• SVG
This format is not available if the Export type of Print Regions is
selected. Exports the design data as a Lean SVG, (Siemens
proprietary Scalar Vector Graphics format). With this option
selected, click the Configure button to the right of the field, to
display the SVG Page Settings Dialog Box and configure the
export.
Filename Displays the currently configured format used to construct the
filename(s) for the exported data. This defaults to {Diagram}
indicating that the diagram name will be used and appended with the
file extension appropriate to the selected format. Click the ellipsis (...)
button to the right of the field, to display the Edit File Name Dialog
Box, and specify the way in which file names are constructed.
Location Displays the path to the directory in which the exported files will be
placed. Click the ellipsis (...) button to the right of the field, to display a
file browser dialog box, and navigate to the required location to be
displayed in the field upon selection.
Related Topics
Print to a File

December 2023
Project Diagram Settings Dialog Box
Project Diagram Settings Dialog Box

To access: Click the Configure button to the right of the Export option on the Print to File
Dialog Box when the Export option is set to Project or Selection. Alternatively, click the
Configure button to the right of the Print option on the Print Dialog Box when the Print
option is set to Project or Selection.
Used to refine the selection of diagrams to be printed.
Objects
Table 12-73. Project Diagram Settings Dialog Box Contents
Field Description
Latest Design Revisions / All Specify whether to print all revisions of each design, or only the
Design Revisions latest revision. Mandatory.
Include Derivative Diagrams Select to send any derivatives for printing along with the
selected composite design. With this option cleared, only the
composite design is printed. Mandatory.
Related Topics

December 2023

Box, with a format of SVG selected. Examples of the effects of the settings on rendered
SVG’s can be found here “SVG Page Settings Examples” on page 679
Used to configure the creation of an SVG file format document from exported design data.
Note
The default values displayed in this dialog box, and various other SVG configuration
parameters can be amended in the file svgprops.xml located in your Capital_home/config
installation folder. Amendments will have a system wide effect and should only be made by
your SVG expert System Administrator.
Objects
Table 12-74. SVG Page Settings Dialog Box Contents
Field Description
Line Thickness Scale Use to specify a factor by which line thickness will be adjusted to
the SVG format. Default value is 1.0.
Minimum Line Width Use to specify a minimum SVG line width. Default value is 1.0.
Display Width Use to specify an initial size for the width of the created SVG. Default
value is 1024.0.
Display Height Use to specify an initial size for the height of the created SVG. Default
value is 768.0.
Line Pattern Scale Use to specify a factor by which line patterns, such as dotted lines and
Factor dot and dash size, will be adjusted to maintain the display rendering
accuracy between the Capital data and the SVG format. Default value
is 0.5.
Fill Pattern Scale Use to specify a factor by which fill patterns will be adjusted to
the SVG format. Default value is 0.5.
Related Topics
Print to a File

December 2023
Rules and Constraints Dialogs
Rules and Constraints Dialogs

This section offers a description of dialog boxes related to rules and constraints. For each dialog
Condition Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
Constraint Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941
Define Rules Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 942
Rule Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944

December 2023
Condition Dialog Box

To access:
• In Capital Harness Designer and Capital Harness Designer Modular
o Click the editable string {any} (by default) in a relevant constraint in the Define
Rules Dialog Box, and then select Edit or New.
• In Capital Harness Process Designer and Capital Harness Costing
o Click the editable string {any} (by default) on the Conditions or Exclusions tabs of
the Edit Patterns Dialog Box, or in the Create Formula Dialog Box / Edit Formula
Dialog Box or Create Task Dialog Box, and then select Edit or New.
• In Capital E/E Insight
o Click an editable string in a metric element definition displayed in the Edit Metrics
Dialog Box, or a constraint query in the Edit Design Properties Dialog Box, and then
select Edit or New.
Used to create or edit a condition using a simple query expression. This condition is used to
determine which definition is used to calculate the metric element value for a particular object,
or when specifying queries in constraints.
Figure 12-29. Condition Dialog Box
Objects
Table 12-75. Condition Dialog Box Contents
Field Description
Name Enter the name of the query expression used for the condition. The
query expression is saved to the database and made available for use
wherever query expressions can be selected. Mandatory.

December 2023
Table 12-75. Condition Dialog Box Contents (cont.)

Field Description
Condition Window Used to define the simple query expression. Mandatory.
Click ( ) to add a term to the expression. Depending on the
preceding element, the following terms may be available:
Attribute/Property/Value/Calculation/Condition
If you select Attribute or Property, that term is added to the window.
Click the term to display either, a dropdown list of available attributes
or a field to enter a property name.
If you select Value, 0.0 is added to the window. Click that value to
display a field and enter a different value.
If you select Calculation or Condition, that term is added to the
window. Click the term to display a dropdown list of available queries
or plugins.
Brackets can be used to control the query evaluation order.
Operators Select an operator from the following:
= Equal to
≠ Not equal to
< Less than
> Greater than
≤ Less than or equal to
≥ Greater than or equal to
is Set — the attribute or property is not blank
Starts with — queries objects starting with
Contains — queries objects containing
Ends with — queries objects ending with
is Like — queries objects similar to the term in the second argument
Figure 12-30. Operators

December 2023
Table 12-75. Condition Dialog Box Contents (cont.)

Field Description
AND/OR Specifies whether you want to add something to the previous term
(AND) or whether you want to specify an alternative to the previous
term (OR).
Usage Notes
• To clear the window, click Clear Calculation ( ).
• To delete the last term in the expression, click Remove last element ( ).
• Click Go to Advanced Editor ( ), to access the Edit Query Expressions dialog box,
and use the advanced query editing functionality (see “Query Expressions” in the
Capital Project Manager User Guide).
Related Topics
Creating a Metric Element
Editing a Metric Element Definition
Deleting a Metric Element Definition

December 2023
Constraint Selection Dialog Box
Constraint Selection Dialog Box

To access: Click the Add Constraint ( ) button in the Define Rules Dialog Box or the Add
Constraint ( ) button on the Rules Tab in Properties Dialog Box of an object.
Used to select constraints that you want to apply to an object or add to a rule.
Objects
Table 12-76. Constraint Selection Dialog Box Contents
Field Description
Constraints browser Expand the browser to view the available constraints. The
constraints are grouped under the applications in which they can
be used. Click a constraint to select it. You can select multiple
constraints.
Note that when you are applying constraints to an object, only
constraints that are applicable to that object are displayed.
Hover over a constraint name to see the full constraint construct.
Related Topics
Defining Rules

December 2023
Define Rules Dialog Box

To access: In a design tool, Press Space Bar and enter Rules. In Capital Project Manager either
double-click the Rules folder for the project, right-click the Rules folder for the project and
select Edit or right-click the system’s Rule Libraries folder.
This dialog box is titled Edit Rules when you open it in Capital Project Manager. Use this
dialog box to create, edit, rename, or delete rules that can be used in a project.
Objects
Table 12-77. Define Rules Dialog Box Contents
Field Description
Rules window Lists the rules that have been created.
New Creates a new rule that can be used in the project. Displays the Rule
Name dialog where you specify a name for it. When you click OK,
the rule name is added to the Rules window.
Rename Renames the selected rule in the Rules window. Displays the
Rename Rule dialog where you specify the new name. When you
click OK, the new name is displayed in the Rules window.
Delete Deletes the selected rule in the Rules window.
Add Rule Reference Adds the constraints from one rule to the rule selected in the Rules
window. Displays the Rule Selection Dialog Box where you select
the rule whose constraints you are adding. When you click OK, the
constraints are displayed in the Constraints window (grouped under
the name of the rule from which they come).
Add Constraint Adds one or more constraints to the rule selected in the Rules
window. Displays the Constraint Selection Dialog Box where you
select the constraints. When you click OK, the constraints are
displayed in the Constraints window.
Constraints window Displays the constraints included in the rule selected in the Rules
window. You can edit the constraints in this window.
indicates a rule reference (where the constraints from another rule
have been added to this rule). Click the rule name to display its
constraints directly below it. Alternatively, you can hold your mouse
cursor over the rule name and its constraints are displayed in a
tooltip. You cannot edit those constraints here. You can only edit
them by editing the rule itself.
indicates a standard constraint. Click to display a dropdown list
to select a customized version of the constraint (if any have been
made available using Extensibility Plugins).
Click to delete a constraint.

December 2023
Table 12-77. Define Rules Dialog Box Contents (cont.)

Field Description
Show All Constraints/ Controls which constraints are displayed in the Constraints window.
<Type_of_Constraint> All Constraints displays all constraints included in the rule selected
in the Rules window. Otherwise, the dropdown list includes the
types of constraint used in that rule. Select a constraint type to
display only the constraints of that type.
Related Topics
Defining Rules

December 2023
Rule Selection Dialog Box
Rule Selection Dialog Box

To access: Click the Add Rule Reference ( ) button on the Define Rules Dialog Box or click
the Add Rule Reference ( ) button on the Rules Tab in Properties Dialog Box of an
object.
Use this dialog to select a rule whose constraints you want to add to another rule or to an object.
Objects
Table 12-78. Rule Selection Dialog Box Contents
Field Description
Rule window Displays the rules that are available for selection. Select the rule
whose constraints you want to add and click OK.
Related Topics
Defining Rules
Rules Tab in Properties Dialog Box

To access: Open the Properties dialog for an object.
Use this tab to edit the rules and constraints that apply to the object whose properties you are
editing.
Table 12-79. Rules Tab in Properties Dialog Box Contents

Field Description
Add Rule Reference Used to add the constraints from one rule to the object whose
properties you are editing. Displays the Rule Selection Dialog Box
where you select the rule whose constraints you are adding. When
you click OK, the constraints are displayed in the Constraints
window (grouped under the name of the rule from which they
come).
Add Constraint Used to add one or more constraints to the object whose properties
you are editing. Displays the Constraint Selection Dialog Box where
you select the constraints. When you click OK, the constraints are
displayed in the Constraints window.

December 2023
Rules Tab in Properties Dialog Box
Table 12-79. Rules Tab in Properties Dialog Box Contents (cont.)

Field Description
Constraints window Displays all of the constraints that are applicable to the object whose
properties you are editing. These constraints may have been applied
directly to that object or to objects higher up the object hierarchy.
The constraints are grouped under the objects to which they were
applied.
In the case of a bundle, for example, constraints are displayed for the
bundle itself, for the harness to which it belongs and for the diagram.
You can edit only those constraints that have been applied directly to
the object whose properties you are editing.
If you editing the properties for multiple objects, this window
displays only constraints that are common to all of those objects.If
there are no common constraints, the window is blank.
indicates a rule. Click the rule name to display its constraints
directly below it. Alternatively, you can hold your mouse cursor
over the rule name and its constraints are displayed in a tooltip. You
cannot edit those constraints here. You can only edit them by editing
the rule itself in the Define Rules Dialog Box.
indicates that the rule does not contain any rules or constraints
that are applicable to the object.
indicates a standard constraint. Click to display a dropdown list
to select a customized version of the constraint (if any have been
made available using Extensibility Plugins).
Click to delete a constraint.
Show All Constraints/ Controls which constraints are displayed in the Constraints window.
<Type_of_Constraint> All Constraints displays all constraints applied to the object.
Otherwise, the dropdown list includes the types of constraint
applied. Select a constraint type to display only the constraints of
that type.
Related Topics

December 2023
Collaborate Dialogs
Collaborate Dialogs
This section offers a description of Collaborate dialog boxes. For each dialog box, all fields are
listed, along with a full description of the field’s function.
Associated Objects Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 947
Checklist Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
Comments Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
Edit Collaborate Options Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
Manage Notifications Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 956
Notes Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 957

December 2023
Associated Objects Dialog Box
Associated Objects Dialog Box

To access: In the Comments or Notes tab, click Associate on an existing comment or note.
Used to reference, or associate, individual design objects in specific comments or notes.
Figure 12-31. Manage Associate Objects Dialog Box
Objects
Object Description
Object List Displays a list of objects that have been selected from
either the diagram or design browser windows.
Remove objects Removes any highlighted objects from the list.
OK All objects listed in the dialog box are added as
associated objects to the note or comment.
Usage Notes
• To add objects to the list, click an object either in the Design Browser or Diagram
Window.
• To select multiple objects in the Object List, use the Shift-click action.

December 2023
Checklist Tab
Checklist Tab
To access: Press Space Bar and enter Checklists.
The Checklist tab displays checklist items associated with the design and provides functionality
to create, search, or filter the items.
Figure 12-32. Checklist Tab
Objects
Object Description
Search Search the Checklist tabs for a specified string. The
first match is highlighted in orange, additional
matches in yellow. You can navigate through
multiple matches using arrow keys that appear next
to the search box.
Filter by: Filter which checklist items are visible based on
these properties:
• All - Shows all checklist items in the currently
selected design.
• Completed - Shows all completed checklist
items in the current design.
• Pending - Shows all pending checklist items in
the current design.
Add Checklist Opens the Collaborate Editor Dialog Box to create a

new checklist item.

December 2023
Checklist Tab
Object Description
Refresh Checklist As designs and diagrams can have shared read/write
access, refresh checklist will load any changes to the
checklist made remotely.
Edit Edit an existing checklist item (administrator or item
creator only).
Delete Delete an existing checklist item (administrator or
item creator only).
Item Status Toggle Display the checklist item’s status. Checklist item
states can be toggled between Pending (red/white)
and Complete (green).
Related Topics
Checklist

December 2023
Collaborate Editor Dialog Box

To access: Use one of the following methods:
• In the Comments, Notes, or Checklist tab page:
o Click the Add button.
o On an existing comment, note, or checklist item click Edit or Reply.

• Right-click a diagram in the Project Browser Window and select Collaborate > Add
Comment or Collaborate > Add Note
• Right-click over an object in the diagram or Design Browser Window and select
Collaborate > Add Comment or Collaborate > Add Note
Used to create, edit, or format the content of Collaborate comments, notes, and checklist items.
Figure 12-33. Collaborate Editor Dialog Box
Objects
Object Description
Insert a hyperlink to an external location. Once clicked,
Insert Link an Insert External Hyperlink dialog box opens with the
following fields:
• Link address - Select an object in a diagram or enter
an external hyperlink location.
• Display text (optional) - Used to change the text
displayed in the hyperlink from default text based on
the Link address content.
Insert a graphical image. Images file must be of type:
Insert Image *jpg, *.jpeg, *.png, *.gif

December 2023
Object Description
Once clicked, an Insert User dialog box opens to allow a
Insert User user name to be entered. Only user accounts with
domain access for the project or design can be selected.
An inserted, or tagged user, receives an email once. The
email notifies them of the comment or note content they
are tagged in.
Insert Link To Selected Insert a hyperlink to an object(s) selected in the diagram.
Objects
Bold, Italic, Underline, Apply emphasis/formatting to text.
Strikethrough
Insert a full width horizontal line.

Insert Horizontal Rule
Alignment Alignment formating, content can be:
• Left aligned
• Right aligned
• Centered
• Justified
Apply or remove indentations to content.
Indentation
Create a list, either bulleted or numbered.
Lists
Color Opens a color picker to apply text or background color

changes to content.
Note Name. Add a text-based identifying tag to a note.
Available only when
creating or editing a note.

December 2023
Comments Tab
Comments Tab
To access: Press Space Bar and enter Comments.
The Comments tab displays comments associated with the design and provides functionality to
create, search, or filter the comments.
Figure 12-34. Comments Tab
Objects
Object Description
Search Search the Comments tab for a specified string. The
first match is highlighted in orange, additional
matches in yellow. You can navigate through
multiple matches using arrow keys that appear next
to the search box.
Filter by: Limit which comments are visible based on a filter
type:
• Design - Shows all unresolved comments in the
current design.
• All - Shows all comments in current design.
• Diagram - Shows any unresolved comments with
associated objects in the active diagram.
• Resolved - Shows any resolved comments in the
current design.
Add Comment Opens the Collaborate Editor Dialog Box to create a

new comment.
Refresh Comments As designs and diagrams can have shared read/write
access, refresh comments will load any changes to
the comments made remotely.
Reply Add a sub-comment to an existing comment.

December 2023
Comments Tab
Object Description
Edit Edit an existing comment (administrator or
comment creator only).
Delete Delete an existing comment (administrator or
comment creator only).
Associate Opens the Associated Objects Dialog Box to
associate design objects with this comment.
Resolve Mark this comment as resolved, and add a sub-
comment (optional). Once resolved this comment
will now only appear under the Resolved or All
filter.
Reopen Add a sub-comment and mark this comment as open
again. The comment will become visible on standard
filters again.
Associated Objects List objects associated with this comment. Navigate
to the object in the diagram by clicking the listed
associated object name.
Related Topics
Comments

December 2023
Edit Collaborate Options Dialog Box

To access: In your open dialog box, click the Collaborate Options button.
Used to select which types of Collaborate data are included in an action. Changes to attributes
here override the default export properties set for the Collaborate set in Capital Project
Manager.
Note
This topic covers a number of different user actions that result in the use of this dialog box,
such as exporting or copying a design. The user action is reflected in the dialog box title.
Figure 12-35. Example Dialog Box: Edit Collaborate Design Export Options
Dialog Box
Objects
Object Description
Unresolved Comments Check to include all
unresolved comments in the
action.
Resolved Comments Check to include all resolved
comments in the action.
Pending Checklists Check to include all pending
(unresolved) checklist items
in the action.
Completed Checklists Check to include all
completed (resolved)
checklist items in the action.

December 2023
Object Description
Notes Check to include all notes in
the action.
Watchlists Check to include all users
from the Manage
Notifications list for the
action.
Usage Notes
To complete the action with only unresolved data included, you must select Unresolved
Comments and Pending Checklists, and then clear Resolved Comments and Completed
Checklists.

December 2023
Manage Notifications Dialog Box
Manage Notifications Dialog Box

To access: Press Space Bar and enter Notifications.
Used to associate a user account with a design, any user on the watch list will receive an email
when new Collaborate content is created or edited.
Objects
Object Description
Username List of users who have domain access to the current active
project / design.
Add user to Opens an Add Users dialog box. Add a user to the notification
notifications list list for this design. Only users with domain access for the
design (from Capital Access Manager) can be added.
Remove user from Removes the selected user from the notification list.
notifications list
Usage Notes
• Only user accounts created in Capital Access Manager, with domain access, will be
listed as choices when selecting users to be added to a design watch list.
Related Topics
Notifications
Enabling Collaborate Notify Me Updates

December 2023
Notes Tab
Notes Tab
To access: Press Space Bar and enter Notes.
The Notes tab displays notes associated with the design and provides the functionality to create,
search, or filter the notes.
Figure 12-36. Notes Tab
Objects
Object Description
Search Search the Notes tab for a specified string. The first
match is highlighted in orange, additional matches
in yellow. You can navigate through multiple
matches using arrow keys that appear next to the
search box.
Filter by: Limit which notes are visible based on a filter
property:
• Design - Show all notes in the current design.
• Diagram - Shows only notes with associated
objects in the active diagram.
Add Note Opens the Collaborate Editor Dialog Box for the
creation of a new note.
Refresh Notes As designs and diagrams can have shared read/write
access, refresh notes will load any changes to the
notes made remotely.
Edit Edit an existing note (administrator or note creator
only).
Delete Delete an existing note (administrator or note creator
only).

December 2023
Notes Tab
Object Description
Associate Opens the Associated Objects Dialog Box to
associate design objects with this note.
Associated Objects List objects associated with this note. Navigate to
objects in the diagram by clicking the listed
associated object name.
Related Topics
Notes

December 2023
Warning Dialogs
Warning Dialogs
This section offers a description of warning dialog boxes. For each dialog box, all fields are
listed, along with a full description of the field’s function.
Undoable Operation Confirmation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 960

December 2023
Undoable Operation Confirmation Dialog Box
Undoable Operation Confirmation Dialog Box

To access: Displayed when you perform an action that cannot be undone because it causes the
diagram to be saved automatically.
Used to confirm whether you want to perform an action or operation that cannot be undone.
Objects
Table 12-80. Undoable Operation Confirmation Dialog Box Contents
Field Description
Don’t show me this Specifies whether you want this message to be displayed the next time
message again that you perform an undoable action (cleared) or whether you do not
want this message to be displayed again (selected).
OK Click to proceed with the undoable action.
Cancel Click to cancel the undoable action.

December 2023
Design Log Dialogs
Design Log Dialogs

This section describes the dialogs associated with viewing and configuring Design Logs:
Design Log Filter Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
Design Log Viewer Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 964
View Design Logs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 966

December 2023
Design Log Event Filter Options Dialog Box
Design Log Event Filter Options Dialog Box

To access: Press Space Bar and enter Event View.
Used to set default filtering behavior for all logs displayed in the Design Log Viewer Dialog
Box.
Objects
Table 12-81. Design Log Event Filter Dialog Box Contents
Field Description
Filter Options The following line items can be turned off or on in all design logs by
default. Select an option to have it displayed; clear an option to hide
that line item. The following line items are available: Header, Info,
Warnings, Errors, Blank.
Usage Notes
The Filter Options can be set interactively in the Design Log Viewer Dialog Box.
Related Topics
Viewing Design Logs

December 2023
Design Log Filter Options Dialog Box
Design Log Filter Options Dialog Box

To access: Press Space Bar and enter Log View.
Used to set default filtering behavior for the list of design logs offered in the View Design Logs
Dialog Box.
Objects
Table 12-82. Design Log Filter Options Dialog Box Contents
Field Description
View Log Displays historical design logs generated for the design, or only the
latest log. Select View All or View Latest as appropriate.
Filter By Controls the display of design logs in which warnings and/or errors
were generated.
Warnings
Select to display design logs in which warnings were generated;
clear to hide all logs containing warnings.
Errors
Select to display design logs in which errors were generated; clear to
hide all logs containing errors.
Related Topics
Viewing Design Logs
View Design Logs Dialog Box

December 2023
Design Log Viewer Dialog Box

To access: Double-click a log in the Logs grid of the View Design Logs Dialog Box, or select a
log and click View.
Used to display the contents of a design log. The dialog box displays in two different layouts for
Capital Connector related log files and non-Connector related log files.
Objects
Table 12-83. Design Log Viewer Dialog Box (Non-Connector Logs) Contents
Field Description
Filter Options The following Event Type line items can be turned off or on in the
design log. Select an option to have it displayed; clear an option to
hide that line item. The following line items are available: Header,
Info, Warnings, Errors, Blank.
Refresh Click to update the Events grid to reflect any changes made to the
Filter Options.
Events This window displays the contents of the log file.
Table 12-84. Design Log Viewer Dialog Box (Capita Connector Logs) Contents
Field Description
Severity Whether the result is an error ( ), a warning ( ), or an information
message ( ).
Operation The particular type of bridging activity that has been run (for
example, Place, Autolink, Synchronize, and so on).
Object type The specific object type on which a bridging activity has been run.
To make the list more manageable it can be filtered to show only the
required object types. These are:
• All
• Connector
• Bundle
• Splice
• Clip
• Grommet
• Tape
• Tube
• Wire
• Multicore
Object The specific object on which a bridging activity has been run.

December 2023
Table 12-84. Design Log Viewer Dialog Box (Capita Connector Logs) Contents
Field Description
Message Detailed message about the bridging activity that has occurred. You
can click an object in the message to jump to that object in the
diagram window.
Usage Notes
• You can open multiple viewers simultaneously to review the content of the logs and
interact with the diagram at the same time.
• The Filter Options can be set as defaults in the Design Log Event Filter Options Dialog
Box.
Related Topics
Viewing Design Logs

December 2023

To access: Press Space Bar and enter View Design Log. The dialog can be accessed in a
different mode (with the dialog title Open Design Logs) by pressing Space Bar and entering
Open Design Log.
When the dialog box is accessed as View Design Logs, it is used to select log files to view in the
Design Log Viewer dialog box. When the dialog is accessed as Open Design Logs, it is used to
select a log to open in the Output Window.
Objects
Table 12-85. View Design Logs Dialog Contents
Field Description
View Log Displays all historical design logs generated for the design, or only
the latest log. Select View All or View Latest as appropriate.
Filter By Controls the display of design logs in which warnings and/or errors
were generated.
Warnings
Select to display design logs in which warnings were generated;
clear to hide all logs containing warnings.
Errors
Select to display design logs in which errors were generated; clear to
hide all logs containing errors.
Preview Only displays when the dialog box is opened in Open Design Log
mode. Click to open the log in the Output Window.
View Only displays when the dialog box is opened in View Design Log
mode. Click to the view the selected log in the Design Log Viewer
Dialog Box.

December 2023
Table 12-85. View Design Logs Dialog Contents (cont.)

Field Description
Logs This grid displays the design logs available for the currently open
harness. To view a log, select it and then click View > Preview;
alternatively, double-click the log in the grid. The following
information is displayed for each log:
Log
This column lists the logs available, named according to the
processes from which they were generated. When you are viewing
the available logs for a composite harness, the logs are displayed
beneath the composite or derivatives to which they relate.
User
The name of the user who ran the harness process from which the
log was generated.
Time
The time at which the process from which the log was generated was
started.
Date
The date upon which the process from which the log was generated
was started.
Warning
If the log contains one or more warnings, this column displays a
symbol.
Error
If the log contains one or more errors, this column displays a
symbol.
Related Topics
Viewing Design Logs

December 2023
Help Button Landing Pages for Dialog Boxes

The following topics are displayed when you click the Help button or press F1 for a dialog box
in the software.
Add Shared Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
Add Text Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 971
Applicable Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
Assemblies Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 972
Batch Translate Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
Build Lists Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
Capital Systems Integrator or Topology Design Filter Help . . . . . . . . . . . . . . . . . . . . . . 973
CGM Page Settings Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973
Change Manager Preview ECO Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
Choose Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 974
Collaborate Manage Notifications Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
Collaborate Notes Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
Condition Dialog Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 976
Copy Design Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Design Assistant Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Design Effectivity Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Design Log Viewer Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Design Revision/Build List Selection Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Define Rules Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Details Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980

December 2023
Edit Border Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980

Edit Breakout/Spot Tape Details Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
Edit Build List Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
Edit Capital Configuration Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
Edit Design Properties Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
Edit Multicore or Overbraid Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Edit Objects Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Edit Print Region Groups Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
Edit Project Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
Edit Shared Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983
Embedded Library Portal Import Configuration Help . . . . . . . . . . . . . . . . . . . . . . . . . . 984
Engineering Change Orders Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
Freeze / Unfreeze Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
Image Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
Import Designs to Project/Copying to Project Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
Import Designs to Project Wizard/Copying to Project Wizard Help . . . . . . . . . . . . . . . 986
Manage Designs & Effectivity Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
Managing Collaborate Data Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
Map Equivalent Devices Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 986
Merge Into Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
New Folder or Rename Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 987
New Project Dialog Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
Open Project Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
Options (Apply ECO) Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 988
Options Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989
PDF Page Settings Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 989

December 2023
Add Shared Help

Plugins Dialog Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
Print Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
Print to File Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 990
Project Usages Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992
Properties and Attributes Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 992
Query Criteria Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993
Release Designs Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994
Replacing Composite Symbols for Shared Objects Help . . . . . . . . . . . . . . . . . . . . . . . . . 994
Rules and Constraints Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994
Rule Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
Select by Attribute/Property Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
Select By Name Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 995
Select Designs to Copy Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
Select Project Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 996
Share Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
Split Table Dialog Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 997
Symbol Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
Undoable Operation Confirmation Dialog Box Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
Update Symbol - Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
View Design Logs Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 998
Add Shared Help

For logical designs:
• Understanding Shared Objects concepts

December 2023
Add Shared Pins/Ports Help
• Understanding Shared Objects and Domains concepts

• Adding an Instance of a Shared Device or Connector as a Parameterized Object
• Adding an Instance of a Shared Device as a Symbol
• Adding an Instance of a Shared Splice
• Automatic Sharing of ICDs
• The Add Shared Dialog Boxes fields
For functional designs:
• Adding an Instance of a Shared Function as a Parameterized Object

• Adding an Instance of a Shared Function as a Symbol
• The Add Shared Function Dialog Box fields
Add Shared Pins/Ports Help

For logical design objects:

• Editing Shared Devices and Connectors
• The Add Shared Pins Dialog Box fields
• Promoting a Device or Connector
For functional design objects:
• Editing Shared Functions

• The Add Shared Ports Dialog Box fields
• Promoting a Function to a Shared Function
Add Text Help

• The Add Text Dialog Box fields
• Adding a Text Frame to a Diagram

December 2023
Applicable Options Help
Applicable Options Help

• The Applicable Options concepts
• The Applicable Options Dialog Box fields
• Creating a Composite Harness Design
• Creating a Derivative Harness Design
• Specifying the Applicable Options for a Design
Assemblies Help
• The Edit Assemblies Dialog Box fields.
• The Edit Assembly Dialog Box fields.
• The New/Edit Assembly Dialog Box fields.
• The Assemblies concept.
• Creating an Assembly
• Deleting an Assembly
• Editing an Assembly
• Renaming an Assembly
• Removing an Object from an Assembly
• Creating an Assembly from the Part Selection Dialog
• Adding Assemblies Containing Connectivity
• Adding Associated Comment Graphics or Comment Symbols to an Assembly
• Adding Objects Within the Associated Comment Graphic Boundary to an Assembly
• Extending the Selection of Objects for an Assembly Comment Graphic or Symbol
• Removing Objects No Longer Within the Associated Comment Graphic Boundary from
an Assembly
• Updating Assembly Contents

December 2023
Batch Translate Help
Batch Translate Help

• Understanding Diagram Language Translation concepts
• The Batch Translate Dialog Box fields
• “Converting Text Strings into Translations” on page 90
Build Lists Help

• Understanding Build List concepts
• The Build lists Dialog Box fields
• Viewing a Build Lists Report
Capital Systems Integrator or Topology Design

Filter Help
• The Capital Systems Integrator or Topology Design Filter Dialog Box fields
• Filtering the Objects Displayed in a Capital Systems Integrator or Capital Wiring
Systems Diagram
CGM Page Settings Help

• The CGM Page Settings Dialog Box fields
• Print to a File
• Print to File Dialog Box
• The PDF Page Settings Dialog Box fields
• The DXF Page Settings Dialog Box fields
• The SVG Page Settings Dialog Box fields

December 2023
Change Manager Apply ECO Help
Change Manager Apply ECO Help

• Understanding Engineering Change Orders concepts
• The Change Manager Apply ECO Dialog Box fields
• Capture and Apply a Change Within an ECO
• Harness Object Behavior on Applying ECO Changes
• Viewing Engineering Change Orders
Change Manager Preview ECO Help

• The Change Manager Preview ECO Dialog Box fields
Choose Options Help

• Options and Option Relationships
• The Choose Options Dialog Box fields
• Creating an Option at Project Level
• Creating an Option Folder at Project Level
• Defining Inclusive and Exclusive Relationships for an Option
• Creating an Option Combination at Project Level
• Adding a Valid Selection to an Option Combination
• Deleting a Valid Selection from an Option Combination
• Deleting an Option

December 2023
Collaborate Checklists Help
Collaborate Checklists Help

• Understanding how Checklist are used
• Viewing Comments, Notes and Checklists
• Creating a Comment, Note or Checklist Item
• Modifying a Comment, Note, or Checklist Item (Including resolving checklist items)
• The Checklist Tab fields
• An Introduction to Collaborate
Collaborate Comments Help

• Understanding how Comments are used
• Modifying a Comment, Note, or Checklist Item (Including resolving comments)
• Replying to a Comment
• The Comments Tab fields
Collaborate Editor Help

• The Collaborate Editor Dialog Box fields
• The Associated Objects Dialog Box fields
Collaborate Manage Notifications Help

• Understanding Collaborate Notifications
• Enabling Collaborate Notify Me Updates with the Notify Me ribbon action

December 2023
Collaborate Notes Help
• Adding, or tagging, users in Collaborate content, see the Insert User field in the
• Adding new users to the notification system, see Modifying Collaborate Notifications
• Changing the email notification frequency, see Modifying Collaborate Notifications
• The Manage Notifications Dialog Box fields
Collaborate Notes Help

• Understanding how Notes are used
• Modifying a Comment, Note, or Checklist Item
• The Notes Tab fields
• The Collaborate Editor Dialog Box fields
• Adding Notes to a diagram using the styling table
Compare Designs Help

• The Compare Designs Dialog Box fields
• Comparing Objects and Their Properties in Design Revisions or Build Lists
• Mapping Equivalent Devices During Design Comparison
Condition Dialog Help

• Using Conditions in Capital Harness Process Designer
• Understanding Capital E/E Insight concepts
o Creating a Metric Element
o Editing a Metric Element Definition

December 2023
Convert to Ring Terminal Help
o Deleting a Metric Element Definition

• Creating components in Capital Harness Designer and Capital Harness Designer
Modular:
o Automatically creating components
o Marker Text
• The Condition Dialog Box fields
Convert to Ring Terminal Help

Capital Logic Designer

• Converting Plugs to Ring Terminals
• Adding a Plug, Jack, Inline or Ring Terminal Manually
Capital Harness Designer

• Editing the Attributes and Properties of a Connector
• Ring Terminals
Copy Design Help

• Copying a Design within a Project
• Copying a Merged or Combined Formboard Design
• Copy Design Dialog Box fields
Create New Design Revision Help

• The Design Revision concepts
• Revisioning a Merged or Combined Formboard Design
• The Create New Design Revision Dialog Box fields
• Creating a Design Revision

December 2023
Design Assistant Help
Design Assistant Help

• The Design Assistant in Capital Systems Integrator
• The Design Assistant in Capital Wiring Integrator
Design Effectivity Help

• Understanding Effectivity concepts
• Understanding Build List concepts
• The Design Effectivity Dialog Box fields
• Creating a Build List Using Effectivity
Design Log Event Filter Options Help

• Design Logs
• Viewing Design Logs
• The Design Log Event Filter Options Dialog Box fields
Design Log Filter Options Help

• Design Logs
• The Design Log Filter Options Dialog Box fields
Design Log Viewer Help

• Design Logs
• The Design Log Viewer Dialog Box fields

December 2023
Design Revision/Build List Selection Help
Design Revision/Build List Selection Help

• The Design Revision - Build List Selection Dialog Box fields
• The Select Design Dialog Box fields
• Mass Design Revision and Effectivity Changes
• Selecting Specific Designs for Mass Revision and Effectivity Changes
• Mapping Equivalent Devices During Design Comparison
Design Rule Checks Help

• The Design Rule Checks Dialog Box fields
• Design Rule Check Descriptions
• Running Design Rule Checks
• Design Rule Checks Output Window
• Release Designs Help
Define Rules Help

• Understanding Rules and Constraints concepts
• Usage Examples for Rules and Constraints in Capital Systems Integrator
• Defining Rules
• Capital Harness Designer and Capital Harness Designer Modular Constraints
o Attributes and Properties
o Routing
o Module Assignation
o Cavity Details Generation
o Auto Create and Delete Components

December 2023
Details Help
o Markers
• Capital Systems Integrator constraint descriptions
• Constraints for Platform Designs in Capital Systems Architect
• Editable Elements in Constraints
Details Help
• The fields on the 3Dfindit.com Configure Import Dialog Box.
• The fields on the component Details Dialog Box.
DXF Page Settings Help

• Print to a File
Edit Border Help

• The Edit Border Dialog Box fields
• Adding a Border to a Diagram
• Replacing a Border on a Diagram
• Removing a Border from a Diagram

December 2023
Edit Breakout/Spot Tape Details Help
Edit Breakout/Spot Tape Details Help

• The Edit Breakout/Spot Tape Details Dialog Box fields
Edit Build List Help

• The Build List concept
• The Edit Build List Dialog Box fields
• Creating a Build List
• Creating a Build List Using Effectivity
• Defining a Current Vehicle Configuration Using a Dynamic Build List
• Editing an Existing Build List
• Copying the Content of a Build List to a New Build List
Edit Capital Configuration Help

• The Edit Capital Configuration Dialog Box fields
• Specifying the Memory Allocation of Capital Applications
• To enable Capital Formboard Designer, see “Enabling Capital Formboard Designer” in
the Capital Harness Designer User Guide
• To enable Capital E/E Insight, see “Enabling Capital E/E Insight” in the Capital Design
Tools - Common Functions User Guide
• Enabling add-on functionality (licenses), see “License Policy” in the Capital Access
Manager User Guide
Edit Design Properties Help

• The Edit Design Properties Dialog Box fields
• Editing a Property for a Design
• Rules and Constraints concepts

December 2023
Edit Effectivity Help
Edit Effectivity Help

• The Edit Effectivity Dialog Box fields
• Understanding Mass Design Revision and Effectivity Changes
• Using ECOs for Mass Revision and Effectivity Changes
• Using Build Lists for Mass Revision and Effectivity Changes
Edit File Name Help

• The Edit File Name Dialog Box fields
• Print to a File
Edit Multicore or Overbraid Help

In logical designs:
• The Edit Multicore Dialog Box fields

• The Edit Overbraid Dialog Box fields
• The Generic Multicore Dialog Box fields
• The Overbraid Dialog Box fields
• The Create Shared Multicore Dialog Box fields
• The Create Shared Overbraid Dialog Box fields
• Creating a Multicore or Overbraid Without a Library Part
• Creating a Shared Multicore or Overbraid
In Capital Systems Integrator designs:
• Creating a Multicore
Edit Objects Help

• Bulk Editing the Properties of Design Objects

December 2023
Edit Option Expression Help
• The fields of the Edit Objects Dialog Box.
Edit Option Expression Help

• Options and Option Expression concepts
• The Edit Option Expression Dialog Box fields
• The Set Variant Dialog Box fields
Edit Print Region Groups Help

• Understanding Print Regions
• The Edit Print Region Groups Dialog Box fields
• Adding a Print Region to a Design
• Editing a Print Region
• Locking a Print Region in Position
Edit Project Help

• The Edit Project Dialog Box fields
Edit Properties Help

• The Edit Properties Dialog Box fields
Edit Shared Help



December 2023
Embedded Library Portal Import Configuration Help

• The Edit Shared Dialog Boxes fields
• Editing a Shared Pin List

• The Edit Shared Function Dialog Box fields
• Editing a Shared Port List
Embedded Library Portal Import Configuration Help

• Understanding Configuring Internal Part Numbers on Import concepts.
• The Configure Import Dialog Box fields.
Engineering Change Orders Help

• The Engineering Change Orders Dialog Box fields
• Creating an Engineering Change Order
• The Assign ECOs Dialog Box fields
• Understanding ECO Import and Export concepts
• The Export ECOs Dialog Box fields
• Information about Deleting an Engineering Change Order.

December 2023
Fill Pattern Selection Help
Fill Pattern Selection Help

• The Fill Pattern Selection Dialog Box fields
• Editing the Graphical Properties of a Graphical Shape
Freeze / Unfreeze Help

• Freezing and Unfreezing Shared Objects
For freeze / unfreeze concepts in logical designs:
• Freeze and Unfreeze Shared Objects

For freeze / unfreeze concepts and tasks at the project level:
• Freeze and Unfreeze Shared Objects
Generate Advanced Names Help

• Understanding Advanced Naming Functionality concepts
• The Generate Advanced Names Dialog Box fields
• Generating Names for Selected Objects in a Diagram
• Generating Names for all Objects in a Build List, Design or Diagram
Image Selection Help

• The Image Selection Dialog Box fields
• Adding an Image to a Diagram
• Changing the Image in an Image Frame
Import Designs to Project/Copying to Project Help

• The Import Designs to Project - Copying to Project Dialog Box fields

December 2023
Import Designs to Project Wizard/Copying to Project Wizard Help
• Copying Designs From One Project to Another

• Overview of Copying Designs Between Projects
• Importing Designs into a Project
Import Designs to Project Wizard/Copying to

Project Wizard Help
• The Import Designs to Project Wizard - Copying to Project Wizard Dialog Box fields
• Overview of Copying Designs Between Projects
Manage Designs & Effectivity Help

• The Manage Designs & Effectivity Dialog Box fields
Managing Collaborate Data Help

• Managing Collaborate Data in a Project or Design Action
• The Edit Collaborate Options Dialog Box fields
Map Equivalent Devices Help

• The Map Equivalent Devices Dialog Box fields

December 2023
Map Pins/Ports Help
Map Pins/Ports Help

• Assigning a New Library Part to an Object

• Updating Library Parts Assigned to Components
• Replacing a Symbol with a Compatible Symbol
• Updating Devices and Mapping Pins
• The Map Pins Dialog Box fields
• Replacing a Symbol with a Compatible Symbol

• The Map Ports Dialog fields
Merge Into Help

• The Merge Into Dialog Box fields

• Merging Non-shared Objects
• The Merge Into Dialog fields

• Merging Instances of Design Wide Objects
New Folder or Rename Help

• The New Folder or Rename Dialog Box fields
• Editing Design Folders in Design Applications
• The Design Folder concept

December 2023
New Project Dialog Help
New Project Dialog Help

• Creating a Project
• The New Project Dialog Box fields
New Property Help

• The New Property Dialog Box fields
• The Properties Dialog Box fields
• Editing a Property for a Design
• Understanding Object Attributes and Properties concepts
Open Project Help

• Opening a Project
• The Open Project Dialog Box fields
Options (Apply ECO) Help

• The Options (Apply ECO) Dialog Box fields
• Capturing a Change with an ECO
• Applying a Stored Change from an ECO

December 2023
Options Help
Options Help
• Options and Option Relationships
• The Options Dialog Box fields
• Creating an Option at Project Level
• Creating an Option Folder at Project Level
• Defining Inclusive and Exclusive Relationships for an Option
• Creating an Option Combination at Project Level
• Adding a Valid Selection to an Option Combination
• Deleting a Valid Selection from an Option Combination
• Deleting an Option
Part Selection Help

• The Part Selection Dialog Box fields
• Capital Harness Designer Parts Browser
• Capital Systems Integrator Parts Browser
• Capital Logic Designer Parts Browser
• The Details Dialog Box fields
PDF Page Settings Help

• Print to a File

December 2023
Plugin Details Help
Plugin Details Help

• The Plugin Details Dialog Box fields
• The Plugins Dialog Box fields
Plugins Dialog Help

• The Plugins Dialog Box fields
• The Plugin Details Dialog Box fields
• Harness Processing Extensibility
• Information on Reloading Extensibility Plugins.
Print Help
• The Print Dialog Box fields
• Print to a Printer or Plotter
• Printing a Single Diagram
• Printing All Diagrams in a Project
• Printing All Diagrams in a Design
• Printing Selected Print Regions
Print to File Help

• The Print to File Dialog Box fields
• Print to a File
• CGM Page Settings Dialog Box
• DXF Page Settings Dialog Box
• PDF Page Settings Dialog Box
• SVG Page Settings Dialog Box

December 2023
Project Diagram Settings Help
Project Diagram Settings Help

• The Project Diagram Settings Dialog Box fields
• Printing All Diagrams in a Project
• Printing Selected Diagrams in a Project
Project Folders Help

• The Project Folders Dialog Box fields
Project Preferences Help

• The Project Preferences concept
• The Project Preferences Dialog Box fields
• Project Preferences for Capital Analysis Designs
• Project Preferences for Manufacturing Tools
• Project Preferences for Capital Device Modeler
• Project Preferences for Capital Harness Designer and Capital Harness Designer Modular
Designs
• Project Preferences for Capital Systems Integrator Designs
• Project Preferences for Capital Logic Designer Designs
• Project Preferences for Capital Project Manager
• Project Preferences for Capital Wiring Integrator Designs
• Project Preferences for Capital Systems Modeler Designs
• Project Preferences for Design Release
• General Project Preferences Applicable to all Applications
• Project Preferences - Checks Node
• Project Preferences for Platform Designs in Capital Systems Architect
• Design Rule Check Descriptions

December 2023
Project Usages Help
Project Usages Help

• The Where Used In Project Dialog Box fields
Properties and Attributes Help

Diagram Object Attributes and Properties

• The Propertied Graphic Dialog Box fields
• Editing an Object's General Attributes
• Simultaneous Editing of Multiple Objects
• Specifying the Name Attribute of an Object
• Editing the User-Defined Properties of an Object
• Defining Specification Attributes for a Conductor
• Modular connectors:
o An overview of Modular Connectors
o The Modular Tab (Properties Dialog Box) fields
• Editing the Graphical Attributes of an Object
• Propertied Graphic Dialog Box
• Assigning/Editing an Object's Options
• Specifying Option-Specific Values for Net Attributes and Properties
Editing Attributes and Properties

• The Properties Dialog Box fields
• The Edit Properties Dialog Box fields
• Editing an Object's General Attributes
• Simultaneous Editing of Multiple Objects

December 2023
Query Criteria Help
• Specifying the Name Attribute of an Object

• Editing the User-Defined Properties of an Object
• Defining Specification Attributes for a Conductor
• Editing the Graphical Attributes of an Object
• Graphical shapes and graphical objects:
o The Propertied Graphic Dialog Box fields
o Editing a Property Value of a Graphical Shape
o Editing the Graphical Properties of a Graphical Shape
• Assigning/Editing an Object's Options
• Specifying Option-Specific Values for Net Attributes and Properties
Connector Cavity Component Drivers

• Specifying Connector Cavity Component Drivers in Capital Logic Designer and Capital
Systems Integrator
• Connections Tab (Properties Dialog Box)
Symbols And Borders

• Adding a Port to a Function Symbol
• Specifying Attributes for a Function Symbol
• Working with User Defined Zones
• Using Drill Point Datums
Query Criteria Help

• The Query Criteria Dialog Box fields

December 2023
Release Designs Help
Release Designs Help

• The Release Designs Dialog Box fields
• Enforcing Design Rule Checks During Release Level Transitions
Replacing Composite Symbols for Shared Objects

Help
• Replacing Composite Symbols for Shared Devices

• Replacing Composite Symbols for Shared Functions
Rules and Constraints Selection Help

• Capital Harness Designer and Capital Harness Designer Modular Constraints
o Attributes and Properties
o Routing
o Module Assignation
o Cavity Details Generation
o Auto Create and Delete Components
o Markers
• Standard Constraints for Capital Systems Integrator

December 2023
Rule Selection Help
• Constraints for Platform Designs in Capital Systems Architect

Rule Selection Help

• Defining Rules
• Assigning a Rule or Constraint to an Object or Design
Rules Tab in Properties Help

• The Rules Tab in Properties Dialog Box fields
• Assigning a Rule or Constraint to an Object or Design
Save as Function or Device Symbol Help

• The Save as Function or Device Symbol Dialog Box fields
• In Capital Logic Designer: Saving Diagram Objects as a Device Symbol
• In Capital Systems Modeler: Saving Diagram Objects as a Function Symbol
Select by Attribute/Property Help

• Finding and Selecting Objects by Attribute or Property
• The Select by Attribute/Property Dialog Box fields
Select By Name Help

• Finding and Selecting Objects by Name

December 2023
Select Designs to Copy Help
• The Select By Name Dialog Box fields
Select Designs to Copy Help

• The Select Designs to Copy Dialog Box fields
• Concept information about Overview of Copying Designs Between Projects
Set Grid Defaults Help

• The Set Grid Defaults Dialog Box fields
Select Project Help

• The Select Project Dialog Box fields
• Exporting a Project
• Exporting a Project in Capital Compressed Format
• Creating a Logic Build List from a Pro Product Plan
Set separation distances Help

• Understanding how to work with Separation Categories and Distances
• Setting Separation Categories and Distances
• Creating a File of Separation Categories and Distances
• The Set separation distances Dialog Box fields
• The 3D Viewer concept

December 2023
Share Help
Share Help

• Promoting a Device or Connector
• Promoting a Splice
• The Share Dialog Box [Devices, Connectors and Splices] fields
• Creating a Shared Device Based on a Symbol
• The Create Shared Device Dialog Box fields
• Creating a Shared Splice Based on a Symbol
• The Create Shared Splice Dialog Box fields
• Promoting a Multicore or Overbraid
• The Share Dialog Box [Multicores and Overbraids] fields
• Promoting a Function to a Shared Function

• The Share Dialog Box [Functions] fields
Split Table Dialog Help

• The Split Table Dialog Box fields
SVG Page Settings Help

• Print to a File

December 2023
Symbol Selection Help

Symbol Selection Help

• The Symbol Selection Dialog Box fields
• Adding a Comment Symbol to a Diagram
Undoable Operation Confirmation Dialog Box Help

• The Undoable Operation Confirmation Dialog Box fields
Update Symbol - Options Help

• The Update Symbol - Options Dialog Box fields
View Design Logs Help

• The concepts of Design Logs
• Opening Design Logs
• The View Design Logs Dialog Box fields
• The Design Log Viewer Dialog Box fields
• The Design Log Filter Options Dialog Box fields
• The Design Log Event Filter Options Dialog Box fields

December 2023
Chapter 13
Capital E/E Insight
Capital E/E Insight is a product that provides functionality for measuring and assessing your
designs as well as conducting physical architectural trade studies in Capital Systems Integrator
(including Capital Configuration Optimizer), Capital Wiring Integrator, Capital Harness
Designer, Capital Harness Designer Modular, or Capital Systems Architect.
If you have a Capital E/E Insight license, you have access to all of its functionality and an
Insight tab is available at the bottom left of the application window. This enables you to create
studies on designs and to create/edit metrics that you use in those studies. If you use Capital
Configuration Optimizer or Capital Systems Architect, this functionality is included by default.
If you do not have a license, you have access to default metrics that can be run against designs
to measure and assess them. A Metrics tab is available at the bottom left of the application
window. There are fewer default metrics and you cannot modify them. See Viewing Metric
Results for the Open Design for instructions on how to view them.
Note
The system administrator enables access to add-on functionality (such as Capital E/E
Insight) by using license policies and user groups (see “License Policy” in the Capital
In order for an application to start with the Capital E/E Insight functionality enabled, you must
have also selected the Enable Insight option on the Edit Capital Configuration dialog box.
Enabling Capital E/E Insight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1001

Overview of Studies and Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
Studies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
Creating a Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
Editing a Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
Deleting a Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
Creating a Scenario (and Study) from the Insight Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
Default Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007
Creating a Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009

December 2023
Capital E/E Insight

Specifying the Architectural Cost of a Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
Viewing Metric Results for the Open Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013
Snapshots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1015
Taking a Snapshot of Metric Results for Current Design Data . . . . . . . . . . . . . . . . . . . . . 1015
Editing a Snapshot Name and Display Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
Opening a Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
Opening a Snapshot in the Insight Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017
Comparing Snapshots from Different Studies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
Comparing Snapshots from One or More Studies in the Insight Tab. . . . . . . . . . . . . . . . . 1019
Capital E/E Insight Dialog and Field Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020
Calculation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
Edit Snapshot Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1030
Edit Study Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031
Edit Study/Scenario Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
Metrics/Insight Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
Metrics Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
New Scenario Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038
New Study Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039
Snapshot Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042
Usage Example - Study of Alternative Harness Routing Paths. . . . . . . . . . . . . . . . . . . . 1044
Help Button Landing Pages for Capital E/E Insight Dialog Boxes . . . . . . . . . . . . . . . . . 1047
Edit Metrics Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
Edit Scenario Properties Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
Edit Study Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
New Scenario Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
New Study Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
Snapshot Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
Take Snapshot Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050

December 2023
Capital E/E Insight
Enabling Capital E/E Insight
Enabling Capital E/E Insight

The system administrator enables access to Capital E/E Insight by using license policies and
user groups. However, in order for an application to start with the Capital E/E Insight
functionality enabled, you must have also selected the Enable Insight option on the Edit
Capital Configuration dialog box.
Note
For information about creating and editing license policies, see “License Policy” in the
Capital Access Manager User Guide
If you do not have a Capital E/E Insight license, a Metrics tab is available at the bottom left of
the application window. It has a subset of default metrics that can be run against designs to
measure and assess them. There are fewer default metrics and you cannot modify them. This tab
is visible regardless of whether Capital E/E Insight is enabled.
Prerequisites
• You must have a valid license for Capital E/E Insight, and your user account must have
a license policy that includes Capital E/E Insight.
Procedure
1. In the Capital Application Launcher, click Configuration (located under Support at the
top); the Edit Capital Configuration dialog box is displayed.
2. Select the Enable Insight option (located at the bottom of the dialog) and click OK.
3. Close and re-start the Capital applications; when you next open the applications, the
Capital E/E Insight functionality will be available.
Results
An Insight tab with all of its functionality enabled is available at the bottom left of the
application window. This enables you to create studies on designs and to create/edit metrics that
you use in those studies.
Related Topics
Capital E/E Insight
Metrics/Insight Tab

December 2023
Capital E/E Insight
Overview of Studies and Scenarios

Capital E/E Insight uses the concepts of architectural studies and scenarios.
Studies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1002
Creating a Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
Editing a Study. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1003
Deleting a Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
Creating a Scenario (and Study) from the Insight Tab . . . . . . . . . . . . . . . . . . . . . . . . . . 1004
Studies
A study exists within a project and is a container in which an entire physical architectural design
evaluation can take place. The different architectural changes being considered and compared
are created and accessed within the context of a study.
For each study, you can decide which Metrics will be available and used to measure your
scenarios.
A study can contain multiple Scenarios. When evaluating or editing a scenario, you can take
Snapshots of the metric results when design changes are made. The metric results of these
snapshots can then be compared with each other or with the current (live) data in a design.
For an example of a study (including its scenarios), see “Usage Example - Study of Alternative
Harness Routing Paths” on page 1044.
Scenarios
Within a study, you can create multiple scenarios. The purpose of a scenario is to provide a
context for one of the design options being considered and compared as part of an architectural
exercise (that is, a study). You associate each scenario with a specific design revision. You can
associate a design revision with multiple scenarios. When a design revision is associated with a
scenario, you can still edit it using the standard functionality of the application for which it was
created.
The key metrics used in a scenario can be generated and viewed as its design revision is being
developed. When two or more scenarios are available within a study, you can compare their key
metrics. You might then carry forward the preferred scenario as the basis of the production
design.

December 2023
Capital E/E Insight
Creating a Study
Creating a Study
When working in Capital E/E Insight, you create a study and its scenarios in order to run design
evaluations.
Procedure
1. Right-click the project in the Project Browser Window and select New Study; the New
Study Dialog Box is displayed.
2. Specify the Name.
3. Add the scenarios to use:
a. Click Add new Scenario to Study ( ); a row is added to the Scenarios table.
b. Specify the Name of the scenario and the Design to be associated with the scenario.
c. Repeat steps a and b for each scenario you want to create.
4. In the Metrics window, select the metric elements to use in the study. For each metric,
click the Change Default Chart Type to display for Metric dropdown list (located on
the right of the metric line) and select the default chart type to use for the metric when
viewing metric results.
5. Select the Groups to make available to the Scenarios in the study, and click OK; the
study is added to the Project Browser Window and the scenarios are listed below it.
Related Topics
Editing a Study
Deleting a Study
Creating a Scenario (and Study) from the Insight Tab
Opening a Scenario
Editing a Study
You can add, edit, and remove scenarios, edit the metrics used in the study, and edit the groups
applied to the study metric results.
Procedure
1. Right-click the study in the Project Browser Window and select Edit Study; the Edit
Study Dialog Box is displayed.
2. Edit the study as required and click OK.

December 2023
Capital E/E Insight
Deleting a Study
Related Topics
Creating a Study
Deleting a Study
Opening a Scenario
Deleting a Study
You can delete a study in Capital E/E Insight when you no longer want to use it.
Procedure
1. Right-click on the study in the Project Browser Window.
2. Select Delete; all scenarios within the study are deleted along with the associations to
designs. The designs are not deleted.
Related Topics
Creating a Study
Editing a Study
Opening a Scenario
Creating a Scenario (and Study) from the Insight

Tab
You can create a new scenario (and new study if required) from the Insight tab displayed at the
bottom left of the application. The system automatically associates the scenario with the design
currently open in the diagram window.
Procedure
1. On the Insight tab (see Metrics/Insight Tab), click the Create a new scenario ( )
button; the New Scenario Dialog Box is displayed.
2. In the Study field, either select an existing study from the dropdown list or enter a name
for a new study.
3. Specify the Name of the scenario and click Create Scenario.
If you selected an existing study, you have completed creating the scenario.

December 2023
Capital E/E Insight
Opening a Scenario
If you entered the name for a new study, the New Study Dialog Box is displayed with
the new scenario in the Scenarios table (associated with the currently open design).
4. If required, add any additional scenarios to use in the study:
a. Click Add new Scenario to Study ( ); a row is added to the Scenarios table.
b. Specify the Name of the scenario and the Design to be associated with the scenario.
c. Repeat steps a and b for each scenario you want to create.
5. In the Metrics window, select the metric elements to use in the study. For each metric,
6. Select the Groups to make available to the scenarios in the study, and click OK.
Results
• The scenario is added to the Project Browser Window below the appropriate study.
• The currently open design/scenario switches to the newly created scenario.
Related Topics
Creating a Study
Editing a Study
Opening a Scenario
Opening a Scenario
When working with Capital E/E Insight, you can open a scenario and view its metric results.
Procedure
1. Double-click the scenario in the Project Browser Window
or
Right-click the scenario in the Project Browser Window
2. Select Open Scenario.
Results
• The design associated with the scenario is opened in the diagram window.

December 2023
Capital E/E Insight
Opening a Scenario
• The Insight tab (bottom left of application, see Metrics/Insight Tab) and Metrics Table
(in the Output Window at the bottom of the application) display the metric results for the
design.
For information about the interface elements (including information on changing chart type and
filtering the display of metric results, see “Metrics/Insight Tab” on page 1033).
Related Topics
Creating a Study
Editing a Study
Deleting a Study

December 2023
Capital E/E Insight
Metrics
Metrics
A metric is a single value calculated as a measure of ‘goodness’ (for example, cost or weight).
You define metrics at system level and you can apply them in all projects.
Each metric is calculated by adding together values for different types of object. These are
called metric elements and are listed separately when displayed in the interface. Metric
elements can be turned on or off when viewing a study to control whether they are used in
calculations or not.
You can export and import metrics from Capital Project Manager, see “Exporting Metrics” or
“Importing Metrics” in the Capital Project Manager User Guide.
Default Metrics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1007

Creating a Metric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1009
Specifying the Architectural Cost of a Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1012
Viewing Metric Results for the Open Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1013
Default Metrics
A metric can be applied to multiple studies (and scenarios) and can be used to judge which
scenario within a study best addresses the needs of that study.
Depending on whether you have a Capital E/E Insight license, the default metrics supplied for
the Metrics or Insight tab are:
• Measure: Cost
Calculates the total architectural cost of design objects. Available only if you have a
Capital E/E Insight license.
• Measure: Count
Calculates the total number of objects of a particular object type.
• Measure: Length
Calculates the total length of wires.
• Measure: Weight
Calculates the total weight of design objects. Available only if you have a Capital E/E
Insight license.

December 2023
Capital E/E Insight
Default Metrics
• Optimize: Harness Complexity

Used by Capital Configuration Optimizer to automatically optimize complexity
solutions. Available only if you have a Capital E/E Insight license and visible only when
a scenario is open in the diagram window.
• Report: Blank Cost Attribute
Counts the number of objects that do not have an assigned cost. These objects are
therefore reporting estimations in the cost metric. Available only if you have a Capital
E/E Insight license and visible only when a scenario is open in the diagram window.
• Report: Blank Part Number
Counts the number of objects that do not have an assigned part number. Available only
if you have a Capital E/E Insight license and visible only when a scenario is open in the
diagram window.
• Report: Blank Weight Attribute
Counts the number of objects that do not have an assigned weight. These objects are
therefore reporting estimations in the weight metric. Available only if you have a
Capital E/E Insight license and visible only when a scenario is open in the diagram
window.
• Report: Harness Complexity
Used to see complexity-related attributes quickly (for example, level counts and
giveaway costs). Available only if you have a Capital E/E Insight license and visible
only when a scenario is open in the diagram window.
Examples of metric elements for a cost metric could be Cost of Splices, Cost of Wires, Cost of
Connectors, and so on. The total cost would then be calculated by adding together each of these
metric elements.
Each metric element is calculated from one of a set of element definitions. Each definition will
apply to a subset of the objects in the metric element and only one applies to any particular
object. Examples for a Cost of Splice metric element could be the cost of a center-strip splice or
the cost of a normal splice.
Metric results can be viewed:
• For the current (live) design data on the Metrics/Insight Tab at the bottom left of the
application.
• For a snapshot either on the Insight tab or in the Snapshot Dialog Box. Available only if
you have a Capital E/E Insight license.
• For comparing snapshots either in the Compare Snapshots Dialog Box or Compare
Snapshot With Dialog Box. Available only if you have a Capital E/E Insight license.

December 2023
Capital E/E Insight
Creating a Metric
See the Capital E/E Insight Dialog and Field Reference topics, for information on filtering the
metric results and changing the chart type used in these dialogs.
If you have a Capital E/E Insight license, within the Edit Metrics Dialog Box, you can modify
the default metrics or even define new ones based on attributes and properties of design objects.
For even more flexibility, you can develop custom metrics and groups as part of an extensibility
plugin. For more information about developing and using extensibility plugins, see the
PluginDevelopment.pdf file that is located in the doc\plugin directory of your Capital
installation.
Related Topics
Creating a Metric
Deleting a Metric Element
Specifying the Architectural Cost of a Component
Viewing Metric Results for the Open Design
Creating a Metric
You can create a new (non-default) metric for use in Capital.
Procedure
1. Press Space Bar and enter Metrics; the Edit Metrics Dialog Box is displayed.
2. Click Add New Metric ( ); a new row is created in the Definition window.
3. Edit the name of the metric. Click elsewhere on the dialog to finish; the row is displayed
like the other metrics.
Related Topics
Metrics

December 2023
Capital E/E Insight

You can create a new metric element. Metric elements can be turned on or off in an architectural
study to control whether they are included in calculations.
Procedure
2. On the relevant metric type row, click the plus symbol (+); a new metric element name
is added below the metric.
Note
You can duplicate an existing metric element by right-clicking it and choosing
Duplicate; the duplicate is added below the same metric. Alternatively, you can
right-click an existing metric element and choose Copy or Cut. Right-click another
metric or one of its metric elements and choose Paste to add the copied or cut element
below it.
3. Edit the metric element name and click the color square in that row to select the color
that you want used to display the results for that metric element.
4. Define the element definitions:
a. Click Add New Definition ( ); the template for the new element definition is
added to the window.
b. Edit the element definition as required.
c. Repeat steps a and b for each element definition that you want to add.
Caution
The order in which the element definitions are listed dictates the order in which
they are calculated for design objects. If a design object matches more than one
element definition, only the value calculated for the first matching definition is
included in the metric result. This means that you should put the more specific
definitions at the top of the list and general definitions nearer the bottom.
5. Click OK.
Related Topics
Metrics
Creating a Metric

December 2023
Capital E/E Insight

You can delete a metric element when you no longer want to use it.
Procedure
2. In the Metrics window, either:
• Right-click the metric element and choose Delete.
• Click the metric element and click the minus symbol (-) on the relevant metric.
The metric element is deleted.
Related Topics
Metrics
Creating a Metric

You can edit the metric element definitions of an existing metric at any time.
Procedure
2. In the Metrics window, click the metric element; the element definitions are displayed in
the Definition window.
3. Edit the element definitions as required.
4. Click OK.
Related Topics
Metrics
Creating a Metric

December 2023
Capital E/E Insight


You can delete a metric element definition from an existing metric if you no longer want to use
it.
Procedure
2. In the Metrics window, click the metric element; the element definitions for the metric
element are displayed in the Definition window.
3. In the Definition window, select the element definition to be deleted and click Remove
Selected Definition ( ). The element definition is removed from the window.
4. Click OK.
Related Topics
Metrics
Creating a Metric

You can specify the Architectural Cost attribute for an instance of an object in a design. The
default Cost metric in Capital uses this attribute when calculating its result. In addition, the
attribute can be referenced when defining new metric element definitions.
It does not use a particular unit of measurement and is a generic value used for comparing the
cost of a component. For example, a cheaper component may have a value of “1” whereas a
more expensive component may have a value of “4” (four times the value of the cheaper
component).
Note
If the object instance has a library part associated, the Architectural Cost attribute takes its
value from the library part definition in Capital Component Manager and is read-only in the
design tool.

December 2023
Capital E/E Insight
Procedure
1. Right-click the object in the Design Browser Window or the Diagram Window and
select Properties; the Edit Properties dialog is displayed.
2. Click the General tab; the Architectural Cost attribute is listed. Edit the Value as
required and click OK.
Related Topics
Metrics
Creating a Metric

If you do not have a Capital E/E Insight license, you can view the results of some default
metrics for the design currently open in the diagram window.
The results for the Metrics are displayed on the Metrics tab displayed on the bottom left of the
application window (see “Metrics/Insight Tab” on page 1033 for full details of this tab) and in
the Metrics Table displayed in the Output Window at the bottom of the application.
For example, you could use the Length metric grouped by harness to view the length of wiring
in each harness.
Procedure
1. Click the Metrics tab.
2. Click the Group dropdown list and select the subset of design objects for which you
want to display metric results.
3. Click the Cycle Metric to display arrows to scroll through the available metrics.
The metric results chart on the tab updates as you scroll through the metrics.
The Metrics Table also updates in the Output Window.
Note
By default, you can display the results for Measure: Count and Measure: Length
metrics. Further metrics are available if you have a Capital E/E Insight license.

December 2023
Capital E/E Insight
Related Topics
Metrics
Capital E/E Insight

December 2023
Capital E/E Insight
Snapshots
Snapshots
A snapshot stores the metric results at a given design stage for a scenario. These results can be
compared with the current metric results for a scenario or with another snapshot, from the same
or a different study).
Taking a Snapshot of Metric Results for Current Design Data . . . . . . . . . . . . . . . . . . . 1015
Editing a Snapshot Name and Display Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
Opening a Snapshot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1016
Opening a Snapshot in the Insight Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1017
Comparing Snapshots from Different Studies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1018
Comparing Snapshots from One or More Studies in the Insight Tab . . . . . . . . . . . . . . 1019
Taking a Snapshot of Metric Results for Current

Design Data
When using Capital E/E Insight, you can take a snapshot of the metric results for the current
design data. You can compare these results with another snapshot from the same or a different
study.
Procedure
1. Open the scenario for which you want to take a snapshot (see Opening a Scenario).
2. On the Metrics/Insight Tab, click the Take a Snapshot of the current data button
( ); the Take Snapshot Dialog Box is displayed.
3. Specify the Name for the snapshot and the color you want to use to display the metric
results for it when comparing snapshots.
4. Click OK; the snapshot is added below the scenario in the Project Browser Window.
Related Topics
Snapshots
Editing a Snapshot Name and Display Color
Opening a Snapshot
Opening a Snapshot in the Insight Tab
Comparing Snapshots from One Study
Comparing Snapshots from Different Studies
Comparing Snapshots from One or More Studies in the Insight Tab

December 2023
Capital E/E Insight

You can edit the name and display color of an existing snapshot of metric results at any time.
Procedure
1. Right-click the snapshot in the Project Browser Window and select Edit; the Edit
Snapshot Dialog Box is displayed.
2. Edit the name and color as required.
3. Click OK.
Related Topics
Snapshots
Taking a Snapshot of Metric Results for Current Design Data
Opening a Snapshot
Opening a Snapshot
When working with Capital E/E Insight, you can open the Snapshot dialog box that displays the
metric results both in a chart and a table.
Procedure
1. Right-click the snapshot in the Project Browser Window and select Open; the Snapshot
2. Filter the metric results as required. See “Snapshot Dialog Box” on page 1042 for
information about the user-interface elements available on the dialog box.
Related Topics
Snapshots

December 2023
Capital E/E Insight

Capital E/E Insight allows you to open a snapshot in the Metrics/Insight Tab, which is located at
the bottom left of the application when a scenario is open.
Procedure
1. Open the scenario to which the snapshot belongs (see “Opening a Scenario” on
page 1005).
2. On the Metrics/Insight Tab, select the snapshot from the <Live> dropdown list; the
metric results for the snapshot are displayed in the metric results chart.
Related Topics
Snapshots
Opening a Snapshot

When working with Capital E/E Insight, you can compare the metric results from multiple
snapshots from one study.
Procedure
1. Right-click a snapshot in the Project Browser Window and select Compare snapshot
with followed by the second snapshot to be compared; the Compare Snapshot With
2. You can add other snapshots to the comparison by right-clicking the metric results chart
and selecting Add to Comparison followed by a snapshot or by dragging the additional
snapshot from the Project Browser Window into the Compare Snapshot With Dialog
Box.
3. Filter the metric results as required. See “Compare Snapshot With Dialog Box” on
page 1023 for information about the user-interface elements available on the dialog box.

December 2023
Capital E/E Insight
Related Topics
Snapshots
Opening a Snapshot

snapshots from different studies.
Procedure
1. Right-click a study name in the Project Browser Window and select Compare
Snapshots; the Compare Snapshots Dialog Box is displayed.
2. Select the snapshots that you want to compare by adding them to the Chosen window
and click OK; the Compare Snapshot With Dialog Box is displayed.
3. You can add other snapshots to the comparison by right-clicking the metric results chart
and selecting Add to Comparison followed by a snapshot.
Related Topics
Snapshots
Opening a Snapshot

December 2023
Capital E/E Insight
Comparing Snapshots from One or More Studies in

the Insight Tab
snapshots from one or more studies in the Metrics/Insight Tab, which is located at the bottom
left of the application when a scenario is open.
Procedure
1. Open the scenario to which the first snapshot belongs (see “Opening a Scenario” on
page 1005).
2. On the Metrics/Insight Tab, click Compare Snap-Shots ( ); the metric results for all
snapshots in the scenario are displayed in a spider chart in the metric results chart.
3. If you want to include a snapshot from another scenario or study in the comparison,
right-click the metric results chart and select Add to comparison followed by the
snapshot.
4. Filter the metric results as required. See “Metrics/Insight Tab” for information about the
user-interface elements available on the dialog box.
Related Topics
Snapshots
Opening a Snapshot

December 2023
Capital E/E Insight
Capital E/E Insight Dialog and Field Reference
Capital E/E Insight Dialog and Field Reference

This section offers a description of all input dialog boxes used in the creation, maintenance, and
viewing of studies. For each dialog box, all fields are listed, along with a full description of the
field’s function.
Calculation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1021
Edit Snapshot Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1030
Edit Study Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1031
Edit Study/Scenario Properties Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1032
Metrics/Insight Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1033
Metrics Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1037
New Scenario Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1038
New Study Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039
Snapshot Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1042

December 2023
Capital E/E Insight
Calculation Dialog Box
Calculation Dialog Box

To access: Click on an editable string in a metric element definition displayed in the Edit
Metrics Dialog Box and click Edit or New.
Used to create or edit a calculation using a simple query expression. This calculation is used
when a total is calculated for the metric element.
Objects
Table 13-1. Calculation Dialog Box Contents
Field Description
Calculation window Used to define the simple query expression.
Click the plus icon, ( ), to add a term to the expression. Depending

on the preceding element, the following terms may be available:
• Attribute/Property/Value
If you select Attribute or Property, that term is added to the
window. Click the term to display either a dropdown list of
available attributes or a field to enter a property name.
If you select Value, 0.0 is added to the window. Click that value to
display a field and enter a different value.
• Operators
Select an operator from +, -, x or /.
To clear the window, click Clear Calculation ( ).
To delete the last term in the expression, click Remove last
element ( ).
Click Go to Advanced Editor ( ), to access the Edit Query
Expressions dialog and use the advanced query editing
functionality (see “Query Expressions” in the Capital Project
Manager User Guide).
• Brackets can be used to control the query evaluation order.
Related Topics

December 2023
Capital E/E Insight
Compare Snapshots Dialog Box
Compare Snapshots Dialog Box

To access: Right-click on a study name in the Project Browser Window and select Compare
Snapshots
Used to compare the metric results from multiple snapshots from different studies.
Objects
Table 13-2. Compare Snapshots Dialog Box Contents
Field Description
Studies Specifies the study for which snapshots are listed in the Available
window.
Scenarios Specifies the scenario for which snap-shops are listed in the Available
window.
Available Lists snapshots that are available for the specified study (Studies field)
and scenario (Scenarios field). Select the snapshots to include in the
comparison and click Add to move them to the Chosen window. You
can click Add All to move them all. Change the values in the Studies
field and Scenarios field to select further snapshots from other studies
and scenarios.
Chosen Lists the snapshots that have been selected for comparison. To remove
a snapshot, select it and click Remove. To remove all selected
snapshots, click Remove All.
Related Topics

December 2023
Capital E/E Insight
Compare Snapshot With Dialog Box

To access: Right-click a snapshot in the Project Browser Window and select Compare
SnapshotWith, followed by the second snapshot to be compared.
Used to compare the metric results from multiple snapshots from one study.
Objects
Table 13-3. Compare Snapshot With Dialog Box Contents
Field Description
Group Select the subset of design objects for which you want to display metric
results.
Metrics are calculated to return a single numerical value for each
Group Type in a design.
Cycle Metric to Click the green arrows at the top of the reports to scroll between
Display the results for different metrics. When you click an arrow, the metric
results chart changes accordingly.
Alternatively, click the icon (located between the arrows) to select a
metric from a list.
The name of the metric for which results are currently displayed is
shown between the arrows.
Metric Results Chart Displays the metric results for snapshots being compared in a spider
chart.
You can add a snapshot to the comparison by right-clicking the metric
results chart and selecting Add to Comparison followed by the
snapshot.
You can use the Group field to specify the subsets of design objects for
which you want to display metric results.
Below the Metrics table is a legend listing the snapshots currently
displayed in the chart together with the display colors for those
snapshots. To hide a snapshot in the chart, click it in the legend; it is
then dimmed. To display it again, click the dimmed entry in the legend.
To show or hide particular metric elements, you can right-click the
chart and select Show Metrics or Hide Metrics followed by a metric
name.
You can select and copy the chart by right-clicking it and selecting
Copy Chart. The report can be pasted into other applications, such as
Microsoft Word.
Metrics Table Displays the same data as displayed in the metric results chart.
You can select and copy any range of cells. Cells can be pasted into
other applications, such as Microsoft Excel or Microsoft Word. When
you copy cells, the column header is also copied.

December 2023
Capital E/E Insight
Table 13-3. Compare Snapshot With Dialog Box Contents (cont.)

Field Description
Enter Filter String ( ) Applies a filter to the Group names on the metric results chart. In the
/ Clear Filter String field next to the Enter Filter String icon ( ), enter a series of
( ) characters.
For example, if Harness is selected in the Group field and the chart
shows results for harnesses named BODY and DOORS, you could
enter the string BO so that the results for DOORS disappear from the
chart.
Click the Clear Filter String icon ( ) to clear the filter.
Usage Notes
The default groups for Capital Systems Integrator, Capital Wiring Integrator, and Capital
Systems Architect are:
• Harness
• Multicore Type
• None
• Option
• Vehicle Model
• Wire Material
• Wire Specification
Capital Systems Architect also has the following groups (which are listed for all applications):
• Carrier
• Carrier Type
• Component
• System Component Type
• ECU
The default groups for Capital Harness Designer and Capital Harness Designer Modular are:
• Assembly

December 2023
Capital E/E Insight
• Component Type
• Library Group
• Multicore Type
• None
• Option
• Terminal Material
• Wire Material
• Wire Specification

December 2023
Capital E/E Insight
Edit Metrics Dialog Box

To access: Press Space Bar and enter Metrics or select Edit Metrics on the Insight tab.
Used to add, edit, and delete the Metrics that are available for use in Studies in Capital E/E
Insight or in Capital Configuration Optimizer.
Note
If you are using Capital Configuration Optimizer, click Edit Metrics Dialog Box (Capital
Configuration Optimizer).
If you are using Capital E/E Insight, continue reading this topic.
Objects
Table 13-4. Edit Metrics Dialog Box Contents
Field Description
Metrics Lists the existing metrics and their metric elements. The default types
are:
• Cost
Calculates the total architectural cost of design objects.
• Count
Calculates the total number of objects of a particular object type.
• Length
Calculates the total length of wires.
• Weight
Calculates the total weight of design objects.
Definition Lists the element definitions of the metric element currently selected in
the Definition window.
To add a new element definition, click Add New Definition ( ). The
template for the new element definition is added to the window.
Usage Notes
• You can edit metrics only if you have the Edit Metrics permission set for your user
account.
• The metric elements are displayed in rows below each metric. The color square on a
metric element row indicates the color used to display results for that metric. To change
the color, click the square.
• When you select a metric element, the element definitions are listed in the Definition
window.

December 2023
Capital E/E Insight
• You can add a new metric. Click the Add New Metric ( ) button, to create a new row,
and then edit the name of the metric. Click elsewhere on the dialog box to finish. The
row is displayed like the other metrics.
• You can create a metric element. Click the plus symbol (+) on a metric row, to add a
new metric element name below the metric. Edit the metric element name, and then
click the color square in that row, to select the color to display the results for that metric
element.
To delete a metric element, select it and click the minus symbol (-) on the metric row.
• You can duplicate an existing metric element by right-clicking it and choosing
Duplicate; the duplicate is added below the same metric. Alternatively, you can right-
click an existing metric element and choose Copy or Cut. Right-click another metric or
one of its metric elements and choose Paste to add the copied or cut element below it.
• The order in which the element definitions are listed dictates the order in which they are
calculated for design objects. If a design object matches more than one element
definition, only the value calculated for the first matching definition is included in the
metric result. This means that you should put the more specific definitions at the top of
the list and general definitions nearer the bottom.
• You can move an element up or down in the list by selecting it and clicking Move
Selected Definition Up in the list ( ) or Move Selected Definition Down in the list
( ).
• To delete an element definition, select it and click Remove Selected Definition ( ).

The element definition is removed from the window.
• The template for a element definition is:
Object Type matching {any} value is Expression
The red and green text indicates editable strings:
o Click Object Type to select an object type from a list.
o Click {any} to display a menu to select or create a condition using a query
expression. Either:
• Select an existing query expression directly from the menu. If you select {any},
all objects of the selected Object Type are considered by the element definition.
• Select New to display the Condition Dialog Box and define a query expression.
The query expression is saved to the database and is available wherever you can
select a query expression in the system.
• Select Edit to display either the Condition dialog box or the Edit Query
Expressions dialog box.

December 2023
Capital E/E Insight
The displayed dialog box depends on which dialog box was used to create the
condition currently displayed in the metric template.
o Click Expression, to display the Calculation dialog box and create a calculation
using a query expression.

December 2023
Capital E/E Insight
Edit Scenario Properties Dialog Box
Edit Scenario Properties Dialog Box

To access: Click the ellipsis (...) in the Props column for a scenario on the New Study Dialog
Box or the Edit Study Dialog Box.
Used to edit properties for a scenario.
Objects
Table 13-5. Edit Scenario Properties Dialog Box Contents
Field Description
Properties Table To add a property to the scenario, click the New button, enter a
Property Name in the New Property dialog box, and then click OK.
following fields:
• Name
A unique identifier for the property. Mandatory.
• Value
• Type
The data type of the value. Mandatory.
The following types are available:
• String - a mix of letters, numerical or special characters
Usage Notes
• If you enter a Value that is not supported by the selected Type, the Value is displayed in
red text and the OK button is dimmed.
• To delete a property from the list, select it and click the Delete button, and then click
OK to confirm the deletion.
Related Topics
Creating a Study
Editing a Study

December 2023
Capital E/E Insight
Edit Snapshot Dialog Box
Edit Snapshot Dialog Box

To access: Right-click a snapshot in the Project Browser Window and select Edit.
Used to edit the name and display color of an existing snapshot of metric results.
Objects
See the descriptions for the fields of the “Take Snapshot Dialog Box” on page 1044.
Related Topics

December 2023
Capital E/E Insight
Edit Study Dialog Box
Edit Study Dialog Box

To access: Right-click a study in the Project Browser Window and select Edit Study.
Used to edit an existing study in a project.
Objects
See the descriptions for the fields of the “New Study Dialog Box” on page 1039.
Related Topics
Editing a Study

December 2023
Capital E/E Insight
Edit Study/Scenario Properties Dialog Box
Edit Study/Scenario Properties Dialog Box

To access: Click the Properties button on the New Scenario Dialog Box, New Study Dialog
Box, or the Edit Study Dialog Box.
Used to edit properties for a study or scenario.
Objects
Table 13-6. Edit Study/Scenario Property Dialog Box Contents
Field Description
Properties Table To add a property to the study/scenario, click the New button, enter a
Property Name in the New Property dialog box, and then click OK.
following fields:
• Name
A unique identifier for the property. Mandatory.
• Value
• Type
The data type of the value. Mandatory.
The following types are available:
• String - a mix of letters, numerical or special characters
Usage Notes
• If you enter a Value that is not supported by the selected Type, the Value is displayed in
red text and the OK button is dimmed.
• To delete a property from the list, select it and click the Delete button, and then click
OK to confirm the deletion.
Related Topics
Creating a Study
Editing a Study

December 2023
Capital E/E Insight
Metrics/Insight Tab
Metrics/Insight Tab
To access: This tab is displayed with the tabs at the bottom left of the application when a design
or scenario is opened (except when working in multi-user mode).
Used to view metric results for the currently open design or scenario. If you have a Capital E/E
Insight license, you can also create a new scenario (and new study if required) from here.
Note
If you have a Capital E/E Insight license, this tab is called Insight. If you do not have a
license, this tab is called Metrics. See “Capital E/E Insight” on page 999 for an introduction
to the functionality available from this tab.
Description
Metrics are calculated to return a single numerical value for each group selected in a design.
This tab can be dragged from its location to display it as a separate floating dialog box.
Close the dialog box to return it to the original tab location.
Objects
Table 13-7. Metrics/Insight Tab Contents
Field Description
Create a new Unavailable if you do not have a Capital E/E Insight license.
scenario Opens the New Scenario Dialog Box to create a new scenario (and new
study if required). See “Creating a Scenario (and Study) from the Insight
Tab” on page 1004.
Group Click and select a group name to display metric results for a subset of
design objects.
Take a Snapshot of Unavailable if you do not have a Capital E/E Insight license.
the current data Displays the Take Snapshot Dialog Box to capture a snapshot of the
metric results for the current (live) design data.
<Live> Dropdown Unavailable if you do not have a Capital E/E Insight license.
List Located to the right of the “Take a Snapshot of the current data” button.
Select a snapshot to view the metric results in the Insight tab. To return to
the metrics for the current (live) design data, select <Live>.

December 2023
Capital E/E Insight
Metrics/Insight Tab
Table 13-7. Metrics/Insight Tab Contents (cont.)

Field Description
Compare Snap-Shots Unavailable if you do not have a Capital E/E Insight license.
Displays a spider chart in the Metric Results Chart that contains data
from all snapshots for the currently open scenario, and for the current
(live) design.
Below the Metric Results Chart is a legend listing the snapshot names of
the metric results currently displayed in the report. It also lists the display
colors for the snapshots. Click the snapshot name in the legend to show
or hide the metric results. The snapshot name is dimmed if hidden.
When comparing snapshot data, the button changes to Revert to Live
Snapshot ( ). Click to display only data for the live design.
Show Metrics Table Opens the Metrics Table in the Output window at the bottom of the
application, if the tab has been hidden or closed.
Pause metrics Pauses or restarts the calculation of metrics for design data. For platform
calculation designs, it also pauses background synthesis calculations.
When you pause calculations, the system dims other actions on the
Metrics/Insight tab.
Resume metrics
calculation You can pause the calculation if the software is running slow (because of
plugins, size of the diagram, and so on).
Cycle Metric to Click the green arrows at the top of the reports to scroll between the
display results for different metrics. When you click an arrow, the Metric Results
Chart changes accordingly.
metric from a list. If you have a Capital E/E Insight license and want to
create a new metric, click Edit Metrics in the list, to open the Edit
Metrics Dialog Box.

December 2023
Capital E/E Insight
Metrics/Insight Tab
Table 13-7. Metrics/Insight Tab Contents (cont.)

Field Description
Metric Results Chart Displays a scrollable chart of the metric results for the current (live)
design data or a snapshot selected from the <Live> dropdown list.
You can use the Group field to display metric results for a subset of
design objects, and press Ctrl while scrolling the middle mouse button, to
zoom in and out of the chart to display more or fewer results.
Below the chart is a legend listing the names and display colors of the
metric elements currently displayed. Click the element name in the
legend to show or hide the metric results. The element name is dimmed if
hidden. Alternatively, right-click the chart and select Show Metrics >
<Element Name> or Hide Metrics > <Element Name>.
To change the chart type (for example, Pie Chart, or Horizontal Bar
Chart), right-click the chart and select Chart Type > <Type Name>.
To copy the chart, right-click the chart and select Copy Chart. The
report can be pasted into other applications, such as Microsoft Word.
Enter Filter String Applies a dynamic filter to the element names on the Metric Results
( ) / Clear Filter Chart. In the field next to the Enter Filter String icon ( ), type a series
String ( ) of characters.
For example, if Harness is selected in the Group field, and the chart
shows results for harnesses named BODY and DOORS, you could type
the string BO to display BODY only.
The behavior of the filter varies if you use wildcards or upper and
lowercase characters. See also “Browser Tab and Dialog Box Filters” on
page 880.
Usage Notes
• Default groups for Capital Systems Integrator, Capital Wiring Integrator, and Capital
Systems Architect:
o Harness
o Multicore Type
o None
o Option
o Option Expression
o Vehicle Model
o Wire Material
o Wire Specification

December 2023
Capital E/E Insight
Metrics/Insight Tab
• Capital Systems Architect also has the following groups (which are listed for all
applications):
o Carrier
o Carrier Type
o Component
o System Component Type
o ECU
• Default groups for Capital Harness Designer and Capital Harness Designer Modular:
o Assembly
o Component Type
o Library Group
o Multicore Type
o None
o Option
o Option Expression
o Terminal Material
o Wire Material
Related Topics
Opening a Scenario

December 2023
Capital E/E Insight
Metrics Table
Metrics Table
To access: This table is displayed in the Output Window at the bottom of the application when a
scenario or design is opened.
Used to display metric results for the currently open design or scenario in a table format.
Objects
This is the same data as displayed in the Metrics/Insight Tab.
Usage Notes
If this table has been hidden or closed, it can be re-opened by clicking the Show Metrics
Table button on the Metrics/Insight tab.
You can select and copy any range of cells. Those cells can be pasted into other applications,
such as Microsoft Excel or Microsoft Word. When you copy cells, the column header is also
copied.
The Total column displays the total values for the other columns. It is available only for
individual snapshots and is not displayed when comparing snapshots.
Related Topics
Metrics/Insight Tab
Opening a Scenario

December 2023
Capital E/E Insight
New Scenario Dialog Box
New Scenario Dialog Box

To access: Click the Create a new scenario ( ) button on the Insight tab located at the bottom
left of the application window.
Used to create a new scenario (and new study if required) in the project.
Objects
Table 13-8. New Scenario Dialog Box Contents
Field Description
Study Either select an existing study from the dropdown list or enter a new
study name. Mandatory.
Name Specify a name for the scenario. Mandatory.
Properties Displays the Edit Study/Scenario Properties Dialog Box, to add
properties to the study. Optional.
Description Enter additional text to describe the intended usage of the scenario.
Optional.
Create Scenario Creates the scenario. If you entered a new study name, the New Study
Dialog Box is displayed to enter details for the study.
Related Topics
Metrics/Insight Tab

December 2023
Capital E/E Insight
New Study Dialog Box

To access: Right-click a project in the Project Browser Window and select New Study.
Used to create a new study in a project.
Metrics are calculated to return a single numerical value for each of the selected Groups types in
a design.
Objects
Table 13-9. New Study Dialog Box Contents
Field Description
Name Enter the name of the study. This must be unique within the project.
You can click the ellipsis (...) next to this field to select a name from a
pre-defined list if such a list has been created in Capital Project
Manager. Mandatory.
Properties Displays the Edit Study/Scenario Properties Dialog Box where you can
add properties to the study. Optional.
Description Enter additional text to describe the intended usage of the study.
Optional.
Scenarios Used to list the details of the scenarios to use in the study. Mandatory.
To add a scenario, click Add new Scenario to Study ( ).
To delete a scenario, select it and click Remove selected Scenario
from Study ( ).
• Name
The name of the scenario. This must be unique in the study.
Mandatory.
• Description
Enter additional text to describe the intended usage of the scenario.
Optional.
• Design
Select the design to associate with the scenario. Mandatory.
• Props
Click the ellipsis (...) to display the Edit Scenario Properties Dialog
Box where you can specify properties for the scenario. Optional.

December 2023
Capital E/E Insight
Table 13-9. New Study Dialog Box Contents (cont.)

Field Description
Metrics Lists the metrics and metric elements that have been created for use in
studies. The listed metrics are created at system level. See “Creating a
Metric Element” on page 1010.
Select the metric elements to use in the study. If cleared, a metric
element will not be included in any calculations for any scenarios in the
study.
For each metric, click the Change Default Chart Type to display for
Metric dropdown list (located on the right of the metric line) and select
the default chart type to use for the metric when viewing study results.
This default can be overridden when viewing study results. Mandatory.
Groups Select the subsets of design objects for which you want metric results
to be calculated. If you select None, the metric results are calculated for
the design as a whole. If you select a group, you will have the option of
displaying the metric results for those subsets on the Insight tab or in
snapshot dialog box. Mandatory.
Select the subset of design objects for which you want to display metric
results.
Usage Notes
• The default groups for Capital Systems Integrator and Capital Wiring Integrator are:
o Harness
o Multicore Type
o None
o Option
o Option Expression
o Vehicle Model
o Wire Material
The default groups for Capital Harness Designer and Capital Harness Designer Modular
are:
o Assembly
o Component Type
o Library Group
o Multicore Type

December 2023
Capital E/E Insight
o None
o Option
o Option Expression
o Terminal Material
o Wire Material
• You can develop custom groups as part of an extensibility plugin. For more information
about developing and using extensibility plugins, see the PluginDevelopment.pdf file
that is located in the doc\plugin directory of your Capital installation.
Related Topics
Creating a Study

December 2023
Capital E/E Insight
Snapshot Dialog Box
Snapshot Dialog Box

To access: From the Project Browser Window, double-click the snapshot or right-click and
select Open.
Used to view metric results for a snapshot.
Metrics calculated return a single numerical value for each group selected in a design.
Objects
Table 13-10. Snapshot Dialog Box Contents
Field Description
Group Click and select a group name to display metric results for a subset of
design objects.
Cycle Metric to Click the green arrows at the top of the reports to scroll between
display the results for different metrics. When you click an arrow, the Metric
Results Chart changes accordingly.
metric from a list.
Metric Results Chart Displays a scrollable chart of the metric results for the snapshot.
You can use the Group field to display metric results for a subset of
design objects, and press Ctrl while scrolling the middle mouse button,
to zoom in and out of the chart to display more or fewer results.
Below the chart is a legend listing the names and display colors of the
metric elements currently displayed. Click the element name in the
legend to show or hide the metric results. The element name is dimmed
if hidden. Alternatively, right-click the chart and select
Show Metrics > <Element Name> or Hide Metrics > <Element
Name>.
To change the chart type (for example, Pie Chart, or Horizontal Bar
Chart), right-click the chart and select Chart Type > <Type Name>.
To copy the chart, right-click the chart and select Copy Chart. The
report can be pasted into other applications, such as Microsoft Word.
Metrics Table Displays the same data as displayed in the Metric Results Chart.
You can select and copy any range of cells. Those cells can be pasted
into other applications, such as Microsoft Excel or Microsoft Word.
When you copy cells, the column header is also copied.

December 2023
Capital E/E Insight
Snapshot Dialog Box
Table 13-10. Snapshot Dialog Box Contents (cont.)

Field Description
Enter Filter String ( ) Applies a dynamic filter to the element names on the Metric Results
/ Clear Filter String Chart. In the field next to the Enter Filter String icon ( ), type a
( ) series of characters.
For example, if Harness is selected in the Group field, and the chart
shows results for harnesses named BODY and DOORS, you could type
the string BO to display BODY only.
The behavior of the filter varies if you use wildcards or upper and
lowercase characters. See also “Browser Tab and Dialog Box Filters”
on page 880.
Usage Notes
• Default groups:
o Harness
o Multicore Type
o None
o Option
o Option Expression
o Vehicle Model
o Wire Material
Related Topics
Opening a Snapshot

December 2023
Capital E/E Insight
Take Snapshot Dialog Box
Take Snapshot Dialog Box

To access: Click the Take a Snapshot of the current data ( ) button on the Metrics/Insight
Tab with a scenario open.
Used to take a snapshot of the metric results for the current design data.
Objects
Table 13-11. Take Snapshot Dialog Box Contents
Field Description
Name Specify a name for the snapshot. This must be unique for the scenario.
Click the color square beside the field to select the color that you want
used to display the metric results for the snapshot when comparing it
with another snapshot. Mandatory.
Related Topics
Usage Example - Study of Alternative Harness

Routing Paths
This usage example for Capital E/E Insight creates and compares snapshot metrics for two
scenarios where you use alternative routing paths.
Prerequisites
• If you want to work through this usage example, create a project containing two designs
with the names “Driver Side Only” and “Driver and Passenger Side”. Populate those
designs with dummy data of your own creation.
• In a light truck, there are two alternative paths for the harnesses to connect to the lights,
ABS wheel sensors, and fuel sender. In this case, the metrics of interest are total wiring
cost and weight.
o Scenario 1 - All wiring runs down the driver’s side of the vehicle, and then crosses to
the passenger side in front of the rear bumper. This topology is detailed in a design
called “Driver Side Only”.
o Scenario 2 - Wiring for the driver’s side lights, fuel sender and wheel sensor run
down the driver’s side of the vehicle. Wires for the passenger side lights, license
plate light and wheel sensor cross just behind the cabin and run down the passenger
side of the vehicle. This topology is detailed in a design called “Driver and
Passenger Side”.
• The two designs are created in the same project.

December 2023
Capital E/E Insight
Usage Example - Study of Alternative Harness Routing Paths
Procedure
1. The following steps will create a study with two scenarios:
2. In the Project Browser Window (located at the top left of the application), right-click the
project containing the two designs and select New Study; the New Study Dialog Box is
displayed.
3. Specify Alternative Harness Routes in the Name field.
4. Click Add a new Scenario to Study ( ); a row is added to the Scenarios table.
5. Specify Driver Side Scenario as the Name of the scenario and select the Driver Side
Only design as the Design.
6. Repeat steps 3 and 4 for the second scenario, specifying Driver and Passenger
Scenario as the Name and selecting the Driver and Passenger Side design as the
Design.
7. In the Metrics window, select Wire cost and Wire weight (both default metrics
supplied with the system) as the metric elements to use in the study. For each metric,
8. Select the groups to which you want to apply the study. In this example case, you might
want to select only Harness (to view the wire cost and weight for each harness in the
designs) and None (to view the total wire cost and weight for each design).
Click OK; the study is added to the Project Browser Window, expanding the study
reveals the scenarios listed below it.
9. The following steps will take a snapshot of the metric totals:
10. Double-click the Driver Side Scenario in the Project Browser Window and click the
Metrics/Insight Tab (located on the lower left of the application) to view the metric
totals for that scenario.
11. On the Metrics/Insight Tab, click Take a Snapshot of the current data ( ); the Take
Snapshot Dialog Box is displayed.
12. Specify Driver Only Snapshot as the Name for the snapshot. Click the colored box and
select the color you want to use to display the metric results when comparing snapshots.
13. Click OK; the snapshot is added below the scenario in the Project Browser Window.
14. Repeat steps 1 to 4 for the “Driver and Passenger Scenario” scenario, specifying Driver
and Passenger Snapshot as the Name for the snapshot and a different color for
displaying its metric results.

December 2023
Capital E/E Insight
Usage Example - Study of Alternative Harness Routing Paths
15. The following steps will compare the snapshots:

16. Right-click the Driver Only Snapshot in the Project Browser Window and select
Compare snapshot with followed by the Driver and Passenger Snapshot; the
Compare Snapshot With Dialog Box is displayed.
The metric totals for the two scenarios are displayed together in the metric results chart
and Metrics table, to compare the cost and weight. Click the right or left arrows ( )
to scroll views between the various metrics of interest. You can also select the metric of
interest from the dropdown box ( ) next to the metric title.

December 2023
Capital E/E Insight
Help Button Landing Pages for Capital E/E Insight Dialog Boxes
Help Button Landing Pages for Capital E/E

Insight Dialog Boxes
The following topics are displayed when you click the Help button or press F1 for a dialog box
in the software.
Edit Metrics Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
Edit Scenario Properties Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1048
Edit Study Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
New Scenario Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
New Study Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1049
Snapshot Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
Take Snapshot Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1050
Calculation Help
• The Calculation Dialog Box fields
• Creating a Metric Element
• Editing a Metric Element Definition
• Deleting a Metric Element Definition
Compare Snapshots Help

• The Compare Snapshots Dialog Box fields
• Comparing Snapshots from Different Studies

December 2023
Capital E/E Insight
Compare Snapshot With Help
Compare Snapshot With Help

• The Compare Snapshot With Dialog Box fields
• Comparing Snapshots from One Study
• Comparing Snapshots from Different Studies
Edit Metrics Help

• The Edit Metrics Dialog Box fields
• Creating a Metric
• Deleting a Metric Element
• Editing a Metric Element Definition
• Deleting a Metric Element Definition
Edit Scenario Properties Help

• The Edit Scenario Properties Dialog Box fields
• Creating a Study
• Editing a Study
Edit Snapshot Help

• The Edit Snapshot Dialog Box fields

December 2023
Capital E/E Insight
Edit Study Help
• Editing a Snapshot Name and Display Color
Edit Study Help

• The Edit Study Dialog Box fields
• Editing a Study
Edit Study Properties Help

• The Edit Study/Scenario Properties Dialog Box fields
• Editing a Study
New Scenario Help

• The New Scenario Dialog Box fields
• Overview of Studies and Scenarios
• Creating a Scenario (and Study) from the Insight Tab
New Study Help

• The New Study Dialog Box fields

December 2023
Capital E/E Insight
Snapshot Help
Snapshot Help
• The Snapshot Dialog Box fields
• Opening a Snapshot
Take Snapshot Help

• The Take Snapshot Dialog Box fields
• Taking a Snapshot of Metric Results for Current Design Data

December 2023
Index
Revision Node, 423

Index
—A— Design Log Event Filter Options dialog, 962

Assign Design Log Filter Options dialog, 963
library description, 590 Design Log Viewer dialog, 964
options, 592 Designs
Attributes editing information, 236
finding values, 629 refreshing, 29
replacing values, 629 Diagrams
—B— changing background color, 496
Background color, 496 —E—
Bundles Edit
reconnecting sliced ends, 641 general properties, 597
slicing, 645 graphical properties of cross-references,
—C— 785
Capital Change Validator, 703 options, 592
CGM Page Settings Dialog, 924, 936 properties, 589
Change Edit Assemblies Dialog, 799
background color, 496 Edit Assembly Dialog, 800
Change Policies Edit Properties facility, 589
refreshing, 30 Effectivity, 805, 982
Clip To Border, 932 —F—
Component Filter
selecting, 636 topology, 473
Copy a Design Find
From one Project to another, 232 attribute/property values, 629
Creating a checklist item, 697 Freeze shared objects, 602
Creating a comment, 697 Fused table layout, 873
Creating a note, 697
Cross references —G—
refreshing, 29, 30 General properties, 597
Cross-references Group objects, 556
editing graphical properties, 785
Custom action plugins, 33 —H—
CustomActionDevelopment.pdf, 33 Harness Group, 239
Hatching Pattern Scale Factor, 924
—D—
Design Folders —K—
Design Folder, 423 Keyboard Shortcuts
Normal Folder, 423 All Tool s Styling, 479

December 2023
All Tools Editing, 478 Names
All Tools General Actions, 478 specifying, 607
All Tools Graphics, 479 New Assembly Name, 839
All Tools Navigation, 480
Capital Harness Designer Actions, 484 —O—
Capital Harness Designer Editing, 483 Objects
Capital Harness Designer Harness moving, 485
Processing, 485 Options
Capital Harness Designer Process Part assigning, 592
Selection, 484 editing, 592
Capital Harness Designer Processing, 484 refreshing, 29
Capital Harness Designer Rules, 483 —P—
Capital Harness Designer Styling, 482 Plugin, 33
Capital Harness Process Designer Actions, PluginDevelopment.pdf, 1010, 1042
485 Printing a build list, 663
Capital Logic Designer Add, 481 Printing a build list (print to file), 676
Capital Logic Designer Editing, 480 Properties
Capital Systems Integrator Add, 482 editing, 589
Capital Systems Integrator Editing, 482 editing general, 597
Capital Wiring Integrator Add, 481 finding values, 629
Capital Wiring Integrator Editing, 481 replacing values, 629
—L— —R—
Layout, 873 Refreshing Design Connectivity, 30
Library description Report Builder, 61
assigning, 590 Resolution, 924
unassigning, 609
updating, 609 —S—
viewing, 611 Save Design into Assembly, 615
Library parts Scaling, 932
refreshing, 29 Select
selecting, 636 component, 636
Line Pattern Scale Factor, 924, 936 library parts, 636
Line Thickness Scale Factor, 924, 936 Shared
Logical changes freeze objects, 602
refreshing, 30 unfreeze objects, 602
Logs Shared Objects
viewing, 658 refreshing, 29
Short Description, 800
—M— Slice
Max Grid Distance for Toggle Indicator, 192 bundles, 645
Moving Snap To Object, 569
objects, 485 Specify
—N— name property, 607
Name Uniqueness, 174, 211 Split Table Dialog, 873, 997
Symbol libraries

December 2023
refreshing, 29
—T—
Topologies
filtering, 473
—U—
Unassign
library descriptions, 609
Unfreeze shared objects, 602
Ungroup objects, 557
Uniqueness, 174, 211
Update
—V—
Variants
refreshing, 29
View
logs, 658
View Design Logs dialog, 966

December 2023
December 2023
Third-Party Information
Information on open source and third-party software that may be included in this product can be found in the
<HOME>\Acknowledgements folder.

Capital Design Tools - Common Functions User Guide

Uploaded by

Copyright:

Available Formats

Capital Design Tools - Common Functions User Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Capital Design Tools - Common Functions User Guide

Uploaded by

Copyright:

Available Formats

SIEMENS

Capital Design Tools -

About Siemens Digital Industries Software

Support Center: support.sw.siemens.com

Capital Design Tools - Common Functions User Guide, 2207 3

Editing the Language Dictionary CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

4 Capital Design Tools - Common Functions User Guide, 2207

Capital Design Tools - Common Functions User Guide, 2207 5

Defining Inclusive and Exclusive Relationships for an Option . . . . . . . . . . . . . . . . . . . . . 430

6 Capital Design Tools - Common Functions User Guide, 2207

Moving Objects on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487

Capital Design Tools - Common Functions User Guide, 2207 7

Drawing a Fillet in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

8 Capital Design Tools - Common Functions User Guide, 2207

Object Rule Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576

Capital Design Tools - Common Functions User Guide, 2207 9

Using a Plugin Interface to Control Physical Line Thickness . . . . . . . . . . . . . . . . . . . . . . 628

10 Capital Design Tools - Common Functions User Guide, 2207

Line Pattern Scale Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 683

Capital Design Tools - Common Functions User Guide, 2207 11

Copy Design Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745

12 Capital Design Tools - Common Functions User Guide, 2207

Add Text Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855

Capital Design Tools - Common Functions User Guide, 2207 13

Condition Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938

14 Capital Design Tools - Common Functions User Guide, 2207

Design Rule Checks Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979

Capital Design Tools - Common Functions User Guide, 2207 15

Release Designs Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 994

16 Capital Design Tools - Common Functions User Guide, 2207

Capital E/E Insight Dialog and Field Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1020

Capital Design Tools - Common Functions User Guide, 2207 17

18 Capital Design Tools - Common Functions User Guide, 2207

Figure 1-1. String in Client Application Window Banners . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Capital Design Tools - Common Functions User Guide, 2207 19

Figure 5-5. Example with Trimmed and Extended Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . 532

20 Capital Design Tools - Common Functions User Guide, 2207

Figure 8-25. Make the Slice Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655

Capital Design Tools - Common Functions User Guide, 2207 21

Figure 12-17. Map Pins Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834

22 Capital Design Tools - Common Functions User Guide, 2207

Table 1-1. API, Plugin, and Web Service Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Capital Design Tools - Common Functions User Guide, 2207 23

24 Capital Design Tools - Common Functions User Guide, 2207

Table 12-49. Applicable Changes Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 876

Capital Design Tools - Common Functions User Guide, 2207 25

Table 13-9. New Study Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039

26 Capital Design Tools - Common Functions User Guide, 2207

Capital Design Tools - Common Functions User Guide, 2207 27

Multiple Language Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

28 Capital Design Tools - Common Functions User Guide, 2207

Capturing Performance Profiling Data and Heap Dump Data. . . . . . . . . . . . . . . . . . . . 118

Refreshing External Data

Capital Design Tools - Common Functions User Guide, 2207 29

30 Capital Design Tools - Common Functions User Guide, 2207

Viewing the Details of Installed Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Viewing the Details of Installed Extensibility

Capital Design Tools - Common Functions User Guide, 2207 31

Reloading Extensibility Plugins

32 Capital Design Tools - Common Functions User Guide, 2207