Capital Integrator User

Capital® Integrator™ User Guide
Incorporating Capital® AutoView Assist for Integrator™

and Capital® Level Manager™
Release 2015.1
February 2016
© 2016 Mentor Graphics Corporation

All rights reserved.
This document contains information that is proprietary to Mentor Graphics Corporation. The original recipient of this
document may duplicate this document in whole or in part for internal business purposes only, provided that this entire
notice appears in all copies. In duplicating any part of this document, the recipient agrees to make every reasonable
effort to prevent the unauthorized use and distribution of the proprietary information.
This document is for information and instruction purposes. Mentor Graphics reserves the right to make
changes in specifications and other information contained in this publication without prior notice, and the
reader should, in all cases, consult Mentor Graphics to determine whether any changes have been
made.
The terms and conditions governing the sale and licensing of Mentor Graphics products are set forth in
written agreements between Mentor Graphics and its customers. No representation or other affirmation
of fact contained in this publication shall be deemed to be a warranty or give rise to any liability of Mentor
Graphics whatsoever.
MENTOR GRAPHICS MAKES NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
FITNESS FOR A PARTICULAR PURPOSE.
MENTOR GRAPHICS SHALL NOT BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL, OR
CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS)
ARISING OUT OF OR RELATED TO THIS PUBLICATION OR THE INFORMATION CONTAINED IN IT,
EVEN IF MENTOR GRAPHICS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
U.S. GOVERNMENT LICENSE RIGHTS: The software and documentation were developed entirely at
private expense and are commercial computer software and commercial computer software
documentation within the meaning of the applicable acquisition regulations. Accordingly, pursuant to
FAR 48 CFR 12.212 and DFARS 48 CFR 227.7202, use, duplication and disclosure by or for the U.S.
Government or a U.S. Government subcontractor is subject solely to the terms and conditions set forth in
the license agreement provided with the software, except for provisions which are contrary to applicable
mandatory federal laws.
TRADEMARKS: The trademarks, logos and service marks ("Marks") used herein are the property of
Mentor Graphics Corporation or other parties. No one is permitted to use these Marks without the prior
written consent of Mentor Graphics or the owner of the Mark, as applicable. The use herein of a third-
party Mark is not an attempt to indicate Mentor Graphics as a source of a product, but is intended to
indicate a product from, or associated with, a particular third party. A current list of Mentor Graphics’
trademarks may be viewed at: www.mentor.com/trademarks.
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.
Mentor Graphics Corporation

8005 S.W. Boeckman Road, Wilsonville, Oregon 97070-7777
Telephone: 503.685.7000
Toll-Free Telephone: 800.592.2210
Website: www.mentor.com
SupportNet: supportnet.mentor.com/
Send Feedback on Documentation: supportnet.mentor.com/doc_feedback_form

Table of Contents
Chapter 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Overview of Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Capital Insight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Styling Objects in Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Logical Design Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Associating Logical Designs with the Topological Design. . . . . . . . . . . . . . . . . . . . . . . . . . 37
Replacing a Logical Design Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Object Attribute Descriptions for Use in Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . 42
Viewing the Details of Installed Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Reloading Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Selecting an Extensibility Plugin from the Plugins Dialog Box. . . . . . . . . . . . . . . . . . . . . 43
Custom Action Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Object Model Integrity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Launching Capital Library from this Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Launching Capital Symbol from this Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Diagram Language Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Engineering Change Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Harness Concurrency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Relationships between Locks and User Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Selecting Multi User or Single User Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Selecting which Lockable Objects to View on the Concurrency Tab . . . . . . . . . . . . . . . . 49
Locking a Harness or Slot when Running in Multi User Mode . . . . . . . . . . . . . . . . . . . . . 50
Unlocking a Harness or Slot when Running in Multi User Mode . . . . . . . . . . . . . . . . . . . 51
Dimming (graying out) Slots and Harnesses that are Locked by Other Users or that Are
Unlocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Refreshing Harness Information with Changes from Other Users . . . . . . . . . . . . . . . . . . . 52
Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Chapter 2
Setting up Projects and Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Opening a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Editing the Attributes and Properties of a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Deleting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Importing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Exporting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Closing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Applying Scopes to a Project or Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Project Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Capital® Integrator™ User Guide, 2015.1 3

February 2016
Table of Contents
Designs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Creating a New Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Importing a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Editing the Information for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Deleting a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Adding a Property to a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Editing a Property for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Deleting a Property for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Saving the Designs in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Comparing Objects and Their Properties in Design Revisions . . . . . . . . . . . . . . . . . . . . . 69
Refreshing External Data for an Open Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Synchronizing Changes in Capital Logic Designs with the Capital Integrator Design . . . 70
Managing Design Changes When Synchronizing Designs . . . . . . . . . . . . . . . . . . . . . . . . 71
Releasing a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Design Rule Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Running Design Rule Checks in Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Running Design Rule Checks Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Running Design Rule Checks in the Design Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Design Rule Check Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Chapter 3
Setting up Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Working with Multiple Diagrams Overview Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Creating a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Editing the Name of a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Specifying the Style Set Applied to the Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Adding a Property to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Deleting a Property from a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Specifying the Physical Scale of a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Changing the Background Color of a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Adding a Skeleton Graphic to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Removing a Skeleton from a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Chapter 4
Editing Diagram Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Undoing an Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Redoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Repeating an Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Cutting and Pasting an Object in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Copying and Pasting an Object in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Copying an Object from Diagram to Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Moving Objects from a Diagram to Another Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Deleting an Object in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Selecting Objects in a Diagram Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Selecting All Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Finding and Selecting Objects by Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Finding and Selecting Objects by Attribute or Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Selecting the Parent Object of an Object in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
4 Capital® Integrator™ User Guide, 2015.1

February 2016
Table of Contents
Specifying the Highlight Color of Selected Objects in a Diagram . . . . . . . . . . . . . . . . . . . . 87

Moving Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Using the Stroke Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Filtering the Objects Displayed in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Locating the Source Functional Object for a Physical Object. . . . . . . . . . . . . . . . . . . . . . . . 90
Slice Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Window Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Arranging Diagram Windows for Viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Moving Browser Windows Around the Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Zooming In and Out of Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Panning Across a Diagram Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Chapter 5
Creating Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Creating an Empty Slot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Creating a Slot for a Specific Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Resizing a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Specifying a Slot Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Overview of Junction Box Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Creating Multiple Slot Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Chapter 6
Creating Bundles and Harnesses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Harness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Creating a Bundle in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Moving a Bundle in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Deleting a Bundle from a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Creating Multiple Bundle Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Specifying the Physical Length of a Bundle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Specifying Variant Physical Lengths for a Bundle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Including a Slot with a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Excluding a Slot from a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Specifying a Domain for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Merging Harnesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Splitting a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Multiple Harnesses at Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Bundle Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Defining a Bundle Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Deleting a Bundle Region. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Moving a Bundle Region Node Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Sliding a Bundle Region along a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Using the Adjust Bundle Region Menu Option to Move a Bundle Region Node . . . . . . . 124
Editing the Offsets of a Bundle Region from the Bundle Ends . . . . . . . . . . . . . . . . . . . . . 125
Through Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Creating a Through Node on a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Deleting a Through Node from a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

February 2016
Table of Contents
Converting Through Nodes from Structure Nodes to Reference Nodes . . . . . . . . . . . . . . 128

Integrator Harness Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Exporting a Harness from a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Exporting Multiple Harnesses from a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Importing Modified Data for an Existing Harness in a Design . . . . . . . . . . . . . . . . . . . . . . . 133
Importing the Data for a New Harness into a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Importing the Data for a New Harness into a Design and Mating a Connector . . . . . . . . . . 135
Chapter 7
Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
Slot Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Adding a Slot Connector to a Slot Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Moving a Slot Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Device Connectors and Harness Connectors in Capital Integrator . . . . . . . . . . . . . . . . . . . . 141
Mapping Cavities and Pins between a Device Connector and a Harness Connector . . . . . . 144
Mapping a Footprint Connector to a Slot Connector (Device Connector and Harness Connector)
on a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Inline Pair. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Adding an Inline Pair to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Deleting an Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Adding an Inline Receptacle with an Associated Library Part . . . . . . . . . . . . . . . . . . . . . . 149
Adding an Inline Receptacle without an Associated Library Part . . . . . . . . . . . . . . . . . . . 150
Adding an Inline Plug with an Associated Library Part . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Adding an Inline Plug without an Associated Library Part . . . . . . . . . . . . . . . . . . . . . . . . 152
Converting an Inline Half Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Adding a Cavity to an Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Deleting a Cavity from an Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Mating Disconnected Inline Pair Halves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Disconnecting the Halves of an Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Adding an Interface Connector to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Exporting an Interface Connector Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Importing an Interface Connector Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Common Editing Tasks for Multiple Connector Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Adding a Cavity to a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Deleting a Cavity from a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Cloning and Replicating Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Copied Data When Cloning a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Specifying a Route Code for a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Backshells and Backshell Terminations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
Adding a Backshell to a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Deleting a Backshell from a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Adding a Backshell Termination to a Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Deleting a Backshell Termination from a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Chapter 8
Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Placement of a Device or Ground Device in a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174

February 2016
Table of Contents
Placement of Normal Devices in Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Placement of Ground Devices in Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Optimized Ground Placement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Placement of Devices with Footprints in Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Manually Placing a Normal or Ground Device in a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Automatically Placing a Normal Device in a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Automatically Placing all Unplaced Normal Devices from a Particular Logical Design. . 184
Automatically Placing all Unplaced Normal Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Automatically Placing all Unplaced Ground Devices from a Particular Logical Design. . 185
Automatically Placing all Unplaced Ground Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Unplacing a Placed Device from a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Unplacing all Placed Devices from a Particular Logical Design . . . . . . . . . . . . . . . . . . . . 187
Unplacing all Placed Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Unplacing all Placed Ground Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Mapping of Connectors and Cavities when Placing a Device in a Slot . . . . . . . . . . . . . . . . 188
Combining Normal Devices in a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Combining Ground Devices in Selected Ground Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Combining Ground Devices in All Ground Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Defining Footprints on Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Reevaluation and Updating of Footprints when Changes Are Made . . . . . . . . . . . . . . . . . 196
Implementing Grounds in the Generative Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Grounds and Ground Wiring Flow Using Ground Design Functionality. . . . . . . . . . . . . . 198
Grounds and Ground Wiring Flow Using Shared Objects . . . . . . . . . . . . . . . . . . . . . . . . . 202
150% Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Chapter 9
Connector Refinement and Signal Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Connector Refinement and Signal Mapping Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Generalized Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Specialized Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Fanout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Variant Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Variant Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Signal Map for a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Signal Map for an Interface Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Signal Map for an Inline Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Usage Examples for Connector Refinement and Signal Mapping . . . . . . . . . . . . . . . . . . . 217
Usage Example - Refining an Inline Connector Before Composite Wiring Synthesis to Have
Two Connectors on Each Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Usage Example - Refining an Inline Connector After Composite Wiring Synthesis To Have
Two Connectors on Each Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Usage Example - Setting Two Preferred Signals for One Cavity in the Signal Map of an Inline
Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Refining a Slot Connector on a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Mapping a Signal to a Hole or Slot Connector Cavity on a Slot . . . . . . . . . . . . . . . . . . . . 240
Mapping a Signal to Multiple Slot Connector Cavities on a Slot. . . . . . . . . . . . . . . . . . . . 241
Updating the Signal Maps for Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Refining an Interface Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

February 2016
Table of Contents
Mapping a Signal to an Interface Connector Cavity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Refining an Inline Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Mating the Cavities of the Two Halves of an Inline Connector . . . . . . . . . . . . . . . . . . . . . 245
Mapping a Signal Between Cavities on the Halves of an Inline Connector. . . . . . . . . . . . 246
Mapping Multiple Shield Signals to One Backshell Termination on an Inline Connector 247
Creating Variant Wire and Variant Signal Mappings on the Signal Mappings Tab for a Slot
248
Creating Variant Wire and Variant Signal Mappings on the Signal Mappings Tab for an Inline
249
Deleting a Variant Wire and Variant Signal Mapping on the Signal Mappings Tab for a Slot or
Inline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Editing the Variant Option Expression of a Variant Wire Mapping on the Wire Info Tab for a
Slot or Inline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Creating Variant Signal and Wire Mappings in the Signal Map for an Interface Connector 252
Deleting a Variant Signal Mapping in the Signal Map for an Interface Connector . . . . . . 253
Creating a Variant Connector in the Signal Map for a Slot, Inline or Interface Connector 254
Chapter 10
Editing Slots. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257
Slot Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Generating a Slot Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Internal Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Removing Unused Connectors, Holes and Cavities from Slots . . . . . . . . . . . . . . . . . . . . . . 262
Modeling Direct to Device Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Equipotential Nets at a Pin. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Comparison of Use of Equipotential Attribute, Equipotential Global Attribute and Equivalence
Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Setting the Equipotential Attribute for a Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Setting the Equipotential Global Attribute for a Shared Pin . . . . . . . . . . . . . . . . . . . . . . . 267
Chapter 11
Editing the Attributes and Properties of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269
Accessing an Edit Properties Dialog Box for a Design or Diagram Object . . . . . . . . . . . . . 269
Editing of Multiple Objects Simultaneously . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Specifying the Name of an Object in a Design or Diagram . . . . . . . . . . . . . . . . . . . . . . . . . 271
Displaying a Conductor Name For Multiple Segments of a Conductor . . . . . . . . . . . . . . . . 273
Displaying an Object's Short Description Attribute in a Diagram. . . . . . . . . . . . . . . . . . . . . 273
Assigning a Library Part to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Library Part Usage in Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Updating the Details of an Object's Library Part. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Removing a Library Part from an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Viewing the Library Part Details for an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Selecting a Component Part Number in the Part Selection Dialog Box . . . . . . . . . . . . . . . . 277
Performing a Batch Update of Library Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Specifying the Physical Length of a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Assigning an Option Expression to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Editing an Object Attributes and Graphical Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Using Quick Editing for Object Attribute Displayed on Diagram . . . . . . . . . . . . . . . . . . . . 281

February 2016
Table of Contents
Adding a Property to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Deleting a Property from an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Specifying How an Object is Displayed Graphically in a Diagram . . . . . . . . . . . . . . . . . . . 284
Foreground, Background and Manual Color Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Advanced Naming Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Chapter 12
Rules and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Overview of Rules and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Evaluation of Rules on Bundle Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Creating a Strategy for Constraint Definition in Capital Integrator . . . . . . . . . . . . . . . . . . . 294
Standard Constraints for Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Usage Examples for Rules and Constraints in Capital Integrator . . . . . . . . . . . . . . . . . . . . . 313
Using Rules to Add Properties and Attributes to Wires, Splices and Multicores During Wiring
Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Using a Constraint to Set Properties and Attributes on Objects . . . . . . . . . . . . . . . . . . . . . 314
Using a Constraint to Manage the Length of a Jumper Wire . . . . . . . . . . . . . . . . . . . . . . . 315
Using a Constraint to Manage the Length of Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Chapter 13
Composite Data Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Composite Data Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Examples of Composite Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Example Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Example Vehicle Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Example Harnesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Example Harness Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Example Vehicle Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Creating an Option at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Defining Inclusive and Exclusive Relationships for an Option . . . . . . . . . . . . . . . . . . . . . 339
Display of Option/Module Names or Option/Module Descriptions in Dialog Boxes . . . . 339
Option Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Creating an Option Folder at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Variant Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Defining a Variant Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Option Expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Generating Option Expressions for Wires and Splices. . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Option Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Creating an Option Combination at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Adding a Valid Selection to an Option Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Vehicle Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Defining Vehicle Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Exporting Vehicle Models from a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348
Importing Vehicle Models into a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Platform Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Specifying the Platform Options in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Harness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

February 2016
Table of Contents
Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

Specifying the Options that Affect a Harness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Creating a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Editing a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Combining Harness Levels into One . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Editing the Properties of a Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 356
Specifying a Part Number for a Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Active Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358
Setting Individual Active Harness Levels for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . 358
Setting all Harness Levels for Selected Harnesses to Active . . . . . . . . . . . . . . . . . . . . . . 359
Setting Individual Harness Levels to Inactive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Setting all Harness Levels for Selected Harnesses to Inactive. . . . . . . . . . . . . . . . . . . . . 360
Harness Level Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Importing Harness Level Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Exporting Harness Level Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363
Vehicle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Methods of Defining a Vehicle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Defining a Vehicle Configuration Based on Harness Levels . . . . . . . . . . . . . . . . . . . . . . . 365
Defining a Vehicle Configuration Based on Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Setting an Active Vehicle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 368
Giveaway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Specifying Giveaway Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Usage Example - Giving Away an Option on a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Usage Example - Giving Away Together Two Mutually-Exclusive Options on a Harness 375
Harness Replacement Technology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Usage Example - Importing Multiple Harnesses Using Harness Replacement Technology 385
Exporting a Harness from Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Importing a Harness into Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Chapter 14
Module Code Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Module Code Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Viewing the Modules in a Capital Integrator Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Setting Wiring in Particular Modules to Active in the Design . . . . . . . . . . . . . . . . . . . . . . . 391
Renaming a Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Merging Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Creating a New Module Based on an Option Expression . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Moving Wiring Between Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Sharing Wires Between Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Chapter 15
Terminal Bars, Holes and Relays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Hole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Terminal Bar Design Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Adding a Hole to a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Moving a Hole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Importing Terminal Bar Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Deleting Terminal Bar Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

February 2016
Table of Contents
Relays. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Relay Design Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Chapter 16
Stud Pins and Ring Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415
Overview of Stud Pins and Ring Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Adding Ring Terminals to a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Mapping a Stud Pin to Multiple Ring Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417
Chapter 17
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 419
Harness Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Creating a Topological Design's Harness Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Options and Levels Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Creating an Options and Levels Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Customized Connectivity Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Creating a Set of Customized Connectivity Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Material Statistics Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Creating a Material Statistics Report for a Topological Design . . . . . . . . . . . . . . . . . . . . . 426
Wire Count Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Creating a Wire Count Report for a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Bundle Width Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Creating a Bundle Width Report for a Bundle Section . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Component BOM Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Creating a Component BOM Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Multicore List Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Creating a Multicore List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Applied Constraints Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Creating an Applied Constraints Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Configured Wire List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Using the Report Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436
Chapter 18
Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437
Synthesizing Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
How Synthesis Calculates the Cost of a Wiring Route for a Signal. . . . . . . . . . . . . . . . . . 441
Composite Wiring Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Composite Wiring Synthesis Flows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Synthesizing Composite Wiring in the Level Import Flow . . . . . . . . . . . . . . . . . . . . . . . . 447
Regenerating Harness Levels and Finishing Composite Wiring Synthesis . . . . . . . . . . . . 447
Generating Initial Harness Levels for Composite Wiring Synthesis . . . . . . . . . . . . . . . . . 448
Viewing the Wiring for a Vehicle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Deleting Wiring, Harness Levels and Vehicle Configurations. . . . . . . . . . . . . . . . . . . . . . 449
Modular Wiring Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Synthesizing Modular Wiring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 451
Viewing the Synthesized Wires for all Levels of a Harness after Modular Wiring Synthesis
452
Viewing the Synthesized Wires for a Harness Level after Modular Wiring Synthesis . . . 453

February 2016
Table of Contents
Viewing the Synthesized Wires for all Harnesses after Modular Wiring Synthesis . . . . . 454
Viewing the Synthesized Wires for all Harnesses in a Vehicle Model after Modular Wiring
Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Reporting on Missing or Inconsistent Options Promoted to Harnesses . . . . . . . . . . . . . . . 455
Manual Wiring Synthesis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Manually Synthesizing Wiring for Selected Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Deleting the Synthesized Wiring for all Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Deleting the Synthesized Wiring for Selected Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
Detailed Descriptions of Wiring Synthesis Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
Running Modular or Composite Wiring Synthesis for Selected Signals. . . . . . . . . . . . . . . . 467
Merge of Logical Multicores in Wiring Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Import of Carry-Over Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
High-level Flow for Importing Carry-Over Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Importing Carry-Over Wiring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Merging a Slot and Interface Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Wire Editing in Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Generating a Wiring View of a Synthesized Signal or Multicore . . . . . . . . . . . . . . . . . . . 476
Adding a Wire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Ground-to-ground Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Moving a Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Editing Wire Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Defining Specification Attributes for a Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Specifying the Harness Levels on which a Wire Exists . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Combined Signals and Combined Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Combining Wires at a Cavity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Setting a Constraint to Combine Wires at a Cavity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Creating a New Combined Signal from Selected Signals . . . . . . . . . . . . . . . . . . . . . . . . . 488
Adding Selected Signals to an Existing Combined Signal . . . . . . . . . . . . . . . . . . . . . . . . . 488
Combining Selected Signals with a Compatible Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Removing Selected Child Signals from a Combined Signal . . . . . . . . . . . . . . . . . . . . . . . 490
Uncombining All Child Signals from a Combined Signal . . . . . . . . . . . . . . . . . . . . . . . . . 491
Creating a New Combined Wire from Selected Wires. . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Creating a New Combined Wire from a Selected Set of Wires for a Combined Signal . . 492
Adding Selected Wires to an Existing Combined Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Combining Selected Wires with a Compatible Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Uncombining Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Assigning Wire / Splice / Multicore Properties by Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Splice Editing in Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Creating a Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Moving a Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Merging Two Splices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Decomposing a Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Converting a Multiple Termination to a Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Automatically Converting Butt Splices to Center Strip Splices . . . . . . . . . . . . . . . . . . . . . . 501
Converting a Butt Splice to a Center Strip Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Converting a Center Strip Splice to a Butt Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
Creating a Multicore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Updating Wire Lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Modifying a Shield Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505

February 2016
Table of Contents
Copying Wiring Across the Levels of a Harness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505

Depopulating Wiring from Active Harness Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Editing Ground Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Exporting Wiring from a Capital Integrator Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Importing Wiring into a Capital Integrator Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Editing the Module Code for a Wire, Shield or Multicore . . . . . . . . . . . . . . . . . . . . . . . . . . 510
Routed States of Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Calculating the Routed State of Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Preserving Wiring during Topology Edits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Editing the Topology in Preserve Wiring Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516
Troubleshooting Wiring Synthesis Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Top-Level Debugging Process for Synthesis. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527
Chapter 19
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Available Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Chapter 20
Graphics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 535
Borders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Adding a Border to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Replacing a Border on a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Removing a Border from a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Graphic Drawing Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Drawing a Line in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Drawing a Rectangle in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Drawing a Polygon in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Drawing a Circle in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Drawing an Arc in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Drawing a Curved Line in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Adding Text Frames to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Adding a Picture to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Changing the Picture in an Image Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Adding a Comment Symbol to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Resizing a Comment Symbol in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Adding Properties to a Graphical Shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Editing a Property Value of Graphical Shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Editing the Graphical Properties of a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Stretching a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Moving a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Deleting a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542
Controlling the Layering Order (Z-Order) of Graphical Shapes and Objects . . . . . . . . . . 542
Graphics Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Adding a Graphics Point to a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Deleting a Graphics Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Grip Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Adding a Grip Point to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Deleting a Grip Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545

February 2016
Table of Contents
Chapter 21
Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Aligning Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Distributing Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Flipping Objects in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Rotating Objects in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Defining Rotation Increments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Free Rotation of an Object or Comment Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Pivoting Text about its Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Setting Snap To Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Setting Grid Defaults for a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Using Japanese Text on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Chapter 22
Capital AutoView Assist for Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Capital AutoView Assist for Integrator Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Functionally Partitioned Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
Generating a Single Design with Partitioned Wiring Diagrams Based on the Layout of
Functional Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Generating a Build List with Partitioned Wiring Diagrams Based on the Layout of Functional
Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Topology Led Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Generating a Topology-Led Wiring Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Translation of Objects When Generating Topology Led Diagrams . . . . . . . . . . . . . . . . . . 567
Custom Partitioned Wiring Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Overview of Flow for Custom Partitioned Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Generating Custom Partitioned Wiring Diagrams According to a User-Defined Property 572
Translation of Objects When Generating Partitioned Diagrams . . . . . . . . . . . . . . . . . . . . . . 576
Translation of Objects When Generating Diagrams Using Templates (Prototypes). . . . . . . 595
Generation of Slot Connectivity in Partitioned Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . 611
Distribution of Inlines By Home Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617
Chapter 23
Application Interface Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Ribbon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Project Browser Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Diagram Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Design Browser (Design Tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Logical Designs Browser (Function Tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
Parts Browser (Parts Tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
Configuration Setting Browser Window (Configuration Tab) . . . . . . . . . . . . . . . . . . . . . . . 632
Concurrency Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
Design Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Design Assistant (in Preserve Wiring Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
Design Inspector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Icons (Glyphs) in Browser Windows. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650

February 2016
Table of Contents
Chapter 24
Capital Integrator Dialog Box and Field Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 653
Bundle and Harness Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Harness Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Select Integral Harness Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658
Composite Data Management Dialog Boxes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Combine Levels for Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Configuration Builder Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
Define Harness Levels Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Define Vehicle Models Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
Give Away Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Set Standardized Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Set Harness Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
Connector Refinement and Signal Mapping Dialog Boxes. . . . . . . . . . . . . . . . . . . . . . . . . . 673
Connector Map Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
Fanout Viewer Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Manage Variance Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
Set Variant Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Signal Map Dialog Box for Inline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
Signal Map Dialog Box for Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
Signal Map Dialog Box for Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Diagram Creation Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
Edit Physical Scale Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
Edit Diagram Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703
Edit Skeleton Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
New Integrator Diagram Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 706
Printing Related Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Report Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
Connectivity Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
Report Material Statistics Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
Select Attributes/Properties for Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
Select Inclusion Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
Select Output for Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Wiring Synthesis Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
Miscellaneous Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Add Selected Logical Design Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Add Wire Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Assign Wiring Specifications by Rule Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 724
Associate Logical Designs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Capital Integrator design Filter Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Choose Functional Module Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
Combine Devices Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
Combine Wires at Cavity Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
Edit Ground Signals Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
Edit Levels Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
Edit Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Generate Slot Circuit Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745

February 2016
Table of Contents

Import Harness Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Move Wire Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
Name Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
New Property Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Place Device Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
Project Functional Module Codes Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
Select a Module Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
Select Codes for Combination Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
Select Module Code Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
Variant Expression Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
Capital AutoView Assist for Integrator Dialog Box and Field Reference . . . . . . . . . . . . . . 762
AutoView: Generate Wiring Diagram Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763
Diagram Partitioning Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797
Parent Folder Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803
Help Button Landing Pages for Capital Integrator Dialog Boxes . . . . . . . . . . . . . . . . . . . . . 804
Harness Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Select Integral Harness Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Combine Levels for Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Configuration Builder Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
Define Harness Levels Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
Define Vehicle Models Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
Give Away Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
Set Standardized Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Set Harness Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Connector Map Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Fanout Viewer Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Manage Variance Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
Set Variant Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
Signal Map for Inline Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
Signal Map for Interface Connector Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
Signal Map for Slot Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
Edit Physical Scale Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
Edit Diagram Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
Edit Skeleton Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
New Integrator Diagram Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
Connectivity Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Report Material Statistics Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Select Attributes/Properties for Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Select Inclusion Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Select Output for Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Wiring Synthesis Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Add Selected Logical Design Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Add Wire Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Assign Wiring Specifications by Rule Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Associate Logical Designs Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Capital Integrator Design Filter Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Combine Devices Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Combine Wires at Cavity Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813

February 2016
Table of Contents
Edit Ground Signals Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813

Edit Levels Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Generate Slot Circuit Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Import Harness Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Move Wire Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Place Device Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Select a Module Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
Select Module Code Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
Variant Expression Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
AutoView: Generate Wiring Diagram Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
Diagram Partitioning Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
Parent Folder Selection Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 816
Chapter 25
Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
Capital Integrator Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
Chapter 26
Capital Level Manager- Product Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 819
Introduction to Product Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
Enabling Capital Level Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
High-Level Flows for Using Capital Level Manager Product Planner and Harness Level
Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
Hierarchy of Product Planner Elements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
Product Planner Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
Importing a Product Plan in XML Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
Exporting a Product Plan in XML Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
Saving the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
Troubleshooting a Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
Mutually-Exclusive Variant Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
Creating a Variant in the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
Deleting a Variant from the Product Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
Editing the Vehicle Models in a Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
Creating a Mutually-Exclusive Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
Deleting a Mutually-Exclusive Variant Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
Importing Variant Group Data in XLS Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
Exporting Variant Group Data in XLS Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
Vehicle Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
Adding a Vehicle Model to the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
Deleting a Vehicle Model from the Product Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
Splitting a Vehicle Model in the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
Editing the Association of a Package with a Vehicle Model . . . . . . . . . . . . . . . . . . . . . . . 852
Editing the Association of an Option from a Package with a Vehicle Model . . . . . . . . . . 853
Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
Adding an Option to the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855

February 2016
Table of Contents
Deleting an Option from the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856

Creating an Exclusive Group of Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
Deleting an Exclusive Group of Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858
Creating an Inclusive Group of Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
Deleting an Inclusive Group of Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
Specifying an Option as Electrical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 862
Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863
Adding a Package to the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
Adding Options to a Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 866
Deleting a Package from the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
Creating an Exclusive Group of Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
Deleting an Exclusive Group of Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 869
Creating an Inclusive Group of Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
Deleting an Inclusive Group of Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
Creating a Must Have or Not Available Restriction on a Package. . . . . . . . . . . . . . . . . . . 872
Deleting a Must Have or Not Available Restriction on a Package. . . . . . . . . . . . . . . . . . . 874
VVD - Vehicle Variant Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
EVD - Electrical Variant Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
Generating VVD and EVD Counts for a Vehicle Model . . . . . . . . . . . . . . . . . . . . . . . . . . 876
Vehicle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
Take Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
Editing the Take Rates for Vehicle Models. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879
Chapter 27
Product Planner Dialog Box and Field Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881
Add New Option Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883
Package-Option Association Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884
Edit Custom Groups Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885
Edit Models Associated with Variant Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886
Exclusive/Inclusive Option Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
Exclusive/Inclusive Package Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
Variant Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
Option Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
Option Domain Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894
Package Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
Select Association Dialog Box (for an Option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
Select Association Dialog Box (for a Package). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
Select Standard Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899
Select Vehicle Models for Deletion Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
Take Rate Editor Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
Usage of Option Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
Exclusive Variant Groups Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
Product Planner Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907
Vehicle Creator Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
Help Button Landing Pages for Product Planner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Add New Option Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Package-Option Association Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Edit Custom Groups Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919

February 2016
Table of Contents
Edit Models associated with Variant Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919

Exclusive/Inclusive Option Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
Exclusive/Inclusive Package Editor Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
Variant Editor Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
Option Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
Option Domain Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
Package Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
Select Association (for an Option) Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
Select Association (for a Package) Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Select Standard Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Select Vehicle Models for Deletion Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Take Rate Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Usage of Option Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Exclusive Variant Groups Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
Product Planner Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
Vehicle Creator Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
Chapter 28
Capital Level Manager - Harness Level Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925
Introduction to Harness Level Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
Harness Level Optimization Tool Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
Harness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927
Metric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928
Creating a Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 929
Creating a Metric Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 930
Deleting a Metric Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
Editing a Metric Element Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 931
Deleting a Metric Element Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 932
Specifying the Architectural Cost of a Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934
Manually Specifying the Options that Affect a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . 934
Manually Creating a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
Manually Editing a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
Manually Combining Harness Levels into One . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
Manually Deleting a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
Manually Deleting all Harness Levels for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
Editing the Properties and Attributes of a Harness Level. . . . . . . . . . . . . . . . . . . . . . . . . . 939
Harness Level Definitions (Harness Optimization). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941
Importing Harness Level Definitions (Harness Optimization). . . . . . . . . . . . . . . . . . . . . . 942
Exporting Harness Level Definitions (Harness Optimization). . . . . . . . . . . . . . . . . . . . . . 943
Full Complexity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
Manually Generating the Full Complexity Harness Levels for a Harness . . . . . . . . . . . . . 944
Validating Physical Harness Levels against Full Complexity Harness Levels . . . . . . . . . 945
Optimized Complexity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
Creating the Optimized Complexity Harness Levels for a Harness . . . . . . . . . . . . . . . . . . 948
Giveaway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950

February 2016
Table of Contents
Chapter 29
Harness Level Optimization Dialog Box and Field Reference . . . . . . . . . . . . . . . . . . . . . . 951
Calculation Dialog Box (Capital Level Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
Combine Levels for Dialog Box (Capital Level Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . 953
Define Giveaway: Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
Condition Dialog Box (Capital Level Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959
Connector Mapping Tool Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962
Edit Metrics Dialog Box (Capital Level Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
Harness Levels for: Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
Harness Level Optimization Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
Set Harness Options Dialog Box (Capital Level Manager). . . . . . . . . . . . . . . . . . . . . . . . . . 974
Validation: Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
Help Button Landing Pages for Harness Level Optimization . . . . . . . . . . . . . . . . . . . . . . . . 977
Calculation (Capital Level Manager) Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Combine Levels (Capital Level Manager) Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Define Giveaway Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Condition (Capital Level Manager) Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Connector Mapping Tool Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Edit Metrics Dialog Box (Capital Level Manager) Help . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Harness Levels Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Harness Level Optimization Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Set Harness Options (Capital Level Manager) Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Validation Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
Chapter 30
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 981
Troubleshooting Wiring Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Wiring Synthesis Removes a Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Unexpected Option Expression on a Generated Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Troubleshooting Capital AutoView Assist for Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . 984
New Symbol Instance for Additional Pins when Using a Prototype . . . . . . . . . . . . . . . . . 984
Troubleshooting Capital Level Manager - Product Planner . . . . . . . . . . . . . . . . . . . . . . . . . 985
Error while Initializing Licensing Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 985
Third-Party Information
Index
End-User License Agreement

February 2016
List of Figures
Figure 1-1. Platform Level View of Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Figure 1-2. Design Problems Reported in Design Assistant . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 6-1. Example of Complex Harnesses Modeled without Multiple Harnesses at a Connector
116
Figure 6-2. Example of Complex Harnesses Modeled with Multiple Harnesses at a Connector
117
Figure 6-3. Modular Connector with Poked Home Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Figure 6-4. Topology Modeling of a Modular Connector with Poked Home Wire . . . . . . . 118
Figure 6-5. Modeling of Modular Connector with Poke Home . . . . . . . . . . . . . . . . . . . . . . 119
Figure 7-1. Example Modification of Signal Mapping for Replicated Connector (1). . . . . . 165
Figure 8-1. 150% Device in Capital Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Figure 8-2. Option Attribute of Market-RHD on Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Figure 8-3. Variant Slots in Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Figure 8-4. Variant Slots and Devices in Design Browser (Design Tab) . . . . . . . . . . . . . . . 205
Figure 8-5. Option Attribute of Market-LHD on Edit Properties Dialog Box for Device in Slot
TAPE_LHD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 8-6. Library Part Assignment on Edit Properties Dialog Box for Device in Slot
TAPE_LHD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 8-7. Footprint Details for Library Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 8-8. FP1 Pin Mapping Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Figure 8-9. FP2 Pin Mapping Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Figure 9-1. Inline Pair P3 and J3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218
Figure 9-2. Signal Map for J3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Figure 9-3. P3 with 12 Cavities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Figure 9-4. Cavity Matings between P3 and J3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Figure 9-5. Signal Mappings from P3 to J3. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Figure 9-6. New Connector Mating Row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Figure 9-7. Cavity Matings between P3, J3 and J3_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
Figure 9-8. Signal Mappings between P3, J3 and J3_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222
Figure 9-9. Fanout for J3, P3, J3_1 and P3_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Figure 9-10. Updated Fanout for J3, P3, J3_1 and P3_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Figure 9-11. Preferred Signal for P3_1 Cavity 1 to J3_1 Cavity 1 . . . . . . . . . . . . . . . . . . . . 226
Figure 9-12. 2N-SPKR-RT-1 and 2N-SPKR-RT-2 Mapped to Cavities. . . . . . . . . . . . . . . . 227
Figure 9-13. Wire Info Tab for Mapped Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Figure 9-14. Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Figure 9-15. Signal Map for P3 and J3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
Figure 9-16. Cavity Matings for Inline Pair P3 and J3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

February 2016
List of Figures
Figure 9-17. New Connector Mating Row for Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
Figure 9-18. Cavity Matings for Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Figure 9-19. Signal Mappings for Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232
Figure 9-20. Fanout for Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Figure 9-21. Updated Fanout for Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235
Figure 9-22. Unmapping 2N-SPKR-RT-1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Figure 9-23. Unmapped 2N-SPKR-RT-1 in New Row . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Figure 9-24. Mapping 2N-SPKR-RT-1 to P3_1 Cavity 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . 236
Figure 9-25. Signal Mappings with Two Rows with No Signals . . . . . . . . . . . . . . . . . . . . . 237
Figure 9-26. Rows with No Signals Disappeared . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
Figure 9-27. P3 Mapped to J3 and J3_1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Figure 9-28. P3 Cavity 1 Mapped to J3 Cavity 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Figure 9-29. 2N-SPKR-RR-1 Mapped to J3 Cavity 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Figure 10-1. Design with Four Devices and Four Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Figure 10-2. Devices Placed in Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260
Figure 10-3. Design with Four Devices and Three Nets . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261
Figure 10-4. Devices Placed in Slots Using Variant-Based Placement . . . . . . . . . . . . . . . . 261
Figure 10-5. Alternative Variant-Based Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262
Figure 12-1. Single-ended Shield in Capital Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310
Figure 12-2. Synthesized Shield in Capital Integrator - Desired Result . . . . . . . . . . . . . . . . 310
Figure 12-3. Synthesized Shield in Capital Integrator - Actual Result . . . . . . . . . . . . . . . . . 310
Figure 12-4. Desired result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311
Figure 13-1. Hierarchy of Composite Data Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Figure 13-2. Quick Start - Automotive Generative Project . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Figure 13-3. Example Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 322
Figure 13-4. Example Variant Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Figure 13-5. Audio Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Figure 13-6. Obsolete A-TAPE Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Figure 13-7. Other Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Figure 13-8. Valid Selections for AUDIO Option Combination. . . . . . . . . . . . . . . . . . . . . . 324
Figure 13-9. Example Vehicle Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Figure 13-10. Variants Supported by Vehicle Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325
Figure 13-11. Options from Option Folder Other . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326
Figure 13-12. Valid Selections from Option Combination AUDIO . . . . . . . . . . . . . . . . . . . 327
Figure 13-13. Options Included in Valid Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327
Figure 13-14. Example Harnesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328
Figure 13-15. Styled Harness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Figure 13-16. Highlighted Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329
Figure 13-17. BODY Harness in Design Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Figure 13-18. BODY Harness with no Harness Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Figure 13-19. Abstract Harness Levels for BODY Harness . . . . . . . . . . . . . . . . . . . . . . . . . 332
Figure 13-20. Variant Options, Options and Option Combinations Supported by Vehicle Model
332
Figure 13-21. Options Included in Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
Figure 13-22. Valid Selection of Audio Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

February 2016
List of Figures
Figure 13-23. Inclusion of Option in Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

Figure 13-24. Composite Wiring Synthesis Progress Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . 335
Figure 13-25. Harness Levels after Modular Wiring Synthesis . . . . . . . . . . . . . . . . . . . . . . 335
Figure 13-26. Harness Levels after Composite Wiring Synthesis. . . . . . . . . . . . . . . . . . . . . 335
Figure 13-27. Expanded Harness Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336
Figure 13-28. Example Vehicle Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Figure 13-29. Vehicle Models and Options Supported by Harness Level . . . . . . . . . . . . . . 337
Figure 13-30. Harness Levels Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Figure 13-31. Progress Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376
Figure 14-1. Modules Before a Merge Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394
Figure 14-2. Modules After a Merge Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395
Figure 14-3. Create a Module Example: Before . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Figure 14-4. Create a Module Example: After . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396
Figure 15-1. Terminal Bar in Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402
Figure 15-2. Internal Splices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404
Figure 15-3. Slot in Capital Integrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Figure 15-4. Connector with Net Conductors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Figure 15-5. Hole with Wires Spliced . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406
Figure 17-1. Connectivity Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Figure 18-1. Signal between Four Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Figure 18-2. Composite Wiring Synthesis Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Figure 18-3. Define Harness Levels Dialog Box with One Level. . . . . . . . . . . . . . . . . . . . . 443
Figure 18-4. Define Harness Levels Dialog Box with Multiple Levels . . . . . . . . . . . . . . . . 444
Figure 18-5. Unnecessary Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Figure 18-6. No Unnecessary Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
Figure 18-7. Harness H1 with One Level L1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Figure 18-8. Twisted Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Figure 18-9. Single-ended Shielded Multicore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 461
Figure 18-10. Multiple-ended Twisted Pair. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
Figure 18-11. Network Wiring Example Implementation. . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Figure 18-12. Network Wiring Structure Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
Figure 18-13. Before and After Example A for Combining Wires Connected to Slot Connectors
482
Figure 18-14. Before and After Example B for Combining Wires Connected to Slot Connectors
483
Figure 18-15. Before and After Example of Combined Splice . . . . . . . . . . . . . . . . . . . . . . . 483
Figure 18-16. Before and After Example of Combined Slot-Internal Splice . . . . . . . . . . . . 484
Figure 18-17. Before and After Example of Combined Wire Connected to Slot Device Pins
Through Slot Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Figure 18-18. Before and After Example of Combined Wire Connected to Slot Device Pin
Through Hole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Figure 18-19. Before and After Example of Combined Wire Connecting to Cavities or Backshell
Terminations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485
Figure 18-20. Unmapped Signal State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Figure 18-21. Internal Signal State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512

February 2016
List of Figures
Figure 18-22. Unconnected Signal State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513

Figure 18-23. Unrouted Signal State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Figure 18-24. Partially Routed Signal State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513
Figure 18-25. Routed Signal State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Figure 18-26. Signal Map Showing Unmapped Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519
Figure 18-27. No Physical Path Between Harnesses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 521
Figure 18-28. Path Broken by Optioned Bundles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 522
Figure 18-29. Path Broken by Inlines with no Available Cavities . . . . . . . . . . . . . . . . . . . . 523
Figure 18-30. Path Broken by Routing Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524
Figure 18-31. Constraint Preventing Multi-terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525
Figure 18-32. Constraints Preventing Splices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 526
Figure 18-33. Constraints Preventing Splices Due to Bundle Length . . . . . . . . . . . . . . . . . . 526
Figure 18-34. Top-Level Debugging Process for Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . 528
Figure 18-35. No Synthesis Required Debugging Process . . . . . . . . . . . . . . . . . . . . . . . . . . 529
Figure 18-36. No Route Available Debugging Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Figure 18-37. No Synthesis Solution Debugging Process . . . . . . . . . . . . . . . . . . . . . . . . . . . 530
Figure 22-1. System Wiring Diagram Property. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Figure 22-2. Indicator Each End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Figure 22-3. Indicators at End of First Wire Only. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576
Figure 22-4. Indicators at End of Each New Wire Segment . . . . . . . . . . . . . . . . . . . . . . . . . 577
Figure 22-5. Additional Connector Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577
Figure 22-6. Parallel Components in a Slot: Capital Logic Functional View . . . . . . . . . . . 579
Figure 22-7. Capital Integrator Slot - Power Distribution Box . . . . . . . . . . . . . . . . . . . . . . . 579
Figure 22-8. Resultant Shared Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 580
Figure 22-9. Generated Wiring Diagrams in Capital Logic: . . . . . . . . . . . . . . . . . . . . . . . . 580
Figure 22-10. Generated Wiring Diagrams: All Slot Internal Connectivity . . . . . . . . . . . . . 581
Figure 22-11. Series Connectivity: Capital Logic Functional View . . . . . . . . . . . . . . . . . . 581
Figure 22-12. Capital Integrator Slot - Power Distribution Box (Components within Slot) 582
Figure 22-13. Series Connectivity: Shared device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Figure 22-14. Series Connectivity: Generated Wiring Diagram in Capital Logic . . . . . . . . 583
Figure 22-15. Series Connectivity: Generated Wiring Diagrams without Slot Internal
Connectivity: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
Figure 22-16. Wiring Demoted Internally: Capital Logic Functional View: . . . . . . . . . . . . 584
Figure 22-17. Capital Integrator Slot (Power Distribution Box) and Initial Synthesized Wiring:
585
Figure 22-18. Internal Connectivity of Slot and Demoted Topology Wiring: . . . . . . . . . . . 585
Figure 22-19. Wiring Demoted Internally: Shared Device:. . . . . . . . . . . . . . . . . . . . . . . . . . 585
Figure 22-20. Wiring Demoted Internally: Generated Wiring Diagrams in Capital Logic: . 585
Figure 22-21. Distributed Objects: Capital Logic Functional View:. . . . . . . . . . . . . . . . . . . 587
Figure 22-22. Net Path to Distribute Physical Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . 588
Figure 22-23. Component Positioning: Capital Integrator Diagram and Prototype Template
Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 589
Figure 22-24. Component Positioning: New Wiring Diagram . . . . . . . . . . . . . . . . . . . . . . . 589
Figure 22-25. Fewer Pins: Capital Integrator Diagram and Prototype Template Diagram . . 590
Figure 22-26. Fewer Pins: New Wiring Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590

February 2016
List of Figures
Figure 22-27. Same Number of Pins: Capital Integrator Diagram and Prototype Template
Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591
Figure 22-28. Same Number of Pins: New Wiring Diagram . . . . . . . . . . . . . . . . . . . . . . . . 591
Figure 22-29. Different Connectivity: Capital Integrator Diagram and Prototype Template
Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592
Figure 22-30. Different Connectivity: New Wiring Diagram . . . . . . . . . . . . . . . . . . . . . . . . 592
Figure 22-31. Less Complexity: Capital Integrator Diagram and Prototype Template Diagram
593
Figure 22-32. Less Complexity: New Wiring Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 593
Figure 22-33. Route Paths: Capital Integrator Diagram and Prototype Template Diagram . 594
Figure 22-34. Route Paths: New Wiring Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 594
Figure 22-35. Original Functional Design with Multicore and Daisy Chain . . . . . . . . . . . . 595
Figure 22-36. Generated Wiring Diagram with Multicore and Shields Termination . . . . . . 595
Figure 22-37. Structural Matching of Prototype Paths: Prototype Path . . . . . . . . . . . . . . . . 597
Figure 22-38. Structural Matching of Prototype Paths: Generated Diagram. . . . . . . . . . . . . 598
Figure 22-39. Structural Matching of Prototype Paths: Structural Match . . . . . . . . . . . . . . . 599
Figure 22-40. Prototype Path Example 1. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 600
Figure 22-41. Prototype Path Example 1: Generated Diagram . . . . . . . . . . . . . . . . . . . . . . . 600
Figure 22-43. Inline and Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601
Figure 22-48. Prototype Path Example 1: New Functional Diagram . . . . . . . . . . . . . . . . . . 604
Figure 22-50. Prototype Path Example 5: Three Wires for Same Signal . . . . . . . . . . . . . . . 604
Figure 22-52. Prototype Path Example 7: Functional Diagram. . . . . . . . . . . . . . . . . . . . . . . 605
Figure 22-53. Prototype Path Example 7: Topological Diagram . . . . . . . . . . . . . . . . . . . . . 606
Figure 22-54. Prototype Path Example 7: Prototype for both LHD and RHD Configurations 606
Figure 22-55. Prototype Path Example 7: Generated Diagram for LHD and RHD Configurations
607
Figure 22-56. Connector Matching Example: Associated Functional Design . . . . . . . . . . . 608
Figure 22-57. Connector Matching Example: Topological Design. . . . . . . . . . . . . . . . . . . . 609
Figure 22-58. Connector Matching Example: Template (Prototype) LHD Configuration Design
609
Figure 22-59. Connector Matching Example: Generated RHD Configuration Design Using LHD
Configuration Design as Prototype . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 610
Figure 22-60. Example of Complex Slot-internal Connectivity where Multiple Functional Pins
Connect to a Single Slot Cavity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
Figure 22-61. Example of Complex Slot-internal Connectivity where a Single Functional Pin
Connects to Multiple Holes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612
Figure 22-62. Example of Complex Slot-internal Connectivity where Multiple Functional
Devices Connect to the Same Slot Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612

February 2016
List of Figures
Figure 22-63. Slot-internal Splice Connected to Cavities . . . . . . . . . . . . . . . . . . . . . . . . . . . 613

Figure 22-64. Example of Simple Slot-internal Connectivity where Each Functional Pin Maps
One to One with Cavities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Figure 22-65. Example of Simple Slot-internal Connectivity Generated in All Slot Internal
Connectivity Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 613
Figure 22-66. Simple Slot-internal Connectivity Generated in Minimum Slot Internal
Connectivity Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614
Figure 22-67. Functional Pin Mapped to Multiple Cavities Topology . . . . . . . . . . . . . . . . . 614
Figure 22-68. Functional Pin Mapped to Multiple Cavities Generated Diagram . . . . . . . . . 614
Figure 22-69. Generation of a Slot Internal Splice Mapped Entirely to Holes . . . . . . . . . . . 614
Figure 22-70. Net Instances Marked with Home Conditions . . . . . . . . . . . . . . . . . . . . . . . . 618
Figure 22-71. Inline Connectors in Path of Two Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . 618
Figure 22-72. Distribute Inlines Not Selected: Generated Diagram 1. . . . . . . . . . . . . . . . . . 619
Figure 22-75. Distribute Inlines Selected: Generated Diagram 1 . . . . . . . . . . . . . . . . . . . . . 620
Figure 23-1. Project Browser Window in Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Figure 23-2. Elements in Project Browser Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Figure 23-3. Diagram Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Figure 23-4. Design Browser (Design Tab) in Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627
Figure 23-5. Logical Designs Browser (Function Tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 630
Figure 23-6. Parts Browser (Parts Tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
Figure 23-7. Configuration Setting Browser Window (Configuration Tab) . . . . . . . . . . . . . 632
Figure 23-8. Concurrency Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
Figure 23-9. Output Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
Figure 23-10. Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Figure 23-11. Design Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Figure 24-1. Example Material Report by Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711
Figure 24-2. Wiring Diagram with and without Distribute Splices selected. . . . . . . . . . . . . 791
Figure 24-3. Wiring Diagram with and without Create Ported Wires where Functional Nets are
Ported Selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793
Figure 24-4. Wiring Diagrams with different Minimum Wire Spacing settings. . . . . . . . . . 794
Figure 26-1. Unconstrained Harness Complexity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823
Figure 26-2. Product Planner Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835

February 2016
List of Tables
Table 2-1. Release Level Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Table 4-1. Stroke Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Table 13-1. Composite Data Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Table 18-1. Messages Displayed When No Synthesis is Required . . . . . . . . . . . . . . . . . . . 519
Table 18-2. Messages Displayed When No Route Is Available . . . . . . . . . . . . . . . . . . . . . . 524
Table 18-3. Messages Displayed When No Synthesis Solution Is Possible . . . . . . . . . . . . . 527
Table 22-1. Example Project Structures when Generating Functionally-Partitioned Diagrams
554
Table 22-2. Results of Partitioning Properties on Objects . . . . . . . . . . . . . . . . . . . . . . . . . . 570
Table 22-3. Examples of Source Connectivity and Generated Results . . . . . . . . . . . . . . . . 615
Table 22-4. Propagation of Home Condition by Object Type . . . . . . . . . . . . . . . . . . . . . . . 621
Table 23-1. Project Browser Window Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 624
Table 23-2. Design Tab Toolbar Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628
Table 23-3. Signals Folder Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
Table 23-4. Design Browser Filter Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
Table 23-5. Configuration Setting Browser Window (Configuration Tab) Contents . . . . . 633
Table 23-6. Concurrency Tab Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
Table 23-7. Output Window Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 640
Table 23-8. Signal/Multicore Name (Wiring View) Tab Contents . . . . . . . . . . . . . . . . . . . 641
Table 23-9. Status Bar Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 643
Table 23-10. Topology Edits Tab Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
Table 23-11. Modified Object Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Table 24-1. Harness Selection Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657
Table 24-2. Select Integral Harness Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 658
Table 24-3. Combine Levels for Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660
Table 24-4. Configuration Builder Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 661
Table 24-5. Define Harness Levels Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Table 24-6. Define Vehicle Models Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 666
Table 24-7. Give Away Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Table 24-8. Platform Options Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671
Table 24-9. Set Harness Options Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
Table 24-10. Connector Map Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
Table 24-11. Fanout Viewer Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675
Table 24-12. Manage Variance Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
Table 24-13. Set Variant Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Table 24-14. Signal Map Dialog Box for Inline Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 680
Table 24-15. Signal Map Dialog Box for Interface Connector Contents . . . . . . . . . . . . . . . 688
Table 24-16. Signal Map Dialog Box for Slot Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 692
Table 24-17. Edit Physical Scale Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
Table 24-18. Edit Diagram Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703

February 2016
List of Tables
Table 24-19. Edit Skeleton Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705

Table 24-20. New Integrator Diagram Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . 706
Table 24-21. Connectivity Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
Table 24-22. Report Material Statistics Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . 711
Table 24-23. Select Attributes/Properties for Dialog Box Contents . . . . . . . . . . . . . . . . . . 713
Table 24-24. Select Inclusion Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
Table 24-25. Select Output for Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Table 24-26. Wiring Synthesis Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
Table 24-27. Add Selected Logical Design Dialog Box Contents . . . . . . . . . . . . . . . . . . . . 722
Table 24-28. Add Wire Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Table 24-29. Assign Wiring Specifications by Rule Dialog Box Contents . . . . . . . . . . . . . 724
Table 24-30. Associate Logical Design Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . 725
Table 24-31. Capital Integrator Design Filter Dialog Box Contents . . . . . . . . . . . . . . . . . . 727
Table 24-32. Combine Devices Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
Table 24-33. Combine Wires at Cavity Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . 731
Table 24-34. Edit Ground Signals Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
Table 24-35. Edit Levels Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
Table 24-36. General Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735
Table 24-37. Properties Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739
Table 24-38. Graphical Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 740
Table 24-39. Rules Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
Table 24-40. Routes Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 742
Table 24-41. Variance Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 743
Table 24-42. Variant Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 744
Table 24-43. Generate Slot Circuit Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 745
Table 24-44. Edit Build List Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Table 24-45. Import Harness Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 748
Table 24-46. Move Wire Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
Table 24-47. Name Selection Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
Table 24-48. New Property Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Table 24-49. Place Device Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
Table 24-50. Select a module Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
Table 24-51. Edit Option Expression Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . 760
Table 24-52. Generate Topology Led Diagram/Functionally Partitioned Diagrams/Custom
Partitioned Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764
Table 24-53. Design Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765
Table 24-54. Design Details (with Generate Single Diagram Selected or Not Applicable) . 766
Table 24-55. Design Details (without Generate Single Diagram Selected) . . . . . . . . . . . . . 768
Table 24-56. Option Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 770
Table 24-57. Options Tab (with Generate Topology Led Diagram Selected) . . . . . . . . . . . 770
Table 24-58. Options Tab (with Generate Functionally Partitioned Diagrams Selected) . . 772
Table 24-59. Options Tab (with Custom Partitioned Diagrams Selected) . . . . . . . . . . . . . . 781
Table 24-60. Filter Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 788
Table 24-61. Slot GraphicsTab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790
Table 24-62. Prototype Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 790

February 2016
List of Tables
Table 24-63. Diagram Partitioning Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 800

Table 27-1. Add New Option Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883
Table 27-2. Edit Package-Option Association Editor Dialog Box Contents . . . . . . . . . . . . 884
Table 27-3. Edit Custom Groups Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885
Table 27-4. Exclusive/Inclusive Option Editor Dialog Box Contents . . . . . . . . . . . . . . . . . 887
Table 27-5. Exclusive/Inclusive Package Editor Dialog Box Contents . . . . . . . . . . . . . . . . 889
Table 27-6. Variant Editor Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
Table 27-7. Option Editor Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
Table 27-8. Option Domain Editor Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 894
Table 27-9. Package Editor Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
Table 27-10. Select Association Dialog Box (for Option) Contents . . . . . . . . . . . . . . . . . . 897
Table 27-11. Select Association Dialog Box (for Package) Contents . . . . . . . . . . . . . . . . . 898
Table 27-12. Take Rate Editor Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
Table 27-13. Usage of Option Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
Table 27-14. Exclusive Variant Groups Editor Dialog Box Contents . . . . . . . . . . . . . . . . . 905
Table 27-15. Product Planner Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907
Table 27-16. Vehicle Creator Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
Table 29-1. Calculation Dialog Box (Capital Level Manager) Contents . . . . . . . . . . . . . . . 952
Table 29-2. Combine Levels for Dialog Box (Capital Level Manager) Contents . . . . . . . . 953
Table 29-3. Define Giveaway: Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
Table 29-4. Condition Dialog Box (Capital Level Manager) Dialog Box Contents . . . . . . 959
Table 29-5. Connector Mapping Tool Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . 962
Table 29-6. Edit Metrics Dialog Box (Capital Level Manager) Dialog Box Contents . . . . 964
Table 29-7. Harness Levels for: Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
Table 29-8. Harness Level Optimization Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . 970
Table 29-9. Set Harness Options Dialog Box (Capital Level Manager) Contents . . . . . . . . 974
Table 29-10. Validation: Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975

February 2016
List of Tables

February 2016
Chapter 1
Overview
This chapter contains high-level, introductory information about Capital Integrator and aspects
of its functionality.
Overview of Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Capital Insight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Styling Objects in Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Logical Design Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Associating Logical Designs with the Topological Design . . . . . . . . . . . . . . . . . . . . . . . . 37
Replacing a Logical Design Association. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Object Attribute Descriptions for Use in Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . 42
Viewing the Details of Installed Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Selecting an Extensibility Plugin from the Plugins Dialog Box. . . . . . . . . . . . . . . . . . . . . 43
Custom Action Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Object Model Integrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Launching Capital Library from this Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Launching Capital Symbol from this Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Diagram Language Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Engineering Change Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Harness Concurrency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Selecting which Lockable Objects to View on the Concurrency Tab . . . . . . . . . . . . . . . . 49
Locking a Harness or Slot when Running in Multi User Mode . . . . . . . . . . . . . . . . . . . . . 50
Unlocking a Harness or Slot when Running in Multi User Mode . . . . . . . . . . . . . . . . . . . 51
Unlocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Refreshing Harness Information with Changes from Other Users . . . . . . . . . . . . . . . . . . . 52
Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

February 2016
Overview
Overview of Capital Integrator

Capital Integrator is the application that is used to create platform designs for a project. It is at
the core of the generative flow and automates the integration of vehicle logical connectivity data
into full platform wiring designs. It allows you to automatically synthesize a physical electrical
wiring design from a logical functional design.
Capital Integrator provides a platform level view of the design.
Figure 1-1. Platform Level View of Design
The tool allows systems integration engineers to capture engineering knowledge and
constraints, and assists in the complex task of transforming the electrical intent of platform
systems to full composite harness designs. Capital Integrator supports this task at all stages of
the design process:
• Conceptual phase
Capital Integrator provides rapid analysis of alternative topologies and functional
packaging options to enable cost and complexity trade-offs.
• Design stage

February 2016
Overview
Composite wiring synthesis automates the process of determining optimum harness

content, based on the option and variant constraints defined both in the functional
schematics and as market requirements. This process is also driven by physical,
electrical and regulatory constraints captured as customer-specific rules and rule sets.
Note
Capital Integrator works with Capital Logic for the definition of components and
connectivity which comprise the electrical system, Capital Library for the creation
and maintenance of parts, Capital User for the management of user roles and
permissions, Capital Project for the management of projects, Capital Symbol for the
management of the borders and skeletons and Capital Enterprise Reporter for the
production of reports and queries from the database.
• Validation phase
At certain points in the design process, designers will want to check that the information
they have inputted is correct. The design rule checks and design assistant facility
provide users with the option to validate the design at various intervals, checking for
instances such as correct part number selection, connectivity of wires, routing of wires
and placement of devices in slots.
A number of pre-defined design rule checks exist, these can be configured by users to
validate design content. The design assistant tool allows you to configure and run
specific checks as, and when, they are required. The results are displayed in an output
window with messages underlining where the problem is occurring and where possible,
why that problem is occurring. Hyper links will zoom in to the affected area of the
design.
Figure 1-2. Design Problems Reported in Design Assistant
A platform design contains information about the physical layout of the vehicle harnesses. It is
used to specify the physical location of devices within the vehicle and to synthesize wiring for
the logical signals specified in Capital Logic designs. When you synthesize wiring, Capital
Integrator determines the lowest cost set of wires and splices that adhere to any specified rules
and constraints.
A project is usually an automotive or aerospace product line. Projects are top-level 'containers'
for all of the harness designs and data that comprise a specific product line.
Once created, a project can have data added from many of the design applications.

February 2016
Overview
The information that is contained within a project is arranged into distinct 'sub-containers'
called Designs. Designs are versional data containers that can have their contents copied as
required. A Capital Logic design is usually created for each sub-system of a product line. A
Capital Integrator design is often created for each alternative physical layout of the product line.
Designs can be created for a project using Capital Project.
In Capital Logic and Capital Integrator the information that is contained in a design can be
represented across one or more diagrams.
Once created in Capital Project, a project can be opened into Capital Logic and the logical
schematic diagrams for the connectivity of the harnesses created for the designs within that
project. A logical schematic contains devices and nets, it does not contain wires and connectors.
The project can then be opened in Capital Integrator and the platform diagrams created. After
you have synthesized wiring, the platform diagrams will contain connectors, wires, and splices
that implement the connectivity defined in the associated system designs. The Open Project
facility in Capital Integrator, displays the same project list as that in Capital Project and Capital
Logic (unless project access restrictions have been imposed on the user using the Capital User
application).
Capital Integrator can be used to create platform designs and synthesize wiring for single
harnesses and also for composite harnesses. See “Composite Data Overview” on page 318 for
more information about working with composite harnesses.
After a platform design has been created in Capital Integrator, you can view wiring data from it
in Capital Logic by using Capital AutoView Assist for Integrator (see “Capital AutoView Assist
for Integrator” on page 551) or use it in Capital HarnessXC where harnesses are engineered. It
is also possible to copy Capital Integrator designs within a project and to report on the electrical
connectivity within a Capital Integrator design in Capital Reporter.
When a platform design is complete, it can be imported into Capital Harness & Factory where
the data can be used to manufacture harnesses. See the Capital Engineer help system for more
information on accessing Capital Integrator designs from Capital Engineer.
Accessing Capital Integrator

Capital Integrator can be accessed from the Capital Launcher by selecting Capital Integrator.
Alternatively, you can select the Capital Design option from the Capital Launcher. The Capital
Design application allows the user to access both Capital Logic designs and Capital Integrator
designs from the same window.
Opening Capital Design will check out both a Capital Logic and a Capital Integrator license.
When using Capital Design, you must open a Capital Logic diagram to access the menu options
and functionality for Capital Logic. You must open a Capital Integrator diagram to access the
menu options and functionality for Capital Integrator.

February 2016
Overview
User Access Rights in Capital Integrator

The access that a user has to the various aspects of Capital Integrator is controlled by the Capital
User application. See your Capital administrator and /or the Capital User help system for more
information on the access controls and levels available.
High-Level Wiring Synthesis Process in Capital Integrator

The electrical wiring creation process begins by opening a project. You then open a diagram
within a design (if the design does not exist, you use Capital Project to create it). In the diagram,
you define the harness topology and route wiring for all composite harness levels, save the
diagram, and close the project when complete.
This process is described below and assumes that the project structure has been decided.
1. Open the project. Enter the name if new, select from list if existing.
See “Opening a Project” on page 56 or “Creating a Project” on page 56.
2. Open Integrator design. Enter the name if new, select from the list if existing.
If creating a new design, see “Creating a New Design” on page 62.
3. Open Integrator diagram. Enter the name if new, select from list if existing.
See “Setting up Diagrams” on page 75.
4. Create slots. Add placement rules to them if applicable. See “Creating Slots” on
page 95.
5. Add harness topology by adding bundles. See “Creating Bundles and Harnesses” on
page 103.
6. Define harnesses by inserting inline connectors and naming harnesses. See “Inline Pair”
on page 147.
7. Run design rule checks to validate bundle connectivity.
See “Design Rule Checks” on page 72.
8. Associate logical designs. When doing this, select either a build list or individual
designs. See “Associating Logical Designs with the Topological Design” on page 37.
9. Place devices in the slots. Do this manually or by using automatic rule-based placement.
See “Placement of a Device or Ground Device in a Slot” on page 174.
10. Run design rule checks manually or using the Design Assistant to check for empty slots
and unplaced devices.
See “Design Rule Checks” on page 72.
11. Define vehicle models. When doing this, define variant option and model restrictions.
See “Vehicle Model” on page 346.

February 2016
Overview
Capital Insight
12. Generate (or import) harness levels for each harness family. See “Harness Level” on
page 352.
13. Synthesize all wiring: Use either Modular Wiring Synthesis, Composite Wiring
Synthesis or manual synthesis. Route signals automatically and perform manual
adjustments as required. See “Synthesizing Wiring” on page 440.
14. Save the design.
15. Run final design rule checks.
16. Close the design and project.
Capital Insight
Capital Insight is an additional product that provides functionality for conducting physical
architectural trade studies on designs created in Capital Integrator, Capital Topology, Capital
HarnessXC or Capital ModularXC. These studies use metrics to compare design data, for
example, using cost and weight.
Styling Objects in Diagrams

You specify the way in which you want to style objects in diagrams by using a style set. Style
sets are maintained at the system level but are applied to individual diagrams. Capital Integrator
uses a Default style set.
The creation of style sets beyond the default offered is a licensed operation; if you do not have
the license required, the option to create new style sets is unavailable.
See the Diagram Styling User Guide for more information about style sets and how to edit
them.
Logical Design Association

In order to place devices and synthesize wiring in a topological design, you must associate one
or more logical designs from Capital Logic with it. When doing this, you associate a specific
revision of each design.
You can associate more than one logical design with a single topological design. To do this, you
can either associate the designs individually or associate a build list.
You can replace a logical design association with either an association to a newer revision of
that design or with an association to a similar design that is not a related revision. When you do
this, the topological design retains the device placement and wiring for common devices and
nets from those logical designs or revisions.

February 2016
Overview
Associating Logical Designs with the Topological Design
Note
An audit trail event Associated logical designs changed is available for when changes are
made to logical design associations. See Audit Trail in the Capital Project User Guide.
Build List Association (Managed Mode)

If you use a build list, you enter a managed mode where Capital Integrator is aware of any
changes to the build list. New logical designs and revisions can be added to the build list at any
time in Capital Logic or Capital Project.
When you open the topological design in Capital Integrator, an Update design associations?
message is displayed if changes have been made to the build list. At that point, you select either
to not update the associations (Don’t Update) or to review those changes (Review Changes). If
you review the changes, they are not applied until you click OK in the Associate Logical
Designs dialog box. You click Cancel if you do not want to apply them.
Related Topics
Replacing a Logical Design Association
Associate Logical Designs Dialog Box
Associating Logical Designs with the

Topological Design
In order to place devices and synthesize wiring in a topological design, you must associate one
or more designs from Capital Logic with it. When doing this, you associate a specific revision
of each design.
You can associate more than one logical design with a single topological design. To do this, you
can either associate the designs individually or associate a build list.
Procedure
Either:
• Press Space Bar and enter Associate Logical Designs.

• Click the Associate Logical Designs ( ) button on the Design Browser (Design
tab).

February 2016
Overview
The Associate Logical Designs Dialog Box is displayed and the Associated Designs
window displays any logical designs that are associated already.
If you want to... Do the following:

Associate individual designs 1. Select None from the Managed by Build List
drop-down list.
2. Click the Add associated designs ( ) button;
the Add Selected Logical Design Dialog Box is
displayed.
3. In the Logical designs window, select the logical
designs that you want to associate and click Add
Selected; the logical designs are added to the
Associated Designs window in the Associate
Logical Designs dialog box.
An icon ( ) is displayed next to the added
designs.
If you add a design that is a newer revision of an
already associated design, the following indicates
that the new one will replace the old:
4. Click OK to save the changes.
Associate a build list 1. Select the build list from the Managed by Build
List drop-down list; the design revisions from the
build list are displayed in the Associated Designs
window.
2. Click OK to associate the design revisions from
the build list.
Note
When associating individual designs, you can remove the association with a logical
design by selecting it in the Associated Designs window and clicking the Remove
associated designs button. An icon indicates that you are going to remove the
association when you click OK.
Results
• The devices and nets from the associated designs are added to the Logical Designs
Browser (Function tab). The listed devices are ready to be placed in slots. See
“Placement of a Device or Ground Device in a Slot” on page 174.
• After the devices are placed in slots, you can synthesize wiring for the nets. See
“Synthesizing Wiring” on page 440.

February 2016
Overview
Notes relating to option expressions on devices and nets:

• Any nets that are tagged with an option expression that evaluates to FALSE because of
obsolete options are not added to the Logical Designs Browser. Similarly, a net
connection is not added if that connection’s pins are tagged with an option expression
that evaluates to FALSE because of obsolete options.
• Devices tagged with an option expression that evaluates to FALSE because of obsolete
options are not added. Similarly, a device is not added even if one of its pins is tagged
with an option expression that evaluates to FALSE because of obsolete options.
• In the case of a net connected to multiple pins, the net is added if at least one of its pins
has an option expression that is TRUE. However, the net is ignored if its pins all have
option expressions that are FALSE.
Related Topics
Placement of a Device or Ground Device in a Slot
Synthesizing Wiring
Logical Designs Browser (Function Tab)

You can replace a logical design association with either an association to a newer revision of
that design or with an association to a similar design that is not a related revision.
When you do this, the topological design retains the device placement and wiring for common
devices and nets from those logical designs or revisions.
Prerequisites
• The new design or design revision must have been created in Capital Logic or Capital
Project.
• If you are working in managed mode (where a build list association is used), the new
design/revision must be added to the associated build list and the old one must be
removed.
• If you are replacing an associated design with a similar design that is not a related
revision, any devices and nets that are common to both must have the same names in
both.
Note
If you are replacing an associated design with a newer revision, devices and nets are
matched by UID and therefore do not need to have the same names.

February 2016
Overview
Procedure
Follow the appropriate procedure from the table.

Replace an old design 1. Open the topological design in Capital Integrator;
revision with a new revision an Update design associations? message is
in managed mode (where a displayed.
build list association is used) 2. Click Review Changes, the Associate Logical
Designs Dialog Box is displayed and indicates
the changes that are suggested as a result of the
build list changes.
3. Click OK to accept the changes.
Replace a design with a 1. Open the topological design in Capital Integrator;
design that is not a related an Update design associations? message is
revision in managed mode displayed.
(where a build list 2. Click Review Changes, the Associate Logical
association is used) Designs Dialog Box is displayed and indicates
the changes that are suggested as a result of the
build list changes.
3. Indicate that the new design replaces the old
design. To do this, either drag the old design with
the icon over the new design with the icon
or select them both and click the Replace the
selected ‘removed’ design with the selected
‘added’ design ( ) button.
4. Click OK to accept and save the changes.
Replace an old design 1. With the topological design open in Capital
revision with a new revision Integrator, press Space Bar and enter Associate
in non-managed mode Logical Designs; the Associate Logical Designs
(where individual design Dialog Box is displayed.
associations are used) 2. Click the Add associated designs ( ) button;
displayed.
3. In the Logical designs window, select the new
logical design revision and click Add Selected;
the design revision is added to the Associated
Designs window in the Associate Logical
Designs dialog box. The following icons indicate
that the new one will replace the old.
4. Click OK to save the changes.

February 2016
Overview

Replace a design with a 1. With the topological design open in Capital
design that is not a related Integrator, press Space Bar and enter Associate
revision in non-managed Logical Designs; the Associate Logical Designs
mode (where individual Dialog Box is displayed.
design associations are used) 2. Click the Add associated designs ( ) button;
displayed.
3. In the Logical designs window, select the new
logical design and click Add Selected; the design
is added to the Associated Designs window in
the Associate Logical Designs dialog box.
4. Select the old design association and click the
Remove associated designs ( ) button. An icon
( ) indicates that you are going to remove the
association.
5. Indicate that the new design replaces the old
design. To do this, either drag the old design with
the icon over the new design with the icon
or select them both and click the Replace the
selected ‘removed’ design with the selected
‘added’ design ( ) button.
6. Click OK to accept and save the changes.
Results
• The topological design retains the device placement and wiring for common parts of
those logical designs or design revisions.
• New devices are ready to be placed.
• New nets are ready to have wiring synthesized.
Related Topics
Synthesizing Wiring

February 2016
Overview
Extensibility Plugins
You can view the details of any extensibility plugins that you have installed, load new plugins
and reload modified plugins.
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.
Object Attribute Descriptions for Use in Extensibility Plugins. . . . . . . . . . . . . . . . . . . . 42

Viewing the Details of Installed Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Selecting an Extensibility Plugin from the Plugins Dialog Box . . . . . . . . . . . . . . . . . . . . 43
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.
Related Topics
Viewing the Details of Installed Extensibility Plugins
Reloading Extensibility Plugins
Design Inspector
Viewing the Details of Installed Extensibility

Plugins
You can view the details of the extensibility plugins that you have installed.
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. The Plugin Details
Dialog Box is displayed.
3. View the details and click Close.

February 2016
Overview
Related Topics
Design Inspector

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 in which you are working.
Procedure
1. Press Space Bar and enter Plugins. The Plugins Dialog Box is displayed.
2. Click Reload All. The Available Plugins table is updated and any new or modified
plugins are available to use in your Capital applications.
Related Topics
Design Inspector
Selecting an Extensibility Plugin from the Plugins

Dialog Box
You can select an extensibility plugin from the Plugins dialog box when you want to specify an
extensibility plugin in a field on another dialog box.
Procedure
In the Plugins Dialog Box, select the extensibility plugin from the Available Plugins table and
click OK; the Plugins dialog box closes and the extensibility plugin is added to the field in the
other dialog box.
Custom Action Plugins

Custom actions are customer-delivered functions that are exposed in the Capital Integrator 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 Java-script - which is
placed into the \plugins sub-directory of the Capital installation location. These plugins are
loaded when the application is launched, and can be inspected from within Capital Integrator;
see “Viewing the Details of Installed Extensibility Plugins” on page 42 for more information.

February 2016
Overview
Object Model Integrity
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:
• In 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 on an object in the Design Browser
(Design tab). 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.
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.

To ensure the integrity of all data within the Capital database, the integrity of data object models
(for example: components, designs, nets, and so on) can be automatically validated as, and
when, changes are made.
Any validation errors will be reported in a warning dialog box and written to the event log, and
the action that triggered the validation will be aborted, removing the possibility that the invalid
object model can be written to the database, possibly resulting in data corruption.
The level of validation is specified in the clientprops.xml file, located in the config sub-directory
of your Capital install directory.
The following line sets the level of validation:
<validation level=”VALUE”/>
Replace VALUE with one of the following options:
• NONE - no validation will be performed.

• LOW - validation will be performed on import, save and design generation. Otherwise,
no validation will be performed unless an exception is raised, in which case validation
will then also be performed on export and load.

February 2016
Overview
• MEDIUM - validation will be performed on import, export, load, save and design
generation. Otherwise, no validation will be performed unless an exception is raised, in
which case validation will then also be performed on object modification.
• HIGH - validation will be performed on load, save, import, export, design generation
and object modification.
A number of optional arguments can be added to the validation level statement in the form:
<validation level="HIGH" failureStopsExportValidation="true"

exceptionIncreasesLevel="true"
exceptionTriggersValidation="true"/>
replacing attribute name with one of the following attributes:
• failureStopsValidation
o false - if a validation failure has been detected, validation will continue to be
performed.
o true - if a validation failure has been detected, validation will no longer be
performed.
• failureStopsExportValidation
o false - if a validation failure has been detected, validation will not be performed on
export operations, thus allowing customers to export projects with invalid data to us.
o true - if a validation failure has been detected, validation will be performed on export
operations.
• exceptionIncreasesLevel
o false - if an exception has been raised anywhere in the code, the validation level will
remain the same.
o true - if an exception has been raised anywhere in the code, the validation level will
be increased once (from LOW to MEDIUM, or MEDIUM to HIGH).
• exceptionTriggersValidation
o false - when the validation is set to LOW, any exceptions will not force a validation.
o true - when the validation level is set to LOW, any exception encountered will
trigger a validation at level HIGH.
Note
None, any or all of the optional attributes can be added to the validation level
statement, with each attribute being separated by a space.

February 2016
Overview
Launching Capital Library from this Application
Launching Capital Library from this

Application
You can launch Capital Library from this application.
Procedure
Press Space Bar and enter Capital Library; Capital Library launches in a separate window.
Launching Capital Symbol from this

Application
You can launch Capital Symbol from this application.
Procedure
Press Space Bar and enter Capital Symbol; Capital Symbol launches in a separate window.
Diagram Language Translation

You can display, print and publish diagrams 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.
See Diagram Language Translation in the Capital Design Tools - Common Functions User
Guide for full details.
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.
You can:
• manually create ECOs within the Capital design applications.

For detailed information about ECOs, see the Engineering Change Orders section in the
Capital Design Tools - Common Functions User Guide.

February 2016
Overview
Harness Concurrency
Harness Concurrency
Harness concurrency is functionality that allows you to run Capital Integrator in multi user
mode or single user mode. Multi user mode enables multiple users to open the same Capital
Integrator design for simultaneous editing and allows each user to work on a different portion of
the design. This is achieved primarily by the ability to lock individual harnesses and slots.
If you do not run Capital Integrator in multi user mode, you run it in single user mode. In this
mode, if a user opens a design, other users can open the same design in read-only mode only.
If a lock is held on a design in Capital Integrator, the design for that design cannot be edited or
deleted in Capital Project. If you hold a lock on a slot or harness in Capital Integrator, other
users cannot perform editing actions that operate directly on that locked object and connected
objects. Connected objects can be bundles, nodes, bundle regions, inline connectors, interface
connectors, cavities and wiring objects. Any actions that they cannot perform are disabled for
the locked objects.
Note
To run Capital Integrator in single user mode, your user account must have the Manage
Design permission set in Capital User. You can still edit a design in multi user mode even if
you do not have this permission set. See the Capital User help system for more information
about setting permissions for user accounts.

Selecting which Lockable Objects to View on the Concurrency Tab . . . . . . . . . . . . . . . 49
Locking a Harness or Slot when Running in Multi User Mode . . . . . . . . . . . . . . . . . . . 50
Unlocking a Harness or Slot when Running in Multi User Mode. . . . . . . . . . . . . . . . . . 51
Unlocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Refreshing Harness Information with Changes from Other Users . . . . . . . . . . . . . . . . 52
Relationships between Locks and User Modes

The following describe the relationships between locks and user modes.
Complete Design Lock in Single User Mode

If you edit a design in single user mode, you have a complete design lock that allows you to edit
everything and prohibits other users from editing any object in that design. When editing a
design, you cannot change to single user mode if another user is editing the design in multi user
mode. If you have the Manage Design permission, when you open a design that is not being

February 2016
Overview
Relationships between Locks and User Modes
edited by another user, you are automatically in single user mode and therefore have a complete
design lock. When you close the design in single user mode, the design lock is removed.
Weak Design Lock in Multi User Mode

If you edit a design in multi user mode, you have a weak lock on that design. This means other
users can edit the design only in multi user mode too. In order to edit a slot or harness in that
design, you must lock that object so that other users cannot edit it at the same time as you (see
“Locking a Harness or Slot when Running in Multi User Mode” on page 50). When you close a
design in multi user mode, your weak lock is removed. If you change from multi user mode to
single user mode, any slot or harness locks are removed because you can then edit any objects
without manually locking them.
When you are editing a diagram in multi user mode, you can dim (gray out) objects that are
unlocked and objects that are locked by other users. This means that you only see objects that
you have locked and can edit. See “Dimming (graying out) Slots and Harnesses that are Locked
by Other Users or that Are Unlocked” on page 52.
After you have finished editing an object, you should unlock it so that other users can edit it if
required (see “Unlocking a Harness or Slot when Running in Multi User Mode” on page 51).
If you create a new harness or slot in multi user mode, no other user will see the new object on
their Concurrency Tab until you save it. When you save the object, you have a lock on it
automatically.
When users are editing a Capital Integrator design in multi user mode, they must all have the
same view of the data in the associated Capital Logic designs. This means that:
• The Synchronize Logical Changes functionality is disabled.

• Opening a Capital Integrator design in multi user mode is not allowed if any associated
Capital Logic design has changed.
• Any associated Capital Logic design cannot be opened for editing in the same session of
Capital Design.
Related Topics
Harness Concurrency
Concurrency Tab
Selecting Multi User or Single User Mode
Selecting which Lockable Objects to View on the Concurrency Tab
Locking a Harness or Slot when Running in Multi User Mode
Unlocking a Harness or Slot when Running in Multi User Mode

February 2016
Overview
Unlocked
Refreshing Harness Information with Changes from Other Users

You can switch between multi user and single user mode when using harness concurrency.
Procedure
1. Select Actions - Concurrency - Switch to Multi User Mode/Switch to Single User
Mode from the menu or click on the Concurrency tab to the left of the application
window.
2. In the Mode field, select either Multi User or Single User from the drop-down list. If
another user has a weak lock on the design that you have open, you cannot change to
Single User mode.
Related Topics
Harness Concurrency
Concurrency Tab
Unlocked
Selecting which Lockable Objects to View on the

Concurrency Tab
You can select which lockable objects to view on the Concurrency tab when using harness
concurrency.
Procedure
Click on the buttons that are situated below the table on the Concurrency tab .
The buttons represent harnesses, multi-harness slots (that is, slots connected to multiple
harnesses), single-harness slots (that is, a slot connected to a single harness) and multi-harness
connectors (that is, connectors connected to multiple harnesses. If the red stop sign is displayed
on a button, it means those objects are not currently displayed on the tab. If a red stop sign is not
displayed on a button, it means that the objects are already displayed on the tab.

February 2016
Overview
Related Topics
Harness Concurrency
Concurrency Tab
Unlocked
Locking a Harness or Slot when Running in Multi

User Mode
You can lock a harness or slot when running in multi user mode when using harness
concurrency.
Procedure
1. Do one of the following:
• Right-click on the harness or slot in the Diagram Window or Design Browser
(Design tab) and select Lock.
• Click on the harness or slot in the Diagram Window or Design Browser (Design
tab), press Space Bar and enter Lock.
• Ensure that the object you want to lock is listed on the Concurrency tab and click
the unlocked padlock symbol at the start of the table row for it.
2. If the object is listed on the Concurrency tab, the padlock symbol for the object changes
to a locked padlock to indicate that the object is locked. The name of the user holding
the lock is also displayed in the Locked By column for that object. Any other users
viewing the object on the Concurrency tab in another session will see a locked padlock
with an extra mark .
If you have locked a harness, the action also refreshes and locks all single-harness slots
on the harness.
If you have locked a slot connected to a single harness, the action also refreshes and
locks the harness attached to the slot.
If you have locked a slot connected to more than one harness, the action also refreshes
any harnesses directly connected to it.

February 2016
Overview
Related Topics
Harness Concurrency
Concurrency Tab
Unlocked
Unlocking a Harness or Slot when Running in Multi

User Mode
You can unlock a harness or slot when running in multi user mode when using harness
concurrency.
Note
You can unlock an object only if it is has been saved since it was last modified.
Procedure
• Right-click on the harness or slot in the Diagram Window or Design Browser
(Design tab) and select Unlock from the menu.
• Click on the harness or slot in the Diagram Window or Design Browser (Design tab)
, press Space Bar and enter Unlock.
• Ensure that the object you want to unlock is listed on the Concurrency tab and click
the locked padlock symbol at the start of the table row for it.
2. If the object is listed on the Concurrency tab, the padlock symbol for the object changes
to an unlocked padlock to indicate that the object is unlocked.
Related Topics
Harness Concurrency
Concurrency Tab

February 2016
Overview
Dimming (graying out) Slots and Harnesses that are Locked by Other Users or that Are Unlocked
Unlocked
Dimming (graying out) Slots and Harnesses that

are Locked by Other Users or that Are Unlocked
You can dim (gray out) slots and harnesses that are locked by other users or that are unlocked
when using harness concurrency.
You can dim (gray out) slots and harnesses in the design if they are locked by other users or are
unlocked. This helps you to see which objects are locked by you and are therefore editable in
the design. If you print out a design, any dimmed objects are printed normally.
Procedure
1. Ensure that the dimming functionality is enabled by clicking the Dim By Harness Lock
Status button at the bottom of the application window so that it has no red stop sign
displayed. If a red stop sign is displayed , no objects are dimmed in the design.
Alternatively, you can right-click on the Dim By Harness Lock Status button to
display two sliders and a Dim check box. Check the box to enable the dimming of
objects.
2. Display the sliders by right-clicking on the button. One slider is for unlocked objects
and the other is for objects locked by other users . Move the sliders down to dim out
objects and move the slider up to make objects clearer.
3. Click in the main application window to hide the sliders.
Related Topics
Harness Concurrency
Refreshing Harness Information with Changes from

Other Users
You can refresh harness information with changes from other users when using harness
concurrency.
Procedure
1. Select an unlocked object on the Concurrency tab and click the Refresh Harnesses
and Slots button next to the Mode field. You can select multiple objects. This
refreshes only the selected objects.
Or

February 2016
Overview
Metrics
2. Do no select anything and click the Refresh Harnesses and Slots button next to the
Mode field. This refreshes the entire design.
Or
3. Select an unlocked object in the diagram, press Space Bar and enter Refresh to refresh
the harness on which the object is located and any adjacent modified harnesses.
Related Topics
Harness Concurrency
Concurrency Tab
Metrics
The Metrics or Insight tab at the bottom left of the application window supplies metrics that can
be run against the open design.
For a full description of this functionality, see Capital Insight in the Capital Design Tools -
Common Functions User Guide.

February 2016
Overview
Metrics

February 2016
Chapter 2
Setting up Projects and Designs
This chapter contains details on how to create and edit a project and its designs. It also contains
details of how to run design rule checks on a design.
Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Editing the Attributes and Properties of a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Deleting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Deleting a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Saving the Designs in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Comparing Objects and Their Properties in Design Revisions . . . . . . . . . . . . . . . . . . . . . 69
Refreshing External Data for an Open Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Synchronizing Changes in Capital Logic Designs with the Capital Integrator Design . . . 70
Releasing a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Design Rule Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Running Design Rule Checks Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Running Design Rule Checks in the Design Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Design Rule Check Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

February 2016
Projects
Projects
A project is a container for all of the designs and data that comprise a specific product line.
The following sections explain how to open, create, edit and delete projects from within the
application:
Editing the Attributes and Properties of a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Deleting a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Opening a Project
You can open an existing project.
Procedure
See Opening a Project in the Capital Design Tools - Common Functions User Guide.
Related Topics
Creating a Project
Deleting a Project
Importing a Project
Exporting a Project
Closing a Project
Creating a Project
You can create a project from within the application. Once a project has been created, all
project-level data can be managed within Capital Project. Refer to the Capital Project User
Guide for more information.
Procedure
See Creating a Project in the Capital Design Tools - Common Functions User Guide.

February 2016
Editing the Attributes and Properties of a Project
Related Topics
Opening a Project
Deleting a Project
Importing a Project
Exporting a Project
Closing a Project

You can edit the attributes and properties of a project.
Procedure
1. Right-click on the project name in the Project Browser Window and select Edit. The
Edit Project Dialog Box is displayed.
2. Edit the attributes and properties as required. Click OK.
Related Topics
Creating a Project
Deleting a Project
Deleting a Project
You can delete a project from the database.
Caution
The deletion of a project cannot be undone without recourse to a database backup, which
may not be up-to-date.
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. The project is removed from the database.
Related Topics
Opening a Project

February 2016
Importing a Project
Creating a Project
Importing a Project
Exporting a Project
Closing a Project
Importing a Project
You can import an existing project (as a Project XML file) that has been exported from another
installation of Capital.
Procedure
See Importing a Project in the Capital Design Tools - Common Functions User Guide.
Related Topics
Opening a Project
Creating a Project
Deleting a Project
Exporting a Project
Closing a Project
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 etc.) that are contained in its original database record.
Note
Even if you do not have Capital Analysis installed, you must have the Analysis permission
assigned to your user account in Capital User if you want to import and export projects that
have Analysis project models attached to them.
Procedure
See Exporting a Project in the Capital Design Tools - Common Functions User Guide.
Related Topics
Opening a Project

February 2016
Closing a Project
Creating a Project
Deleting a Project
Importing a Project
Closing a Project
Closing a Project
You can close a project in the application.
Procedure
See Closing a Project in the Capital Design Tools - Common Functions User Guide.
Related Topics
Opening a Project
Creating a Project
Deleting a Project
Importing a Project
Exporting a Project
Applying Scopes to a Project or Design

You can apply scopes to a project or design.
If scopes are defined at project level and there are no design-level scope definitions, then 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.
Note
You can use extensibility (a plugin) to manage component scoping. If a plugin is available
then it will override the default rules, and will determine part suitability based on project,
design and library scoping but using the business logic defined within the plugin. 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.
Prerequisites
• The required scopes must have been created in Capital Library.

February 2016
Project Preferences
Procedure
1. Right-click on the project name or design in the Project Browser Window and select
Edit; the Edit Project Information dialog box or Edit Design dialog box is displayed.
2. Click Properties; an Edit Properties dialog box is displayed.
3. Click the Scopes tab; the scope codes that have been created in Capital Library are
displayed in the Available window.
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 window.
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
Tree, the applied scopes are displayed.
Project Preferences
Project preferences are default settings that you specify for the designs and diagrams in a
project.
You specify them in the Project Preference Dialog Box, accessed in the design applications by
pressing Space Bar and entering Project Preferences.
You can also edit them in Capital Project 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.

February 2016
Project Preferences
Note
Preferences can also be specified at the system level.
Related Topics
Project Preferences for Capital Integrator Designs
Project Preferences for Design Rule Checks
General Project Preferences Applicable to all Applications

February 2016
Designs
Designs
Designs are versionable data containers. Usually, one design is created for each sub-system of a
product line.
Deleting a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Saving the Designs in a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Comparing Objects and Their Properties in Design Revisions . . . . . . . . . . . . . . . . . . . . 69
Refreshing External Data for an Open Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Synchronizing Changes in Capital Logic Designs with the Capital Integrator Design. 70
Releasing a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Creating a New Design

You can create a new design for a project in Capital Integrator and then create diagrams for the
design.
Procedure
• Right-click on the project in the Project Browser and select New Integrator Design.
• Press Space Bar and enter New Integrator Design.
The New Integrator Design facility is displayed.
2. Specify the following for the design:
• Name - The name of the design. This field is mandatory. If valid names for the
designs have been created in Capital Project, 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 remove properties for the design.

February 2016
Creating a New Design
• Revision - The revision of the design. This field is mandatory.

• Short Description - A brief description for the design.
• Description - A detailed description for the design.
• Release Level - The release level of the design. Release levels are created in Capital
Project. See the Capital Project help system for more information on creating release
levels.
• Abstraction - The level of abstraction for the design. A level of abstraction is a user-
defined value that is assigned to a design and indicates what type of design it is. For
example, a top-level overview of a system could be labeled with a level of
abstraction System and a more detailed schematic of the same system could be
labeled with a level of abstraction Schematic. Levels of abstraction are created in
Capital Project. See the Capital Project help system for more information on creating
levels of abstraction.
• Domain - The domain of the design. See the Capital Project for more information
about domains.
• Option Expression - the option or option expression that you want to apply to the
whole design. You must enter this in the Option Expression field by clicking the
ellipsis (...) button to display the Edit Option Expression facility.
• Diagrams Details- Specify the details for the first diagram that you want to create
for this design.
• Template - If required, specify a template design that you want to use for the
diagram. If you select a design with multiple diagrams, the Name and Style Set
fields below this are disabled.
• Name - Specify the name of the diagram. If valid names for the diagrams have been
created in Capital Project, you can select a name by clicking the ellipsis button (...)
to display the Name Selection dialog box.
• Style Set - the style set that you want to apply to the diagram. See the Diagram
Styling User Guide for more information about style sets and how to edit them.
Note
You can click the Properties button to display the Edit Diagram Properties
dialog box that allows you to add or remove properties for the diagram.
3. Click the OK button.

Results
• A folder for the design is added to the Project Browser Window tree. Under the folder
for the design, the design revision is displayed. The diagram is displayed under the

February 2016
Importing a Design
design revision in the Project Browser Window tree and the diagram is opened in the
Diagram Window.
• If you selected a template design with multiple diagrams, the system creates diagrams
matching those and with the same names.
• If you select to create a diagram using a platform diagram as a template, the system
performs the following actions:
o It translates the following objects:
• Pathways become harnesses
• Components become slots
• Interfaces become virtual connectors
• Breaks become inlines
• Pathway branches become bundles
o It transfers the following information:
• Physical scale settings
• Graphical objects, such as text, shapes, comment symbols, images, borders and
skeletons
• Properties on all transferred objects and the design itself
• Attributes if they are common between the platform object and Capital Integrator
object (for example, Architectural Cost)
o It does not transfer the following information:
• Logical and functional design associations
• Rules and constraints
o It applies the selected style set.
Related Topics
Project Browser Window
Creating a Diagram
Importing a Design
You can import a designs from XML files into a project.

February 2016
Editing the Information for a Design
Procedure
See Importing Designs into a Project in the Capital Design Tools - Common Functions User
Guide.

If the necessary permissions have been set for your user account, you can edit the information
(such as design name, revision, abstraction) for a design.
If you use advanced naming functionality, design properties may be included in the naming
compositions that are set up in Capital Project. This means that the values that you specify for
design properties in this facility may influence the names that are generated. See the Capital
Project help system for more information about setting up naming compositions and see
“Advanced Naming Functionality” on page 284 for more information about applying advanced
naming to objects in Capital Logic.
Procedure
1. Right-click on 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 facility is displayed. You can edit the following properties for the
design:
• Name - the name of the design. If valid names for the object type have been created
in Capital Project, you can select a name by clicking the ellipsis button (...) to
display the Name Selection dialog box.
• Part Number (Capital HarnessXC design only) - a unique part number for the
design.
• Revision - the revision for the design.
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.
• Short Description - the short description for the design.

• Description - the long description for the design.
• Release Level - the release level for the design. Select the release level from the
drop-down list. The release levels that you can assign to the design depend on the
permissions that have been set for your user account in Capital User. See the Capital
User help system for more information about setting permissions for a user account.

February 2016
If the release level of a design is changed and saved in Capital HarnessXC, the
release level will be automatically be transferred when the design is opened in
Capital Harness & Factory.
The release levels will be mapped between Capital Harness & Factory and Capital
HarnessXC as follows:
Table 2-1. Release Level Mappings

H&F HarnessXC
Draft Draft
Pending Checking
Released Released
Obsolete Obsolete
• Abstraction - the abstraction level for the design.

• Domain - the domain for the design. See the Capital Project help system for more
information about domains.
• Applicable Options - 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.
• Option - the option or option expression that you want to apply to the whole design.
You must enter this in the Option Expression field by clicking the ellipsis (...)
button to display the Edit Option Expression facility.
• Style Set - the style set that you want to apply to the design. See the Diagram
Styling User Guide for more information about style sets and how to edit them.
• Sealing Requirements (displayed for Capital HarnessXC designs only) - Select the
sealing options for specific component types on the design.
• Seal Harness (displayed for Capital HarnessXC designs only) - 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.
• Seal Connectors (displayed for Capital HarnessXC designs only) - check this box if
you want all of the connectors inserted into the design to be sealed by default.
Optional.
• Plug Connectors (displayed for Capital HarnessXC designs only) - check this box if
you want all of the connectors inserted into the design to be plugged by default.
Optional.

February 2016
Deleting a Design
• Insulate Splices (displayed for Capital HarnessXC designs only) - check this box if
you want all of the splices inserted into the design to be insulated by default.
Optional.
3. Click the OK button to confirm the changes and to exit the facility.
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 facility is displayed automatically when you click the
OK button so that you can freeze them.
Deleting a Design
You can delete one or more designs from a project.
Note
The ability to delete a design may depend on its release level, and the allowable behaviors
assigned to that release level in Capital Project. Also, when working in a design application,
you can delete only designs that can be authored in that application.
Procedure
1. In the Project Browser Window, select one or more of the following:
• a design
The action will delete all revisions listed below the design.
• a design revision
The action will delete just the design revision.
• a design folder
The action will delete all designs, design revisions and folders contained within the
selected folder.
2. Right-click on a selected object and select Delete; a message asks you to confirm that
you want to delete the objects. When you delete a composite design, you have the option
of deleting both the composite and its derivatives or just the composite.
3. Click Yes.
Note
If a design cannot be deleted, an error message provides details of why it cannot be
deleted.

February 2016
Adding a Property to a Design
Adding a Property to a Design

You can add a property to a design when creating a new design or editing the information for a
design.
Procedure
See Adding a Property to a Design in the Capital Design Tools - Common Functions User
Guide.
Editing a Property for a Design

You can edit a property value for a design when editing the information for a design.
Procedure
See Editing a Property for a Design in the Capital Design Tools - Common Functions User
Guide.
Deleting a Property for a Design

You can delete a property for a design when editing the information for a design.
Procedure
See Deleting a Property for a Design in the Capital Design Tools - Common Functions User
Guide.
Saving the Designs in a Project

Pressing Space Bar and entering Save commits changes made in the current session to the
database. All of the designs that have been created for the open project are saved into it.
It can take a while for the project to be saved. You can continue to work on the project while the
data is being saved to the database. If you make any changes after you have entered Save, these
are not saved to the database until the next time you enter Save. If you attempt to close the
application before the data has been saved to the database, a warning message is displayed.
Whenever you attempt to close a diagram that has been amended since it was last saved in the
current session, you will be asked if you wish to save the changes.

February 2016
Comparing Objects and Their Properties in Design Revisions
Comparing Objects and Their Properties in Design

Revisions
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.
For example, you can compare a junction box wiring design that has been generated from a slot
in Capital Integrator or Capital Topology against a reusable junction box design.
Procedure
See Comparing Objects and Their Properties in Design Revisions or Build Lists in the Capital
Design Tools - Common Functions User Guide.
Refreshing External Data for an Open Design

The following options are available to refresh data that has been updated outside of the open
design in which are you working. All options are available by pressing Space Bar and entering
Refresh.
• Refresh All
Refreshes data for all of the items below:
o Symbol Libraries
Refreshes symbol library data when it has been modified in Capital Symbol.
o Options & Variants
Refreshes option and variant data for a design when they have been modified in
other Capital applications.
o Shared Objects
Refreshes shared object data for a design when it has been modified in other Capital
applications.
o Designs
Refreshes design data for the design in which you are working when it has been
modified in other Capital applications.
o Library Parts
Refreshes cached library part data when it has been modified in Capital Library.
o Cross References

February 2016
Synchronizing Changes in Capital Logic Designs with the Capital Integrator Design
Refreshes cross-reference data when it has been modified in other Capital

applications.
o Synchronize Logical Changes
Refreshes design data relating to associated Capital Logic designs when it has been
modified in Capital Logic.
Synchronizing Changes in Capital Logic Designs

with the Capital Integrator Design
If you make changes in an associated Capital Logic design after opening the Capital Integrator
diagram, you can update the Capital Integrator design with these changes.
This action refreshes the Logical Designs Browser (Function tab) in Capital Integrator.
For example, if a device has been deleted in Capital Logic, synchronizing the changes will
delete the device in Capital Integrator.
Caution
You can synchronize changes in an associated Capital Logic design only when you run
Capital Integrator in single user mode.
Procedure
1. Press Space Bar and enter Synchronize Logical Changes.
2. The Sync tab in the Output Window displays the status of the synchronization and
details any changes made in Capital Integrator. When the synchronization is complete,
the Logical Designs Browser (Function tab) is updated with the changes from the
Capital Logic design.
Results
If the synchronization finds a change to a net or device that means the object is now obsolete,
the device/signal or its wiring is not removed from the Capital Integrator design but the Sync
tab indicates that it cannot remove the signal/device:
• If the system finds a change to a net that now has wiring, the signal is not removed from
the design.
• If the system finds a change to a net that has not yet got wiring generated, the signal is
removed from the design and a message is displayed on the Sync tab.
• If the systems finds a change to a device that is now placed, the device is not removed
from the design.
• If the system finds a change to a device that is not placed, the device is removed from
the design and a message is displayed on the Sync tab.

February 2016
Managing Design Changes When Synchronizing Designs
Related Topics
Output Window
Managing Design Changes When Synchronizing

Designs
When synchronizing design changes between designs in different applications, you can
configure preferences for the data synchronization.
For example, if a wire has changed size in a Capital Logic design, you may want to synchronize
this data in a Capital HarnessXC design. However, you may not want to synchronize the wire
color if Capital HarnessXC is used as the master application for specifying wire colors.
These preferences can be set by using the Design Change Policy Manager functionality in
Capital Project. See the Capital Project help system for more information.
Releasing a Design
You can release designs and enforce the running of particular design rule checks when doing so.
This action is available for designs created in Capital Logic, Capital Topology, Capital
Integrator, Capital HarnessXC and Capital ModularXC.
See Releasing Designs with Enforced Design Rule Checks in the Capital Design Tools -

February 2016
Design Rule Checks
Design Rule Checks

Design rule checks ensure connectivity and consistency across a design and diagram by
identifying errors. Checks can be run independently of any other activity or as part of releasing
a design. The severity and frequency of the checks are set in your project preferences.
Checks can be run on a single design or a build list, and can be turned off if needed.
Releasing a design will automatically run checks and a design will not be released by the system
if there are any errors.

Running Design Rule Checks Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Running Design Rule Checks in the Design Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Design Rule Check Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Running Design Rule Checks in Background

You can run design rule checks 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.
For a full list and descriptions of the project preferences related to design rule checks, see the
following section of the General Preferences for Design Rule Checks section of the Project
Preferences Dialog Box topic in the Capital Designs Tools - Common Functions User Guide.
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 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 Output Window and Design Rule Checks toggle
update dynamically to reflect the latest results.

February 2016
Running Design Rule Checks Manually
Related Topics
Design Rule Checks
Running Design Rule Checks in the Design Assistant
Design Rule Check Descriptions
Status Bar
Output Window

You can manually run design rule checks to identify errors in designs.
Procedure
See Running Design Rule Checks in the Capital Design Tools - Common Functions User
Guide.
Related Topics
Design Rule Checks
Running Design Rule Checks in the Design Assistant
Running Design Rule Checks in the Design

Assistant
You can use the Design Assistant to run design rule checks to identify errors in designs.
Prerequisites
• The Design Assistant must have been made visible by pressing Space Bar and entering
Assistant.
• The checks that you want to run in the Design Assistant must have been specified in the
project preferences. See “Project Preferences” on page 60.
Procedure
1. Select the toggle Include Design Assistant DRCs ( ) in the Design Assistant.
2. Click the Run Checks ( ) button in the Design Assistant; the results of the checks are
displayed in the Design Assistant Output Table.

February 2016
Related Topics
Design Assistant
Design Rule Checks

You can use the Design Rule Checks facility to check for specific errors in designs. You can
check a single Capital Logic design, a single Capital Integrator design or all of the Capital Logic
designs in a build list.
If you are using Web Services with your Capital applications, you can release a Capital Logic or
Capital Integrator 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.
For a full list of the design rule checks available for use in Capital Integrator, seeDesign Rule
Checks Applicable to Capital Integrator Designs in the Capital Design Tools - Common
Functions User Guide.
Related Topics
Design Rule Checks

February 2016
Chapter 3
Setting up Diagrams
This chapter contains details of how to create diagrams (not diagram content).
This chapter also details of how to control the display of diagrams.
Working with Multiple Diagrams Overview Video . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Creating a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Editing the Name of a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Specifying the Style Set Applied to the Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Adding a Property to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Deleting a Property from a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Specifying the Physical Scale of a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Changing the Background Color of a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Adding a Skeleton Graphic to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Removing a Skeleton from a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Working with Multiple Diagrams Overview

Video
A design in Capital Integrator can have multiple diagrams.
For an overview of working with multiple diagrams see the video Multiple Diagrams Overview.
It includes examples of:
• Slicing bundles and slots

• Creating multiple instances of a dangling bundle
• Moving objects between diagrams
• Navigating between instances of an object
• Viewing signals that go across split bundles
• Using harness synchronization on a design with multiple harness instances

February 2016
Setting up Diagrams
Creating a Diagram
Creating a Diagram
You can create a new diagram in a design. Multiple diagrams can be created for a design.
Procedure
1. Either:
• Select an Integrator design in the Project Browser Window, press Space Bar and
enter ‘New > New Integrator Plane’.
• Right-click on an Integrator design in the Project Browser Window and select New
Integrator Diagram.
The New Integrator Diagram Dialog Box is displayed.
2. Specify the name of the diagram and click OK; the diagram is created and placed
beneath the design to which it belongs in the Project Browser Window.
Related Topics
Editing the Name of a Diagram
Specifying the Style Set Applied to the Diagram
Adding a Property to a Diagram
Deleting a Property from a Diagram

You can edit the name of a diagram.
Procedure
1. Right-click on the diagram in the Project Browser Window and select Edit; the Edit
Diagram Dialog Box is displayed.
2. Specify the Name and click OK; the name changes in the Project Browser Window.
Related Topics
Creating a Diagram

February 2016
Setting up Diagrams
Specifying the Style Set Applied to the

Diagram
You can specify the style set applied to a diagram.
Procedure
2. Specify the Style Set and click OK.
Related Topics
Creating a Diagram

You can add a property to a diagram.
Procedure
2. Click New below the Properties Table, the New Property Dialog Box is dialog box.
3. Enter the property name or select an existing property name and click OK; the property
is added to the table.
4. Specify the Value and Type for the property and click OK.
Related Topics
Creating a Diagram

February 2016
Setting up Diagrams

You can delete a property from a diagram.
Procedure
2. Select the property in the Properties Table and click Delete; the property is removed
from the table.
Related Topics
Creating a Diagram
Specifying the Physical Scale of a Diagram

You can specify the physical scale of a diagram.
The default lengths of the bundles as drawn in an Integrator diagram are based on the physical
scale of the diagram. The physical scale is the distance between grid points which is used for
calculating bundle lengths in the diagram.
The physical scale does not effect the size of the diagram when it is printed. You must set the
Project Preferences to specify the scale for a printout of the diagram.
A skeleton graphic has a certain size but this size will not change even if the physical scale is
changed - only the number of grid points that fit within the skeleton will vary.
Procedure
1. Open the diagram, press Space Bar and enter Physical Scale; the Edit Physical Scale
2. Specify the Physical Scale (that is, the length between the points of the grid that is
visible on the diagram), the unit of measurement and click OK.
Note
You can use the Set Grid Defaults facility to specify how the grid is displayed on
the diagram. See “Setting Grid Defaults for a Diagram” on page 549.

February 2016
Setting up Diagrams
Changing the Background Color of a Diagram
Changing the Background Color of a Diagram

For ease of visibility, Capital Integrator supports toggling of the background color in the
diagram window between black and white.
Procedure
Press Space Bar and enter Invert Colors to select either white or black backgrounds for
diagrams.
Note
The background color change only affects on-screen viewing; printing a diagram is
always executed with a white background.
Adding a Skeleton Graphic to a Diagram

You can add a skeleton graphic to a diagram.
The functionality for creating borders in Capital Symbol also enables you to create skeleton
graphics that can be added to a diagram in Capital Integrator. The skeleton is created and saved
as a border. The skeleton graphic uses the physical scale that has been set for the diagram and
not the pin spacing scale that is set in Project Preferences. See “Specifying the Physical Scale of
a Diagram” on page 78 for more information.
Prerequisites
• The skeleton graphic must have been created in Capital Symbol.
Procedure
1. With the diagram open, press Space Bar and enter Skeleton; the Edit Skeleton Dialog
Box is displayed.
2. Navigate to the skeleton graphic that you want to use and select it.
3. Click OK; the skeleton is added to the diagram.
Related Topics
Removing a Skeleton from a Diagram

You can remove a skeleton graphic from a diagram.

February 2016
Setting up Diagrams
Procedure
1. With the diagram open, press Space Bar and enter Skeleton; the Edit Skeleton Dialog
Box is displayed.
2. Select [No Skeleton] in the Skeleton Browser.
3. Click OK; the skeleton is removed from the diagram.
Related Topics

February 2016
Chapter 4
Editing Diagram Objects
This chapter contains details of how to perform various generic editing actions.
Undoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Redoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Repeating an Action. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Cutting and Pasting an Object in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Copying and Pasting an Object in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Copying an Object from Diagram to Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Moving Objects from a Diagram to Another Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Deleting an Object in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Selecting Objects in a Diagram Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Selecting All Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Finding and Selecting Objects by Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Finding and Selecting Objects by Attribute or Property . . . . . . . . . . . . . . . . . . . . . . . . . 87
Selecting the Parent Object of an Object in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Specifying the Highlight Color of Selected Objects in a Diagram . . . . . . . . . . . . . . . . . 87
Moving Objects in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Using the Stroke Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Filtering the Objects Displayed in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Locating the Source Functional Object for a Physical Object . . . . . . . . . . . . . . . . . . . . 90
Slice Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Window Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Moving Browser Windows Around the Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Zooming In and Out of Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Panning Across a Diagram Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
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.

February 2016
Redoing an Action
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.
Redoing an Action
You can use the redo facility to 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.
Procedure
1. Press Space Bar and enter Redo.
2. The previously undone action is redone.
Repeating an Action
You can repeat an action. If there are no undone actions that can be redone, the Edit menu
includes an option to repeat the last action that was performed.
Procedure
1. Press Space Bar and enter Repeat.
2. The application is put in the correct mode to repeat the last action performed.
Cutting and Pasting an Object in a Diagram

You can cut and paste an object in a diagram.
Procedure
1. Select the object.
2. Either:
• Press Space Bar and enter Cut
• Right-click on the selected entity and select Cut
The object is cut from the diagram and pasted to the clipboard.
3. Press Space Bar and enter Paste.

February 2016
Copying and Pasting an Object in a Diagram
4. Click where you want to place the entity.
Copying and Pasting an Object in a Diagram

You can copy and paste an object in a diagram.
Procedure
2. Either:
• Press Space Bar and enter Copy
• Right-click on the selected entity and select Copy
3. Press Space Bar and enter Paste.
A copy of the object is added to the diagram near the original object.
4. Drag the copy to the location where you want to paste it.
Note
If you attempt to undo this action, you will clear the clipboard only.
Copying an Object from Diagram to Diagram

In Capital Integrator, you can copy topology objects and comment graphics from one
topological diagram to another. You cannot copy wiring. As a result, you cannot copy
placement data. If a default name has been overridden on an object in Capital Integrator, the
new name is preserved when the object is copied.
Procedure
1. Select the objects that you want to copy in the diagram window, press Space Bar and
enter Copy, or right-click on the selection and select Copy from the pop-up menu.
Alternatively, you can use the key combination CTRL + C.
2. Open the other diagram and either right-click on the diagram window and select the
Paste menu option from the pop-up menu or click on the diagram window, press Space
Bar and enter Paste. Alternatively, you can use the key combination CTRL + V. If you
do any of these, the copies of the objects are given unique names.
In addition, you can use the key combination CTRL + SHIFT + V. If you do this, the
copies of the objects retain the same names as the original objects.

February 2016
Moving Objects from a Diagram to Another Diagram
In Capital Integrator, the following objects can be copied and pasted:

• Slot - When a slot is copied, slot connectors, holes and physical devices are also
copied.
• Bundle
• Bundle region - Regions cannot be copied partially or by themselves. If you select
enough bundle segments to cover the entire region (or the entire bundle), the region
will be copied.
• Slot connector and hole - These cannot be copied on their own but are copied with
slots. The cavities of a slot connector are copied only if the connector has a part
number. Connector refinement data is not copied. Harness-side connectors are
copied when their connected bundles and the slot are copied. Slot device connectors
are copied with a slot connector.
• Inline connector - If you select one half of an inline pair, both halves will be copied.
If the inline has no part number, no cavities are copied. If either half has a part
number, the cavities are copied. Harness-side connectors are copied when their
connected bundles and the inline connector are copied.
• Interface connector
• Node - Nodes cannot be copied independently. They are only copied with a bundle.
Reference nodes are ignored.
• Text
• Graphics
Any connections or relationships between two objects are copied only if both objects are
copied (for example, a pin and a wire). No relationships are created between new and
old objects when objects are pasted.
3. 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.
Moving Objects from a Diagram to Another

Diagram
It is possible to move objects from one diagram to another diagram within a design.
Procedure
See Moving Objects from a Diagram to Another Diagram in the Capital Design Tools -

February 2016
Deleting an Object in a Diagram
Deleting an Object in a Diagram

You can delete an object in a diagram.
Procedure
• Press Space Bar and enter Delete
• Right-click on the selected entity and select Delete
• Click the Delete key on your keyboard
The object is deleted.
Selecting Objects in a Diagram Window

You can select multiple objects in a diagram window by holding down the right-mouse key and
dragging the mouse cursor to form a box around the objects that you want to select. When you
click the mouse to position the opposite corner of the box, the box disappears and all objects
within the area of the box are selected.
If you want to select objects of only one or more particular types, you must click on one
instance of each type of object that you want to select and hold down the SHIFT key on your
keyboard while dragging the mouse to form the box around the area in which you want to select
the objects.
For example:
You have the following design.
To select only the name text in the design, you click on one instance of name text and then hold
down the SHIFT key on your keyboard and drag the mouse cursor to form a box around the
design.

February 2016
Selecting All Objects in a Diagram
When you click to place the opposite corner of the box, the box disappears and the name text in
the diagram is selected:
Selecting All Objects in a Diagram

You can select all objects in a diagram so that you can perform an action on all of them at once.
Procedure
1. Press Space Bar and enter Select All.
All of the objects on the diagram are highlighted.
2. Perform the required action.
Finding and Selecting Objects by Name

You can search for an object in a diagram by using its name.

February 2016
Finding and Selecting Objects by Attribute or Property
Procedure
See Finding and Selecting Objects by Name in the Capital Design Tools - Common Functions
User Guide.
Finding and Selecting Objects by Attribute or

Property
You can search for an object in a diagram by using a value for a particular attribute or property.
Procedure
See Finding and Selecting Objects by Attribute or Property in the Capital Design Tools -
Selecting the Parent Object of an Object in a

Diagram
You can select the parent object of an object (for example, the slot on which a pin is located) by
selecting the child object (for example, the pin), pressing Space Bar and entering Extend
Selection.
The parent object (for example, the slot) is then highlighted in red.
Specifying the Highlight Color of Selected

Objects in a Diagram
You can select (specify) the color used to display (highlight) selected objects in a diagram.
Procedure
1. Press Space Bar and enter Selection Color; the Select Color dialog box is displayed.
2. Select the color that you want the system to use when highlighting selected objects in a
diagram and click OK.
Note
The color that you have selected will also be used in other sessions of Capital design
tools when you start them.
Moving Objects in a Diagram

You can move objects within a diagram.

February 2016
Using the Stroke Tool
Procedure
1. Select one or more objects.
2. Either:
• Drag the objects using the mouse
• Hold Shift and use the arrow keys on your keyboard to move the objects by:
o One pin grid point, if one or more selected objects have pins
o One Drawing Grid point if no selected objects have pins
• Hold Ctrl and use the arrow keys on your keyboard to move the objects by:
o One Major Grid Interval if one or more selected objects have pins
o Approximately half of a pin grid point if no selected objects have pins. Note that
when there are less than two Drawing Grid points per pin grid point, objects with
no pins will move a great distance.
Using the Stroke Tool

You can use the stroke tool to perform various actions by moving the mouse.
Note
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.
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.

February 2016
Filtering the Objects Displayed in a Diagram
The following stroke actions are available:
Table 4-1. Stroke Actions

Stroke Action Grid Path
Zoom Area 159
Zoom All 951
Zoom in by 20% 357
Zoom out by 20% 753
Delete 741236987
Undo 1478963
Redo 7412369
Add bundle 258

The Capital Integrator Design Filter dialog box enables you to filter the graphical topology in a
diagram.
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
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.

February 2016
Locating the Source Functional Object for a Physical Object
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. 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 will be 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 Integrator diagram.
2. Press Space Bar and enter Filter platform design.
The Capital Integrator design Filter Dialog Box is displayed.
3. Select one of the Filter options and click OK.
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.
Locating the Source Functional Object for a

Physical Object
When working on a Capital Integrator diagram in Capital Design, you can locate a functional
object in a Capital Logic diagram that is the source for a particular physical object in the Capital
Integrator diagram. This functionality opens the appropriate Capital Logic diagram
automatically and highlights the functional object in that diagram.

February 2016
Slice Objects
You can locate the source for the following objects:
• Devices placed in a slot (listed under the slot on the Design tab)
• Devices not placed in a slot (listed on the Function tab)
• Signals (listed on the Design tab or on the Function tab)
• Multicores (listed under harnesses on the Design tab)
• Cavities on a slot connector, but not on an inline pair (listed on the Design tab)
• Wires (listed under harnesses on the Design tab)
Procedure
1. With the Capital Integrator diagram open in Capital Design, click on the physical object,
press Space Bar and enter Show Functional Source. Alternatively, right-click on the
object and select the Show Functional Source option from the pop-up menu.
2. If there is only one functional object that is represented by the selected physical object,
the Capital Logic design and its diagram are opened and the functional object is
highlighted. If the Capital Logic diagram is already open, it is brought to the front of the
diagram window.
If there is more than one functional object that is represented by the selected physical
object, the Show Functional Source dialog box is displayed. It lists the functional
objects and the functional designs where they are located. You must select the functional
object that you want to locate and click the OK button. The Capital Logic design and
diagram are opened and the functional object is highlighted.
Slice Objects
Certain objects on diagrams can be sliced, simplifying diagram modifications and making
diagams easier to understand.
The Slice functionality allows you to draw an intersection line across an applicable object, to
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.
• Slots and bundles can be sliced.

• Slices can be vertical or horizontal.
See Slice Objects in the Capital Design Tools - Common Functions User Guide for full details.

February 2016
Window Controls
Window Controls
You can 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.
Moving Browser Windows Around the Screen. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Zooming In and Out of Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Panning Across a Diagram Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Arranging Diagram Windows for Viewing

You can use the window controls to arrange open diagram windows for viewing purposes. The
window controls are available from the Windows menu.
• New
Creates a copy of the active window and its contents. Any changes made in the copy are
also made in the original. This is useful for viewing smaller sections of large diagrams.
• Cascade
Rearranges and resizes the open diagram windows in a staggered fashion, allowing
selection and viewing of a window by clicking on it once.
• Tile Horizontal
Rearranges and resizes the open diagram windows so that they are aligned horizontally.
• Tile Vertical
Rearranges and resizes the open diagram windows so that they are aligned vertically.
• Tabbed Mode
Resizes each diagram to occupy the entire display area, but adds a row of tabs at the
bottom of the display area to switch between open diagrams.
Moving Browser Windows Around the Screen

You can display browser windows in separate windows that you can move around your screen.
Any browser windows and tabs that are displayed at the bottom left of the application window
can be dragged away from that position so that they are displayed in their own separate
windows.

February 2016
Zooming In and Out of Diagrams
Procedure
1. Click on 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.
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.
Zooming In and Out of Diagrams

You can use the zoom controls to zoom in and out of diagram windows.
• Zoom In
Increases the scale of the diagram so that objects appear larger.
Press Space Bar and enter Zoom In.
• Zoom Out
Decreases the scale of the diagram so that objects appear smaller.
Press Space Bar and enter Zoom Out.
• Zoom Selected
Zooms in on the objects that you have selected in the diagram.
Select the objects and do one of the following:
o Press Space Bar and enter Zoom Selected
o Right-click on the diagram and select Zoom Selected
• Zoom Area
Zooms in on a specified area of a diagram.
Press Space Bar and enter Zoom Area.
The cursor changes to . Click once on 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.
Do one of the following:
o Press Space Bar and enter Zoom All

February 2016
Panning Across a Diagram Window
o Right-click on the diagram and select Zoom All

• Zoom
Allows you to zoom in or out by moving your mouse.
o Press Space Bar and enter Zoom
o Right-click on the diagram and select Zoom
To zoom out, move your mouse forwards or to the left. To zoom in, move your mouse,
backwards or to the right. Press the Esc key on your keyboard to turn off the zoom
mode.
Panning Across a Diagram Window

You can pan across a diagram window.
Procedure
• Press Space Bar and enter Pan
• Right-click on the diagram and select Pan
2. The cursor changes to . Hold down the left mouse key and drag the cursor across the
diagram to pan. The diagram moves as you drag the cursor.

February 2016
Chapter 5
Creating Slots
This chapter includes details of how to create slots in diagrams.

Slot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Creating an Empty Slot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Resizing a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Specifying a Slot Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Creating Multiple Slot Instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

February 2016
Creating Slots
Slot
Slot
Slots represent the location of electrical equipment within the electrical wiring system. At the
most basic level, a slot is a connection point to the harness system. A slot is also referred to as a
component. Electrical devices, as defined in the Capital Logic diagrams, can be placed into slots
to define connectivity for the slot prior to automated wire synthesis.
Slots are connected together by bundles and there must be a slot connector wherever a bundle
connects to a slot.
You can either create an empty slot and place a device in it later or you can create a slot for a
specific device (this action creates the slot and places the device in one step).
You can specify different types of slots:
• Equipment - this indicates that the slot will contain normal devices
• Ground - this indicates that the slot will contain ground devices.
• Junction Box - this indicates that signals can be routed through this slot.
The icon for the slot in the Design Browser (Design tab) indicates the slot type:
• Equipment slot
• Ground slot
• Junction box slot
For a ground slot, a symbol is added to the center of the slot in the diagram:
For a junction box slot, a symbol is added to the center of the slot in the diagram:
Creating an Empty Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Resizing a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
Specifying a Slot Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

February 2016
Creating Slots
Creating an Empty Slot
Creating Multiple Slot Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

You can create an empty slot in a diagram, into which you will place a device later.
Procedure
1. Press Space Bar and enter Add Slot, Add Ground Slot or Add Junction Box.
2. Position the mouse cursor over a grid point where you want to place one corner of
the slot.
3. Drag the mouse away to place the opposite corner of the slot. A gray rectangle is
displayed. Drag the mouse until the rectangle is the size that you want the slot to be and
click the grid point where you want to place the opposite corner.
Results
• The line color changes and the slot is added to the list in the Design Browser (Design
tab).
• When you create a slot in a diagram, it has the following constraint by default:
Do place devices with property matching Object Name = Ruled Object Name
When devices are placed in slots automatically later, this constraint specifies that any devices
with the same Object Name as the slot will be placed in that slot. You can edit or remove this
constraint for a slot as required.
See “Overview of Rules and Constraints” on page 287 for more information about constraints
and “Placement of a Device or Ground Device in a Slot” on page 174 for more information
about placing devices.
Note
You can change the slot from a ground slot to an equipment or junction box slot and vice
versa.
Related Topics
Creating a Slot for a Specific Device

February 2016
Creating Slots

You can create a slot for a specific device. This action creates a slot and places the selected
device in one step.
Note
Alternatively, you can create a slot and place a device at a later stage (see “Creating an
Empty Slot” on page 97 and “Placement of a Device or Ground Device in a Slot” on
page 174).
Procedure
1. In the Logical Designs Browser (Function tab), either double-click on the device or
right-click on it and select Create Slot from the popup menu.
2. If the device has not been placed in the design before, skip to step 4.
If the device has been placed in a slot before but was assigned an option expression, a
message asks you whether you want to place it again. Click Yes to continue.
3. This instance of the device must be assigned an option expression. The Edit Option
Expression dialog box is displayed. Specify the option expression for this instance and
click the OK button to exit the dialog box.
4. In the diagram, position the mouse cursor over a grid point where you want to place
one corner of the slot.
5. Drag the mouse away to place the opposite corner of the slot. A gray rectangle is
displayed. Drag the mouse until the rectangle is the size that you want the slot to be and
click the grid point where you want to place the opposite corner.
Results
• The line color changes and the slot is added to the list in the Design Browser (Design
tab).
• The device is placed in the slot automatically.
• The slot is named after the device.
Related Topics
Design Browser (Design Tab)

February 2016
Creating Slots
Resizing a Slot
Resizing a Slot
You can resize a slot.
Procedure
1. Click on the slot in the diagram window.
2. A square is displayed at each corner of the slot. Position your cursor over the corner that
you want to move so that the stretch symbol is displayed.
3. Hold down the right mouse key, drag the corner to the new position where you want to
place it and release the right mouse key.
Specifying a Slot Type

You can specify a slot type.
Procedure
1. Right-click on the slot in the diagram or Design Browser (Design tab) and select
Properties; the Edit Properties Dialog Box is displayed.
2. In the Slot Type field, select the type from the drop-down list:
• Equipment - this indicates that the slot will contain normal devices
• Ground - this indicates that the slot will contain ground devices.
• Junction Box - this indicates that signals can be routed through this slot.
3. Click OK.
Results
• The icon for the slot in the Design Browser (Design tab) changes accordingly:
o Equipment slot
o Ground slot
o Junction box slot
• For a ground slot, a symbol is added to the center of the slot in the diagram:

February 2016
Creating Slots
Overview of Junction Box Slots
• For a junction box slot, a symbol is added to the center of the slot in the diagram:
Overview of Junction Box Slots

Junction boxes are used to implement internal connections and to join several harnesses.
A junction box slot is indicated by a junction box icon in the Design Browser (Design tab).
You can use the Edit Properties facility for a slot to set it as a junction box slot (see
“Specifying a Slot Type” on page 99) or you can add a junction box slot to a diagram (see
“Creating an Empty Slot” on page 97).
When signals are routed generally, they always terminate on a slot or in a slot. Signals cannot be
routed through an equipment slot or a ground slot.
However, a signal can be routed through a junction box slot. You can use the Route by
Attribute/Property rules on a junction box slot to specify which signals can be routed through
it and which signals cannot be routed through it. (See “Overview of Rules and Constraints” on
page 287). If you do not specify any rules on a junction box slot, all signals can be routed
through it.
Note
During synthesis, the signal map on a junction box slot is typically altered to allow signals
to route through the slot.
When wiring is synthesized, signals are connected inside a slot in the same way as a splice that
is dragged into a slot. This means that the internal connection will be modeled as a multiple
termination to a slot-device pin inside the slot.
When a signal is routed through a junction box slot, one wire will carry it into the slot and
another wire will carry it out of the slot. Note that signals are able to pass through a junction box
slot even if no device is placed in it.
Footprints work on a junction box slot in the same way as they work on other slots.
Creating Multiple Slot Instances

You can create multiple instances of a single slot so that it is represented in different places in
one or more diagrams. A slot with multiple instances can be referred to as a split slot.

February 2016
Creating Slots
Video
For an overview of working with multiple diagrams, including creating multiple slot
instances, see the video Multiple Diagrams Overview.
Prerequisites
• At lease one instance of the slot must exist.
Procedure
Perform one of the following procedures:

Split or slice an existing slot See Slicing a Slot in the Capital Design Tools -
instance in a diagram Common Functions User Guide.
Create a new instance of a 1. Right-click on the slot in the Design Browser
slot using the context menu (Design tab) and select Create Slot Instance;
(on the same diagram or the cursor changes as for the ‘Create Slot’
another) action.
2. Draw the new instance of the slot.
Create a new instance of a 1. Drag the slot name from the Design Browser
slot using drag and drop (on (Design tab) to the diagram canvas; the
the same diagram or cursor changes as for the ‘Create Slot’ action.
another) 2. Draw the new instance of the slot.
Results
The new instance is created in the diagram.
In the Design Browser (Design tab), an Instances folder displays under the slot and lists the
instances of the slot with the name of the diagram containing that instance. The connectors on
an instance are listed below it.
You can use styling to control whether and how cross-reference text is displayed at a slot with
multiple instances. You apply this styling to the slot object in your style set. See Adding a
Cross-Reference Text Decoration in the Capital Diagram Styling User Guide.

February 2016
Creating Slots

February 2016
Chapter 6
Creating Bundles and Harnesses
This chapter includes details of how to create bundles and harnesses in diagrams.
Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Creating a Bundle in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Deleting a Bundle from a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Creating Multiple Bundle Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Specifying the Physical Length of a Bundle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Specifying Variant Physical Lengths for a Bundle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Splitting a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Multiple Harnesses at Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Bundle Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Defining a Bundle Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Deleting a Bundle Region. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Using the Adjust Bundle Region Menu Option to Move a Bundle Region Node . . . . . . . 124
Editing the Offsets of a Bundle Region from the Bundle Ends . . . . . . . . . . . . . . . . . . . . . 125
Through Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Creating a Through Node on a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Deleting a Through Node from a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Converting Through Nodes from Structure Nodes to Reference Nodes . . . . . . . . . . . . . . 128
Integrator Harness Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Exporting a Harness from a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Exporting Multiple Harnesses from a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Importing Modified Data for an Existing Harness in a Design . . . . . . . . . . . . . . . . . . . . 133
Importing the Data for a New Harness into a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Importing the Data for a New Harness into a Design and Mating a Connector . . . . . . 135

February 2016
Bundle
Bundle
A bundle is used in Capital Integrator to join together slots and represents an available wire
routing path within the electrical system. After you have associated the topological design with
a Capital Logic design, signals from the Capital Logic design are routed along these bundles
and wiring is synthesized. There must be a slot connector wherever a bundle connects to a slot.
Bundle Segment
When a bundle has turning points, each straight section is a bundle segment. For example, the
following bundle has three bundle segments:
You can also divide a bundle into bundle regions and add rules or properties to the individual
regions. This may be desirable if you want to impose different conditions on different parts of a
bundle. A bundle region is different to a bundle segment. A bundle segment is a graphical object
only whereas a bundle region is a connectivity object. A bundle region can be represented by a
set of sequential bundle segments. See “Bundle Region” on page 121 for more information.
Bundles connect together to form a Harness.
Related Topics
Creating a Bundle in a Diagram
Moving a Bundle in a Diagram
Deleting a Bundle from a Diagram
Specifying the Physical Length of a Bundle
Specifying Variant Physical Lengths for a Bundle
Harness
Bundle Region

February 2016
Harness
Harness
Bundles connect together to form a harness. When you add an unconnected bundle to a diagram
a harness is added to the Design Browser (Design tab). The bundle is displayed below it in a
Bundles folder.
For example:
In the diagram:
In the Design Browser:
When you connect another bundle to it, the original bundle BUN2 is split into two bundles and
the new bundles are added below the harness in the Design Browser:
Creating a Bundle in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Deleting a Bundle from a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Creating Multiple Bundle Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Specifying the Physical Length of a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Specifying Variant Physical Lengths for a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

February 2016

Splitting a Harness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

You can create a bundle in a diagram.
Procedure
1. Press Space Bar and enter Bundle.
2. Position the mouse cursor over a grid point where you want to place one end of the
bundle.
You can define sections in the bundle by clicking once to place a segment end-point and
then continuing to drag the line.
3. You can connect a bundle to a slot or another bundle. To place the end-point of the
bundle, double-click on the location where you want the bundle to end. Alternatively,
left-click once with the mouse on the location and then right-click to display a pop-up
menu and select Commit.
Results
• The line color changes and the bundle is added to the list in the Design Browser (Design
tab).
• Bundles that are connected together form a harness and these bundles are listed under
the harness in the Design Browser (Design tab).
• A single bundle that is not connected to any other harnesses will be listed under a
harness by itself.
• When you connect bundles from two separate harnesses together, the harnesses merge to
form one harness in the diagram and in the Design Browser (Design tab).
• If you connect bundles together in such a way that it forms a loop, a through node is
created on the last bundle that you create in the loop. A Through Node is green, whereas
other nodes are blue. You can manually add through nodes to bundles. See “Creating a
Through Node on a Bundle” on page 127 for more information on through nodes.
• If you connect a bundle to a slot, a slot connector is created automatically where the
bundle and slot connect. The slot connector is displayed as a gray square on the diagram.
• You can connect further bundles from different harnesses to the same connector without
the harnesses merging. See “Multiple Harnesses at Connectors” on page 115 for more
information.

February 2016
• When you have finished creating the bundles that make up a harness. You can specify
the name for the harness by using the Properties dialog box. See “Specifying the Name
of an Object in a Design or Diagram” on page 271 for more information about
specifying the name.
Related Topics

You can move a bundle in a diagram.
Procedure
1. Click on the bundle that you want to move.
2. The bundle changes color and its name is highlighted in the Design Browser (Design
tab).
You can move or stretch a bundle.
To move a section, click on the line and drag and drop it to a new location. The four-way
move symbol ( ) is displayed while you do this. Connected bundles move to maintain
the connectivity. You can disconnect the section from an inline pair by right-clicking on
the end-point square where the connection is to display a pop-up menu and selecting
Disconnect Selected.
To stretch a section, click on an end-point or grip point and drag and drop it to a new
location. The two-way stretch symbol is displayed while you do this. Connected objects
move to maintain connectivity.
Related Topics

You can delete a bundle from a diagram.

February 2016
Creating Multiple Bundle Instances
Procedure
1. Right-click on the bundle in the lower browse box on the left side of the screen to
display a pop-up menu and select Delete.
2. Alternatively, right-click on the bundle in the diagram to display a pop-up menu and
select Delete to delete the bundle.
Related Topics
Creating Multiple Bundle Instances

You can create multiple instances of a single bundle so that it is represented in different places
in one or more diagrams. A bundle with multiple instances can be referred to as a split bundle.
Video
For an overview of working with multiple diagrams, including creating multiple bundle
instances, see the video Multiple Diagrams Overview.
Procedure
Perform one of the following procedures:

Split or slice an existing See Slicing a Bundle in the Capital Design Tools -
bundle on a diagram. Common Functions User Guide.
Create a new instance of a 1. Right-click on the bundle in the Design Browser
bundle using the context (Design tab) and select Create Bundle
menu (in the same diagram or Instance; the cursor changes as for the ‘Create
another) Bundle’ action.
2. Draw the new instance of the bundle.
Create a new instance of a 1. If it does not exist, add the first instance as a
bundle using drag and drop dangling bundle to a diagram. A dangling bundle
(in the same diagram or is only connected to something at one end.
another) Note: In the Design Browser (Design tab), a
dangling bundle has a specific icon ( ).
2. Either in the same diagram or another, drag the
bundle name from the Design Browser (Design
tab) to the diagram canvas; the cursor changes as
for the ‘Create Bundle’ action.
3. Draw the new instance of the bundle.

February 2016
Results
The new instance is created in the diagram.
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 that these are sliced
bundles.
You can drag a sliced end to stretch and move a bundle.
You can also extend an instance by adding a bundle at a sliced end. This results in a longer
instance and not a new bundle.
If a harness has multiple instances, you cannot merge it with another harness by dragging a
sliced end. You must drag a non-sliced bundle end. However, you can merge instances of the
same harness to form one instance by dragging a sliced end to any place on the other instance.
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.
There are various ways you can navigate between object instances, see Navigating Between
Sliced Object Instances in the Capital Design Tools - Common Functions User Guide.

You can specify (edit or override) the physical length of a bundle.
The physical length is initially determined by the length of the bundle in the diagram.
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.
Procedure
1. Right-click on the bundle in the Logical Designs Browser (Function tab), Design
Browser (Design tab) or Diagram Window and select Properties; the Edit Properties
2. On the General tab, select Override next to the Length field and change the value in the
field.
3. Click OK to exit the Edit Properties facility and to commit your changes.
Related Topics

February 2016

You can specify variant physical lengths for a selected bundle. The individual lengths are used
only when a particular option expression or functional variant module code is applied to a
bundle.
You may want to do this when a vehicle topology is identical across its variants except for
differences in bundle length.
The physical length is initially determined by the length of the bundle in the diagram. This
length is displayed on the General tab of the Edit Properties Dialog Box for the bundle and can
be overridden (see “Specifying the Physical Length of a Bundle” on page 109). This is the
physical length used by default. However, the bundle length may vary for different variants of
the built vehicle.
The lengths are passed from Capital Integrator to Capital HarnessXC and Capital ModularXC
when designs are synchronized between the two. Capital HarnessXC uses the variant lengths
when performing composite breakdown.
Note
The physical Variant Length is different to the nominal Length of the bundle (specified on
the General tab of the Edit Properties Dialog Box for a bundle). The nominal length is
calculated from the graphical length of the bundle, although it can be overridden by the user. It
is used to calculate the length of the wires that pass through the bundle. The variant lengths are
not used to calculate wire lengths in Capital Integrator and Synthesizing Wiring does not create
a separate wire for each variant.
Procedure
1. Right-click on the bundle in the Design Browser (Design tab) or Diagram Window and
select Properties; the Edit Properties Dialog Box is displayed.
2. Click the Variant tab.
3. In the Variant Expression column of the currently empty row, enter the option
expression or functional variant module code for which you want to specify a variant
length; a new empty row is added to the table.
4. In the Variant Length column for the option expression/functional variant module code
that you have entered, specify the variant length.
5. Repeat steps 3 and 4 for each variant physical length that you want to enter.

February 2016
Including a Slot with a Harness
Results
• Composite Wiring Synthesis and Modular Wiring Synthesis synthesize a single wire
regardless of the number of variant lengths specified in the table. The wire length uses
the graphical or overridden bundle length from the General tab of the Edit Properties
dialog box.
• Wiring import and export does not support variant bundle information.
• When the Capital Integrator design is synchronized with a Capital HarnessXC or Capital
ModularXC design, the variant lengths are displayed on the Variant tab of the Edit
Bundle dialog box for the appropriate bundle in those applications.
• There is no support for linking variant bundles through bridges or Change Manager. The
MCAD bridge is used to set the nominal length.
• When bundles are merged:
o The bundles retain variants and merge where required.
o When merging a variant bundle with a non-variant bundle, the resulting bundle
retains the variant information. The lengths for each variant will be modified by
adding the default length of the non-variant bundle.
o When merging two variant bundles, the variances are merged. Where option
expressions match, the variant lengths are added together.
o When a variant length is unique on one of the bundles, it is not modified on the
merged bundle.
• When splitting a variant bundle, the resulting bundles both have the variant lengths
applied. The lengths are adjusted according to the proportional nominal position where
the bundle is split.
Related Topics

If you want to combine a slot and one or more bundles to form one manufacturable component,
you can include a slot on a harness. This harness is then considered an integral harness for that
slot.
Prerequisites
• The slot connector for that harness must have been added to the slot.

February 2016
Excluding a Slot from a Harness
Procedure
1. Select the slot connector for that harness on the slot in the diagram or in the Design
Browser (Design tab) and either:
• right-click it and select Include Slot with Harness
• press Space Bar and enter Include Slot with Harness
2. If the slot connector is connected to multiple harnesses, the Select Integral Harness
Dialog Box is displayed. Select the harness for which you want to include the slot and
click OK.
Results
• The gray square representing the slot connector becomes smaller.
• In the Attributes section of the General tab of the Edit Properties facility for the slot
connector, the Integral attribute is selected.
• In the Attributes section of the General tab of the Edit Properties facility for the slot,
the Integral Harness attribute displays the name of the harness.
• If you combine a slot with more than one harness, the names of the slot connectors
change so that they all have the same name as the slot connector on the first harness that
was combined with the slot.
Note
You can specify a route code to distinguish between slot connectors when there is
more than one slot connector combined with a slot. This information is not used in
Capital Integrator but is used if the design is synchronized with a Capital HarnessXC
design. See “Specifying a Route Code for a Connector” on page 167.
Related Topics
Specifying a Route Code for a Connector

If you have combined a slot with one or more harnesses to form one manufacturable component
but now want to separate them so that they are separate pieces again, you can exclude a slot
from a harness.
Prerequisites
• The slot placement must not be constrained. See “Device Connectors and Harness
Connectors in Capital Integrator” on page 141 for more information about constrained
placements.

February 2016
Specifying a Domain for a Harness
• The selected slot connector must not have a library part assigned to it.
Procedure
Select the slot connector for that harness on the slot in the diagram or in the Design Browser
(Design tab) and either:
• right-click it and select Exclude Slot from Harness

• press Space Bar and enter Exclude Slot with Harness
Note
If you have more than one bundle combined with the slot, you must repeat this
for each of these bundles to exclude the slot from the harness.
Results
• The gray square representing the slot connector becomes larger.
• On the Attributes section of the General tab of the Edit Properties facility for the slot
connector, the Integral attribute is unselected.
• If the name of the slot connector changed when it was combined with the harness, it
changes back to the original name.
Related Topics
Specifying a Domain for a Harness

You can specify a domain for a harness so that only users with that domain assigned to their
user account can edit it. This allows multiple suppliers to work concurrently on the same
topology design, while allowing the design owner to manage access to each individual harness.
See Domains in the Capital User User Guide for more information about domains.
Procedure
1. In the Design Browser (Design tab), select the harness.
2. Either:
• right-click on the harness and select Properties
• press Space Bar and enter Properties
The Edit Properties: Virtual Harness dialog box is displayed.
3. On the General tab, select the Domain from the drop-down list and click OK.

February 2016
Merging Harnesses
Merging Harnesses
You can merge two harnesses.
Procedure
Drag the grip point at the end of one harness (harness A) to a point on the other harness (harness
B) into which you want to merge it; harness A merges into harness B.
Note
If a harness has multiple instances, you cannot merge it with another harness by
dragging a sliced end. You must drag a non-sliced end. However, you can merge
instances of the same harness to form one instance by dragging a sliced end to any place
on the other instance.
Results
• Properties from harness A are added to harness B, unless harness B has a property of the
same name already.
• Mergable attributes from harness A are set on harness B, unless harness B already has a
value for that attribute.
• If only one harness has a domain specified, the resulting harness has that domain. If both
harnesses have domains, the domain from harness B is used.
• Options on harness A are added to harness B, unless harness B has that option already.
• Rules and constraints on harness A are copied to harness B. You must check manually
whether there are any conflicts on the merged harness.
• Giveaway options on harness A are merged onto harness B without affecting any
existing giveaway options on harness B. An option cannot appear in the giveaway of a
harness more than once, so:
o If a giveaway from harness A already exists as part of a “Give Away With” group on
harness B, it is not added.
o If any member of a giveaway group on harness A already exists as part of a
giveaway group or as a single giveaway on harness B, the group is not added.
If a giveaway group exists on harness A with the same name as a giveaway group on
harness B, the group is renamed when added to harness A. The renaming uses the
format <GroupName>_<Index> where <Index> is an integer generated to ensure
that the name is unique within the harness.
• Harness levels from harness A are replicated onto harness B, unless harness B already
has a harness level that is equivalent.

February 2016
Splitting a Harness
If an equivalent level is found, the attributes and properties of the top-level harness level
are replicated onto the equivalent top-level harness level on harness B, without
overwriting any existing properties or attributes.
If no equivalent level is found, the harness level and all its children are replicated to
harness B.
If harness B already has a harness level with the same name as a level being replicated
from harness A, the replicated level is renamed using the format
<LevelName>_<Index> where <Index> is an integer.
Splitting a Harness
There are various ways in which a harness can be split.
A harness can be split by:
• deleting a bundle region in the harness.

• adding an inline pair (see “Adding an Inline Pair to a Diagram” on page 148)
This means there are now two harnesses. One of the harnesses is renamed and both have the
same properties, attributes, domains, options, rules, giveaway options, harness levels and
graphical attributes.
Multiple Harnesses at Connectors

There are several features to support the representation of complex harnesses. For example, a
composite harness can be drawn with option-tagged bundles and slots, and variantly-placed
devices. This topology can then be filtered to display particular vehicle configurations.
However, you may want to manage multiple, composite harnesses targeted at a particular region
or other major vehicle variant.
For example:
Rather than have a single complex instrument panel (IP) harness, you may prefer to manage a
composite left-hand drive (LHD) harness as well as a separate, composite right-hand drive
(RHD) harness.
To model multiple, complex harness variants, you model the interface between two or more
harnesses on one side of an inline and a single composite harness on the other. For example,
where the LHD IP and the RHD IP meet the body harness, there will be a single inline
connector on the body harness which needs to mate to either the LHD IP or the RHD IP.
Graphically, this is displayed as multiple bundles connected to the same inline. You add option
expressions to the bundles to allow them to be filtered.

February 2016
The primary scenario for multiple harnesses at a connector is at an inline connector, for
instance, modeling wires poked home at an inline. However, there are some cases where you
may want to have multiple harnesses at a connector on a slot, for example, if the LHD IP and
RHD IP harnesses connect to the same junction box. In this case, you may not want to duplicate
the connectors on the slot.
Figure 6-1. Example of Complex Harnesses Modeled without Multiple

Harnesses at a Connector
LHD IP and RHD IP are shown as filtered in the first two pictures. The third picture shows both
harnesses unfiltered. Note that a dummy harness is required to join the two IP harnesses to the
door harness.

February 2016
Figure 6-2. Example of Complex Harnesses Modeled with Multiple Harnesses at

a Connector
Both IP harnesses are connected to the single door harness via a single inline connector.
Scenarios Modeled Using Multiple Harnesses at a Connector

The use of multiple harnesses at a connector enables you to model various scenarios.
• Mutually exclusive harnesses and connectors (including many-to-many mating)

In this case, the cavities on the connector are connected to wires from multiple
harnesses. You apply option expressions to the harnesses to ensure that only one is
active at a time. A cavity can be connected to wires from different harnesses only if the
signals on these wires are the same.
If the connectors for these harnesses have different library parts, you must model this in
connector refinement.
• Modular connectors (multiple harnesses that meet at a single modular connector)
This is where the topology connector represents multiple physical connectors and it
would be modeled in connector refinement.
• Poke home wires (wire from one harness plugged into the connector of another
harness at installation)

February 2016
This is where a wire is to be connected to a connector at harness installation time rather

than harness manufacture time. This setting is not reflected graphically in the topology
design but is passed on to Capital HarnessXC during synchronization. When this
information is transferred to Capital Harness Classic or Capital HarnessXC, the
connector is marked as Not on BOM.
If any wire in a bundle is poked home, all wires in that bundle will be poked home.
A simple case being where a harness has only poked home wires at a connector; all
bundles at that connector for that harness contain only poke home wires.
A more complex case is a modular connector where one or more wires from one harness
are poked home into the connector of the other harness.
Figure 6-3. Modular Connector with Poked Home Wire
Here P1 and P2 are modules of a single modular connector.

You can model this with a takeout near the connector such that WIRE3, the poke home
wire, enters the connector on a bundle of its own. This matches how the harness would
be manufactured.
Figure 6-4. Topology Modeling of a Modular Connector with Poked Home Wire
You apply constraints to the poke home bundle to ensure that the correct signals are
routed that way. The poke home setting is displayed and edited in the Routes tab of the
Edit Properties dialog box for the slot connector.
You can model this scenario with two slot connectors, one for each module.

February 2016
Figure 6-5. Modeling of Modular Connector with Poke Home
Composite Wiring Synthesis and Multiple Harnesses at a Connector

In some scenarios, composite wiring synthesis creates a jumper wire at a connector. Generally,
the jumper wire is just placed into the harness connected to the connector. With multiple
harnesses, the wire is placed in the first suitable harness found. You can, however, use
constraints on bundles or harnesses to control the placement of the wire.
Synchronization with Capital HarnessXC

If you synchronize a design containing multiple harnesses at a connector with a Capital
HarnessXC design, Capital HarnessXC will recognize that not all the nodes at a connector
belong to the harness being edited. In addition, it recognizes that just because a cavity has no
wire in this harness, it does not mean a plug should be inserted into the cavity. The cavity might
be required for a wire on another harness.
Example High-Level Flows Using Multiple Harnesses at Connectors

The following examples give high-level details of how multiple harnesses at connectors may be
used.
Example Flow 1
1. Add a new bundle that either starts or finishes at a connector that is already connected to
another bundle; the system treats this as a new connection to a complex connector
junction.
2. Add option expressions to the bundles to identify their applicability.
3. Specify bundles at the connector that contain poke home wires.
4. Synchronize the data with a design in Capital Harness Classic or Capital HarnessXC; the
system treats the complex junction as if there is a connector applicable to each harness.
Note
All other tools that access the data (including reports, design rule checks and Capital
Enterprise Reporter) treat the complex junction as if multiple bundles are connected
to a single connector.
Example Flow 2

February 2016
In this example, there are two mutually exclusive harnesses for the engine, a LHD and a RHD
harness. They both need to connect to the IP harness, currently they are connected via two
separate inlines. There have been no constraints set on either harness or inline.
1. Select the inline for the RHD engine harness and delete it.
2. Connect the dangling bundle from the RHD harness to the remaining inline that is
connecting the LHD harness to the IP harness; both harnesses now connect to the same
inline.
3. Run Composite Wiring Synthesis; the results show the wiring for both harnesses passing
successfully through the inline and into the correct harness.
4. Check the signal map for the inline; the wires for signals that are common to both
harnesses flow through the same cavities.
5. Synchronize the data with a design in Capital Harness Classic or Capital HarnessXC; the
system treats the complex junction as if there is a connector applicable to each harness.
Note
All other tools that access the data (including reports, design rule checks and Capital
Enterprise Reporter) treat the complex junction as if multiple bundles are connected
to a single connector.

February 2016
Bundle Region
Bundle Region
You can divide a bundle into bundle regions and add rules or properties to the individual
regions. This may be desirable if you want to impose different conditions on different parts of a
bundle. For example, you may want to prevent the creation of splices in one region of a bundle.
See “Evaluation of Rules on Bundle Regions” on page 291 for more information about how
rules are evaluated on bundle regions.
A bundle region is different from a bundle segment. A bundle segment is a graphical object only
whereas a bundle region is a connectivity object. A bundle region can be represented by a set of
sequential bundle segments. Bundle regions cannot overlap each other.
You can set project style preferences for the graphical display of a bundle region. See the
Capital Project help system for more information about project style preferences. You can also
edit the properties of the bundle region in Capital Integrator. See “Editing the Attributes and
Properties of Objects” on page 269 for more information.
If you click a segment within a bundle region to select it and access the Edit Properties facility,
you edit the properties for the bundle region, not the bundle segment and not the bundle as a
whole.
If a bundle region covers a whole bundle, then you can select the bundle in the Design Browser
(Design tab) to edit its properties. Alternatively, you can right-click on the bundle region and
select the Extend Selection option from the pop-up menu before accessing the Edit Properties
facility.
You can add grip points to a region. If you insert an inline or a through node, or if you connect
another bundle end to the region, the region is split, and the properties of the region are copied
to both resulting regions.
Bundle regions are defined using offsets from the bundle ends. The Offset section of the Edit
Properties facility for a bundle region indicates the offset from the bundle start node and
bundle end node for each of the region nodes.
After you have defined a bundle region, you can edit it.
Defining a Bundle Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Deleting a Bundle Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

February 2016
Defining a Bundle Region

Using the Adjust Bundle Region Menu Option to Move a Bundle Region Node. . . . . . 124
Editing the Offsets of a Bundle Region from the Bundle Ends . . . . . . . . . . . . . . . . . . . . 125

You can define a bundle region.
Procedure
1. Press Space Bar and enter Bundle Region.
2. The mouse cursor displays the bundle region symbol. Click on the bundle at the point
where you want to start the region. If you are at a point where you cannot start a region,
the symbol has a line crossing it . If you are at a point where you can start a region,
there is no line crossing the bundle symbol . You cannot intersect an exiting bundle
region.
If you move the cursor over an end point (bundle start node or bundle end node) of a
bundle, you can right-click and select the New Node menu option to create a region
node at the same position as the bundle start node or bundle end node.
If you do not create a region node at the bundle node, the region shares the node with the
bundle. In this case:
• Moving the node changes both the region length and the bundle length.
• Sliding the region along the bundle changes the bundle length.
If you do create a region node at the bundle node, there are two nodes located there. In
this case:
• Moving the region node within the bundle changes the region length but not the
bundle length.
• Sliding the region along the bundle moves the region without changing the region
length or bundle length.
If you create a bundle region that does not reach the end point of a bundle, region nodes
are created automatically at each end of it.
Similarly, you can share a region node with another region node. Moving a shared node
changes the lengths of both regions.
3. A red square is displayed at the point you have selected to indicate the region start node
location. Click on the point where you want to end the region. You cannot define a
bundle region across multiple bundles.

February 2016
Deleting a Bundle Region
4. The red square disappears and the bundle region is displayed according to the project
style preferences that have been set in Capital Project. At each end of the bundle region,
there is a bundle region node. These nodes are not visible unless the bundle region is
selected. If the bundle region node is an adjacent node of two regions (shared region
node), the node will be visible.
In the Design Browser (Design tab), the region is displayed under the harness on which
it is located.
Related Topics
Bundle Region
Moving a Bundle Region Node Manually
Sliding a Bundle Region along a Bundle
Using the Adjust Bundle Region Menu Option to Move a Bundle Region Node
Editing the Offsets of a Bundle Region from the Bundle Ends

You can delete a bundle region.
Procedure
1. Right-click on the bundle region in the diagram or in the Design Browser (Design tab)
and select the Delete option from the pop-up menu.
2. The bundle region is deleted.
Related Topics
Bundle Region

You can move a bundle region node manually.

February 2016
Procedure
Position your cursor over the bundle region node so that the two-way stretch symbol is
displayed. Hold the left mouse button down and drag and drop the region node to the new
location. If you drag it to a location not on the current bundle path, the bundle will change
accordingly to maintain connectivity.
Related Topics
Bundle Region

You can slide a bundle region along a bundle.
Procedure
Position your cursor over the bundle region so that the four-way move symbol is displayed.
Hold the left mouse button down and drag and drop the region to the new location.
Related Topics
Bundle Region
Using the Adjust Bundle Region Menu Option to

Move a Bundle Region Node
You can use the Adjust Bundle Region menu option to move a bundle region node.
Procedure
1. Press Space Bar and enter Adjust Bundle Region.

February 2016
2. The mouse cursor displays the bundle region symbol. Click on the bundle region node
that you want to move. When you are on a bundle region node, there is no line crossing
the bundle symbol .
3. The bundle region node is highlighted with a red square. Move the cursor to the location
to which you want to move the bundle region node and click.
4. The bundle region node moves and the bundle region changes accordingly.
Related Topics
Bundle Region
Editing the Offsets of a Bundle Region from the

Bundle Ends
You can use the Edit Properties dialog box to edit the offsets of a bundle region from the bundle
ends.
Procedure
1. Right-click on the object in the Design Browser (Design tab) or Diagram Window and
select Properties; the Edit Properties Dialog Box is displayed.
2. On the General tab, edit the attributes in the Bundle: < Bundle Name> as required.
This section indicates the offset from the bundle start node and bundle end node for each
of the region nodes. Edit them as required.
The fields in the Offset section are:
• Bundle Start - From - the offset from the bundle start node to the region start node.
• Bundle Start - To - the offset from the bundle start node to the region end node.
• Bundle End - From - the offset from the bundle end node to the region start node.
• Bundle End - To - the offset from the bundle end node to the region end node.

February 2016
For example:
A region has the following offset values:
The following image indicates the sections of the bundle to which the offset distances
correspond:
3. In the diagram, red squares indicate the new locations of the region nodes. If you have
entered conflicting offsets, the offset values are displayed in red. Click OK to accept
your changes to the offsets.
4. The bundle region changes accordingly in the diagram window.
Related Topics
Bundle Region

February 2016
Through Node
Through Node
Through nodes can be used to make a wire pass through a particular bundle. When you connect
bundles together in such a way that they form a loop, a through node is added automatically to
the last bundle that you create in the loop. You can add through nodes to bundles manually.
After you have synthesized wiring, you can use the Edit Wire Path to reroute a wire so that it
passes through a particular through node. See “Editing Wire Paths” on page 479 for more
information.
Creating a Through Node on a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Deleting a Through Node from a Bundle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Converting Through Nodes from Structure Nodes to Reference Nodes . . . . . . . . . . . . 128
Creating a Through Node on a Bundle

You can create a through node on a bundle.
Procedure
1. Press Space Bar and enter Through Node. If you want to add more than one through
node to the diagram, hold down the SHIFT key on the keyboard when selecting the
menu option. Note that you can add only one through node per bundle.
2. The mouse cursor changes to a cross with an arrow symbol . Click on the point on a
bundle where you want to create the through node.
Note
If you are creating more than one through node, click the Esc button when you have
created them all.
Results
• The through node is added to the diagram window as a green circle and to the Nodes
folder for the relevant harness in the Design Browser (Design tab).
• The bundle is not split because the through node is treated as a reference node.
Related Topics
Through Node
Deleting a Through Node from a Bundle
Converting Through Nodes from Structure Nodes to Reference Nodes

February 2016

You can delete a through node from a bundle.
Procedure
Click on the through node in the diagram window or in the Design Browser (Design tab) and
press the Del button on your keyboard. Alternatively, right-click on the through node and select
the Delete option from the pop-up menu; the through node is deleted.
Related Topics
Through Node
Converting Through Nodes from Structure Nodes to Reference Nodes
Converting Through Nodes from Structure Nodes

to Reference Nodes
You can convert through nodes that are structure nodes to reference nodes.
Procedure
Press Space Bar and enter Convert All Structure Through Nodes.
Results
• Any through nodes that are structure nodes become reference nodes.
• Bundles on either side of a converted node merge together and attribute conflicts are
reported in the Output Window.
Related Topics
Through Node
Integrator Harness Exchange

Original equipment manufacturers (OEMs) can exchange individual harnesses managed at
platform level with suppliers. The exchanged data includes all placement, constraint and
connectivity information, enabling wire synthesis to be completed on a single harness. The
exchanged data does not include the associated logical designs or the library data (both of these
must be transferred separately).
Why do this?

February 2016
• Reduce costs
o A single design can be spread among multiple suppliers in order to distribute the
design cost
o Harnesses can be designed and costed individually as the data becomes available,
meaning time is not wasted waiting for the full platform to be complete before
costing can begin
o Multiple suppliers can cost the same harness
o Cost of re-work is reduced by changes being restricted to individual harnesses

February 2016
Flow for Integrator Harness Exchange

Note
Although concurrent editing of a Capital Integrator design can provide a productive
environment for an OEM and its suppliers to develop vehicle wiring, it is not always
feasible (or even desirable) for all the organizations to work within the same network and
Capital installation. The steps outlined here, show how the work may be distributed to
individuals working within their own Capital environment, by exchanging harness data between
Capital Integrator designs.
1. The OEM synthesizes the full vehicle to determine the initial vehicle wiring and inline
interfaces:
o The OEM prepares the vehicle data as for a standard generative process
o The system designs are created and associated with the Capital Integrator design
o Within Capital Integrator, the topology is prepared (possibly by bridging data from
MCAD), the devices and grounds are placed, and then an initial synthesis is
performed
Note
This synthesis is important because it defines the signals passing through each
inline pair - in other words, the interfaces between the harness families.
2. The OEM exports harnesses and distributes these, together with the latest system
designs, to the harness suppliers.
Note
It is important that the suppliers have a compatible project and Capital Integrator
design ready to receive the data.
3. Each supplier imports their harnesses into the empty Capital Integrator design:
o the import creates an identical topology with all its bundles and slots
o inlines are imported as interface connectors (with the required signals defined for
each cavity)
o logical devices are placed automatically as they were in the OEM’s design
4. Each supplier refines the topology, placement and wiring as required.
Almost any modification can be made. Wiring synthesis (such as, Modular Wiring
Synthesis or Composite Wiring Synthesis) can also be performed, but this will be
limited to the harnesses with the supplier’s design rather than the scope of the full
vehicle.

February 2016
5. Each supplier exports modified harnesses and returns them to the OEM for
incorporation.
6. The OEM updates the master design with changes from each supplier and ensures
compatibility.
All the changes from the supplier are imported. The OEM is able to view this data in the
full vehicle context, as well as to run validation such as design rule checks or the Design
Assistant.
7. Further modifications to the data can be exchanged in either direction.
The OEM can provide new revisions of the system designs and can also distribute new
harness data if, for example, changes are needed at the inline connector interfaces.
The suppliers can also continue to modify their own harness data and provide updates to
the OEMs as required.
Harness Sets
When you export multiple harnesses, you have the option to export them as a harness set. If you
do this, they are exported as a set in a ZIP file that contains an XML file for each harness.
When importing harnesses, you can import one of these ZIP files. The system scans the contents
of the ZIP file looking for harness names and compares them with the harness names on the
design.
If there are matching names (and the harnesses are locked), the system allows you to select one
matching harness to replace (that is, overwrite the harness in the design with the incoming data).
For example:
If you have a source design with harnesses A, B, C and you export them as a harness set, a ZIP
file is created containing three XML files (one for each harness). If you then import this set into
a design containing harnesses B, C and D, the import offers you the option of overwriting B or
C only. You can select only one of those. If you wanted to import both, you would have to
repeat the import process.
If you want to import a harness set into a blank diagram, unzip the XML files and import them
individually. The system does not support the import of multiple harness XML files in a single
operation (that is, the complete contents of a harness set in one go) because there are difficulties
analyzing the impact of import failures on later operations.
Related Topics
Exporting a Harness from a Design
Exporting Multiple Harnesses from a Design
Importing Modified Data for an Existing Harness in a Design

February 2016
Importing the Data for a New Harness into a Design

Importing the Data for a New Harness into a Design and Mating a Connector

You can use Integrator Harness Exchange functionality to export a harness in XML format from
a design.
Procedure
1. Right-click on the harness in the Design Browser (Design tab) (Design tab), and select
Export Harness; the Export Harness dialog box is displayed.
2. Navigate to the location where you want to save the XML file and specify a name for it.
Click Export; the XML file is created and saved in that location.
Results
• The XML file contains the topology information for the harness, placement information,
all of the harness levels and all of the wiring data for that harness.
• The exported file contains details of the diagrams on which the diagram objects exist.
When imported, the system returns the objects to each diagram if they exist or creates
the diagrams as required.
Related Topics

You can use Integrator Harness Exchange functionality to export multiple harnesses in XML
format from a design.
Procedure
1. Press Space Bar and enter Export Harness; the Harness Selection Dialog Box dialog box
is displayed.
2. Select the harnesses that you want to export and click OK; the Export Harness dialog
box is displayed.

February 2016
3. Navigate to the location where you want to save the XML files and click Export; one
XML file per harness is created and saved in that location.
Results
• The XML files are named using the harness names.
• The XML files contain the topology information for the harnesses, all of the harness
levels and all of the wiring data for those harnesses.
Related Topics
Importing Modified Data for an Existing

Harness in a Design
You can use Integrator Harness Exchange functionality to import the modified data (in XML
format) for an existing harness in a design.
Procedure
1. In the Design Browser (Design tab), right-click on the harness for which you are
importing data and select Import Harness; the Import Harness dialog box is
displayed.
2. Navigate to the location where the XML file is saved and select it.
Note
You have the option of importing an XML file from a harness set ZIP file.
3. Specify whether you want to Run Harness Transfer DRCs. If you select this, the
import will run all design rule checks set to run in Harness Transfer mode and will
indicate any issues.
Note
You can view and edit the design rule checks set to run in Harness Transfer mode
in the Project Preferences.
4. Click Import; the imported harness data overwrites the existing harness.

February 2016
Results
• If there are any issues, they are displayed on the Harness Import tab of the Output
Window.
Related Topics
Importing the Data for a New Harness into a

Design
You can use Integrator Harness Exchange functionality to import the data (in XML format) for
a harness that does not yet exist in a design.
Procedure
1. Press Space Bar and enter Import Harness; the Import Harness dialog box is displayed.
Note
4. Click Import; the harness is imported.

Results
Window.
• If nothing on the imported harness exists on the diagram, it is placed as close as possible
to the position it had in its source diagram.
• If a connector or hole exists both on the harness and on the diagram, the harness is
placed so that it connects to the connector or hole on the diagram.
• If an inline exists on multiple harnesses, when the first harness with the inline is
imported, the inline is placed (with the rest of the harness) on the diagram. When any

February 2016
other harnesses with that inline are imported, the inline already exists in the diagram and
the harnesses are connected to it.
Related Topics
Importing the Data for a New Harness into a

Design and Mating a Connector
You can use Integrator Harness Exchange functionality to import the data (in XML format) for
a harness that does not yet exist in a design and mate one of its unmated connectors with an
unmated connector already in the design.
Procedure
1. Right-click on the unmated connector in the diagram and select Import Anchored
Harness; the Import Harness dialog box is displayed.
Note
4. Click Import; the system looks at the incoming harness data to find any connectors that
could mate with the selected connector in the diagram.
If there is only one eligible connector, the harness is placed and that connector is mated
with the connector in the diagram.
If there are multiple eligible connectors, the Import Harness dialog box displays a list
of them. Select the connector that you want to mate with the connector in the diagram
and click OK; the harness is then placed in the diagram and the connectors are mated.
Results
Window.

February 2016
Related Topics

February 2016
Chapter 7
Connectors
This chapter contains details on how to create and edit connectors: slot connectors, device
connectors, harness connectors, inline pairs, and interface connectors.
Note
For information about connector refinement and signal mapping, see “Connector
Refinement and Signal Mapping” on page 209.
Slot Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

Adding a Slot Connector to a Slot Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Moving a Slot Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Device Connectors and Harness Connectors in Capital Integrator . . . . . . . . . . . . . . . . 141
Mapping Cavities and Pins between a Device Connector and a Harness Connector . . 144
Mapping a Footprint Connector to a Slot Connector (Device Connector and Harness
Connector) on a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
Adding an Inline Pair to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Deleting an Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Adding an Inline Receptacle with an Associated Library Part . . . . . . . . . . . . . . . . . . . . . . 149
Adding an Inline Receptacle without an Associated Library Part . . . . . . . . . . . . . . . . . . . 150
Adding an Inline Plug with an Associated Library Part . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Adding an Inline Plug without an Associated Library Part . . . . . . . . . . . . . . . . . . . . . . . . 152
Adding a Cavity to an Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Deleting a Cavity from an Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Adding an Interface Connector to a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Exporting an Interface Connector Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Importing an Interface Connector Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Common Editing Tasks for Multiple Connector Types . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Deleting a Cavity from a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Copied Data When Cloning a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

February 2016
Connectors
Backshells and Backshell Terminations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Adding a Backshell to a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Deleting a Backshell from a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Adding a Backshell Termination to a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Deleting a Backshell Termination from a Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

February 2016
Connectors
Slot Connector
Slot Connector
Also referred to as a virtual connector, a slot connector connects devices in a slot to a bundle.
There must be a slot connector wherever a bundle connects to a slot.
Generally, you can have only one bundle going into a slot connector. However, there are ways
to model multiple harnesses at a connector (see“Multiple Harnesses at Connectors” on
page 115).
When devices are placed in a slot, there are signals that travel through pins on the devices and
that need to pass out of the slot through cavities in the slot connectors. The pins and signals have
been specified in Capital Logic. In Capital Integrator, you add cavities to the slot connector and
define through which cavity in which slot connector each signal from a device travels.
When you create a bundle that connects to a slot, a slot connector is created automatically where
the bundle and slot connect.
In Capital Integrator, physical device connectors and physical harness connectors are managed
in tandem with slot connectors. This means, when a slot connector is created, a physical device
connector and physical harness connector pair is created as well. The pins on the physical
connectors are mated to each other and referenced by a cavity. See “Device Connectors and
Harness Connectors in Capital Integrator” on page 141 for more information.
You cannot delete a slot connector if:
• the slot placement is constrained. See “Device Connectors and Harness Connectors in
Capital Integrator” on page 141 for more information about constrained placements.
• the slot has more than one integral slot connector and they are associated with a library
part.
Adding a Slot Connector to a Slot Manually. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Moving a Slot Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140
Adding a Slot Connector to a Slot Manually

You can add a slot connector to a slot manually.
Note
When you create a bundle that connects with a slot, a slot connector is created
automatically.
Procedure
1. Right-click on the slot in the diagram or on the name of the slot in the Design Browser
(Design tab) and select Add Virtual Connector from the pop-up menu. If you want to

February 2016
Connectors
Moving a Slot Connector
add multiple slot connectors, hold down the SHIFT key on your keyboard when
selecting Virtual Connector.
2. In the Diagram Window, click on the points of the slot where you want to add slot
connectors.
Note
During the action, circles denote the valid grid points.
3. A hexagon is added to the diagram wherever a slot connector has been placed and the
names of the connectors are added to the Design Browser (Design tab).
Press the Esc key on your keyboard to stop adding slot connectors or double-click when
adding the last connector.
Note
After you have added slot connectors and synthesized wiring, the Refine
Connectors facility enables you to define different connector configurations with
different pin mappings and part numbers for different levels. See“Connector Refinement
and Signal Mapping” on page 209 for more information. If you want to use the Edit
Properties facility to assign a library part to a slot connector, you cannot use the Refine
Connector facility on that slot connector. If you have done so, you must delete any
bundle fanouts that you have defined before you can assign the library part.
Related Topics
Slot Connector
Adding a Cavity to a Connector
Connector Refinement and Signal Mapping

You can move a slot connector to another grid point on the edge of the slot. This is purely a
visual movement and does not change the connectivity of the slot connector.
If you have multiple instances of a slot, you can move the slot connector to another instance in
the same diagram. You cannot move it to an instance on another diagram.
Procedure
• Right-click the slot connector that you want to move and select the Move slot
connector option from the pop-up menu. Click on the new location.

February 2016
Connectors
Device Connectors and Harness Connectors in Capital Integrator
• Click on the slot connector to select it, press Space Bar and enter Move slot
connector. Click on the new location.
• Click on the slot connector, hold the mouse button down and drag the slot connector
to the new location.
Note
During the action, circles denote the valid grid points.
Results
The slot connector moves to the new location and is re-styled appropriately (for example, to
move related text).
Related Topics
Slot Connector
Adding a Slot Connector to a Slot Manually
Device Connectors and Harness Connectors

in Capital Integrator
In Capital Integrator, physical device connectors and physical harness connectors are managed
in tandem with slot connectors. When a physical device connector and physical harness
connector pair is created under a slot connector, the pins on the physical connectors are mated to
each other and referenced by a cavity of the slot connector.
When working with device connectors and harness connectors, you need to be aware of the
concept of constrained placement. Constrained placement is when a Capital Logic device that
has a footprint definition with device connectors or a footprint is placed into a Capital Integrator
slot. In this case, there are constraints on what can be modified on the slot.
The physical device connector is displayed below the slot connector in the Design Browser
(Design tab) but the pins for the device connector are not listed. You can edit a device connector
by right-clicking on it and selecting the Properties option from the pop-up list. See the “Editing
the Attributes and Properties of Objects” on page 269 for more information about editing an
object's general attributes and properties. If there is a corresponding functional connector in an
associated Capital Logic design, you cannot edit the properties of a physical device connector.
A physical device connector is not represented graphically in a diagram window.
The physical harness connector is not displayed explicitly in the Design Browser (Design tab)
but can be edited by right-clicking on the slot connector and selecting the Properties option
from the pop-up list. When you then edit the name, properties and part specification for the slot

February 2016
Connectors
connector, this applies to the physical harness connector too. See “Editing the Attributes and
Properties of Objects” on page 269 for more information about editing an object's general
attributes and properties.
If a Capital Logic device is specified with a harness-based footprint, when that device is placed
in a slot, the slot connectors (and physical harness connectors and physical device connectors)
are created corresponding to the Capital Logic device and its footprint definition. Part
specifications are assigned to the harness connectors. You cannot change (except update) the
part assignment for the harness connector unless you unplace the device.
The physical device connector is not specified directly by the footprint and only a connector
part number with the correct number of cavities (and it is preferred a mate-able part) can be
chosen when assigning a library part number.
If a functional device that has functional device connectors defined for it is placed in a slot, the
slot connectors (and physical device connectors) are created corresponding to the functional
device and its functional device connectors. This fixes the part assignment and names on the
physical device connectors. In addition, any properties on the functional device connectors are
copied to each corresponding physical device connector and are fixed.
If a new slot connector is created because of a device-based footprint placement, then there is no
physical harness connector created until later when a harness connects to it.
The physical harness connector is not specified directly by the functional device connectors and
only a connector part number with the correct number of cavities (and it is preferred a mate-able
part) can by chosen when a library part is assigned.
If either the physical device connector or the physical harness connector has a part number, the
number of cavities on the slot connector is fixed. Cavities cannot be added nor deleted from
such a slot connector.
Cavity names are the same as the pin names for the physical harness connector. When a part
number has been assigned to the physical harness connector, the cavity names of the library
connector definition are used. You can modify cavity names only when there is no part number
assigned to the physical harness connector. If you change the cavity names, this also changes
the names of pins on the physical harness connector.
When they are created, the slot connector name is the same as the physical harness connector
name. You can view and edit the name of the physical harness connector or the name of the
physical device connector by right-clicking on the connector and selecting the Properties
option from the pop-up list.
When you assign a part to a physical harness connector or to a physical device connector that
already has pins (because the slot connector has some cavities), but the mated physical
connector has no part assigned yet, the part selection is constrained to connectors with the same
or a greater number of cavities. Additional cavities and the corresponding pairs of physical

February 2016
Connectors
connector pins are created or removed as necessary when the part number assignment is
accepted.
In this case, the names of the cavities from the part definition must be mapped to the existing
physical pins.
When you auto-place a footprint device, Capital Integrator automatically maps the connectors
using mapping rules. See “Placement of a Device or Ground Device in a Slot” on page 174 for
more information.
If a slot is integral to a harness, the integral physical connector can be assigned for a library part.
The existing slot connectors and their cavities (if there are any) will be reused when possible.
For example:
A physical device connector is associated with two integral slot connectors. Slot connector 1
(VC1) has 2 cavities and slot connector 2 (VC2) has 4 cavities. The device connector in the
footprint has 6 cavities and its name matches the name of the physical device connector. When
the footprint is placed, the 2 cavities on VC1 are mapped with 2 library pins and the 4 cavities
on VC2 are mapped with 4 library pins.
Mapping Cavities and Pins

When you use either the Properties facility or the Place Device facility (for a constrained
placement) and this results in a connector part number being assigned to a slot connector,
physical device connector or an inline connector that already has cavities/pins, those cavities/
pins are mapped automatically to the cavities from the library part in the following way:
• Capital Integrator attempts to map the existing cavity/pin name to the same name in the
library part.
• If there is no match for the above, Capital Integrator attempts to match the existing,
mated physical connector cavity/pin name to one in the library part.
• If there is no match for either of the above, Capital Integrator will select a cavity at
random.
You can use the Cavity Map facility to re-map the names of cavities/pin between a physical
device connector and a physical harness connector. See “Mapping Cavities and Pins between a
Device Connector and a Harness Connector” on page 144 for more information about using that
facility.
During, or after, the placing of a new device, you can use the Connector Map facility to map
footprint-defined connectors to physical connectors. See “Placement of a Device or Ground
Device in a Slot” on page 174 for more information about the Mapping tab and its use.

February 2016
Connectors
Mapping Cavities and Pins between a Device Connector and a Harness Connector
Invalid Constrained Placements

A constrained placement can become invalid if the footprint definition in Capital Library or the
Capital Logic device is changed. The synchronize action adjusts the changes from Capital Logic
with Capital Integrator. For automatic synchronization (that is, when you switch from a Capital
Logic diagram to a Capital Integrator diagram), invalid placements are updated only where the
devices being placed have a device-based footprint. The synchronize action that is invoked
manually will update the placements for both footprint types. You can also manually update the
harness-based footprint placements by editing the properties on the devices and slot connectors
in the slot.
The design rule checks for Capital Integrator can be used to check for invalid constrained
placements. See “Running Design Rule Checks Manually” on page 73 for more information
about running design rule checks.
Related Topics
on a Slot
Mapping Cavities and Pins between a Device

Connector and a Harness Connector
You can use the Cavity Map facility to re-map the names of cavities/pin between a physical
device connector and a physical harness connector.
See “Device Connectors and Harness Connectors in Capital Integrator” on page 141 for more
information on these types of connector and on the constraints that apply to the cavities of these
connectors.
When you use the Cavity Map facility, the actual cavities/pins are not switched and the signals
are not remapped but the names of the cavities/pins are changed. This facility enables you to
remap the cavities from the two mated connector library parts. Note that you cannot edit a
cavity map if a footprint defines the selected slot connector or physical device connector.
Procedure
1. Right-click on either the slot connector (that defines the harness connector) or the device
connector in the Design Browser (Design tab) and select the Cavity Map option from
the pop-up menu. Alternatively, click on one of the connectors, press Space Bar and
enter Cavity Map..
2. The Cavity Map facility is displayed. The cavities of the connector that you selected in
the Design Browser (Design tab) are displayed in the second column and the cavities of

February 2016
Connectors
Mapping a Footprint Connector to a Slot Connector (Device Connector and Harness Connector) on
the mated connector are displayed in the first column. The cavities on each row are
mapped with each other. You can edit the second column only.
Click on a cavity name in the second column that you want to change. A drop-down list
of the available cavity names for the connector are displayed. Click on the name that you
want to map to the cavity name in the first column. Note that the cavity name that you
change moves to the row where the cavity name that you select was previously
displayed.
Note
If a connector has a footprint, you can click the Faceview button for it to view its
graphical faceview.
Related Topics
on a Slot
Mapping a Footprint Connector to a Slot

Connector (Device Connector and Harness
Connector) on a Slot
You can edit the mapping of footprint connectors to slot connectors (device connectors and
harness connectors on a slot) after you have placed a device with a footprint.
Note
You can edit these mappings when you place a device with a footprint manually. See
“Manually Placing a Normal or Ground Device in a Slot” on page 182.
Procedure
1. Either:
• Right-click on the slot in the Design Browser (Design tab) or Diagram Window and
select Connector Map.
• Click on the slot, press Space Bar and enter Connector Map.
The Connector Map Dialog Box is displayed and the Footprint Mappings table lists the
footprint connectors and their mappings.
2. If you want to change the slot connector to which a footprint connector is mapped, click
the Slot Connector - Harness field for that mapping and select the required connector
from the drop-down list.

February 2016
Connectors
Mapping a Footprint Connector to a Slot Connector (Device Connector and Harness Connector) on
Note
You can create a new slot connector by selecting <New Connector> from the drop-
down list.
3. When the mappings are correct, click OK.
Caution
After you have re-mapped the connectors in a slot, you may need to manually delete
any slot connectors that are no longer mapped and that you do not want to keep in
the design. You can delete only slot connectors that are not part of a footprint.
Related Topics
Slot Connector

February 2016
Connectors
Inline Pair
Inline Pair
When an inline pair is placed on a bundle, the wires passing through that bundle are
automatically terminated at the relevant half of the connector pair.
Each connector half has its own, individual property set.
Inline pairs split the bundles into separate harnesses.
All inline pairs are displayed on the Design tab of the project browser tree.
Note
You can edit which signal goes into which cavity of an inline connector. See “Mapping a
Signal Between Cavities on the Halves of an Inline Connector” on page 246 for more
information.
There are several factors that are considered when placing inline pairs, the following highlights
some of the possible factors:
• Manufacturing - if the sections of the vehicle (the harnesses) are to be manufactured

(or designed) at separate locations (companies, factories, and so on).
• Assembly - to aid fitting the harnesses into the vehicle.
• Option content - large numbers of options on a harness will result in many harness
levels which may be difficult to manage.
• Physical constraints - where the connectors can be placed for easy assembly, for
accessibility and for reliability (where the connectors will not undergo physical or
environmental distress).
Adding an Inline Pair to a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Deleting an Inline Pair. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
Adding an Inline Receptacle with an Associated Library Part . . . . . . . . . . . . . . . . . . . . 149
Adding an Inline Receptacle without an Associated Library Part . . . . . . . . . . . . . . . . . 150

February 2016
Connectors
Adding an Inline Pair to a Diagram
Adding an Inline Plug with an Associated Library Part . . . . . . . . . . . . . . . . . . . . . . . . . 151

Adding an Inline Plug without an Associated Library Part . . . . . . . . . . . . . . . . . . . . . . 152
Adding a Cavity to an Inline Pair. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Deleting a Cavity from an Inline Pair . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

You can add an inline pair to a diagram.
Procedure
1. Press Space Bar and enter Add Inline Pair.
2. Click on a bundle where you want to add the inline pair.
Results
• Any wires passing through that bundle are automatically terminated at the relevant half
of the connector pair.
• Each inline half has its own, individual property set.
• The inline pair splits the bundle into separate harnesses.
• The inline pair is displayed on the Design tab of the project browser tree.
Related Topics
Inline Pair
Deleting an Inline Pair
Adding a Cavity to an Inline Pair

You can delete both halves of an inline pair simultaneously.
Caution
Do not attempt to delete an inline pair using the Delete option, as this will only remove the
graphical representation of the connector from the diagram without re-joining the wires.

February 2016
Connectors
Adding an Inline Receptacle with an Associated Library Part
Procedure
Right-click over either half of the pair and click the Delete Inline Pair option; the inline pair is
removed from the bundle.
Results
• Any wires in that bundle are re-joined.
• If there is more than one bundle connected to either side of the inline, it is replaced with
a structure node.
• Any cavity that has multiple conductors connected to it (whether from the same or
different bundles), or has no conductor at the mated pin, is replaced by a splice.
Related Topics
Inline Pair
Deleting a Cavity from an Inline Pair
Adding an Inline Receptacle with an Associated

Library Part
You can place an inline receptacle (inline half) onto a topological design by associating a
connector from the library.
Procedure
1. Press Space Bar and enter Add Receptacle.
A ghost image of the inline receptacle is displayed next to the cursor.
2. Click to place the inline receptacle:
• If you click the end of a bundle, the inline receptacle is connected to that bundle.
• If you click on an empty area of the design, the inline receptacle is not connected to
anything.
An inline receptacle is placed on the diagram and added to the Design Browser (Design
tab).
3. Either:
• Right-click on the inline receptacle and select Properties.
• Click on the inline receptacle, press Space Bar and enter Properties.
The Edit Properties: Inline Receptacle Connector dialog box is displayed.

February 2016
Connectors
Adding an Inline Receptacle without an Associated Library Part
4. In the Library Part section, click Add.

The Part Selection dialog box is displayed allowing you to search for and insert a
connector from the library. Find the part you want, select it and click Insert.
5. The associated connector is displayed next to the Library Part text.
6. Click OK.
Related Topics
Inline Pair
Adding an Inline Plug with an Associated Library Part
Adding an Inline Plug without an Associated Library Part
Adding an Inline Receptacle without an Associated

Library Part
You can place an inline receptacle (inline half) onto a topological design without an associated
library part.
Procedure
1. Press Space Bar and enter Add Receptacle.
A ghost image of the inline receptacle is displayed next to the cursor.
2. Click to place the inline receptacle:
• If you click the end of a bundle, the inline receptacle is connected to that bundle.
• If you click on an empty area of the design, the inline receptacle is not connected to
anything.
An inline receptacle is placed on the diagram and added to the Design Browser (Design
tab).
Related Topics
Inline Pair

February 2016
Connectors

Adding an Inline Plug with an Associated Library

Part
You can place an inline plug (inline half) onto a topological design by associating a connector
from the library.
Procedure
1. Press Space Bar and enter Add Plug.
A ghost image of the inline plug is displayed next to the cursor.
2. Click to place the inline plug:
• If you click the end of a bundle, the inline plug is connected to that bundle.
• If you click on an empty area of the design, the inline plug is not connected to
anything.
An inline plug is placed on the diagram and added to the Design Browser (Design tab).
3. Either:
• Right-click on the inline plug and select Properties.
• Click on the inline plug, press Space Bar and enter Properties.
The Edit Properties: Inline Plug Connector dialog box is displayed.
4. In the Library Part section, click Add.
The Part Selection dialog box is displayed allowing you to search for and insert a
connector from the library. Find the part you want, select it and click Insert.
5. The associated connector is displayed next to the Library Part text.
6. Click OK.
Related Topics
Inline Pair

February 2016
Connectors
Adding an Inline Plug without an Associated

Library Part
You can place an inline plug (inline half) onto a topological design without an associated library
part.
Procedure
1. Press Space Bar and enter Add Plug.
A ghost image of the inline plug is displayed next to the cursor.
2. Click to place the inline plug:
• If you click the end of a bundle, the inline plug is connected to that bundle.
• If you click on an empty area of the design, the inline plug is not connected to
anything.
An inline plug is placed on the diagram and added to the Design Browser (Design tab).
Related Topics
Inline Pair
Converting an Inline Half Type

You can convert (switch) an inline receptacle to an inline plug and vice versa.
Procedure
1. Select the inline half in the Diagram Window or Design Browser (Design tab).
2. Either:
• right-click on the inline half and select Toggle Inline Type
• press Space Bar and enter Toggle Inline Type
3. The inline half type changes. If the inline half is connected to another inline half, the
type for that inline half changes too. The symbol for the inline half in the Design
Browser (Design tab) Tree changes accordingly ( for an inline receptacle, for an
inline plug).

February 2016
Connectors
Related Topics
Inline Pair

After you have added an inline pair, you can add cavities to it.
Procedure
1. Right-click on the inline pair in the Design Browser (Design tab) and select Cavity from
the pop-up menu. Alternatively, click the inline pair in the Design Browser (Design tab),
press Space Bar and enter Cavity.
2. A new cavity is added to the list of cavities in the Design Browser (Design tab).
Related Topics
Inline Pair

You can delete a cavity from an inline pair.
Procedure
1. Right-click on the cavity in the Design Browser (Design tab) and select Delete from the
pop-up menu.
2. The cavity name is removed from the list. Click the OK button.
Related Topics
Inline Pair
Mating Disconnected Inline Pair Halves

You can mate (join together) two disconnected halves of an inline pair.
Procedure
In the diagram window, drag an inline half up to the other inline half. If you are editing the
Capital Integrator design in multi user mode, you must have a lock on both halves for this to
work.

February 2016
Connectors
Disconnecting the Halves of an Inline Pair
Related Topics
Inline Pair

You can disconnect two halves of an inline pair.
Procedure
1. In the diagram window, right-click on one half of the inline pair and select the
Disconnect Selected option from the pop-up menu. Alternatively, click on one half,
press Space Bar and enter Disconnect Selected. If you are editing the Capital Integrator
design in multi user mode, you must have a lock on both halves for this to work.
2. The two halves disconnect and you can drag them apart in the diagram.
Related Topics
Inline Pair
Mating Disconnected Inline Pair Halves
Interface Connector
An overall vehicle design may be split between multiple organizations (for example, the engine
harness may be designed by a sub-contractor). The two, or more, teams agree on an interface
between separate areas of the vehicle and then design their own areas autonomously. The
interface is defined as an interface connector.
In Capital Integrator, you can place an interface connector which then acts just like a device (so
wiring synthesis routes directly to it).
An interface connector is not an inline connector. It is a generic connector and is not specified
as a receptacle or plug.
An interface connector terminates a harness. It acts much like an inline connector half. For
example, you can:
• Connect it to one bundle end only

• Add/delete cavities
• Add/delete backshells and backshell terminations
• Assign a library part
• Assign rules

February 2016
Connectors
Interface Connector
• Add or move wires

• Move a splice to it for a multiterm
• Refine the connector
An interface connector connects only to a bundle end. That means, a bundle connected to the
interface connector stops right there and does not associate to any objects beyond the interface
connector boundary.
When you synthesize wiring, wires are routed up to an interface connector and an interface
connector can act like an originating signal source with regard to routing. To make this happen,
you must map signals and, if required, option expressions on the cavities and backshell
terminations of an interface connector. The router treats these cavities or terminations (with
signals and options) on the interface connector as additional target points when generating
wiring.
Interface connectors can be included in a connectivity report. See “Creating a Set of

Customized Connectivity Reports” on page 424 for more information.
If you use Capital AutoView Assist for Integrator to generate a wiring design based on wiring
data that includes interface connectors, plug connectors are used for the interface connectors in
the generated design. See “Capital AutoView Assist for Integrator” on page 551 for more
information about using Capital AutoView Assist for Integrator.
Note
In Capital Project, you can use the default naming and advanced naming functionality for
interface connectors. See the Capital Project help system for more information about these.
Mapping Signals and Option Expressions to a Cavity

You can map one, or more, signals to a cavity of an interface connector. If necessary, an option
expression can be specified for a signal that is mapped to a cavity.
For example:
In a Capital Logic design, there are three functional devices connected with two nets. One
device has two pins and each has an option assigned.

February 2016
Connectors
Interface Connector
In Capital Integrator, there are two projects that contain slots with the functional devices placed
in them. The design from Project-2 has an interface connector that does not know anything
about the functional device placed in the design from Project-1.
The interface connector splits the whole topology into two areas (designs), therefore the
Project-2 design does not inherit any OPT-A or OPT-B information from the functional device
pins.
If you want the wires that are generated for both signals to connect to CAV2, both signals must
be assigned to CAV2 in the interface connector definition.
In addition, to prevent the wires of different signals being shorted together, the system must be
able to control when a wire is active for a particular configuration. This is done by associating
the relevant options to the signal/cavity mapping in the interface connector definition.
Interface Connector Design Flow

1. Add an interface connector to the Capital Integrator design. See “Adding an Interface
Connector to a Diagram” on page 157.
2. Place devices in the slots to create the associated signals in Capital Integrator.
3. Select the interface connector and specify the required interface. This includes:
o The number of cavities on the interface connector. This can be done by assigning a
part number to the connector (see “Assigning a Library Part to an Object” on
page 274) or by manually adding cavities (see “Adding a Cavity to a Connector” on
page 162). If a library part is assigned to a connector, you cannot add any extra
cavities.
o The backshell and backshell terminations on the interface connector. See “Adding a
Backshell to a Connector” on page 170 and “Adding a Backshell Termination to a
Connector” on page 171.

February 2016
Connectors
Adding an Interface Connector to a Diagram
o The signal to be routed at each cavity or termination. You use a signal map facility
for interface connectors to do this. See “Connector Refinement and Signal Mapping”
on page 209.
o If required, an option expression for a cavity, defining under what circumstance the
specified signal is present. You use a signal map facility for interface connectors to
do this. See “Connector Refinement and Signal Mapping” on page 209.
Note
You can export the interface connector definition as an XML file for use by other
users (this is optional). The XML file contains just one interface connector
definition that includes the connector name, names of cavities, and signal/option
expression mappings for each cavity. See “Exporting an Interface Connector
Definition” on page 159 for more information.
If an interface connector definition has been created and exported from another
installation, you can import it rather than specifying it yourself. Any options in the
XML file must exist in the project and there must be no duplicate signals mapped to
the same cavity; otherwise the import aborts. See “Importing an Interface Connector
Definition” on page 159 for more information.
4. Synthesize wiring either manually or using composite wiring synthesis. In both cases,
the router treats the pins on the interface connector like routing targets, taking note of
the specified signal and option expression.
5. You can refine the connector using the Refine Connector facility. This is optional.
Note
When you refine an interface connector, you must have knowledge of the interface
connector definition that is used in the other area of the vehicle design because the
Refine Connector facility cannot provide you with this information. Refinement
information is not included in the XML file when you export an interface connector
definition.
Related Topics
Exporting an Interface Connector Definition
Importing an Interface Connector Definition

An overall vehicle design may be split between multiple organizations (for example, the engine
harness may be designed by a sub-contractor). The two or more teams agree on an interface
between separate areas of the vehicle and then design their own areas autonomously. The
interface is defined as an interface connector.

February 2016
Connectors
See “Interface Connector” on page 154 for more information about interface connectors and the
design flow for working with them.
You can add an interface connector anywhere in a diagram.
Procedure
1. Press Space Bar and enter Add Inteface Connector.
2. A grayed-out image of an interface connector is displayed next to the cursor on the
diagram.
Click once to place the interface connector.

An interface connector connects only to a bundle and snaps to an unconnected bundle
end if you position the connector over the bundle end. The interface connector aligns
itself according to the bundle direction.
While moving an interface connector to the position where you want to place it, you can
flip the graphic by pressing the F key on your keyboard or rotate it by pressing the R
button on your keyboard. You cannot flip or rotate the connector after you have placed
it.
3. The interface connector is added to the diagram window and to the Design Browser
(Design tab).
Related Topics
Interface Connector

February 2016
Connectors

You can export an interface connector definition as an XML file for use by other users (this is
optional). The XML file contains just one interface connector definition that includes the
connector name, names of cavities, names of backshells and terminations, and signal/option
expression mappings for each cavity/termination.
Procedure
1. Right-click on the interface connector for which you want to export the definition and
select the Export Interface Connector Definition option from the pop-up menu.
Alternatively, click on the interface connector, press Space Bar and enter Export
Definition.
2. The Export Interface Connector Definition facility is displayed. Browse to the folder
where you want to save the interface connector definition file (XML file) and click the
Export button.
3. Any messages are displayed on the Export tab in the Capital Integrator Output Window.
Related Topics
Interface Connector

If an interface connector definition has been created and exported from another installation, you
can import it rather than specifying it yourself.
Note
Any options in the XML file must exist in the project and there must be no duplicate signals
mapped to the same cavity or backshell termination; otherwise the import aborts. Any
signals in the XML file with names that do not match the signals from the design are created as
new signals when imported. If there is a library part assigned to the interface connector, and the
number of cavities in the XML file is not equal to the one in the connector or there is any cavity
name in the XML file that does not have a match in the connector, the existing library part on
the connector is removed.

February 2016
Connectors
During the import, the system tries to reuse any existing cavities/terminations, delete extra
cavities/terminations, and create new cavities/terminations as necessary. The prioritized
algorithm for matching cavities/terminations in the XML with existing ones are:
• Match both the name and any signal name on the cavity/termination
• Match name
• Match any signal name on the cavity/termination
• Pick any cavity/termination
After the cavity/termination matching, the cavity/termination name on the connector may be
renamed by the definition from the XML file (if necessary).
Example scenarios:
S4W1 is not mapped to either Cavity 2 or Cavity 3 as now there are option restrictions.
S1W1, S2W2 are dangling or deleted.
Both S1W1 or S1W2 can map to Cavity 3.
S3W1 can be mapped to Cavity 1 as there is no option restriction now.
S4W1 is not mapped as the options are different now.

February 2016
Connectors
S2W1 is dangling or deleted.
S4W1 is mapped to either Cavity B or Cavity C.
Note
When existing cavities are deleted, any wires connected to the cavities are also deleted if the
wiring signal does not have a functional source net conductor in the associated logical
design. After a cavity is deleted, if there is a signal that does not have any wiring nor functional
source nets and is not mapped to any cavities of other interface connectors, the signal is
removed automatically from the design. The name matching for options, signals or cavities is
case-insensitive. After the import, you can edit the definition (that is, add/delete cavities, and so
on). The import action can be undone.
Procedure
1. Right-click on the interface connector for which you want to import a definition and
select the Import Interface Connector Definition option from the pop-up menu.
Alternatively, click on the interface connector, press Space Bar and enter Import
Definition.
2. The Import Interface Connector Definition facility is displayed. Browse to the
interface connector definition file (XML file) and click the Import button.
3. Any messages are displayed on the Import tab in the Capital Integrator Output
Window. The imported definition replaces the definition that was on the interface
connector.
Related Topics
Interface Connector

February 2016
Connectors
Common Editing Tasks for Multiple Connector Types
Common Editing Tasks for Multiple Connector

Types
There are various editing tasks that apply to multiple types of connector (virtual, interface,
inline).
Deleting a Cavity from a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Copied Data When Cloning a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

You can add a cavity to a connector manually.
Note
If you are editing the cavities of an inline pair, see “Adding a Cavity to an Inline Pair” on
page 153.
If a library part is assigned to a connector, you cannot add cavities because the library part
controls the number of cavities.
Otherwise, after you have added a connector to a slot or after you have added an interface
connector to a diagram, you can add cavities to the connector.
In the first scenario, when a device is then placed in that slot, you can select which cavity each
signal from the device passes through. See “Connector Refinement and Signal Mapping” on
page 209.
Procedure
1. Right-click on the connector in the Design Browser (Design tab) or diagram window
and select Add Cavity from the pop-up menu. Alternatively, click the connector in the
Design Browser (Design Tab) or diagram, press Space Bar and enter Cavity.
2. A new cavity is added to the list of cavities in the Design Browser (Design tab).
Note
This functionality is disabled if the connector has been refined. See “Connector
Related Topics
Slot Connector

February 2016
Connectors
Deleting a Cavity from a Connector
Interface Connector

You can delete a cavity from a connector.
Note
If you are editing the cavities of an inline pair, see “Deleting a Cavity from an Inline Pair”
on page 153.
If a library part is assigned to a connector, you cannot add cavities because the library part
controls the number of cavities.
Procedure
1. Right-click on the cavity in the Design Browser (Design tab) and select Delete from the
pop-up menu.
2. The cavity name is removed from the list. Click the OK button.
Note
A cavity cannot be deleted if it has wiring connected. If there are signals defined on
the cavity without their wiring, you can delete the cavity.
Related Topics
Slot Connector
Interface Connector
Cloning and Replicating Connectors

You can copy cavity definitions from a selected virtual, inline or interface connector and how to
paste that data to an inline or interface connector. The cavity definitions can be copied within a
designs and between designs.
For a list of the data that is copied, see “Copied Data When Cloning a Connector” on page 164.
Procedure
1. In the Design Browser (Design tab) or Diagram Window, right-click the virtual, inline
or interface connector from which you want to copy data and select Clone Cavities.
2. Right-click on the inline or interface connector in which you want to replicate the data
and select Replicate Cavities.

February 2016
Connectors
Copied Data When Cloning a Connector
The target connector is modified with the copied data.

Related Topics

When you use the Clone Cavities action to copy cavity definitions from a virtual, inline or
interface connector, certain data is copied.
The copied data includes:
• cavity names
• backshell termination names
• signal mappings for backshell terminations and cavities (including inline preferred
signal and option expression mappings for interface connectors), see below for
examples of how signal mappings are modified on the replicated connector.
• rules on the connector and children objects
• cavity attributes/properties
The copied data does not include:
• graphical properties
• connector names
• backshell names
• connector refinement data
• connector attributes/properties
Modified Signal Mappings

When signal mapping data is replicated in a connector, object types and names (but not actual
objects) are compared. For example, when comparing a signal mapping for a backshell
termination, both the signal name and signal type must match.

February 2016
Connectors
Figure 7-1. Example Modification of Signal Mapping for Replicated Connector

(1)
• In the above example, target signal S1 has the same mapping as the source signal S1. In
addition, a signal such as S1 here will always be assigned as the preferred signal in the
target.
• The source signal S222 is assigned to target signal S2; target cavity CAV22 is renamed
to CAV2.
• Target old signal mappings for signals S33, S44, S55 and S77 are removed because they
do not match the source mappings. That means, wires on those target cavities are
disconnected. The leftover cavities are unused.
• Target signal SD1 maps to an unused cavity that is renamed to CAV6; backshell
termination BK1 is removed and wiring connected to BK1 connects to CAV6.
• The target old mapping has no S3 signal. The source mapping has a preferred signal
S333. In the target new mapping, signal S333 is mapped to an unused cavity that is
renamed to CAV3. In this case, S3 is not used as the preferred signal.
• In the target new mapping, an unused cavity is renamed to CAV4 and signal S4 is
mapped to it as the preferred signal to match the source mapping.
• In the target new mapping, an unused cavity is renamed to CAV5 with no signal to
match the source mapping.
• Extra cavity CAV7 is deleted in the target new mapping.
(2)
• In the above example, signal S1 has three source mappings but the target old mapping
lists signal S1 just once. The target new mapping contains two new mappings with S1 as
the preferred signal.

February 2016
Connectors
• In the source mapping, backshell termination BK1 has two mappings. In the target old
mapping, BK1 has not match. In the target new mapping, the mapping for signal SD33
is removed along with the connecting wiring. No preferred signal can be assigned to a
backshell termination.
(3)
• In the above example, the target old mapping for signal S2 partly matches the source
mapping for cavity CAV1. In this case, the signal S1 is not assigned to CAV1 in the
target new mapping.
• In the target new mapping for CAV2, signal S3 or S4 can be assigned as the preferred
signal.
• The target old mapping for signal SD2 partly matches the source mapping for backshell
termination BK1. In this case, the signal SD1 is not assigned to BK1 in the target new
mapping.
(4)
• In the above example, the option expression in the target interface connector is replaced
by the source option expression if the source data is from an interface connector;
otherwise, any option expressions on the target mapping are removed.
• In the target new mapping, signals S3 and S4 are added and mapped to the cavity CAV3.
Note
When copying connector data between designs, it is possible that a design
containing a target connector does not contain all of the signals listed in the source
data. If the target is an inline connector, the resulting mapping will list the signal as a
preferred signal (the entry is just a string and no actual signal is created). If the target is
an interface connector a new signal is created for the new mapping as long as the signal
type is not a shield.
Related Topics
Cloning and Replicating Connectors

February 2016
Connectors

You can specify a route code for a connector.
The route code is not used in Capital Integrator but is used in Capital HarnessXC, for example,
to distinguish between slot connectors when there is more than one slot connector combined
with a slot. If there are multiple harnesses entering the connector, you can specify a different
route code for the connector on each harness.
Procedure
1. Right-click on the connector in the Design Browser (Design tab) or diagram window
and select Properties; the Edit Properties dialog box is displayed.
2. Click the Routes tab, specify the Route Code and click OK.
Backshells and Backshell Terminations

In Capital Integrator, there are various actions that you can perform for a backshell.
You can:
• select a backshell part number and backshell terminations for a slot connector, inline
connector or interface connector.
• select which shield terminations terminate at backshell terminations instead of a slot
connector or inline connector.
• use the backshell/connector association when defining harness connector footprints.
• use the Backshell Termination by Attribute/Property and Pigtail Usage by
Attribute/Property constraints to define backshell termination rules for slots so that
wiring synthesis takes backshells into consideration. See “Overview of Rules and
Constraints” on page 287 for more information about these constraints.
Holes cannot have backshell terminations.
If a backshell symbol has been associated with the backshell library part in Capital Library,
Capital AutoView Assist for Integrator does not use the backshell symbol when generating
wiring diagrams.
Backshell Terminations Design Flows

Flow without a harness connector footprint
1. You create a functional Capital Logic design and terminate multicore shield
terminations to a pin on a device.

February 2016
Connectors
2. You create a Capital Integrator design, associate the logical design and place devices
according to the rules and constraints defined for slots.
3. Designate connector cavities to be used as backshell terminations.
Note
There can be only one backshell on a single connector but there can be multiple
backshell terminations.
There are two ways to do this:

o Add a Backshell Termination by Attribute/Property constraint to slot connectors
and inline connectors. See “Overview of Rules and Constraints” on page 287 for
more information about using rules and constraints.
When placing a device, the system examines this constraint to determine when and
how backshell terminations are used instead of normal cavities. Any backshell
terminations are indicated in the Signal Map facility for the slot. See “Connector
o Manually add backshell terminations to slot connectors and inline connectors. See
“Adding a Backshell Termination to a Connector” on page 171.
4. Select the appropriate slot connector or inline connector and assign a connector part
number, appropriate backshell and backshell terminations.
Backshells are displayed in the Design Browser (Design tab) under the slot connector or
inline connector.
Note
Designated cavities that belong to the same backshell are electrically connected in
the signal map. If you select more backshell terminations than there are designated
cavities, new designated cavities are created and the signal map is updated accordingly.
5. Synthesize wiring. Any constraints that have been added to objects are taken into
account and these decide whether backshell terminations are created. Note that this step
could be run before step 4 and would have to be run before step 4 in the case of inline
connectors because inline cavities are not created until wiring synthesis is performed.
When the router determines that a shield needs to terminate at a particular cavity, the
cavity is examined to see if there is a Backshell Termination rule on the backshell
termination (or above in the rule-hierarchy). If so, the rule is used to determine if the
connection will be made with a pigtail or not. By default, a pigtail is used.
Wires that route to the designated backshell cavities are connected to physical backshell
terminations instead of the connector pins.

February 2016
Connectors
When wiring is synthesized, the necessary cavities may not exist yet (for example, on an
inline). In this case, the connector is examined for rules to determine if, and how, a
shield conductor should terminate.
For slot connectors on slots, the backshell terminations are expected to have been
created already (as in step 3 of this design flow).
For inline connectors and junction boxes, the backshell terminations probably will not
exist prior to wiring synthesis. The backshell termination rule on the inline connector (or
above in the rule hierarchy) is used to determine if backshell terminations are used for
terminating a signal on an inline.
The Signal Map facility can be used to edit the mappings after synthesis. See
“Connector Refinement and Signal Mapping” on page 209 for more information about
this facility.
6. Optionally, change the pigtail type termination to a regular shield termination. See
“Modifying a Shield Termination” on page 505.
Flow with a harness connector footprint
1. Create a harness-side device footprint in Capital Library.

2. Create a functional Capital Logic diagram that uses devices with the harness-side device
footprint.
3. You create a Capital Integrator design, associate the logical design and place devices
according to rules and constraints defined for slots.
When the devices with footprints are placed in Capital Integrator, the system recognizes
the default backshells with all their terminations and designates corresponding cavities
on the slot connectors. The system determines backshell usage based on Integrator rules
and constraints, not library information.
Backshells are displayed in the Design Browser (Design tab) under the slot connector or
inline connector.
Signal mapping information is restricted if library parts are assigned.
Design Rule Checks Related to Backshells

You can run design rule checks to determine if there are rule conflicts on cavities. See “Running
Design Rule Checks Manually” on page 73 for more information about running checks. The
following checks can be run with regard to backshells:
• Signals that break backshell usage rule

Identifies backshells where a cavity should be used according to assigned rules and
constraints.
• Signal that breaks pigtail usage rule

February 2016
Connectors
Adding a Backshell to a Connector
Identifies signals that connect using a pigtail, where no pigtail should be used according
to assigned rules and constraints.
Also identifies signals that connect without a pigtail, where a pigtail should be used
according to assigned rules and constraints.
Related Topics
Deleting a Backshell from a Connector
Adding a Backshell Termination to a Connector
Deleting a Backshell Termination from a Connector

You can add a backshell to a slot connector, inline connector or interface connector.
Procedure
1. Right-click on the connector in the diagram window or in the Design Browser (Design
tab) and select the Add Backshell option from the pop-up menu. Alternatively, click the
connector, press Space Bar, and enter Backshell.
2. The backshell is listed under the connector in the Design Browser (Design tab).
3. If you want to add a backshell termination, right-click on the connector or backshell in
the diagram window or in the Design Browser (Design tab) and select the Add
Backshell Termination option from the pop-up menu. Alternatively, click the
connector or backshell, press Space Bar, and enter Backshell Termination.
4. The backshell termination is listed under the backshell in the Design Browser (Design
tab).
Related Topics

You can delete a backshell from a connector.

February 2016
Connectors
Procedure
1. Right-click on the backshell in the Design Browser (Design tab) and select Delete from
the pop-up menu.
2. The backshell is deleted.
Related Topics
Adding a Backshell Termination to a

Connector
If you are working with backshells in Capital Integrator, you must create any required backshell
terminations on slot connectors, inline connectors and interface connectors before synthesizing
wiring.
See “Backshells and Backshell Terminations” on page 167 for more information about
backshell terminations and the possible design flows for working with them.
Procedure
1. Right-click on the connector or its backshell in the diagram window or in the Design
Browser (Design tab) and select the Add Backshell Termination option from the pop-
up menu. Alternatively, click the connector or its backshell, press Space Bar, and enter
Backshell Termination.
2. The backshell termination is listed under the backshell in the Design Browser (Design
tab). If no backshell was on the connector, one is created and the termination is listed
under it.
Related Topics

February 2016
Connectors
Deleting a Backshell Termination from a

Connector
You can delete a backshell termination from a connector.
Procedure
1. Right-click on the backshell termination in the Design Browser (Design tab) and select
Delete from the pop-up menu.
2. The backshell termination is deleted.
Related Topics

February 2016
Chapter 8
Devices
This chapter contain details about how to place devices in slots and how to edit slots and the
devices placed in them.
Placement of a Device or Ground Device in a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Optimized Ground Placement. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Placement of Devices with Footprints in Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Manually Placing a Normal or Ground Device in a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Automatically Placing all Unplaced Normal Devices from a Particular Logical Design. . 184
Automatically Placing all Unplaced Ground Devices from a Particular Logical Design. . 185
Automatically Placing all Unplaced Ground Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Unplacing all Placed Devices from a Particular Logical Design . . . . . . . . . . . . . . . . . . . . 187
Mapping of Connectors and Cavities when Placing a Device in a Slot. . . . . . . . . . . . . . 188
Combining Normal Devices in a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
Combining Ground Devices in Selected Ground Slots. . . . . . . . . . . . . . . . . . . . . . . . . . . 191
Combining Ground Devices in All Ground Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Defining Footprints on Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Reevaluation and Updating of Footprints when Changes Are Made . . . . . . . . . . . . . . . . . 196
Implementing Grounds in the Generative Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Grounds and Ground Wiring Flow Using Ground Design Functionality. . . . . . . . . . . . . . 198
Grounds and Ground Wiring Flow Using Shared Objects . . . . . . . . . . . . . . . . . . . . . . . . . 202
150% Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

February 2016
Devices
Placement of a Device or Ground Device in a

Slot
A slot represents a physical piece of equipment that can contain one or more logical devices.
After you have associated a logical design with the topological design, you can place one or
more devices from the logical schematic in each slot. Ground devices can be placed in slots with
the slot type Equipment, Junction Box, or Ground. Normal devices can be placed only in
slots with the slot type Equipment or Junction Box.
When you create a slot in a diagram, it has the following constraint by default:
When devices are placed in slots automatically, this constraint specifies that any devices with
the same Object Name as the slot will be placed in that slot. You can edit or remove this
constraint for a slot as required.
See “Overview of Rules and Constraints” on page 287 for more information about constraints.
Once you have placed devices in a slot, you can combine two or more devices. See “Combining
Normal Devices in a Slot” on page 189 for more information. Devices with footprints cannot be
combined with any other devices.
A device can be manually placed in more than one place in a topology but must be mutually
exclusive. For example, a battery may be placed in a particular slot in one variant option but be
placed in a different slot in another variant option.

Optimized Ground Placement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Placement of Devices with Footprints in Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Manually Placing a Normal or Ground Device in a Slot . . . . . . . . . . . . . . . . . . . . . . . . . 182
Automatically Placing all Unplaced Normal Devices from a Particular Logical Design 184
Automatically Placing all Unplaced Ground Devices from a Particular Logical Design 185
Automatically Placing all Unplaced Ground Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Unplacing all Placed Devices from a Particular Logical Design . . . . . . . . . . . . . . . . . . . 187

February 2016
Devices
Placement of Normal Devices in Slots

When you place normal devices, you can do the one of the following actions.
• manually place one normal device at a time. See “Manually Placing a Normal or Ground
Device in a Slot” on page 182.
When you manually place a device, you have the option of using manual variant-based
placement.
A device can be manually placed in more than one slot in a topology depending on the
variant options. For example, a battery may be placed in a particular slot in one variant
option but be placed in a different slot in another variant option.
After variant-based placement has been used on a device, you can view which variant
option applies to a device in a slot by positioning the mouse cursor over the device in the
Design Browser (Design tab) Tree and holding it there.
• automatically place one normal device at a time. See “Automatically Placing a Normal
Device in a Slot” on page 183.
• have the system place all available unplaced normal devices from a particular logical
design simultaneously. See “Automatically Placing all Unplaced Normal Devices from
a Particular Logical Design” on page 184.
• have the system place all available unplaced normal devices for all associated logical
designs simultaneously. See “Automatically Placing all Unplaced Normal Devices” on
page 184.
If you place all devices simultaneously or automatically place a single device, the system uses
the rules and constraints that you have defined to select the slots in which it places the devices.
These can include the “Option place by Attribute/Property” constraint that allows you to specify
whether objects with a particular property or attribute should or cannot be placed conditionally
with an option expression in a slot. This enables the automatic variant-based placement of an
object in multiple slots. During the automatic placement of devices, a device is placed in any
slots where it matches this constraint and the option expression from this constraint is applied to
the placed device. See “Overview of Rules and Constraints” on page 287.
Related Topics
Placement of Ground Devices in Slots
Optimized Ground Placement
Placement of Devices with Footprints in Slots
Manually Placing a Normal or Ground Device in a Slot
Automatically Placing a Normal Device in a Slot
Automatically Placing all Unplaced Normal Devices from a Particular Logical Design

February 2016
Devices
Automatically Placing all Unplaced Normal Devices

Automatically Placing all Unplaced Ground Devices from a Particular Logical Design
Automatically Placing all Unplaced Ground Devices
Unplacing a Placed Device from a Slot
Unplacing all Placed Devices from a Particular Logical Design
Unplacing all Placed Devices
Unplacing all Placed Ground Devices

Ground devices are placed separately from other devices since their optimal location will
depend on the physical location of any connected devices.
See “Grounds and Ground Wiring Flow Using Ground Design Functionality” on page 198 for
more information about the overall workflow when using ground devices.
You can either:
• manually place ground devices one at a time. See “Manually Placing a Normal or
Ground Device in a Slot” on page 182.
When you manually place a device, you have the option of using manual variant-based
placement. You may want to variantly place a ground device because its connected
device is variantly placed.
A device can be manually placed in more than one slot in a topology depending on the
variant options. For example, a battery may be placed in a particular slot in one variant
option but be placed in a different slot in another variant option.
After variant-based placement has been used on a device or ground device, you can view
which variant option applies to a device in a slot by positioning the mouse cursor over
the device in the Design Browser (Design tab) Tree and holding it there.
• have the system place all available unplaced ground devices from a particular logical
design simultaneously or place all available unplaced ground devices for all associated
logical designs simultaneously.
See either:
o “Automatically Placing all Unplaced Ground Devices from a Particular Logical
Design” on page 185.
o “Automatically Placing all Unplaced Ground Devices” on page 185.

February 2016
Devices
If you place all ground devices simultaneously or automatically place a single ground device,
the system uses the rules and constraints that you have defined to select the slots in which it
places the ground devices.
These can include the “Option place by Attribute/Property” constraint that allows you to specify
whether objects with a particular property or attribute should or cannot be placed in a slot and be
assigned a particular option expression (see “Overview of Rules and Constraints” on page 287
for general information about using constraints).
Each ground device being placed is treated in the following ways:
• If there are one or more “Option place by Attribute/Property” constraints that match the
ground device, it is placed in all these matching slots with the specified variant option
expression. This occurs regardless of whether any attached, non-ground devices have
been placed yet. If there are two or more connectors, the connector is chosen using
Optimized Ground Placement. If you do not have a license for optimized ground
placement, the device is still placed but it is mapped to one of the connectors without
using ground optimization. This is exactly what happens when you place a normal
device in a slot with multiple connectors.
• If there is a single “Place by Attribute/Property” constraint that matches the ground
device, it is placed accordingly, regardless of whether any attached, non-ground devices
have been placed yet.
• If there are multiple “Place by Attribute/Property” constraints that match the ground
device, it is placed according to Optimized Ground Placement. If you do not have
Optimized Ground Placement available, the ground device is not placed and a warning
is generated.
• If placement of a ground device fails, a message is displayed on a Placement tab in the
Output Window. It details the name of the device and the reason it could not be placed.
Note
The Ground device that breaks placement rule and Placement conflict design
rule checks are available to identify any issues after the placement of ground
devices.
Related Topics

February 2016
Devices

This is licensed functionality. If you do not have the appropriate license, optimized ground
placement is not available.
It occurs when there are multiple slots with “Place by Attribute/Property” constraints that match
a ground device and at least one attached, non-ground device has been placed. Optimized
Ground Placement takes into account variant placement of the attached non-ground devices as
well as options on the ground slots, which may result in a single ground device being placed
multiple times.
Considering this functionality at a high-level, when a device is variantly placed in the vehicle, it
may be desirable to ground it at different points in each variant. In addition, some ground points
may only be available in certain vehicle configurations (controlled by putting an option on a
slot).
The following is a low-level, detailed description of the steps that optimized ground placement
follows:
• Identifies the number of placement contexts that are required

This is done by considering the variant placement expressions on the attached devices as
well as the options on all slots that match the ground device.
Each placement context is a unique combination of the variant placement expressions,
but unsupported combinations (exclusive options or options that cannot appear together)
are ignored.
If there are no variantly-placed, attached devices and no options on the matching ground
slots, there is a single placement context.
• Variant placement of ground devices

February 2016
Devices
For each placement context, it is necessary to place the ground device once at most:
o The activeness of the attached device pins is determined by applying the placement
context. Any options on the functional device pins that have not been considered (for
example, because they have not been used in variant placement expressions or on the
ground slots) are assumed to be true. In other words, a device pin is considered
active unless it has been explicitly set as inactive by one of the options in the
placement context. If none of the attached devices is active, the placement context is
skipped.
o The optimal ground position is determined using wiring synthesis. However, since
there is a context for this, no routing through non-applicable bundles occurs and the
ground device is not placed in a non-applicable slot. Exclusive option relationships
are used to determine this applicability.
o Once the optimal ground slot is found, the ground device is placed using the
placement context as its variant placement expression.
o Placement then moves on to the next placement context. If the ground device is
placed in a slot where it has already been placed for a previous context, the
placement Option Expressions are combined using OR and are simplified.
For example:
Ground device G1 is connected to a non-ground device DEV1. DEV1 has a logical option
expression of ABS.
DEV1 is variantly placed as LHD and RHD. LHD and RHD are marked as mandatory
exclusive.
There are three matching ground slots with options LHD, RHD and ‘none’ (that is, a slot with
no option expression).
The placement contexts are calculated as unique, supported combinations of the variant
placements and ground slot options. Therefore, the contexts are LHD and RHD.
Placement will place the ground device once at most for each context LHD and RHD.
For the first placement context LHD:
The placement of the ground device is determined using the lowest cost algorithm. However,
the placement context must be used (so it must not route through a RHD bundle for example).
The optimal ground slot might either be LHD or ‘none’. In either case, the ground device is
placed and tagged with the variant placement expression LHD.

February 2016
Devices
For the second placement context RHD:
The optimal ground slot might either be RHD or ‘none’. There are several possibilities
depending on where the ground device was originally placed:
• If the optimal slot is RHD, the ground device is placed and tagged with the variant
placement expression RHD.
• If the optimal slot is ‘none’ and the original placement was in the LHD slot, the ground
device is placed and tagged with the variant placement expression RHD.
• If the optimal slot is ‘none’ and the original placement was also in this slot, the ground
device variant placement expression is changed from LHD to LHD||RHD.
Related Topics

When a device with a footprint is placed in a slot, the appropriate number of slot connectors on
the slot are associated with the device automatically. Those slot connectors are mapped to the
connectors from the footprint. If necessary, new slot connectors are created accordingly to
provide the required mapped connectors.
You can place multiple devices with footprints in a slot. This enables you to place devices that
are normally mutually exclusive but have similar connectivity in the same slot. For example,
two different radios may be available in a vehicle. The radios have some connectivity in
common but also have some different connectivity. It is desirable to place both radios in the

February 2016
Devices
same slot so that any common wiring can be synthesized once, rather than having duplicate
wires.
The placing of multiple device with footprints also supports a scenario where a slot represents a
cabinet or room. In this case, the devices might not be mutually exclusive and will have entirely
separate slot connectors for each device.
Capital Integrator requires a Capital Logic footprint to be well-defined when it attempts to place
a device. Otherwise, a warning is generated and the placement action is aborted.
Capital Integrator cannot place a device if pins from the library definition have not been mapped
to the connectors. It also cannot place a device if it has fewer pins than are defined in the library
footprint.
However, Capital Integrator can place a shared device if the instances of the device have fewer
pins than in the library footprint because a shared device definition should have the correct
number of pins (even if the instances do not). Therefore, if you want to place a device with
fewer connectors and pins than it has defined in its footprint, you must promote the device to a
shared device first.
If a device in a slot has a footprint, the footprint name is displayed on the General tab of the
Edit Properties Dialog Box for the device. You cannot edit any signal to pin associations for the
footprint because this information is set when the device is placed in the slot.
Related Topics

February 2016
Devices
Manually Placing a Normal or Ground Device in a

Slot
You can manually place a normal or ground device in a slot.
Video
In addition to the instructions below, you can drag and drop devices to place them in slots.
See the video “Placing Devices Using Drag and Drop”.
Procedure
1. Right click on the normal device or ground device in the Logical Designs Browser
(Function tab) and select Place Device. Alternatively, click on the device in the Logical
Designs Browser (Function tab), press Space Bar and enter Place Device. The symbols
for unplaced devices are grayed out in the Logical Designs Browser (Function tab).
2. Any slots already containing devices that are connected to the device to be placed are
highlighted in red in the diagram window. A list of slots is displayed in a Place Device
Dialog Box. The slots are split into the following groups:
• Slots with Matching Rule
Slots with rules that say the device should be placed here.
• Slots without Applicable Rule
Slots with no rules that relate to the device. The device could be place in one of
these.
• Slots with Conflicting Rule
Slots with rules that say the device should not be placed here.
Click on the slot in which you want to place the device.
Note
When placing a ground device, you can show or hide all non-ground slots by
toggling the Show device (non-ground) slots option: indicates that all slots
(including non-ground slots) are displayed currently, indicates that only ground slots
are displayed currently.
3. If you do not want to perform a manual variant-based placement of a device, skip to step
5.
If you want to perform a variant-based placement of a device, you enter an expression in
the Expression box at the bottom of the Place Device facility. You can either enter the
expression manually or click the ellipsis button (...) to display the Edit Option
Expression Dialog Box that aids you in creating an option expression.

February 2016
Devices
Performing a variant-based placement is distinct from using the Edit Properties Dialog
Box to add an option expression to a functional device itself in Capital Logic because
that would affect all instances of that device.
Whenever an expression is entered during placement, this is treated as a variant-
placement even when the option expression includes non-variant options. When variant-
based placement has been used for a device, its symbol is slightly different in the Design
Browser (Design tab). It looks like a device overlaid by a second device .
Variant-Based Placement
Devices placed using variant-based placement can be placed in more than one slot.
There is no check to ensure that the option expressions for multiple variant placements
are mutually exclusive or exhaustive.
Composite Wiring Synthesis takes into account any options used in variant-placement
when promoting options.
For devices placed in junction box slots, any options on the device are promoted to all
harnesses connected to the junction box.
After variant-based placement, the General tab of the Edit Properties Dialog Box for a
device displays the Expression field under the heading Placement to distinguish the
option expression from regular option tagging.
4. If you are placing a device with a footprint, use the Connector Map tab to map the
footprint connectors to the harness and device connectors on the slot. By default, a new
harness connector is created for each footprint connector and has the same name. You
can rename the new connectors later.
6. The symbol for the device is no longer grayed out in the Logical Designs Browser
(Function tab) and the device is added to the Design Browser (Design tab).
Related Topics
Mapping of Connectors and Cavities when Placing a Device in a Slot

You can automatically place a normal device in a slot.
Procedure
1. Right click on the device in the Logical Designs Browser (Function tab) and select
Auto-Place Devices. Alternatively, click on the device in the Logical Designs Browser
(Function tab), press Space Bar and enter Auto-Place Devices. The symbols for
unplaced devices are grayed out in the Logical Designs Browser (Function tab).

February 2016
Devices
2. The progress of the action is displayed. You can click the Stop button to abort the
placement of the device.
3. When the device has been placed, click the Close button. The symbol for the device is
no longer grayed out in the Logical Designs Browser (Function tab) and the device is
added to the Design Browser (Design tab).
Note
When you place a device with a footprint, the system maps each footprint to a new
or unused slot connector with the same default mapping as you would place it
manually. You can use the Connector Map facility to edit the mapping.
Related Topics

from a Particular Logical Design
You can automatically place all unplaced normal devices from a particular logical design in
slots.
Procedure
1. Right-click on the design name in the Logical Designs Browser (Function tab) and
select the Auto-Place Devices option from the pop-up menu. Alternatively, click on the
device in the Logical Designs Browser (Function tab), press Space Bar and enter Auto-
Place Devices.
placement of the devices.
3. When the devices have been placed, click the Close button. The symbols for the devices
are no longer grayed out in the Logical Designs Browser (Function tab) and the devices
are added to the Design Browser (Design tab).
Related Topics

You can automatically place all unplaced normal devices from the associated logical designs in
slots.

February 2016
Devices
Procedure
1. Press Space Bar and enter Auto-Place All Devices.
placement of the devices.
3. When the devices have been placed, click the Close button. The symbols for the devices
are no longer grayed out in the Logical Designs Browser (Function tab) and the devices
are added to the Design Browser (Design tab).
Related Topics

from a Particular Logical Design
You can automatically place all unplaced ground devices from a particular logical design in
slots.
Procedure
1. Click on the design name in the Logical Designs Browser (Function tab), press Space
Bar, and enter Auto-Place Grounds.
placement of the devices. When placing a ground device, the system maps signals to
cavities on the best connector in the slot. A cavity in the chosen connector already
associated with a signal on the device is reused, otherwise a new cavity is created for
each signal.
3. When the ground devices have been placed, click the Close button. The symbols for the
ground devices are no longer grayed out in the Logical Designs Browser (Function tab)
and the devices are added to the Design Browser (Design tab).
Related Topics

You can automatically place all unplaced ground devices from the associated logical designs in
slots.

February 2016
Devices
Procedure
1. Press Space Bar and enter Auto-Place All Grounds.
placement of the devices. When placing a ground device, the system maps signals to
cavities on the best connector in the slot. A cavity in the chosen connector already
associated with a signal on the device is reused, otherwise a new cavity is created for
each signal.
3. When the ground devices have been placed, click the Close button. The symbols for the
ground devices are no longer grayed out in the Logical Designs Browser (Function tab)
and the devices are added to the Design Browser (Design tab).
When you place a device, any signals associated with that device are added to the
Signals folder in the Design Browser (Design tab). They are placed in one of the
following sub-folders:
• Unrouted
Signals that are required for the active levels in the topological design but that have
not been routed yet.
• Unconnected
Signals that are not required for the active levels in the topological design and that
will not be routed.
Related Topics

You can unplace a device from a slot.
Procedure
1. Right-click on the device in the Logical Designs Browser (Function tab) and select
Unplace Devices from the pop-up menu. Alternatively, click on the device in the
Logical Designs Browser (Function tab), press Space Bar and enter Unplace Devices.
2. The symbol for the device is grayed out in the Logical Designs Browser (Function tab)
and the device is removed from the Design Browser (Design tab).
Related Topics

February 2016
Devices
Unplacing all Placed Devices from a Particular

Logical Design
You can unplace all placed devices (from a particular logical design) from the slots.
Procedure
1. Right-click on the design name in the Logical Designs Browser (Function tab) and
select Unplace Devices from the pop-up menu. Alternatively, click on the device in the
Logical Designs Browser (Function tab), press Space Bar and enter Unplace Devices.
2. The symbols for the devices are grayed out in the Logical Designs Browser (Function
tab) and the devices are removed from the Design Browser (Design tab).
Related Topics

You can unplace all placed devices (from all associated logical designs) from the slots.
Procedure
1. Press Space Bar and enter Unplace all Devices.
2. The symbols for the devices are grayed out in the Logical Designs Browser (Function
tab) and the devices are removed from the Design Browser (Design tab).
Related Topics

You can unplace all placed ground devices (from all associated logical designs) from the slots.
Procedure
1. Press Space Bar and enter Unplace All Grounds.
2. The symbols for the ground devices are grayed out in the Logical Designs Browser
(Function tab) and the ground devices are removed from the Design Browser (Design
tab). Any combined ground devices are uncombined.
Related Topics

February 2016
Devices
Mapping of Connectors and Cavities when

Placing a Device in a Slot
The system performs various mappings when devices are placed in slots.
• Mapping of Pins to Connectors
• Mapping of Pins to Connector Cavities When Placing Devices in Slots
• Mapping of Pins from Devices with Footprints
Mapping of Pins to Connectors

If a pin on a functional device has a value specified for its Connector Group attribute, the pin
is mapped to a slot connector with a name equal to that value. If such a connector does not exist,
a new slot connector is created with that name.
Mapping of Pins to Connector Cavities When Placing Devices in Slots

If a pin on a functional device has a value specified for its Connector Cavity attribute, the pin
is mapped to a cavity with a name equal to that value. This attribute is used only if the pin also
has a value specified for its Connector Group attribute. This mapping occurs even it shorts
another existing signal on the cavity. If a cavity with a matching name does not exist, one is
created. If a connector part restricts the creation of a new cavity, an existing cavity is used even
though the name does not match.
By default, each instance of a signal and the pin for that instance are mapped to different
cavities. You can use the Map To Same Cavity by Signal Attribute/Property constraint to
specify that multiple instances of a signal and the pins for that instance are mapped to the same
connector cavity. See “Overview of Rules and Constraints” on page 287 for more information
about using rules and constraints.
After you have placed devices and connector cavities have been mapped, you can:
• Update the signal map for a slot

This action evaluates whether signals are mapped to the correct slot connectors so that
harnesses are routed correctly. See “Grounds and Ground Wiring Flow Using Ground
Design Functionality” on page 198.
• Remove any unused connectors, holes and cavities from slots. See “Removing Unused
Connectors, Holes and Cavities from Slots” on page 262.
Mapping of Pins from Devices with Footprints

You can use the Assign Connector by Attribute/Property constraint either on a whole design
or on a slot. This controls whether a device connector with a particular value for an attribute or
property is mapped to a slot connector with an attribute or property that has the same value. See

February 2016
Devices
Combining Normal Devices in a Slot
“Overview of Rules and Constraints” on page 287 for more information about using rules and
constraints.
If no slot connectors have attributes or properties that match, the device connector is mapped
either to an existing re-usable slot connector or a new one is created if necessary.
When multiple devices with footprints are placed in the same slot:
• If their connector part numbers match, they share the slot connector map and signals can
be multi-termed
• If their connector part numbers do not match, a separate slot connector is created for
each device connector
Related Topics

Sometimes logical schematics contain two or more devices that could be the same device (that
is, a shared device).
For example, you may have drawn two systems that each contain a fuse. The systems could use
exactly the same fuse if they are fed from the same fuse box but this is not known until the fuses
are placed in the topological design.
Capital Integrator allows you to combine devices that you have placed in the same slot and
thereby merge signals from identical pins.
Devices with footprints cannot be combined with any other devices.
Procedure
1. Hold down the SHIFT key on your keyboard and click the devices to be combined in
the Design Browser (Design tab). Still holding down the SHIFT key, right-click one of
the selected devices and select Combine Devices.
2. The Combine Devices Dialog Box is displayed. Specify the Name that you want the
combined device to have.
3. Use the Pin Map to map the signals that terminate at the uncombined device pins to the
pins of the combined device. The table displays the following information for each
signal that terminates at the devices to be combined:
• Device
The uncombined device at which the signal terminates.
• Pin

February 2016
Devices
The pin on the uncombined device at which the signal terminates.

• Signal
The name of the signal.
• Combined
The pin on the new combined device at which the signal will terminate.
Capital Integrator automatically merges signals that terminate at pins with the same
name on the devices to be combined.
For example:
A signal COND01 terminates at PIN1 on a device A1 and a signal COND02 terminates
at PIN1 on a device A2. The devices A1 and A2 are being combined in a slot. COND01
and COND02 are merged together to terminate at a pin PIN1 on the new combined
device because they both terminate at a pin called PIN1 on the original devices.
If you want to change the pin at which a signal will terminate on the combined device,
click the pin name in this column and select a different one from the drop-down list.
If you select New Pin from the drop-down list, a new pin is created with a unique name
following on from the existing pin names. For example: If the combined device
currently has 6 pins, named 1 to 6, the new pin is called 7.
Note
When you combine devices, multiple pins are mapped to a single slot device pin. If
these pins each have a Pin Group attribute, one of the values from the combined
pins is used.
4. Click the OK button to combine the devices; the option expression on the combined
device is the logical OR of the option expressions on the constituent logical devices.
Also, the device is considered to be variantly placed using the logical OR option
expression of the constituent placement option expressions.
Note
If at least one of the devices has no option expression or variant placement, the
resulting combined device is considered to have no option expression or variant
placement.
Related Topics
Merge of Logical Multicores in Wiring Synthesis

February 2016
Devices
Combining Ground Devices in Selected Ground Slots
Combining Ground Devices in Selected

Ground Slots
After some ground devices have been placed in ground slots and before signals have been
routed, you can automatically combine ground devices located together in selected ground slots.
This action automates the process of creating multiple-terminations for ground signals that
connect to the cavities of ground slots.
If multiple harnesses are connected to ground devices, the ground devices can be combined if
they connect to the same harnesses.
Note
If you have placed ground devices in equipment slots instead of ground slots, then you must
combine ground devices manually. See “Combining Normal Devices in a Slot” on
page 189. If a ground device has a library part, it will not be combined with other devices.
The following constraints can be set for slots so that the automatic combination of ground
devices and the creation of multiple terminations follow rules: Ground Device Combination,
Max Ground Slot Connector Cavities, Max multitermed Ground Signals and Multiterm
Ground Devices. See “Overview of Rules and Constraints” on page 287 for descriptions of
these constraints. You must set a Ground Device Combination constraint before combining
ground devices.
When the system combines ground devices automatically, the following points apply:
• Ground devices with multiple signals will not merge their signals on a combined device
but they can form multiple terminations.
• Devices with part numbers are never combined.
• If some ground devices are already combined before you perform this action, they stay
combined regardless of any constraints that have been set on any object in the design.
You must unplace a device to un-combine it.
• Slot connectors that are de-populated due to the combination of signals (multiple
terminations) are not deleted.
• Bundle connectivity is never changed.
• The option expression on the combined device is the logical OR of the option
expressions on the constituent logical devices. Also, the device is considered to be
variantly placed using the logical OR option expression of the constituent placement
option expressions. If at least one of the devices has no option expression or no variant
placement, the resulting combined device is considered to have no option expression or
no variant placement.

February 2016
Devices
Combining Ground Devices in All Ground Slots
Procedure
1. Having placed ground devices in ground slots, select the slots in which you want to
combine ground devices in the Design Browser (Design tab), press Space Bar and enter
Auto-Refine Grounds.
The system combines the ground devices automatically and displays the combined
devices in the Design Browser (Design tab) with the original devices listed below the
combined device.
Signal mappings are re-balanced across existing slot connectors and their cavities taking
into account the Max multitermed Ground Signals constraint. New cavities may be
generated on existing slot connectors as a result of the constraint as long as the new
cavity does not violate a Max Ground Slot Connector Cavities constraint. Once the
maximum number of cavities is reached on a slot connector, the remaining signal will be
multi-termed regardless of any Max multitermed Ground Signals constraint.
This may result in cavities having too many terminations because no more cavities can
be added to a slot connector.
2. Run the Ground device that breaks placement rule design rule check, this informs
you of any cavities with too many terminations. Make changes to the design to fix these.
Related Topics
Combining Ground Devices in All Ground

Slots
After some ground devices have been placed in ground slots and before signals have been
routed, you can automatically combine all placed ground devices located together in ground
slots. This action automates the process of creating multiple-terminations for ground signals
that connect to the cavities of ground slots.
If multiple harnesses are connected to ground devices, the ground devices can be combined if
they connect to the same harnesses.
Note
If you have placed ground devices in equipment slots instead of ground slots, then you must
combine ground devices manually. See “Combining Normal Devices in a Slot” on
page 189. If a ground device has a library part, it will not be combined with other devices.
The following constraints can be set for slots so that the automatic combination of ground
devices and the creation of multiple terminations follow rules: Ground Device Combination,
Max Ground Slot Connector Cavities, Max multitermed Ground Signals and Multiterm

February 2016
Devices
Ground Devices. See “Overview of Rules and Constraints” on page 287 for descriptions of
these constraints. You must set a Ground Device Combination constraint before combining
ground devices.
When the system combines ground devices automatically, the following points apply:
• Ground devices with multiple signals will not merge their signals on a combined device
but they can form multiple terminations.
• Devices with part numbers are never combined.
• If some ground devices are already combined before you perform this action, they stay
combined regardless of any constraints that have been set on any object in the design.
You must unplace a device to un-combine it.
• Slot connectors that are de-populated due to the combination of signals (multiple
terminations) are not deleted.
• Bundle connectivity is never changed.
• The option expression on the combined device is the logical OR of the option
expressions on the constituent logical devices. Also, the device is considered to be
variantly placed using the logical OR option expression of the constituent placement
option expressions. If at least one of the devices has no option expression or no variant
placement, the resulting combined device is considered to have no option expression or
no variant placement.
Procedure
1. Having placed ground devices in ground slots, press Space Bar and enter Auto- Refine
All Grounds.
The system combines the ground devices automatically and displays the combined
devices in the Design Browser (Design tab) with the original devices listed below the
combined device.
Signal mappings are re-balanced across existing slot connectors and their cavities taking
into account the Max multitermed Ground Signals constraint. New cavities may be
generated on existing slot connectors as a result of the constraint as long as the new
cavity does not violate a Max Ground Slot Connector Cavities constraint. Once the
maximum number of cavities is reached on a slot connector, the remaining signal will be
multi-termed regardless of any Max multitermed Ground Signals constraint.
This may result in cavities having too many terminations because no more cavities can
be added to a slot connector.
2. Run the Ground device that breaks placement rule design rule check, this informs
you of any cavities with too many terminations. Make changes to the design to fix these.

February 2016
Devices
Related Topics
Combining Ground Devices in Selected Ground Slots

February 2016
Devices
Defining Footprints on Devices

In Capital Logic, footprints can be defined on a device either by assigning a library part with a
footprint or by using device pin attributes. However, defining a device in Capital Logic can
limit the re-usability of the system designs across vehicle programs when re-using designs.
For details of the process in Capital Logic, see Defining a Footprint Directly on a Device
(Generative Flow) in the Capital Logic User Guide.
This topic details how to assign a library part with a footprint to a device in Capital Integrator.
By doing this, the mapping of device pins to slot connector cavities is controlled automatically
using library-defined footprints or is directly defined using a custom constraint in Capital
Integrator.
If the devices have not yet been placed in slots, you can use an “Assign Footprint to Device”
constraint applied to slots to specify the library part that is assigned to a device (with a particular
property or attribute value) when that device is placed in the slot. It also allows you to specify
which footprint from that library part is used. See “Rules and Constraints” on page 287 for
general information about using constraints.
If the devices have already been placed in slots, you can either:
• define an “Assign Footprint to Device” constraint on a slot, press Space Bar and enter
Footprint; the constraint is applied to the slot and the library part and footprint are
updated accordingly.
• right-click on a device in the Design Browser (Design tab) and select Properties; the
Edit Properties dialog box for that slot is displayed. On the General tab, use the Library
Part field to specify the library part for that device. After specifying the library part,
click the View ( ) button next to that field; the Details dialog box for that library part
is displayed. Use the Footprints tab to select the footprint that you want to use for the
device.
Note
You can define a custom constraint in Java that will also define the pin mapping
when the part is assigned to the device. This custom constraint assigns the pin
mapping directly without the need to define device part numbers and footprints in
Capital Library. For more information about writing and loading custom constraints, see
the PluginDevelopment.pdf document that is located in the doc\plugin folder of your
installation.
Reevaluation and Updating of Footprints when Changes Are Made . . . . . . . . . . . . . . . 196

February 2016
Devices
Reevaluation and Updating of Footprints when Changes Are Made
Reevaluation and Updating of Footprints when

Changes Are Made
Footprints can be updated in Capital Library and Capital Logic. Therefore the footprints on
placed devices may need to be re-evaluated and updated.
Synchronizing logical design changes and performing a batch update of library parts is
sufficient to update all library parts and footprint definitions. For details of how to perform
these steps, see “Synchronizing Changes in Capital Logic Designs with the Capital Integrator
Design” on page 70 and “Performing a Batch Update of Library Parts” on page 278.
Note
Performing those steps does not prompt a re-evaluation of the “Assign Footprint to Device”
constraint (if used). If required, the constraint can be re-evaluated by pressing Space Bar and
entering Footprint.
When the system re-evaluates footprint data, any changes must be synchronized into the
topological design. This can affect previously placed devices and therefore previously created
wiring:
• An affected device will not be left with a pin mapping that does not match the footprint.
The data defined in the footprint (which is some or all of the connectors, their part
numbers and the device to pin to cavity mapping) are reflected in the topological design.
o Whenever possible, the device pin mapping is updated to match the new footprint
data. If this cannot be done, then the device is left placed but may have one or more
device pins unmapped.
• Affected wiring will not be left if there is a signal mismatch caused by a change of pin
mapping.
o Whenever possible, existing wiring is moved together with the change in pin
mapping. If this is not possible, the wiring may be deleted.
• If a device is unplaced or wiring is deleted, a message is displayed in the Output
Window (the tab depends on whether logical changes have been synchronized or a batch
update of library parts has been performed).
• When device pins are unmapped, the system naps all the pins associated with a
connector, not just some of them. This is so that the whole footprint can be re-mapped in
the Connector Map dialog box.
• When multiple devices with footprints are placed in the same slot, all footprint
connectors mapped to the same slot connector must be compatible (that is, have the
same part number).

February 2016
Devices
Reevaluation and Updating of Footprints when Changes Are Made
Related Topics

February 2016
Devices
Implementing Grounds in the Generative Flow

There are two flows for implementing the design of grounds and ground wiring when using
Capital Logic and Capital Integrator in the Generative flow.
• Flow 1: Use Ground Design functionality in Capital Integrator
In Capital Logic, rather than specify exactly where in the vehicle each device is
grounded, you specify only that a device needs to be grounded. You do this by adding
unique ground devices and also usually specifying some further properties for them that
Capital Integrator uses to drive the placement and combination of ground points.
• Flow 2: Use shared devices in Capital Logic before placing them in Capital Integrator
In Capital Logic, each ground point in the vehicle is represented by a device (usually
shared because it will appear on many different system design). These grounds are used
in the system designs like normal devices. Note that they are not normally created as
ground device symbols because such symbols cannot be shared. The grounds are
connected to a single, shared net that represents the entire ground signal connected to
this ground point.
In Capital Integrator, the grounds are placed and routed just like a normal device.
In order to use this flow, you must know exactly where in the vehicle each device will be
grounded. This, in turn, means that you must take into account the physical placement of
each device while editing logical system designs. This limits the re-usability of the
system designs since, if the same devices are placed into a different vehicle, the ground
points and normal device positions may change. Therefore, you would have to change
all of the ground connections in your system schematics.
Grounds and Ground Wiring Flow Using Ground Design Functionality . . . . . . . . . . . 198
Grounds and Ground Wiring Flow Using Shared Objects . . . . . . . . . . . . . . . . . . . . . . . 202
Grounds and Ground Wiring Flow Using Ground

Design Functionality
You can use ground design functionality to implement ground devices when creating Capital
Logic and Capital Integrator designs in the generative flow.
Caution
For an overview of the possible ground device flows and the differences between them, see
“Implementing Grounds in the Generative Flow” on page 198.
The generative flow is intended to separate the logical connectivity requirements (in Capital
Logic designs) from the physical constraints and implementation (in Capital Integrator designs).

February 2016
Devices
Grounds and Ground Wiring Flow Using Ground Design Functionality
When creating logical designs, you specify that a device needs to be grounded but you do not
need to know where in the vehicle each device will be grounded. You specify the locations of
the ground devices in the associated Capital Integrator designs).
A ground device can have any number of pins.
Note
When using this flow, you do not share a ground device in Capital Logic.
There are three stages to using ground design functionality in Capital Integrator:
1. Setup
Logical designs and Integrator constraints must be developed in such a way to support
the ground design process.
2. Placement
After placing all non-ground devices in Capital Integrator, you place the ground devices.
3. Combination
An important capability within ground design is to combine the individual logical
grounds so that specified ground signals can share wiring.
These stages are explained in greater detail in the following sections:
Setup
In Capital Symbol:
Create one or more ground symbols in Capital Symbol. See Creating a New Symbol in the
Capital Symbol User Guide.
Note
The starter data supplied with the software includes symbols for grounds in the Quick Start
- Electrical symbol library.
In Capital Logic:
1. Add ground devices to a design and connect them to devices that require grounding. It is
normally most efficient to use a separate ground device for every single pin that needs to
be grounded. In the case that you know that two or more pins must be connected to the
same ground point, you can use a single ground device. However, connecting large
numbers of pins to the same ground device will adversely affect the performance of
ground placement in Capital Integrator and is undesirable.

February 2016
Devices
You can create a ground device in Capital Logic only by adding a device with a ground
symbol. You cannot convert an existing device in a design to a ground device nor can
you convert a ground device to a normal device. See Adding a Device from Capital
Library in the Capital Logic User Guide.
2. Properties are typically used to drive the specification of Capital Integrator constraints
that control the placement and combination of ground devices. A strategy for this should
be determined before any significant design work is done and the appropriate properties
assigned to the ground devices. It may be most efficient to use a small number of
different ground device symbols which have been pre-populated with the appropriate
properties. Typically, one property is used to drive placement of grounds and at least one
more used to drive combination.
For example, you could use a Ground type property (using values such as Engine and
Body) to control placement and a Ground class property (using values such as A and B)
to control combination.
In Capital Integrator:
1. Specify which slots in Capital Integrator designs will contain ground devices that have
been added to the associated Capital Logic designs. You do this by specifying a Slot
Type of Ground in a slot’s properties.
Note
The best way to represent multiple ring terminals connected to a single ground stud
is to add multiple slot connectors to the ground slot. Each slot connector represents a
potential ring terminal and should have a single cavity. This should be enforced using
the Max Ground Slot Connector Cavities constraint: Maximum cavities per ground
slot connector is 1.
2. Assign ground refinement constraints to objects in the Capital Integrator design that will
control the placement and combination of ground devices.
The “Place by Attribute/Property” constraint is used to control the placement of ground
devices.
For a list of the constraints that control the combining of ground devices, see “Ground
Refinement” in the Overview of Rules and Constraints section.
Placement of Ground Devices

Note
Before placing ground devices in Capital Integrator, it is essential that most (if not all) non-
ground devices have been placed. If you have a license for optimized ground placement, it
relies on this information to calculate the optimum placement slot for each ground device.

February 2016
Devices
Place the ground devices in ground slots in Capital Integrator. You can either:
• manually place individual ground devices

• have the system place ground devices. The result of this depends on whether you have a
license for Optimized Ground Placement.
See “Placement of Ground Devices in Slots” on page 176 for details of both.
Combination
If multiple ground devices have been placed (either manually or automatically) in the same
ground slots, this results in separate ground trees running from each grounded device back to
the connected device in the ground slot. It is therefore desirable to combine these ground
devices which can then share wiring with fewer signals. This is done before routing signals.
When you combine ground devices, any constraints on the slot are taken into account.
1. You can combine ground devices in two ways:

o By manually combining selected ground devices in a slot and editing the signal map
of the slot. See “Combining Normal Devices in a Slot” on page 189.
o By automatically combining ground devices in ground slots. See “Combining
Ground Devices in All Ground Slots” on page 192 or “Combining Ground Devices
in Selected Ground Slots” on page 191.
Note
Generally, slot connectors have one cavity. However, if you have slot connectors
with multiple cavities, the following applies:
In both cases, signal mappings are re-balanced across existing slot connectors and
their cavities taking into account the Max multitermed Ground Signals constraint.
New cavities may be generated on existing slot connectors as a result of the
constraint as long as the new cavity does not violate a Max Ground Slot Connector
Cavities constraint. Once the maximum number of cavities is reached on a slot
connector, the remaining signal will be multi-termed regardless of any Max
multitermed Ground Signals constraint. This may result in cavities having too
many terminations because no more cavities can be added to a slot connector. If you
run the Ground device that breaks placement rule design rule check, this informs
you of any cavities with too many terminations and you can make changes to the
design to fix these.
2. After you have placed and combined ground devices in slots, you may want to remove
any unused connectors and cavities that have been created during the process. See
“Removing Unused Connectors, Holes and Cavities from Slots” on page 262.
3. After placing devices in slots and routing signals, you may want to add wire connections
between cavities in ground slots.

February 2016
Devices
Grounds and Ground Wiring Flow Using Shared Objects
It is sometimes a requirement to protect against the failure of a ground point (that is,
where a weld fails and the ground stud is no longer attached to the chassis). This is often
achieved by adding additional wires between the ground points themselves.
These wires are not based on any net conductor connection in the functional design from
Capital Logic. You cannot add wire connections like this between equipment slots (even
if ground devices are placed in the equipment slot). See “Adding a Wire” on page 477
for more information about adding wires.
Related Topics
Grounds and Ground Wiring Flow Using Shared Objects
Grounds and Ground Wiring Flow Using Shared

Objects
You have the option of implementing ground devices without using the Ground Design
functionality but instead using shared objects in Capital Logic before placing them in Capital
Integrator.
Caution
If you want to use Ground Design functionality, see “Grounds and Ground Wiring Flow
Using Ground Design Functionality” on page 198. For an overview of the possible flows
and the differences between them, see “Implementing Grounds in the Generative Flow” on
page 198.
In Capital Logic:
1. For each ground point, place multiple instances of a shared normal device that you want
to represent it. See Adding a Shared Device/Connector/Splice to a Diagram in the
Capital Logic User Guide.
Note
You cannot use a ground device symbol to add a ground point because such symbols
cannot be shared.
2. For each ground point, add a shared net that connects all of the instances of it. This
shared net represents the entire ground signal connected to the ground point. See
Adding a Shared Conductor to a Diagram in the Capital Logic User Guide.
In Capital Integrator:
Place the ground points in slots in the same way as you place a normal device. See either
“Manually Placing a Normal or Ground Device in a Slot” on page 182 (remembering that the

February 2016
Devices
150% Device
ground point has been created as a normal device) or “Automatically Placing a Normal Device
in a Slot” on page 183.
Related Topics
150% Device
A 150% device is one that represents a merging of multiple, very similar devices. The devices
(for example, two different radios) typically have a great deal of common connectivity (that is,
pins and net connections) but often each have some unique connectivity. In particular, they are
likely to have different connector part numbers and often a different number of cavities. Due to
the high level of commonality, it is advantageous to represent the devices with a single 150%
device in Capital Logic designs. In Capital Integrator, you then variantly place the merged
device in separate slots so that the individual devices are implemented.
To support this, Capital Integrator allows pins from logical devices to be left unmapped, without
this causing failures when Synthesizing Wiring or when running Design Rule Checks.
The Design Assistant will not report unmapped pin errors if the pin (or all nets attached to the
pin) have an option expression which is exclusive with the variant placement option (that is, the
pin can never be active in this slot).
Usage Example - 150% Device

In a Capital Logic design, you have a device TAPE PLAYER with eight pins.
Figure 8-1. 150% Device in Capital Logic

February 2016
Devices
150% Device
Note
The pin names are numbers in this example. However, this is not best practice and it is
normally recommended that you name pins based on their function (for example, PWR,
GND, AUDIO_OUT_L, and so on).
Pin 7 and pin 8 are used only in right-hand drive vehicles so you define an Option attribute for
each of them with the expression Market-RHD. This means those pins are conditional on the
Variant Option Market-RHD and are active only in right-hand drive vehicles.
Figure 8-2. Option Attribute of Market-RHD on Pin
Pin 5 and pin 6 are used only in left-hand drive vehicles so you define an Option attribute for
each of them with the expression Market-LHD. This means those pins are conditional on the
Variant Option Market-LHD and are active only in left-hand drive vehicles.
The Capital Logic design is associated with a Capital Integrator design.
The TAPE PLAYER device can be placed in two different slots using variant placement, one
slot for right-hand drive vehicles (TAPE_RHD) and another for left-hand drive vehicles
(TAPE_LHD).

February 2016
Devices
150% Device
Figure 8-3. Variant Slots in Capital Integrator
When the you place the device in slot TAPE_LHD, you specify a Placement Option of
Market-LHD on the Place Device Dialog Box. This means it is conditional on the variant
option Market-LHD and appears only in left-hand drive vehicles.
Therefore, if you look at the Edit Properties Dialog Box of the device in the TAPE_LHD slot, it
has a “Configuration: Option” value Market-LHD.
Figure 8-4. Variant Slots and Devices in Design Browser (Design Tab)

February 2016
Devices
150% Device
Figure 8-5. Option Attribute of Market-LHD on Edit Properties Dialog Box for
Device in Slot TAPE_LHD
Similarly, when you place the device in slot TAPE_RHD, you specify a Placement Option of
Market_RHD. This means it is conditional on the variant option Market-RHD and appears
only in right-hand drive vehicles. Therefore, if you look at the Edit Properties dialog box of the
device in the TAPE_RHD slot, it has an Option value Market-RHD.
You assign a library part TAPE_PLAYER_PART to the device in both slots.
Figure 8-6. Library Part Assignment on Edit Properties Dialog Box for Device in
Slot TAPE_LHD
Looking at the details of the library part, it has two footprints FP1 and FP2.
Note
It is normally recommended that you name footprints in a way that helps to distinguish
between them. For example, LHD and RHD.
Figure 8-7. Footprint Details for Library Part
The device in slot TAPE_LHD uses FP1 where the device pins have been mapped to a six pin
connector so that pins 7 and 8 are unmapped. Remember that pins 7 and 8 are not active in a
left-hand drive vehicles.
Figure 8-8. FP1 Pin Mapping Details

February 2016
Devices
150% Device
The device in slot TAPE_RHD uses FP2 where the device pins have once again been mapped
to a six pin connector but pins 5 and 6 are unmapped this time. Remember that pins 5 and 6 are
not active in a right-hand drive vehicles.
Figure 8-9. FP2 Pin Mapping Details
In each case, the device uses only some of its pins, the others remain unconnected.
When a device has been placed in a Capital Integrator design, the Design Assistant would
normally display an error when pins are unmapped. However, such errors are not displayed in
this case because of the option expressions that were specified on the device pins in Capital
Logic.
If those option expressions were not specified on the pins, those pins would be active always. In
that case, the Design Assistant would report errors, such as:
Signal 2N-POWER-3 is Unmapped for TAPE PLAYER:8 in Slot TAPE_LHD
This error indicates that pin 8 is unmapped in slot TAPE_LHD.
The device uses footprint FP1 in that slot and FP1 has pin 8 unmapped. Without an option
expression of Market-RHD specified on the pin, the system would expect it to be active, even
in slot TAPE_LHD.
However, when the option expressions are specified on the pins, no such error is reported and
the Signal Map Dialog Box for Slots in Capital Integrator shows the unmapped pins.
Synthesizing Wiring also runs correctly with connections made to the common pins, as well as
connections made to the mapped pins in each slot.

February 2016
Devices
150% Device

February 2016
Chapter 9
This chapter contains details about connector refinement and signal mapping.
Connector Refinement and Signal Mapping Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Specialized Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Fanout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Variant Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Variant Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Signal Map for a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Signal Map for an Interface Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Signal Map for an Inline Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Usage Examples for Connector Refinement and Signal Mapping . . . . . . . . . . . . . . . . . . . 217
Mapping a Signal to a Hole or Slot Connector Cavity on a Slot . . . . . . . . . . . . . . . . . . . . 240
Mapping a Signal to Multiple Slot Connector Cavities on a Slot. . . . . . . . . . . . . . . . . . . . 241
Refining an Interface Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Mapping a Signal to an Interface Connector Cavity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Mating the Cavities of the Two Halves of an Inline Connector . . . . . . . . . . . . . . . . . . . . . 245
Mapping a Signal Between Cavities on the Halves of an Inline Connector. . . . . . . . . . . . 246
Mapping Multiple Shield Signals to One Backshell Termination on an Inline Connector 247
248
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Inline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Slot or Inline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Creating Variant Signal and Wire Mappings in the Signal Map for an Interface Connector 252
Deleting a Variant Signal Mapping in the Signal Map for an Interface Connector . . . . . . 253
Creating a Variant Connector in the Signal Map for a Slot, Inline or Interface Connector 254

February 2016
Connector Refinement and Signal Mapping Overview

Overview
The Signal Map dialog boxes in Capital Integrator enable you to perform connector refinement.
That means, you can take a generalized connector (inline, interface or virtual) and create a mini-
topology that replaces the generalized connector with one or more specialized connectors.
Once specialized connectors have been created, the signal map is used to map signals and/or
wires to specific connector cavities. Connector refinement provides a separation between the
basic topology of harnesses (which harnesses connect to which others) and the exact
implementation of the connectors. Optimization of the number of connectors and exact signal
connectivity can be made without the need to edit and re-edit the bundle topology on the
diagram. If a connector has a library part assigned, you cannot change the number of cavities or
cavity names.
Note
If you have upgraded from a version of Capital prior to 2010.1, connector refinement data is
migrated. The old refinement data was based on harness levels, which are a collection of
options. Therefore, where a wire was mapped to different connector cavities in separate
mappings, a variant wire will be created. The variant option expression will be a combination of
the options on the harness levels for that mapping.
This functionality enables you to model:
• multiple connectors at a slot connector on a slot, an interconnect connector or an inline

connector
By adding specialized connectors in the Connector Mating Table at the top of the
Signal Map dialog box.
• different wires connected to the same cavity
By defining the exact mapping on the Signal Mappings tab at the bottom of the Signal
Map dialog box. Each wire has its own mapping. This would only normally be done
when the wires are mutually exclusive, however, the system does not check for this.
• variant wires
By defining Variant Wires or Variant Signals on the Signal Mappings tab at the bottom
of the Signal Map dialog box. These are listed on the Signal Mappings tab like any
other wire but display the variant option expression in addition to the wire and signal
name.
• looped wires
By defining two mappings for a wire on the Signal Mappings tab at the bottom of the
Signal Map dialog box. Each row displays the same wire but maps it to a different
connector cavity.

February 2016
• N:M mating
By defining the exact mapping on the Signal Mappings tab at the bottom of the Signal
Map dialog box.
See “Usage Examples for Connector Refinement and Signal Mapping” on page 217 for detailed
examples.
There are various terms related to connector refinement that you must understand, see
“Generalized Connector” on page 212, “Specialized Connector” on page 212, and “Fanout” on
page 213.
There are various terms related to signal mapping that you must understand, see “Variant Wire”
on page 213 and “Variant Signal” on page 214.
Caution
You cannot import wiring data XML from a Capital version prior to v2010.1.

Specialized Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Fanout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Variant Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Variant Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Signal Map for a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Signal Map for an Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Signal Map for an Inline Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Usage Examples for Connector Refinement and Signal Mapping . . . . . . . . . . . . . . . . . 217
Mapping a Signal to a Hole or Slot Connector Cavity on a Slot . . . . . . . . . . . . . . . . . . . 240
Mapping a Signal to Multiple Slot Connector Cavities on a Slot . . . . . . . . . . . . . . . . . . 241
Refining an Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Mapping a Signal to an Interface Connector Cavity . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Mating the Cavities of the Two Halves of an Inline Connector. . . . . . . . . . . . . . . . . . . . 245
Mapping a Signal Between Cavities on the Halves of an Inline Connector . . . . . . . . . . 246
Mapping Multiple Shield Signals to One Backshell Termination on an Inline Connector
247
Creating Variant Wire and Variant Signal Mappings on the Signal Mappings Tab for a
Slot. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

February 2016
Generalized Connector
Creating Variant Wire and Variant Signal Mappings on the Signal Mappings Tab for an
Inline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Deleting a Variant Wire and Variant Signal Mapping on the Signal Mappings Tab for a
Slot or Inline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250
Editing the Variant Option Expression of a Variant Wire Mapping on the Wire Info Tab
for a Slot or Inline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Creating Variant Signal and Wire Mappings in the Signal Map for an Interface Connector
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Deleting a Variant Signal Mapping in the Signal Map for an Interface Connector . . . 253
Creating a Variant Connector in the Signal Map for a Slot, Inline or Interface Connector
254
The term ‘generalized connector’ refers to the slot connectors on slots, interface connectors and
inline connectors that are displayed in a Capital Integrator diagram window and Design
Browser (Design Tab). The Signal Map dialog boxes in Capital Integrator allow you to refine
these connectors by creating a mini-topology that replaces the generalized connector with one
or more specialized connectors.
Within a Signal Map dialog box, a specialized connector becomes a generalized connector
when only one specialized connector exists for a generalized connector and there are no variant
wires. In this case, the last specialized connector is removed from the Signal Map dialog box
(see Signal Map Dialog Box for Inline, Signal Map Dialog Box for Interface Connector or
Signal Map Dialog Box for Slot as appropriate for full details of the dialog box) and its
attributes are transferred to the generalized connector.
Related Topics
Specialized Connector
The term ‘specialized connector’ refers to the connectors in a mini-topology created using
connector refinement for a slot connector on a slot, an interface connector or an inline connector
(also referred to as generalized connectors).
The specialized connectors are not used by any other Capital Integrator functionality but are
displayed in the Design Browser (Design tab). They are used in Capital HarnessXC when the
harness is manufactured.

February 2016
Fanout
Within a Signal Map dialog box, a generalized connector becomes a specialized connector
when:
• a new connector is added using the Add Connector Mapping button ( ) on a Signal
Map dialog box (see Signal Map Dialog Box for Inline, Signal Map Dialog Box for
Interface Connector or Signal Map Dialog Box for Slot as appropriate for full details of
the dialog box).
• a new variant signal or wire is created on a signal or wire mapped to a generalized
connector cavity.
Related Topics
Fanout
A fanout is a graphical representation of the specialized connectors in a generalized connector.
The fanout diagram allows you to reorder the connectors, add new bundle nodes and define the
length of the bundles.
It is displayed when you click the Show Fanout ( ) button on a Signal Map dialog box.
The fanout diagram cannot be used to add or remove specialized connectors; this is done
automatically when you add or remove connector mappings in the Signal Map dialog box for
an object.
Related Topics
Fanout Viewer Dialog Box
Variant Wire
A variant wire is a wire that is connected to different cavities depending on the active options in
a vehicle.
Variant wires can be added and have their variant option expression edited or removed on the
Signal Mapping tab on a Signal Map dialog box. The Wire Info tab allows you to edit the
variant option expression.

February 2016
Variant Signal
Related Topics
Inline
Slot or Inline
Deleting a Variant Signal Mapping in the Signal Map for an Interface Connector
Variant Signal
A variant signal is a signal that can travel to different cavities depending on the active options in
a vehicle. A variant signal can be defined prior to running wiring synthesis.
Variant signals can be added and have their variant option expression edited or removed on the
Signal Mappings tab on a Signal Map dialog box.
Related Topics
Inline
Slot or Inline
Signal Map for a Slot

When devices have been placed in a slot, the connected signals travel to/from pins on the
devices via connector cavities and holes.
In some cases (for example, fuse boxes), a signal may need to map from a single pin to a cavity
on more than one connector.

February 2016
Signal Map for an Interface Connector
A hole can house one or several different wires and, unlike a connector, does not have cavities.
A hole connection cannot be changed if the logical device specifies the Hole attribute (whether
originally from the library part or not). If you are working with a relay design flow, the Signal
Map dialog box takes into account the Pin Group attribute on the pins. If no Pin Group
attribute is specified for a pin, you can create an explicit mapping of a signal to a hole or change
the mapping between a connector/cavity and a hole.
The signal map for a slot enables you to perform the following actions:
• Map signals and wires to connector cavities in the slot

o “Mapping a Signal to a Hole or Slot Connector Cavity on a Slot” on page 240
o “Mapping a Signal to Multiple Slot Connector Cavities on a Slot” on page 241
o “Updating the Signal Maps for Slots” on page 242
• Create, delete and edit variant signals and wires
o “Creating a Variant Connector in the Signal Map for a Slot, Inline or Interface
Connector” on page 254
o “Deleting a Variant Wire and Variant Signal Mapping on the Signal Mappings Tab
for a Slot or Inline” on page 250
o “Editing the Variant Option Expression of a Variant Wire Mapping on the Wire Info
Tab for a Slot or Inline” on page 251
• Refine slot connectors
o “Refining a Slot Connector on a Slot” on page 239

Signals and wires travel to and from cavities on an interface connector.
The signal map for an interface connector enables you to perform the following actions:
• Map signals and wires to cavities in the interface connector

o “Mapping a Signal to an Interface Connector Cavity” on page 243
• Create, delete and edit variant signals
o “Creating Variant Signal and Wire Mappings in the Signal Map for an Interface

February 2016
Signal Map for an Inline Connector
o “Deleting a Variant Signal Mapping in the Signal Map for an Interface Connector”
on page 253
• Refine an interface connector
o “Refining an Interface Connector” on page 242
Signal Map for an Inline Connector

Signals and wires travel to, from and between cavities on an inline pair.
The signal map for an interface connector enables you to perform the following actions:
• Map signals and wires to cavities in the inline connector

o “Mating the Cavities of the Two Halves of an Inline Connector” on page 245
o “Mapping a Signal Between Cavities on the Halves of an Inline Connector” on
page 246
o “Mapping Multiple Shield Signals to One Backshell Termination on an Inline
• Create, delete and edit variant signals and wires
o “Creating Variant Wire and Variant Signal Mappings on the Signal Mappings Tab
for an Inline” on page 249
o “Deleting a Variant Wire and Variant Signal Mapping on the Signal Mappings Tab
for a Slot or Inline” on page 250
o “Editing the Variant Option Expression of a Variant Wire Mapping on the Wire Info
Tab for a Slot or Inline” on page 251
• Refine the inline halves
o “Refining an Inline Connector” on page 244

February 2016
Usage Examples for Connector Refinement and Signal Mapping
Usage Examples for Connector Refinement and

Signal Mapping
Various usage examples are available for connector refinement and signal mapping.
Usage Example - Refining an Inline Connector Before Composite Wiring Synthesis to Have
Two Connectors on Each Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Usage Example - Refining an Inline Connector After Composite Wiring Synthesis To Have
Two Connectors on Each Side . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Usage Example - Setting Two Preferred Signals for One Cavity in the Signal Map of an
Inline Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Usage Example - Refining an Inline Connector Before

Composite Wiring Synthesis to Have Two Connectors on
Each Side
The following usage example demonstrates how to use connector refinement and signal
mapping before running Composite Wiring Synthesis to model an inline pair where you want to
have two connectors on each side.
You might want to do this because:
• There are a large number of signals going between the harnesses and a single, very large
connector is unavailable or impractical.
• Some of the signals are only required on a small number of vehicles. By moving these
into a separate connector, you can save the cost of the connector for the majority of the
vehicles.
This example uses a Quick Start - Automotive Generative project. If you want to re-create the
steps in Capital Integrator, download the Project.zip file from here, extract the contents and
import the Quick Start - Automotive Generative.xml project.
In the Sports Coupe Integrator design of the Quick Start - Automotive Generative project,
you will refine the inline pair P3 / J3 that connect the instrument panel IP (yellow color) and
passenger door DOOR-PASS (green color) harnesses.

February 2016
Figure 9-1. Inline Pair P3 and J3
You will assume that the majority of vehicles are sold with either the option A-2SPKR (2
Speaker - Base Audio System) or A-4SPKR (4 Speaker - Premium Audio System). A smaller
percentage of vehicles are sold with the option A-6SPKR (6 Speaker - Premium Audio
System). You therefore decide to map the two additional A-6SPKR wires to their own
connectors on each side of the inline pair. This allows you to use a 12 cavity connector most of
the time and to add the extra 2 cavity connector only when the A-6SPKR option is selected.
Video
You can play a video of the steps in this usage example, see video.

February 2016
Prerequisites
• If you are re-creating the steps, the Vehicle Topology diagram must be open in the
diagram window.
• Normally, you would need to have added the harnesses and the inline pair to the design.
This has already been done here because we are using the starter data.
Procedure
1. In the Design Browser (Design tab), right-click on the J3 inline connector and select
Signal Map; the Signal Map Dialog Box for Inline is displayed.
Figure 9-2. Signal Map for J3
The Connector Mating table indicates that one connector P3 is mapped to one connector
J3 and neither of them have any cavities.
The Signal Mappings tab indicates that no signals are mapped to any cavities (because
there are no cavities).
The Cavity Matings tab is blank (because there are no cavities).
2. Specify that P3 and J3 have 12 cavities by entering 12 in the No. of Cavities column for
P3:
Figure 9-3. P3 with 12 Cavities

February 2016
When you click another column, the No. of Cavities cell for J3 will update to display 12
automatically.
The Cavity Matings tab displays 12 rows in which the P3 cavities (numbered 1 to 12)
are mated with the equivalent cavities on J3 (that is, P3 cavity 1 is mated with J3 cavity
1, and so on).
Figure 9-4. Cavity Matings between P3 and J3
The Signal Mappings tab displays 12 rows which display the same matings as on the
Cavity Matings tab as well as the fact that no signals are currently mapped to any of the
mated cavities.
Figure 9-5. Signal Mappings from P3 to J3
3. Add a 2-cavity connector to each side of the inline pair:

a. In the Connector Mating table, click the cell in the mating row for the P3 and J3
connectors and click Add Connector Mapping ( ).

February 2016
A new connector mating row is added:

Figure 9-6. New Connector Mating Row
There are now two connectors (P3 and P3_1) on the IP side of the inline pair and
two connectors (J3 and J3_1) on the DOOR-PASS side. P3 is mated with J3. P3_1
is mated with J3_1.
b. In the No. of Cavities cells for P3_1, and J3_1, specify that they each have 2
cavities and click the top of the table.
The Cavity Matings tab indicates that:
o the P3 connector cavities are mated to the equivalent J3 connector cavities (that
is, P3 cavity 1 to J3 cavity 1, and so on)
o the P3_1 connector cavities are mated to the equivalent J3_1 connector cavities
(that is, P3_1 cavity 1 to J3_1 cavity 1, and so on).
Figure 9-7. Cavity Matings between P3, J3 and J3_1
The Signal Mappings tab displays rows for the new cavity matings and still
indicates that no signals are currently mapped to any of the cavities.

February 2016
Figure 9-8. Signal Mappings between P3, J3 and J3_1
Note
Note that if you select one of the connector mating rows in the top Connector
Mating table, the Signal Mappings and Cavity Matings tabs display only
details related to that specific connector mating. You can click the Clear Selection
button to display the details for all connector matings.
4. With one of the rows in the Connector Mating table selected, click the Show Fanout
( ) button at the top right corner of the Connector Mating table to view the fanout
diagram for the connectors J3, P3, J3_1 and P3_1.

February 2016
Figure 9-9. Fanout for J3, P3, J3_1 and P3_1
The fanout is used to specify whether any add-on bundle length is required for a wire to
pass from the end of the harness bundle to the cavities of the connectors. The length
value uses the standard unit of measurement applied to harnesses by your company.
At the moment, this indicates no add-on is required for any of the connectors which
means that both J3 and J3_1 would be located at the end of the DOOR-PASS harness
and P3 and P3_1 would be located at the end of the IP harness.
You will specify that:
• the wires for the A-6SPKR option need an add-on of 10 to reach the cavities of the
2-cavity J3_1 and P3_1 connectors.
• the wires for the A-2SPKR and A-4SPKR options need an add-on of 50 to reach the
cavities of the 12-cavity J3 and P3 connectors (this could be because it clips onto the
harness in a different way).

February 2016
To do this:
a. Click P3_1 in the top left window (as in Figure 9-9); the bundle add-on graphic for it
is highlighted in red. In the Length field on the left, enter 10. You may need to click
outside of the field several times before the length is updated on the fanout diagram
b. Click J3_1 in the top right window; the bundle add-on graphic for it is highlighted in
red. In the Length field on the right, enter 10. You may need to click outside of the
field several times before the length is updated on the fanout diagram.
c. Click P3 in the top left window; the bundle add-on graphic for it is highlighted in
red. In the Length field on the left, enter 50. You may need to click outside of the
d. Click J3 in the top right window; the bundle add-on graphic for it is highlighted in
The dialog box should look like this:
Figure 9-10. Updated Fanout for J3, P3, J3_1 and P3_1

February 2016
e. Click Close to exit the dialog box.

5. Specify component library parts for the connectors:
a. Double-click in the Part Number cell for the P3 connector in the Connector Mating
table.
The Part Selection dialog box is displayed.
b. Click Search parts using criteria specified ( ); the Parts table lists all the
available connectors with 12 or more cavities.
c. Select C-61517 and click Insert; the Part Number cell for P3 updates.
d. Repeat steps a to c for the other three connectors, selecting C-61517 for J3, C-61276
for P3_1 and C-61277 for J3_1.
6. Specify that you want the signals for the A-6SPKR option to go to the P3_1 and J3_1
cavities.
The signals 2N-SPKR-RT-1 and 2N-SPKR-RT-2 are the signals for that option. You
will map them as follows:
• signal 2N-SPKR-RT-1 to P3_1 cavity 1 (and therefore also to J3_1 cavity 1)
To do this:
a. On the Signal Mappings tab, click the Preferred Signal cell for the P3_1 cavity 1
to J3_1 cavity 1 mapping and select 2N-SPKR-RT-1.

February 2016
Figure 9-11. Preferred Signal for P3_1 Cavity 1 to J3_1 Cavity 1
b. Click the Preferred Signal cell for the P3_1 cavity 2 to J3_1 cavity 2 mapping and
select 2N-SPKR-RT-2.
c. Click OK to exit the dialog box.
7. Run Composite Wiring Synthesis to see that it maps the 2N-SPKR-RT-1 and 2N-
SPKR-RT-2 signals to those mated cavities and creates wires accordingly:
a. Press Space Bar and enter CWS; the Wiring Synthesis Dialog Box is displayed.
b. Click Full Synthesis (the default selection) and click Go; wiring is synthesized.
c. In the Design Browser (Design tab), right-click on the J3 harness and select Signal
Map; the Signal Map Dialog Box for Inline is displayed.
The Signal Mappings tab shows that the 2N-SPKR-RT-1 and 2N-SPKR-RT-2
signals have been mapped to those cavities and so have the wires that carry those
signals.

February 2016
Figure 9-12. 2N-SPKR-RT-1 and 2N-SPKR-RT-2 Mapped to Cavities
A Wire Info tab has been added to the dialog box and lists the details of all the wires
that have been mapped to the inline pair.
Figure 9-13. Wire Info Tab for Mapped Inline Pair
Related Topics
Usage Example - Refining an Inline Connector After

Composite Wiring Synthesis To Have Two Connectors on
Each Side
The following usage example demonstrates how to use connector refinement and signal
mapping after running Composite Wiring Synthesis to model an inline pair where you want to
have two connectors on each side.

February 2016
You might want to do this because:
• There are a large number of signals going between the harnesses and a single, very large
connector is unavailable or impractical.
• Some of the signals are only required on a small number of vehicles. By moving these
into a separate connector, you can save the cost of the connector for the majority of the
vehicles.
This example uses a Quick Start - Automotive Generative project. If you want to re-create the
steps in Capital Integrator, download the Project.zip file from here, extract the contents and
import the Quick Start - Automotive Generative.xml project.
In the Sports Coupe Integrator design of the Quick Start - Automotive Generative project,
you will refine the inline pair P3 / J3 that connect the instrument panel IP (yellow color) and
passenger door DOOR-PASS (green color) harnesses.

February 2016
Figure 9-14. Inline Pair
You will assume that the majority of vehicles are sold with either the option A-2SPKR (2
Speaker - Base Audio System) or A-4SPKR (4 Speaker - Premium Audio System). A smaller
percentage of vehicles are sold with the option A-6SPKR (6 Speaker - Premium Audio
System). You therefore decide to map the two additional A-6SPKR wires to their own
connectors on each side of the inline pair. This allows you to use a 12 cavity connector most of
the time and to add the extra 2 cavity connector only when the A-6SPKR option is selected.
Prerequisites
• If you are re-creating the steps, the Vehicle Topology diagram must be open in the
diagram window.

February 2016
• Normally, you would need to have added the harnesses and the inline pair to the design.
This has already been done here because we are using the starter data.
Procedure
1. Run Composite Wiring Synthesis to synthesize the wiring in the vehicle:
a. Press Space Bar and enter CWS; the Wiring Synthesis dialog box is displayed.
b. Select Full Synthesis and click Go; a progress bar is displayed.
c. When synthesis is complete, click Close.
2. View the signal map for the inline pair P3 / J3:
In the Design Browser (Design tab), right-click on the J3 harness and select Signal
Figure 9-15. Signal Map for P3 and J3

February 2016
The Connector Mating table at the top indicates that one connector P3 is mapped to one
connector J3 and they both have 13 cavities.
The Signal Mappings tab indicates that signals and wires are mapped to those cavities.
The Cavity Matings tab displays 13 rows in which the P3 cavities (numbered 1 to 13)
are mated with the equivalent cavities on J3 (that is, P3 cavity 1 is mated with J3 cavity
1, and so on).
Figure 9-16. Cavity Matings for Inline Pair P3 and J3
The Wire Info tab has been added to the dialog box during wiring synthesis and lists the
details of all the wires that have been mapped to the inline pair.
3. Add a 2-cavity connector to each side of the inline pair:
a. In the Connector Mating table, click the cell in the mating row for the P3 and J3
connectors and click Add Connector Mapping ( ).
A new connector mating row is added:

Figure 9-17. New Connector Mating Row for Inline Pair
There are now two connectors (P3 and P3_1) on the IP side of the inline pair and
two connectors (J3 and J3_1) on the DOOR-PASS side. P3 is mated with J3. P3_1
is mated with J3_1.
b. In the No. of Cavities cells for P3_1, and J3_1, specify that they each have 2
cavities.

February 2016
The Cavity Matings tab indicates that:

o the P3_1 connector cavities are mated to the equivalent J3_1 connector cavities
(that is, P3_1 cavity 1 to J3_1 cavity 1, and so on).
Figure 9-18. Cavity Matings for Inline Pair
The Signal Mappings tab displays rows for the new cavity matings and indicates
that no signals are currently mapped to the cavities of the new connectors.
Figure 9-19. Signal Mappings for Inline Pair

February 2016
Note
Note that if you select one of the connector mating rows in the top Connector
Mating table, the Signal Mappings and Cavity Matings tabs display only
details related to that specific connector mating. You can click the Clear Selection
button to display the details for all connector matings.
4. With one of the rows in the Connector Mating table selected, click the Show Fanout
( ) button at the top right corner of the Connector Mating table to view the fanout
diagram for the connectors J3, P3, J3_1 and P3_1.
Figure 9-20. Fanout for Inline Pair
The fanout is used to specify whether any add-on bundle length is required for a wire to
pass from the end of the harness bundle to the cavities of the connectors. The length
value uses the standard unit of measurement applied to harnesses by your company.
At the moment, this indicates no add-on is required for any of the connectors which
means that both J3 and J3_1 would be directly at the end of the DOOR-PASS harness
and P3 and P3_1 would be directly at the end of the IP harness.

February 2016
You will specify that:

• the wires for the A-6SPKR option need an add-on of 10 to reach the cavities of the
2-cavity J3_1 and P3_1 connectors.
• the wires for the A-2SPKR and A-4SPKR options need an add-on of 50 to reach the
cavities of the 12-cavity J3 and P3 connectors (this could be because it clips onto the
harness in a different way).
To do this:
a. Click P3_1 in the top left window (as in Figure 9-20); the bundle add-on graphic for
it is highlighted in red. In the Length field on the left, enter 10. You may need to
click outside of the field several times before the length is updated on the fanout
diagram
b. Click J3_1 in the top right window; the bundle add-on graphic for it is highlighted in
c. Click P3 in the top left window; the bundle add-on graphic for it is highlighted in
red. In the Length field on the left, enter 50. You may need to click outside of the
d. Click J3 in the top right window; the bundle add-on graphic for it is highlighted in

February 2016
The dialog box should look similar to this:

Figure 9-21. Updated Fanout for Inline Pair
e. Click Close to exit the dialog box.

5. Specify that you want the signals for the A-6SPKR option to go to the P3_1 and J3_1
cavities.
The signals 2N-SPKR-RT-1 and 2N-SPKR-RT-2 are the signals for that option.
Note
You can identify that the signals 2N-SPKR-RT-1 and 2N-SPKR-RT-2 are the
signals for the A-6SPKR option by looking at the Wire Info tab. Find where A-
6SPKR is displayed in the Option Expression column and check the signals in the
Signal column for those rows.
You will map them as follows:


February 2016

To do this:
a. In the Signal Mappings table, unmap 2N-SPKR-RT-1 from P3 cavity 12 and J3
cavity 12 by clicking on the Signal column cell for P3 cavity 12 and selecting the
blank option at the top of the drop-down list.
Figure 9-22. Unmapping 2N-SPKR-RT-1
The Signal column cells in that mapping row become blank and a new row is added
to the top of the table. This new row contains the unmapped 2N-SPKR-RT-1 signal
and no Connector or Cavity values.
Figure 9-23. Unmapped 2N-SPKR-RT-1 in New Row
b. In the Connector Mating table, click the P3_1 to J3_1 mating; the Signal Mappings
table displays the unmapped signal row and the two mapping rows for the P3_1 and
J3_1 connectors.
c. In the Signal Mappings table, map the 2N-SPKR-RT-1 signal to P3_1 cavity 1
(and therefore also to J3_1 cavity 1) by clicking on the Signal column cell for P3_1
cavity 1 and selecting 2N-SPKR-RT-1 from the drop-down list; the unmapped
signal row disappears from the table.
Figure 9-24. Mapping 2N-SPKR-RT-1 to P3_1 Cavity 1
d. Repeat steps a to c for signal 2N-SPKR-RT-2, unmapping it from P3 cavity 13 / J3

cavity 13 and mapping it to P3_1 cavity 2 (and therefore also to J3_1 cavity 2); the
Signal Mappings table now has two rows with no signals.

February 2016
Figure 9-25. Signal Mappings with Two Rows with No Signals
6. In the Connector Mating table, reduce the number of cavities on the P3 and J3
connectors from 13 to 11; the Signal Mappings rows with no signals disappear.
Figure 9-26. Rows with No Signals Disappeared
Note
When you remapped the 2N-SPKR-RT-1 and 2N-SPKR-RT-2 signals, you also
remapped the wires that carry those signals.
Related Topics

February 2016
Usage Example - Setting Two Preferred Signals for One

Cavity in the Signal Map of an Inline Connector
The following usage example demonstrates how to use a signal map to set two preferred signals
for one cavity when working with connector refinement and signal mapping. You may want to
do this for two signals that are mutually-exclusive in a vehicle. Rather than using two cavities
where one is always empty, the signals can share a single cavity.
In this example, the signals 2N-SPKR-RR-1 and 2N-SPKR-RR-2 are mutually-exclusive and
are mapped to an inline connector P3. You will map them to cavity 2 on P3. P3 is mated with
the inline connectors J3 and J3_1. Therefore, you will also be mapping the signals to inline
connector J3 cavity 2 and inline connector J3_1 cavity 2.
To do this, you will first set 2N-SPKR-RR-1 as the preferred signal for the mapping between
P3 cavity 2 and J3 cavity 2, then duplicate that cavity mapping and then change the preferred
signal to 2N-SPKR-RR-2 in duplicate mappings.
Procedure
1. In the Design Browser (Design tab), right-click on the P3 harness and select Signal
The Connector Mating table indicates that Generalized Connector P3 is mapped to the
specialized connectors J3 and J3_1.
Figure 9-27. P3 Mapped to J3 and J3_1
The Signal Mappings tab indicates that P3 cavity 1 is mapped to J3 cavity 2.

Figure 9-28. P3 Cavity 1 Mapped to J3 Cavity 2
2. Map 2N-SPKR-RR-1 to J3 cavity 2. To do this:

On the Signal Mappings tab, click the Preferred Signal cell for that mapping and
select 2N-SPKR-RR-1.
Figure 9-29. 2N-SPKR-RR-1 Mapped to J3 Cavity 2
Note that 2N-SPKR-RR-1 is also automatically set as the preferred signal for the
mapping between P3 cavity 2 and J3_1 cavity 2. This is because the system assumes

February 2016
Refining a Slot Connector on a Slot
that you will want that signal to go to P3 cavity 2 even when it is mated with J3_1
instead of J3.
3. Duplicate the mapping between P3 cavity 2 and J3 cavity 2. To do this:
Select that mapping and click Duplicate Cavity ( ); a duplicate of this mapping is
added to the table.
Note that a duplicate of the mapping between P3 cavity 2 and J3_1 cavity 2 is also
added to the table.
4. In the Preferred Signal cells for the two duplicate mappings, change 2N-SPKR-RR-1
to 2N-SPKR-RR-2.
Related Topics

You can refine a slot connector (generalized connector) on a slot by creating specialized
connectors for it.
See “Connector Refinement and Signal Mapping” on page 209 for an overview of refined
connectors.
Procedure
1. Select the slot connector or slot in the Diagram Window or Design Browser (Design tab)
and either:
• Right-click on the selected object and select Signal Map
• Press Space Bar and enter Signals
The Signal Map Dialog Box for Slot is displayed.
2. In the Connector Mating table, click the cell displaying the name of the slot connector
and click the Add Connector Mapping ( ) button; a new row for a specialized
connector is added to the table.
3. For the specialized connector, specify the Name and Part Number or Number of Pins.
4. Repeat steps 2 and 3 for each specialized connector that you want to create for the slot
connector.

February 2016
Mapping a Signal to a Hole or Slot Connector Cavity on a Slot
5. Optionally, create a Fanout diagram for the slot connector:

a. Click a cell displaying the name of the slot connector or one of the specialized
connectors in the Connector Mating table and click the Show Fanout ( ) button;
the Fanout Viewer Dialog Box is displayed.
b. Select a specialized connector in the Node tree located at the top of the dialog box
and specify a Length for the bundle segment connecting to that specialized
connector.
Note
In the node tree, you can reorder the connectors and add new bundle nodes.
c. Repeat step b for each specialized connector and then click Close; you return to the
Signal Map Dialog Box for Slot.
6. Click OK.
Results
• The specialized connectors are not displayed in the Diagram Window or Design
Browser (Design tab) but are saved in the signal map for the slot.
Related Topics
Mapping a Signal to Multiple Slot Connector Cavities on a Slot
Updating the Signal Maps for Slots
Mapping a Signal to a Hole or Slot Connector

Cavity on a Slot
You can map a signal and wire to a hole or slot connector cavity (either a generalized connector
or a specialized connector) on a slot.
Procedure
1. Select the slot, hole or slot connector in the Diagram Window or Design Browser

February 2016
2. On the Signal Mappings tab, find the row for the Signal and Wire and select the
connector or hole (Connector column) and Cavity.
3. Click OK.
Related Topics
Mapping a Signal to Multiple Slot Connector

Cavities on a Slot
In some scenarios, such as fuse boxes. it is necessary to map a signal from a single device pin to
cavities on more than one connector.
This topic details how to map a signal and wire to multiple slot connector cavities (either on
Generalized Connectors or Specialized Connectors) on a slot.
Procedure
1. Select the slot or one of its holes / slot connectors in the Diagram Window or Design
2. On the Signal Mappings tab, select the existing mapping row for the Signal and Wire
and click the Duplicate Cavity ( ) button; a new row containing duplicate values is
created.
3. In the new row, select the connector or hole (Connector column) and Cavity for this
second mapping of the signal and wire.
4. Repeat steps 2 and 3 for each mapping that you want to create for the signal and wire.
5. Click OK.
Related Topics

February 2016

You can update the signal maps for selected slots.
This action evaluates whether signals are mapped to the correct slot connectors so that harnesses
are routed correctly.
Procedure
1. Select the slots in the Diagram Window or the Design Browser (Design tab), press
Space Bar and enter Update Slot Signals.
2. The current signal mappings are evaluated and changes made accordingly:
• if a signal cannot be routed via the current mapping, all slot connectors on the slot
are evaluated as possible routes
• if another slot connector allows the routing of an otherwise unroutable signal, the
mapping is changed to enable a successful route (this action takes any Map To
Same Cavity by Signal Attribute/Property constraints)
Related Topics
Refining an Interface Connector

You can refine an interface connector (generalized connector) by creating specialized
connectors for it.
connectors.
Procedure
1. Select the interface connector in the Diagram Window or Design Browser (Design tab)
and either:
The Signal Map Dialog Box for Interface Connector is displayed.

February 2016
Mapping a Signal to an Interface Connector Cavity
2. In the Connector Table, click the cell displaying the name of the interface connector and
click the Add Connector Mapping ( ) button; a new row for a specialized connector
is added to the table.
3. For the specialized connector, specify the Connector name, and Part Number or No. of
Cavities.
4. Repeat steps 2 and 3 for each specialized connector that you want to create for the
interface connector.
5. Optionally, create a Fanout diagram for the interface connector:
a. Click a row in the Connector Table and click the Show Fanout ( ) button; the
Fanout Viewer Dialog Box is displayed.
b. Select a specialized connector in the Node tree located at the top of the dialog box
connector.
Note
c. Repeat step b for each specialized connector and then click Close; you return to the
Signal Map Dialog Box for Interface Connector.
6. Click OK.
Results
Browser (Design tab) but are saved in the signal map for the interface connector.
Related Topics
Interface Connector

You can map a signal and wire to an interface connector cavity (either a generalized connector
or a specialized connector).
Procedure
and either:

February 2016
Refining an Inline Connector

2. In the Signal Mappings table, find the row for the connector cavity and select the Signal
by either:
• clicking this field and select the name of an existing signal from the drop-down list
• entering the name of a new signal and pressing Enter. Note that any new signals
created in this Signal Map dialog box do not have any corresponding functional nets
initially.
3. Click OK.
Related Topics
Interface Connector

You can refine the halves of an inline pair (generalized connectors) by creating specialized
connectors for them.
connectors.
Procedure
1. Select either half of the inline pair in the Diagram Window or Design Browser (Design
tab) and either:
The Signal Map Dialog Box for Inline is displayed.
2. In the Connector Mating table, click the cell in the mating row for the inline halves
to be refined and click the Add Connector Mapping ( ) button; a new row for a
specialized connector is added to the table.
3. For the new specialized connector on one side of the inline, specify the Connector name,
and Part Number or No. of Cavities.
4. Repeat steps 2 and 3 for each specialized connector that you want to create for the first
inline half.

February 2016
Mating the Cavities of the Two Halves of an Inline Connector
5. Mate one of the new specialized connectors with a generalized connector or specialized
connector on the other inline half by double-clicking the Connector cell on the other side
of the mating row and either:
• selecting an existing connector name from the drop-down list
• entering a new connector name and pressing Enter to create a new specialized
connector on the second inline half
6. Repeat step 5 for each specialized connector created on the first inline half.
7. Optionally, create Fanout diagrams for the inline halves:
a. Click a row in the Connector Mating table and click the Show Fanout ( ) button;
the Fanout Viewer Dialog Box is displayed.
b. Select a specialized connector in either Node tree located at the top of the dialog box
connector.
Note
c. Repeat step b for each specialized connector of each inline half and then click Close;
you return to the Signal Map Dialog Box for Inline.
8. Click OK.
Results
Browser (Design tab) but are saved in the signal map for the inline pair.
Related Topics
Mapping a Signal Between Cavities on the Halves of an Inline Connector
Mating the Cavities of the Two Halves of an Inline

Connector
You can mate the cavities of the two halves of an inline pair (either generalized connectors or
specialized connectors).

February 2016
Procedure
tab) and either:
2. On the Cavity Matings tab, each row represents a mating of cavities from each inline
half (either Generalized Connectors or Specialized Connectors). In the Cavity columns,
specify the cavities that you want to mate. Either:
• click on the table cell and select an existing cavity name from the drop-down list. If
the selected cavity is used in another cavity mating row, the previous value from the
row being edited moves to that row.
• enter a new name for the cavity and press Enter; the old cavity name is updated to
the new name wherever used in this table. Not possible if the connector has a library
part.
3. When all cavities are mated correctly, click OK.
Related Topics
Mapping a Signal Between Cavities on the Halves

of an Inline Connector
You can map a signal and wire between the cavities of the two halves of an inline pair (either
generalized connectors or specialized connectors).
There are several reasons why you may want to do this:
• Specific signals are not allowed within a certain proximity of each other.
• Positive and negative signals are not allowed next to each other.
• A particular cavity may be able to take a thicker wire than other cavities.
• You are mapping signals for a particular option to a particular connector.

February 2016
Procedure
tab) and either:
2. On the Cavity Matings tab, each row represents a mating of cavities from each inline
half (either Generalized Connectors or Specialized Connectors). Ensure that the cavities
of each inline half are mated with each other correctly. Specify any changes in the
Cavity columns.
3. On the Signal Mappings tab, each row represents the signal mapping between mated
cavities from the inline halves. For a signal mapping row, select the Signal that is
mapped between those mated cavities.
Note
If wiring has not yet been synthesized when you edit the signal map, you can select a
signal in the Preferred Signal column. This assigns the cavity to a signal and the
wiring synthesis process will use this cavity as a preference for the signal rather than
using an unassigned cavity or creating a new cavity.
4. Repeat step 3 for each signal mapping that you want to change.
5. Click OK.
Related Topics
Mapping Multiple Shield Signals to One Backshell

Termination on an Inline Connector
You can map multiple shield signals to one backshell on both halves of an inline pair.
Procedure
tab) and either:

February 2016

2. On the Signal Mappings tab, each row represents the signal mapping between mated
cavities or backshell terminations from the inline halves. In the row containing the
backshell, select the first shield Signal that is mapped to the backshell.
3. With the first mapping row for the backshell selected, click Duplicate Cavity ( ); a
new row containing duplicate values is added.
4. In the new row, specify the second shield signal to be mapped.
5. Repeat steps 3 and 4 for each shield signal to be mapped to that backshell.
6. Click OK.
Related Topics
Creating Variant Wire and Variant Signal Mappings

on the Signal Mappings Tab for a Slot
You can create variant signals and variant wires on the Signal Mappings tab of a Signal Map
dialog box for a slot.
Prerequisites
• The option codes required for the variant option expressions must exist in the project.
Procedure
1. Select a slot, a slot’s slot connector or a hole on a slot in the Diagram Window or Design
2. Click the Signal Mappings tab, select the rows for the Signals or Wires for which you
want to create variant mappings and click the Manage Variance ( ) button; the
Manage Variance Dialog Box is displayed.

February 2016
3. Add the variant option expressions that will be applied to mappings for the signals or
wires:
a. Click the Add a new option ( ) button; the Set Variant Dialog Box is displayed.
b. Define a variant option expression and click OK; the variant option expression is
displayed in the Manage Variance dialog box.
c. Repeat steps a and b for each variant option expression that will be applied to the
variant signal or wire mappings.
d. Click OK on the Manage Variance dialog box; for each of the selected signal or wire
rows, duplicate rows are created so that there is one row for each of the variant
option expressions that you have applied. The Signal and Wire columns display the
variant option expression in brackets (). In addition, a new row is added on the Wire
Info tab for each mapping of the variant wires.
4. On the Signal Mappings tab, specify the cavity to which each mapping of the variant
wires / signals is mapped.
Related Topics
Inline
Slot or Inline
Creating Variant Wire and Variant Signal Mappings

on the Signal Mappings Tab for an Inline
You can create variant signals and variant wires on the Signal Mappings tab of a Signal Map
dialog box for an inline.
Prerequisites
Procedure
1. Select an inline in the Diagram Window or Design Browser (Design tab) and either:

February 2016
Deleting a Variant Wire and Variant Signal Mapping on the Signal Mappings Tab for a Slot or Inline
2. Click the Signal Mappings tab, select the rows for the Signals or Wires for which you
wires:
variant option expression in brackets (). In addition, a new row is added on the Wire
Info tab for each mapping of the variant wires.
Related Topics
Inline
Slot or Inline
Deleting a Variant Wire and Variant Signal Mapping

on the Signal Mappings Tab for a Slot or Inline
You can delete a mapping for a variant signal and a variant wire on the Signal Mappings tab of
a Signal Map dialog box for a slot or an inline.
Note
Unmapped variant wires and signals are deleted automatically when you close the Signal
Map dialog box.
Procedure
1. Select a slot, a slot’s slot connector, or an inline in the Diagram Window or Design

February 2016
Editing the Variant Option Expression of a Variant Wire Mapping on the Wire Info Tab for a Slot or
The Signal Map dialog box is displayed (see Signal Map Dialog Box for Inline or
Signal Map Dialog Box for Slot as appropriate for full details of the dialog box).
2. Click the Signal Mappings tab, select the row for the wire / signal and click the
Manage Variance ( ) button; the Manage Variance Dialog Box is displayed.
3. Select the variant option expression that applies to the mapping and click the Delete
selected options button; the variant option expression is deleted from the dialog box.
4. Click OK on the Manage Variance dialog box; the dialog box closes and the mapping
row is removed from the Signal Mappings tab on the Signal Map.
Related Topics
Slot or Inline
Editing the Variant Option Expression of a Variant

Wire Mapping on the Wire Info Tab for a Slot or
Inline
You can edit the variant option expression for a variant wire on the Wire Info tab of a Signal
Map dialog box for a slot or an inline.
Prerequisites
• The variant wire must have been created on the Signal Mappings tab of the Signal Map
dialog box for the slot or inline. See “Creating Variant Wire and Variant Signal
Mappings on the Signal Mappings Tab for a Slot” on page 248 or “Creating Variant
Wire and Variant Signal Mappings on the Signal Mappings Tab for an Inline” on
page 249.
Procedure
1. Select a slot, a slot’s slot connector, or an inline in the Diagram Window or Design
The Signal Map dialog box is displayed (see Signal Map Dialog Box for Inline or
Signal Map Dialog Box for Slot as appropriate for full details of the dialog box).

February 2016
2. Click the Wire Info tab, select the row for the variant wire mapping and click Set
Variance ( ); the Set Variant Dialog Box is displayed.
3. Specify the variant option expression that will apply to the mapping of the variant wire
and click OK; the Variant field on the selected row is updated with the variant option
expression.
Related Topics
Inline
Creating Variant Signal and Wire Mappings in the

You can create variant signals and variant wires in the Signal Map dialog box for an interface
connector.
Prerequisites
Procedure
and either:
2. In the Signal Mappings table, select the rows for the Signals or Wires for which you
wires:

February 2016
variant option expression in brackets ().
4. On the Signal Mappings table, specify the cavity to which each mapping of the variant
wires / signals is mapped.
Related Topics
Interface Connector
Deleting a Variant Signal Mapping in the Signal Map

for an Interface Connector
You can delete a variant signal and a variant wire mapping in the Signal Map dialog box for an
interface connector.
Note
Unmapped variant wires and signals are deleted automatically when you close the Signal
Map dialog box.
Procedure
and either:
The Signal Map Dialog Box for Interface Connectordisplays.
2. In the Signal Mappings table, select the row for the mapping of the variant signal /wire
and click the Manage Variance ( ) button; the Manage Variance Dialog Box is
displayed.
3. Select the variant option expression that applies to the mapping and click the Delete
selected options button; the variant option expression is deleted from the dialog box.
4. Click OK on the Manage Variance dialog box; the dialog box closes and the mapping
row is removed from the Signal Mappings table on the Signal Map.

February 2016
Related Topics
Interface Connector
Creating a Variant Connector in the Signal Map for

a Slot, Inline or Interface Connector
You can create a variant connector for a generalized connector or specialized connector in the
Signal Map for a slot connector, inline connector or interface connector. For example, you may
want to left-hand drive and right-hand drive variants of a connector in a vehicle.
connectors.
Procedure
1. Select a slot, a slot’s slot connector, an inline or an interface connector in the Diagram
Window or Design Browser (Design tab) and either:
The Signal Map Dialog Box for Slot, Signal Map Dialog Box for Inline or Signal Map
Dialog Box for Interface Connector is displayed.
2. In the Connector Table at the top of the signal map, click the cell displaying the name of
the connector for which you want to create a variant and click the Create Variant
Connector ( ) button; the Set Variant Dialog Box is displayed.
If you are editing an inline, select the : column and click the Create Variant Connector
( ) button so that a variant is created for the connectors on both halves of the inline
(both with the same option expression).
3. Define the variant option expression that applies to the variant connector and click OK;
a new row for the variant connector is added to the Connector Table. The variant
connector has the same part number and number of pins as the original connector. For
the variant connector, the Signal Mappings tab contains a row for each cavity. These
cavities have the same signals and wires mapped to them as the original connector
cavities but will have the new variant option expression applied to them.
Results
• The variant connector is displayed below its generalized connector in the Design
Browser (Design tab).

February 2016
Related Topics

February 2016

February 2016
Chapter 10
Editing Slots
This chapter contains details of how to edit slots after they have been created in a diagram:
Slot Circuit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Internal Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259
Removing Unused Connectors, Holes and Cavities from Slots . . . . . . . . . . . . . . . . . . . . 262
Modeling Direct to Device Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263
Equipotential Nets at a Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265
Comparison of Use of Equipotential Attribute, Equipotential Global Attribute and Equivalence
Sets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Setting the Equipotential Attribute for a Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Setting the Equipotential Global Attribute for a Shared Pin . . . . . . . . . . . . . . . . . . . . . . . 267

February 2016
Editing Slots
Slot Circuit
Slot Circuit
The Generate Slot Circuit facility enables you to create a new Capital Logic design and
connectivity for the interior of a slot in a Capital Integrator Design. The connectivity is
generated for a specific vehicle configuration. You also have the option of creating a diagram of
the connectivity. Before you can do this, you must have placed devices and synthesized wiring
for the vehicle configuration in the Capital Integrator design.
The connectivity is determined from the functional devices placed in the slot, the signals on the
pins of the functional devices and the pin map to the slot connectors.
The slot circuit that is generated includes each functional device that is placed in the slot.
Connectivity between these functional devices is defined as net conductors. A logical
connector is added for each slot connector from the Capital Integrator design.
If a slot is integral to the harness, this means one or more slot connectors have been marked as
integral. See “Including a Slot with a Harness” on page 111 for more information. In this case,
one logical connector is generated that combines all of the integral slot connectors.
If devices have been combined in Capital Integrator, a single device is used in the slot circuit. If
shared devices are placed in the slot, only one device represents the complete shared device in
the slot circuit.
If there are variant placements in the slot, only the placements that are active for the selected
vehicle configuration are generated in the slot circuit.
Variant connectors (bundle fan-outs) do not affect the slot circuit that is generated because these
model the connector plug ends. The slot circuit only uses the receptacle (jack) ends of
connectors that are considered to be part of the equipment. The receptacles do not vary with
vehicle configurations.
Note
The Generate Slot Circuit facility makes no distinction between backshells and cavities
and therefore uses the same graphics for both.
Generating a Slot Circuit

You can generate a slot circuit for a specific slot.

February 2016
Editing Slots
Internal Signal
Procedure
1. Either:
• Click on the slot in the Diagram Window or in the Design Browser (Design tab),
press Space Bar and enter Generate Slot Circuit.
• Right-click on the slot and select Generate Slot Circuit.
The Generate Slot Circuit Dialog Box is displayed.
2. On the Design tab, specify the Name, Revision, Short Description, Description, Release
Level and Abstraction.
3. If you want the system to generate a diagram for the design, select Generate diagram.
4. On the Filter tab, use the drop-down list to select the Vehicle Configuration for which
you want to generate the slot circuit.
Results
• The design is added to the tree in the Project Browser Window at the top left of the
application window.
• If you have generated a diagram, this is opened automatically in the diagram window.
Related Topics
Slot Circuit
Internal Signal
A signal associated with a placed functional device in a slot is mapped to the slot cavities by the
device pins that carry the signal by default. Sometimes a signal may appear only within a single
slot for a particular configuration and there is no need for its wiring to be routed outside of the
slot.
You can unmap a signal from slot cavities so that associated wiring is not routed when wiring is
synthesized. The signal is then given the status internal. An internal signal is not considered an
error, although this scenario involves unmapped device pins. Internal signals are listed in the
Design Browser (Design tab).
A signal has an internal status if all of the active hit points for it are within one slot and none of
them are mapped to a cavity. An active hit point is a placed device pin that is active in the
currently active vehicle configuration.
The system changes the internal status of a signal to a non-internal status as necessary when
various actions are performed on the diagram.

February 2016
Editing Slots
Internal Signal
Internal signals can be edited in the Signal Map for a slot. See “Connector Refinement and
Signal Mapping” on page 209 for more information.
Examples of Internal Signals

Example A:
A Capital Logic design has four devices and four nets connected as follows:
Figure 10-1. Design with Four Devices and Four Nets
In Capital Integrator, the device are placed in slots as follows:
Figure 10-2. Devices Placed in Slots
Signals COND11 and COND12 are completely within one slot and can be internal.

February 2016
Editing Slots
Internal Signal
Example B:
A Capital Logic design has four devices and three nets connected as follows:
Figure 10-3. Design with Four Devices and Three Nets
In Capital Integrator, DEV1 and DEV2 are placed together twice in separate slots using variant-
based placement:
Figure 10-4. Devices Placed in Slots Using Variant-Based Placement
Signal COND12 can be internal for the current configuration as long as the device pins of
COND12 are active only in one of the slots but not both.

February 2016
Editing Slots
Removing Unused Connectors, Holes and Cavities from Slots
Alternatively, the devices may be placed as below using variant-based placement:
Figure 10-5. Alternative Variant-Based Placement
In this case, COND12 can still be internal if the hit points are active on the left slot but not on
the right and bottom slots.
Removing Unused Connectors, Holes and

Cavities from Slots
You can remove unused slot connectors, holes and cavities from selected slots.
An unused cavity does not connect to any wires and is on a connector that does not have a
library part assigned. It also either:
• does not map to a placed device

• maps to a device in a junction box and is not the only cavity to which the device pin
maps
Unused slot connectors and holes are not attached to any bundles, have no cavities and have no
library part assigned.
Procedure
1. Select the slots in the Diagram Window or Design Browser (Design tab).
2. Either:
• press Space Bar and enter Remove Unused Connectors and Cavities

February 2016
Editing Slots
Modeling Direct to Device Connections
• right-click on a selected slot and select Remove Unused Connectors and Cavities
Unused connectors, holes and cavities are removed from the slots.

You can model wires connected directly to devices across the Capital applications. Such
connections are referred to as direct to device connections or D2D connections.
Capital Library
A direct to device connection must be modeled as part of a device footprint.
1. Create a connector for which the Include on BOM option on the Base tab of the
Component Maintenance dialog box is unselected.
2. Add the connector to a device connector footprint for the device for which you want to
create the direct to device connection. See Update/Edit Device Footprint in the
Capital Library User Guide.
Capital Interactive Flow using Capital Logic

The Capital interactive flow is where you manually define wiring in Capital Logic.
1. Add the device with the footprint to a logical diagram. See Adding a Device from
Capital Library in the Capital Logic User Guide.
2. Connect the device to wire conductors in the logical diagram. See Creating /Moving/
Deleting a Wire Conductor in the Capital Logic User Guide.
3. Specify the harness attribute for any wire conductors that you want to synchronize with
a harness design in Capital HarnessXC. See Specifying the Harness Attribute for an
Object in the Capital Logic User Guide.
4. In Capital HarnessXC, synchronize the logical design with the harness design. See
Harness Synchronization in the Capital HarnessXC User Guide.
Note
If a footprint connector is defined as included on BOM, it is ignored during the
synchronization and all of the connected wiring is ignored too. If a footprint
connector is defined as not included on BOM, it is included in the synchronization and
so is any connected wiring.
Capital Generative Flow using Capital Logic and Capital Integrator

The Capital Logic generative flow is where you use Capital Logic to design the logical
connections in a harness and use Capital Integrator to synthesize the wiring.

February 2016
Editing Slots
1. Add the device with the footprint to a logical diagram. See Adding a Device from
Capital Library in the Capital Logic User Guide.
2. Connect the device to net conductors in the logical diagram. See Creating/Moving/
Deleting a Net Conductor in the Capital Logic User Guide.
3. Place the device in a slot in a Capital Integrator design. See Placing a Device in a Slot
in the Capital Integrator User Guide. Capital Integrator detects the connector in the
footprint that is set as “not included on BOM” and maps the connector to a hole with a
name using the format [DeviceName]:[DeviceConnectorName]. If a hole with a
matching name already exists, that hole is used. If a hole with that name does not exist, a
new hole is created.
4. Synthesize wiring for the Capital Integrator design. See “Synthesizing Wiring” on
page 440.
5. In Capital HarnessXC, synchronize the harness design with the topological design. See
Harness Synchronization in the Capital HarnessXC User Guide.
Capital Harness XC
When you synchronize a logical design with a harness design, Capital HarnessXC detects the
device connector that is set as “not included on BOM”, selects the relevant part from the library
and places it on the harness diagram.
When you synchronize a topological design with a harness design, Capital HarnessXC detects
where a hole has been used for a device connector that is set as “not included on BOM”, selects
the relevant part from the library and places it on the harness diagram.

February 2016
Editing Slots
Equipotential Nets at a Pin

In Capital Logic, you can connect several nets to a single device pin. When Capital Integrator
synthesizes wiring, it treats each of these nets as a different signal and creates a multiterm at the
appropriate connector cavity. This is ideal for the case where a pin can be connected to different
signals depending on the vehicle configuration (that is, when the nets are tagged with options).
However, in some cases, you may want to treat these nets as a single signal during wiring
synthesis. This allows synthesis rules to control the creation of either multiterms or spliced
wires for this signal. Although this can be achieved with equivalence sets, you can also define
the equivalence of the nets directly within the Capital Logic design. To do this, you set the
Equipotential attribute for the pin to which the nets connect.
In Capital Logic, it is possible that several pins with an Equipotential attribute are connected.
In Capital Integrator, all connected and equipotential nets will be combined into a single signal
that uses the name of one of the equipotential nets.
In Capital Integrator, the Design Browser (Design tab) displays the signal and lists all of the
nets below it.
In the case of shared pins, the Equipotential attribute is stored on each instance of the pin. This
provides a way of varying its value in different designs or different revisions of the same design.
It also allows separate groups of nets to be merged resulting in multiple signals on the pin.
However, this mechanism means that it is necessary to connect all the shared nets that are to be
merged onto the same instance of the device pin. In some cases, this is not desirable. For such
cases, you can use the Equipotential Global attribute on a shared pin. This results in all nets
connected to any instance of that pin being merged.
When a signal in Capital Integrator includes nets which have been merged using more than one
mechanism, the signal name is determined using the following precedence (that is, 1 overrides 2
and 3, and 2 overrides 3):
1. Equivalence Set name (if there is one)

2. Global Equipotential attribute value (if there is one)
3. Equipotential attribute value (if there is one)
Comparison of Use of Equipotential Attribute, Equipotential Global Attribute and
Equivalence Sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266
Setting the Equipotential Attribute for a Pin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

February 2016
Editing Slots
Comparison of Use of Equipotential Attribute, Equipotential Global Attribute and Equivalence Sets
Setting the Equipotential Global Attribute for a Shared Pin . . . . . . . . . . . . . . . . . . . . . 267
Comparison of Use of Equipotential Attribute,

Equipotential Global Attribute and Equivalence
Sets
Use of the Equipotential attribute or equivalence sets provide similar functionality. That is, the
ability to merge nets that have been defined separately into a single signal. This contrasts with
combining wires/signals, which does not provide that ability. Combining wires is completely
manual and does not any effect on synthesis. Combining wires is intended for the specific case
where a physical implementation of the wiring requires a single wire to implement multiple
(exclusive) signals.
Equivalence sets can be defined only in Capital Project. This means that they can be used to
modify the merging of signals even when all the system designs are released and are therefore
read-only.
The Equipotential attribute is defined on an instance of a device pin. That means that it is
stored within a design and can therefore be revised with that design. In other words, you can
have multiple revisions of a system design and the definition of equipotential signals can be
different in each.
Use of the Equipotential Global attribute is very similar to the use of the Equipotential
attribute. The main difference is that Equipotential requires you to connect all the nets you
want to combine to a single instance of a device pin. However, Equipotential Global allows
you to combine all nets connected to any instance of the device pin.
Related Topics
Setting the Equipotential Attribute for a Pin
Setting the Equipotential Global Attribute for a Shared Pin

You can set the Equipotential attribute for a pin in Capital Logic.
For details of the effect of setting this, see “Equipotential Nets at a Pin” on page 265.
Procedure
1. Right-click on the device pin and select the Properties option from the pop-up menu.
2. The Edit Properties facility is displayed. Go to the Attributes section of the General
tab.

February 2016
Editing Slots
3. For the Equipotential attribute, click in the Value field and select a net name from the
drop-down list. The listed nets are those that connect to the pin. The name that you select
is the name that will be used for the single signal in Capital Integrator.
If you select the blank value for the Equipotential attribute, the nets will not be treated
as equipotential.
Note
If the selected net is later deleted, the attribute changes to reference another net
connected to the pin. If the deletion leaves just one net connected to the pin, the
attribute remains set so that the equipotential behavior is preserved in case another net is
later multitermed at the pin.
4. Click the OK button to exit the Edit Properties facility.
Note
When wiring is synthesized in Capital Integrator, the system recognizes the
equipotential attribute and creates a single signal containing the connectivity of all
the nets attached to this device pin. This signal is synthesized as a single entity.
Related Topics
Setting the Equipotential Global Attribute for a

Shared Pin
You can set the Equipotential Global attribute for a shared pin in Capital Logic.
For details of the effect of setting this, see “Equipotential Nets at a Pin” on page 265.
Procedure
1. Right-click on an instance of the shared device pin in Capital Logic and select the
Properties option from the pop-up menu.
2. The Edit Properties facility is displayed. Go to the Attributes section of the General
tab.
3. For the Equipotential Global attribute, enter a string in the Value field; this value is
used as the name of the combined signal in Capital Integrator.
Note
When the Equipotential Global attribute is set, the Equipotential attribute is
disabled but is not cleared. The Equipotential Global value overrides the
Equipotential value when the combined signal is named in Capital Integrator.

February 2016
Editing Slots

Related Topics

February 2016
Chapter 11
Editing the Attributes and Properties of
Objects
This chapter contains details of how to use the Edit Properties dialog box to edit various
attributes and properties of design and diagram objects.
You can select individual or multiple objects for which you want to edit properties.
Accessing an Edit Properties Dialog Box for a Design or Diagram Object . . . . . . . . . . 269
Editing of Multiple Objects Simultaneously . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270
Specifying the Name of an Object in a Design or Diagram . . . . . . . . . . . . . . . . . . . . . . . 271
Displaying a Conductor Name For Multiple Segments of a Conductor . . . . . . . . . . . . . 273
Displaying an Object's Short Description Attribute in a Diagram . . . . . . . . . . . . . . . . . 273
Assigning a Library Part to an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Library Part Usage in Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274
Updating the Details of an Object's Library Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275
Removing a Library Part from an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276
Viewing the Library Part Details for an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277
Selecting a Component Part Number in the Part Selection Dialog Box . . . . . . . . . . . . . 277
Performing a Batch Update of Library Parts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Specifying the Physical Length of a Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278
Assigning an Option Expression to an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279
Editing an Object Attributes and Graphical Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . 280
Using Quick Editing for Object Attribute Displayed on Diagram . . . . . . . . . . . . . . . . . 281
Adding a Property to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282
Deleting a Property from an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283
Specifying How an Object is Displayed Graphically in a Diagram . . . . . . . . . . . . . . . . 284
Foreground, Background and Manual Color Options. . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Advanced Naming Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284
Accessing an Edit Properties Dialog Box for a

Design or Diagram Object
To edit the properties for an object, you must access the Edit Properties dialog box for an object.

February 2016
Editing the Attributes and Properties of Objects
Editing of Multiple Objects Simultaneously
Procedure
1. Right-click on an object in the Project Browser Window, Logical Designs Browser
(Function tab), Design Browser (Design tab), Configuration Setting Browser Window
(Configuration tab) or Diagram Window and select Properties; the Edit Properties
2. If you want to select multiple segments of a conductor (net or wire) in Capital Logic,
bundle in Capital Integrator or multiple objects, hold down the Shift key on your
keyboard and click the segments and objects. Selected objects are displayed in red.
3. If you select a conductor (net or wire) or bundle from a browser window, all segments
are selected automatically.
4. If you want to select a closed graphic, you must click on the border (outline) of the
graphic.
Related Topics
Edit Properties Dialog Box

You can select multiple objects in order to edit properties and attributes that apply to all of those
objects.
If you select multiple objects of different object types, the selection of tabs displayed on the
Edit Properties facility 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.
If any of the selected objects are frozen, you can edit only graphical properties.
You cannot edit equipotential nets as part of a multiple selection.
Related Topics
Specifying the Name of an Object in a Design or Diagram
Displaying an Object's Short Description Attribute in a Diagram

February 2016
Assigning a Library Part to an Object

Updating the Details of an Object's Library Part
Removing a Library Part from an Object
Viewing the Library Part Details for an Object
Selecting a Component Part Number in the Part Selection Dialog Box
Performing a Batch Update of Library Parts
Assigning an Option Expression to an Object
Editing an Object Attributes and Graphical Display
Adding a Property to an Object
Deleting a Property from an Object
Specifying How an Object is Displayed Graphically in a Diagram
Specifying the Name of an Object in a Design

or Diagram
You can specify the name of an object in a design or a diagram.
Procedure
1. Right-click on an object in the Project Browser Window, Logical Designs Browser
2. On the General tab, specify the Name of the object. If valid names for the object type
have been created, 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, you can edit the name only if the signal is not
associated with a functional source net conductor from the associated Capital Logic
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, the Name Selection dialog box lists only the

February 2016
names that are used in the usage definitions by default. You can display all available
names for the object type by unchecking the Filter on Usage box at the top of the dialog
box. See the Capital Project 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, 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 Library. See the Capital Library help system for more information about
defining pin types.
In Capital Symbol, you can specify the pin type U that means that no pin type is
specified.
3. If you want the specified name to be displayed with the object in the diagram, select the
Visible box next to the Name field and then click the Edit Attributes ( ) button to
display the Edit Name Text Attributes Dialog Box where you specify how the text is
displayed in the diagram. Click OK on the Edit Name Text Attributes dialog box when
finished.
Note
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. See
“Displaying a Conductor Name For Multiple Segments of a Conductor” on page 273 for
more information. If name text has been added to segments previously and has not been
deleted, checking the Visible box will display the name text for each instance of name
text that has been added.
4. Click OK on the Edit Properties dialog box; the dialog box closes and the text is
displayed on the diagram.
Related Topics
Displaying a Conductor Name For Multiple Segments of a Conductor
Displaying an Object's Short Description Attribute in a Diagram

February 2016
Displaying a Conductor Name For Multiple Segments of a Conductor
Displaying a Conductor Name For Multiple

Segments of a Conductor
If the name of a conductor (nets, wires and shields in Capital Logic, bundles in Capital
Integrator) has been set as Visible in the conductor's general properties, the name of the
conductor is displayed once on the diagram by default.
See “Specifying the Name of an Object in a Design or Diagram” on page 271 for more
information about displaying an object's name.
You can display the name more than once along the course of a conductor.
Procedure
1. Ensure that the name of the conductor has been set as visible in the conductor's general
properties.
2. Select one or more segments of the conductor next to which you want to display the
conductor name and right-click one of the selected segments. Select the Add Name
Text menu option from the pop-up menu. Alternatively, select one or more segments of
the conductor, press Space Bar and enter Name Text.
3. The name of the conductor is displayed next to each selected segment and follows the
property style preferences that have been specified in Capital Project.
Related Topics
Displaying an Object's Short Description

Attribute in a Diagram
If an object has a name that has been specified as a valid name in Capital Project and the valid
name has a short description associated with it, the short description can be displayed with the
instance of the object on the diagram.
Note
If the Short Description specified for the name has changed in Capital Project, you must
reassign the name to the object to update the Short Description in the diagram. See
“Specifying the Name of an Object in a Design or Diagram” on page 271.
Procedure
1. Right-click on an object in the Diagram Window and select Properties; the Edit
Properties Dialog Box is displayed.

February 2016
2. On the General tab, select the Visible box next to the Short Description field and then
click the Edit Attributes ( ) button to display the Edit Name Text Attributes Dialog
Box where you specify how the text is displayed in the diagram. Click OK on the Edit
Name Text Attributes dialog box when finished.
3. Click OK on the Edit Properties dialog box; the dialog box closes and the text is
Related Topics

You can assign a component library part to an object.
See Library Part Usage in Capital Integrator for detailed notes on the use of library parts in
Capital Integrator.
Procedure
See Assigning a New Library Part to an Object in the Capital Design Tools - Common
Related Topics
Library Part Usage in Capital Integrator

If a slot has been included with a harness, a library part can be assigned to the underlying
physical connector. To do this, you continue as though assigning a library part to the slot, but
the library part is really assigned to the connector.
Footprint Library Parts

In Capital Logic 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 Integrator.

February 2016
When the device with the footprint is placed in a slot in Capital Integrator, the physical
connectors are defined by this information. This means that you cannot delete related slot
connectors in a slot that has such a library part assigned.
Parts on Slots
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.
Parts on Specialized Connectors and Generalized Connectors

You can assign a library part to a slot 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 dialog box 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
“Connector Refinement and Signal Mapping” on page 209) to assign library parts to the
individual specialized connectors. If a specialized connector has been defined by a footprint in
Capital Logic, you cannot assign a library part to it in Capital 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 Library is filtered to show only those with the an equal or greater
number of cavities to the device in the design.
Related Topics
Updating the Details of an Object's Library

Part
You can update the details of an object’s library part in a design with changes that have been
made to the library part in the component library.
See Library Part Usage in Capital Integrator for detailed notes on the use of library parts in
Capital Integrator.

February 2016
Procedure
1. Right-click on the object in the Project Browser Window, Logical Designs Browser
2. On the General tab, click the Update ( ) button in the Library Part section; the details
for the library description are updated in the Edit Properties dialog box.
Related Topics

You can remove a component library part from an object.
Procedure
2. On the General tab, click the Remove ( ) button in the Library Part section; the
details for the library description are removed from the Edit Properties dialog box.
Related Topics

February 2016

You can view the details for a library part that has been assigned to an object.
Procedure
See Viewing the Library Part Details for an Object in the Capital Design Tools - Common
Related Topics
Selecting a Component Part Number in the

Part Selection Dialog Box
You can 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
See Selecting a Component Part Number in the Part Selection Dialog Box in the Capital Design
Tools - Common Functions User Guide.
Related Topics

February 2016

You can perform a batch update of library part information for objects based on the Part
Number attribute for each object. The action can update library part information for all objects
in the currently active design or in a build list to which that design belongs.
Note
You can use extensibility plugins to assign part numbers to objects. Having used such a
plugin, you can then use this batch update functionality to update the association of library
parts. 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.
Procedure
See Performing a Batch Update of Library Parts in the Capital Design Tools - Common
Related Topics

You can specify (edit or override) the physical length of a bundle.
The physical length is initially determined by the length of the bundle in the diagram.
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.
Procedure
1. Right-click on the bundle in the Project Browser Window, Logical Designs Browser

February 2016
2. On the General tab, select Override next to the Length field and change the value in the
field.
Related Topics

You can assign an option expression to an object.
Procedure
2. On the General tab, enter the option expression in the Option field in the Configuration
section. You can either enter the expression manually or click the ellipsis button (...) to
display the Edit Option Expression Dialog Box.
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
application. See the Capital Project 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 Expression box, the
text is displayed in red and the OK button is disabled. If you attempt to enter an invalid
expression in the Edit Option Expression dialog box, an error message is displayed.
3. If you want the specified option expression to be displayed with the object in the
diagram, select the Visible box next to the Option field and then click the Edit
Attributes ( ) button to display the Edit Name Text Attributes Dialog Box where you
specify how the text is displayed in the diagram. Click OK on the Edit Name Text
Attributes dialog box when finished.
Related Topics

February 2016
Editing an Object Attributes and Graphical

Display
You can edit the attributes of an object.
Attributes are listed in the Attributes table on the General tab of the Edit Properties Dialog Box
for an object. They must not be confused with properties on an object.
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 (for example, Connector

Plating Material = Tin on a wire). No use is made of the properties within Capital other than
the ability to display and report them.
The attributes that are displayed in the Attributes table for an object vary depending on the type
of object.
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 grayed out. If you enter an invalid value, it changes to
red.
The Show All Attributes option is selected by default. Unselect this option to display only the
editable attributes on this tab.
Procedure
2. On the General tab, edit the attributes in the Attributes table as required.
Note
If harness names have been created in Capital Project, you can click the ellipsis (...)
button by the Harness attribute value to select one. In Capital Logic, you can specify
the Harness attribute for an object either on the General tab of the Edit Properties
facility or using the Edit Harness Attribute facility.

February 2016
Using Quick Editing for Object Attribute Displayed on Diagram
Note
Editing Multiple Objects Simultaneously
If you have selected multiple objects of different object types, all of the attributes for
all of the selected objects are displayed, but you can edit only those attributes that apply
to all of the selected objects. If there are multiple values for an editable attribute,
Multiple Values is displayed in the Value field with a drop-down list of the different
values. You can select one of these values to apply it to all selected objects or you can
leave the field as Multiple Values so that the objects retain their different values. If a
library part is assigned to any of the selected objects, the attributes cannot be edited.
3. If you want an attribute value to be displayed with the object in the diagram, select the
Visible box for that attribute and click the Edit Attributes ( ) button to display the
Edit Graphical Attributes Dialog Box where you can specify graphical attributes for the
display of the attribute value on the diagram.
4. When you have edited the attributes, you must click the OK button to exit the Edit
Properties facility and to commit your changes.
Related Topics
Using Quick Editing for Object Attribute Displayed on Diagram
Using Quick Editing for Object Attribute

Displayed on Diagram
You can perform a quick edit of an object attribute value that is displayed on a diagram (for
example, the object’s name). This action does not work for user-defined properties or option
expressions.
Prerequisites
• The attribute value must be visible on the diagram.
Procedure
1. Double-click on the attribute value in the diagram window; an editable window
containing the value is displayed.
2. Edit the value as required and press Enter; the value is updated in the diagram window.

February 2016
Note
If pre-defined values are available for selection, an ellipsis (...) button is displayed
next to the field. Click that button to select a value. You can expand the window to
display the full Edit Properties dialog box for the object by clicking or by pressing ALT
+ Up Arrow. You can hit the Esc button on your keyboard to cancel the action at any
time. If you want to edit the graphical display of the text, select it on the diagram and
press ALT + Enter on your keyboard to display the Attribute Text dialog box.
Related Topics

You can add a user-defined property to an object.
Properties are listed in the Properties table on the Properties tab of the Edit Properties Dialog
Box for an object. They must not be confused with attributes on an object.
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. No use is made of the

properties within Capital other than the ability to display and report them.
Note
Editing Multiple Objects Simultaneously
If you have selected multiple objects of different object types, all of the properties for all of
the selected objects are displayed, but the values do not necessarily apply to all of the selected
objects. 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 click on it. Check this box 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 drop-down list of
the different values. You can select one of these values and check 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 drop-down 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, then you cannot edit it and
Different Types is displayed in the Value field

February 2016
Procedure
2. On the Properties tab, click the New button; the New Property dialog box is displayed.
3. Specify the name of the property and click OK; the property is added to the Properties
table.
Note
If a drop-down list of names is available, the property names in the drop-down list
are predefined for object types in a project in Capital Project. See the Capital Project
help system for more information on creating them. When a project is defined in Capital
Project, the valid values for the property can be specified. If you enter a property value
that is not valid in Capital Logic or Capital Integrator, a warning is displayed.
4. Specify the property’s Value and the Type of value it can have.
5. Select the Visible box if you want the property value to be displayed with the object in
the diagram and click the Edit Attributes ( ) button to display the Edit Graphical
Attributes Dialog Box where you can specify graphical attributes for the display of the
property value on the diagram.
6. Click OK to exit the Edit Properties dialog box.
Related Topics

You can delete a user-defined property from an object.
Procedure
2. On the Properties tab, select the property in the Properties table and click the Delete
button; the property is deleted from the table.

February 2016
Specifying How an Object is Displayed Graphically in a Diagram
Related Topics
Specifying How an Object is Displayed

Graphically in a Diagram
You can use the Edit Properties dialog box to specify the graphical attributes of an object in a
diagram.
Procedure
1. Right-click on the object in the Logical Designs Browser (Function tab), Design
Browser (Design tab), Configuration Setting Browser Window (Configuration tab) or
Diagram Window and select Properties; the Edit Properties Dialog Box is displayed.
2. On the Graphical tab, specify the Primary Color, Thickness, Line Style, Secondary
Color and Fill Pattern Selection (if available).
Related Topics
Foreground, Background and Manual Color

Options
Wherever you can select a color, the list contains particular options (in addition to color names).
• 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 vice versa.
• Manual
The Choose Object Color dialog box is displayed, where you can select a color.
Advanced Naming Functionality

There are three types of object name that are involved with advanced naming functionality.

February 2016
• Default names - these are generated automatically.

• Fixed names - these are defined in the Properties for objects and set as a fixed. See
“Specifying the Name of an Object in a Design or Diagram” on page 271 for more
information about how to do this.
• Generated names - these are based on the naming compositions set up in the advanced
naming functionality in Capital Project. 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.
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. For example, the condition
"color"="Blue" matches all objects with the property set to "Blue".
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” on page 65 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.
If you want to use the advanced naming conventions, you can:
• Use the Generate Advanced Names dialog box to generate them for specific selected
objects. See Generating Names for Selected Objects in a Diagram in the Capital Design
• Use the Generate Advanced Names dialog box to generate them for all objects in a
build list, design or diagram. See Generating Names for all Objects in a Build List,
Design or Diagram in the Capital Design Tools - Common Functions User Guide.

February 2016

February 2016
Chapter 12
Rules and Constraints
This chapter contains details of how to apply rules and constraints to objects in Capital
Integrator.
Overview of Rules and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287
Evaluation of Rules on Bundle Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Creating a Strategy for Constraint Definition in Capital Integrator . . . . . . . . . . . . . . . 294
Standard Constraints for Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Usage Examples for Rules and Constraints in Capital Integrator . . . . . . . . . . . . . . . . . 313
Using Rules to Add Properties and Attributes to Wires, Splices and Multicores During Wiring
Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Using a Constraint to Set Properties and Attributes on Objects . . . . . . . . . . . . . . . . . . . . . 314
Using a Constraint to Manage the Length of a Jumper Wire . . . . . . . . . . . . . . . . . . . . . . . 315
Using a Constraint to Manage the Length of Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Overview of Rules and Constraints

Rules and constraints can be used in the design applications to control certain actions.
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
• Rules
• Object Rule Hierarchies in Capital Integrator
When starting to work with this toolset, it is recommended that you create an organized strategy
for using constraints:
• “Creating a Strategy for Constraint Definition in Capital Integrator” on page 294
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.

February 2016
For example (in Capital Integrator):
Don't place devices with property matching Name=Battery here.
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 in Capital Integrator to define a constraint.
The templates listed below in this topic are standard in Capital Integrator. You can write your
own custom constraints in Java and load them into Capital Integrator. 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 Capital Integrator, 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 not loaded any longer in Capital
Integrator. See “Running Design Rule Checks Manually” on page 73 for more information
about running design rule checks.
For further details about constraints, see Creating a Strategy for Constraint Definition in Capital
Integrator and Assigning a Rule or Constraint to an Object in the Capital Design Tools -
Rules
A rule is a group of constraints that can be applied to a whole design or to individual objects in
a diagram. You can define rules from within Capital Integrator or from within Capital Project.
In Capital Project, 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 help system for
more information about defining rule libraries.
For further details about rules, see Defining Rules in the Capital Design Tools - Common
Functions User Guide or Assigning a Rule or Constraint to an Object in the Capital Design
Object Rule Hierarchies in Capital Integrator

Rules and constraints 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, there are the
following general hierarchies that determine which constraint is used on each object:
• Bundle hierarchy
A constraint on a bundle overrides a constraint on a harness. A constraint on a harness
overrides a constraint on a design.

February 2016
• Slot hierarchy
A constraint on a slot overrides a constraint on a design.
• Cavity hierarchies
A constraint on a cavity overrides a constraint on a slot connector. A constraint on a slot
connector overrides a constraint on a slot. A constraint on a slot overrides a constraint on
a design.
• Inline cavity hierarchy
A constraint on an inline cavity overrides a constraint on an inline connector. A
constraint on an inline connector overrides a constraint on a design.
An inline connector inherits rules and constraints from the design but does not inherit
constraints from any connected harnesses.
Caution
Constraints of the same type (that is, they potentially conflict) use the rule resolver
mechanisms described below. Constraints of different types (that is, they do not
directly conflict) are not evaluated in any particular sequence. This is not usually a
problem because most constraints are evaluated at different times anyway. However,
there can be an issue if you have different but related constraints. For example, one
constraint sets the attribute CSA and then another constraint uses the CSA to assign a
different attribute/property. In this case, you cannot guarantee it will work correctly.
You need to re-evaluate (that is, trigger) the constraints multiple times in order to be
sure they are assigned correctly.
Hierarchical Object Rule Resolver

The following rule resolver works vertically within these hierarchies:
• First Match Wins

This resolver is used in the hierarchies listed above and starts from the lowest object in
the hierarchy and works its way up until it finds a matching constraint for that object and
then stops.
For example, a Max Wires per Splice constraint on a bundle overrides a Max Wires
per Splice constraint on the harness to which a bundle belongs.
Same Level Object Rule Resolvers

If an object has multiple constraints of the same type but with different values on the same level
within the hierarchy, additional rule resolvers are used to evaluate the rules:
• Max Value

February 2016
In this scenario, the constraint with the largest value on that level of the hierarchy
overrides the other constraints on that level. Examples of numeric constraints that follow
this type of rule resolver are:
o Minimum Splice Separation
o Cost of wire per unit length
o Cost of splice
For example, a bundle has a constraint Cost of splice = 5 and a constraint Cost of splice
= 10. In this case, the constraint Cost of splice = 10 is used.
• Min Value
In this scenario, the constraint with the smallest value on that level of the hierarchy
overrides the other constraints on that level. Examples of numeric constraints that follow
this type of rule resolver are:
o Max Wires per Splice
o Max Wires per Multiterm
For example, a bundle has a constraint Max Wires per Splice = 10 and a constraint
Max Wires per Splice = 5. In this case, the constraint Max Wires per Splice = 5 is
used.
• Don’t Overrides Do
In this scenario, any instance of a boolean constraint set to Don't will override another
instance of that constraint set to Do within that hierarchy. Examples of constraints that
follow this type of rule resolver are:
o Place by Property
o Route by Property
• Prioritized Pattern Match
For constraints that set attributes or properties, the system uses a special resolver based
on how closely the constraint matches the object in question. For example, if one of the
constraints matches exactly (that is, with no wild-cards), then this will override a more
general match based on wild-cards. Similarly, a constraint with some normal characters
and some wild-cards will override the default match of .*.
For example:
A specific match such as Name = Sig01 overrides a refined wild card value such as
Name = Sig.*. However, the refined wild-card overrides a broad default such as Name
= .*

February 2016
Evaluation of Rules on Bundle Regions
Note
After trying to resolve constraints using the Prioritized Pattern Match mechanism,
the system may still not be able to determine which constraint wins. In this case, it
reports an error message when evaluating the constraints.
The Effect of Collective Objects

Some rule evaluations are based on a single object hierarchy. For example if there is a Cost of
Splice constraint on a bundle, the system needs to evaluate the object rule on the bundle only.
However, some rule evaluations are based on a collective rule effect of the rules on the objects
on the same level of the hierarchy and those on other levels of the hierarchy.
For example:
A wire passes through a two regions on a bundle. The regions have Cost of wire per unit
length constraints with different values. As a result of the regions being in the same ruled object
level, the system evaluates both rules collectively using the Max Value rule resolver for objects
on the same level. Additionally, the system ignores any Cost of wire per unit length
constraints on other levels of the hierarchy because it uses the First Match Wins rule resolver
for objects in the hierarchy.
For further information, see Evaluation of Rules on Bundle Regions and Creating a Strategy for
Constraint Definition in Capital Integrator.

A rule on a bundle region has a higher priority than a rule of the same type on the bundle.
Evaluations of rules on bundle regions can be divided into two categories:
• The bundle region rules are collected and evaluated along with the rules on the bundle
hierarchy to which the bundle region belongs.
• The bundle region rules are collected and evaluated directly as well as with the rules on
the bundle hierarchy and the position of objects (bundle end nodes, splices) in relation to
the bundle regions is significant for the evaluation results.
Considerations by Rule Types

• Route by Property
If the bundle hierarchy has a Don't Route rule and the region has either a Don't Route
or Do Route rule, the False Overwrites True rule resolver is used in a simple
hierarchical evaluation and the route cannot finish at the bundle.

February 2016
If the bundle hierarchy has a Do Route rule and the bundle region has a Do Route rule,
a simple hierarchical evaluation is performed and it allows routing at the bundle.
If the bundle hierarchy has a Do Route rule and the region has a Don't Route rule,
normally the route cannot finish at the bundle because the region blocks the wire path
when a simple hierarchical evaluation is performed.
However, if there is a condition as follows:
Then, if necessary, it should be possible to allow finishing the partial route as follows:
• Max Wires per Splice

The region hierarchy rules are evaluated at the splice location. At each level in the
hierarchy, the rule with the minimum value wins and controls the number of wires
allowed on the splice. The router does not look up further on the bundle hierarchy
because it uses the First Match Wins rule resolver.

February 2016
If the rule on the region states that the region cannot have any splices and the router must
determine a splice location on the bundle, the router skips the region and searches for
other locations along the bundle.
Similarly, if the rule on the region states that no more wires can connect to the splice
inside the region, then any splices outside of the region are scanned for a possible route.
• Cost of Wire per Unit Length
If there are rules on regions along the wire path, the rule with the maximum value wins
and controls the cost. The router does not examine other levels of the object hierarchy
because it uses the First Match Wins rule resolver.
If there are no region rules, then the bundle hierarchy rules of the wire path are
evaluated.
For example:
In this case, the wire cost for wires connecting SP1 and SP2 and connecting SP2 and P2
is the value from the region rule. The wire cost for wires connecting P1 and SP1 is the
value from the bundle rule.
When the router is determining a splice location on the bundle and scans in this region,
the router compares the route cost for this formation with the route cost for a formation
where the splice stays outside of the region. This is because moving a splice into the
region may result in a greater number of wires.
• Cost of Splice
hierarchy, the rule with the maximum value wins and controls the cost. The router does
not look up further on the bundle hierarchy because it uses the First Match Wins rule
resolver.
When the router determines a splice location on the bundle and scans this region, the
router compares the route cost for a splice in the region against the route cost for a splice
outside the region.
• Minimum Splice Separation
hierarchy, the rule with the maximum value wins and controls the distance. The router
does not look up further on the bundle hierarchy because it uses the First Match Wins
rule resolver.

February 2016
Creating a Strategy for Constraint Definition in Capital Integrator
When the router determines a splice location in the region and uses a region rule to
control the splice separation, the router ensures that there is the minimum allowed
distance between any splices regardless of whether they are inside or outside the region.
• Wire Part Specification
If there are region rules along the wire path, prioritized pattern matching is used to find
applicable rules. Regardless of whether a valid result is found, the router does not look
up further on the bundle hierarchy because it uses the First Match Wins rule resolver.
Note
Max Wires per Multiterm and Terminal Type Specification rules are not applied
to bundle regions.
Related Topics
Creating a Strategy for Constraint Definition in

Capital Integrator
When starting to work with this toolset, it is recommended that you create an organized strategy
for defining and using constraints. This ensures the re-usability and consistency of the
constraints across vehicle programs.
Do:
• Assign constraints as high up the hierarchy as possible (that is, at design and harness
level). This avoids duplication of constraints on multiple objects.
• Define constraints that use properties/attributes specified on logical objects. This
enables constraints to be very generalized and a single constraint can apply to multiple
objects. Using a property defined on a symbol removes the need for an engineer to
remember to add it.
Do not:
• Define constraints that use object names (unless absolutely necessary). These
constraints are very specific and may require constant editing and management.

February 2016
Defining a Strategy
One approach to defining the initial constraints used by an organization is as follows:
• Breakdown the available constraint templates into their areas of influence:

o Placement
o Wire Routing
o Wire Synthesis
o Network Synthesis
o Wiring Specification
o Ground Design
• Consider each area in turn and determine the requirements:
o What control do you need over the resulting objects synthesized in Capital
Integrator?
o It may be necessary to experiment to determine how to achieve the exact control
required. Custom constraints can help make this easier.
• Define generically applicable constraints:
o Try to define default constraints that can be applied at the design level.
o Try to define groups of constraints that can be applied together (for example, as a
rule).
• Expect to refine the constraints over time.
The following sections provide further details for constraint strategies related to particular areas
of functionality.
Placement Constraints Strategy

Placement of devices into slots is influenced by the following main constraints:
• Option place by Attribute/Property

• Place by Attribute/Property
By default, there is a placement rule on any design that places devices into slots with the same
name.
There are limited strategies available for device placement. You can either use a name-based
placement strategy or a property-based one. If possible, consider using symbol properties to
drive placement as these can be defined once avoiding errors. It is also good to use consistent

February 2016
names/properties to allow placement rules to be re-used across vehicle programs. Custom

constraints can allow some additional flexibility.
Wire Routing Constraints Strategy

Wire routing is an integral part of synthesis. It is the control of which paths through a vehicle
harness topology are taken by each signal. Wire routing is influenced by the following main
constraints:
• Route by Attribute/Property
• Cost of wire per unit length (Note that wire has a cost of 1 per unit length by default)
• Cost per wire for Inline/Junction Box
The first of these constraints provides an absolute method of control (for example, never use
this path for this signal). The second and third constraints, when applied to a subset of the
signals, can be considered a hint to synthesis (that is, prefer one path over another if possible).
These constraints are self-explanatory and not many strategies are available. However, note that
the first constraint may stop synthesis from finding any solution at all. For this reason, you may
want to use the other constraints where possible. The router will find the optimum route based
on wire length and costs. However, the first constraint can be useful to keep classes of signal
separate (for example, through parallel or similar paths).
Consider using the second constraint to limit the use of certain paths requiring expensive wire
types (for example, high temperature) or where a routing channel has limited space available.
The third constraint is often used for safety or ground signals, where it is highly desirable for all
connections to be made within a single harness.
Wire Synthesis Constraints Strategy

Achieving the required synthesis solution in terms of numbers and positions of splices and
multi-terms can be the most challenging part of defining constraints. Wire synthesis is
influenced by the following main constraints:
• Cost of splices
• Cost of wire per unit length
• Cost of multiterm
• Cost per wire for Inline/Junction box
• Max Wires per Multiterm

February 2016
The first two constraints are used to trade-off wire length against splice cost. They provide the
major control over splice creation. By default, the system assumes that the cost of a splice is
zero and that the cost of wire per unit length is one. This means, it will use as many splices as
necessary to ensure that there are no overlapping wires in a signal (resulting in a splice at every
harness takeout where three wires are required). As the cost of splice increases (in relation to the
cost of wire per unit length), the system will tend to reduce the number of splices and increase
the amount of additional wire. If, for example, two splices were initially placed at takeouts 100
units apart, you would need the cost of a splice to be100 times greater than the cost of a wire per
unit length before the system would effectively combine these splices (that is, use one splice
instead of two).
The Cost of multiterm constraint is similar but it controls the trade-off between splices and
multi-terms. As indicated above, as splice cost increases, the system will tend to increase the
amount of overlapping wire. This can lead to multi-terms being created in preference to splices.
This constraint will reduce that tendency (although typically multi-terms are prohibited by the
majority of cases using the Max Wires per Splice constraint).
The Max Wires per Multiterm and Max Wires per Splice constraints are usually defined
based on physical or mechanical requirements (for example, splice parts available). They are
often used to provide differing control for signal classes (for example, power and ground can be
multi-termed, but other signals cannot). These constraints can also be used to prohibit splices or
multi-terms completely (for example, no splices in a wet harness).
The Minimum Splice Separation constraint may only require a single default rule (on the
design) to define allowable spacing.
Network Synthesis Constraints Strategy

Networks (such as LIN, CAN or FlexRay) typically require very specific synthesis constraints
to ensure the generated wiring adheres to the network specification. The “Network termination”
constraint is designed to provide explicit control over network synthesis.
Wiring Specification Constraints Strategy

Wire specification is influenced by the following constraints:
• Wire Specification
• Splice Separation
• Multicore Specification
• Terminal Type Specification
• Length change for Wire
When defining these constraints, it is important to consider all downstream requirements. In the
majority of cases, it should be possible to use defaults (for example, on the design). For

February 2016
Standard Constraints for Capital Integrator
example, a single constraint can set a wire attribute based on a value specified on the logical net.
Wherever possible, apply constraints to classes of signals (for example, using properties). This
provides a straightforward mechanism for engineers designing systems to assign a meaningful
value to an object, without having to be concerned about the resulting behavior in Capital
Integrator.
Related Topics

Standard constraint templates are available for Capital Integrator.
The constraints are:
Attributes and Properties

• Length change for Jumper
Allows you to automatically set the Length Change Type and Length Change Value
attributes for jumper wires (which are generated by wiring synthesis and are given a
length of 0.0 by default). The constraint can be applied to a connector, a hole, a slot or a
design.
Length change Type = Value for jumper of signal matching Name = .*
Specify the following:
o Type
Specify a Length Change Type of either:
• Absolute
The Length attribute of jumper wires is set to value of the Length Change
Value attribute.
• Offset
The Length attribute of jumper wires is set to the calculated graphical length
plus the value of the Length Change Value attribute.
o Value
Specify the value for the Length Change Value attribute. This can be positive or
negative.
o Name = .*

February 2016
Specify an attribute or property name for a signal and a value for it (you can use
wild-cards). The constraint will be applied only to jumper wires carrying signals
matching this condition.
For example:
Length change Absolute = 5.0 for jumper of signal matching Name = COND.*
In this example, the Length attribute is set to 5.0 for any jumper wires carrying signals
with a Name attribute value that starts COND.
Length change Offset = 4.0 for jumper of signal matching Name = COND.*
In this example, the Length attribute is set to the calculated graphical length plus 4.0 for
any jumper wires carrying signals with a Name attribute value that starts COND.
• Length change for Wire
Allows you to automatically set the Length Change Type and Length Change Value
attributes for wires. This is useful for increasing wire length in the case of u-turn wires.
The constraint can be applied to a bundle region, a bundle, a harness or a design.
Length change Type = Value for wire of signal matching Name = .*
o Type
Specify a Length Change Type of either:
• Absolute
The Length attribute of wires is set to value of the Length Change Value
attribute.
• Offset
The Length attribute of wires is set to the calculated graphical length plus the
value of the Length Change Value attribute.
o Value
Specify the value for the Length Change Value attribute. This can be positive or
negative.
o Name = .*
wild-cards). The constraint will be applied only to wires carrying signals matching
this condition.
For example:
Length change Absolute = 5.0 for wire of signal matching Name = COND.*

February 2016
In this example, the Length attribute is set to 5.0 for any wires carrying signals with a
Name attribute value that starts COND.
Length change Offset = 4.0 for wire of signal matching Name = COND.*
any wires carrying signals with a Name attribute value that starts COND.
Allows you to specify that a topological multicore should have an attribute or property
with a fixed value or a value derived from an attribute or property of the functional
multicore from which the topological multicore is being routed.
This is used when you want to use rules to add properties and attributes to multicores.
See “Using Rules to Add Properties and Attributes to Wires, Splices and Multicores
During Wiring Synthesis” on page 313.
• Set Integrator/Topology Attribute/Property on Object
Allows you to specify that a property or attribute must be set to a particular value on
objects of a particular type when they have another property or attribute with a particular
value. The property/attribute and value are assigned to the object when you run the
Apply Constraints action in Capital Integrator. The Violated attribute/property rule
design rule check can be run to check for objects that violate this constraint.
• Splice Specification
Allows you to specify that a splice should have an attribute or property with a fixed
value or a value derived from an attribute or property of the signal from which the splice
is being routed.
This is used when you want to use rules to add properties and attributes to splices. See
“Using Rules to Add Properties and Attributes to Wires, Splices and Multicores During
Wiring Synthesis” on page 313.
• Terminal Type Specification
Allows you to specify the specification that a terminal must have for a particular signal.
This can be added to a cavity, a slot connector, a slot or a design.
Allows you to specify that a wire should have an attribute or property with a fixed value
or a value derived from an attribute or property of the signal from which the wire is
being routed.
This is used when you want to use rules to add properties and attributes to wires. See
“Using Rules to Add Properties and Attributes to Wires, Splices and Multicores During

February 2016
Placement
• Assign Connector by Attribute/Property
This is used when you place devices with footprints in slots. It allows you to control
whether a device connector with a particular value for an attribute or property is mapped
to a slot connector with an attribute or property that has the same value.
• Assign Footprint to Device
Default: Assign part library part and footprint where slot device Name = .*
Allows you to specify the library part that is assigned to a device (with a particular
property or attribute value) when that device is placed in the slot. It also allows you to
specify which footprint from that library part is used.
For example:
Assign part device01 and footprint fp02 where slot device Name = dev01
In this example, when a device with the name dev01 is placed in a slot with this
constraint applied, the library part device01 is assigned to that device and the footprint
fp02 from that library part definition is used.
This can be set for a design or an individual slot.
Note
You can define a custom constraint in Java that will also define the pin mapping
when the part is assigned to the device. This custom constraint assigns the pin
mapping directly without the need to define device part numbers and footprints in
Capital Library. For more information about writing and loading custom constraints, see
the PluginDevelopment.pdf document that is located in the doc\plugin folder of your
installation.
• Map To Same Cavity by Signal Attribute/Property

By default, each instance of a signal and the pin for that instance are mapped to different
connector cavities when a device is placed in a slot. This constraint allows you to
specify that multiple instances of a signal and the pins for those instances are mapped to
the same connector cavity. This constraint is applied again if a re-mapping occurs.
• Option place by Attribute/Property
Allows you to specify whether objects with a particular property or attribute should or
cannot be placed conditionally with an option expression in a slot. This enables the
automatic variant-based placement of an object in multiple slots. During the automatic
placement of devices, a device is placed in any slots where it matches this constraint and
the option expression from this constraint is applied to the placed device.
The Slot that breaks placement rules design rule check will identify conflicts between
this constraint and the Place by Attribute/Property constraint and will identify any

February 2016
placed object whose option expression does not match the option expression from this
constraint. The check will not validate the option expression and it will not check for
variant placements that result in an object being active in multiple slots at the same time.
• Place by Attribute/Property
Allows you to specify whether objects with a particular property or attribute should or
cannot be placed in a slot. The system obeys this rule when automatically placing
objects. By default, any slot has the following constraint:
This constraint can be edited or removed.
Ground Refinement
• Ground Device Combination
This is relevant only to ground devices in ground slots. It allows you to specify whether
ground devices with the same value for a particular property or attribute (either on the
devices or on connected signals) are to be combined when the Auto-Refine All
Grounds or Auto-Refine Grounds operation is performed. See “Combining Ground
Devices in Selected Ground Slots” on page 191 or “Combining Ground Devices in All
Ground Slots” on page 192. This can be set for a design or an individual ground slot.
• Max Ground Slot Connector Cavities
This is relevant only to ground slots and the combining of ground devices. It allows you
to specify the maximum number of cavities that can be added to a slot connector during
the combining of ground devices. This can be set for a design or an individual ground
slot. When the maximum number of cavities has been added to a slot connector, a new
slot connector is generated. Note that external bundle connections will not be altered and
you will need to make the proper harness connections to the new slot connector. If the
maximum number of cavities is set to 1, each ground signal will have its own slot
connector with one cavity.
• Max multitermed Ground Signals
This is relevant to the combining of ground devices (see “Combining Ground Devices in
All Ground Slots” on page 192). It allows you to specify the maximum number of
ground signals that can be mapped to the same cavity in a ground slot. Any cavities that
reach or exceed this maximum will not allow more signals to be added to the multiple
termination at them during the combining of ground devices.
• Multiterm Ground Devices
This is relevant to the combining of ground devices (see “Combining Ground Devices in
All Ground Slots” on page 192). It allows you to specify whether signals of ground
devices, that have been placed in the same ground slot and have been mapped to the
same harness, form a multiple termination so that they use the same connector cavity.

February 2016
Routing
• Backshell Termination by Attribute/Property
Allows you to specify whether a signal with a particular property or attribute terminates
at a backshell or at a slot connector pin.
• Combine Wires at Cavity
Default: Do combine Wires At Splice of signals Name = .* where cavity matches Name
= .*
Can be set on connectors, slots or the design.
Allows you to specify that wires carrying particular signals should be combined at
particular cavities when the post wiring synthesis action “Combine Wires” runs.
o Do/Don’t
Specifies whether wires at the specified cavities should be combined.
o Wires/Wires At Splice
Wires At Splice
Specifies the system inserts a splice. The wires meet at the splice and a single
combined wire goes from the splice to the cavity. For example, you might want to do
this if you have three shields connecting to one cavity.
Wires
Specifies that the system does not insert a splice. The wires are replaced by one wire.
You might want to do this where the wires can be combined one side of an inline
connector but need to be separate wires on the other side.
o signals Name = .*
Specify an attribute/property and value combination to identify the wires that
combine.
o cavity Name = .*
Specify an attribute/property and value combination to identify the cavities at which
wires carrying particular signals combine. If this combination does not match a
cavity, the signals Name =.* values are ignored. That is, this setting dictates
whether the constraint is applied.
For example:
Do combine Wires At Splice of signals Name = scrn.* where cavity matches Name =
SCR

February 2016
In this example, the system will identity cavities with a Name attribute SCR. At those
cavities, it identifies wires carrying signals with a Name attribute value that starts scrn.
It inserts a splice to which those wires connect. A single combined wire for those wires
connects the splice to the cavity.
• Cost of multiterm
Allows you to specify the cost of a multiterm. By default, the cost of a multiterm is 0.
This constraint is compared with the Cost of splice constraint in order to identify
whether a multiterm or a splice is generated by wiring synthesis. The cheaper option is
generated.
This constraint can be applied to a cavity, a connector, a slot, a hole or a design. It can be
set so that it only applies if a particular signal runs along a route.
Cost of multiterm = num for where Signal matches Name = .*
o num
Specify a value to represent the cost of a multiterm. Note that this cost is added only
once for each cavity that has more than one wire (from a particular signal)
connected. The cost will not be more if, for example, there are three wires rather
than two.
o Name = .*
wild-cards). The constraint will be applied only to objects carrying signals matching
this condition.
• Cost of splice
Every bundle has a default cost of 0 for a splice. If you increase the value for a bundle,
the less likely a splice will be created on it during routing. This can be set so that it only
applies if a wire with a particular signal is included in the splice.
• Cost of wire per unit length
Allows you to specify how expensive it is to route a wire along a bundle. The higher the
cost for a bundle, the less likely a signal will be routed along it.
By default, a bundle has cost of 1 per unit length. When the system routes signals, it
looks for the cheapest (and therefore shortest) route. If routing a signal along a particular
bundle costs more (for example, if the wire requires extra shielding), you increase the
cost per unit length.
If an alternative route costs less per unit length and is not too much longer, the system
selects the alternative route.
• Cost per wire for Inline/Junction Box

February 2016
Every inline half and junction box has a default cost of 0 for a wire traversing it. If you
increase the value for an inline half/junction box, the less likely a wire will follow a
route traversing it. This allows you, for example, to trade-off the cost of additional wires
and connector cavities against the additional wire length of taking an alternative path.
The constraint can be used to specify different costs for signals with a particular
property or attribute and can be placed on an inline half or junction box itself, a harness
or a design.
Caution
For inlines, the cost is checked for each inline half independently. This enables you
to place a different cost on each half.
This constraint causes the additional cost to be added to the signal wiring during
synthesis. For an inline, the cost is added for each mated pin-pair that has wiring on both
sides. For a junction box, the cost is added once and only if no internal devices connect
to the signal. For example:
o If an inline has one or more wires connected to one half but not the other half, the
cost will not be added.
o If an inline has one or more wires from the same signal connected to one half and
one or more connected to the other half, the cost is added once for each mated pin-
pair. This ensures, for example, that the cost of moving a splice from one side of an
inline to the other can be considered. For example:
o If a junction box slot has one or more wires connected and those wires connect
internally to a placed device, the cost is not added.
o If a junction box slot has two or more wires connected and those wires connect
internally to an internal splice (and not a placed device), the cost is added only once.
• Create Bypass Wiring
Default: Don’t create bypass wiring for Splice/Signal matching Name = .*
When Composite Wiring Synthesis is run with the “Generate Bypass Wiring” option
selected, if in any harness level a splice is connected to just two wires, the system
replaces the splice and wires in that level with a single bypass wire (that has a read-only
Bypass attribute). However, there are some situations where it is necessary to retain a
two wire splice (for example, near to a connector where a larger CSA wire is required to
fit the cavity and terminal).

February 2016
This constraint allows you to control whether the generation of a bypass wire is or is not
allowed for a splice or a signal with a particular property or attribute. It can be set on a
bundle region, a bundle, a harness or a design.
• Generate center-strip Splices
Allows you to specify whether butt splices should be converted to center strip splices
when converting them automatically. This is determined by whether the signal passing
through the splice has a property or attribute with a particular value. This constraint can
be applied to a harness or an entire design.
For information on running the automatic conversion, see “Automatically Converting
Butt Splices to Center Strip Splices” on page 501.
• Map To Inline Cavity by Signal Attribute/Property
Allows you to control the cavity assignment when a signal is routed through an inline.
The signal and cavity can be specified by matching against their properties or attributes.
This constraint can be applied to an inline half, harness or design.
Note
When there is a conflict regarding signal mapping to cavities, the following priority
hierarchy is applied (first item has higher priority): signal map, preferred signal,
Map To Inline Cavity by Signal Attribute/Property constraint and normal cavity
allocation. This constraint will work only for inlines whose cavities have been created
(by adding a library part) prior to wiring synthesis.
• Max Wires per Multiterm

Allows you to specify the maximum number of wires that can terminate at one cavity.
This can be applied to any object that contains cavities (for example, a design, a
connector, a cavity). If you specify a num value of 0, no wire can terminate at the
cavities to which the rule applies.
Note
If Max Wires per Splice, Max Wires per Multiterm and other related rules are
applied to a set of related objects, Capital Integrator may not be able to synthesize all
wiring. This is because some wires may not have a route to follow due to the combined
restrictions from the rules.

Allows you to specify the maximum number of wires that can be in a splice. This can be
set so that it only applies if a wire with a particular signal is included in the splice.
• Maximum multicore takeout
Default: Maximum multicore Wire takeout length = num where signal matches Name =
.*

February 2016
Allows you to specify the maximum length of takeout (untwist) possible for the wires or
shields of a multicore when it is synthesized. This can be set so that it only applies if
particular signals are included in the multicore. This constraint can be applied to a
bundle, harness or diagram.
For example:
In the following case, the “Termination of single ended wires/shields” constraint has
been used to create dangling wires for unused signals in the multicore. Therefore, this
constraint will not be evaluated as there are no 1:1 splices.
In the following case, the “Termination of single ended wires/shields” constraint has not
been used to create dangling wires for unused signals in the multicore. Therefore, this
constraint is used and if the length of D1 and D2 is less than the specified multicore
takeout length, the splices are removed.
In the following case, a shielded multicore has a dangling shield but no dangling wires
on the inner-cores. The shield is not evaluated for this constraint because it has no 1:1
splices. Note that this constraint has no effect on pigtail splices.
However, if the multicore has no dangling shield, the shield is evaluated by this
constraint and the splice may be released. Note that the length evaluated against the
constraint is the total of the shield and the pigtail wire.

February 2016

Allows you to specify the minimum distance that there must be between a splice and a
connector, splice or takeout. This can be set so that it only applies if a wire with a
particular signal is included in the splice.
If you specify a minimum separation from connectors or splices you will also need to
specify a minimum separation from takeout nodes. The two rules are intended to work in
conjunction with one another.
• Network Specification
Can be set for a diagram only (does not work if applied to any other objects) and allows
you to control the routing of particular network multicores or signals by specifying the
following:
o max length
The maximum length of the overall network.
o min stub length
The minimum length of a stub in the network.
o max stub length
The maximum length of a stub in the network.
o min stub length
The minimum distance between stubs in the network
• Network termination
Default: Do set cavity as IxO terminated where logical Multicore matches Name = .*
Allows you to specify whether wiring synthesis sets logical pins as IxO Terminated or
not.
When wiring synthesis defines a network, it identifies logical device pins of the type
IoX Terminated as the network start and end. This information may not be available in
the associated logical designs so this constraint enables synthesis to set pins as IoX
Terminated when a multicore or signal going to that pin has a particular property or
attribute value.

February 2016
This constraint can be applied to a cavity, slot connector, interface connector, hole, slot
or diagram. It cannot be applied to an inline or its cavities.
When synthesis looks for IxO Terminated cavities, it:
o Firstly, uses this constraint and looks for a Do or Don’t
o If no matching constraint is found, defaults to using the pin type from the associated
logical design
• Pigtail Usage by Attribute/Property
Allows you to specify whether a shield signal (the shield termination of a shield
multicore) with a particular property or attribute connects to a connector using a pigtail
splice and wire or whether it connects directly into the connector.
This constraint can be used on cavities, backshell terminations or any object further up
the rule hierarchy for these objects.
• Protect Wiring by Attribute/Property
Allows you to specify whether the wiring of signals with a particular property or
attribute is protected from the following batch synthesis operations:
o Modular Wiring Synthesis
o Composite wiring synthesis (when both Clear Promoted Options and Delete all
Wiring, Harness Levels and Configurations are not selected)
o Delete all wiring
o Generate center-strip splices
o Generate option expressions
o Synthesize all wiring
Does not protect wiring from batch wire length update and batch attribute assignment.
This constraint applies separately for combined signals and their children. If the
constraint matches a combined signal, it protects wiring directly owned by the combined
signal. If the constraint matches a child signal, it protects only wiring directly owned by
the child signal.
Protected signals will not be reported as not routed or partly routed during synthesis
operations.
• Route by Attribute/Property
Allows you to specify whether signals with a particular property or attribute can or
cannot be routed along a bundle, through a junction box, or through an inline pair. This
constraint can apply to bundles, inline connectors, harnesses and designs.
• Terminate shield to pigtail near connector

February 2016
Default: Terminate shields matching Name = .* near Slot matching Name = Value
Capital Integrator is capable of synthesizing multicore shields, including connections
through pigtail wires and single-ended shields using cut-end splices. In Capital Logic,
you specify that a shield terminates at one or more pins (on devices or grounds).
However, Capital Integrator does not know which end of the multicore should be
connected to a shield termination point and arbitrarily chooses. This is often correct but
can produce unintended results in some cases. For example:
Figure 12-1. Single-ended Shield in Capital Logic
Figure 12-2. Synthesized Shield in Capital Integrator - Desired Result
Figure 12-3. Synthesized Shield in Capital Integrator - Actual Result
This constraint allows you to indicate the multicore end to which a particular single-
ended shield termination must connect (normally with a pigtail wire). It can be applied
to a slot, a connector on a slot, or a diagram.

February 2016
Typically, you would place it on the slot where the terminating device (that is, ground) is
placed. For the example already mentioned, you would place it on the GND1 slot at the
bottom:
Terminate shields matching Name = SH1 near Slot matching Name = DEV1
Figure 12-4. Desired result
You are specifying that the shield SH1 must terminate at the end of the multicore
connecting to the slot called DEV1.
Note
You can change Slot to Connector and therefore specify that it must terminate near a
particular connector on a slot.
• Termination of single ended wires/shields

Default: Do terminate single ended Wire where Multicore matches Name = .*
For cases where not all signals in a multicore connect to a device, this allows you to
specify whether wiring synthesis creates dangling wires or shields that terminate on cut-
end splices close to the device’s connector. This can be set so that it only applies for
multicores with a particular attribute or property. This constraint can be applied to a
device, a slot, a connector on a slot, or a diagram.
If Do is selected, a wire (or shield) with a cut-end splice is created on any branch of the
multicore where the signal does not connect to the device.
If Don’t is selected and the signal does not connect to the device on a branch of the
multicore, then no wire (or shield) is created but a two-wire splice exists at the splice
between multicores.

February 2016
For example:
You have the following logical connectivity:
The synthesized topological design may look like this:
In this example, there are seven physical multicores. All of them contain four wires
except for the multicore connected to slot DEV5 (bottom right), which has only two
wires.
At the middle slot DEV4, this constraint has been applied with Do selected so a wire
with a cut-end is created.
At the slot DEV5, this constraint has been applied with Don’t selected so there are no
cut ends and the wiring for the signals that do not go to this slot are spliced at the same
point as the wiring of the signals that do. These splices have just two wires connecting to
them (one from DEV2 and the other to the next splice along) as opposed to the signals
that do go to DEV5 whose splices have three wires connected (one from DEV2, one
from DEV5 and one from the next splice along).
Related Topics

February 2016
Usage Examples for Rules and Constraints in Capital Integrator
Usage Examples for Rules and Constraints in

Capital Integrator
You can use rules and constraints for specific purposes.
The following are examples of possible purposes.
Using Rules to Add Properties and Attributes to Wires, Splices and Multicores During
Wiring Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313
Using a Constraint to Set Properties and Attributes on Objects . . . . . . . . . . . . . . . . . . 314
Using a Constraint to Manage the Length of a Jumper Wire . . . . . . . . . . . . . . . . . . . . . 315
Using a Constraint to Manage the Length of Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Using Rules to Add Properties and Attributes to

Wires, Splices and Multicores During Wiring
Synthesis
You can set rules on objects so that specific properties and attributes are added to wires, splices
or multicores during wiring synthesis. The properties and attributes can have fixed values or a
value derived from an attribute or property of the signal (or functional multicore) from which
the wire or splice or multicore is being routed.
There are three constraints that you can use for this (see “Overview of Rules and Constraints”
on page 287 for more information about the general use of rules and constraints):
Allows you to specify that a wire should have an attribute or property with a fixed value
or a value derived from an attribute or property of the signal from which the wire is
being routed.
For example:
Wire Spec: Wirecolor is ValueOf(color) where Signal matches Name=.*
In this case, a wire has a Wirecolor attribute with a value derived from the value of the
color property of the signal.
• Splice Specification
Allows you to specify that a splice should have an attribute or property with a fixed
value or a value derived from an attribute or property of the signal from which the splice
is being routed.
For example:
Splice Spec: Type is ValueOf(splicetype) where Signal matches Name=.*

February 2016
Using a Constraint to Set Properties and Attributes on Objects
In this case, a splice has a Type attribute with a value derived from the value of the
splicetype property of the signal.
Allows you to specify that a topological multicore should have an attribute or property
with a fixed value or a value derived from an attribute or property of the functional
multicore from which the topological multicore is being routed.
For example:
Multicore Spec: Sheath Type is ValueOf(type) where Multicore matches Name=.*
In this case, a topological multicore has a Sheath Type attribute with a value derived
from the value of the type property of the functional multicore.
The following design rule checks are available to check for wires/splices/multicores that violate
any applicable specification constraints:
• Wires violating specification rules

• Splice that breaks specification rule
• Multicore that breaks specification rules
See “Running Design Rule Checks Manually” on page 73 for more information about running
design checks.
Related Topics
Using a Constraint to Set Properties and Attributes

on Objects
You can use the Set Integrator Attribute/Property on Object constraint to set a property or
attribute with a particular value on objects of a particular type.
Procedure
1. Set the Set Integrator Attribute/Property on Object constraint on a design or objects
within a design. You can set this constraint multiple times, specifying a different object
type and different property/attribute values each time. See Overview of Rules and
Constraints for more information about setting rules and constraints.
The constraint is:
Set Object Type AttrOrProp to Value where AttrOrProp = Value

February 2016
Using a Constraint to Manage the Length of a Jumper Wire
An example of its use is:

Set Wire Name to ValueOf(PartNumber) where EMC Category = A
In this example, if a wire has an EMC Category property of A, the Name attribute of
that wire will be set to its part number value.
2. To apply the constraint or constraints to a diagram, press Space Bar and enter ‘Apply
Constraints > Set Attribute/Property’.
The properties and attributes from the constraints are set for the appropriate objects.
Using a Constraint to Manage the Length of a

Jumper Wire
You can manage the length of jumper wires that are generated by wiring synthesis. Jumper
wires have a length of 0.0 by default.
Procedure
1. Prior to running wiring synthesis, set the “Length change for Jumper” constraint on the
necessary objects in a design (connectors, holes, slots or the design itself). See Overview
of Rules and Constraints for more information about setting rules and constraints.
2. Edit the constraint. Examples of using the constraint are:
Length change Absolute = 5.0 for jumper of signal matching Name = COND.*
In this example, the Length attribute is set to 5.0 for any jumper wires carrying signals
with a Name attribute value that starts COND.
Length change Offset = 4.0 for jumper of signal matching Name = COND.*
any jumper wires carrying signals with a Name attribute value that starts COND.
Using a Constraint to Manage the Length of Wires

You can manage additional length for wires that are generated by wiring synthesis. This is
useful for increasing wire length in the case of u-turn wires.
Procedure
1. Prior to running wiring synthesis, set the “Length change for Wire” constraint on the
necessary objects in a design (bundle regions, bundles, harnesses or the design itself).
See Overview of Rules and Constraints for more information about setting rules and
constraints.

February 2016
Using a Constraint to Manage the Length of Wires
2. Examples of using the constraint are:

Length change Absolute = 5.0 for wire of signal matching Name = COND.*
In this example, the Length attribute is set to 5.0 for any wires carrying signals with a
Name attribute value that starts COND.
Length change Offset = 4.0 for wire of signal matching Name = COND.*
any wires carrying signals with a Name attribute value that starts COND.

February 2016
Chapter 13
Composite Data Management
This chapter provides information on managing composite data in Capital Integrator.

Composite Data Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Examples of Composite Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Example Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Example Vehicle Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Example Harness Levels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Creating an Option at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338
Defining Inclusive and Exclusive Relationships for an Option . . . . . . . . . . . . . . . . . . . . . 339
Display of Option/Module Names or Option/Module Descriptions in Dialog Boxes . . . . 339
Option Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Creating an Option Folder at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Variant Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Option Expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Generating Option Expressions for Wires and Splices. . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Option Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Creating an Option Combination at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Adding a Valid Selection to an Option Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Vehicle Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Defining Vehicle Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Platform Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Specifying the Platform Options in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351
Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352
Specifying the Options that Affect a Harness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353
Creating a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Editing a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Specifying a Part Number for a Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357

February 2016
Composite Data Overview
Active Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

Harness Level Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Vehicle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Methods of Defining a Vehicle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364
Defining a Vehicle Configuration Based on Harness Levels . . . . . . . . . . . . . . . . . . . . . . . 365
Defining a Vehicle Configuration Based on Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366
Giveaway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Specifying Giveaway Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369
Usage Example - Giving Away an Option on a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . 370
Usage Example - Giving Away Together Two Mutually-Exclusive Options on a Harness 375
Harness Replacement Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385
Usage Example - Importing Multiple Harnesses Using Harness Replacement Technology 385
Exporting a Harness from Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Importing a Harness into Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

Before using Capital Integrator, you would normally have been working with a design
containing worst-case data in Capital Logic. Worst-case means all of the data for every possible
configuration of a vehicle. A worst-case scenario harness cannot be built because there would
be conflicts between some of the harness modules that the vehicle could contain.
When you associate this worst-case scenario with a Capital Integrator design, you have the
option of synthesizing wiring for the worst-case scenario (150% composite wiring) but your
ultimate aim is to synthesize wiring for each individual vehicle configuration. In order to do
this, you must set up composite data.
Hierarchy of Composite Data Elements

The following shows the hierarchy of composite data elements. Links to detailed descriptions of
the elements are listed below.

February 2016
Figure 13-1. Hierarchy of Composite Data Elements
Composite Data Concepts

Composite data consists of various concepts.
Table 13-1. Composite Data Concepts

Composite Data Concept Description
Option A code representing a feature or capability in a vehicle. See
“Option” on page 338.
Option Folder A way to organize options into groups. See “Option Folder” on
page 340.
Variant Option A special classification of option that supports mechanical
variations. See “Variant Option” on page 341.

February 2016
Table 13-1. Composite Data Concepts (cont.)

Composite Data Concept Description
Option Expression A combination of option (or variant option) codes. An example
is LHD && ABS indicating an object required only in a left-
hand drive vehicle containing the anti-lock braking system. See
“Option Expression” on page 342.
Option Combination A collection of options that have been arranged into specific,
valid selections. See “Option Combination” on page 344.
Vehicle Model A representation of a major vehicle variation. Each vehicle
model defines an allowable combination of all the variant
options and also limits the options that are applicable to each
major vehicle variation. See “Vehicle Model” on page 346.
Harness Also referred to as harness families, composite harnesses,
master harnesses and 150% harnesses. These are supersets of
actual harness products containing all optional wiring content,
even incompatible items. Examples are Instrument Panel,
Driver’s Door and Engine Harness. The harness will not be
built but is used as a container for harness levels.
Harness Level Also referred to as derivative harnesses, these are sub-sets of
the content of a harness on a vehicle, corresponding to precise
combinations of options and variant options. See “Harness
Level” on page 352.
Vehicle Configuration A vehicle configuration is a set of harness levels (one per
harness) that could be ordered and fitted into a specific vehicle.
This can be the max-complexity vehicle or a less complex
derivative. See “Vehicle Configuration” on page 364.
Giveaway Wiring content that is included in a vehicle although the
electrical features it services may not be included. See
“Giveaway” on page 369.
Related Topics
Examples of Composite Data

February 2016

The examples of composite data use a Quick Start - Automotive Generative project.
If you want to view the data in Capital Integrator, download the Project.zip file from here,
extract the contents and import the Quick Start - Automotive Generative.xml project. Open
the Vehicle Topology design:
Figure 13-2. Quick Start - Automotive Generative Project
Note
If you already have a project called Quick Start - Automotive Generative, you must
rename the project during the import.
Each example builds on the previous example.
Example Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

Example Vehicle Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324
Example Harness Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Example Options
You can view the options in a project by pressing Space Bar and entering Options.
The Options Dialog Box is displayed.
See “Option” on page 338 for a definition of an option.
The following are the default options from the Quick Start - Automotive Generative project
(see “Examples of Composite Data” on page 321 for instructions on how to access this project).

February 2016
Example Options
Figure 13-3. Example Options
The top-level Options folder contains options grouped into Option Folders.
In the option folder called Variants, you can see two Variant Options Market-LHD (Left Hand
Drive Market) and Market-RHD (Right Hand Drive Market) that have been grouped together

February 2016
Example Options
and are mutually-exclusive. Figure 13-4 shows that Market-RHD has been added to the
Exclusive window for Market-LHD:
Figure 13-4. Example Variant Options
The Audio folder contains the options related to the audio system in the vehicle.
Figure 13-5. Audio Folder
Some of these have exclusive relationships, such as A-CD (Single Disk Player) and A-CDC
(CD Changer). This is because you could not have both the Single Disk Player and the CD
Changer.
Some have inclusive relationships, such as A-4SPKR (4 Speaker - Premium Audio System) and
A-2SPKR (2 Speaker - Base Audio System). This is because the 4 Speaker - Premium Audio
System requires the wiring for the 2 Speaker - Base Audio System to be included.
Note that the A-TAPE (Tape Player) option has been marked as obsolete.
Figure 13-6. Obsolete A-TAPE Option
The Other folder contains options that relate to other features of the vehicle such as door locks
and fog lamps. Note that the options in this folder are not set as Mutually Exclusive and they
are not marked as Mandatory.
Figure 13-7. Other Folder

February 2016
Example Vehicle Models
If Mutually Exclusive was selected, none of the options in the folder could be selected together
in a vehicle.
If Mandatory was selected, at least one of the options within this folder would have to be
included in any vehicle.
The Combinations folder contains one Option Combination called AUDIO. An option
combination is used to define the complex relationships between a group of options (that is, the
possible combinations of those options that can be included in a vehicle). In this case, all of the
options involved come from the Audio option folder.
The possible combinations are displayed as a list of valid selections. Click the AUDIO option
combination to view the valid selections that are named AUDIOPHILE, PREMIUM and
BASE.
Figure 13-8. Valid Selections for AUDIO Option Combination
You can see that the AUDIOPHILE valid selection contains everything apart from A-CD
(Single Disk Player) because A-CD and A-CDC are mutually exclusive.
The BASE valid selection contains only the A-2SPKR (2 Speaker - Base Audio System) and A-
CD options.
When Harness Levels are generated later, only harness levels that adhere to these three valid
selections can be created. No other combinations of these options are required.
For the next composite data example, see “Example Vehicle Models” on page 324.
Related Topics
Option

Each vehicle model is a representation of a major vehicle variation.

February 2016
It defines the allowable selections of Variant Options, Options and Option Combinations in that
variation.
This example refers to variant options, options and option combinations seen in the “Example
Options” on page 321.
You can view the Vehicle Models in a project by pressing Space Bar and entering Models when
a diagram is open.
Figure 13-9. Example Vehicle Models
Three models are defined here:
• RHD-BS - Right Hand Drive - Basic

• LHD-BS - Left Hand Drive - Basic
• LHD-SP - Right Hand Drive - Special
Note
Vehicle models such as these are sometimes called constrained and have only STD
(and empty) options. This is not typical and would normally be used only for
describing cost-control models. You might use cost-control models when you are doing
some form of architecture study or possibly a request-for-quote. For real production
data, it is much more common to have unconstrained vehicle models where the majority
of options are OPT.
The Variants section of the table indicates which Variant Option is supported by each vehicle
model. You can see that RHD-BS supports the Market-RHD (Right Hand Drive Market)
variant option whereas LHD-BS and LHD-SP support the Market-LHD (Left Hand Drive
Market) variant option.
Figure 13-10. Variants Supported by Vehicle Models

February 2016
Note
LHD-BS and LHD-SP have the same combination of variant options (that is, only Market-
LHD). This works when you have fully constrained vehicle models but this would be bad
practice in unconstrained vehicle models (that is, models containing OPT options) because the
vehicle models tend to be redundant. In unconstrained vehicle models, you should only ever
have one vehicle model with a given combination of the variants. That is, only one vehicle
model that supports only Market-LHD and only one vehicle model that supports only Market-
RHD.
The next section of the table lists the options from the Option Folder called Other (as seen in
the “Example Options” on page 321).
Figure 13-11. Options from Option Folder Other
Each vehicle model row indicates whether the options are supported by that vehicle model:
• A blank cell indicates that the option is not supported by the vehicle model. For
example, the PWndws (Power Windows) option is not available on the RHD-BS (Right
Hand Drive - Basic) vehicle model.
• STD indicates that the option is always included in the vehicle model. For example, the
PWndws (Power Windows) option is available on the LHD-BS (Left Hand Drive -
Basic) and LHD-SP (Left Hand Drive - Special) vehicle models.
• If any options were marked as OPT, it would indicate that the option can be supported
by the vehicle model and the final product is available with or without the option. When
harness levels are generated later, this could result in a greater number of harness levels
because different ones may be required to support vehicles with and without the option.
Note
The options from the Option Folder called Audio (as seen in the “Example Options”
on page 321) are not listed here because their valid selections are controlled by an
Option Combination.
The last section of the table lists the valid selections from the Option Combination called
AUDIO (as seen in the “Example Options” on page 321).

February 2016
Example Harnesses
Figure 13-12. Valid Selections from Option Combination AUDIO
Each vehicle model row indicates whether the valid selection is supported by that vehicle
model. For example, the AUDIOPHILE valid selection is supported only by the LHD-SP (Left
Hand Drive - Special) vehicle model. If you hold the mouse cursor over one of the columns, a
tool tip displays the options that are included in that valid selection.
Figure 13-13. Options Included in Valid Selection
In this case, you can see that the options A-2SPKR, A-4SPKR, A-6SPKR, A-CDC, A-RJ and
A-SBWFR are included in the LHD-SP vehicle model.
For the next composite data example, see “Example Harnesses” on page 327.
Related Topics
Vehicle Model
Example Harnesses
Example Options
Example Harnesses
The harnesses in a design are listed under the Harnesses node of the design browser (Design
tab) on the bottom left of the application window.
These examples are the harnesses from the Quick Start - Automotive Generative project (see
“Examples of Composite Data” on page 321 for instructions on how to access this project).

February 2016
Example Harnesses
If you open the Vehicle Topology diagram of the Quick Start - Automotive Generative
project and expand the Harnesses node of the Design Browser (Design tab), you will see the
following:
Figure 13-14. Example Harnesses
There are seven harnesses, each used in a different section of the vehicle: BODY, DOOR-DR,
DOOR-PASS, ENGINE-LH, ENGINE-RH, IP and MIRROR.

February 2016
Example Harnesses
In this starter data, each harness is styled with a different color in the diagram:
Figure 13-15. Styled Harness
If you click a harness in the Design Browser (Design tab), it is highlighted in red in the diagram.
For example, if you click the BODY harness:
Figure 13-16. Highlighted Harness

February 2016
Example Harness Levels
For the next composite data example, see “Example Harness Levels” on page 330.
Related Topics
Harness

Each harness level for a harness is a sub-set of the content of that harness on a vehicle,
corresponding to precise combinations of options and variant options.
Harness levels can be defined manually or generated automatically using the wiring synthesis
facility. For this example, you will generate the harness levels using Composite Wiring
Synthesis.
This example refers to harnesses seen in the “Example Harnesses” on page 327.
Assuming that you have not edited the data in the Vehicle Topology diagram, no harness levels
exist for those harnesses yet.
Confirm that no Harness Levels Exist for the BODY Harness

Assuming that you have not edited the data in the Vehicle Topology design, no harness levels
exist for those harnesses yet.
Procedure
1. Right-click on the BODY harness in the Design Browser (Design tab) and select Define
Harness Levels.
Figure 13-17. BODY Harness in Design Browser
The Define Harness Levels - Harness:BODY dialog box is displayed and contains no
harness levels.

February 2016
Figure 13-18. BODY Harness with no Harness Levels
2. Click Cancel to exit the dialog box.
Use Modular Wiring Synthesis to Generate Wiring with Option Expressions

and Abstract Harness Levels
Modular Wiring Synthesis (MWS) generates wiring with option expressions. It does not
consider physical harness levels. This wiring can be used to determine (calculate) option
complexity and option costing information but cannot be used for composite/derivative analysis
or harness detailing. The option costing information can be used as a basis to decide which
options you want to specify as giveaway options when running Composite Wiring Synthesis.
This wiring represents a ‘full vehicle’, which is a vehicle that:
• contains all options, including exclusive ones (although exclusive wiring is not
connected together by MWS)
• is not composite, in that buildable harness levels are not generated or assigned to the
wires
Procedure
1. Press Space Bar and enter MWS; the Wiring Synthesis Dialog Box is displayed with the
default selections for MWS.
o The Update Harness Options action will identify the options that affect each
harness (including pass-through options) and promotes them onto each harness. The
required options are calculated from the slots and from wiring, and then unnecessary
options are removed.
o The Generate Abstract Harness Levels action will generate one or more special
harness levels for each harness. These special harness levels are not intended to be
built and are therefore abstract. They are created because the system requires all
physical wires to exist on at least one harness level. The abstract harness levels allow

February 2016
the wires to be persisted and this in turn allows you to do some form of investigation
or costing, and so on.
2. Click Go; a progress bar is displayed.
3. When MWS is complete click Close.
Confirm that Abstract Harness Levels Exist for the BODY Harness
MWS will have generated abstract harness levels for the BODY harness.
Procedure
Right-click on the BODY harness in the Design Browser (Design tab) and select Define
Harness Levels; the Define Harness Levels - Harness:BODY dialog box is displayed and lists
the abstract harness levels down the left side of the table.
Figure 13-19. Abstract Harness Levels for BODY Harness
The top of the table lists the vehicle models and options that can be supported by these harness
levels.
In this instance, three abstract harness levels have been generated, each equating to one of the
vehicle models. This is basically what happens with MWS: you get a maximum of one harness
level per vehicle model (unless they are identical, in which case they are combined).
For example, the BODY:LHD-BS-Abstract harness level supports the LHD-BS (Left Hand
Drive - Basic) vehicle model. Here is a reminder of the allowable selections of Variant Options,
Options and Option Combinations supported by that vehicle model:
Figure 13-20. Variant Options, Options and Option Combinations Supported by

Vehicle Model
The LHD-BS vehicle model has the following options from the Other option folder as standard
(STD): PDrLcks-Ps, PDrLcks-Dr, PWndws, FuelLid, Trunk, and Fog Lamps-FRONT.
The Define Harness Levels - Harness:BODY dialog box indicates that the BODY:LHD-BS-
Abstract harness level includes the options FuelLid and Trunk.

February 2016
Figure 13-21. Options Included in Harness Level
Note
The other options PDrLcks-Ps, PDrLcks-Dr, PWndws and Fog Lamps-FRONT are not
listed because their wiring does not pass through the BODY harness. However, they are
listed (in varying combinations) for the harness levels of other harnesses through which their
wiring does pass. For example, the PDrLcks-Dr (Power Door Locks - Driver) is listed for the
harness levels of the DOOR-DR (Driver door) harness.
The LHD-BS vehicle model supports the Base valid selection of Audio options. This valid
selection includes the A-2SPKR and A-CD options.
Figure 13-22. Valid Selection of Audio Options
The Define Harness Levels - Harness:BODY dialog box indicates that the BODY:LHD-BS-
Abstract harness level includes the option A-CD.
Figure 13-23. Inclusion of Option in Harness Level
The A-2SPKR option is not listed because its wiring does not pass through the BODY harness.
However, it is listed for the harness levels for the harnesses DOOR-DR (Driver door), DOOR-
PASS (Passenger Door) and IP (Instrument Panel) through which its wiring does pass.
Note
After running MWS, you could generate a material statistics report to view information
related to option costing and use the report as a basis to work out which options you want to
specify as giveaway options. Giveaway options are specified to reduce the number of buildable
harness levels that are generated by Composite Wiring Synthesis (CWS).
However, this default Quick Start - Automotive Generative project data does not contain any
options that could be specified as giveaway and result in fewer harness levels. Therefore, you
will run Composite Wiring Synthesis (CWS) next to generate buildable harness levels.
A separate usage example exists for giveaway options. See “Usage Example - Giving Away an
Option on a Harness” on page 370.

February 2016
Use Composite Wiring Synthesis to Generate Buildable Harness Levels and

Wiring with Option Expressions
Composite Wiring Synthesis (CWS) generates physical harness levels for each harness in the
vehicle, builds Vehicle Configurations from them and then synthesizes wiring for the physical
harness levels and therefore the vehicle configurations. It considers only physical harness levels
and does not consider abstract harness levels.
Procedure
1. Press Space Bar and enter CWS; the Wiring Synthesis Dialog Box is displayed. Click
Generate & Finish at the top of the dialog box; the following options are selected.
o The Generate Physical Harness Levels action will generate the full set of buildable
harness levels, adhering to the vehicle model definitions and the option
relationships. These levels can be viewed through the Define Harness Levels Dialog
Box for each harness.
o The Synthesize All Wiring action will:
• re-create all the vehicle configurations.
• route all logical signals along the topological bundles of the vehicle
configurations.
• create the wires along which the signals travel and creates splices where
necessary in all of the harness levels. When doing this, the system re-uses as
much wiring as possible in each configuration.
• generate option expressions for the wires that are synthesized, even if a wire is
present in all harness levels.
• generate a module code for each wire.
o The Combine Identical Harness Levels action will:
• combine harness levels that have identical wires. Sometimes, two harness levels
that support different option combinations have identical wires. In this case, the
two harness levels are combined into one, supporting all options from the
original harness levels.
• removes any harness levels that contain no wiring.
o The Generate Vehicle Configurations - Maximum Complexity Only action will
generate max-complexity vehicle configurations. Note that this has no impact on
synthesis. This only affects the vehicle configurations that are created as an
assistance to the user (that is, to save you having to generate some manually).
Synthesis always generates its own set of configurations completely independently
of this setting.
2. Click Go; a progress bar is displayed.

February 2016
Figure 13-24. Composite Wiring Synthesis Progress Bar
3. When CWS is complete click Close.
Confirm that Physical Harness Levels Exist for the BODY Harness
CWS will have generated physical harness levels for the BODY harness.
Procedure
Right-click on the BODY harness in the Design Browser (Design tab) and select Define
Harness Levels; the Define Harness Levels - Harness:BODY dialog box is displayed.
After MWS, it looked like this:
Figure 13-25. Harness Levels after Modular Wiring Synthesis
After CWS, it looks like this:
Figure 13-26. Harness Levels after Composite Wiring Synthesis
This shows that there are now two harness levels:
• _LHD-SP1 supports the LHD-SP1 (Left Hand Drive - Special) vehicle model.
• _LHD-BS1 supports both the LHD-BS (Left Hand Drive - Basic) and RHD-BS1 (Right
Hand Drive - Basic) vehicle models even though they are mutually exclusive.

February 2016
Example Vehicle Configurations
If you click the + icon to expand the _LHD-SP1 harness level, the table looks like this:
Figure 13-27. Expanded Harness Level
Now, you can see that the _RHD-BS1 and _LHD-BS1 harness levels have been combined to
form a parent harness level called _LHD-BS1 that supports all of the options from _RHD-BS1
and _LHD-BS1. These child harness levels are not used individually, only the parent harness
level is used.
This is an unlikely scenario for a body harness but, in the case of this data, there are no
mechanical or wiring differences between the child _RHD-BS1 and _LHD-BS1 harness levels
for the BODY harness so they have been combined into one parent harness level.
Normally, you may expect some differences between Left Hand Drive and Right Hand Drive
harness levels for a body harness (for example, bundle lengths). You would not necessarily
expect differences for other harnesses.
For the next composite data example, see “Example Vehicle Configurations” on page 336.
Related Topics
Harness Level
Example Harnesses

A vehicle configuration is a set of harness levels (one per harness) that could be ordered and
fitted into a specific vehicle. Harness levels can be defined manually or generated automatically
using wiring synthesis or Capital Level Manager.
For this example, they were generated by CWS using the Example Harness Levels.
You can view the vehicle configurations in a design by pressing Space Bar and entering Vehicle
Configurations.

February 2016
Figure 13-28. Example Vehicle Configurations
Three vehicle configurations were generated, each equating to one of the vehicle models. For
example, the LHD-BS1 vehicle configuration uses the LHD-BS (Left Hand Drive - Basic)
vehicle model.
The top of the table lists all of the harnesses in the design and the column entries indicate the
harness levels that are used in the vehicle configurations. The LHD-BS1 vehicle configuration
uses the _LHD-BS1 harness level for the BODY harness.
If you hold your mouse cursor over a harness level, a tool-tip indicates the vehicle models and
options that it supports:
Figure 13-29. Vehicle Models and Options Supported by Harness Level
Related Topics
Vehicle Configuration

February 2016
Option
Option
Options and variant options can be created at project level from Capital Logic, Capital
Integrator or Capital HarnessXC.
Note
See “Variant Option” on page 341 for a definition of variant options.
An option is a code representing a feature or capability in a vehicle. Examples are ABS (Anti-
lock Braking System) or DDL (Driver Door Lock). Options are used in expressions to convey
the conditional inclusion of an object in a particular vehicle configuration. Once created for a
project, options or option expressions can be assigned to designs, devices, nets, and so on. The
options applied to designs are known as applicable options.
There are three ways in which you can define relationships between options at project level:
• Define inclusive and exclusive relationships for individual options.

• Group them within Option Folders that allow you to specify whether the options in the
folder are mutually exclusive (that is, none of the options within this folder can be
selected together in a vehicle) or mandatory (that is, at least one of the options within
this folder must be selected in a vehicle). At system or project level.
• Create Option Combinations that allow you to specify valid selections of options.
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 (CWS) procedure in Capital
Integrator.
For an example of options and their relationships in a project, see “Examples of Composite
Data” on page 321.
Creating an Option at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

Defining Inclusive and Exclusive Relationships for an Option . . . . . . . . . . . . . . . . . . . . 339
Display of Option/Module Names or Option/Module Descriptions in Dialog Boxes. . . 339
Creating an Option at Project Level

You can create options and variant options at a project level. You can specify inclusive and
exclusive relationships for the option.

February 2016
Defining Inclusive and Exclusive Relationships for an Option
Procedure
See Creating an Option at Project Level in the Capital Design Tools - Common Functions User
Guide.
Defining Inclusive and Exclusive Relationships for

an Option
You can define inclusive and exclusive relationships between options at a project level.
Procedure
See Defining Inclusive and Exclusive Relationships for an Option in the Capital Design Tools -
Display of Option/Module Names or Option/Module

Descriptions in Dialog Boxes
You can display either option/module names or option/module descriptions in dialog boxes
where they are listed (both as column titles and as selectable objects in windows).
Press Space Bar and enter ‘Show Option/Module Description’ to select either option/module
names or option/module descriptions.
When option/module descriptions are displayed, they are followed by the name in brackets.
For example:
V6 3.0L Engine [ENG_3.0] where V6 3.0L Engine is the option description and ENG_3.0 is
the option name.
When just option names are displayed, it would read ENG_3.0.
If option descriptions have been selected but no description has been given for an option, the
option name is displayed in brackets, such as [ENG_3.0].
Note
Options displayed in the diagram window and options displayed in option expressions will
be displayed as the option name regardless of the setting.

February 2016
Option Folder
Option Folder
A way to organize options into groups. Option folders can have a hierarchical structure and can
be used to define groups of related options that are exclusive (that is, none of the options within
this folder can be selected together in a vehicle) or that are mandatory (that is, at least one of the
options within this folder must be selected in a vehicle).
Examples include a group of different engines, gearboxes or audio systems.
For an example of option folders in a project, see “Examples of Composite Data” on page 321.
Creating an Option Folder at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340
Creating an Option Folder at Project Level

You can create an option folder at a project level. You can specify whether the options in the
folder are mutually exclusive or mandatory.
Procedure
See Creating an Option Folder at Project Level in the Capital Design Tools - Common

February 2016
Variant Option
Variant Option
A special classification of option that supports mechanical variations.
Variants often describe a topology variation such as Left-hand Drive or Long Wheelbase. They
sometimes describe a regional variation such as US, EU or Japan.
It is not mandatory to manage variant options - they are mostly used to separate data.
For an example of variant options in a project, see “Examples of Composite Data” on page 321.
Defining a Variant Option

You can create a variant option 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 Options.
The Options Dialog Box is displayed.
2. Select the node of the Options Browser under which you want to create the option:
• If you want to create an option at the top level of the Options Browser outside of any
other folders, select the Options node.
• If you want to create an option in a particular option folder, select that folder.
3. Click Create a new option ( ); a new option is added to the Options Browser.
4. Specify the Name and Description for the option and select the Variant option.
5. Define any Inclusive or Exclusive relationships for the option.
6. Click OK.
Related Topics
Variant Option

February 2016
Option Expression
Option Expression
Option expressions are used on logical schematics to define required variations in connectivity.
They are calculated for wiring after synthesis and define variations in wiring content.
They are a combination of option (or variant option) codes, defined using boolean operators
AND (intersection) and OR (union) together with NOT (negation).
The binary operators used are:
&& = AND
|| = OR
! = NOT (can be combined with either AND or OR
An example is LHD && ABS indicating an object required only in a left-hand drive vehicle
containing the anti-lock braking system.
Generating Option Expressions for Wires and Splices . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Generating Option Expressions for Wires and

Splices
You can generate the option expressions for wires and splices either when running Composite
Wiring Synthesis or by running the Generate Option Expressions facility after you have
synthesized wiring.
During the calculation, option expressions related to the signal for the wire (or signals for a
splice) are examined and collected. The collected options are used as a filter so that only options
found in the collected options can be used to generate an option expression for the wire.
Procedure
1. Press Space Bar and enter Generate Option Expressions.
2. A Generate Option Expressions progress bar is displayed. When the generation is
complete, click the Close button. You can view the option expression in the Edit
Properties Dialog Boxs for the individual wires. See “Assigning an Option Expression
to an Object” on page 279 for more information.
Note
The option expressions are included in the Harness report and the Connectivity
report. See “Creating a Topological Design's Harness Report” on page 420 and
“Creating a Set of Customized Connectivity Reports” on page 424 for more information
about these reports.

February 2016
Generating Option Expressions for Wires and Splices
Related Topics
Option Expression
Composite Wiring Synthesis

February 2016
Option Combination
Option Combination
While many option relationships can be represented by inclusive and exclusive options, there
are times when a group of options have a complex relationship with each other. These complex
relationships can be defined by specifying the allowable combinations of a group of options.
This, in turn, helps to limit the potentially large number of harness levels that can be generated
by Composite Wiring Synthesis.
An option combination is a collection of options that have been arranged into specific, valid
selections.
For example:
If no inclusive or exclusive relationships exist between the 6 options A, B, C, D, E, F, and they

are all optional in a particular vehicle model, then there are 64 possible combinations. In order
to lower the complexity (or for other design reasons), the 6 options can be selected in an option
combination and arranged to permit only the following combinations:
• (A, B, C, D, E, F)
• (B, F)
• (A)
• (F)
Each of the 4 combinations of the original 6 options is known as a valid selection (that is, there
are only 4 valid selections in the option combination).
The following considerations apply to option combinations and valid selections:
• An option can exist in either no option combination or just one option combination (that
is, not multiple option combinations).
• An option combination does not have to include a valid selection where all options are
selected.
• Within an option combination, the only limitation on its 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,
then an explicit, empty valid selection must be created for that option combination.
For an example of an option combination and its valid selections in a project, see “Examples of
Composite Data” on page 321.
Creating an Option Combination at Project Level. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

Adding a Valid Selection to an Option Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

February 2016
Creating an Option Combination at Project Level
Creating an Option Combination at Project Level

You can create an option combination and its valid selections.
Procedure
See Creating an Option Combination at Project Level in the Capital Design Tools - Common
Adding a Valid Selection to an Option Combination

You can add a valid selection row to the Valid Selections table for an option combination in the
Options dialog box.
Procedure
See Adding a Valid Selection to an Option Combination in the Capital Design Tools - Common

February 2016
Vehicle Model
Vehicle Model
A representation of a major vehicle variation. Each vehicle model defines an allowable
combination of all the variant options and also limits the options that are applicable to each
major vehicle variation.
Examples might be “US, LHD, 3 liter” and “UK, RHD, 1.2”.
When you define a vehicle model, you specify a set of possible combinations of variant options,
options and option combinations that could be in a vehicle. For example, electric windows and a
4-speaker or 6-speaker stereo system.
You can then set which vehicle model you want to use in a vehicle configuration. This restricts
the harness levels that can be used for each harness in the vehicle configuration. You can define
a unique set of vehicle models for each Capital Integrator design in a project. In addition, you
can export a set of vehicle models from one Capital Integrator design and import them into
another. If variant options are not defined, a single vehicle model is sufficient for a project.
The Capital definitions of STD and OPT options in a vehicle model are not always the same as
those used within OEMs and their suppliers:
• STD - an option marked as STD will always be included in the vehicle and cannot be
removed or switched for a different feature.
• OPT - an option marked as OPT may or may not be included in the vehicle. Composite
Wiring Synthesis will consider all allowable combinations of OPT options.
In particular, note that a STD option is not a feature that is included in the base model but may
be exchanged for another feature. In Capital, such a feature would be modeled as an OPT option
since it may or may not be in a vehicle.
For an example of vehicle models in a project, see “Examples of Composite Data” on page 321.
Defining Vehicle Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

Defining Vehicle Models

You can define a unique set of vehicle models for each Capital Integrator design in a project. If
variant options are not defined for a project, then a single vehicle model is sufficient.
Procedure
1. Open a diagram for the design for which you want to define vehicle models, press Space
Bar and enter Models.

February 2016
2. The Define Vehicle Models Dialog Box is displayed. It contains a table that shows the
variant options, options and valid selections that are available. Note that if an option is
included in a valid selection, it is not available individually. Click the Add button and
specify the name of the vehicle model.
Note
You can display either option names or option descriptions in dialog boxes where
options are listed (both as column titles and as selectable objects in windows). See
“Display of Option/Module Names or Option/Module Descriptions in Dialog Boxes” on
page 339.
3. Check the boxes under the variant options that you want the vehicle model to support.
Note
You can check boxes for variant options that cannot be built together (for example, a
right-hand drive variant option and a left-hand drive variant option) because you are
saying that the vehicle model could support either of these variant options.
4. For the options listed as column headers in the table, specify one of the following:
• STD
The option is always included in the vehicle model. This option is therefore
ALWAYS present. Although the electrical system design allows for versions of the
final product to be produced without the option, the product will not be offered
without the option.
For example, product marketing may decide to make 4W ABS standard. No vehicles
will be offered without 4W ABS.
• OPT
The option can be supported by the vehicle model and the final product is available
with or without the option. This increases the harness complexity required to support
the final product, because different harness levels may be required to support
vehicles with the option and those without the option.
• Blank
The option is not supported by the vehicle model. Although the option has been
captured as part of the electrical system design, the option will not be offered on the
final product. More often than not, options are not available for specific vehicles, for
example, Power Moonroof is not available on convertible vehicles.
Note
If an option is standard for a model, any inclusive options for that parent option
must also be standard for the model. Similarly, if an option is optional for a
model, any inclusive options must be either optional or standard.

February 2016
Exporting Vehicle Models from a Design
5. Check the boxes under the valid selections that you want the vehicle model to support.
Any valid selections are listed as column headers under the name of the option
combination to which they belong.
6. Click OK.
Note
If you have specified variant options that cannot be built together (for example, a
small wheelbase and long wheelbase) in the same vehicle model, the variant options
must be able to support the same options. For example, if a small wheelbase variant
option has a 4-speaker stereo option as standard but a long wheelbase variant option has
a 6-speaker stereo as standard. You would have to define one vehicle model with a small
wheelbase variant option and the 4-speaker stereo option, and a second vehicle model
with a long wheelbase variant option and a 6-speaker stereo option.
Related Topics
Importing Vehicle Models into a Design
Methods of Defining a Vehicle Configuration

You can export a set of vehicle models (as an XML file) from a Capital Integrator design. They
can be imported into another Capital Integrator design.
Procedure
1. Open the diagram for the Capital Integrator design.
2. Press Space Bar and enter Export Vehicle Models.
The Export Models dialog box is displayed.
3. Navigate to the location where you want to save the XML file and specify a file name.
4. Click Export Models.
Related Topics

February 2016

You can import a set of vehicle models (as an XML file) into a Capital Integrator design.
Procedure
1. Open the diagram for the Capital Integrator design into which you want to import a set
of vehicle models.
2. Press Space Bar and enter Import Vehicle Models.
The Import Models dialog box is displayed.
3. Navigate to the XML file containing the vehicle models and click Import Models.
4. The Import Models tab in the Output Window informs you whether the import was
successful or not and whether there were any errors.
Results
• Existing vehicle models are deleted or replaced in the design.
• Any vehicle models that match by name or UID are retained and updated with the
imported version so that any references to those models from harness levels or vehicle
configurations remain.
Related Topics

February 2016
Platform Options
Platform Options
Platform options are those options that are standard within the design. Components tagged with
these option codes will always be included on all physical harnesses but will never appear on
any option expressions and will never be available for selection on any option based user
interface. Associated Capital Logic designs may contain references to these codes. The
specified platform options will then not be included on any vehicle models, harnesses, harness
levels or option expressions within the Capital Integrator design.
Design reports, wiring designs generated by Capital AutoView Assist for Integrator, or a
synchronization of data with a Capital HarnessXC design will not reference these platform
options, though wiring is generated for them.
Options that are either obsolete or specified as variant options cannot be specified as platform.
Specifying the Platform Options in a Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350
Specifying the Platform Options in a Design

You can specify which option codes are considered to be platform options within a Capital
Integrator design.
Procedure
1. Press Space Bar and enter Models; the Define Vehicle Models Dialog Box is displayed.
2. Click the Set Standardized Options ( ) button; the Set Standardized Options Dialog
Box is displayed.
3. In the Available window, select the options that you want to specify as active and click
Add; the options are added to the Standardized window.
Results
• The selected options are treated as standard within all vehicle models in the Capital
Integrator design but with the following differences in behavior:
o These options do not appear on any expressions generated by the tool.
o The design rule checks for Inconsistent harness option and Obsolete Option will
not include these options in any output.
o These options will not be promoted to any harness or be available for selection on
any harness.
o When the system considers logical option expressions that contain these option
codes, they will always be considered ‘true’.
• Platform options cannot be modified in the Edit Options dialog box, that is, they cannot
be set as variant/obsolete or be deleted.

February 2016
Harness
• Platform options will not appear on any other dialog boxes in Capital Integrator that
display options.
• When a vehicle model is imported, any options both in the database and in the imported
data remain as platform options regardless of their state in the imported data.
• When a vehicle model is exported, all platform options are included as standard options.
• If an option has been made platform after wiring synthesis has been run, it will be
present on harness levels and wires until synthesis is run again.
• With regard to option relationships, if an option C includes an option D and C is made
platform, D does not automatically get included in the set of platform options.
Related Topics
Platform Options
Harness
Also referred to as harness family, composite harness, master harness and 150% harness. These
are supersets of actual harness products containing all optional wiring content, even
incompatible items. Examples are Instrument Panel, Driver’s Door and Engine Harness. The
harness will not be built but is used as a container for harness levels.
The harnesses in a design are listed under the Harnesses node of the Design Browser (Design
tab).
For an example of harnesses in a project, see “Examples of Composite Data” on page 321.
Related Topics
Harness Level

February 2016
Harness Level
Harness Level
Also referred to as derivative harness, this a sub-set of the content of a harness on a vehicle,
corresponding to precise combinations of options and variant options.
The relationship between a harness and its derivative levels is typically described in a table such
as the following:
Figure 13-30. Harness Levels Example
In this table, derivative harness level part numbers are listed on the left side and their option
content (and applicability to a vehicle configuration) can be deduced from the intersection with
the columns representing the options (or variant options).
The Define Harness Levels Dialog Box enables you to manually define harness levels
(derivatives) for the harnesses in a design. When you define a harness level, you specify which
vehicle model(s) and which options the harness level supports. This breaks the harness down
into a number of buildable levels.
If you have previously-defined harness levels stored in an XML file, you can import this file so
that you do not have to manually define the levels again. See “Importing Harness Level
Definitions” on page 362.
Before synthesizing wiring for signals, you set which harness level is active for each harness,
the system takes this information into account when synthesizing wiring. You can also use a
vehicle configuration to set which harness level is active for each harness.
If there are too many harness levels, you can either specify giveaway options when working
with Composite Wiring Synthesis or manually combine some harness levels in the Define
Harness Levels dialog box (see “Combining Harness Levels into One” on page 355). This
second option creates a parent-child relationship where a parent harness level (to which the
other harness level has been referred) supports all the options in the referred harness level.
When you combine harness levels that contain mutually exclusive options, the parent harness
level is marked as supporting both of these mutually exclusive options.

February 2016
Specifying the Options that Affect a Harness
If you are working with composite harnesses, you can use Composite Wiring Synthesis to
generate harness levels automatically.
If you have the necessary license, Capital Level Manager can also be used to generate harness
levels automatically. See “Capital Level Manager- Product Planner” on page 819 and “Capital
Level Manager - Harness Level Optimization” on page 925.
You can use the Edit Properties facility to add general properties to a harness level and to give
it a part number. See “Editing the Properties of a Harness Level” on page 356 for more
information.
For an example of harness levels in a project, see “Examples of Composite Data” on page 321.
Specifying the Options that Affect a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

Creating a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354
Editing a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355
Specifying a Part Number for a Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 357
Active Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 358

You can specify the options that affect a harness and that can then be supported by harness
levels for that harness.
Procedure
1. Select a harness in the Design Browser (Design tab).
2. Either:
• Right-click on the selected harness, select Define Harness Levels and click “Set the
options that affect the Harness” on the Define Harness Levels Dialog Box.
• Press Space Bar and enter Levels, and click “Set the options that affect the Harness”
on the Define Harness Levels Dialog Box.
The Set Harness Options Dialog Box is displayed.

3. Add the options that affect the harness to the Selected window.
4. Click OK.
5. The selected options are displayed in the Levels table on the Define Harness Levels
dialog box.

February 2016
Creating a Harness Level for a Harness
Related Topics
Editing a Harness Level for a Harness
Combining Harness Levels into One
Editing the Properties of a Harness Level
Specifying a Part Number for a Harness Level
Harness Level Definitions

You can create a harness level for a harness and how to specify the options that are supported by
that harness level.
Procedure
2. Either:
• Right-click on the selected harness, select Define Harness Levels.
• Press Space Bar and enter Levels.
The Define Harness Levels Dialog Box is displayed.
3. Click “Add a new Level to the harness” .
The Add Level dialog box is displayed.

4. Specify the name of the harness level and click OK.
The harness level is added to the Levels table.
5. Specify whether you want the harness “Set as Active” and select any Model and Options
supported by the harness level.
Related Topics

February 2016

You can edit an existing harness level for a harness; that is, change its name and supported
options.
Procedure
2. Either:
3. Edit the harness level in the Levels table as required:
• To edit the name, double click it and enter the new name.
• Select any model and options supported by the harness level.
Related Topics

You can combine harness levels for a harness.
Note
It is not possible to combine harness levels with different part numbers.
Procedure
2. Either:

February 2016

3. Click on the parent level in the Levels table with which you want to combine another
harness level and click “Combine two Levels into one” .
The Combine Levels for Dialog Box is displayed.

4. Add the levels that you want to combine with the parent harness level to the Selected
window and click OK.
5. The child levels are displayed below the parent level in the Levels table and a flipper
allows you to hide or show the referred harness levels.
Any vehicle models and options that are supported by the referred harness levels are
now supported by the parent harness.
Related Topics

You can edit properties for a harness level (properties like name, part number and abstract
level).
Procedure
2. Either:
3. Select the harness level in the Levels table and click “Set the properties for the selected
Level” .
The Edit Properties dialog box is displayed. See “Editing the Attributes and Properties
of Objects” on page 269 for more information about the properties that you can edit.

February 2016
Related Topics

You can specify a part number for a harness level.
Note
This part number is not used in Capital Library. If harness levels have been combined, a part
number cannot be specified for a child harness level.
Procedure
1. Select the harness level in Define Harness Levels Dialog Box and click the Set the
properties for the selected Level button; the Edit Properties Dialog Box is
displayed.
2. Enter the part number in the Part Number field and click the OK button to close the
Edit Properties dialog box.
Related Topics

February 2016
Active Harness Level

Before synthesizing wires, you must specify which harness levels you want to route for each
harness in the topological design. You do this by setting active harness levels. One or more
harness levels can be active for a harness.
You can set individual harness levels for a harness to active or you can set all harness levels in
the topological design to active. If you set all harness levels to active, you will route wires for
the worst-case scenario harness.
Instead of manually setting the active harness levels for each harness, you can define a vehicle
configuration and set that to active. See “Methods of Defining a Vehicle Configuration” on
page 364 and “Setting an Active Vehicle Configuration” on page 368.
If you set active harness levels and close a design, Capital Integrator reapplies the active levels
next time you open the design.
Setting Individual Active Harness Levels for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . 358

Setting all Harness Levels for Selected Harnesses to Active . . . . . . . . . . . . . . . . . . . . . . 359
Setting Individual Harness Levels to Inactive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
Setting all Harness Levels for Selected Harnesses to Inactive. . . . . . . . . . . . . . . . . . . . . 360
Setting Individual Active Harness Levels for a Harness

You can set individual active harness level for a harness.
Procedure
• Check the box next to the harness level in the Configuration Setting Browser
Window (Configuration tab).
• Right-click on the harness name in the Design Browser (Design tab) and select
Define Harness Levels; the Define Harness Levels Dialog Box displays a list of
harness levels for the harness. Select the Set as Active box in the row for harness
level that you want to set as active and click the OK button.
Results
• The harness level is now active.
• The details for it are displayed on the Active tab at the bottom of the Configuration
Setting Browser Window (Configuration tab).
• When you hold the mouse cursor over a harness name in the Design Browser (Design
tab), the active levels for that harness are displayed.

February 2016
Related Topics
Setting all Harness Levels for Selected Harnesses to Active
Setting Individual Harness Levels to Inactive
Setting all Harness Levels for Selected Harnesses to Inactive
Harness Level
Synthesizing Wiring
Setting all Harness Levels for Selected Harnesses to

Active
You can set all harness levels for selected harnesses to active.
Procedure
Select the harnesses in the Design Browser (Design tab), right-click and select Set All Levels
Active; all of the harness levels for the selected harnesses are set to active.
Related Topics
Harness Level
Synthesizing Wiring

You can set individual harness levels to inactive.
Procedure
1. Uncheck the box next to the harness level in the Configuration Setting Browser Window
(Configuration tab). Note that if this harness level was set as active as a result of a
vehicle configuration being set as active, the vehicle configuration is also set to inactive.

February 2016
2. Alternatively, perform the following steps:

3. Right-click on the harness name in the Design Browser (Design tab) and select Define
Harness Levels; the Define Harness Levels Dialog Box displays a list of harness levels
for the harness.
4. Uncheck the Set as Active box for the harness level that you want to set as inactive and
click the OK button.
Related Topics
Harness Level
Synthesizing Wiring
Setting all Harness Levels for Selected Harnesses to

Inactive
You can set all harness levels for selected harnesses to inactive.
Procedure
Select the harnesses in the Design Browser (Design tab), right-click and select Set All Levels
Inactive; all of the harness levels for the selected harnesses are set to inactive.
Related Topics
Harness Level
Synthesizing Wiring

February 2016

Harness levels are saved as definitions in the database. If you want to import harness level
definitions, they must be in an XML file that conforms to the document type definition
(leveldef.dtd) that is located in the dtd directory of your Capital installation.
The XML file can contain the following information:
• All options that affect the harness (regardless of their support by individual levels)
A leveldef element defines the options which affect the harness and contains the levels.
• Harness level names
Defined by a name attribute in the level element. A level element can contain child level
elements. Note that no child level element can contain another child level element.
• The partnumber attribute for a harness level
This can be contained in the level element.
• Vehicle models supported by each harness level
Defined by a vehiclemodelref that can be contained in a level element.
• Options supported by each harness level
Options can be defined as optionref elements and can be contained in the leveldef or
level elements.
The following is an example of an XML import file:
<?xml version=”1.0” encoding=”UTF-8”?>

<DOCTYPE leveldef PUBLIC “-//Mentor Graphics Corporation//Capital Level
Definition 1.0//EN" “h:/capital_home/dtd/leveldef.dtd”>
<leveldef>
<optionref name=”ENG-V6”/>
<level name=”Level-A” max=”true” partnumber=”H12345”>
<vehiclemodelref name=”Model1”/>
<level name=”Level-A-A”>
</level>
</level>
</leveldef>


February 2016
Importing Harness Level Definitions

You can import harness level definitions for a selected harness in XML format.
Procedure
2. Either:
• Right-click on the selected harness, select Define Harness Levels and click “Import
Levels from level definition file” on the Define Harness Levels Dialog Box.
• Press Space Bar and enter Levels, and click “Import Levels from level definition
file” on the Define Harness Levels Dialog Box.
The Import Levels dialog box is displayed.

3. Navigate to the XML file containing the harness level definitions.
4. Specify whether you want to Retain existing levels.
If you select this, existing levels with the same name as an imported level are
overwritten and existing levels with a different name from all of the imported levels are
retained.
If you do not select this. existing levels with the same name as an imported level are
overwritten but existing levels with a different name from all of the imported levels are
deleted.
5. Click Import.
The harness levels are displayed in the Define Harness Levels Dialog Box. Any
previously defined harness levels are retained, deleted or updated as appropriate. The
“Set as Active” setting for any matching levels will not change.
6. To apply the imported levels, click the OK button. If you do not want to apply the
imported harness levels, click the Cancel button.
If there are any errors with importing or validating the data from the XML file, a
message is displayed and the import is aborted. The following validation checks are
performed:
• The options that affect the harness must exist in the project options list.
• The vehicle models supported by each level must exist in the project.
• The vehicle model reference elements must have a name attribute.
• The options supported by each level must exist in the project.
• The option elements must have a name attribute.
• Any option supported by a level must be included in the options that affect a harness.

February 2016
Exporting Harness Level Definitions
• A level can contain a child level but a child level cannot contain another child level.
• There cannot be more than one level element with the same name attribute.
• A child level cannot have a part number.
• There cannot be two level attributes with the same name attribute in the file.
Related Topics
Harness Level

You can export harness level definitions for a selected harness in XML format.
Procedure
2. Either:
• Right-click on the selected harness and select Export Harness Levels.
• Press Space Bar and enter Export Vehicle Levels.
• Right-click on the selected harness, select Define Harness Levels and click “Export
Levels to Level definition file” on the Define Harness Levels Dialog Box.
• Press Space Bar and enter Levels, and click “Export Levels to Level definition file”
on the Define Harness Levels Dialog Box.
The Export Levels dialog box is displayed.

4. Click Export.
Related Topics
Harness Level

February 2016
A vehicle configuration is a set of harness levels (one per harness) that can be ordered and fitted
into a specific vehicle. This can be the max-complexity vehicle or a less complex derivative.
When you define a vehicle configuration, you specify the vehicle model that you want to use
and the active harness level for each harness in the vehicle configuration. Each configuration is
applicable to at least one vehicle model.
For an example of harness levels in a project, see “Examples of Composite Data” on page 321.
Methods of Defining a Vehicle Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364

Defining a Vehicle Configuration Based on Harness Levels . . . . . . . . . . . . . . . . . . . . . . 365
Defining a Vehicle Configuration Based on Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . 366

A vehicle configuration represents an entire vehicle harness (i.e. all of the harness modules in a
vehicle).
You can use various facilities to define vehicle configurations.
• Vehicle Configurations
This facility allows you to define vehicle configurations based on harness levels. You
must specify the vehicle model that you want to use and the active harness level for each
harness in that vehicle model. You then have the option of setting the vehicle
configuration as active and routing the signals just for the active harness levels in that
configuration. See “Defining a Vehicle Configuration Based on Harness Levels” on
page 365 for more information.
• Configuration Builder
This facility allows you to define vehicle configurations based on the selection of
validated options. You must specify the vehicle model that you want to use. You can
then restrict the list of harness levels that are displayed for selection by specifying which
options you want to include or exclude from the vehicle configuration. See “Defining a
Vehicle Configuration Based on Options” on page 366 for more information about this
facility.
• Composite Wiring Synthesis
As well as manually entering vehicle configurations, you can use the Composite Wiring
Synthesis facility to generate the possible maximum complexity configurations
automatically. These max-complexity vehicle configurations are added to the list of

February 2016
Defining a Vehicle Configuration Based on Harness Levels
vehicle configurations in the Define Vehicle Configurations dialog box where they are
displayed in bold.
Related Topics
Defining a Vehicle Configuration Based on Options
Setting an Active Vehicle Configuration
Defining a Vehicle Configuration Based on Harness

Levels
You can define a vehicle configuration based on harness levels.
Note
See “Methods of Defining a Vehicle Configuration” on page 364 for an overview of the
different ways that you can define vehicle configurations.
Procedure
1. Press Space Bar and enter Configurations.
2. A list of existing vehicle configuration is displayed.
Note
If you hold the mouse cursor over a cell in the Model column in the Vehicle
Configurations facility, the name of the model and information about variant
options and options for the model is displayed. If you hold the mouse cursor over a level
cell in a harness column, the name of the harness, the name of the vehicle model and the
options that apply to the combination are displayed.
3. Click the New button and enter the Configuration Name.

4. Click on the field in the Model column, hold down the mouse key and select the vehicle
model that you want this configuration to use.
5. For each of the harnesses, click on the field in the column, hold down the mouse key and
select the harness level that you want the configuration to contain.
Note
You can view the details of a vehicle configuration in the Configuration Setting
Browser Window (Configuration tab).

February 2016
Related Topics

You can define a vehicle configuration based on options.
Note
See “Methods of Defining a Vehicle Configuration” on page 364 for an overview of the
different ways that you can define vehicle configurations.
Procedure
1. Press Space Bar and enter Configuration Builder.
2. The Configuration Builder Dialog Box is displayed.
3. In the Vehicle Model section, select the vehicle model that you want to use from the
drop-down list. The options and valid selections that have been set as optional for the
vehicle model are listed at the top of the table in the Configuration Builder section of
the facility. Any options that are standard or not available for the vehicle model are not
displayed in this facility because they are either included or excluded automatically from
the vehicle model.
Note
You can display either option names or option descriptions in dialog boxes where
options are listed (both as column titles and as selectable objects in windows). See
“Display of Option/Module Names or Option/Module Descriptions in Dialog Boxes” on
page 339.
The harnesses and the levels that match the displayed options and valid selections are
displayed in the first column of the table in a tree. At the bottom of the tree, Capital
Integrator lists any existing configurations for the vehicle model.
If you check the box for an existing configuration, Capital Integrator checks the boxes
for the harness levels included in that configuration. If you then check or uncheck boxes
for harness levels, the box for the existing configuration becomes unchecked.

February 2016
The check boxes in the Options columns indicate whether a harness level supports that
option.
You can refine the list of harness levels that are displayed by changing the states of the
options listed in the Configuration Builder table. To change the state of an option, click
the check box at the top of the option column. The states are:
This is the default state for each option and means that a harness level can be
displayed whether it is supports this option or not.
This means that the option is required in the vehicle configuration and only harness
levels that support this option are displayed.
This means that the option must not be included in the vehicle configuration and any
harness levels that support this option are not displayed.
4. Check the boxes for the harness levels that you want to include in a new configuration.
Alternatively, you can check the box for an existing configuration that you want to use
as a basis for a new configuration and then check or uncheck harness levels as required.
5. In the Actions section of the facility, check the Create New Vehicle Configuration box
and specify a name for the new vehicle configuration.
Note
If you want to set the new vehicle configuration or selected harness levels as active,
check the Set Selected Levels Active box in the Actions section. When you then
click OK to exit the Configuration Builder, the new configuration will become active
automatically.
Note
You can view the details of a vehicle configuration in the Configuration Setting
Related Topics

February 2016

If you have defined a vehicle configuration, you can set it to active. If a configuration is active,
you can synthesize the wiring just for the harness levels defined in the configuration.
You can also view whether signals are Routed, Unrouted or Unconnected in the Design
Browser (Design tab) and depopulate wires that are not required in the configuration.
Procedure
You can do one of the following:
• Press Space Bar and enter Configurations, check the Set as Active box for the
configuration that you want to be active and click the OK button.
• Press Space Bar and enter Configuration Builder, check the box next to the
configuration that you want to be active and click the OK button.
• Check the box next to the vehicle configuration in the Configuration Setting
Results
In all cases, the details for the active vehicle configuration are displayed on the Active tab at the
bottom of the Configuration Setting Browser Window and the boxes for the vehicle
configuration and any harness levels used in the vehicle configuration are checked in the tree in
the Configuration Setting Browser Window.
Note
When you set a vehicle configuration to active, the signals displayed in the Design Browser
(Design tab) are Routed, Unrouted or Unconnected depending on any routing activity that
has been performed for the vehicle configuration already.
Related Topics
Synthesizing Wiring

February 2016
Giveaway
Giveaway
Giveaway wiring is wiring content that is included in a vehicle although the electrical features it
services may not be included in the electrical distribution system. This is typically done to lower
the management and logistical cost of harness manufacturing by reducing the total number of
harness levels in a harness family. Giveaways are therefore harness-specific.
The giveaway content is indicated by specifying that an option is to be a giveaway option. This
results in the wiring associated with this option being included in all compatible harness levels.
In addition, it is possible to give away an option with one or more other options. This effectively
ties the options together so that, in any harness level, they are either all supported or none of
them is supported.
Specifying Giveaway Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

Usage Example - Giving Away an Option on a Harness . . . . . . . . . . . . . . . . . . . . . . . . . 370
Usage Example - Giving Away Together Two Mutually-Exclusive Options on a Harness
375
Specifying Giveaway Options

Once you have used either Modular Wiring Synthesis or Composite Wiring Synthesis to
generate harness levels, you can specify options as giveaway options for harnesses.
After specifying the giveaway options, you can then complete the process for synthesizing
composite wiring. The number of harness levels is reduced.
Prerequisites
You must have run Modular Wiring Synthesis or Composite Wiring Synthesis to generate
harness levels.
Procedure
1. In the Design Browser (Design tab), click the harness for which you want to specify
giveaway options.
2. Either:
• Right-click the harness and select Define Harness Levels.
3. Click Give away options ( ).
Add the options that you want to specify as giveaway options to the Selected window
and click OK.

February 2016
Usage Example - Giving Away an Option on a Harness
Note
Giveaway options are displayed with a giveaway icon () in the Define Harness
Levels Dialog Box.
4. You can now go to the Wiring Synthesis Dialog Box to complete the process for
synthesizing composite wiring. See “Composite Wiring Synthesis” on page 442 for
information about the process.
Related Topics
Giveaway
Usage Example - Giving Away an Option on a

Harness
The following usage example demonstrates how to specify an option as giveaway for a harness
and view the difference that this makes to the number of harness levels.
Prerequisites for Giving Away an Option

• This example uses a Quick Start - Automotive Generative project. If you want to re-
create the steps in Capital Integrator, download the Project.zip file from here, extract
the contents and import the Quick Start - Automotive Generative.xml project.
• Open the Vehicle Topology design of the Sports Coupe design in the project.
Edit the Vehicle Models So That Giveaway Options Are Required

Giveaway options are specified to reduce the number of buildable harness levels that are
generated by Composite Wiring Synthesis (CWS). However, the default Quick Start -

February 2016
Automotive Generative project data has only a small number of harness levels defined due to
the highly constrained vehicle models.
Therefore, it is necessary to edit the default vehicle models in the project in order to use the
starter data for this example.
Procedure
1. Press Space Bar and enter Models; the Define Vehicle Models dialog box is displayed.
By default, they are defined as follows
2. Edit the values for the Fog Lamps-REAR and Fog Lamps-FRONT options so that
they are optional for the RHD-BS (Right Hand Drive - Basic) model and LHD-BS (Left
Hand Drive - Basic) vehicle models. To do this, click the table cells and select OPT
from the drop-down list.
The table should look as follows:
This indicates that the RHD-BS and LHD-BS vehicle models can be built both with and
without the Fog Lamps-REAR and Fog Lamps-FRONT options. This means that
more harness levels will be generated by Composite Wiring Synthesis (CWS) than
would have been generated otherwise.
3. Click OK.
Run CWS to Generate Harness Levels for the Harness

In a standard flow, you would typically run Modular Wiring Synthesis (MWS) to identify the
options affecting each harness. The abstract harness levels (and their wiring) are a side-effect of
this (and are often not really needed). Having run MWS, you then generate a material statistics
report to view information related to option costing and use the report as a basis to work out
which options you want to give away. Having specified the giveaway options, you would then
run MWS to generate physical harness levels.

February 2016
For this example, you will skip MWS and immediately run CWS to generate physical harness
levels. This is so that you can view the full set of levels that are generated. Note that, in a full
vehicle, you would not normally do this because CWS can generate thousands of levels per
harness.
Procedure
1. Press Space Bar and enter CWS; the Wiring Synthesis Dialog Box is displayed.
2. Select Full Synthesis.
Note
As your aim is only to generate physical harness levels, you could select just the
Update Harness Options and Generate Physical Harness Levels steps. This
would give slightly different results because some harness levels are combined when all
Full Synthesis steps are selected.
Click Go; a progress bar is displayed.
3. When CWS is complete, click Close; wiring has been synthesized for all signals and
physical harness levels have been generated for the harnesses.
View the Harness Levels for the IP Harness

You could view the harness levels for any harness but you will concentrate on the IP
(Instrument Panel) harness.
Procedure
Right-click on the IP harness in the Design Browser (Design tab) and select Define Harness
Levels; the Define Harness Levels - Harness:IP dialog box is displayed.

February 2016
It lists the seven harness levels that have been generated for the IP harness:
In particular, you are interested in the relationship between the harness levels and the Fog
Lamps-REAR and Fog Lamps-FRONT options. You can see that some of the harness levels
do not support either one or both of those options. Therefore, they could be specified as
giveaway on the IP harness in order to reduce the number of harness levels.
Specify the Fog Lamps-REAR and Fog Lamps-FRONT Options as Giveaway

for the IP Harness
This is done from the Define Harness Levels - Harness:IP dialog box.
Procedure
1. Click the Give away options ( ) button; the Give Away - Harness:IP dialog box is
displayed.
2. Select the Fog Lamps-REAR and Fog Lamps-FRONT options in the Available
window and click Add; the options are added to the Selected window.

February 2016
3. Click Recalculate; the Estimated Level Count value changes to an estimation of the
number of harness levels that would be generated by CWS for the IP harness with those
two options as giveaway.
4. Click OK; the options are saved as giveaway and the dialog box closes. Nothing
changes on the Define Harness Levels - Harness:IP dialog box at this point.
5. Click OK to exit the Define Harness Levels - Harness:IP dialog box.
Run CWS to Re-generate Harness Levels

CWS will re-generate the harness levels and will treat the Fog Lamps-REAR and Fog Lamps-
FRONT options as giveaway on the IP harness.
Procedure
1. Press Space Bar and enter CWS; the Wiring Synthesis dialog box is displayed.
2. Select Generate & Finish and click Go; a progress bar is displayed.
3. When CWS is complete, click Close; wiring has been re-synthesized for all signals and
physical harness levels have been re-generated for the harnesses.
View the Re-generated Harness Levels for the IP Harness

Procedure
(Instrument Panel) harness again.
1. Right-click on the IP harness in the Design Browser (Design tab) and select Define
Harness Levels; the Define Harness Levels - Harness:IP dialog box is displayed.
It now lists three harness levels that have been generated for the IP harness:
You can see that the Fog Lamps-REAR and Fog Lamps-FRONT options are now
present on all three harness levels.
Related Topics
Giveaway

February 2016
Usage Example - Giving Away Together Two

Mutually-Exclusive Options on a Harness
The following usage example demonstrates how to give away together two mutually-exclusive
options for a harness and view the difference that this makes to the number of harness levels.
Giveaway is intended to reduce the number of harness levels by removing some that contain a
sub-set of the wiring in another harness level. Although this results in unnecessary wiring being
included in some built vehicles, the reduction in the number of levels removes the cost of
managing these separate part numbers. Mutually-exclusive options will normally result in
mutually-exclusive wiring in separate levels that are never a sub-set and therefore not normally
given away. In some cases, however, the reduction in harness levels is desirable despite the
redundant wiring that results. For this reason, the ‘giveaway together’ functionality allows
mutually-exclusive options to be given away and their separate harness levels merged.
Prerequisites for Giving Away Mutually-Exclusive Options

• This example uses a Quick Start - Automotive Generative project. If you want to re-
create the steps in Capital Integrator, download the Project.zip file from here, extract
the contents and import the Quick Start - Automotive Generative.xml project.
• Open the Vehicle Topology design of the Sports Coupe design in the project.
Run Composite Wiring Synthesis to Promote All Options to the Appropriate

Harnesses
You will start by promoting all options to harnesses. To do this, run Composite Wiring
Synthesis (CWS).
Procedure
2. Select Full Synthesis.

February 2016
Note
As your aim is only to promote options to harnesses, you could select just the
Update Harness Options step. This would give slightly different results because
some harness levels are combined when all Full Synthesis steps are selected.

Figure 13-31. Progress Bar
3. When CWS is complete, click Close; options have been promoted to harnesses, wiring
has been synthesized for all signals and physical harness levels have been generated for
the harnesses.
Edit the Options to Make the Front and Rear Fog Lights Mutually-Exclusive
You will place the Fog Lamps-REAR and Fog Lamps-FRONT options in their own Option
Folder and mark the folder as containing mutually-exclusive options.
Procedure
View the Options in the project by pressing Space Bar and entering Options; the Options Dialog
Box is displayed. The following are the default options from the Quick Start - Automotive
Generative project.

February 2016
The top-level Options folder contains options grouped into Option Folders.
The Other folder contains options that relate to other features of the vehicle such as door locks
and fog lamps. Note that the options in this folder are not set as Mutually Exclusive and they
are not marked as Mandatory.
If Mutually Exclusive was selected, none of the options in the folder could be selected together
in a vehicle.
If Mandatory was selected, at least one of the options within this folder would have to be
included in any vehicle.

February 2016
1. Click the Create a new Folder ( ) button; a new folder is added to the Options
browser:
2. Specify a folder name of FOG and select Mutually Exclusive and Mandatory.
3. Drag the Fog Lamps-REAR and Fog Lamps-FRONT options into the FOG folder.
The Fog Lamps-REAR and Fog Lamps-FRONT options are now mutually-exclusive
and at least one of them must be included in the vehicle.
Edit the Vehicle Models So That Giveaway Options Are Required

Giveaway options are specified to reduce the number of buildable harness levels that are
generated by Composite Wiring Synthesis (CWS). However, the default Quick Start -
Automotive Generative project data has only a small number of harness levels defined due to
the highly constrained vehicle models.
Therefore, it is necessary to edit the default vehicle models in the project in order to use the
starter data for this example.
Procedure
1. Press Space Bar and enter Models; the Define Vehicle Models dialog box is displayed.
The Fog Lamps-REAR and Fog Lamps-FRONT options are currently both STD in the
LHD-SP vehicle model. They are displayed in red because they are now mutually-
exclusive and therefore cannot both be STD in a vehicle model.

February 2016
2. Edit the values for the Fog Lamps-REAR and Fog Lamps-FRONT options so that
they are both optional for all three vehicle models. To do this, click the table cells and
select OPT from the drop-down list.
The table should look as follows:
This means that the vehicle models can be built both with and without the Fog Lamps-
REAR and Fog Lamps-FRONT options. This means that more harness levels will be
generated by Composite Wiring Synthesis (CWS) than would have been generated
otherwise.
3. Click OK to exit the dialog box.
Run CWS to Generate Harness Levels for the Harness

You will use CWS to re-generate physical harness levels.
Procedure
2. Deselect all of the steps apart from Generate Physical Harness Levels step.
3. When CWS is complete, click Close; physical harness levels have been generated for
the harnesses.
View the Harness Levels for the IP Harness

(Instrument Panel) harness.

February 2016
Procedure
It lists the six harness levels that have been generated for the IP harness:
In particular, you are interested in the relationship between the harness levels and the Fog
Lamps-REAR and Fog Lamps-FRONT options. You can see that each harness level supports
only one of these options. Therefore, they could be specified as giveaway on the IP harness in
order to reduce the number of harness levels.
Specify the Fog Lamps-REAR and Fog Lamps-FRONT Options as Giveaway

for the IP Harness
This is done from the Define Harness Levels - Harness:IP dialog box. At this point, you are
specifying that the options are given away separately. You will then see that this makes no
difference to the number of harness levels.
Procedure
displayed.
2. Select the Fog Lamps-REAR and Fog Lamps-FRONT options in the Available
window and click Add; the options are added to the Selected window.

February 2016
two options as giveaway.
Giving away those two options like this has made no difference to the number of levels.
4. Click OK; the options are saved as giveaway and the dialog box closes. Nothing
changes on the Define Harness Levels - Harness:IP dialog box at this point.
5. Click OK to exit the Define Harness Levels - Harness:IP dialog box.
Run CWS to Re-generate Harness Levels

FRONT options as given away separately on the IP harness.
Procedure
2. Deselect all of the steps apart from Generate Physical Harness Levels step again and
click Go; a progress bar is displayed.
3. When CWS is complete, click Close; the physical harness levels have been re-generated
for the harnesses.

February 2016
View the Re-generated Harness Levels for the IP Harness

This demonstrates that giving away the options separately made no difference to the number of
harness levels.
Procedure
The listed harness levels are exactly the same as before. This is because none of the levels are a
sub-set of the others (with respect to fog lights):
Specify That Fog Lamps-FRONT and Fog Lamps-REAR Are Given-Away

Together for the IP Harness
This is done from the Define Harness Levels - Harness:IP dialog box again and you will see
how this does make a difference to the number of harness levels.
Procedure
displayed.

February 2016
2. Click New Group to create a new give-away group in the Selected window.
3. Move the Fog Lamps-REAR and Fog Lamps-FRONT options into the Group1 folder
by dragging them onto it; they are now listed below it.
Despite being mutually-exclusive, the two options are given away together now. This
means, any vehicle will contain the wiring for both options (even though the wiring for
one of these options will be redundant).
two options given away together.
5. Click OK; the options are saved as being given away together and the dialog box closes.
Nothing changes on the Define Harness Levels - Harness:IP dialog box at this point.
6. Click OK.

February 2016
Re-run CWS to Re-generate Harness Levels

FRONT options as given away together on the IP harness.
Procedure
2. Deselect all of the steps apart from Generate Physical Harness Levels step again and
click Go; a progress bar is displayed.
3. When CWS is complete, click Close; physical harness levels have been re-generated for
the harnesses.
View the Newly Re-generated Harness Levels for the IP Harness

You will see the difference made by giving away the options together.
Procedure
There are now three harness levels:
Note that the Fog Lamps-REAR and Fog Lamps-FRONT options are included as giveaway
on all three harness levels. This means that there is always a cost to this giveaway as the wiring
for one set of fog lights will always be redundant. However, it does reduce the number of
harness levels which might result in a reduction in the cost of managing the part numbers.
Note that the harness levels are displayed in red because they include mutually-exclusive
options. This does not prevent you working with them.
Related Topics
Giveaway

February 2016
Harness Replacement Technology

OEMs want to view and maintain an entire vehicle topology at all times. They also want to pass
on individual harnesses to suppliers who then edit those harnesses and send them back to the
OEM. The OEM then reassembles those harnesses to keep the entire vehicle up-to-date.
From Capital Integrator, you can import and export data for an individual harness using an
XML file. The file contains the topology information for the harness, all of the harness levels
and all of the wiring data for the harness. It does not contain part library data.
Usage Example - Importing Multiple Harnesses Using Harness Replacement Technology

385
Exporting a Harness from Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386
Importing a Harness into Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387
Usage Example - Importing Multiple Harnesses

Using Harness Replacement Technology
In this example, three suppliers have been managing individual harnesses. The OEM has a
single diagram that is used to connect all three together and it is currently empty.
Procedure
1. Each supplier exports the harness and sends it to the OEM.
2. The OEM imports the first harness (H1); the harness appears on the blank diagram and
the OEM can select all the graphics to position it.
3. The OEM imports the second harness (H2):
a. The harness appears on the blank diagram.
b. If the OEM drags H2 such that an inline on H2 is within one grid space of an inline
on H1, they snap together.
c. Ending the drag mates the two inline halves.
4. The OEM imports the third harness (H3) as in step 3.
5. Supplier 1 modifies H1 and re-sends it to the OEM.
6. The OEM imports the new H1 data and overwrites the existing H1 data in the design.
Results
• The old H1 is removed from the diagram.
• The new H1 is placed at the same location as the old H1. The inline connector that was
previously mated H2 is mated to an inline connector with the same name on the new H1.

February 2016
Exporting a Harness from Capital Integrator
• That inline is placed at the same location as the old inline, regardless of where it exists
on the incoming harness. The bundle that connects the inline to harness is extended as
needed.
• Any other changes needed to any of the other harnesses are not made but are reported to
the user on a Harness Import tab in the Output Window.
Related Topics
Importing a Harness into Capital Integrator

You can export the data for an individual harness as an XML file. It can then be imported into
another installation of Capital.
Procedure
1. With a Capital Integrator diagram open, select the harness in the Design Browser
• right-click on it and select Export Harness
• press Space Bar and enter Export Harness
An Export Harness dialog box is displayed
2. Specify the directory where you want to save the XML file and the name of the file.
Click Export.
Results
The XML file contains the topology information for the harness, all of the harness levels and all
of the wiring data for the harness.
The exported file contains details of the diagrams on which the diagram objects exist. When
imported, the system returns the objects to each diagram if they exist or creates the diagrams as
required
Related Topics

February 2016

You can use Capital Integrator to import the data for an individual harness from an XML file
that has been exported from Capital. When importing the harness data, you can either create a
new harness in the design or overwrite an existing harness.
Prerequisites
• You must have a set of Capital Logic designs that cover everything in the harness and
those designs must be associated with the Capital Integrator design into which you are
importing the harness.
Procedure
1. With a Capital Integrator diagram open, either:
• press Space Bar and enter Import Harness
• right-click on the harness to be overwritten in the Design Browser (Design tab) and
select Import Harness
An Import Harness dialog box is displayed
2. Browse to the XML file, select it and click Import.
Results
• If you selected a harness to overwrite, the new harness data is imported and overwrites
it.
• If you did not select a harness to overwrite, the new harness is imported and is added to
the Design Browser (Design tab) and is placed in free space in the diagram window.
Note that if it has the same name as an existing harness in the design, a message is
displayed on a Harness Import tab in the Output Window at the bottom of the
application.
• If you have overwritten a harness, the Harness Import tab in the Output Window also
reports on any changes that are required to any other harnesses as a result of the import
and displays any warnings where differing data has caused issues.
• If you are importing a harness that was created across multiple diagrams, the system
returns the objects to each diagram if they exist or creates the diagrams as required.
• Although the data file does not include actual library parts, it does include object
attributes such as Part Number so the import automatically re-associates any available
library parts.
• Slots on the imported harness that also exist on other harnesses are merged.
• Constraints on the imported harness and its child objects are retained.

February 2016
• Rules that are on the imported harness and its children and are present (matched by UID
and then name) on the harness to be overwritten are retained on the harness after the
import.
• Rules that are on the harness in the XML file but are not in the database are removed and
do not appear on the harness after the import.
• References to custom constraints are included in the transfer but the constraints
themselves are not.
• Harness levels on the imported harness are retained.
• Vehicle models are not included in the transfer.
• If an option (matched by UID and then name) does not exist on the target project. In this
case, the import removes the option from any harness levels that reference it.
• A combined wire can be mapped to an inline cavity. During export, all inlines convert to
interface connectors. When an interface connector imports onto a target diagram, the
signal carried by that wire is a combined signal. When an importing harness contains a
combined signal that is not present on the diagram, the import combines the appropriate
matching child signals on the design to create a new combined signal if the user has the
diagram locked.
• If an imported slot contains a device that is currently placed in a different slot on the
target design, the device is unplaced from the slot on the target design and the wiring is
deleted. The exception to this is when the device is variantly placed in both slots and the
variants are different, in which case the device is left alone.
• If a slot in the XML file already exists on the diagram but exists on multiple harnesses,
the incoming slot merges with the target slot following these rules:
o All slot connectors on the incoming harness are added to the existing slot.
o If the devices in a slot are not mapped to the connectors that are being imported, then
they are left alone.
o Properties of the incoming slot are merged into the existing slot. If there is a
collision between properties, the incoming slot is the master.
o Rules on the incoming slot are added to the existing slot - collisions are not resolved.
• Connectors are imported following the same rules as described for slots.
Related Topics

February 2016
Chapter 14
Module Code Management
This chapter contains details of how to manage functional module codes in Capital Integrator.
Module Code Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389
Viewing the Modules in a Capital Integrator Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390
Setting Wiring in Particular Modules to Active in the Design . . . . . . . . . . . . . . . . . . . . 391
Renaming a Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392
Merging Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393
Creating a New Module Based on an Option Expression . . . . . . . . . . . . . . . . . . . . . . . . 395
Moving Wiring Between Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397
Sharing Wires Between Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 398
Module Code Management Overview

You create and manage functional module codes at project level (for use across the design
tools).
This is done using the Project Functional Module Codes Dialog Box.
In Capital Integrator, wiring synthesis generates wires in modules whose names are initially
based on the option expressions on those wires. These names may be different from the
functional module codes. In this case, the names are referred to as module strings in this guide.
The Configuration Setting Browser Window (Configuration tab) enables you to manage the
modules, whether it be renaming, sharing or merging them.
If one of these module strings has the same name as a functional module code, the system
automatically associates them. The association also occurs if you edit a module string to have
the same name as a functional module code. Any module strings that are not associated with a
functional module code will be indicated with a warning icon ( ).
Note
If you rename an associated functional module code at project-level, the change is reflected
in Capital Integrator.
The Harness Synchronization process will pass the module codes, assigned to wires, from
Capital Integrator to Capital ModularXC, allowing them to be used in the Capital Modular XC
Modular Processing. See the Applicable Functional Module Codes Dialog section in the Capital
ModularXC guide for full details.

February 2016
Viewing the Modules in a Capital Integrator Design
Transfer of Capital Integrator Design Data and Module Codes

Module code references are included if you transfer Capital Integrator design data by:
• Copying a design between projects.

• Using design export/import.
• Using harness export/import.
• Using wiring export/import.
When doing this, the system matches transferred module codes by name with existing codes in
the target project.
Related Topics
Setting Wiring in Particular Modules to Active in the Design
Renaming a Module
Merging Modules
Creating a New Module Based on an Option Expression
Moving Wiring Between Modules
Sharing Wires Between Modules
Synthesizing Wiring
Viewing the Modules in a Capital Integrator

Design
You can view the modules that have been created by wiring synthesis. You can also see the
wires within each of these modules.
Prerequisites
• Wiring must have been synthesized in the design. See “Synthesizing Wiring” on
page 440.
• The design must be open in the Diagram Window.
Procedure
1. Click the Configuration Setting Browser Window (Configuration tab) on the left of the
application window and select Module from the drop-down Mode list; the browser
window on the tab lists the harnesses in the design.

February 2016
2. Select the harness(es) for which you want to view modules and click the Manage
module codes for selected harnesses ( ) button; the browser tree expands below each
selected harness to display the modules that have been created for the wires in them. It
also displays the wires in those modules. See the Browser Window (Module) section of
“Configuration Setting Browser Window (Configuration Tab)” on page 632 for full
details of its contents but note that any module strings that are not associated with a
functional module code will be indicated with a warning icon ( ).
Related Topics
Renaming a Module
Merging Modules
Setting Wiring in Particular Modules to Active

in the Design
You can set wiring in particular modules to active in the design.
You can then filter the display of graphical objects in the Diagram Window to only those
objects with active wiring. See “Filtering the Objects Displayed in a Diagram” on page 89.
Procedure
2. Select the harness(es) for which you want to edit modules and click the Manage module
codes for selected harnesses ( ) button; the browser tree expands below each selected
harness to display the modules that have been created for the wires in them. It also
displays the wires in those modules. See the Browser Window (Module) section of
details of its contents.
3. Set the required modules to active. Either:
• Without a harness selected, click the “Set all modules in place active” ( ) button;
the system sets all wiring for all modules in the design to active. All modules and
wires are displayed in bold in the browser window.

February 2016
Renaming a Module
• Select the harnesses for which you want to make the modules active, and click the
“Set all modules in selected harnesses active” ( ) button; the system sets the
modules for those harnesses to active. The modules and wires for them are displayed
in bold in the browser window.
• Select the box next to each module for which you want to make the wiring active;
the system sets all wiring for the selected modules to active. The modules and wires
listed below them are displayed in bold in the browser window.
Related Topics
Renaming a Module
Merging Modules
Renaming a Module
You can rename a module.
Note
Functional module codes can be created and managed at project level (for use across the
design tools). This is done using the Project Functional Module Codes Dialog Box. When
you rename a module, you can select one of the project functional module codes. When you do
this, an association is created between them.
Procedure

February 2016
Merging Modules
3. Either:
• Right-click on the module to be renamed and select Rename Module or select it and
press F2 on your keyboard; the module is displayed as an editable field.
• Slowly double-click the module.
4. Either:
• Manually type the new name in the editable field and click outside of it.
• Click the ellipsis (...) at the end of the field to display the Select Module Code
Dialog Box where you can select from a list of functional module codes.
Results
• The new name is displayed in the browser window.
• If you selected a functional module code, an association is created between that and the
module. If it had a warning icon, indicating that it was an unassociated module string,
the icon changes.
Related Topics
Merging Modules
Merging Modules
You can merge two modules to make one.
Procedure

February 2016
Merging Modules
3. Either:
• In the browser window, select one of the modules to be merged. Drag and drop it on
top of the other module.
• In the browser window, right-click on one of the modules to be merged and select
Merge Module > [Other module].
Results
• The option expression sub-folders and their wires from the first module are moved under
the second module. This indicates that all the wires with any of the option expressions
are contained within the same module.
• The second module is not renamed.
Examples
You can see two modules A-CDC (containing wires with option expression A-CDC) and A-RJ
(based on option expression A-RJ).
Figure 14-1. Modules Before a Merge Example

February 2016
If module A-CDC is dragged and dropped on to A-RJ, you get the following:
Figure 14-2. Modules After a Merge Example
You now have one module called A-RJ. Wires with an option expression of A-CDC or an
option expression of A-RJ will all be contained within this same module.
Related Topics
Renaming a Module
Creating a New Module Based on an Option

Expression
You can create a new module based on an option expression that is currently listed under a
different module. This action splits the wiring with that option expression into a separate
module.
Procedure

February 2016
3. Right-click on the option expression and select create new module.
Results
• The option expression sub-folder and its wires are moved under a new module named
after the option expression.
• If a module already exists with that name, a suffix is added to the new module.
Examples
You can see one module A-RJ. There are wires with the option expression A-CDC and A-RJ
that are in that module.
Figure 14-3. Create a Module Example: Before
If you right-click on the A-CDC option expression and select Create New Module, you get the
following:
Figure 14-4. Create a Module Example: After

February 2016
You now have two modules A-CDC and A-RJ, each of which contain wires with matching
option expressions.
Related Topics
Renaming a Module
Merging Modules

You can move wires with a particular option expression from one module to another.
Procedure
displays the wires with those modules. See the Browser Window (Module) section of
3. Either:
• In the browser window, select the option expression sub-folder containing the wiring
that you want to move. Drag and drop it on top of the module to which you want to
move it.
• In the browser window, right-click on the option expression sub-folder to be moved
and select Move Wiring > [Target module] or ...
Note
If you select ..., the Select a Module Dialog Box is displayed where you can
select the module into which the wiring is moved.

February 2016
Results
• The option expression sub-folder and its wires are moved under the target module. This
indicates that those wires are now in that module but still have their original option
expressions.
• If you moved the only option expression sub-folder from under a module (so that it now
has no wiring), that module is removed from the browser window.
Related Topics
Renaming a Module
Merging Modules

You can share wires with a particular option expression between modules. Wires which are
shared between two modules will be contained within both modules when processed in Capital
HarnessXC. Therefore, the modules should normally be marked as exclusive.
Procedure
3. Either:
• In the browser window, select the option expression sub-folder containing the wiring
that you want to share. Hold down the CRTL key on your keyboard, drag the sub-
folder and drop it on top of the module with which you want to share it.
• In the browser window, right-click on the option expression sub-folder to be shared
and select Share Wiring > [Other module] or ...

February 2016
Note
If you select ..., the Select a Module Dialog Box dialog box is displayed where
you can select the module with which to share the wiring.
Results
• The option expression sub-folder and its wires remain under the original module but are
also added under the other module. This indicates that those wires will now be included
in both modules.
• The option expression on the wires does not change.
• If you hold your mouse cursor over one of the wires in the browser window, a tool-tip
displays details for it. The Module Code(s) item lists both module codes separated by /.
Related Topics
Renaming a Module
Merging Modules

February 2016

February 2016
Chapter 15
Terminal Bars, Holes and Relays
This chapter contains details of how to implement terminal bars and holes.
Hole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 401
Terminal Bar Design Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 403
Adding a Hole to a Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Moving a Hole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409
Importing Terminal Bar Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410
Deleting Terminal Bar Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411
Relays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Relay Design Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Hole
A hole allows signals to be routed to the inside of a slot without passing through an actual
connector. A hole is never created as a harness connector but still acts as the interface for the
harness-side connection of bundles and for routing.
A hole does not have cavities. A signal/wire passes through the hole in the boundary of a slot in
order to connect to something inside (for example, a splice or device). Any wire that is
connected through a hole is a poke-home.
Only one harness can connect to a hole.
You use a hole if you want to route wires that do not terminate on a connector but poke home on
an electrical pin of the equipment that is represented by a slot's physical device (such as a
terminal bar).
Holes can be used to add relays or terminal bars to designs. See “Relays” on page 413 for
information about adding relays to designs. Continue reading this topic, if you want to add
terminal bars to designs.
Terminal Bar
Terminal bars are a modular interconnection system. They are used for harness-to-harness
interfaces as well as to implement equipotentials. The phrase 'terminal bar' indicates a complete
assembly that includes:
• conductive bar (a mounting rail or DIN rail)

February 2016
Hole
• several terminal blocks mounted on the bar

• terminal block connectors (also known as plug-in terminals) mated to some of the
terminal blocks
If you are using a terminal bar design flow using Capital Integrator, wiring in the Integrator
design connects directly to a slot representing a terminal bar using holes, without any harness-
side or device-side connectors.
Terminal Bar Model Concept

The terminal bar model consists of specialized pin lists and conductors. The central concept is a
terminal block (a specialized device). Terminal blocks have mated terminal block connectors.
They may also have internal shorts between pins, called pin groups. There are also two
specialized types of conductors, the bar (or DIN rail) and jumpers.
For example:
Figure 15-1. Terminal Bar in Design
Note
This is a schematic representation only. You do not need to draw a diagram like this to use
the terminal bar design flow in Capital Integrator.
This example terminal bar shows 2 terminal blocks, each with a terminal block connector that
connects to 3 of its 6 pins. One pin of each terminal block is specifically for connecting to the
bar (DIN rail). Each terminal block also has 2 pin groups, each of which internally connects 3 of
its pins.
The following terminal block pins are connected together:
• TBLK1: PIN1, PIN2, RAILPIN; TBLK2: PIN1, PIN2, RAILPIN.

These pins are shorted together by the Bar ‘DIN RAIL’, and implement a Splice for
WIRE2 and WIRE4.

February 2016
Terminal Bar Design Flow
• TBLK1: PIN3, PIN4, PIN5; TBLK2: PIN3, PIN4, PIN5.

These pins are shorted together by the Jumper ‘JUMP1’, and implement a Splice for
WIRE1 and WIRE3.
Terminal bar data is not displayed directly in the Design Browser (Design tab) or on a diagram.
In Capital Project, you can use the following functionality for holes and terminal bars:
• Default Object Names

• Advanced Naming
• Object Type Information
Related Topics
Adding a Hole to a Slot
Moving a Hole
Importing Terminal Bar Definitions
Deleting Terminal Bar Definitions

Terminal bars can be implemented in Capital.
1. Create logical diagrams in Capital Logic. You do not create terminal blocks or terminal
bars at this stage.
2. Create the topology in Capital Integrator. When doing this, define slots as junction
boxes to represent terminal bars. See “Overview of Junction Box Slots” on page 100.
3. Add holes to the junction box slots. See “Adding a Hole to a Slot” on page 409.
4. Connect bundles to the holes.
Bundles/harnesses that terminate at holes do not have a harness-side connector.
Unlike slot connectors:
o Holes cannot have bundle fanouts so the Refine Connector functionality is not
available on a hole.
o Holes cannot be marked Integral to Harness.
Any wires connecting to slots through holes are considered to terminate internally on the
splice or device placed in that slot.

February 2016
You can route signals through a junction box slot. This creates internal splices between
two hole connections. These internal splices can be visualized as follows:
Figure 15-2. Internal Splices
Multiple connections to the same placed functional device pin are also represented as an
internal splice.
5. Place functional devices in the slots with holes. This applies to diodes or other devices in
junction box slots to be manufactured with the terminal bar. See “Placement of a Device
or Ground Device in a Slot” on page 174.
6. Synthesize wiring to create splices in the junction boxes. See “Composite Wiring
Synthesis” on page 442.
o Wires can be routed to and terminated on holes. Any wire terminating at a hole is a
poke home.
o Hole connections are never multi-termed (there is no connector pin or cavity on
which to terminate). Instead, wires on the same signal are internally-spliced so that
routes are completed.
o Internal splices are displayed in the Design Browser (Design tab) when they are
connected to wires routed via a hole.
o It is possible for an internal splice to connect signals between two different holes but
it is not possible for internal splices to connect signals between holes and slot
connector cavities.
o In order to force splice creation inside the junction box slot, you would apply rules to
other slots, harnesses or the design that prohibit splices and multi-terms.
o Signal Map
• You can use the Signal Map dialog box to alter signal mapping to holes in
junction box slots. The behavior of the Signal Map dialog box is slightly
different when a slot has holes.

February 2016
• A hole contains 'hole connections' but you do not see or manipulate these
directly. You determine only the hole for each signal. You do not select which
cavity is connected to a given signal.
• However, you could add additional holes (without a cavity) or slot connectors
(with a cavity) to the slot as mappings for a given signal.
• Internal splices are shown explicitly in the Signal Map dialog box when the
wires in the splice are connected via a hole.
7. Use Generate Slot Circuit functionality to output a graphical representation of the slot.
You could either print this, export the design or use Capital Enterprise Reporter to
generate a custom report.
Slot Circuits
The Generate Slot Circuit functionality can be used with holes. See “Slot Circuit” on
page 258 for more information about slot circuits.
When a signal is mapped to a hole connection, then a wire (with a name based on the
external wire at that connection) is used to represent the connectivity from the
appropriate internal splice or placed device.
When signals are mapped to more than one hole connection (that is, an internal splice),
the corresponding wires are spliced together using standard Capital Logic parameterized
splices (that is, 1-pin splices with no symbol). In the case of holes, it is not possible to
generate a wire that passes through the slot without being connected to a splice. There is
no limit on the number of wires connected to an internal splice.
Wires are also displayed connected to parameterized devices that represent the logical
devices, such as diodes, that are placed in the slot.
Example of Generating a Slot Circuit:
You have a slot in Capital Integrator.

February 2016
Figure 15-3. Slot in Capital Integrator
If you used a connector instead of the hole, generating a slot circuit would create a
connector with net conductors indicating the internal short:
Figure 15-4. Connector with Net Conductors
With the hole, the wires are shown spliced together without a connector because the
wires connect directly to the internal splice.
Figure 15-5. Hole with Wires Spliced

February 2016
8. You use your own process (outside of Capital) to create definitions of terminal bars and
terminal blocks which can be input back into Capital Integrator. These definitions must
be in XML format and be structured as in the following example.
In this example, the terminal bar definition represents a single terminal bar with two
terminal blocks.
The first block TB1 has three pins, including the connection for the bar conductor, and
one for mating to a terminal block connector. All three pins are shorted internally, so
TB1 is essentially a splice.
The second block TB2 has one pin only. The jumper connects one pin from each
terminal block.
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE connectivity “-//Mentor Graphics Corporation//Terminal Bar 1.0//EN"
"H:/capital_home/dtd/project.dtd">
<connectivity id="_52" modified="32" baseid="_52">
<terminalbar id="_41" name="My Terminal Bar" nameindex="-1">
<terminalblock id="_47" name="TB1" nameindex="-1">
<pin id="_53" name="BusBar" nameindex="-1" />
<pin id="_54" name="PIN1" nameindex="-1" wirename="WIRE1" />
<pin id="_55" name="ConnPin1" nameindex="-1" wirename="WIRE2" />
<pingroup id="_61">
<connection pinref="_53" />
</pingroup>
</terminalblock>
<terminalblock id="_49" name="TB2" nameindex="-1">
<pin id="_56" name="PIN1" nameindex="1" wirename="WIRE3" />
</terminalblock>
<terminalblockconnector id="_57" name="TBC1" nameindex="-1">
<pin id="_58" name="PIN1" nameindex="-1" connectedpin="_55" />
</terminalblockconnector>

February 2016
<bar id="_59" name="BusBar" nameindex="-1">

</bar>
<jumper id="_60" name="JUMP1" nameindex="-1">
</jumper>
</terminalbar>
</connectivity>
9. Import the external definition of terminal bars and terminal blocks. The system stores
this information with the junction box slot for future reporting and consistency
checking. See “Importing Terminal Bar Definitions” on page 410 for more information.
10. Run the Inconsistent terminal bar design rule check that reports any inconsistencies in
the internal connectivity between the previously imported terminal bar definition and the
slot itself (that is, the placed devices and the signal map). See “Running Design Rule
Checks Manually” on page 73 for more information about running design rule checks.
The Inconsistent terminal bar check validates that wires connected together by slot-
internal splices created by wiring synthesis correspond to the wires connected together
by terminal bar data. Terminal bar data includes terminal block internal connectivity,
jumpers between terminal bar pins and the conductive bar itself.
This verifies that changes to the signal map, changes to placement data or changes to
wiring in Capital Integrator have not invalidated the terminal bar definition and that the
terminal bar definition itself corresponds to the slot's model of internal connectivity.
This design rule check also verifies that the connectivity of components embedded in the
terminal blocks corresponds to the slot-internal connectivity of the corresponding
functional devices placed in the slot.
11. The terminal bar data is now persisted and is passed on to other Capital applications that
use the data from Capital Integrator.
Note
Capital AutoView Assist for Integrator does not support holes and terminal bars.
Capital Enterprise Reporter can be used to report on terminal bars.
Related Topics
Hole

February 2016
Moving a Hole

You can add a hole to a slot.
A hole allows signals to be routed to the inside of a slot without passing through an actual
connector. A hole is never created as a harness connector but still acts as the interface for the
harness-side connection of bundles and for routing. See “Terminal Bars, Holes and Relays” on
page 401 for more information about holes.
Holes can be added to any type of slot but they must be added to a junction box slot if you are
working with the Terminal Bar Design Flow.
Procedure
1. Right-click on the slot and select the Add Hole option from the pop-up menu.
Alternatively, click on the slot, press Space Bar and enter Hole.
2. The hole is added to the slot and is listed below the slot in the Design Browser (Design
tab).
Related Topics
Hole
Moving a Hole
Moving a Hole
You can move a hole within a slot.
Procedure
1. Right-click on the hole and select Move Hole.
2. Move the mouse cursor to the location where you want to place the hole and click the
left mouse button. When you hold the cursor over a valid location, it looks like this .
When you hold the cursor over an invalid location, it looks like this .
3. The hole moves to the new location.

February 2016
Related Topics
Hole

If you are using a terminal bar design flow using Capital Integrator, you can import definitions
for terminal bars and terminal blocks that have been created outside of Capital. These
definitions represent the internal structure of terminal bars.
See “Terminal Bars, Holes and Relays” on page 401 for more information about terminal bars,
holes and the terminal bar design flow.
You import definitions for specific junction box slots and the system stores this information
with the junction box slot for future reporting and consistency checking. You can import
terminal bar definitions only for junction box slots with at least one hole.
The terminal bar definition is applied to the junction box slot and is matched using wire names
against the existing hole connections. The system then stores the terminal bar definition with the
slot and the corresponding hole connections.
A definition can contain more than one terminal bar so you can associate only one terminal bar
definition file with a slot. All of the terminal bars in a definition file are applied to the slot.
If there is no wire connected to a hole connection (physical electrical device pin), a terminal
block pin cannot be associated to that hole connection. If some of the wires named in the
terminal bar definition are not found in the Integrator design data connected via holes to the slot,
then the import of the terminal bar definition fails with an error message.
Note
Wires do not have to be active during the import because the system takes into account all
composite data when matching wire references in the terminal bar definition to wires in the
design.
After the import, the relationship between terminal bar pins and the hole connections can be
changed only by deleting the terminal bar definition or by importing another definition. See
“Deleting Terminal Bar Definitions” on page 411 for more information.
The terminal bar definition may contain functional devices, such as diodes, embedded within
terminal blocks. These devices must correspond to devices that are placed in the slot.

February 2016
The import process also verifies whether the internal connectivity of the slot corresponds to the
connectivity of the terminal bar definition. Any inconsistency is reported but does not stop the
import.
Procedure
1. Right-click on the junction box slot and select Import Terminal Bar Definition.
Alternatively, click on the slot, press Space Bar and enter Import Terminal Bar
Definition; the Import Terminal Bar Definition dialog box is displayed.
2. Browse to the terminal bar definition file (XML file) and click the Import button; any
messages are displayed on the Import tab in the Capital Integrator Output Window.
Results
When a slot has an imported terminal bar definition associated, some of the reports and user
interface in Capital Integrator use names from the technical bar definition (terminal bar,
terminal block, terminal block connector and terminal block pin/connector pin) rather than the
usual Capital Integrator names (for example, physical electrical device pins).
Reports referencing terminal bar definitions are:
• Connectivity Report
• Harness Report
Not only is the terminal bar and block reported but also any terminal bar connector and specific
pin. You cannot configure the reports to display only the terminal bar and block.
User interface elements that reference names from terminal bar definitions are:
• Generate Slot Circuit dialog box
• Tool tips for wires
• Design rule check results
Related Topics

The relationship between terminal bar pins and the hole connections, defined during the import
of terminal bar definitions, cannot be changed after the import, other than by deleting the
terminal bar definition or by importing another definition.

February 2016
Procedure
Right-click on the junction box slot and select the Delete Terminal Bar Definition option from
the pop-up menu. Alternatively, click on the slot, press Space Bar and enter Delete Terminal
Bar Definition.
Related Topics

February 2016
Relays
Relays
Devices typically use connectors to connect to their wiring. However, some devices do not and
have wires connected directly to them instead (that is, relays). Capital Integrator enables you to
do this by adding holes to slots.
See “Terminal Bars, Holes and Relays” on page 401 for more information about holes.
You can predefine groupings of device pins that are mapped automatically to separate holes
when the device is placed in a slot.
Relay Design Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 413
Relay Design Flow

Device pins are assigned group codes in this flow. Each group code indicates that the pin
belongs to a set of pins that typically have their wires grouped together in the final wiring. Often
each group of wires is on a separate harness.
For example:
A relay could be defined in Capital Library as follows:
Two pin groups are defined:
• Pins 3, 1 and C2
• Pins 4, 2 and C1
Wires for each of these groups are grouped together as they connect to the relay - one group
from either side of the mounting rail.
The flow is as follows:
1. Define a device in Capital Library. Use the Pin Group column on the Pin Attribute tab
to assign grouping codes to pins. See Devices in the Capital Library User Guide for
more information about defining devices.

February 2016
Relay Design Flow
As an alternative to creating a library part with pin groupings, you can set the Pin
Group attribute for device pins directly in the Attributes section of the General tab of
the Edit Properties dialog box for pins in Capital Logic. If you choose this method, you
skip step 2 in this flow.
If you assign a library part to a device in Capital Logic, the Pin Group attribute is set for
the device pins according to the library definition.
If a library device has both a footprint and a Pin Group attribute, the attribute is
ignored.
2. Assign the part number to one or more devices in Capital Logic. See “Assigning a
Library Part to an Object” on page 274 for more information about how to do this.
3. Associate the Capital Logic design with a Capital Integrator design (see “Associating
Logical Designs with the Topological Design” on page 37) and place the devices in slots
(either manually or automatically, see “Placement of a Device or Ground Device in a
Slot” on page 174).
Multiple relay devices could be placed in one slot that represents a rail which has several
relays mounted on it.
4. If holes with the pin group names do not already exist on the slot, the system
automatically adds new holes (with the pin group names) to the slot according to the
number of pin groups defined for the device or devices in Capital Library and maps the
device pins to the holes.
You can move the holes around the slot to an appropriate position and you can connect
them to bundles. See “Moving a Hole” on page 409 for more information.
Related Topics
Relays

February 2016
Chapter 16
Stud Pins and Ring Terminals
You can specify stud pins on device library parts in Capital Library and on devices in Capital
Logic. When a device with a stud pin is placed in a slot in Capital Integrator, you can see it in
the signal map.
Overview of Stud Pins and Ring Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416
Mapping a Stud Pin to Multiple Ring Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

February 2016
Overview of Stud Pins and Ring Terminals

You can specify stud pins on device library parts in Capital Library and on devices in Capital
Logic. When a device with a stud pin is placed in a slot in Capital Integrator, the system:
• Maps the device pins to cavities.
• Maps the stud pin to a ring terminal if the slot has one. If the slot does not have a ring
terminal, the system creates one (with no part number) connecting to the stud pin.
• Lists the ring terminal ( ) under the Connectors for the slot in the Design Browser
(Design tab).
• Displays the ring terminal in the slot’s signal map, both in the Connector Mating table at
the top of the dialog box and on the Signal Mappings tab, where it displays the mapping
between the ring terminal and the stud pin.
Note
If the device has no footprint, you can manipulate all pin mappings in the signal
map. If the device has a footprint, you can manipulate only stud pin mappings. You
can map stud pins only to ring terminals.
If the device has a library part number, the housing definition for the device dictates the
allowable part numbers for the ring terminals.
If required, you can add additional ring terminals to a slot by adding connectors and converting
them to ring terminals.
You can also map a stud pin to multiple ring terminals. If there are multiple signals connected to
the stud pin and you want to route each signal to a separate ring terminal, you can either:
• Set up Route by Attribute/Property constraints on the bundles connecting to the ring

terminals prior to running wiring synthesis. See “Overview of Rules and Constraints” on
page 287 for information about working with constraints.
• Edit the signal map for the slot after synthesis. That is, copy the stud pin row and map
the new row to an additional ring terminal.
When you synchronize Capital Integrator design data with a Capital HarnessXC design, the ring
terminals are included.

Mapping a Stud Pin to Multiple Ring Terminals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

February 2016
Adding Ring Terminals to a Slot

The system adds ring terminals to slots automatically when placing devices with stud pins. You
can add further ring terminals to a slot manually. To do this, you add a connector and convert it
to a ring terminal.
Procedure
1. Add a connector to the slot by right-clicking on it, selecting Add slot connector and
clicking on the appropriate location on the slot; the system creates a slot with no
cavities.
2. Convert the connector to a ring terminal by right-clicking it and selecting Convert to
Ring Terminal. Alternatively, click the connector, press Space Bar and enter Convert to
Ring Terminal.
Note
You can convert only connectors with no cavities or just one cavity to ring terminals.
Results
• The connector becomes a ring terminal.
• The ring terminal is listed with the Connectors for the slot in the Design Browser
(Design tab).
• You can edit the name attribute for the ring terminal.
• You can convert the ring terminal back to a connector by right-clicking it and selecting
Convert to Connector.
Related Topics
Mapping a Stud Pin to Multiple Ring Terminals

To do this, you duplicate a stud pin row in the signal map for a slot and map the connectors
accordingly.
Prerequisites
• You must have placed the device with the stud pin in the slot.
• If the system did not create all required ring terminals when you placed the device, you
must have created the other ring terminals manually.

February 2016
Procedure
1. Right-click on the slot and select Signal Map; the Signal Map Dialog Box for Slot is
displayed. The Signal Mappings tab displays any mappings of ring terminals to stud
pins.
2. On the Signal Mappings tab, select a mapping for the stud pin and click the Duplicate
Cavity ( ) button; a second, identical mapping is added to the table.
3. In the Connector column of the new row, select the additional ring terminal that you
want to map to the stud pin.
Results
The stud pin is mapped to both ring terminals.
Related Topics

February 2016
Chapter 17
Reports
This chapter contains details of the reports that you can create in Capital Integrator:
Harness Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Creating a Topological Design's Harness Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Options and Levels Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Creating an Options and Levels Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Customized Connectivity Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423
Creating a Set of Customized Connectivity Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424
Material Statistics Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 426
Creating a Material Statistics Report for a Topological Design . . . . . . . . . . . . . . . . . . . . . 426
Wire Count Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Creating a Wire Count Report for a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Bundle Width Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429
Creating a Bundle Width Report for a Bundle Section . . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Component BOM Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Creating a Component BOM Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Multicore List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Creating a Multicore List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Applied Constraints Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Creating an Applied Constraints Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Configured Wire List Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435
Using the Report Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436

February 2016
Reports
Harness Report
Harness Report
Enables the creation of a summary report window detailing all of the design objects (and their
measurements) that are located on the currently selected topological design.
The report is displayed in the Capital Integrator Output Window when the Report tab is
selected. The report can be used for on-screen reference, or its contents may be copied for
pasting into other applications, for example, MS Excel.
To view the hierarchical relationships between the objects on a design, the report's design object
items are hyper-linked to the Design tab's browser tree, clicking an item on the report highlights
the same item on the diagram.
Creating a Topological Design's Harness Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420
Creating a Topological Design's Harness Report

You can create a harness report.
The report is displayed in the Capital Integrator Output Window if the Report tab is selected.
The report can be used for on-screen reference, or its contents may be copied for pasting into
other applications, for example, MS Excel.
Procedure
1. Press Space Bar and enter Platform to create the report window.
2. Right click over the report in the Capital Integrator Output Window and click the Select
All option.
3. Right click again over the report and click the Copy option to copy the entire content of
the report to the Windows Clipboard.
You may now paste the report content into the appropriate application.
Note
You may also copy only the required sections of the report by highlighting the
appropriate section with your mouse and clicking the Copy option before pasting
into the other application.
Related Topics
Harness Report

February 2016
Reports
Options and Levels Report

Enables the creation of a report detailing the options and levels for the topological design.
This report contains the following information:
• A list of variant options and their inclusive/exclusive options

• A list of options and their inclusive/exclusive options
• A list of option combinations, their valid selections and the options in the valid
selections
• A list of platform options
• A list of vehicle models, their standard options and optional options
• A list of harnesses detailing their levels and the model and options for the levels. If
harness levels have been combined, the child harness levels are indented from the parent
harness level in the tables.
• A list of vehicle configurations detailing the model and harness levels used
The report is displayed in the Capital Integrator Output Window when the Level tab is selected.
If a cell in the report is red, this indicates that there is an issue with the setting. Possible issues
are:
• The option is active on the harness level, but is unavailable on any vehicle models
supported by the level.
• The option is inactive on the harness level, but is standard on a vehicle model supported
by the level.
• The option is inactive on the harness level, but is included by another option that is
active on the level.
Creating an Options and Levels Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 421
Creating an Options and Levels Report

You can create an options and levels report.
The report is displayed in the Capital Integrator Output Window when the Level tab is selected.

February 2016
Reports
Creating an Options and Levels Report
Procedure
1. Press Space Bar and enter Platform to create the report.
2. Right click over the report in the Capital Integrator Output Window and click the Select
All option.
3. Right click again over the report and click the Copy option to copy the entire content of
the report to the Windows Clipboard.
You may now paste the report content into the appropriate application.
Note
You may also copy only the required sections of the report by highlighting the
appropriate section with your mouse and clicking the Copy option before pasting
into the other application.
Related Topics

February 2016
Reports
Customized Connectivity Reports

Enables the simultaneous creation of customizable topological diagram reports at a chosen
location. The reports list connectivity objects of a specific type with specific fields, attributes
and properties for them.
The reports created automatically by this facility are:
• Bundle.csv
• Bundle Region.csv
• Cavity.csv
• Harness.csv
• InlineConnector.csv
• InterfaceConnector.csv
• Level.csv
• Signal.csv
• Slot.csv
• Splice.csv
• VirtualConnector.csv
• Wire.csv
When generating the reports, you can select to generate a subset of these.
The reports use the comma separated variable (CSV) format enabling them to be opened into
applications such as MS Excel. HTML and Output Window formats are not available in this
version of the software.

February 2016
Reports
Creating a Set of Customized Connectivity Reports
Figure 17-1. Connectivity Report
When you create the reports, you specify the fields, attributes and properties displayed as
columns for the objects in each report.
You can save a set of columns for a subset of reports as a scheme. A report scheme is a single
file that you can select in a Scheme field in the Connectivity dialog box used to create the
reports. The other fields in the dialog box pick up their settings from the scheme file. This
enables you to quickly create a set of reports containing the same columns as used previously.
Creating a Set of Customized Connectivity Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

You can create a set of customized connectivity reports.
Procedure
1. With a Capital Integrator diagram open, press Space Bar and enter Platform; the
Connectivity Dialog Box is displayed and the Format field defaults to CSV.
Note
The HTML and Output Window formats are not available in this version of the
software.
2. Specify the Location where you want the reports to be created.

February 2016
Reports
Note
If you have previously generated a set of reports, saved the selections of columns as
a scheme, and want to use those same selections again, select the scheme in the
Scheme field; the other fields in the dialog box update with the selections automatically.
Skip to step 5.
3. In the Inclusion window, specify the list of connectivity object types for which you want
to generate reports. To do this, click Edit and specify the list in the Select Inclusion
Dialog Box.
4. For each connectivity object type, specify the columns that you want included in the
report:
a. Select the connectivity object type in the Inclusion window; the Output window lists
the columns that are currently included in the report.
b. Click Edit and specify the columns in the Select Output for Dialog Box.
c. Specify the order in which you want the columns to be displayed in the report. The
report will display the columns in the order that they are displayed in this list. You
can select a column in this list and click the Move Up or Move Down button to
change the order.
Note
Select the “Use Single Attributes/Properties Column” option if you want the
selected object type's attributes/properties to be displayed in only one column of
the report, rather than separated into individual columns. This moves any attribute
and property fields from the Output window to the Attributes/Properties window
(that can be included in or removed from the report just like the other columns). In
the Output window, they are replaced with one column Attributes/Properties. The
Attributes/Properties window allows you to edit the attributes and properties that are
displayed in the single column.
d. Repeat steps a to c for each connectivity object type for which you are generating a
report.
Note
If you want to save your report and column selections as a scheme, specify a
scheme name in the Scheme field and click Save As; the scheme is saved for
future use.
5. Click “Write Report Files”; the CSV report files are created at the specified location.
Related Topics

February 2016
Reports
Material Statistics Report

Enables you to create a report about the materials that are used in the topological design. The
materials that are included in the report are connectors, inlines, splices and wires. You can
display the totals for the design, the totals for the harnesses, the totals for each harness level of
each harness and the totals for the options.
If you have assigned properties to the nets in Capital Logic or to the wires in Capital Integrator,
you can breakdown the statistics for number of wires and wire length by wire property value.
You can save the report in comma separated variable (CSV) format. The enables the report to be
opened into applications such as MS Excel.
Creating a Material Statistics Report for a Topological Design . . . . . . . . . . . . . . . . . . . 426
Creating a Material Statistics Report for a

Topological Design
You can create a material statistics report for a topological design.
Procedure
1. Select Reports - Material Statistics from the menu; the Report Material Statistics
2. In the Report Detail section, select how the report is structured.
3. If required, use the “By Wire Attribute/Property drop-down list” to add columns to the
table for a particular wire attribute or property. See the Usage Notes in the Report
Material Statistics Dialog Box topic for an example of this.
4. Click the Generate button to generate the report table.
Note
To save the report as a .CSV file, click the “Save Report File” button; a save dialog
box is displayed. Specify the file name and the directory where you want to save the
file and click the OK button. By default, the reports are saved into the install location
folder.
Related Topics

February 2016
Reports
Wire Count Report
Wire Count Report

You can create an HTML report about the wires connected to a connector (inline, virtual or
interface). The report provides details about the number of wires that are connected to the
connector in the various harness levels and options.
The information contained in the report is as follows:
• For each harness level:

o The total number of wires active in the connector
o The number of these wires that are standard (that is, that are always present
regardless of optional content)
o The number of these wires that are optioned (that is, that may vary dependent on the
options in a particular vehicle)
• For each option that has some impact on the connector contents:
o Which harness level supports this option
o The number of wires at the connector which are required to support this option (this
is normally only an approximate figure showing the relative sizes of each option)
The system calculates the number of wires supporting each option column. This can be quite
complex if the wire option expressions are complex. The system therefore determines whether
the individual wires are present if only a particular option is in the vehicle. This can result in the
following calculations:
• If a wire has an OR option expression (for example, A or B), 'double accounting' will
occur because the wire will be added to both the A option and the B option.
• If a wire has an AND expression (for example, A AND B), the wire will not be added to
any option. In effect, it will be treated more like a standard wire.
• If a wire has a NOT expression (for example, NOT A), the wire will again be added to
multiple option columns.
Note that wires with no option expression (that is, are standard) are not included in the count for
each option.
Option expressions must exist on wires before you can generate a wire count report.
Creating a Wire Count Report for a Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 427
Creating a Wire Count Report for a Connector

You can create a wire count report for a connector.

February 2016
Reports
Creating a Wire Count Report for a Connector
Prerequisites
• Option Expressions must exist on wires before you can generate a wire count report.
Procedure
1. Select the connector in the Diagram Window or Design Browser (Design tab), press
Space Bar and enter Platform.
2. The Wire Count Report dialog box is displayed. Select the directory where you want to
save the report and specify the file name.
If you want to view the report immediately, check the Open in Browser box. If you do
not want to view the report immediately, uncheck the box.
3. Click the Save button.
4. If you have checked the Open in Browser box, the report is displayed.
Related Topics
Wire Count Report

February 2016
Reports
Bundle Width Report
Bundle Width Report

If the WireCSA attribute has been set on wires within Capital Integrator, you can create a
bundle width report to view the number of wires in a bundle section and the estimated diameter
of that bundle section.
The following project preferences are used when calculating a bundle diameter for this report:
• Wire Gap Coefficient

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.
Note
A multicore is treated as one wire by these calculations.
Bundle diameter (DBundle) is calculated in the following ways (given a number of

wires of diameter DWire):
o If the bundle contains one wire:
DBundle = DWire
o If the bundle contains two wires:
DBundle =
o 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):
o 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 content of the
multicore is ignored.
o 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.
o 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

February 2016
Reports
Creating a Bundle Width Report for a Bundle Section
copper diameter and an insulation thickness determined from Capital Library (from
the Wire Insulation Thickness table is added to calculate DWire.
Note
In all these cases, this value of DWire is used to calculate the overall CSA of
copper plus insulation.
• Default Insulation Thickness

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.
Note
For details of how to specify project preferences, see “Project Preferences” on
page 60.
Creating a Bundle Width Report for a Bundle Section . . . . . . . . . . . . . . . . . . . . . . . . . . 430
Creating a Bundle Width Report for a Bundle

Section
You can create a bundle width report for a bundle section.
Note
There are two project preferences for Wire Gap Coefficient and Default Insulation
Thickness that are used when calculating a bundle diameter. See “Project Preferences” on
page 60.
Procedure
1. Press Space Bar and enter Platform.
2. The mouse cursor changes to a wire symbol. Click on the bundle section for which you
want to create the report.
3. A Bundle tab is displayed in the Capital Integrator Output Window. The Bundle tab
displays the name of the bundle, the estimated total diameter of the bundle section, the
names of the wires and their widths.

February 2016
Reports
Creating a Bundle Width Report for a Bundle Section
Note
To copy the report, right-click on the report in the Capital Integrator Output Window
and click the Select All option. Then, right-click again over the report and click the
Copy option to copy the entire content of the report to the Windows Clipboard. You can
now paste the report content into the appropriate application. You can also copy only the
required sections of the report by highlighting the appropriate section with your mouse
and clicking the Copy option before pasting into the other application. To clear the
bundle width report, right-click on the Integrator Output Window with the Bundle tab
displayed and select the Clear option from the pop-up menu.
Related Topics
Bundle Width Report

February 2016
Reports
Component BOM Report

This report lists all library components used on the topological design, along with the number of
each component used.
For each component, the following information is displayed:
• Part Number
The part number of the library component.
• Quantity
The number of times the library part is used on the selected design(s).
Creating a Component BOM Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432
Creating a Component BOM Report

You can generate a component BOM report for a topology design.
Procedure
Press Space Bar and enter Component BOM. The report opens in a new window, listing all
library components used on the design, along with the number of each component used.
Note
You can save the report as an HTML file or print it.
Related Topics

February 2016
Reports
Multicore List Report

A multicore list report lists all multicores on the design.
For each multicore, the following information is displayed:
• Name
The unique identifier for the multicore within the design.
• Design
The design upon which the multicore appears.
• Part Number
The part number of any library part associated with the multicore.
• Multicore Contents
A listing of the wires and child multicores assigned to the multicore.
• Multicore Parent
If a multicore is nested as a child of another multicore, the parent “containing” multicore
is listed here.
• Overbraid?
Specifies whether the multicore has been applied to the diagram as an overbraid (Y) or
as a traditional multicore (N).
Creating a Multicore List Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433
Creating a Multicore List Report

You can create a multicore list report for the topology design.
Procedure
Press Space Bar and enter Multicore List. The report opens in a new window,
Note
You can save the report as an HTML file or print it.
Related Topics

February 2016
Reports
Applied Constraints Report

You can generate (create) an HTML or csv report about the constraints that have been set on
objects in the currently open design.
Note
The report lists only those objects that have a constraint applied directly to them. For
example, a connector with a constraint will be listed but its pins will not, even though they
inherit constraints added to the connector.
The report is generated with the following columns:
• Harness
Specifies the name of the harness to which the object belongs if appropriate.
• Object Name
Specifies the name of the object.
• Object Type
Specifies the type of object.
• Constraint Type
Specifies whether the constraint is standard (STANDARD) or customized (CUSTOM).
• Constraint
The constraint that has been applied to the object. If multiple constraints have been
applied to an object, the object is listed multiple times. If a constraint was applied via a
rule (that is, the rule was referenced rather than adding a constraint directly, then the
entry in this column starts with the rule name and a colon.
Creating an Applied Constraints Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434
Creating an Applied Constraints Report

You can generate (create) an applied constraints report.
Procedure
1. Press Space Bar and enter Platform; the Applied Constraints Report dialog box is
displayed.
2. Specify the directory where you want to save the report and the name of the HTML or
csv file.

February 2016
Reports
Configured Wire List Report
Note
Select Open in Browser or Spreadsheet if you want the report to open
automatically when it is generated.
3. Click Save; the report is generated.

Related Topics
Configured Wire List Report

The Configured Wire List report is defined by editing an XML configuration file located in the
reporter\templates\embedded sub-directory of your Capital installation directory. This allows
you to determine which entries appear on your wire list report.
Either a single report may be generated, or a combination of reports for Capital HarnessXC,
Capital Logic and Capital Integrator. For each wire any, or all, of the following information
may be displayed:
• Type
The type of report being generated. For Capital Integrator this is specified as
“Integrator”.
• Attribute
This element displays the attribute value in the column title, for example “Name” -
listing the name attributes of the wire.
• Property
The property element displays the property value in the column title. for example
“Signal” - listing the signal properties of the wire.
• Wireendexpressions
This element contains all expressions listed below, that are applicable in a wire reports,
as well as the start and end fields of the wire.
• Component
The name of the component at which end 1 of the wire is terminated.
• Connector
The connector at which end 1 of the wire is terminated.
• Pin

February 2016
Reports
Using the Report Builder
The name of the Pin1 connector cavity at which end 1 of the wire is terminated. The pin
element can have an additional attribute set; “mated” which means any mated pin option
details applicable will be listed in the report.
• Component
The name of the component at which end 2 of the wire is terminated.
• Connector
The connector at which end 2 of the wire is terminated.
• Pin
The name of the Pin2 connector cavity at which end 2 of the wire is terminated. The pin
element can have an additional attribute set; “mated” which means any mated pin option
details applicable will be listed in the report.
Using the Report Builder

Capital provides a dynamic report generator enabling you to quickly and easily specify, create
and modify customized reports. The Report Builder interface is intuitive and user-friendly,
offering control via icons and drag and drop functionality enabling the simple creation and
management of reports.
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
Enterprise Reporter.
For further information see Using the Report Builder in the Capital Design Tools - Common

February 2016
Chapter 18
Wiring
This chapter contains details of how to synthesize (generate) wiring and edit wires.
Synthesizing Wiring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
How Synthesis Calculates the Cost of a Wiring Route for a Signal. . . . . . . . . . . . . . . . . . 441
Composite Wiring Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Composite Wiring Synthesis Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Synthesizing Composite Wiring in the Level Import Flow . . . . . . . . . . . . . . . . . . . . . . . . 447
Regenerating Harness Levels and Finishing Composite Wiring Synthesis . . . . . . . . . . . . 447
Generating Initial Harness Levels for Composite Wiring Synthesis . . . . . . . . . . . . . . . . . 448
Viewing the Wiring for a Vehicle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Deleting Wiring, Harness Levels and Vehicle Configurations. . . . . . . . . . . . . . . . . . . . . . 449
Modular Wiring Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 450
452
Viewing the Synthesized Wires for a Harness Level after Modular Wiring Synthesis . . . 453
Viewing the Synthesized Wires for all Harnesses after Modular Wiring Synthesis . . . . . 454
Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Reporting on Missing or Inconsistent Options Promoted to Harnesses . . . . . . . . . . . . . . . 455
Manual Wiring Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Deleting the Synthesized Wiring for all Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Deleting the Synthesized Wiring for Selected Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
Detailed Descriptions of Wiring Synthesis Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
Running Modular or Composite Wiring Synthesis for Selected Signals . . . . . . . . . . . . 467
Merge of Logical Multicores in Wiring Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 468
Import of Carry-Over Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 470
High-level Flow for Importing Carry-Over Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Importing Carry-Over Wiring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Merging a Slot and Interface Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Wire Editing in Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Generating a Wiring View of a Synthesized Signal or Multicore . . . . . . . . . . . . . . . . . . . 476
Adding a Wire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Moving a Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479

February 2016
Wiring
Editing Wire Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479

Defining Specification Attributes for a Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Specifying the Harness Levels on which a Wire Exists . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Combined Signals and Combined Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Setting a Constraint to Combine Wires at a Cavity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Creating a New Combined Signal from Selected Signals . . . . . . . . . . . . . . . . . . . . . . . . . 488
Adding Selected Signals to an Existing Combined Signal . . . . . . . . . . . . . . . . . . . . . . . . . 488
Combining Selected Signals with a Compatible Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Removing Selected Child Signals from a Combined Signal . . . . . . . . . . . . . . . . . . . . . . . 490
Uncombining All Child Signals from a Combined Signal . . . . . . . . . . . . . . . . . . . . . . . . . 491
Creating a New Combined Wire from Selected Wires. . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Creating a New Combined Wire from a Selected Set of Wires for a Combined Signal . . 492
Adding Selected Wires to an Existing Combined Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Combining Selected Wires with a Compatible Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Uncombining Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Assigning Wire / Splice / Multicore Properties by Rules . . . . . . . . . . . . . . . . . . . . . . . . . 495
Splice Editing in Capital Integrator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Creating a Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Moving a Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Merging Two Splices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Decomposing a Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Converting a Multiple Termination to a Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 500
Automatically Converting Butt Splices to Center Strip Splices . . . . . . . . . . . . . . . . . . . 501
Converting a Butt Splice to a Center Strip Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Converting a Center Strip Splice to a Butt Splice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502
Creating a Multicore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 503
Updating Wire Lengths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504
Modifying a Shield Termination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Copying Wiring Across the Levels of a Harness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505
Depopulating Wiring from Active Harness Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Editing Ground Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507
Exporting Wiring from a Capital Integrator Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Importing Wiring into a Capital Integrator Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509
Editing the Module Code for a Wire, Shield or Multicore . . . . . . . . . . . . . . . . . . . . . . . 510
Routed States of Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512
Calculating the Routed State of Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Preserving Wiring during Topology Edits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515
Editing the Topology in Preserve Wiring Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 516

February 2016
Wiring
Troubleshooting Wiring Synthesis Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517

Top-Level Debugging Process for Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

February 2016
Wiring
Synthesizing Wiring
Synthesizing Wiring
You can generate wire information after a topology has been defined, Capital Logic designs
have been associated with the Capital Integrator design, and devices have been placed into slots.
The following methods are available for generating the wires for each harness in the design:
• An automated Composite Wiring Synthesis process, used if you are working with
composite harnesses. It automates the steps necessary to synthesize wiring for all of the
harness levels for each harness in the vehicle and thereby synthesize wiring for each
possible vehicle configuration. It considers only physical harness levels and does not
consider abstract harness levels. It assigns wiring to physical levels. See “Composite
• An automated Modular Wiring Synthesis process, used to generate wiring with option
expressions, but without physical harness levels. This wiring can be used to determine
(calculate) option complexity and option costing information, as a basis to decide which
options will be specified as giveaway when running composite wiring synthesis.
Alternatively, it can be used when working with a modular harness flow that requires the
synthesis of wiring to implement all combinations of features in the vehicle, but without
the definition of harness levels. Modular Wiring Synthesis generates this wiring by
considering buildable configurations of exclusive options. See “Modular Wiring
Synthesis” on page 450.
• A manual wiring synthesis process, used only if you are working with a design that has
no complexity (that is, only a single harness level, which normally means there are no
options). This process can be used to synthesize wiring for selected signals or all signals
in the design at once). See “Manual Wiring Synthesis” on page 456.
For an example of basis synthesis, consider a simple signal between four devices.
Figure 18-1. Signal between Four Devices
• First, a connection is made between two device pins.

• Each additional device pin is then connected into the existing wiring using a splice or a
multi-term.

February 2016
Wiring
How Synthesis Calculates the Cost of a Wiring Route for a Signal
• Lowest cost implementation is used in each case (see “How Synthesis Calculates the
Cost of a Wiring Route for a Signal” on page 441).
How Synthesis Calculates the Cost of a Wiring Route for a Signal . . . . . . . . . . . . . . . . 441
How Synthesis Calculates the Cost of a Wiring

Route for a Signal
When the system synthesizes signals, it looks for the cheapest (generally the shortest) route.
The cost of a route is calculated by summing the following:
• Cost of each wire

Calculated by multiplying the wire length by cost per unit length. By default, the cost
per unit length is 1 but this can be changed by applying the “Cost of wire per unit
length” constraint to the design, a harness or a bundle.
• Cost of each splice
By default, the cost of a splice is 0 but this can be changed by applying the “Cost of
splice” constraint to the design, a harness or a bundle.
• Cost of each multi-term
By default, the cost of a a multi-term is 0 but this can be changed by applying the “Cost
of multiterm” constraint to a cavity, a connector, a slot or a design.
• Cost of traversing an inline pair
By default, the cost of traversing an inline pair is 0 but this can be changed by applying
the “Cost per wire for Inline/Junction Box” constraint to an inline half, a harness or a
design.
• Cost of traversing a junction box
By default, the cost of traversing a junction box is 0 but this can be changed by applying
the “Cost per wire for Inline/Junction Box” to a junction box itself, a harness or a design.
The cost values are not monetary values. They are simply units to indicate that something is less
or more desirable than something else. For example, if the cost of a splice is 1 and the cost of a
multi-term is 3, the splice is a third of the cost of the multi-term.
Note that only the cost of each wire has a default value higher than 0. Therefore, unless the other
constraints are applied, the system will assume that the shortest wiring solution is best
regardless of the number of splices, and so on. When the other constrains are applied, a longer
route may be cheapest because it has fewer splices, and so on.
Also, note that constraints can vary across a design so a wire or splice in one area may cost more
or less than a wire or splice elsewhere.

February 2016
Wiring
Related Topics
Synthesizing Wiring

Composite Wiring Synthesis (CWS) is an optional, add-on product for Capital Integrator. It is
only available if you have the necessary license. It is of most value in projects containing
complex topologies with significant option content as it enables you to generate harness levels
and wiring information automatically as part of the Capital generative flow.
It automates the steps necessary to synthesize wiring for all of the harness levels for each
harness in the vehicle and thereby synthesize wiring for each possible vehicle configuration. It
considers physical harness levels and assigns wiring to physical levels.
Figure 18-2. Composite Wiring Synthesis Overview
CWS and Harness Level Generation

For each harness in the electrical system, options that drive complexity for that harness are
identified and associated with the harness. Harness Levels are defined to support various
combinations of options for a harness. The following is a simple explanation using a car as the
example for simplicity:
Every car has an ‘Instrument Panel Harness’ that sends signals to the various options available
(for example, CD player, radio, steering column, air conditioning, and so on). Each harness
level has a different combination of these options: one model may have the CD player another
only the radio option while both may have air conditioning.

February 2016
Wiring
Obviously, several harness may connect to the various options; for example, the air
conditioning option could be associated with the ‘Engine Harness’ as it supplies the necessary
power.
The more options and option combinations that exist, the more complex the generation of
harness levels will be, therefore you may want to use CWS to automate the generation of
harness levels (taking into account option definitions and wire routing requirements).
It is not compulsory to use CWS to generate harness levels. You can define them manually or
import pre-defined harness levels if desired. If this is done, then only the ‘wiring synthesis’ and
‘combine identical harness’ steps are necessary when you run CWS.
The ‘wiring synthesis’ step requires that Harness Levels exist in order that the wires can be
generated for each harness within those levels. At a basic level, if no options exist, then just one
harness level exists for each harness.
When options are introduced, you can generate or define several harness levels depending on
the required combination of options.
In the example below, no options exist, therefore only one harness level is generated.
Figure 18-3. Define Harness Levels Dialog Box with One Level

February 2016
Wiring
In the next example, two options have been created, therefore you must define or generate a
harness level to reflect each possible combination of these two options:
Figure 18-4. Define Harness Levels Dialog Box with Multiple Levels
See “Harness Level” on page 352 for more information about defining/generating harness
levels and associated options.
CWS and Wiring Generation

Once harness levels have been created, and options assigned, CWS can define and route the
wires for the individual harness levels. When doing this, the system routes the logical signals
and generates the required wires, splices and multi-terms. It determines the impact of optional
devices and connections on the complexity of the harness system. Options and their
relationships as well as additional combinational constraints described in the vehicle model(s)
are used to derive the content of the max complexity harness for each of the harnesses defined in
the topology. Wiring is then synthesized for each max complexity vehicle configuration.
Depopulated harnesses are then defined by removing options and associated wiring from the
max complexity harnesses and synthesizing any new wiring required.
The resultant output from CWS is a fully defined set of harness levels and associated wiring
which will support all possible buildable system combinations. See “Examples of Composite
Data” on page 321.
If you have added Wire Part Specification constraints and Terminal Type Specification
constraints to objects, these will be used to add properties to the wires that are created. When
creating splices, the system takes into account any constraints or rules that have been set.
See “Wire Routing Constraints Strategy” on page 296 and“Wire Synthesis Constraints
Strategy” on page 296 for details of other constraints that are taken into account by wiring
synthesis.

February 2016
Wiring
To summarize, CWS has the following prerequisites:
• at least one vehicle model has been defined. See “Defining Vehicle Models” on
page 346.
• options and option relationships have been defined in Capital Project or Capital
Integrator (inclusive/exclusive relationships and variants). See “Option” on page 338 for
more information.
• all optional devices and connections have been option tagged in the functional Capital
Logic diagrams and placed in slots in Capital Integrator. See “Assigning an Option
Expression to an Object” on page 279 and “Placement of a Device or Ground Device in
a Slot” on page 174 for more information.
• the system topology has been defined including harness boundaries (inlines) and
equipment positions (slots).
• allowable combinations of options have been defined in the vehicle model(s). See
“Defining Vehicle Models” on page 346.
• constraints have been added to topology objects as required. See “Creating a Strategy
for Constraint Definition in Capital Integrator” on page 294.
Once these prerequisites have been met, you can use the Wiring Synthesis Dialog Box to select
particular synthesis steps that you want the system to perform or select all of the steps at once.
All steps can be run more than once and synthesis is incremental. There is no need to delete
existing wiring after design changes are made and before running synthesis steps because the
steps add new wiring as required and remove existing wiring that is not longer required. The
individual steps for composite wiring synthesis are listed if you click Custom Settings.
If you click one of the buttons at the top of the dialog box, particular steps are selected
automatically. These options allow you to break the process for composite wiring synthesis so
that you can specify giveaway options and thereby reduce the number of harness levels that are
generated in the overall process.
Reporting on CWS Results

After the wiring has been synthesized, you can generate basic reports from the Reports menu.
Reports can be created for bundle contents, multicore wire lists and a component bill of
material. More detailed reports can be generated for options, harness levels and connectivity
information. See “Reports” on page 419 for more information.
The topological layout can be edited after wiring has been synthesized and the signals can be re-
routed.
Related Topics
Composite Wiring Synthesis Flows
Synthesizing Composite Wiring in the Level Import Flow

February 2016
Wiring

There are three flows for using wiring synthesis.
• Level Import Flow
Where you manage option relationships in a separate system and import them into
Capital before running wiring synthesis.
a. Import the harness level definitions into Capital. See “Importing Harness Level
Definitions” on page 362.
b. Run the Composite Wiring Synthesis steps necessary to complete wiring synthesis.
See “Synthesizing Composite Wiring in the Level Import Flow” on page 447.
• Modular and Composite Wiring Synthesis Flow (Preferred Flow)
Where you ensure that the options relationships are defined in vehicle models, run
modular wiring synthesis, specify giveaway options and generate buildable harness
levels before completing wiring synthesis.
a. Run Modular Wiring Synthesis to generate wiring with option expressions. See
“Modular Wiring Synthesis” on page 450.
b. Create a material statistics report to view information related to option costing. See
“Creating a Material Statistics Report for a Topological Design” on page 426.
c. Use the report as a basis to specify which options are giveaway options. See
“Specifying Giveaway Options” on page 369.
d. Run the Composite Wiring Synthesis steps necessary to regenerate buildable harness
levels taking into account giveaway options. See “Regenerating Harness Levels and
Finishing Composite Wiring Synthesis” on page 447.
• Full Composite Wiring Synthesis Flow
Where you ensure that the options relationships are defined in vehicle models, run
composite wiring synthesis to generate harness levels and specify giveaway options.
You then repeat these steps until you are satisfied with the predicted number of
buildable harness levels. You generate those levels before completing wiring synthesis.
a. Run Composite Wiring Synthesis to generate an initial set of harness levels. See
“Generating Initial Harness Levels for Composite Wiring Synthesis” on page 448.
b. Specify which options are giveaway options. See “Specifying Giveaway Options”
on page 369.
Note
You can repeat steps a and b until you satisfied with the predicted number of
buildable harness levels.

February 2016
Wiring
c. Run the Composite Wiring Synthesis steps necessary to regenerate buildable harness
levels taking into account giveaway options. See “Regenerating Harness Levels and
Finishing Composite Wiring Synthesis” on page 447.
Synthesizing Composite Wiring in the Level Import Flow . . . . . . . . . . . . . . . . . . . . . . . 447
Regenerating Harness Levels and Finishing Composite Wiring Synthesis . . . . . . . . . . 447
Generating Initial Harness Levels for Composite Wiring Synthesis . . . . . . . . . . . . . . . 448
Viewing the Wiring for a Vehicle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Deleting Wiring, Harness Levels and Vehicle Configurations . . . . . . . . . . . . . . . . . . . . 449
Synthesizing Composite Wiring in the Level Import

Flow
This topic explains how to complete Composite Wiring Synthesis after importing harness level
definitions in the level import flow.
Procedure
1. Press Space Bar and enter CWS.
The Wiring Synthesis Dialog Box is displayed.
2. Click Finish Synthesis and Go.
A progress bar indicates when the synthesis is complete.
3. When complete, click Close.
The Synthesis and Signal Details tabs in the Output Window report on the synthesis
actions and any signals that have failed to route.
Related Topics
Viewing the Wiring for a Vehicle Configuration
Deleting Wiring, Harness Levels and Vehicle Configurations
Running Modular or Composite Wiring Synthesis for Selected Signals
Regenerating Harness Levels and Finishing

You can use Composite Wiring Synthesis to regenerate harness levels (after specifying
giveaway options) and to complete wiring synthesis.

February 2016
Wiring
Generating Initial Harness Levels for Composite Wiring Synthesis
Procedure
2. Click Generate & Finish and Go.
The Synthesis and Signal Details tabs in the Output Window report on the synthesis
actions and any signals that have failed to route.
Related Topics
Generating Initial Harness Levels for Composite

Wiring Synthesis
You can use Composite Wiring Synthesis to generate initial harness levels from which you can
decide which options you want to specify as giveaway options.
Procedure
2. Click Update Harness Options and Go.
The Synthesis tab in the Output Window report on the synthesis actions.
Related Topics

February 2016
Wiring


This topic explains how to view the wiring that has been generated for a vehicle configuration in
the design browser (Design tab).
Procedure
1. Set the vehicle configuration to active. See “Setting an Active Vehicle Configuration”
on page 368 for more information.
2. Expand the Signals folder in the Design Browser (Design tab). Any wires and splices
that have been created are listed in the sub-folders. See Design Browser (Design tab) for
more information on the contents of each folder.
Related Topics
Deleting Wiring, Harness Levels and Vehicle

Configurations
If you have synthesized wiring and generated harness levels and vehicle configurations, you can
delete all of this data and start again.
Procedure
1. Press Space Bar and enter Reset Composite Wiring.
2. A message asks you whether you want to proceed. Click the OK button to proceed.
Related Topics

February 2016
Wiring
Modular Wiring Synthesis

A modular harness flow requires the synthesis of wiring to implement all possible combinations
of features in the vehicle but without the definition of harness levels. It considers only abstract
wiring and does not consider physical harness levels. Modular Wiring Synthesis (MWS)
generates this wiring by routing wiring based on manufacturable configurations of exclusive
options. Composite Wiring Synthesis (CWS) can be then be used to assign this wiring to
physical harness levels.
In contrast to Composite Wiring Synthesis, Modular Wiring Synthesis does not consider all
combinations of options. However, it does take into account mutually exclusive content, both in
the case of:
• options defined as mutually exclusive

• inverted option expressions (for example, A and !A)
For example:
If LHD and RHD are NOT defined as exclusive, MWS could synthesize the following
unnecessary wire:
Figure 18-5. Unnecessary Wire
In comparison, if LHD and RHD are correctly defined as exclusive, MWS does not synthesize
that wire:
Figure 18-6. No Unnecessary Wire

February 2016
Wiring
Synthesizing Modular Wiring
When you run Modular Wiring Synthesis, it performs the following steps:
1. Creates or re-uses a level on each harness for each vehicle model.

2. Creates or re-uses wiring for each vehicle model based on the patterns of options
permitted for the vehicle model.
3. Allocates option expressions and module codes to the synthesized wiring.
4. Promotes options affecting a harness to the harness.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452
Viewing the Synthesized Wires for a Harness Level after Modular Wiring Synthesis. 453
Viewing the Synthesized Wires for all Harnesses after Modular Wiring Synthesis . . . 454
Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454
Reporting on Missing or Inconsistent Options Promoted to Harnesses . . . . . . . . . . . . . 455

You can run Modular Wiring Synthesis to generate wiring with option expressions.
See “Modular Wiring Synthesis” on page 450 for more information about what Modular Wiring
Synthesis is and for what it is used.
Note
Modular Wiring Synthesis can be run only in single-user mode.
Prerequisites
• A Capital Integrator design with at least one associated Capital Logic design.
• At least one vehicle model.
• At least one signal to route from the Capital Logic design.
• At least one harness in the Capital Integrator design.
• Your user account must have the appropriate permissions and locks such that you can
perform edits on the design.
• You must have a license that allows the use of designs with complex wiring.
Procedure
1. Press Space Bar and enter MWS; the Wiring Synthesis Dialog Box is displayed.

February 2016
Wiring
2. Ensure that Modular Synthesis is selected:
3. Click Go; a progress bar indicates when synthesis is complete.

Results
• The Synthesis tab in the Output Window reports on the synthesis actions and any
signals that have failed to route.
Related Topics
Viewing the Synthesized Wires for a Harness Level after Modular Wiring Synthesis
Viewing the Synthesized Wires for all Harnesses after Modular Wiring Synthesis
Synthesis
Viewing the Synthesized Wires for all Levels of a

Harness after Modular Wiring Synthesis
You can view the wires that have been generated for all levels of a harness during modular
wiring synthesis.
Procedure
Right-click on a harness name in the Design Browser (Design tab) and select Set All Levels
Active.
Results
The signals listed under the Signals node in the Design Browser (Design tab) are updated to list
the wires that have been generated for that harness.
Note
You can click on a wire to highlight the path that it follows in the diagram window. To hide
the generated wiring for a harness, right-click on the harness name and select Set All Levels
Inactive.

February 2016
Wiring
Related Topics
Synthesis
Viewing the Synthesized Wires for a Harness Level

after Modular Wiring Synthesis
You can view the wires that have been generated for a specific harness level during modular
wiring synthesis.
Procedure
In the Configuration Setting Browser Window (Configuration tab), expand the Harnesses
node, expand the harness node and select the harness level.
Results
the wires that have been generated for that harness level.
Note
the generated wiring for all harnesses, right-click on the harness name and select Set All
Levels in Design Inactive.
Related Topics
Synthesis

February 2016
Wiring
Viewing the Synthesized Wires for all Harnesses

after Modular Wiring Synthesis
You can view the wires that have been generated for all levels of all harnesses during modular
wiring synthesis.
Procedure
Right-click on the Harnesses node in the Design Browser (Design tab) and select Set All
Levels in Design Active.
Results
the wires that have been generated for the harnesses.
Note
You can click on a wire to highlight the path that it follows in the diagram window.
To hide the generated wiring for all harnesses, right-click on the harness name and select
Set All Levels in Design Inactive.
Related Topics
Synthesis
Viewing the Synthesized Wires for all Harnesses in

a Vehicle Model after Modular Wiring Synthesis
You can view the wires that have been generated for all harnesses in a vehicle model during
modular wiring synthesis.
Procedure
In the Configuration Setting Browser Window (Configuration tab), expand the Models node
and select the vehicle model.
Results
the wires that have been generated for the harnesses in that vehicle model.

February 2016
Wiring
Reporting on Missing or Inconsistent Options Promoted to Harnesses
Note
the generated wiring for all harnesses, right-click on the harness name and select Set All
Levels in Design Inactive.
Related Topics
Reporting on Missing or Inconsistent Options

Promoted to Harnesses
You can report on missing or inconsistent options promoted to harnesses. This report runs a
simulation of wiring synthesis in the Design Assistant. It therefore also reports on general
synthesis issues. This does not update the harnesses or create any new objects.
Prerequisites
Assistant.
Procedure
1. In the Design Assistant, select the toggle Report inconsistent harness options. ( ).
2. Click the Run Checks ( ) button; a summary of problems is listed in the Design
Assistant Output table and more detailed descriptions are displayed on the Synthesis tab
of the Output Window.

February 2016
Wiring
Manual Wiring Synthesis

This is used only if you are working with a design that has no complexity (that is, only a single
harness level, which normally means there are no options). This process can be used to
synthesize wiring for selected signals.
Note
The results of manually synthesizing wiring may be different to the results of using
Composite Wiring Synthesis (CWS). This is because manual synthesis does not take into
account some factors that CWS does (for example, variant options and non-active levels). You
can use CWS to synthesize wiring for selected signals. See “Running Modular or Composite
Wiring Synthesis for Selected Signals” on page 467.
The process requires that one Harness Level is defined for each Harness in the design in order
that wiring can be routed through all harnesses. The harness levels are generated automatically
if you do not have the Composite Wiring Synthesis option installed).
In the example below, the harness H1 has just one level L1.
Figure 18-7. Harness H1 with One Level L1
Once the harness level for each harness has been created, the next step is to define and route the
wires for the individual harness levels.
In order to do this, you must set the harness levels as active. This means that the system can
generate wires and routing through all of the harnesses.
Once the harness levels are active, you can synthesize (create) the wires from the logical
signals. When you do this, the system will route the signals and generate the required wires,
splices and multi-terms. See “Detailed Descriptions of Wiring Synthesis Output” on page 458
for details of how wiring synthesis generates and routes wires in specific scenarios.
If you have added Wire Part Specification constraints and Terminal Type Specification
constraints to objects, these will be used to add properties to the wires that are created. When
creating splices, the system takes into account any constraints or rules that have been set.

February 2016
Wiring
Manually Synthesizing Wiring for Selected Signals
After the wiring has been synthesized, you can generate basic reports from the Reports menu.
Reports can be created for bundle contents, multicore wire lists and a component bill of
material. More detailed reports can be generated for options, harness levels and connectivity
information. See “Reports” on page 419 for more information.
The topological layout can be edited after wiring has been synthesized and the signals can be
rerouted.

You can manually synthesize wiring for selected logical signals in the design.
Prerequisites
• The harness level for each harness in the design must be set as active. This means that
the system can generate wires and routing through all of the harnesses. See “Active
Harness Level” on page 358.
Procedure
Select the signals in the Design Browser (Design tab) and either:
• right-click on them and select Synthesize Wiring.

Results
• The system routes the signals and generated the required wires, splices and multi-terms.
• The system highlights the new wires on the design.
• The Synthesis and Signal Details tabs in the Output Window report on the synthesis
actions and provide details if the signal failed to route.
Related Topics
Deleting the Synthesized Wiring for Selected Signals
Deleting the Synthesized Wiring for all Signals

You can delete the wiring that has been synthesized for all signals in the design.
Procedure
1. Press Space Bar and enter Delete All Wiring.
2. The wires and splices are deleted.

February 2016
Wiring
Related Topics
Deleting the Synthesized Wiring for Selected

Signals
You can delete the wiring that has been synthesized for selected signals in the design.
Procedure
1. Right-click on the routed signal in the Design Browser (Design tab) and select Delete
Wiring. Alternatively, click on the routed signal in the Design Browser (Design tab),
pressing Space Bar and entering Delete Wiring.
2. The wires and splices are deleted.
Related Topics
Deleting the Synthesized Wiring for all Signals
Detailed Descriptions of Wiring Synthesis

Output
Wiring synthesis generates and routes wires in particular ways for specific scenarios.
Synthesis of Jumper Wires

If two devices that are connected by a net conductor in a Capital Logic schematic have been
placed in the same topological slot, each internal pin has its own cavity. When wiring is
synthesized, these two cavities are connected by a jumper wire. When you select the signal or
wire in the Design Browser (Design tab) after wiring has been synthesized, the jumper wire is
highlighted in the diagram as an arc shape on the side of the slot.
Synthesis of Multicores
Where signals in Capital Logic are grouped into a multicore, one or more physical multicores
are created in Capital Integrator when you synthesize wiring:
• The signals in a multicore are routed along the same bundles as far as possible and
physical multicores are created in each harness where more than one wire is synthesized.

February 2016
Wiring
Detailed Descriptions of Wiring Synthesis Output
• If the multicore in Capital Logic has a shield, a shield conductor is created for each
physical multicore.
• Where the shield is unconnected in Capital Logic, a cut-end splice is created in Capital
Integrator and positioned close to the end of the physical multicore to provide shielding
over as much of the multicore as possible. The offset of the cut-end from a connector
can be controlled using “Minimum Splice Separation” constraints.
• Where the shield is connected to a device in Capital Logic (and where the multicore
connects to an inline connector), Capital Integrator synthesizes either a pigtail wire and
splice or will connect directly to the connector cavity or backshell. The actual
implementation can be controlled using constraints (see “Overview of Rules and
Constraints” on page 287).
• After wiring synthesis, you can edit the shield termination. See “Modifying a Shield
Termination” on page 505 for more information.
Synthesis of Complex Multicores

In Capital Integrator, a multicore is treated as a single cable containing exactly the same number
of wires as defined in the associated Capital Logic design.
During synthesis of a complex multicore, the implications of this are:
• If one or more of the signals follow a particular path (for example, through an inline), all
the signals follow this path.
• Network synthesis supports networks that are embedded within another multicore.
• Whenever one or more of the signals in the multicore need to be spliced in order to
connect to a device, all of the wires in the multicore are spliced.
• Where not all signals connect to a device, a constraint (Termination of single ended
wires/shields) is applied to connectors to control whether synthesis creates dangling
wires / shields that terminate on cut-end splices close to the device’s connector. These
cut-end splices are supported when design data is passed to other Capital applications.
o If the wires are not created, the main multicore is still spliced (that is, with two wire
splices).
o If the logical multicore has a library part number assigned, it is not assigned to
multicores containing fewer conductors.
• Sometimes, a signal within a multicore connects to more than one cavity at the same
device connector. These additional connections result in a single splice in the
appropriate signal’s wire and then two (or more) wires connected to the various
connector pins. These additional wires are not included in a multicore.
• Although a multicore which terminates at multiple connectors will normally need to be
cut and spliced, in some cases it is possible to terminate the innercores at multiple

February 2016
Wiring
connectors without cutting. For example, if the connectors are close together, it may be
possible to untwist the multi-core. A constraint (Maximum multicore takeout) can be
applied to bundles to control the maximum length of untwist.
o In the case where the innercore (or shield) of a multicore is spliced with a 1:1 (two
wire) splice, this constraint is applied. If the length of wire from the splice to the
connector is less than the length specified by this constraint, the splice is not created.
o In the case that a shield has a pigtail, the length used to check against this constraint
is the total length from the 1:1 splice to the connector (that is, the length of the shield
and pigtail wire added together).
o This constraint has no effect on pigtail splices (used to terminate shields).
• The synthesized cut-end splices are supported when wiring is exported or imported.
Examples of Multicore Routing

The following are simple examples of multicore routing from wiring synthesis.
In each case:
• The top image is a logical system design from Capital Logic.

• The middle image is the associated topological design from Capital Integrator.
• The bottom image is the resulting wiring design generated using Capital AutoView
Assist for Integrator.
Figure 18-8. Twisted Pair
This example contains a simple twisted pair and shows that two physical multicores are created
because of the inline.

February 2016
Wiring
Figure 18-9. Single-ended Shielded Multicore
This example contains a single-ended shielded multicore and shows how pigtails are
synthesized at the inline and left-hand device. This could also show that a cut-end splice is
created near DEV4 (this would need to be shown in Capital Integrator because it is not shown in
a wiring diagram.

February 2016
Wiring
Figure 18-10. Multiple-ended Twisted Pair
This example contains a special case of a multiple-ended twisted pair (typically used for
networks). Note that there is only one multicore in the logical schematic, but four physical
multicores are created.

February 2016
Wiring

February 2016
Wiring

February 2016
Wiring
Network Wiring Synthesis

Networks (for example, LIN, CAN, FlexRay) are typically implemented as a linear bus created
using multiple twisted pairs which are spliced together. A typical physical implementation is as
follows:
Figure 18-11. Network Wiring Example Implementation
Each network has a number of rules that govern its structure, depending on the type of bus.
These rules can be categorized as follows:
Figure 18-12. Network Wiring Structure Rules
• Connections are made by a twisted pair multicore or a single wire.

• Multi-terminations are not allowed (splices are used where more than two device are
connected.
• The ends of the bus are connected to devices containing resistor terminations. These two
devices are separated by the longest wire length in the network.

February 2016
Wiring
• The overall length of the bus between the ends (L) has a maximum length.
• The multicore stubs that tie devices to the bus (l) have a minimum and maximum length
(a stub is defined as a twisted pair or single wire connecting a device to a splice on the
bus).
• There is a minimum distance (d) between stubs (splices).
• When an optional device is not attached to the network, the stub for that device should
not appear on the harness and bypass wires take the place of the splice.
When synthesizing network wiring, you must consider the following:
• In the Capital Logic design:

o You must set a Pin Type attribute of IxO Terminated on the pins at the ends of the
network
o You may set a Pin Type attribute of IxO on the pins on the network stubs
• In the Capital Integrator design, you must set a “Network Specification” constraint that
applies to that network.
• Wiring synthesis applies the constraint to network signals and identifies them by using
the following rules;
o If a “Network Specification” constraint matches a top-level multicore, all signals in
that multicore and its children belong to the same network, regardless of whether the
signals also match other “Network Specification” constraints. If any of the signals
match a different constraint, a warning is generated. Only top-level multicores are
matched against the constraint.
o If a multicore does not match the constraint but all of the signals within the multicore
match a “Network Specification” constraint, they are treated as a network. A
warning is generated if not all of the signals match or if some match another
“Network Specification” constraint with different values. In this case, none of the
signals are routed as a network.
Note
If a shielded multicore matches a “Network Specification” constraint, a warning
is generated. The multicore wiring is synthesized as for a network and the shield
is added as for any other multicore.
o A signal that is not in a multicore but that matches a “Network Specification”

constraint is routed as a single core network.
• Wiring synthesis generates network wiring as follows:
o If a network signal does not have exactly two terminated cavities, it is not routed and
wiring synthesis generates an error. If the values specified for stubs in the “Network
Specification” constraint cannot be met for a signal, it is not routed. However, if the

February 2016
Wiring
max length for the network cannot be met for a signal, it is still routed. This situation
can be identified by running the design rule check for Network wiring that breaks
specified limit after wiring synthesis.
o Only splices connect stubs to the network (never multi-terminations or direct
connections to other stubs).
o Splices adhere to the “Network Specification” constraint with regard to the length of
a wire from an unterminated device and the distance between stub splices. A splice
will also adhere to any “Minimum Splice Separation” constraint.
o During the routing of a signal for a non-terminated device, a splice adheres to the
“Network Specification” constraint. That means, it may be pulled back along the
stub bundle or pushed on to the mainline bundle.
o When optional devices are not active, bypass wiring is used. Wiring synthesis adds
the bypass wires to the multicore if all of the active wires have been bypassed.
Running Modular or Composite Wiring

Synthesis for Selected Signals
You can run modular wiring synthesis (MWS) or composite wiring synthesis (CWS) for
individual signals or a set of selected signals.
Note
Whichever type of synthesis is selected, it will only affect changes for the specified signals
and will not alter any other wiring or generate new wiring for other signals within the
diagram.
Prerequisites
• You must have a complex wiring synthesis license.
• If you want to run CWS, the normal perquisites for it must have been met. See the CWS
and Wiring Generation section in “Composite Wiring Synthesis” on page 442 for a list
of these prerequisites.
• If you want to run MWS, the normal prerequisites for it must have been met. See
Synthesizing Modular Wiring.
Procedure
1. Select the signals in the Design Browser (Design tab), right-click on one of them and
select Synthesize Wiring; the Wiring Synthesis Dialog Box is displayed.
2. Select which sort of synthesis you want to run and click Go; a progress bar indicates
when synthesis is complete.

February 2016
Wiring
Results
• The Synthesis tab in the Output Window reports on the synthesis actions and any
signals that have failed to route.
Related Topics
Merge of Logical Multicores in Wiring

Synthesis
A number of Capital features enable you to identify nets, which have been designed separately,
as representing the same signal. These features include equivalence sets, combined devices in
Capital Integrator and the Equipotential attribute on pins in Capital Logic. In each case, the
individual nets are merged so that they represent a single signal in Capital Integrator.
Multicores are merged along with the nets so that physical multicores can be synthesized. Not
all of the logical nets need to be in a logical multicore. However, for those that are, the logical
multicores must meet the following conditions:
• For hierarchical (or nested multicores), each level of the multicore must be identical and
meet the other constraints in this list.
• The multicores must be the same type (that is, the indicator type must be the same).
• The number and type of conductors in each multicore must be identical. This means, for
example, if one multicore contains three nets and a shield, all the other multicores must
contain three nets and a shield.
• The resulting merged logical multicore must also match the number and type of
conductors in each of the original multicores. This means that all the conductors in each
multicore must be equivalenced to a conductor in the other multicore(s).
• Attributes and properties on the multicores do not need to be the same. However, they
will be considered merged in the same way that attributes and properties on normal
signals are merged. This means that, if there is a conflict, the resulting merged multicore
will act as if it does not have that particular attribute or property. This could effect the
behavior of constraints.
If the multicores cannot be combined (that is, they do not have equivalent structures), the
signals are combined but synthesis routes these signals as normal signals and does not put the
wiring into a multicore. An error message is displayed on the Synthesis tab of the Output
Window.

February 2016
Wiring
If previously combined multicores are modified in the associated logical diagrams so that their
structures no longer match, the Sync tab in the Output Window displays a notification message
but no wiring is removed from the combined multicore.
Related Topics

February 2016
Wiring
Import of Carry-Over Wiring

Many vehicle programs have a high percentage of systems and legacy wiring that are carried-
over from existing vehicles. If the new vehicle requires only minor changes, it may not be
desirable to re-create all the system designs and attempt to re-create the existing wiring in a full
generative process. Instead of this, you can import the wiring in X2ML format (Harness X2ML
or Wiring X2ML) into a Capital Integrator design and then integrate any new or changed
systems into these existing harnesses. The X2ML data required can be generated from existing
Capital HarnessXC or Capital Logic wiring designs or potentially translated from any third-
party wiring format.
This enables the following:
• You can import X2ML data for a harness for re-use in a Capital Integrator design. All
connectors are imported as interface connectors.
Note
If the X2ML includes the bundle topology, the system imports it. Otherwise, it
creates a dummy topology, which can be modified in Capital Integrator.
• Each wire must be associated with a signal. You can define how signals are identified
from the imported data (for example, extracted from the wire's name).
• You can incorporate new systems by associating a Capital Logic design (system design)
and placing the new devices into slots as normal.
• You can also retain imported wiring for modified devices by merging an imported
interface connector into a new slot.
For example, you have imported a harness that includes a radio. The radio is represented
by an interface connector in Capital Integrator.
In a system design in Capital Logic, you add some extra signals to the radio and then
associate the system design with the Capital Integrator design. The modified radio is
represented as a device in Capital Integrator.
You want to use this device to determine the signals but want to keep the old wiring. To
do this, you place the radio device in a slot and then merge the interface connector into
that slot. This replaces the interface connector with a slot connector but retains the
wiring.
High-level Flow for Importing Carry-Over Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Importing Carry-Over Wiring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Merging a Slot and Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474

February 2016
Wiring
High-level Flow for Importing Carry-Over Wiring
High-level Flow for Importing Carry-Over Wiring

There is a particular flow for importing carry-over wiring.
1. Create an empty Capital Integrator design and diagram. You must have defined any
options required by the wiring in the project. The diagram can have a skeleton.
2. Import the carry-over wiring for a harness in X2ML format, specifying scaling and how
to map wires to signals. A new harness is created in the design and diagram.
3. Import any other required carry-over wiring for other harnesses. Again, the harnesses
are created in the design and diagram. During the import, you place the harnesses in the
diagram.
4. Merge the harnesses at inline connectors by mating interface connectors. At this point,
you have a Capital Integrator design with wiring but no associated system designs from
Capital Logic.
5. If you want to incorporate a new system into the imported wiring:
a. Create a system design in Capital Logic.
b. Associate the system design with the Capital Integrator design.
c. Place the new devices in slots and connect them to the topology as required.
If you need to modify an existing, imported device to add connections to new signals:
a. Create a system design that contains the existing devices that need to be changed as
well as any new devices.
b. In the system design, for any existing signals, create dangling nets connected to the
existing device in the system design. The nets will be merged with imported signals
in Capital Integrator, so should be named accordingly.
c. In the system design, for any new signals, create nets that connect the devices as for
a normal system design.
d. Associate the system design with the Capital Integrator design. Note that the objects
in the system design should be tagged with any required options.
e. Place the existing and new devices in slots in Capital Integrator.
f. You now have two representations of the existing device: a device in a slot and an
interface connector (created during the harness import). Merge them by dragging the
interface connector over the slot.
The interface connector is removed, its bundle is connected to the slot connector and
the wiring connects to the slot connector. The system considers existing signals fully
routed and connects them to the device. However, the system considers new signals
unrouted and connects them to new cavities.
6. If required, define new harness levels.

February 2016
Wiring
Importing Carry-Over Wiring
Note
If the X2ML file for a harness contains no derivatives, the system creates a single
harness level containing all options on import. It associates all wires with this
harness level. If the file contains one or more derivatives, the system imports them as
harness levels and associates wires with the appropriate ones.
7. Synthesize new wiring.

Wiring synthesis creates wiring for new signals but does not modify the wiring for any
imported, fully routed signals. In some cases, it may add a wire into an existing signal
(for example where a new device has a connection to an existing signal).
Caution
As a general rule, you should not delete existing wiring. However, you may want to
do this if you make large changes to a signal. Delete the wiring only after associating
a system design containing the signal. The system automatically associates signals from
the system design with signals of the same name in the Capital Integrator design. If you
delete existing wiring that was imported as a multicore, without associating the imported
signals with ones from a system design, wiring synthesis does not recreate the wires as a
multicore. It creates them as normal wires. In this case, the system does not synthesize
shield signals at all.
Related Topics
Merging a Slot and Interface Connector

You can import carry-over wiring for a harness in X2ML format (Harness X2ML or Wiring
X2ML) into a Capital Integrator design and diagram, specifying scaling and how to map wires
to signals. A new harness is created in the design and diagram.
Prerequisites
• The carry-over wiring is available in X2ML format.
• You have created and opened the Capital Integrator design and diagram.
• You must have defined any options required by the wiring in the project.
Procedure
1. Press Space Bar and enter Import Harness; the Import Harness Dialog Box is displayed.
2. Specify the X2ML File that you want to import and whether you want to Run DRCs.

February 2016
Wiring
3. Specify the Signal Name - Method.

4. Click Import. The following happens:
• A new harness is created in the Capital Integrator design and diagram. The harness
consists of interface connectors and bundles.
• If the X2ML includes the bundle topology, the system imports it. Otherwise, it
creates a dummy topology. Initially, the topology is displayed as a ghost image that
you can drag around the diagram to place it.
• A Scale field is displayed at the top left of the diagram window. You can increase
the value in this field to increase the size of the ghost image in the diagram. This
field affects only the location of the interface connectors and bundle nodes so that
they are closer together or further apart. A lower number means they are closer
together and bundle segments are graphically shorter. A larger number means they
are further apart and bundle segments are graphically longer. The interface
connector symbols do not change size. Alternatively, you can use the + and - keys on
your keypad.
• A Rotation field is displayed at the top left of the diagram window. You can specify
the number of degrees (positive or negative) by which you want to rotate the ghost
image. Only the locations of the interface connectors rotate, not their symbols.
Alternatively, you can use keyboard shortcuts:
o Ctrl+,
Rotates anti-clockwise by the major rotation increment specified for rotation
increments. See Defining Rotation Increments in the Capital Design Tools -
o Ctrl+.
Rotates clockwise by the major rotation increment specified for rotation
increments.
o Ctrl+<
Rotates anti-clockwise by the minor rotation increment specified for rotation
increments.
o Ctrl+>
Rotates clockwise by the minor rotation increment specified for rotation
increments.
o R
Rotates clockwise by 90 degrees.
o T

February 2016
Wiring
Rotates anti-clockwise by 90 degrees.

5. Click the diagram window or press the Enter key to place the graphics at their current
location; a progress bar indicates the completion of the harness import.
Results
• Slots and connectors always remain their original size. Physical bundle lengths also
remain the same.
• All attributes and properties of the imported wiring and topology are retained, except for
connector types that become interface.
• Each import creates a distinct set of interface connectors. That is, the import does not
attempt to use existing connectors.
• Ring terminals are represented as connectors in the X2ML. These are converted to
interface connectors.
• Node names from X2ML are not preserved.
• Any options referenced by the harness in the X2ML are assigned to the harness as
applicable in Capital Integrator.
• If the X2ML file contains no derivatives, a single harness level containing all options is
created. All wires are associated with this harness level.
• If the X2ML file contains one or more derivatives, the system imports them as harness
levels and associates wires with the appropriate ones.
Related Topics

After importing carry-over wiring, you may need to modify an existing, imported device to add
connections to new signals. You do this by creating a system design that contains the existing
devices that need to be changed as well as any new devices. When you associate that with the
Capital Integrator design and place the devices in slots, you have two representations of the
existing device: a device in a slot and an interface connector (created during the harness
import). You must merge those representations.
Note
See “High-level Flow for Importing Carry-Over Wiring” on page 471 for the full carry-over
wiring flow, including modifying an existing device.
Prerequisites
You must have placed the modified device from the system design in a slot.

February 2016
Wiring
Procedure
Drag and drop the interface connector over the slot.
Results
• The interface connector is removed and the wiring connects to the slot connector.
• If the slot has a single slot connector, the wiring connects to that.
• If the slot has multiple slot connectors, a dialog box asks you to select the required
connector for merging.
• Wires that were connected to the interface connector re-connect to the cavities of the slot
connector, matched by signal.
• If the slot connector has multiple cavities carrying the appropriate signal, the system
selects a cavity as follows:
o If there is a cavity with a matching name, it uses that.
o If there is an unconnected cavity, it uses that (or the first of multiple, unconnected
ones).
o If neither of the above apply, the first matching cavity is used.
• The system considers new signals unrouted and connects them to new cavities.
• If the interface connector has a wire from a signal that does not exist at the slot, the wire
is deleted (and a message displays in the Output Window).
Related Topics

February 2016
Wiring
Wire Editing in Capital Integrator

After synthesizing wiring, you can edit the wires in various ways.
Generating a Wiring View of a Synthesized Signal or Multicore . . . . . . . . . . . . . . . . . . 476
Adding a Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Moving a Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Editing Wire Paths. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Defining Specification Attributes for a Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Specifying the Harness Levels on which a Wire Exists . . . . . . . . . . . . . . . . . . . . . . . . . . 480
Generating a Wiring View of a Synthesized Signal

or Multicore
After wiring synthesis, you can generate a wiring view of a synthesized signal or multicore.
The wiring view shows individual devices, connectors and wires that implement a signal. If the
signal is a member of a multicore, the entire multicore is included in the wiring view.
Prerequisites
• Wiring must have been synthesized. See “Synthesizing Wiring” on page 440.
Procedure
1. In the Design Browser (Design tab), select the signal and click the Visualize the
selected signal button; a tab named after the signal is displayed in the Output Window.
If the signal is a member of a multicore, the tab is named after the multicore. The tab
contains a wiring diagram for the signal or entire multicore. See the “Signal/Multicore
Name (Wiring View)” section in “Output Window” on page 639 for a description of all
the features of this tab.
2. If you have the necessary license to maintain multiple style sets, select the style set you
want to use from the Style drop-down list on the wiring view. If you do not have the
necessary license, only the default style set for Capital Logic is available.
3. If the wiring view is cluttered, specify a higher number for the Spacing option on the
wiring view so that the amount of whitespace between the objects increases.
Note
You can tear this tab from the application interface so that it is a free-floating dialog
box that can be resized. To do this, click the tab name and drag it. To return the
wiring view to the Output Window, close the dialog box.
4. If you select an object in the wiring view, it highlights in the Capital Integrator diagram.

February 2016
Wiring
Adding a Wire
5. If required, edit the wiring (see “Wire Editing in Capital Integrator” on page 476).
Within the wiring view, you can right-click on an object to display the standard menu
available for that object within Capital Integrator. For example, you can select
Properties and edit the attributes/properties for that object.
6. After editing the data, click the Refresh ( ) button on the wiring view tab to update the
wiring view with the changes.
Related Topics
Adding a Wire
Moving a Wire
Editing Wire Paths
Updating Wire Lengths
Defining Specification Attributes for a Wire
Specifying the Harness Levels on which a Wire Exists
Creating a New Combined Wire from Selected Wires
Adding a Wire
When you synthesize wiring, wires are added to the design. However, you may want to add
more wires manually. For example, if you have any unrouted signals, you may want to add a
wire along which you can route them.
You can either add a wire starting from an existing cavity in a connector (virtual, inline or
interface) or create a new cavity and then add a wire. See “Adding a Cavity to a Connector” on
page 162 for more information about creating a new cavity.
You can also add a wire between existing cavities on ground slots. These wires are not based on
any net conductor connection from the functional designs in Capital Logic. You cannot add
wire connections like this between equipment slots (even if ground devices are placed in the
equipment slots). See “Grounds and Ground Wiring Flow Using Ground Design Functionality”
on page 198 for more information about the overall workflow when using ground devices and
slots.
The Add Wire facility works in the context of active harness levels so you must set the
appropriate vehicle configuration or specific harness levels to active before adding a wire. See
“Active Harness Level” on page 358 or “Setting an Active Vehicle Configuration” on page 368
for more information about how to do this.
Procedure
1. Right-click on the connector from which you want the wire to start in the Design
Browser (Design tab) and select Add Wire. Alternatively, click on the connector, press
Space Bar and enter Add Wire. The Add Wire Dialog Box is displayed.

February 2016
Wiring
Ground-to-ground Connections
2. In the From End window, click the cavity at which you want the wire to start.
3. In the To End window, click the cavity at which you want the wire to end.
Note
If you are adding a wire from a cavity on a ground slot, the To End box lists cavities
on all other ground slots (including those on different harnesses). Note that you may
need to create more than one wire if the target cavity is in a different harness). If a cavity
in the To End box connects to a different signal to the one that is connected to the cavity
in the From End field, the signal name in the To End box is displayed in red.
4. If there are multiple harnesses at the connector, a Harness field is displayed. Select the
harness to which you are adding the wire from the drop-down list.
5. Click OK.
Results
• The wire is added to the design.
• If there is a signal connected to one of the cavities, the wire is added to the list of wires
under that signal in the Design Browser (Design tab).
Ground-to-ground Connections
Ground-to-ground connections are made either using existing signals in one of the ground slots
or by creating a new signal when neither cavity already has a signal. The following scenarios
are possible:
• If the source cavity has one signal, it is used as the signal for the new wire.
• If the source cavity has multiple signals, the user is prompted to select a signal.
• If the source cavity has no signals, the signal is chosen from the destination cavity.
• If neither cavity has a signal, a new Ground-Connecting signal is created. This is
displayed in browser trees with the ground device icon . Ground-connecting signals
can be edited only manually, cannot be routed automatically, and are removed if the last
wire is deleted from the signal. A ground-connecting signal is named after the source
ground slot with a unique numeric suffix.
• If the cavities are associated with different signals, the signal on the source cavity is
associated with the destination cavity when the wire is added. The destination cavity is
then associated with more than one signal, effectively shorting those signals together.
All ground-to-ground connections made using the Add Wire facility will be listed in the
Depopulate Wiring dialog box because they are surplus to the wiring required by the
functional data. If you depopulate all wiring (from all levels) of a ground-connecting signal, this
deletes the signal as well.

February 2016
Wiring
Moving a Wire
Related Topics
Moving a Wire
Moving a Wire
When you synthesize wiring, wires are added to the design. However, you may want to move
wires after you have routed logical signals. You can do this by moving a wire end from one
cavity to another.
Procedure
1. Right-click on the wire name in the Design Browser (Design tab) and select Move Wire
from the pop-up menu. Alternatively, click on the wire name in the Design Browser
(Design tab), press Space Bar and enter Move. The Move Wire Dialog Box is displayed.
2. In the From End window, select the wire end that you want to move.
3. In the To End window, select the cavity to which you want the wire end to move.
Related Topics
Adding a Wire
Editing Wire Paths

When you synthesize wiring, Capital Integrator automatically uses the shortest route that a wire
can take. However, you may want a wire to take a different, longer route. After you have
synthesized wiring, the Edit Wire Path facility enables you to reroute a wire so that it passes
through a particular through node.
When you connect bundles together in such a way that they form a loop, a through node is
added automatically to the last bundle that you create in the loop. You can also create through
nodes manually. See “Creating a Through Node on a Bundle” on page 127 for more
information.
Procedure
1. Right-click on the wire in the Design Browser (Design tab) and select Edit Wire Path.
Alternatively, click on the wire, press Space Bar and enter Set Path.
2. In the diagram window, click on a through node through which you want the wire to
pass instead of its current route. When the mouse cursor is over a valid through node, a
bundle symbol is displayed . Otherwise, a circle with a diagonal line is displayed
.

February 2016
Wiring
3. The new route of the wire is displayed in red. To accept this new route, right-click on the
through node in the diagram window or on the wire in the Design Browser (Design tab)
and select Commit from the pop-up menu. Alternatively, select Cancel from the pop-up
menu to cancel the reroute.
Related Topics

You can use the Edit Properties dialog box to specify the color, material, spec and CSA
attributes for a wire.
Note
When you assign a library part to the conductor, the Part Selection dialog box uses these
attributes to restrict the search for a library part.
Procedure
1. Right-click on the wire in the Design Browser (Design tab) and select Properties; the
Edit Properties Dialog Box is displayed.
2. On the General tab, edit the Color, Material, Spec and CSA attributes in the
Specification section.
Specifying the Harness Levels on which a Wire

Exists
You can specify the harness levels on which a wire exists.
Harness levels are assigned to wires to indicate that those wires exist in the derivative harness
that the level represents. When wiring is synthesized, wires are assigned to appropriate harness
levels to support the functional options that have been defined. The Edit Properties dialog box
for a wire enables you to edit manually the harness levels to which a wire has been assigned.
The Configuration section also contains an Option Expression field that cannot be edited.
This contains the option expression that has been generated either by running Composite Wiring
Synthesis (see “Composite Wiring Synthesis” on page 442) or by using the Generate Option
Expressions facility.
Procedure
1. Right-click on the wire in the Design Browser (Design tab) and select Properties; the
Edit Properties Dialog Box is displayed.

February 2016
Wiring
2. On the General tab, click the ellipsis (...) button next to the “Configuration: Level” field;
the Edit Levels Dialog Box is displayed.
3. Add the harness levels on which the wire exists to the Selected window and click OK;
the Edit Levels dialog box closes and the “Configuration: Level” field updates
accordingly.

February 2016
Wiring
Combined Signals and Combined Wires

Normally, each wire in a vehicle is used to implement a single signal. However, in some cases,
it is desirable to re-use a wire to implement more than one, mutually exclusive signal. This can
be achieved by creating a combined signal and combined wire. Wires in a combined signal can
either belong to just one child signal or be shared between all the signals.
Combined signals can contain only child signals of the same type. For example, if a shielded
signal is added as a child signal to a combined signal, all child signals for that combined signal
become shield signals.
When wires are combined:
• The individual wires are removed from the child signals of the combined signal and the
combined wire is added to that combined signal. The reverse action splits a combined
wire and adds regular wires into the child signals.
• The attributes and properties are not copied from the wires and splices being combined.
Instead, the combined wires and splices will use the “Wire Specification” or “Splice
Specification” constraints to identify which attributes and properties should be set for
them.
• If the wires are attached to a connector on a junction box slot, the cavities or backshell
terminations to which the wires are connected lose their signal mappings unless they are
connected to other connectors that are not being combined.
Figure 18-13. Before and After Example A for Combining Wires Connected to
Slot Connectors
In the above example, two wires going through the slot connector on the right of the slot are
combined. Note that the mapping from the splice onto the right bottom cavity is removed
because it has no connections after the combination.

February 2016
Wiring
Figure 18-14. Before and After Example B for Combining Wires Connected to
Slot Connectors
In the above example, two dashed wires going through the slot connector on the right are
combined. Note that the mapping from the splice onto the right bottom cavity is kept because it
has a connection to a wire that is not combined.
Wires can be combined if the following is true:
• The wires belong to the same harness.

• The wires belong to a combined signal or its child signals.
• The wires are not center-stripped.
• The wires do not belong to a multicore.
• Each wire does not connect to more than one splice.
• The wires connect to the same two combinable ends and to nothing else.
A combinable end can be one of the following:
• Set of splices
The splices must belong to the same harness and carry the combined signal or its
children. When the wires between the splices are combined, the splices are combined
into a single splice. For example:
Figure 18-15. Before and After Example of Combined Splice
• Set of slot-internal splices

February 2016
Wiring
The splices must belong to the same slot and carry the combined signal or its children.
The splices must connect to the wires through the same slot connector or hole. In the
case of a connector, the splices connect to the wires either only through cavities or only
through backshell terminations.
When the wires between the slot-internal splices are combined, the splices are combined
into a single slot-internal splice. For example:
Figure 18-16. Before and After Example of Combined Slot-Internal Splice
• Set of slot device pins through a slot connector

The devices must belong to the same slot and carry the combined signal or its children.
The slot device pins can belong to slot-internal splices, regular slot-internal devices or a
mix of them. The pins must connect to the wires through a single backshell termination
or cavity.
When the wires between the slot device pins are combined, the slot internal connectivity
does not change.
Figure 18-17. Before and After Example of Combined Wire Connected to Slot
Device Pins Through Slot Connector
• Single slot device pin through a hole

The slot device pin must carry children of the combined signal and belong to a regular
slot internal device. The slot device pin must connect to the wires through a single hole.

February 2016
Wiring
When the wires are combined, the slot device pin will loose mappings onto wires that
have been combined and will gain a mapping to the combined wire. For example:
Figure 18-18. Before and After Example of Combined Wire Connected to Slot
Device Pin Through Hole
• Set of cavities or backshell terminations

The set must belong to the same inline or interface connector. Cavities and backshell
terminations cannot be mixed. Each cavity or backshell termination must carry the
combined signal or its children. The combined wire will connect to the cavity or
backshell termination with the lowest name.
For example:
Figure 18-19. Before and After Example of Combined Wire Connecting to
Cavities or Backshell Terminations
This example shows an inline before and after four wires on the right are combined.
Note that all of the conductors on mated cavities on the left have been moved to the
cavity mated to the one to which the combined wire connects. This applies to any
conductor that carries the same signal as the wires being combined.
Setting a Constraint to Combine Wires at a Cavity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Creating a New Combined Signal from Selected Signals. . . . . . . . . . . . . . . . . . . . . . . . . 488
Adding Selected Signals to an Existing Combined Signal . . . . . . . . . . . . . . . . . . . . . . . . 488
Combining Selected Signals with a Compatible Signal . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Removing Selected Child Signals from a Combined Signal . . . . . . . . . . . . . . . . . . . . . . 490
Uncombining All Child Signals from a Combined Signal . . . . . . . . . . . . . . . . . . . . . . . . 491

February 2016
Wiring
Combining Wires at a Cavity
Creating a New Combined Wire from Selected Wires. . . . . . . . . . . . . . . . . . . . . . . . . . . 491

Creating a New Combined Wire from a Selected Set of Wires for a Combined Signal 492
Adding Selected Wires to an Existing Combined Wire . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Combining Selected Wires with a Compatible Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
Uncombining Wires . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494

A “Combine Wires at Cavity” action provides the ability to combine signals and wires in one
step and to insert a splice at a cavity for wires from different signals.
If you insert a splice, the wires meet at the splice and a single combined wire goes from the
splice to the cavity. For example, you might want to do this if you have three shields connecting
to one cavity.
If you do not insert the splice, the wires are replaced by one wire. You might want to do this
where the wires can be combined one side of an inline connector but need to be separate wires
on the other side.
Note
You can set a constraint on a connector, slot or design to trigger the combining of wires at a
cavity when the post wiring synthesis action ‘Combine Wires’ runs. See “Setting a
Constraint to Combine Wires at a Cavity” on page 487.
Prerequisites
Multiple conductors (wires or shields) from different signals must connect to the cavity. If all of
the conductors are from the same signal, only the “Add Splice at Cavity” action is available (see
“Converting a Multiple Termination to a Splice” on page 500).
Procedure
1. In the Design Browser (Design tab), right-click on the cavity and select Combine Wires
at Cavity; the Combine Wires at Cavity Dialog Box displays.
2. Specify the signal name for the combined signal.
3. Select the wires that you want to combine and specify whether you want to insert a
splice at the cavity.
4. Click Combine Selected.
5. If you have selected to insert a splice, the cursor changes to a black splice symbol .
Position the cursor over the point on the diagram where you want the splice to be created
and click. If you position the cursor over a location where the splice cannot be created,
the cursor is a splice symbol with a line through it .

February 2016
Wiring
Setting a Constraint to Combine Wires at a Cavity
Results
• If you did not insert a splice, the wires combine.
• If you inserted a splice, the splice appears in the Design Browser (Design tab).
• The combined signal and combined wire are created and display in the Design Browser
(Design tab).
Related Topics

You can set a constraint on a connector, slot or design to trigger the combining of wires at a
cavity when the post wiring synthesis action ‘Combine Wires’ runs.
Procedure
1. Right-click on a connector or slot (or design in the Design Browser (Design tab) and
select Properties; the Edit Properties Dialog Box displays.
2. Click the Rules tab; the rules and constraints set on the object are displayed.
3. Click the Add Constraint ( ) button; the Constraint Selection dialog box displays.
4. From under the Routing node, select Combine Wires at Cavity and click OK; the
dialog closes and the default constraint appears on the Rules tab.
5. Edit the constraint as required. See the “Combine Wires at Cavity” section in “Standard
Constraints for Capital Integrator” on page 298 for details of how to edit it.
6. Click OK.
Results
• When synthesizing wiring with the “Combine Wires” action selected, the system
identifies cavities matching the constraint. At those cavities, it identifies wires matching
the constraint.
• If you did not insert a splice, the wires combine.
• The combined signal and combined wire are created and display in the Design Browser
(Design tab).
• If you inserted a splice, the splice appears in the Design Browser (Design tab).
• If another uncombined wire goes to the cavity and you insert a splice for the combined
wires, the system connects the uncombined wire to the splice, not directly to the cavity.

February 2016
Wiring
Creating a New Combined Signal from Selected Signals
Related Topics
Synthesizing Wiring
Creating a New Combined Signal from Selected

Signals
You can combine one or more signals to create a new combined signal.
Procedure
1. In the Design Browser (Design tab), select the signals that you want to add to the
combined signal as child signals.
2. Right-click on a selected signal and select Combine > Selected.
A combined signal ( )is added to the Design Browser (Design tab) and the selected
child signals are moved below it.
Related Topics
Adding Selected Signals to an Existing Combined Signal
Combining Selected Signals with a Compatible Signal
Removing Selected Child Signals from a Combined Signal
Uncombining All Child Signals from a Combined Signal
Creating a New Combined Wire from a Selected Set of Wires for a Combined Signal
Adding Selected Wires to an Existing Combined Wire
Combining Selected Wires with a Compatible Wire
Uncombining Wires
Adding Selected Signals to an Existing Combined

Signal
You can add (combine) one or more signals into an existing combined signal.

February 2016
Wiring
Procedure
1. In the Design Browser (Design tab), select the signals that you want to add to the
combined signal as child signals.
2. Right-click on a selected signal and select Combine > Into > [Combined Signal
Name].
The selected signals are moved below the combined signal in the Design Browser
(Design tab). Any wires for the child signals remain with them.
Related Topics
Uncombining Wires
Combining Selected Signals with a Compatible

Signal
You can combine one or more selected signals with a compatible signal to create a new
combined signal.
Procedure
1. In the Design Browser (Design tab), select the signals that you want to combine with a
compatible signal.
2. Right-click on a selected signal and select Combine > With > [Compatible Signal
Name].
Note
To be compatible, a signal must share at least two combinable ends with the selected
signals. If no compatible signals are available, there is no compatible menu option
for you to select.

February 2016
Wiring
A combined signal ( )is added to the Design Browser (Design tab) and the child
signals are moved below it. Any wires for the child signals remain with them.
Related Topics
Uncombining Wires
Removing Selected Child Signals from a Combined

Signal
You can remove (uncombined) selected child signals from a combined signal.
Procedure
1. In the Design Browser (Design tab), select the child signals below the combined signal.
2. Right-click a selected child signal and select Uncombine.
The selected signals are moved from under the combined signal in the Design Browser
(Design tab).
Any combined wires that belong to the signals are split and are added to the split child
signals.
Related Topics

February 2016
Wiring

Uncombining Wires
Uncombining All Child Signals from a Combined

Signal
You can uncombine a combined signal and split out all of its child signals.
Procedure
In the Design Browser (Design tab), right-click the combined signal and select Uncombine.
Results
• The child signals are moved from under the combined signal and the combined signal is
removed from the Design Browser (Design tab).
• Any combined wires that belong to the combined signal are split and are added to all of
the split child signals.
Related Topics
Uncombining Wires
Creating a New Combined Wire from Selected

Wires
You can combine one or more combinable wires to create a new combined wire.
Procedure
1. In the Design Browser (Design tab), select the wires that you want to add to combine.

February 2016
Wiring
2. Right-click on a selected wire and select Combine > Selected.

Results
The individual wires are removed and a combined wire is added below the combined signal to
which the wires belong in the Design Browser (Design tab).
Related Topics
Uncombining Wires
Creating a New Combined Wire from a Selected Set

of Wires for a Combined Signal
You can combine a set of combinable wires for a combined signal to create a new combined
wire.
Procedure
In the Design Browser (Design tab), right-click the combined signal and select Combine >
Wires > [Combinable Set of Wires].
Results
Related Topics

February 2016
Wiring

Uncombining Wires
Adding Selected Wires to an Existing Combined

Wire
You can add (combine) one or more combinable wires into an existing combined wire.
Procedure
1. In the Design Browser (Design tab), select the wires that you want to add to the
combined wire.
2. Right-click on a selected wire and select Combine > Into > [Combined Wire Name].
Results
The individual wires are removed from the Design Browser (Design tab) and are added to the
combined wire.
Related Topics
Uncombining Wires

You can combine one or more selected combinable wires with a compatible wire to create a new
combined wire.

February 2016
Wiring
Uncombining Wires
Procedure
1. In the Design Browser (Design tab), select the wires that you want to combine with a
compatible wire.
2. Right-click on a selected wire and select Combine > With > [Compatible Wire
Name].
Note
To be compatible, a wire must share at least two combinable ends with the selected
wires. If no compatible wires are available, there is no compatible menu option for
you to select.
Results
Related Topics
Uncombining Wires
Uncombining Wires
You can uncombine (split) a combined wire.
Procedure
In the Design Browser (Design tab), right-click the combined wire and select Uncombine.
Results
• The combined wire is removed from the Design Browser (Design tab) and is traced back
to the child signals for which it is relevant.
• New wires are created for those child signals and are added below them.

February 2016
Wiring
Assigning Wire / Splice / Multicore Properties by Rules
• Cavities and Splice are created as necessary.

Related Topics
Assigning Wire / Splice / Multicore Properties

by Rules
If you have added Wire, Splice or Multicore Specification constraints and Terminal Type
Specification constraints to objects in a design, these rules are used during wiring synthesis to
assign part properties and attributes to wires, splices and multicores that are created.
See “Overview of Rules and Constraints” on page 287 for more information about constraints.
After you have synthesized wiring, however, you may want to change the rules and constraints
relating to property/attribute specification and terminal type specification and re-apply them.
You could delete all wiring and run wiring synthesis again, but it may be easier to modify the
rules and constraints as required and then use the Assign Specifications by Rule facility to re-
assign properties and attributes to wires, splices and multicores.
Procedure
1. Press Space Bar and enter Specs. The Assign Wiring Specifications by Rule Dialog Box
is displayed.
2. Select the boxes next to the type of objects to which you want to re-assign properties and
attributes.
Select one of the following Where data exists options:
• Don't Overwrite

February 2016
Wiring
Splice Editing in Capital Integrator
Select this if you do not want to overwrite properties and attributes that are already
set on objects but do want to apply the properties and attributes to objects where they
are not set already.
• Preserve Library Data
Select this if you do not want to overwrite the properties and attributes on any wires
that have library parts assigned to them but do want to overwrite the values on
objects without library parts.
• Overwrite and Remove Part
Select this if you want to overwrite the properties and attributes on all objects and
unassign library parts.
3. Click the OK button to exit the facility and to re-assign the properties and attributes in
the design.
Splice Editing in Capital Integrator

There are various ways in which you can edit splices.
• Add a splice (see “Creating a Splice” on page 496)
• Move a splice (see “Moving a Splice” on page 497)
• Convert a multiple termination to a splice (see “Converting a Multiple Termination to a
Splice” on page 500)
• Decompose a splice (see “Decomposing a Splice” on page 499)
• Convert a butt splice to a center strip splice (see “Converting a Butt Splice to a Center
Strip Splice” on page 501)
• Convert a center strip splice to a butt splice (see “Converting a Center Strip Splice to a
Butt Splice” on page 502)
Creating a Splice
When you synthesize wiring for logical signals, butt splices may be added to the design. You
may want to create more butt splices manually. Butt splices can be converted to center strip
splices and vice versa.
Procedure
1. In the Design Browser (Design tab), click on the wire on which you want to create a butt
splice, press Space Bar and enter Splice. Alternatively, right-click on the wire and select
Add Splice.

February 2016
Wiring
Moving a Splice
2. The cursor changes to a splice symbol. If you place a cursor over a point in the diagram
where a splice cannot be created, the symbol has a diagonal line across it.
Click on the point in the diagram where you want to create a butt splice.
Results
• The splice is added to the diagram and to the Design Browser (Design tab).
• When the butt splice is created, wires will be split to become two wires.
• New wires are created accordingly and are added to the Design Browser (Design tab).
Related Topics
Moving a Splice
Merging Two Splices
Converting a Multiple Termination to a Splice
Decomposing a Splice
Converting a Butt Splice to a Center Strip Splice
Converting a Center Strip Splice to a Butt Splice
Moving a Splice
After synthesizing wiring and creating splices, you can move splices.
You can see the location of a splice in a diagram by clicking on it in the Design Browser
(Design tab). The splice is then displayed in red in the diagram.
As well as moving a splice to a new location, you can use the Move Splice function to merge
two splices that are on the same harness and are associated with the same signal. Note that a
pigtail splice cannot be merged with another splice.
Procedure
1. Right-click on the splice in the Design Browser (Design tab) and select Move Splice.
Alternatively, click on the splice in the Design Browser (Design tab), press Space Bar
and enter Move.
Note
You can perform this action to move a splice to the currently open diagram from
another diagram.
2. Move the mouse cursor to the location where you want to place the splice and click
once. The system automatically calculates the offset required as you move the splice to
another point in the diagram and displays this offset by the cursor.

February 2016
Wiring
Moving a Splice
A splice can be moved to:

• Another point on the harness
The cursor changes to a splice with a line through it when positioned where the
splice cannot be placed. When positioned where the splice can be placed, the cursor
is a black splice symbol .
• A slot connector where it is converted into a multiple termination

If you position the cursor over a slot connector, the cursor changes to a multiple
termination symbol . If you place the splice here, it changes to a multiple
termination and the splice is removed from the Design Browser (Design tab). It is
possible to change a multiple termination to a splice. See “Converting a Multiple
Termination to a Splice” on page 500 for more information.
• A slot
If you position the cursor over a slot, the cursor changes to a splice symbol in a box
. If you place the splice in a slot, the pin map for the slot is updated accordingly.
• A point across one inline pair to a harness that is connected directly adjacent to
the harness from where the splice is being moved
If you move the splice across an inline pair, the splice moves in the Design Browser
(Design tab) to be under the harness on which it is now located. In addition, any
required wires are created and necessary cavities are added to the inline pair.
Note
If you want to move the splice across more than one inline pair, hold down the
SHIFT key on your keyboard when you select the Move Splice option. You can
then repeat the action of moving the splice across an inline pair. When you have
finished moving the splice across inline pairs, press the Esc key on your keyboard.
Related Topics
Creating a Splice
Merging Two Splices

February 2016
Wiring
Merging Two Splices
Merging Two Splices

As well as moving a splice to a new location, you can use the Move Splice function to merge
two splices that are on the same harness and are associated with the same signal. Note that a
pigtail splice cannot be merged with another splice.
Procedure
1. Right-click on the splice that you want to move in the Design Browser (Design tab) and
select Move Splice. Alternatively, click on the splice in the Design Browser (Design
tab), press Space Bar and enter Move.
2. In the diagram, move the mouse cursor over the splice with which you want to merge the
first splice and click once. A message is displayed asking you if you want to merge the
two splices. Click Yes to merge them. If you click No, the splice is moved to the
position as in a normal Move Splice action.
Results
The splices are merged in the Design Browser (Design tab) and the merged splice has the name
of the splice that has moved.
Related Topics
Creating a Splice
Moving a Splice
The Decompose Splice function allows you to split a splice into two and to position the newly
created splice in a different location.
Procedure
1. Right-click the splice in the diagram or in the Design Browser (Design tab) and select
Decompose Splice. Alternatively, click on the splice in the Design Browser (Design
tab), press Space Bar and enter Decompose.
2. The Decompose Splice facility displays the wires in the splice. Select the wires that you
want to move to a new splice and click the Add button. If you want to move all of the
wires to the new splice, click the Add All button.

February 2016
Wiring
3. The wires are added to the New Splice Wires box. You can remove any wires from that
box, by selecting them and clicking the Remove button. Click the OK button to exit the
facility.
4. The cursor changes to a splice symbol. Move the cursor to the position where you want
to place the new splice and click once. See “Moving a Splice” on page 497 for more
information about moving a splice.
Results
The new splice is added to the diagram and to the Design Browser (Design tab) and any
necessary wires are created.
Related Topics
Creating a Splice
Moving a Splice

You can convert a multiple termination to a splice.
Procedure
1. Right-click on the cavity where the multiple termination is located in the Design
Browser (Design tab) Tree and select the Add Splice at Cavity option from the pop-up
menu. Alternatively, select the cavity, press Space Bar and enter Splice at Cavity.
2. The cursor changes to a black splice symbol . Position the cursor over the point on
the diagram where you want the splice to be created and click. If you position the cursor
over a location where the splice cannot be created, the cursor is a splice symbol with a
line through it .
Results
The splice is added to the diagram and to the Design Browser (Design tab) and a wire is added
between the splice and the cavity where the multiple termination was located.
Related Topics
Creating a Splice
Moving a Splice

February 2016
Wiring
Automatically Converting Butt Splices to Center Strip Splices
Automatically Converting Butt Splices to

Center Strip Splices
You can convert butt splices to center strip splices automatically when the Generate center-
strip Splices constraint has been set for objects on a design.
Note
Wiring synthesis creates butt splices so this action is performed after wiring has been
synthesized. Center strip wires are selected automatically from the wires connected to each
butt splice. By default, the system tries to use wires that are in the maximum number of harness
levels, contain the largest number of splices and are as long as possible. Butt splices in slots and
shield signals are ignored by this action.
Procedure
1. With the design open, press Space Bar and enter Generate Center-Strip Splice.
The Generate Center-Strip Splices dialog box displays a progress bar.
2. When the conversion is complete, click Close.
Results
• In the Design Browser (Design tab), the center strip wires have the icon and the
center strip splices have the icon .
• The Synthesis tab in the Output Window lists the converted splices.
Related Topics
Creating a Splice
Moving a Splice
Converting a Butt Splice to a Center Strip

Splice
If a butt splice does not use a symbol, you can convert it to a center strip splice.

February 2016
Wiring
When splices are created manually or automatically during wiring synthesis, they are butt
splices by default. Butt splices are indicated by the butt splice icon in the design browser
(Design tab).
Procedure
In the Design Browser Window, select the two wires that you want to make the center strip in
the splice, press Space Bar and enter Convert to Center Stripped.
Results
• The wires become one wire that has the name of the first wire that you selected and has
the center strip wire icon next to it.
• The splice is now center-stripped and has the center strip splice icon in the Design
Related Topics
Creating a Splice
Moving a Splice
Converting a Center Strip Splice to a Butt

Splice
You can manually convert a center strip splice to a butt splice.
Procedure
In the Design Browser (Design tab), select the center strip wire that you want to split and the
splice.
Note
In the Design Browser (Design tab), center strip wires have the center strip wire icon
next to them and center strip splices have a center strip splice icon next to them.
Press Space Bar and enter Convert to Splice Terminated.

Results
A new wire is added to the Design Browser (Design tab) and the splice is converted to a butt
splice. The butt splice icon is displayed next to it.

February 2016
Wiring
Creating a Multicore
Related Topics
Creating a Splice
Moving a Splice
Creating a Multicore
The Multicores facility enables you to create multicores manually in a Capital Integrator design
and to edit these multicores. The multicores can contain only wires and multicores from a single
harness.
Note
Before you can create multicores, you must have synthesized wiring. See “Synthesizing
Wiring” on page 440.
Procedure
1. Select the harness (in which you want to create a multicore) in the Design Browser
(Design tab), press Space Bar and enter Multicores. Alternatively, right-click on the
harness and select Multicores.
2. In the Multicores dialog box, click the New button on the right part of the dialog box.
3. In the Edit Multicore dialog box, name the new multicore and click the indicator types
that apply to the multicore. Coax and oval multicores are shielded. Twist-commercial,
twist-military and twist-z are not shielded.
If you do not want to use the name that the system uses by default, uncheck the Default
Name box and enter a new name in the Name box.
Click OK to close the New Multicore dialog box.
4. On the Multicores facility, the multicore is added to the Selected box. It has the
appropriate indicator displayed below it. Click on the multicore in the Selected column
to make it active, and click on a wire or multicore in the Available column to select it.
Click Add to put the wire or multicore into the selected multicore.
5. Click OK to accept your changes.
Results
The multicore is added to a Multicores folder under the harness in the Design Browser (Design
tab). The wires in the multicore are listed under it.

February 2016
Wiring
Note
You can assign a part number from Capital Library to a multicore. See “Assigning a Library
Part to an Object” on page 274.

After wire routing has taken place, actions that update the length of a bundle also automatically
update wire lengths.
These actions include:
• Adding/moving a wire
• Adding/removing an inline pair
• Synthesizing wiring
• Adding/removing a splice
• Combining/splitting wire segments
• Importing a harness
• Replacing a wire when editing the topology
• Converting a multiterm to a splice
• Converting a splice to a multiterm
• Moving a splice into a slot
• Terminating a shield
• Editing a wire path
• Converting a butt splice to a center strip splice
• Bridging in data
• Moving a pin on a a slot
• Any action that moves/stretches a bundle
• Changing wire paths in a Signal Map dialog box
You can manually update all wire lengths and you may want to do this before transferring the
project to another application that will use them.
Procedure
Press Space Bar and enter Update All Lengths; the wire lengths are updated.

February 2016
Wiring
Modifying a Shield Termination
Modifying a Shield Termination

After wiring synthesis, you can edit the shield termination or backshell termination of a shield
multicore. You can also change whether it connects to a connector using a pigtail splice and
wire or whether the shield connects directly into the connector.
Normally, the non-pigtail scenario creates a cut-end connection that consists of a splice
connected to nothing. In the case of a backshell, the non-pigtail scenario creates a direct
connection to the cavity rather than a cut-end.
During wiring synthesis, the termination is added to a Multicores folder under the relevant
harness folder in the Design Browser (Design tab).
Procedure
1. Click on the shield termination in the Design Browser (Design tab), press Space Bar and
enter Edit Shield Termination. Alternatively, right-click on the shield termination and
select Edit Shield Termination from the menu.
2. The Edit Shield Termination dialog box is displayed.
This displays the name of the shield termination, whether an end is a cut-end (that does
not terminate at a connector) or whether an end terminates in a connector, and whether it
is a backshell termination. By default, an end that terminates in a connector is a pigtail
(that is, the shield connects to a splice and a wire connects the splice and the connector).
3. If you want to use a pigtail where the shield connects to a connector, check the Use
Pigtail box. This is the default setting.
If you do not want to use a pigtail and you want the shield to connect directly with the
connector, uncheck the Use Pigtail box.
4. Click OK to exit the facility. If you have unchecked a Use Pigtail box, the
corresponding pigtail splice and wire are deleted.
Related Topics
Synthesizing Wiring
Copying Wiring Across the Levels of a

Harness
When you have synthesized the wiring for a max-complexity harness, you may want to
synthesize the wiring for a simpler derivative harness whose components are all contained
within the max-complexity harness. A harness can have a different active level in a derivative to
the active level that it had in the max-complexity harness. You can copy the wiring for this
harness from the harness level in the max-complexity diagram to the harness level in the

February 2016
Wiring
Depopulating Wiring from Active Harness Levels
derivative. This will work because the max-complexity harness contains all the wiring needed
for the simpler derivative.
However, the max-complexity harness may also contain additional wires that are not needed in
the simpler derivative. You can remove these wires from the harness level for the harness in the
simpler derivative by using the depopulate function (see “Depopulating Wiring from Active
Harness Levels” on page 506).
Procedure
1. Right-click on the harness in the Design Browser (Design tab) and select Copy Wiring
by Levels. Alternatively, click on the harness in the Design Browser (Design tab), press
Space Bar and enter Copy Wiring by Levels.
2. A table showing the levels for the harness is displayed. Click on the level from which
you want to copy wiring and click the Set Target Levels button.
3. A list of Available target levels is displayed. Select the level to which you want to copy
the wiring and click the Add button. You can copy to multiple levels at once. Click the
Add All button to copy to all other levels for the harness. Click the Close button.
Note
You can remove a level from the Included column by selecting it and clicking the
Remove button.
4. The target levels are displayed in the Target Levels box. Click the OK button.
Results
Any Partly Routed signals that are now routed move into the Routed folder in the Design
Related Topics
Depopulating Wiring from Active Harness Levels
Depopulating Wiring from Active Harness

Levels
When wiring is copied from one harness level to another, this can result in there being
unnecessary wires and splices in the routing for a harness level. The Depopulate Wiring
function allows you to remove unnecessary wiring from the currently active harness levels.
Procedure
1. Set the harness levels that you want to depopulate to active. You can do this either by
setting the active harness level for each individual harness (see “Active Harness Level”

February 2016
Wiring
Editing Ground Signals
on page 358) or by setting a vehicle configuration to active (see “Setting an Active

Vehicle Configuration” on page 368).
2. Press Space Bar and enter Depopulate Wiring.
3. A list of wires and splices that the system considers unnecessary are displayed.
Note
If there are no wires that the system considers unnecessary, a message is displayed
indicating that there is nothing to do.
All ground-to-ground connections made using the Add Wire facility will be listed in the
Depopulate Wiring dialog box because they are surplus to the wiring required by the
functional data. If you depopulate all wiring (from all levels) of a ground-connecting
signal, this deletes the signal as well.
Check the Depop box for the wires and splices that you want to remove and click the
OK button.
Related Topics
Copying Wiring Across the Levels of a Harness

Before you create wires, you can add ground signals to a design. This can be done when editing
a Capital Integrator design in single user mode only. You specify a name for a signal and the
cavities between which it flows.
After you have added a ground signal, you can use either wiring synthesis or the manual Add
Wire functionality to connect wires to the cavities to implement the ground signal.
Procedure
1. Press Space Bar and enter Export Wiring; the Edit Ground Signals Dialog Box is
displayed.
2. The Ground Signal window lists the existing ground signals. To add a ground signal to
the design, click the Add button below the Ground Signal window and specify the
signal name in the Signal Name dialog box that is displayed. Click the OK button to
exit that dialog box.
Note
You can delete or rename a ground signal by clicking on it in the Ground Signal
window and clicking the Delete button or Rename button.

February 2016
Wiring
Exporting Wiring from a Capital Integrator Design
3. The cavities between which it can flow are displayed in the Available Cavities window.
Keep the signals selected in the Ground Signals window and select the cavities between
which you want the ground signal to flow and click the Add button to the right of the
window to add them to the Selected Cavities window.
Note
You can remove cavities from the Selected Cavities window by clicking on them
and clicking the Remove button. To add all of the cavities to the Selected Cavities
window, click the Add All button. To remove all cavities from the Selected Cavities
window, click the Remove All button.
4. Click the OK button to save your changes and exit the dialog box.
Related Topics
Synthesizing Wiring
Adding a Wire
Exporting Wiring from a Capital Integrator

Design
You can export wiring from selected or all harnesses in a Capital Integrator design in X2ML
format so that it can be imported into another Capital Integrator design.
Note
The exported XML file contains data about wires, connectors, connector cavities, splices,
multicores and connector refinement. The connector refinement data includes specialized
connectors and connector mappings (between the generalized connector and specialized
connectors) but does not include bundle fanout data. That means, if you have defined a complex
bundle fanout topology or included bundle lengths, that data will not be exported.
Procedure
1. Open the diagram for the Capital Integrator design.
2. Select the File > Export Wiring menu.
The Harness Selection Dialog Box is displayed.
3. Select the harnesses for which you want to export wiring.
4. Click OK.
The Export Wiring Data dialog box is displayed.

February 2016
Wiring
Importing Wiring into a Capital Integrator Design
Note
To export the wiring for all harness levels, select the All Harness Levels option. To
export wiring for just the active harness levels, ensure the All Harness Levels
option is unselected.
6. Click Export.
Related Topics
Importing Wiring into a Capital Integrator

Design
You can import wiring that has been exported from selected or all harnesses from a Capital
Integrator design in X2ML format (an XML file) into another Capital Integrator design.
Caution
You cannot import wiring data XML from a Capital version prior to v2010.1.
The exported XML file contains data about wires, connectors, connector cavities, splices,
multicores and connector refinement.
The connector refinement data includes specialized connectors and connector mappings
(between the generalized connector and specialized connectors) but does not include bundle
fanout data. That means, the import data does not include data about complex bundle fanout
topologies or bundle lengths.
Prerequisites
• Capital Logic designs must be associated with the Capital Integrator design. See
“Associating Logical Designs with the Topological Design” on page 37.
• All devices in the design should be placed in slots. See “Placement of a Device or
Ground Device in a Slot” on page 174. If they are not, wires will connect to slots only
when relevant devices are placed already.
• At least one harness level must be defined for each harness. See “Harness Level” on
page 352.
• The X2ML data in the XML file must contain wiring information that has been created
for the specific Capital Integrator design into which you are importing it.
• Signal names and connectors defined in the X2ML data must match those in the Capital
Integrator design.

February 2016
Wiring
Editing the Module Code for a Wire, Shield or Multicore
Caution
When you perform the import, any existing wires in harnesses that are selected for
import are deleted in the design and are replaced with the imported wiring.
Procedure
1. Open the diagram for the Capital Integrator design into which you want to import the
wiring.
2. Press Space Bar and enter Import Wiring.
The Harness Selection Dialog Box is displayed.
3. Select the harnesses for which you want to import wiring.
4. Click OK.
The Import Wiring Data dialog box is displayed.
5. Navigate to the XML file containing the wiring and click Import.
If there are harnesses with no harness levels in the design, a warning message is
displayed and you confirm whether you want to continue or not.
6. The Import Wiring tab in the Output Window informs you whether the import was
successful or not and whether there were any errors.
Results
After importing the wiring, you can:
• run design rule checks to identify any violations of design rules.
• make manual changes to the wiring
• use Capital AutoView Assist for Integrator to generate Capital Logic wiring diagrams.
See “Capital AutoView Assist for Integrator” on page 551.
Related Topics
Design Rule Checks
Editing the Module Code for a Wire, Shield or

Multicore
You can specify or edit the module code for a wire, shield or multicore in a Capital Integrator
design.

February 2016
Wiring
Editing the Module Code for a Wire, Shield or Multicore
Procedure
1. Select the wire, shield or multicore in the Design Browser (Design tab).
2. Either:
• Press Space Bar and enter Properties.
• Right-click on the object and select Properties.
The Edit Properties Dialog Box is displayed.
3. In the Configuration section on the General tab, specify the module code in the
Module field. Click the ellipsis (...) to select a pre-defined module code.
Note
If you have run composite wiring synthesis with Generate Option Expressions
selected, a module code will have been generated for a wire or shield. Module codes
for multicores must be edited manually in the Module Code field.
4. Click OK.

February 2016
Wiring
Routed States of Signals

You can use the Design Assistant to calculate the routed state of signals (signal states).
See “Design Assistant” on page 645 for more information about it.
The following states are possible:
• Unmapped
One or more device pins are not mapped to a slot connector cavity. Signals may not be
fully mapped if a cavity on a slot connector has been deleted and this has left a
functional device pin not mapped to a cavity.
Figure 18-20. Unmapped Signal State
• Internal
Signals that are completely internal to a slot, not mapped to any cavities.
Figure 18-21. Internal Signal State
• Unconnected
The signal has zero or one active pin and therefore no wiring is required.

February 2016
Wiring
Figure 18-22. Unconnected Signal State
• Unrouted
The signal has two or more active pins, but no wiring exists for it.
Figure 18-23. Unrouted Signal State
• Partially Routed
Has some wiring, but not all active device pins are connected.
Figure 18-24. Partially Routed Signal State
• Routed

February 2016
Wiring
Calculating the Routed State of Signals
All active pins to which this signal connects have valid wiring which connects them all
together.
Figure 18-25. Routed Signal State
Calculating the Routed State of Signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Calculating the Routed State of Signals

You can use the Signal Route State Calculator in the Design Assistant to calculate the route
state of signals (routed, unrouted, unconnected, and so on).
Prerequisites
Assistant.
Procedure
1. If you want to calculate the routed state of selected signals, select them in the Design
2. In the Design Assistant, set the scope of the calculations using the toggles:
• None / Active Levels / Persisted Configurations / All Configurations
• Entire Design / Selected Signals

February 2016
Wiring
Preserving Wiring during Topology Edits
3. Click the Run the Design Assistant’s Checks ( ) button; the results of the calculations
are displayed in the Design Assistant Output Table.
Related Topics

You can make changes to a design’s topology while preserving any wiring that has been
synthesized and edited.
Changes to the topology in a design can occur at various stages of a platform’s life-cycle, even
after wiring implementation has been determined and may have even been released.
In Capital Integrator, wires can only exist if they have a valid path through the topology.
Therefore, topology changes must be made in a way that controls and contains any wiring
changes in order to preserve as much of the wiring implementation as possible.
To do this, you switch into a Preserve Wiring mode.
Preserve Wiring Mode

In this mode:
• The system reports in the Output Window when a valid path no longer exists for a wire.
• If you have wires that no longer have valid path, the only available actions are those that
edit the topology (including via Bridges).
• Saving is not enabled.
• Wires with no valid paths are not deleted automatically. However, you can commit your
topology changes and delete the wires.
• When a new path is available for wire whose valid path had been deleted, the wire is re-
instated automatically.
As soon as you exit this mode, the system deletes any wires that are displayed in the Output
Window because they have no valid path.

February 2016
Wiring
Editing the Topology in Preserve Wiring Mode
Note
A wire will only be re-instated into the same harness from which it was removed. If a
harness name is changed during the topology edits (for example, by adding "_split"),
preserved wires will not be re-instated until you manually rename the harness. Messages in the
Design Assistant (in Preserve Wiring Mode) indicate the name of the harness from which each
wire was removed. When rejoining harnesses split due to topology modifications, adding a
bundle from a stub on the split harness (whether an _split or a newly named harness, for
example, H32) to the remaining section of correctly named harness results in a single harness
with the original, correct name.
Related Topics

You can make topology edits in a design in preserve wiring mode.
Prerequisites
• Wiring must have been synthesized. See “Synthesizing Wiring” on page 440.
Procedure
1. Click the Automatically preserve wiring ( ) button on the Status Bar at the bottom
of the application so that it looks like ; the system enters Preserve Wiring Mode so
preserves any wires with no valid path from now on.
2. Edit the topology as required.
If an edit results in a wire no longer having a valid route or an unplaced splice:
• Capital Integrator switches into Topology Edit mode and only actions applicable for
editing topology (not wiring) are available.
• The Design Assistant (in Preserve Wiring Mode) is displayed in the Output
Window. It lists any wires that no longer have a valid route and any unplaced
splices.
3. Continue editing the topology as required. The list of wires with no valid path and
unplaced splices updates in the Topology Edits tab accordingly.

February 2016
Wiring
Troubleshooting Wiring Synthesis Output
Note
If there are unplaced splices, you may need to place them manually; a hyper-link is
displayed in the Design Assistant to enable moving or placing the splice. If there are
wires with no valid paths and you want to delete them, click the Commit current
changes button () on the Design Assistant (in Preserve Wiring Mode). When all wires
have a valid path, the Design Assistant changes to its normal appearance.
4. If you are making significant changes to the topology, you may want to stop preserving
the existing wiring. To stop the system from preserving wiring without a valid path,
click the Automatically preserve wiring ( ) button on the Status Bar at the bottom of
the application so that it looks like ; the system no longer preserves any wires with
no valid paths.
Note
A wire will only be re-instated into the same harness from which it was removed. If
a harness name is changed during the topology edits (for example, by adding
"_split"), preserved wires will not be re-instated until you manually rename the harness.
Messages in the Design Assistant indicate the name of the harness from which each wire
was removed. When rejoining harnesses split due to topology modifications, adding a
bundle from a stub on the split harness (whether an _split or a newly named harness, for
example, H32) to the remaining section of correctly named harness results in a single
harness with the original, correct name.
Results
• Wires with a new valid path are re-routed and connected to pins accordingly.
• Wire lengths are recalculated.
• If a signal has been removed though the deletion of an interface connector, the wiring
for that signal is deleted.
• All editing actions are available again.
Related Topics

When wiring synthesis has run, the Synthesis tab in the output window at the bottom of the
application reports on the synthesis actions and signals that have failed to route. For a failed
signal, you can click the Details link to view the reasons why it failed to route. When you click
the link, the details are displayed on the Signal Details tab in the Output Window.

February 2016
Wiring
You can click Save detailed failure report to access the Select Output File dialog box that
enables you to save a report detailing failed signals and the reasons why they failed to route.
You can save the report in CSV (comma-separated values) or HTML format.
Each pane also has a pop-up menu, accessible with a right mouse button click, that contains text
manipulation commands (Select All, Copy, and Clear).
Note
You can also use the Design Assistant to calculate the routed state of signals (signal states)
or can generate a wiring view of a synthesized signal (see “Generating a Wiring View of a
Synthesized Signal or Multicore” on page 476). However, the Synthesis tab remains the
primary source of messages to understand synthesis failure.
What Causes a Signal Not to Synthesize Wiring?

There are various possible causes of a signal not synthesizing.
• System thinks no synthesis is required

• No route is available
• No synthesis solution is possible
System Thinks No Synthesis Is Required
This occurs when there are fewer than two active device pins for the signal. This situation is
typically identified when you expect some wiring but find it is missing. This is not considered
an error and therefore does not normally result in warning or error messages on the Synthesis
tab in the Output Window.
Causes
• Unmapped Device Pins

February 2016
Wiring
All device pins must be mapped to a slot connector cavity. For example:
Figure 18-26. Signal Map Showing Unmapped Pin
• Inactive Device Pins

A pin must be active in at least one harness level. If it is not, this can be caused by:
o Missing option on harness family
You can use the Design Assistant to investigate this. See “Reporting on Missing or
Inconsistent Options Promoted to Harnesses” on page 455.
o Conflict between effective device pin option expression and harness levels
This normally requires you to manually check the option expressions on device pins
and harness levels. The Design Assistant reports if a pin is never active when you
calculate the routed state of signals.
The conflict may also be on another harness family. You can use an Options and
Levels report to identify harness families to check. See “Creating an Options and
Levels Report” on page 421.
Messages Displayed when System Thinks No Synthesis Is Required
The application can display various messages.
Table 18-1. Messages Displayed When No Synthesis is Required

Synthesis Tab in Output Window Design Assistant Messages
None (not a synthesis error) Harness is missing option

February 2016
Wiring
Table 18-1. Messages Displayed When No Synthesis is Required (cont.)

Option not referenced in any levels
Unmapped in slot
Connects to cavity which is never active
Steps to Identify Issues
1. Use the Design Assistant to run design rule checks to identify options not referenced by
any harness levels and options that should be promoted from placed devices. See
“Running Design Rule Checks in the Design Assistant” on page 73.
2. Use the Design Assistant to run a signal status check on all configurations to identify
unmapped device pins as well as pins that are never active. See “Calculating the Routed
State of Signals” on page 514.
3. If a pin is never active, calculate its effective option expression by combining
expressions from the device pin, the device, the net and variant placement of the device
(if any).
Examine harness level definitions to ensure this option expression is supported by at
least one harness level.
Note
It may be necessary to consider other harness family level definitions. For example,
if the effective option expression of the device pin is (LHD && ABS), you will need
to ensure that every harness family that supports both these options has at least one
harness level that has them both active.
No Route Is Available
In this case, the system cannot find an available path between all active device pins. Typically,
this is reported during synthesis, but requires investigation to determine the exact cause.
Causes
All of these causes are reported on the Synthesis tab of the Output Window when synthesis is
run.
• No physical path between harnesses

February 2016
Wiring
For example:
Figure 18-27. No Physical Path Between Harnesses
This can also be caused by a multi-harness slot with the correct signal mapping.
• Path broken by optioned bundles

February 2016
Wiring
Can be debugged using graphical filtering. For example:

Figure 18-28. Path Broken by Optioned Bundles
• Path broken by inlines with no available cavities

This can only occur if part numbers have been assigned to the inline pair and can be
caused by incorrect Preferred Signal settings in the Signal Map for the inline pair.

February 2016
Wiring
Figure 18-29. Path Broken by Inlines with no Available Cavities
• Path broken by routing constraints

February 2016
Wiring
Figure 18-30. Path Broken by Routing Constraints
Messages Displayed when No Route Is Available

The system can display various messages.
Table 18-2. Messages Displayed When No Route Is Available

Harness is not physically connected Partially routed due to unconnected groups
Disconnect due to no available cavities
Disconnect due to option expression
Disconnect due to routing/splice constraint

1. View the Synthesis tab of the Output Window at the bottom of the application to
identify the possible issues. Note that you could also use the Design Assistant to run a
signal status report (see “Calculating the Routed State of Signals” on page 514).
2. If a harness is not physically connected:
a. Check slots and inlines that appear to provide a connection.
b. Check for errors in signal mapping in multi-harness slots.

February 2016
Wiring
c. Check for disconnects in the topology. Disconnects can be identified using the
Unterminated Bundle design rule check or by unexpected harness names in the
browser list.
3. If several disconnects are identified, some of them may be expected. Set all harness
levels as active and then select the signal in the Design Browser (Design tab) so that it is
highlighted in the diagram window. Identify slots that need to be connected together and
identify the expected routing paths. If the signal is partially routed, you can use the
groups of wiring reported by the Design Assistant to identify where there is a gap in the
expected route.
4. Work through any disconnects reported on the Synthesis tab of the Output Window and
identify any that appear on the expected routing path.
No Synthesis Solution Is Possible
In this case, routing paths exist between the active device pins but the required wiring could not
be synthesized.
Causes
Consider the following:
• Are multi-terms allowed?

If multi-terms are disallowed (as below), the only mechanism to join wiring together is
splices.
Figure 18-31. Constraint Preventing Multi-terms
• Are splices allowed?

If splices are disallowed (as below), the only mechanism to join wiring together is multi-
terms. Note that splices can only be created along the path of a signal’s wires.

February 2016
Wiring
Figure 18-32. Constraints Preventing Splices
• Are bundles long enough to support the required number of splices?

Splice separation rules can stop a splice being created, especially when bundles are short
or have many takeouts.
Note that a rule for Maximum wires per splice can result in more splices needing extra
space.
Figure 18-33. Constraints Preventing Splices Due to Bundle Length
Messages Displayed when No Synthesis Solution Is Possible

The system can display various messages.

February 2016
Wiring
Top-Level Debugging Process for Synthesis
Table 18-3. Messages Displayed When No Synthesis Solution Is Possible

Constraints could not be met Partially routed due to unconnected groups

1. Set all harness levels as active and then select the signal in the Design Browser (Design
tab) so that it is highlighted in the diagram window. View the connected slots.
2. Look for a probable route and select a bundle where a splice might be expected.
If the signal is partially routed, you probably want to look at the bundles that already
have wires created. In order to finish the route, one or more of these wires will need to
be spliced or multi-termed.
3. View the bundle’s properties and view the Rules tab.
a. Click the Show Inherited button.
b. Look for wires per multi-term and wires per splice constraints.
c. If there are constraints that completely restrict splice and multi-term creation,
consider whether any splices/multi-terms are possible anywhere in the design.
d. Look at the Rules and Constraints report for the diagram and determine whether
these constraints apply to the whole design or whether there are some places in the
design where splices/multi-terms can be created. See “Creating an Applied
Constraints Report” on page 434.
If a splice cannot be created in any of the harnesses joining the slots on a signal,
synthesis will probably fail (because it only considers adding splices along the path
of an existing wire).
4. If the constraints restricting splice and multi-term creation appear correct and splices can
be created in the design, repeat the above looking for splice separation constraints.
Consider the splice separation that is required and therefore the minimum length of a
bundle required to create a splice. If all the bundles in the area where a splice is required
are too short, synthesis will fail.
Related Topics

The following diagram shows the top-level debugging process for wiring synthesis results.

February 2016
Wiring
Figure 18-34. Top-Level Debugging Process for Synthesis
Further details are available for the following debugging processes:
• No Synthesis Required Debugging Process

No Synthesis Required Debugging Process

The following diagram shows the process.

February 2016
Wiring
Figure 18-35. No Synthesis Required Debugging Process
No Route Available Debugging Process


February 2016
Wiring
Figure 18-36. No Route Available Debugging Process
No Synthesis Solution Debugging Process

Figure 18-37. No Synthesis Solution Debugging Process

February 2016
Wiring
Related Topics

February 2016
Wiring

February 2016
Chapter 19
Printing
The Capital Design Tools - Common Functions User Guide contains full details of the options
available for configuring Projects, Designs, Print Regions and Diagrams for Printing and
Printing to a File.
Available Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 533
Available Topics
The following topics are available.
Printing
These topics detail 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 to a File
These topics detail how Print to File can export the design data from one or more diagrams to
either PDF, DXF, CGM or SVG format.
Using Print Regions
These topics detail how to add print regions to a design, with additional topics on resizing,
moving and editing print regions once created:
Printing Dialog Boxes
This section offers a description of all dialog boxes related to printing functions. For each dialog
box, all fields are listed, along with a full description of the field’s function.

February 2016
Printing
Available Topics

February 2016
Chapter 20
Graphics
The following topics explain how to add and edit graphical shapes and graphical objects in a
diagram.
Borders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Replacing a Border on a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Graphic Drawing Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Drawing a Rectangle in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Drawing a Circle in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Drawing an Arc in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Drawing a Curved Line in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Adding Text Frames to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Changing the Picture in an Image Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Adding a Comment Symbol to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Resizing a Comment Symbol in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Adding Properties to a Graphical Shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Editing a Property Value of Graphical Shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Editing the Graphical Properties of a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Controlling the Layering Order (Z-Order) of Graphical Shapes and Objects . . . . . . . . . . 542
Graphics Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Adding a Graphics Point to a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Grip Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Adding a Grip Point to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Deleting a Grip Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545

February 2016
Graphics
Borders
Borders
The following topics explain how to add and edit the border in a diagram. Borders are created in
Capital Symbol.
Replacing a Border on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Adding a Border to a Diagram

You can add a border that has been created in Capital Symbol to a diagram.
Procedure
See Adding a Border to a Diagram in the Capital Design Tools - Common Functions User
Guide.
Related Topics
Replacing a Border on a Diagram
Removing a Border from a Diagram

You can replace a border that has been added to a diagram.
Procedure
See Replacing a Border on a Diagram in the Capital Design Tools - Common Functions User
Guide.
Related Topics

You can remove a border that has been added to a diagram.
Procedure
See Removing a Border from a Diagram in the Capital Design Tools - Common Functions User
Guide.

February 2016
Graphics
Related Topics

February 2016
Graphics
Graphic Drawing Tools
Graphic Drawing Tools

You can add and edit non-intelligent, graphical shapes and text in a diagram. These design
objects are considered comments and do not represent any electrical connectivity.
Drawing a Rectangle in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538
Drawing a Circle in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Drawing an Arc in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Drawing a Curved Line in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Adding Text Frames to a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Changing the Picture in an Image Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Adding a Comment Symbol to a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 540
Resizing a Comment Symbol in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Adding Properties to a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Editing a Property Value of Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Editing the Graphical Properties of a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . 541
Controlling the Layering Order (Z-Order) of Graphical Shapes and Objects . . . . . . . 542
Drawing a Line in a Diagram

You can use the drawing tools to add a line to a diagram.
Procedure
See Drawing a Line in a Diagram in the Capital Design Tools - Common Functions User Guide.
Drawing a Rectangle in a Diagram

You can use the drawing tools to add a rectangle to a diagram.
Procedure
See Drawing a Rectangle in a Diagram in the Capital Design Tools - Common Functions User
Guide.

February 2016
Graphics
Drawing a Polygon in a Diagram
Drawing a Polygon in a Diagram

You can use the drawing tools to add a polygon to a diagram.
Procedure
See Drawing a Polygon in a Diagram in the Capital Design Tools - Common Functions User
Guide.
Drawing a Circle in a Diagram

You can use the drawing tools to add a circle to a diagram.
Procedure
See Drawing a Circle in a Diagram in the Capital Design Tools - Common Functions User
Guide.
Drawing an Arc in a Diagram

You can use the drawing tools to add an arc to a diagram.
Procedure
See Drawing an Arc in a Diagram in the Capital Design Tools - Common Functions User
Guide.
Drawing a Curved Line in a Diagram

You can use the drawing tools to add a curved line to a diagram.
Procedure
See Drawing a Curved Line in a Diagram in the Capital Design Tools - Common Functions
User Guide.
Adding Text Frames to a Diagram

You can use the drawing tools to add a text frame to a diagram.
Procedure
See Adding Text Frames to a Diagram in the Capital Design Tools - Common Functions User
Guide.

February 2016
Graphics
Adding a Picture to a Diagram

You can add a picture from an image file (with the extensions JPG, JPEG or GIF) to a diagram.
Note
To do this, the image file must be saved in the central image repository folder that has been
specified in the system preferences for Paths in Capital Project. The diagram saves only the
path to the image file (that is, it does not import the image) so it will lose the image if the file is
moved.
Procedure
See Adding a Picture to a Diagram in the Capital Design Tools - Common Functions User
Guide.
Related Topics
Changing the Picture in an Image Frame
Changing the Picture in an Image Frame

You can change the picture that is displayed in an image frame, created by the drawing tools.
Procedure
See Changing the Picture in an Image Frame in the Capital Design Tools - Common Functions
User Guide.
Related Topics
Adding a Comment Symbol to a Diagram

You can add a comment symbol, created in Capital Symbol, to a diagram and how to 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
See Adding a Comment Symbol to a Diagram in the Capital Design Tools - Common Functions
User Guide.
Related Topics
Resizing a Comment Symbol in a Diagram

February 2016
Graphics

You can resize (scale) an instance of a comment symbol in a diagram.
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 to redraw the symbol at the required scales.
Procedure
See Resizing a Comment Symbol in a Diagram in the Capital Design Tools - Common
Related Topics
Adding a Comment Symbol to a Diagram
Adding Properties to a Graphical Shape

You can add a property to a graphical shape, created by the drawing tools, so that the property
value is displayed on the diagram.
Procedure
See Adding Properties to a Graphical Shape in the Capital Design Tools - Common Functions
User Guide.
Editing a Property Value of Graphical Shape

You can edit a displayed property value of a graphical shape, created by the drawing tools.
Procedure
See Editing a Property Value of Graphical Shape in the Capital Design Tools - Common
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, created by the drawing tools.
Procedure
See Editing the Graphical Properties of a Graphical Shape in the Capital Design Tools -

February 2016
Graphics
Stretching a Graphical Shape
Stretching a Graphical Shape

You can stretch a graphical shape, created by the drawing tools.
Procedure
See Stretching a Graphical Shape in the Capital Design Tools - Common Functions User Guide.
Moving a Graphical Shape

You can move a graphical shape, created by the drawing tools.
Procedure
See Moving a Graphical Shape in the Capital Design Tools - Common Functions User Guide.
Deleting a Graphical Shape

You can remove a graphical shape, created by the drawing tools, from a diagram.
Procedure
See Deleting a Graphical Shape in the Capital Design Tools - Common Functions User Guide.
Controlling the Layering Order (Z-Order) of

Graphical Shapes and Objects
You can control the layering order (z-order) of overlapping graphical shapes and objects
(graphics, 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.

February 2016
Graphics
Controlling the Layering Order (Z-Order) of Graphical Shapes and Objects
Caution
Z-order settings for an object are lost if styling is applied to it, either manually or
automatically. If using z-order settings with conductors and symbols, ensure that you
apply the z-order to the symbol (for example, Bring To Front) and not to the conductor.
Prerequisites
• The graphical shapes must have been added to the diagram.
Procedure
In the diagram window, select one or more graphical shapes and either:
• right-click on 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.

February 2016
Graphics
Graphics Points
Graphics Points
A graphics point is a point at which 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544

Adding a Graphics Point to a Graphical Shape

You can add a graphics point to a line, polygon, or curved line, created by the drawing tools.
Procedure
See Adding a Graphics Point to a Graphical Shape in the Capital Design Tools - Common
Related Topics
Deleting a Graphics Point
Deleting a Graphics Point

You can delete a graphics point on a graphical shape in a diagram.
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.
Procedure
See Deleting a Graphics Point in the Capital Design Tools - Common Functions User Guide.
Related Topics
Adding a Graphics Point to a Graphical Shape

February 2016
Graphics
Grip Points
Grip Points
A grip point is point that you add to a wire, net or bundle. It divides the object into graphical
sections that can be resized and reshaped.
Adding a Grip Point to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Deleting a Grip Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Adding a Grip Point to an Object

You can add a grip point to an object.
Procedure
See Adding a Grip Point to an Object in the Capital Design Tools - Common Functions User
Guide.
Related Topics
Deleting a Grip Point

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
See Deleting a Grip Point in the Capital Design Tools - Common Functions User Guide.
Related Topics
Adding a Grip Point to an Object

February 2016
Graphics

February 2016
Chapter 21
Layout
The following topics explain how to perform layout-related actions.

Aligning Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Distributing Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Flipping Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 547
Rotating Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Defining Rotation Increments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Free Rotation of an Object or Comment Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 548
Pivoting Text about its Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Setting Snap To Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Setting Grid Defaults for a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Using Japanese Text on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549
Aligning Objects in a Diagram

You can align objects in a diagram.
See Aligning Objects in a Diagram in the Capital Design Tools - Common Functions User
Guide.
Distributing Objects in a Diagram

You can distribute objects in a diagram so that there is an equal distance between them.
You can distribute all objects apart from pins and indicators in a diagram window.
See Distributing Objects in a Diagram in the Capital Design Tools - Common Functions User
Guide.
Flipping Objects in a Diagram

You can flip objects horizontally or vertically about their centers in a diagram.
In Capital Integrator, you can flip:
• primitive graphical objects

February 2016
Layout
Rotating Objects in a Diagram
• comment symbols
• slots
• mated inline connector pairs
• unmated inline halves
• interface connectors
See Flipping Objects in a Diagram in the Capital Design Tools - Common Functions User
Guide.
Rotating Objects in a Diagram

You can rotate objects around their center point by increments of 90 degrees.
In Capital Integrator, you can rotate:
• primitive graphical objects

• comment symbols
• slots
• mated inline connector pairs
• unmated inline halves
• interface connectors
See Rotating Objects in a Diagram in the Capital Design Tools - Common Functions User
Guide.
Defining Rotation Increments

You can specify the major and minor rotation increments that are used in the free rotation of
primitive graphical objects and comment symbols around their center point.
See Defining Rotation Increments in the Capital Design Tools - Common Functions User
Guide.
Free Rotation of an Object or Comment

Symbol
You can freely rotate a primitive graphical object or comment symbol around its center point by
a pre-defined major or minor rotation increment.

February 2016
Layout
Pivoting Text about its Axis
See Free Rotation of an Object or Comment Symbol in the Capital Design Tools - Common
Pivoting Text about its Axis

You can pivot text about its axis from 0 degrees to 270 degrees and vice versa.
See Pivoting Text About its Axis in the Capital Design Tools - Common Functions User Guide.
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 disable it should you wish to position
objects close together, but not touching. The Snap To Object setting only affects comment
graphics.
See Setting Snap To Object in the Capital Design Tools - Common Functions User Guide.
Setting Grid Defaults for a Diagram

You can specify how grid points are displayed on a diagram.
See Setting Grid Defaults for a Diagram in the Capital Design Tools - Common Functions User
Guide.
Using Japanese Text on a Diagram

There are prerequisites for displaying Japanese fonts and characters in diagrams.
See Using Japanese Text on a Diagram in the Capital Design Tools - Common Functions User
Guide.

February 2016
Layout
Using Japanese Text on a Diagram

February 2016
Chapter 22
Capital AutoView Assist for Integrator
This chapter contains details of how to use Capital AutoView Assist for Integrator.
Capital AutoView Assist for Integrator Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551
Functionally Partitioned Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554
Functional Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Topology Led Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Generating a Topology-Led Wiring Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565
Translation of Objects When Generating Topology Led Diagrams . . . . . . . . . . . . . . . . . . 567
Custom Partitioned Wiring Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Overview of Flow for Custom Partitioned Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569
Generating Custom Partitioned Wiring Diagrams According to a User-Defined Property 572
Translation of Objects When Generating Partitioned Diagrams . . . . . . . . . . . . . . . . . . 576
Translation of Objects When Generating Diagrams Using Templates (Prototypes) . . 595
Generation of Slot Connectivity in Partitioned Diagrams . . . . . . . . . . . . . . . . . . . . . . . . 611
Distribution of Inlines By Home Condition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617

Overview
Capital AutoView Assist for Integrator (CAVAI) enables you to generate Capital Logic designs
containing wiring diagrams based on the wiring data for a vehicle configuration in a Capital
Integrator design.
You can generate diagrams for the wiring from multiple vehicle configurations. The generated
wiring diagrams contain all objects that are active in at least one of the vehicle configurations.
When selecting the vehicle configurations, you can restrict the objects that are rendered in the
generated diagrams by selecting particular Capital Logic designs. You can also select which
harnesses you want to be rendered in the generated diagrams.
Capital AutoView Assist for Integrator generates a diagram with symbols that have been used in
the Capital Integrator design.
You can modify the generated diagrams after they have been generated.

February 2016
Capital AutoView Assist for Integrator Overview
You can generate:
• one or more Capital Logic wiring diagrams based on the logical layout of the
connectivity in the Capital Logic functional designs that are associated with the Capital
Integrator design and on the wiring information from the Capital Integrator design. You
can generate either one design containing all of the diagrams or multiple designs
belonging to a new build list. See “Functionally Partitioned Diagrams” on page 554 and
“Translation of Objects When Generating Partitioned Diagrams” on page 576 for more
information about how Capital AutoView Assist for Integrator generates these
diagrams.
• a single Capital Logic wiring diagram based on the wiring information and bundle
layout from the Capital Integrator design. The wires will follow the routes of the bundles
in the Capital Integrator design. See “Topology Led Diagram” on page 565 and
“Translation of Objects When Generating Topology Led Diagrams” on page 567 for
more information about how Capital AutoView Assist for Integrator generates these
diagrams.
• a set of Capital Logic wiring diagrams that are partitioned according to a user-defined
property that has been set on the functional devices and pins in the associated Capital
Logic designs. The user-defined property values must be comma-separated lists of the
wiring designs on which the devices and pins must appear. See “Custom Partitioned
Wiring Diagrams” on page 569 and “Translation of Objects When Generating
Partitioned Diagrams” on page 576.
Use of Template (Prototype) Diagrams

You can use any existing wiring diagrams as templates for the layout of other wiring diagrams
that you generate using Capital AutoView Assist for Integrator. This means that instead of using
a functional layout as the template (which is what happens when associated functional designs
are used), you are using an existing wiring (physical) layout as the basis for the layout of
another wiring diagram.
See “Translation of Objects When Generating Diagrams Using Templates (Prototypes)” on

page 595 for more information.
Guided Layout
Guided layout, sometimes called net layout, refers to the way a schematic is created in the
generated wiring diagrams. In this case, the wiring follows the layout, or path, of nets in
template (prototype) functional diagrams.
If the templates do not contain nets that correspond to some of the wires, those additional wires
will not follow any guided layout from the functional design. Instead, point-to-point routing is
used.

February 2016
Capital AutoView Assist for Integrator Overview
Routing of Wires in Generated Diagrams

Capital AutoView Assist for Integrator will not route wires in the generated design if:
• The physical connectivity does not have a corresponding net conductor on an associated
functional design from Capital Logic.
• Physical connectivity is associated to net segments (of the same shared net) that are not
connected on a diagram.
• Physical connectivity corresponds to a single merged point on a functional net depiction.
Capital AutoView Assist for Integrator:
• Positions devices where they were located in the functional designs from Capital Logic
that have been associated with the Capital Integrator designs.
• Uses the locations of any name text from the functional designs.
• Uses the paths of signals from the functional designs but replaces the nets with
connectors and wires.
Related Topics
Functionally Partitioned Diagrams
Topology Led Diagram
Custom Partitioned Wiring Diagrams

February 2016

You can use Capital AutoView Assist for Integrator to generate one or more Capital Logic
wiring diagrams based on the logical layout of the connectivity in the Capital Logic functional
designs that are associated with the Capital Integrator design and on the wiring information
from the Capital Integrator design.
You can generate either one design containing all of the diagrams or multiple designs belonging
to a new build list (Generate Single Design option on the Design tab of the AutoView: Generate
Wiring Diagram Dialog Box).
Selecting “Generate Single Design” means that you generate just one design containing
multiple diagrams, one for each of the functional diagrams from Capital Logic that have been
associated with the Capital Integrator design. The layout of the generated diagrams is based on
the net layouts in the functional diagrams.
Not selecting “Generate Single Design” means that you generate multiple designs, one for each
of the associated Capital Logic designs. All of the generated designs are in a single new build
list and will contain the same number of diagrams as the matching Capital Logic design
(assuming no content has been filtered out). The layout of the generated diagrams is based on
the net layouts in the functional diagrams.
See the following table for an example of each of these scenarios:
Table 22-1. Example Project Structures when Generating Functionally-

Partitioned Diagrams
Example Project Description of Structure Screenshot of Structure
Structure
Initial project structure One Capital Integrator design
before generating (IntegratorDesign1)
wiring diagrams Two associated Capital Logic
designs:
Design1 with two functional
diagrams (Diagram1 and
Lights)
Design2 with one functional
diagram (Diagram1)

February 2016
Generating a Single Design with Partitioned Wiring Diagrams Based on the Layout of Functional
Table 22-1. Example Project Structures when Generating Functionally-

Partitioned Diagrams (cont.)
Example Project Description of Structure Screenshot of Structure
Structure
Project structure after New Capital Logic design
generating one design (IntegratorDesign1_rt1_1)
(Generate Single containing three wiring
Design selected) diagrams:
Design1:1-Diagram1
Design1:1-Lights
Design2:1-Diagram1
Project structure after New parent folder
generating multiple (GeneratedDesigns)
designs and saving containing two designs:
them in a parent folder Design1_WiringDesign with
called two wiring diagrams
GeneratedDesigns (Diagram1 and Lights)
(Generate Single Design2_WiringDesign with
Design unselected) one wiring diagram
Diagram1
Note
You can develop an extensibility plugin to control your own custom partitioning mode. 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.
Functional Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555
Generating a Build List with Partitioned Wiring Diagrams Based on the Layout of
Functional Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560
Generating a Single Design with Partitioned Wiring

Diagrams Based on the Layout of Functional
Diagrams
You can generate one design containing one or more Capital Logic wiring diagrams based on
the logical layout of the connectivity in the Capital Logic functional designs that are associated
with the Capital Integrator design and on the wiring information from the Capital Integrator
design.

February 2016
See “Translation of Objects When Generating Partitioned Diagrams” on page 576 for more
information about how Capital AutoView Assist for Integrator generates these diagrams.
Prerequisites
• You must have synthesized wiring in the Capital Integrator design. See “Synthesizing
Procedure
1. Right-click on the Capital Integrator design in the Project Browser Window and select
AutoView: Generate Wiring Diagram; the AutoView: Generate Wiring Diagram
2. From the drop-down list at the top of the dialog box, select Generate Functionally
Partitioned Diagrams.
3. On the Design tab, ensure that “Generate Single Design” is selected and specify the
following for the design that will be generated:
• Name
• Revision
• Release Level
• Parent Folder
• Style Set
4. On the Options tab (with “Generate Functionally Partitioned Diagrams” selected),
specify whether you want the wiring diagrams to include any “Slot Internal
Connectivity”.
5. Still on the Options tab (with “Generate Functionally Partitioned Diagrams” selected),
specify the following options for the diagram generation:
• Always Add Ground Paths
• Distribute Splices
• Pin and Device Name Retention (Displayed only if Slot Internal Connectivity setting
is None)
• Utilize Combined Devices (Displayed only if Slot Internal Connectivity setting is
Minimum or All)
• Property Retention (Displayed only if Slot Internal Connectivity setting is None)
• Merge Combined Device Properties (Displayed only if Slot Internal Connectivity
setting is Minimum or All)
• Hide Unconnected Pins and Connector Cavities

February 2016
Caution
If you are generating partitioned diagrams with a view to bridging out the wiring
data and importing it into a Capital Integrator design again, you should ensure
the following: - Hide Unconnected Pins And Connector Cavities on the Options
tab is not selected. This is so that cavities with no connected wires are generated in
the wiring diagrams. Otherwise, the result is different signal routings when the
wiring is imported back into a Capital Integrator design. Note also that connector
refinement is not supported by Capital AutoView Assist for Integrator when you are
using the specific flow in this caution.
• Use Refined Connectors

• Copy Graphics and Border from Prototype
• Strictly Use Prototype During Wiring Distribution
• Distribute Inlines By Home Condition
• Create Ported Wires where Functional Nets are Ported
• Multicore Indicator Offset
• Wire spacing
6. Click the Filter tab.
Caution
data and importing it into a Capital Integrator design again, you should ensure the
following: - All of the configurations are selected on the Filter tab so that no wiring is
lost when importing it back into a Capital Integrator design.
If vehicle configurations have been defined for the Capital Integrator design, the
Configuration field is displayed. Select the vehicle configurations for which you want to
generate the wiring diagram or diagrams. The generated wiring diagrams contain all
objects that are active in at least one of the vehicle configurations.
Note
The Diagram Partitioning button enables you to specify whether you want to
generate only one or multiple diagrams for each of the functional designs from
Capital Logic that have been associated with the Capital Integrator design. You also
specify how you want to partition the data in the diagrams (based on either
configurations or options). See “Diagram Partitioning Dialog Box” on page 797 for
more information.
7. In the Harness field, select the harnesses that you want to be rendered in the generated
wiring diagrams.

February 2016
The selection of particular harnesses means that Capital AutoView Assist for Integrator
renders the following in the generated diagrams:
• Conductors, connectors, multicores and splices that are active in the selected
configurations and that belong to the selected harnesses.
• Devices (and their pins) that are active in the selected configurations, that are not
integral to a harness and that are connected to at least one of the selected harnesses.
• Devices (and their pins) that are active in the selected configurations and that are
integral to the selected harnesses.
8. The Design field lists the Capital Logic designs that are associated with the topological
design. You can restrict the objects that are rendered in the generated wiring diagram by
selecting particular associated designs. By default, all designs are selected.
By selecting particular designs, you restrict the objects that are rendered in the generated
diagrams to the following:
• Devices (and their pins) that are active in the selected configurations and that have
functional sources in the selected Capital Logic designs
• Wires and splices that are active in the selected configurations and that belong to the
signals that have functional sources in the selected Capital Logic designs. This
includes signals that represent net equivalence sets with at least one functional
source in the selected functional designs.
• Multicores that include at least one conductor that is active in the selected
configurations and that belong to the signals that have functional sources in the
selected Capital Logic designs.
• Shields that are active in the selected configurations, belong to the signals that have
functional sources in the selected Capital Logic designs and that connect to
multicores rendered in the generated diagrams.
• Connector pins attached to the conductors that are rendered in the generated
diagrams.
• Connectors whose pins are rendered in the generated diagrams.
• Connector pins of the rendered connectors that have mated connector pins rendered
in the generated diagram.
• Backshells and backshell terminations.
9. If you have selected a “Slot Internal Connectivity” setting of Minimum or All, the Slot
Graphics tab is displayed. Edit the graphical properties for the objects created from
slot-internal connectivity as required. See “Specifying How an Object is Displayed
Graphically in a Diagram” on page 284 for more information about editing graphical
properties.

February 2016
10. If you have already used the Capital AutoView Assist for Integrator feature to generate
wiring diagrams for a Capital Integrator design in the project, the Prototype tab is
displayed. You can use a generated wiring diagram or build list as a template for a new
wiring diagram or build list of wiring diagrams. If you do not want to do this, skip to
step 11.
If you use a template, Capital AutoView Assist for Integrator uses the positioning of
objects and text annotations from it when generating new wiring diagrams. If the
template cannot provide positioning information for an object, the functional diagram
that is associated with the Capital Integrator diagram provides this information. In this
case, the wiring data from Capital Integrator is redistributed in the new wiring diagrams.
If a functional design exists and connectivity for the design exists but no graphical
diagrams exist for it, the wiring diagram connectivity is placed in a newly created wiring
design but no diagram graphics are generated.
See “Translation of Objects When Generating Diagrams Using Templates (Prototypes)”
Note
Template diagrams that were generated with a Generate Functionally Partitioned
Diagrams setting will give optimal results only if they are used to generate diagrams
with the same slot internal connectivity setting. That is, if a template diagram was
generated with the Minimum setting for Slot Internal Connectivity, it should be used
as a template diagram only when generating diagrams with the same setting. If a path in
the source Capital Integrator diagram is more complex than the reference path in the
template diagrams, Capital AutoView Assist for Integrator uses its own improved
algorithm to determine the layout of the path in the new diagram.
If you want to use a build list as a prototype, select the “Use Build List Prototype”
option (if it is displayed) and select the build list in the Build Lists field.
If you want to use a design as a prototype, unselect the “Use Build List Prototype”
option (if it is displayed) and select the diagram in the Prototypes field.
11. Click OK.
Results
• The new design and appropriate number of diagrams are generated and added to the
Project Browser Tree for Capital Logic.
• One diagram is opened automatically in a diagram window.
• The generated design is named using the Capital Integrator design name, the
configuration name and a unique suffix.
• If the wiring diagrams use the layouts of already existing functional diagrams from
Capital Logic, the wiring diagrams are given the same names as the functional diagrams.

February 2016
• A generated design has a Description property with a value that consists of the vehicle
configuration name, the vehicle model and the harness levels.
Related Topics
Diagrams
Translation of Objects When Generating Partitioned Diagrams
Generating a Build List with Partitioned Wiring

Diagrams Based on the Layout of Functional
Diagrams
You can generate multiple designs containing one or more Capital Logic wiring diagrams based
on the logical layout of the connectivity in the Capital Logic functional designs that are
associated with the Capital Integrator design and on the wiring information from the Capital
Integrator design.
The generated designs belong to a new build list. See “Translation of Objects When Generating
Partitioned Diagrams” on page 576 for more information about how Capital AutoView Assist
for Integrator generates these diagrams.
Prerequisites
Procedure
Dialog Box dialog box is displayed.
2. From the drop-down list at the top of the dialog box, select Generate Functionally
3. On the Design tab, ensure that “Generate Single Design” is not selected and specify the
following for the design that will be generated:
• Build List Name
• Release Level
• Design Name
• Revision
• Short Description

February 2016
• Release Level
• Abstraction
• Parent Folder
• Folder Name
• Style Set
4. On the Options tab (with “Generate Functionally Partitioned Diagrams” selected),
specify whether you want the wiring diagrams to include any “Slot Internal
Connectivity”.
5. Still on the Options tab (with “Generate Functionally Partitioned Diagrams” selected),
specify the following options for the diagram generation:
is None)
Minimum or All)
Caution

• Copy Graphics and Border from Prototype
• Strictly Use Prototype During Wiring Distribution
• Distribute Inlines By Home Condition
• Create Ported Wires where Functional Nets are Ported

February 2016

• Wire spacing
Caution
following: All of the configurations are selected on the Filter tab so that no wiring is lost
when importing it back into a Capital Integrator design.
Note
The Diagram Partitioning button enables you to specify whether you want to
generate only one or multiple diagrams for each of the functional designs from
Capital Logic that have been associated with the Capital Integrator design. You also
specify how you want to partition the data in the diagrams (based on either
configurations or options). See “Diagram Partitioning Dialog Box” on page 797 for
more information.
wiring diagrams.
functional sources in the selected Capital Logic designs.

February 2016
diagrams.
9. If you have selected a Slot Internal Connectivity setting of Minimum or All, the Slot
properties.
displayed. You can use a generated wiring diagram or build list as a template for a new
wiring diagram or build list of wiring diagrams. If you do not want to do this, skip to
step 11.

February 2016
Note
generated with the Minimum setting for “Slot Internal Connectivity”, it should be used
If you want to use a build list as a prototype, select the “Use Build List Prototype”
option and select the build list in the Build Lists field.
If you want to use a diagram as a prototype, unselect the “Use Build List Prototype” (if it
is displayed) and select the diagram in the Prototypes field.
11. Click OK.
Results
• The designs and appropriate number of diagrams are generated and added to the Project
Browser Tree for Capital Logic.
Related Topics
Functional Diagrams

February 2016

You can use Capital AutoView Assist for Integrator to generate a Capital Logic wiring design
based on wiring information and bundle layout from a Capital Integrator design. Each diagram
in the Capital Integrator design will result in a new diagram in the Capital Logic wiring design.
The wires will follow the routes of the bundles in the Capital Integrator design.
See “Translation of Objects When Generating Topology Led Diagrams” on page 567 for more
Generating a Topology-Led Wiring Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565

Translation of Objects When Generating Topology Led Diagrams . . . . . . . . . . . . . . . . 567
Generating a Topology-Led Wiring Diagram

You can generate a single Capital Logic wiring diagram based on the wiring information and
bundle layout from the Capital Integrator design. The wires will follow the routes of the bundles
in the Capital Integrator design.
See “Translation of Objects When Generating Topology Led Diagrams” on page 567 for more
Prerequisites
Procedure
Dialog Box dialog box is displayed.
2. From the drop-down list at the top of the dialog box, select Generate Topology Led
Diagram.
3. On the Design tab, specify the following for the design that will be generated:
• Name
• Revision
• Release Level
• Style Set
• Parent Folder

February 2016
4. On the Options tab (with “Generate Topology Led Diagram” selected), specify the
following options for the diagram generation:
• Use Logic Diagram Grid Spacing
• Minimum Wire Spacing
If no vehicle configurations have been defined for the Capital Integrator design, skip to
step 6.
wiring diagrams.

February 2016
Translation of Objects When Generating Topology Led Diagrams
diagrams.
8. Click OK.
Results
Related Topics
Translation of Objects When Generating Topology

Led Diagrams
When you use Capital AutoView Assist for Integrator to generate topology led wiring diagrams
in Capital Logic, objects are translated in various ways.
• Routing
o All wires follow the route paths that were created in the Capital Integrator design.
o Inline connectors are expanded to display all connections within and through
harnesses.
o Splices are displayed in the approximate location in which they exist in a bundle.
• Layout
o The wiring diagrams are scaled so that all of the connectivity can be displayed.
o Pins for slots can flip within a connector in order to reduce net overlap.

February 2016
o Connectivity that is internal to a slot is not displayed in the generated wiring

diagrams.
o Slots retain their relative position but may be adjusted to improve the wire routing.
o The shape of a slot may change to accommodate additional pins that are added to
display all connections.
o A splice shows all available connections.
o Inline connections may expand in size to account for the individual connections
required to be displayed.
Related Topics

February 2016

You can use Capital AutoView Assist for Integrator to generate a set of Capital Logic wiring
diagrams that are partitioned according to a user-defined property that has been set on the
functional devices and pins in the associated Capital Logic designs. The devices and their pins
can appear on multiple diagrams.
The user-defined property values must be comma-separated lists of the wiring designs on which
the devices and pins must appear. See “Translation of Objects When Generating Partitioned
Diagrams” on page 576.
Overview of Flow for Custom Partitioned Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . 569

Generating Custom Partitioned Wiring Diagrams According to a User-Defined Property
572
Overview of Flow for Custom Partitioned Diagrams

There is a particular flow for custom partitioned diagrams.
1. In the associated Capital Logic designs, you must set a partitioning property on the
functional devices and their pins. The property values must be the name of one or more
wiring diagrams on which the devices and pins must appear. In the case of multiple
names, the list must be comma-separated. The property name is user-defined but must
be the same on all objects because Capital AutoView Assist for Integrator looks for this
property when generating custom partitioned diagrams. See To add a property to an
object in the Capital Logic User Guide for information about adding a property to an
object.
For example:
Figure 22-1. System Wiring Diagram Property
In this example, the property is called System Wiring Diagram and this object would
appear on two generated wiring diagrams AUDIO-POWER and LIGHT-POWER.
Note
You can use the Object Type Information functionality in Capital Project to define
the property name and its values.

February 2016
The following table explains the results of combining the partitioning property on
devices and pins:
Table 22-2. Results of Partitioning Properties on Objects

Partitioning Partitioning Result in Generated Example
Property on Property on Diagrams
Device? Pin?
No No The device and pin will not DEV1 has no partitioning
be present on any diagram. property.
DEV1 has only PIN1 with
no partitioning property.
DEV1 and PIN1 do not
appear in any wiring
diagram.
Yes No The pin is present on the Example 1:
diagrams specified for the DEV1 has a partitioning
device. property value of A and B.
DEV1 has PIN1 with no
partitioning property.
DEV1 and PIN1 appear in
wiring diagrams A and B.
Example 2:
DEV1 has a partitioning
property value of A and B.
DEV1 has no pins.
DEV1 does not appear in
any wiring diagram
because Capital
AutoView Assist for
Integrator ignores devices
without pins.

February 2016
Table 22-2. Results of Partitioning Properties on Objects (cont.)

Partitioning Partitioning Result in Generated Example
Property on Property on Diagrams
Device? Pin?
No Yes The pin and device are DEV1 has no partitioning
present on the diagrams property.
specified for the pin. DEV1 has PIN1 with no
DEV1 has PIN2 with a
partitioning property
value of A and B.
PIN1 does not appear in
any wiring diagram.
DEV1 and PIN2 appear in
wiring diagrams A and B.
Yes Yes The pin is present only on DEV1 has a partitioning
the diagrams specified for property value of A and B.
the pin. DEV1 has PIN1 with no
DEV1 has PIN2 with a
partitioning property
value of B and C.
PIN1 and DEV1 appear in
the wiring diagrams A and
B.
PIN2 and DEV1 appear in
the wiring diagrams B and
C.
2. When you run Capital AutoView Assist for Integrator, you must select the “Generate
Custom Partitioned Diagrams” option and specify the “Partitioning Property” that has
been set on the objects in Capital Logic. See “Generating Custom Partitioned Wiring
Diagrams According to a User-Defined Property” on page 572.
When generating the diagrams, Capital AutoView Assist for Integrator examines all
active functional devices and pins to determine which system wiring diagrams must be
generated. The diagram layout is based on the pieces of the layouts of the functional
diagrams that contain the corresponding devices. The layout reuses positions of the
functional devices and uses nets as guides for the layout of the wiring where possible.
You can specify a template (prototype) design.
Related Topics

February 2016
Generating Custom Partitioned Wiring Diagrams

According to a User-Defined Property
You can generate a single design containing a set of Capital Logic wiring diagrams that are
partitioned according to a user-defined property that has been set on the functional devices and
pins in the associated Capital Logic designs. The user-defined property values must be comma-
separated lists of the wiring designs on which the devices and pins must appear.
See “Translation of Objects When Generating Partitioned Diagrams” on page 576.
Prerequisites
• In the associated Capital Logic designs, you must have set a partitioning property on the
functional devices and their pins. See “Overview of Flow for Custom Partitioned
Diagrams” on page 569.
• You must have synthesized wiring in the Capital Integrator design. See “Composite
Data Management” on page 317.
Procedure
2. From the drop-down list at the top of the dialog box, select Generate Custom
3. On the Design tab, specify the following for the design that will be generated:
• Name
• Revision
• Release Level
• Parent Folder
• Style Set
4. On the Options tab (with “Custom Partitioned Diagrams” selected), select the
Partitioning Property and specify whether you want the wiring diagrams to include any
“Slot Internal Connectivity”.
5. Still on the Options tab, specify the following options for the diagram generation:

February 2016
is None)
Minimum or All)
Caution

• Wire spacing
Caution
following: All of the configurations are selected on the Filter tab so that no wiring is lost
when importing it back into a Capital Integrator design.
wiring diagrams.

February 2016
diagrams.
9. If you have selected a Slot Internal Connectivity setting of Minimum or All, the Slot
properties.
displayed. You can use a generated wiring diagram as a template for a new wiring
diagram. If you do not want to do this, skip to step 11.

February 2016
Note
generated with the Minimum setting for Slot Internal Connectivity, it should be used
Select the design to be used as a template (prototype) in the Prototypes field.

11. Click OK.
Results
Related Topics

February 2016
Translation of Objects When Generating

Partitioned Diagrams
When you use Capital AutoView Assist for Integrator to generate functionally partitioned
wiring diagrams in Capital Logic, objects are translated in particular ways.
Multicores
For each multicore, Capita Integrator Assist looks for the longest section of parallel running
wires or for where the wires are closest together. The multicore indicators are placed on these
sections.
If the section is long enough, an indicator is added at each end. If the multicore is shielded,
Capital AutoView Assist for Integrator routes the shield from the indicator to wherever it is
connected.
Figure 22-2. Indicator Each End
If Capital AutoView Assist for Integrator cannot find any parallel section of the wires, it adds
indicators at the ends of only the first wire in the multicore.
Figure 22-3. Indicators at End of First Wire Only
Additionally, if the multicore has been defined in Capital Logic, Capital AutoView Assist for
Integrator may create one or more inline connections across the original functional path for
which the multi-term was defined. In this case, multi-term indicators are required at the ends of
each new wire segment created near the inline connectors.

February 2016
Figure 22-4. Indicators at End of Each New Wire Segment
If the multicore is terminated, an additional connector pin is created to accommodate the shield
termination for each inline connector in the path.
Figure 22-5. Additional Connector Pin

February 2016
Device Attributes
If you are generating diagrams with no slot internal connectivity and multiple devices exist in a
slot, all attribute values are retained for each device. If a slot contains several devices of the
same type, the attributes of each instance are retained and placed appropriately onto the wiring
diagrams.
If you are generating diagrams with minimum slot internal connectivity or all slot internal
connectivity, a device is generated for each functional source device so the attributes of the
functional source device are replicated onto the appropriate device in the generated diagram
(except in the case of combined devices).
Multiple Components in a Slot

Examples of a slot with multiple components are a fuse box and a power distribution box. These
slots represent assemblies that are made up of several components that provide current
protection between the vehicles power system and loads.
A power distribution box contains fuses and relays that protect and activate loads in the vehicle.
The configuration typically includes a direct feed to the battery/generator that many of the fuses
and relays connect to via a buss bar. The buss bar connections are all internal to the power
distribution box. Additionally, there may also be connections between relays that exist within
the power distribution box. Any connection that is required by the vehicle loads will then have a
feed from the power distribution box to the loads or fuse panel.
The internal connections are considered virtual because they are part of the power distribution
assembly. Regardless, they need to be represented in the functionally-partitioned wiring
diagrams because, in many cases, the contents of the power distribution box is distributed across
a set of diagrams based on function. Without this additional connectivity, the wiring diagrams
would have open connections.
• Parallel components in a slot

The following example shows how parallel components are translated if Capital
AutoView Assist for Integrator is running in All Slot Internal Connectivity mode.

February 2016
Figure 22-6. Parallel Components in a Slot: Capital Logic Functional View
Figure 22-7. Capital Integrator Slot - Power Distribution Box
In order to visualize logical connectivity that exists between the relays in the wiring
diagram, a shared device must be created and it must contain both logical and physical
connections defined within the slot. This is the only way that the connectivity can be
recognized and translated to the wiring diagrams.
In this example, the physical connections are the connections to the slot connector pins
1, 2 and 3. Pins 2 and 4 of the relays are the slot connectors required for display.
Therefore, two additional connections need to be defined for the shared device in order

February 2016
to display the logical connectivity in the wiring diagrams. The resultant shared device
will therefore have five connections, three real and two virtual as shown below:
Figure 22-8. Resultant Shared Device
Figure 22-9. Generated Wiring Diagrams in Capital Logic:
Note that the power distribution box assembly contains its own connectors. Therefore,
the connections must be displayed as part of the physical connectivity in the wiring
diagrams. Additionally, the correct slot connector is displayed in the wiring diagrams.

February 2016
If Capital AutoView Assist for Integrator is running in All Slot Internal Connectivity
mode, the above example is translated as follows:
Generated wiring diagrams in Capital Logic:
Figure 22-10. Generated Wiring Diagrams: All Slot Internal Connectivity
Note that the logical slot connectivity is missing. All connections that are within a slot
are not added to the generated wiring diagrams.
• Series connectivity for components within a slot
The following example shows how connectivity that exists between components within
a slot is displayed in the generated wiring diagrams if Capital AutoView Assist for
Integrator is running in All Slot Internal Connectivity mode:
Figure 22-11. Series Connectivity: Capital Logic Functional View

February 2016
Figure 22-12. Capital Integrator Slot - Power Distribution Box (Components

within Slot)
Note that the slot contains two components in series. In this case, only the connections to
the slot connector are normally created as part of the shared device. In order to display
the connectivity in the wiring diagram, the shared device must have two more
connections defined.
The connection defined by Rly1 pin 2 and Rly 2 pin 3 must be included in the shared
device as shown below:
Figure 22-13. Series Connectivity: Shared device

February 2016
Figure 22-14. Series Connectivity: Generated Wiring Diagram in Capital Logic
Note that a shared device pin exists for each relay pin.
If the Add Slot Internal Connectivity box is not checked on the Wiring Design
Generator facility, the above example is translated as follows:
Figure 22-15. Series Connectivity: Generated Wiring Diagrams without Slot
Internal Connectivity:
Wiring Demoted Internally to a Slot

Within Capital Integrator, synthesized wiring can be demoted to slots. That means, the wiring
no longer exists as part of the harness but as part of the slot assembly.

February 2016
The following example shows how this is translated by Capital AutoView Assist for Integrator:
Figure 22-16. Wiring Demoted Internally: Capital Logic Functional View:

February 2016
Figure 22-17. Capital Integrator Slot (Power Distribution Box) and Initial
Synthesized Wiring:
Figure 22-18. Internal Connectivity of Slot and Demoted Topology Wiring:
The shared device created in order to display the internal splice pins and the resulting wiring
diagrams are shown below:
Figure 22-19. Wiring Demoted Internally: Shared Device:
Figure 22-20. Wiring Demoted Internally: Generated Wiring Diagrams in Capital

February 2016
Logic:
Distributed Objects (Power and Ground Paths)

Ground signals must be added manually to diagrams in Capital Logic and Capital Integrator. In
Capital Integrator, the ground devices are grouped together within slots based on proximity.
This causes the ground device within each slot to be instantiated with a common name. When
you use Capital AutoView Assist for Integrator to generate wiring diagrams in Capital Logic,
the new names for the ground devices are applied to the wiring diagrams for each ground signal.

February 2016
The following example shows how these distributed objects are translated when using Capital
AutoView Assist for Integrator to generate wiring diagrams:
Figure 22-21. Distributed Objects: Capital Logic Functional View:
The physical path between components and ground device appear as continuous and unbroken.
This requires the distribution of splices and inline connectors. The splice and inline pin pairs are
repeated as needed for each ground path. Only the wires that reside on the current diagram are
available for a splice (for ground path only). Inline pairs are repeated along the ground path to
ensure an unbroken path. Therefore, there are no off page connections for splices because they
will always be distributed across diagrams.
When multiple wires (like those associated to a splice or multi-term) exist for a net path, Capital
AutoView Assist for Integrator ensures that they are not laid over one another. Instead, they are
routed near the net path and parallel to the path without lying on top of each other.
In conjunction with this, all wiring entities associated with the wires must also follow a net path.
Capital AutoView Assist for Integrator selects a net path to distribute physical connectivity and
distributes accordingly along that path without overlap of parallel conductors or arbitrary

February 2016
distribution of other entities (splices and inline connector pairs). The following is an example of
this:
Figure 22-22. Net Path to Distribute Physical Connectivity
Note that each splice is placed near a device pin with enough space provided to place the
conductor name. In many cases, the splice can be associated to several pins.
Once the splices and inline pin pairs have been placed, Capital AutoView Assist for Integrator
routes the wires along the net path without overlap of parallel conductors.
Component Positioning
If you have used the Prototype tab to select an existing wiring design as a template for the new
wiring diagrams, Capital AutoView Assist for Integrator does not extract the X, Y position of
objects from the template diagrams in the following scenarios:
• If an instance of an object on a template does not have a corresponding object in the

original Capital Integrator design.

February 2016
For example:
Figure 22-23. Component Positioning: Capital Integrator Diagram and
Prototype Template Diagram
Figure 22-24. Component Positioning: New Wiring Diagram
• If an instance of an object on a template has fewer pins than a corresponding object in

the original Capital Integrator design. In this case, the object and its positioning is
copied from the Capital Integrator design.

February 2016
For example:
Figure 22-25. Fewer Pins: Capital Integrator Diagram and Prototype Template
Diagram
Figure 22-26. Fewer Pins: New Wiring Diagram
Note that if the instance on the Capital Integrator diagram has the same number of pins
but the symbol has been modified, the new symbol is used but the positioning is still
based on the instance in the template diagram.

February 2016
For example:
Figure 22-27. Same Number of Pins: Capital Integrator Diagram and Prototype
Template Diagram
Figure 22-28. Same Number of Pins: New Wiring Diagram
• Sometimes an instance of an object in the template design is attached to a path that

differs in connectivity from the path in the new wiring design. In this case, the
corresponding instance in the Capital Integrator diagram is copied to the generated
diagram.

February 2016
For example:
Figure 22-29. Different Connectivity: Capital Integrator Diagram and Prototype
Template Diagram
Figure 22-30. Different Connectivity: New Wiring Diagram
• If an instance of an object on a template diagram has less complexity based on option tag
expressions, only the options that apply based on the template definition are visible in
the new wiring diagram that is generated. In short, if there are components that are
visible in the Capital Integrator diagram but they are not visible on the template diagram
because of optioning, those components are not added to the new wiring diagram that is
generated.

February 2016
For example:
Figure 22-31. Less Complexity: Capital Integrator Diagram and Prototype
Template Diagram
Figure 22-32. Less Complexity: New Wiring Diagram
Route Paths
If you have used the Prototype tab to select an existing wiring design as a template for the new
wiring diagrams, the routing of signals follows the paths in the template diagrams when:
• The path connectivity in the template diagram is the same as the path connectivity that is
defined in the Capital Integrator diagrams.

February 2016
For example:
Figure 22-33. Route Paths: Capital Integrator Diagram and Prototype Template
Diagram
Figure 22-34. Route Paths: New Wiring Diagram
• The device pins that are connected by the path in the Capital Integrator design are in the
same locations as on the generated wiring diagram.
Otherwise, the routing uses the route defined by the logical connectivity.
Device Attributes and Device Pin Attributes

Source functional device attributes and device pin attributes are converted into the properties on
the generated physical devices and device pins. The graphical representation of the source
functional attributes is used for the representation of the corresponding properties.
Daisy Chains
Wiring shields are generated as daisy chains when the corresponding shield in the original
functional diagram is drawn as a daisy chain. Daisy chains are not supported when the wiring
shield is connected to a splice in the original functional diagram and the Capital Integrator
design does not use pig tails.

February 2016
Translation of Objects When Generating Diagrams Using Templates (Prototypes)
For example:
Figure 22-35. Original Functional Design with Multicore and Daisy Chain
Figure 22-36. Generated Wiring Diagram with Multicore and Shields

Termination
Translation of Objects When Generating

Diagrams Using Templates (Prototypes)
When you use Capital AutoView Assist for Integrator to generate partitioned diagrams using a
template (prototype) design, objects are translated in particular ways.
Prototype Diagram Matching

You can use any wiring design (and its diagrams) as a template (prototype) when generating
wiring diagrams. The template design can:
• have been generated previously from any topological design using Capital AutoView
Assist for Integrator.
• have been created manually in Capital Logic without using Capital AutoView Assist for
Integrator.

February 2016
Template (Prototype) Generated by Capital AutoView Assist for Integrator

The system works out which wiring diagrams from the template design to use. It does this using
the following algorithm:
1. Checks for the existence of diagram properties on the template diagram that matches
with the functional diagrams. Any matched diagrams are not considered in the following
steps.
Note
Capital AutoView Assist for Integrator creates two properties on any diagrams that it
generates. These properties are Functional Diagram and Logical Design. These are
the properties used in the first step. For example, a wiring diagram has a property
Functional Diagram=Diagram1 and the wiring design has a property Logic
Design=Functional power design.
2. Attempts to use internal base IDs to match the remaining template diagrams with the
remaining functional diagrams. Any matched diagrams are not considered in the next
step.
3. Uses diagram names to match the remaining template and functional diagrams.
Note
If there are unmatched functional wiring diagrams, the corresponding wiring
diagrams will be created with no template.
Template (Prototype) Created Manually in Capital Logic

In order to use a design that has not been generated previously by Capital AutoView Assist for
Integrator, you must add a property to the design. The property must be called
SOURCE_PLANE_ID but can have any value. By adding this value, you enable the selection
of this design in the Prototype field when generating diagrams. Without doing this, it will not
be available for selection.
You must also associate a functional diagram with each diagram in the template wiring design.
You can do this by either:
• Naming the template diagrams so that the names follow the pattern
[FunctionalDesignName]:[FunctionalDiagramName]. This creates an association
between the template diagrams and the functional diagrams.
Or
• Adding the following two properties to the template diagrams:

o Logical Design

February 2016
Specify the name of the functional design with which you want to associate the
template diagram.
o Functional diagram
Specify the name of the functional diagram with which you want to associate the
template diagram.
Structural Matching of Prototype Paths

When finding the content to be replicated using a prototype, the system first determines the
paths to be compared between the prototype diagram and the newly generated diagram. A path
is the physical content that corresponds to a functional signal. After the system finds the
prototype path to be replicated for a path in the generated wiring diagram, the internal content of
the path is matched using base ids.
If internal content item (a wire or splice) has a match, it uses the layout from the prototype,
otherwise, it ignores the prototype for that path and uses the net for a guided layout or routes
from scratch between the end points of the path.
The systems also uses option expression information on the wires to correctly match paths.
When there is no harness level/configuration information or if there are no matches using
harness levels, the system picks path pairings deterministically.
For example:
There is a prototype path like this:
Figure 22-37. Structural Matching of Prototype Paths: Prototype Path

February 2016
When the system generates a new wiring diagram using this as a prototype, the system attempts
to match the ends of the path (PIN 1 on P1, PIN1 on P2 and PIN1 on P3) with path ends on the
generated diagram. If there is no match, the system ignores all content within the path (splices
and wires) when prototyping.
In this example, the ends match with the connectivity in the generated diagram:
Figure 22-38. Structural Matching of Prototype Paths: Generated Diagram
With the structural match of the path ends, the system can match the internal content based on
the connection ends. It then traverses the path content. As there has been a re-synthesis in the
Capital Integrator design, the internal content is not matched using base ids or names.
In this example, the system looks for WIRE1 in the generated path starting from PIN1 on
DEV1. In the prototype path, PIN1 of DEV1 and SP1 are both connected to the wire so the
content between these two (WIRE1) is a structural match for WIRE4.
The structural match means that the system uses an algorithm that determines which joints are
similar in the prototype path and the generated path.

February 2016
Figure 22-39. Structural Matching of Prototype Paths: Structural Match
In this screenshot, the left side is the prototype and the right side is the generated diagram. The
colored arrow lines indicate how the system has determined the similar joints. It identifies the
edges to be mapped based on this information and uses the matched edges as prototypes.
WIRE1 is matched with and used for WIRE4, WIRE3 for WIRE5, and WIRE2 for WIRE6.
In this example, the complete path content matches and so the complete path is used as a
prototype and replicated.

February 2016
The following examples show how the software behaves in different scenarios:
Prototype Path Example 1

The prototype has the path:
Figure 22-40. Prototype Path Example 1
And the generated diagram has a path like this:
Figure 22-41. Prototype Path Example 1: Generated Diagram
In this case, the system matches WIRE6 with WIRE2 and WIRE5 with WIRE3.
WIRE4 matches with WIRE1 : INLINE : WIRE12.

February 2016
Therefore, the schematic route of WIRE1, J200.PIN1 and WIRE12 will be used as the route for
WIRE4.

This example uses a different Capital Integrator design to previous examples.
A functional Capital Logic design is mapped to a Capital Integrator design with no inlines and
splices. You generate the first wiring design:
The Capital Logic design is associated with a second Capital Integrator design. This design
contains an inline and a splice as additional items:
Figure 22-43. Inline and Splice

February 2016
When Capital AutoView Assist for Integrator is invoked on this design using the first generated
diagram as a prototype, the newly generated diagram is as follows:

A prototype is as follows:

February 2016
The generated wiring diagram contains a path like this:
In this case, there is a complete structural match and the whole prototype is used.

When there is a partial content match, part of it may be matched structurally. For the non-
matching content, guided layout/routing is used.
A wiring diagram has been generated as follows:

February 2016
The functional diagram is changed such that some devices are replaced and the wiring is re-
synthesized in Capital Integrator. The new functional diagram is as follows:
Figure 22-48. Prototype Path Example 1: New Functional Diagram
The new devices DEV6 and DEV7 have been added.
When Capital AutoView Assist for Integrator is run again, the path DEV1 > WIRE1 > SP1 >
WIRE3 > DEV3 matches structurally.
The other path from DEV7 to DEV6 does not have a match in the prototype. For this path, the
system uses the functional diagram as the guide for layout and the standard guided layout rules
apply.

This example is concerned with center-strip splices. A prototype has two center-strip splices:
The generated design has three wires for the same signal with two splices:
Figure 22-50. Prototype Path Example 5: Three Wires for Same Signal

February 2016
It is not possible to use a prototype in this case even though it can be said that there is a
structural match. This is because the system cannot map multiple generated objects to a single
prototype object.
As in all examples, when a prototype cannot be used, the system uses the schematic route of the
prototype to place the generated objects.

This example is concerned with splices and multiterms.
Given the prototype and generated diagram above, WIRE201 uses the schematic route of
WIRE200 > SP1 > WIRE201 from the prototype. WIRE202 uses the schematic route of
WIRE200 > SP1 > WIRE202.

The topological design has different harnesses for LHD and RHD configurations for a signal
from an associated functional diagram.
The functional diagram looks like this:
Figure 22-52. Prototype Path Example 7: Functional Diagram
It contains a signal COND1.

February 2016
The topological diagram looks like this:
Figure 22-53. Prototype Path Example 7: Topological Diagram
There are different harnesses for LHD and RHD configurations.
There is a prototype (template) wiring diagram that has been generated for both the LHD and
RHD configurations together:
Figure 22-54. Prototype Path Example 7: Prototype for both LHD and RHD
Configurations

February 2016
The names of the inline connectors have been changed (J3x to J3, P7x to P7 and so on).
The new, generated wiring diagram looks like this:
Figure 22-55. Prototype Path Example 7: Generated Diagram for LHD and RHD
Configurations
The prototype matching uses structure and option expressions rather than object names. This
means, the prototype inlines are matched correctly.
Mapping Using Base IDs and Names

The mapping algorithm uses a mixture of matching based on base IDs and name attributes of
harness end objects (such as, devices) and structural matching for the inner content and
connectivity.
Devices, harness connectors and their pins are matched using base IDs or names:
• First the system matches by base ID (some devices and connectors find a match with this
rule).
• Then, for unmatched devices and connectors, the system matches by name.
The system follows a different approach for pin matching:
• If the device or connector is matched by base ID, all of its pins are matched by base-ID
where possible.
• If the device or connector is matched by base ID and a pin cannot be matched by base ID
(such as connector pins deleted and recreated in Capital Integrator with the same name),
the pin is matched by name.

February 2016
• If the device or connector is matched by name, all of its pins are matched by name.
Base IDs or names are not used for matching harness plugs.
Structural matching is used to map wires, splices and inlines.
Example of Connector Matching

Consider the following example diagrams where an LHD Configuration Wiring Design (see
Connector Matching Example: Template (Prototype) LHD Configuration Design) is used as a
template (prototype) for generating an RHD Configuration Wiring Design (see Connector
Matching Example: Generated RHD Configuration Design Using LHD Configuration Design
as Prototype):
Figure 22-56. Connector Matching Example: Associated Functional Design

February 2016
Figure 22-57. Connector Matching Example: Topological Design
Figure 22-58. Connector Matching Example: Template (Prototype) LHD

Configuration Design

February 2016
Figure 22-59. Connector Matching Example: Generated RHD Configuration

Design Using LHD Configuration Design as Prototype
The RHD device DEV1 has a different base ID and option expression from the LHD device
named DEV1. Despite the different base IDs and option expressions, name matching (without
expression) identifies the DEV1 in the Template (Prototype) LHD Configuration Design as a
prototype for RHD DEV1.
However, the RHD connector P3 does not match the LHD connector P2 either by base ID or
name. The system therefore uses device pin association to treat P2 as a prototype for P3.
By matching P3 with P2, the path or WIRE1 from the template is used as the prototype for
WIRE2.
Resolution of Name Collisions During Prototype Mapping

If multiple devices in the generated design have the same name, one of the generated devices is
mapped to all the devices with the same name in the prototype design. The remaining generated
devices do not use any prototype. Any name collisions for harness plug connectors and unmated
connectors are resolved in the same way.
Generation of Pins on Symbols

Capital AutoView Assist for Integrator generates a pin on a symbol only if the pin is used on the
Capital Integrator diagram. That means, any pins from the symbol that are not used in the
Capital Integrator diagram are not added to the symbol instance in the generated wiring
diagram.
When Capital AutoView Assist for Integrator creates a wiring diagram, if it uses a prototype
containing symbols and those symbol instances have insufficient pins for the newly synthesized
wiring, then a new symbol instance is created for the additional pins.

February 2016
Generation of Slot Connectivity in Partitioned Diagrams
Capital AutoView Assist for Integrator will not add additional pins to symbol instances already
existing in a prototype diagram.
Note
You can prevent the creation of a new symbol instance by adding the required pins to the
prototype wiring diagram prior to running Capital AutoView Assist for Integrator.
Generation of Slot Connectivity in Partitioned

Diagrams
Capital AutoView Assist for Integrator generates one device (slot-internal device) for each
placement of a functional device in a slot. The generated device has the name and all the
properties and attributes of the functional device. The generated device also has an attribute that
contains the name of the Integrator slot from which it was generated. This attribute is not
editable in the wiring diagram and will be displayed only if it is set. If the slot has an integral
connector, the device is generated with a Harness attribute and a Levels property. If the device
has a single functional source, any library data, analysis data and symbol model data is
replicated onto the generated device.
The option expression of the generated device is the following expressions ANDed together:
• The option expression used for the placement of the functional device.
• The option expression of the functional device itself.
The final expression puts each non-empty expression in parenthesis and separates them with
&&:
(Option expression 1) && (Option expression 2)
One pin (slot-internal pin) is generated on the slot internal device to represent each functional
pin. The pin inherits the name, attributes and properties of the functional pin.
Capital AutoView Assist for Integrator sometimes generates a slot boundary device to represent
a slot and its slot external pins. A slot boundary device is always a shared device.
Slot boundary devices are required when there is complex slot-internal connectivity. Examples
of complex slot-internal connectivity are:
• There is a connector cavity or a hole connection associated with the slot that has
multiple functional pins mapped to it. A pin would be generated for each such connector
cavity or hole connection on the slot boundary device.

February 2016
Figure 22-60. Example of Complex Slot-internal Connectivity where Multiple

Functional Pins Connect to a Single Slot Cavity
• There is a functional pin mapped onto multiple connector cavities or hole connections.
A pin would be generated on the slot boundary device for each such connector or cavity
hole.
Figure 22-61. Example of Complex Slot-internal Connectivity where a Single
Functional Pin Connects to Multiple Holes
• There are more than one functional devices mapped to cavities connected to the same
slot connector.
Figure 22-62. Example of Complex Slot-internal Connectivity where Multiple
Functional Devices Connect to the Same Slot Connector
• Although not complex slot-connectivity, the mapping of cavities to an internal splice

also requires a slot boundary device.

February 2016
Figure 22-63. Slot-internal Splice Connected to Cavities
Slot boundary devices are optional in a generated design when:
• The mapping of functional pins to cavities or holes is one to one and all the cavities of
the connector are connected to a single functional device, this is simple slot internal
connectivity.
Figure 22-64. Example of Simple Slot-internal Connectivity where Each
Functional Pin Maps One to One with Cavities
Capital AutoView Assist for Integrator can run in two modes where it displays slot-internal
connectivity in the generated wiring diagrams:
• Generate Functionally Partitioned Diagrams (All Slot Internal Connectivity) - all

slot-internal connectivity is generated. The connectors are always associated with the
slot boundary device.
Figure 22-65. Example of Simple Slot-internal Connectivity Generated in All
Slot Internal Connectivity Mode
• Generate Functionally Partitioned Diagrams (Minimum Slot Internal

Connectivity) - Optional slot-internal connectivity (simple connectivity) is not
displayed in the generated wiring diagrams. The connector pin is directly mated with the
slot internal device pin.

February 2016
Figure 22-66. Simple Slot-internal Connectivity Generated in Minimum Slot

Internal Connectivity Mode
When generating diagrams in the Generate Functionally Partitioned Diagrams (No Slot
Internal Connectivity) mode, if there is complex slot-internal connectivity caused by multiple
cavities mapped to the same functional source, the system generates a pin to represent each
cavity. For example, 2 pins of a device DEV1 are mapped to the same cavity of a slot SLOT1:
Figure 22-67. Functional Pin Mapped to Multiple Cavities Topology
Figure 22-68. Functional Pin Mapped to Multiple Cavities Generated Diagram
If there are holes mapped to an internal splice, no slot internal connectivity is generated,
regardless of the generation mode. For example:
Figure 22-69. Generation of a Slot Internal Splice Mapped Entirely to Holes

February 2016
When Capital AutoView Assist for Integrator generates slot-internal connectivity, it generates a
pin for each connector cavity or hole connection on the slot boundary device and connects it to
the slot-internal device or splice.
The slot boundary device inherits the name, attributes, properties and option expression of the
slot. However, its name may be appended with a unique suffix to avoid conflicting names with
generated slot-internal devices. If the slot has an integral connector, the slot boundary device is
generated with a Harness attribute and a Levels property. Library and symbol references are
replicated from the slot to the generated boundary device.
If a slot-internal pin is mapped to a single connector cavity, the connector pin is attached to a
slot-internal pin.
Where a slot-internal device represents a splice, a splice is generated only when there is at least
one hole. If all of the pins are mapped to connector cavities, a net conductor is generated to
connect the slot-external pins. Where there is at least one hole, a splice is generated and
connected to any slot-external pins with wires (splices cannot be attached to nets). Where the
slot-internal splice is connected through a hole, the external conductor connects directly to the
generated splice. The splice inherits the name, properties and attributes of its slot device. The
splice will also have a read-only attribute that is only displayed when it is set, containing the
name of the slot from which it was generated.
Examples of Source Connectivity and Generated Results
Table 22-3. Examples of Source Connectivity and Generated Results

Representation of source Expected generated result Expected generated
connectivity with All Slot Internal result with Minimum
Connectivity Slot Internal
Connectivity
Example of simple slot-internal connectivity where DEV2 has a pin mapped to a hole:
Example of complex slot-internal connectivity where the mapping between pins and cavities/
holes is not one to one:

February 2016
Table 22-3. Examples of Source Connectivity and Generated Results (cont.)

Representation of source Expected generated result Expected generated
connectivity with All Slot Internal result with Minimum
Connectivity Slot Internal
Connectivity
As for All Slot Internal
Connectivity
Example of complex slot-internal device connectivity where more than one device is
connected to the same connector:
Connectivity
Example of a slot-internal splice mapped entirely to connector cavities with multiple wires:
Connectivity
Example of a slot-internal splice mapped entirely to holes with multiple wires connected to
one hole:
Connectivity

February 2016
Distribution of Inlines By Home Condition

When Distribute Inlines By Home Condition is selected in Capital AutoView Assist for
Integrator, inlines are distributed across the generated diagrams in particular ways.
Select this option if you want to distribute inline connectors across the generated wiring
diagrams using the home condition set on the functional source signal (set in Capital Logic) to
which the inline connector belongs.
In this case, an inline connector is distributed to all of the generated diagrams where the
functional signal of its attached wire conductor’s home condition is set. It is assumed that if any
of the functional conductor schematics on a diagram is a home object (that is, its home
condition is set), then all of its conductor schematics on that diagram are considered to be home
objects.
The algorithm for distributing the inlines by home condition uses the following rules:
• If a single-ended (ported) net in a logical diagram has its home condition set to true, all
wires and inline connectors needed to implement this net stub will be added to the
wiring diagram
• If a single-ended (ported) net in a logical diagram has its home condition set to false, just
the single wire stub used to implement this net stub will be added to the wiring diagram.
No inline connectors will be added to the wiring diagram.
• If a net is connected on both ends in the logical diagram, all wires and inline connectors
needed to implement this net connection will be added to the wiring diagram regardless
of the home condition setting on the net.
• If no instance of a net in the logical diagram has the home condition set to true and no
full connection on both ends of the net is available, the algorithm picks the net stubs and
implements the appropriate structure with all wires and inline connectors. The wires and
inline connectors can be distributed to several net stubs.
• When using the wiring prototype flow, the template is considered as the master for
determining the distribution of inlines and splices. If there is additional connectivity that
requires distribution, then the rules above are used for the distribution.
Example of Generated Diagrams With and Without Selecting to Distribute

Inlines by Home Condition
Assume the functional designs are as shown in the image below where the Functional Diagram
1 net instances are marked with home conditions as true and no other instance of these nets are
home objects.

February 2016
Figure 22-70. Net Instances Marked with Home Conditions
In Functional Diagram 3, there is a full implementation of the conductors.
Assume the Capital Integrator design is as shown in the image below with two inline connectors
in the path of the two devices.
Figure 22-71. Inline Connectors in Path of Two Devices

February 2016
Without Distribute Inlines by Home Condition selected, the generated wiring diagrams are as
follows:
Figure 22-72. Distribute Inlines Not Selected: Generated Diagram 1

February 2016
With Distribute Inlines by Home Condition selected, the generated wiring diagrams are as
follows:
Figure 22-75. Distribute Inlines Selected: Generated Diagram 1

February 2016
Propagation of Home Conditions

Home conditions from the functional source objects are propagated to the generated wiring
content. If a prototype (template) object exists for a wiring object, the home condition is copied
from the prototype. For wiring content with no matching prototype object, the home condition is
copied from the functional source diagram.
Table 22-4. Propagation of Home Condition by Object Type

Generated Object Condition for Propagation of Home Condition
Wire Set if the functional source signal is a home object.
Shield Set if the functional source signal is a home object.
Splice Set if any of the attached wires have a functional
source that is a home object.
Harness connector with Set if the attached device’s functional source is a home
owner object.
Normal device Set if the functional source device is a home object.
Ground device Set if the functional source device is a home object.
Inline connector Set if any of the attached wires have a functional
Interface inline connector Set if any of the attached wires have a functional
Home Condition on Object with Slot Internal Connectivity

When generating diagrams with minimum or all slot internal connectivity, the home condition
on the generated slot internal objects is as follows:
• The home condition on the slot internal device is the same as on its functional source.
• The home condition on the slot external device is set using the home condition of the
functional signal of the attached conductor (to the slot external device or to the
connectors of the slot external device).
• The home condition on the slot internal net conductor is unchanged or not modified
from the default settings. By default, the home condition is set on a conductor.
Home Condition on Combined Devices

When you generate diagrams with Use Combined Devices selected, the home condition is set
as per the table “Propagation of Home Condition by Object Type” on page 621.

February 2016
Home Condition on Added Content for Ground Paths

When you generate diagrams with Always Add Ground Paths selected, the wiring content that
connects ground devices is added to the generated diagrams. The home condition is not set on
the ground device but is set on the other generated objects, that is, wires, splices and inlines.
If the functional diagram (that corresponds to the wiring diagram to which the ground path is
distributed) does not contain the ground path for the generated ground device, the home
condition is not set on the generated ground path.
Home Condition on Splices Added to Generated Diagram

When you generate diagrams with Distribute Splices selected, the home condition is set on the
distributed splices if any of the wire’s functional signal is a home object.
Home Condition on Extracted Connectivity Objects

When you generate diagrams with a prototype (template) and select Strictly Use Prototype
during Wiring Distribution, the home condition on objects with matching prototype objects is
determined by the prototype. The home condition on objects without matching prototype
objects is determined by the functional source diagrams.
When you generate diagrams with a prototype but without selecting Strictly Use Prototype
during Wiring Distribution, wiring content for objects without prototype objects is added to
the generated diagrams. The home condition on these objects is determined by home conditions
in the original functional diagrams.

February 2016
Chapter 23
Application Interface Help
There are various elements to the Capital Integrator application interface.

Ribbon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Project Browser Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623
Diagram Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 625
Design Browser (Design Tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 626
Logical Designs Browser (Function Tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 629
Parts Browser (Parts Tab) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631
Configuration Setting Browser Window (Configuration Tab) . . . . . . . . . . . . . . . . . . . . 632
Concurrency Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 638
Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 639
Status Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642
Design Assistant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645
Design Assistant (in Preserve Wiring Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649
Design Inspector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Icons (Glyphs) in Browser Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650
Ribbon
The ribbon at the top of an application contains tabs with menu items and buttons for various
actions.
You can use a Ribbon Helper to find a particular action.
See Searching for an Action on the Ribbon in the Capital Design Tools - Common Functions
User Guide.

The Project Browser is located on the upper left side of the application window.
Note
You can hide and show the Design Browser / Logical Designs / Configuration Settings
Browser Window and Project Browser Window by pressing the Space Bar and entering
Browser Area.

February 2016
Figure 23-1. Project Browser Window in Tool
Table 23-1. Project Browser Window Contents

Toolbar Button Description
Close Project button Closes the currently viewed project.
Project drop-down list Lists the currently open projects so that you can 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 the plus
sign (+). To collapse a section of the browser tree, click the
minus sign (-).
In the image below, Plane indicates a diagram.
Figure 23-2. Elements in Project Browser Tree

February 2016
Diagram Window
Table 23-1. Project Browser Window Contents (cont.)

Toolbar Button Description
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 project browser
tree so that only designs with names containing that series of
characters are listed. If you want to use a regular expression
character, such as a bracket, in the filter, you must prefix it with
\. For example, \(P.
Click the Clear Filter String icon ( ) to clear the filter and
view all designs in the project.
Design Filter Click the drop-down list to filter the designs displayed in the
tree menu window to those of a particular type, all designs in
the project, all designs in the currently active build list or only
those designs and build lists in your working set.
Related Topics
Opening a Project
Creating a Project
Deleting a Project
Importing a Project
Exporting a Project
Closing a Project
Diagram Window
Diagram windows are displayed on the right-hand side of the application window.

February 2016
Figure 23-3. Diagram Window
This is where diagrams are edited. When no diagram is open, a launch pane is visible. See
Launch Pane in the Capital Design Tools - Common Functions User Guide.
To open a diagram window, double-click on the diagram name in the browser tree in the Project
Browser Window.
More than one diagram window can be open in the application. See “Arranging Diagram
Windows for Viewing” on page 92.
Note
If a diagram window is not large enough for everything to be visible, scroll bars are added to
it automatically and you can move these to display different areas of the diagram window.
Alternatively, you can change the size of a diagram window by holding down the right mouse
button over an edge of the diagram window (the cursor changes to a two-way arrow ) and
dragging the edge.

The Design Browser is located on the lower left side of the application window and is opened
by clicking the Design tab.

February 2016
Figure 23-4. Design Browser (Design Tab) in Tool
It contains a browser tree that lists the objects that are in the diagram window that is currently
active.
Note
You can hide the Design Browser / Logical Designs / Configuration Settings Browser
Window and Project Browser Window by selecting View from the menu and un-checking
the Browser Area option. To display the browser windows again, select View from the menu
and check the Browser Area option.
The browser tree is split into folders. Every folder in the Design Browser allows you to perform
different functions.
Note
The browser tree displays wires only in the currently active configuration.
Design Tab Toolbar

There is a toolbar at the top of the tab.

February 2016
Table 23-2. Design Tab Toolbar Contents

Field Description
Associate Logical Displays the Associate Logical Designs Dialog Box where you
Designs associate logical designs with the currently open topological
design. See “Associating Logical Designs with the Topological
Design” on page 37.
Synthesize Wiring Displays the Wiring Synthesis Dialog Box where you run wiring
synthesis. See “Synthesizing Wiring” on page 440.
If you have one or more signals selected, the system will
synthesize wiring for only those signals.
Set all levels in design Displayed only when Configuration is selected in the Mode list of
active the Configuration Setting Browser Window (Configuration Tab).
Sets the wiring for all of the harness levels and harnesses in the
design to active. The wires are then displayed in the sub-folders of
the Signals folder on this tab.
Set all levels in design Displayed only when Configuration is selected in the Mode list of
inactive the Configuration Setting Browser Window (Configuration Tab).
Sets the wiring for all of the harness levels and harnesses in the
design to inactive. The wires are then no longer displayed in the
sub-folders of the Signals folder on this tab.
Set all modules in design Displayed only when Module is selected in the Mode list of the
active Configuration Setting Browser Window (Configuration tab).
Sets the wiring for all module codes in the design to active. The
wires are then displayed in the sub-folders of the Signals folder on
this tab.
Set all modules in design Displayed only when Module is selected in the Mode list of the
inactive Configuration Setting Browser Window (Configuration Tab).
Sets the wiring for all module codes in the design to inactive. The
wires are then no longer displayed in the sub-folders of the
Signals folder on this tab.
Set Rules and Constraints If you have a harness, slot or connector selected, this displays the
Edit Properties dialog box for that object. Otherwise, it displays
the Edit Properties dialog box for the diagram.
You can use the Rules tab to set rules and constraints on the
object. See “Rules and Constraints” on page 287.
Visualize the selected Generates a wiring view for the signal currently selected on this
signal tab. A new tab named after the signal is displayed in the Output
Window. The tab contains a wiring view for the signal.
See Generating a Wiring View of a Synthesized Signal or
Multicore for the procedure for using this functionality.

February 2016
Table 23-2. Design Tab Toolbar Contents (cont.)

Field Description
Open Design Assistant Opens the Design Assistant.
Signals Folder
Contains the following sub-folders to provide information about the signals in the design:
Table 23-3. Signals Folder Contents

Field Description
Source Nets These sub-folders are located under signals and contain the net
conductors from the associated Capital Logic designs that are the
source for that particular signal.
Wires Only displayed when harness levels are active. These sub-folders
are located under signals and contain the wires carrying the signal
in the active harness levels.
Design Browser Filter

You can use the field at the bottom of the tab to filter the objects displayed in the browser tree.:
Table 23-4. Design Browser Filter Contents

Field Description
Enter Filter String Enter a series of characters. A filter is applied to the Design
Browser Window so that only objects with names containing that
series of characters are listed. If you want to use a regular
expression character, such as a bracket, in the filter, you must
prefix it with \. For example, \(P.
Active diagram filter You can toggle this to control whether the design browser
displays all objects in the design or only objects in the currently
active diagram ( ).

The Logical Designs Browser is located on the lower left side of the application window and is
opened by clicking the Function tab.

February 2016
Figure 23-5. Logical Designs Browser (Function Tab)
It contains a browser tree that lists the devices and signals that are available for you to place and
route in the topological diagram that is currently open. The devices and signals come from the
Capital Logic designs that you have associated with the topological design.
The browser tree contains the following folders:
• Designs
Contains a sub-folder for each logical design that has been associated with the logical
design. Under the design folders there are further sub-folders that contain the devices
and signals from the designs.
• Devices
Contains the placed and unplaced devices from all of the associated logical designs. The
symbols for unplaced devices are grayed out.
Note
You can hide the Design Browser / Logical Designs / Configuration Settings
Browser Window and Project Browser Window by selecting View from the menu
and un-checking the Browser Area option. To display the browser windows again,
select View from the menu and check the Browser Area option.
Logical Designs Browser Filter

You can use the field at the bottom of the tab to filter the objects displayed in the browser tree.

February 2016
Parts Browser (Parts Tab)
• Enter Filter String ( )
Enter a series of characters. A filter is applied to the Logical Designs Browser so that
only objects with names containing that series of characters are listed.
Parts Browser (Parts Tab)

The Parts tab, located on the lower-left side of the application window, allows you to use Part
Selection dialog box functionality to search for library parts and view their details.
Figure 23-6. Parts Browser (Parts Tab)
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.
In addition to that functionality, you can right-click on part numbers for certain component
types and add a component to a harness with that part number. This action creates a component
in the same way as using a menu option but Library Part fields will be pre-populated. You can
do this for the following components:
• Slots
• Ground slots
• Junction box slots
• Connectors
• Splices

February 2016
Configuration Setting Browser Window (Configuration Tab)
• Backshells
Related Topics
Configuration Setting Browser Window

(Configuration Tab)
The Configuration Setting Browser Window is located on the lower left side of the application
window and is opened by clicking the Configuration tab.
Figure 23-7. Configuration Setting Browser Window (Configuration Tab)
It enables you to set wiring active in the design either based on Vehicle Configurations (their
related Vehicle Models and Harness Levels) or based on modules. You can then:
• Filter the display of graphical objects in the Diagram Window to only those objects with
active wiring or on active harness levels. See “Filtering the Objects Displayed in a
Diagram” on page 89.
• Depopulate wiring from active harness levels. See “Depopulating Wiring from Active
Harness Levels” on page 506.
wiring synthesis generates wires in modules whose names are initially based on the option
expressions on those wires. This tab also enables you to manage those module, whether it be
renaming, sharing or merging them.

February 2016
Table 23-5. Configuration Setting Browser Window (Configuration Tab)

Contents
Field Description
Mode list Specifies the mode in which you are viewing this tab.
Composite / Module / • Composite
[Custom Filter] View wires in the context of vehicle configurations, vehicle
models and harness levels.
• Module
View wires in the context of modules.
• [Custom Filter]
The option is available to deploy your own custom filters for this
tab, written in Java or JavaScript using the extensibility
architecture. These custom filters would be displayed in this
drop-down list. For example, you could create a filter that sets all
multicores active or all safety wires active.
For detailed information on the creation of custom filter plugins,
see the CustomActionDevelopment.pdf document, located in the
doc\plugin sub-directory of your Capital installation directory.
Set all levels in design Displayed only when Composite is selected in the Mode list.
active Sets the wiring for all of the harness levels and harnesses in the
design to active. The Browser Window (Composite) updates
accordingly.
Set all levels in design Displayed only when Composite is selected in the Mode list.
inactive Sets the wiring for all of the harness levels and harnesses in the
design to inactive. The Browser Window (Composite) updates
accordingly.
Set all modules in Displayed only when Module is selected in the Mode list.
design active If you have not selected a harness in the Browser Window (Module),
Set all modules in this sets the wiring for all modules in the design to active.
selected harnesses If you have selected one or more harnesses in the browser window,
active this sets all modules for just those harnesses to active.
The active harnesses are displayed in bold in the browser window.
Set all modules in Displayed only when Module is selected in the Mode list.
design inactive If you have not selected a harness in the Browser Window (Module),
Set all modules in this sets the wiring for all modules in the design to inactive.
selected harnesses If you have selected one or more harnesses in the browser window,
inactive this sets all modules for just those harnesses to inactive.
The inactive harnesses are no longer displayed in bold in the browser
window.

February 2016

Contents (cont.)
Field Description
Manage module codes Enabled only when Module is selected in the Mode list and when one
for selected or more harnesses are selected in the browser window.
harnesses By default, the browser window displays only the harnesses. Select
one or more harnesses in the browser window and click this to
display the modules, option expressions and wires for those
harnesses.
See Browser Window (Module) for a full description of what is
displayed.
Stop managing module Displayed and enabled only when you select one or more harnesses
codes for selected in the browser window that have module codes displayed below
harnesses them.
Hides the modules, option expressions and wires for the selected
harnesses in the browser window.
Browser window The contents of this depends on the selection in the Mode list.
See Browser Window (Composite) or Browser Window (Module).

February 2016

Contents (cont.)
Field Description
Browser Window The browser tree contains the following folders:
(Composite) • Configurations
Contains a sub-folder for each of the Vehicle Models in the
design that is currently open in the Diagram Window. Under each
vehicle model, the systems lists the Vehicle Configurations that
use it. If you hold your mouse cursor over a name, a tool tip
displays detailed information about it (for example, options
included in a vehicle model, harness levels in a vehicle
configuration).
Select the box next to a vehicle configuration to set the wiring for
that vehicle configuration and vehicle model combination to
active.
• Harnesses
Contains a sub-folder for each of the Harnesses in the design that
is currently open in the Diagram Window. Each sub-folder
contains a list of the Harness Levels that have been defined for
the harness. If you hold the mouse cursor over the name of a
harness level, a tool tip displays information about the vehicle
models that use this harness level and the options that apply to
this harness level.
Under each harness level, the systems lists the wires that have
been synthesized for it. If you hold the mouse cursor over the
name of a wire, a tool tip displays detailed information about it.
Select the box next to a harness level, to set the wiring for that
harness level to active.
Items that are currently active in the design are displayed in bold.

February 2016

Contents (cont.)
Field Description
Browser Window By default, this tree lists only the Harnesses in the design that is
(Module) currently open in the Diagram Window. If you select one or more of
the harnesses and click the Manage module codes for selected
harnesses ( ) button, the browser tree expands below each selected
harness as follows:
Each harness name folder contains further sub-folders for each of the
modules containing wires for that harness. Immediately below a
module are sub-folders for the option expressions on wires in that
module. Each option expression sub-folder contains the wires with
that option expression in that module. Variant wires (wires that
terminate at refined connectors) will typically be displayed within
multiple sub-folders relating to each variant option expression.
For example:
This example shows two wires with the same option expression
Audio Base. They are contained in a module called Audio which is
in the harness DOOR-LF. There is another module DoorLock-Drvr
&& LHD in that harness. The warning sign indicates that its name
is a module string and not a functional module code.
The symbol next to a harness indicates that all of its modules are
associated with functional module codes defined in the project.
If you hold the mouse cursor over the name of a module, a tool tip
displays the option expressions and numbers of wires in that module.
If you hold the mouse cursor over the name of a wire, a tool tip
displays detailed information about it.
You can select the box next to a module to set the wiring in it to
active.
Items that are currently active in the design are displayed in bold.
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 browser window so that only
items with names containing that series of characters are listed.
Click the Clear Filter String icon ( ) to clear the filter.

February 2016

Contents (cont.)
Field Description
Show all harness levels Enables you to filter the browser window based on whether items are
/ Show active harness active in the design or not.
levels / Show all The displayed options depend on the selection in the Mode list.
modules / Show active
modules
Active tab The contents of this depends on the selection in the Mode list.
If Configuration is selected, this displays the details of the vehicle
configuration and harness levels that are currently active.
If Module is selected, this displays a list of the harnesses with active
modules. Next to each harness, the tab displays the active modules
for it.
Detail tab Only relevant when Composite is selected in the Mode list.
This enables you to select a vehicle configuration for which you want
to view its details.
Usage Notes
You can hide the Project Browser Window / Design Browser (Design Tab) / Logical Designs
Browser (Function Tab) / Parts Browser (Parts Tab) / Configuration Setting Browser Window
(Configuration Tab) / Concurrency Tab by selecting the View menu option and un-checking the
Browser Area box. To display the browser windows again, select the View menu option and
check the Browser Area box.
Related Topics
Renaming a Module
Merging Modules

February 2016
Concurrency Tab
Concurrency Tab
The Concurrency tab is displayed at the bottom left of the application window and enables you
to view the lock state for the design, each harness and each slot.
Figure 23-8. Concurrency Tab
It contains the following:
Table 23-6. Concurrency Tab Contents

Field Description
Mode field Enables you to select whether you are running in multi user or
single user mode. See “Selecting Multi User or Single User Mode”
on page 49.

February 2016
Output Window
Table 23-6. Concurrency Tab Contents (cont.)

Field Description
Table of harnesses and Enables you to view a list of slots, harnesses and their lock states
slots (see “Selecting which Lockable Objects to View on the
Concurrency Tab” on page 49). The table contains the following
columns:
• Lock - shows whether the object is unlocked , locked by
you or locked by another user .
• Modified - shows whether the object has been modified
since the last save in the current session. The column is blank
for unmodified objects.
• Object Type - shows whether an object is a slot or a harness.
• Name - shows the name of the object.
• Locked By - shows the name of the user who has the object
locked.
Connected Objects table Shows you the slots and harnesses that are connected to the objects
that are currently selected in the table above. The columns are the
same as in the table above.
Output Window
The Capital Integrator Output Window is located at the bottom of the application window.
Figure 23-9. Output Window

February 2016
Output Window
Note
Press Space Bar and enter Toggle Output Window to view or hide the output window. If the
box is checked, the Output Window is visible; if it is not checked, the Output Window is
hidden. Information sent to the window is not lost while the window is hidden.
It displays the tool output during operation.
Each tab has a pop-up menu, accessible with a right mouse button click, that contains text
manipulation commands (Select All, Copy, and Clear).
Table 23-7. Output Window Tabs

Field Description
Capital Integrator Shows the output of the Integrator commands.
Design Assistant Groups together a number of design rule checks and other actions
within a single interface. This helps you to understand where you
are in the design flow. It allows you to run a sub-set of design rule
checks on the design. See “Design Assistant” on page 645.
Harness Import Displays any issues when importing harness data using “Integrator
Harness Exchange” on page 128 functionality.
Level Displays the report when you create an options and levels report for
a topological design.
Place Shows the status of any device placements performed in the
diagrams.
Report Displays the report when you create a topological design’s harness
report.
Route Shows the status of any routing actions performed in the diagrams.
Signal Details Provides details of why specific signals have failed to route when
you have synthesized wiring.
If the reason given for a routing failure is Disconnect due to
routing constraint, this normally indicates a constraint related to
splices or multiterms.

February 2016
Output Window
Table 23-7. Output Window Tabs (cont.)

Field Description
Signal/Multicore Name Displayed when you select a signal in the Design Browser (Design
(Wiring View) tab) and click the Visualize the selected signal button. This
displays a wiring view of the selected signal. If the signal is a
member of a multicore, it displays a wiring view of the entire
multicore.
The wiring view shows individual devices, connectors and wires
that implement the signal.
You can tear this tab from the interface so that it is a free-floating
dialog box that can be resized. To do this, click the tab name and
drag it. If you do not tear the tab from the interface, the tab is
replaced when you generate a wiring view for another signal. If you
tear off the tab, it remains unchanged when you generate a wiring
view for another signal and a separate tab is created. To return the
wiring view to the Output Window, close the dialog box.
See “Generating a Wiring View of a Synthesized Signal or
Multicore” on page 476.
Sync Displays information about the synchronization of topological data
with logical data from Capital Logic.
Synthesis Reports on the synthesis actions and signals that have failed to
route. For a failed signal, you can click the Details link to view the
reasons why it failed to route. When you click the link, the details
are displayed on the Signal Details tab in the Output Window.
You can click Save detailed failure report to access the Select
Output File dialog box that enables you to save a report detailing
failed signals and the reasons why they failed to route. You can
save the report in CSV (comma-separated values) or HTML
format.
Signal/Multicore Name (Wiring View) Tab Contents
Table 23-8. Signal/Multicore Name (Wiring View) Tab Contents

Field Description
Style This read-only view can use any style set defined for Capital Logic
(because it is a wiring view). You select the style set from this drop-
down list. The ability to have multiple style sets is controlled by
licensing. If you do not have the necessary license, only the default
style set for Capital Logic is available.
Spacing Allows you to control the amount of whitespace between objects in
the wiring view. Increase the number to move objects further apart.
Decrease the number to move objects closer together.

February 2016
Status Bar
Table 23-8. Signal/Multicore Name (Wiring View) Tab Contents (cont.)

Field Description
Refresh Updates the wiring view based on any changes to the data. The view
does not update automatically when changes are made.
Zoom All You can pan around the view and zoom in/out. If you have zoomed
in to a specific area of the wiring view, you can zoom back out again
by clicking this.
Wiring view If you select an object in the wiring view, it highlights in the Capital
Integrator diagram.
Within the wiring view, you can right-click on an object to display
the standard menu available for that object within Capital Integrator.
For example, you can select Properties and edit the attributes/
properties for that object.
If you hold the mouse cursor over a device, the effective option
expression for that device is displayed. An effective option
expression is calculated based on all of the related objects at that
location (such as, the device itself, the connecting net, and any
option expression assigned to the placement of the device). The
option expression for each of the related objects is displayed below
the effective one.
Status Bar
The Status Bar is located at the bottom of the application window.

February 2016
Status Bar
Figure 23-10. Status Bar
Table 23-9. Status Bar Contents

Field Description
Show/Hide Grid Specifies whether grid points are displayed on the diagram. Even if
this is set to off so grid points are not displayed, they still exist and
objects that would otherwise snap to the grid continue to do so. You
can toggle between On and Off by clicking the button. See “Setting
Grid Defaults for a Diagram” on page 549
Enable/Disable Object Specifies, when adding or modifying a comment graphic, whether
Snapping you can position it to automatically ‘Snap To’ alignment with
another graphic on a diagram. You can toggle between On and Off
by clicking the button. See “Setting Snap To Object” on page 549.
Design Rule Checks Indicates whether Design Rule Checks are running in the
Toggle background. Click the toggle button (play icon) to start the checks
(Start Background Run running in the background.
/ Stop Background Run) When running, the toggle button changes to a square (stop icon) that
you can click to stop the checks running:
The symbol next to the toggle button (start / stop icon) indicates
whether the checks have currently found failures or not.
Automatically preserve Toggles the Preserve Wiring Mode off and on.
wiring If it is on, the icon displayed is: .

February 2016
Status Bar
Table 23-9. Status Bar Contents (cont.)

Field Description
Toggle Splice Visibility •
Indicates that the splices are not visible in the diagram and will
not be visible if you print or output to PDF/DXF/CGM. Click
this to make them visible.
•
Indicates that the splices on the currently active wiring are
visible in the diagram. You can use style sets to determine how
their appearance is styled. See “Styling Objects in Diagrams” on
page 36.
If you print to PDF, DXF SVG or CGM with the diagram open,
the splices are printed exactly as seen on the diagram. If the
diagram is closed when you print, the splices are not printed.
Click this to hide them in the diagram.
Filtering Icon Indicates whether any filtering is applied to the open diagram. You
can click this icon to open the Design Filter dialog box that allows
you to apply filtering. See “Filtering the Objects Displayed in a
Selected Object Displays the number of objects (including text) that are selected on
Counter a diagram.
Cursor Co-ordinate Displays the co-ordinates of the position of the mouse cursor in a
diagram window.
Box
Username Icon Position the mouse cursor over this icon to display the name of the
active user.
Active Language Indicates which diagram translation language is active. By default,
this is EN.
Note
You can hide the Status Bar by selecting the View menu option and unchecking the Status
Bar box. To display the Status Bar again, select the View menu option and check the Status
Bar box.

February 2016
Design Assistant
Design Assistant
Accessed by pressing Space Bar and entering Assistant, or by clicking the Open Design
Assistant button on the Design Browser (Design tab).
Figure 23-11. Design Assistant
The Design Assistant is displayed as a tab in the Output Window. It groups together a number
of design rule checks and other actions within a single interface. This helps you to understand
where you are in the design flow. It allows you to run a sub-set of design rule checks on the
design.
If you are in Preserve Wiring Mode, the Design Assistant looks different. For details of that, see
“Design Assistant (in Preserve Wiring Mode)” on page 649.
It can be closed by right-clicking on the tab and selecting Remove tab.
• Save to CSV
Saves the content of the Design Assistant Output Table as a comma separated variable
(CSV) file. A dialog box is displayed where you specify the file name and where you
want to save it.
• Run the Design Assistant’s checks
Runs the design rule checks that have been specified to run in the Design Assistant.

February 2016
Design Assistant
Runs the Design Assistant actions that have been toggled to run using Include Design
Assistant DRCs, Report inconsistent harness options and None / Active Levels /
Persisted Configurations / All Configurations buttons.
The results of the actions are displayed in the Design Assistant Output Table. You can
specify which design rule checks are run by clicking Configure Checks ( ).
• IncludeDesign Assistant DRCs
Specifies whether to use a simulation of wiring synthesis to calculate the options that
impact each harness. The report is generated if this toggle is selected when Run the
Design Assistant’s checks is clicked. You can specify which design rule checks are run
in the Design Assistant by clicking Configure Checks ( ).
• Report inconsistent harness options
Specifies whether to use a simulation of wiring synthesis to calculate the options that
impact each harness. The report is generated if this toggle is selected when Run the
Design Assistant’s checks is clicked.
The simulation reports on any potential synthesis problems or problems with options on
harnesses. This does not update the harnesses or create any new objects. A summary of
problems is listed in the Design Assistant Output Table and more detailed descriptions
are displayed on the Synthesis tab of the Output Window.
• None / Active Levels / Persisted Configurations / All Configurations
Specifies whether the Signal Route State Calculator that calculates the route state of
signals (routed, unrouted, unconnected, and so on) is run or not when Run the Design
Assistant’s checks is clicked. It also specifies the scope of the calculations:
o None
The Signal Route State Calculator is not run.
o Active Levels
Runs for only the currently active harness levels.

February 2016
Design Assistant
o Persisted Configurations
Runs for the set of configurations that you can see in the Configuration Setting
o All Configurations
Runs for all configurations including those that would be created by the wiring
synthesis option for generating full configurations. These configurations are
generated only temporarily and your data is not changed in any way.
The results are displayed in the Design Assistant Output Table.
This toggle is used in conjunction with Entire Design / Selected Signals.
• Entire Design / Selected Signals
Sets the scope of the Signal Route State Calculator to objects from the entire design or
objects only carrying the signals currently selected in the Design Browser (Design tab).
This toggle is used in conjunction with None / Active Levels / Persisted Configurations /
All Configurations.
• Configure Checks
Opens the Project Preferences dialog box where you specify which design rule checks
are run by the Design Assistant.
• Design Assistant Output Table
Displays the output of the actions performed by the Design Assistant when Run the
Design Assistant’s checks is clicked.
The table includes columns in which you can filter the contents by selecting an item
from the drop-down list at the top. It can be cleared by right-clicking on the tab and
selecting Clear. You can also filter some columns by typing a string into the box in the
column header. This allows you to filter on partial words, and so on.
You can sort the contents of a column by clicking the column header. The columns are:
o Severity
Whether the result is an error ( ), a warning ( ) or an information message ( ).
o Message

February 2016
Design Assistant
Detailed message about what has been identified by a design rule check, the Signal
Route State Calculator or the Harness Option report. You can click an object in the
message to jump to that object in the diagram window.
o Category
Displays Design Assistant to indicate that the row relates to a design rule check.
Depending on the Design Assistant functionality that has been run, this displays:
• Design Assistant if the row relates to a design rule check
• Pre-synthesis if the row relates to the Harness Option report
• Signal Route State if the row relates to the Signal Route State Calculator
o Check
The specific design rule check or Design Assistant functionality that has identified
something in the design.
If it relates to the Signal Route State Calculator, it displays the routed state of the
signals (see “Routed States of Signals” on page 512 for a description of what each
state means).
o Design / Build list
The design or build list in which the functionality has identified something.
o Object
The specific object for which the functionality has identified something.
For flows that use this dialog, see “Running Design Rule Checks in the Design Assistant” on
page 73, “Calculating the Routed State of Signals” on page 514, and “Reporting on Missing or
Inconsistent Options Promoted to Harnesses” on page 455.
Design Assistant (in Preserve Wiring Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649

February 2016
Design Assistant (in Preserve Wiring Mode)
Design Assistant (in Preserve Wiring Mode)

To access: Displayed in the Output Window when you are working in Preserve Wiring Mode
and a topology edit creates a situation where a wire has no valid path.
Use this to view a list of wires that have no valid path.
Objects
Table 23-10. Topology Edits Tab Contents

Field Description
Save to CSV Saves the content of the tab as a comma separated variable (CSV)
file. A dialog box is displayed where you specify the file name and
where you want to save it.
Commit current Deletes any listed wires that have no valid path (leaving any re-
changes instated wires on the design).
Severity Indicates that this is a warning.
Message In the case of a wire with no valid path, this informs you of the
wire, its ends and the harness to which it belongs.
In the case of an unplaced splice, this informs you of the splice and
the bundle where it was placed previously. You may also be
informed that you must place the splice manually; a hyperlink is
displayed to enable moving or placing the splice.
Design objects that exist in the diagram are displayed as
hyperlinks. Click a hyperlink to jump to that object in the Diagram
Window.
Category Indicates that this is Preserved Wiring. That is, wiring that no
longer has a valid path but has not been deleted.
Check Indicates that the type of issue that has been detected (for example,
No Valid Route or Unplaced Splice).
Design/BuildList Indicates the design where the wire has been found.
Object Displays the name of the signal carried by the wire.
Usage Notes
A wire will only be re-instated into the same harness from which it was removed. If a harness
name is changed during the topology edits (for example, by adding "_split"), preserved wires
will not be re-instated until you manually rename the harness. Messages in the Design Assistant
indicate the name of the harness from which each wire was removed.

February 2016
Design Inspector
Tip
When rejoining harnesses split due to topology modifications, adding a bundle from a stub
on the split harness (whether an _split or a newly named harness, for example, H32) to the
remaining section of correctly named harness results in a single harness with the original,
correct name.
Related Topics
Design Inspector
Accessed by pressing Space Bar and entering Show Design Inspector.
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’s functions can be accessed.
The creation and application of plugins is detailed in a separate document called

CustomInspectorDevelopment.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 Capital Integrator, press Status 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
Selecting an Extensibility Plugin from the Plugins Dialog Box
Icons (Glyphs) in Browser Windows

Icons (glyphs) are used for specific objects in the browser windows (for example, the Diagram
tab).
The system modifies object icons in browser windows in certain scenarios.
Table 23-11. Modified Object Icons

Modified Icon Identifies

February 2016
Table 23-11. Modified Object Icons (cont.)

Grayed out slot Indicates no devices have been placed in the slot.
Colored slot Indicates devices have been placed in the slot.
Analysis model An orange circle on an object icon indicates that it has a Capital Analysis
icon model attached to it.
Library part An orange tick on an object indicates that is has a library part assigned to
assigned it.
Shared object A hand under an object icon indicates that the object is shared. If a blue
snowflake is displayed at the top of the icon, it indicates that the shared
object is frozen.
Variant-based In the Logical Designs Browser (Function tab), when variant-based
placement placement has been used for a device, its icon looks like a red device
overlaid by a blue device.

February 2016

February 2016
Chapter 24
Capital Integrator Dialog Box and Field
Reference
This chapter offers a description of the dialog boxes available in the Capital Integrator
application. For each dialog box, all fields are listed, along with a full description of the field’s
function.
Bundle and Harness Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 656
Composite Data Management Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659
Define Harness Levels Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Define Vehicle Models Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
Give Away Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Set Harness Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672
Connector Refinement and Signal Mapping Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . 673
Connector Map Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
Manage Variance Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
Set Variant Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Signal Map Dialog Box for Inline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
Signal Map Dialog Box for Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688
Diagram Creation Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701
Edit Physical Scale Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
Edit Skeleton Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705
Printing Related Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 707
Report Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 708
Connectivity Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
Select Attributes/Properties for Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
Select Inclusion Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714

February 2016
Capital Integrator Dialog Box and Field Reference
Miscellaneous Dialog Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721

Add Selected Logical Design Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Add Wire Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Associate Logical Designs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Capital Integrator design Filter Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Combine Devices Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
Edit Ground Signals Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
Edit Levels Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
Move Wire Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
Name Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
New Property Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Place Device Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
Project Functional Module Codes Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
Select a Module Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
Select Codes for Combination Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
Select Module Code Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
Variant Expression Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760
Capital AutoView Assist for Integrator Dialog Box and Field Reference . . . . . . . . . . . 762
Help Button Landing Pages for Capital Integrator Dialog Boxes. . . . . . . . . . . . . . . . . . 804
Select Integral Harness Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Combine Levels for Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Define Vehicle Models Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
Give Away Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
Set Standardized Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Connector Map Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Fanout Viewer Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Set Variant Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
Signal Map for Interface Connector Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809

February 2016
Signal Map for Slot Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809

Edit Physical Scale Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
Edit Diagram Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
Edit Skeleton Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
Report Material Statistics Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Select Attributes/Properties for Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Select Inclusion Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Select Output for Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Wiring Synthesis Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Add Selected Logical Design Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Add Wire Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Capital Integrator Design Filter Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Combine Devices Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Combine Wires at Cavity Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Edit Levels Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Move Wire Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Place Device Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Select a Module Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
AutoView: Generate Wiring Diagram Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815

February 2016
Bundle and Harness Dialog Boxes
Bundle and Harness Dialog Boxes

This section offers a description of all dialog boxes used to create and edit bundles and
harnesses. For each dialog box, all fields are listed, along with a full description of the field’s
function.
Harness Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657

February 2016
Harness Selection Dialog Box

To access: Press Space Bar and enter Export Harness.
Use this dialog box to export multiple harnesses in XML format from a design.
Description
This action uses Integrator Harness Exchange functionality.
Objects
Table 24-1. Harness Selection Dialog Box Contents

Field Description
Harnesses window Lists the harnesses in the design. Select the ones that you want to
export.
As harness set If you select this, the harnesses are exported as a set in a ZIP file
containing the XML file for each harness.
Select All Selects all of the harnesses in the Harnesses window.
Clear All Unselects all of the harnesses in the Harnesses window.
Related Topics

February 2016
Select Integral Harness Dialog Box
Select Integral Harness Dialog Box

To access: Right-click on a slot connector connected to multiple harnesses in the diagram or in
the Design Browser (Design tab) and select the Include Slot with Harness option from the
pop-up menu. Alternatively, click on the slot connector, press Space Bar, and enter Include
Slot with Harness.
Use this dialog box to select the harness (integral harness) with which you want to include the
slot.
Objects
Table 24-2. Select Integral Harness Dialog Box Contents

Field Description
Harness Select the integral harness with which you want to include the slot.
Mandatory.
Related Topics

February 2016
Composite Data Management Dialog Boxes
Composite Data Management Dialog Boxes

This section offers a description of all dialog boxes used to manage and edit composite data. For
each dialog, all fields are listed, along with a full description of the field’s function.
Define Harness Levels Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663
Define Vehicle Models Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 666
Give Away Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669
Set Harness Options Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672

February 2016
Combine Levels for Dialog Box
Combine Levels for Dialog Box

To access: Click Combine two levels into One ( ) on the Define Harness Levels dialog box.
Use this dialog box to select harness levels that you want to combine with the selected harness
level in the Define Harness Levels dialog box.
Caution
If you are using Capital Level Manager, see “Combine Levels for Dialog Box (Capital
Level Manager)” on page 953.
Objects
Table 24-3. Combine Levels for Dialog Box Contents

Field Description
Available Lists the harness levels that are available for selection. Select the harness
levels and click Add to move them to the Selected window. Click Add All
to move all available harness levels to the Selected window.
Selected Lists the harness levels have been selected. To remove harness levels from
the list, select them and click Remove to move them to the Available
window. To empty the list, click Remove All.
Related Topics
Define Harness Levels Dialog Box

February 2016
Configuration Builder Dialog Box

To access: Press Space Bar and enter Configuration Builder.
Use this dialog box to define a vehicle configuration based on options.
Objects
Table 24-4. Configuration Builder Dialog Box Contents

Field Description
Vehicle Model Select the vehicle model that you want to use.
Configuration The options and valid selections that have been set as optional for the
Builder selected vehicle model are listed at the top of the table. Any options that are
standard or not available for the vehicle model are not displayed because they
are either included or excluded automatically from the vehicle model.
The harnesses and the levels that match the displayed options and valid
selections are displayed in the first column of the table in a tree. At the
bottom of the tree, Capital Integrator lists any existing configurations for the
vehicle model.
If you check the box for an existing configuration, Capital Integrator checks
the boxes for the harness levels included in that configuration. If you then
check or uncheck boxes for harness levels, the box for the existing
configuration becomes unchecked.
The check boxes in the options columns indicate whether a harness level
supports that option.
You can refine the list of harness levels that are displayed by changing the
states of the options listed in the table. To change the state of an option, click
the check box at the top of the option column. The states are:
• This is the default state for each option and means that a harness level
can be displayed whether it is supports this option or not.
• This means that the option is required in the vehicle configuration and
only harness levels that support this option are displayed.
• This means that the option must not be included in the vehicle
configuration and any harness levels that support this option are not
displayed.
Check the boxes for the harness levels that you want to include in a new
configuration. Alternatively, you can check the box for an existing
configuration that you want to use as a basis for a new configuration and then
check or uncheck harness levels as required.
Set Selected Select this if you want to set the new vehicle configuration or selected
Levels Active harness levels as active. When you click OK, the new configuration becomes
active automatically.

February 2016
Table 24-4. Configuration Builder Dialog Box Contents (cont.)

Field Description
Create New Select this to create the new vehicle configuration when you click OK.
Vehicle
Configuration
Related Topics

February 2016

To access: Select a harness in the Design Browser (Design tab), press Space Bar and enter
Levels. Alternatively, right-click on the selected harness and select Define Harness Levels.
Use this dialog box to create and edit harness levels for a selected harness.
Caution
If you are using Capital Level Manager, see “Harness Levels for: Dialog Box” on page 967.
Objects
Table 24-5. Define Harness Levels Dialog Box Contents

Field Description
Set the options that Displays the Set Harness Options Dialog Box where you can select
affect the Harness the options that apply to the harness.
Give away options Displays the Give Away Dialog Box where you specify the giveaway
options for the harness.
Import Levels from Displays the Import Levels dialog where you browse to an XML file
level definition file that contains harness level definitions that you want to import and
click Import.
Export Levels to Level Displays the Export Levels dialog where you browse to the location
definition file where you want to save an XML file that contains the harness level
definitions, specify a file name and click Export.
Add a new Level to the Displays the Add Level dialog where you specify a name for a new
harness harness level and click OK. The harness level is created and a row
for it is added to the Levels table.
Combine two Levels Displays the Combine Levels for Dialog Box where you select
into one harness levels to combine with the harness level that is selected in the
Levels table.
Set the properties for Displays the Edit Properties dialog for the harness level that is
the selected Level selected in the Levels table. See “Editing the Attributes and
Delete the selected Deletes the harness level that is selected in the Levels table.
Level

February 2016
Table 24-5. Define Harness Levels Dialog Box Contents (cont.)

Field Description
Delete all Levels Deletes all harness levels in the Levels table.
Levels Table Lists the existing harness levels for the harness selected in the Design
Level The name of the harness level. The name is displayed in red if there
is a conflict between the vehicle models and options that have been
selected in the table.
Set as Active Specifies whether the harness level is currently active (selected) or
not (unselected).
Model Specifies whether the vehicle model represented by each column is
supported by the harness level (selected) or not (unselected). If you
hold the mouse cursor over a model column, information is displayed
about the variant options and options that are associated with it.
Note: When you select a vehicle model, you are specifying that the
harness level supports the variant options in the vehicle model.
Options Specifies whether the option represented by each column is
supported by the harness level (selected) or not (unselected). If you
hold the mouse cursor over an option column, information is
displayed about inclusive and exclusive options.
The boxes can be the following colors.
White with or without Indicates that the state of this option is OK as it is (selected or
a tick unselected) and will still be OK if changed (that is, select or unselect
it). This can occur only if the option is OPT in the vehicle model. It
also means that there are no issues with inclusive/exclusive
relationships with other options.
Green Indicates that the setting is OK as it is (selected or unselected) but
that there will be an issue if you change the setting (that is, select or
unselect it).
An example of a selected option (with a tick) marked green is one

that is STD in the vehicle model.
An example of an unselected option (without a tick) marked green is
one that is marked as N/A (that is, empty) in the vehicle model.

February 2016
Table 24-5. Define Harness Levels Dialog Box Contents (cont.)

Field Description
Red Indicates that there is an issue with the setting.
Possible issues are:
• The option is active on the harness level, but is unavailable on
any vehicle models supported by the level.
• The option is inactive on the harness level, but is standard on a
vehicle model supported by the level.
• The option is inactive on the harness level, but is included by
another option that is active on the level.
If an option is selected (with a tick), unselecting it will normally fix
the issue. If an option is unselected (without a tick), selecting it will
normally fix the issue.
In both cases, there may be some scenarios where there is no viable
setting of an option to other option settings.
Related Topics

February 2016
Define Vehicle Models Dialog Box

To access: Press Space Bar and enter Models.
Use this dialog box to view and define vehicle models.
Objects
Table 24-6. Define Vehicle Models Dialog Box Contents

Field Description
Add a new Vehicle Enables you to manually add a new vehicle model to the Model table.
Model Displays the Add Model dialog box where you specify the vehicle
model name.
Delete the selected Deletes the vehicle model that is currently selected in the Model table.
Vehicle Model(s)
Set Standardized Displays the Set Standardized Options Dialog Box.
Options Use this dialog box to specify the platform options that are standard
within the project. Components tagged with these option codes must be
included on all physical harnesses.
Model table Contains one row for each of the existing vehicle models.
Variants This section of the Model table contains one column for each of the
available Variant Options. In a vehicle model row, select the boxes for
the variant options that the vehicle model includes.

February 2016
Table 24-6. Define Vehicle Models Dialog Box Contents (cont.)

Field Description
Option Folders and This section of the Model table contains one column for each available
Options Option that can be included in the vehicle models. The option columns
are grouped based on the Option Folders to which they belong.
In a vehicle model row, specify whether an option is:
• STD
The option is always included in the Vehicle Model. This option is
therefore ALWAYS present. Although the electrical system design
allows for versions of the final product to be produced without the
option, the product will not be offered without the option.
For example, product marketing may decide to make 4W ABS
standard. No vehicles will be offered without 4W ABS.
• OPT
The option can be supported by the Vehicle Model and the final
product is available with or without the option. This increases the
harness complexity required to support the final product, since
different harness levels may be required to support vehicles with the
option and those without the option.
• Blank
The option is not supported by the Vehicle Model. Although the
option has been captured as part of the electrical system design, the
option will not be offered on the final product. More often than not,
options are not available for specific vehicles, for example, Power
Moonroof is not available on convertible vehicles.
Note: If an option is standard for a model, any inclusive options for that
parent option must also be standard for the model. Similarly, if an
option is optional for a model, any inclusive options must be either
optional or standard.
If a cell is red, this indicates that there is an issue with the setting.
Possible issues are:
• The option is inactive on the vehicle model, but is included by
another option that is active on the model.
• The option is standard or optional in the vehicle model, but is
exclusive with another option that is standard on the model.
NOTE: In the second scenario, you can include two exclusive options in
the same vehicle model, but they must both be marked as OPT. If one is
STD, the other must be unavailable.

February 2016
Table 24-6. Define Vehicle Models Dialog Box Contents (cont.)

Field Description
Option This section of the Model table contains one column for each available
Combinations valid selection that can be included in vehicle models. See “Option
Combination” on page 344 for a description of option combinations and
valid selections (including examples).
In a vehicle model row, select the boxes for the option combinations
that the vehicle model includes.
Move selected Move the selected vehicle model row in the Model table up or down.
Model to top /
Move selected
Model up / Move
selected Model
down / Move
selected Model to
bottom
Related Topics
Vehicle Model

February 2016
Give Away Dialog Box

To access: Click Give away options ( ) on the Define Harness Levels dialog box.
Use this dialog box to specify the giveaway options for a harness.
Objects
Table 24-7. Give Away Dialog Box Contents

Field Description
Available Lists the options that are available for the harness. Select the
options that you want to specify as giveaway options and click
Add to move them to the Selected window. Click Add All to
move all available options to the Selected window.
To add an option to the Selected window, you can also:
• Double-click it
• Drag and drop it
If you want to specify giveaway options that must be given away
together, select them and click New Group to move them to the
Selected window where they are displayed in a group folder (see
“Usage Example - Giving Away Together Two Mutually-
Exclusive Options on a Harness” on page 375).
If a group is selected in the Selected window when you click Add
or Add All, the options are added to that group in the Selected
window.
Selected Lists the options that have been specified as giveaway options. To
remove options from the list, select them and click Remove to
move them to the Available window. To empty the list, click
Remove All.
To remove an option from the Selected window, you can also:
• Double-click it
• Drag and drop it to the Available window.
If options are displayed within a folder, those are giveaway options
that must be given away together. You can rename the folders.
You can drag and drop options within the Selected window to
move them in or out of folders.
Filter Located below the Available and Selected lists. Enter a series of
characters. A filter is applied to the list so that only options with
names containing that series of characters are listed.

February 2016
Table 24-7. Give Away Dialog Box Contents (cont.)

Field Description
Recalculate Calculates the estimated number of harness levels that will result
when composite wiring syntheses is run for this harness with the
specified giveaway options. The number is displayed as the
Estimated Level Count below the Available window.
Note: The Estimated Level Count cannot exceed 1,000,000. If
the calculation reaches this figure, it stops.
Related Topics
Specifying Giveaway Options

February 2016
Set Standardized Options Dialog Box
Set Standardized Options Dialog Box

To access: Press Space Bar and enter Models to display the Define Vehicle Models dialog box,
and click the Set Standardized Options ( ) button.
Use this dialog box to specify the platform options that are supplied as standard within the
vehicles in the project. Components tagged with these option codes must be included on all
physical harnesses.
Objects
Table 24-8. Platform Options Dialog Box Contents

Field Description
Available Lists the available options that are not currently platform in a
tree structure. To specify an option as platform, select it and
click Add; the option moves to the Selected window.
Standardized Lists the options that have been specified as platform in a tree
structure. To specify an option as no longer platform, select it
and click Remove; the option moves to the Available window.
Filter Located below the Available and Selected lists. Enter a series of
characters. A filter is applied to the list so that only options with
names containing that series of characters are listed.
Related Topics

February 2016
Set Harness Options Dialog Box
Set Harness Options Dialog Box

To access: Click Set the options that affect the Harness ( ) on the Define Harness Levels
dialog box.
Use this dialog box to select options that apply to a harness.
Caution
If you are using Capital Level Manager, see “Set Harness Options Dialog Box (Capital
Level Manager)” on page 974.
Objects
Table 24-9. Set Harness 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 window. Click Add All to move
all available options to the Selected window.
Selected Lists the options have been selected. To remove options from the list, select
them and click Remove to move them to the Available window. To empty
the list, click Remove All.
Related Topics

February 2016
Connector Refinement and Signal Mapping Dialog Boxes

Dialog Boxes
This section offers a description of all input dialog boxes used in connector refinement and
signal mapping. For each dialog box, all fields are listed, along with a full description of the
field’s function.
Connector Map Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674
Manage Variance Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677
Set Variant Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678
Signal Map Dialog Box for Inline . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 680
Signal Map Dialog Box for Interface Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 688

February 2016
Connector Map Dialog Box
Connector Map Dialog Box

To access: Right-click a slot that contains a device with a footprint in the Design Browser
(Design tab) or Diagram Window and select Connector Map. Alternatively, click on the
slot, press Space Bar and enter Connector Map. This option is not available if there is no
device with a footprint in the slot.
Use this dialog box to map footprint connectors to the device and harness connectors on the slot.
Objects
Table 24-10. Connector Map Dialog Box Contents

Field Description
Footprint Mappings Displays the footprint connectors for devices in the slot and the
table harness/device connectors to which they are mapped. Read-only.
Footprint - Device Displays the name of the device with a footprint. Read-only.
Footprint - Displays the name of the footprint connector. Read-only.
Connector
Slot Connector - Displays the name of the harness connector to which the footprint
Harness connector is mapped. Click on the field to display a drop-down list
from which you can select a harness connector or create a new harness
connector. You can rename any new harness connector after editing the
map. For existing harness connectors, the list also displays the harness
on which it is located.
Slot Connector - Displays the name of the device connector to which the mapped
Device harness connector is mated. Read-only.
Harness Displays the name of the harness on which the slot connector (and
harness connector) are located. Read-only.
Library Information Displays library part information for the device, footprint connector
table and harness connector.
Name Displays the name of the device or connector. Read-only.
Part No. Displays the component part number that has been assigned to the
device or connector. Read-only.
No. of Cav./Pins Displays the number of cavities or pins on the device/connector. Read-
only.
View Click the button to display a Details dialog box where you can view all
of the library details for the Part No.
Related Topics
on a Slot

February 2016

To access: Click the Show Fanout button on the top right of a Signal Map dialog box.
Use this dialog box to create a fanout diagram for the specialized connectors s in a generalized
connector. The fanout diagram allows you to reorder the connectors, add new bundle nodes and
define the length of the bundles.
Objects
Table 24-11. Fanout Viewer Dialog Box Contents

Field Description
Node tree Displays a node tree for the Specialized Connectors of the
Generalized Connector. The node tree is displayed as a graphic
in the Fanout diagram. By default, the specialized connectors
are listed under the top node.
Each node ( ) represents a bundle section.
You can add a new bundle section to the end of an existing one
by right-clicking on it and selecting New Node. The new
bundle section node is added below the existing node in the
Node tree. In the Fanout diagram, the new bundle section is
added:
• Leading straight on from the selected bundle section if no
bundle section is already attached
• Branching off from the end of the selected bundle section if
another bundle section is already attached
If a bundle section node has no other bundle node or
specialized connector attached at the end, you can delete it by
right-clicking on it and selecting Remove Node.
To move a specialized connector from one bundle segment to
another, drag and drop the connector.
To specify the length of a bundle segment, select its node
( ) and enter a Length in the standard unit of
measurement used by your company.
Length Specifies the length of the bundle segment node ( )
selected in the Node tree. The length is specified in your
company’s standard unit of measurement. Zero (0) is a valid
length. Mandatory.

February 2016
Table 24-11. Fanout Viewer Dialog Box Contents (cont.)

Field Description
Fanout diagram Displays a graphical representation of the Node tree specified
for the Specialized Connectors of the Generalized Connector.
The specified Length of a bundle node is displayed next to it.
Select a bundle segment node ( ) or specialized
connector in the Node tree to highlight it in the fanout diagram.
Usage Notes
If you are editing an inline pair, a Node tree and Fanout diagram are displayed for each inline
half.
This dialog box can be left open while editing the Signal Map Dialog Box for Inline or Signal
Map Dialog Box for Slot. If a connector mating is selected in the Connector Mating table, the
connectors are highlighted in the Node tree and Fanout diagram.
Related Topics
Signal Map Dialog Box for Inline
Signal Map Dialog Box for Interface Connector
Signal Map Dialog Box for Slot

February 2016
Manage Variance Dialog Box

To access: With one or more signals or wires selected, click the Manage Variance button ( )
on the Signal Mappings tab of a Signal Map dialog box. This dialog box has the heading
Signal <Signal Name> or Multiple signals.
Use this dialog box to define variant option expressions for the selected signals or wires.
Objects
Table 24-12. Manage Variance Dialog Box Contents

Field Description
Add a new Displays the Set Variant Dialog Box where you define a variant
option option expression to apply to the selected signals or wires. Once
defined, the variant option expression is added to the Variant
option expression list.
Edit selected Displays the Set Variant Dialog Box where you can edit the variant
option option expression selected in the Variant option expression list.
Delete selected Deletes the variant option expression selected in the Variant option
options expression list.
Variant option Lists the variant option expressions that have been defined for the
expression list selected signals or wires in the Signal Map Dialog Box for Inline,
Signal Map Dialog Box for Interface Connector or Signal Map
Dialog Box for Slot.
Related Topics
Inline
Slot or Inline

February 2016
Set Variant Dialog Box

To access: Click either the Create Variant Connector ( ) button on a Signal Map dialog box,
or the Add a new option ( ) button or the Edit selected option ( ) button on the
Manage Variance dialog box.
Use this dialog box to define a variant option expression.
Objects
Table 24-13. Set Variant Dialog Box Contents

Field Description
Options Lists all applicable options assigned to the design. To add an
option to the expression, double-click the option name.
Mandatory.
Operators The mathematical symbols available from which you can construct
an option expression. Optional.
To add an operator to the expression, 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]
appears on those derivatives with either option assigned.
• ! [not]
appears on only those derivatives without the option assigned.
• (X and Y)
An opening and closing parenthesis. Enclosing a subset of an
option expression in parentheses allows 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 also have the option to type an expression
into this field instead of selecting from the lists above. The
expression is displayed in red if it is not valid. Mandatory.
Related Topics

February 2016
Inline
Slot or Inline

February 2016

To access: Select an inline half in the Diagram Window or Design Browser (Design tab) and
either right-click on the selected object and select Signal Map, or press Space Bar and enter
Signals.
Use this dialog box to refine inline halves and map signals between the cavities on them.
Objects
Table 24-14. Signal Map Dialog Box for Inline Contents

Field Description
Connector Mating Table Displays the Generalized Connectors (inline connectors)
Located at top of dialog box. and is used to define the Specialized Connectors for each
side of the inline half and to mate them with each other.
Each row represents a mating of a connector on one inline
half with a connector on the other inline half. By default, the
table is split into two sections by the connector splitter ( )
column. The fields on either side of this represent the two
halves of the inline pair.
Duplicate matings are not allowed. If you create duplicates,
they are displayed in red and the OK button for the dialog
box is disabled.
To sort the table rows based on the contents of a column,
click on the column header.
To select which columns you want displayed in the table,
right-click on a column header and select/unselect the
column names as required.
Add Connector Mapping When a connector cell is selected in the Connector Mating
Table (on the left or the right half of the inline), this adds a
new row. The row represents a new Specialized Connector
on the same inline half as the selected connector cell. By
default, its name is prefixed by the name of its parent
connector. You can mate this new specialized connector
with another one on the other inline half. Enabled only if a
connector field is selected in the Connector Mating Table.
Delete Connector Mapping When a connector mating row is selected in the Connector
Mating Table, this deletes that row. If no other mating exists
for either connector in the row, one or both of those
connectors is also deleted from the system. If all but one
Specialized Connector has been deleted for a Generalized
Connector, the remaining specialized connector is deleted
and replaced by the generalized connector. Any attributes
are transferred to the generalized connector. Enabled only if
a connector field is selected in the Connector Mating Table.

February 2016
Table 24-14. Signal Map Dialog Box for Inline Contents (cont.)
Field Description
Create Variant Connector When a connector is selected in the Connector Mating
Table, this creates a variant connector based on that selected
connector. Clicking this button displays the Set Variant
Dialog Box where you specify the variant option expression
that applies to the variant connection. When you then click
OK, a new row for the variant connector is added to the
Connector Mating Table. The variant connector has the
same part number and number of pins as the original
connector. For the variant connector, the Signal Mappings
tab contains a row for each cavity. These cavities have the
same signals and wires mapped to them as the original
connector cavities but will have the new variant option
expression applied to them.
Show Fanout Displays the Fanout Viewer Dialog Box that allows you to
create a Fanout diagram of the Specialized Connectors in a
Generalized Connector (inline connectors). The fanout
diagram allows you to reorder the connectors, add new
bundle nodes and define the length of the bundles. The
Fanout Viewer Dialog Box can be left open alongside this
dialog box.
Connector A unique identifier for a Generalized Connector or
(Column header) Specialized Connector. Either:
• enter a new identifier to rename the connector
• select the identifier for an existing connector from the
drop-down list
Part Number Specifies a library part for the Generalized Connector or
(Column header) Specialized Connector in the Connector column. Click the
field and click the ellipsis (...) button in the field to display
the Part Selection Dialog Box where you can select a library
part.
If a library part is already selected, you can:
• right-click on the field and click Update Library Part
to update it with the latest details for it from Capital
Library
• right-click on the field and select Remove Library Part
to remove the library part association from the
specialized connector

February 2016
Field Description
No. of Cavities Specifies the number of cavities on the Generalized
(Column header) Connector or Specialized Connector in the Connector
column. If a Part Number is selected, this is read-only. If no
part number is selected, enter the number of cavities
manually. If you reduce the number of cavities to less than
the number of used cavities, cavities are deleted, starting
with the highest cavity in an alphanumeric sorted list. Any
wires that mapped to the deleted cavities are listed as
unmapped and the OK button is disabled until the wires are
re-mapped. If a specialized cavity is deleted and the
generalized cavity to which it maps has no other
specializations (and no wiring terminates at it), the
generalized cavity is also deleted.
Connector Splitter Splits the table between the two halves of the inline pair.
Click the Select both halves icon to select both halves in
the row.
Clear Selection Clears any selection that you have made in the connector
mating table at the top of the dialog box.
Signal Mappings tab Used to map signals and wires between the cavities of
connectors on each inline half.
Each row represents a signal and wire mapping between
connector cavities on both halves of the inline. If no
connector mating row is selected in the Connector Mating
table (at the top of the dialog box), all mappings for all
connectors are displayed. If a connector mating row is
selected, only the mappings that apply to the connectors in
that row are displayed.
The table is divided into two sections by the Preferred
Signal column. The fields on either side of this apply to the
connector cavities on either side of the inline. If you are
working in multi user mode (Harness Concurrency) and you
have the lock on both halves of the inline, any changes to
wire / signal assignment on one half will also change the
other half.
Duplicate Cavity Creates a new row that is a duplicate of the currently
selected mapping row.
Delete Copied Row Deletes the selected duplicate row from the table. Enabled
only if you have selected a duplicate row.

February 2016
Field Description
Auto-Set Preferred Signal Automatically sets the preferred signal on every generalized
cavity based on the signal(s) connected to the cavity
(including via specialized cavities). If this results in an
ambiguous result (that is, multiple signals), the preferred
signal is not set.
Manage Variance Displays the Manage Variance Dialog Box where you
specify variant option expressions for the currently selected
mapping rows and thereby create variant signals and wires.
Status Column Displays an error or warning symbol if there is an issue with
(Blank column header at start of the mapping. Move your mouse over the symbol to view a
table) brief description of the issue.
Connector Displays the name of a Generalized Connector or

(Column header) Specialized Connector from the Connector Mating table.
Read-only.
Cavity Displays the name of a cavity or backshell termination ( )
(Column header) on the connector. Read-only.
You can right-click on a cavity in this column and select
Properties to view the attributes and properties for it.
Harness Displays the name of the harness owning the connector.
(Column header) Read-only.
Signal Specifies the signal traveling between the connector cavities

(Column header) from the Cavity columns. Click this field and select the
signal name from the drop-down list. Mandatory.
Wire Displays the wire that is carrying the Signal and is mapped
(Column header) to the connector cavity in the Cavity column. Editable by
double-clicking only if there are multiple wires for the
signal, otherwise read-only.
Preferred Signal If wiring has not yet been synthesized, you can select a
(Column header) preferred signal for the Cavity in this row. Wiring synthesis
will map that signal to this cavity as a preference rather than
using an unassigned cavity or creating a new cavity. If you
are working in multi user mode (Harness Concurrency), the
first user to lock a half of the inline can edit this. You can
use the Auto-Set Preferred Signal button to populate this
column. Optional.

February 2016
Field Description
Cavity Matings tab Used to mate the cavities of the mated connectors from the
Connector Mating table. Each row represents a mating of
two cavities. The table is divided into two sections (one for
each of the mated cavities) between the Cavity columns.
By default, the cavity matings are inferred from the Signal
Mappings tab.
If no connector mating row is selected in the Connector
Mating table, all cavity mappings for all of the connectors
are displayed.
If a connector mating row is selected in the Connector
Mating table, cavity matings only for the selected connector
pair are displayed. If the selected row contains only one
inline half, only that connector and its cavities are displayed
on this tab and the fields are read-only because there is no
cavity mating to do.

click on the column header. To select which columns you
want displayed in the table, right-click on a column header
and select/unselect the column names as required.
Read-only if a mating for the inline pair has been defined in
Capital Library or if only one inline half is locked by the
user.
(Blank column header at start) the cavity mating. Move your mouse over the symbol to
view a brief description of the issue. For example, an error
symbol is displayed for a duplicate cavity mating.
(Column header) Specialized Connector from the Connector Mating table.
The two connectors specified in a row are mated. Read-
only.

February 2016
Field Description
Cavity Displays the name of a cavity on a connector. The two
(Column header) cavities specified in a row are mated.
To change the cavity for this mating, either:
• click on the table cell and select an existing cavity name
from the drop-down list. If the selected cavity is used in
another cavity mating row, the previous value from the
row being edited moves to that row.
• enter a new name for the cavity and press Enter; the old
cavity name is updated to the new name wherever used
in this table. Not possible if the connector has a library
part.
Wire Info tab Displays details of the wires connecting to the connectors
from the Connector Mating table. Each row represents a
wire.
Mating table, all wires connecting to all of the connectors
are displayed.
Mating table, wires connecting to only the selected mated
connectors are displayed.
You can right-click on a row for a wire and select Wire
Properties to view and edit the properties for the wire,
including its library part.
Set Variance Displays the Set Variant Dialog Box where you can specify
a variant option expression for the wire currently selected
on the Wire Info tab. If you specify this, the wire becomes
a Variant Wire. You can select multiple rows on the tab to
specify the same variant option expression for multiple
wires. Optional, enabled only when a wire row is selected
on the Wire Info tab.
(Blank column header at start) the wire. Move your mouse over the symbol to view a brief
description of the issue.
Harness The harness to which the wire belongs. Read-only.
(Column header)

February 2016
Field Description
Connector/Hole The connector to which the wire is connected. Read-only.
(Column header)
Cavity/Backshell The connector cavity or backshell through which the wire
(Column header) passes. Read-only.
Signal The signal carried by the wire. Read-only.

(Column header)
Wire The name of the wire. Read-only.
(Column header)
Part The library part assigned to the wire. Read-only.
(Column header)
Spec The specification of the wire. Read-only.
(Column header)
Material The material of the wire. Read-only.
(Column header)
Color The color of the wire. Read-only.
(Column header)
Variant The variant option expression for a variant wire. Optional,
(Column header) read-only here, edited by clicking Set Variance.
Option Expression The option expression on the wire. Read-only.

(Column header)
Module Code The module code of the wire. Read-only.
(Column header)
To The object and pin to which the wire connects at the other
(Column header) end. Read-only.
OK Closes the dialog box. Disabled if any wires are unmapped.
Related Topics

February 2016
Inline
Slot or Inline

February 2016

To access: Select an interface connector in the Diagram Window or Design Browser (Design
tab) and either right-click on the selected object and select Signal Map, or press Space Bar
and enter Signals.
Use this dialog box to refine an interface connector and map signals to connector cavities.
Objects
Table 24-15. Signal Map Dialog Box for Interface Connector Contents
Field Description
Connector Table Displays the Generalized Connector (interface connector)
and is used to define the Specialized Connectors for it.
Each row represents a connector (either generalized or
specialized).
If you create duplicate matings, they are displayed in red
and the OK button for the dialog box is disabled.
Add Connector Mapping When a connector name is selected in the Connector
column, this adds a new row. The row represents a new
Specialized Connector. By default, its name is prefixed by
the name of its parent connector. Enabled only if a
Connector field is selected in the Connector Table.
Delete Connector Mapping When a connector row is selected in the Connector table,
this deletes that row.
If all but one Specialized Connector has been deleted for a
Generalized Connector, the remaining specialized
connector is deleted and replaced by the generalized
connector. Any attributes are transferred to the generalized
connector. Enabled only if a Connector field is selected in
the Connector Table.

February 2016
Table 24-15. Signal Map Dialog Box for Interface Connector Contents (cont.)
Field Description
Create Variant Connector When a connector is selected in the Connector Table, this
creates a variant connector based on that selected connector.
Clicking this button displays the Set Variant Dialog Box
where you specify the variant option expression that applies
to the variant connection. When you then click OK, a new
row for the variant connector is added to the Connector
Table. The variant connector has the same part number and
number of pins as the original connector. For the variant
connector, the Signal Mappings tab contains a row for each
cavity. These cavities have the same signals and wires
mapped to them as the original connector cavities but will
have the new variant option expression applied to them.
create a Fanout diagram of the Specialized Connectors of
the Generalized Connector (interface connector). The
fanout diagram allows you to reorder the connectors, add
new bundle nodes and define the length of the bundles. The
Fanout Viewer Dialog Box can be left open alongside this
dialog box.
Connector A unique identifier for a Generalized Connector or
(Column header) Specialized Connector. Either:
drop-down list
Part Number Specifies a library part for the Generalized Connector or
(Column header) Specialized Connector in the Connector column. Click the
part.
• click the ellipsis (...) button to display the Details Dialog
Box where you can view the details of the library part
Library

February 2016
Field Description
No. of Cavities Specifies the number of cavities on the Generalized
(Column header) Connector or Specialized Connector in the Connector
column. If a Part Number is selected, this is read-only. If no
part number is selected, enter the number of cavities
manually. If you reduce the number of cavities to less than
the number of used cavities, cavities are deleted, starting
with the highest cavity in an alphanumeric sorted list. Any
wires that mapped to the deleted cavities are listed as
unmapped and the OK button is disabled until the wires are
re-mapped. If a specialized cavity is deleted and the
generalized cavity to which it maps has no other
specializations (and no wiring terminates at it), the
generalized cavity is also deleted.
Clear Selection Clears any selection that you have made in the connector
mating table at the top of the dialog box.
Signal Mappings Table Used to map signals to the cavities of the Generalized
Connector and Specialized Connectors of the interface
connector being edited.
Each row represents a signal mapping to a connector cavity.
Table, all mappings for all connectors are displayed. If a
connector mating row is selected, only the mappings that
apply to the connector in that row are displayed.
selected mapping row.
specify variant option expression for the currently selected
(Blank column header at start) the mapping. Move your mouse over the symbol to view a
brief description of the issue.
(Column header) Specialized Connector from the Connector Table. Read-
only.
Cavity Displays the name of a cavity or backshell termination ( )
(Column header) on the connector in the Connector column. Read-only.

February 2016
Field Description
Harness Displays the name of the harness owning the connector in
(Column header) the Connector column. Read-only.
Signal Specifies the signal mapped to the cavity in the Cavity

(Column header) column. Either:
• click this field and select the name of an existing signal
from the drop-down list
• enter the name of a new signal
Mandatory.
Option Expression Specifies the option expression for the connector cavity in
(Column header) the Cavity column. The system uses this to determine
whether or not to route a signal to this cavity. Click the field
and click the ellipsis (...) button in the field to display the
Edit Option Expression dialog box where you can edit the
option expression.
Editable only when the Signal column contains a signal.
OK Closes the dialog box.
Related Topics

February 2016

To access: Select a slot connector, ring terminal, hole or slot in the Diagram Window or Design
Browser (Design tab) and either right-click on the selected object and select Signal Map, or
press Space Bar and enter Signals.
Use this dialog box to refine slot connectors on a slot and map signals to connector cavities, ring
terminals and holes in a slot.
Objects
Table 24-16. Signal Map Dialog Box for Slot Contents

Field Description
Connector Mating Table Displays the devices, holes, Generalized Connectors (slot
connectors) and ring terminals on the slot. This table can be
used to define the Specialized Connectors for the
generalized connectors, as well as to mate them with device
connectors and backshells. Read-only rows represent the
devices in the slot. Other rows represent holes, ring
terminals or the mating of a harness connector with a device
connector and backshell (as required).
If you create duplicate matings, they are displayed in red
and the OK button for the dialog box is disabled.
Add Connector Mapping When a connector name is selected in the Name column,
this adds a new row. The row represents a new Specialized
Connector. By default, its name is prefixed by the name of
its parent connector. You can mate this new specialized
connector with a device connector and backshell (as
required). Enabled only if a Name field is selected in the
Connector Mating Table. Disabled if the connector has a
footprint.

February 2016
Table 24-16. Signal Map Dialog Box for Slot Contents (cont.)
Field Description
Delete Connector Mapping When a connector row is selected in the Connector Mating
Table, this deletes that row. If the row contains a slot
connector, that connector is deleted from the system.
If all but one Specialized Connector has been deleted for a
Generalized Connector, the remaining specialized
connector is deleted and replaced by the generalized
connector. Any attributes are transferred to the generalized
connector. Enabled only if a Name field is selected in the
Connector Mating Table. Disabled if the connector has a
footprint.
Create Variant Connector When a connector is selected in the Connector Mating
Table, this creates a variant connector based on that selected
connector. Clicking this button displays the Set Variant
Dialog Box where you specify the variant option expression
that applies to the variant connection. When you then click
OK, a new row for the variant connector is added to the
Connector Mating Table. The variant connector has the
same part number and number of pins as the original
connector. For the variant connector, the Signal Mappings
tab contains a row for each cavity. These cavities have the
same signals and wires mapped to them as the original
connector cavities but will have the new variant option
expression applied to them. Disabled if the connector has a
footprint.
create a Fanout diagram of the Specialized Connectors of
the Generalized Connector (slot connector) to which the
currently selected connector belongs. The fanout diagram
allows you to reorder the connectors, add new bundle nodes
and define the length of the bundles. The Fanout Viewer
Dialog Box can be left open alongside this dialog box.
Object Type Indicates the type of object represented in the row: device
( ), connector ( ), ring terminal ( ) or hole ( ).

February 2016
Field Description
Name A unique identifier for the device, hole, ring terminal,
(Column header) Generalized Connector (slot connector) or Specialized
Connector.
For a connector or ring terminal, either:
drop-down list
For a hole, specify a unique identifier.
For a device, this is read-only.
Part Number Specifies a library part for the object in the Name column.
(Column header) For a device, this is read-only.
For a hole, this is not used.
For a connector:
Click the field and click the ellipsis (...) button in the field to
display the Part Selection Dialog Box where you can select
a library part.
Library
Device Connector Part Number Specifies a library part for the device connector with which
(Column header) you want to mate the object in the Name column. Click the
part.
Library
Disabled for a device or hole.

February 2016
Field Description
Backshell Part Number Specifies a library part for the backshell with which you
(Column header) want to mate the object in the Name column. Click the field
and click the ellipsis (...) button in the field to display the
Part Selection Dialog Box where you can select a library
part.
Library
Disabled for a device or hole.
Number of Pins Specifies the number of pins on the object in the Name
(Column header) column.
For a device, ring terminal or hole, this is read-only.
For a connector:
If a Part Number is selected, this is read-only. If no part
number is selected, enter the number of pins manually.
Signal Mappings tab Used to map signals and wires to holes, connector cavities
or ring terminals in the slot.
Each row represents a signal mapping to a connector cavity,
hole or ring terminal. If no row is selected in the Connector
Mating Table, all mappings for all connectors are displayed.
If a row is selected, only the mappings that apply to the
object in that row are displayed.
If you are working in multi user mode, a row will have a
gray background if a connector in it is locked by another
user.
selected mapping row. This enables you to map:
• Multiple connector cavities to the same slot device pin
• Multiple ring terminals to the same stud pin
Each mapping has a separate row.

February 2016
Field Description
Unmap Internal Signal Unmaps any internal signal candidates in the slot. Not
Candidates available if there are no internal signal candidates.
Auto Map Cavities Automatically maps a set of signals to cavities from a
particular connector.
Before clicking this, select a mapping row on the Signal
Mappings tab where you select a Connector and Cavity for
that mapping.
When you then click this button, the subsequent cavities
from the connector are mapped in the rows directly below
the selected row.
For example, if you specified cavity 3 in the selected
mapping row and the connector has ten cavities, the cavities
4 to 10 are mapped in the rows below the selected row. If
only four rows are available below the selected row, only
cavities 4 to 7 would be mapped.
Any rows that are read-only (for example, due to footprints)
are skipped by the automatic mapping.
specify variant option expression for the currently selected
(Blank column header at start) the mapping. Move your mouse over the symbol to view a
brief description of the issue.
Connector Displays the name of a hole, ring terminal, Generalized
(Column header) Connector or Specialized Connector from the Connector
Mating Table. Mandatory.
To change the object for this mapping, click on the table
cell and select a hole, ring terminal or connector name from
the drop down list.
Cavity Displays the name of a cavity on the connector or ring
(Column header) terminal in the Connector column. Mandatory.
To change the cavity for this mapping, either:
• click on the table cell and select an existing cavity name
from the drop-down list. Selecting a cavity that has
already been used will not swap the mapping but leaves
both rows mapped to the same cavity.
• enter a new name for the cavity; the old cavity name is
updated to the new name wherever used in this table.
Not possible if the connector has a library part.

February 2016
Field Description
Harness Displays the name of the harness owning the object in the
(Column header) Connector column. Read-only.
ISC If a signal only connects to devices within a single slot, then

it is an internal signal candidate. That is, it may be fully
implemented inside the slot and may not need to be mapped
to another cavity.
An example is when you have some devices (such as fuses)
that are connected in a series. The signal joining these fuses
does not need to be routed as long as both fuses are in the
same slot.
The system also takes variant placement into account. If the
fuses are both placed in one slot with option expression
LHD and in another slot with option expression RHD, then
the signal is still an internal signal candidate.
Signal Specifies the signal mapped to the object cavity in the
(Column header) Cavity column. Read-only.
Wire Displays the wire that is carrying the Signal and is mapped
(Column header) to the object cavity in the Cavity column. Editable only if
there are multiple wires for the signal, otherwise read-only.
Pin Displays the name of the device pin to which the Signal is
(Column header) mapped. Read-only.
Device Displays the name of the device to which the Signal is

(Column header) mapped. Read-only.
Slot instance filter Filters the contents of the Signal Mappings tab so that only
connectors and holes on the selected instance of the slot are
displayed. You can toggle this setting to display all
connectors and holes on all instances of the slot.
Active Wiring Filter Filters the contents of the Signal Mappings tab so that only
wiring that is currently active in the diagram is displayed.
Connected cavities filter Filters the contents of the Signal Mappings tab so that only
connected cavities are displayed.

February 2016
Field Description
Wire Info tab Displays details of the wires connecting to the connectors,
ring terminals and holes from the Connector Mating Table.
Each row represents a wire.
Mating Table, all wires connecting to all of the objects are
displayed.
Mating Table, wires connecting to only the selected objects
are displayed.
You can right-click on a row for a wire and select Wire
Properties to view and edit the properties for the wire,
including its library part.
Set Variance Displays the Set Variant Dialog Box where you can specify
a variant option expression for the wire currently selected
on the Wire Info tab. If you specify this, the wire becomes
a Variant Wire. You can select multiple rows on the tab to
specify the same variant option expression for multiple
wires. Optional, enabled only when a wire row is selected
on the Wire Info tab.
(Blank column header at the the wire. Move your mouse over the symbol to view a brief
start) description of the issue.
Harness The harness to which the wire belongs. Read-only.

(Column header)
Connector/Hole The connector, ring terminal or hole to which the wire is
(Column header) connected. Read-only.
Cavity/Backshell The connector/ring terminal cavity or backshell through

(Column header) which the wire passes. Read-only.

February 2016
Field Description
ISC If a signal only connects to devices within a single slot, then
it is an internal signal candidate. That is, it may be fully
implemented inside the slot and may not need to be mapped
to another cavity.
An example is when you have some devices (such as fuses)
that are connected in a series. The signal joining these fuses
does not need to be routed as long as both fuses are in the
same slot.
The system also takes variant placement into account. If the
fuses are both placed in one slot with option expression
LHD and in another slot with option expression RHD, then
the signal is still an internal signal candidate.
Signal The signal carried by the wire. Read-only.
(Column header)
Device The device to which the wire connects. Read-only.
(Column header)
Pin The pin to which the wire connects. Read-only.
(Column header)
Wire The name of the wire. Read-only.
(Column header)
Part The library part assigned to the wire. Read-only.
(Column header)
Spec The specification of the wire. Read-only.
(Column header)
Material The material code of the wire. Read-only.
(Column header)
Color The color code of the wire. Read-only.
(Column header)
Variant The variant option expression for a variant wire. Optional,
(Column header) read-only here, edited by clicking Set Variance.
Option Expression The option expression on the wire. Read-only.

(Column header)
Module Code The module code of the wire. Read-only.
(Column header)

February 2016
Field Description
To The object and pin to which the wire connects at the other
(Column header) end. Read-only.
OK Closes the dialog box. Disabled if any wires are unmapped.
Related Topics
Inline
Slot or Inline

February 2016
Diagram Creation Dialog Boxes
Diagram Creation Dialog Boxes

This section offers a description of all dialog boxes used to create diagrams (not the diagram
content). For each dialog box, all fields are listed, along with a full description of the field’s
function.
Edit Physical Scale Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702
Edit Skeleton Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705

February 2016
Edit Physical Scale Dialog Box
Edit Physical Scale Dialog Box

To access: With a diagram open, press Space Bar and enter Physical Scale.
Use this dialog box to specify the physical scale of a topological diagram.
Description
The default lengths of the bundles as drawn in an Integrator diagram are based on the physical
scale of the diagram. The physical scale is the distance between grid points which is used for
calculating bundle lengths in the diagram.
The physical scale does not effect the size of the diagram when it is printed. You must set the
project preferences to specify the scale for a printout of the diagram.
A skeleton graphic has a certain size but this size will not change even if the physical scale is
changed - only the number of grid points that fit within the skeleton will vary.
Objects
Table 24-17. Edit Physical Scale Dialog Box Contents

Field Description
Physical Scale Specify the physical length between the points of the grid that is
visible on the diagram. Select the unit of measurement from the drop-
down list.
Note: You can use the Set Grid Defaults facility to specify how the
grid is displayed on the diagram. See “Setting Grid Defaults for a
Related Topics

February 2016
Edit Diagram Dialog Box

To access: Right-click on the name of the diagram in the Project Browser Window and select
Edit.
Use this dialog box to edit the name of a diagram, specify the style set that is applied to the
diagram, and edit the properties of a diagram.
Note
If you have accessed this dialog box when creating a new design, you cannot edit the name
of the diagram here.
Objects
Table 24-18. Edit Diagram Dialog Box Contents

Field Description
Name A unique name for the diagram. If valid names for the designs have
been created in Capital Project, you can select a name by clicking
the ellipsis button (...) to display the Name Selection dialog box.
Mandatory.
Style Set The style set that you want to apply to the design. See the Diagram
Styling User Guide for more information about style sets and how
to edit them. Mandatory.
Properties Table To add a property to the diagram, click the New button, enter a
Property Name in the New Property dialog box, then click OK.
The new property is added to the list. Optional.
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 disabled. 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
To delete a property from the list, select it and click the Delete
button, then click OK to confirm the deletion.

February 2016
Related Topics

February 2016
Edit Skeleton Dialog Box
Edit Skeleton Dialog Box

To access: With a diagram open, press Space Bar and enter Skeleton.
Use this dialog box to add a skeleton to a diagram or to remove a skeleton from a diagram.
Objects
Table 24-19. Edit Skeleton Dialog Box Contents

Field Description
Skeleton Browser Displays the available libraries of borders that can contain
skeleton graphics. Navigate to the skeleton that you want to use
and select it.
If you do not require a skeleton on the diagram, select [No
Skeleton].
Related Topics

February 2016
New Integrator Diagram Dialog Box
New Integrator Diagram Dialog Box

To access: Select a Integrator design in the Project Browser Window, press Space Bar and
enter New Integrator Plane. Alternatively, right-click on a wiring design in the Project
Browser Window and select New Integrator Diagram.
Use this dialog box to create a new Integrator diagram.
Objects
Table 24-20. New Integrator Diagram Dialog Box Contents

Field Description
Name A unique name for the diagram. If valid names for the designs have
been created in Capital Project, you can select a name by clicking the
ellipsis button (...) to display the Name Selection dialog box.
Mandatory.
Style Set The style set that you want to apply to the design. See the Diagram
Styling User Guide for more information about style sets and how to
edit them. Mandatory.
Properties Table To add a property to the diagram, click the New button, enter a
Property Name in the New Property dialog box, then click OK.
The new property is added to the list. Optional.
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 disabled. 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
To delete a property from the list, select it and click the Delete
button, then click OK to confirm the deletion.
Related Topics
Creating a Diagram

February 2016
Printing Related Dialog Boxes
Printing Related Dialog Boxes

The Capital Design Tools - Common Functions User Guide contains full details of the
printing-related dialog boxes available for configuring Projects, Designs, Print Regions and
Diagrams for Printing and Printing to a File.
The following topic is available:
Printing Dialog Boxes
This section offers a description of all dialog boxes related to printing functions. For each dialog
box, all fields are listed, along with a full description of the field’s function.

February 2016
Report Dialog Boxes
Report Dialog Boxes

This section offers a description of all input dialog boxes used in reports. For each dialog box,
all fields are listed, along with a full description of the field’s function.
Connectivity Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709
Select Attributes/Properties for Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
Select Inclusion Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714

February 2016
Connectivity Dialog Box

To access: Press Space Bar and enter Platform.
Use this dialog box to create customized connectivity reports.
Objects
Table 24-21. Connectivity Dialog Box Contents

Field Description
Format Specifies the format of the reports. Only the comma separated
variable (CSV) format is available. This enables them to be opened
into applications such as MS Excel. The HTML and Output
Window formats are not available in this version of the software.
Location Specifies the location where the reports are saved. Click the
Browse button to navigate to the location.
Scheme If you want to save your Inclusion window, Output window and
Attributes/Properties window selections as a scheme for future re-
use, specify a new scheme name in the Scheme field and click Save
As; the scheme is saved.
If you want to use an existing scheme, select it from the drop-down
list; the Inclusion window, Output window and Attributes/
Properties window are updated with those existing selections.
To delete a scheme, select it in the drop-down list and click Delete.
Inclusion window Click the Edit button to display the Select Inclusion Dialog Box
where you select the connectivity object types for which you want
to create reports. One report is generated for each selected object
type.
Output window Lists the columns that are included in the report currently selected
in the Inclusion window.
Click the Edit button to display the Select Output for Dialog Box
where you add or remove columns.
The report will display the columns in the order that they are
displayed in this list. You can select a column in the window and
click the Move Up or Move Down button to change where it
appears in the list.

February 2016
Table 24-21. Connectivity Dialog Box Contents (cont.)

Field Description
Use Single Attributes/ Select this option if you want the selected object type's attributes/
Properties Column properties to be displayed in only one column of the report, rather
than separated into individual columns. This moves any attribute
and property fields from the Output window to the Attributes/
Properties window. In the Output window, they are replaced with
one column Attributes/Properties (that can be included in or
removed from the report just like the other columns). The
Attributes/Properties window allows you to edit the attributes and
properties that are displayed in the single column.
Attributes/Properties Enabled only if “Use Single Attributes/Properties” column is
window selected and if Attributes/Properties is included in the Output
window.
Lists the attributes and properties that are included in the
Attributes/Properties column of the report currently selected in
the Inclusion window.
Click the Edit button to display the Select Attributes/Properties for
Dialog Box where you add or remove attributes and properties.
The report will display the attribute/property values in the order that
they are displayed in this list. You can select an attribute/property
in the window and click the Move Up or Move Down button to
change the order.
Write Report Files Creates the reports using the settings in this dialog box.
Related Topics

February 2016
Report Material Statistics Dialog Box

To access: Select Reports > Material Statistics from the menu.
Use this dialog box to create a material statistics report.
Objects
Table 24-22. Report Material Statistics Dialog Box Contents

Field Description
Report Detail Select one of the following to determine how the report is structured:
• Totals
The report contains one line with the totals for the whole design.
• By Harness
In addition to the totals for the whole design, the report contains
lines with the totals for each harness.
• By Level
lines for each harness level of each harness. For example:
Figure 24-1. Example Material Report by Level
In this example:
• The Totals row shows the total number of objects in the design as
a whole. That is, 56 connectors, 12 inlines, 11 splices, and so on.
• The top BODY row shows the total number of objects on the
BODY harness regardless of harness levels. That is, 12
connectors, 1 inline, 1 splice, and so on.
• The other BODY rows show the total number of objects on
particular harness levels for the BODY harness. For the _US-SP1
level, there are 6 non-inline connectors. In other words, there are
6 slot connectors or interface connectors populated for this
harness level.
• By Option
lines for each harness and is further divided by option.

February 2016
Table 24-22. Report Material Statistics Dialog Box Contents (cont.)

Field Description
By Wire Attribute/ Gives you the option of adding columns to the table for a particular
Property drop-down wire attribute or property. Select the wire attribute or property for
list which you want to display information from the drop-down list. See
Usage Notes below this table.
Number of Wires (No./ Check this box if you want to add columns labeled #.W. that contain
W.) the number of wires for a particular wire property value. See Usage
Notes below this table.
Wire Length (W./L.) Check this box if you want to add columns labeled W.L. that contain
the length of wire used for a particular wire property value. See
Usage Notes below this table.
Material statistics table Displayed when you click Generate.
Displays the material statistics report.
Generate Generates the material statistics report and displays it in the Material
statistics table.
Save Report File Displays a Material Statistics Report dialog box that enables you to
save the report as a CSV file.
Usage Notes
If you check the Number of Wires (#.W.) box and select WireColor from the drop-down list.
Columns are added showing how many wires for each WireColor value are used.
In this example, you can see that 1 wire with the WireColor value U/P is used in total and that
3 wires with the WireColor value G are used in the BODY LH harness.
Related Topics
Creating a Material Statistics Report for a Topological Design

February 2016
Select Attributes/Properties for Dialog Box
Select Attributes/Properties for Dialog Box

To access: Click Edit next to the Attributes/Properties window on the Connectivity dialog
box.
Use this dialog box to select the attributes and properties that you want included in the
Attributes/Properties column of the report for the connectivity object type currently selected
in the Inclusion window of the Connectivity dialog box.
Objects
Table 24-23. Select Attributes/Properties for Dialog Box Contents

Field Description
Available window Lists the available attributes and properties that are not currently
selected. To select one to include in the Attributes/Properties
column, select it and click Add; it moves to the Included window.
Included window Lists the attributes and properties that are included in the
Attributes/Properties column. To remove one, select it and click
Remove; it moves to the Available window.
Related Topics

February 2016
Select Inclusion Dialog Box
Select Inclusion Dialog Box

To access: Click Edit next to the Inclusion window on the Connectivity dialog box.
Use this dialog box to select the connectivity object types for which you want to create
customized connectivity reports.
Objects
Table 24-24. Select Inclusion Dialog Box Contents

Field Description
Available window Lists the available connectivity object types that are not currently
selected. To select an object type to have a report generated, select
it and click Add; the object type moves to the Included window.
Included window Lists the connectivity object types that have been selected to have
reports generated. To remove an object type, select it and click
Remove; the object type moves to the Available window.
Related Topics

February 2016
Select Output for Dialog Box
Select Output for Dialog Box

To access: Click Edit next to the Output window on the Connectivity dialog box.
Use this dialog box to select the fields, attributes and properties that you want included in the
report for the connectivity object type currently selected in the Inclusion window of the
Connectivity dialog box.
Objects
Table 24-25. Select Output for Dialog Box Contents

Field Description
Available window Lists the available fields, attributes and properties that are not
currently selected. To select one to include in the report, select it
and click Add; the field, attribute or property moves to the Included
window.
Included window Lists the fields, attributes and properties that are included in the
report. To remove one, select it and click Remove; the field,
attribute or property moves to the Available window.
Related Topics

February 2016
Wiring Synthesis Dialog Box

To access: Press Space Bar and enter CWS or MWS, or click the button on the Design
Use this dialog box to run the actions for modular wiring synthesis and composite wiring
synthesis.
Objects
Table 24-26. Wiring Synthesis Dialog Box Contents

Field Description
Specifies that all of the steps necessary to complete composite
wiring synthesis are run when you click Go. The steps run are:
Full Synthesis
• Update Harness Options
• Generate Physical Harness Levels
• Synthesize All Wiring
• Combine Identical Harness Levels
Modular Specifies that modular wiring synthesis will run when you click
Go. See “Modular Wiring Synthesis” on page 450 for information
about the process. The steps run are:
Synthesis
• Update Harness Options
• Generate Abstract Harness Levels (if “Delete all Wiring” is
selected, or none have been generated)
• Synthesize All Wiring (if “Delete all Wiring” is selected, or
none has been synthesized)
Generate & Specifies that the steps necessary for generating the full set of
buildable harness levels and synthesizing wiring for those levels
are run when you click Go. The steps are:
Finish
• Generate Physical Harness Levels
Specifies that the steps necessary for completing wiring synthesis
on the existing harness levels are run when you click Go. The steps
Finish Synthesis
are:
Custom Settings Specifies that you have manually modified the steps to be run.
Expands the Advanced section that displays the individual steps
that can be run and the additional settings for customizing wiring
synthesis.

February 2016
Table 24-26. Wiring Synthesis Dialog Box Contents (cont.)

Field Description
Delete all Harness Levels Specifies whether harness levels and configurations generated
and Configurations during previous synthesis runs will be deleted (selected) or not
(unselected) when you click Go. When you select this, Delete all
Wiring is also selected.
When you run multi-user mode, this option is called Delete All
Wiring and Harness Levels from Locked Harnesses as you can
only use this functionality on harnesses that you have locked.
Composite wiring synthesis can proceed even if there are some
harnesses unlocked. It is run as though you are running in single
user mode and have a complete design lock. After the process is
finished, the system keeps the wiring synthesis changes only for
the harnesses that you have locked. Unlocked harnesses keep their
original wiring. Signals in an inline can short together during
wiring synthesis but you can edit the signal map for inline cavities
to correct this. See “Mapping a Signal Between Cavities on the
Halves of an Inline Connector” on page 246 for more information
about editing a signal map.
Clear Promoted Options Specifies whether previously promoted options and giveaway
options are deleted (selected) or not (unselected) when you click
Go. When you select this, Delete all Harness Levels and
Configurations and Delete all Wiring are also selected.
Delete all Wiring Specifies whether composite wiring from previous synthesis runs
will be deleted (selected) or not (unselected) when you click Go.
Advanced Expands to display the list of actions that can be run when you
click Go and the settings that can be used to customize wiring
synthesis.
Update Harness Options Specifies whether the system does the following (selected) or not
(unselected) when you click Go:
• Identifies the options that affect each harness (including pass-
through options) and promotes them onto each harness.
• Removes options from harness levels if they are not required.
To determine options to be removed, the systems looks at the
options on the wires passing through the harness (as well as
options promoted directly from the devices within slots).
Generate Abstract Enabled only if Modular Synthesis has been selected.
Harness Levels Specifies whether the system does the following (selected) or not
• Re-generates a set of abstract harness levels, typically one per
vehicle model.

February 2016

Field Description
Generate Physical Specifies whether the system does the following (selected) or not
Harness Levels (unselected) when you click Go:
• Re-generates the full set of buildable harness levels, adhering
to the vehicle model definitions and the option relationships.
• These levels can be viewed through the Define Harness Levels
Dialog Box for each harness.
If you have specified giveaway options, these are taken into
account when generating the depopulated harness levels.
Synthesize All Wiring Specifies whether the system does the following (selected) or not
• Re-creates all the vehicle configurations.
• Routes all logical signals along the topological bundles of the
vehicle configurations.
• Creates the wires along which the signals travel and creates
splices where necessary in all of the harness levels. When
doing this, the system re-uses as much wiring as possible in
each configuration.
• Generates option expressions for the wires and shields (not
multicores) that are synthesized, even if a wire is present in all
harness levels.
• Generates a module code for each wire and shield.
The generated module codes match the option expressions for the
wires. However, module codes must not exceed 30 characters so
new, unique module codes are generated when an option
expression is too long. To ensure consistency, the mapping of
codes is taken from existing wiring before new option expressions
and module codes are generated. When multiple existing wires
have the same option expression but different module codes, the
system selects just one of the module codes.
Combine Identical Specifies whether the system does the following (selected) or not
Harness Levels (unselected) when you click Go:
• Combine harness levels that have identical wires. Sometimes,
two harness levels that support different option combinations
have identical wires. In this case, the two harness levels are
combined into one, supporting all options from the original
harness levels.
• Removes any harness levels that contain no wiring.
If you do not want a harness level to be combined, you should give
it a part number.

February 2016

Field Description
Stop process when Specifies whether the number of generated harness levels per
Harness Levels reach harness is limited (selected) or not (unselected). Enter the
maximum number of harness levels per harness in the box below
this option.
If you do not specify a limit or the limit is more than a thousand,
composite wiring synthesis may not complete.
Run Complexity Report Specifies whether a complexity report is generated and displayed
in the Output Window (selected) or not (unselected) when you
click Go.
The complexity report runs in conjunction with the steps: Update
Harness Options and Generate Physical Harness Levels. For each
step, the report lists the most complex harnesses, the options
affecting each harness and the most complex vehicle models
affecting the harness.
Combine Wires If you have set Combine Wires at Cavity constraints on
connectors, slots or the design, the system combines the
appropriate wires at the cavities matching the constraints.
Generate Bypass Wiring Specifies whether the system does the following (selected) or not
• If, in any harness level, a splice is connected to just two wires,
the system replaces the splice and wires in that level with a
single bypass wire (that has a read-only Bypass attribute).
This process does not affect shield conductors. You cannot add a
splice to the bypass wires. Also, you can use a “Create Bypass
Wiring” constraint to control whether the generation of a bypass
wire is allowed for a splice or a signal with a particular property or
attribute.
Generate Vehicle Specifies whether the system generates vehicle configurations for
Configurations the design (selected) or not (unselected) when you click Go. When
you select this, you must select one of the following:
• Maximum Complexity Only
The system generates just the max-complexity vehicle
configurations.
• Full
The system generates all possible vehicle configurations.
Note that this has no impact on synthesis. This only affects the
vehicle configurations that are created to save you having to
generate some manually. Synthesis always generates its own set of
configurations completely independently of this setting.

February 2016
Related Topics
Regenerating Harness Levels and Finishing Composite Wiring Synthesis
Generating Initial Harness Levels for Composite Wiring Synthesis

February 2016
Miscellaneous Dialog Boxes
Miscellaneous Dialog Boxes

This section offers a description of miscellaneous dialog boxes. For each dialog box, all fields
are listed, along with a full description of the field’s function.
Add Selected Logical Design Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722
Add Wire Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Associate Logical Designs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 725
Capital Integrator design Filter Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Combine Devices Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730
Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 732
Edit Ground Signals Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733
Edit Levels Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 734
Harness Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747
Move Wire Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 750
Name Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 751
New Property Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752
Place Device Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 753
Project Functional Module Codes Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 756
Select a Module Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 757
Select Codes for Combination Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 758
Select Module Code Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 759
Variant Expression Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 760

February 2016
Add Selected Logical Design Dialog Box
Add Selected Logical Design Dialog Box

To access: Click the Add associated designs ( ) button on the Associate Logical Designs
dialog box.
Used to select individual logical designs that you want to associate with the topological design.
Objects
Table 24-27. Add Selected Logical Design Dialog Box Contents

Field Description
Filter by Build List From the drop-down list, select whether you want to filter the logical
designs displayed in the Logical designs window to only those from
a particular build list. If you want to display all available designs,
select None.
Logical designs Displays the logical designs that are available for association with
window the topological design. Select the designs that you want to associate
with the topological design and click Add Selected; the designs are
added to the Associated Designs window in the Associate Logical
Designs Dialog Box.
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 Logical designs window 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
available designs.
Related Topics

February 2016
Add Wire Dialog Box
Add Wire Dialog Box

To access: Right-click on the connector from which you want the wire to start in the design
browser (Design tab) and select Add Wire. Alternatively, click on the connector, press
Space Bar and enter Add Wire.
Use this dialog box to add a wire between two cavities on separate connectors.
Objects
Table 24-28. Add Wire Dialog Box Contents

Field Description
Signal The name of the signal that connects to the selected cavity in the From
End window.
From End Select the cavity at which you want the wire to start. Each cavity is
displayed in the format <slot name>:<connector name>:<cavity
name> (signal name). If the connector is not on a slot, no slot name is
displayed.
To End Select the cavity at which you want the wire to end. Each cavity is
displayed in the format <slot name>:<connector name>:<cavity
name> (signal name). If the connector is not on a slot, no slot name is
displayed.
If you are adding a wire from a cavity on a ground slot, the To End
box lists cavities on all other ground slots (including those on different
harnesses). Note that you may need to create more than one wire if the
target cavity is in a different harness).
If a cavity in the To End box connects to a different signal to the one
that is connected to the cavity in the From End field, the signal name
in the To End box is displayed in red.
Harness Displayed only if there are multiple harnesses at the connector. Select
the harness to which you are adding the wire from the drop-down list.
Related Topics
Adding a Wire

February 2016
Assign Wiring Specifications by Rule Dialog Box
Assign Wiring Specifications by Rule Dialog Box

To access: Press Space Bar and enter Specs.
Use this dialog box to re-assign properties and attributes to wires, splices, multicores and
terminal specifications.
Objects
Table 24-29. Assign Wiring Specifications by Rule Dialog Box Contents

Field Description
Wires / Multicores/ Select the boxes next to the type of objects to which you want to re-
Splices / Terminal assign properties and attributes.
Specification
Where data exists Select one of the following options:
• Don't Overwrite
Select this if you do not want to overwrite properties and attributes
that are already set on objects but do want to apply the properties
and attributes to objects where they are not set already.
• Preserve Library Data
Select this if you do not want to overwrite the properties and
attributes on any wires that have library parts assigned to them but
do want to overwrite the values on objects without library parts.
• Overwrite and Remove Part
Select this if you want to overwrite the properties and attributes on
all objects and unassign library parts.
Related Topics
Assigning Wire / Splice / Multicore Properties by Rules

February 2016

To access: Press Space Bar and enter Associate Logical Designs, or click the Associate Logical
Designs ( ) button on the Design Browser (Design tab).
Use this dialog box to associate individual logical designs or a build list with the topological
design.
Objects
Table 24-30. Associate Logical Design Dialog Box Contents

Field Description
Managed by Build Displays any logical design build lists that can be associated with the
List Capital Integrator design. If you select a build list, you enter managed
mode where the association of the logical designs is managed by the
build list.
If you want to associate individual designs rather than a build list,
select None.
Replace the selected If you are replacing a design association with a design that is not a
‘removed’ design related revision, you must indicate that the new design is replacing the
with the selected old. To do this, either drag the old design association with the icon
‘added’ design over the new design with the icon or select them both and click this
button.
If you have made an incorrect selection when doing this, simply select
one of the design associations and click this button again; the link
between them is removed.
Enabled only if you have selected a design association to be removed
and one to be added, or if you select a design that has been linked with
another.
Remove associated Removes the association with any logical designs selected in the
designs Associated Designs window.
Enabled only if you have selected None in the Managed by Build
List field. That means the logical design associations are not managed
by a particular build list. You can therefore select which designs are
associated.
Add associated Displays the Add Selected Logical Design Dialog Box where you
designs select individual logical designs that you want to associate with the
topological design.
Enabled only if you have selected None in the Managed by Build
List field. That means the logical design associations are not managed
by a particular build list. You can therefore select which designs are
associated.

February 2016
Table 24-30. Associate Logical Design Dialog Box Contents (cont.)

Field Description
Associated Designs Displays the logical designs that have been associated with the
window topological design. Icons are displayed next to the designs when you
add or remove them.
indicates that the design association will be added when you click
OK.
indicates that the design association will be removed when you
click OK.
If you add a design revision that replaces an older revision, the
following is displayed:
If you are replacing a design with a design that is not a related revision,
you must indicate that the new design is replacing the old. To do this,
either drag the old design with the icon over the new design with the
icon or select them both and click the Replace the selected
‘removed’ design with the selected ‘added’ design ( ) button.
Enter Filter String In the field next to the Enter Filter String icon ( ), enter a series of
( ) / Clear Filter characters. A filter is applied to the Associated Designs window so
String ( ) 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
available designs.
All / Changed / To be An additional filter for the Associated Designs window.
• All
Displays all designs in the window.
• Changed
Displays only the designs that will be added ( ) or removed ( )
when you click OK.
• To be
Displays only the designs that will remain associated when you
click OK.
Related Topics

February 2016
Capital Integrator 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 24-31. Capital Integrator Design Filter Dialog Box Contents

Field Description
Filter Select a filtering option from the drop-down 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
Harness Levels active. See “Setting an Active Vehicle Configuration” on page 368
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 the “Show Harnesses with no Levels” option if you
want to display harnesses that have no harness levels at all.
Graphics by Active Displays bundles, slots, inlines and interface connectors only if
Wiring they 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 will be filtered (hidden)
because they have no active wiring content. Inlines and interface
connectors connected to inactive bundles will be filtered and
hidden. Slot portals on the active slot will be filtered if they are not
connected to any bundle or if the connected bundle does not
contain any active wiring.
Graphics by Option Displays only objects that have been assigned particular options.
Ensure that you are showing the filter options (Show Filter
Options) and add the options to the Selected window. If you want
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 are displayed in the diagram.

February 2016
Table 24-31. Capital Integrator Design Filter Dialog Box Contents (cont.)
Field Description
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
Status Bar

February 2016
Choose Functional Module Code
Choose Functional Module Code

To access: Opened from the Module Code dialog box.
This dialog box allows you to select module codes during Module Code configuration.
Objects
See the Module Code Dialog Box section of the Capital HarnessXC User Guide for full details.
For information on how Capital Integrator handles Module Codes please see “Module Code
Management” on page 389.

February 2016
Combine Devices Dialog Box
Combine Devices Dialog Box

To access: Hold down the SHIFT key on your keyboard and click the devices to be combined in
the Design Browser (Design tab). Still holding down the SHIFT key, right-click one of the
selected devices and select Combine Devices.
Use this dialog box to combine devices that you have placed in the same slot and thereby merge
signals from identical pins.
Objects
Table 24-32. Combine Devices Dialog Box Contents

Field Description
Name Specify the name that you want the combined device to have.
Pin Map Used to map the signals that terminate at the pins on the uncombined
devices to the pins on the combined device. Each row represents a signal.
Device The uncombined device at which the signal terminates
Pin The pin on the uncombined device at which the signal terminates.
Signal The name of the signal that you are mapping to a pin on the combined
device.
Combined Pin The name of the pin on the combined device to which the signal has been
mapped.
Capital Integrator automatically merges signals that terminate at pins
with the same name on the devices to be combined. For example:
A signal COND01 terminates at PIN1 on a device A1 and a signal
COND02 terminates at PIN1 on a device A2. The devices A1 and A2
are being combined in a slot. COND01 and COND02 are merged
together to terminate at a pin PIN1 on the new combined device because
they both terminate at a pin called PIN1 on the original devices.
If you want to change the pin at which a signal will terminate on the
combined device, click the pin name in this column and select a different
one from the drop-down list.
If you select New Pin from the drop-down list, a new pin is created with
a unique name following on from the existing pin names. For example: If
the combined device currently has 6 pins, named 1 to 6, the new pin is
called 7.
Related Topics

February 2016
Combine Wires at Cavity Dialog Box
Combine Wires at Cavity Dialog Box

To access: In the Design Browser (Design tab), right-click on a cavity and select Combine
Wires at Cavity. Multiple conductors (wires or shields) from different signals must connect
to the cavity. If all of the conductors are from the same signal, only the “Add Splice at
Cavity” action is available.
Use this dialog box to combine signals and wires in one step and, if required, to insert a splice at
a cavity for wires from different signals
Objects
Table 24-33. Combine Wires at Cavity Dialog Box Contents

Field Description
Signal Name Specify the name of the combined signal created by this action.
Wire browser Select the wires that you want to combine.
window
Insert splice at If you insert a splice, the wires meet at the splice and a single combined
cavity wire goes from the splice to the cavity. For example, you might want to
do this if you have three shields connecting to one cavity.
If you do not insert the splice, the wires are replaced by one wire. You
might want to do this where the wires can be combined one side of an
inline connector but need to be separate wires on the other side.
Combine Selected Combines the wires (and their signals) that are selected and closes the
dialog box.
Related Topics

February 2016
Details Dialog Box
Details Dialog Box

To access: Select a component in the Part Selection dialog box and click View part details
( ).
Use this dialog box to display the component details tabs for a component.
Objects
See Component Maintenance Dialog Box in the Capital Library User Guide for more
information about the fields on the tabs.
Related Topics

February 2016
Edit Ground Signals Dialog Box
Edit Ground Signals Dialog Box

To access: Right-click on the connector from which you want the wire to start in the design
browser (Design tab) and select Add Wire. Alternatively, click on the connector, press
Space Bar and enter Add Wire.
Use this dialog box to add and edit ground signals in the design.
Objects
Table 24-34. Edit Ground Signals Dialog Box Contents

Field Description
Ground Signal Lists the existing ground signals. To add a ground signal to the design,
click the Add button below the Ground Signal window and specify
the signal name in the Signal Name dialog box that is displayed. Click
the OK button to exit that dialog box.
You can delete or rename a ground signal by clicking on it in the
Ground Signal window and clicking the Delete button or Rename
button.
Available Cavities Lists the available cavities between which the selected signal in the
Ground Signal window can flow but currently does not. Select the
cavities between which you want the ground signal to flow and click
the Add button to add them to the Selected Cavities window.
Selected Cavities Lists the cavities between which the selected signal in the Ground
Signal window is flowing.
You can remove cavities from the Selected Cavities window by
clicking on them and clicking the Remove button. To add all of the
cavities to the Selected Cavities window, click the Add All button. To
remove all cavities from the Selected Cavities window, click the
Remove All button.
Related Topics

February 2016
Edit Levels Dialog Box
Edit Levels Dialog Box

To access: Click the ellipsis (...) button next to the Configuration: Level field on the Edit
Properties dialog box.
Use this dialog box to select the harness levels on which a wire exists.
Objects
Table 24-35. Edit Levels Dialog Box Contents

Field Description
Available window Lists the available harness levels on which the wire does not
currently exist.
Select a harness level and click Add to move it to the Selected
window.
Selected window Lists the harness levels on which the wire exists.
If you want to remove the wire from a harness level, select the
harness level and click Remove to move it to the Available
window.
Related Topics

February 2016

To access: Right-click on an object in the Project Browser Window, Logical Designs Browser
(Function Tab), Design Browser (Design Tab), Configuration Setting Browser Window
(Configuration Tab) or Diagram Window and select Properties.
Use this dialog box to edit the attributes and properties of design and diagram objects.
Description
The dialog box consists of various tabs that are displayed depending on what object has been
selected:
Objects
Table 24-36. General Tab

Field Description
General Tab Use this tab to specify the values of system-defined attributes for
the selected object.
Name A label for the object (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 object names maintained in the project’s Object
Type Information in Capital Project.
Select the Visible box if you want the specified name to be
displayed with the object in the diagram.
Click the Edit Attributes ( ) button to display the Edit Name
Text Attributes Dialog Box where you can specify graphical
attributes for the display of the name on the diagram.
See “Specifying the Name of an Object in a Design or Diagram”
on page 271.
Short Description Automatically displays the short description associated with the
selected name for the object if it is already defined in the object
type information. If no predefined information exists then it
allows you to enter and edit the Short Description. This attribute
is available for use in styling and for search queries. Optional.
Select the Visible box if you want the specified short description
to be displayed with the object in the diagram.
attributes for the display of the short description on the diagram.
See “Displaying an Object's Short Description Attribute in a

February 2016
Table 24-36. General Tab (cont.)

Field Description
Slot Type Displayed only for a slot.
Specifies the type of slot:
• Equipment - this indicates that the slot will contain normal
devices (that is, not ground devices or junction boxes).
• Ground - this indicates that the slot will contain ground
devices.
• Junction Box - this indicates that signals can be routed
through this slot.
See “Specifying a Slot Type” on page 99.
Library Part Displays the library part that has been assigned to the object.
Click the Add (...) button to display the Part Selection Dialog Box
where you can select a library part.
The Update ( ) button updates the details for the library part in
the Edit Properties facility with any changes that have been
made in the component library.
The Remove ( ) button removes the library part from the object.
The View ( ) button displays the details for the library part. The
details are displayed in a read-only version of the Part Selection
Dialog Box.
See “Assigning a Library Part to an Object” on page 274,
“Updating the Details of an Object's Library Part” on page 275,
“Removing a Library Part from an Object” on page 276 or
“Viewing the Library Part Details for an Object” on page 277.
Length Displayed only when editing a bundle.
Specifies the physical length of the bundle. This is initially
determined by the length of the bundle in the diagram.
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.
To override the length, select Override and change the value in
the field.
Select the Visible box if you want the physical length to be
displayed with the bundle in the diagram.
attributes for the display of the physical length on the diagram.
See “Specifying the Physical Length of a Bundle” on page 109.

February 2016

Field Description
Configuration: Module Displayed only for a wire, shield or multicore.
Specifies the module code for the object. Click the ellipsis (...) to
select a pre-defined module code.
See “Editing the Module Code for a Wire, Shield or Multicore”
on page 510.
Configuration: Option Displays the option expression that has been assigned to the
object. Not displayed for some objects, such as wires.
Click the ellipsis (...) button to display the Edit Option
Expression Dialog Box where you can specify an option
expression.
Select the Visible box if you want the specified option expression
to be displayed with the object in the diagram.
attributes for the display of the option expression on the diagram.
See “Assigning an Option Expression to an Object” on page 279.
Configuration: Level Displayed only when editing a wire.
Specifies the harness levels that are assigned to this wire.
Harness levels are assigned to wires to indicate that those wires
exist in the derivative harness that the level represents. When
wiring is synthesized, wires are assigned to appropriate harness
levels to support the functional options that have been defined.
Click the ellipsis (...) button to display the Edit Levels Dialog
Box where you select the harness levels.
See “Specifying the Harness Levels on which a Wire Exists” on
page 480.

February 2016

Field Description
Bundle: <Bundle Name> Displayed only when editing a bundle region.
(Bundle Region Node Indicates the offset from the bundle start node and bundle end
Offsets) node to each of the bundle region nodes.
• Bundle Start - From - the offset from the bundle start node
to the region start node.
• Bundle Start - To - the offset from the bundle start node to
the region end node.
• Bundle End - From - the offset from the bundle end node to
the region start node.
• Bundle End - To - the offset from the bundle end node to the
region end node.
See “Editing the Offsets of a Bundle Region from the Bundle
Ends” on page 125.
Specification Displayed only when editing a net or wire. Read-only for a
logical source net, editable for a wire.
Color - the color of the net or wire.
Material - the material of the net or wire.
Spec - the specification of the net or wire.
CSA - the cross-sectional area of the net or wire.
See “Defining Specification Attributes for a Wire” on page 480.
Part Number Displayed only when editing a harness level.
Specify a part number for the harness level. This part number is
not used in Capital Library. If harness levels have been
combined, a part number cannot be specified for a child harness
level.
See “Specifying a Part Number for a Harness Level” on
page 357.
Attributes Table Lists the attributes that have been specified for the object.
Select the Visible box if you want the attribute value to be
Click the Edit Graphical Attributes ( ) button to display the
Edit Graphical Attributes Dialog Box where you can specify
graphical attributes for the display of the attribute value on the
diagram.
See “Editing an Object Attributes and Graphical Display” on
page 280.

February 2016

Field Description
Show All Attributes If selected, all attributes for the object are displayed whether they
can be edited or not.
If not selected, only attributes that can be edited are displayed.
Table 24-37. Properties Tab

Field Description
Properties tab Use this tab to add and edit user-defined properties for the
selected object.
Properties Table Lists the user-defined properties that have been specified for the
object.
It contains the columns listed below.
See “Adding a Property to an Object” on page 282 and “Deleting
a Property from an Object” on page 283.
Name The name of the property. This is editable only when you first
add the property to the object.
Value The value of the property. This is the value that is displayed with
the object in the design if you tick the Visible box
Type The type of value that the property can have. The following
options are available:
• String - a mixture of letters, numbers and special symbols.
• Integer - a whole number.
• Float - a decimal number.
Visible Select the Visible box if you want the property value to be
Attributes Click the Edit Attributes ( ) button to display the Edit
Graphical Attributes Dialog Box where you can specify graphical
attributes for the display of the property value on the diagram.
New Allows you to add a new property to the object. Displays the New
Property dialog box where you specify the name of the property.
When you click OK, the property is added to the Properties
Table.
Delete Deletes the property selected in the Properties Table and removes
it from the object.

February 2016
Table 24-38. Graphical Tab

Field Description
Graphical Tab Use this tab to specify how the selected object is displayed
graphically on the diagram. See Specifying How an Object is
Displayed Graphically in a Diagram.
Primary Color The color of the object as it is displayed in the diagram. As well
as color names, the list contains the following options:
• Default
The default color used for the object by the system.
• 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
vice versa.
• Manual
The Choose Object Color dialog box is displayed, where you
can select a color.

February 2016
Table 24-38. Graphical Tab (cont.)

Field Description
Thickness Specify the thickness of the lines of the graphical shape.
Mandatory. To use the default thickness, select Default from the
drop-down list.
To use a different thickness, select Override from the first drop-
down list and select the type of thickness from the final drop-
down 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 middle drop-down list.
• Physical (unit of measurement)
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 drop-down 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.
See Physical Line Thickness in the Capital Design Tools -
Common Functions User Guide for a definition and links to
related task flows.
Line Style The style of the lines of the object in the design. Select the line
style from the drop-down list box.
Secondary Color A secondary color, (for highways and conductors in Capital
Logic/Capital Publisher, and bundles in Capital Integrator only)
is the color of the gap in a broken line style as it is displayed in
the diagram. This setting is disabled until a broken line style is
selected.

February 2016
Table 24-38. Graphical Tab (cont.)

Field Description
Fill Pattern Selection Display of this option depends on the object type.
Specifies whether a fill pattern is used in a polygon or closed
object.
To select a fill pattern, click the Change field; the Fill Pattern
Selection dialog box is displayed where you select the fill
pattern.
You also specify the foreground color and background color that
you want to use for the fill pattern. As well as color names, the
lists contain the following options:
• 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
vice versa.
• Manual
The Choose Object Color dialog box is displayed, where you
can select a color.
Table 24-39. Rules Tab

Field Description
Rules tab Use this tab to edit the rules and constraints that apply to the
object whose properties you are editing. See Rules Tab in
Properties Dialog Box in the Capital Design Tools - Common
Functions User Guide for full descriptions of the fields.
See Rules and Constraints for an overview of the concepts.
Table 24-40. Routes Tab

Field Description
Routes tab Use this tab to specify the route code for a connector. If there are multiple
harnesses entering the connector, you can specify a different route code
for the connector on each harness. Also use this to specify whether
bundles entering the connector are poke home bundles. See Including a
Slot with a Harness and Specifying a Route Code for a Connector.
Harness The name of the harness entering the connector. Read-only.
Connector The name of the connector. Read-only.

February 2016
Table 24-40. Routes Tab (cont.)

Field Description
Bundle The name of the harness bundle entering the connector. Read-only.
Route Code The route code is not used in Capital Integrator but is used in Capital
HarnessXC, for example, to distinguish between slot connectors when
there is more than one slot connector combined with a slot.
If no route codes have been defined for the library part or no library part is
assigned, you can manually specify a route code for the connector when
on the harness specified in this row. Optional.
If route codes have been defined for the library part used for the
connector, this field is not editable and displays the appropriate code from
the library part. Read-only.
Poke Home Whether the bundle specified in this row is a poke home bundle (selected)
or not (unselected). Mandatory.
Table 24-41. Variance Tab

Field Description
Variance tab Use this tab to view option-specific values that have been set for the net’s
attributes. These values will have been set on the net in Capital Logic. See
Specifying Option-Specific Values for Net Attributes and Properties in
the Capital Logic User Guide.
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.
The attributes that can have option-specific values are:
• WireColor
• WireCSA
• WireMaterial
• WireSpecification
Attribute The attribute for which option-specific values have been specified.
Options The options for which the value in the Value column has been specified.
Value The value that has been specified for the options in the Options column.
Type The type of value that the property can have. The following types are
available:
• String - a mixture of letters, numbers and special symbols.
• Integer - a whole number.
• Float - a decimal number.

February 2016
Table 24-42. Variant Tab

Field Description
Variant tab Visible only when one bundle is selected. Not visible when multiple
bundles are selected.
Use this tab to specify different physical lengths for the selected bundle
when different option expressions or functional variant module codes are
applied to it. See Specifying Variant Physical Lengths for a Bundle.
Variant Bundle This table lists the different physical lengths of the selected bundle when
Length Table different option expressions or functional variant module codes are applied
to it.
An additional blank row is added when all existing rows contain an option
expression or module code.
Delete variant Deletes the variant bundle length row from the table.
length
Variant Specifies the option expression or functional variant module code that must
Expression be applied to the bundle in order for the specified Variant Length to be
used.
Either type the option expression/module code manually or click the
ellipsis (...) at the right end of the field to display the Variant Expression
Editor Dialog Box where you can create the option expression or select a
module code.
Different rows cannot contain identical option expressions or module
codes.
Variant Length Specifies a variant physical length that is only used when the specified
Variant Expression is applied to the bundle.
Different rows cannot contain identical lengths.

February 2016
Generate Slot Circuit Dialog Box

To access: Click on the slot in the Diagram Window or in the Design Browser (Design tab),
press Space Bar and enter Generate Slot Circuit. Alternatively, right-click on the slot and
select Generate Slot Circuit.
Use this dialog box to create a new Capital Logic design and connectivity for the interior of a
slot in a Capital Integrator Design.
Objects
Table 24-43. Generate Slot Circuit Dialog Box Contents

Field Description
Design tab Enables you to specify the attributes for the Capital Logic design that
will be generated.
Name A label to identify the design.
You can 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 in Capital
Project. Mandatory.
Properties Opens the Edit Design Properties Dialog Box where you can add
properties to the design. Optional.
Revision Specifies the version of the design, allowing multiple updated
versions of the same design to exist in the database. When creating a
new design, you enter the initial version number or letter. When
creating a revision, you enter the subsequent numbers or letters. See
Creating a Design Revision in the Capital Project User Guide for
more information on creating a new revision. Mandatory.
Short Description Enter a line of descriptive text to provide more information about the
design. This information is displayed alongside the design Name and
Revision in the Project Browser Window. Optional.
Description This is a free-text field into which you can enter additional
comments or notes relevant to this design. Optional.

February 2016
Table 24-43. Generate Slot Circuit Dialog Box Contents (cont.)

Field Description
Release Level This field is used to record the design's progress through the stages
of the design life-cycle. A number of system-defined release levels
are available, but it is possible to create custom levels in Capital
Project (see the Create a Project's Release Levels topic in the
Capital Project User Guide for more information). Regardless of
the number of custom levels available, they must correspond to one
of the system-defined release levels:
• If no custom levels are configured, the only option available is
Draft, which is selected by default.
• Any custom levels configured must correspond to the Draft
system-defined level, so select the custom level required as
dictated by your internal procedures.
In either case, this is field is mandatory.
Abstraction If you are using design abstractions, select the abstraction to which
this design belongs, from the drop-down list. Maintained in Capital
Project, abstractions allow you to group related harnesses together
for reporting purposes, providing a view of a subset of a vehicle's
wiring. See the Design Abstraction topic in the Capital Project User
Guide for more information. Optional.
Domain If you are using domains to restrict user access to designs, select the
domain to which this design belongs from the drop-down list. Only
users with access rights to the selected domain are able to access this
design. Domains are created and associated with user accounts in
Capital User. See the Domains topic in the Capital User User Guide
for more information. Optional.
Applicable Options Specify 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. Optional.
Option Specify the option or option expression that you want to apply to the
whole design. You must enter this in the Option Expression field by
clicking the ellipsis (...) button to display the Edit Option
Expression facility. Optional.
Generate diagram Select this option if you want the system to generate a diagram for
the design automatically.
Filter tab Use the drop-down list to select the Vehicle Configuration for which
you want to generate the slot circuit.
Related Topics
Generating a Slot Circuit

February 2016

To access: Press Space Bar and enter Import Wiring or Export Wiring.
Used to select specific harnesses for which you either want to import or export wiring
information.
Objects
Table 24-44. Edit Build List Dialog Box Contents

Field Description
Harnesses Lists the harnesses for which wiring information is available. Select
the harnesses for which you want to import or export wiring
information.
Select All Selects all of the harnesses listed in the Harnesses window.
Clear All Clears any selections in the in the Harnesses window.
Related Topics

February 2016
Import Harness Dialog Box

To access: Press Space Bar and enter Import Harness.
Use this dialog box to import harness wiring into the open design in Capital Integrator.
Objects
Table 24-45. Import Harness Dialog Box Contents

Field Description
File Click the ellipsis (...) button to display the Select Harness dialog box
where you locate and select the harness file to be imported.
Run DRCs If you select this, the import will run all design rule checks set to run in
Harness Transfer mode and will indicate any issues. If there are any
issues, they are displayed on the Harness Import tab of the Output
Window.

February 2016
Table 24-45. Import Harness Dialog Box Contents (cont.)

Field Description
Signal Name - Enabled only when a valid X2ML file (harness X2ML or wiring
Method X2ML) is selected in the File field.
Specify how the imported signals are named in the Capital Integrator
design:
• Sequential
The import names the signals sequentially with a prefix. Specify
the Prefix (for example, SIG). Each signal is named in the order
that it is encountered during the import, starting at 1 (for example,
SIG1, SIG2, SIG3).
• Positional
The import names the signals based on an attribute/property value
of the wires that carry them. Specify a wire Attribute/Property
whose value you want to use. Specify the number of the Start and
End characters of the value string to be used.
For example, Attribute/Property = Name, Start = 2 and End = 5. In
this case, if a wire name is WABCD12, the signal name is ABCD.
You can leave the End field blank to mean the end of the value
string.
• Delimiter
The import names the signals based on a wire attribute/property
value that uses delimiters (prefix and suffix). Specify a wire
Attribute/Property whose value you want to use. Specify the
First delimiter and Last delimiter used in the value, and the Max
Length that the signal names can have.
For example, Attribute/Property = Name, First delimiter = - and
Last delimiter = -. In this case, if a wire name is W-ABCD-12, the
signal name is ABCD. If Max length = 3, the wire name is ABC.
You can leave the First delimiter and Last delimiter fields blank
to mean the start or end of the value string. You can leave the Max
Length field blank to mean no maximum length.
If the system names multiple signals the same, it merges them into one
signal.
You can develop your own custom methods using extensibility
plugins. See the PluginDevelopment.pdf file, located in the doc\plugin
folder of your Capital installation.
Related Topics

February 2016
Move Wire Dialog Box
Move Wire Dialog Box

To access: Right-click on the wire in the design browser (Design tab) and select Move Wire.
Alternatively, click on the wire, press Space Bar and enter Move.
Use this dialog box to add a move a wire end from one cavity to another.
Objects
Table 24-46. Move Wire Dialog Box Contents

Field Description
Signal The name of the signal that travels along the wire.
From End Select the the wire end that you want to move. Each cavity at which
the wire ends is displayed in the format <slot name>:<connector
name>:<cavity name>. If a connector is not on a slot, no slot name is
displayed.
To End Displays cavities to which you can move the wire end. Select the
cavity to which you want the wire end to move.
Related Topics
Moving a Wire

February 2016
Name Selection Dialog Box
Name Selection Dialog Box

To access: From an Edit Properties dialog box, click the ellipsis (...) button to the right of a
Name field.
Use this dialog box to select the name of an object from a list of names created for the object
type in Capital Project.
Objects
Table 24-47. Name Selection Dialog Box Contents

Field Description
Find Enter a string to limit the listed names to those that start with that string.
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
box displays all available names for the object type (unselected) or just
those names used in the usage definitions by default (selected). Optional.
Name The name created in the object type information. Read-only.
Description The description that is applied to the object with the name. Read-only.
Short Description The short description that is applied to the object with the name. Read-
only.
Related Topics

February 2016
New Property Dialog Box
New Property Dialog Box

To access: Accessed from property maintenance dialog boxes or tabs (click the New button).
Use this dialog box to enter a name for a component, design or diagram property.
Objects
Table 24-48. New Property Dialog Box Contents

Field Description
New Property Offers a list of every property configured for the project-level object type
information of the selected object type in Capital Project. Either select a
property from the drop-down list or enter the name of a property to be
created later. Mandatory.

February 2016
Place Device Dialog Box

To access: Right click on a device or ground device in the Logical Designs Browser (Function
tab) and select Place Device. Alternatively, click on the device in the Logical Designs
Browser, press Space Bar and enter Place Device. These menus are enabled only if the
device is unplaced.
Use this dialog box to select a slot into which you are placing a device.
Objects
Table 24-49. Place Device Dialog Box Contents

Field Description
Slot Selection tab
Slots browser Displays the slots in the design.
The slots are split into the following groups:
• Slots with Matching Rule
Slots with rules that say the device should be placed here.
• Slots without Matching Rule
Slots with no rules that relate to the device. The device could be
place in one of these.
• Slots with Conflicting Rule
Slots with rules that say the device should not be placed here.
Click on the slot in which you want to place the device.
A grayed out slot ( ) indicates that it does not have a device placed in
it yet.
Hiding device (non- Displayed only when placing a ground device.
ground) slots When placing a ground device, you can show or hide all non-ground
slots by toggling the Show device (non-ground) slots option:
Showing device indicates that all slots (including non-ground slots) are displayed
(non-ground) slots currently, indicates that only ground slots are displayed currently.

February 2016
Table 24-49. Place Device Dialog Box Contents (cont.)

Field Description
Placement Option If you want to perform a variant-based placement of a device, you
enter an expression in this field. You can either enter the expression
manually or click the ellipsis button (...) to display the Edit Option
Expression Dialog Box where you can create an option expression.
Performing a variant-based placement is distinct from using the Edit
Properties Dialog Box to add an option expression to a functional
device itself in Capital Logic because that would affect all instances of
that device.
Whenever an expression is entered during placement, this is treated as
a variant-placement even when the option expression includes non-
variant options. When variant-based placement has been used for a
device, its symbol is slightly different in the Design Browser (Design
tab). It looks like a device overlaid by a second device .
Variant-Based Placement
Devices placed using variant-based placement can be placed in more
than one slot. There is no check to ensure that the option expressions
for multiple variant placements are mutually exclusive or exhaustive.
Composite Wiring Synthesis takes into account any options used in
variant-placement when promoting options.
For devices placed in junction box slots, any options on the device are
promoted to all harnesses connected to the junction box.
After variant-based placement, the General Tab of the Edit Properties
Dialog Box for a device displays the Expression field under the
heading Placement to distinguish the option expression from regular
option tagging.
Connector Map tab Displayed only when placing a device with a footprint.
Allows you to map any footprint connectors to harness and device
connectors in the slot.
Footprint Mappings Displays the footprint connectors for devices in the slot and the
table harness/device connectors to which they are mapped. Read-only.
Footprint - Device Displays the name of the device with a footprint. Read-only.
Footprint - Connector Displays the name of the footprint connector. Read-only.
Slot Connector - Displays the name of the harness connector to which the footprint
Harness connector is mapped. Click on the field to display a drop-down list
from which you can select a harness connector or create a new harness
connector. By default, a new harness connector is created for each
footprint connector and has the same name. You can rename the new
connectors later. For existing harness connectors, the list also displays
the harness on which it is located.

February 2016
Table 24-49. Place Device Dialog Box Contents (cont.)

Field Description
Slot Connector - Displays the name of the device connector to which the mapped
Device harness connector is mated. Read-only.
Harness Displays the name of the harness on which the slot connector (and
harness connector) are located. Read-only.
Library Information Displays library part information for the device, footprint connector
table and harness connector.
Name Displays the name of the device or connector. Read-only.
Part No. Displays the component part number that has been assigned to the
device or connector. Read-only.
No. of Cav./pins Displays the number of cavities or pins on the device/connector. Read-
only.
View Click the button to display a Details dialog box where you can view all
of the library details for the Part No.
Related Topics

February 2016
Project Functional Module Codes Dialog Box
Project Functional Module Codes Dialog Box

To access: Accessed from the Module Code dialog box.
This dialog box allows you to define and maintain Project Functional Module codes.
Objects
Related Topics

February 2016
Select a Module Dialog Box
Select a Module Dialog Box

To access: In the Configuration Setting Browser Window (Configuration tab), select Module
from the drop-down Mode list; the browser window on the tab lists the harnesses in the
design and the module codes that have been created for the wires in them. It also displays
the wires with those module codes. In the browser window, right-click on a option
expression sub-folder to be shared or moved and select Share Wiring > ... or Move Wiring
> ....
Use this dialog box to select the target module with which you want to share wires or into which
you want to move wires.
Objects
Table 24-50. Select a module Dialog Box Contents

Field Description
Module list Displays a list of option expressions on which the module codes are based.
Select an option expression and click Select.
Related Topics

February 2016
Select Codes for Combination Generation
Select Codes for Combination Generation

To access: Accessed from the Module Code dialog box.
This dialog box allows you to select module codes during the creation of Module Code
Combinations.
Objects

February 2016
Select Module Code Dialog Box
Select Module Code Dialog Box

To access: Right-click on a module in the Configuration Setting Browser Window
(Configuration tab) and select Rename Module; the module is displayed as an editable
field. Click the ellipsis (...) at the end of the field.
Use this dialog box to select a name for the module from a list of project-level, functional
module codes.
Objects
Click the code that you want to use and click Select.
Note
This dialog box does not display obsolete functional module codes or codes that are already
referenced in the current harness.
Related Topics
Renaming a Module

February 2016
Variant Expression Editor Dialog Box

To access: Click the ellipsis (...) button in a Variant Expression field.
Used to define an option expression based on variant options.
Objects
Table 24-51. Edit Option Expression Dialog Box Contents

Field Description
Expression Specify whether you want to use an option expression or functional variant
Type module code (Functional Variant Code).
Expression When defining an option expression, this section displays the Options,
Builder Operators and Option Expression fields.
When using a functional variant module code (Functional Variant Code),
this section lists the available module codes.
Options All applicable options assigned to the design. To add an option to the
expression, double-click the option name. Mandatory.
Operators The mathematical symbols available from which you can construct an option
expression. Optional.
To add an operator to the expression, 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]
The component to which the option expression is assigned appears on
those derivatives with either option assigned.
• ! [not]
The component to which the option expression is assigned appears on only
those derivatives without the option assigned.
• ( and )
An opening and closing parenthesis. Enclosing a subset of an option
expression in parentheses allows 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 also have the option to type an expression into this field instead
of selecting from the lists above. Mandatory.

February 2016
Related Topics

February 2016
Capital AutoView Assist for Integrator Dialog Box and Field Reference
Capital AutoView Assist for Integrator Dialog

Box and Field Reference
This section offers a description of all input dialog boxes used by the Capital AutoView Assist
for Integrator application. For each dialog box, all fields are listed, along with a full description
of the field’s function.

February 2016
AutoView: Generate Wiring Diagram Dialog Box

To access: Right-click on a platform design in the Project Browser Window and select
AutoView: Generate Wiring Diagram.
Use this dialog box to run Capital AutoView Assist for Integrator to generate logical diagrams
for the wiring data in the platform design.
Description
The dialog box consists of various options and tabs; the contents of which depend on various
selections that you make.

February 2016
Objects
Table 24-52. Generate Topology Led Diagram/Functionally Partitioned

Diagrams/Custom Partitioned Diagrams
Field Description
Generate Topology Led From this drop-down list, select one of the following:
Diagram / Generate • Generate Topology Led Diagram
Functionally Partitioned
Diagrams / Generate Custom Select this option if you want to generate one wiring diagram
Partitioned Diagrams for all of the functional designs from Capital Logic that have
been associated with the Capital Integrator design but want the
generated diagram to use the bundle layout from the Capital
Integrator design. See Topology Led Diagram and
“Translation of Objects When Generating Topology Led
Diagrams” on page 567 for more information about how
Capital AutoView Assist for Integrator generates these
diagrams.
• Generate Functionally Partitioned Diagrams
Select this option if you want to generate one or more wiring
diagrams for each of the functional designs from Capital Logic
that have been associated with the Capital Integrator design.
The diagrams use the net layouts from the functional designs.
You can generate either one design containing all of the
diagrams or multiple designs belonging to a new build list. See
Functionally Partitioned Diagrams and Translation of Objects
When Generating Partitioned Diagrams for more information
about how Capital AutoView Assist for Integrator generates
these diagrams.
• Generate Custom Partitioned Diagrams
Select this option if you want to generate system wiring
diagrams that are partitioned according to a user-defined
property that has been set on the functional devices and pins in
the associated Capital Logic designs. The property values
must be the name of one or more wiring diagrams on which
the devices and pins must appear. In the case of multiple
names, the list must be comma-separated. See Custom
Partitioned Wiring Diagrams and Translation of Objects When
Generating Partitioned Diagrams for more information about
using this option.

February 2016
Table 24-53. Design Tab

Field Description
Design tab The contents of this tab depends on whether Generate Single
Design is selected or not. For the appropriate list of fields,
jump to the appropriate section of this table:
• Design Details (with Generate Single Diagram Selected or
Not Applicable)
• Design Details (without Generate Single Diagram
Selected)
Generate Single Design Displayed only if you have selected Generate Functionally
Select this if you want to generate just one design containing
multiple diagrams, one for each of the functional diagrams
from Capital Logic that have been associated with the Capital
Integrator design. The layout of the generated diagrams is
based on the net layouts in the functional diagrams.
Do not select this if you want to generate multiple designs, one
for each of the associated Capital Logic designs. All of the
generated designs are in a single new build list and will
contain the same number of diagrams as the matching Capital
Logic design (assuming no content has been filtered out). The
layout of the generated diagrams is based on the net layouts in
the functional diagrams.
For an example of a project structure created when selecting or
not selecting this option, see “Example Project Structures
when Generating Functionally-Partitioned Diagrams” in the
Functionally Partitioned Diagrams topic.
The contents of this tab depends on whether this option is
selected or not. For the appropriate list of fields, jump to the
appropriate section of this table:
• Design Details (with Generate Single Diagram Selected or
Not Applicable)
• Design Details (without Generate Single Diagram
Selected)
Build List Name Displayed only if you have selected Generate Functionally
Partitioned Diagrams and have not selected Generate Single
Design.
Enter the name of the new build list to which the generated
wiring designs will belong.

February 2016
Table 24-53. Design Tab (cont.)

Field Description
Release Level Displayed only if you have selected Generate Functionally
Design.
This field is used to record the build list's progress through the
stages of the design life-cycle. A number of system-defined
release levels are available, but it is possible to create custom
levels in Capital Project (see the Create a Project's Release
Levels topic in the Capital Project User Guide for more
information). Regardless of the number of custom levels
available, they must correspond to one of the system-defined
release levels:
• If no custom levels are configured, the only option
available is Draft, which is selected by default.
Table 24-54. Design Details (with Generate Single Diagram Selected or Not
Applicable)
Field Description
Design Details (with The contents of this section is the same if you have selected
Generate Single Diagram one of the following:
Selected or Not Applicable) • Generate Topology Led Diagram
• Generate Custom Partitioned Diagrams
• Generate Functionally Partitioned Diagrams without
Generate Single Design selected
Name A label to identify the wiring design, which defaults to the
name of the Capital Topology design followed by
WiringDesign and an incrementing number. For example, if
the Capital Topology design is called Vehicle Topology, the
default wiring diagram name is Vehicle
Topology_WiringDesign_1.
You can enter a new name, or click the ellipsis (...) button to
the right of the field to select from a list of pre-specified
topology design names maintained in the project's Object Type
Information in Capital Project. Mandatory.
Properties Opens the Edit Design Properties Dialog Box where you can
add properties to the wiring design. Optional.

February 2016
Applicable) (cont.)
Field Description
Revision Specifies the version of the design, allowing multiple updated
versions of the same design to exist in the database.
Mandatory.
Short Description Enter a line of descriptive text to provide more information
about the design. This information is displayed alongside the
design name and revision in the Project Browser Window.
Optional.
Description This is a free-text field into which you can enter additional
comments or notes relevant to this design. Optional.
Release Level This field is used to record the design's progress through the
stages of the design life-cycle. A number of system-defined
release levels:
Abstraction If you are using design abstractions, select the abstraction to
which this design belongs, from the drop-down list.
Maintained in Capital Project, abstractions allow you to group
related harnesses together for reporting purposes, providing a
view of a subset of a vehicle's wiring. See the Create a
Project's Design Abstractions topic in the Capital Project
User Guide for more information. Optional.
Domain If you are using domains to restrict user access to designs,
select the domain to which this design belongs from the drop-
down list. Only users with access rights to the selected domain
are able to access this design. Domains are created and
associated with user accounts in Capital User. See the
Domains topic in the Capital User User Guide for more
information. Optional.
Applicable Options Specify 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. Optional.

February 2016
Applicable) (cont.)
Field Description
Option Specify the option or option expression that you want to apply
to the whole design. You must enter this in the Option
Expression field by clicking the ellipsis (...) button to display
the Edit Option Expression facility. Optional.
Style Set By default, Capital AutoView Assist for Integrator uses the
Default style set for Capital Logic to style objects in the
generated design. If you have a license to use Capital Styling,
you can use the dropdown list to select a different style set if
they are available. Mandatory.
Parent Folder Specify the parent folder (within the project structure) that will
contain the generated design and diagram. Click the ellipsis
(...) to display the Parent Folder Selection Dialog Box where
you select the folder. The folder path is displayed in the field.
Mandatory.
Table 24-55. Design Details (without Generate Single Diagram Selected)

Field Description
Design Name A label to identify each wiring designs. Specify the Prefix and
Suffix strings that are combined with the names of the
matching Capital Logic designs to form the names of the
generated designs. Mandatory.
Revision Specifies the version of the designs, allowing multiple updated
versions of the same designs to exist in the database.
Specify the Prefix and Suffix strings that are combined with
the revisions of the matching Capital Logic designs to form the
revisions of the generated designs. Both fields can be left
blank. Mandatory.
Short Description Specifies a line of descriptive text to provide more information
about the designs. This information is displayed alongside the
design name and revision in the Project Browser Window.
Specify the Prefix and Suffix strings that are combined with
the short descriptions of the matching Capital Logic designs to
form the short descriptions of the generated designs. Both
fields can be left blank. Optional.

February 2016
Table 24-55. Design Details (without Generate Single Diagram Selected)

Field Description
Release Level This field is used to record the progress of the designs through
the stages of the design lifecycle. A number of system-defined
release levels:
Abstraction If you are using design abstractions, select the abstraction to
which the designs belong, from the dropdown list. Maintained
in Capital Project, abstractions allow you to group related
harnesses together for reporting purposes, providing a view of
a subset of a vehicle's wiring. See the Create a Project's
Design Abstractions topic in the Capital Project User Guide
for more information. Optional.
Style Set By default, Capital AutoView Assist for Integrator uses the
Default style set for Capital Logic to style objects in the
generated designs and diagrams. If you have a license to use
Capital Styling, you can use the dropdown list to select a
different style set if they are available. Mandatory.
Parent Folder Specify the parent folder (within the project structure) that will
contain the generated designs and diagrams. Click the ellipsis
(...) to display the Parent Folder Selection Dialog Box where
you select the folder. The folder path is displayed in the field.
Mandatory.
Folder Name Displayed only if you have selected Generate Functionally
Design.
Enter the name of the new folder which is added below the
parent folder (within the project structure) and contains the
generated designs and diagrams. The Folder Name must be
unique within the Parent Folder. Mandatory.

February 2016
Table 24-56. Option Tab

Field Description
Options Tab The contents of the tab depends on the selection you have
made for Generate Topolgy Led Diagram / Generate
Functionally Partitioned Diagrams / Generate Custom
See one of the following sections for a list of fields:
• Options Tab (with Generate Topology Led Diagram
Selected)
• Options Tab (with Generate Functionally Partitioned
Diagrams Selected)
• Options Tab (with Custom Partitioned Diagrams Selected
Table 24-57. Options Tab (with Generate Topology Led Diagram Selected)
Field Description
Use Logic Diagram Grid Displayed only if you have selected Generate Topology Led
Spacing Diagram.
Specifies the grid spacing that will be used in the generated
diagram. Select this option if you want to use the grid spacing
from the Capital Logic diagrams that are associated to the
Capital Integrator diagram. Do not check this box if you want
to use the grid spacing from the Capital Integrator diagram.
Mandatory.
Use Refined Connectors Specify whether you want the generated wiring diagrams to
have one wiring connector for each virtual, interface or inline
connector (unselected) or if you want the generated wiring
diagrams to have one wiring connector for each refined
connector (selected). Mandatory.
Note that many-to-many and many-to-one matings of refined
inline connectors are not supported. If there are conflicts
between the refined connectors in the harness levels, they are
ignored.

February 2016
Table 24-57. Options Tab (with Generate Topology Led Diagram Selected)
Field Description
Minimum Wire Spacing Displayed only if you have selected Generate Topology Led
Diagram.
Specify a value of 1 or above to control the minimum spacing
between wires in the generated diagram. Mandatory.
Note that as a result of the figure that you enter:
• The size of devices or inline connectors may increase. This
could cause the overlapping of devices or inline connectors
with other logical devices.
• Routing may not be optimal at bundle junctions if there is
not enough space to route the wires.
For an example of these issues and examples of a generated
wiring diagram with different Minimum Wire Spacing
settings, see “Wiring Diagrams with different Minimum Wire
Spacing settings” in the Usage Notes section at the bottom of
this topic.

February 2016
Table 24-58. Options Tab (with Generate Functionally Partitioned Diagrams

Selected)
Field Description
Slot Internal Connectivity Displayed only if you have selected Generate Functionally
Partitioned Diagrams or Generate Custom Partitioned
Diagrams.
Select one of the following:
• None - Select this if you do not want the wiring diagrams
to include any slot-internal connectivity. In this case,
device names and pin names are generated from the names
of the slots in which they are located in the Capital
Integrator design.
• Minimum - Select this if you want the wiring diagrams to
include slot-internal connectivity only if it is required to
display slot-external connectivity correctly. In this case,
device names and pin names are taken from the functional
designs in Capital Logic.
• All - Select this if you want the wiring diagrams to include
all slot-internal connectivity. In this case, device names
and pin names are taken from the functional designs in
Capital Logic.
Mandatory.
See “Generation of Slot Connectivity in Partitioned Diagrams”
on page 611 for a detailed description of how slot-internal
connectivity is generated in these different modes.

February 2016

Selected) (cont.)
Field Description
Exclude slot graphics This is available when you select All or Minimum for 'Slot
Internal Connectivity' and is relevant to a work flow that uses
Capital Publisher.
If you do not select this option, internal connections and
objects are created and the external facing pins are mated to a
virtual slot object. The connectors then all mate to that device.
This causes problems if you want to perform ‘click and sprout’
(where connectivity is automatically rendered) on the internal
connectivity in Capital Publisher. This is because the slot can
have many pins and ‘click and sprout’ will show a large device
that can make the generated diagram hard to read.
If you select this option, CAVAI produces diagrams with no
slot devices. This means, all the internal devices can be
selected in Capital Publisher without having to navigate
through the slot device and you are able to perform 'click and
sprout' on that internal connectivity. Therefore, generated
designs are more easily analyzed within Capital Publisher.
Service technicians and end-of-line engineers can easily trace
the internal connections of a slot, such as the fuses in a power
distribution board, and this helps them to identify faults
quicker.
Always Add Ground Paths Displayed only if you have selected Generate Functionally
Diagrams.
Specify whether you want Capital AutoView Assist for
Integrator to add ground paths on every wiring diagram as
required (selected) or not (unselected). Ground paths include
wires, inline pairs, splice segments and the ground terminal
itself. Mandatory.

February 2016

Selected) (cont.)
Field Description
Distribute Splices This is displayed only if you have selected Generate
Functionally Partitioned Diagrams or Generate Custom
Select this option if you want to distribute splice connectivity
across the generated wiring diagrams. Splice symbols can be
broken and distributed across each sheet to provide a
continuous path on every sheet. This is an alternative to a
conservative view in which the entire splice is represented on a
single sheet. Mandatory.
For an example of a generated wiring diagram with and
without distributed splices, see “Wiring Diagram with and
without Distribute Splices selected” in the Usage Notes
section at the bottom of this topic.
Pin and Device Name This is displayed only if you have selected Generate
Retention Functionally Partitioned Diagrams or Generate Custom
Partitioned Diagrams with a Slot Internal Connectivity setting
of None.
In some cases, the pin names in the generated designs do not
match those in the original Capital Logic functional designs.
Select this option if you want to display the original pin names
on the generated diagram when this is the case. In the
generated design:
• The original pin name is stored as a property on the pin and
is set as visible.
• The generated name of the pin is not set as visible so is not
• The functional source name for a device is retained only if
it is the only device in a slot.
• The functional source name for a pin is retained only if it is
the only pin representing a cavity and it represents a single
cavity (that is, a one to one mapping).
Do not select this option if you want to display the generated
pin names.
Mandatory.

February 2016

Selected) (cont.)
Field Description
Utilize Combined Devices This is displayed only if you have selected Generate
of Minimum or All.
In Capital Integrator, devices can be combined to create a
single entity and signal.
Select this option if you want the devices to remain combined
in the functionally-partitioned diagrams. Do not select this if
you want the devices to be separate in the functionally-
partitioned diagrams and if you want multiple paths to be
generated to each shared device pin.
This is ideal for combining ground symbols. You do not
necessarily know that they are combined until you create the
physical representation of them. At that time, you can combine
them in Capital Integrator and use this option to recognize that
change.
Mandatory.

February 2016

Selected) (cont.)
Field Description
Property Retention This is displayed only if you have selected Generate
of None.
In some cases, there is a conflict between the values of the
properties on the pins or devices in the functional source
diagrams. This can be the case if multiple functional pins have
been mapped to one pin in Capital Integrator or if multiple
functional devices have been placed in one slot in Capital
Integrator.
If you do not select this, the properties of the functional source
pins and devices are not copied onto the pins and devices in
the generated diagrams.
Select this if you want to store all of the conflicting property
values in separate properties on the objects in the generated
diagrams. Any properties that are modified are visible in the
Edit Properties dialog box for the object in the generated
diagram but are not visible on the diagram itself. In the case of
property conflicts where the values are different, the system
resolves them by appending the name of the property owner.
For example:
Dev1 has the properties:
Prop1 with the value VALUE_1
Dev_Prop with the value VALUE_1
Prop with the value VALUE
Dev_Prop with the value VALUE2
When the properties are merged on a generated device, the
properties are as follows:
Dev_Prop_Dev1 with the value VALUE_1
If the properties of a pin need to have conflicts resolved, the
new properties on the generated diagram will have names in
the form
776 <Property_Name>_<Pin_Owner_Name>_<Pin_Name>.
Capital® Integrator™ User Guide, 2015.1
Mandatory. February 2016

Selected) (cont.)
Field Description
Merge Combined Device Displayed only if you have selected Generate Functionally
Properties Partitioned Diagrams or Generate Custom Partitioned
Diagrams with a Slot Internal Connectivity setting of
Minimum or All. It is enabled only if Utilize Combined
Devices is checked.
Select this option if you want combined devices in the
functionally-partitioned diagrams to inherit properties and
attributes from all functional source devices. The device
names will be prefixed with the functional device names if
there is a naming conflict.
Do not select this if you want combined devices to inherit the
properties and attributes from one functional source device
that is selected randomly but deterministically.
Mandatory.
Hide Unconnected Pins and Displayed only if you have selected Generate Functionally
Connector Cavities Partitioned Diagrams or Generate Custom Partitioned
Diagrams.
Specify whether you want unconnected pins and connector
cavities on objects to be hidden in the generated diagrams
(selected). Mandatory.
See “Connector Refinement and Signal Mapping” on page 209
for an overview of refining connectors.
inline connectors are not supported. If refined connectors in
the harness levels included in the current run of Capital
AutoView Assist for Integrator conflict, they are ignored.
Copy Graphics and Border Displayed only if you have selected Generate Functionally
from Prototype Partitioned Diagrams and applies if you are using a prototype
(template) for generated diagrams.
Specify whether you want to use the border and graphics from
the prototype on the generated diagram (selected) or whether
you want the generated diagrams to use the border and
graphics from the original functional diagrams (unselected).
Mandatory.

February 2016

Selected) (cont.)
Field Description
Strictly Use Prototype During Displayed only if you have selected Generate Functionally
Wiring Distribution Partitioned Diagrams and applies if you are using a prototype
(template) for generated diagrams.
Select this option if you want the generated diagram to strictly
follow the prototype. For example, if you delete an instance of
a wire (that has multiple instances) in the prototype, then the
deleted instance will not be generated in the newly generated
diagram.
Do not select this option if you want the generated diagram to
include wiring content that is not present in the prototype.
Mandatory.
Distribute Inlines By Home Displayed only if you have selected Generate Functionally
Condition Partitioned Diagrams.
If you do not select this, the inline connectors are distributed
such that their placement depends on the nearest devices and
the wiring diagram sequence.
Select this option if you want to distribute inline connectors
across the generated wiring diagrams using the home
condition set on the functional source signal (set in Capital
Logic) to which the inline connector belongs.
In this case, an inline connector is distributed to all of the
generated diagrams where the functional signal of its attached
wire conductor’s home condition is set. If the functional signal
of the attached wire is an equipotential conductor or belongs to
an equivalence set, then the inline is distributed to all the
diagrams wherever the conductors of the equivalence set are
home objects. It is assumed that if any of the functional
conductor schematics on a diagram is a home object (that is,
its home condition is set), then all of its conductor schematics
on that diagram are considered to be home objects.
Mandatory.
Create Ported Wires where This is displayed only if you have selected Generate
Functional Nets are Ported Functionally Partitioned Diagrams.
If you select this, any nets that are ported in the associated
functional diagrams will be ported in the generated diagrams.
If you do not select this, any nets that are ported in the
associated functional diagrams will not be ported in the
generated diagrams but will be closed by a splice.
Mandatory.

February 2016

Selected) (cont.)
Field Description
Multicore Indicator Offset This is displayed only if you have selected Generate
Specify the offset in pin grids between multicore indicators
and the end of the multicore. Mandatory.
For example:

February 2016

Selected) (cont.)
Field Description
Wire spacing When multiple, parallel-running wires use the same guided
This is displayed only if you layout from the functional (system) designs, there may be
have selected Generate results where wire decorations overlap. In these cases, you can
Functionally Partitioned configure this Wire Spacing parameter.
Diagrams or Generate This parameter specifies the distance (measured in pin grids)
Custom Partitioned between the newly generated wires which are following the
Diagrams. same guided layout. This parameter is not used for any other
wire routing (additional wires get routed using the default
spacing of 1 grid unit).
For example:
Wire spacing = 1
Wire spacing = 10

February 2016
Table 24-59. Options Tab (with Custom Partitioned Diagrams Selected)

Field Description
Partitioning Property Displayed only if you have selected Generate Custom
Select the user-defined property that has been set on the
functional devices and pins in the associated Capital Logic
designs to control the partitioning of the generated wiring
designs. Mandatory.
Slot Internal Connectivity Displayed only if you have selected Generate Functionally
Diagrams.
Select one of the following:
• None - Select this if you do not want the wiring diagrams
to include any slot-internal connectivity. In this case,
device names and pin names are generated from the names
of the slots in which they are located in the Capital
Integrator design.
• Minimum - Select this if you want the wiring diagrams to
include slot-internal connectivity only if it is required to
display slot-external connectivity correctly. In this case,
device names and pin names are taken from the functional
designs in Capital Logic.
• All - Select this if you want the wiring diagrams to include
all slot-internal connectivity. In this case, device names
and pin names are taken from the functional designs in
Capital Logic.
Mandatory.
See “Generation of Slot Connectivity in Partitioned Diagrams”
on page 611 for a detailed description of how slot-internal
connectivity is generated in these different modes.

February 2016

Field Description
Exclude slot graphics This is available when you select All or Minimum for 'Slot
Internal Connectivity' and is relevant to a work flow that uses
Capital Publisher.
If you do not select this option, internal connections and
objects are created and the external facing pins are mated to a
virtual slot object. The connectors then all mate to that device.
This causes problems if you want to perform ‘click and sprout’
(where connectivity is automatically rendered) on the internal
connectivity in Capital Publisher. This is because the slot can
have many pins and ‘click and sprout’ will show a large device
that can make the generated diagram hard to read.
If you select this option, CAVAI produces diagrams with no
slot devices. This means, all the internal devices can be
selected in Capital Publisher without having to navigate
through the slot device and you are able to perform 'click and
sprout' on that internal connectivity. Therefore, generated
designs are more easily analyzed within Capital Publisher.
Service technicians and end-of-line engineers can easily trace
the internal connections of a slot, such as the fuses in a power
distribution board, and this helps them to identify faults
quicker.
Always Add Ground Paths Displayed only if you have selected Generate Functionally
Diagrams.
Specify whether you want Capital AutoView Assist for
Integrator to add ground paths on every wiring diagram as
required (selected) or not (unselected). Ground paths include
wires, inline pairs, splice segments and the ground terminal
itself. Mandatory.
Distribute Splices This is displayed only if you have selected Generate
Select this option if you want to distribute splice connectivity
across the generated wiring diagrams. Splice symbols can be
broken and distributed across each sheet to provide a
continuous path on every sheet. This is an alternative to a
conservative view in which the entire splice is represented on a
single sheet. Mandatory.
For an example of a generated wiring diagram with and
without distributed splices, see “Wiring Diagram with and
without Distribute Splices selected” in the Usage Notes
section at the bottom of this topic.

February 2016

Field Description
Pin and Device Name This is displayed only if you have selected Generate
Retention Functionally Partitioned Diagrams or Generate Custom
of None.
In some cases, the pin names in the generated designs do not
match those in the original Capital Logic functional designs.
Select this option if you want to display the original pin names
on the generated diagram when this is the case. In the
generated design:
• The original pin name is stored as a property on the pin and
is set as visible.
• The generated name of the pin is not set as visible so is not
• The functional source name for a device is retained only if
it is the only device in a slot.
• The functional source name for a pin is retained only if it is
the only pin representing a cavity and it represents a single
cavity (that is, a one to one mapping).
Do not select this option if you want to display the generated
pin names.
Mandatory.
Utilize Combined Devices This is displayed only if you have selected Generate
of Minimum or All.
In Capital Integrator, devices can be combined to create a
single entity and signal.
Select this option if you want the devices to remain combined
in the functionally-partitioned diagrams. Do not select this if
you want the devices to be separate in the functionally-
partitioned diagrams and if you want multiple paths to be
generated to each shared device pin.
This is ideal for combining ground symbols. You do not
necessarily know that they are combined until you create the
physical representation of them. At that time, you can combine
them in Capital Integrator and use this option to recognize that
change.
Mandatory.

February 2016

Field Description
Property Retention This is displayed only if you have selected Generate
of None.
In some cases, there is a conflict between the values of the
properties on the pins or devices in the functional source
diagrams. This can be the case if multiple functional pins have
been mapped to one pin in Capital Integrator or if multiple
functional devices have been placed in one slot in Capital
Integrator.
If you do not select this, the properties of the functional source
pins and devices are not copied onto the pins and devices in
the generated diagrams.
Select this if you want to store all of the conflicting property
values in separate properties on the objects in the generated
diagrams. Any properties that are modified are visible in the
Edit Properties facility for the object in the generated
diagram but are not visible on the diagram itself. In the case of
property conflicts where the values are different, the system
resolves them by appending the name of the property owner.
For example:
Dev_Prop with the value VALUE_1
Dev_Prop with the value VALUE2
When the properties are merged on a generated device, the
properties are as follows:
If the properties of a pin need to have conflicts resolved, the
new properties on the generated diagram will have names in
the form
<Property_Name>_<Pin_Owner_Name>_<Pin_Name>.
784 Mandatory. Capital® Integrator™ User Guide, 2015.1
February 2016

Field Description
Merge Combined Device Displayed only if you have selected Generate Functionally
Properties Partitioned Diagrams or Generate Custom Partitioned
Diagrams with a Slot Internal Connectivity setting of
Minimum or All. It is enabled only if Utilize Combined
Devices is checked.
Select this option if you want combined devices in the
functionally-partitioned diagrams to inherit properties and
attributes from all functional source devices. The device
names will be prefixed with the a functional device names if
there is a naming conflict.
Do not select this if you want combined devices to inherit the
properties and attributes from one functional source device
that is selected randomly but deterministically.
Mandatory.
Hide Unconnected Pins and Displayed only if you have selected Generate Functionally
Connector Cavities Partitioned Diagrams or Generate Custom Partitioned
Diagrams.
Specify whether you want unconnected pins and connector
cavities on objects to be hidden in the generated diagrams
(selected) or whether you want to display unconnected pins in
the generated diagrams (unselected). Mandatory.
inline connectors are not supported. If refined connectors in
the harness levels included in the current run of Capital
AutoView Assist for Integrator conflict, they are ignored.

February 2016

Field Description
Multicore Indicator Offset Displayed only if you have selected Generate Functionally
Diagrams.
Specify the offset in pin grids between multicore indicators
and the end of the multicore. Mandatory.
For example:

February 2016

Field Description
Wire spacing When multiple, parallel-running wires use the same guided
This is displayed only if you layout from the functional (system) designs, there may be
have selected Generate results where wire decorations overlap. In these cases, you can
Functionally Partitioned configure this Wire Spacing parameter.
Diagrams or Generate This parameter specifies the distance (measured in pin grids)
Custom Partitioned between the newly generated wires which are following the
Diagrams. same guided layout. This parameter is not used for any other
wire routing (additional wires get routed using the default
spacing of 1 grid unit).
For example:
Wire spacing = 1
Wire spacing = 10

February 2016
Table 24-60. Filter Tab

Field Description
Configuration Displayed only if vehicle configurations have been defined for
the Capital Integrator design.
Select the vehicle configurations for which you want to
generate the wiring diagram or diagrams. The generated
wiring diagrams contain all objects that are active in at least
one of the vehicle configurations.
When you select configurations from the list, details about the
harnesses (including the harness level for those configurations
and supported options are displayed in the Harness field.)
Mandatory.
Diagram Partitioning Displayed only if you have selected Generate Functionally
Displays the Diagram Partitioning Dialog Box that enables
you to specify whether you want to generate only one or
multiple diagrams for each of the functional designs from
Capital Logic that have been associated with the Capital
Integrator design. You also specify how you want to partition
the data in the diagrams (based on either configurations or
options).
Harness The content of this field is determined by the Configuration
field.
Select the harnesses that you want to be rendered in the
generated wiring diagrams. Mandatory.
The selection of particular harnesses means that Capital
AutoView Assist for Integrator renders the following in the
generated diagrams:
• Conductors, connectors, multicores and splices that are
active in the selected configurations and that belong to the
selected harnesses.
• Devices (and their pins) that are active in the selected
configurations, that are not integral to a harness and that
are connected to at least one of the selected harnesses.
configurations and that are integral to the selected
harnesses.

February 2016
Table 24-60. Filter Tab (cont.)

Field Description
Design Lists the Capital Logic designs that are associated with the
topological design. You can restrict the objects that are
rendered in the generated wiring diagram by selecting
particular associated designs. By default, all designs are
selected. Mandatory.
By selecting particular designs (and configurations if
available), you restrict the objects that are rendered in the
generated diagrams to the following:
configurations and that have functional sources in the
selected Capital Logic designs
• Wires and splices that are active in the selected
configurations and that belong to the signals that have
functional sources in the selected Capital Logic designs.
This includes signals that represent net equivalence sets
with at least one functional source in the selected
functional designs.
• Multicores that include at least one conductor that is active
in the selected configurations and that belong to the signals
that have functional sources in the selected Capital Logic
designs.
• Shields that are active in the selected configurations,
belong to the signals that have functional sources in the
selected Capital Logic designs and that connect to
• Connector pins attached to the conductors that are rendered
in the generated diagrams.
• Connectors whose pins are rendered in the generated
diagrams.
• Connector pins of the rendered connectors that have mated
connector pins rendered in the generated diagram.

February 2016
Table 24-61. Slot GraphicsTab

Field Description
Slot Graphics Tab Displayed only if you have selected a Slot Internal
Connectivity setting of Minimum or All on the Options tab.
This tab enables you to edit the graphical properties for the
objects created from slot-internal connectivity. See
“Specifying How an Object is Displayed Graphically in a
Diagram” on page 284 for more information about editing
graphical properties.
Table 24-62. Prototype Tab

Field Description
Prototype Tab Displayed only if you have already used the Capital AutoView
Assist for Integrator feature to generate wiring diagrams for a
Capital Integrator design in the project. Never displayed when
Generate Topology Led Diagram is selected.
You can use a generated wiring diagram or build list as a
template for a new wiring diagram or build list of wiring
diagrams.
See “Translation of Objects When Generating Diagrams Using
Templates (Prototypes)” on page 595 for more information.
Use Build List Prototype Displayed only if you have already used the Capital AutoView
Assist for Integrator feature to generate a build list of wiring
diagrams for a Capital Integrator design in the project.
Specify whether you want to use a build list as the prototype
(selected) or whether you want to use a diagram (unselected).
Mandatory.
This option controls whether the Prototypes and Short
Description fields or the Build Lists and Contents fields are
displayed.
Prototypes Displayed only if Use Build List Prototype is not selected.
Select the existing wiring diagram to use as a template
(prototype). To unselect a diagram, hold down the CTRL key
and click the diagram. Optional.
A logical design is available as a template:
• If the design’s base UID matches that of the selected
topological diagram
• If the design has a property SOURCE_PLANE_ID with a
non-blank value

February 2016
Table 24-62. Prototype Tab (cont.)

Field Description
Build Lists Displayed only if Use Build List Prototype is selected.
Select the existing build list of wiring diagrams to use as a
template (prototype). To unselect a build list, hold down the
CTRL key and click the build list. Optional.
A build list is available as a template:
• If it was created by an earlier run of Capital AutoView
Assist for Integrator (this is determined using internal data
that associates the design UID with the build list)
• If it contains a design with a non-blank value for the
property SOURCE_PLANE_ID
Integrator Design Displays the name of the Capital Integrator design for which
the selected design in the Prototypes window or the selected
build list in the Build Lists window was generated. Read-only.
Short Description Displayed only if Use Build List Prototype is not selected.
Displays the short description for the selected diagram in the
Prototypes field. Read-only.
Description If “Use Build List Prototype” is selected, this displays the
description for the build list selected in the Build Lists field.
If “Use Build List Prototype” is not selected, this displays the
vehicle configuration, vehicle model and harness levels for the
selected diagram in the Prototypes field.
Read-only.
Contents Displayed only if Use Build List Prototype is selected.
Lists the diagrams in the selected build list in the Build Lists
field. Read-only.
Usage Notes
The following examples are available:
• Wiring Diagram with and without Distribute Splices selected

• Wiring Diagram with and without Create Ported Wires where Functional Nets are
Ported Selected
• Wiring Diagrams with different Minimum Wire Spacing settings
Figure 24-2. Wiring Diagram with and without Distribute Splices selected

February 2016
Example of a Wiring Diagram with and without Distribute Splices selected:
You have two functional diagrams in Capital Logic as follows:
They are associated with the following Capital Integrator design:
If you do not check the Distribute Splices option, the generated wiring diagrams are as follows:

February 2016
If you do check the Distribute Splices option, the generated wiring diagrams are as follows:
Figure 24-3. Wiring Diagram with and without Create Ported Wires where
Functional Nets are Ported Selected
Example Wiring Diagram with and without “Create Ported Wires where Functional Nets are
Ported” selected
These are the ported nets in the associated functional diagrams:

February 2016
With Create Ported Wires where Functional Nets are Ported selected, the wires in the
generated diagram are ported:
Without Create Ported Wires where Functional Nets are Ported selected, the wires in the
generated diagram are not ported but are closed by a splice:
Figure 24-4. Wiring Diagrams with different Minimum Wire Spacing settings
Examples of Wiring Diagrams with different “Minimum Wire Spacing” settings:
The following shows a diagram with a Minimum Wire Spacing of 3 and a diagram with a
Minimum Wire Spacing of 1.

February 2016
As a result of the figure that you enter:
• The size of devices or inline connectors may increase. This could cause the overlapping
of devices or inline connectors with other logical devices. See Case 1 in the diagram
below.
• Routing may not be optimal at bundle junctions if there is not enough space to route the
wires. See Case 2 in the diagram below.

February 2016
Related Topics
Functional Diagrams
Diagrams

February 2016
Diagram Partitioning Dialog Box

To access: Click Diagram Partitioning on the Filter tab of the AutoView: Generate Wiring
Diagram dialog box.
Use this dialog box to specify whether you want to generate only one or multiple diagrams for
each of the functional designs from Capital Logic that have been associated with the Capital
Integrator design. Also, specify how you want to partition the data in the diagrams (based on
either configurations or options).

February 2016
Objects

February 2016

February 2016
Table 24-63. Diagram Partitioning Dialog Box Contents

Field Description
Partitioning Diagram Per Configuration
Type: Specifies that you want to generate multiple diagrams based on vehicle
configurations for each of the functional designs selected in the “Diagrams
per Configuration Table”.
If you do not select a design, only one diagram is created for it. That diagram
contains all data for all vehicle configurations.
If you do select a design, multiple diagrams are created for it. Each diagram
contains all of the data for one vehicle configuration. Note that if the
connectivity for multiple configurations is the same, only one diagram is
generated for them.
For example:
If there are three configurations VM1, VM2 and VM3 and if VM1 and VM3
have exactly the same content, then two diagrams are generated, that is,
Diagram1:VM3 and Diagram 1:VM1. VM2 is added as a property to
Diagram 1:VM1 as Subset Configuration: VM2.
Note also, if the connectivity for one configuration is a sub-set of the
connectivity for another configuration, only one diagram is generated for
those configurations by retaining the latter generated diagram.
For example:
If there are three configurations VM1, VM2 and VM3 and if the content of
VM1 is a subset of VM3, then two diagrams are generated, that is,
Diagram1:VM2 and Diagram1:VM3.
The names of the generated wiring diagrams are suffixed with the
configuration name.
Option Based Partitioning
Specifies that you want to generate multiple diagrams based on options for
selected functional designs.
If you do not specify any partitioning for a design, the system generates the
same number of diagrams as it has already.
When you select a functional design in the “Configure Diagram Partitions -
Functional Design”, you can specify as many partitions as you want for it in
the Diagram Partitions table.
Custom Partitioning
If you have developed an extensibility plugin to control your own custom
partitioning mode, the custom mode is listed here. The content of the
Diagram Partitions table is controlled by the plugin.
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.

February 2016
Table 24-63. Diagram Partitioning Dialog Box Contents (cont.)

Field Description
Diagrams per Displayed only if you have selected Partitioning Type: Diagram Per
Configuration Configuration.
Table Lists the functional designs from Capital Logic that have been associated
with the Capital Integrator design. Select the designs for which you want to
generate multiple diagrams based on vehicle configurations (see Partitioning
Type: Diagram Per Configuration).
Select All Displayed only if you have selected Partitioning Type: Diagram Per
Configuration.
Selects all designs in the Diagrams per Configuration Table.
Clear All Displayed only if you have selected Partitioning Type: Diagram Per
Configuration.
Unselects all designs in the Diagrams per Configuration Table.
Invert Displayed only if you have selected Partitioning Type: Diagram Per
Selection Configuration.
Unselects any selected designs in the Diagrams per Configuration Table and
selects any unselected designs.
Configure Displayed only if you have selected Partitioning Type: Option Based
Diagram Partitioning.
Partitions - Lists the functional designs from Capital Logic that have been associated
Functional with the Capital Integrator design.
Design
Select a design for which you want to generate multiple diagrams based on
options (see Partitioning Type: Option Based Partitioning); the currently
specified diagram partitions for the design are displayed in the Diagram
Partitions table where you can specify further partitions.

February 2016
Table 24-63. Diagram Partitioning Dialog Box Contents (cont.)

Field Description
Diagram Displayed only if you have selected Partitioning Type: Option Based
Partitions table Partitioning or Partitioning Type: Custom Partitioning.
If you selected a Partitioning Type: Custom Partitioning mode, the content of
this table is controlled by the extensibility plugin.
If you selected Partitioning Type: Option Based Partitioning, this table
displays:
• the options that are supported by the design selected in the “Configure
Diagram Partitions - Functional Design drop-down list
• the diagrams that will be generated for the design
By default, each diagram can include content for all of the options supported
by the design.
To create a new diagram partition (that is, a separate diagram), select one of
the existing diagrams that you want to partition further and click the
button; the new partition is added to the table.
For each diagram partition, select the options that it supports. Only content
relevant to those options can be included in it.
To delete a diagram partition, select it and click the button.
You can copy an existing diagram partition by selecting it and clicking the
button.
With a diagram partition selected, you can click Select All to select all of the
options or you can click Clear to unselect all of the options.
Undistributed If an option is not supported by any of the diagrams, content relevant to that
Content option is added to an additional diagram. This specifies the name of that
Diagram diagram.
Name
Related Topics
Functional Diagrams
Diagrams

February 2016
Parent Folder Selection Dialog Box
Parent Folder Selection Dialog Box

To access: Click the ellipsis (...) button next to the Parent Folder field in the AutoView:
Generate Wiring Diagram dialog box.
Use this dialog box to select the parent folder (within the project structure) that will contain the
generated wiring design and diagrams.
Objects
Within the browser tree, select the parent folder and click OK.
Related Topics
Functional Diagrams
Diagrams

February 2016
Help Button Landing Pages for Capital Integrator Dialog Boxes
Help Button Landing Pages for Capital

Integrator Dialog Boxes
The following topics are displayed when you click the Help button or press F1 for a dialog box
in the software.
Select Integral Harness Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Combine Levels for Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 805
Define Vehicle Models Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
Give Away Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 806
Set Standardized Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Connector Map Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Fanout Viewer Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 807
Set Variant Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808
Signal Map for Interface Connector Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
Signal Map for Slot Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 809
Edit Physical Scale Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
Edit Diagram Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
Edit Skeleton Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 810
Report Material Statistics Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Select Attributes/Properties for Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Select Inclusion Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Select Output for Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811
Wiring Synthesis Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Add Selected Logical Design Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812
Add Wire Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 812

February 2016
Harness Selection Help
Capital Integrator Design Filter Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813

Combine Devices Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Combine Wires at Cavity Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Edit Levels Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813
Move Wire Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Place Device Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814
Select a Module Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815
AutoView: Generate Wiring Diagram Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815

What do you need help with?
• Understanding Integrator Harness Exchange concepts
• The Harness Selection Dialog Box fields
• Exporting Multiple Harnesses from a Design
Select Integral Harness Help

• The Select Integral Harness Dialog Box fields
• Including a Slot with a Harness
Combine Levels for Help

• The Combine Levels for Dialog Box fields
• Combining Harness Levels into One

February 2016
Configuration Builder Help
Configuration Builder Help

• The Configuration Builder Dialog Box fields
• The Vehicle Configuration concept
• Defining a Vehicle Configuration Based on Options
Define Harness Levels Help

• Understanding composite data concepts (see Composite Data Overview)
• The Define Harness Levels Dialog Box fields
• Specifying the Options that Affect a Harness
• Creating a Harness Level for a Harness
• Editing a Harness Level for a Harness
• Combining Harness Levels into One
• Editing the Properties of a Harness Level
• Importing Harness Level Definitions
• Exporting Harness Level Definitions
Define Vehicle Models Help

• The Define Vehicle Models Dialog Box fields
• Defining Vehicle Models
• Specifying the Platform Options in a Design
Give Away Help

• The Give Away Dialog Box fields

February 2016
Set Standardized Options Help
• Specifying Giveaway Options
Set Standardized Options Help

• The Set Standardized Options Dialog Box fields
• Specifying the Platform Options in a Design
Set Harness Options Help

• The Set Harness Options Dialog Box fields
• Specifying the Options that Affect a Harness
Connector Map Help

• Understanding Device Connectors and Harness Connectors in Capital Integrator
• The Connector Map Dialog Box fields
• Mapping a Footprint Connector to a Slot Connector (Device Connector and Harness
Connector) on a Slot
Fanout Viewer Help

• Understanding Connector Refinement and Signal Mapping concepts
• The Fanout Viewer Dialog Box fields
• Refining a Slot Connector on a Slot
• Refining an Interface Connector
• Refining an Inline Connector

February 2016
Manage Variance Help
Manage Variance Help

• The Manage Variance Dialog Box fields (this dialog box has the heading Signal <Signal
Name> or Multiple signals)
• Creating Variant Wire and Variant Signal Mappings on the Signal Mappings Tab for a
Slot
• Deleting a Variant Wire and Variant Signal Mapping on the Signal Mappings Tab for a
Slot or Inline
• Editing the Variant Option Expression of a Variant Wire Mapping on the Wire Info Tab
for a Slot or Inline
• Creating Variant Signal and Wire Mappings in the Signal Map for an Interface
Connector
• Deleting a Variant Signal Mapping in the Signal Map for an Interface Connector
Set Variant Help

• The Set Variant Dialog Box fields
Slot
Slot or Inline
Connector
Signal Map for Inline Help


February 2016
Signal Map for Interface Connector Help
• The Signal Map Dialog Box for Inline fields

• Refining an Inline Connector
• Mating the Cavities of the Two Halves of an Inline Connector
• Mapping a Signal Between Cavities on the Halves of an Inline Connector
• Creating Variant Wire and Variant Signal Mappings on the Signal Mappings Tab for an
Inline
Slot or Inline
Signal Map for Interface Connector Help

• The Signal Map Dialog Box for Interface Connector fields
• Refining an Interface Connector
• Mapping a Signal to an Interface Connector Cavity
Connector
Signal Map for Slot Help

• The Signal Map Dialog Box for Slot fields
• Refining a Slot Connector on a Slot
• Mapping a Signal to a Hole or Slot Connector Cavity on a Slot
• Mapping a Signal to Multiple Slot Connector Cavities on a Slot
Slot

February 2016
Edit Physical Scale Help
Slot or Inline
• Mapping a Stud Pin to Multiple Ring Terminals
Edit Physical Scale Help

• Specifying the Physical Scale of a Diagram
• The Edit Physical Scale Dialog Box fields.
Edit Diagram Help

• The Edit Diagram Dialog Box fields
• Editing the Name of a Diagram
• Specifying the Style Set Applied to the Diagram
• Adding a Property to a Diagram
• Deleting a Property from a Diagram
Edit Skeleton Help

• The Edit Skeleton Dialog Box fields
• “Adding a Skeleton Graphic to a Diagram” on page 79
• Removing a Skeleton from a Diagram
New Integrator Diagram Help

• The New Integrator Diagram Dialog Box fields
• Creating a Diagram

February 2016
Connectivity Help
Connectivity Help
• The Customized Connectivity Reports concept
• The Connectivity Dialog Box fields
• Creating a Set of Customized Connectivity Reports
Report Material Statistics Help

• The Material Statistics Report concept
• The Connectivity Dialog Box fields
Select Attributes/Properties for Help

• The Select Attributes/Properties for Dialog Box fields
Select Inclusion Help

• The Select Inclusion Dialog Box fields
Select Output for Help

• The Select Output for Dialog Box fields

February 2016
Wiring Synthesis Help
Wiring Synthesis Help

• Understanding Synthesizing Wiring concepts
• Understanding Composite Wiring Synthesis Flows
• The Wiring Synthesis Dialog Box fields
• Synthesizing Modular Wiring
• Regenerating Harness Levels and Finishing Composite Wiring Synthesis
• Generating Initial Harness Levels for Composite Wiring Synthesis
• Deleting Wiring, Harness Levels and Vehicle Configurations
• Running Modular or Composite Wiring Synthesis for Selected Signals
Add Selected Logical Design Help

• The Logical Design Association concept
• The Add Selected Logical Design Dialog Box fields
• Associating Logical Designs with the Topological Design
Add Wire Help

• The Add Wire Dialog Box fields
• Adding a Wire
Assign Wiring Specifications by Rule Help

• The Assign Wiring Specifications by Rule Dialog Box fields
• Assigning Wire / Splice / Multicore Properties by Rules
Associate Logical Designs Help


February 2016
Capital Integrator Design Filter Help
• The Logical Design Association concept

• The Associate Logical Designs Dialog Box fields
• Associating Logical Designs with the Topological Design
• Replacing a Logical Design Association
Capital Integrator Design Filter Help

• The Capital Integrator design Filter Dialog Box fields
• Filtering the Objects Displayed in a Diagram
Combine Devices Help

• The Combine Devices Dialog Box fields
• “Combining Normal Devices in a Slot” on page 189
Combine Wires at Cavity Help

• The Combine Wires at Cavity Dialog Box fields
• Combined Signals and Combined Wires concepts
• Combining Wires at a Cavity
Edit Ground Signals Help

• The Edit Ground Signals Dialog Box fields
• Editing Ground Signals
Edit Levels Help

• The Edit Levels Dialog Box fields

February 2016
Generate Slot Circuit Help
• Specifying the Harness Levels on which a Wire Exists
Generate Slot Circuit Help

• Understanding Slot Circuit concepts
• The Generate Slot Circuit Dialog Box fields
• Generating a Slot Circuit

• The Harness Selection Dialog Box fields
• Exporting Wiring from a Capital Integrator Design
• Importing Wiring into a Capital Integrator Design
Import Harness Help

• The Import Harness Dialog Box fields
• The Import of Carry-Over Wiring concept
• The Integrator Harness Exchange concept
Move Wire Help

• The Move Wire Dialog Box fields
• Moving a Wire
Place Device Help

• Concept information for Placement of a Device or Ground Device in a Slot
• The Place Device Dialog Box fields

February 2016
Select a Module Help
• Manually Placing a Normal or Ground Device in a Slot
Select a Module Help

• Module Code Management concepts
• The Select a Module Dialog Box fields
• Moving Wiring Between Modules
• Sharing Wires Between Modules
Select Module Code Help

• Module Code Management concepts
• The Select Module Code Dialog Box fields
• Renaming a Module
Variant Expression Editor Help

• The Edit Levels Dialog Box fields
• Specifying Variant Physical Lengths for a Bundle
AutoView: Generate Wiring Diagram Help

• Understanding Capital AutoView Assist for Integrator concepts
• The AutoView: Generate Wiring Diagram Dialog Box fields
• Generating a Single Design with Partitioned Wiring Diagrams Based on the Layout of
Functional Diagrams
• Generating a Build List with Partitioned Wiring Diagrams Based on the Layout of
Functional Diagrams
• Generating a Topology-Led Wiring Diagram
• Generating Custom Partitioned Wiring Diagrams According to a User-Defined Property

February 2016
Diagram Partitioning Help
Diagram Partitioning Help

• The Diagram Partitioning Dialog Box fields
Functional Diagrams
Functional Diagrams
Parent Folder Selection Help

• The Diagram Partitioning Dialog Box fields
Functional Diagrams
Functional Diagrams
• Generating a Topology-Led Wiring Diagram
• Generating Custom Partitioned Wiring Diagrams According to a User-Defined Property

February 2016
Chapter 25
Bridges
Full details on how to bridge data in, and out of Capital Systems, use the bridges and their
functionality is contained within the Bridging Data In and Out of Capital Systems User Guide.
Capital Integrator Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817
Capital Integrator Bridges

Bridges are applications that permit the exchange of design data between Capital and other
enterprise design systems using either intermediate file transfer or by direct connection.
Bridges provide two generic functions:
• Bridge Out - the exportation of Capital design or build list data in a format acceptable to
third party design systems.
• Bridge In - the re-importation of design or build list data, that was previously authored
and bridged out from Capital and since modified, using a third-party design system.
File translators, known as the Bridges (that are specific to each third-party design system),
automatically re-format the outgoing and incoming design data to the specific format required
by each system.
During the bridge out procedures, design data is initially extracted from Capital as an X2ML
formatted file. X2ML is the Capital 3D Wiring proprietary XML-based format that is used by
the Bridges to create a suitably formatted design file for the various third-party design systems.
For example, when using the CATIA V5 Electrical Adapter, the Capital design data is initially
(and invisibly) exported using the X2ML format before being automatically re-formatted to a
Dassault Systèmes iXF formatted XML file.
Note
If the harness is split across multiple diagrams, all parts of the harness are exported. The
system re-combines the harness parts so that the bridged-out file contains a harness laid out
correctly. For example, a harness, laid out left to right, is split in the middle. The left half is on
diagram 1 and the right half is on diagram 2. The resulting file contains a harness with the two
halves combined using common coordinate spacing and scaling. The system translates the
diagram points to make this happen. If the layout of one part has been significantly modified
(such as, rotated), the resulting re-combined, bridged-out harness may not have an expected
layout. All components are connected but you may need to manually adjust the layout.

February 2016
Bridges
Capital Integrator Bridges
Conversely, whenever a third-party design system's design file is bridged into Capital, the
Bridges automatically convert the file to the X2ML format prior to importing the design data
into Capital.
Note
Before you can use Bridges the bridge types that you wish to utilize, and hence wish to
appear in the Files of Type list in the Bridge Data In/Bridge Data Out dialog boxes, must
be un-commented in the 1- Adaptors declarations section of the adaptors.xml file. Once un-
commented, the same adaptors will appear in all applicable Capital product bridge lists. For
guidance see the Usage Example - Modifying the Adaptors xml File in the “Bridging Data In
and Out of Capital” User Guide.
For further information, see the Bridging Data In and Out of Capital User Guide.

February 2016
Chapter 26
Capital Level Manager- Product Planner
This chapter contains information about Capital Level Manager - Product Planner.
Introduction to Product Planner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820
Enabling Capital Level Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 828
Optimization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829
Hierarchy of Product Planner Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834
Product Planner Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835
Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
Importing a Product Plan in XML Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837
Exporting a Product Plan in XML Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
Troubleshooting a Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841
Creating a Variant in the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
Deleting a Variant from the Product Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
Creating a Mutually-Exclusive Variant . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
Deleting a Mutually-Exclusive Variant Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
Importing Variant Group Data in XLS Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
Exporting Variant Group Data in XLS Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
Vehicle Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
Adding a Vehicle Model to the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849
Deleting a Vehicle Model from the Product Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
Splitting a Vehicle Model in the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
Editing the Association of a Package with a Vehicle Model . . . . . . . . . . . . . . . . . . . . . . . 852
Editing the Association of an Option from a Package with a Vehicle Model . . . . . . . . . . 853
Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
Adding an Option to the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
Deleting an Option from the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
Creating an Exclusive Group of Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
Creating an Inclusive Group of Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
Deleting an Inclusive Group of Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863

February 2016
Introduction to Product Planner
Adding a Package to the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865

Deleting a Package from the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
Creating an Exclusive Group of Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
Creating an Inclusive Group of Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
Deleting an Inclusive Group of Packages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
Creating a Must Have or Not Available Restriction on a Package. . . . . . . . . . . . . . . . . . . 872
Deleting a Must Have or Not Available Restriction on a Package. . . . . . . . . . . . . . . . . . . 874
VVD - Vehicle Variant Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 875
EVD - Electrical Variant Definition. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876
Generating VVD and EVD Counts for a Vehicle Model . . . . . . . . . . . . . . . . . . . . . . . . . . 876
Vehicle Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
Take Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877
Editing the Take Rates for Vehicle Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879

Capital Level Manager is an add-on to Capital Integrator. The two main elements of it are the
Product Planner and the Harness Level Optimization tool.
See Capital Level Manager - Harness Level Optimization for more information about it.
The Product Planner is a tool that allows you to model vehicle-level Product Plans, obtain
information regarding permutations of orderable vehicles (VVDs) or domain-specific orderable
vehicles (EVDs), and define volume and take rate information.
Data from the Product Planner is used as input by the Capital Level Manager - Harness Level
Optimization tool.
Note
Capital Level Manager requires a valid license in order to enable (expose) the functionality.
Contact Capital Support to obtain a license. If you possess a valid license, see “Enabling
Capital Level Manager” on page 828.
Consumer Choice versus Purchasing Reality

For most consumers the ability to purchase an automobile with exactly the features and options
they want is often not possible. Their choices must fit within a pre-defined set of available
options that may or may not be available in the combinations that they prefer. These restrictions
to the customer’s purchasing freedom can lead to dissatisfied customers and potentially loss of
sales.

February 2016
Offering the customer freedom of choice clearly has an economic benefit. In the following, we
review how option content affects the way in which a vehicle can be purchased. Later, we look
at how these permutations of possibilities affect the engineering domain.
Unconstrained Vehicle Complexity

To begin, consider how option content affects the whole vehicle. The following example is a
very simple case in which there are three options: Hand of drive (LHD/RHD), Fog Lamps and
Anti-lock Brakes. Since there are no constraints in how these options can be ordered, the
number of possible ways to order this vehicle is eight.
Essentially, every new option doubles the number of possible permutations as can be
represented by the simple formula of 2n. This is an oversimplification, but the point is that as
the number of options increases, the number of orderable possibilities increases at an
exponential rate. An average vehicle could easily have hundreds of options to choose from
which can lead to billions of possibilities, or more.
Constrained Vehicle Complexity

To reduce this exponential increase of orderable possibilities, the marketing departments of
automotive OEMs will eliminate orderable possibilities by applying restrictions. These
restrictions constrain the permutations, but at the cost of hindering consumer choice.
Using the previous example, assume that marketing research shows that in RHD markets most
consumers typically purchase Fog Lamps. To constrain the complexity, they may then decide to
create a restriction that all RHD vehicles must-have Fog Lamps. The effect of this is that entire
branches of the tree are eliminated. In the following diagram, note that the final number of
orderable combinations is reduced to six.

February 2016
While this has constrained the vehicle complexity, it has added an additional burden to the
organization as there is now a restriction (RHD must-have Fog Lamps) that must be
documented, understood and taken into account in designs.
Composite Wire Harness Complexity

Any product that varies based on the ordered options must have a method of coping with this
variation. For example, if a wire harness has a connector for the Fog Lamp bulbs, then a method
of supporting vehicles that have the bulbs and supporting vehicles that do not have the bulb
must be used.
One method is called a modular approach, where each option is released as a unique module.
When the option content of a specific vehicle is known, the various modules are combined with
a base harness to create a custom wire harness for that specific vehicle.
A more common approach is a composite (or derivative) design approach, in which unique
designs are released for each possible combination. In the above example, there would have to
be derivatives that have fog lamps and some that do not. It is this approach that Capital Level
Manager supports.
Unconstrained Harness Complexity

The optional wiring content defines for which options a given harness is made complex. Just as
adding options at a vehicle level causes an exponential growth in the number of orderable
possibilities.
Consider the previous example. Assume that this very simple vehicle has a very simple wire
harness architecture consisting of two wire harnesses. The first has wiring content for Fog
Lamps and is routed differently depending upon the hand-of-drive (LHD or RHD). The second
has wiring for the Antilock Brake System. The resulting complexity is displayed in Figure 26-1.

February 2016
Figure 26-1. Unconstrained Harness Complexity
There are a total of five harness levels (or derivatives) for the entire vehicle. If another option
were added to Harness 1, the number of levels would double from three to six. Note that in
Harness 1 there is no level that is RHD without Fog Lamps. Remember that earlier the OEM
Marketing department stated that the RHD must have Fog Lamps. The engineer for this harness
has had to understand that restriction, interpret it, and act accordingly to remove that level from
the complexity.
Harness Complexity with Giveaway

Just as additional options can exponentially increase the number of orderable permutations of
vehicles, the same is true for harness complexity. You have already seen how Marketing can
constrain the vehicle complexity through restricting how a customer can order the vehicle.
Engineers likewise have a mechanism for constraining harness complexity. This is called
giveaway. Giveaway occurs when an engineer decides to delete a level that is missing optional
content and replace it with a level that has the content. Consider Harness 1 from our previous
example. If the engineer decides to giveaway Fog Lamps, one level is eliminated.

February 2016
Note that this in no way changes how the customer orders the vehicle. If the vehicle is ordered
without Fog Lamps, the vehicle will still not have functioning Fog Lamps because the necessary
switches, bulbs fuses, and so on, will be missing. However, a wire harness that has the
necessary wiring will be placed in the vehicle. This additional wiring has an associated cost and
weight that must be accounted for. It can be challenging to understand exactly what these costs
are.
Complexity Management Costs

As already covered, Marketing departments and engineers are working to constrain complexity
and eliminate orderable possibilities. This can have a negative impact on customer satisfaction
and ordering habits and has a costly impact in the engineering domain. Since there are clearly
negative impacts to constraining the complexity, why would you do it?
There are costs that increase as the number of levels increases. These are called Complexity
Management costs. The following are just a few examples. There are many other types
depending on the engineering and business realities of the organization.
• Production Costs
There are many areas where production costs increase. A simple example is in-line
changeover. Production processes are most efficient when there is as little variation in
the vehicles being constructed as possible. A unique level is by definition a unique
variation of the vehicle. The need to stop the line, make the appropriate changes to the
tooling/fixtures, then start the line again is inefficient and costly.

February 2016
• Sequencing
As the number of harness levels increases, it becomes impossible for the vehicle
production line to physically house bins for each level because there is not enough floor
space. The alternative is to have an external facility (normally a third party) to house
these parts, then ship them into the plant in sequenced order based on the vehicle
production sequence. This can become extremely expensive.
• Inventory
As the number of harness levels increases, more inventory must be maintained
throughout the manufacturing process. This leads to additional storage space and
additional costs for logistics and rework.
• Obsolescence
There are a number of ways in which this can be costly. One example is end-of-year
obsolescence as new designs come in for the new vehicle. Most suppliers will only ship
parts in minimum pack sizes (usually around thirty parts to a box). If during the year
only one part has been used out of the box, the other twenty nine must be destroyed,
reworked or recycled. As the number of harness levels increases, the production
volumes of each level decrease and lead to more of this type of obsolescence.
Complete Cost Model

To accurately understand how complexity affects the final cost of a product, it is imperative that
not only the implications of piece costs be understood, but the complexity management costs as
well.
A purely piece cost view of the world acts as an incentive for the organization to eliminate as
much giveaway as possible which results in a large number of harness levels. This is shown in
the curve that decreases left to right in the figure below.

February 2016
A purely complexity management cost view of the world acts as an incentive for using
maximum giveaway to reduce the number of levels to as few as possible. This is the linearly
increasing line in the figure.
If we combine these two views of the world into a complete view of the design, we can find an
optimal solution as shown in the bowl shaped curve, which is the addition of the other two
functions. Note that this is an idealized view of the cost models. Real-world models will have
different shapes depending upon business realities, but the concept still stands.
Process Overview
Capital Level Manager assists the design process by automatically generating the unconstrained
wire harness complexity (called full complexity), then by allowing the user to define giveaway
scenarios and immediately feeding back the resulting cost implications. Additionally, it can
validate that an existing design will meet all of the requirements of the full complexity solution.
To understand this, below is a very high-level flow.

February 2016
Note that there are three primary inputs needed to create harness complexity:
• A product plan describes the options, vehicle models, restrictions, and so on. It can also
optionally describe the take rates for each option so that the expected volumes of all
orderable possibilities can be calculated.
• The system designs describe the logical connectivity of the electrical system. These
designs are tagged with option expressions so that it is understood how the connectivity
changes based on the ordered options.
• The wiring architecture describes the physical aspects of the design in a topological
manner. The key concepts are what are the harnesses, what device connectors are they
connected to, and how do all of the harnesses interconnect through inlines.
Once the three primary inputs are understood, Capital Level Manager can automatically
calculate the full complexity requirements.
Based on the full complexity requirement, the user can then define giveaway in the Harness
Level Optimization step.
Once an optimal giveaway solution is found and the final harness complexity is chosen, the
resulting levels can automatically be used during Composite Wiring Design in a generative
flow. This process creates physical wiring for each harness level.
Lastly, the Design Validation step will allow the user to compare a design against a set of full
complexity requirements. This can be useful for:
• Ensuring that a released design still meets the requirements and has not been
inadvertently altered.
• Determining whether new marketing requirements invalidate a previously released
design.
• Confirming that an externally created complexity solution meets the complete vehicle
requirements and determining the cost associated with this complexity solution.
For a more detailed description of the individual steps in this process, see “High-Level Flows
for Using Capital Level Manager Product Planner and Harness Level Optimization” on
page 829.
Related Topics
Enabling Capital Level Manager
Optimization
Hierarchy of Product Planner Elements
Product Planner Concepts

February 2016

In order to use Capital Level Manager functionality, you must have a valid license and you must
enable (expose) the functionality in one of the following ways.
• Edit Capital Configuration Dialog
Open the Capital Launcher and click the Configuration option from the Support
section; the Edit Capital Configuration dialog box is displayed. At the bottom of the
dialog box, select the Enable Insight, Enable Product Planner and Enable Harness
Optimization options. Click Apply or OK.
• clientprops.xml file
Edit the clientprops.xml file, located in the config sub-directory of your Capital
installation directory, so that the <packages> section contains the entries below for the
Product Planner (lvlmgr_plan), the Harness Level Optimization tool (lvlmgr_optimize)
and Capital Insight (insight):
<packages>
<feature check="Yes" name="insight"></feature>
<feature check="Yes" name="lvlmgr_optimize"></feature>
<feature check="Yes" name="lvlmgr_plan"></feature>
</packages>
Disabled Functionality When Using Capital Level Manager

When you enable Capital Level Manager, some Capital functionality is disabled:
• The Options dialog box (accessed by pressing Space Bar and entering Options in
Capital Logic and Capital Integrator) is viewable but not editable. You cannot create or
select options from this dialog box because you now edit them in the Product Planner.
• The Define Vehicle Models dialog box (accessed by pressing Space Bar and entering
Models in Capital Integrator) is not available. You cannot create, edit or delete vehicle
models in this dialog box because you now edit them in the Product Planner.
• The Harness Levels dialog box is available but is no longer accessed by pressing Space
Bar and entering Levels in Capital Integrator. Instead, it is available from the Harness
Level Optimization Dialog Box where you click the Define harness levels ( ) button.
Related Topics
Capital Level Manager - Harness Level Optimization

February 2016
Optimization
High-Level Flows for Using Capital Level

Manager Product Planner and Harness Level
Optimization
There are two intended flows for using Capital Level Manager: New Design Flow and Product
Plan Change Flow.
New Design Flow

This particular flow assumes that you are creating the connectivity and topology designs within
Capital. Alternatively, you can bridge in the design data from MCAD via one of the Capital
MCAD bridges. Full details on how to bridge data in, and out of Capital, how to use the bridges
and their functionality is contained within the Bridging Data In and Out of Capital User Guide.
1. Create a project in Capital.

2. In Capital Logic, create the connectivity schematics for the project but do not specify
option expressions for design objects. The option expressions will be specified later.
3. In Capital Integrator, create the topology design for the project but do not create vehicle
models (these are created using product plan data later) and do not specify option
expressions for design objects. The option expressions will be specified later.
4. Either:
o import a Product Plan (see “Importing a Product Plan in XML Format” on page 837)
or
o create a new product plan in the Vehicle Creator Dialog Box. From Capital
Integrator (with the topology diagram open), open the Product Planner by pressing
Space Bar and entering Product Planner; the Product Planner Dialog Box is
displayed.
See “Hierarchy of Product Planner Elements” on page 834 for an overview of how
the plan elements relate to each other.
i. Add Options into the product plan (see “Adding an Option to the Product Plan”
on page 855).
ii. If necessary, group the options into exclusive groups and inclusive groups (see
“Creating an Exclusive Group of Options” on page 857 or “Creating an Inclusive
Group of Options” on page 859).

February 2016
iii. Create Packages of options (see “Adding a Package to the Product Plan” on
page 865 and “Adding Options to a Package” on page 866).
iv. Create Vehicle Models (see “Adding a Vehicle Model to the Product Plan” on
page 849).
v. Specify the association between the packages and the vehicle models (see
“Editing the Association of a Package with a Vehicle Model” on page 852).
vi. Specify the association between the options in the packages and the vehicle
models (see “Editing the Association of an Option from a Package with a
Vehicle Model” on page 853).
vii. Create Variants (for example, LHD and RHD) (see “Creating a Variant in the
Product Plan” on page 842).
You can import this data in XLS format if available (see “Importing Variant
Group Data in XLS Format” on page 846).
viii. Create Mutually-Exclusive Variant Groups (groups of variants that are mutually-
exclusive). These are used for variants such as RHD vs. LHD, Short Wheelbase
vs. Long Wheelbase, and so on. See “Creating a Mutually-Exclusive Variant” on
page 844.
You can import this data in XLS format if available (see “Importing Variant
Group Data in XLS Format” on page 846).
ix. Use the Take Rate Editor Dialog Box to specify volumes and calculate Take
Rate information (see “Editing the Take Rates for Vehicle Models” on
page 879).
x. Specify which options are electrical (see “Specifying an Option as Electrical” on
page 862).
xi. This step is optional. Generate VVD - Vehicle Variant Definitions and EVD -
Electrical Variant Definitions for the vehicle models (see “Generating VVD and
EVD Counts for a Vehicle Model” on page 876).
Any electrical options in the product plan can now be used in option expressions in
Capital Logic and Capital Integrator.
In Capital Integrator, the system has used product plan data at this point to generate
vehicle models.
5. Having created or imported the product plan, link it to the schematics and topology
design by adding option expressions to devices, pins and nets in Capital Logic and
Capital Integrator.
6. Associate the schematic designs with the topology design.
7. Ensure that the devices from the schematic designs are correctly placed in the slots of
the topology design.

February 2016
8. Run Modular Wiring Synthesis functionality on the topology design. This routes signals
through the inline connectors and calculates the option expressions for the inline
connectors. Note that the rules and constraints used in the topology design enable the
system to determine whether it is optional for a signal to pass through an inline
connector.
You can use Design Rule Checks to analyze the synthesis output. If necessary, you can
edit the designs and re-run synthesis until you are satisfied with the output.
At this stage, the system has all the data required to generate Harness Levels in the
Capital Level Manager - Harness Level Optimization tool.
9. From Capital Integrator (with the topology diagram open), open the Harness Level
Optimization tool by pressing Space Bar and entering Optimize Harnesses; the Harness
Level Optimization Dialog Box is displayed.
10. In the Harness Level Optimization tool, select Metrics that can be applied to any
Harness. A metric is a single value calculated as a measure of worth (for example, cost
or weight).
11. As an optional step, create the Full Complexity harness levels. Note that they are
generated automatically when you create the Optimized Complexity builds in the next
step.
To create them prior to generating the optimized complexity builds, generate the full
complexity harness levels for each harness in the Harness Level Optimization dialog
box (see “Manually Generating the Full Complexity Harness Levels for a Harness” on
page 944).
12. Create the optimized complexity builds for the each harness in the Harness Level
Optimization dialog box by specifying which options are to be Giveaway (see “Creating
the Optimized Complexity Harness Levels for a Harness” on page 948).
13. If you have Capital Insight with Capital Integrator, you can run architectural studies on
the builds to assess the designs.
The following step is optional:
14. Validate physical harness levels from a design against the full complexity harness levels
from the product plan. The product plan harness levels are the base requirement and the
physical design is being compared to determine whether anything is incorrect within it.
See “Validating Physical Harness Levels against Full Complexity Harness Levels” on
page 945.
Product Plan Change Flow

This flow assumes that the schematic and topology designs already exist and have had a product
plan applied (as in the new design flow). However, an updated product plan with has been
created.

February 2016
1. From Capital Integrator (with the topology diagram open), import the new Product Plan.
See Importing a Product Plan in XML Format.
2. From Capital Integrator (with the topology diagram open), open the Product Planner by
pressing Space Bar and entering Product Planner; the Product Planner Dialog Box is
displayed.
See “Hierarchy of Product Planner Elements” on page 834 for an overview of how the
plan elements relate to each other.
a. If necessary, create Vehicle Models (see “Adding a Vehicle Model to the Product
Plan” on page 849).
b. If necessary, specify the association between the Packages and the new Vehicle
Models (see “Editing the Association of a Package with a Vehicle Model” on
page 852).
c. If necessary, specify the association between the Options in the packages and the
vehicle models (see “Editing the Association of an Option from a Package with a
Vehicle Model” on page 853).
d. If necessary, create Variants (for example, LHD and RHD) (see “Creating a Variant
in the Product Plan” on page 842).
You can import this data in XLS format if available (see “Importing Variant Group
Data in XLS Format” on page 846).
e. If necessary, create Mutually-Exclusive Variant Groups (groups of variants that are
mutually-exclusive). See “Creating a Mutually-Exclusive Variant” on page 844.
You can import this data in XLS format if available (see “Importing Variant Group
Data in XLS Format” on page 846).
f. Use the Take Rate Editor Dialog Box to specify volumes and calculate Take Rate
information (see “Editing the Take Rates for Vehicle Models” on page 879).
g. Specify which new options are electrical (see “Specifying an Option as Electrical”
on page 862).
h. This step is optional. Regenerate VVD - Vehicle Variant Definitions and EVD -
Electrical Variant Definitions for the Vehicle Models (see “Generating VVD and
EVD Counts for a Vehicle Model” on page 876).
Any electrical options in the product plan can now be used in option expressions in
Capital Logic and Capital Integrator.
In Capital Integrator, the system has used the new product plan data at this point to
regenerate vehicle models.
3. If necessary, create new revisions of all schematic and topology designs in Capital Logic
and Capital Integrator.

February 2016
4. If necessary, update the option expressions on devices, pins and nets in Capital Logic
and Capital Integrator.
5. If necessary, associate the new schematic design revisions with the new topology design
revision.
6. If necessary, ensure that the devices from the schematic designs are correctly placed in
the slots of the topology design.
7. Run Modular Wiring Synthesis functionality on the topology design. This routes signals
through the inline connectors and calculates the option expressions for the inline
connectors. Note that the rules and constraints used in the topology design enable the
system to determine whether it is optional for a signal to pass through an inline
connector.
You can use Design Rule Checks to analyze the synthesis output. If necessary, you can
edit the designs and re-run synthesis until you are satisfied with the output.
At this stage, the system now has all the data required to generate Harness Levels in the
Capital Level Manager - Harness Level Optimization tool.
8. From Capital Integrator (with the topology diagram open), open the Harness Level
Optimization tool by pressing Space Bar and entering Optimize Harnesses; the Harness
Level Optimization Dialog Box is displayed.
9. As an optional step, create the Full Complexity harness levels. Note that they are
generated automatically when you create the Optimized Complexity builds in the next
step.
To create them prior to generating the optimized complexity builds, generate the full
complexity harness levels for each harness in the Harness Level Optimization dialog
box (see “Manually Generating the Full Complexity Harness Levels for a Harness” on
page 944).
10. Create the optimized complexity builds for the each harness in the Harness Level
Optimization dialog box by specifying which options are to be Giveaway (see “Creating
the Optimized Complexity Harness Levels for a Harness” on page 948).
Note
Note that any previously specified giveaway is persisted so the dialog box will be
populated with the last applied giveaway.
11. If you have Capital Insight with Capital Integrator, you can run architectural studies on
the builds to assess the impact of the product plan changes.
The following step is optional:
12. Validate physical harness levels from a design against the full complexity harness levels
from the product plan. The product plan harness levels are the base requirement and the
physical design is being compared to determine whether anything is incorrect within it.

February 2016
See “Validating Physical Harness Levels against Full Complexity Harness Levels” on
page 945.
Related Topics
Harness Level Optimization Tool Concepts

There is a hierarchy of elements in a product plan.
Links to detailed descriptions of the elements are listed in the topic “Product Planner Concepts”
on page 835.

February 2016
Figure 26-2. Product Planner Elements

There are various concepts used within the Product Planner tool.
• “Product Plan” on page 837
• “Option” on page 855

February 2016
o Standard Option
o Exclusive Group
o Inclusive Group
• “Package” on page 863
o Exclusive Group
o Inclusive Group
o Retail
o Fleet
o No Association
o Must Have
o Not Available
• “Vehicle Model” on page 849
• “Variant” on page 841
o “Mutually-Exclusive Variant Group” on page 841
• “VVD - Vehicle Variant Definition” on page 875
• “EVD - Electrical Variant Definition” on page 876
• “Vehicle Configuration” on page 877
• “Take Rate” on page 877

February 2016
Product Plan
Product Plan
A product plan is a marketing requirement that defines a vehicle’s market and optional content.
It defines a set of high-level vehicles that are typically defined by market, trim level, hand-of-
drive, etc.
Most original equipment manufacturers have a particular name for these high-level definitions,
but the generic term is a Vehicle Model. For each vehicle model, the product plan will define
which content is standard and which is optional. For the optional content, it will also define any
restrictions it might have with other options. For example, the rear entertainment system may be
not-available with the 2-pane sunroof because the display and the rear sunroof pane would need
to occupy the same space. Or perhaps the heated seat option must have the leather seat option
because marketing has found that very few people order heated seats with cloth.
Some subset of the optional content defined in the product plan will affect any given product’s
configurations. Wiring will be affected by heated seats, but probably will not be affected by the
interior color. It is the relationships between this subset of optional content that define what is
orderable and the orderable combinations must be supported by the product. If heated seats are
only available with power seats, then the seat wiring harness does not need to maintain a part
number that supports heated seats by itself. There needs to be a level for power seats, and a level
for power seat with heated seats.
Importing a Product Plan in XML Format. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837

Exporting a Product Plan in XML Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838
Troubleshooting a Product Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839
Importing a Product Plan in XML Format

You can import a product plan in XML format.
Prerequisites
• The Capital Integrator diagram must be open.
Procedure
1. Press Space Bar and enter Import Product Plan; a Select directory to import plan from
dialog box is displayed.
2. Browse to the directory containing the product plan XML files and click Import; the
data is imported. Note that when the product plan was exported from a Capital Integrator
installation, two files (ProductPlan.xml and VehicleModel.xml) would have been
exported.

February 2016
Exporting a Product Plan in XML Format
Related Topics
Product Plan
Saving the Product Plan
Troubleshooting a Product Plan

You can export a product plan in XML format.
Prerequisites
• The Capital Integrator diagram must be open.
Procedure
1. Press Space Bar and enter Export Product Plan; a Select directory to export plan to
2. Browse to the directory where you want to save the product plan and click Export; the
data is exported and saved in two XML files (ProductPlan.xml and
VehicleModel.xml).
Related Topics
Product Plan

You can save the product plan.
Procedure
1. In the Product Planner Dialog Box, either:
• press Space Bar and enter Save Project
• click the Save ( ) button
2. A progress bar is displayed and the project plan is saved.

Related Topics
Product Plan

February 2016


There are various ways to troubleshoot any errors and warnings that are displayed for a product
plan.
As you edit a product plan, errors and warnings are displayed in the Status Log at the bottom of
the Product Planner Dialog Box.
Warnings
Warnings are created when a Package can never be ordered or is always ordered on a vehicle
model due to some conflict. Warnings are always displayed in blue font. The following is an
example of a warning:
Warning: Package ColdWeatherGrp cannot be ordered for Retail sales of Vehicle Model Base
SUV ROW LHD-BUX after applying Restriction NAG%AND%OPT%ColdWeatherGrp
This is stating that the ColdWeatherGrp package is never ordered on one of the vehicle models
and that it is due to one of its Not Available restrictions.
Errors
Errors are created when an entire vehicle model can never be ordered due to a conflict. Errors
are always displayed in red font. The following is an example of an error:
Error >> Conflict occurred in Base SUV US-US on applying CD Players multiple exclusive
standard options were found: A-CDC A-CD
This is stating that the Base SUV US-US vehicle model is never ordered due to the restrictions
applied by the mutually exclusive group called CD Players. Additionally, the two options in
this group that are causing the issue are A-CDC and ACD. It is recommended that the user
investigate why these two options are always present.
Note that if the errors are not corrected when first displayed, they will be reported again later in
the design process when any complexity action (such as full complexity, optimization or
validation) is performed.
Related Topics
Product Plan

February 2016

February 2016
Variant
Variant
Variant is the term used by the Product Planner to refer to a collection of vehicle models that
have a common attribute such as hand-of-drive, market, trim level, and so on.
A Product Plan consists of a collection of variants.
You should also understand the concept of a mutually-exclusive variant group. See “Mutually-
Exclusive Variant Group” on page 841.

Creating a Variant in the Product Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842
Deleting a Variant from the Product Plan. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843
Creating a Mutually-Exclusive Variant. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844
Deleting a Mutually-Exclusive Variant Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845
Importing Variant Group Data in XLS Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846
Exporting Variant Group Data in XLS Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847
Mutually-Exclusive Variant Group

Groups of these variants can be used to identify mechanical differences within harness families.
The key attribute of this ‘group of vehicle model groups’ (called Mutually-Exclusive Variant
Groups) is that the groups within the group are mutually-exclusive. For example, there may be
two groups: 1) LHD and 2) RHD. These can then be placed in a Mutually-Exclusive Variant
Group called LHD_RHD. Once that is done, you can state that the LHD_RHD group applies to
a harness family later in the harness optimization process. This means, harness levels generated
for a vehicle model that is part of the LHD group cannot be shared with levels generated for
vehicle models in the RHD group. This is how you can force mechanical variations into the
complexity for that specific harness family.
Related Topics
Vehicle Model
Creating a Variant in the Product Plan
Deleting a Variant from the Product Plan
Editing the Vehicle Models in a Variant
Creating a Mutually-Exclusive Variant
Deleting a Mutually-Exclusive Variant Group
Importing Variant Group Data in XLS Format
Exporting Variant Group Data in XLS Format

February 2016

You can create (add) a variant in the product plan.
Prerequisites
The Vehicle Models in the variant must already exist in the product plan (see “Adding a Vehicle
Model to the Product Plan” on page 849).
Procedure
1. From the Product Planner Dialog Box, either:
• select Tools > Exclusive Variant Group Editor from the menu
• click the Exclusive Variant Group Editor ( ) button
The Exclusive Variant Groups Editor Dialog Box is displayed.

2. Click the Edit button at the bottom of the dialog box, the dialog box is placed in an
editing mode.
3. Click the Edit Variants button; the Variant Editor Dialog Box is displayed.
4. Click the Add button; the Add New Variant dialog box is displayed.
5. Specify the name of the variant and click OK; the Associate Variant with Vehicle
Models dialog box is displayed.
6. Select the vehicle models to be included in the variant and click OK; the variant is added
to the Variant Name list in the Variant Editor dialog box.
7. Click Save.
Results
The variant is added to the Members window in the Exclusive Variant Groups Editor dialog
box.
Related Topics
Variant
Product Plan

February 2016

You can delete (remove) a variant from the product plan.
Procedure

2. Click the Edit button at the bottom of the dialog box; the dialog box is placed in an
editing mode.
4. Click the Delete button; the Select Variant for Deletion dialog box is displayed.
5. Select the variant and click OK; the variant is removed from the Variant Name list in the
Variant Editor dialog box.
6. Click Save; the variant is removed from the Members window in the Exclusive Variant
Groups Editor dialog box.
Related Topics
Variant
Product Plan

You can edit the vehicle models in a variant.
Prerequisites
• Any Vehicle Models that you want to add in the variant must already exist in the product
plan (see “Adding a Vehicle Model to the Product Plan” on page 849).

February 2016
Procedure

editing mode.
4. Click the Edit button; the Edit Variant dialog box is displayed.
5. Select the variant to be edited and click OK; the Edit Models Associated with Variant
6. Select the vehicle models to be added to the variant and unselect those to be removed
from the variant and click OK.
7. Click Save on the Variant Editor dialog box.
Related Topics
Variant
Vehicle Model

You can create (add) a mutually-exclusive variant group to the product plan.
Prerequisites
• The Variants in the Mutually-Exclusive Variant Group must already exist in the product
plan (see “Creating a Variant in the Product Plan” on page 842).

February 2016
Procedure

editing mode.
3. Right-click on the Variant Groups list and select Add New Group; the Add New
Group dialog box is displayed.
4. Specify the name of the Mutually-Exclusive Variant Group and click OK; it is added to
the Variant Groups list.
5. In the Members window, select the mutually-exclusive variants that are included in the
mutually-exclusive variant group.
6. Click Save&Close.
Related Topics
Variant
Product Plan

You can delete (remove) a mutually-exclusive variant group from the product plan. This action
deletes only the mutually-exclusive variant group, it does not delete the individual variants
within it.
Procedure

February 2016

editing mode.
3. Right-click on the Mutually-Exclusive Variant Group in the Variant Groups list and
select Delete Group.
Related Topics
Variant
Product Plan

You can import variant and mutually-exclusive variant group data in XLS format into the
product plan.
Procedure

editing mode.
3. Click the Import button; an Open dialog box is displayed.
4. Navigate to the XLS file containing the data and click Open.
5. The data is imported and is displayed in the Exclusive Variant Groups Editor dialog box.

February 2016
Related Topics
Variant
Product Plan

You can export variant and mutually-exclusive variant group data in XLS format into the
product plan. This data can be imported into another installation.
Procedure

editing mode.
3. Click the Export button; a Save dialog box is displayed.
4. Navigate to the directory where you want to save the file, specify its name and click
Save.
5. The data is exported.
Related Topics
Variant
Product Plan

February 2016


February 2016
Vehicle Model
Vehicle Model
A representation of a major vehicle variation as defined by the product plan. Each vehicle
model defines an allowable combination of all the options and also limits the options that are
applicable to each major vehicle variation.
The bases are typically defined based on trim level, market, hand of drive, vehicle line, and so
on. Examples might be “US, LHD, 3 liter” and “UK, RHD, 1.2”.
A vehicle model is formed from a collection of standard Options, Packages and the restrictions
between them.
Adding a Vehicle Model to the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 849

Deleting a Vehicle Model from the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 850
Splitting a Vehicle Model in the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851
Editing the Association of a Package with a Vehicle Model . . . . . . . . . . . . . . . . . . . . . . 852
Editing the Association of an Option from a Package with a Vehicle Model. . . . . . . . . 853
Adding a Vehicle Model to the Product Plan

You can add (create) a vehicle model in the product plan.
Procedure
• select Tools > Vehicle Creator Tool from the menu
• click the Launch Vehicle Creator Tool ( ) button
The Vehicle Creator Dialog Box is displayed.

editing mode.
3. Select Vehicle Model > Create from the menu; an Input dialog box is displayed.
4. Specify the name of the vehicle model and click OK; the Select Standard Options
5. Select the standard Options that are included in the vehicle model and click OK.
6. In the Vehicle Creator dialog box, the vehicle model is displayed on the Standard
Options tab (with the standard options selected) and on the Retail/Fleet Packages tab.
7. Click Save&Close; the vehicle model is added to the Vehicle Configuration Manager
Tree on the Product Planner dialog box.

February 2016
Deleting a Vehicle Model from the Product Plan
Related Topics
Vehicle Model
Product Plan
Splitting a Vehicle Model in the Product Plan
Editing the Association of a Package with a Vehicle Model
Editing the Association of an Option from a Package with a Vehicle Model

You can delete (remove) a vehicle model from the product plan.
Procedure

editing mode.
3. Select Vehicle Model > Delete from the menu; the Select Vehicle Models for Deletion
4. Select the vehicle model to be deleted and click Delete.
5. In the Vehicle Creator dialog box, the vehicle model is removed from the Standard
Options tab and the Retail/Fleet Packages tab.
6. Click Save&Close; the vehicle model is removed from the Vehicle Configuration
Manager Tree on the Product Planner dialog box.
Related Topics
Vehicle Model
Product Plan

February 2016

You can split a vehicle model in the product plan.
Procedure

editing mode.
3. Select Vehicle Model > Split from the menu; a Selection Dialog is displayed.
4. Select the vehicle model to be split and click OK; a Vehicle Model Editor dialog box is
displayed.
5. In the table, enter the names of the vehicle models that will be created by the split and
click OK.
6. In the Vehicle Creator dialog box, the new vehicle models are displayed on the
Standard Options tab and the Retail/Fleet Packages tab. They have the same options
and package associations as the original vehicle model.
7. On the Standard Options tab, edit the options that are selected for each of the new
vehicle models.
8. On the Retail/Fleet Packages tab, edit the associations between the packages and the
new vehicle models.
9. Click Save&Close; the new vehicle models are displayed in the Vehicle Configuration
Manager Tree on the Product Planner dialog box.
Related Topics
Vehicle Model
Product Plan

February 2016
Editing the Association of a Package with a Vehicle

Model
This topic details how to edit the association of a package with a vehicle model.
When doing this, you specify the type of association:
• No association
The package does not apply to the vehicle model being edited.
• R-S - standard retail option
Retail buyers get the package as standard.
• R - retail option
Retail buyers can order the package on a vehicle.
• F-S standard fleet option
Fleet buyers get the package as standard.
• F - fleet option
Fleet buyers can order the package on a vehicle.
Procedure

editing mode.
3. On the Retail/Fleet Packages tab (either on the Retail Packages or Fleet Packages
tab), right-click on the cell in the appropriate package row and in the appropriate vehicle
model column, and select Edit Association; the Select Association Dialog Box (for a
Package) is displayed.
4. Specify the association between the package and the vehicle model, both for retail
buyers and for fleet buyers, and click OK. The types of association are listed at the top
of this topic.
5. The cells in the Retail Packages and Fleet Packages tabs are updated.
6. Click Save&Close; the package is displayed below the vehicle model in the Vehicle
Configuration Manager Tree on the Product Planner dialog box.

February 2016
Note
You must edit the association of the options within the packages with the vehicle
models. That is, whether the options are included when the package is selected for a
vehicle model. See “Editing the Association of an Option from a Package with a Vehicle
Model” on page 853.
Related Topics
Vehicle Model
Package
Editing the Association of an Option from a

Package with a Vehicle Model
You can edit the association of an option (from a package) with a vehicle model.
When doing this, you specify the type of association:
• No association
The option does not apply to the vehicle model being edited.
• S - included
When a buyer orders the package on the vehicle model, this option is included.
• D - deleted
When a buyer orders the package on the vehicle model, this option is not included.
Prerequisites
• The package must be associated with the vehicle model (see “Editing the Association of
a Package with a Vehicle Model” on page 852).
Procedure

February 2016
editing mode.
3. On the Retail/Fleet Packages tab (either on the Retail Packages or Fleet Packages
tab), right-click on the cell in the appropriate option row and in the appropriate vehicle
model column, and select Edit Association; the Select Association Dialog Box (for an
Option) is displayed.
4. Specify the association between the option and the vehicle model, both for retail buyers
and for fleet buyers, and click OK.
5. The cells in the Retail Packages and Fleet Packages tabs are updated.
6. Click Save&Close; if included, the option is displayed below the package under the
vehicle model in the Vehicle Configuration Manager Tree on the Product Planner dialog
box.
Related Topics
Vehicle Model
Option
Package

February 2016
Option
Option
An option is a code representing a feature or capability in a vehicle. Examples are ABS (Anti-
lock Braking System) or DDL (Driver Door Lock).
• Standard Option
A standard option is present on the base vehicle. However, it can be removed or replaced
based on the Packages. For example, a Low-line radio option may be standard. The
package for High-line radio may consist of the High-line radio option, plus a deletion of
the Low-line radio. That way, when a customer orders a High-line radio, the package
will remove the standard Low-line radio and replace it with the High-line radio.
Options can be collected into groups and these groups apply globally across all packages.
• Exclusive Group
Options in an exclusive group are mutually-exclusive. That is, they cannot exist on a
vehicle together. An example might be the radios in a vehicle. The Low-line radio is a
standard option. The Mid-line radio is under two different packages (sun & sound
package and convenience package), and the High-line radio is in one package (High-line
radio). In this case, the exclusive group dictates that you cannot have more than one
radio in a single buildable vehicle.
• Inclusive Group
Used rarely in practice. Options in an inclusive group are mutually-inclusive. That is, if
one of the options in the group is on the vehicle, then all of the options in the group must
also be there. If a vehicle is built that violates this, an error is reported to the user.
Adding an Option to the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855
Deleting an Option from the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856
Creating an Exclusive Group of Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 857
Creating an Inclusive Group of Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859
Deleting an Inclusive Group of Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861
Adding an Option to the Product Plan

You can add (create) options in the product plan.
Procedure

February 2016
Deleting an Option from the Product Plan

editing mode.
3. Select Option/Package > Option Editor from the menu; the Option Editor Dialog Box
is displayed.
4. Click the Edit button at the bottom of the Option Editor dialog box, the dialog box is
placed in an editing mode.
5. Click Add; the Add New Option dialog box is displayed.
6. Specify the name and a description for the option. Click OK; the option is added to the
Option Editor dialog box.
7. Click Save&Close on the Option Editor dialog box.
8. In the Vehicle Creator dialog box, the option is displayed on the Standard Options tab.
Related Topics
Option
Product Plan
Creating an Exclusive Group of Options
Deleting an Exclusive Group of Options
Creating an Inclusive Group of Options
Deleting an Inclusive Group of Options
Specifying an Option as Electrical

You can delete (remove) one or more options from the product plan.
Procedure

February 2016
editing mode.
is displayed.
5. Select the options to be deleted in the Option Name list and click Delete; a dialog box
asks you to confirm the deletion.
6. Click OK; the options are deleted from the database and removed from the Option
Editor dialog box.
Related Topics
Option
Product Plan

You can create an exclusive group of options.
Prerequisites
• The options to be included in the group must already exist in the product plan (see
“Adding an Option to the Product Plan” on page 855).
Procedure

editing mode.

February 2016
is displayed.
5. Click the Edit Groups button; the Exclusive/Inclusive Option Editor Dialog Box is
displayed.
6. Click the Edit button at the bottom of the Exclusive/Inclusive Option Editor dialog box,
the dialog box is placed in an editing mode.
7. Right-click on the Exclusive Groups window and select Add New Exclusive Group;
the Add New Exclusive Group dialog box is displayed.
8. Specify a name for the group and click OK; the name is added to the Exclusive Groups
window.
9. Right-click on the exclusive group name and select Add Option To Selected Group; a
Selection Dialog is displayed.
10. Select the options to be included in the group and click OK. When the group name is
selected in the Exclusive Groups window of the Exclusive/Inclusive Option Editor
dialog box, the options are displayed in the Options window.
Related Topics
Option

You can delete (remove) an exclusive group of options from the product plan. This deletes the
group but not the individual options.
Procedure

February 2016

editing mode.
3. Select Option > Option Editor from the menu; the Option Editor Dialog Box is
displayed.
displayed.
7. Right-click on the exclusive group name in the Exclusive Groups window and select
Delete Selected Exclusive Group; the group is deleted from the database and removed
from the Exclusive Groups window.
Related Topics
Option

You can create an inclusive group of options.
Prerequisites
The options to be included in the group must already exist in the product plan (see “Adding an
Option to the Product Plan” on page 855).

February 2016
Procedure

editing mode.
is displayed.
displayed.
7. Right-click on the Inclusive Groups window and select Add New Inclusive Group; the
Add New Inclusive Group dialog box is displayed.
8. Specify a name for the group and click OK; the name is added to the Inclusive Groups
window.
9. Right-click on the inclusive group name and select Add Option To Selected Group; a
10. Select the options to be included in the group and click OK. When the group name is
selected in the Exclusive Groups window of the Exclusive/Inclusive Option Editor
dialog box, the options are displayed in the Options window.
11. Click Save&Close on the Exclusive/Inclusive Option Editor dialog box.
12. Click Save&Close on the Option Editor dialog box.
Related Topics
Option

February 2016

You can delete (remove) an inclusive group of options from the product plan. This deletes the
group but not the individual options.
Procedure

editing mode.
is displayed.
displayed.
7. Right-click on the inclusive group name in the Inclusive Groups window and select
Delete Selected Inclusive Group; the group is deleted from the database and removed
from the Inclusive Groups window.
Related Topics
Option

February 2016

You can specify (identify) an option as electrical (in other words, it impacts the electrical
connectivity of the vehicle). Some options (for example, seat coverings) do not involve any
electronic components.
Prerequisites
• The option must already exist in the product plan (see “Adding an Option to the Product
Plan” on page 855).
Procedure
editing mode.
3. Select Option/Package > Option Domain Editor from the menu; the Option Domain
Editor Dialog Box is displayed.
4. Click the Edit button at the bottom of the Option Domain Editor dialog box, the dialog
box is placed in an editing mode.
5. Select the box in the Electrical column for the options that are electrical.
Related Topics
Option

February 2016
Package
Package
A package is an orderable combination of options in a vehicle. Options listed under a package
that can be deleted are displayed in red in the system. This indicates that when the package is
ordered, the option should be removed from the vehicle if it is present. This is how packages can
remove standard option content. An example might be a package where the standard low-line
radio is deleted and replaced with a high-line radio.
Note
The system will automatically delete a standard Option if a package adds an option that is
mutually-exclusive with that standard option. In the example above, the standard low-line
radio is deleted automatically as long as the low-line and high-line radios are in an exclusive
option group.
In a Vehicle Model, a package can be specified as the following:
• Retail
A retail package is a package that is available to retail buyers.
• Fleet
A fleet package is a package that is available to fleet buyers.
Note
Retail packages and fleet packages cannot be ordered together. If you want to mix
fleet and retail packages, you should create them all as retail packages.
• No Association
This indicates that the package does not apply to the vehicle model being edited.
• Must Have
A must-have is a restriction placed on a package. The package must be ordered with
something else. For example, the Rear DVD player package must have the High-line
radio package as well. This means, you can order a vehicle with neither option, just the
high-line radio, or you can order the High-line radio and the DVD player. You cannot
order a vehicle with just the DVD player.
The order of the elements in the must-have statement matters. In the above example,
saying that the Rear DVD must have the High-line radio means that I cannot buy the
Rear DVD without the High-line radio. You can buy the High-line radio without the
Rear DVD.
• Not Available

February 2016
Package
Not-available is another (asymmetric) restriction type similar to a must-have, but

logically different. in this case, a package is restricted so that it is not available when
another package is ordered.
Not-availables are bi-directional meaning that the order of the statement does not matter.
If you say that the Trailer-Tow package is not available with the 5.7L engine, then you
can order a vehicle with Trailer-Tow or with the 5.7L engine, but you cannot order a
vehicle with both.
Note
With regard to Must Have and Not Available restrictions, the restrictions apply
to packages. However, the target can be either another package or an option. In the
Must Have example above (Rear DVD must have High-line radio), the Rear DVD is a
package. It must be because restrictions can apply only to packages. However, the High-
line radio can be either a package or an option (which depends upon the Product Plan). If
Rear DVD is a package, then it means what is described above. However, it is possible
that High-line radio is not a package of its own. It may be that there are several packages
and High-line radio is an option underneath those packages.
The target does not have to be a single package or option but can be a list. If it is a list,
there is a condition that needs to be included of AND or OR. For example, a must-have
can be defined to dictate Trailer-Tow must have 5.7L OR 3.0L. Another example might
be that Heated Seats must have Leather AND Memory.
Outside of vehicle models, packages can be collected into groups.
• Exclusive Group
Packages in an exclusive group are mutually-exclusive. That is, they cannot exist on a
vehicle together.
• Inclusive Group
Used rarely in practice. Packages in an inclusive group are mutually-inclusive. That is, if
one of the packages in the group is on the vehicle, then all of the packages in the group
must also be there. If a vehicle is built that violates this, an error is reported to the user.
Adding a Package to the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 865
Deleting a Package from the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 867
Creating an Exclusive Group of Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868
Creating an Inclusive Group of Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 870
Deleting an Inclusive Group of Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 871
Creating a Must Have or Not Available Restriction on a Package . . . . . . . . . . . . . . . . . 872
Deleting a Must Have or Not Available Restriction on a Package . . . . . . . . . . . . . . . . . 874

February 2016
Adding a Package to the Product Plan

You can add (create) a package in the product plan.
Procedure

editing mode.
3. Select Option/Package > Package Editor from the menu; the Package Editor Dialog
Box is displayed.
4. Click the Edit button at the bottom of the Package Editor dialog box, the dialog box is
5. Click Add; the Add New Package dialog box is displayed.
6. Specify the name and a description for the package. Click OK; the package is added to
the Package Editor dialog box.
7. Click Save&Close on the Package Editor dialog box.
8. In the Vehicle Creator dialog box, the package is displayed on the Retail/Fleet
Packages tab.
Related Topics
Package
Product Plan
Adding Options to a Package
Deleting a Package from the Product Plan
Creating an Exclusive Group of Packages
Deleting an Exclusive Group of Packages
Creating an Inclusive Group of Packages
Deleting an Inclusive Group of Packages
Creating a Must Have or Not Available Restriction on a Package
Deleting a Must Have or Not Available Restriction on a Package

February 2016

You can add (include) options to a package.
Prerequisites
• The package must already exist in the product plan (see “Adding a Package to the
• The Options to be added must already exist in the product plan (see “Adding an Option
to the Product Plan” on page 855).
Procedure

editing mode.
3. Select Option/Package > Option/Package Association from the menu; the Package-
Option Association Editor Dialog Box is displayed.
4. Click the package in the Packages tree; the options in the product plan are listed in the
Option table on the right.
5. Click the Edit button at the bottom of the Package-Option Association Editor dialog
box, the dialog box is placed in an editing mode.
6. In the Include In the Package column of the Option table, select the boxes for the
options that are to be included in the package.
7. Click Close on the Package-Option Association Editor dialog box.
8. In the Vehicle Creator dialog box, the options are listed with the package on the Retail/
Fleet Packages tab. Note that you may need to close and reopen the Vehicle Creator
dialog box.
Related Topics
Package

February 2016


You can delete (remove) one or more packages from the product plan.
Procedure

Box is displayed.
editing mode.
4. Select the package and click Delete; a dialog box asks you to confirm the deletion.
5. Click OK; the package is deleted from the database and removed from the Package
Editor dialog box.
6. Click Save&Close on the Package Editor dialog box.
7. In the Vehicle Creator dialog box, the package is removed from the Retail/Fleet
Packages tab.
Related Topics
Package
Product Plan

February 2016


You can create an exclusive group of packages.
Prerequisites
• The packages to be included in the group must already exist in the product plan (see
“Adding a Package to the Product Plan” on page 865).
Procedure
editing mode.
Box is displayed.
5. Click the Edit Groups button; the Exclusive/Inclusive Package Editor Dialog Box is
displayed.
6. Click the Edit button at the bottom of the Exclusive/Inclusive Package Editor dialog
7. Right-click on the Exclusive Groups window and select Add New Exclusive Group;
the Add New Exclusive Group dialog box is displayed.
8. Specify a name for the group and click OK; the name is added to the Exclusive Groups
window.
9. Right-click on the exclusive group name and select Add Package To Selected Group; a
10. Select the packages to be included in the group and click OK. When the group name is
selected in the Exclusive Groups window of the Exclusive/Inclusive Package Editor
dialog box, the packages are displayed in the Packages window.

February 2016
Related Topics
Package

You can delete (remove) an exclusive group of packages from the product plan. This deletes the
group but not the individual packages.
Procedure
editing mode.
Box is displayed.
displayed.
7. Select the exclusive group name in the Exclusive Groups window, right-click on it and
select Delete Selected Exclusive Group; the group is deleted from the database and
removed from the Exclusive Groups window.

February 2016
Related Topics
Package

You can create an inclusive group of packages.
Prerequisites
• The packages to be included in the group must already exist in the product plan (see
Procedure

editing mode.
Box is displayed.
displayed.

February 2016
7. Right-click on the Inclusive Groups window and select Add New Inclusive Group; the
Add New Inclusive Group dialog box is displayed.
8. Specify a name for the group and click OK; the name is added to the Inclusive Groups
window.
9. Right-click on the inclusive group name and select Add Package To Selected Group; a
selected in the Inclusive Groups window of the Exclusive/Inclusive Package Editor
Related Topics
Package

You can delete (remove) an inclusive group of packages from the product plan. This deletes the
group but not the individual packages.
Procedure

editing mode.
Box is displayed.

February 2016
displayed.
7. Select the inclusive group name in the Inclusive Groups window, right-click on it and
select Delete Selected Inclusive Group; the group is deleted from the database and
removed from the Inclusive Groups window.
Related Topics
Package
Creating a Must Have or Not Available Restriction

on a Package
You can create a Must Have or Not Available restriction on a package.
See “Package” on page 863 for a description of these terms.
Prerequisites
• The packages involved in the restriction must already exist in the product plan (see
Procedure

February 2016

editing mode.
Box is displayed.
displayed.
7. Right-click on the MTH/NAW Groups window and select one of the following:
• Create New Package-To-Package Level Must Have Group > Add New Must
Have AND Group or Add New Must Have OR Group
• Create New Package-To-Package Level Not Available Group > Add New Not
Allowed AND Group or Add New Not Allowed OR Group
• Create New Package-To-Option Level Must Have Group > Add New Must
Have AND Group or Add New Must Have OR Group
• Create New Package-To-Option Level Not Available Group > Add New Not
Available AND Group or Add New Not Available OR Group
The Select Leading Option dialog box is displayed
8. Select the leading package for which you are creating the Must Have or Not Available
restriction and click OK; the group is added to the MTH/NAW Groups window.
9. Right-click on the group name and select Add Package To Selected Group; a
selected in the Exclusive Groups window of the Exclusive/Inclusive Package Editor
Related Topics
Package

February 2016

Deleting a Must Have or Not Available Restriction

on a Package
You can delete (remove) a Must Have or Not Available restriction on a package from the
product plan. This deletes the restriction but not the individual packages.
See “Package” on page 863 for a description of these terms.
Procedure
editing mode.
Box is displayed.
displayed.
7. Select the group name in the MTH/NAW Groups window, right-click on it and select
Delete Selected Group; the group is deleted from the database and removed from the
MTH/NAW Groups window.
Related Topics
Package

February 2016
VVD - Vehicle Variant Definition


A VVD is a collection of standard options and packages (with particular options set as included)
that form an orderable permutation of a vehicle.
Unlike EVDs (electrical variant definitions), VVDs are not necessarily electrically-unique.
These are similar to Vehicle Configurations in the other applications in the suite, although
vehicle configurations are permutations built up from possible combinations of harness levels.
Along with EVD - Electrical Variant Definitions, VVDs give you an indication of the amount of
variability in the Product Plan. However, their main role is as an intermediate step in the process
of producing Optimized Complexity harness levels.
Related Topics
Option
Package
EVD - Electrical Variant Definition
Generating VVD and EVD Counts for a Vehicle Model

February 2016

A EVD is a collection of standard options and packages (with particular options set as included)
that form an electrically unique, orderable permutation of a vehicle
These are similar to Vehicle Configurations in the other applications in the suite, although
vehicle configurations are permutations built up from possible combinations of harness levels.
EVDs are used to generate Full Complexity harness levels.
Along with VVD - Vehicle Variant Definitions, EVDs give you an indication of the amount of
variability in the Product Plan. However, their main role is as an intermediate step in the process
of producing Optimized Complexity harness levels.
Generating VVD and EVD Counts for a Vehicle Model . . . . . . . . . . . . . . . . . . . . . . . . . 876
Generating VVD and EVD Counts for a Vehicle

Model
You can generate (calculate) the number of VVD - vehicle variant definitions and EVD -
electrical variant definitions for a vehicle model.
Prerequisites
• Options must have been added into the product plan (see “Adding an Option to the
• If necessary, the options must have been grouped into Exclusive Groups and Inclusive
Groupss (see “Creating an Exclusive Group of Options” on page 857 or “Creating an
Inclusive Group of Options” on page 859).
• Packages of options must exist (see “Adding a Package to the Product Plan” on
page 865 and “Adding Options to a Package” on page 866).
• Vehicle Models must exist (see “Adding a Vehicle Model to the Product Plan” on
page 849).
• The association between the packages and the vehicle models must have been specified
(see “Editing the Association of a Package with a Vehicle Model” on page 852).
• The association between the options in the packages and the vehicle models must have
been specified (see “Editing the Association of an Option from a Package with a Vehicle
Model” on page 853).
• Mutually-Exclusive Variant Groups (groups of Variants that are mutually-exclusive)
must have been created or imported (see “Creating a Mutually-Exclusive Variant” on
page 844 or “Importing Variant Group Data in XLS Format” on page 846).

February 2016
• Specify which options are electrical (see “Specifying an Option as Electrical” on

page 862).
Procedure
1. On the Product Planner Dialog Box, click the Generate Variant Count button; the
Select Vehicle Models To Generate VVD dialog box is displayed.
2. Select the vehicle model for which you want to generate VVDs and EVDs. Click
Generate; a progress bar is displayed.
Results
Once the calculation is complete, the Total Num. of Variants and Num. of EE Variants
columns are updated for the vehicle model in the “Number of Variants Associated with”
window.
Related Topics
Vehicle Model
Vehicle configurations are vehicle permutations built up from harness levels in the other
applications in the suite.
They are similar, though not equivalent, to VVD - Vehicle Variant Definitions and EVD -
Electrical Variant Definitions.
Take Rate
The take rate is a percentage of vehicles that will contain a certain option or package. If you say
that the take rate for a 3.7L engine is 20% (0.2), then if 100,000 vehicles will be built, 20,000 of
them will have a 3.7L engine.
Therefore, the Take Rate Editor Dialog Box allows you to assign:
• a volume for an entire vehicle platform (that is, how many are produced in a year)
• take rates for Options in those vehicles (that is, the percentage of the annual volume that
include each option)
Note
The system automatically sets take rates for options that are always or never present
(100% or 0%).

February 2016
Take Rate
The system uses take rates during giveaway calculations, particular during automated
optimization. The algorithm needs to know the take rates because if is often preferable to give
away an option with a high take rate rather than an option with a low one.
From the Take Rate Editor dialog box, you can view an HTML report that provides information
about options, their restrictions, their application to vehicle models, the take rate you entered,
the calculated take rate, and the difference between them (otherwise referred to as the error).
Entered Take Rate versus Calculated Take Rate

The system determines whether there are any inconsistencies in the take rates that you enter or
import via the product plan. Inconsistencies might be take rates for mandatory, mutually-
exclusive options exceeding 100% or two options from the same package having different take
rates.
When there are inconsistencies, the system attempts to meet your requirements but will
distribute any error among the take rates for the various options to produce a calculated take
rate. The system uses the calculated take rates in any calculations.
For example, if you have two mandatory, mutually-exclusive options, one with a manually
entered take rate of 25%, the other with a manually entered take rate of 85%, each will have a
calculated error of 5%. Their calculated take rates are 20% and 80%.
If there are no inconsistencies, the entered take rate and the calculated take rate are the same.
Splitting Take Rates

Sometimes options have different take rates in different scenarios, for example, different
markets or different vehicle models. You can therefore split the options in the Take Rate Editor
dialog box (that is have multiple rows for each one) and enter those take rates separately.
They can be split based on the following:
• Vehicle Models
The options have a take rate for each vehicle model.
• Variants
You can select a variant group. The options then have a take rate for each variant in the
group. For example, you may have a variant group LHD_RHD. You can then enter a
take rate for the option when the LHD variant is used and a take rate for when the RHD
variant is used.
• Custom Groups
You can create your own custom groupings of variant expressions. The options then
have a take rate for each variant expression.

February 2016
Editing the Take Rates for Vehicle Models
For example, you may create a group called Market and Hand-of-Drive. In this group,
you have variant expressions US, Mexico and Canada. In addition, you have variant
expressions ROW && RHD and ROW && LHD. These last two expressions are for
the rest of the world but based on both right-hand drive and left-hand drive options.
When the custom group is selected in the Split Option by field of the Take Rate Editor
dialog box, each option has a row for each of the five variant expressions.
Related Topics
Option
Package

The Take Rate Editor dialog box enables you to define take rates for options. The specified take
rates are used by the system when calculating cost. This is done any time Capital Level
Manager performs any type of complexity calculation (such as, full complexity, optimized
complexity and even validation).
For an explanation and examples of take rates (including splitting them), see “Take Rate” on
page 877.
Prerequisites
The basic product plan data must have been entered.
Procedure
1. With a Capital Integrator diagram open, press Space Bar and enter Take Rate Editor; the
Take Rate Editor Dialog Box is displayed and Option take rate table shows the current
take rates for the options in the product plan.
2. Specify the Annual Volume of vehicles produced for the platform and an Error
Threshold.
3. For each Option, specify a Take Rate. When you enter a take rate, the Calculated Error
column displays Needs Update.
Note
You can use the Split Option by field to enable you to enter different take rates for
each option in different scenarios. See “Take Rate” on page 877 for a full
explanation and example.
4. Update the Calculated Error column by clicking the Recalculate errors based on
updated take rates ( ) button; any percentage errors are displayed. They are red if
they exceed the Error Threshold.

February 2016
5. If required, you can hold your mouse cursor over the end of an Option field and click the
Click to view an HTML report on this option ( ) button; this displays an HTML
report that shows the calculated take rates for this option and for the vehicle models.
6. Click OK to exit the Take Rate Editor dialog box.
Results
• Capital Level Manager uses the take rates when calculating cost.
• When the system saves optimized harness levels as harness levels for use in Capital
Integrator, the Take Rate attribute updates for those harness levels (based on the
calculated take rates).
Related Topics
Take Rate
Vehicle Model
Option
Package

February 2016
Chapter 27
Product Planner Dialog Box and Field
Reference
This appendix offers a description of the dialog boxes available in the Capital Level Manager -
Product Planner application. For each dialog box, all fields are listed, along with a full
description of the field’s function.
Add New Option Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883
Package-Option Association Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884
Edit Custom Groups Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885
Edit Models Associated with Variant Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 886
Exclusive/Inclusive Option Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887
Exclusive/Inclusive Package Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889
Variant Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 892
Option Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893
Option Domain Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894
Package Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895
Select Association Dialog Box (for an Option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897
Select Association Dialog Box (for a Package) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898
Select Standard Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899
Select Vehicle Models for Deletion Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900
Take Rate Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
Usage of Option Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904
Exclusive Variant Groups Editor Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
Product Planner Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907
Vehicle Creator Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914
Help Button Landing Pages for Product Planner. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Add New Option Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Package-Option Association Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Edit Models associated with Variant Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
Exclusive/Inclusive Option Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
Exclusive/Inclusive Package Editor Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919

February 2016
Product Planner Dialog Box and Field Reference

Select Standard Options Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Usage of Option Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Exclusive Variant Groups Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
Vehicle Creator Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923

February 2016
Add New Option Dialog Box
Add New Option Dialog Box

To access: In the Option Editor dialog box, click Add.
Use this dialog box to create a new option.
Objects
Table 27-1. Add New Option Dialog Box Contents

Field Description
New Name Specify the name of the new option.
Description Specify a description for the new option.
Related Topics
Option Editor Dialog Box
Option

February 2016
Package-Option Association Editor Dialog Box
Package-Option Association Editor Dialog Box

To access: In the Vehicle Creator dialog box, select Option/Package > Option/Package
Association from the menu.
Use this dialog box to specify the options that are associated with packages.
Objects
Table 27-2. Edit Package-Option Association Editor Dialog Box Contents

Field Description
Packages Tree Lists the packages available in the project. Click a
package to display which options are associated with it
in the Option table.
Option Table Lists the options that are available in the project. If an
option is associated with a package, you select it in the
Include In the Package column.
Edit Changes the dialog box into an edit mode.
Show Selected Only Filters the options displayed in the Option table to
those that are associated with the package selected in
the Packages tree.
Show All Displays all available options in the project in the
Option table. Displayed only after Show Selected Only
has been clicked.
Update Saves any changes in this dialog box to the database
without closing the dialog box. Displayed only after
Edit has been clicked.
Related Topics
Vehicle Creator Dialog Box
Option
Package

February 2016
Edit Custom Groups Dialog Box
Edit Custom Groups Dialog Box

To access: In the Take Rate Editor dialog box, click the Launch custom group manager
dialog ( ) button.
Use this dialog box to create custom groups of variant expressions that can be used to split
option take rates in the Take Rate Editor dialog box. When the custom group is applied, each
option has a row for each variant expression. This allows you to enter a take rate for each
variant expression.
Objects
Table 27-3. Edit Custom Groups Dialog Box Contents

Field Description
Group Lists the custom groups that have been created. Click a
group to display the variant expressions in it. Red text
indicates an invalid group. To add a group, click the
button. To remove a group, select it and click the
button.
Variant Expression Lists the variant expressions in the currently selected
custom group. When this custom group is used to split
option take rates in the Take Rate Editor Dialog Box,
each option will have a row for each variant
expression.
To enter a new variant expression, click in the Enter
Variant Expression line and either type the variant
expression manually or click the ellipsis (...) to display
the Variant Expression Editor Dialog Box.
Related Topics

February 2016
Edit Models Associated with Variant Dialog Box
Edit Models Associated with Variant Dialog

Box
To access: In the Variant Editor dialog box, click Edit; a drop-down list of variants is displayed
on the Edit Variant dialog box. Select the group for editing and click OK.
Use this dialog box to specify which vehicle models are included in the variant being edited.
Objects
Select the vehicle models to be associated in the list and click OK.
Related Topics
Variant Editor Dialog Box
Vehicle Model
Variant

February 2016
Exclusive/Inclusive Option Editor Dialog Box

To access: In the Option Editor dialog box, select option names and click Edit Groups.
Use this dialog box to define the inclusive / exclusive relationships between the options selected
in the Option Editor dialog box.
Objects
Table 27-4. Exclusive/Inclusive Option Editor Dialog Box Contents

Field Description
Exclusive Groups Window Lists the exclusive groups of options.
To create a new exclusive group, right-click on this
window and select Add New Exclusive Group; a
dialog box asks you to specify the name of the group.
The group name is added to this window.
To delete a group, select it, right-click on it and select
Delete Selected Exclusive Group.
To add options to the group, select it, right-click on it
and select Add Option to Selected Group; a Selection
dialog box is displayed where you select the options.
Once selected, the mutually-exclusive options are
displayed in the Options window whenever the group
name is selected in this window.
Inclusive Groups Window Lists the inclusive groups of options.
To create a new inclusive group, right-click on this
window and select Add New Inclusive Group; a
Delete Selected Inclusive Group.
To add options to the group, select it, right-click on it
and select Add Option to Selected Group; a Selection
dialog box is displayed where you select the options.
Once selected, the mutually-inclusive options are
displayed in the Options window whenever the group
name is selected in this window.
Options Window Displays the options included in the group selected in
the Exclusive Groups window or Inclusive Groups
window.

February 2016
Related Topics

February 2016
Exclusive/Inclusive Package Editor Dialog Box

To access: In the Package Editor dialog box, select a package name and click Edit Groups.
Use this dialog box to define the inclusive / exclusive relationships between the packagess and
to define Must Have and Not Available restrictions.
Objects
Table 27-5. Exclusive/Inclusive Package Editor Dialog Box Contents

Field Description
Exclusive Groups Window Lists the exclusive groups of packages.
To create a new exclusive group, right-click on this
window and select Add New Exclusive Group; a
Delete Selected Exclusive Group.
To add packages to the group, select it, right-click on it
and select Add Package to Selected Group; a
Selection dialog box is displayed where you select the
packages. Once selected, the mutually-exclusive
packages are displayed in the Packages window
whenever the group name is selected in this window.
Inclusive Groups Window Lists the inclusive groups of packages.
To create a new inclusive group, right-click on this
window and select Add New Inclusive Group; a
Delete Selected Inclusive Group.
To add packages to the group, select it, right-click on it
and select Add Option to Selected Group; a
Selection dialog box is displayed where you select the
packages. Once selected, the mutually-inclusive
packages are displayed in the Packages window
whenever the group name is selected in this window.

February 2016
Table 27-5. Exclusive/Inclusive Package Editor Dialog Box Contents (cont.)

Field Description
MTH/NAW Groups Window Lists the Must Have (MTH) and Not Available (NAW)
restriction groups for the packages.
To create a new group, right-click on this window and
select one of the following:
• Create New Package-To-Package Level Must
Have Group > Add New Must Have AND
Group or Add New Must Have OR Group
• Create New Package-To-Package Level Not
Available Group > Add New Not Allowed AND
Group or Add New Not Allowed OR Group
• Create New Package-To-Option Level Must
Have Group > Add New Must Have AND
Group or Add New Must Have OR Group
• Create New Package-To-Option Level Not
Available Group > Add New Not Available AND
Group or Add New Not Available OR Group
A Select Leading Package dialog box is displayed
where you select the package that is Must Have or Not
Available with the other packages and options in the
group. When you click OK, the restriction group is
added to this window.
To add packages to a restriction group, select it, right-
click on it and select Add Package to selected group;
a Selection dialog box is displayed where you select
the options. Once selected, the options are displayed in
the Packages window whenever the group name is
selected in this window.
Delete Selected Group.
Packages Window Displays the Packages or Options included in the
group selected in the Exclusive Groups window,
Inclusive Groups window or MTH/NAW Groups
window.
Related Topics
Package Editor Dialog Box

February 2016


February 2016

To access: In the Exclusive Variant Groups Editor dialog box, select a variant and click the Edit
Variants button.
Use this dialog box to create and edit the variants in the product plan.
Objects
Table 27-6. Variant Editor Dialog Box Contents

Field Description
Variant Name List Lists the existing Variants. When you select a variant
in this list, the Vehicle Models included in it are listed
in the Associated Vehicle Models.
Associated Vehicle Models Lists the vehicle models collected together in the
variant selected in the Variant Name list.
Add Enables you to create a new variant. Displays the Add
New Variant dialog box where you specify a name for
the variant. When you click OK, the Associate
Variant with Vehicle Models dialog box is displayed
where you select the vehicle models collected together
in the variant. Once created, the variant name is
displayed in the Variant Name list. When that name is
selected, the vehicle models are displayed in the
Associated Vehicle Models.
Delete Displays the Select Variant for Deletion dialog box
where you select any variants that you want to delete.
When you click OK, the selected variants are removed
from the Variant Name list.
Edit Displays the Edit Variant dialog box where you select
a variant group for editing, then the Edit Models
Associated with Variant Dialog Box is displayed
where you specify which vehicle models are included
in the variant being edited.
Related Topics
Exclusive Variant Groups Editor Dialog Box

February 2016

To access: In the Vehicle Creator dialog box, click the Edit button and then select Option/
Package > Option Editor from the menu.
Use this dialog box to create new options, delete existing options and define the inclusive /
exclusive relationships between options.
Objects
Table 27-7. Option Editor Dialog Box Contents

Field Description
Option Name List Lists the Options available in the project.
Add Displays the Add New Option Dialog Box that allows
you to create a new option that will be added to the
Option Name list. Displayed only after Edit has been
clicked.
Delete Deletes the selected options in the Option Name list.
Displayed only after Edit has been clicked.
Edit Groups Displays the Exclusive/Inclusive Option Editor Dialog
Box where you can define the inclusive / exclusive
relationships between the selected options in the
clicked.
Related Topics

February 2016
Option Domain Editor Dialog Box
Option Domain Editor Dialog Box

To access: In the Product Planner dialog box, select Tools > Option Domain Editor from the
menu. In the Vehicle Creator dialog box, select Option/Package > Option Domain Editor
from the menu.
Use this dialog box to create new domains, delete existing domains and specify the domains to
which options belong.
Objects
Table 27-8. Option Domain Editor Dialog Box Contents

Field Description
Option Name List The first column lists the Options available in the
project. Any domains that have been created are listed
along the top of the table. By default, only the
Electrical domain is listed; it designates options that
are to be retained when VVD - Vehicle Variant
Definitions are filtered down to EVD - Electrical
Variant Definitions and options that are to appear
when creating option expressions in the other
applications in the suite.
Delete Opens the Domain Selection dialog box where you
can select a domain that you want to delete from the
database. Displayed only after Edit has been clicked.
Add Opens an Input dialog box where you can enter a
name for a new domain that will be added to the
clicked.
Select All / Unselect All Displays the Domain Selection dialog box where you
can select a domain to which you want to assign all
options or from which you want to unassign all
options. Displayed only after Edit has been clicked.
Related Topics
Product Planner Dialog Box

February 2016

To access: In the Vehicle Creator dialog box, select Option/Package > Package Editor from
the menu.
Use this dialog box to create and edit packages.
Objects
Table 27-9. Package Editor Dialog Box Contents

Field Description
Package Editor Table Lists the existing Packages in the product plan with the
following information:
• Description
The description of the option.
• Associated Exclusive Group(s)
Any exclusive groups in which the package is
included.
• Associated Inclusive Group(s)
Any inclusive groups in which the package is
included.
• Associated MTH/NAW Group(s)
Any Must Have and Not Available restriction
groups in which the package is included.
Add Displays the Add New Package dialog box where you
specify a name and description for a new package.
Delete Deletes the selected packages in the Package Editor
table. Displayed only after Edit has been clicked.
Edit Groups Displays the Exclusive/Inclusive Package Editor
Dialog Box where you define the inclusive / exclusive
relationships between the packages and define Must
Have and Not Available restrictions. Displayed only
after Edit has been clicked.
Related Topics

February 2016


February 2016
Select Association Dialog Box (for an Option)
Select Association Dialog Box (for an Option)

To access: In the Vehicle Creator dialog box, open the Retail Packages or Fleet Packages tab,
right-click on a variant base column for an option name and select Edit Association.
Use this dialog box to specify how the option is associated with the vehicle model.
Objects
Table 27-10. Select Association Dialog Box (for Option) Contents

Field Description
Retail Specifies the association between the Vehicle Model
and the package or Option for a retail buyer:
• No association
The option does not apply to the vehicle model
being edited.
• S - included
When a retail buyer orders the package on the
vehicle model, this option is included.
• D - deleted
When a retail buyer orders the package on the
vehicle model, this option is not included.
Fleet Specifies the association between the vehicle model
and the package or option for a fleet buyer:
• No association
The option does not apply to the vehicle model
being edited.
• S - included
When a fleet buyer orders the package on the
vehicle model, this option is included.
• D - deleted
When a fleet buyer orders the package on the
vehicle model, this option is not included.
Related Topics

February 2016
Select Association Dialog Box (for a Package)
Select Association Dialog Box (for a Package)

right-click on a variant base column for a package and select Edit Association.
Use this dialog box to specify how the package is associated with the vehicle model.
Objects
Table 27-11. Select Association Dialog Box (for Package) Contents

Field Description
Retail Specifies the association between the Vehicle Model
and the Package or option for a retail buyer:
• No association
The package or option does not apply to the vehicle
model being edited.
Retail buyers get the package or option as standard.
Retail buyers can order the package or option on a
vehicle.
Fleet Specifies the association between the vehicle model
and the package or option for a fleet buyer:
• Black - no association
model being edited.
• F-S - standard fleet option
Fleet buyers get the package or option as standard.
Fleet buyers can order the package or option on a
vehicle.
Related Topics

February 2016
Select Standard Options Dialog Box
Select Standard Options Dialog Box

To access: In the Vehicle Creator dialog box, select Vehicle Model > Create from the menu; an
Input dialog box is displayed where you specify the name of the vehicle model and then this
Use this dialog box to select the standard options that are included in the vehicle model being
created.
Objects
Select the appropriate options in the displayed list.
Related Topics

February 2016
Select Vehicle Models for Deletion Dialog Box
Select Vehicle Models for Deletion Dialog Box

To access: In the Vehicle Creator dialog box, select Vehicle Model > Delete.
Use this dialog box to select vehicle models that you want to delete from the database.
Objects
Select the appropriate vehicle models in the displayed list and click Delete.
Related Topics

February 2016
Take Rate Editor Dialog Box

To access: With a Capital Integrator diagram open, press Space Bar and enter Take Rate Editor.
Use this dialog box to specify annual vehicle platform volume and to specify take rates for
options.
Objects
Table 27-12. Take Rate Editor Dialog Box Contents

Field Description
Annual Volume Specify the projected number of vehicles expected to be ordered for
the platform during a given model year.
Error Threshold You can allow some inconsistency in the entered take rate data by
setting a percentage error threshold. For example, if you enter 1%
here, the Calculated Error column displays any values greater than
1% in red. Those values are also displayed in red in the HTML report
and in the output window during full complexity and optimized
complexity calculations. Inconsistent data does not prevent you or
the system from proceeding with any operations.
Split Option by Sometimes options have different take rates in different scenarios,
for example, different markets or different vehicle models. You can
therefore split the options in the table (that is have multiple rows for
each one) and enter those take rates separately.
You use this drop-down to determine how you split the options in the
table:
• All Vehicle Models
The options have a row for each vehicle model.
• Variants
You can select a variant group. The options then have a row for
each variant in the group. For example, you may have a variant
group LHD_RHD. You can then enter a take rate for the option
when the LHD variant is used and a take rate for when the RHD
variant is used.
• Custom Groups
You can create your own custom groupings for splitting the table
by clicking the Launch custom group manager dialog ( )
button; the Edit Custom Groups Dialog Box is displayed. When
you select the group in this drop-down, the options have rows for
each variant expression in the group.
Option take rate table Lists the options in the product plan and allows you to enter the take
rates for them.

February 2016
Table 27-12. Take Rate Editor Dialog Box Contents (cont.)

Field Description
Option The name of an option available in the product plan. All options from
the product plan are displayed in this column.
The filter at the top of this column allows you to:
• Select an option folder (restricts the displayed options to only
those in the folder).
• Enter a string (restricts the displayed options to only those
containing that string).
• To select a filter previously used in this session (listed under
History).
You can hold your mouse cursor over the end of an option field and
click the Click to view an HTML report on this option ( ) button;
this displays an HTML report that provides information about
options, their restrictions, their application to vehicle models, the
take rate you entered, the calculated take rate, and the difference
between them (otherwise referred to as the error).
You can copy and paste tabular information from the report into
Microsoft Excel.
Split Displays the vehicle model, variant, or custom variant expression for
which you are entering a take rate.
Take Rate Enter the take rate for the option.
If an option is always present or never present on vehicle models
(based on the product plan), the value 100% or 0% is displayed and
you cannot edit it.
The filter at the top of the column allows you to restrict the displayed
take rates to only those you can edit.
Calculated Error Indicates whether any entered take rate data is inconsistent. The
percentage displayed here is the difference between your manually-
entered take rate and the system-calculated take rate. To view the
calculated take rate, hold your mouse cursor over the calculated
error; a tooltip displays it.
Whenever you enter take rate data, this column displays Needs
Update until you click the Recalculate errors based on updated
take rates ( ) button. If the percentage value is displayed in red,
this indicates that the calculated error exceeds the specified Error
Threshold. This does not prevent you or the system from proceeding
with any operations.
The filter at the top of this column enables you to display only rows
where the error exceeds the Error Threshold.

February 2016
Related Topics

February 2016
Usage of Option Dialog Box
Usage of Option Dialog Box

right-click on the Package Name, Description, Member(s) or Description column for a
package name and select Set Option Usage.
Use this dialog box to edit the usage of options on vehicle models.
Objects
Table 27-13. Usage of Option Dialog Box Contents

Field Description
Vehicle Model table Lists the Vehicle Models in the first column. The
Options from the package being edited are listed along
the top of the columns.
If the box for a option / vehicle model combination is
selected, the option is included on the vehicle model.
However, if the table cell is red, the option is always
deleted when the package is ordered on this vehicle
model.
Assign To All Selects all option / vehicle model combinations in the
table.
Related Topics

February 2016

To access: In the Product Planner dialog box, click the Exclusive Variant Group Editor
button ( ), select Tools > Exclusive Variant Group Editor from the menu, or right-click
on the top product plan node in the Vehicle Configuration Manager Tree and select
Exclusive Variant Group Editor.
Use this dialog box to create and edit mutually-exclusive variant groupss (groups of variants
that are mutually-exclusive).
Objects
Table 27-14. Exclusive Variant Groups Editor Dialog Box Contents

Field Description
Variant Groups List Lists the Mutually-Exclusive Variant Groups in the
product plan.
Select a Mutually-Exclusive Variant Group in this
window to display the Variants that are set as
mutually-exclusive within it in the Members window.
To add a new Mutually-Exclusive Variant Group,
right-click on the window and select Add New Group;
the Add New Group dialog box is displayed where
you specify the name. The name is added to the
window.
To delete a Mutually-Exclusive Variant Group, select
it, right-click on it and select Delete Group.
Members Window Displays which variants are set as mutually-exclusive
in the Mutually-Exclusive Variant Group that is
selected in the Variants Groups list. Any variants that
are selected in this list are mutually-exclusive when the
Mutually-Exclusive Variant Group is applied to a
vehicle.
Associated Vehicle Models Lists the Vehicle Models collected together in the
Mutually-Exclusive Variant Group selected in the
Variants Groups list.
Edit Variants Opens the Variant Editor Dialog Box where you can
create and edit the variants in the Product Plan.
Import Displays a dialog box where you can navigate to an
XLS file containing variant group data that you want to
import into the product plan. Displayed only after Edit
has been clicked.

February 2016
Table 27-14. Exclusive Variant Groups Editor Dialog Box Contents (cont.)
Field Description
Export Enables you to export variant group data from the
product plan in an XLS file that can be imported into
other installations. Displayed only after Edit has been
clicked.
Related Topics

February 2016

To access: Open a diagram in Capital Integrator, press Space Bar and enter Product Planner.
Use this dialog box to view and edit vehicle configuration informations, import standard
product plan formats and to generate VVD - vehicle variant definitions and EVD - electrical
variant definitions.
Objects
Table 27-15. Product Planner Dialog Box Contents

Field Description
Save Saves the product plan and vehicle configuration data.
Launch Vehicle Creator Tool Launches the Vehicle Creator Dialog Box. This is used
for editing Option, Package and Vehicle Model
information.
Exclusive Variant Group Editor Launches the Exclusive Variant Groups Editor Dialog
Box. This is used for creating groups of mutually-
exclusive vehicle models. These can be used later in
harness optimization for identifying non-electrical
complexity drivers in harness families (for example,
LHD versus RHD, long wheel base versus short wheel
base).

February 2016
Table 27-15. Product Planner Dialog Box Contents (cont.)

Field Description
Vehicle Configuration Manager Tree Displays the project name and the Vehicle Models in
the product plan for the project. Under each vehicle
model, the tree lists the options for that vehicle model.
The options are grouped under the following:
• STANDARD OPTIONS
These are options that are present by default when
the vehicle model is ordered.
• RETAIL PACKAGES / FLEET PACKAGES
These are packages that the user can (but does not
have to) choose when ordering a vehicle model.
• MUST HAVE RESTRICTIONS / NOT
AVAILABLE RESTRICTIONS
These are option restrictions defined in the
packages that can be disabled on particular vehicle
models.
Clicking the following nodes determines what is
displayed to the right of the tree:
• The project name node displays the “Number of
Variants Associated with” window.
• The vehicle model node displays the Retail
Packages tab and Fleet Packages tab.
• A STANDARD OPTIONS node displays the
“Standard Option for:” window.
• A RETAIL PACKAGES node displays the “Retail
Packages for:” window.
• A FLEET PACKAGES node displays the “Fleet
Packages for:” window.
• A package under a FLEET PACKAGES or
RETAIL PACKAGES node displays the Package
window.
• A MUST HAVE RESTRICTIONS node displays
the “Must Have restrictions for model:” window.
• A NOT AVAILABLE RESTRICTIONS node
displays the “Not Available restrictions for model:”
window.

February 2016

Field Description
Number of Variants Associated with Lists the vehicle models for the project selected in the
Window Vehicle Configuration Manager tree.
If you click the Generate Variant Count button, the
system calculates the number of VVD - Vehicle
Variant Definitions and EVD - Electrical Variant
Definitions for each variant base and displays the
results in the Total Num. of Variants and Num. of
EE Variants columns. Displayed only when the
project name is selected in the Vehicle Configuration
Manager Tree.
Retail Packages tab Lists the retail packages for the vehicle model selected
in the Vehicle Configuration Manager tree. A retail
package is a package that is available to retail buyers.
For each package, it displays the name and description
as well as whether either of the following apply:
• Electrically Impacted
Specifies whether the package has an electrical
impact (selected) or not (unselected) on the vehicle.
• Select to Order
Specifies whether the package is ordered for the
vehicle model.
If you click the Generate Options button, the system
generates a list of options for the ordered vehicle.
Displayed only when a vehicle model is selected in the
Vehicle Configuration Manager Tree.

February 2016

Field Description
Fleet Packages tab Lists the fleet packages for the vehicle model selected
in the Vehicle Configuration Manager tree. A fleet
package is a package that is available to fleet buyers.
For each package, it displays the name and description
as well as whether either of the following apply:
• Electrically Impacted
Specifies whether the package has an electrical
impact (selected) or not (unselected) on the vehicle.
• Select to Order
Specifies whether the package is ordered for the
vehicle model.
If you click the Generate Options button, the system
generates a list of options for the ordered vehicle.
Displayed only when the vehicle model is selected in
the Vehicle Configuration Manager Tree.
Standard Option for: Window Lists the options in the product plan and indicates the
following:
• Available in Vehicle Model
Indicates whether the option is a standard option
that is present by default on the vehicle model
(selected) or not (unselected).
These settings are edited in the Vehicle Creator Dialog
Box.
Click the Show Selected Only button to reduce the
options displayed to only those that are standard on the
vehicle model (that is, selected in the Available in
Vehicle Model column).
Displayed only when a STANDARD OPTIONS node is
selected in the Vehicle Configuration Manager Tree.

February 2016

Field Description
Retail Packages for: Window Lists the packages for the vehicle model and indicates
the following for each option:
• Set As Standard
Indicates whether the package is sold on the
vehicle model as standard (selected) or not
(unselected) for a retail buyer.
Indicates whether the package is available on the
vehicle model (selected) or not (unselected) for a
retail buyer.
Box.
packages displayed to only those that are selected in
either of the columns.
Displayed only when a RETAIL PACKAGES node is
Package Window Lists the options in the package and indicates the
following:
• Delete Option
Indicates whether the option is not available on this
vehicle model for retail or fleet buyers. It is deleted
when a buyer orders the vehicle on this vehicle
model.
• Is Selected
retail or fleet buyer.
These settings are edited on the Retail Packages tab
and Fleet Packages tab of the Vehicle Creator Dialog
Box.
Displayed only when you double-click a package
under a RETAIL PACKAGES or FLEET PACKAGES
node in the Vehicle Configuration Manager Tree.

February 2016

Field Description
Fleet Packages for: Window Lists the packages for the vehicle model and indicates
the following for each option:
• Set As Standard
Indicates whether the package is sold on the
vehicle model as standard (selected) or not
(unselected) for a fleet buyer.
fleet buyer.
Box.
packages displayed to only those that are selected in
either of the columns.
Displayed only when a FLEET PACKAGES node is
Must Have restrictions for model: Lists the Must Have restriction groups defined for the
Window packages in the vehicle model.
If the box in the Apply ‘Must Have’ Restriction
column is selected, it indicates that the restriction
group has been applied to the vehicle model.
These settings are specified on the Restrictions tab of
the Vehicle Creator Dialog Box.
Displayed only when a MUST HAVE RESTRICTIONS
node is selected in the Vehicle Configuration Manager
Tree.
Not Available restrictions for model: Lists the Not Available restriction groups defined for
Window the packages in the vehicle model.
If the box in the Apply ‘Not Available’ Restriction
column is selected, it indicates that the restriction
group has been applied to the vehicle model.
These settings are specified on the Restrictions tab of
the Vehicle Creator Dialog Box.
Displayed only when a NOT AVAILABLE
RESTRICTIONS node is selected in the Vehicle
Configuration Manager Tree.

February 2016

Field Description
Status Log Displays the status, including error messages and
warnings, of the actions performed in the application.
See “Troubleshooting a Product Plan” on page 839.
Usage Notes
• You can open the Option Domain Editor dialog box from this dialog box by selecting
Tools > Option Domain Editor from the menu. Use this dialog box to create new
domains, delete existing domains and specify the domains to which options belong.
• You can display the total number of VVD - Vehicle Variant Definitions and EVD -
Electrical Variant Definitionss for a vehicle model by right-clicking on the vehicle
model node in the Vehicle Configuration Manager tree and selecting Show Number of
Variants; a Variant Number Count for... dialog box displays the totals.
• You can display a list of VVD - Vehicle Variant Definitionss for a vehicle model by
right-clicking on the vehicle model node in the Vehicle Configuration Manager tree and
selecting Show all VVDs; a VVD List for... dialog box displays the VVDs.
• In the Vehicle Configuration Manager tree, you can:
o Search for a vehicle model by right-clicking on the top product plan node and
selecting Find Model.
o Search for an option under a STANDARD OPTIONS node by right-clicking on that
node and selecting Find Standard Selection.
o Search for a package under a RETAIL PACKAGES / FLEET PACKAGES node
by right-clicking on that node and selecting Find Retail Package/ Find Fleet
Package.
o Search for a Must Have or Not Available restriction under a MUST HAVE
RESTRICTIONS/ NOT AVAILABLE RESTRICTIONS node by right-clicking
on that node and selecting Find Must Have / Find Not Available.
A Search dialog box is displayed where you enter a string. When you click Search, the
system searches in the tree for an appropriate element whose name contains the string.
Related Topics
Generating VVD and EVD Counts for a Vehicle Model

February 2016

To access: In the Product Planner dialog box, either click the Launch Vehicle Creator Tool
button ( ) or select Tools > Vehicle Creator Tool from the menu.
Use this dialog box to edit option, package and vehicle model information.
Objects
Table 27-16. Vehicle Creator Dialog Box Contents

Field Description
Standard Options tab The Option Name column lists the standard options in
the product plan. The Vehicle Models for the product
plan are listed along the top of the table. An option is
included on a vehicle model if it is selected in the
vehicle model column. To edit the table and enable the
menus, click the Edit button.

February 2016
Table 27-16. Vehicle Creator Dialog Box Contents (cont.)

Field Description
Retail/Fleet Packages tab Contains two tabs Retail Packages and Fleet
Packages. On both these tabs, the Package Name
column lists the packages available for retail buyers
and fleet buyers. The vehicle models for the project are
listed along the top of the table.
The vehicle model column for a package and its
included options indicates whether there is an
association between the package or option and the
vehicle model:
• Black - no association
model being edited.
Retail buyers get the package or option as standard.
Retail buyers can order the package or option on a
vehicle.
• F-S standard fleet option
Fleet buyers get the package or option as standard.
Fleet buyers can order the package or option on a
vehicle.
• S - included option
When a buyer orders the package on the vehicle
model, this option is included.
• D - deleted option
When a buyer orders the package on the vehicle
model, this option is not included.
To edit the table, click the Edit button.
You can right-click on the Package Name,
Description, Member(s) or Description column for a
package name and select Set Option Usage to display
the Usage of Option Dialog Box where you can edit
the usage of package options on vehicle models.
You can right-click on a variant base column for a
package name and select Edit Association to display
the Select Association Dialog Box (for a Package) to
specify how the package or option is associated with
the vehicle model.

February 2016
Table 27-16. Vehicle Creator Dialog Box Contents (cont.)

Field Description
Restrictions tab The Source Object Type->Name lists the packages
that have a Must Have or Not Available restriction and
that are supported by a vehicle model (either for retail
or fleet buyers).
For each package, the following is displayed:
• Restriction Name
Displays the Must Have or Not Available
restrictions that apply to the package.
• Restriction Members
The options (from the package in the Source
Object Type->Name column) that are associated
with the Must Have or Not Available restriction in
the Restriction Name column.
The rest of the table consists of columns for the vehicle
models in the product plan. Select the box in a column
where the Must Have or Not Available restriction
applies to that variant base. If a package is selected for
both retail and fleet, the status of the Must Have / Not
Available restrictions selected here applies to both
retail and fleet.
Note that you must click the Edit button before editing
these settings.
Usage Notes
• You can open the Option Editor Dialog Box from this dialog box by selecting Option/
Package > Option Editor from the menu. Use this dialog box to create new options,
delete existing options and define the inclusive / exclusive relationships between
options.
• You can open the Option Domain Editor Dialog Box from this dialog box by selecting
Option/Package > Option Domain Editor from the menu. Use this dialog box to
create new domains, delete existing domains and specify the domains to which options
belong.
• You can open the Package-Option Association Editor Dialog Box from this dialog box
by selecting Option/Package > Option/Package Association from the menu. Use this
dialog box to specify the options that are associated with packages.
• You can create a vehicle model from this dialog box by selecting Vehicle Model >
Create from the menu; an Input dialog box is displayed where you specify the name of
the vehicle model and you then specify the baseline options for the vehicle model in the
Select Standard Options Dialog Box.

February 2016
• You can delete a vehicle model from this dialog box by selecting Vehicle Model >
Delete from the menu to display the Select Vehicle Models for Deletion Dialog Box.
• You can split a vehicle model from this dialog box by selecting Vehicle Model > Split
from the menu. A selection dialog box is displayed where you select the vehicle model
to split, then you specify the names of the new vehicle models in a Vehicle Model
Editor dialog box. They are added to the Standard Options tab.
Related Topics

February 2016
Help Button Landing Pages for Product Planner
Help Button Landing Pages for Product

Planner
in the software.
Add New Option Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Package-Option Association Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 918
Edit Models associated with Variant Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
Exclusive/Inclusive Option Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
Exclusive/Inclusive Package Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919
Select Standard Options Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Usage of Option Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Exclusive Variant Groups Editor Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
Vehicle Creator Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
Add New Option Help

• Understanding Product Planner Concepts
• The Add New Option Dialog Box fields
• Adding an Option to the Product Plan
Package-Option Association Editor Help


February 2016
Edit Custom Groups Help

• The Package-Option Association Editor Dialog Box fields
• Adding Options to a Package
Edit Custom Groups Help

• Understanding Take Rates
• Understanding splitting take rates (see Splitting Take Rates)
• The Take Rate Editor Dialog Box fields
• Editing the Take Rates for Vehicle Models
Edit Models associated with Variant Help

• The Edit Models Associated with Variant Dialog Box fields
• Editing the Vehicle Models in a Variant
Exclusive/Inclusive Option Editor Help

• The Exclusive/Inclusive Option Editor Dialog Box fields
• Creating an Exclusive Group of Options
• Deleting an Exclusive Group of Options
• Creating an Inclusive Group of Options
• Deleting an Inclusive Group of Options
Exclusive/Inclusive Package Editor Help


February 2016
Variant Editor Help
• The Exclusive/Inclusive Package Editor Dialog Box fields

• Creating an Exclusive Group of Packages
• Deleting an Exclusive Group of Packages
• Creating an Inclusive Group of Packages
• Deleting an Inclusive Group of Packages
• Creating a Must Have or Not Available Restriction on a Package
• Deleting a Must Have or Not Available Restriction on a Package
Variant Editor Help

• The Variant Editor Dialog Box fields
• Creating a Variant in the Product Plan
• Deleting a Variant from the Product Plan
• Editing the Vehicle Models in a Variant
Option Editor Help

• The Option Editor Dialog Box fields
• Adding an Option to the Product Plan
• Deleting an Option from the Product Plan
• Creating an Exclusive Group of Options
• Deleting an Exclusive Group of Options
• Creating an Inclusive Group of Options
• Deleting an Inclusive Group of Options
Option Domain Editor Help


February 2016
Package Editor Help

• The Option Domain Editor Dialog Box fields
• Specifying an Option as Electrical
Package Editor Help

• The Package Editor Dialog Box fields
Packages
• Adding a Package to the Product Plan

• Deleting a Package from the Product Plan
Exclusive Groups of Packages
• Creating an Exclusive Group of Packages

• Deleting an Exclusive Group of Packages
Inclusive Groups of Packages
• Creating an Inclusive Group of Packages

• Deleting an Inclusive Group of Packages
Must Have or Not Available Restrictions
• Creating a Must Have or Not Available Restriction on a Package

• Deleting a Must Have or Not Available Restriction on a Package
Select Association (for an Option) Help

• The Select Association Dialog Box (for an Option) fields
• Editing the Association of an Option from a Package with a Vehicle Model

February 2016
Select Association (for a Package) Help
Select Association (for a Package) Help

• The Select Association Dialog Box (for a Package) fields
• Editing the Association of a Package with a Vehicle Model
Select Standard Options Help

• The Select Standard Options Dialog Box fields
• Adding a Vehicle Model to the Product Plan
Select Vehicle Models for Deletion Help

• The Select Vehicle Models for Deletion Dialog Box fields
• Deleting a Vehicle Model from the Product Plan
Take Rate Editor Help

• Understanding Take Rates
• Understanding splitting take rates (see Take Rate)
• The Take Rate Editor Dialog Box fields
• Editing the Take Rates for Vehicle Models
Usage of Option Help

• The Usage of Option Dialog Box fields

February 2016
Exclusive Variant Groups Editor Help
Exclusive Variant Groups Editor Help

• The Exclusive Variant Groups Editor Dialog Box fields
• Creating a Mutually-Exclusive Variant
• Deleting a Mutually-Exclusive Variant Group
• Importing Variant Group Data in XLS Format
• Exporting Variant Group Data in XLS Format
Product Planner Help

• The Product Planner Dialog Box fields
• Generating VVD and EVD Counts for a Vehicle Model
• Troubleshooting a Product Plan
Vehicle Creator Help

• The Vehicle Creator Dialog Box fields
• Adding a Vehicle Model to the Product Plan
• Deleting a Vehicle Model from the Product Plan
• Splitting a Vehicle Model in the Product Plan
• Editing the Association of a Package with a Vehicle Model
• Editing the Association of an Option from a Package with a Vehicle Model

February 2016
Vehicle Creator Help

February 2016
Chapter 28
Capital Level Manager - Harness Level
Optimization
This chapter contains information about working with Capital Level Manager - Harness Level
Optimization.
Introduction to Harness Level Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
Harness Level Optimization Tool Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 926
Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 927
Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 928
Creating a Metric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 929
Specifying the Architectural Cost of a Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 934
Manually Specifying the Options that Affect a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . 934
Manually Creating a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
Manually Editing a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
Manually Combining Harness Levels into One . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
Manually Deleting a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
Manually Deleting all Harness Levels for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
Editing the Properties and Attributes of a Harness Level. . . . . . . . . . . . . . . . . . . . . . . . . . 939
Harness Level Definitions (Harness Optimization) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941
Importing Harness Level Definitions (Harness Optimization). . . . . . . . . . . . . . . . . . . . . . 942
Exporting Harness Level Definitions (Harness Optimization). . . . . . . . . . . . . . . . . . . . . . 943
Full Complexity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 944
Manually Generating the Full Complexity Harness Levels for a Harness . . . . . . . . . . . . . 944
Validating Physical Harness Levels against Full Complexity Harness Levels . . . . . . . . . 945
Optimized Complexity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 948
Creating the Optimized Complexity Harness Levels for a Harness . . . . . . . . . . . . . . . . . . 948
Giveaway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 950

February 2016
Introduction to Harness Level Optimization
Introduction to Harness Level Optimization

Capital Level Manager is an add-on to Capital Integrator. The two main elements of it are the
Product Planner and the Harness Level Optimization tool.
See Capital Level Manager- Product Planner for further details about it.
The Harness Level Optimization tool allows you to define Giveaways for a harness, calculate
the cost of the giveaways and create Optimized Complexity harness levels using the chosen
giveaway settings.
It uses three main inputs:
• Connectivity data in the form of schematics in Capital Logic

• Topology data in the form of a design in Capital Integrator
• A Product Plan (either import an existing product plan or create a new product plan)
Note
Capital Level Manager requires a valid license in order to enable (expose) the functionality.
Contact Capital Support to obtain a license.
Related Topics
Optimization

There are various concepts used within the Harness Level Optimization tool.
• “Harness” on page 927
• “Metric” on page 928
• “Full Complexity” on page 944
• “Harness Level” on page 934
• “Harness Level Definitions (Harness Optimization)” on page 941
• “Giveaway” on page 950
• “Optimized Complexity” on page 948
• “Giveaway” on page 950

February 2016
Harness
Harness
An entire harness. An example could be Instrument Panel, Driver’s Door or Engine Harness. It
is sometimes referred to as a family in other systems because it consists of a number of part
numbers (or levels).

February 2016
Metric
Metric
Metrics are a defined methodology of costing a harness. A metric is a single value calculated as
a measure of worth (for example, cost or weight).
Capital Level Manager uses metrics for calculating the complexity costs when generating Full
Complexity and Optimized Complexity harness levels.
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.
A metric can be applied to multiple harnesses.
The default metrics supplied for Capital Level Manager are:
• Complexity Optimization
Used by Capital Level Manager to automatically optimize complexity solutions.
• Complexity Report
Used to see complexity-related attributes quickly (for example, level counts and
giveaway costs).
• 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.
• Missing Cost Report
Counts the number of objects that do not have an assigned cost. These objects are
therefore reporting estimations in the cost metric.
• Missing Weight Report
Counts the number of objects that do not have an assigned weight. These objects are
therefore reporting estimations in the weight metric.
• Weight
Calculates the total weight of design objects.
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.

February 2016
Creating a Metric
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.
Within the interface, you can modify the default metrics or even define new ones based on
attributes and properties of design objects. You can develop custom metrics 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.
Creating a Metric. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 929

Specifying the Architectural Cost of a Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933
Creating a Metric
You can create a new metric.
Procedure
1. With a Capital Integrator diagram open, press Space Bar and enter Harness Level
optimization; the Harness Level Optimization Dialog Box is displayed.
2. Click the Edit Metrics ( ) button; the Edit Metrics Dialog Box (Capital Level
Manager) is displayed.
3. Click Add New Metric ( ); a new row is created in the Metrics window.
4. Edit the name of the metric. Click elsewhere on the dialog box to finish; the row is
displayed like the other metrics.
Related Topics
Metric
Creating a Metric Element
Deleting a Metric Element
Editing a Metric Element Definition
Deleting a Metric Element Definition
Specifying the Architectural Cost of a Component

February 2016

You can create a new metric element. Metric elements can be turned on or off in an architectural
study.
Procedure
3. 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.
4. 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.
5. 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. See the Definition section of “Edit Metrics
Dialog Box (Capital Level Manager)” on page 963 for detailed information about
editing the element definition.
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.
6. Click OK.
Related Topics
Metric

February 2016
Creating a Metric

You can delete a metric element.
Procedure
3. 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
Metric
Creating a Metric

You can edit the metric element definitions of an existing metric.
Procedure

February 2016
3. In the Metrics window, click the metric element; the element definitions are displayed in
the Definition window.
4. Edit the element definitions as required. See the Definition section of “Edit Metrics
Dialog Box (Capital Level Manager)” on page 963 for detailed information about
editing a element definition.
5. Click OK.
Related Topics
Metric
Creating a Metric

You can delete a metric element definition from an existing metric.
Procedure
3. In the Metrics window, click the metric element; the element definitions for the metric
element are displayed in the Definition window.
4. In the Definition window, select the element definition to be deleted and click Remove
Selected Definition ( ). The element definition is removed from the window.
5. Click OK.
Related Topics
Metric
Creating a Metric

February 2016


You can specify the Architectural Cost attribute for an instance of an object in a design. The
default Cost metric uses this attribute when calculating its result. 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 Library and is read-only in the design tool.
Procedure
1. Right-click on the object in the Design Browser Window or the Diagram Window and
select Properties; the Edit Properties dialog box is displayed.
2. Click the General tab; the Architectural Cost attribute is listed. Edit the Value as
required and click OK.
Related Topics
Metric
Creating a Metric

February 2016
Harness Level
Harness Level
A uniquely orderable configuration of a harness based on standard and optional content. The
system can generate both full complexity and optimized complexity harness levels
automatically.
Alternatively, you can create harness levels manually within Capital Level Manager. You can
also export and import them in XML format. See “Harness Level Definitions (Harness
Optimization)” on page 941.
Manually Specifying the Options that Affect a Harness . . . . . . . . . . . . . . . . . . . . . . . . . 934

Manually Creating a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 935
Manually Editing a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 936
Manually Combining Harness Levels into One . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 937
Manually Deleting a Harness Level for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
Manually Deleting all Harness Levels for a Harness . . . . . . . . . . . . . . . . . . . . . . . . . . . . 938
Editing the Properties and Attributes of a Harness Level . . . . . . . . . . . . . . . . . . . . . . . . 939
Manually Specifying the Options that Affect a

Harness
You can manually specify the options that affect a harness and that can then be supported by
harness levels for that harness.
You do not need to do this if you have run Modular Wiring Synthesis.
Procedure
optimization; the Harness Level Optimization Dialog Box is displayed. The harnesses in
the design are listed in the Harness table.
2. Select the harness for which you want to specify the options and click the Define
Harness Levels ( ) button; the Harness Levels for: Dialog Box is displayed. The
dialog box lists the harness levels that have been created for the harness.
3. Click the Set the options that affect the Harness ( ) button; the Set Harness Options
Dialog Box (Capital Level Manager) is displayed.
4. Add the options that affect the harness to the Selected window.
5. Click OK.
6. The selected options are displayed in the Levels table on the Harness Levels for: Dialog
Box.

February 2016
Manually Creating a Harness Level for a Harness
Related Topics
Harness Level
Manually Editing a Harness Level for a Harness
Manually Combining Harness Levels into One
Manually Deleting a Harness Level for a Harness
Manually Deleting all Harness Levels for a Harness
Editing the Properties and Attributes of a Harness Level
Importing Harness Level Definitions (Harness Optimization)
Exporting Harness Level Definitions (Harness Optimization)

You can create a harness level for a harness and how to specify the options that are supported by
that harness level.
See “Harness Level” on page 352 for a definition of what a harness level is.
Procedure
2. Select the harness for which you want to create a harness level and click the Define
3. Click the Add a new Level to the harness ( ) button; the Add Level dialog box is
displayed.
4. Specify the name of the harness level and click OK.
The harness level is added to the Levels table.
5. Specify whether you want the harness Set as Active and select any models and options
supported by the harness level.
6. Click OK.
Related Topics
Harness Level
Manually Specifying the Options that Affect a Harness

February 2016


You can edit an existing harness level for a harness; that is, change its name and supported
options.
Procedure
2. Select the harness for which you want to edit a harness level and click the Define
3. Edit the harness level in the Levels table as required:
• To edit the name, double click it and enter the new name.
• Select any model and options supported by the harness level.
4. Click OK.
Related Topics
Harness Level

February 2016

You can combine harness levels for a harness.
Note
It is not possible to combine harness levels with different part numbers.
Procedure
2. Select the harness for which you want to combine harness levels and click the Define
3. Click on the parent level in the Levels table with which you want to combine another
harness level and click Combine two Levels into one ( ) button.
The Combine Levels for Dialog Box (Capital Level Manager) is displayed.
4. Add the levels that you want to combine with the parent harness level to the Combined
window and click OK.
5. The child levels are displayed below the parent level in the Levels table and a flipper
allows you to hide or show the referred harness levels.
Any vehicle models and options that are supported by the referred harness levels are
now supported by the parent harness.
6. Click OK.
Related Topics
Harness Level

February 2016

You can delete a selected harness level for a harness.
Procedure
2. Select the harness for which you want to delete a harness level and click the Define
3. Select the harness level in the Levels table and click the Delete the selected Level ( )
button; the harness level is deleted.
4. Click OK.
Related Topics
Harness Level

You can delete all harness levels for a harness.
Procedure
2. Select the harness for which you want to delete all harness levels and click the Define

February 2016
3. Click the Delete all Levels ( ) button.
All harness levels in the Levels table are deleted.

4. Click OK.
Related Topics
Harness Level
Editing the Properties and Attributes of a Harness

Level
You can edit the attributes and properties of a harness level.
Procedure
2. Select the harness for which you want to edit the properties or attributes of a harness
level and click the Define Harness Levels ( ) button; the Harness Levels for: Dialog
Box is displayed. The dialog box lists the harness levels that have been created for the
harness.
3. Select the harness level in the Levels table and click the Set the properties for the
selected Level ( ) button.
The Edit Properties dialog box for the harness level is displayed. See “Editing the
Attributes and Properties of Objects” on page 269 for more information about the
properties and attributes that you can edit.
4. When you have finished editing the attributes and properties, click OK.
5. Click OK on the “Harness Levels for:” dialog box.

February 2016
Related Topics
Harness Level

February 2016
Harness Level Definitions (Harness Optimization)
Harness Level Definitions (Harness

Optimization)
If you want to export/import harness level definitions, they must be in an XML file that
conforms to the document type definition (leveldef.dtd) that is located in the dtd directory of
your Capital installation.
The XML file can contain the following information:
• All options that affect the harness (regardless of their support by individual levels) - A
leveldef element defines the options which affect the harness and contains the levels.
• Harness level names - Defined by a name attribute in the level element. A level element
can contain child level elements. Note that no child level element can contain another
child level element.
• The partnumber attribute for a harness level - This can be contained in the level element.
• Vehicle models supported by each harness level - Defined by a vehiclemodelref that can
be contained in a level element.
• Options supported by each harness level - Options can be defined as optionref elements
and can be contained in the leveldef or level elements.
The following is an example of an XML import file:
<?xml version=”1.0” encoding=”UTF-8”?>

<DOCTYPE leveldef PUBLIC “-//Mentor Graphics Corporation//Capital Level
Definition 1.0//EN" “h:/capital_home/dtd/leveldef.dtd”>
<leveldef>
<level name=”Level-A” max=”true” partnumber=”H12345”>
<level name=”Level-A-A”>
</level>
</level>
</leveldef>
Importing Harness Level Definitions (Harness Optimization) . . . . . . . . . . . . . . . . . . . . 942

Exporting Harness Level Definitions (Harness Optimization) . . . . . . . . . . . . . . . . . . . . 943

February 2016
Importing Harness Level Definitions (Harness

Optimization)
You can import harness level definitions for a selected harness in XML format.
Procedure
2. Select the harness for which you want to import harness level definitions and click the
Define Harness Levels ( ) button; the Harness Levels for: Dialog Box is displayed.
3. Click the Import Levels from Level definition file ( ) button; the Import Levels
4. Navigate to the XML file containing the harness level definitions.
5. Specify whether you want to Retain existing levels.
If you select this, existing levels with the same name as an imported level are
overwritten and existing levels with a different name from all of the imported levels are
retained.
If you do not select this. existing levels with the same name as an imported level are
overwritten but existing levels with a different name from all of the imported levels are
deleted.
6. Click Import.
The harness levels are displayed in the Levels table. Any previously defined harness
levels are retained, deleted or updated as appropriate. The Set as Active setting for any
matching levels will not change.
7. To apply the imported levels, click the OK button. If you do not want to apply the
imported harness levels, click the Cancel button.
The following validation checks are performed:
• The options that affect the harness must exist in the project options list.
• The vehicle models supported by each level must exist in the project.
• The vehicle model reference elements must have a name attribute.
• The options supported by each level must exist in the project.
• The option elements must have a name attribute.
• Any option supported by a level must be included in the options that affect a harness.
• A level can contain a child level but a child level cannot contain another child level.

February 2016
• There cannot be more than one level element with the same name attribute.
• A child level cannot have a part number.
• There cannot be two level attributes with the same name attribute in the file.
If there are any errors with importing or validating the data from the XML file, a
message is displayed and the import is aborted.
Related Topics
Harness Level
Exporting Harness Level Definitions (Harness

Optimization)
You can export harness level definitions for a selected harness in XML format. This data can
then be imported into an installation of Capital Integrator.
Procedure
2. Select the harness for which you want to export harness levels and click the Export
Harness Levels ( ) button; a Export Harness Levels dialog box is displayed.
4. Click Export.
Related Topics
Harness Level

February 2016
Full Complexity
Full Complexity
Full complexity refers to a set of harness levels with zero giveaway prior to optimization.
You can manually generate the full complexity harness levels for a harness but this is an
optional step in the overall flow for using Capital Level Manager. They are generated
automatically when you open the Define Giveaway: Dialog Box that is used to generate the
Optimized Complexity harness levels.
In either case, the full complexity algorithm looks at harness variance definitions (HVDs).
HVDs are uniquely orderable sets of options (as defined by the product plan) scoped to a single
harness. HVDs are a further filtering of VVD - Vehicle Variant Definitions down to a single
harness.
Full complexity is the basis for optimized complexity and forms the base requirements for
validation.
Manually Generating the Full Complexity Harness Levels for a Harness. . . . . . . . . . . 944
Validating Physical Harness Levels against Full Complexity Harness Levels. . . . . . . . 945
Manually Generating the Full Complexity Harness

Levels for a Harness
You can create (generate) the full complexity harness levelss for a harness.
Prerequisites
• Basic product plan data must have been entered.
• In Capital Logic, the connectivity schematics for the project must have been created and
option expressions specified for design objects.
• In Capital Integrator, the topology design for the project must have been created and
option expressions specified for design objects.
• Modular Wiring Synthesis must have been run on the topology design.
Procedure
optimization, or right-click on a harness in the Design Browser (Design Tab) and select
Optimize Harness; the Harness Level Optimization Dialog Box is displayed.
2. Use the Metrics drop-down list to select the type of metrics that you want to apply to the
harnesses.
3. Select the harness in the Harness table and click the Calculate full complexity for
selected harnesses ( ) button.

February 2016
Validating Physical Harness Levels against Full Complexity Harness Levels
Results
• The Full Levels column displays how many Harness Levels this harness has if there is
no Giveaway.
• The Full <Metric> column displays the cost of the harness based on the metric selected
in the Metrics drop-down if there is no giveaway.
Related Topics
Full Complexity
Validating Physical Harness Levels against Full

Complexity Harness Levels
You can validate physical harness levels from a topology design against the full complexity
vehicle levels from the product plan.
When running validation, you open two diagrams from the project:
• One diagram from a design with modular wiring in it that was used when creating the
product plan. The modular is derived from the product plan and this defines the required
connectivity.
• One diagram that contains the physical wiring that should support the modular. This can
be created in Capital Integrator or be imported via a bridge.
Prerequisites
• The Full Complexity harness levels must have been generated for the harness (see
“Manually Generating the Full Complexity Harness Levels for a Harness” on page 944).
• The topology diagram containing the physical harness levels must exist in the same
project as the design used to create the product plan.
Procedure
1. Open the two diagrams in Capital Integrator.
2. Click on the diagram containing the synthesized, required wiring to ensure that it is
active in the Diagram Window, press Space Bar and enter Harness Level optimization;
the Harness Level Optimization Dialog Box is displayed.
Caution
The diagram containing the synthesized, required wiring must be the active diagram.
The diagram containing the physical wiring will be validated against it.

February 2016
3. Select a harness in the Harness table and click the Validate another complexity design
against this Full Complexity requirement ( ) button.
The Validation: Dialog Box is displayed and the full complexity harness levels for the
harness are displayed in the Full Complexity Requirements window. This window
indicates which of those harness levels are supported or are not supported by the
physical harness level.
Note
If harness connector names in the full complexity design do not match connector
names in the physical design, the Connector Mapping Tool Dialog Box is displayed
first. Use the dialog box to map the full complexity connectors to connectors on the
physical harness. The mapping is stored on the physical connector as a property. This
property can be viewed/edited/deleted like any other property. When you click OK or
Cancel on the Connector Mapping Tool dialog box, the “Validation:” dialog box is
displayed. OK saves any changes to the mappings whereas Cancel does not.
4. Either:
• Select a supported harness level in the Full Complexity Requirements window, the
Available Levels window displays the physical harness levels that support it. The
lowest cost physical level is displayed in bold at the top of the list.
• Select an unsupported harness level in the Full Complexity Requirements window,
the Available Levels window displays the physical harness levels that could be made
to support it.
5. Select a physical harness level in the Available Levels window:
• If a supported harness level is selected in the Full Complexity Requirements window
and a physical level that supports it is selected in the Available Levels window, the
Harness Results, Connectors window and Signals window indicate the Giveaway
cost of that harness level and which connectors / signals are given away.
• If an unsupported harness level is selected in the Full Complexity Requirements
window and a physical level that could support it is selected in the Available Levels
window, the Harness Results, Connectors window and Signals window indicate the
additional cost of using that physical harness level to support the full complexity
harness level and which required connectors / signals are currently missing from the
physical harness level.
6. Create a detailed report by clicking the Save detailed validation report for this
harness ( ) button to display a dialog box where you specify where you want to save
the report and the file name.
7. Click Save to return to the “Validation:” dialog box.
8. Click OK to exit the dialog box.

February 2016
Related Topics
Full Complexity
Manually Generating the Full Complexity Harness Levels for a Harness

February 2016
Optimized Complexity
Optimized complexity refers to a complexity solution of harness levels in which the user has
optimized the levels based on metrics and volumes.
The volumes result from the take rates entered in the Take Rate Editor Dialog Box. In most
cases, this requires Giveaway. In some cases, the zero giveaway solution may be optimal in
which case the Full Complexity and optimized complexity results will be the same.
The optimized levels are used in Composite Wiring Synthesis. The purpose of an optimized
level is that it can be manufactured cost effectively.
When defining the optimized complexity for a harness you can either:
• manually specify giveaway Options

• have the system automatically calculate which options to give away in order to have the
optimal harness complexity
In the automatic process, you define an upper limit of harness levels and can exclude specific
options from being given away as well as define conditions under which an option can be given
away. The system calculates the optimized complexity (giveaway) within these restrictions.
Creating the Optimized Complexity Harness Levels for a Harness . . . . . . . . . . . . . . . . 948
Creating the Optimized Complexity Harness Levels

for a Harness
You can create (generate) the optimized complexity harness levelss for a harness. This flow
includes specifying which options you want to be giveaway.
Prerequisites
• Take Rates must have been specified for the Vehicle Models and Options/Packages in
the harness. See “Editing the Take Rates for Vehicle Models” on page 879.
• You must have created the metrics that you want to use for costing the harnesses. See
“Metric” on page 928.
Procedure
optimization, or right-click on a harness in the Design Browser (Design Tab) and select
Optimize Harness; the Harness Level Optimization Dialog Box is displayed.
2. Use the Metrics drop-down drop-down list to select the type of metrics that you want to
apply to the harnesses.

February 2016
Creating the Optimized Complexity Harness Levels for a Harness
3. Select the harness in the Harness table and click the Define giveaway ( ) button; the
Define Giveaway: Dialog Box is displayed. The Full Complexity section displays the
number of harness levels and annual cost for the full complexity harness levels for the
harness.
4. Specify whether you want to use the MANUAL or AUTOMATIC method of specifying
giveaway options.
5. If using the MANUAL method:
a. You have the option to specify the Level Limit (that is, the upper limit of harness
levels that the harness can have).
b. In the Giveaway table, specify whether you want each option to be given away
Always, Never or Sometimes (in the case of Sometimes, specify the option
expression that represents the conditions under which the option can be given away).
6. If using the AUTOMATIC method:
a. You must specify the Level Limit (that is, the upper limit of harness levels that the
harness can have).
b. For options that cannot be given away, select Don’t in the Giveway table.
c. For options that can be given away under certain conditions, specify the option
expression representing those conditions in the Only when column.
Note
When you select an option in the table, the Connectors table and Signals table
show the connectors and signals associated with it.
7. In the Optimized Complexity section of the dialog box, click Recalculate Optimized
Complexity results ( ).
If using the MANUAL method:

The Optimized Complexity section updates to show the number of harness levels and
annual cost for the optimized complexity based on your giveaway options.
If using the AUTOMATIC method:
The system calculates which options to give away in order to have the optimal harness
complexity within your restrictions and displays the Levels and Cost for that solution.
Note
You can compare the Optimized Complexity figures with those in the Full
Complexity section. If the system cannot calculate an optimized complexity solution
within your Levels Limit restriction, a warning triangle () is displayed next to that field.

February 2016
Giveaway
8. Edit the giveaway options and click Recalculate Optimized Complexity results ( )
until you are satisfied with the number of optimized complexity harness levels and cost.
9. Click OK; you return to the Harness Level Optimization dialog box.
Results
In the Harness table:
• The Optimized Complexity Levels column displays how many harness levels this
harness has with the specified giveaway taken into account.
• The Optimized Complexity <Metric name> column displays the cost of the harness
based on the metric selected in the Metrics drop-down with the specified giveaway taken
into account.
Related Topics
Giveaway
Giveaway is a set of content (wires, connectors, bundles, etc.) that an engineer will place on
harness levels (harnesses) that only sometimes need it in order to reduce the number of levels.
For example, if you have a harness that has fog lamps and one that does not, you can choose to
give away fog lamps on all vehicles and eliminate the level without fog lamps. The
disadvantage is that the piece cost goes up (and the weight of the vehicles that do not actually
order fog lamps), but the advantage is that you keep the number of levels down, which reduces
the complexity management costs.
When defining the Optimized Complexity for a harness you can either:
• manually specify giveaway Options

• have the system automatically calculate which options to give away in order to have the
optimal harness complexity
In the automatic process, you define an upper limit of harness levels and can exclude specific
options from being given away as well as define conditions under which an option can be given
away. The system calculates the optimized complexity (giveaway) within these restrictions.
Related Topics
Harness Level
Harness

February 2016
Chapter 29
Harness Level Optimization Dialog Box and
Field Reference
This chapter offers a description of the dialog boxes available in the Capital Level Manager -
Harness Level Optimization application. For each dialog box, all fields are listed, along with a
full description of the field’s function.
Calculation Dialog Box (Capital Level Manager). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 952
Combine Levels for Dialog Box (Capital Level Manager) . . . . . . . . . . . . . . . . . . . . . . . . 953
Define Giveaway: Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 954
Condition Dialog Box (Capital Level Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 959
Connector Mapping Tool Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 962
Edit Metrics Dialog Box (Capital Level Manager) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963
Harness Levels for: Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 967
Harness Level Optimization Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 970
Set Harness Options Dialog Box (Capital Level Manager) . . . . . . . . . . . . . . . . . . . . . . . 974
Validation: Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 975
Help Button Landing Pages for Harness Level Optimization . . . . . . . . . . . . . . . . . . . . . 977
Calculation (Capital Level Manager) Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Combine Levels (Capital Level Manager) Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Define Giveaway Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Condition (Capital Level Manager) Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Edit Metrics Dialog Box (Capital Level Manager) Help . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Harness Level Optimization Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Set Harness Options (Capital Level Manager) Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Validation Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980

February 2016
Harness Level Optimization Dialog Box and Field Reference
Calculation Dialog Box (Capital Level Manager)
Calculation Dialog Box (Capital Level

Manager)
To access: Click on an editable string in a metric element definition displayed in the Edit
Metrics dialog boxfor Capital Level Manager and click Edit or New.
Use this dialog box 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 29-1. Calculation Dialog Box (Capital Level Manager) Contents

Field Description
Calculation window Used to define the simple query expression.
Click the blue circle ( ) 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 where you can enter a
property name.
If you select Value, 0.0 is added to the window. Click
that value to display a field where you can 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 Goto Advanced Editor ( ) to access
the Edit Query Expressions dialog box where you can use
advanced query editing functionality (see the Query
Expressions topic in the Capital Project User Guide for
information on how to use this dialog box).
Related Topics
Edit Metrics Dialog Box (Capital Level Manager)

February 2016
Combine Levels for Dialog Box (Capital Level Manager)
Combine Levels for Dialog Box (Capital Level

Manager)
To access: Click the Combine two Levels into one ( ) button on the Harness Levels for:
dialog box.
Used to select harness levels that you want to combine with the selected harness level in the
Harness Levels for: dialog box.
Objects
Table 29-2. Combine Levels for Dialog Box (Capital Level Manager) Contents
Field Description
Available Lists the harness levels that are available for selection. Select
the harness levels and click Add to move them to the Selected
window. Click Add All to move all available harness levels to
the Selected window.
Combined Lists the harness levels have been selected. To remove harness
levels from the list, select them and click Remove; they move
them to the Available window. To empty the list, click Remove
All.
Related Topics
Harness Levels for: Dialog Box

February 2016
Define Giveaway: Dialog Box

To access: In the Harness Level Optimization dialog box, select a harness in the Harness table
and click the Define giveaway ( ) button.
Use this dialog box to define optimized complexity by specifying giveaways for the harness and
view the effects of those giveaways in terms of how many harness levels you will have and the
harness cost.
Objects
Table 29-3. Define Giveaway: Dialog Box Contents

Field Description
Full Complexity The following data is displayed for the Full Complexity
Harness Levels for the Harness:
• Levels
Displays the number of harness levels for the full
complexity.
• Cost
Displays the annual cost for the full complexity harness
levels based on the metric selected in the Metrics drop-
down of the Harness Level Optimization Dialog Box.
If the Levels field displays a large number preceded by < and
the Cost field displays “Not available”, holding your mouse
cursor over them displays the tooltip “Calculating Full
Complexity would take too long”. This means that
calculating Full Complexity is likely to take a significant
amount of time and memory. The system, therefore, has not
calculated it automatically. If you want to see these values,
use the 'Generate Full Complexity' action in the Harness
Level Optimization dialog box to force the calculation. Be
aware that if the displayed number is very large, it is
possible that the memory requirements for full complexity
calculation may exceed the allocated memory.

February 2016
Table 29-3. Define Giveaway: Dialog Box Contents (cont.)

Field Description
Optimized Complexity The following data is displayed for the Optimized
Complexity of the Giveaway options selected in the
Giveaway table:
• Levels
Displays the number of harness levels for the current
optimized complexity. If this figure is red, this figure is
not up-to-date with the specified giveaway. Click
Recalculate Optimized Complexity results ( ) to
update this figure and the Cost.
• Level Limit
You specify the upper limit of harness levels that a
harness can have. Any optimized complexity solutions
above this level are considered unacceptable. If you have
selected the AUTOMATIC method of defining
giveaway, the system calculates the giveaway and
optimized complexity within this limit.
If the system cannot calculate an optimized complexity
solution within this restriction, a warning triangle ( ) is
displayed next to this.
• Cost
Displays the annual cost for the current optimized
complexity based on the metric selected in the Metrics
drop-down of the Harness Level Optimization Dialog
Box. If this figure is red, this figure is not up-to-date with
the specified giveaway. Click Recalculate Optimized
Complexity results ( ) to update this figure and the
Levels.
This enables you to compare the number of harness levels
and cost for the full complexity harness against the number
of levels and cost for the optimized complexity with the
specified giveaway.
MANUAL Specifies whether you want to:
AUTOMATIC • manually specify giveaway Options
• have the system automatically calculate which options to
give away in order to have the optimal harness
complexity within your specified restrictions (that is,
“Level Limit” and “Don’t/Only when” giveaway
restrictions on options).

February 2016

Field Description
Save optimized complexity Displays a Select Optimized Complexity Report file
matrix report resulting from dialog box where you specify the directory in which you
last applied giveaway want to save an optimized complexity matrix for the harness
levels.
The report contains:
• Device-Level Map - this matrix displays the generated
harness levels, which devices are on the harness levels,
the volumes of the harness levels, the costs for the
harness levels, the Variants supported by the harness
levels and the options supported by each harness level.
• Vehicle Model Map - this matrix displays which
Vehicle Models are supported by the harness levels.
• Derived Connector-Pin Map - this matrix displays
which unique pin outs for each connector are on which
signals.

February 2016

Field Description
Giveaway Table The appearance of this table depends on whether you have
selected the MANUAL or AUTOMATIC method of
specifying Giveaway.
Lists the options for the harness.
When using the MANUAL method, select whether you want
to give away each option:
• Always
• Never
• Sometimes
This column allows you to associate the giveaway of an
option with an option expression and thereby restrict the
conditions under which it is given away (for example, in
a particular market). Either enter the option expression
manually or click the ellipsis (...) button to display the
Edit Option Expression Dialog Box.
When you click Recalculate Optimized Complexity
results ( ), the Optimized Complexity data updates to
display the effect of giving away the selected options.
When using the AUTOMATIC method, you can apply the
following restrictions for each option:
• Don’t
Never give away this option.
• Only when
This column allows you to associate the giveaway of the
option with an option expression and thereby restrict the
conditions under which it is given away (for example, in
a particular market). Either enter the option expression
manually or click the ellipsis (...) button to display the
Edit Option Expression dialog box.
When you click Recalculate Optimized Complexity
results ( ), the system calculates which options to give
away in order to have the optimal harness complexity within
your restrictions and displays the Levels and Cost for that
solution.
When you select an option in the table, the connectors and
signals associated with it are displayed in the Connector
table and Signals table.

February 2016

Field Description
Enter Filter String ( ) In the field next to the Enter Filter String icon ( ), enter a
Clear Filter String ( ) series of characters. A filter is applied to the Giveaway table
so that only options with names containing that series of
characters are listed.
Click the Clear Filter String icon ( ) to clear the filter and
view all options.
Connectors Table Displays the connectors associated with the option selected
in the Giveaway table.
Signals Table Displays the signals associated with the option selected in
the Giveaway table.
Related Topics
Harness Level Optimization Dialog Box

February 2016
Condition Dialog Box (Capital Level Manager)

To access: Click on an editable string in a metric element definition displayed in the Edit
Metrics dialog box for Capital Level Manager and click Edit or New.
Use this dialog box to create or edit a condition using a simple query expression. This condition
is used to determine which of a set of metric element definitions is used to calculate the metric
element value for a particular object.
Objects
Table 29-4. Condition Dialog Box (Capital Level Manager) 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
this name will be listed to all users wherever they can select
a query expression in the system. Mandatory.

February 2016
Table 29-4. Condition Dialog Box (Capital Level Manager) Dialog Box
Contents (cont.)
Field Description
Condition window Used to define the simple query expression. Mandatory.
Click the blue circle ( ) 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 where you can enter a
property name.
If you select Value, 0.0 is added to the window. Click
that value to display a field where you can enter a
different value.
• 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 - this means that the attribute or property is not blank
• 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).
To clear the window, click Clear Condition ( ). To delete
the last term in the expression, click Remove last element
( ). Click Goto Advanced Editor ( ) to access the Edit
Query Expressions dialog box where you can use advanced
query editing functionality (see the Query Expressions topic
in the Capital Project User Guide for information on how to
use this dialog box).
Related Topics

February 2016

February 2016
Connector Mapping Tool Dialog Box
Connector Mapping Tool Dialog Box

To access: When you select a harness in the Harness Level Optimization dialog box and click
the Validate another complexity design against this Full Complexity requirement ( )
button, this dialog box is displayed if harness connector names in the full complexity design
do not match connector names in the physical design.
Use this dialog box to map the full complexity connectors to connectors on the physical harness.
Objects
Table 29-5. Connector Mapping Tool Dialog Box Contents

Field Description
Full Connectors Lists the connectors from the full complexity harness.
Physical Connectors Lists the connectors on the physical harness. Click on a cell to
display a dropdown list from which you select one or more
physical connectors to map to the full complexity connector.
Related Topics

February 2016
Edit Metrics Dialog Box (Capital Level

Manager)
To access: Click the Edit Metrics ( ) button on the Harness Level Optimization dialog box.
Use this dialog box to add, edit and delete the metrics that are available for use in harness
optimization.
Note
You can edit metrics only if you have the Edit Metrics permission set for your user
account.

February 2016
Objects
Table 29-6. Edit Metrics Dialog Box (Capital Level Manager) 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.
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 click on a metric element, the element definitions
are listed in the Definition window.
You can add a new metric by clicking Add New Metric
( ).
A new row is created and you edit the name of the metric.
Click elsewhere on the dialog to finish; the row is displayed
like the other metrics.
You can create a metric element by clicking the plus symbol
(+) on a metric row. A new metric element name is added
below the metric. 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.
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.
To delete a metric element, select it and click the minus
symbol (-) on the metric row. Alternatively, right-click it and
select Delete.

February 2016
Table 29-6. Edit Metrics Dialog Box (Capital Level Manager) Dialog Box
Contents (cont.)
Field Description
Definition Lists the element definitions of the metric element currently
selected in the Metrics window. See the Usage Notes below
for details of how to edit the element definitions.
Usage Notes
To add a new element definition, click Add New Definition ( ). The template for the new
element definition is added to the window.
Note
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 a 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:
• Click Object Type to select an object type from a list.

• Click {any} to display a menu where you can select or create a condition using a query
expression. Either:
o 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.
o Select New to display the Condition Dialog Box (Capital Level Manager) where you
can define a query expression. The query expression is saved to the database and
will be available to all users wherever they can select a query expression in the
system.

February 2016
o Select Edit to display either the Condition dialog box or the Edit Query Expressions
dialog box (see the Query Expressions topic in the Capital Project User Guide for
information on how to use this dialog box).
The displayed dialog box depends on which dialog box was used to create the
condition currently displayed in the metric template.
• Click Expression to display the Calculation Dialog Box (Capital Level Manager) where
you can create a calculation using a query expression.
Related Topics
Creating a Metric

February 2016

To access: Select a harness in the Harness Level Optimization dialog box and click the Define
Harness Levels ( ) button.
Use this dialog box to create and edit harness levels for a selected harness.
Objects
Table 29-7. Harness Levels for: Dialog Box Contents

Field Description
Set the options that Displays the Set Harness Options Dialog Box (Capital Level
affect the Harness Manager) where you can select the options that apply to the harness.
Import Levels from Displays the Import Levels dialog box where you browse to an
Level definition file XML file that contains harness level definitions that you want to
import.
Export Levels to Level Displays the Export Levels dialog box where you browse to the
definition file location where you want to save an XML file that contains the
harness level definitions. Specify a file name and click Export.
Add a new Level to the Displays the Add Level dialog box where you specify a name for a
harness new harness level and click OK. The harness level is created and a
row for it is added to the Levels table.
Combine two Levels Displays the Combine Levels for Dialog Box (Capital Level
into one Manager) where you select harness levels to combine with the
harness level that is selected in the Levels table.
Set the properties for Displays the Edit Properties dialog box for the harness level that is
the selected Level selected in the Levels table. See “Editing the Attributes and
Delete the selected Deletes the harness level that is selected in the Levels table.
Level
Delete all Levels Deletes all harness levels in the Levels table.

February 2016
Table 29-7. Harness Levels for: Dialog Box Contents (cont.)

Field Description
Levels Table Lists the existing harness levels for the harness selected in the
Design Browser (Design Tab).
• Level - The name of the harness level. The name is displayed in
red if there is a conflict between the vehicle models and options
that have been selected in the table.
• Set as Active -Specifies whether the harness level is currently
active (selected) or not (unselected).
• Model -Specifies whether the vehicle model represented by each
column is supported by the harness level (selected) or not
(unselected). If you hold the mouse cursor over a model column,
information is displayed about the variant options and options
that are associated with it.
When you select a vehicle model, you are specifying that the
harness level supports the variant options in the vehicle model.
• Options - Specifies whether the option represented by each
column is supported by the harness level (selected) or not
(unselected). If you hold the mouse cursor over an option
column, information is displayed about inclusive and exclusive
options.
The boxes can be the following colors:
• White with or without a tick - Indicates that the state of this
option is OK as it is (selected or unselected) and will still be OK
if changed (that is, select or unselect it). This can occur only if
the option is OPT in the vehicle model. It also means that there
are no issues with inclusive/exclusive relationships with other
options.
• Green - Indicates that the setting is OK as it is (selected or
unselected) but that there will be an issue if you change the
setting (that is, select or unselect it).
An example of a selected option (with a tick) marked green is
one that is STD in the vehicle model.
An example of an unselected option (without a tick) marked
green is one that is marked as N/A (that is, empty) in the vehicle
model.
• Magenta - Indicates that there is an issue with the setting. The
option is active on the harness level but unsupportd by any
vehicle model supported by the harness level.
If an option is selected (with a tick), unselecting it will normally
fix the issue.
If an option is unselected (without a tick), selecting it will
normally fix the issue.
In both cases, there may be some scenarios where there is no
viable setting of an option.
February 2016
Related Topics

February 2016

To access: With a Capital Integrator diagram open, press Space Bar and enter Optimize
Harnesses, or right-click on a harness in the Design Browser (Design tab) and select
Optimize Harnesses. Alternatively, use the keyboard shortcut Ctrl+F7.
Use this dialog box to select the harnesses for you which you want to perform actions related to
the generation of full complexity and optimized complexity harness levels.
Objects
Table 29-8. Harness Level Optimization Dialog Box Contents

Field Description
Save complexity matrix When a Harness is selected in the Harness table, this
displays a Select Complexity Report file dialog box where
you specify the directory in which you want to save a
complexity matrix for the harness levels for that harness in
an XLS file.
On that dialog box, you select whether you want the matrix
to be for Full Levels or Optimized Levels.
In both cases, the report contains:
• Device-Level Map - this matrix displays the generated
harness levels, which devices are on the harness levels,
the volumes of the harness levels, the costs for the
harness levels, the Variants supported by the harness
levels and the Options supported by each harness level.
• Vehicle Model Map - this matrix displays which
Vehicle Models are supported by the harness levels.
• Derived Connector-Pin Map - this matrix displays
which unique pin outs for each connector are on which
signals.
• Summary
Full The buttons in this section of the toolbar relate to Full
Complexity data.
Recalculate Full Complexity Recalculates the full complexity harness levels for the
results for selected harness(es) harnesses selected in the Harness table.
Note that this action is optional. When you click the Define
giveaway ( ) button, the full complexity harnesses are
calculated automatically in the Define Giveaway: Dialog
Box.

February 2016
Table 29-8. Harness Level Optimization Dialog Box Contents (cont.)

Field Description
Validate another complexity Displays the Validation: Dialog Box. This validates whether
design against this Full a physical design has harness levels that support the required
Complexity requirement connectivity from the design for which you have been
editing the product planner. The physical design is in a
different diagram. See “Validating Physical Harness Levels
against Full Complexity Harness Levels” on page 945.
Note that if harness connector names in the full complexity
design do not match connector names in the physical design,
the Connector Mapping Tool Dialog Box is displayed where
you map the full complexity connectors to connectors on the
physical harness.
Optimized The buttons in this section of the toolbar relate to Optimized
Complexity data.
Define giveaway Displays the Define Giveaway: Dialog Box where you
specify Giveaways for the harness and view the effects of
those giveaways in terms of how many harness levels you
will have and the harness cost.
Recalculate Full and Optimized Generates the Full Complexity and Optimzed Comlexity
Complexity results for selected harness levels for the harnesses selected in the Harness table.
harness(es) Note that this action is optional. When you click the Define
giveaway ( ) button, the full complexity harnesses and
optimized complexity harnesses are calculated automatically
in the Define Giveaway: Dialog Box.
Export harness levels for When a harness is selected in the Harness table, this displays
selected harnesses a Export Harness Levels dialog box where you specify the
directory in which you want to save the Harness Level data
for the harness in an XML file. This data can be imported
into an installation of Capital Integrator.
Import harness levels for When a harness is selected in the Harness table, this displays
selected harnesses a Select file containing harness levels to import dialog box
where you navigate to an XML file of harness levels that you
want to import for the harness.
Define harness levels Displays the Harness Levels for: Dialog Box where you
create and edit harness levels for a selected harness.
Edit Metrics Closes Harness Level Optimization and opens the Edit
Metrics Dialog Box (Capital Level Manager) where you can
specify the metrics available for use in harness optimization.

February 2016
Table 29-8. Harness Level Optimization Dialog Box Contents (cont.)

Field Description
Metrics Drop-down By default, this contains Count / Length / Cost / Weight.
Indicates the type of Metrics that are being used. Select the
type from the drop-down list. Typically, you would use cost
but you may want to optimize your design for something like
weight or length.
Harness Table Lists all harnesses in the diagram for which you are running
harness optimization. If you are working in multi-user mode,
this list is filtered down to those that you have locked.
If is displayed, this indicates that Variants are used in this
harness. If you hold your mouse cursor over the icon, a tool
tip displays any variants that are used in variantly-placed
devices, or are on bundles or bundle regions in that
particular harness. This therefore gives you an idea of how
mechanical differences effect the harness wiring.
For each harness, it displays:
• Full Complexity Levels
How many Harness Levels this harness has if there is no
Giveaway.
• Full Complexity <Metric name>
The cost of the harness based on the metric selected in
the Metrics drop-down if there is no giveaway.
• Limit
The upper limit of harness levels that a harness can have,
as specified in the Level Limit field of the Define
Giveaway: Dialog Box. Any optimized complexity
solutions above this level are considered unacceptable. If
the level limit is breached, a warning triangle ( ) is
displayed next to this.
• Optimized Complexity Levels
How many harness levels this harness has when any
specified giveaway is taken into account.
• Optimized Complexity <Metric name>
The cost of the harness based on the metric selected in
the Metrics drop-down when any specified giveaway is
taken into account.
The totals for all of the harnesses are listed at the bottom of
the table.
Related Topics
Manually Generating the Full Complexity Harness Levels for a Harness

February 2016


February 2016
Set Harness Options Dialog Box (Capital Level Manager)
Set Harness Options Dialog Box (Capital Level

Manager)
To access: Click the Set the options that affect the Harness ( ) button on the Harness Levels
for: dialog box.
Use this dialog box to select the options that apply to a harness.
Objects
Table 29-9. Set Harness Options Dialog Box (Capital Level Manager) Contents
Field Description
Available Lists the options that are available for selection. Select the
options and click Add to move them to the Selected window.
Click Add All to move all available options to the Selected
window.
Selected Lists the options have been selected. To remove options from
the list, select them and click Remove to move them to the
Available window. To empty the list, click Remove All.
Related Topics

February 2016
Validation: Dialog Box

To access: Select a harness in the Harness Level Optimization dialog box and click the Validate
Harness Levels ( ) button.
Use this dialog box to validate physical harness levels from a topology design against the full
complexity harness levels from the product plan design. The physical design is in a different
diagram.
Description
See “Validating Physical Harness Levels against Full Complexity Harness Levels” on page 945.
Objects
Table 29-10. Validation: Dialog Box Contents

Field Description
Save detailed validation Saves a report that contains a summary of everything from the
report for this harness validation.
Full Complexity Displays the Full Complexity harness levels from the product
Requirements Window plan and indicates whether the physical harness levels support
them or not.
The Total Cost at the bottom of this window is the cost for the
full complexity (based on the metric and the take rates). The
Volume is the number of vehicles this harness will be installed
in (most will be the platform volume, but some smaller
harnesses are optional meaning they won't be on all vehicles).
Available Levels Window If a supported harness level is selected in the Full Complexity
Requirements window, this displays the physical harness levels
that support it. The lowest cost physical level is displayed in
bold at the top of the list.
If an unsupported harness level is selected in the Full
Complexity Requirements window, this displays the physical
harness levels that could be made to support it.
The Total Cost at the bottom of this window is for the validated
design (based on the chosen metric and based on the volumes of
the full complexity levels they support). The Giveaway Cost is
the difference between these 2 costs and is the giveaway cost.

February 2016
Table 29-10. Validation: Dialog Box Contents (cont.)

Field Description
Harness Results The results in this box are calculated once for the entire harness.
The Count column indicates how many of the vehicles that
could be ordered and that require this harness are supported by a
harness level in the validated design. The Volume column
similarly shows the support/unsupported vehicles in relation
with their expected volumes (calculated from the take rates).
The Giveaway is the total giveaway cost calculated based on the
total cost of the full complexity and the total cost of
implementing the validated design against it using the metric
selected in the Harness Level Optimization Dialog Box. This
indicates to the user how “efficient” the validated design might
be.
Connectors Window If a supported harness level is selected in the Full Complexity
Requirements window and a physical level that supports it is
selected in the Available Levels window, this displays which
connectors are given away for that level.
Complexity Requirements window and a physical level that
could support it is selected in the Available Levels window, this
displays:
• Which required connectors are currently missing from the
physical harness level (indicated by an error icon)
• Which connectors are given away for that level (no error
icon)
Signals Window If a supported harness level is selected in the Full Complexity
Requirements window and a physical level that supports it is
selected in the Available Levels window, this displays which
signals are given away for that level.
Complexity Requirements window and a physical level that
could support it is selected in the Available Levels window, this
displays:
• Which required signals are currently missing from the
physical harness level (indicated by an error icon)
• Which signals are given away for that level (no error icon)
Related Topics

February 2016
Help Button Landing Pages for Harness Level Optimization
Help Button Landing Pages for Harness Level

Optimization
in the software.
Calculation (Capital Level Manager) Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Combine Levels (Capital Level Manager) Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Define Giveaway Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 977
Condition (Capital Level Manager) Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 978
Edit Metrics Dialog Box (Capital Level Manager) Help . . . . . . . . . . . . . . . . . . . . . . . . . 978
Harness Level Optimization Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Set Harness Options (Capital Level Manager) Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . 979
Validation Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 980
Calculation (Capital Level Manager) Help

• Understanding Harness Level Optimization Tool Concepts
• The Calculation Dialog Box (Capital Level Manager) fields
• Creating a Metric Element
• Editing a Metric Element Definition
• Deleting a Metric Element Definition
Combine Levels (Capital Level Manager) Help

• The Combine Levels for Dialog Box (Capital Level Manager) fields
• Manually Combining Harness Levels into One
Define Giveaway Help


February 2016
Condition (Capital Level Manager) Help

• The Define Giveaway: Dialog Box fields
• Creating the Optimized Complexity Harness Levels for a Harness
Condition (Capital Level Manager) Help

• The Condition Dialog Box (Capital Level Manager) fields
Connector Mapping Tool Help

• The Connector Mapping Tool Dialog Box fields
• Validating Physical Harness Levels against Full Complexity Harness Levels

Help
• The Edit Metrics Dialog Box (Capital Level Manager) fields
• Creating a Metric
• Capital Level Manager - Harness Level Optimization

February 2016
Harness Levels Help
Harness Levels Help

• The Harness Levels for: Dialog Box fields
• Manually Specifying the Options that Affect a Harness
• Manually Creating a Harness Level for a Harness
• Manually Editing a Harness Level for a Harness
• Manually Combining Harness Levels into One
• Manually Deleting a Harness Level for a Harness
• Manually Deleting all Harness Levels for a Harness
• Editing the Properties and Attributes of a Harness Level
• Importing Harness Level Definitions (Harness Optimization)
• Exporting Harness Level Definitions (Harness Optimization)
Harness Level Optimization Help

• The Harness Level Optimization Dialog Box fields
• Manually Generating the Full Complexity Harness Levels for a Harness
• Creating the Optimized Complexity Harness Levels for a Harness
Set Harness Options (Capital Level Manager) Help

• The Set Harness Options Dialog Box (Capital Level Manager) fields
• Manually Specifying the Options that Affect a Harness

February 2016
Validation Help
Validation Help
• The Validation: Dialog Box fields

February 2016
Chapter 30
Troubleshooting
This chapter contains troubleshooting tips.

Troubleshooting Wiring Synthesis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Unexpected Option Expression on a Generated Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Troubleshooting Capital AutoView Assist for Integrator . . . . . . . . . . . . . . . . . . . . . . . . 984
New Symbol Instance for Additional Pins when Using a Prototype . . . . . . . . . . . . . . . . . 984
Troubleshooting Capital Level Manager - Product Planner . . . . . . . . . . . . . . . . . . . . . . 985

February 2016
Troubleshooting
Troubleshooting Wiring Synthesis
Troubleshooting Wiring Synthesis

Troubleshooting tips are available for wiring synthesis.
Unexpected Option Expression on a Generated Wire . . . . . . . . . . . . . . . . . . . . . . . . . . . 982
Wiring Synthesis Removes a Splice

Symptom: Wiring Synthesis removes a splice that has been added manually after a previous
wiring synthesis run.
Solution
Add a “Protect Wiring by Attribute/Property” constraint to the topology design or harness on
which the splice is placed. When setting the constraint specify the name of the signal that passes
through the splice.For example, if the signal is called 2N-AUX-CTL-1, the constraint would be:
Do protect wiring of signals with attribute/property matching Name = 2N-AUX-CTL-1
See Assigning a Rule or Constraint to an Object in the Capital Design Tools - Common
Functions User Guide for instructions on how to add a constraint.
Unexpected Option Expression on a Generated

Wire
Symptom: You observe an unexpected option expression on a wire generated during wiring
synthesis.
Solution
This requires you to perform some investigation to determine why the wire has been assigned
the option expression. To do this, you need to investigate all of the connectivity for that wire
and its source signal:
1. Set all harness levels active to see all generated wires. Ensure that the whole signal is
routed as you may need to investigate all of the generated wires for the signal and not
just one wire.
2. Identify all the wires that carry this signal and:
a. Identify the option expressions on the individual wires. If they have different option
expressions, try to identify why they have the expressions that they do.
b. Identify multi-terms and splices to which the wires are connected. Identify whether
there are any rules that apply to these objects, particularly regarding options.

February 2016
Troubleshooting
Unexpected Option Expression on a Generated Wire
3. Determine the option expression assigned to the source signal (net) in Capital Logic.
The wire should have that option expression within its own option expression.
4. Determine the option expression assigned to the connected pins/devices for the signal in
Capital Logic. Options defined for those objects will be passed to any wires generated
for the signal.
5. Consider any variant placement of connectors. When connectors are variantly placed,
they are given another option expression that would also affect the option expression
generated for connecting wires.
6. Consider any options assigned to bundles. These also affect the option expression for
any wires that pass through them.

February 2016
Troubleshooting
Troubleshooting Capital AutoView Assist for Integrator
Troubleshooting Capital AutoView Assist for

Integrator
Troubleshooting tips are available for Capital AutoView Assist for Integrator.
New Symbol Instance for Additional Pins when Using a Prototype . . . . . . . . . . . . . . . . 984
New Symbol Instance for Additional Pins when

Using a Prototype
Symptom: When creating a design using a prototype containing symbols, Capital AutoView
Assist for Integrator generates a new symbol instance for newly required pins.
Solution
When Capital AutoView Assist for Integrator creates a wiring diagram, if it uses a prototype
containing symbols and those symbol instances have insufficient pins for the newly synthesized
wiring, then a new symbol instance is created for the additional pins.
Capital AutoView Assist for Integrator will not add additional pins to symbol instances already
existing in a prototype diagram.
You can prevent the creation of a new symbol instance by adding the required pins to the
prototype wiring diagram prior to running Capital AutoView Assist for Integrator.

February 2016
Troubleshooting
Troubleshooting Capital Level Manager - Product Planner
Troubleshooting Capital Level Manager -

Product Planner
Troubleshooting tips are available for Capital Level Manager - Product Planner.
Error while Initializing Licensing Subsystem

Symptom: When opening the Product Planner dialog box, the following error is displayed:
Error whilst initializing licensing subsystem. Attempting to re-initialize.
Solution
The Product Planner attempts to create a licensing connection to the main Capital system. The
initialization of this is sometimes delayed and is then subject to a later attempt at re-
initialization. This message indicates this situation.
If the connection cannot be obtained after this second attempt, you will see further error
messages telling you to restart the application.

February 2016
Troubleshooting
Error while Initializing Licensing Subsystem

February 2016
Third-Party Information
For full information on open source and third-party software that may be included in Capital products see the Third-Party
Information section in the Capital Design Tools - Common Functions User Guide. For last minute additions to this
information refer to the latest Capital Release Highlights document.
Index
—C—
Index
—A— Capital AutoView Assist for Integrator, 551

Add Capital Bridges
backshell terminations, 171 Bridge In, 817
cavities to bundle fanout, 144 Bridge Out, 817
connectors to slots, 139 Overview, 817
hole to slot, 409 Capital Integrator
inline plugs, 151, 152 overview, 32
inline receptacles, 149, 150 Capital Project, 67
interface connector, 158 Cavities, 162
properties, 480
editing maps, 144
properties to conductor using rules, 313 removing unused from slots, 262
skeleton graphic, 810 Change
wires, 477
background color, 79
adding, 149, 150, 151, 152 Changes
Advanced naming, 284 synchronizing, 70
Assign
Check
library description, 274
designs errors, 74
options, 279 Checks
Associate
design rule checks, 74
logical designs, 37
Combine
Attributes devices in slots, 189
descriptions, 42
ground devices in slots, 192
editing, 280
Component
—B— selecting, 277
Background color, 79 Composite data
Backshell terminations overview, 318
adding, 171 Composites
overview, 167 synthesizing wiring, 442
Bundle length Concurrency tab, 638
editing, 480 Conductors
Bundle regions displaying name for multiple segments, 273
editing offset of nodes, 284 Connectivity
Bundles reports, 424
creating, 106 Connectors
evaluating rules, 291 adding to slot, 139
regions, 121 editing cavities, 162
reporting widths, 430 editing mapping for slot, 145
overview, 141
refining, 210

February 2016
removing unused from slots, 262 creating, 62
slot, 139 deleting, 67
wire count reports, 427 editing information, 65
Constraints editing properties, 74
overview, 287 managing change synchronization, 71
Convert refreshing, 69
butt splice to center strip, 501 releasing, 71
center strip splice to butt, 502 saving, 68
multiple termination to splice, 500 Device connectors
Copy overview, 141
objects, 83 Devices
wiring across levels, 505 combining in slots, 189
Create ground devices, 198
bundles, 106 placing in slots, 174
designs, 62 Diagrams
diagrams, 76 adding skeleton graphic, 810
harness report, 420 changing background color, 79
inline pairs, 148 creating, 76
multicores, 503 Display
Project, 56, 837 conductor name for multiple segments, 273
slot, 97 option names descriptions, 339
slot for device, 98
splices, 496 —E—
through nodes, 127 Edit
Cross references attributes, 280
refreshing, 70 bundle lengths, 480
cavities of connector, 162
—D— cavity map, 144
Decompose connector mapping for slot, 145
splices, 499 ground signals, 507
Define inline pair cavities, 153
harness levels, 352 options, 279
variant options, 341 splices, 496
vehicle configurations based on levels, 364 wire paths, 479
vehicle models, 346 wires, 476
Delete editing connector, 162
harness levels, 449 Errors
terminal bar definitions, 411 checking designs, 74
vehicle configurations, 449 Evaluate
wiring, 449 rules on bundle regions, 291
Depopulate Exclude
wiring, 506 slot from harness, 112
Designs Export
associating, 37 interface connector definitions, 159
checking for errors, 74 wiring, 508
checks, 74 Extensibility plugins

February 2016
attribute descriptions, 42 adding, 158
exporting, 159
—F— importing definition, 159
Fanouts overview, 154
adding bundles, 144 Internal
Filter signals, 259
topology, 89
—J—
—G— Junction boxes
Generate overview, 100
option expressions, 342
slot circuits, 258 —L—
Ground devices, 198 Levels
combining in slots, 192 reports, 421
Ground signals Library description
editing, 507 assigning, 274
unassigning, 276
—H— updating, 275
Harness connectors viewing, 277
overview, 141 Library parts
Harness levels refreshing, 69
defining, 352 Locate
deleting, 449 source functional object, 90
editing on which wire exists, 480 Logical changes
set active, 358 refreshing, 70
specifying part numbers, 357
Harnesses —M—
specifying domain, 113 Manage
Holes design change synchronization, 71
adding to slot, 409 Materials
moving, 409 reporting statistics, 426
removing unused from slots, 262 Modify
shield terminations, 505
—I— Move
Icons, 650 holes, 409
Import slot connectors, 140
interface connector definition, 159 splices, 497
terminal bar definitions, 410 Multicores
wiring, 509 assigning properties by rules, 495
Include creating, 503
slot with harness, 111 Multiple terminations
Inline pairs converting to splices, 500
cavities, 153
creating, 148 —N—
Inline plugs, 151, 152 Names
Inline receptacles, 149, 150 advanced naming, 284
Interface connectors specifying, 271

February 2016
New Property dialog box, 752 editing for design, 74
—O— —R—
Objects Refine
copying, 83 connectors, 210
locating source object, 90 Relays
select in diagrams, 85 overview, 413
selecting all in diagram, 83 Release
selecting parent object, 87 designs, 71
Offsets of bundle region nodes, 284 Release levels, 67
Option expressions Remove
generating for wires, 342 unused connectors and cavities from slots,
Options 262
assigning, 279 Reports
displaying names or descriptions, 339 bundle width, 430
editing, 279 connectivity, 424
refreshing, 69 harnesses, 420
reports, 421 material statistics, 426
Overview options and levels, 421
backshell terminations, 167 wire count for connector, 427
Capital Integrator, 32 Resize
composite data, 318 slots, 99
connectors, 141 Route codes
constraints, 287 specifying, 167
ground devices, 198 Rules
interface connectors, 154 adding properties to conductors, 313
relays, 413 overview, 287
rules, 287
slot connectors, 139 —S—
Save
—P— designs, 68
Part numbers Scale, 810
specifying for harness levels, 357 Select
Physical scale all objects in diagram, 83
specifying, 810 component, 277
Place objects in diagram, 85
devices in slots, 174 parent object, 87
Plugin, 650 Set
PluginDevelopment.pdf, 930 active harness level, 358
Plugins active vehicle configuration, 368
attribute descriptions, 42 Shared Objects
Project refreshing, 69
Create, 56, 837 Shield terminations
Properties modifying, 505
adding, 480 Short description, 273
assigning to wires by rules, 495 Signals

February 2016
internal, 259 deleting definitions, 411
Skeleton graphics importing definitions, 410
adding to diagram, 810 Through nodes
Slot connectors creating, 127
moving, 140 Topologies
Slots filtering, 89
adding connectors, 139
adding holes, 409 —U—
creating, 97 Unassign
creating for device, 98 library descriptions, 276
editing connector mapping, 145 Update
excluding from harness, 112 library descriptions, 275
generating circuits, 258 wire lengths, 504
including with harness, 111 —V—
junction boxes, 100 Variant options
placing devices, 174 defining, 341
removing unused connectors and cavities, Variants
262 refreshing, 69
resizing, 99 Vehicle configurations
Snap To Object, 549 defining with harness levels, 364
Specify deleting, 449
domain for harnesses, 113 setting active, 368
name property, 271 Vehicle models
part number for harness level, 357 defining, 346
physical scale, 810 View
route codes, 167 library descriptions, 277
specifying physical, 810
Splices —W—
assigning properties by rules, 495 Wire lengths
converting butt to center strip, 501 updating, 504
converting center strip to butt, 502 Wires
creating, 496 adding, 477
decomposing, 499 assigning properties by rules, 495
editing, 496 editing, 476
moving, 497 editing harness levels, 480
Symbol libraries editing paths, 479
refreshing, 69 generating option expressions, 342
Synchronize reports for connectors, 427
change management, 71 Wiring
changes, 70 copying across levels, 505
Synthesize deleting, 449
composite wiring, 442 depopulating, 506
wiring, 440 exporting, 508
importing, 509
—T— synthesizing, 440
Terminal bars

February 2016
February 2016
End-User License Agreement
The latest version of the End-User License Agreement is available on-line at:
www.mentor.com/eula
IMPORTANT INFORMATION
USE OF ALL SOFTWARE IS SUBJECT TO LICENSE RESTRICTIONS. CAREFULLY READ THIS LICENSE
AGREEMENT BEFORE USING THE PRODUCTS. USE OF SOFTWARE INDICATES CUSTOMER’S COMPLETE
AND UNCONDITIONAL ACCEPTANCE OF THE TERMS AND CONDITIONS SET FORTH IN THIS AGREEMENT.
ANY ADDITIONAL OR DIFFERENT PURCHASE ORDER TERMS AND CONDITIONS SHALL NOT APPLY.
END-USER LICENSE AGREEMENT (“Agreement”)
This is a legal agreement concerning the use of Software (as defined in Section 2) and hardware (collectively “Products”)
between the company acquiring the Products (“Customer”), and the Mentor Graphics entity that issued the corresponding
quotation or, if no quotation was issued, the applicable local Mentor Graphics entity (“Mentor Graphics”). Except for license
agreements related to the subject matter of this license agreement which are physically signed by Customer and an authorized
representative of Mentor Graphics, this Agreement and the applicable quotation contain the parties’ entire understanding
relating to the subject matter and supersede all prior or contemporaneous agreements. If Customer does not agree to these
terms and conditions, promptly return or, in the case of Software received electronically, certify destruction of Software and all
accompanying items within five days after receipt of Software and receive a full refund of any license fee paid.
1. ORDERS, FEES AND PAYMENT.
1.1. To the extent Customer (or if agreed by Mentor Graphics, Customer’s appointed third party buying agent) places and Mentor
Graphics accepts purchase orders pursuant to this Agreement (each an “Order”), each Order will constitute a contract between
Customer and Mentor Graphics, which shall be governed solely and exclusively by the terms and conditions of this Agreement,
any applicable addenda and the applicable quotation, whether or not those documents are referenced on the Order. Any
additional or conflicting terms and conditions appearing on an Order or presented in any electronic portal or automated order
management system, whether or not required to be electronically accepted, will not be effective unless agreed in writing and
physically signed by an authorized representative of Customer and Mentor Graphics.
1.2. Amounts invoiced will be paid, in the currency specified on the applicable invoice, within 30 days from the date of such invoice.
Any past due invoices will be subject to the imposition of interest charges in the amount of one and one-half percent per month
or the applicable legal rate currently in effect, whichever is lower. Prices do not include freight, insurance, customs duties, taxes
or other similar charges, which Mentor Graphics will state separately in the applicable invoice. Unless timely provided with a
valid certificate of exemption or other evidence that items are not taxable, Mentor Graphics will invoice Customer for all
applicable taxes including, but not limited to, VAT, GST, sales tax, consumption tax and service tax. Customer will make all
payments free and clear of, and without reduction for, any withholding or other taxes; any such taxes imposed on payments by
Customer hereunder will be Customer’s sole responsibility. If Customer appoints a third party to place purchase orders and/or
make payments on Customer’s behalf, Customer shall be liable for payment under Orders placed by such third party in the event
of default.
1.3. All Products are delivered FCA factory (Incoterms 2010), freight prepaid and invoiced to Customer, except Software delivered
electronically, which shall be deemed delivered when made available to Customer for download. Mentor Graphics retains a
security interest in all Products delivered under this Agreement, to secure payment of the purchase price of such Products, and
Customer agrees to sign any documents that Mentor Graphics determines to be necessary or convenient for use in filing or
perfecting such security interest. Mentor Graphics’ delivery of Software by electronic means is subject to Customer’s provision
of both a primary and an alternate e-mail address.
2. GRANT OF LICENSE. The software installed, downloaded, or otherwise acquired by Customer under this Agreement, including any
updates, modifications, revisions, copies, documentation, setup files and design data (“Software”) are copyrighted, trade secret and
confidential information of Mentor Graphics or its licensors, who maintain exclusive title to all Software and retain all rights not
expressly granted by this Agreement. Except for Software that is embeddable (“Embedded Software”), which is licensed pursuant to
separate embedded software terms or an embedded software supplement, Mentor Graphics grants to Customer, subject to payment of
applicable license fees, a nontransferable, nonexclusive license to use Software solely: (a) in machine-readable, object-code form
(except as provided in Subsection 4.2); (b) for Customer’s internal business purposes; (c) for the term of the license; and (d) on the
computer hardware and at the site authorized by Mentor Graphics. A site is restricted to a one-half mile (800 meter) radius. Customer
may have Software temporarily used by an employee for telecommuting purposes from locations other than a Customer office, such as
the employee’s residence, an airport or hotel, provided that such employee’s primary place of employment is the site where the
Software is authorized for use. Mentor Graphics’ standard policies and programs, which vary depending on Software, license fees paid
or services purchased, apply to the following: (a) relocation of Software; (b) use of Software, which may be limited, for example, to
execution of a single session by a single user on the authorized hardware or for a restricted period of time (such limitations may be
technically implemented through the use of authorization codes or similar devices); and (c) support services provided, including
eligibility to receive telephone support, updates, modifications, and revisions. For the avoidance of doubt, if Customer provides any
feedback or requests any change or enhancement to Products, whether in the course of receiving support or consulting services,
evaluating Products, performing beta testing or otherwise, any inventions, product improvements, modifications or developments made
by Mentor Graphics (at Mentor Graphics’ sole discretion) will be the exclusive property of Mentor Graphics.
3. BETA CODE.
3.1. Portions or all of certain Software may contain code for experimental testing and evaluation (which may be either alpha or beta,
collectively “Beta Code”), which may not be used without Mentor Graphics’ explicit authorization. Upon Mentor Graphics’
authorization, Mentor Graphics grants to Customer a temporary, nontransferable, nonexclusive license for experimental use to
test and evaluate the Beta Code without charge for a limited period of time specified by Mentor Graphics. Mentor Graphics may
choose, at its sole discretion, not to release Beta Code commercially in any form.
3.2. If Mentor Graphics authorizes Customer to use the Beta Code, Customer agrees to evaluate and test the Beta Code under normal
conditions as directed by Mentor Graphics. Customer will contact Mentor Graphics periodically during Customer’s use of the
Beta Code to discuss any malfunctions or suggested improvements. Upon completion of Customer’s evaluation and testing,
Customer will send to Mentor Graphics a written evaluation of the Beta Code, including its strengths, weaknesses and
recommended improvements.
3.3. Customer agrees to maintain Beta Code in confidence and shall restrict access to the Beta Code, including the methods and
concepts utilized therein, solely to those employees and Customer location(s) authorized by Mentor Graphics to perform beta
testing. Customer agrees that any written evaluations and all inventions, product improvements, modifications or developments
that Mentor Graphics conceived or made during or subsequent to this Agreement, including those based partly or wholly on
Customer’s feedback, will be the exclusive property of Mentor Graphics. Mentor Graphics will have exclusive rights, title and
interest in all such property. The provisions of this Subsection 3.3 shall survive termination of this Agreement.
4. RESTRICTIONS ON USE.
4.1. Customer may copy Software only as reasonably necessary to support the authorized use. Each copy must include all notices
and legends embedded in Software and affixed to its medium and container as received from Mentor Graphics. All copies shall
remain the property of Mentor Graphics or its licensors. Except for Embedded Software that has been embedded in executable
code form in Customer’s product(s), Customer shall maintain a record of the number and primary location of all copies of
Software, including copies merged with other software, and shall make those records available to Mentor Graphics upon
request. Customer shall not make Products available in any form to any person other than Customer’s employees and on-site
contractors, excluding Mentor Graphics competitors, whose job performance requires access and who are under obligations of
confidentiality. Customer shall take appropriate action to protect the confidentiality of Products and ensure that any person
permitted access does not disclose or use Products except as permitted by this Agreement. Customer shall give Mentor Graphics
written notice of any unauthorized disclosure or use of the Products as soon as Customer becomes aware of such unauthorized
disclosure or use. Customer acknowledges that Software provided hereunder may contain source code which is proprietary and
its confidentiality is of the highest importance and value to Mentor Graphics. Customer acknowledges that Mentor Graphics
may be seriously harmed if such source code is disclosed in violation of this Agreement. Except as otherwise permitted for
purposes of interoperability as specified by applicable and mandatory local law, Customer shall not reverse-assemble,
disassemble, reverse-compile, or reverse-engineer any Product, or in any way derive any source code from Software that is not
provided to Customer in source code form. Log files, data files, rule files and script files generated by or for the Software
(collectively “Files”), including without limitation files containing Standard Verification Rule Format (“SVRF”) and Tcl
Verification Format (“TVF”) which are Mentor Graphics’ trade secret and proprietary syntaxes for expressing process rules,
constitute or include confidential information of Mentor Graphics. Customer may share Files with third parties, excluding
Mentor Graphics competitors, provided that the confidentiality of such Files is protected by written agreement at least as well as
Customer protects other information of a similar nature or importance, but in any case with at least reasonable care. Customer
may use Files containing SVRF or TVF only with Mentor Graphics products. Under no circumstances shall Customer use
Products or Files or allow their use for the purpose of developing, enhancing or marketing any product that is in any way
competitive with Products, or disclose to any third party the results of, or information pertaining to, any benchmark.
4.2. If any Software or portions thereof are provided in source code form, Customer will use the source code only to correct software
errors and enhance or modify the Software for the authorized use, or as permitted for Embedded Software under separate
embedded software terms or an embedded software supplement. Customer shall not disclose or permit disclosure of source
code, in whole or in part, including any of its methods or concepts, to anyone except Customer’s employees or on-site
contractors, excluding Mentor Graphics competitors, with a need to know. Customer shall not copy or compile source code in
any manner except to support this authorized use.
4.3. Customer agrees that it will not subject any Product to any open source software (“OSS”) license that conflicts with this
Agreement or that does not otherwise apply to such Product.
4.4. Customer may not assign this Agreement or the rights and duties under it, or relocate, sublicense, or otherwise transfer the
Products, whether by operation of law or otherwise (“Attempted Transfer”), without Mentor Graphics’ prior written consent and
payment of Mentor Graphics’ then-current applicable relocation and/or transfer fees. Any Attempted Transfer without Mentor
Graphics’ prior written consent shall be a material breach of this Agreement and may, at Mentor Graphics’ option, result in the
immediate termination of the Agreement and/or the licenses granted under this Agreement. The terms of this Agreement,
including without limitation the licensing and assignment provisions, shall be binding upon Customer’s permitted successors in
interest and assigns.
4.5. The provisions of this Section 4 shall survive the termination of this Agreement.
5. SUPPORT SERVICES. To the extent Customer purchases support services, Mentor Graphics will provide Customer with updates and
technical support for the Products, at the Customer site(s) for which support is purchased, in accordance with Mentor Graphics’ then
current End-User Support Terms located at http://supportnet.mentor.com/supportterms.
6. OPEN SOURCE SOFTWARE. Products may contain OSS or code distributed under a proprietary third party license agreement, to
which additional rights or obligations (“Third Party Terms”) may apply. Please see the applicable Product documentation (including
license files, header files, read-me files or source code) for details. In the event of conflict between the terms of this Agreement
(including any addenda) and the Third Party Terms, the Third Party Terms will control solely with respect to the OSS or third party
code. The provisions of this Section 6 shall survive the termination of this Agreement.
7. LIMITED WARRANTY.
7.1. Mentor Graphics warrants that during the warranty period its standard, generally supported Products, when properly installed,
will substantially conform to the functional specifications set forth in the applicable user manual. Mentor Graphics does not
warrant that Products will meet Customer’s requirements or that operation of Products will be uninterrupted or error free. The
warranty period is 90 days starting on the 15th day after delivery or upon installation, whichever first occurs. Customer must
notify Mentor Graphics in writing of any nonconformity within the warranty period. For the avoidance of doubt, this warranty
applies only to the initial shipment of Software under an Order and does not renew or reset, for example, with the delivery of (a)
Software updates or (b) authorization codes or alternate Software under a transaction involving Software re-mix. This warranty
shall not be valid if Products have been subject to misuse, unauthorized modification, improper installation or Customer is not in
compliance with this Agreement. MENTOR GRAPHICS’ ENTIRE LIABILITY AND CUSTOMER’S EXCLUSIVE
REMEDY SHALL BE, AT MENTOR GRAPHICS’ OPTION, EITHER (A) REFUND OF THE PRICE PAID UPON
RETURN OF THE PRODUCTS TO MENTOR GRAPHICS OR (B) MODIFICATION OR REPLACEMENT OF THE
PRODUCTS THAT DO NOT MEET THIS LIMITED WARRANTY. MENTOR GRAPHICS MAKES NO WARRANTIES
WITH RESPECT TO: (A) SERVICES; (B) PRODUCTS PROVIDED AT NO CHARGE; OR (C) BETA CODE; ALL OF
WHICH ARE PROVIDED “AS IS.”
7.2. THE WARRANTIES SET FORTH IN THIS SECTION 7 ARE EXCLUSIVE. NEITHER MENTOR GRAPHICS NOR ITS
LICENSORS MAKE ANY OTHER WARRANTIES EXPRESS, IMPLIED OR STATUTORY, WITH RESPECT TO
PRODUCTS PROVIDED UNDER THIS AGREEMENT. MENTOR GRAPHICS AND ITS LICENSORS SPECIFICALLY
DISCLAIM ALL IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NON-INFRINGEMENT OF INTELLECTUAL PROPERTY.
8. LIMITATION OF LIABILITY. TO THE EXTENT PERMITTED UNDER APPLICABLE LAW, IN NO EVENT SHALL
MENTOR GRAPHICS OR ITS LICENSORS BE LIABLE FOR INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES (INCLUDING LOST PROFITS OR SAVINGS) WHETHER BASED ON CONTRACT, TORT OR ANY OTHER
LEGAL THEORY, EVEN IF MENTOR GRAPHICS OR ITS LICENSORS HAVE BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES. IN NO EVENT SHALL MENTOR GRAPHICS’ OR ITS LICENSORS’ LIABILITY UNDER THIS
AGREEMENT EXCEED THE AMOUNT RECEIVED FROM CUSTOMER FOR THE HARDWARE, SOFTWARE LICENSE OR
SERVICE GIVING RISE TO THE CLAIM. IN THE CASE WHERE NO AMOUNT WAS PAID, MENTOR GRAPHICS AND ITS
LICENSORS SHALL HAVE NO LIABILITY FOR ANY DAMAGES WHATSOEVER. THE PROVISIONS OF THIS SECTION 8
SHALL SURVIVE THE TERMINATION OF THIS AGREEMENT.
9. THIRD PARTY CLAIMS.
9.1. Customer acknowledges that Mentor Graphics has no control over the testing of Customer’s products, or the specific
applications and use of Products. Mentor Graphics and its licensors shall not be liable for any claim or demand made against
Customer by any third party, except to the extent such claim is covered under Section 10.
9.2. In the event that a third party makes a claim against Mentor Graphics arising out of the use of Customer’s products, Mentor
Graphics will give Customer prompt notice of such claim. At Customer’s option and expense, Customer may take sole control
of the defense and any settlement of such claim. Customer WILL reimburse and hold harmless Mentor Graphics for any
LIABILITY, damages, settlement amounts, costs and expenses, including reasonable attorney’s fees, incurred by or awarded
against Mentor Graphics or its licensors in connection with such claims.
9.3. The provisions of this Section 9 shall survive any expiration or termination of this Agreement.
10. INFRINGEMENT.
10.1. Mentor Graphics will defend or settle, at its option and expense, any action brought against Customer in the United States,
Canada, Japan, or member state of the European Union which alleges that any standard, generally supported Product acquired
by Customer hereunder infringes a patent or copyright or misappropriates a trade secret in such jurisdiction. Mentor Graphics
will pay costs and damages finally awarded against Customer that are attributable to such action. Customer understands and
agrees that as conditions to Mentor Graphics’ obligations under this section Customer must: (a) notify Mentor Graphics
promptly in writing of the action; (b) provide Mentor Graphics all reasonable information and assistance to settle or defend the
action; and (c) grant Mentor Graphics sole authority and control of the defense or settlement of the action.
10.2. If a claim is made under Subsection 10.1 Mentor Graphics may, at its option and expense: (a) replace or modify the Product so
that it becomes noninfringing; (b) procure for Customer the right to continue using the Product; or (c) require the return of the
Product and refund to Customer any purchase price or license fee paid, less a reasonable allowance for use.
10.3. Mentor Graphics has no liability to Customer if the action is based upon: (a) the combination of Software or hardware with any
product not furnished by Mentor Graphics; (b) the modification of the Product other than by Mentor Graphics; (c) the use of
other than a current unaltered release of Software; (d) the use of the Product as part of an infringing process; (e) a product that
Customer makes, uses, or sells; (f) any Beta Code or Product provided at no charge; (g) any software provided by Mentor
Graphics’ licensors who do not provide such indemnification to Mentor Graphics’ customers; (h) OSS, except to the extent that
the infringement is directly caused by Mentor Graphics’ modifications to such OSS; or (i) infringement by Customer that is
deemed willful. In the case of (i), Customer shall reimburse Mentor Graphics for its reasonable attorney fees and other costs
related to the action.
10.4. THIS SECTION 10 IS SUBJECT TO SECTION 8 ABOVE AND STATES THE ENTIRE LIABILITY OF MENTOR
GRAPHICS AND ITS LICENSORS, AND CUSTOMER’S SOLE AND EXCLUSIVE REMEDY, FOR DEFENSE,
SETTLEMENT AND DAMAGES, WITH RESPECT TO ANY ALLEGED PATENT OR COPYRIGHT INFRINGEMENT
OR TRADE SECRET MISAPPROPRIATION BY ANY PRODUCT PROVIDED UNDER THIS AGREEMENT.
11. TERMINATION AND EFFECT OF TERMINATION.
11.1. If a Software license was provided for limited term use, such license will automatically terminate at the end of the authorized
term. Mentor Graphics may terminate this Agreement and/or any license granted under this Agreement immediately upon
written notice if Customer: (a) exceeds the scope of the license or otherwise fails to comply with the licensing or confidentiality
provisions of this Agreement, or (b) becomes insolvent, files a bankruptcy petition, institutes proceedings for liquidation or
winding up or enters into an agreement to assign its assets for the benefit of creditors. For any other material breach of any
provision of this Agreement, Mentor Graphics may terminate this Agreement and/or any license granted under this Agreement
upon 30 days written notice if Customer fails to cure the breach within the 30 day notice period. Termination of this Agreement
or any license granted hereunder will not affect Customer’s obligation to pay for Products shipped or licenses granted prior to
the termination, which amounts shall be payable immediately upon the date of termination.
11.2. Upon termination of this Agreement, the rights and obligations of the parties shall cease except as expressly set forth in this
Agreement. Upon termination of this Agreement and/or any license granted under this Agreement, Customer shall ensure that
all use of the affected Products ceases, and shall return hardware and either return to Mentor Graphics or destroy Software in
Customer’s possession, including all copies and documentation, and certify in writing to Mentor Graphics within ten business
days of the termination date that Customer no longer possesses any of the affected Products or copies of Software in any form.
12. EXPORT. The Products provided hereunder are subject to regulation by local laws and European Union (“E.U.”) and United States
(“U.S.”) government agencies, which prohibit export, re-export or diversion of certain products, information about the products, and
direct or indirect products thereof, to certain countries and certain persons. Customer agrees that it will not export or re-export Products
in any manner without first obtaining all necessary approval from appropriate local, E.U. and U.S. government agencies. If Customer
wishes to disclose any information to Mentor Graphics that is subject to any E.U., U.S. or other applicable export restrictions, including
without limitation the U.S. International Traffic in Arms Regulations (ITAR) or special controls under the Export Administration
Regulations (EAR), Customer will notify Mentor Graphics personnel, in advance of each instance of disclosure, that such information
is subject to such export restrictions.
13. U.S. GOVERNMENT LICENSE RIGHTS. Software was developed entirely at private expense. The parties agree that all Software is
commercial computer software within the meaning of the applicable acquisition regulations. Accordingly, pursuant to U.S. FAR 48
CFR 12.212 and DFAR 48 CFR 227.7202, use, duplication and disclosure of the Software by or for the U.S. government or a U.S.
government subcontractor is subject solely to the terms and conditions set forth in this Agreement, which shall supersede any
conflicting terms or conditions in any government order document, except for provisions which are contrary to applicable mandatory
federal laws.
14. THIRD PARTY BENEFICIARY. Mentor Graphics Corporation, Mentor Graphics (Ireland) Limited, Microsoft Corporation and
other licensors may be third party beneficiaries of this Agreement with the right to enforce the obligations set forth herein.
15. REVIEW OF LICENSE USAGE. Customer will monitor the access to and use of Software. With prior written notice and during
Customer’s normal business hours, Mentor Graphics may engage an internationally recognized accounting firm to review Customer’s
software monitoring system and records deemed relevant by the internationally recognized accounting firm to confirm Customer’s
compliance with the terms of this Agreement or U.S. or other local export laws. Such review may include FlexNet (or successor
product) report log files that Customer shall capture and provide at Mentor Graphics’ request. Customer shall make records available in
electronic format and shall fully cooperate with data gathering to support the license review. Mentor Graphics shall bear the expense of
any such review unless a material non-compliance is revealed. Mentor Graphics shall treat as confidential information all information
gained as a result of any request or review and shall only use or disclose such information as required by law or to enforce its rights
under this Agreement. The provisions of this Section 15 shall survive the termination of this Agreement.
16. CONTROLLING LAW, JURISDICTION AND DISPUTE RESOLUTION. The owners of certain Mentor Graphics intellectual
property licensed under this Agreement are located in Ireland and the U.S. To promote consistency around the world, disputes shall be
resolved as follows: excluding conflict of laws rules, this Agreement shall be governed by and construed under the laws of the State of
Oregon, U.S., if Customer is located in North or South America, and the laws of Ireland if Customer is located outside of North or
South America or Japan, and the laws of Japan if Customer is located in Japan. All disputes arising out of or in relation to this
Agreement shall be submitted to the exclusive jurisdiction of the courts of Portland, Oregon when the laws of Oregon apply, or Dublin,
Ireland when the laws of Ireland apply, or the Tokyo District Court when the laws of Japan apply. Notwithstanding the foregoing, all
disputes in Asia (excluding Japan) arising out of or in relation to this Agreement shall be resolved by arbitration in Singapore before a
single arbitrator to be appointed by the chairman of the Singapore International Arbitration Centre (“SIAC”) to be conducted in the
English language, in accordance with the Arbitration Rules of the SIAC in effect at the time of the dispute, which rules are deemed to be
incorporated by reference in this section. Nothing in this section shall restrict Mentor Graphics’ right to bring an action (including for
example a motion for injunctive relief) against Customer in the jurisdiction where Customer’s place of business is located. The United
Nations Convention on Contracts for the International Sale of Goods does not apply to this Agreement.
17. SEVERABILITY. If any provision of this Agreement is held by a court of competent jurisdiction to be void, invalid, unenforceable or
illegal, such provision shall be severed from this Agreement and the remaining provisions will remain in full force and effect.
18. MISCELLANEOUS. This Agreement contains the parties’ entire understanding relating to its subject matter and supersedes all prior
or contemporaneous agreements. Any translation of this Agreement is provided to comply with local legal requirements only. In the
event of a dispute between the English and any non-English versions, the English version of this Agreement shall govern to the extent
not prohibited by local law in the applicable jurisdiction. This Agreement may only be modified in writing, signed by an authorized
representative of each party. Waiver of terms or excuse of breach must be in writing and shall not constitute subsequent consent, waiver
or excuse.
Rev. 151102, Part No. 265968

Capital Integrator User

Caricato da

Informazioni sul documento

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Capital Integrator User

Caricato da

Copyright:

Formati disponibili

Capital® Integrator™ User Guide

Incorporating Capital® AutoView Assist for Integrator™

© 2016 Mentor Graphics Corporation

Mentor Graphics Corporation

Send Feedback on Documentation: supportnet.mentor.com/doc_feedback_form

Capital® Integrator™ User Guide, 2015.1 3

4 Capital® Integrator™ User Guide, 2015.1

Specifying the Highlight Color of Selected Objects in a Diagram . . . . . . . . . . . . . . . . . . . . 87

Capital® Integrator™ User Guide, 2015.1 5

Converting Through Nodes from Structure Nodes to Reference Nodes . . . . . . . . . . . . . . 128

6 Capital® Integrator™ User Guide, 2015.1

Placement of Normal Devices in Slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

Capital® Integrator™ User Guide, 2015.1 7

Mapping a Signal to an Interface Connector Cavity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

8 Capital® Integrator™ User Guide, 2015.1

Adding a Property to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 282

Capital® Integrator™ User Guide, 2015.1 9

Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

10 Capital® Integrator™ User Guide, 2015.1

Capital® Integrator™ User Guide, 2015.1 11

12 Capital® Integrator™ User Guide, 2015.1

Copying Wiring Across the Levels of a Harness. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505

Capital® Integrator™ User Guide, 2015.1 13

14 Capital® Integrator™ User Guide, 2015.1

Capital® Integrator™ User Guide, 2015.1 15

Harness Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 747

16 Capital® Integrator™ User Guide, 2015.1

Edit Ground Signals Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813

Capital® Integrator™ User Guide, 2015.1 17

Deleting an Option from the Product Plan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 856

18 Capital® Integrator™ User Guide, 2015.1

Edit Models associated with Variant Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919

Capital® Integrator™ User Guide, 2015.1 19

20 Capital® Integrator™ User Guide, 2015.1

Figure 1-1. Platform Level View of Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Capital® Integrator™ User Guide, 2015.1 21

22 Capital® Integrator™ User Guide, 2015.1

Figure 13-23. Inclusion of Option in Harness Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

Capital® Integrator™ User Guide, 2015.1 23

Figure 18-22. Unconnected Signal State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513

24 Capital® Integrator™ User Guide, 2015.1

Capital® Integrator™ User Guide, 2015.1 25

Figure 22-63. Slot-internal Splice Connected to Cavities . . . . . . . . . . . . . . . . . . . . . . . . . . . 613

26 Capital® Integrator™ User Guide, 2015.1

Table 2-1. Release Level Mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Capital® Integrator™ User Guide, 2015.1 27

Table 24-19. Edit Skeleton Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 705

28 Capital® Integrator™ User Guide, 2015.1

Table 24-63. Diagram Partitioning Dialog Box Contents . . . . . . . . . . . . . . . . . . . . . . . . . . 800

Capital® Integrator™ User Guide, 2015.1 29

30 Capital® Integrator™ User Guide, 2015.1

Capital® Integrator™ User Guide, 2015.1 31

Overview of Capital Integrator

Figure 1-1. Platform Level View of Design

32 Capital® Integrator™ User Guide, 2015.1

Composite wiring synthesis automates the process of determining optimum harness

Capital® Integrator™ User Guide, 2015.1 33

Accessing Capital Integrator

34 Capital® Integrator™ User Guide, 2015.1

User Access Rights in Capital Integrator

High-Level Wiring Synthesis Process in Capital Integrator

Capital® Integrator™ User Guide, 2015.1 35

Styling Objects in Diagrams

Logical Design Association