Capital Design User PDF
Capital Design User PDF
Functions
Incorporating Capital® Insight™ User Guide
Release 2015.1
February 2016
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.
Chapter 1
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Refreshing External Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Viewing the Details of Installed Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Reloading Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Design Inspectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Custom Action Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Object Attribute Descriptions for Use in Extensibility Plugins . . . . . . . . . . . . . . . . . . . . . 27
Usage Example - Loading an Extensibility Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Specifying the Memory Allocation of Capital Applications . . . . . . . . . . . . . . . . . . . . . . . . . 30
Encrypted Client-Manager Communication Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Enabling Encrypted Client-Manager Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Creating Additional Icons in the Capital Launcher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Using the Report Builder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
User Interface Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
Diagram Language Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Language Dictionary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Active Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Translatable Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Notes About Specific Dialogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Chinese and Japanese Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Editing the Language Dictionary CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Saving a Language Dictionary CSV File with UTF-8 or Non-Ascii Characters . . . . . . . . 45
Importing a Language Dictionary CSV File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Exporting a Language Dictionary CSV File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Refreshing Language Dictionary Data in a Design Application . . . . . . . . . . . . . . . . . . . . 47
Adding a Translation of an Existing Translatable Term for the Currently Active Language 48
Adding a Translation of a New Translatable Term for the Currently Active Language . . 49
Converting Free Text Strings into Translations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Running Capital Tasks in the Background (Flexible Execution Model). . . . . . . . . . . . . . . . 51
Server Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Configuring a Capital Integration Server as the Task Execution Manager . . . . . . . . . . . . 54
Configuring a Capital Integration Server as a Task Execution Slave. . . . . . . . . . . . . . . . . 54
Configuring a Client to Connect to the Task Execution Manager when Submitting a Task 55
Running Harness Processing in Capital HarnessXC (or Capital ModularXC) in the Background
55
Tasks tab in Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Running SBOM Generation and Costing in Capital Harness MPM and Capital Harness TVM
in the Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
Running FMEA Scenarios in Capital Analysis in the Background . . . . . . . . . . . . . . . . . . 59
Creating Audit Reports When Capital Analysis Operations are Run in the Background . . . 60
Searching for an Action on the Ribbon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Launch Pane. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Chapter 2
Projects and Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Projects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Project Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Opening a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Deleting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Importing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Exporting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Closing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Project Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Capital Compressed Format for Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Exporting a Project in Capital Compressed Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Importing a Project in Capital Compressed Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Designs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Importing Designs into a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Migrating a Design from Capital Harness Classic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Editing the Information for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Adding a Property to a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Editing a Property for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Deleting a Property for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Comparing Objects and Their Properties in Design Revisions or Build Lists . . . . . . . . . . 81
Running Design Rule Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Running Design Rule Checks in Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Design Rule Checks Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Design Rule Check Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Releasing Designs with Enforced Design Rule Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Build List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Options and Option Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Define Option Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Creating an Option Folder at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Creating an Option at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Defining Inclusive and Exclusive Relationships for an Option . . . . . . . . . . . . . . . . . . . . . 119
Creating an Option Combination at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Adding a Valid Selection to an Option Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Deleting a Valid Selection from an Option Combination. . . . . . . . . . . . . . . . . . . . . . . . . . 121
Deleting an Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Engineering Change Orders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
ECO Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Working with an ECO Created in Capital . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Creating an Engineering Change Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Deleting an Engineering Change Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Viewing Engineering Change Orders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Capture and Apply a Change Within an ECO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Chapter 3
Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
Common Edit Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Undoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Redoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Repeating an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Cutting and Pasting an Object in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Copying and Pasting an Object in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Deleting an Object in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Moving Objects from a Diagram to Another Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Selecting All Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Finding and Selecting Objects by Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Finding and Selecting Objects by Attribute or Property. . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Specifying the Highlight Color of Selected Objects in a Diagram. . . . . . . . . . . . . . . . . . . 161
Using the Stroke Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Using Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Window Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Arranging Diagram Windows for Viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Using Tearable Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Zooming In and Out of Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Panning Across a Diagram Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Chapter 4
Graphics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Borders. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Adding a Border to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Replacing a Border on a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Removing a Border from a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Graphic Drawing Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Drawing a Line in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Chapter 5
Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Grouping Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Creating a Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Moving a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Ungrouping Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Aligning Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Distributing Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Flipping Objects in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Rotating Objects in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Rotating Objects Around a Specified Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Defining Rotation Increments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Free Rotating Text Decorations, Comment and RED Symbols or Graphical Objects . . . . 204
Example of Applying Styling on Rotated or Flipped Objects . . . . . . . . . . . . . . . . . . . . . . 205
Pivoting Text About its Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Setting Snap To Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Setting Grid Defaults for a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Manual Table Splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Using Japanese Text on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Chapter 6
Rules and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211
Overview of Rules and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Object Rule Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Editable Elements in Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Defining Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Assigning a Rule or Constraint to an Object or Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Usage Example - Using a Null Value in a Constraint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Chapter 7
Modifying Objects. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Editing the Properties of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Editing Multiple Object Simultaneously . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Editing the Attributes and Properties of Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225
Editing an Object's General Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Specifying the Name Property of an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Editing the Display-details of the Object's Short Description . . . . . . . . . . . . . . . . . . . . . . . . 232
Adding a Property to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234
Editing Multiple Objects Simultaneously . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238
Deleting an Existing Property from an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Editing a Bundle's Length in Capital Integrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Assigning a New Library Part to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239
Updating an Object's Library Part . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Unassigning a Library Part from an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242
Viewing the Library Part Details for an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Defining Specification Attributes for a Conductor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Specifying the Slot Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243
Assigning/Editing an Object's Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244
Assigning Module Codes (Capital Logic only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Associating a Block with a Design (Capital Logic only) . . . . . . . . . . . . . . . . . . . . . . . . . . . 246
Specifying a Part Number for a Harness Level in Capital Integrator . . . . . . . . . . . . . . . . . . 246
Editing the Harness Levels on which a Wire Exists . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
Editing the Offset of Bundle Region Nodes from Bundle Ends . . . . . . . . . . . . . . . . . . . . . . 248
Foreground, Background and Manual Color Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249
Specifying Option-Specific Values for Net Attributes and Properties . . . . . . . . . . . . . . . . . 249
Object Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251
Symbol Attributes in Capital Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
Editing an Object's Graphical Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
Changing an Object's Primary or Secondary Graphical Color Property . . . . . . . . . . . . . . 253
Changing an Object's Graphical Thickness Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Changing an Object's Graphical Line Style Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
Changing the Fill Color Attribute for an Object. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Changing an Object's Graphical Fill Pattern Property . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Changing the Line End Style of a Conductor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256
Physical Line Thickness . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258
Setting the Physical Line Thickness for Graphics in Diagrams . . . . . . . . . . . . . . . . . . . . . 258
Chapter 8
Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289
Print to a Printer or Plotter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Printing a Single Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290
Printing Selected Diagrams in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291
Printing All Diagrams in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292
Printing All Diagrams in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293
Printing Selected Print Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294
Print Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Adding a Print Region to a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296
Resizing a Print Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297
Moving a Print Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Editing a Print Region. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298
Deleting a Print Region. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299
Print to a File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Printing To File - All Diagrams in a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Printing To File - All Diagrams in a Design. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Printing To File - Single Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Printing To File - Selected Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Printing To File - Print Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
SVG Page Settings Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Line Thickness Scale Factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306
Chapter 9
Trace and Navigate, Compare and Propagate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315
Trace and Navigate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Tagging Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 316
Working Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Adding Designs to a Working Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317
Tracing an Object across Designs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 318
Trace Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319
Trace Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321
Configuring Tagging Tasks to Run in the Background . . . . . . . . . . . . . . . . . . . . . . . . . . . 323
Configuring Stale Tag Cleanup Tasks to Run in the Background . . . . . . . . . . . . . . . . . . . 326
Compare and Propagate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
Viewing the To Do List for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330
To Do List Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331
Troubleshooting Tagging Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333
ANSTagGenerationTask or ANSStaleTagCleanupTask Fails . . . . . . . . . . . . . . . . . . . . . . 333
ANSTagGenerationTask or ANSStaleTagCleanupTask Runs for a Long Time . . . . . . . . 333
CapitalRunner Log File Indicates Out-of-Memory Issues . . . . . . . . . . . . . . . . . . . . . . . . . 334
Tagging Tasks Have Not Started After Data Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . 334
First Tagging Task Takes a Long Time After Data Migration. . . . . . . . . . . . . . . . . . . . . . 335
Chapter 10
Dialog and Field Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337
Project-related Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Edit Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Edit Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Project Folders Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Import Designs to Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Import Designs to Project Wizard Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Select Project Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
New Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Open Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Choose Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Project Preferences Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Copy Design Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Create New Design Revision Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Editing Action Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Applicable Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Compare Designs Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443
Design Revision - Build List Selection Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446
Design Rule Checks Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447
Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449
Chapter 11
Bridges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Available Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 579
Chapter 12
Capital Insight. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581
Enabling Capital Insight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582
Architectural Study Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 583
This user guide contains information on the functions that are common between the design
applications. These functions include the handling of projects and designs, the layout of design
objects and the ability to add comment graphics to a diagram.
For complete information on each of the design applications, refer to the following user guides:
Refreshes Functional Module Code data when it has been modified in other Capital
applications.
o Production Module Codes
Refreshes Production Module Code data when it has been modified in other Capital
applications.
o Language Dictionary
Refreshes any Diagram Language Translation changes made in other Capital
applications.
Extensibility Plugins
The following topics explain how to view the details of any extensibility plugins that you have
installed and how to load new plugins or reload modified plugins.
Compiled plugins - written in Java or JavaScript - provide custom actions and are placed into
the \plugins sub-directory of the Capital installation location. These plugins are loaded when an
application is launched, and can be inspected from within an application, see “Viewing the
Details of Installed Extensibility Plugins” on page 24.
Note
For more information about developing and using extensibility plugins, see the
PluginDevelopment.pdf file that is located in the doc\plugin folder of your Capital
installation.
The function of a custom action is entirely dependent upon the plugin design; refer to the user
documentation supplied with the plugin for information on using the action.
Design Inspectors
Custom Action Plugins
Usage Example - Loading an Extensibility Plugin
Design Inspectors
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 functions can be accessed.
Once the plugin has been placed in the correct location, check it has been loaded and refresh the
installed plugins list if necessary. Open the required Capital application, press Space Bar and
enter Plugins. If the custom plugin is not displayed in the Available Plugins list, click the
Reload All button to refresh the list. Once you have verified that the plugin is present, close the
dialog.
Related Topics
Viewing the Details of Installed Extensibility Plugins
Reloading Extensibility Plugins
Custom Action Plugins
Usage Example - Loading an Extensibility Plugin
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.
• On the ribbon. Press Space Bar and enter Custom. The name of the action - as coded in
the plugin - is displayed as a selectable option.
• In the context-menu, accessed by right-clicking on an object in the design browser. Any
installed custom actions available are offered beneath a Custom > menu option.
• In the context-menu, accessed by right-clicking on an object on the diagram. Any
installed custom actions available are offered beneath a Custom > menu option.
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.
Related Topics
Viewing the Details of Installed Extensibility Plugins
Reloading Extensibility Plugins
Design Inspectors
Usage Example - Loading an Extensibility Plugin
The normal scenario for using this plugin is when CWS has already run for all signals, some
signals have been edited and you want to run CWS again only for those edited signals.
Prerequisites
• The plugin must have been developed and compiled. For more information about
developing extensibility plugins, see the PluginDevelopment.pdf file that is located in
the doc\plugin folder of your Capital installation. For the purposes of this example, we
are using a pre-developed plugin.
• For this example, you must have a SupportNet user account in order to access the
compiled plugin.
• This example uses a Quick Start - Automotive Generative project. If you want to re-
create the steps in Capital Integrator, import the Quick Start - Automotive
Generative.xml project file from here.
• If you want to try out the plugin used in this example, CWS should already have been
run for all signals in the Vehicle Topology design of the project. This is so that harness
levels have been generated.
Procedure
1. Obtain the compiled plugin and add it to your Capital installation as below:
a. Download the ProtectUnselectedSignals.zip file that contains the plugin from:
http://communities.mentor.com/mgcx/docs/DOC-1415.
Note
The zip file also contains a ProtectUnselectedSignals.java file, which is an
uncompiled version of the ProtectUnselectedSignals.jar file. You do not need
to do anything with this file.
Note
The plugin might not be listed if Capital Integrator was already running when
you added it to your installation. In this case, click Reload All on the Plugins
dialog. This will load the plugin.
Note
The steps from this point onwards depend on the plugin that you are using. In this
example, you will apply the custom constraint from the plugin to a topological plane
and run Composite Wiring Synthesis (CWS) for selected signals.
c. In the Topological Plane Browser Window, right-click the Vehicle Topology plane
and select Properties.
The Plane: Vehicle Topology dialog is displayed where you edit properties and
attributes for it.
d. On the Rules tab, click Add Constraint; the Constraint Selection dialog is
displayed.
e. Select the Protect Wiring by Attribute/Property constraint and click OK; the
standard template for the constraint is added to the Rules tab.
f. Click the icon; a drop-down list is displayed from which you select
ProtectUnselectedSignals.
The memory allocation is recorded in the application log file, where “xxx” is the set memory
allocation:
“Allocated Maximum Heap Size = xxxMb”
Authentication
This is the process by which the Capital client and Capital Manager establish to each other that
they are genuine and not an impersonator. This is done using public key certificates which hold
information about its owner's identity and a public key. A server can give out copies of its
public key certificate to all of the clients that want to communicate with it. When the server
starts to communicate with the client, the client uses the server's certificate to confirm that it is
genuine. This also occurs in the other direction with the server authenticating the client with the
client's certificate.
Keystore
The certificates are held in the keystore. Access to the keystore is controlled by a password. By
default your installation comes with two sample keystore files: manager_ks and client_ks (in the
config directory). There are also generated certificates: manager_cert and client_cert. These
certificates are embedded into the keystores for mutual authentication.
SSL
SSL (secure socket layer) is the secure communications protocol that is used for encrypted
communications. This needs to be turned on for both the clients and Capital Manager. Capital
uses a CORBA ORB for communication between clients and Capital Manager and therefore the
configuration for SSL is done in the ORB properties files.
Ciphers
It is possible to configure which ciphers are used for encrypting the communication. Strong
ciphers can make the encryption extremely difficult to break but require more CPU time for the
encrypt/decrypt operations.
To enable and configure encrypted communication you must edit the manager_orb.properties
file in the Capital Manager installation and a client_orb.properties file in each client
installation.
Procedure
1. Enabling encryption is achieved by turning on SSL on both the Capital Manager and the
clients. Do the following:
• On the Capital Manager installation, navigate to the config directory and open the
manager_orb.properties file for editing.
• Find the jacorb.security.support_ssl property and set its value to ON. This enables
the use of secure sockets for communication.
• In the Capital client installations, navigate to the config directory and open the
client_orb.properties file for editing.
• Again find the jacorb.security.support_ssl property and set its value to ON.
2. If you want to replace the keystore provided in your installation with an alternative, then
you will need to make the following changes to the client and manager orb.properties
file:
3. Find the jacorb.security.keystore property and specify the location of the keystore.
Specify the complete path of the keystore file.
4. Find the jacorb.security.keystore_password property and specify the keystore password
used while regenerating the keystore. The existing value corresponds to the sample
keystore.
5. Find the jacorb.security.default_user property and specify the default user for the
regenerated keystore. This avoids prompting for the user whenever you use the keystore.
The existing value corresponds to the sample keystore.
6. Find the jacorb.security.default_password property and specify the default user
password for the regenerated keystore. This avoids prompting for the password
whenever you use the keystore. The existing value corresponds to the sample keystore.
7. If you want to control the ciphers being used in the encryption, find the
jacorb.security.ssl.server.cipher_suites property and specify the set of all cipher suites
which need to be supported. By default, all the supported types are included. Specify
only the ones you really want to support.
Note
Specify at least one of the cipher suites matching the algorithm used for generating
the keystore file. For example if RSA is used for the key generation algorithm, then
at least one RSA supported cipher suite must be present in the list.
• Starting an internet browser with the Capital Enterprise Reporter start page displayed
</launcherentry>
</launcher>
• Custom icon for opening Capital Enterprise Reporter in Firefox Browser
<launcher>
<launcherentry name="Capital Enterprise Reporter"
exec="C:\ProgramFiles(x86)\MozillaFirefox\firefox.exehttp://localhost:49912/reporter/
Login.jsp"
section="Custom" icon="">
<launcherentrydescription text="Enterprise wide Reporting" />
</launcherentry>
</launcher>
• Custom icon for starting Capital Project with Login dialog even when Single sign-on is
active
<launcher>
<launcherentry name="Capital Project with Login"
exec="C:\MentorGraphics\Capital\bin\CapitalProject.exe -login"
section="Manager" icon="">
<launcherentrydescription text="Manage Designs and Projects" />
</launcherentry>
</launcher>
• Custom icon for starting Capital Logic with parameter -Xmx1400m for bigger heap
space
<launcher>
<launcherentry name="Capital Logic 1400m"
exec="C:\MentorGraphics\Capital\bin\CapitalLogic.exe -Xmx1400m"
section="Design" icon="">
<launcherentrydescription text="CLogic with more Memory allocation" />
</launcherentry>
</launcher>
• Custom icon for starting Capital Logic with parameter -Xmx1400m (to increase the
default memory allocation)
<launcher>
<launcherentry name="Capital Logic 1400m"
exec="C:\MentorGraphics\Capital\bin\CapitalLogic.exe -Xmx1400m"
section="Design" icon="">
<launcherentrydescription text="CLogic with more Memory allocation" />
</launcherentry>
</launcher>
Reports
In Capital Logic, Capital HarnessXC and Capital HarnessMPM, you can run reports on designs.
If you are using Capital Logic, see the Capital Logic User Guide for more information.
If you are using Capital HarnessXC or Capital ModularXC, see the Capital HarnessXC User
Guide for more information.
If you are using Capital Harness MPM or Capital Harness TVM, see the Capital Harness MPM
User Guide for more information.
If you are using Capital Publisher, see the Capital Publisher User Guide for more information.
If you are using Capital Systems Capture, see the Function Design in Capital Systems Capture
User Guide for more information.
If you are creating platform designs in Capital Systems Architect, see the Platform Design in
Capital Systems User Guide for more information.
The following topic provides details about how you can configure reports:
Prerequisites
A design must be open in the browser.
Procedure
1. Press Space Bar and enter Build.
2. Either:
• Click the icon to create a new report
• Click the icon to load an existing report (as a plugin) and edit as required.
3. Select the Tool or Tools you wish to report on by clicking on the relevant icon.
• Select for Capital Logic
Note
You can report on one, or a combination of tools. The objects that can be
reported on changes according to the tool(s) selected and are displayed for
selection in the Include: section at the bottom of the window. Click the icons to
include in, or remove from the report.
Only applicable object types are available for each of the design types. Combining
design types narrows the scope of possible objects for selection, as only common
objects are shown. as available.
4. Choose the type of report, or reports you wish to generate. Options are:
• Select to generate output as an embedded report
5. Enter a unique name, version and description for your report by typing in the free text
entry boxes.
6. Click the icon to add columns to the report. Once there is at least one column in the
report click the icon to specify the contents of the column.
Tip
Double click the heading of the column to change or edit its name. Columns may be
reordered by dragging or dropping into the required configuration.
Clicking the icon allows you to delete the selected column.
7. After clicking the icon the Edit Contents of Column dialog opens:
8. Drag and drop available elements, including attributes, queries and plugin queries, to
construct the desired content of the report. You can also insert your own text by typing
in between the elements. A preview of how the elements will appear in the report
column is shown at the bottom of the dialog.
Where there are a number of different options available under an element a drop down
list is accessible by clicking the down arrow.
When selecting the Attribute element a list of specific attributes are displayed for
conductors, devices, connectors and splices, along with common attributes for all
objects. In addition you can add a "User specified" attribute where you can include
attributes not listed in the above sections.
Plugins not created by Capital cannot be opened, or used as the basis for report content.
The From and To elements are available if only Nets or Wires are selected. Selecting
any other object will remove the From and To fields.
If you add a calculation element then its drop down list allows access to a further list of
options enabling you to construct your required calculation. You can also format the
calculation, including specifying the number of decimal places shown by clicking the
Format option from the calculation dropdown menu.
Tip
Reports are always sorted by the first column, unless you include an Index element,
in which case this is used for sorting purposes.
9. Click the icon compile and save your report, ensuring you have specified a name and
description, if required, in the Plugin Name and Plugin Description fields.
Reports automatically become available in the Capital tool suite, negating any need to
restart the Capital Enterprise Reporter server.
Results
The report is available as a plugin and, depending on the choice of output, can be viewed as an
embedded report in the tool, as a plugin in table in Styling, via the design inspector or in Capital
Enterprise Reporter.
Related Topics
Report Builder Dialog Box
Language Dictionary
In order to start using diagram language translation, you must edit and import a comma
separated variable (CSV) file, that acts as a language dictionary of translatable terms. This is the
starting point for the language database.
See “Editing the Language Dictionary CSV File” on page 43 and “Importing a Language
Dictionary CSV File” on page 45.
Any updates made in the applications will only be included in the database, the CSV file is not
updated automatically but you can export an updated CSV file. See “Exporting a Language
Dictionary CSV File” on page 47.
The CSV file lists the available translation languages and any translations that already exist for
specific translated words or terms. Each translation entry has a quick code and a list of
translations for the available languages. The quick code links each translatable string within the
design tools, or library data, with the translation entry in the language dictionary.
An example CSV file, dictionary.csv, is included in the starter data supplied with the software
see capital_home\data\xml\Language Dictionary. You can take a copy of that and edit it or
create a new CSV file.
Active Language
Within Capital Project or a design application, you control which translation language is active
by selecting a language code in the box that is at the bottom right of the application window. By
default, the is EN. In Capital Library, you control it by pressing Space Bar and entering Switch
Language.
The default EN language is used:
Translatable Terms
When you enter property, attribute or comment text into a dialog, predictive text displays a list
of translated terms in the active language, thereby allowing you to select an existing translated
term. You can enter free, non-translated text as normal, including text that exists within the
language database.
Wherever a translatable term is used, that translation is displayed against a gray background
( ). When the active language is changed, the displayed text will change to the one for
the now active language.
If a translatable term was entered for a previously active language and the currently active
language does not have a translation for that term, the quick code will be displayed.
If a translatable term does not have a translation for the active language, you can enter one using
the context menu for that highlighted term. See “Adding a Translation of an Existing
Translatable Term for the Currently Active Language” on page 48).
You can enter a new translatable term and add it to the dictionary. See “Adding a Translation of
a New Translatable Term for the Currently Active Language” on page 49).
• where a translatable term has been used but no translation exists for the active language
so the quick code is displayed.
• where a translatable term has been entered as free text and has no link to the language
database.
See “Running Design Rule Checks” on page 82.
Font settings for comment text on diagrams are taken from the Project Preferences for each
application (Applicaton Name > Property > Text). By default, they use the Lucida Sans font
which does not support East Asian characters. To use East Asian characters, you must change
the font in these preferences. See “Project Preferences” on page 70.
Related Topics
Editing the Language Dictionary CSV File
Saving a Language Dictionary CSV File with UTF-8 or Non-Ascii Characters
Importing a Language Dictionary CSV File
Exporting a Language Dictionary CSV File
Refreshing Language Dictionary Data in a Design Application
Adding a Translation of an Existing Translatable Term for the Currently Active Language
Adding a Translation of a New Translatable Term for the Currently Active Language
Converting Free Text Strings into Translations
Note
Editing the file in Microsoft Office Excel removes UTF-8 encoding. See “Saving a
Language Dictionary CSV File with UTF-8 or Non-Ascii Characters” on page 45 for a
workaround.
The first line of the file lists the available languages. For example:
QuickCode,EN_UK:ENGLISH:UK:BRITISH,DE:GERMAN:GERMANY:GERMAN
Note that QuickCode is mandatory, this code is not necessarily in any particular language but
links a translation with a particular translatable term. All other listed languages are optional.
You can add any languages to this row. For example, if you wanted to add French to the
available languages, you would add FR:FRENCH:FRANCE:FRENCH. For example:
QuickCode,EN_UK:ENGLISH:UK:BRITISH,DE:GERMAN:GERMANY:GERMAN,FR:FRE
NCH:FRANCE:FRENCH
The remaining lines within the CSV file describe each translated entry. Each row consists of a
unique quick code followed by the translations. The QuickCode that you use for a language can
be anything. The translations must follow the same order as the language list in the first row.
For example:
PWR,Leistung,power
PWRC,Leistungsteil,power circuit
SUP,Lieferant,supplier
YES,möglich,possible
SWPOS,Positionsschalter,position switch
In this example, PWR is the quick code, Leistung is the German translation and power circuit is
the English translation.
Each translatable term must have a quick code as this is used to identify which term is being
translated when you enter a translation from an application.
Each translatable term should have one translation for each available language defined in the
first line. However, if no translation exists for a particular language, the entry for that language
is placed as an empty string.
Using the above example, if there was an English translation for PWR but no German
translation, its row would be:
PWR,Leistung,,
Note
If a translation string contains an explicit comma (,), you must enter a backslash before it
(\,).
Related Topics
Diagram Language Translation
Saving a Language Dictionary CSV File with UTF-8 or Non-Ascii Characters
Importing a Language Dictionary CSV File
Exporting a Language Dictionary CSV File
Refreshing Language Dictionary Data in a Design Application
Adding a Translation of an Existing Translatable Term for the Currently Active Language
Adding a Translation of a New Translatable Term for the Currently Active Language
Converting Free Text Strings into Translations
Note
Do not select ANSI or you will lose any accents.
Note
When importing and exporting system data, any language dictionary data will be included in
your system data and as such will be imported and exported. You do not need to import and
export language dictionary data separately, although you may want to just import language
dictionary data from a separate CSV file.
Prerequisites
• The CSV file must contain the languages that you want available. See “Editing the
Language Dictionary CSV File” on page 43.
• Your user account must have the Import Language Dictionary permission.
Procedure
1. In Capital Project, press Space Bar and enter Import Language Dictionary; the Import
Dictionary dialog is displayed.
2. Navigate to the language dictionary CSV file and select it. If your database already
contains language dictionary data, you must specify one of the following:
• Overwrite
Completely overwrites the contents of the existing language dictionary in the
database and removes existing translations that are not in the imported CSV file.
• Merge
Merges the contents of the CSV file with the existing language dictionary in the
database. Existing strings that are not included in the CSV file remain in the
database. New strings are added and existing strings are updated with any new
translation strings in the file.
3. Click Import Dictionary.
Results
The contents of the language dictionary CSV file are stored as part of your system data.
Related Topics
Diagram Language Translation
Editing the Language Dictionary CSV File
Exporting a Language Dictionary CSV File
Refreshing Language Dictionary Data in a Design Application
Adding a Translation of an Existing Translatable Term for the Currently Active Language
Adding a Translation of a New Translatable Term for the Currently Active Language
Converting Free Text Strings into Translations
Prerequisites
• Your user account must have the Export Language Dictionary permission.
Procedure
1. In Capital Project, press Space Bar and enter Export Language Dictionary; the Export
Dictionary dialog is displayed.
2. Navigate to the location where you want to save the file, specify a name and click
Export Dictionary.
Results
The contents of your language dictionary are saved in the CSV file.
Related Topics
Diagram Language Translation
Editing the Language Dictionary CSV File
Importing a Language Dictionary CSV File
Refreshing Language Dictionary Data in a Design Application
Adding a Translation of an Existing Translatable Term for the Currently Active Language
Adding a Translation of a New Translatable Term for the Currently Active Language
Converting Free Text Strings into Translations
Procedure
Press Space Bar and enter Language Dictionary; the language dictionary accessed by the
application is updated.
Results
• Any new languages that have been added are now visible in the application.
• Any modified translations are displayed in the application.
Related Topics
Diagram Language Translation
Editing the Language Dictionary CSV File
Importing a Language Dictionary CSV File
Exporting a Language Dictionary CSV File
Adding a Translation of an Existing Translatable Term for the Currently Active Language
Adding a Translation of a New Translatable Term for the Currently Active Language
Converting Free Text Strings into Translations
Related Topics
Diagram Language Translation
Editing the Language Dictionary CSV File
Importing a Language Dictionary CSV File
Exporting a Language Dictionary CSV File
Refreshing Language Dictionary Data in a Design Application
Adding a Translation of a New Translatable Term for the Currently Active Language
Converting Free Text Strings into Translations
Related Topics
Diagram Language Translation
Editing the Language Dictionary CSV File
Importing a Language Dictionary CSV File
Exporting a Language Dictionary CSV File
Refreshing Language Dictionary Data in a Design Application
Adding a Translation of an Existing Translatable Term for the Currently Active Language
You can do this in the design applications and it will work on any texts in fields where
translation is supported. You specify whether you want to perform this for an entire project, a
design or a diagram.
Procedure
1. Press Space Bar and enter Translation; the Batch Translate Dialog Box is displayed.
2. In the Scope tree, select the designs and diagrams in which you want to perform the
action and click Translate; a progress bar indicates that the action is being performed.
Results
• A Batch Translate tab in the Output Window at the bottom of the application reports on
the results of the action.
• If multiple entries are found for a particular text in the language dictionary, the one
whose quick code appears alphabetically first is used.
Related Topics
Diagram Language Translation
Editing the Language Dictionary CSV File
Importing a Language Dictionary CSV File
Exporting a Language Dictionary CSV File
Refreshing Language Dictionary Data in a Design Application
Adding a Translation of an Existing Translatable Term for the Currently Active Language
Adding a Translation of a New Translatable Term for the Currently Active Language
Server Setup
You can distribute these tasks across multiple servers by having one CIS server running as a
task execution manager and other CIS installations running as task execution slaves:
• Configuring a Capital Integration Server as the Task Execution Manager
• Configuring a Capital Integration Server as a Task Execution Slave
When a task is sent to the task execution manager, it finds the first idle slave and forwards the
task to it. The client computer on which the tasks are submitted must be configured to connect
to the Task Execution Manager (see “Configuring a Client to Connect to the Task Execution
Manager when Submitting a Task” on page 55).
Starts client in headless mode, supplying tasks and parameters. When a task is complete
(success or failure), the slave reports back to the Task Execution Manager.
The status of tasks is viewable in the Tasks tab in Output Window of the design tools.
Tasks can be submitted to a Capital Integration Server (CIS) either for execution as soon as
possible or for execution at a specified time. If you want to schedule specific times when
running a task in the background, you can use web services to schedule it. See the
WebServiceDevelopment.pdf document located in the doc folder of your Capital installation for
more information about web services.
At v2014.1, running FMEA analysis scenarios as background tasks supports the Flexible
Execution Model (FEM). See “Running FMEA Scenarios in Capital Analysis in the
Background” on page 59.
Note
In order to manage Flexible Execution Model (FEM) tasks, your user account must have the
Task Administration permission set in Capital User.
• SubmitTask
Enables you to submit a new task.
• ListTasks
Enables you to retrieve a list of submitted tasks.
• DescribeTask
Enables you to view the execution records and parameters for a specific task.
• DeleteTask
Enables you to delete a submitted task.
See the WebServiceDevelopment.pdf document located in the doc folder of your Capital
installation for more information about these web services and how to use them.
The doc/webservices/ folder also contains a data sub-folder that provides an example task
parameters file for use in SBOM and costing generation. You can access FEM using these
parameters, adapted for your own requirements.
Related Topics
Configuring a Capital Integration Server as the Task Execution Manager
Configuring a Capital Integration Server as a Task Execution Slave
Configuring a Client to Connect to the Task Execution Manager when Submitting a Task
Running SBOM Generation and Costing in Capital Harness MPM and Capital Harness TVM in
the Background
• Edit the cismaster node in the file to specify parameters that control the behavior of the
task execution manager and to specify the connection details for the task execution
slaves.
• Check that the use_licensed_services parameter for the Capital Integration Server
section is set appropriately for your licensing setup.
See the Flexible Execution Manager (FEM) section and Capital Integration Server (CIS)
entry in the Capital Configuration Files Reference guide.
Related Topics
Running Capital Tasks in the Background (Flexible Execution Model)
Configuring a Capital Integration Server as a Task Execution Slave
Configuring a Client to Connect to the Task Execution Manager when Submitting a Task
• Edit the cismaster node in the file to specify the connection details for the task
execution manager.
• Check that the use_licensed_services parameter for the Capital Integration Server
section is set appropriately for your licensing setup.
See the Flexible Execution Manager (FEM) section and Capital Integration Server (CIS)
entry in the Capital Configuration Files Reference guide.
Related Topics
Running Capital Tasks in the Background (Flexible Execution Model)
Configuring a Capital Integration Server as the Task Execution Manager
Configuring a Client to Connect to the Task Execution Manager when Submitting a Task
See the cismaster section of the Capital Configuration Files Reference guide.
Related Topics
Running Capital Tasks in the Background (Flexible Execution Model)
Configuring a Capital Integration Server as the Task Execution Manager
Configuring a Capital Integration Server as a Task Execution Slave
Prerequisites
• You must have configured the Capital Integration Server that is running as the task
execution manager. See “Configuring a Capital Integration Server as the Task Execution
Manager” on page 54.
• You must have configured the Capital Integration Servers that are running as the task
execution slaves. See “Configuring a Capital Integration Server as a Task Execution
Slave” on page 54.
• The Capital Integration Servers must be running. On the task execution manager
computer, you must have logged in to the Capital Integration Server with a user name
and password.
• The client from which you are running harness processing must have been configured to
connect to the Task Execution Manager (see “Configuring a Client to Connect to the
Task Execution Manager when Submitting a Task” on page 55).
Procedure
Run harness processing as detailed in the Processing a Harness Design topic in the Capital
HarnessXC User Guide but ensure that you select the Background Run box at the bottom of
the Harness Processing dialog.
Note
If you want to use scheduling when running harness processing in the background,
you can use web services to schedule it. See the WebServiceDevelopment.pdf
document located in the doc folder of your Capital installation for more information
about web services.
Results
When the harness processing starts, the task will be viewable in the Tasks Tab.
Related Topics
Running Capital Tasks in the Background (Flexible Execution Model)
Tasks tab in Output Window
Future
Related Topics
Configuring a Capital Integration Server as the Task Execution Manager
Configuring a Capital Integration Server as a Task Execution Slave
Configuring a Client to Connect to the Task Execution Manager when Submitting a Task
Running SBOM Generation and Costing in Capital Harness MPM and Capital Harness TVM in
the Background
Prerequisites
• You must have configured the Capital Integration Server that is running as the task
execution manager. See “Configuring a Capital Integration Server as the Task Execution
Manager” on page 54.
• You must have configured the Capital Integration Servers that are running as the task
execution slaves. See “Configuring a Capital Integration Server as a Task Execution
Slave” on page 54.
• The Capital Integration Servers must be running. On the task execution manager
computer, you must have logged in to the Capital Integration Server with a user name
and password.
• The client from which you are running SBOM generation and costing must have been
configured to connect to the Task Execution Manager (see “Configuring a Client to
Connect to the Task Execution Manager when Submitting a Task” on page 55).
• Capital Harness MPM and Capital Harness TVM are installed, with the appropriate
licenses, on your remote machines.
Procedure
Run SBOM generation and costing as detailed in the Generating an SBOM topic in the Capital
Manufacturing Systems Solutions User Guide but ensure that you select the Background
Run box at the bottom of the SBOM Processing Wizard dialog.
Note
If you want to use scheduling when running SBOM generation and costing in the
background, you can use web services to schedule it. See the
WebServiceDevelopment.pdf document located in the doc folder of your Capital
installation for more information about web services.
Results
SBOM generation and costing runs, the task will be viewable in the Tasks tab of the Output
window.
Related Topics
Running Capital Tasks in the Background (Flexible Execution Model)
Note
If you want to use scheduling when running FMEA analysis in the background, you
can use web services to schedule it. See the WebServiceDevelopment.pdf document
located in the doc folder of your Capital installation for more information about web
services.
Results
When the FMEA starts, the task will be viewable in the Tasks tab in Output Window.
Related Topics
Running Capital Tasks in the Background (Flexible Execution Model)
Prerequisites
• You must have configured the Capital Integration Server that is running as the task
execution manager. See Configuring a Capital Integration Server as the Task Execution
Manager.
• You must have configured the Capital Integration Servers that are running as the task
execution slaves. See Configuring a Capital Integration Server as a Task Execution
Slave.
• The Capital Integration Servers must be running. On the task execution manager
computer, you must have logged in to the Capital Integration Server with a user name
and password.
• The client from which you are running the Create audit report task must have been
configured to connect to the Task Execution Manager (see Configuring a Client to
Connect to the Task Execution Manager when Submitting a Task).
Procedure
Use either the SCA Wizard, the Stress Analysis Wizard or the simulation tool, Capital
SimScript tab to create the required audit report as detailed in the Creating a SCA Report, the
Stress Analysis Wizard and the Using a Script File topics in the Capital Analysis User Guide,
but ensure that you select the Run in background box at the bottom of the appropriate dialog.
Note
If you want to use scheduling to create audit reports when running analysis
operations in the background, you can use web services to schedule it. See the
WebServiceDevelopment.pdf document located in the doc folder of your Capital
installation for more information about web services.
Results
When the audit reports are created, the task will be viewable in the Tasks tab of the Output
window.
2. Start typing the name of the action in the box; the Ribbon Helper searches for actions
matching the string.
Results
If only one actions matches the string, the ribbon jumps to the appropriate tab and the action is
highlighted.
If multiple actions match the string, the dialog box lists the matches. Click the action you want
and the ribbon jumps to that action.
To activate an action, do one of the following:
• Select it in the search results and press Enter
• Double-click it in the search results
• Click it on the ribbon
Launch Pane
The Launch Pane is displayed in a design application when no diagram is open.
The top panels on it change each release and provide links to information on such things as new
functionality.
At the bottom of the launch pane, the following icons link to the following sources of
information:
On Demand Training Mentor Learning Center where you can enroll on courses
about Capital software.
This chapter contains the following topics which explain how to perform various generic editing
actions on diagrams.
Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Project Browser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Opening a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Deleting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Importing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Exporting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Closing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Project Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Capital Compressed Format for Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Exporting a Project in Capital Compressed Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Importing a Project in Capital Compressed Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Designs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Importing Designs into a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Migrating a Design from Capital Harness Classic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Editing the Information for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Adding a Property to a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Editing a Property for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Deleting a Property for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Comparing Objects and Their Properties in Design Revisions or Build Lists . . . . . . . . . . 81
Running Design Rule Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Running Design Rule Checks in Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Design Rule Checks Output Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Design Rule Check Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Releasing Designs with Enforced Design Rule Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Build List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Options and Option Relationships . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Define Option Relationships. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Creating an Option Folder at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Creating an Option at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
Defining Inclusive and Exclusive Relationships for an Option . . . . . . . . . . . . . . . . . . . . . 119
Creating an Option Combination at Project Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Adding a Valid Selection to an Option Combination . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Deleting a Valid Selection from an Option Combination. . . . . . . . . . . . . . . . . . . . . . . . . . 121
Deleting an Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Projects
The topics in the following sections explain how to open, create, edit and delete projects from
within the application.
Project Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Opening a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Creating a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Deleting a Project. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
Importing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Exporting a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Closing a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Project Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Capital Compressed Format for Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Exporting a Project in Capital Compressed Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Importing a Project in Capital Compressed Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Project Browser
The Project Browser is located on the upper left side of the application window.
It contains the following:
In the field next to the Enter Filter String icon ( ), enter a series of characters. A filter
is applied to the Project Browser Tree so that only designs with names containing that
series of characters are listed.
Click the Clear Filter String icon ( ) to clear the filter and view all designs in the
project.
• Design Filter ( )
Click the dropdown list to filter the designs displayed in the Project Browser Tree
window to those of a particular type, all designs in the project or all designs in the
currently active build list.
Related Topics
Opening a Project
Creating a Project
Deleting a Project
Importing a Project
Exporting a Project
Closing a Project
Project Preferences
Opening a Project
This topic explains how to open an existing project.
Procedure
1. Press Space Bar and enter Open.
The Open Project Dialog Box is displayed.
2. Click the project that you want to open and click OK.
Results
The project opens and is added to the Project Browser.
Related Topics
Creating a Project
Deleting a Project
Importing a Project
Exporting a Project
Closing a Project
Project Preferences
Creating a Project
This topic details how to 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
1. Press Space Bar and enter New Project. The New Project Dialog Box is displayed.
2. Enter a Name for the project.
3. Click OK.
Results
The project is created and added to the Project Browser.
Related Topics
Opening a Project
Deleting a Project
Importing a Project
Exporting a Project
Closing a Project
Project Preferences
Deleting a Project
This topic details how to delete a project from the database.
Caution
The deletion of a project can only be undone from a database backup.
Procedure
1. Open the project you want to delete.
2. Press Space Bar and enter Delete Project.
3. A message is displayed asking you to confirm the deletion. Click Yes to proceed and
delete the project.
Results
The project is removed from the database.
Related Topics
Opening a Project
Creating a Project
Importing a Project
Exporting a Project
Closing a Project
Project Preferences
Importing a Project
This topic details how to import a project (from a Project XML file) that has been exported from
another instance of Capital.
Procedure
1. Press Space Bar and enter Import Project. A generic file browser is displayed.
2. Navigate to the Project XML (*.xml) file that you want to import.
3. Click Import Project. A progress bar monitors the status of the import and disappears
once complete.
Note
An imported project is not opened by default and must be opened manually.
Related Topics
Opening a Project
Creating a Project
Deleting a Project
Exporting a Project
Closing a Project
Project Preferences
Exporting a Project
Projects may be exported from, and imported into, the Capital Design databases (as XML files).
The use of XML files as the data-transfer medium enables the exchange of project data between
other data systems and also increases the portability of Capital project data. The data stored in
XML files is readily manipulated manually.
An exported project's XML file contains all of the information (options, object names, designs,
diagrams 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
1. If you want to export the currently open project, press Space Bar and enter Export
Current Project, or right-click on the project and select Export.
If you want to export a project that is not open, press Space Bar and enter Select Project
to Export; the Select Project dialog box is displayed. Select the project to export and
click OK.
The Export Project dialog box is displayed.
2. Specify the folder location and file name for the project's exported XML file.
3. Choose the following as required:
• As Copy
Select this if you want the project to be exported with anonymous unique identifiers
(UIDs). This option replaces all of the exported project's database UIDs (within the
exported XML file) with anonymous UIDs so that the project can be imported back
into Capital in the future. A project exported with anonymous UIDs are
automatically assigned new UIDs when it is imported back into Capital.
Note
When a project is exported from Capital, its original record remains in the
database with its original UIDs. Therefore, if the project is exported without
anonymous UIDs, it cannot be imported back into Capital unless its UIDs have been
changed, as its original UIDs are already present in the original project in the
database and are not allowed to be overwritten.
4. Click Export Project; the selected project is exported from the database.
Related Topics
Opening a Project
Creating a Project
Deleting a Project
Importing a Project
Closing a Project
Project Preferences
Closing a Project
This topic explains how to close a project in the application.
Procedure
1. Click the project in the Project Browser and either:
• Press Space Bar and enter Close Project
• Right-click on the project and select Close Project
2. A warning prompts you to save any modified designs in the project. Click Yes to save
them and close the project. Click No to discard any changes you have made and close
the project.
Related Topics
Opening a Project
Creating a Project
Deleting a Project
Importing a Project
Exporting a Project
Project Preferences
Project Preferences
Project preferences are default settings that you specify for the designs and diagrams in a
project.
You specify them in the Project Preferences Dialog Box, accessed in the design applications by
pressing Space Bar and entering Project Preferences.
You can also edit them in Capital Project by opening a project, expanding the Project Browser
Tree for that project and double-clicking the Preferences node.
Note
Some preferences work alongside Capital styling to control the appearance of designs. See
the Capital Diagram Styling User Guide for more information about all aspects of Capital
styling.
If a preference (for example, bundle thickness) is specified for an object type, whenever a new
instance of that object type is inserted into a design, it will automatically assume this pre-set
preference setting.
All new and existing designs within a project automatically inherit their project's preferences.
Note
Preferences can also be specified at the system level.
Related Topics
Project Preferences Dialog Box
When you import a project in Capital Compressed Format, the system does not perform design
validation checks automatically. However, it runs those checks when you open an imported
design in any Capital application.
In addition, you can use Capital compressed format to export a corrupted project from the
database. The project data is exported in a .ccf file that can be sent directly to Mentor Graphics
support or to your own in-house support, who should forward it to Mentor Graphics support.
For instructions about exporting a project as a raw data dump, see “Exporting a Project in
Capital Compressed Format” on page 71.
Related Topics
Exporting a Project in Capital Compressed Format
Importing a Project in Capital Compressed Format
Procedure
Choose an action:
Results
The system saves the .ccf file at the specified location.
Results
• If a project with the same name does not exist in the database already, the specified
project is imported into the database and now appears in the Project Browser Tree.
Related Topics
Capital Compressed Format for Projects
Exporting a Project in Capital Compressed Format
Designs
The following topics explain how to import designs, edit design properties and attributes and
how to compare the content of designs.
Importing Designs into a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Migrating a Design from Capital Harness Classic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Editing the Information for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Adding a Property to a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Editing a Property for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Deleting a Property for a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Comparing Objects and Their Properties in Design Revisions or Build Lists. . . . . . . . 81
Running Design Rule Checks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Running Design Rule Checks in Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Design Rule Checks Output Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Design Rule Check Descriptions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Releasing Designs with Enforced Design Rule Checks. . . . . . . . . . . . . . . . . . . . . . . . . . . 113
Prerequisites
• Design XML file is available for import
Procedure
1. Press Space Bar and enter Import >Designs; the Import dialog is displayed.
2. Locate and select the XML files containing the designs. Click Import; the Import
Designs to Project Dialog Box is displayed with the designs listed.
3. Select the Target Project into which you are importing the designs.
4. If you want to specify advanced details for the designs that will be created in the target
project, click the Advanced button; the Import Designs to Project Wizard Dialog Box is
displayed. Skip to step 6.
If you want to specify only basic details for the designs that will be created in the target
project, edit the following as required:
• Name
• Short Description
• Description
• Revision
• Release Level
• Abstraction
• Effectivity - Displayed only if Effectivity is enabled in the target project.
• Overwrite
• Copy As Revision
• Copy Effectivity - Displayed only if Effectivity is enabled in the target project.
5. Click OK and skip to step 6
6. On the Designs tab, map the design abstractions from the source designs (designs being
imported) to the design abstractions in the target project.
7. On the Design Details tab, specify the basic details for the designs that will be created in
the target project:
• Name
• Part Number (if importing a Capital HarnessXC design)
• Revision
• Short Description
• Description
• Release Level
• Design
• Copy Associated Logic Designs (if importing a Capital Integrator design)
• Copy Generated Wiring (if importing a Capital Integrator design)
• Overwrite Revision
• Copy As Revision
8. If the imported designs contain any shared conductors, click the Shared Conductors
tab and specify the following for them:
• Project Shared Conductor
• Copy Shared Conductor
9. If the imported designs contain any shared pin lists, set the defaults for automatic shared
pin association by clicking the Shared Pin Association Defaults tab and specifying:
• Automatic Association Configuration Mode
• Automatically Associate
10. If you want to manually associate source shared pin lists with shared pin lists in the
target project, click the Shared Pin Lists tab and specify the following settings:
• Associate Pin Lists
• Associate Pins
• Pin Reservations
11. On the Summary tab, check that the listed import settings are correct. You can return to
any of the tabs to edit settings.
12. Click Back to return to the Import Designs to Project dialog box.
13. Click OK.
Results
The imported design(s) are added under the Designs node for that project.
Related Topics
Import Designs to Project Dialog Box
Import Designs to Project Wizard Dialog Box
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 dialog 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.
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.
• Part Number (Capital HarnessXC design only) - a unique part number for the
design.
• Revision - the revision for the design.
• Short Description - the short description for the design.
• Description - the long description for the design.
• 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.
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 Classic.
The release levels will be mapped between Capital Harness Classic and Capital
HarnessXC as follows:
Note
The Applicable Modules field will only display if the project has been
configured to use module codes.
These codes are used to control bundle length and object position variance. See
Variant Length Bundles and Component Positions. Optional.
• Applicable PM Codes - (Capital ModularXC only) - displays the Production
Module codes that have been assigned to this design. Click the ellipsis (...) button to
the right of the field to launch the Applicable Production Module Codes Dialog,
where you can edit the selection.
• Applicable Variant PM Codes
(This field is only available for Capital ModularXC)
Specify any Applicable Variant PM codes to be assigned to the design by clicking
the ellipsis button, (...), next to the field. This displays the Applicable Variant PM
Codes Dialog Box where you can select the required Variant Functional Module
code(s). Optional.
These codes are used to control bundle length and object position variance. See
Variant Length Bundles and Component Positions. Optional.
• Option - 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 dialog.
• Effectivity - if using effectivity, click the ellipsis (...) button to the right of the field
to launch the Edit Effectivity Dialog Box, from where you can specify the effectivity
ranges that apply to the design. See Managing Effectivity in the Capital Project
User Guide for an overview of using effectivity.
• Harness Group - (displayed for Capital HarnessXC and Capital ModularXC
designs only), Use of Harness Groups, allows auto-mapping of valid objects when
Synchronizing from a Capital Logic Build List. Harness Group names can be
manually added or removed here. To select multiple Harness Groups, click the
ellipsis (...) button to the right of the field to launch the Name Selectiondialog box,
from where you can select predefined names.
• Select Derivatives, (displayed for Capital HarnessXC and Capital ModularXC
designs with derivatives only) - If the Release Level of the Composite design has
been changed, click the ellipsis button to open the Change Release Level of Child
Designs dialog, to select, or deselect, any derivative designs to which the Release
Level change should also be applied.
• Select Functional Modules, (displayed for Capital ModularXC designs only) If the
Release Level of the Parent design has been changed, click the ellipsis button to
open the Change Release Level of Child Designs dialog, to select, or deselect, any
child designs to which the Release Level change should also be applied.
• 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.
• 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.
• Modify Harness Details - click this button to launch the Edit Harness Detailsdialog
box, from where you can enter additional manufacturing information for both
internal and customer consumption.
3. Click the OK button to confirm the changes and to exit the dialog.
Note
If you move a design to release level with Frozen Shared Objects behavior, all
shared objects in a design must be frozen. If any shared objects are not frozen, the
Freeze/Unfreeze Shared Objects dialog is displayed automatically when you click the
OK button so that you can freeze them. See the Release Level topic in the Capital
Project User Guide for more information on Release Level behaviors.
Procedure
1. In a design application (such as Capital Logic or Capital HarnessXC):
Open the diagram or plane for one of the design revisions that you want to compare,
press Space Bar and enter Compare.
In Capital Project:
In the Project Browser Tree, right-click one of the design revisions that you want to
compare and select Compare.
Note
You can export and save the comparison results in an HTML file by clicking
Export.
Procedure
1. Press Space Bar and enter DRCs.
The Design Rule Checks Dialog Box is displayed.
2. Select the design or build list that you want to check.
3. Select the checks that you want to run in the Design Rule Checks browser and click OK.
4. Any issues that the checks identify are displayed in the Design Rule Checks Output
Window.
Related Topics
Design Rule Check Descriptions
Procedure
Click the Design Rule Checks Toggle on the Status Bar at the bottom of the application:
Results
• The system runs the design rule checks that have been specified to run in background
mode in Project Preferences.
• The results of the design rule checks are listed on the Check tab of the Design Rule
Checks Output Window.
• The Design Rule Checks Toggle changes to show a square (stop icon) and also indicates
whether the checks have currently found failures or not:
• The checks run whenever changes are made to the design to which the currently active
diagram belongs; the Check tab of the Design Rule Checks Output Window and Design
Rule Checks Toggle update dynamically to reflect the latest results.
The table includes columns in which you can filter the contents by selecting an item from the
dropdown list at the top. You can sort the contents of a column by clicking the column header.
The columns are:
• Severity
Whether the result is an error ( ), a warning ( ) or an information message ( ).
• Message
Detailed message about what the check has identified. You can click an object in the
message to jump to that object in the diagram window.
• Category
The category of design rule check to which the particular design rule check belongs (for
example, Connectivity, Naming, and so on).
• Check
The specific design rule check that has identified something in the design.
• Design/Build List
The design or build list in which the check has identified something/
• Object
The specific object for which the check has identified something.
Note
The design rule check names were changed at v2012.1. For a list of the old names with their
new ones, click communities.mentor.com/mgcx/docs/DOC-3220 to go to a document in the
Electrical System Design and Harness Engineering Community.
The following sections list the design rule checks that are available for each of the applications:
• Design Rule Checks Applicable to Capital Harness MPM and Capital Harness TVM
Designs
• Design Rule Checks Applicable to Capital Topology Designs
• Design Rule Check Descriptions for Platform Designs in the Platform Design in Capital
Systems User Guide
• Design Rule Check Descriptions in the Function Design Capital Systems Capture User
Guide
Table 2-4. Design Rule Checks for Capital HarnessXC and Capital ModularXC
Table 2-4. Design Rule Checks for Capital HarnessXC and Capital ModularXC
(cont.)
Check Name Description
Connectivity
Empty multicore Identifies multicores exist that do not contain any wires.
Unconnected wire Identifies wires are unconnected at one or both ends.
Unterminated bundle Identifies bundles are unconnected at one or both ends.
Unterminated wire end Checks single and multiple wire CSA, with regard to cavity
seal and single/multi terminations. There must be a
termination for each wire.
Wire with zero strip length Checks if the wire instance has zero strip length following
harness processing.
Empty bundle The system checks the routes of all bundles and lists those
without wires or multicores.
Consistency
Blank terminal material Checks if there is any cavity detail object with a blank
driver terminal material.
Bundle arc below minimum Identifies bundles that contain an arc with a bend radius
bend radius lower than that specified in its minimum bend radius value.
Centerstrip splice not on Checks the route of all wires with center strip. The
wire route corresponding splice node should fall on the route.
Component not located on Checks if there is any component that exists on a node
any bundle which is not on any bundle.
Connector route does not Identifies if routes assigned to a connector on the design do
exist in library definition not match the routes defined in Capital Library.
Design assembly does not Detects if a main node component is present in the design
match the library assembly assembly, but not present in assembly details.
Different graphical and On a full scale diagram, if the bundle is made flexible and it
physical bundle lengths is stretched, this DRC will identify the difference between
the physical and graphical length.
Included on BOM with no Indicates if an object has an Include on BOM=true, but no
part number part assigned to it.
Inconsistent variant Evaluates all object’s variant positions against the
position reference node derivative options and validates if the order of the reference
nodes on a bundle in each derivative will be the same as the
default order specified on the bundle.
Table 2-4. Design Rule Checks for Capital HarnessXC and Capital ModularXC
(cont.)
Check Name Description
Invalid variant position Evaluates all object’s variant positions against the
derivative options and validates all object positions on a
bundle is within the bundle length limit for each derivative.
Invalid wire attributes Checks that the specified color, material and specification
versus library definition of the wire exist and are consistent with the applicable
component library codes.
Invalid wire route Checks the route on the wire.
Mid-bundle component Evaluates all object's variant positions against the
with multiple locations in derivative options and validates all object positions on a
the same derivative bundle are within the bundle length limit for each
derivative.
Multiple components at Checks if there is more than one additional component
position occupying the same position.
Multiple instances for Identifies if a variant position connector or splice exists at
variant position object on a more than one position within the same derivative.
derivative
Multiple variant bundles Identifies if more than one variant length exists for the
same bundle within a derivative.
Non-modular connector is Checks the presence of a non modular connector at a node
connected to more than one which is connected to more than one bundle. (such as a
bundle modular connector with inserts placed and connected with
zero-length bundles, then the modular connector part is
removed and a normal connector is added in its place).
Option on object not Checks that the options used for the object match the option
applicable to design expression on the design.
Unrouted wire to multi- Checks if a wire end is terminated at a multi-entry
entry connector connector but no route has been picked for this end.
Assembly insulation/wire Reports on assemblies where there is a mismatch in the
length in design does not length of wires and insulations used on the design versus
match library definition the definition in Assembly Details in Capital Library.
Assembly library definition Detects assembly components from an assembly library
not used in design part which have not been added to the assembly on the
design.
Assembly splits in Indicates if the options assigned to assembly components
derivative design would lead to them being on different derivatives.
Calculated bundle width Checks that the width of a bundle does not exceed the
exceeds max bundle width maximum bundle width specified.
Table 2-4. Design Rule Checks for Capital HarnessXC and Capital ModularXC
(cont.)
Check Name Description
Cavity component does not Checks single/multiple wire csa in relation to cavity seal
fit wire and single and multi terminals.
Cavity multi-location Reports cases where a cavity MLC (multiple location
components without component) is pointing to cavities that no longer exist (e.g.
cavities deleted connector cavities after MLC creation).
Cavity with seal but no Checks that the cavity has a seal defined, but there is no
wire connectivity at the cavity.
Cavity with terminal but no Checks that the cavity has a terminal defined, but there is
wire no connectivity at the cavity.
Child module design (Applicable for Capital ModularXC only) Checks whether
references module code not a child design uses module codes that are no longer
on composite applicable to its parent composite design, this can result
from manual or bridged-in changes to the codes applicable
to the composite. Any violations are reported.
Design has applicable (Applicable for Capital ModularXC only) Reports if objects
module code that is not exist on a design for which no module codes are assigned.
assigned to any object
Design that breaks module (Applicable for Capital ModularXC only) Examines the
code relationships module codes applied to a design and checks the explicit
inclusive/exclusive relationships and the implicit
relationships (such as mutually exclusive folders). Any
violations are reported.
Empty modular design (Applicable for Capital ModularXC only) If the design is a
module parent, this checks the module code on each object.
If a child exists where applicable module codes do not
contain at least one of the module codes used in the parent
then a report is issued.
Inconsistent assembly (Applicable for Capital ModularXC only) Checks whether
module code an assembly and its constituent parts have matching module
code assignation and reports any inconsistencies.
Inconsistent insulation code Identifies whether the contents of an insulation code have
been edited and no longer match the contents of the same
code in use within the design, or whether an insulation code
in use no longer exists within the design.
Inconsistent multicore (Applicable for Capital ModularXC only) Checks whether
inner core module code all inner cores of a multicore have matching code
assignations.
Table 2-4. Design Rule Checks for Capital HarnessXC and Capital ModularXC
(cont.)
Check Name Description
Inconsistent variant Identifies if one or more variant positions for an object
position object (connector or splice) have been modified, and are now out
of synchronization with the primary position object.
Inconsistent variant Identifies if one or more variant positions for a wire have
position wiring been modified, and are now out of synchronization with the
primary position wire.
Invalid overbraid end Identifies if a termination has been specified for an
termination overbraid that does not exist on the routes of any of the
wires contained within it.
Mismatch between Checks the content of assemblies on the design and
assembly content and highlights any that do not conform with the project
project preference preference “Assembly”.
Modular expression too (Applicable for Capital ModularXC only) Checks if the
long to be costed in CapH length of the Module Code Expression is longer than 1024
Costing characters. If this is the case it reports that, due to the
number of characters, the harness will unable to be
accurately costed in Capital Harness Classic.
Modular Objects With No (Applicable for Capital ModularXC only) Checks whether
Functional Module Codes any applicable objects exist without functional module
codes assigned.
Modular Objects With No (Applicable for Capital ModularXC only) Checks whether
Production Module Codes any applicable objects exist without production module
codes assigned.
Module code used on (Applicable for Capital ModularXC only) Reports if
composite but not module codes exist in the design that are not consumed by a
consumed by child module buildable module, indicating that a child module has not
been created to use this module.
Multi-location component Reports cases where a wire multi-location component is
without a wire end pointing to wire ends that no longer exist (e.g. deleted wire
after MLC creation).
Multi-location component Reports cases where a node multi-location component is
without node pointing to nodes that no longer exist (e.g. deleted
connector after MLC creation).
Nested assembly contains Indicates when a standard or connector assembly contains
in-house assembly/ an in-house assembly.
multicore
Table 2-4. Design Rule Checks for Capital HarnessXC and Capital ModularXC
(cont.)
Check Name Description
Object assigned a technical (Applicable for Capital ModularXC only) Examines
module code that has no module codes on each object. If the module code is a
associated combinations technical module code and is not associated with a
combination a report is issued.
Object that breaks module (Applicable for Capital ModularXC only) Examines the
code relationships module codes on each object and checks the explicit
inclusive/exclusive relationships and the implicit
relationships (such as mutually exclusive folders). Any
violations are reported.
Related objects assigned (Applicable for Capital ModularXC only) Checks the
different module codes validity of codes assignments and reports when related
objects, for example connectors and cavity seals, have been
assigned different module codes.
Obsolete option Identifies any obsolete options used on design objects.
Overlapping insulation Checks that there are no overlapping insulation layers with
layers with same layer same layer number in the same derivative.
number
Tube does not fit bundle Identifies any tubes that are too small for the bundle to
which they have been applied.
Assembly component not Checks if an extra component is present in the design
in library assembly, but not present in library.
Insufficient distance Identifies insulation runs for which the Distance between
between items items attribute has a value of 0.
General
Invalid wire path Checks if Wire End2 is reachable from Wire End1 through
the bundles and honoring the thru / not-thru nodes
constraints.
HarnessXC rules
Violated attribute/property Identifies any objects that violate any Set Attribute/
rule Property on Object constraints. These constraints define,
for specific objects, which value an attribute/property
should have when another attribute/property has another
specific value.
Wire that breaks routing Identifies wires that violate any Route by Attribute/
rule Property constraints (rules). Also reports the signal,
bundle, inline connector and harness on which the violation
exists.
Table 2-4. Design Rule Checks for Capital HarnessXC and Capital ModularXC
(cont.)
Check Name Description
Inclusion
Wire does not fit cavity Checks against cavity attributes whether a wire fits or not.
Alternative cavity plug The system has selected a cavity plug where there are two
available or more identical plugs to choose from. This check prompts
you to check the selection was correct.
Alternative cavity seal The system has selected a cavity seal where there are two or
available more identical seals to choose from. This check prompts
you to check the selection was correct
Alternative terminal The system has selected a cavity terminal where there are
available two or more identical terminals to choose from. This check
prompts you to check the selection was correct
Cavity with plug or seal Identifies where the use of plug/seals has been specified but
marked as “none” the corresponding library part does not have it assigned.
Inappropriate terminal Identifies where the terminal material or type does not
material or type for wire match the selected wire terminal or type defined in Cavity
Component Management.
Invalid mandatory item Checks if a mandatory item defined in a library
selection component's housing definition exists on the node with a
matching quantity. For cavity components, check that they
exist in the matching cavity in correct quantity.
Mismatched mated Checks that all the terminals on the cavities of a Connector
connectors and terminal are of same material.
material
Mismatched wire and Identifies the terminal material of the selected terminal
cavity terminal material does not match the wire terminal material defined in Cavity
Component Management.
Plug and wire at the same Checks if a cavity has a plug as well as a wire.
cavity
Terminal material code Identifies where the terminal selected on a derivative in a
mismatch at double multiple termination does not match the terminal material
termination assigned to the wires in Cavity Component Management.
Sealed and unsealed Checks the sealed/unsealed status on each connector and
components exist lists them.
Library Consistency
Component does not exist Identifies where an additional node or cavity component is
in housing definition not defined in the housing definition.
Table 2-4. Design Rule Checks for Capital HarnessXC and Capital ModularXC
(cont.)
Check Name Description
Latest library part status Identifies any library part that is not the latest revision.
check
Obsolete or invalid part Identifies where a part number exists but the corresponding
number part is either not available or obsolete in Library.
Fixture Part Number Validates the assigned part numbers for all fixtures on all
Validity diagrams in the design using the fixture Part Number
Selection Rules (see the Capital HarnessXC User Guide).
Note: The “Auto-Selectable” rule is not is not
considered in this check.
Include-on-BOM status Identifies where an object has a “Not-On-BOM” attribute
changed with a value different to its library setting.
Library part required for Identifies where an insulation run exists that has no library
bundle insulation part assigned.
Library part required for Identifies where a clip exists that has no library part
clip assigned.
Library part required for Identifies where a connector exists that has no library part
connector assigned.
Library part required for Identifies where a grommet exists that has no library part
grommet assigned.
Library part required for Identifies where a multi-location component exists that has
multi-location component no library part assigned.
Library part required for Identifies where a multicore exists that has no library part
multicore assigned.
Library part required for Identifies where a node insulation exists that has no library
node insulation part assigned.
Library part required for Identifies where a splice exists that has no library part
splice assigned.
Library part required for Identifies where a wire exists that has no library part
wire assigned.
Library part without Checks the components that have no supplier part number
supplier number listed in Library.
Out of scope component Identifies components whose scope is not within the scope
of the project or design.
Table 2-4. Design Rule Checks for Capital HarnessXC and Capital ModularXC
(cont.)
Check Name Description
Position assigned does not Checks if a housing component is made applicable to one
match library definition position but is placed in a different one. For example, if a
fuse is present in an incompatible position on a fuse box
connector.
Ring terminal with Issues a warning where ring terminal objects exist with
connector part number connector part numbers assigned.
Undefined route for dressed Identifies where the routes assigned to a connector on the
connector design do not match the routes defined for it in Capital
Library.
Naming
Invalid name for Identifies where objects exist with names that do not appear
component in the list of valid names for that project's object type.
Multiple components with Checks for objects with the same name on a harness design.
same name For example, when synchronizing device connectors of a
device that has two device footprint connectors with the
same part number.
Missing BOM ID Checks that all objects that can be assigned a BOM ID have
a valid BOM ID.
Table 2-5. Design Rule Checks for Capital Harness MPM and Capital Harness
TVM
Check Name Description
SBOM Checks
Costing
Sub-assembly not costed When running checks on a costed harness, this
identifies where there were problems during the cost
calculation run. Examples include:
• Task did not fire on a sub-assembly
• Formula returned no value
• Sub-assembly with no cost results
Part number
management
Table 2-5. Design Rule Checks for Capital Harness MPM and Capital Harness
TVM (cont.)
Check Name Description
Sub-assembly with no part Identifies sub-assemblies on the SBOM that have no
assigned part number assigned.
Sub-assembly structure
Incomplete insulation Identifies sub-assemblies which contain an insulation
object but which do not include all wire sub-
assemblies which run through this insulation.
Incomplete overbraid Identifies sub-assemblies which contain an overbraid
object but which do not include all wire sub-
assemblies which run through this overbraid.
Incomplete splice Checks that all connected wire sub-assemblies are also
included in a sub-assembly which contains a splice.
Orphaned strip Checks that the owner wire sub-assembly is also
included in a sub-assembly which contains a strip
(either wire end or center-strip).
• a single design
• a set of selected designs (including complete design families in composite/derivative or
modular parent/child scenarios)
Note
Default functionality enables users to bypass this process by manually changing the
release levels of designs in the Edit Design dialog. However, a system administrator
can prevent this by selecting the “Enforce Design Rule Checks on release of designs”
project preference.
If you are using Web Services, you can release designs and send an automatic notification to the
Web Services component.
Prerequisites
• In the appropriate design application, open the project that contains the designs.
• The designs to be released must have a current release level setting that can be changed
to a release level of type Released.
• The design rule checks to be run on the designs must have been set to run On Release in
the Project Preferences for the design application (the appropriate preferences are
displayed when you select the Checks node for an application in the Project Preferences
Dialog Box).
Procedure
1. In the appropriate design application for the type of design that you want to release,
press Space Bar and enter Release; the Release Designs Dialog Box is displayed.
2. Select the designs that you want to release.
Note
If you have a design open in the diagram window, it is selected automatically. If you
have selected designs in the Project Browser Window on the top left of the
application window before initiating this action, those designs are selected
automatically.
3. Specify the Release Level that you want to apply to the designs.
4. Specify whether you want to “Annotate results” and “Treat warnings as errors” for the
design rule checks.
Note
When you select to annotate results, the release process is slower if the diagrams
involved are not open in the design application. This is because the application must
open and close each diagram. Project preferences can also be used to set whether the
Annotate results box is checked by default (Annotate by Default) and to customize the
wording of the annotation that is added to the diagram (Annotation Template).
5. Click OK; a progress bar is displayed while the design rule checks run.
Results
• If there are no failures, the release level for the designs is changed and they are saved,
including any modifications such as annotations.
• A summary of the release process is displayed in the Output Window at the bottom of
the application. This indicates whether any design rule checks failed for designs. The
Check tab of the Output Window gives details of the design rule checks that have failed.
The failure messages contain links to objects that caused the failures. You must fix any
issues in a design before you can release it.
• For a Capital Logic design, the summary also lists any shared objects that are frozen
during the release process.
Related Topics
Designs
Build List
A build list is a container for designs, representing a sub-set of a vehicle’s connectivity and
topology at a single point in the design lifecycle. Any number and configuration of build lists
may be created for a project.
See Build List in the Capital Project User Guide for full details of this concept and links to
related tasks.
option can be selected in an option combination and arranged to permit only the
following combinations:
o (A, B, C, D, E, F)
o (B, F)
o (A)
o (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:
o An option can exist in either no option combination or just one option combination
(that is, not multiple option combinations).
o An option combination does not have to include a valid selection where all options
are selected.
o 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.
o 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.
Related Topics
Creating an Option Folder at Project Level
Creating an Option at Project Level
Defining Inclusive and Exclusive Relationships for an Option
Creating an Option Combination at Project Level
Adding a Valid Selection to an Option Combination
Deleting a Valid Selection from an Option Combination
Deleting an Option
A new option folder is added to the Options Browser on the left of the dialog.
4. Specify the Name of the folder and whether it will contain options that are Mutually
Exclusive or Mandatory.
5. Click OK.
Related Topics
Creating an Option at Project Level
Defining Inclusive and Exclusive Relationships for an Option
Creating an Option Combination at Project Level
Adding a Valid Selection to an Option Combination
Deleting a Valid Selection from an Option Combination
Deleting an Option
4. Specify the Name and Description for the option and whether it is a variant option.
A new option combination is added to the Options Browser on the left of the dialog.
3. Specify the Name for the option combination.
4. Drag and drop an option to be included in the option combination from its location in the
Options Browser tree to the option combination node in the tree.
The option is listed under the option combination as well as in its original location in the
tree.
5. Repeat step 4 for each option that you want to add to the option combination.
6. Select the option combination in the Options Browser.
The options are displayed as columns in the Valid Selections table.
7. Click to add a valid selection row to the table.
2. Select the option combination in the Options Browser on the left of the dialog.
The Valid Selections table on the right of the dialog displays the existing valid selections
for the option combination.
3. Select the row that you want to delete.
4. Click .
The row is deleted from the table and the valid selection is deleted from the option
combination.
5. Repeat steps 3 to 4 for each valid selection that you want to add.
6. Click OK.
Related Topics
Creating an Option Folder at Project Level
Creating an Option at Project Level
Defining Inclusive and Exclusive Relationships for an Option
Creating an Option Combination at Project Level
Adding a Valid Selection to an Option Combination
Deleting an Option
Deleting an Option
This topic explains how to delete an option from the Options Dialog Box.
Procedure
1. Select the option in the Options Browser.
2. Click Delete selected objects ( ).
Results
• If the option is used in a combination, an error message is displayed, giving details of the
combination that is using the option, and the option is not deleted.
• If the option has been specified as an applicable option for a design, an error message is
displayed, giving details of the design that is using the option, and the option is not
deleted.
• If the option is not used in a combination, it is removed from the Options Browser.
Related Topics
Creating an Option Folder at Project Level
ECO Introduction
Engineering Change Orders (ECO) allow you to track the implementation of any instructions to
make a change to one or more designs. Once the change has been made, the ECO can be set as
“Completed”.
Image files can be added to the ECO and opened in the Image Viewer, to illustrate and explain
the before and after details of the changes required.
In Capital HarnessXC and Capital ModularXC you can automatically capture and store design
changes against an ECO and re-apply them onto a different design revision at a later date. See
“Capture and Apply a Change Within an ECO” on page 128,
Since the scope of an ECO can span many designs within Capital, each design within an ECO
has a Completion Status (Not Started, In Progress or Completed), and only when the
completion status for each design is set to Completed, can the release level of the ECO be
changed to Released (note that an ECO can transition between Draft, Obsolete, Released -
these levels can be configured within Capital Project). However, the release level assigned to an
ECO does not have to be the same release level assigned to the impacted design revisions.
You can:
• Manually create ECOs within the Capital design applications. See “Creating an
Engineering Change Order” on page 126.
• Import and export ECO Impacted Designs using the Capital applications.
When you export and import project data (as a copy or dataset), all ECO data is included.
However, if you export the project as a template, no ECO data is included.
Related Topics
Working with an ECO Created in Capital
Creating an Engineering Change Order
Deleting an Engineering Change Order
Viewing Engineering Change Orders
Engineering Change Orders Dialog Box
ECO Import and Export
Capture and Apply a Change Within an ECO
Note
You can also change the status on the Engineering Change Orders Tab see “Start and
Stop Recording an ECO Change” on page 130.
4. In Capital Project or a design tool, open the Engineering Change Orders Dialog Box;
note that the Completion value for each design associated with the ECO has changed to
Completed. Change the ECO Release Level to Released.
Related Topics
Creating an Engineering Change Order
Deleting an Engineering Change Order
Viewing Engineering Change Orders
Results
• An association is created between the ECO and the impacted designs and any image
files added.
Related Topics
Working with an ECO Created in Capital
Deleting an Engineering Change Order
Viewing Engineering Change Orders
Engineering Change Orders Dialog Box
Prerequisites
• ECOs have been created for the relevant design.
• The relevant designs have been associated to the ECOs.
Procedure
1. Open the diagram in the relevant Capital Design tool
2. Press Space Bar and enter ECOs.
Results
• ECOs applicable to the active design are displayed in the Engineering Change Orders
Tab, below the diagram. You can use the Filter button to toggle the display to show all
ECOs for the project.
Note
If no diagram is open, then all ECOs applicable to the current project are displayed.
Related Topics
Working with an ECO Created in Capital
Creating an Engineering Change Order
Deleting an Engineering Change Order
Engineering Change Orders Dialog Box
Engineering Change Orders Tab
Note
This functionality is available in Capital HarnessXC and Capital ModularXC only.
• Recorded ECO capture data. See “Recording a Change with an ECO” on page 132
• Images. You can add PNG, JPG or JPEG files to help illustrate details of the ECO.
You can export and import ECO impacted designs between ECOs in the same or different
projects or databases. See “ECO Import and Export” on page 147.
Note
If you change the completion status from Completed to In Progress, any recorded changes
are deleted from the ECO impacted design. If you change the completion status from In
Progress to Not Started, the baseline point where the recording started is deleted from the ECO
impacted design.
• From the ECO Tab on the Edit Design Properties dialog box.
Apply Changes
When you have captured the ECO changes, they can be applied to a target design.
Related Topics
Recording a Change with an ECO
ECO Import and Export
Applying a Stored Change from an ECO
Identifying Topology Changes with Hotspots
Harness Object Behavior on Applying ECO Changes
Prerequisites
• The required Impacted Design is associated to the ECO. See Creating an Engineering
Change Order.
• The Completion Status of the Impacted Design on the ECO is set to Not Started.
Procedure
1. Open the required design diagram.
2. Press Space Bar and enter ECOs.
The Engineering Change Orders Tab opens in the output window below the diagram.
3. Click the ellipsis button in the Name cell of the relevant ECO and choose Completion
Status > In Progress.
Alternatively, open the Edit Design Properties Dialog Box for the required design and
click the ECO Tab. In the Design Status column for the ECO, change the value to In
Progress and click OK.
The Create Baseline message box is displayed.
4. Click the Create Baseline button.
The system creates a baseline and starts recording the ECO changes you make from this
point. This is indicated by the Completion Status of the impacted design changing to “In
Progress (Capturing Changes)” on the Engineering Change Orders Dialog Box.
5. Make the appropriate changes as documented in the ECO description and illustrated by
any associated image files.
6. Optionally add images to confirm that the changes have been made.
7. Save the design.
8. In the Engineering Change Orders Tab, click the ellipsis button in the Name cell and
choose Completion Status > Completed.
Results
• The system stops recording. All the changes you have made are captured and stored
against the ECO Impacted Design. This is indicated by the Completion Status of the
Prerequisites
• The steps in the Recording a Change with an ECO topic have been completed.
• A target design which is a revision or copy of the source design used in the Recording a
Change with an ECO topic is open.
• The target design has been added as an impacted design of the ECO and has a
Completion Status of In Progress. See Creating an Engineering Change Order.
Procedure
1. Press Space Bar and enter Apply Change.
2. The Applicable Changes Dialog Box displays. Select the required ECO Impacted
Design and click the Apply Change button.
3. The Change Manager Apply ECO Dialog Box and/or the Change Manager Preview
ECO Dialog Box are displayed, depending on which was displayed at the end of the
previous session. (You can use the View ( )Toolbar button to toggle between the two
dialog boxes.
Note
The Simulate Change Output Window displays automatically. It reports all the
identified changes that will be applied on processing the ECO, without the design
changes being committed.
4. On the Change Manager Apply ECO Dialog Box, choose File > Options.
The Options (Apply ECO) Dialog Box displays.
5. Configure any ECO apply change settings on the Translation, Change Policy and Setup
tabs. These settings are persisted from the last time the dialog box was used.
6. Any topology changes are highlighted in the Change Manager Preview ECO Dialog Box
as hotspots. See “Identifying Topology Changes with Hotspots” on page 134 for more
information.
7. Click the Process button. The ECO changes are applied to the target design. See
Harness Object Behavior on Applying ECO Changes for information about how the
changes are applied to different harness objects.
Results
• The recorded changes are all applied to the target design revision.
• The Apply Change Output Window displays. It reports the changes that have been
applied on processing the ECO. Any changes that could not be made due to conflict in
the target design state are also reported for manual intervention.
Related Topics
Recording a Change with an ECO
Harness Object Behavior on Applying ECO Changes
Identifying Topology Changes with Hotspots
ECO Import and Export
• Connected bundles at a node in the source data are left unlinked to the same node in the
target design.
• Connected bundles at a node in the target design are left unlinked to the same node in the
source data.
• There is a connector mismatch at a node.
Clicking on a hotspot automatically highlights the bundles and connectors which are causing the
issue, as shown in Figure 2-6, where Bundle 8 has switched nodes. These can then be
investigated.
Bundles
The Change Manager Apply ECO process offers the following support for bundles.
• Place - Appropriate bundles are created as specified.
If multiple objects are selected for placement, all selected bundles are placed first, this is
because placement of splices, fixings and protections, mandates that underlying bundles
are already placed.
• Link - Creates a permanent association between the target object and its counterpart in
the source.
• Unlink - Clears the value in the selected Capital object’s External ID attribute, breaking
the link with the Source object.
• Autolink - Only Name and Length are applicable to bundles.
• Synchronize - Updates the linked object with the source data. The following attributes
are synchronized in accordance with any defined Change Policy:
o MaxBundleWidth
o MinBendRadius
o Option Expression
o The Source ID of a linked bundle is displayed in the Edit Bundle dialog box as an
attribute of the bundle.
Splices
The Change Manager Apply ECO process offers the following support for splices.
• Place - If the source data has a part number specified and the part is available in the
library, then it is assigned to the splice created in the design. If the part is not found, the
splice is still created as per the source data, and a warning related to the missing part is
displayed in the Status field. The splice is created even if the source data does not have a
part number specified.
If the underlying bundle is not linked, the splice is not be placed and an error is
displayed in the Status field.
All splice cavity names (default L, R, X or any other user defined name) are preserved.
• Link - Creates a permanent association between the target object and its counterpart in
the source.
• Unlink - Clears the value in the selected Capital object’s External ID attribute, breaking
the link with the Source object.
• Autolink - Only Name, Offset, ElecId and PartNumber are applicable to splices
• Synchronize - Updates the linked object with the source data.
o The part number specified in the source data is searched for in the library and if
found, is assigned to the splice in the design (accordance with any defined Change
Policy) irrespective of whether it is already part assigned or not. If the part is not
found, then the existing part assigned to the splice in the design will remain.
o The Source ID of a linked splice is displayed in the Capital HarnessXC Edit Splice
dialog box as an attribute of the splice.
Devices
The Change Manager Apply ECO process offers the following support for devices.
• Place - A device is placed at the bundle end node if the connected bundle is already
placed. Otherwise it is placed at the node coordinates. New incoming devices, without a
node, are automatically placed on existing structure nodes in the design with the same
name, and without any node component.
If the source data has a part number specified and the part is available in the library, then
it is assigned to the device created in the design. If the part is not found, the device is
still created as per the source data, and a warning related to the missing part is displayed
in the Status field. The device is created even if the source data does not have a part
number specified.
Cavities are created as specified in the source data. Additional components are created
only as part of the housing of the device part, so the Place function only needs to select
appropriate additional components after assigning the device part.
• Link - Creates a permanent association between the target object and its counterpart in
the source.
• Unlink - Clears the value in the selected Capital object’s External ID attribute, breaking
the link with the Source object.
• Autolink - Only Name, ElecId and PartNumber are applicable to devices.
• Synchronize - The linked device is updated with the source data.
o The part number specified in the source data is searched for in the library and if
found, is assigned to the device in the design (accordance with any defined Change
Policy) irrespective of whether it is already part assigned or not. If the part is not
found, then the existing part assigned to the device in the design will remain.
o If an associated additional component part (or its quantity) are different, a Property
Mismatch is shown. If the additional component part specified in the source data is
different from the selected additional components, and if the new additional
component exists in the library as an available additional component, then that one is
selected.
o If the number of cavities differs between the source data and the harness device, a
Property Mismatch is shown. If the number of cavities is greater in the source device
than the target device, remaining non-linked cavities are created.
Note
Creation of cavities is performed only if there is no part assigned. User-defined
properties of cavities are not considered as this is not supported in Capital
HarnessXC.
• Changes to cavities are managed based on a one-to-one mapping between the cavities in
the source data and those in the target design, using the cavity name.
• The Option Expression and Module Expression fields are also synchronized.
• The Source ID of a linked device is displayed in the Capital HarnessXC Edit Device
dialog box as an attribute of the device.
Connectors
The Change Manager Apply ECO process offers the following support for connectors.
• Place - A connector is placed at the bundle end node if the connected bundle is already
placed. Otherwise it is placed at the node coordinates. New incoming connectors,
without a node, are automatically placed on existing structure nodes in the design with
the same name, and without any node component.
If the source data has a part number specified and the part is available in the library, then
it is assigned to the connector created in the design. If the part is not found, the
connector is still created as per the source data, and a warning related to the missing part
is displayed in the Status field. The connector is created even if the source data does not
have a part number specified.
Cavities are created as specified in the source data. Backshells and any other additional
components are created only as part of the housing of the connector part, so the Place
function only needs to select an appropriate backshell and other components as
additional components after assigning the connector part.
• Link - Creates a permanent association between the target object and its counterpart in
the source.
• Unlink - Clears the value in the selected Capital object’s External ID attribute, breaking
the link with the Source object.
• Autolink - Only Name, ElecId and PartNumber are applicable to connectors.
• Synchronize - The linked connector is updated with the source data.
o The part number specified in the source data is searched for in the library and if
found, is assigned to the connector in the design (accordance with any defined
Change Policy) irrespective of whether it is already part assigned or not. If the part is
not found, then the existing part assigned to the connector in the design will remain.
o If an associated backshell part or additional component part (or its quantity) are
different, a Property Mismatch is shown. If the backshell part or additional
component part specified in the source data are different from the selected additional
components, and if the new backshell/additional component exists in the library as
an available additional component, then that one is selected. User-defined properties
of a backshell are not considered as this is not supported in Capital HarnessXC. The
length of backshell is also not synchronized.
o If the number of cavities differs between the source data and the harness connector, a
Property Mismatch is shown. If the number of cavities is greater in the source
connector than the target connector, remaining non-linked cavities are created.
Note
Creation of cavities is performed only if there is no part assigned. User-defined
properties of cavities are not considered as this is not supported in Capital
HarnessXC.
• Changes to cavities are managed based on a one-to-one mapping between the cavities in
the source data and those in the target design, using the cavity name. Changes to plugs,
seals and terminals are synchronized.
• Cavity wire combinations, including “autoselect” attributes for plugs and seals are
supported, enabling multiple cavity details to be correctly handled.
• The Plugged and Sealed flags of connectors are also synchronized. These flags are
recursively applied to cavities.
• The Option Expression and Module Expression fields are also synchronized.
• The Source ID of a linked connector is displayed in the Capital HarnessXC Edit
Connector dialog box as an attribute of the connector.
Modular Connectors
The Change Manager Apply ECO process offers the following support for modular connectors.
Note
This section details only that functionality that is specific to modular connectors. Refer to
the Connectors section, above, for a full description of connector functionality.
• Place - If the modular connector shell is not yet placed, it is placed at the bundle end
node if the connected bundle is already placed, else it is placed at the node coordinates.
Sub-connectors are placed at reference nodes, connected to the connector shell by zero-
length bundles.
o If none, or some, of the sub-connectors of the shell have been previously linked, the
connector shell is placed and a Topology Mismatch warning is displayed in the
connector shell’s Status field. The Apply Change Output Window displays a
message advising remedial action is taken to ensure that all internal objects are
linked.
o If the sub-connectors are already linked, the connector shell is placed and all sub-
connectors, along with the connector shell, are grouped to be a single modular
connector. The grouping information is obtained from the connector shell object of
the source data and the shellid attribute of the sub-connector objects.
• Link - The connector shell object can be linked to any parent connector using the
Source ID.
o If any of the component connectors are not linked, a Topology Mismatch is
displayed in the Status field for the connector shell.
o In cases where the connector shell is not linked, a Topology Mismatch is displayed
in the Status field on each of the linked sub-connectors.
• Unlink - Unlink the modular connector by clearing the Source ID from the connector
shell and all sub-connectors.
• Autolink - Only Name, ElecId, PartNumber and shellid are applicable to modular
connectors
Fixings
The Change Manager Apply ECO process offers the following support for fixings.
• Place - Appropriate fixings are created as specified by the type (a grommet is placed for
type Grommet, a clip for type Clip, and so on).
o If the fixing type is not specified, but the part number can be found in the library,
that part’s fixing type is used.
o If a matching part is found in the library, but the fixing type assigned to it differs
from that assigned to the source fixing, then the type assigned to the library part is
used.
o If a fixing type is not specified and no matching part number is found in the library,
a clip is placed as default, and Fixing is displayed in the Change Manager.
Note
If a subsequent source file is imported for the same harness, for those fixings
whose type has previously been determined, the correct type will still be
displayed.
o If the source data has a part number specified and the part is available in the library,
then it is assigned to the fixing created in the design. If the part is not found, the
fixing is still created as per the source data, and a warning related to the missing part
is displayed in the Status field. The fixing is created even if the source data does not
have a part number specified.
If the underlying bundle is not linked, the fixing will not be placed and an error is shown
in the Status field.
If the fixing has multiple locations then Unsupported Action is displayed for Place.
• Link - Link the objects by assigning the Source ID. If the fixing has multiple locations
then Unsupported Action is displayed. Also, if the fixing type is specified, only that
type is linkable. (a clip can only be linked to a clip, a grommet can only be linked to a
grommet). However, if the type is not specified, then a fixing is linkable to any of the
types.
• Unlink - Unlink the objects by clearing the Source ID. If the fixing has multiple
locations then Unsupported Action is displayed.
• Autolink - Only Name, Offset and PartNumber are applicable to fixings.
• Synchronize - Updates the fixing with the source data.
Insulations
The Change Manager Apply ECO process offers the following support for insulations.
• Place - Appropriate insulations are created as specified by the insulation type.
o Insulations with the same start and end nodes (after offset conversion and
approximation to multiples of bundle precision, as dictated by the source data) are
created in the same Capital HarnessXC insulation run.
o Insulation type is set as Untaped, Overlap Tape, Spiral Tape, Space Tape, Fixed
Tube, Fixed Cut-back Tube, Fixed Pulled-back Tube, Selected Tube, Selected
Cut-back Tube or Selected Pulled-back Tube as given by the subtype field.
• If the subtype field is not present, but the part number can be found in the library,
that part’s insulation type is used.
• If a matching part is found in the library, but the subtype assigned to it differs
from that assigned to the source insulation, the subtype assigned to the library
part is used.
• If the subtype field is not present and no matching part number is found in the
library, the insulation type is set as FixedTube for source insulation type Tube,
as OverlapTape for source insulation type Tape, and as SpotTape for source
insulation type SpotTape.
Note
If a subsequent source file is imported for the same harness, for those
insulations whose subtype has previously been determined, the correct
subtype will still be displayed.
o Insulations are placed into layers dictated according to the layer values in the source
data. Once placed, all source supplied insulation layer numbers are compared with
their Capital counterparts; a Property Mismatch is displayed if found to be different.
o If the part number is included in the source data, Place will search in the library for
the exact part (using a Tape or Tube filter) and if the part is found it is assigned to
the object. If the part is not found, a warning is displayed in the Status field and the
insulation is created as specified in the source data but without the library part
number.
o If the underlying bundles are not linked, the insulation will not be placed and an
error is displayed in the Status field.
o Spot Tape is placed at a location defined as the mid-point between the startLocation
and endLocation positions.
o If the incoming insulation has an insulation code assigned, and a matching code
exists within the current project, insulation layers are created as dictated by the code.
• Link - Link the objects by assigning the Source ID. If the insulation type is specified,
linking is possible only with same type. For example, a spot tape can only be linked to a
spot tape.
• Unlink - Clears the value in the selected Capital object’s External ID attribute, breaking
the link with the Source object.
• Autolink - Only Name, Offset, Length and PartNumber are applicable to insulations.
• Synchronize - Updates the linked object with the source data.
o An insulation is moved according to the start or end offset supplied in the source
data. This is done by repositioning the reference nodes. Rounding rules in Capital
HarnessXC are honored while updating offset values. If the end node is a structure
node, offset synchronization fails and an error message is displayed. If the insulation
ends happen to be in different linked bundle, they will not be moved across the
bundle.
o The part number specified in the source data is searched for in the library and if
found, is assigned to the insulation in the design (accordance with any defined
Change Policy) irrespective of whether it is already part assigned or not. If the part is
not found, then the existing part assigned to the insulation in the design will remain.
o If an insulation has been placed into a layer of an insulation run containing other
insulations, but has moved in a later iteration of the source data, the updated
insulation is removed from the insulation run and added to a new insulation run,
which is created if required.
o The Convoluted flag, Slit Tube flag, innerDiameter, numberTurns,
wallThickness, tapeThickness, overlap, insulationNote, optionExpression,
colorCode and materialCode fields are synchronized with the corresponding fields
in the Capital HarnessXC insulation.
o The innerDiameter value is mapped to the Width attribute in Capital HarnessXC.
o The wallThickness and tapeThickness fields are mapped to the Thickness value
depending on whether the insulation type is Tube or Tape.
o A Property Mismatch is returned if the offset, length, part number, user-defined
properties, innerDiameter, thickness, option expression, insulation note, overlap,
color or material are different.
o A Topology Mismatch is returned if all underlying bundles are not one-to-one
linked.
o The Source ID is displayed in the Edit Insulation dialog box attributes.
o If either the source insulation does not have an insulation code associated, or the
code does not exist in the current project, and the linked insulation run in the design
has an associated insulation code, a connectivity mismatch is reported, and the run
will need to be synchronized manually.
o Assuming the source protection has an insulation code associated, which also exists
within the current project:
• If the linked insulation run in the design has a different insulation code
associated, a connectivity mismatch is reported, and all existing insulation layers
(associated with the existing insulation code) are deleted, and recreated using the
source insulation code. The “Update” change policy assigned to the TypeCode
attribute is honored.
• If the linked insulation run in the design has the same insulation code, no other
attributes of the source protection are synchronized and no mismatches are
reported.
• If the linked insulation run has no insulation code associated, the source code is
applied to the run. No other attributes of the source protection are synchronized.
Wires
The Change Manager Apply ECO process offers the following support for wires.
• Place - Appropriate wires are created.
o If the source data has a part number specified and the part is available in the library,
then it is assigned to the wire created in the design. If the part is not found, the wire
is still created as per the source data, and a warning related to the missing part is
displayed in the Status field. The wire is created even if the source data does not
have a part number specified.
Multicores
The Change Manager Apply ECO process offers the following support for multicores.
• Place - Appropriate twisted or sheath multicore is created according to the multicore
type in the source data. Internal wires, shields and multicores are also placed. Shields are
placed as wires in Capital HarnessXC.
o If the source data has a part number specified and the part is available in the library,
then it is assigned to the multicore created in the design. If the part is not found, the
multicore is still created as per the source data, and a warning related to the missing
part is displayed in the Status field. The multicore is created even if the source data
does not have a part number specified.
o Route and wire ends are set on wires according to the source data.
o If all the underlying bundles are not linked, or wire pins are not resolved, then wires
are placed and a report message displayed in the Status field.
• Link - Link the multicores by assigning the Source ID. This is also set for internal wires
and multicores. Internal objects are linked after an alphanumeric sort on members is
performed.
• Unlink - Unlink the multicores by clearing the Source ID. This is also cleared for
internal wires and multicores.
• Autolink - Only Name, Electrical Id and PartNumber are applicable to multicores.
• Synchronize - Updates the linked object with the source data.
o A Topology Mismatch is returned if member wires or multicores are different in the
source data and target design.
o If a part is not assigned and there is an incoming part, then that part is searched in the
library and, if found, assigned to the object.
o If the target object’s part number is different from the source part number, the new
part is assigned if there is a Change Policy that allows for part number change. If no
Change Policy is assigned, a warning is displayed in the Status field and the
incoming part is not assigned.
o If enabled in Capital HarnessXC, user-defined properties can be synchronized.
o Cablelength, cablecoverthickness, cablematerial, cablecolor, cablespec, and so
on, are set with the values in the source data. ECO Change Manager also ensures
that attributes are not modified if a library attribute and part are assigned.
o A wire’s attributes and library part are synchronized as specified in the wire section.
o The Source ID is displayed as a multicore attribute in the Edit Multicores dialog
box.
Options
Source options are synchronized with project options.
• Options are not be listed in the Change Manager Apply ECO Dialog Box or Change
Manager Preview ECO Dialog Box.
• If any of the incoming options are not available in the project, a Missing Options
message is displayed on the selected harness’ Status field if linked and selected. You
can then perform the Synchronize action on the harness to import the new options into
the project.
• If the you have the Option Maintenance permission, the new options are imported to
the project, otherwise an error report is displayed.
Related Topics
Change Manager Preview ECO Dialog Box
Capture and Apply a Change Within an ECO
Change Manager Apply ECO Dialog Box
Harness Shape Parameters
The Export file chooser dialog box displays with a default file type of “Engineering
Change Order .eco”. Enter the required name for the export file and navigate to the
required location.
Related Topics
Exporting an ECO Design Change Record
Engineering Change Orders Dialog Box
Capture and Apply a Change Within an ECO
This chapter contains the following topics which explain how to perform various generic editing
actions on diagrams.
Common Edit Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Undoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152
Redoing an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Repeating an Action . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
Cutting and Pasting an Object in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Copying and Pasting an Object in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Deleting an Object in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156
Moving Objects from a Diagram to Another Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Selecting All Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Finding and Selecting Objects by Name. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Finding and Selecting Objects by Attribute or Property. . . . . . . . . . . . . . . . . . . . . . . . . . . 160
Specifying the Highlight Color of Selected Objects in a Diagram. . . . . . . . . . . . . . . . . . . 161
Using the Stroke Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161
Using Keyboard Shortcuts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Window Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Arranging Diagram Windows for Viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Using Tearable Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Zooming In and Out of Diagrams. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Panning Across a Diagram Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Undoing an Action
This topic explains how to use the undo facility to reverse up to the last 20 actions that have
been performed.
Procedure
1. Press Space Bar and enter Undo.
2. The previous action is undone and is added to the stored list of undone actions.
Note
If you perform a new action after you have undone one or more actions, this empties
the stored list of undone actions.
Related Topics
Redoing an Action
Repeating an Action
Cutting and Pasting an Object in a Diagram
Copying and Pasting an Object in a Diagram
Deleting an Object in a Diagram
Selecting All Objects in a Diagram
Redoing an Action
This topic explains how to 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.
Related Topics
Undoing an Action
Repeating an Action
Cutting and Pasting an Object in a Diagram
Copying and Pasting an Object in a Diagram
Deleting an Object in a Diagram
Selecting All Objects in a Diagram
Finding and Selecting Objects by Name
Finding and Selecting Objects by Attribute or Property
Specifying the Highlight Color of Selected Objects in a Diagram
Using the Stroke Tool
Repeating an Action
This topic explains how to 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.
Examples
A number of the component placement functions can be locked to enable the continuous
placement of the same component type until the tool is unlocked. For example, in Capital
HarnessXC, you can lock the Static Bundle function (press Space Bar and enter Static Bundle),
allowing you to keep drawing bundles (and confirming the entered length) without having to
reselect the Static Bundle action.
To lock a function, hold down the Shift key while selecting it, either from the menu or by
clicking the appropriate icon.
Related Topics
Undoing an Action
Redoing an Action
Cutting and Pasting an Object in a Diagram
Copying and Pasting an Object in a Diagram
Deleting an Object in a Diagram
Selecting All Objects in a Diagram
Finding and Selecting Objects by Name
Finding and Selecting Objects by Attribute or Property
Specifying the Highlight Color of Selected Objects in a Diagram
Using the Stroke Tool
• Text
• Circle
• Rectangle
• Curve
• Polygon
• Line
• Arc
• Comment Symbol
• Image
• Group
Procedure
1. Select the object.
2. Use one of the following actions:
• Press Space Bar and enter Copy
• Right-click on the selected entity and select Copy
• Use the key combination CTRL + C.
3. Either:
• Press Space Bar and enter Paste
• Use the key combination CTRL + V.
• Right-click on the selected entity and select Paste
4. Alternatively, select and drag the copy to the location where you want to paste it.
Results
A copy of the object is added to the diagram near the original object.
Related Topics
Undoing an Action
Redoing an Action
Repeating an Action
Cutting and Pasting an Object in a Diagram
Deleting an Object in a Diagram
Selecting All Objects in a Diagram
Finding and Selecting Objects by Name
Finding and Selecting Objects by Attribute or Property
Specifying the Highlight Color of Selected Objects in a Diagram
Using the Stroke Tool
Procedure
1. Select the object.
2. Use one of the following actions:
• Press Space Bar and enter Delete
• Right-click on the selected entity and select Delete
• Click the Delete key on your keyboard
3. The object is deleted.
Related Topics
Undoing an Action
Redoing an Action
Repeating an Action
Cutting and Pasting an Object in a Diagram
Copying and Pasting an Object in a Diagram
Selecting All Objects in a Diagram
Finding and Selecting Objects by Name
Finding and Selecting Objects by Attribute or Property
Specifying the Highlight Color of Selected Objects in a Diagram
Using the Stroke Tool
• Individual pins are not moved without the parent pinlist moving.
• Device connectors cannot be copied without their owning pinlist.
• Inline connectors cannot be split.
• A multicore will not be moved unless the entire multicore has been selected.
• A subset of an assembly cannot be moved. Only the entire assembly can be moved.
In Capital Integrator and Capital Topology, any objects graphically connected to the selected
objects are moved with them.
Procedure
1. Select the objects that you want to move either in the diagram window or in the Design
Browser Window. Right-click on the selected objects and select the Move To option
from the pop-up menu. Alternatively, right-click on the selected objects and select the
Actions > Move To menu option.
2. The Diagram Selection facility is displayed. From the list of diagrams, select the
diagram to which you want to move the objects and click the OK button.
3. The selected diagram is opened in the diagram window and the objects are moved to it
and placed in the same position that they occupied in the original diagram. You can then
move and the objects as required.
Note
Common Regular Expression search wildcards are:
.* searches for any character (.), zero or more times (*), $ matches at the end of a string
(e.g. searchme$), ^ matches at the beginning of a string (e.g. ^searchme)
4. Click OK.
5. Any objects with matching names are selected in the diagram and in any browser trees
where they appear.
Related Topics
Undoing an Action
Redoing an Action
Repeating an Action
Cutting and Pasting an Object in a Diagram
Copying and Pasting an Object in a Diagram
Deleting an Object in a Diagram
Selecting All Objects in a Diagram
Finding and Selecting Objects by Attribute or Property
Specifying the Highlight Color of Selected Objects in a Diagram
Using the Stroke Tool
Note
Common Regular Expression search wildcards are:
.* searches for any character (.), zero or more times (*), $ matches at the end of a
string (e.g. searchme$), ^ matches at the beginning of a string (e.g. ^searchme)
3. Click OK.
4. Any objects with matching values for the specified attribute or property are selected in
the diagram and in any browser trees where they appear.
Related Topics
Undoing an Action
Redoing an Action
Repeating an Action
Cutting and Pasting an Object in a Diagram
Copying and Pasting an Object in a Diagram
Deleting an Object in a Diagram
Selecting All Objects in a Diagram
Finding and Selecting Objects by Name
Specifying the Highlight Color of Selected Objects in a Diagram
Using the Stroke Tool
Note
The color that you have selected will also be used in other sessions of Capital design
tools when you start them.
Related Topics
Undoing an Action
Redoing an Action
Repeating an Action
Cutting and Pasting an Object in a Diagram
Copying and Pasting an Object in a Diagram
Deleting an Object in a Diagram
Selecting All Objects in a Diagram
Finding and Selecting Objects by Name
Finding and Selecting Objects by Attribute or Property
Using 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.
Window Controls
The following topics explain how to arrange open diagram windows and browser windows for
viewing and how to use the zoom and pan controls to change what you are viewing in a
window.
Arranging Diagram Windows for Viewing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170
Using Tearable Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Zooming In and Out of Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Panning Across a Diagram Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
• 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.
Related Topics
Using Tearable Tabs
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.
Related Topics
Arranging Diagram Windows for Viewing
Zooming In and Out of Diagrams
Panning Across a Diagram Window
• Zoom In
Increases the scale of the diagram so that objects appear larger.
Either:
o Press Space Bar and enter Zoom In
o Press Ctrl+Shift+=
o Press Alt+NumPad+
• Zoom Out
Note
You can activate the panning tool at any time by holding down the left mouse button
for at least a second. Once the tool is activated, you can drag the diagram canvas.
Related Topics
Arranging Diagram Windows for Viewing
Using Tearable Tabs
Zooming In and Out of Diagrams
The following topics explain how to add and edit graphical shapes and graphical objects in a
diagram.
Borders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Adding a Border to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Replacing a Border on a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Removing a Border from a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Graphic Drawing Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Drawing a Line in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Drawing a Rectangle in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Drawing a Polygon in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Drawing a Circle in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Drawing an Arc in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Drawing a Curved Line in a Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Adding Text Frames to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Adding a Picture to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Changing the Picture in an Image Frame . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Link or Embed Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Adding a Comment Symbol to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Resizing a Comment Symbol in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Adding Properties to a Graphical Shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Editing a Property Value of Graphical Shape. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Editing the Graphical Properties of a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Stretching a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Moving a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Deleting a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Grouping Graphical Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Ungrouping Graphical Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Controlling the Layering Order (Z-Order) of Graphical Shapes Objects and Images . . . . 189
Graphics Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Adding a Graphics Point to a Graphical Shape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Deleting a Graphics Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Grip Points . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Adding a Grip Point to an Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Deleting a Grip Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Borders
The following topics explain how to add and edit the border in a diagram.
Adding a Border to a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Replacing a Border on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
Removing a Border from a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
3. To insert a waypoint into the line, click once again on the diagram, otherwise, place the
second end of the line by double-clicking or by pressing the Enter key.
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).
3. Click once on the diagram to place further corners and double-click on the diagram or
press the Enter key to place the last corner.
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).
3. Drag the cursor away from the center and click once on the diagram to place the edge of
the circle.
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).
Procedure
1. Press Space Bar and enter Curve. The cursor changes to .
2. Click on the diagram to place the first end of the curved line.
3. Click once on the diagram to place further points along the curve and double-click on
the diagram or press the Enter key to place the second end of the curved line.
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).
2. Click on the diagram to place the first corner of the text frame.
3. Click on the diagram to place the opposite corner of the text frame. The Add Text
Dialog Box is displayed.
4. Enter the text that you want to display in the box at the bottom of the Add Text dialog
box.
5. Click OK. The text frame and text is added to the diagram.
Note
If the text is not displayed, the text frame is not large enough for the text. To increase
the size of the text frame, place the mouse cursor over a corner of the frame so that
the stretch icon is displayed, hold down the left mouse key and drag the corner.
In Capital Logic, if you click once on a pin, connector or device before clicking to start
drawing the graphic, the graphic is automatically associated with the object (that means,
if the object is moved, the graphic moves with it).
2. Click on the diagram to place the first corner of the image frame that will contain the
image.
3. Click on the diagram to place the opposite corner of the image frame. The Image
Selection Dialog Box is displayed.
4. Select the required radio button to either link or embed the image (see Link or Embed
Images). If you are adding an image to a non-comment symbol in Capital Symbol, these
options do not display and the image will be added using the Link to Image method by
default.
5. Select the image file that you want to add.
For linked images, only files and sub-folders from the Images folder area available for
selection. You cannot navigate to another folder location. For embedded images, you
can navigate to any location on your file system.
6. Click Select. The image frame and picture are added to the diagram. The picture is
scaled to fit the image frame.
Note
In Capital Logic, if you click once on a pin, connector or device before clicking to
start drawing the graphic, the graphic is automatically associated with the object
(that means, if the object is moved, the graphic moves with it).
Related Topics
Changing the Picture in an Image Frame
Link or Embed Images
Controlling the Layering Order (Z-Order) of Graphical Shapes Objects and Images
Link to Image
If you choose this option, the selected image displays in the diagram via a link to the image file
in the Images folder (as specified in the system preferences for Paths in Capital Project).
Only the path to the image file is saved with the diagram and not the image file itself. Once
saved, the diagram will not display the image if, for example, the file is moved or you export the
design to another database where the exact file and path are not present on the target system.
All diagrams that link to an image file are automatically updated if the image file is changed.
Embed Image
If you choose this option, the selected image is embedded in the diagram. This removes the need
to maintain a link to the path of the inserted image, as is the case with a linked image, because
the image data is stored with the diagram itself.
This option is available in Capital HarnessXC, Capital ModularXC, Capital Logic, Capital
Integrator, Capital Topology, Capital Publisher, and Capital Symbol (where images can be
embedded in comment symbols).
Related Topics
Image Selection Dialog Box
Adding a Picture to a Diagram
Changing the Picture in an Image Frame
Controlling the Layering Order (Z-Order) of Graphical Shapes Objects and Images
Procedure
1. Press Space Bar and enter Comment Symbol.
The Symbol Selection Dialog Box is displayed.
2. In the Symbol Selection tree, select the comment symbol.
Note
Once a comment symbol has been placed, you can refresh it with the latest
version of the symbol (reflecting any changes that may have been made) by
right-clicking on it and selecting Update Symbol.
Related Topics
Resizing a Comment Symbol in a Diagram
Procedure
1. Move the mouse cursor over the symbol; a bounding box is displayed.
2. Move the mouse cursor over a corner of the bounding box so that the stretch icon ( ) is
displayed, hold down the mouse button and drag the corner to resize the symbol. The
symbol is scaled proportionally along both the X-axis and Y-axis.
Related Topics
Adding a Comment Symbol to a Diagram
5. Enter the name of the property and click OK. The property is added to the Properties
table on the General tab.
6. In the Value field, enter the value of the property and specify whether the value can be a
string, integer or float in the Type field.
7. Click OK.
8. The value is displayed next to the graphical shape on the diagram.
4. On the Graphical tab, edit the values as required and click OK.
5. The appearance of the graphical shape on the diagram changes accordingly.
3. Hold down the left mouse button and drag the graphics point to stretch the shape to its
new location.
• Bring To Front
Brings the selected shapes to the front of the overlapping shapes.
• Send To Back
Sends the selected shapes to the back of the overlapping shapes.
• Bring Forward
Brings the selected shapes one layer forward in the overlapping shapes.
• Send Backward
Sends the selected shapes one layer backward in the overlapping shapes.
Prerequisites
• The graphical shapes must have been added to the diagram and are overlapping each
other.
Procedure
In the diagram window, select one or more graphical shapes and either:
• right-click 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.
Graphics Points
The following topics explain how to add graphics points to graphical shapes in a diagram and
how to delete them.
A graphics point is a point at which you can stretch a graphical shape to resize or reshape it.
Procedure
1. Select the graphical shape on which the graphics point is located.
2. Press Space Bar and enter Delete graphics point.
Grip Points
A grip point is point that you add to a wire or net in Capital Logic, a bundle in Capital Integrator
and a bundle in Capital Harness XC. In Capital Symbol, it can be added to an internal link. It
divides the object into graphical sections that can be resized and reshaped.
The following topics explain how to add a grip point to an object and how to delete it.
Procedure
1. Select the object on which the grip point is located.
2. Either:
• Press Space Bar and enter Delete grip point
or
• Right-click on the selected entity and select Grip Point > Delete
The cursor changes to .
This chapter contains the following topics which explain how to perform layout-related actions.
Grouping Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Creating a Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Moving a Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Ungrouping Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Aligning Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Distributing Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Flipping Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Rotating Objects in a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Rotating Objects Around a Specified Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Defining Rotation Increments. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Free Rotating Text Decorations, Comment and RED Symbols or Graphical Objects . . . . 204
Example of Applying Styling on Rotated or Flipped Objects . . . . . . . . . . . . . . . . . . . . . . 205
Pivoting Text About its Axis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Setting Snap To Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Setting Grid Defaults for a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Manual Table Splitting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209
Using Japanese Text on a Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210
Creating a Group
You can group objects as single entities.
Procedure
1. Select the objects. Either:
• Hold down the Ctrl key on your keyboard and click the objects.
• Click at one corner of the area that encloses the objects, hold down the mouse button
and drag the cursor to define an enclosing window selection.
2. Either;
• Press Space Bar and enter Group
• Right-click and select Group
A new highlight is applied to all of the selected objects, showing the outside limit of the
group.
Moving a Group
Grouped objects can be dragged to a new position on the canvas as a single entity. Clicking to
select any object in the group results in the whole group being selected, which can then be
moved by clicking and dragging the outside border.
Ungrouping Objects
It is not possible to remove a single object from a group. Instead, the collection of objects must
first be ungrouped, then a new group created minus the unwanted object.
Procedure
1. Select the group by clicking on any object within it.
2. Either:
• Press Space Bar and enter Ungroup
• Right-click and select Ungroup
The group highlight disappears, leaving each object independently selectable.
Related Topics
Aligning Objects in a Diagram
Distributing Objects in a Diagram
Note
If an object has pins, they move with the object. If a device and connector are connected,
they move together but the alignment depends on which of those objects has been selected.
If conductors are connected to an object, they move to maintain the connectivity.
Procedure
1. Select the objects.
2. Either:
• Hold down the Ctrl key on your keyboard and click the objects.
or
• Click at one corner of the area that encloses the objects, hold down the mouse button
and drag the cursor to define an enclosing window selection.
3. Press Space Bar and enter Align, then select the appropriate action:
• Align Left ( )
After:
• Align Right ( )
After:
• Align Top ( )
After:
• Align Bottom ( )
After:
• Align Vertically ( )
After:
• Align Horizontally ( )
Before:
After:
Note
If an object has pins, they move with the object. If a device and connector are connected,
they move together but the alignment depends on which of those objects has been selected.
If conductors are connected to an object, they move to maintain the connectivity.
Procedure
1. Select the objects. Either:
• Hold down the Ctrl key on your keyboard and click the objects.
or
• Click at one corner of the area that encloses the objects, hold down the mouse button
and drag the cursor to define an enclosing window selection.
2. Press Space Bar and enter Distribute, then select the appropriate action:
• Distribute Horizontally ( )
The left-most and right-most objects do not move. If there is enough space, the other
selected objects move so that there is an equal horizontal distance between each of
them. Otherwise, the objects move so that there is an equal horizontal distance
between their center points. No objects move vertically.
Before:
After:
• Distribute Vertically ( )
The top and bottom objects do not move. If there is enough space, the other selected
objects move so that there is an equal vertical distance between each of them.
Otherwise, the objects move so that there is an equal vertical distance between their
center points. No objects move horizontally.
Before:
After:
Procedure
1. Select one or more objects that you want to flip.
Note
If you select multiple objects, they are flipped as a group around one axis.
Procedure
1. Select one or more objects that you want to rotate.
Note
If you select multiple objects, they are rotated as a group around one point.
Note
All text labels are orientated as part of the flip process to ensure that they can be read
correctly.
Procedure
1. Press Space Bar and enter Set Rotation Degrees.
2. Set the Minor Rotation Increment used for finer grained rotational control. Default value
is 1 degree.
3. Set the Major Rotation Increment used for coarser grained rotational control. Default
value is 5 degrees.
4. Click on the OK to confirm your settings.
rotate the object clockwise by a minor increment. Press Ctrl + Shift + < to rotate
counter-clockwise.
or
• Press CTRL and move the clickable scroll wheel on your mouse forwards or
backwards to rotate the object clockwise or counter-clockwise by a major increment.
For finer grained control press CTRL + Shift and move the clickable scroll wheel
on your mouse forwards or backwards to rotate the object clockwise or counter-
clockwise by a minor increment.
Results
• The object rotates at the pre-defined degree increment around their center point.
Related Topics
Defining Rotation Increments
Prerequisites
In this example, styling has been defined for a device as follows:
Procedure
1. Define styling for a device as follows:
• If that device is flipped about the horizontal axis and styling is applied to it again, all
decorations respect the flip as in this example:
Related Topics
Flipping Objects in a Diagram
Rotating Objects in a Diagram
Procedure
1. With the diagram open, press Space Bar and enter Snap to Object.
Note
Snap to Object overrides Snap to Grid except for electrical objects. In this case
Snap to Grid settings are also retained.
Note
See the Diagram Styling User Guide for more information about all aspects of table
styling.
Caution
You can export a file with Japanese text and import it into a non-Japanese
operating system. However, you cannot make changes to that data and re-import
it into the Japanese operating system. In this case, the Japanese text remains intact
but some things, such as the diagram name, are no longer readable in the Japanese
operating system.
This chapter contains details of how to apply rules and constraints to objects.
Overview of Rules and Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Object Rule Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Editable Elements in Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Defining Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Assigning a Rule or Constraint to an Object or Design . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Usage Example - Using a Null Value in a Constraint . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
• In Capital Integrator, you can set rules and constraints to control how the system places
devices in slots, synthesizes wiring and sets properties/attributes for objects.
• In Capital Logic, you can use one constraint to set properties and attributes on objects.
• In Capital HarnessXC, you can set rules and constraints to control wire paths on a
harness diagram and to enable harness processing to optimize a harness design based on
preset criteria.
Note
If you are using rules and constraints in Capital Integrator, see the Rules and
Constraints section of the Capital Integrator User Guide for more detailed
information and usage examples.
The generative flow (and wiring synthesis in particular) rely on user-configured constraints to
control the results of the automated process.
Constraints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Object Rule Hierarchies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214
Constraints
A constraint is a statement that can be applied to a whole design, or to individual objects within
a design. It can be applied as an individual constraint or as part of a rule.
For example (in Capital Integrator):
If this example constraint were set for a slot, the system would not place a device with a Name
property of Battery in that slot.
You use constraint templates to define a constraint. For full lists of the standard constraint
templates available for specific design applications, see the following:
The design rule check Missing Custom Constraint Check can be run to report on any custom
constraints that have been defined for an object, but are no longer loaded.
Related Topics
Creating a Strategy for Constraint Definition in Capital Integrator
Assigning a Rule or Constraint to an Object or Design
Rules
A rule can consist of one constraint or a groups of constraints and can be applied to a whole
design or to individual objects within a design. You can define rules from within the design
applications or from within Capital Project. 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.
Note
In Capital Logic a rule can be applied to a whole design only.
A rule can contain (reference) other rules and therefore include their constraints.
You can create rules at a system level and import the required rules into a project when
necessary. All rules are available to every project created within Capital Project.
Related Topics
Defining Rules
Assigning a Rule or Constraint to an Object or Design
Note
For more detailed information about object rule hierarchies and hierarchical object rule
resolvers in Capital Integrator, see Object Rule Hierarchies in Capital Integrator in the
Capital Integrator User Guide.
Related Topics
Editable Elements in Constraints
Defining Rules
Assigning a Rule or Constraint to an Object or Design
• Only/Don't
Select Only or Don't from the drop-down list.
• Do
Select Do or Don't from the drop-down list.
• Expression
When you click on this text, a dialog box is displayed where you define an option
expression. You can type the expression manually or you can click the ellipsis (...) to
open the Edit Option Expression facility.
• Name
By default, this refers to the Name attribute of an object. When you click on this text, a
dialog box is displayed. You can select to reference either an attribute or property and
you select the specific attribute or property from the dropdown list.
• Slot Name
When you click on this text, a dialog box is displayed. If the Use Slot Name box is
checked, the Name attribute of a slot is used. If you uncheck the box, you can enter
another string.
• ObjectName
When you click on this text, a dialog box is displayed. If the Use Object Name box is
checked, the Object Name property is used. If you uncheck the box, you can enter
another property name.
• Ruled Object Name
When you click on this text, a dialog box is displayed. If the Use Ruled Object Name
box is checked, the value for the Object Name property is used. If you uncheck the box,
you can enter another property value.
• Value
This is used typically when you want to use rules to add properties and attributes to
wires, splices and multicores.
Select one of the following:
o Literal
This means it is a literal value. Enter the value string in the box. You can use
wildcards in this string. Click the OK button to exit the dialog.
o Attribute
This means the value is derived from the value of an attribute on the functional
signal or multicore. Select the attribute from the drop-down list in the box. Click the
OK button to exit the dialog.
o Property
This means the value is derived from the value of a property on the functional signal
or multicore. Enter the property name in the box. Click the OK button to exit the
dialog.
• Num
Enter an integer.
• Object
Select an object type from the drop-down list.
• Object Type
Select an object type from the list that is displayed when you click on this.
• Spec
Enter a specification string.
• .*
This is the same as a literal value string but is a wildcard by default.
• Wire Part Specification
Select WireMaterialCode, WireColor or WireSpec from the drop-down list.
• AttrOrProp
Select either Attribute or Property. For an attribute, select the attribute name from the
drop-down list. For a property, enter the property name in the box or select from the list
of pre-defined property names in the drop-down list. Click the OK button to exit the
dialog.
If a constraint contains a clause for matching it to particular objects (for example, Object
Name = PropValue), you can also edit the match operator that is = by default. The
available operators are:
= Equal to
!= Not equal to
< Less than
> Greater than
<= Less than or equal to
>= Greater than or equal to
For example:
Only route signals with property matching Object Name != Signal01
In this example, only signals that do not have a value of Signal01 for the Object Name
property will be routed.
Do place devices with property matching Rating >= 7.5 here
In this example, only devices that have a value greater than or equal to 7.5 for the
Rating property will be placed.
When specifying a property value string in a constraint, you can use wildcards.
For example:
.* is all possible strings
si.* is any string starting with si.
If you are using Wire Part Specification constraints and Terminal Type Specification
constraints and you are using wildcards when defining property value strings, prioritized
pattern matching is used if there are two constraints of the same type on an object. This
means that if two constraints of the same type can both apply to one signal, the
constraint most specific to that signal will be used.
There are three levels of match quality:
o Level 1 - a broad default. For example: ObjectName = .*
o Level 2 - a refined wildcard. For example: ObjectName = sig.*
o Level 3 - a specific match. For example: ObjectName = signal
Level 3 overrides level 2 and level 2 overrides level 1.
If there is a situation where the wildcards in constraints of the same type match, an error
will be generated. For example, the following situations would generate an error:
o ObjectName = .* in one Wire Part Specification constraint on an object and
ObjectName = .* in another Wire Part Specification constraint on the same object.
o ObjectName = si.* in one Terminal Type Specification constraint on an object and
ObjectName = sig.* in another Terminal Type Specification constraint on the
same object.
o ObjectName = signal in one Wire Part Specification constraint on an object and
ObjectName = signal in another Wire Part Specification constraint on the same
object.
Related Topics
Overview of Rules and Constraints
Defining Rules
Assigning a Rule or Constraint to an Object or Design
Defining Rules
This topic explains how to define a rule that can be used in design applications.
Note
If you are using rules and constraints in Capital Integrator, see the Rules and Constraints
section of the Capital Integrator User Guide for more detailed information and usage
examples.
Procedure
1. In a design application, press Space Bar and enter Rules; the Define Rules Dialog Box is
displayed.
2. Click New; the Rule Name dialog is displayed.
3. Specify the name of the rule and click OK; the rule name is added to the Rules window.
4. Specify the constraints that you want the rule to include:
• To add constraints, click the Add Constraint ( ) button; the Constraint Selection
Dialog Box is displayed. Select the constraints and click OK.
• To reference another rule (and therefore add its constraints), click the Add Rule
Reference ( ) button; the Rule Selection Dialog Box is displayed. Select the rule
and click OK.
The constraints are added to the Constraints window.
5. Edit the green and red elements in the constraints so that they contain the required
values. See “Editable Elements in Constraints” on page 214 for a list of editable
elements.
Note
If you have added a rule reference, the rule name is displayed. Click on it to display
the constraints included in it. You cannot edit them here.
Procedure
1. Open the Properties dialog for the object or design and click the Rules tab; the Rules
Tab in Properties Dialog Box displays the rules and constraints that have been assigned
to the object already.
Note
It also displays the rules and constraints that have been assigned to any objects to
which the current object belongs (for example, a slot belongs to a harness, a harness
belongs to a design).
2. Specify the rules and constraints that you want to assign to the object:
• To add constraints, click the Add Constraint ( ) button; the Constraint Selection
Dialog Box is displayed. Select the constraints and click OK.
• To assign a rule (and therefore assign its constraints), click the Add Rule Reference
( ) button; the Rule Selection Dialog Box is displayed. Select the rule and click
OK.
The constraints are added to the Constraints window.
3. Edit the green and red elements in the constraints so that they contain the required
values. See “Editable Elements in Constraints” on page 214 for a list of editable
elements.
Note
If you have added a rule, the rule name is displayed. Click on it to display the
constraints included in it. You cannot edit them here.
If you want to use a customized version of a constraint (if any have been made available
via Extensibility Plugins), click the ( ) icon next to it and select the customized version
from the dropdown list.
Results
The constraints will be taken into account when any related actions are performed.
Related Topics
Overview of Rules and Constraints
Editable Elements in Constraints
Defining Rules
Procedure
1. In Capital Integrator, right-click on the diagram name in the Design Browser (Plane tab)
at the bottom left of the application window and select Properties; the Plane: <Plane
Name> dialog box is displayed.
2. Click the Rules tab; the tab displays any rules or constraints that have been applied to
the diagram already.
3. Click the Add Constraint ( ) button; the Constraint Selection dialog box is displayed.
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 only edit graphical properties.
Note
You cannot edit equipotential nets as part of a multiple selection.
If you select a conductor (net or wire) or bundle from a browser window, all segments
are selected automatically.
If you want to select a closed graphic, you must click on the border (outline) of the
graphic.
2. Right-click one of the selected segments or objects in the diagram window or a blank
area in the diagram browser window in Capital Logic or a blank area in the Topological
Plane Browser Window in Capital Integrator and select Properties from the pop-up
menu that is displayed.
Results
The Edit Properties facility is displayed.
The Edit Properties facility that is displayed, depends on the object that you right-click.
In Capital Logic/Capital Publisher:
Edit Properties facilities for objects can contain the following tabs depending on the object
selected (if you have selected multiple objects, any changes to the parameters on these tabs
apply to all selected objects):
• General (see “Editing an Object's General Properties” on page 228)
• Graphical (see “Editing an Object's Graphical Properties” on page 253)
• Symbol
The Symbol tab displays information detailing if the selected symbol instance is up-to-date by
showing its UID, modification timestamp and time, as well as which library it originated from.
• Properties (see “Adding a Property to an Object” on page 234)
The Edit Properties facilities for devices, connectors, blocks and splices includes the following
tab:
• Parameters
The Edit Properties facilities for modular connectors includes the following tab:
• Modular
See Assigning Connector Positions Using the Modular Tab in the Capital Logic User Guide.
• The Edit Properties facilities for conductors include the following tab:
• Ports
The Edit Properties facility for object name text displays the following tab:
• Text
The Edit Properties facility for a shared object and cross-reference text displays the following
tabs:
• Cross-references
See Cross-reference Rules for Pins in the Capital Logic User Guide.
• Scopes
See “Applying Scopes to a Project or Design” on page 265.
In Capital Integrator:
Edit Properties facilities for all objects (including symbol graphics) contain the following tabs
(if you have selected multiple objects, any changes to the parameters on these tabs apply to all
selected objects):
• General (see “Editing an Object's General Properties” on page 228)
• Graphical (see “Editing an Object's Graphical Properties” on page 253)
• Rules (see “Assigning a Rule or Constraint to an Object or Design” on page 219)
• Properties (see “Adding a Property to an Object” on page 234)
The Edit Properties facility for a signal displays the following tabs:
• Variance (see “Specifying Option-Specific Values for Net Attributes and Properties” on
page 249)
• Scopes
See “Applying Scopes to a Project or Design” on page 265.
In Capital Symbol:
The Edit Properties facility for symbol graphics and borders includes the following tabs:
• Graphical (see “Editing an Object's Graphical Properties” on page 253)
• Properties (see “Adding a Property to an Object” on page 234)
The Edit Properties dialog box for a border, Drill Point Datum or Fixture Placement datum
includes the following tabs:
• General (see “Editing an Object's General Properties” on page 228)
Note that the General tab for a border in Capital Symbol allows you to specify
placeholders for design information that is then displayed automatically when you add
the border to a Capital Logic or Capital Integrator diagram. See Adding Information
Placeholders to a Border in the Capital Symbol User Guide.
The General tab for a drill point datum or a fixture placement datum in Capital Symbol,
allows you to specify various attributes for use when using the datums with Capital
FormboardXC fixtures.
• Paper Layout (see Editing the Paper Layout Properties of a Border in the Capital
Symbol User Guide) - This provides information about the paper size and usable area
within the border.
Note
To edit the general properties of a border in Capital Symbol, you must right-click to
the side of the border in the diagram window to access the Edit Properties facility.
Results
The object's General Properties facility displays.
See the following topics for details of actions that can be performed using this dialog:
Related Topics
Specifying the Name Property of an Object
Editing the Display-details of the Object's Short Description
Object Attributes
Adding a Property to an Object
Deleting an Existing Property from an Object
Editing a Bundle's Length in Capital Integrator
Assigning a New Library Part to an Object
Updating an Object's Library Part
Unassigning a Library Part from an Object
Viewing the Library Part Details for an Object
Defining Specification Attributes for a Conductor
Specifying the Slot Type
Assigning/Editing an Object's Options
Assignation of Module Codes to Capital Logic Components
Associating a Block with a Design (Capital Logic only)
Specifying a Part Number for a Harness Level in Capital Integrator
Editing the Harness Levels on which a Wire Exists
Editing the Offset of Bundle Region Nodes from Bundle Ends
Note
With the exception of pins, you can rename an object to have the same name as
another object in the same diagram. If you do this, the name is displayed in red and a
warning is displayed when you click the OK button.
If you are editing the properties of a multicore indicator, the multicore name is displayed
in the Name field. If you are editing the properties of a signal in Capital Integrator, 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 lists only the 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. 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 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. Check the Visible box if you want the specified name to be displayed with the object in
the diagram.
The name is displayed once for each object. However, in the case of conductors, you can
display the name next to more than one segment of the conductor. If name text has been
added to segments previously and has not been deleted, checking the Visible box will
display the name text for each instance of name text that has been added.
4. Click the Edit Attributes button to display the Edit Name Text Attributes Dialog
Box where you can set the following attributes for the name that is displayed on the
diagram:
• Font
Select the font type for the text and whether the text is plain, bold, italic or bold/
italic. Mandatory.
• Height
Specify the height of the text and select the unit of measurement from the dropdown
list. Mandatory.
• Color
To specify the color of the text, select a color from the dropdown list; it is previewed
in the window to the right of the field. Mandatory.
As well as color names, the list contains the following options:
o Default
The default color used for text by the system.
o Background
The same color used for the background of the diagram. The color changes when
the background color is toggled.
o Foreground
If the diagram background is white, the text is black, and vice versa.
o Manual
The Choose Text Color dialog is displayed, where you can select a color.
• Opaque
Select whether object lines are visible behind the text frame boundary box, (un-
selected), or are not visible behind the text frame boundary box, (selected).
Mandatory.
• Rotation
By default this is 0 for the text to run horizontally (left to right). Enter a different
value manually or select a value from the dropdown list, for example, 270 for the
text to run vertically (bottom to top). Mandatory.
• Auto Flip
If selected, the text flips automatically so that it is never displayed upside down
when it is rotated or flipped. If not selected, a flip or rotation can result in the text
being displayed upside down.
• Balloon Shape
Specify the balloon shape that will enclose text on a diagram. The thickness of the
encasing balloon is controlled by setting the BalloonLineThickness parameter in
Design Settings. The color of the balloon automatically matches the color setting for
the text within it.
Select available balloon styles from the dropdown list. These include:
o None
o Circle
o Rectangle
o Triangle
o Oval
o Rounded Rectangle
o Hexagon
Note
Adding a balloon shape to a diagram automatically disables the Layout
options “Clip Text to Bounding Box” and “Shrink to Fit”.
• Justification
Specify the position of the text within the text frame. Mandatory.
• Layout
The following set of options are available to control the layout of the text within its
frame.
o Clip Text to Bounding Box
If selected, specifies that the text is clipped at the edge of its bounding box.
o Shrink to Fit
If selected, specifies that the font of the text reduces as necessary so that the text
fits in its bounding box.
o Allow Text to Overflow
If selected, specifies that the text ignores the edge of its bounding box and flows
out of it.
o Wrap text
Specifies whether the text wraps onto multiple lines when it reaches the edge of
the text bounding box (selected) or whether the text ignores the bounding box
and continues on one line (unselected). When this is selected, if a word is too
long to fit on a single line, it is wrapped by character. Mandatory.
• Preview
Displays an preview of an example text string formatted using the currently selected
settings. Mandatory.
5. Click the OK button to exit the Edit Name Text Attributes dialog box.
Procedure
1. If the 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. Check the Visible box next to
the Short Description field if you want to display the short description.
2. Click the Edit Attributes button to display the Edit Name Text Attributes Dialog
Box where you can set the following attributes for the name that is displayed on the
diagram:
• Font
Select the font type for the text and whether the text is plain, bold, italic or bold/
italic. Mandatory.
• Height
Specify the height of the text and select the unit of measurement from the dropdown
list. Mandatory.
• Color
To specify the color of the text, select a color from the dropdown list; it is previewed
in the window to the right of the field. Mandatory.
If the object does not have attributes, there is a Properties section on the General tab of the
Edit Properties dialog.
Procedure
1. Right-click on the object and select Properties; the Edit Properties dialog is displayed.
2. Click either the Properties tab or General tab as appropriate. Under the Properties
section, click New; the New Property dialog is displayed. In the Property Name box,
either select a property name from the drop-down list or enter the name of a new
property and click the OK button.
Note
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 a the
property can be specified. If you enter a property value that is not valid in Capital Logic
or Capital Integrator, a warning is generated.
3. The property is added to the properties box. In the property's row, click the following
columns to change their values:
• Name - the name of the property. This box cannot be edited.
• 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:
o String - a mixture of letters, numbers and special symbols.
o Integer - a whole number.
o Float - a decimal number.
• Editable (only in Capital Symbol) - check the box if you want the Value and Type
fields to be editable in other applications.
• Master (only in Capital Symbol) - if the visibility of this property on the symbol is
defined both here (using the Visible and Attributes settings) and as a property
decoration in a style set, this specifies whether the settings here or the settings in the
style set take priority when the symbol is placed in a diagram.
o symbol
If the Override Symbol Styling setting is selected in the style set applied to a
diagram, symbol specifies that only the visibility of the property (that is, whether
it is displayed on the diagram) is dictated by the style set. The font of the
property value is dictated by the settings here and the position of the property
value is dictated by where you position the property value on the symbol.
If the Override Symbol Styling setting is not selected, then the visibility and
font of the property value are dictated by the settings here and the position of the
property value is dictated by where you position the property value on the
symbol.
o style
If the Override Symbol Styling setting is selected in the style set applied to a
diagram, style specifies that:
Where a property is defined on a symbol and it is also styled in the style set, the style set
dictates the visibility, font and position of the property value in the diagram.
Where a property is defined on a symbol but is not styled in the style set, it is not
displayed in the diagram.
See the Override Symbol Styling section in the Capital Diagram Styling User Guide
for further information about that setting. The effect of that setting combined with the
Master setting for a property on a symbol is summarized in the table below.
• Visible - check the box if you want the specified Value to be displayed with the
object on the design. If style set options have been defined for the property, those
options are used to define the appearance of the value. Otherwise, the Attributes
defined in this table define the appearance.
• Attributes - click Edit to display the Edit Text Attributes facility where you can
set the following attributes for the Value text that is displayed for this property on
the diagram:
• Font
Select the font type for the text and whether the text is plain, bold, italic or bold/
italic. Mandatory.
• Height
Specify the height of the text and select the unit of measurement from the dropdown
list. Mandatory.
• Color
To specify the color of the text, select a color from the dropdown list; it is previewed
in the window to the right of the field. Mandatory.
As well as color names, the list contains the following options:
o Default
The default color used for text by the system.
o Background
The same color used for the background of the diagram. The color changes when
the background color is toggled.
o Foreground
If the diagram background is white, the text is black, and vice versa.
o Manual
The Choose Text Color dialog is displayed, where you can select a color.
• Opaque
Select whether object lines are visible behind the text frame boundary box, (un-
selected), or are not visible behind the text frame boundary box, (selected).
Mandatory.
• Rotation
By default this is 0 for the text to run horizontally (left to right). Enter a different
value manually or select a value from the dropdown list, for example, 270 for the
text to run vertically (bottom to top). Mandatory.
• Auto Flip
If selected, the text flips automatically so that it is never displayed upside down
when it is rotated or flipped. If not selected, a flip or rotation can result in the text
being displayed upside down.
• Justification
Specify the position of the text within the text frame. Mandatory.
• Layout
The following set of options are available to control the layout of the text within its
frame.
• Clip Text to Bounding Box
If selected, specifies that the text is clipped at the edge of its bounding box.
• Shrink to Fit
If selected, specifies that the font of the text reduces as necessary so that the text fits
in its bounding box.
• Allow Text to Overflow
If selected, specifies that the text ignores the edge of its bounding box and flows out
of it.
• Wrap text
Specifies whether the text wraps onto multiple lines when it reaches the edge of the
text bounding box (selected) or whether the text ignores the bounding box and
continues on one line (unselected). When this is selected, if a word is too long to fit
on a single line, it is wrapped by character. Mandatory.
• Preview
Displays an preview of an example text string formatted using the currently selected
settings. Mandatory.
4. Click OK to apply the specified property values and exit the facility.
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
If the object does not have attributes, there is a Properties section on the General tab of the
Edit Properties dialog.
Procedure
1. Right-click on the object and select Properties; the Edit Properties dialog is displayed.
2. Click either the Properties tab or General tab as appropriate. Under the Properties
section, select the property and click Delete; the property is removed from the object.
3. Click OK to apply the change and exit the dialog.
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. Check the Override box
2. Edit the Length to the required value.
Prerequisites
• Footprint Library Parts
A library part with a footprint may, or may not have a symbol associated with it in
Capital Library. In either case, you can assign the library part to existing devices
(including shared devices) in a Capital Logic diagram.
If the library part has device connectors, device connectors are added to the device in
Capital Logic. In the case of a shared device, the device connectors are added to the
shared instances.
If a library part has a symbol associated with it, the graphical representation of the
device in Capital Logic does not change to the symbol when you assign that library part
to it.
• Library Part Usage on Shared Objects in Capital Logic
When a library part is assigned to a shared pin list, if the number of pins/cavities on the
library part is greater than the number of pins on the pin list, the number of pins
necessary to account for difference is added to the shared pin list.
When a library part is assigned to a shared device, if you have selected a symbol for the
library part, that symbol is added to the shared device and you are presented with a
dialog to map shared pins to the symbol pins.
• Library Part Usage in Capital Integrator
Library parts on slots that are included with a harness. If a slot has been included with a
harness, a library part can be assigned to the underlying physical connector. To do this,
you continue as though assigning a library part to the slot but the library part is really
assigned to the connector.
o Footprint Library Parts
In Capital Logic 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.
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 virtual connectors in a slot that has such a library part assigned.
o 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.
o Parts on Specialized Connectors and Generalized Connectors
You can assign a library part to a virtual connector or inline connector half
(generalized connectors). If you do this, you cannot use the Refine
Connector facility to define specialized connectors.
If you have defined specialized connectors for a generalized connector, you cannot
use the Edit Properties facility to assign a library part to the generalized connector.
If you want to do this, you must delete any bundle fanouts that you have created for
it.
If you have defined specialized connectors, you can use the Refine Connector
facility (see Refining Connectors in the Capital Integrator User Guide) to assign
library parts to the individual specialized connectors. If a specialized connector has
been defined by a footprint in Capital Logic, 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 an
equal or greater number of cavities to the device in the design.
• Editing Multiple Objects Simultaneously
If you have selected multiple objects with different library parts, Multiple Part
Numbers is displayed at the top of the Library Part section. You can only remove the
library part associations in this scenario.
If you are adding a library part to multiple objects, you will have to associate pins with
each object. In addition, the information passed to the library part selector will be about
the lowest common denominator aspects of the objects. This means, if you have selected
a 4-pin device and a 6-pin device, you can select only library parts with a minimum of 6
pins.
You cannot edit library parts if the selected objects are of different object types.
If you have selected multiple multicores, library part selection is only possible if the
multicore structure is the same for all selected objects.
Procedure
1. Right-click on the object and select Properties; the Edit Properties dialog is displayed.
2. Click the Add (...) button in the Library Part section of the General tab; the Part
Selection Dialog Box is displayed.
3. Search for the library part, select it and click Insert.
4. If you are assigning a library part to a device, connector or backshell, the Associate
Pins with Cavities dialog is displayed. You must associate the cavities from the library
part with the pins on the object. When you have associated the cavities with the pins,
click the OK button.
If you are assigning a library description to a multicore, the Assign Library Multicore
dialog prompts you to assign the innercores from the library multicore to the multicore
wires in the design. When you have associated the multicore wires, click the OK button.
Results
The library part number is displayed at the top of the Library Part section of the General tab.
Note
If the details for a library description are changed in Capital Library, they are not updated
automatically in Capital Logic or Capital Integrator, you must update them manually. See
the To update an object's library part section below.
Related Topics
Part Selection Dialog Box
3. The details for the library description are updated in the Edit Properties facility. Click
the OK button.
3. The View Component facility is displayed. This is like the Part Selection facility but is
read-only. Click the Close button to exit the facility.
Procedure
1. Right-click on the object and select Properties; the Edit Properties dialog is displayed.
2. In the Specification section of the General tab, specify the Color, Material, Spec and
CSA as required. If you want to display any of these attribute values next to the
conductor in the diagram, select the box next to the field and click the button to
display the Edit Graphical Attributes dialog where you specify how it is displayed.
3. Click OK to apply the specified values and exit the facility.
• Junction Box - this indicates that signals can be routed through this slot.
2. The slot type cannot be changed after devices have been placed in the slot.
Procedure
1. In the Option section, enter the option expression in the Expression field. You can
either enter the expression manually or click the ellipsis button (...) to display the Edit
Option Expression dialog.
After a device has been placed using variant-based placement, the General tab of the
Edit Properties facility for a device displays the Expression field under the heading
Placement to distinguish the option expression from regular option tagging.
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, an
error message is displayed.
2. Check the Visible box if you want the option expression to be displayed next to the
object on the diagram. You can set the attributes for the text that is displayed by clicking
the Edit Attributes button and specifying the following:
• Font
Select the font type for the text and whether the text is plain, bold, italic or bold/
italic. Mandatory.
• Height
Specify the height of the text and select the unit of measurement from the dropdown
list. Mandatory.
• Color
To specify the color of the text, select a color from the dropdown list; it is previewed
in the window to the right of the field. Mandatory.
As well as color names, the list contains the following options:
o Default
The default color used for text by the system.
o Background
The same color used for the background of the diagram. The color changes when
the background color is toggled.
o Foreground
If the diagram background is white, the text is black, and vice versa.
o Manual
The Choose Text Color dialog is displayed, where you can select a color.
• Opaque
Select whether object lines are visible behind the text frame boundary box, (un-
selected), or are not visible behind the text frame boundary box, (selected).
Mandatory.
• Rotation
By default this is 0 for the text to run horizontally (left to right). Enter a different
value manually or select a value from the dropdown list, for example, 270 for the
text to run vertically (bottom to top). Mandatory.
• Auto Flip
If selected, the text flips automatically so that it is never displayed upside down
when it is rotated or flipped. If not selected, a flip or rotation can result in the text
being displayed upside down.
• Justification
Specify the position of the text within the text frame. Mandatory.
• Layout
The following set of options are available to control the layout of the text within its
frame.
o Clip Text to Bounding Box
If selected, specifies that the text is clipped at the edge of its bounding box.
o Shrink to Fit
If selected, specifies that the font of the text reduces as necessary so that the text
fits in its bounding box.
o Allow Text to Overflow
If selected, specifies that the text ignores the edge of its bounding box and flows
out of it.
o Wrap text
Specifies whether the text wraps onto multiple lines when it reaches the edge of
the text bounding box (selected) or whether the text ignores the bounding box
and continues on one line (unselected). When this is selected, if a word is too
long to fit on a single line, it is wrapped by character. Mandatory.
• Preview
Displays an preview of an example text string formatted using the currently selected
settings. Mandatory.
3. Click the OK button to exit the Edit Attributes dialog.
4. Click the OK button to exit the Edit Properties dialog.
Note
These part numbers are not used in Capital Library. If harness levels have been combined, a
part number cannot be specified for a child harness level.
Procedure
1. Open the Edit Properties facility for the harness level. To do this, right-click on the
harness level in the Configuration Setting Browser Window and select the
Properties option from the pop-up menu. Alternatively, select the harness level in the
Harness Levels facility (see Defining a Harness Level in the Capital Integrator User
Guide) and click the Properties button.
2. Enter the part number in the Part Number field and click the OK button to close the
facility.
When wiring is synthesized, wires are assigned to appropriate harness levels to support the
functional options that have been defined. The Edit Properties dialog 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 or by using the Generate Option Expressions facility.
Procedure
1. In the Configuration section of the Edit Properties facility, click the ellipsis (...) button
next to the Level field.
2. The Edit Levels facility is displayed. The Available window displays the available
harness levels to which the wire has not been assigned. The Selected window displays
the harness levels to which the wire has been assigned. You can assign a wire to a
harness level by clicking on it in the Available window and clicking the Add button.
You can remove a wire from a harness level by clicking on it in the Selected window
and clicking the Remove button.
3. Click the OK button to confirm the changes and to exit the Edit Levels facility.
The following image indicates the sections of the bundle to which the offset distances
correspond:
2. On 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.
3. The bundle region changes accordingly in the diagram window.
Related Topics
Editing the Properties of Objects
• 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 is displayed, where you can select a color.
When the Capital Logic design is associated with a Capital Integrator design, the Variance tab
can be viewed (but not edited) in the Edit Properties facility for signals in Capital Integrator.
The option-specific values are taken into account when composite wiring synthesis is
performed.
Note
The Variance tab will not be displayed for an object if there are no options defined in a
project or if the project preference for Mandate applicable options has been set and the
design does not have any applicable options.
Any properties specific to the individual net conductor or to the net conductor object type can
have option-specific values.
• WireColor
• WireCSA
• WireMaterial
• WireSpecification
In order for these attributes or net-specific properties to be available on the Variance tab, they
must have a valid value set on the Properties tab or General tab of the Edit Properties facility.
Procedure
1. Right-click on the net conductor in the diagram or Logical Design Browser Window and
select the Properties option from the popup menu.
2. Ensure that the attribute or property has a valid value set on the Properties tab or
General tab of the Edit Properties facility. This value is used as the default value when
no option expression has been applied to the net.
3. Click on the Variance tab and click the New button in the Option Variable Attributes
or Option Variable Properties section as appropriate.
4. The Option Selection dialog is displayed. From the dropdown list, select the attribute or
property and click the OK button.
5. A row for that attribute or property is added to the appropriate table. In the Options
column, specify the option expression to which the value applies. You can click on the
ellipsis (...) button to display the Edit Option Expressions facility that helps you to
define the expression. In the Value field, specify the option-specific value.
You repeat steps 2 to 5 for each option-specific value for that attribute or property.
6. Click the OK button to exit the Edit Properties facility.
Note
There are two design rule checks that can be run in Capital Integrator that are
relevant to these option-specific values, Wire that breaks specification rule and
Option-based variance inconsistency. See Design Rule Checks Applicable to Capital
Integrator Designs.
7. To Delete an Option-Specific Value, click on the row for the option-specific value on
the Variance tab and click the Delete button.
Object Attributes
The Attributes section on General tab of the Edit Properties dialog, enables you to edit the
values for the attributes for that object.
Attributes 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. You can display and report
properties, as well as use them in rules and analysis functionality.
The attributes that are displayed in the Attributes section 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.
When you have edited the attributes, you must click the OK button to exit the Edit Properties
facility and to commit your changes.
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.
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.
When you click the OK button to exit the Edit Properties dialog, the attribute name is
displayed on the symbol diagram. You can move this name to the location where you want the
corresponding value to be displayed in Capital Logic diagrams. When the symbol is added to a
diagram, the name changes to the correct value for that instance of the symbol.
Note
The Pin Type attribute enables you to specify the type of pin. 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 and
Capital Logic, you can specify the pin type U that means that no pin type is specified. This can
be overwritten when you assign the symbol to a library part in Capital Library.
Procedure
1. Select the color from the dropdown list; it is previewed in the window to the right of the
field. 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 is displayed, where you can select a color.
2. Click OK to apply it.
2. Select the required line style from the drop-down list box.
3. Click the OK button to apply the selected Property to the Object.
4. The line style will display with the color currently selected in the Primary Color
setting.
Note
If the object is a highway or conductor in Capital Logic, or a bundle in Capital
Integrator, and the line style selected is broken, then the color of the gaps in the
broken line style can be set with the Secondary Color option
Note
The fill color for an object type can also be controlled by the style set applied to the
diagram. See the Fill Color option in the Styling Options - Graphics section of the Capital
Diagram Styling User Guide.
Procedure
1. Right-click on the object in the diagram and select Properties; the Properties dialog box
is displayed.
2. Click the Graphical tab and select the required color from the Fill Color dropdown list;
it is previewed in the window to the right of the field.
As well as color names, the list contains the following options:
• Default
The default color defined within the style set applied to the diagram.
• 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.
3. Click OK.
Results
The fill color is applied to the object in the diagram.
1. Select the Override option from the drop-down list box to the right of the Fill Pattern
label and click the Change field; the Fill Pattern Selection dialog is displayed.
2. Click on the fill pattern that you want to use.
3. 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.
• Automatic
If the diagram background is white, the object is black, and vice versa.
• Choose Color
The Choose Object Color dialog is displayed, where you can select a color.
4. Click the OK button to exit the Fill Pattern dialog.
When you select an arrow style, it is previewed in the window below the drop-down list.
If you do not want an arrow at the end of the conductor, select the blank line from the
drop-down list.
2. Click on the Right drop-down list and select the style of arrow that you want to display
at the right end of the conductor.
3. Click the OK button to apply the selected end line styles to the object.
Note
The style is applied to every end-segment of the conductor. An end-segment is a
segment where at least one end point is not connected to another segment from the
same conductor.
Note
See the topics”Setting the Physical Line Thickness for an Electrical Symbol or Border” and
“Setting the Physical Line Thickness for a Comment Symbol” in the Capital Symbol User
Guide.
Procedure
1. In the style set that you are using, ensure that the correct unit for your diagrams has been
specified:
a. Press Space Bar and enter Styles; the Style Sets dialog is displayed.
b. In the browser on the left, select the style set that you are using for the diagram and
specify the Unit. This option specifies the unit of measurement upon which all
numerical distances on a design with this style set applied will be based.
2. Within the style set in the browser on the left, navigate to the object type for which you
want to specify a physical line thickness and select the Graphics node; a Thickness
field is displayed on the right of the dialog (among other fields).
3. In the Thickness field, select Override from the first dropdown list and Physical from
the last dropdown list. The unit that you set for the Unit is displayed next to the Physical
option.
4. In the field that now appears between the dropdown lists, specify the value for the line
thickness. The value can be any floating-point number up to three decimal places.
5. Click OK.
6. Apply the style set change to the diagram. See Applying Styles in the Capital Diagram
Styling User Guide.
Results
• The line thickness for objects of that type updates accordingly. Zooming in or out
maintains the line thickness with respect to the diagram grid size (for example, the lines
become thinner if you zoom out).
• You can override the line thickness for a graphic in a diagram by right-clicking it and
selecting Properties. On the Graphical tab, specify the required Thickness.
Related Topics
Physical Line Thickness
Procedure
1. In the Style Sets dialog, navigate to the style set that you are using in the browser tree on
the left.
2. Within the style set in the browser tree, navigate to the Graphics node for the object
type.
3. Specify the Graphics attributes that are not controlled by the plugin.
4. Create the plugin to set the line thickness of the object type. For information about
developing and using extensibility plugins, see the PluginDevelopment.pdf file, located
in the doc\plugin folder of your Capital installation.
5. Assign the plugin in the Style Sets dialog:
a. Within the style set in the browser tree, navigate to the Graphics node for the object
type.
Procedure
1. Press Space Bar and enter Find and Replace. Alternatively, you can select an object and
then select the menu option.
2. The Find and Replace dialog box is displayed. Specify the following:
• Scope - select the project, build list, designs or diagrams in which you want to
search. If build lists exist, they are listed above the designs.
3. The filter symbol in the Scope section indicates whether a filter has been set or
not .
If a filter has been set and you do not want to use a filter, click the Clear Filter button.
If you want to set a filter for the search, click the Set Filter button to display the Find
and Replace Filters dialog. In that dialog, specify the following;
• Object Types - select the object types that you want to be included in the search.
You can clear the selection at any point by clicking the Clear Selection button.
Note
If you search for pins, the search results include backshell terminations, if you
search for devices, the search results also include ground devices.
• Revision - specify the design revision in which you want to search. You can check
the Latest Revision Only box to only ever search across the latest revision.
• Release Level - from the dropdown list, select either no release level (blank) or a
release level across which you want to search.
• Domain - from the dropdown list, select either no domain (blank) or a domain
across which you want to search.
• Effectivity (only visible if effectivity functionality has been enabled for the project
in Capital Project) - specify the effectivity range within which you want to search.
Click the OK button to exit the Find and Replace Filters dialog.
4. In the Find section, you specify for what you are searching and potentially want to
replace. If you use wildcards in this section, you must check the Regular Expression
box, otherwise the search will not use the wildcards correctly. When the Regular
Expression box is checked, an empty field is equivalent to *. You can check the Match
Case box if you want the search to be case-sensitive with regard to the specified values.
You can specify the following:
Note
In the following fields, if you want to search for a special character such as $, ensure
that you type a delimiter (\) before it. For example, \$.
• Object Name - if you want to limit the search to objects with particular names, you
can enter a full name or part of a name using wildcards.
• Attribute/Property - specify the attribute or property name. You can either enter
the name manually or select it from the drop-down list in the field.
• Matches - specify the value of the attribute or property.
If Exact Match is selected, every value string found will be fully replaced by the
content in the replace section.
If Exact Match is not selected, each and every occurrence of the string entered will
be replaced by the content in the replace section. For example, find “AB” and
replace with “C”, results in the renaming of Property=ABDAB with
Property=CDC.
If nothing is specified here, the entire value strings of the attribute/property
occurrences found will be replaced by the content in the replace section. For
example, find “” and replace with “C”, results in the renaming of
Property=ABDAB with Property=C.
• Symbol - if you want to search on objects that use a particular symbol only, you can
click the ellipsis (...) button to display the Symbol Selection dialog that enables you
to browse the available symbol libraries to select the symbol. If you select a symbol,
it is displayed in a preview window.
You can click the Clear button to clear the symbol selection.
• Symbol - the symbol that you want to replace the symbols found by the search. You
click the ellipsis (...) button to display the Select Symbol dialog that enables you to
browse the available symbol libraries to select the symbol. If you select a symbol, it
is displayed in a preview window.
You can click the Clear button to clear the symbol selection.
• Update Symbol Only - select this if you want to replace only the symbols used for
the found objects and not their attributes or properties. You cannot replace comment
symbols or symbols associated to library parts.
• Preserve Pin Positions
Select this if you want the pins on the symbol instances to remain where they are in
the diagram already.
• Remove Properties Not on Symbol
Select this if you want to remove any properties from the symbol instances that are
not on the symbol in the symbol library.
• Copy Attribute/Property Values from Symbol
Select this if you want to copy any properties and attributes that are on the symbol in
the symbol library to the symbol instances.
• Preserve Attribute Text
The attribute visibility settings on a diagram instance of a symbol may be different to
the attribute visibility settings on that symbol in the symbol library. If this is
selected, the attribute visibility settings on the symbol instance in the diagram are
retained. If this is not selected, the attribute visibility settings on the diagram
instance are overwritten by those on the symbol in the library.
• Preserve Diagram Pin Name
In a diagram, you can rename a pin name on a symbol instance. If this is selected, the
pin names in the diagram are retained. If this is not selected, the pin names in the
diagram are replaced by the pin names from the symbol in the symbol library.
6. Click one of the following buttons:
• Find - finds the specified attributes and properties but does not replace any values.
The output window at the bottom of the application displays the found objects on the
Find and Replace tab. You can click on an object name to view that object in a
diagram.
• Preview - previews the changes that would be made if you did a replace but does not
change the actual designs. The changes are displayed on the Find and Replace tab
of the output window at the bottom of the application but are not made to the actual
design. You can click on an object name to view that object in a diagram.
• Replace - finds and replaces the specified values. This works on editable designs
only. If the replace action affects a shared object, the design is saved automatically.
This button is disabled if the Replace section does not contain valid data. The
objects with replaced values are listed on the Find and Replace tab of the output
window at the bottom of the application. You can click on an object name to view
that object in a diagram. Some replacement values may be invalid for some of the
found objects and the Find and Replace tab lists these as errors.
7. If you are replacing values, a message states that the operation is undoable and you must
confirm whether you want to proceed. You can check a box so that this message is not
displayed again.
If you are replacing symbols and the replacement symbol has a different number of pins
to the symbol instance, the Map Pins Dialog is displayed and you map the pins from the
replacement symbol to pins on the symbol instances. You also specify what data on the
symbol instance you want to preserve and what data you want to remove. After doing
this, click OK.
• Fill Patterns
Select the fill pattern.
• Foreground Color
Specify the foreground color for the pattern. As well as color names, the list contains the
following options:
o Background
The same color used for the background of the diagram. The color changes when the
background color is toggled.
o Foreground
If the diagram background is white, the object is black, and vice versa.
o Manual
The Choose Object Color dialog is displayed, where you can select a color.
• Background Color
Specify the background color for the pattern. Click on the square to display the Choose
Object Color Dialog where you specify a color. As well as color names, the list
contains the following options:
o Background
The same color used for the background of the diagram. The color changes when the
background color is toggled.
o Foreground
If the diagram background is white, the object is black, and vice versa.
o Manual
The Choose Object Color dialog is displayed, where you can select a color.
If scopes are defined both at project and design level, the design-level scopes are used within a
design.
Only one customer or manufacturing site scope code is allowed per design or project.
For a usage example detailing how to use component scoping, including applying it to projects
or designs see the Capital Library User Guide.
Note
You can use Extensibility Plugins to manage component scoping. If a plugin is available
then it will override the default part selection rules. For more information about developing
and using extensibility plugins, see the PluginDevelopment.pdf file that is located in the
doc\plugin folder of your Capital installation.
Prerequisites
• The required scopes must have been created in Capital Library.
Procedure
1. Right-click on the project name or design in the Project Browser Tree and select Edit;
the Edit Project dialog box or Edit Design dialog box is displayed.
2. Click Properties; an Edit Properties dialog 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.
Note
If the name for an object has been modified from the default in the Name field of the
Edit Properties dialog, it is set as fixed by default.
• 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 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.
• Use the Generate Advanced Names dialog to generate them for specific selected
objects. See “Generating Names for Selected Objects in a Diagram” on page 267.
• Use the Generate Advanced Names dialog 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” on page 268.
Related Topics
Generating Names for Selected Objects in a Diagram
Generating Names for all Objects in a Build List, Design or Diagram
Note
If you want to replace names on shared objects, you must select Fixed Names
because shared object names are considered as fixed by the system.
3. Specify whether you want to “Reset Object Indices” and/or “Reset Counters”.
4. Click OK; the dialog closes and the new names for the selected objects are generated.
Related Topics
Advanced Naming Functionality
Generating Names for all Objects in a Build List, Design or Diagram
Note
If you want to replace names on shared objects, you must select Fixed Names
because shared object names are considered as fixed by the system.
4. Specify whether you want to “Reset Object Indices” and/or “Reset Counters”.
5. Click OK; the dialog closes and the new names for the selected objects are generated.
Related Topics
Advanced Naming Functionality
Generating Names for Selected Objects in a Diagram
Procedure
1. In the Part Selection Dialog Box, enter your search criteria as required and click Search
parts using criteria specified ( ).
Procedure
1. Press Space Bar and enter Library Parts; the Confirm Batch Update Library Parts
dialog is displayed.
2. If given the choice, select whether you want to update library parts in the currently
active design or in a build list to which that design belongs.
3. Select Preserve Include on BOM attribute to maintain the current setting for an object so
it is not overwritten with its library setting.
4. Select Reset parts to preferred supplier if you wish update all objects in design(s) with a
preferred supplier part number and details. Leave the option unchecked to retain existing
supplier details on all objects in design(s).
Note
In cases where the Batch Update of Library parts action is run in Capital Logic with
the option Reset parts to preferred Supplier unchecked, on a design which has Auto
Generate Harness Connectors enabled, the supplier part number and supplier name of
footprint harness connectors are reset to preferred supplier details.
5. Click OK; a status bar indicates that the update is taking place.
Slice Objects
This functionality applies to Capital Logic, Capital Publisher, Capital Integrator and Capital
Topology only.
Certain objects on diagrams can be sliced, simplifying diagram modifications and making
diagrams easier to understand.
The Slice functionality allows you to draw an intersection line across an applicable object, 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 diagrams, or to trim oversized
devices and connectors.
• In Capital Logic and Capital Publisher: Devices, blocks, connectors and conductors
(including multicores, overbraids and highways) can be sliced
• In Capital Integrator and Capital Topology: Slots and bundles can be sliced
• Slices can be vertical or horizontal
• Slices can not be made directly across pins or mated edges
• Inline connectors can not be sliced across just one of the inline halves.
• Slices on devices, slots or connectors must leave at least one pin on each side of the
slice. If not the object will be trimmed to the size of the slice. See Slice to Trim Objects.
Video
Slicing Objects - this video illustrates how to perform this task. Click to view it.
Slice Devices
This topic explains how to slice devices.
Prerequisites
• Valid device on open diagram
Procedure
1. Press Space Bar and enter Slice.
Note
Selecting Shift & Slice will enable the cursor to retain the Slice action and allow
repeated slices. Press Escape to return to the standard cursor.
3. Click on the diagram to place the first end of the slice line.
4. Place the second end of the line by clicking at the desired location. In Example 7-1
below, the slice line is made horizontally across device DEV305, between conductors
COND114 and COND115.
Figure 7-1. Slice Device
Results
• The device is split as in Example 7-2 below.
Figure 7-2. Device Slice Complete
• The devices can be selected and moved apart as in Example 7-3 below.
Related Topics
Slice Blocks
Slice Connectors
Slice Conductors
Slice to Trim Objects
Slice and Move To
Slice Blocks
This topic explains how to slice blocks.
Prerequisites
• Valid block on open diagram
Procedure
1. Press Space Bar and enter Slice.
Note
Selecting Shift & Slice will enable the cursor to retain the Slice action and allow
repeated slices. Press Escape to return to the standard cursor.
3. Click on the diagram to place the first end of the slice line.
4. Place the second end of the line by clicking at the desired location. In Example 7-1
below, the slice line is made horizontally across device BLOCK200, between highways
HW101 and HW102.
Results
• The block is split as in Example 7-2 below.
Figure 7-5. Block Slice Complete
• The blocks can be selected and moved apart as in Example 7-3 below.
Figure 7-6. Separate Blocks
Related Topics
Slice Connectors
Slice Conductors
Slice Connectors
This topic explains how to slice connectors.
Prerequisites
• Valid connector on open diagram
Procedure
1. Press Space Bar and enter Slice.
Note
Selecting Shift & Slice will enable the cursor to retain the Slice action and allow
repeated slices. Press Escape to return to the standard cursor.
3. Click on the diagram to place the first end of the slice line.
4. Place the second end of the line by clicking at the desired location. In Example 7-7
below, the slice line is made horizontally across the connector Conn1, between Wire 002
and Wire 003.
Figure 7-7. Slice Connector
Results
• The connector is split as in Example 7-8 below.
• The connectors can be selected and moved apart as in Example 7-9 below.
Figure 7-9. Separate Connectors
Related Topics
Slice Devices
Slice Blocks
Slice Conductors
Slice to Trim Objects
Slice and Move To
Slice Conductors
This topic explains how to slice conductors.
Prerequisites
• Valid conductors on open diagram
Procedure
1. Press Space Bar and enter Slice.
Note
Selecting Shift & Slice will enable the cursor to retain the Slice action and allow
repeated slices. Press Escape to return to the standard cursor.
3. Click on the diagram to place the first end of the slice line.
4. Place the second end of the line by clicking at the desired location. In Example 7-10
below, the slice line is made vertically across conductors 001, 002 and 003.
Figure 7-10. Slice Conductors
Results
• The conductors are sliced and display with appropriate cross-references. See
Example 7-11 below
Figure 7-11. Slice Complete
Related Topics
Slice Devices
Slice Blocks
Slice Connectors
Slice to Trim Objects
Slice and Move To
Slicing a Slot
In Capital Integrator or Capital Topology, you slice a slot in order to separate harness objects
that you want to move to another diagram or to create an instance with a sub-set of the
connectors on it.The separation is purely graphical, it does not break any connectivity.
Each instance represents the entire slot (that is, a device placed in the slot is available in all
instances).
Prerequisites
• A valid slot on an open diagram.
Procedure
1. Press Space Bar and enter Slice.
2. Click once on the diagram, drag the cursor over where you want to slice the slot. You
decide this based on which connectors you want on which instance.
Figure 7-12. Slot Before Slice
Slicing a Bundle
In Capital Integrator or Capital Topology, you slice a bundle to create multiple instances of it.
Instances can remain on the same diagram but you may want multiple instances in order to
separate harness objects that you want to move to another diagram.The separation is purely
graphical, it does not break any connectivity.
Prerequisites
• A valid bundle on an open diagram.
Procedure
1. Press Space Bar and enter Slice.
Results
The sliced sections of the bundle reconnect.
Note
Selecting Shift & Slice will enable the cursor to retain the Slice action and allow
repeated slices. Press Escape to return to the standard cursor.
3. Click on the diagram to place the first end of the slice line.
4. Place the second end of the line by clicking at the desired location. In Example 7-14
below, the slice line is made horizontally across the device below conductor 003.
Results
• Because there were no pins on either side of the slice line, the device is trimmed to the
size of the slice. See Example 7-15 below.
Figure 7-15. Trimmed Device
Related Topics
Slice Devices
Slice Blocks
Slice Conductors
Slice Connectors
Slice and Move To
Prerequisites
• Valid objects on the diagram that can be sliced.
• Second diagram available for selection to Move To
Procedure
1. Press Space Bar and enter Slice.
Note
Selecting Shift & Slice will enable the cursor to retain the Slice action and allow
repeated slices. Press Escape to return to the standard cursor.
3. In this example, Example 7-16 below, we will slice and move the six speakers and their
associated connectivity from the top right of the diagram to a new diagram.
Figure 7-16. Starting Point
4. Click on the diagram to place the slice line. In Example 7-17 below, the slice line is
made vertically across the conductors.
5. The Slice is made and the six speakers and their conductors have been separated. See
Example 7-18 below, cross-references are created for the new instances of the nets.
Figure 7-18. Slice Made
6. Select the objects as below in Example 7-19, press Space Bar and enter Move To.
Choose the required diagram and press OK.
Results
• The selected objects are removed from the original diagram. See Example 7-20
Figure 7-20. Objects Removed
• The selected objects can now bee seen on the new diagram as selected in earlier step.
See Example 7-21 below.
Related Topics
Slice Devices
Slice Blocks
Slice Connectors
Slice Conductors
Slice to Trim Objects
Design Logs
There are multiple processes that generate a design log file, which details the results of the
process, as well as any warnings or errors that may have occurred.
By inspecting these logs, you can investigate the causes of any problems encountered.
Note
If you are viewing the logs for a composite harness, you can expand the log structure
(by clicking on the plus [+] symbols) until the logs for any derivative, functional
module, or production module child are displayed.
Results
• The Design Log Viewer Dialog Box opens, displaying the contents of the log.
• You can repeat step 3 to open multiple Design Log Viewer Dialog boxes
simultaneously.
• All filtering controls on the View Design Logs dialog box remain active when Design
Log Viewer dialog box(es) are open.
• You are able to keep the viewer dialog box open and interact with the design.
o However, if you invoke any action that creates a log file, then all open viewers are
automatically closed. See “Design Logs” on page 286 for details of such actions.
Related Topics
View Design Logs Help
Design Log Viewer Help
Design Log Event Filter Options Help
Design Log Filter Options Help
Note
If you are viewing the logs for a composite harness, you can expand the log structure
(by clicking on the plus [+] symbols) until the logs for any derivative, functional
module, or production module child are displayed.
Results
The log opens in the Output Window, this allows you to review the log and interact with the
open design.
Parameterized Object
Parameterized objects are design objects that have no symbols and their graphics are controlled
by a configuration file. Some examples of parameterized objects are devices, connectors,
splices, and slots.
This chapter contains topics which detail the options available in configuring how diagrams are
output to printing devices, including diagram scaling and the configuration and selection of
print regions.
The following topics are available:
Procedure
1. With the designs and diagrams selected in the Project Browser, press Space Bar and
enter Print. The Print Dialog Box is displayed.
Note
If you select a block of diagrams, the diagrams are printed in the order in which they
are listed in the project tree. If you select individual diagrams, the diagrams are
printed in the order in which they were selected.
percentage value, either by overwriting the value in the field to the right, or by
clicking the up and down arrow buttons.
6. Check the Clip To Border checkbox to print only the diagram elements falling within the
border outline. Unchecked, all harness elements will be printed, including those placed
outside of the border.
7. Check the Black/White Only checkbox to generate prints using only black lines/text
against a white background, regardless of the specified text/line colors in use in a
diagram. Unchecked, prints will be generated in color.
8. Specify a Dash Multiplier setting to stretch or shrink dashes relative to the size of output
page.
9. Click OK. The selection of diagrams are sent to the specified printer.
Related Topics
Printing a Single Diagram
Printing All Diagrams in a Project
Printing All Diagrams in a Design
Printing Selected Print Regions
applied style set; see the Diagram Styling User Guide for more information).
Alternatively, the diagram can be printed larger or smaller by specifying a new
percentage value, either by overwriting the value in the field to the right, or by
clicking the up and down arrow buttons.
6. Check the Clip To Border checkbox to print only the diagram elements falling within the
border outline. Unchecked, all harness elements will be printed, including those placed
outside of the border.
7. Check the Black/White Only checkbox to generate prints using only black lines/text
against a white background, regardless of the specified text/line colors in use in a
diagram. Unchecked, prints will be generated in color.
8. Specify a Dash Multiplier setting to stretch or shrink dashes relative to the size of output
page.
9. Click OK. The diagrams are sent to the specified printer.
Related Topics
Printing a Single Diagram
Printing Selected Diagrams in a Project
Printing All Diagrams in a Design
Printing Selected Print Regions
• Print to Scale — This option specifies that the diagram should be printed at 100%
size, as dictated by the design’s grid spacing value (as specified in the currently
applied style set; see the Diagram Styling User Guide for more information).
Alternatively, the diagram can be printed larger or smaller by specifying a new
percentage value, either by overwriting the value in the field to the right, or by
clicking the up and down arrow buttons.
7. Check the Clip To Border checkbox to print only the diagram elements falling within the
border outline. Unchecked, all harness elements will be printed, including those placed
outside of the border.
8. Check the Black/White Only checkbox to generate prints using only black lines/text
against a white background, regardless of the specified text/line colors in use in a
diagram. Unchecked, prints will be generated in color.
9. Specify a Dash Multiplier setting to stretch or shrink dashes relative to the size of output
page.
10. Click OK. The diagrams are sent to the specified printer.
Related Topics
Printing a Single Diagram
Printing Selected Diagrams in a Project
Printing All Diagrams in a Project
Printing All Diagrams in a Design
Print Regions
The following topics detail how to add print regions to a design, with additional topics on
resizing, moving and editing print regions once created.
It is possible to create print regions within a border symbol, which will then be added to a
design as the border is selected.
It is also possible to create one or more print regions for comment symbols that contain
connector and splice information on a harness diagram.
Topics detailing the creation and maintenance of border and comment symbol print regions are
available in the Capital Symbol User Guide.
1. Press Space Bar and enter Add print region. The cursor changes to .
2. Click to place the first corner of the print region, then drag out a rectangle until the
region is of the required size.
3. Click to confirm the placement of the print region.
Note
Multiple print regions can be placed without reselecting the Add Print Region tool.
Once a print region has been placed, single-clicking again will place the first corner
of a new print region.
4. Double-click or press Enter to finish. The Edit Print Region Groups Dialog Box is
displayed.
5. Either accept the default Print Region Name offered, or enter your own.
6. By default, print regions are set to Active and the Visible setting is unselected; change
these settings if required.
7. Click OK.
Results
The print region is placed onto the design.The following print region entities are displayed:
• The print region outline
• The print region name
Related Topics
Resizing a Print Region
Moving a Print Region
Editing a Print Region
Deleting a Print Region
Procedure
1. Either:
• Hover the cursor over the print region outline
or
• Click on the print region outline to select it
2. The gray boxes identifying the draggable corners are displayed.
3. Click on one of the gray boxes and drag until the outline is of the required size.
Related Topics
Moving a Print Region
Editing a Print Region
Deleting a Print Region
Procedure
1. Click on any edge of the print region outline (not on the corners).
2. Drag the print region to the new location and release the mouse button.
Note
Begin dragging as soon as you click on the print region outline; if you wait too long
before starting to drag, the Panning Tool will activate.
Related Topics
Adding a Print Region to a Design
Resizing a Print Region
Editing a Print Region
Deleting a Print Region
Note
Print regions configured against the border applied to the design can only be
renamed by editing the border symbol in Capital Symbol. See Editing a Print Region
in the Capital Symbol User Guide. However the Active and Visible status can be
amended within the design.
Related Topics
Adding a Print Region to a Design
Procedure
1. Select the print region to be deleted.
2. Either:
• Press Space Bar and enter Delete
• Right-click and select Delete
• Press the Delete key
Results
The print region is removed from the design.
Related Topics
Adding a Print Region to a Design
Resizing a Print Region
Moving a Print Region
Editing a Print Region
Print to a File
The following topics detail how to export the design data from one or more diagrams to either
PDF, DXF, CGM or SVG format.
Printing To File - All Diagrams in a Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 300
Printing To File - All Diagrams in a Design . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301
Printing To File - Single Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302
Printing To File - Selected Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303
Printing To File - Print Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304
Note
If you select PDF, DXF, CGM or SVG in the Format field, the Configure button to
the right of the field is enabled, offering access to either the PDF Page Settings
Dialog Box, the DXF Page Settings Dialog Box, the CGM Page Settings Dialog Box or
the SVG Page Settings Dialog Box, from where you can configure a number of PDF,
DXF, CGM or SVG specific generation parameters.
5. Either:
• Accept the default Filename of {Diagram}, in which case the data files created will
be named based on the diagram name appended with the file extension appropriate
to the selected export Format.
• Click the ellipsis (...) button to the right of the Filename field to display the Edit File
Name Dialog Box and configure a new file name template.
6. Click the ellipsis (...) button to the right of the Location field and use the file browser
dialog to navigate to the directory in which the exported data file(s) should be placed.
7. Click OK.
Results
The design data is exported and the generated file(s) placed in the specified location.
Related Topics
Printing To File - All Diagrams in a Design
Printing To File - Single Diagram
Printing To File - Selected Diagrams
Printing To File - Print Regions
Note
If you select PDF, DXF, CGM or SVG in the Format field, the Configure button to
the right of the field is enabled, offering access to either the PDF Page Settings
Dialog Box, the DXF Page Settings Dialog Box, the CGM Page Settings Dialog Box or
the SVG Page Settings Dialog Box, from where you can configure a number of PDF,
DXF, CGM or SVG specific generation parameters.
4. Either:
• Accept the default Filename of {Diagram}, in which case the data files created will
be named based on the diagram name appended with the file extension appropriate
to the selected export Format.
• Click the ellipsis (...) button to the right of the Filename field to display the Edit File
Name Dialog Box and configure a new file name template.
5. Click the ellipsis (...) button to the right of the Location field and use the file browser
dialog to navigate to the directory in which the exported data file(s) should be placed.
6. Click OK.
Results
The design data is exported and the generated file(s) placed in the specified location.
Related Topics
Printing To File - All Diagrams in a Project
Printing To File - Single Diagram
Printing To File - Selected Diagrams
Printing To File - Print Regions
Note
If you select PDF, DXF, CGM or SVG in the Format field, the Configure button to
the right of the field is enabled, offering access to either the PDF Page Settings
Dialog Box, the DXF Page Settings Dialog Box, the CGM Page Settings Dialog Box or
the SVG Page Settings Dialog Box, from where you can configure a number of PDF,
DXF, CGM or SVG specific generation parameters.
4. Either:
• Accept the default Filename of {Diagram}, in which case the data files created will
be named based on the diagram name appended with the file extension appropriate
to the selected export Format.
• Click the ellipsis (...) button to the right of the Filename field to display the Edit File
Name Dialog Box and configure a new file name template.
5. Click the ellipsis (...) button to the right of the Location field and use the file browser
dialog to navigate to the directory in which the exported data file(s) should be placed.
6. Click OK.
Results
The design data is exported and the generated file(s) placed in the specified location.
Related Topics
Printing To File - All Diagrams in a Project
Printing To File - All Diagrams in a Design
Printing To File - Selected Diagrams
Printing To File - Print Regions
Procedure
1. With the designs and diagrams or build list selected in the Project Browser, press Space
Bar and enter Print to File. The Print to File Dialog Box is displayed.
Note
If you select a block of diagrams, the diagrams are printed in the order in which they
are listed in the project tree. If you select individual diagrams, the diagrams are
printed in the order in which they were selected.
Note
If you select PDF, DXF, CGM or SVG in the Format field, the Configure button to
the right of the field is enabled, offering access to either the PDF Page Settings
Dialog Box, the DXF Page Settings Dialog Box, the CGM Page Settings Dialog Box or
the SVG Page Settings Dialog Box, from where you can configure a number of PDF,
DXF, CGM or SVG specific generation parameters.
5. Either:
• Accept the default Filename of {Diagram}, in which case the data files created will
be named based on the diagram name appended with the file extension appropriate
to the selected export Format.
• Click the ellipsis (...) button to the right of the Filename field to display the Edit File
Name Dialog Box and configure a new file name template.
6. Click the ellipsis (...) button to the right of the Location field and use the file browser
dialog to navigate to the directory in which the exported data file(s) should be placed.
7. Click OK.
Results
The design data is exported and the generated file(s) placed in the specified location.
Related Topics
Printing To File - All Diagrams in a Project
Printing To File - All Diagrams in a Design
Printing To File - Single Diagram
Printing To File - Print Regions
Note
If you select PDF, DXF or CGM in the Format field, the Configure button to the
right of the field is enabled, offering access to either the PDF Page Settings Dialog
Box, the DXF Page Settings Dialog Box or the CGM Page Settings Dialog Box, from
where you can configure a number of PDF, DXF or CGM specific generation
parameters.
6. Either:
• Accept the default Filename of {Diagram}, in which case the data files created will
be named based on the diagram name appended with the file extension appropriate
to the selected export Format.
• Click the ellipsis (...) button to the right of the Filename field to display the Edit File
Name Dialog Box and configure a new file name template.
7. Click the ellipsis (...) button to the right of the Location field and use the file browser
dialog to navigate to the directory in which the exported data file(s) should be placed.
8. Click OK.
Results
The design data is exported and the generated file(s) placed in the specified location.
Related Topics
Printing To File - All Diagrams in a Project
Printing To File - All Diagrams in a Design
Printing To File - Single Diagram
Printing To File - Selected Diagrams
Note
It may be necessary to adjust a combination of the Page Settings to achieve accurate
rendering.
The following examples detail each of the available settings, explaining why they may be used
and show the effects that changing the settings have on the final output SVG file. Some
examples have used exaggerated settings to emphasize the effects of the changes.
Example 8-1 below shows an SVG that has been created with the Line Thickness Scale Factor
set to 0.7. The lines appear faint.
By increasing the Line Thickness Scale Factor to 2.0 and regenerating the SVG from the same
source diagram, the output file displays as in Example 8-2 below.
See also “Line Thickness Scale Factor” on page 306 on page 255 for other line width controls
Example 8-3 below shows a set of differing width lines drawn in a design tool.
Example 8-4 below shows a section of an SVG that has been created from the above source
diagram, with the Minimum Line Width set to 30 pixels. All the lines have a line width of 30
pixels or more so the Minimum Line Width has not been applied and the rendering is as in the
source diagram.
By increasing the Minimum Line Width to 180 pixels and regenerating the SVG from the same
source diagram, the output file displays as in Example 8-5 below. The Minimum Line Width
has been applied and has had the effect of rendering all the lines at a minimum width of 180
pixels.
By increasing the Default Width and Default Height setting to 5000 x 4000, and regenerating
the SVG from the same source diagram, a much larger SVG is created and the maximum zoom
now displays the same object in more detail see Example 8-7 below.
The Line Pattern Scale Factor setting applies a percentage increase/decrease to spacing of any
lines styles on the output SVG to ensure an accurate and consistent rendering.
Example 8-9 below, shows the same linestyle, rendered on an SVG that has been created with
the Line Pattern Scale Factor set to 2.0. The linestyle spacing has not been maintained
By decreasing the Line Pattern Scale Factor to 0.5 and regenerating the SVG from the same
source diagram, the linestyle renders as a more accurate representation of the original source
diagram. See Example 8-10 below.
Example 8-12 below, shows the same fill pattern, rendered on an SVG that has been created
with the Fill Pattern Scale Factor set to 2.0. The linestyle spacing has not been maintained
By decreasing the Fill Pattern Scale Factor to 0.5 and regenerating the SVG from the same
source diagram, the fill pattern renders as a more accurate representation of the original source
diagram. See Example 8-13 below.
Related Topics
Printing To File - All Diagrams in a Project
Printing To File - All Diagrams in a Design
Printing To File - Single Diagram
Trace and navigate functionality provides you with the ability to trace related objects across
design revisions and abstractions, and to navigate to those objects.
Compare and propagate functionality provides you with the ability to compare objects in
designs, and generate a To Do list to help propagate changes that ensure your designs and build
lists are consistent.
Video
To see how trace and navigate works, see the video “Using Trace and Navigate”.
Tagging Service
The trace functionality refers to tags that the system generates for various containers in the
Capital database (for example, designs, SBOMs).
Tags are named pieces of data that the system generates for an object in a container and stores
for querying. For example, you can have a tag with type “signal” and value “POWER +12V”.
That tag represents the signal of an object in a design. Wires and nets implementing that signal
have that tag.
The tagging service is triggered by various user actions that run for containers:
• When you edit a container. For example, when you edit and save a design.
• When you delete a container. For example, when you delete a design.
• When you import a project or design.
• When you edit a shared object in a Capital Logic design.
• When you add a design to the working set.
• When you revise or copy a Capital Integrator, Capital HarnessXC, or Capital Topology
design.
In addition, you can modify the schedule of the tagging service and its related parameters. See
Configuring Tagging Tasks to Run in the Background.
When containers are deleted from the database, any tags related to them remain. You can
configure the system to check for these stale tags and remove them on a fixed schedule. See
Configuring Stale Tag Cleanup Tasks to Run in the Background.
Related Topics
Trace and Navigate
Working Set
Adding Designs to a Working Set
Configuring Tagging Tasks to Run in the Background
Configuring Stale Tag Cleanup Tasks to Run in the Background
Working Set
Your working set contains designs that are relevant to your work. You can trace and navigate to
objects in designs in your working set only.
You add individual designs of any type or build lists to the working set. Included designs and
build lists are indicated by a green dot ( ) overlaid on top of the icon for the design or build list
in the Project Browser Window.
The system saves your working set on your computer. If you close and re-open Capital (and the
project) on that computer, the working set is still available. If you access Capital on a different
computer, the working set is not available.
You can filter the Project Browser Window in any design application to display only the designs
in your working set. To do this, select the Show designs and build lists in Working Set icon
( ) at the bottom right of the Project Browser Window.
Related Topics
Adding Designs to a Working Set
Procedure
In the Project Browser Window at the top left of any design application window, right-click on
the design, design folder, or build list and select Add to Working Set.
Note
You can select multiple designs and design folders.
Results
• In the Project Browser Window, a green dot is added to the icon for the design, design
folder, or build list (for example, ).
• Trace and navigate functionality can trace and navigate to objects in that design, design
folder, or build list.
• If multiple revisions of the same design are included in a design folder, the system adds
the latest revision only.
• The working set is saved on the computer on which you are working. If you close and
re-open Capital (and the project) on that computer, the working set is still available. If
you access Capital on another computer, the working set is not available and you will
have to set it up on that computer again.
• You can filter the Project Browser Window in any design application to display only the
designs in your working set. To do this, select the Show designs and build lists in
Working Set icon ( ) at the bottom right of the Project Browser Window.
• You can remove a design, design folder, or build list from a working set by right-
clicking on it in the Project Browser Window and selecting Remove from Working
Set. To remove everything from a working set, right-click the project name in the
Project Browser Window and select Remove from Working Set.
Related Topics
Trace and Navigate
Working Set
Note
If Trace is disabled, the tool tip on it explains why. The most common reasons are
you have multiple objects selected or have an empty working set.
Results
• The Trace tab displays the related objects.
• Click a related object’s name to navigate to it. The appropriate application and design
opens with the related object highlighted and a Trace tab opens for that object.
Note
If you traced from an object that is not in the working set, the Trace tab displays
only related objects that are in the working set.
Related Topics
Trace and Navigate
Working Set
Trace Relationships
Trace Tab
A Trace tab is displayed in the Output Window at the bottom of a design application window
when you use trace functionality to find related objects to the object currently selected in the
design.
The tab displays a table listing the related objects with the following contents:
Usage Notes
You can tear this tab from the interface so that it is a free-floating, re-sizable dialog box. To do
this, click the tab name and drag it. If you do not tear the tab from the interface, the results are
replaced when you use the trace function for another object. If you tear off the tab, it remains
unchanged when you use the trace function for another object and a separate tab is created. To
return the tab to the Output Window, close the dialog box.
When free-floating, the name of the tab also includes the selected object. For example,
Trace:BUN387.
Related Topics
Tracing an Object across Designs
Trace Relationships
Trace Relationships
The Trace functionality identifies various relationships between objects.
The Trace tab results can include the following relationships between objects.
Related Topics
Trace Tab
Tracing an Object across Designs
Prerequisites
• You should be a system administrator.
• You must have configured Capital Integration Server (CIS) in the clientprops.xml file in
the config directory of your installation. The specified user must have access to all
domains that require tagging. See the Capital Integration Server (CIS) entry in the
“clientprops.xml File Format” topic of the Capital Configuration Files Reference Guide
for further information.
Procedure
1. Navigate to the config directory of your Capital installation where you run Capital
Integration Server and open the indexing-configuration.xml file for editing.
2. Find the ANSTagGenerationTask line and edit the parameters:
• autoschedule
Set this to true to enable the background indexing and tagging. The scheduling
specified by the cronexpression runs from when the Capital Integration Server
starts.
• cronexpression
Enter a cron expression to schedule how often the indexing and tagging task runs.
Click here for information and examples of how to define cron expressions. You will
need your SupportNet login details.
For example:
<ANSTagGenerationTask autoschedule="true" cronexpression="0 0 0/1 * * ?" />
3. Find the TaskParameters line and edit the parameters:
• batchsize
The indexing and tagging task processes batches of design containers. Specify how
many design containers are included in each batch.
• waittime
Specify how much time (in milliseconds) the system waits between finishing one
batch of design containers and starting on the next batch. This frees up the system
for any other scheduled tasks.
• cleanupfiles
As the ANSTagGeneration task (and related ANSStaleTagCleanup task) run
frequently, they accumulate task parameter files and log files quickly. Specify “true”
if you want the system to clean up (delete) these files automatically.
Specify “false” if you do not want to run clean-up functionality. If you want to
archive the files rather than delete them, you can implement your own OS batch
script.
• cleanuptype
If you have set cleanupfiles to “true”, this specifies how the files are cleaned up.
Specify one of the following values:
o simple
Deletes all the parameter files and log files for the task, excluding the files for
the current task run.
o retainbytime
Deletes all the files that are older than a specified retention time (retentiontime
parameter).
o retainbycount
Deletes all the files, excluding those for the specified number of last task
executions (retentioncount parameter).
o retentiontime
Relates to the cleanuptype parameter with value retainbytime. Specify the
maximum age (in milliseconds) of the parameter files and log files that are not
deleted.
o retentioncount
Relates to the cleanuptype parameter with value retainbycount. Specify the
number of last executions for which the parameter files and log files are not
deleted.
Default parameters:
With the following default parameters, the system indexes and tags 100 design
containers, then leaves 15000 milliseconds before indexing and tagging the next 100
design containers, and so on. It deletes parameter and log files but retains those with an
Caution
The TaskParameters are shared with any Stale Tag Cleanup tasks configured in the
indexing-configuration.xml file.
Note
If you need to kill a tagging task, for example, when you need to reboot the system
while it is running. You can kill it from your Task Manager. However, check that the
status of the task on the Tasks tab changes to FAILED. If the status is still RUNNING,
see “ANSTagGenerationTask or ANSStaleTagCleanupTask Runs for a Long Time” on
page 333 for instructions on how to reset it.
Related Topics
Configuring Stale Tag Cleanup Tasks to Run in the Background
Tagging Service
Troubleshooting Tagging Tasks
For example:
<ANSStaleTagCleanupTask autoschedule="true" cronexpression="0 0 0/1 * * ?" />
3. Find the TaskParameters line and edit the parameters:
• batchsize
The cleanup task processes batches of design containers. Specify how many design
containers are included in each batch.
• waittime
Specify how much time (in milliseconds) the system waits between finishing one
batch of design containers and starting on the next batch. This frees up the system
for any other scheduled tasks.
• cleanupfiles
As the ANSStaleTagCleanup task (and related ANSTagGeneration task) run
frequently, they accumulate task parameter files and log files quickly. Specify “true”
if you want the system to clean up (delete) these files automatically.
Specify “false” if you do not want to run clean-up functionality. If you want to
archive the files rather than delete them, you can implement your own OS batch
script.
• cleanuptype
If you have set cleanupfiles to “true”, this specifies how the files are cleaned up.
Specify one of the following values:
o simple
Deletes all the parameter files and log files for the task, excluding the files for
the current task run.
o retainbytime
Deletes all the files that are older than a specified retention time (retentiontime
parameter).
o retainbycount
Deletes all the files, excluding those for the specified number of last task
executions (retentioncount parameter).
o retentiontime
Relates to the cleanuptype parameter with value retainbytime. Specify the
maximum age (in milliseconds) of the parameter files and log files that are not
deleted.
o retentioncount
Caution
The TaskParameters are shared with any Indexing and Tagging tasks configured in
the indexing-configuration.xml file.
• You can monitor the tasks in the Tasks tab in Output Window, from which you can also
access log files. You can also access the log files in your temp directory.
Note
If you need to kill a tagging task, for example, when you need to reboot the system
while it is running. You can kill it from your Task Manager. However, check that the
status of the task on the Tasks tab changes to FAILED. If the status is still RUNNING,
see “ANSTagGenerationTask or ANSStaleTagCleanupTask Runs for a Long Time” on
page 333 for instructions on how to reset it.
Related Topics
Configuring Tagging Tasks to Run in the Background
Tagging Service
Troubleshooting Tagging Tasks
Video
To see how compare and propagate works, see the video “Using Compare and Propagate”.
Note
You can swap the designs in the Use and “to Update” fields by right-clicking on the
To Do List tab and choosing Swap. When you complete one or more tasks and click
Refresh, the system strikes the tasks off the list but does not remove them. If you
complete all tasks for an object, the entire group of tasks are struck off and the group
moves to the bottom of the list. To remove all completed tasks from the list, right-click
on the tab and select Restart.
Related Topics
To Do List Tab
Compare and Propagate
To Do List Tab
A To Do List tab is displayed at the bottom left of a design application window when you right-
click a design in the Project Browser Window and select To Do List. You can hide the tab by
right-clicking it and selecting Remove To Do Tab.
The tab displays a list of objects that require updating in a “to update” design due to changes
that have been made in a “Use” design. For example, you have added a device to a system
design (“Use” design) but you have not yet added it to an associated wiring design (“to Update”
design).
Related Topics
Viewing the To Do List for a Design
Compare and Propagate
ANSTagGenerationTask or
ANSStaleTagCleanupTask Fails
ANSTagGenerationTask or ANSStaleTagCleanupTask has a FAILED status in the Tasks tab
displayed in the Output Window of your Capital application.
Solution
Look at the corresponding XML task parameter file and execution log file for this task
execution to view the reason for the failure. The files are located in the temp directory for your
Capital installation on the computer where the task is or was being executed. The Machine
column on the Tasks tab indicates which computer this is.
ANSTagGenerationTask or
ANSStaleTagCleanupTask Runs for a Long Time
ANSTagGenerationTask or ANSStaleTagCleanupTask has a RUNNING status for a long time
in the Tasks tab displayed in the Output Window of your Capital application.
Solution
Check your Task Manager to see whether a CapitalRunner is visible in the processes.
This means the status of the task is stuck in RUNNING, when actually it is not running. For
example, this can occur if Capital Manager shut down during a forced computer restart. Reset
the task so that it starts running as per schedule again.
Look at the corresponding XML task parameter file and execution log file for this task
execution. The files are located in the temp directory for your Capital installation on the
computer where the task is or was being executed. The Machine column on the Tasks tab
indicates which computer this is.
If the log file reports that the task execution is complete, then the status on the Tasks tab has not
updated. Reset the task as described above.
If the log file does not report that the task execution is complete, it will report any exceptions
that have occurred.
For full details of how to configure the cismaster node, see the Flexible Execution Manager
(FEM) section in the Capital Configuration Files Reference Guide. The guide is available from
SupportNet and from InfoHub when you install a Capital client.
This chapter offers a description of the dialogs available in multiple Capital applications. For
each dialog, all fields are listed, along with a full description of the field’s function.
Project-related Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341
Edit Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Edit Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Project Folders Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Import Designs to Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Import Designs to Project Wizard Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Select Project Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
New Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Open Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Choose Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Project Preferences Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Copy Design Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 439
Create New Design Revision Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440
Editing Action Dialogs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 441
Applicable Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 442
Graphics Related Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Edit Border Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478
Add Text Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Image Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481
Symbol Selection Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482
Update Symbol - Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 483
Edit Properties - Propertied Graphic Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 484
Fill Pattern Selection Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487
Layout Related Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 488
Set Grid Defaults Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Split Table Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490
Miscellaneous Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Edit Diagram Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
New Property Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Plugins Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Plugin Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Batch Translate Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Edit Capital Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Release Designs Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Project-related Dialogs
This section offers a description of all dialogs used to open and create projects. For each dialog,
all fields are listed, along with a full description of the field’s function.
Edit Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342
Edit Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344
Project Folders Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345
Import Designs to Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346
Import Designs to Project Wizard Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349
Select Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 359
New Project Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 360
Open Project Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361
Options Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362
Choose Options Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Project Preferences Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365
Usage Notes
To add a property to the project, 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. To delete a property
from the list, select it and click the Delete button, then click OK to confirm the deletion.
Related Topics
Edit Project Dialog Box
Related Topics
Edit Properties Dialog Box
Usage Notes
You cannot rename or delete a project folder that contains a project. If you want to place a
project in a differently named folder, create that folder and select it. Any unused folders do not
display when you next open this dialog box.
Related Topics
Edit Project Dialog Box
Related Topics
Select Project Dialog Box
Import Designs to Project Wizard Dialog Box
Importing Designs into a Project
Table 10-5. Import Designs to Project Wizard Dialog Box Contents (cont.)
Field Description
Target Project Designs Design column lists the design s in the target project (to
which the designs are being copied or imported).
Mapped column indicates the design (in the Source Designs)
to which the target design is mapped. If blank, this means the
design is not mapped.
If a design exists in both the source designs and the target
project, it is mapped automatically.
If a design exists just in the source designs, it is created
automatically in this table and the from the source designs is
mapped to it.
Note that two design s from the source designs can be
mapped to one design in the target project.
Design Details Tab
Design Details Table Lists the source projects and source designs along with the
details for the new designs that will be created in the target
project. Click on a row to select a source design and the
details of its target design; the fields below the table are
updated to display the existing values.
New Adds a new row to the Design Details table, which can then
be populated by specifying values in the fields below it
before clicking Update.
Update Updates the selected row in the Design Details table with the
contents of the fields below it.
Reset Returns the cells in the Design Details table to their previous
state. This means that:
• If you have created a new row, all fields are cleared or
returned to their default selection.
• If you are editing an existing row for a design, the fields
are returned to their previous values.
Delete Deletes the selected row in the Design Details table.
Name A unique label to identify the design in the target project.
Enter a new name or click the ellipsis (...) button to the right
of the field to select from a list of pre-specified design names
maintained in the project’s Object Type Information. The
contents of this field are displayed in red if they are not
unique within the current project. Mandatory.
Table 10-5. Import Designs to Project Wizard Dialog Box Contents (cont.)
Field Description
Part Number Enabled only if a Capital HarnessXC design is selected in the
Design Details table.
By default, the current part number will be displayed in red,
indicating that the number is not unique within the database.
Specify a unique identifier for the derivative harness in the
database. The combination of this field and the Revision must
be unique within the database; if the combination already
exists, the contents of both fields are displayed in red.
Mandatory.
There are two ways to ensure uniqueness for the part number
of the new design:
• Overwrite the part number with a new, unique number.
• Enter a new code in the Revision field. Note that entering
a new revision code will not result in the copied design
being created as a revision of the existing design; to create
the copy as a revision, you must select the Copy As
Revision option.
Revision Specifies the version of the design, allowing multiple updated
versions of the same design (and, hence, the same Part
Number) to exist in the database. When creating a new
design, the initial version number or letter should be entered.
Subsequent revisions receive a new revision number as part
of their creation.
The combination of this field and the Part Number must be
unique within the database; if the combination already exists,
the contents of both fields are displayed in red. Mandatory.
Short Description Enter a line of descriptive text to provide more information
about the derivative design. Optional.
Description This is a free-text field into which you can enter additional
comments or notes relevant to this design. Optional.
Release Level A number of system-defined release levels are available. It is
possible to create custom levels in Capital Project (see
Creating the Release Levels for a Project). Regardless of the
number of custom levels available, they must correspond to
one of the system-defined release levels. Mandatory.
Table 10-5. Import Designs to Project Wizard Dialog Box Contents (cont.)
Field Description
Design If you are using design s, select the to which the design
belongs, from the dropdown list. Maintained in Capital
Project, s allow you to group related harnesses together for
reporting purposes, providing a “view” of a subset of a
vehicle’s wiring. See Creating the Design s for a a Project.
Optional.
Copy Associated Logic A design can have one or more associated Capital Logic
Designs designs. This option specifies whether these associated
designs are copied with this design (selected) or not
(unselected). Mandatory.
Effectivity Displayed only if Effectivity is enabled in the target project.
See Managing Effectivity for information about what
effectivity is.
Displays the effectivity range that is applied to the design.
Copy Generated Wiring A Capital Integrator design may have had wiring generated
for it. This option specifies whether you want to copy the
generated wiring with the design (selected) or not
(unselected). Mandatory.
Overwrite Revision If a design revision with the Name exists in the target project
already, specify whether you want to overwrite the existing
design revision (selected) or not (unselected). An import of a
design with an existing name is possible only when this is
selected. Mandatory if a design with the same name exists.
Copy As Revision To copy the design as a revision, you must select this option.
This means that the design created in the destination project
is a revision of the source design. In this case, you cannot edit
the name of the design but you must edit the revision level
and/or short description.
If you do not select this option, the design is treated as an
entirely new design in the destination project and any
connection with the source design is lost.
The setting of this option also effects the copying of shared
conductors and pin lists on the diagram. With this option
checked, all copied shared objects will retain their parent-
child revision relationships; with this option unselected, any
revision relationships will be lost, and the copied objects will
be created as new shared objects in the target project, with a
default revision of 1.
Mandatory.
Table 10-5. Import Designs to Project Wizard Dialog Box Contents (cont.)
Field Description
Shared Conductors Tab Used to configure the shared conductors used by the selected
designs.
Shared Conductors Table Lists the shared conductor revisions in the source designs.
If the designs being copied or imported contain any shared
conductors, but the target project does not contain any shared
conductors, the shared conductors are copied automatically to
the target project and are listed for reference only in this
table.
If the designs being copied or imported contain any shared
conductors, and the target project contains shared conductors,
you can select to:
• Copy a source shared conductor to the target project
without associating it with a target shared conductor.
To do this, select the source shared conductor in the table,
select Coo and click Update.
• Not copy a source shared conductor to the target project
but instead associate it with one in the target project.
To do this, select the source shared conductor in the table,
unselect Copy Shared Conductor, specify a Project
Shared Conductor and click Update. Note that you can
only associate shared conductors of the same type (for
example, net with net, wire with wire).
New Not used.
Update Updates the selected row in the Shared Conductors table with
the contents of the fields below it.
Reset Returns the cells in the Shared Conductors table to their
previous state.
Delete Not used.
Shared Conductor The name and revision of the shared conductor from the
source designs. Read-only.
Project Shared Conductor The name and revision of the shared conductor (from the
target project) that is associated with the Shared Conductor.
Select the target shared conductor from the drop-down list.
Mandatory only if Copy Shared Conductor is unselected.
Table 10-5. Import Designs to Project Wizard Dialog Box Contents (cont.)
Field Description
Copy Shared Conductor Specifies whether the source shared conductor that is selected
in the Shared Conductors table is copied to the target project
(selected) or whether it is not copied but is associated with a
shared conductor in the target project (unselected). If not
copied, the target shared conductor is specified by Project
Shared Conductor. Mandatory.
Shared Pin Association
Defaults Tab
Automatic Association If the designs being copied or imported contain any shared
Configuration Mode pin lists, this option specifies the method of association
between the pins on the source designs and the pins in the
target project:
• Merge Unrestricted pins - reuse existing pins where
there is a match between names. Unrestricted pins remain
unrestricted. If a reserved pin is used in more than one
design being copied or imported, then it becomes
unrestricted.
• Merge Reserved pins - always reuse existing pins where
there is a match between names. Unrestricted pins remain
unrestricted. Manually reserved pins remain manually
reserved to designs where used. Automatic reservation
pins remain automatic reservation pins and their usages
are updated with all copied or imported designs.
Mandatory.
Automatically Associate Specifies whether any pin lists (and their pins) of the same
name on the source design and target project are associated
automatically (selected) or not (unselected).
If you do not select this, you manually associate the source
pin lists with the target pin lists on the Shared Pin Lists tab.
Note that if this option is selected, any pin lists in the source
design that are not already present in the project will be
automatically be created and associated in the target project.
Mandatory.
Shared Pin Lists Tab Enables you to associate shared pin lists and their pins from
the source designs with shared pin lists in the target project.
Associate Pin Lists Used to associate shared pin lists in the source designs with
shared pin lists in the target project.
Table 10-5. Import Designs to Project Wizard Dialog Box Contents (cont.)
Field Description
Source Design Table Source Design column lists the shared pin lists from the
source designs (designs being copied).
Mapped to column indicates the shared pin list (in the Target
Project table) to which the source shared pin list is mapped. If
blank, this means the shared pin list is not mapped.
The following rules apply to the mapping of pin lists:
• If you have selected Automatically Associate on the
Shared Pin Association Defaults tab, pins are
automatically associated when pin lists are associated.
• You can map a pin list on the source design only to one of
the same type on the target project (that is, device to
device, plug to plug, and so on).
• A shared inline pin list can be mapped to only a target
inline pin list that possesses the same, or a greater number
of pins.
• Any target pin lists that are not permitted to be mapped to
the selected source pin list, are unavailable for selection
(grayed-out).
• Before you can proceed to the next tab, you must have
mapped all of the pin lists (and their pins) on the source
design, with pin lists on the target project.
See Rules for Shared Objects When Copying, Importing or
Exporting Designs for further information about rules that
apply to shared objects.
Associate Maps the selected shared pin list in the Source Design table to
the selected shared pin list in the Target Project table.
Disassociate Clears the currently-selected mapping in the Source Design
table and Target Project table fields.
Disassociate All Clears all mappings in the Source Design table and Target
Project table fields.
Associate All Creates mappings for all shared pin lists in the Source Design
table.
Table 10-5. Import Designs to Project Wizard Dialog Box Contents (cont.)
Field Description
Target Project Table Target Project column lists the shared pin lists in the target
project (to which the designs are being copied or imported).
Mapped from column indicates the shared pin list (in the
Source Design table) to which the target shared pin list is
mapped. If blank, this means the shared pin list is not
mapped.
The following rules apply to the mapping of pin lists:
• If you have selected Automatically Associate on the
Shared Pin Association Defaults tab, pins are
automatically associated when pin lists are associated.
• You can map a pin list on the source design only to one of
the same type on the target project (that is, device to
device, plug to plug, and so on).
• A shared inline pin list can be mapped to only a target
inline pin list that possesses the same, or a greater number
of pins.
• Any target pin lists that are not permitted to be mapped to
the selected source pin list, are unavailable for selection
(grayed-out).
• Before you can proceed to the next tab, you must have
mapped all of the pin lists (and their pins) on the source
design, with pin lists on the target project.
See Rules for Shared Objects When Copying, Importing or
Exporting Designs for further information about rules that
apply to shared objects.
Add Adds a new shared pin list to the Target Project table and
maps the selected shared pin list in the Source Design table to
it. The new shared pin list is named using the default object
naming protocol for the target project.
Remove Removes the selected shared pin list from the Target Project
table.
Associate Pins Used to associate pins from the selected shared pin list in the
Source Design table with pins from the associated shared pin
list in the Target Project table.
Table 10-5. Import Designs to Project Wizard Dialog Box Contents (cont.)
Field Description
Source Pins Table Once you have associated a source shared pin list (Source
Design table) with a target shared pin list (Target Project
table), you can associate their pins.
Source Pins column lists the shared pins from the source pin
list selected in the Source Design table.
Mapped to column indicates the shared pin (in the Target
Pins table) to which the source shared pin is mapped. If
blank, this means the shared pin is not mapped.
If there are duplicate pin names in a pin list, you can double-
click on a pin in a table to display the attributes for the pin.
Associate Maps the selected shared pin in the Source Pins table to the
selected shared pin in the Target Pins table.
Disassociate Clears the currently-selected mapping in the Source Pins
table and Target Pins table fields.
Disassociate All Clears all mappings in the Source Pins table and Target Pins
table fields.
Associate All Creates mappings for all shared pins in the Source Pins table.
Target Pins Table Once you have associated a source shared pin list (Source
Design table) with a target shared pin list (Target Project
table), you can associate their pins.
Target Pins column lists the shared pins in the target pin list
selected in the Target Project table.
Mapped from column indicates the shared pin (in the Source
Pins table) to which the target shared pin list is mapped. If
blank, this means the shared pin list is not mapped.
If there are duplicate pin names in a pin list, you can double-
click on a pin in a table to display the attributes for the pin.
Add Adds a new shared pin to the Target Pins table and maps the
selected shared pin in the Source Pins table to it. The new
shared pin is named using the default object naming protocol
for the target project.
Remove Removes the selected shared pin from the Target Pins table.
Pin Reservations Enables you to specify whether the pins listed in the Target
Pins table are automatic reservation or unrestricted.
Automatic Reservations Table List any automatic reservation pins from the Target Pins
table.
Table 10-5. Import Designs to Project Wizard Dialog Box Contents (cont.)
Field Description
Add Converts the selected automatic reservation pin in the
Automatic Reservations Table to an unrestricted pin and
moves it to the Unrestricted Pins Table. You can select
multiple pins by using the Shift or Ctrl keys with your
mouse.
Add All Converts all automatic reservation pins in the Automatic
Reservations Table to unrestricted pins and moves them to
the Unrestricted Pins Table.
Remove Converts the selected unrestricted pin in the Unrestricted Pins
Table to an automatic reservation pin and moves it to the
Automatic Reservations Table. You can select multiple pins
by using the Shift or Ctrl keys with your mouse.
Remove All Converts all unrestricted pins in the Unrestricted Pins Table
to automatic reservation pins and moves them to the
Automatic Reservations Table.
Unrestricted Pins Table List any unrestricted pins from the Target Pins table.
Summary Tab Displays a summary of the options that you have selected in
the wizard.
Related Topics
Select Project Dialog Box
Import Designs to Project Dialog Box
Importing Designs into a Project
Related Topics
Creating an Option Folder at Project Level
Defining Inclusive and Exclusive Relationships for an Option
Creating an Option Combination at Project Level
Adding a Valid Selection to an Option Combination
Deleting a Valid Selection from an Option Combination
Related Topics
Creating an Option Folder at Project Level
Defining Inclusive and Exclusive Relationships for an Option
Creating an Option Combination at Project Level
Adding a Valid Selection to an Option Combination
Deleting a Valid Selection from an Option Combination
Table 10-11. Project Preferences for Capital Harness MPM and Capital
Harness TVM Designs
Field Description
Capital Harness MPM Displayed in the Project Preferences browser.
node Displays project preferences for Capital Harness MPM and Capital
Harness TVM designs.
Sub-assembly name Displayed in the Project Preferences pane when you select Capital
prefix Harness MPM in the Project Preferences browser.
Setting used to specify a prefix for sub-assemblies such as project or
design name. This is combined with a system generated suffix to
identify where a particular sub-assembly fits in the SBOM structure.
Table 10-11. Project Preferences for Capital Harness MPM and Capital
Harness TVM Designs (cont.)
Field Description
Sub-assembly part Displayed in the Project Preferences pane when you select Capital
number prefix Harness MPM in the Project Preferences browser.
Setting used to specify a prefix for sub-assembly part number. This
is combined with a system generated suffix to help identify common
cross-harness sub-assemblies for maximum reuse and optimization.
Part Number Displayed under Capital Harness MPM in the Project Preferences
Rationalization browser.
Tolerance Used by the Set Master Part Numbers Dialog Box to filter the
display of similar sub-assembly part numbers whose wire/multicore
length differences are greater than but within the defined tolerance
value when configuring sub-assembly part number rationalization.
Mandatory.
Checks node Displayed under Capital Harness MPM in the Project Preferences
browser.
Displays project preferences for running design rule checks on a
Capital Harness MPM/Capital Harness TVM SBOM and Costing
Generation. See Design Rule Checks Applicable to Capital
HarnessXC and Capital ModularXC Designs for full details of
available checks.
Table 10-11. Project Preferences for Capital Harness MPM and Capital
Harness TVM Designs (cont.)
Field Description
Running Mode Displayed in the Project Preferences pane when you select Capital
Harness MPM > Checks in the Project Preferences browser.
Located at the top of the dialog, this enables you to select a running
mode for design rule checks from a dropdown list.
Select a running mode and a Design Abstraction to specify a
scenario for running design rule checks (that is, running checks in a
particular mode on a design with a particular abstraction). You can
then use the Design Rule Checks browser to select the design rule
checks that are run automatically and their severity for this particular
scenario. The running modes are:
• Manual
When you run design rule checks manually in a design
application by pressing Space Bar and entering DRCs and
selecting the checks that you want to run. The Check tab of the
output window displays the results.
• Background
When design rule checks are run automatically in the background
in a design application. Background runs occur when the
background mode has been activated and after changes have
been made to objects in the design to which the currently active
diagram belongs. The Check tab of the output window displays
the results.
You should set as small a number as possible of checks to run in
the background as they will use memory.
• On Save
When design rule checks are run automatically on saving a
diagram in a design application. If there are any failures of
severity Error, the save is canceled and the Check tab of the
Output Window displays the failures. By default, no design rule
checks are run for the On Save mode. If you want checks to run
when you save, you must specify preferences for this mode.
You should set as small a number as possible of checks to run in
the background as they will use memory.
• On Release
When design rule checks are run automatically on releasing a
diagram. The Check tab of the output window displays the
results.
Table 10-11. Project Preferences for Capital Harness MPM and Capital
Harness TVM Designs (cont.)
Field Description
Design Abstraction Displayed in the Project Preferences pane when you select Capital
Harness MPM > Checks in the Project Preferences browser.
Located at the top of the dialog, enables you to select a design
abstraction from a dropdown list.
Select a Running Mode and a design abstraction to specify a
scenario for running design rule checks (that is, running checks in a
particular mode on a design with a particular abstraction). You can
then use the Design Rule Checks browser to select the design rule
checks that are run automatically and their severity for this particular
scenario.
The list of design abstractions depends on those available in the
project. You can select an empty row from the dropdown list that
represents designs without a design abstraction. Designs which
reference an abstraction which no longer exists also default to the
empty abstraction rule check configuration.
Table 10-11. Project Preferences for Capital Harness MPM and Capital
Harness TVM Designs (cont.)
Field Description
Design Rule Checks Displayed in the Project Preferences pane when you select Capital
browser Harness MPM > Checks in the Project Preferences browser.
Lists the available design rule checks, grouped into categories, in a
tree where you can set preferences for each check.
See Design Rule Check Descriptions for a detailed explanation of
each available Design Rule Check.
The preferences for each check apply only to the selected
combination of Running Mode and Design Abstraction. When you
change the preferences for a particular combination, ensure that you
click Apply at the bottom of the dialog before selecting a new
running mode or design abstraction.
Select a design rule check in the tree if you want it to run
automatically. Unselect it if you do not want it to run automatically.
If you select or unselect a design rule check category (for example,
Connectivity), all of the checks under that category are selected or
unselected.
Right-click on the symbol next to a design rule check to specify
whether a failure for that check generates an error, a warning or a
notification (information).
In addition, right-click on the symbol and select or unselect Show to
specify whether the check is (selected) or is not (unselected) listed in
the Design Rule Checks dialog (used for manually running checks)
in the design application. If Show is unselected, the check is grayed
out in the tree, although you can still right-click on it to edit its
preferences. In addition to not being listed for selection, a check with
Show unselected will not run.
The tree includes installed custom design rule checks but their
preferences come from the plug-in and cannot be edited here.
For example:
Number of grids to Displayed in the Project Preferences pane when you select Capital
separate hookups Logic > Multicore > Indicator in the Project Preferences browser.
Specifies the number of grid spaces that separate hookups from the
indicator and from each other if Separate Hookups at different
levels is selected.
same width.
.
If the pin grid preference is changed, for example to 6 and the toggle
action is performed, then the indicator would stretch as shown below
and both these wires are grouped, as the distance between the bottom
left extent of these wires (a setting of 5 in the pin grid field) is still
within the project preference specified (a setting of 6 in the pin grid
field).
Name node Displayed under Capital Logic in the Project Preferences browser.
Expands to display nodes of project preferences for object name text
in Capital Logic diagrams.
Here you can see there is a bright green line drawn for the part of P1
that is flush with the slot. The line for the slot is then drawn over that
bright green line.
If this option is not selected, no connector line is drawn flush with
the slot.
Name node Displayed under Capital Topology in the Project Preferences
browser.
Expands to display nodes of project preferences for object name text
in Capital Topology diagrams.
Text node Displayed under Capital Topology > Name in the Project
Preferences browser.
Displays project preferences for object name text in Capital
Topology diagrams.
Name Displayed in the Project Preferences pane when you select Capital
Topology > Name > Text in the Project Preferences browser.
Specifies the type of font used for the object name text and whether
it is bold and/or italic. Select the values from the dropdown lists.
Objects
Object Description
Standard design fields This dialog box contains the standard
fields used when creating a new design.
For a Capital Integrator design, see
Creating a New Design.
For a Capital Topology design, see New
Topology Design Dialog.
Retain Generated Names Select this if you want the copy to retain
object names that have been generated
using Advanced Naming. If you do not
select this, object names return to default
object names in the copy.
Objects
Object Description
Standard design fields This dialog box contains the standard fields
listed when creating a design.
For a Capital Integrator design, see Creating
a New Design.
For a Capital Topology design, see New
Topology Design Dialog.
Usage Notes
For composite harness designs, the order of the options in the Selected window controls the
order in which they are displayed in the composite table in the design. To change the order,
select an option and click either:
Note
Where applicable - Derivative designs inherit the option order from their composite, hence
these buttons are not available when editing a derivative design. As options are added to the
Selected list, they will adopt the order defined for the composite.
Related Topics
Comparing Objects and Their Properties in Design Revisions or Build Lists
Related Topics
Comparing Objects and Their Properties in Design Revisions or Build Lists
Usage Notes
Click the OK button to save the breakout code information to the object type and close the
dialog.
Related Topics
Applying Scopes to a Project or Design
Delete selected effectivity Deletes the selected row in the Effectivity table.
range
Revisions Lists the existing revisions of the design and the
effectivity ranges that have been specified for those
revisions. Read-only.
For example: if 1[1..10] is listed, this means that the
range 1 to 10 has been specified for revision 1 of this
design.
Table 10-29. Edit Name Text Attributes Dialog Box Contents (cont.)
Field Description
Layout Specifies the layout of the text in relation to its bounding box in the
diagram:
• Clip
If selected, specifies that the text is clipped at the edge of its
bounding box.
• Shrink to fit
If selected, specifies that the font of the text reduces as necessary
so that the text fits in its bounding box.
• Overflow
If selected, specifies that the text ignores the edge of its bounding
box and flows out of it.
• Wrap text
Specifies whether the text wraps onto multiple lines when it
reaches the edge of the text bounding box (selected) or whether the
text ignores the bounding box and continues on one line
(unselected). When this is selected, if a word is too long to fit on a
single line, it is wrapped by character.
The Preview shows the behavior that you have selected.
Related Topics
Specifying the Name Property of an Object
Editing the Display-details of the Object's Short Description
Replace Specify the types of existing object names that you want to replace
with newly generated names:
• Default Names - the names generated automatically when an
object is created.
• Generated Names - names that have been generated previously
using the advanced naming functionality. You may want to select
this if naming compositions and conditions have been updated in
Capital Project.
• Fixed Names - these have been defined in the Edit Properties
dialog for objects and have been set as fixed.
Usage Notes
If you check both the Replace Object Indices box and the Reset Counters box, the indices on
the objects will start from 1.
If the Reset Counters box is checked and the Replace Object Indices box is not checked, the
indices on the selected objects do not change but the counter will start from 1 again when you
create new objects.
For example:
If you have three objects with the indices 4, 5 and 6, those indices will remain 4, 5 and 6.
However, when you create a new object that uses that counter, it will have the index value 1.
The next new object created after that will have the index value 2, and so on.
Related Topics
Generating Names for Selected Objects in a Diagram
Generating Names for all Objects in a Build List, Design or Diagram
Related Topics
Comparing Objects and Their Properties in Design Revisions or Build Lists
Objects
Usage Notes
If a placeholder was used as the value for a property in Capital Symbol, you cannot edit it here.
See Adding Information Placeholders to a Border in the Capital Symbol User Guide for more
information.
Related Topics
Link or Embed Images
Table 10-44. Edit Properties - Propertied Graphic Dialog Box Contents (cont.)
Field Description
Graphics Tab
Primary Color Select a color from the dropdown list; it is previewed in the window to
the right of the field. 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 is displayed, where you can
select a color.
Thickness Specify the thickness of the lines of the graphical shape. Mandatory.
To use the default thickness, select Default from the dropdown list.
To use a different thickness, select Override from the first dropdown
list and select the type of thickness from the final dropdown list:
• Logical
These thicknesses do not have a physical unit of measurement.
They provide a logical progression of thickness with a default of 1.
A line with thickness 2 is displayed twice as thick as a line with
thickness 1, and so on. When you zoom in or out of a diagram, the
line thickness does not appear any different.
You select the thickness from the middle dropdown 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 dropdown list changes to a free
text field where you specify the thickness. The value can be any
floating-point number up to three decimal places.
See “Physical Line Thickness” on page 258 for a definition and
links to related task flows.
Table 10-44. Edit Properties - Propertied Graphic Dialog Box Contents (cont.)
Field Description
Line Style Specify the style of the lines of the graphical shape. Mandatory. To
use the default style, select Default from the dropdown list.
To use a different style, select Override from the dropdown list and
select the style from the second dropdown list that is displayed.
Fill Pattern Selection Specify the fill pattern of the graphical shape. To use the default fill
pattern, select Default from the dropdown list. To use a different fill
pattern, select Override from the dropdown list and click Change to
display the Fill Pattern Selection Dialog Box where you select a fill
pattern. Mandatory
Usage Notes
Displayed only for a graphical shape that encloses space.
Usage Notes
The co-ordinates displayed at the bottom right of the Capital Symbol application use the units
specified for Grid Size.
Related Topics
Manual Table Splitting
Miscellaneous Dialogs
This section offers a description of various miscellaneous dialogs. For each dialog, all fields are
listed, along with a full description of the field’s function.
Edit Diagram Properties Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
New Property Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 494
Plugins Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495
Plugin Details Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 496
Batch Translate Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Edit Capital Configuration Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498
Release Designs Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499
Engineering Change Orders Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501
Engineering Change Orders Tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506
Change Manager Apply ECO Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508
Options (Apply ECO) Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514
Change Manager Preview ECO Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 517
Objects
Object Description
Properties To add a property tjo the design, 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. 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
Related Topics
Converting Free Text Strings into Translations
Design rule checks browser Displays the design rule checks that will be run on the designs
when you click OK.
These are specified in the Project Preferences for an
application (the appropriate preferences are displayed when
you select the Checks node for an application in the Project
Preferences Dialog Box).
Release Level Lists the release levels of type Released that are available.
Select the release level with which you want to release the
designs.
Related Topics
Releasing Designs with Enforced Design Rule Checks
• Clicking the “Details” button on ECO Tab of the Edit Design Properties Dialog Box
Use this dialog box to create, edit, import/export and delete Engineering Change Orders
(ECOs).
Objects
Related Topics
Capture and Apply a Change Within an ECO
Creating an Engineering Change Order
Engineering Change Orders Tab
Change Manager Apply ECO Dialog Box
Options (Apply ECO) Dialog Box
Apply Change Output Window
Change Manager Preview ECO Dialog Box
Applicable Changes Dialog Box
Simulate Change Output Window
Usage Notes
• The columns are sortable by clicking in the column header. The columns are filterable
by clicking in the first cell of each column.
Related Topics
Capture and Apply a Change Within an ECO
Creating an Engineering Change Order
Change Manager Apply ECO Dialog Box
Engineering Change Orders Dialog Box
Options (Apply ECO) Dialog Box
Apply Change Output Window
Change Manager Preview ECO Dialog Box
Applicable Changes Dialog Box
Simulate Change Output Window
Objects
Table 10-56. Change Manager Apply ECO Dialog Box Contents (cont.)
Field Description
Auto Link All objects for which a match can be found will have their source
ids synchronized when a Synchronize Object action is performed.
This is to allow you to compare changes on the object after linking
or auto-linking. The Status field for those objects in the Harness
Objects Grid displays Successful and the Origin field displays
Linked.
See the Link action, below, for a description of the behavior of
linked objects.
Link Creates a permanent association between the target object and its
counterpart in the source. This link is maintained by updating the
Target object with the Source ID of the Source object. If required
the appropriate module code expressions are also assigned to the
object.
To link an object, first select it in the Harness Objects Grid or in
the Change Manager Preview ECO Dialog Box, then press Space
Bar and enter Link, and finally click the object in the open harness
diagram to which the object should be linked. The Status field for
the object displays Successful and the Origin field displays
Linked.
Note: You can cancel the linking process without selecting an
object by pressing Space Bar and entering Cancel.
Upon linking an object, its source id is synchronized whenever a
Synchronize Object action is performed. See the Synchronize
Object action, below, for more information.
Once linked, selecting an object in either the Change Manager
Apply ECO Dialog Box, Change Manager Preview ECO dialog
box or the open diagram for the current harness, results in the same
object being selected in the other two views.
Synchronize Object Updates the attributes and properties of the Target object with the
values belonging to the linked object in the Source, subject to any
change policy specified in the Options (Apply ECO) Dialog Box.
User-defined properties are also synchronized. Filters declared in
adaptors.xml (found in your capital_home/adaptors folder) are
also taken into account. (See “Filters” in the Bridging Data In and
Out of Capital User Guide for further information).
Where applicable, Length rounding rules are honored (see
“Harness Shape Parameters” in the Capital Diagram Styling User
Guide).
The effects of synchronization vary for different objects; see
Harness Object Behavior on Applying ECO Changes for more
information.
Table 10-56. Change Manager Apply ECO Dialog Box Contents (cont.)
Field Description
Unlink Clears the value in the selected Capital object’s External ID
attribute, breaking the link with the Source object.
Report Generates a list of all supported object attributes and the values
contained within the Target and Source objects. All applied
changes are reported. Where a mismatch between the two is found,
the issue is reported as a warning. The report is displayed on the
Apply Change Output Window tab.
Map Derivatives This option opens the Derivative Mapping dialog box which
performs the following action (subject to any change policy
specified in the Options (Apply ECO) Dialog Box).
• If any derivatives exist in the Source harness that are not
currently mapped to Target derivative designs, the dialog box
is displayed enabling you to either map to an existing
derivative, or create a new one using the derivative details in
the Source data.
Map Modules This option opens the Module Mapping dialog box which
performs the following action (subject to any change policy
specified in the Options (Apply ECO) Dialog Box).
• If any modules exist in the Source data, the Module Mapping
dialog box is displayed enabling you to either map to an
existing module design, or create a new one using the module
details in the Source data.
Auto Link Harness Performs an auto-linking on all Source harness objects. Objects for
Objects which a match can be found based on the autolink criteria will
have their source ids synchronized when a Synchronize Object
action is performed. This is to allow you to compare changes on
the object after linking or auto-linking. The Status field for those
objects in the Harness Objects Grid displays Successful and the
Origin field displays Linked.
See the Link action, for a description of the behavior of linked
objects.
Table 10-56. Change Manager Apply ECO Dialog Box Contents (cont.)
Field Description
Process This single action is a combination of Place, Auto Link, and
Synchronize Object. Once the action is selected a progress bar
appears indicating the current status of the action.
This option also performs the following actions (subject to any
change policy specified in the Options (Apply ECO) Dialog Box):
• Updates and synchronizes the attributes and properties of the
objects in the Target harness. If, for any reason, some of the
links were broken, the Auto-Link Criteria will be applied to re-
establish the link.
• Creates new options in the current project if any found in the
changed harness data do not already exist.
• Updates the applicable options on the Target harness with
those in the Source harness (if different).
View
Display Report With this option selected:
• The Apply Change Output Window displays when the ECO is
processed.
• When the harness is validated - either automatically or
manually - a report is generated.
With this option unselected, no report is generated, and a warning
message is issued only if an error is encountered during validation.
Detailed Report Toggles the Change Manager report content between condensed
short reports or full detailed reports.
View Toggles the display of the Change Manager Preview ECO Dialog
Box.
Filter Filters the items displayed in the Harness Objects grid of the
Change Manager Apply ECO Dialog Box.
Refresh Refreshes the Harness Objects grid.
Zoom Selected (Design) Select this option, or press Z, to immediately locate and highlight
the selected object on the harness diagram.
Zoom Selected (Preview) Select this option, or press P, to immediately locate and highlight
the selected harness object in the Preview window.
Harness Objects Grid This grid lists all supported objects found in the ECO change.
Certain actions in the Harness Objects grid are available by right-
clicking and accessing the context menu.
Type The component type, such as Bundle, Clip, Tube, and so on.
Table 10-56. Change Manager Apply ECO Dialog Box Contents (cont.)
Field Description
Origin Specifies whether the object exists only in the source data or, the
Target harness design, or whether it has been linked and is
therefore present in both.
Status Provides feedback on the results of the last linking action
performed for the object. If the linking was not successful, an
appropriate warning is displayed. Where an issue is encountered,
further information on the problem is provided on the Change
Manager tab in the Output Window.
Target The design-level name assigned to the object in the Target harness.
Source The name assigned to the object in the Source.
User FM The user generated functional modules codes assigned to the
object in the Source. It is possible to filter on these by typing the
filter string in the text field of the column header. Capital
ModularXC only
Generated FM The system generated functional modules codes assigned to the
object in the Source. It is possible to filter on these by typing the
filter string in the text field of the column header. Capital
ModularXC only
User PM The user generated production modules codes assigned to the
object in the Source. It is possible to filter on these by typing the
filter string in the text field of the column header. Capital
ModularXC only
Generated PM The system generated production modules codes assigned to the
object in the Source. It is possible to filter on these by typing the
filter string in the text field of the column header. Capital
ModularXC only
Source ID The unique identifier given to the object in the Source. It is this
value that is inserted into the target object’s ID field, creating the
link between the two.
Toolbar The Change Manager toolbar provides quick access to certain
commands on the Actions and View menus. Results of operations
executed from the toolbar are immediately applied to the Change
Manager Preview ECO Dialog Box.
Auto Link Performs an auto-linking on Source harness objects. See Auto
Link.
View Toggles the display of the Change Manager Preview ECO dialog
box.
Filter Used to filter the items displayed in the Harness Objects grid of the
Change Manager Preview ECO dialog box.
Table 10-56. Change Manager Apply ECO Dialog Box Contents (cont.)
Field Description
Refresh Refreshes the Harness Objects Grid.
Process Initiates the Process action, which is a single action that performs
all required steps automatically to apply changes, while adhering
to defined policies.
The Source data applied to the Target harness.
• Objects are Auto-Linked.
• Existing linked objects are synchronized (updated).
• Obsolete objects are deleted.
• New objects are added.
Note: Existing bundles with topology changes are re-connected
using the incoming structure if “Optimize Bundle Topology
Match” was selected on the Applicable Changes Dialog Box.
Related Topics
Capture and Apply a Change Within an ECO
Creating an Engineering Change Order
Simulate Change Output Window
Engineering Change Orders Tab
Engineering Change Orders Dialog Box
Options (Apply ECO) Dialog Box
Apply Change Output Window
Change Manager Preview ECO Dialog Box
Applicable Changes Dialog Box
Description
These are used when applying changes from an ECO Impacted Designusing the “Change
Manager Apply ECO” dialog box. The different options are organized on separate tab pages to
ease accessibility.
Objects
Related Topics
Capture and Apply a Change Within an ECO
Creating an Engineering Change Order
Simulate Change Output Window
Objects
Table 10-58. Change Manager Preview ECO Dialog Box Contents (cont.)
Field Description
View The following options control the way in which the harness is
displayed in the preview window, but do not affect the harness
topology in any way.
• Zoom In
Increases the size at which the preview is displayed. Can also
be accessed by clicking the icon on the toolbar.
• Zoom Out
Decreases the size at which the preview is displayed. Can also
be accessed by clicking the icon on the toolbar.
• Zoom All
Sets the size of the preview such that it comfortably fills the
window. Can also be accessed by clicking the icon on the
toolbar.
• Zoom Synchronized
Sets the zoom level of the preview to match that defined for
the active diagram window. Can also be accessed by clicking
the icon on the toolbar.
• Show Labels
Toggles the display of component names in the preview
window. Can also be accessed by clicking the icon on the
toolbar.
• Show Splices
Table 10-58. Change Manager Preview ECO Dialog Box Contents (cont.)
Field Description
View (continued) • Show Protections
Toggles the display of protections (indicated by a thicker
linestyle than an unprotected bundle). Can also be accessed by
clicking the icon on the toolbar.
• Show Connectors
Usage Notes
The following actions are supported in the preview window:
• Bundles are represented as lines, nodes as the intersections between them. Text labels
can also be displayed, together with splices, connectors, protections and fixings. A
color-coding scheme is used to represent different preview objects as follows:
o Green denotes an unlinked bundle, connector, or device.
o Blue denotes an unlinked splice, fixing or protection.
o Grey denotes a linked bundle or device.
o Red denotes a selected item.
• Object Selection
The preview includes a representation of all of the objects in the recorded change that
can be illustrated graphically. Selecting an object in the preview pane results in the same
object being selected in both the Change Manager Apply ECO Dialog Box and in the
diagram window.
o Select a single object by left-clicking on it.
o Select multiple objects by clicking and dragging out a rectangular selection; upon
releasing the mouse button, all objects falling wholly or partly within the rectangle
are selected.
o Deselect all objects by clicking on an empty area of the window.
• Panning
Middle-click within the preview window and drag to move the window contents.
Note
Middle click is also referred to as mouse button 3, and is activated by pressing down
on the mouse scroll wheel, where available.
• Zooming
If your mouse has a scroll wheel, you can use it to zoom into/out of the preview.
Objects
• An example is shown below.
Usage Notes
Figure 10-1. Simulate Change Tab
Related Topics
Capture and Apply a Change Within an ECO
Creating an Engineering Change Order
Change Manager Preview ECO Dialog Box
Engineering Change Orders Tab
Engineering Change Orders Dialog Box
Applicable Changes Dialog Box
Apply Change Output Window
Change Manager Apply ECO Dialog Box
Objects
Usage Notes
• You can click any hyperlinked object in the report to jump to that object in the diagram
window.
• The columns are sortable by clicking in the column header. The columns are filterable
by clicking in the first cell of each column.
• Click the icon at the top right of the tab to display a popup menu:
o Clear
Clears the Apply Change output window.
o Show All
Displays the complete report generated during the current design session.
o Save to CSV
If required for future reference, the report can be saved 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.
Related Topics
Capture and Apply a Change Within an ECO
Creating an Engineering Change Order
Change Manager Preview ECO Dialog Box
Engineering Change Orders Tab
Engineering Change Orders Dialog Box
Applicable Changes Dialog Box
Change Manager Apply ECO Dialog Box
Objects
Related Topics
Capture and Apply a Change Within an ECO
Creating an Engineering Change Order
Change Manager Preview ECO Dialog Box
Engineering Change Orders Tab
Engineering Change Orders Dialog Box
Change Manager Apply ECO Dialog Box
Apply Change Output Window
Simulate Change Output Window
Objects
Related Topics
Capture and Apply a Change Within an ECO
Creating an Engineering Change Order
Change Manager Preview ECO Dialog Box
Engineering Change Orders Tab
Engineering Change Orders Dialog Box
Change Manager Apply ECO Dialog Box
Apply Change Output Window
Simulate Change Output Window
Related Topics
Using the Report Builder
Design Inspectors
Printing Dialogs
This section offers a description of dialogs related to printing functions. For each dialog, all
fields are listed, along with a full description of the field’s function.
CGM Page Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529
DXF Page Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531
PDF Page Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532
SVG Page Settings Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534
Print Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536
Edit Print Region Groups Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539
Print to File Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541
Project Diagram Settings Dialog Box. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 544
Edit File Name Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 545
Objects
Related Topics
Print to a File
DXF Page Settings Dialog Box
PDF Page Settings Dialog Box
SVG Page Settings Dialog Box
Related Topics
Print to a File
CGM Page Settings Dialog Box
PDF Page Settings Dialog Box
SVG Page Settings Dialog Box
Print to File Dialog Box
Related Topics
Print to a File
CGM Page Settings Dialog Box
DXF Page Settings Dialog Box
SVG Page Settings Dialog Box
Print to File Dialog Box
Objects
Related Topics
Print to a File
CGM Page Settings Dialog Box
DXF Page Settings Dialog Box
PDF Page Settings Dialog Box
Usage Notes
• The option to create multiple diagrams is a licensed operation; if you do not have the
required license, yet are attempting to print a diagram from a design with multiple
diagrams, no printed output is generated.
• If a diagram has an associated border, the “Clip To Border” option will be selected by
default. If the “Clip To Border” option is selected for a diagram without an associated
border, the setting will be ignored when the diagram is printed.
Related Topics
Print to a Printer or Plotter
Printing a Single Diagram
Printing All Diagrams in a Project
Printing All Diagrams in a Design
Usage Notes
To move a print region within the list, first select it, then click one of the following:
• to move the selected print region or group to the top of the list.
• to move the selected print region or group up one position in the list.
• to move the selected print region or group down one position in the list.
• to move the selected print region or group to the bottom of the list.
Related Topics
Print to a File
Related Topics
Printing All Diagrams in a Project
Print to a Printer or Plotter
Related Topics
Print to a File
Related Topics
Defining Rules
Assigning a Rule or Constraint to an Object or Design
Related Topics
Defining Rules
Related Topics
Defining Rules
Assigning a Rule or Constraint to an Object or Design
Related Topics
Assigning a Rule or Constraint to an Object or Design
Warning Dialogs
This section offers a description of warning dialogs. For each dialog, all fields are listed, along
with a full description of the field’s function.
Undoable Operation Confirmation Dialog Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553
Usage Notes
The Filter Options can be set interactively in the Design Log Viewer Dialog Box.
Related Topics
Viewing Design Logs
Related Topics
Viewing Design Logs
View Design Logs Dialog Box
Table 10-79. Design Log Viewer Dialog Box (Non-Bridge Logs) Contents
Field Description
Filter Options The following Event Type line items can be turned off or on in the
design log. Select an option to have it displayed; deselect an option
to hide that line item. The following line items are available:
Header, Info, Warnings, Errors, Blank.
Refresh Click this button to update the Events grid to reflect any changes
made to the Filter Options.
Events This window displays the contents of the log file.
Table 10-80. Design Log Viewer Dialog Box (Bridge Logs) Contents
Field Description
Severity Whether the result is an error ( ), a warning ( ), or an
information message ( ).
Operation The particular type of bridging activity that has been run (for
example, Place, Autolink, Synchronize, and so on).
Object type The specific object type on which a bridging activity has been run.
To make the list more manageable it can be filtered to show only
the required object types. These are:
• All
• Connector
• Bundle
• Splice
• Clip
• Grommet
• Tape
• Tube
• Wire
• Multicore
Table 10-80. Design Log Viewer Dialog Box (Bridge Logs) Contents (cont.)
Field Description
Object The specific object on which a bridging activity has been run.
Message Detailed message about the bridging activity that has occurred. You
can click an object in the message to jump to that object in the
diagram window.
Usage Notes
• You are able to open multiple viewers simultaneously in order to review the content of
the logs and interact with the diagram at the same time.
• The Filter Options can be set as defaults in the Design Log Event Filter Options Dialog
Box.
Related Topics
Viewing Design Logs
Related Topics
Viewing Design Logs
Options Help
What do you need help with?
• The Options Dialog Box fields
• Creating an Option Folder at Project Level
• Defining Inclusive and Exclusive Relationships for an Option
• Creating an Option Combination at Project Level
• Adding a Valid Selection to an Option Combination
• Deleting a Valid Selection from an Option Combination
Print Help
What do you need help with?
• The Print Dialog Box fields
• Print to a Printer or Plotter
• Printing a Single Diagram
• Printing All Diagrams in a Project
• Printing All Diagrams in a Design
• Printing Selected Print Regions
For further information on how to use bridges, the bridge adaptors and functionality available,
see the link below.
Available Topics
The following topics area available:
• Bridging Data In and Out of Capital User Guide.
Capital Insight is a product that provides functionality for measuring and assessing your designs
as well as conducting physical architectural trade studies in Capital Integrator (including Capital
Level Manager), Capital Topology, Capital HarnessXC, Capital ModularXC, or Capital
Systems Architect.
If you have a Capital Insight license, you have access to all of its functionality and an Insight
tab is available at the bottom left of the application window. This enables you to create studies
on designs and to create/edit metrics that you use in those studies. If you use Capital Level
Manager or Capital Systems Architect, this functionality is included by default.
If you do not have a license, you have access to default metrics that can be run against designs
to measure and assess them. A Metrics tab is available at the bottom left of the application
window. There are fewer default metrics and you cannot modify them. See Viewing Metric
Results for the Open Design for instructions on how to view them.
Note
If you do not have a Capital Insight license, a Metrics tab is available at the bottom left of
the application window. It has a subset of default metrics that can be run against designs to
measure and assess them. There are fewer default metrics and you cannot modify them. This tab
is visible regardless of whether Capital Insight is enabled.
Prerequisites
• You must have a valid license for Capital Insight.
Procedure
1. In the Capital Launcher, click Configuration (located under Support at the top); the
Edit Capital Configuration dialog box is displayed.
2. Select the Enable Insight option (located at the bottom of the dialog) and click OK.
3. Close and re-start the Capital applications; when you next open the applications, the
Capital Insight functionality will be available.
Note
Alternatively, you can enable Capital Insight by editing the clientprops.xml file in
the config directory of your Capital installation. Find the <packages> section in that
file and ensure that the line for insight reads: <feature check="YES" name="insight"></
feature>
Results
An Insight tab with all of its functionality enabled is available at the bottom left of the
application window. This enables you to create studies on designs and to create/edit metrics that
you use in those studies.
Related Topics
Capital Insight
Architectural Study Concepts
Metrics/Insight Tab
Related Topics
Overview of Studies and Scenarios
Metrics
Snapshots
Studies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
Scenarios . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 585
Creating a Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Editing a Study. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 586
Deleting a Study . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Creating a Scenario (and Study) from the Insight Tab . . . . . . . . . . . . . . . . . . . . . . . . . . 587
Opening a Scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588
Studies
A study exists within a project and is a container in which an entire physical architectural design
evaluation can take place. The different architectural changes being considered and compared
are created and accessed within the context of a study.
For each study, you can decide which Metrics will be available and used to measure your
scenarios.
A study can contain multiple Scenarios. When evaluating or editing a scenario, you can take
Snapshots of the metric results when design changes are made. The metric results of these
snapshots can then be compared with each other or with the current (live) data in a design.
For an example of a study (including its scenarios), see “Usage Example - Study of Alternative
Harness Routing Paths” on page 630.
Scenarios
Within a study, you can create multiple scenarios. The purpose of a scenario is to provide a
context for one of the design options being considered and compared as part of an architectural
exercise (that is, a study). You associate each scenario with a specific design revision. You can
associate a design revision with multiple scenarios. When a design revision is associated with a
scenario, you can still edit it using the standard functionality of the application for which it was
created.
The key metrics used in a scenario can be generated and viewed as its design revision is being
developed. When two or more scenarios are available within a study, you can compare their key
metrics. You might then carry forward the preferred scenario as the basis of the production
design.
Creating a Study
This topic explains how to create a study and its scenarios.
Procedure
1. Right-click on the project in the Project Browser Window and select New Study; the
New Study Dialog Box is displayed.
2. Specify the Name.
3. Add the scenarios that you want to use:
a. Click Add new Scenario to Study ( ); a row is added to the Scenarios table.
b. Specify the Name of the scenario and the Design to be associated with the scenario.
c. Repeat steps a and b for each scenario you want to create.
4. In the Metrics window, select the metric elements that you want to use in the study. For
each metric, click the Change Default Chart Type to display for Metric dropdown list
(located on the right of the metric line) and select the default chart type that you want to
use for the metric when viewing metric results.
5. Select the Groups to make available to the Scenarios in the study, and click OK; the
study is added to the Project Browser Window and the scenarios are listed below it.
Related Topics
Overview of Studies and Scenarios
Editing a Study
Deleting a Study
Creating a Scenario (and Study) from the Insight Tab
Opening a Scenario
Editing a Study
This topic explains how to edit an existing study.
When editing a study, you can:
Procedure
1. Right-click on the study in the Project Browser Window and select Edit Study; the Edit
Study Dialog Box is displayed.
2. Edit the study as required and click OK.
Related Topics
Overview of Studies and Scenarios
Creating a Study
Deleting a Study
Creating a Scenario (and Study) from the Insight Tab
Opening a Scenario
Deleting a Study
This topic explains how to delete a study.
Procedure
1. Right-click on the study in the Project Browser Window
2. Select Delete; all scenarios within the study are deleted along with the associations to
designs. The designs are not deleted
Related Topics
Overview of Studies and Scenarios
Creating a Scenario (and Study) from the Insight Tab
Creating a Study
Editing a Study
Opening a Scenario
2. In the Study field, either select an existing study from the dropdown list or enter a name
for a new study.
3. Specify the Name of the scenario and click Create Scenario.
If you selected an existing study, you have completed creating the scenario.
If you entered the name for a new study, the New Study Dialog Box is displayed with
the new scenario in the Scenarios table (associated with the currently open design).
4. If required, add any additional scenarios that you want to use in the study:
a. Click Add new Scenario to Study ( ); a row is added to the Scenarios table.
b. Specify the Name of the scenario and the Design to be associated with the scenario.
c. Repeat steps a and b for each scenario you want to create.
5. In the Metrics window, select the metric elements that you want to use in the study. For
each metric, click the Change Default Chart Type to display for Metric dropdown list
(located on the right of the metric line) and select the default chart type that you want to
use for the metric when viewing metric results.
6. Select the Groups to make available to the scenarios in the study, and click OK.
Results
• The scenario is added to the Project Browser Window below the appropriate study.
• The currently open design/scenario switches to the newly created scenario.
Related Topics
Overview of Studies and Scenarios
Creating a Study
Editing a Study
Opening a Scenario
Opening a Scenario
This topic explains how to open a scenario and view its metric results.
Procedure
1. Double-click the scenario in the Project Browser Window
or
Right-click on the scenario in the Project Browser Window
2. Select Open Scenario.
Results
• The design associated with the scenario is opened in the diagram window.
• The Insight tab (bottom left of application, see Metrics/Insight Tab) and Metrics Table
(in the Output Window at the bottom of the application) display the metric results for the
design.
For information about the interface elements (including information on changing chart type and
filtering the display of metric results, see “Metrics/Insight Tab” on page 619).
Related Topics
Overview of Studies and Scenarios
Creating a Study
Editing a Study
Deleting a Study
Metrics
A metric is a single value calculated as a measure of ‘goodness’ (for example, cost or weight).
You define metrics at system level and you can apply them in all projects.
Each metric is calculated by adding together values for different types of object. These are
called metric elements and are listed separately when displayed in the interface. Metric
elements can be turned on or off when viewing a study to control whether they are used in
calculations or not.
You can export and import metrics from Capital Project, see “Exporting Metrics” or “Importing
Metrics” in the Capital Project User Guide.
Default Metrics
A metric can be applied to multiple studies (and scenarios) and can be used to judge which
scenario within a study best addresses the needs of that study.
Depending on whether you have a Capital Insight license, the default metrics supplied for the
Metrics or Insight tab are:
• Measure: Cost
Calculates the total architectural cost of design objects. Available only if you have a
Capital Insight license.
• Measure: Count
Calculates the total number of objects of a particular object type.
• Measure: Length
Calculates the total length of wires.
• Measure: Weight
Calculates the total weight of design objects. Available only if you have a Capital
Insight license.
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.
• For the current (live) design data on the Metrics/Insight Tab at the bottom left of the
application.
• For a snapshot either on the Insight tab or in the Snapshot Dialog Box. Available only if
you have a Capital Insight license.
• For comparing snapshots either in the Compare Snapshots Dialog Box or Compare
Snapshot With Dialog Box. Available only if you have a Capital Insight license.
See the Capital Insight Dialog and Field Reference topics, for information on filtering the
metric results and changing the chart type used in these dialogs.
If you have a Capital Insight license, within the Edit Metrics Dialog Box, you can modify the
default metrics or even define new ones based on attributes and properties of design objects. For
even more flexibility, you can develop custom metrics and groups as part of an extensibility
plugin. For more information about developing and using extensibility plugins, see the
PluginDevelopment.pdf file that is located in the doc\plugin directory of your Capital
installation.
Related Topics
Creating a Metric
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
Viewing Metric Results for the Open Design
Creating a Metric
This topic explains how to create a new metric.
Procedure
1. Press Space Bar and enter Metrics; the Edit Metrics Dialog Box is displayed.
2. Click Add New Metric ( ); a new row is created in the Definition window.
3. Edit the name of the metric. Click elsewhere on the dialog to finish; the row is displayed
like the other metrics.
Related Topics
Metrics
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
Note
You can duplicate an existing metric element by right-clicking it and choosing
Duplicate; the duplicate is added below the same metric. Alternatively, you can
right-click an existing metric element and choose Copy or Cut. Right-click another
metric or one of its metric elements and choose Paste to add the copied or cut element
below it.
3. Edit the metric element name and click the color square in that row to select the color
that you want used to display the results for that metric element.
4. Define the element definitions:
a. Click Add New Definition ( ); the template for the new element definition is
added to the window.
b. Edit the element definition as required.
c. Repeat steps a and b for each element definition that you want to add.
Caution
The order in which the element definitions are listed dictates the order in which
they are calculated for design objects. If a design object matches more than one
element definition, only the value calculated for the first matching definition is
included in the metric result. This means that you should put the more specific
definitions at the top of the list and general definitions nearer the bottom.
5. Click OK.
Related Topics
Metrics
Creating a Metric
Deleting a Metric Element
Editing a Metric Element Definition
Deleting a Metric Element Definition
4. Click OK.
Related Topics
Metrics
Creating a Metric
Deleting a Metric Element
Editing a Metric Element Definition
Creating a Metric Element
Specifying the Architectural Cost of a 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 is displayed.
2. Click the General tab; the Architectural Cost attribute is listed. Edit the Value as
required and click OK.
Related Topics
Metrics
Creating a Metric
Creating a Metric Element
Editing a Metric Element Definition
Deleting a Metric Element Definition
Deleting a Metric Element
For example, you could use the Length metric grouped by harness to view the length of wiring
in each harness.
Procedure
1. Click the Metrics tab.
2. Use the Group dropdown list to select the sub-set of design objects for which you want
to display metric results.
3. Click the Cycle Metric to display arrows to scroll through the available metrics.
The metric results chart on the tab updates as you scroll through the metrics.
The Metrics Table also updates in the Output Window.
Note
By default, you can display the results for Measure: Count and Measure: Length
metrics. Further metrics are available if you have a Capital Insight license.
Related Topics
Metrics
Capital Insight
Snapshots
A snapshot stores the metric results at a given design stage for a scenario.
These results can be compared with the current metric results for a scenario or with another
snapshot, from the same or a different study).
3. Specify the Name for the snapshot and the color you want to use to display the metric
results for it when comparing snapshots.
4. Click OK; the snapshot is added below the scenario in the Project Browser Window.
Related Topics
Snapshots
Editing a Snapshot Name and Display Color
Opening a Snapshot
Opening a Snapshot in the Insight Tab
Comparing Snapshots from One Study
Comparing Snapshots from Different Studies
Comparing Snapshots from One or More Studies in the Insight Tab
Opening a Snapshot
This topic explains how to open the Snapshot Dialog Box that displays the metric results both in
a chart and a table.
Procedure
1. Right-click on the snapshot in the Project Browser Window and select Open; the
Snapshot Dialog Box is displayed.
2. Filter the metric results as required. See “Snapshot Dialog Box” on page 628 for
information about the user-interface elements available on the dialog.
Related Topics
Snapshots
Taking a Snapshot of Metric Results for Current Design Data
Editing a Snapshot Name and Display Color
Opening a Snapshot in the Insight Tab
Comparing Snapshots from One Study
Comparing Snapshots from Different Studies
Procedure
1. Open the scenario to which the first snapshot belongs (see “Opening a Scenario” on
page 588).
2. On the Metrics/Insight Tab, click Compare Snap-Shots ( ); the metric results for all
snapshots in the scenario are displayed in a spider chart in the metric results chart.
3. If you want to include a snapshot from another scenario or study in the comparison,
right-click on the metric results chart and select Add to comparison followed by the
snapshot.
4. Filter the metric results as required. See Metrics/Insight Tab for information about the
user-interface elements available on the dialog.
Related Topics
Snapshots
Taking a Snapshot of Metric Results for Current Design Data
Editing a Snapshot Name and Display Color
Opening a Snapshot
Opening a Snapshot in the Insight Tab
Comparing Snapshots from One Study
Comparing Snapshots from Different Studies
Related Topics
Creating a Metric Element
Editing a Metric Element Definition
Deleting a Metric Element Definition
Related Topics
Comparing Snapshots from Different Studies
Usage Notes
The default groups for Capital Integrator, Capital Topology, and Capital Systems Architect are:
• Harness
• Multicore Type
• None
• Option
• Option Expression
• Vehicle Model
• Wire Material
• Wire Specification
Capital Systems Architect also has the following groups (which are listed for all applications):
• Carrier
• Carrier Type
• Component
• System Component Type
• ECU
The default groups for Capital HarnessXC and Capital ModularXC are:
• Assembly
• Component Type
• Library Group
• Multicore Type
• None
• Option
• Option Expression
• Terminal Material
• Wire Material
• Wire Specification
Related Topics
Creating a Metric Element
Objects
Usage Notes
• You can edit metrics only if you have the Edit Metrics permission set for your user
account.
• The metric elements are displayed in rows below each metric. The color square on a
metric element row indicates the color used to display results for that metric. To change
the color, click the square.
• When you 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.
To delete a metric element, select it and click the minus symbol (-) on the metric row.
• You can duplicate an existing metric element by right-clicking it and choosing
Duplicate; the duplicate is added below the same metric. Alternatively, you can right-
click an existing metric element and choose Copy or Cut. Right-click another metric or
one of its metric elements and choose Paste to add the copied or cut element below it.
• The order in which the element definitions are listed dictates the order in which they are
calculated for design objects. If a design object matches more than one element
definition, only the value calculated for the first matching definition is included in the
metric result. This means that you should put the more specific definitions at the top of
the list and general definitions nearer the bottom.
• You can move an element up or down in the list by selecting it and clicking Move
Selected Definition Up in the list ( ) or Move Selected Definition Down in the list
( ).
The displayed dialog depends on which dialog was used to create the condition
currently displayed in the metric template.
o Click Expression to display the Calculation dialog box where you can create a
calculation using a query expression.
Usage Notes
• If you enter a Value that is not supported by the selected Type, the Value is displayed in
red text and the OK button is disabled.
• 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 Study
Editing a Study
Usage Notes
• If you enter a Value that is not supported by the selected Type, the Value is displayed in
red text and the OK button is disabled.
• 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 Study
Editing a Study
Metrics/Insight Tab
To access: This tab is displayed with the tabs at the bottom left of the application when a design
or scenario is opened (except when working in multi-user mode).
Used to view metric results for the currently open design or scenario. If you have a Capital
Insight license, you can also create a new scenario (and new study if required) from here.
Note
If you have a Capital Insight license, this tab is called Insight. If you do not have a license,
this tab is called Metrics. See “Capital Insight” on page 581 for an introduction to the
functionality available from this tab.
Description
Metrics are calculated to return a single numerical value for each group selected in a design.
This tab can be dragged from its location to display it as a separate floating dialog. Close the
dialog to return it to the original tab location.
Objects
Cycle Metric to Click the green arrows at the top of the reports to scroll between the
display results for different metrics. When you click an arrow, the metric results
chart changes accordingly.
Alternatively, click the icon (located between the arrows) to select a
metric from a list. If you have a Capital Insight license and want to
create a new metric, click Edit Metrics in the list to open the Edit
Metrics Dialog Box.
The name of the metric for which results are currently displayed is
shown between the arrows.
Metric Results Displays the metric results for the current (live) design data or a
Chart snapshot selected from the <Live> dropdown list.
You can use the Group field to specify the sub-sets of design objects for
which you want to display metric results.
Below the metrics report is a legend listing the metric elements
currently displayed in the chart. It also lists the display colors for those
metric elements. To hide a metric element in the chart, click it in the
legend; it is then grayed out. To display it again, click the grayed-out
entry in the legend. Alternatively, you can right-click on the chart and
select Show Metrics or Hide Metrics followed by a metric element
name.
To change the chart type (for example, Pie Chart or Horizontal Bar
Chart), right-click on the chart and select Chart Type followed by the
type that you want to display.
You can select and copy the chart by right-clicking on it and selecting
Copy Chart. The report can be pasted into other applications, such as
Microsoft Word.
Usage Notes
• The default groups for Capital Integrator, Capital Topology, and Capital Systems
Architect are:
o Harness
o Multicore Type
o None
o Option
o Option Expression
o Vehicle Model
o Wire Material
o Wire Specification
• Capital Systems Architect also has the following groups (which are listed for all
applications):
o Carrier
o Carrier Type
o Component
o System Component Type
o ECU
The default groups for Capital HarnessXC and Capital ModularXC are:
o Assembly
o Component Type
o Library Group
o Multicore Type
o None
o Option
o Option Expression
o Terminal Material
o Wire Material
o Wire Specification
Related Topics
Opening a Scenario
Taking a Snapshot of Metric Results for Current Design Data
Opening a Snapshot in the Insight Tab
Comparing Snapshots from One or More Studies in the Insight Tab
Creating a Scenario (and Study) from the Insight Tab
Viewing Metric Results for the Open Design
Metrics Table
To access: This table is displayed in the Output Window at the bottom of the application when a
scenario or design is opened.
Used to display metric results for the currently open design or scenario in a table format.
Objects
This is the same data as displayed in the Metrics/Insight Tab.
Usage Notes
If this table has been hidden or closed, it can be re-opened by clicking the Show Metrics
Table button on the Metrics/Insight tab.
You can select and copy any range of cells. Those cells can be pasted into other applications,
such as Microsoft Excel or Microsoft Word. When you copy cells, the column header is also
copied.
The Total column displays the total values for the other columns. It is available only for
individual snapshots and is not displayed when comparing snapshots.
Related Topics
Metrics/Insight Tab
Opening a Scenario
Viewing Metric Results for the Open Design
Related Topics
Metrics/Insight Tab
Overview of Studies and Scenarios
Creating a Scenario (and Study) from the Insight Tab
Usage Notes
• The default groups for Capital Integrator and Capital Topology are:
o Harness
o Multicore Type
o None
o Option
o Option Expression
o Vehicle Model
o Wire Material
o Wire Specification
The default groups for Capital HarnessXC and Capital ModularXC are:
o Assembly
o Component Type
o Library Group
o Multicore Type
o None
o Option
o Option Expression
o Terminal Material
o Wire Material
o Wire Specification
• You can develop custom groups as part of an extensibility plugin. For more information
about developing and using extensibility plugins, see the PluginDevelopment.pdf file
that is located in the doc\plugin directory of your Capital installation.
Related Topics
Creating a Study
Usage Notes
• The default groups are:
o Harness
o Multicore Type
o None
o Option
o Option Expression
o Vehicle Model
o Wire Material
o Wire Specification
Related Topics
Opening a Snapshot
Related Topics
Taking a Snapshot of Metric Results for Current Design Data
4. Click Add a new Scenario to Study ( ); a row is added to the Scenarios table.
5. Specify Driver Side Scenario as the Name of the scenario and select the Driver Side
Only design as the Design.
6. Repeat steps 3 and 4 for the second scenario, specifying Driver and Passenger
Scenario as the Name and selecting the Driver and Passenger Side design as the
Design.
7. In the Metrics window, select Wire cost and Wire weight (both default metrics
supplied with the system) as the metric elements that you want to use in the study. For
each metric, click the Change Default Chart Type to display for Metric dropdown list
(located on the right of the metric line) and select the default chart type that you want to
use for the metric when viewing metric results.
8. Select the groups to which you want to apply the study. In this example case, you might
want to select only Harness (to view the wire cost and weight for each harness in the
designs) and None (to view the total wire cost and weight for each design).
Click OK; the study is added to the Project Browser Window, expanding the study
reveals the scenarios listed below it.
9. The following steps will take a snapshot of the metric totals:
10. Double click on the Driver Side Scenario in the Project Browser Window and click on
the Metrics/Insight Tab (located on the lower left of the application) where you can view
the metric totals for that scenario.
11. On the Metrics/Insight Tab, click Take a Snapshot of the current data ( ); the Take
Snapshot Dialog Box is displayed.
12. Specify Driver Only Snapshot as the Name for the snapshot. Click the colored box and
select the color you want to use to display the metric results when comparing snapshots.
13. Click OK; the snapshot is added below the scenario in the Project Browser Window.
14. Repeat steps 1 to 4 for the Driver and Passenger Scenario scenario, specifying Driver
and Passenger Snapshot as the Name for the snapshot and a different color for
displaying its metric results.
Calculation Help
What do you need help with?
• Understanding Capital Insight concepts
• The Calculation Dialog Box fields
• Creating a Metric Element
• Editing a Metric Element Definition
• Deleting a Metric Element Definition
Snapshot Help
What do you need help with?
• Understanding Capital Insight concepts
• The Snapshot Dialog Box fields
• Opening a Snapshot
Copyright (c) 1999 The Apache Software Foundation. All rights reserved
This product includes software developed by the Apache Software Foundation (http://www.apache.org/)
This software application may include Hibernate third-party software, portions of which may be subject to the GNU Lesser
General Public License Version 2.1, February 1999. Copyright (C) 1991, 1999 Free Software Foundation, Inc., 59 Temple
Place, Suite 330, Boston, MA 02111-1307 USA. You can view the complete license at: www.gnu.org/licenses/lgpl.htmll, or
find the file at <Capital_install_location>/docs/legal/gnu_lgpl_2.1.pdf. To obtain a copy of the Hibernate source code, or to
obtain a copy of any changes made to the Hibernate source code, send a request [email protected]. This
offer shall only be available for three years from the date Mentor Graphics Corporation first distributed the Hibernate source
code.
This software application may include Hibernate third-party software, portions of which may be subject to the Apache
License, version 2.0, January 2004. You can view the complete license at: www.apache.org/licenses/LICENSE-2.00, or find
the file at <Capital_install_location>/docs/legal/apache_2.0.pdf
This software application may include Hibernate third-party software, portions of which may be subject to the Apache
License, version 1.1, Copyright (c) 2002-2003, The Apache Software Foundation. All rights reserved. You can view the
complete license at:www.apache.org/licenses/LICENSE-1.11, or find the file at <Capital_install_location>/docs/legal/
apache_1.1.pdf
This software application may include Hibernate third-party software, portions of which may contain ANTLR, 1989-2003
Developed by jGuru.com, www.ANTLR.orgg and www.jGuru.comm
This software application may include Hibernate third-party software, portions of which may be subject to the Sun
Microsystems, Inc. Binary Code License Agreement. You can view the complete license at <Capital_install_location>/docs/
legal/sun_binary.pdf
Redistribution and use of this software and associated documentation ("Software"), with or without modification, are
permitted provided that the following conditions are met:
1. Redistributions of source code must retain copyright statements and notices. Redistributions must also contain a copy of
this document.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. The name "DOM4J" must not be used to endorse or promote products derived from this Software without prior written
permission of MetaStuff, Ltd. For written permission, please contact [email protected].
4. Products derived from this Software may not be called "DOM4J" nor may "DOM4J" appear in their names without prior
written permission of MetaStuff, Ltd. DOM4J is a registered trademark of MetaStuff, Ltd.
THIS SOFTWARE IS PROVIDED BY METASTUFF, LTD. AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESSED
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
METASTUFF, LTD. OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-----------------------------------
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holders nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-------------------------------------
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holders nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-------------------------------------
This software application may include Java 1.6 JRE third-party software. Java 1.6 JRE is distributed under the terms of the
Sun Microsystems, Inc. Binary Code License Agreement for the JAVA SE RUNTIME ENVIRONMENT (JRE) VERSION 6
and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license
for the specific language governing rights and limitations under the license. You can view a copy of the license at:
<Capital_install_location>/docs/legal/sun_binary_JRE_6.pdf. Additional copyright notices and license terms applicable to
portions of Java 1.6 JRE can be found at: <install_location>/jre/THIRDPARTYLICENSEREADME.txt. Java 1.6 JRE may be
subject to the following copyrights:
© 1999 by CoolServlets.com.
Any errors or suggested improvements to this class can be reported as instructed on CoolServlets.com. We hope you enjoy this
program... your comments will encourage further development!
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
Neither name of CoolServlets.com nor the names of its contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY COOLSERVLETS.COM AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING INANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE."
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments
normally appear.
4. The names "Graz University of Technology" and "IAIK of Graz University of Technology" must not be used to endorse or
promote products derived from this software without prior written permission.
5. Products derived from this software may not be called "IAIK PKCS Wrapper", nor may "IAIK" appear in their name,
without prior written permission of Graz University of Technology.
THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:
"This product includes software developed by the Apache Software Foundation (http://www.apache.org/)."
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments
normally appear.
4. The names "Apache" and "Apache Software Foundation" and "Apache Turbine" must not be used to endorse or promote
products derived from this software without prior written permission. For written permission, please contact
[email protected].
5. Products derived from this software may not be called "Apache", "Apache Turbine", nor may "Apache" appear in their
name, without prior written permission of the Apache Software Foundation.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies and that both the copyright notice and this permission
notice and warranty disclaimer appear in supporting documentation, and that the names of the authors or their employers not
be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.
The authors and their employers disclaim all warranties with regard to this software, including all implied warranties of
merchantability and fitness. In no event shall the authors or their employers be liable for any special, indirect or consequential
damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or
other tortious action, arising out of or in connection with the use or performance of this software.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby
granted, provided that the above copyright notice appear in all copies and that both the copyright notice and this permission
notice and warranty disclaimer appear in supporting documentation, and that the name of the authors or their employers not be
used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.
The authors and their employers disclaim all warranties with regard to this software, including all implied warranties of
merchantability and fitness. In no event shall the authors or their employers be liable for any special, indirect or consequential
damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or
other tortious action, arising out of or in connection with the use or performance of this software.
Java is a trademark of Sun Microsystems, Inc. References to the Java programming language in relation to JLex are not meant
to imply that Sun endorses this product.
1.Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.
2.Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE CRYPTIX FOUNDATION LIMITED AND CONTRIBUTORS ``AS IS'' AND
ANY EXPRESS ORIMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FORA PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT
SHALL THE CRYPTIX FOUNDATION LIMITED OR CONTRIBUTORS BELIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOTLIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OFTHE POSSIBILITY OF SUCH DAMAGE.
© 1994-2002 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en
Informatique et en Automatique, Keio University). All Rights Reserved.
http://www.w3.org/Consortium/Legal/
Public documents on the W3C site are provided by the copyright holders under the following license. The software or
Document Type Definitions (DTDs) associated with W3C specifications are governed by the Software Notice. By using and/
or copying this document, or the W3C document from which this statement is linked, you (the licensee) agree that you have
read, understood, and will comply with the following terms and conditions:
Permission to use, copy, and distribute the contents of this document, or theW3C document from which this statement is
linked, in any medium for any purpose and without fee or royalty is hereby granted, provided that you include the following on
ALL copies of the document, or portions thereof, that you use:
2. The pre-existing copyright notice of the original author, or if it doesn't exist, a notice of the form: "Copyright © [$date-of-
document] World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en
Informatique et en Automatique, Keio University). All Rights Reserved. http://www.w3.org/Consortium/Legal/" (Hypertext is
preferred, but a textual representation is permitted.)
When space permits, inclusion of the full text of this NOTICE should be provided. We request that authorship attribution be
provided in any software, documents, or other items or products that you create pursuant to the implementation of the contents
of this document, or any portion thereof.
No right to create modifications or derivatives of W3C documents is granted pursuant to this license. However, if additional
requirements (documented in the Copyright FAQ) are satisfied, the right to create modifications or derivatives is sometimes
granted by the W3C to individuals complying with those requirements.
THIS DOCUMENT IS PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO REPRESENTATIONSOR
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES
OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, OR TITLE;THAT THE
CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; NOR THAT THEIMPLEMENTATION OF
SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS,COPYRIGHTS, TRADEMARKS OR
OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL ORCONSEQUENTIAL
DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCEOR IMPLEMENTATION
OF THE CONTENTS THEREOF.
The name and trademarks of copyright holders may NOT be used in advertising or publicity pertaining to this document or its
contents without specific, written prior permission. Title to copyright in this document will at all times remain with copyright
holders.
The following software may be included in this product: Retroweaver; Use of any of this software is governed by the terms of
the license below:
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution. Neither the name of Toby Reyelts nor the names of
his contributors may be used to endorse or promote products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICTLIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holders nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments
normally appear.
4. The names "CyberNeko" and "NekoHTML" must not be used to endorse or promote products derived from this software
without prior written permission. For written permission, please contact [email protected].
5. Products derived from this software may not be called "CyberNeko", nor may "CyberNeko" appear in their name, without
prior written permission of the author.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR OTHER CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
* Neither the name of the Thai Open Source Software Center Ltd nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" ANDANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL
THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANYDIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES;LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ONANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment:
"This product includes software developed by Daisuke Okajima and Kohsuke Kawaguchi (http://relaxngcc.sf.net/)."
Alternately, this acknowledgment may appear in the software itself, if and wherever such third-party acknowledgments
normally appear.
4. The names of the copyright holders must not be used to endorse or promote products derived from this software without
prior written permission. For written permission, please contact the copyright holders.
5. Products derived from this software may not be called "RELAXNGCC", nor may "RELAXNGCC" appear in their name,
without prior written permission of the copyright holders.
THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED.IN NO EVENT SHALL THE APACHE SOFTWARE FOUNDATION OR ITS
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify,
merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution, and in the same place and form as other
copyright, license and disclaimer information.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This
product includes software developed by The XFree86 Project, Inc (http://www.xfree86.org/) and its contributors", in the same
place and form as other third-party acknowledgments.
Alternately, this acknowledgment may appear in the software itself, in the same form and location as other such third-party
acknowledgments.
4. Except as contained in this notice, the name of The XFree86 Project, Inc shall not be used in advertising or otherwise to
promote the sale, use or other dealings in this Software without prior written authorization from TheXFree86 Project, Inc.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY ANDFITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE XFREE86PROJECT, INC OR ITS CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; ORBUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISINGIN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITYOF
SUCH DAMAGE.
For the purposes of this copyright and license, "Info-ZIP" is defined as the following set of individuals:
Mark Adler, John Bush, Karl Davis, Harald Denker, Jean-Michel Dubois, Jean-loup Gailly, Hunter Goatley, Ian Gorman,
Chris Herborth, Dirk Haase, Greg Hartwig, Robert Heath, Jonathan Hudson, Paul Kienitz, David Kirschbaum, Johnny Lee,
Onno van der Linden, Igor Mandrichenko, Steve P. Miller, Sergio Monesi, Keith Owens, George Petrov, Greg Roelofs, Kai
Uwe Rommel, Steve Salisbury, Dave Smith, Christian Spieler, Antoine Verheijen, Paul von Behren, Rich Wales, Mike White
This software is provided "as is," without warranty of any kind, express or implied. In no event shall Info-ZIP or its
contributors be held liable for any direct, indirect, incidental, special or consequential damages arising out of the use of or
inability to use this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and
redistribute it freely, subject to the following restrictions:
1. Redistributions of source code must retain the above copyright notice, definition, disclaimer, and this list of conditions.
2. Redistributions in binary form (compiled executables) must reproduce the above copyright notice, definition, disclaimer,
and this list of conditions in documentation and/or other materials provided with the distribution. The sole exception to this
condition is redistribution of a standard UnZipSFX binary (including SFXWiz) as part of a self-extracting archive; that is
permitted without inclusion of this license, as long as the normal SFX banner has not been removed from the binary or
disabled.
3. Altered versions--including, but not limited to, ports to new operating systems, existing ports with new graphical interfaces,
and dynamic, shared, or static library versions--must be plainly marked as such and must not be misrepresented as being
the original source. Such altered versions also must not be misrepresented as being Info-ZIP releases--including, but not
limited to, labeling of the altered versions with the names "Info-ZIP" (or any variation thereof, including, but not limited to,
different capitalizations), "Pocket UnZip," "WiZ" or "MacZip" without the explicit permission of Info-ZIP. Such altered
versions are further prohibited from misrepresentative use of the Zip-Bugs or Info-ZIP e-mail addresses or of the Info-ZIP
URL(s).
4. Info-ZIP retains the right to use the names "Info-ZIP," "Zip," "UnZip," "UnZipSFX," "WiZ," "Pocket UnZip," "Pocket Zip,"
and "MacZip" for its own source and binary releases.
-------------------------------------
This software application may include Xerces-J 2.8.1 third-party software. Xerces-J 2.8.1 is distributed under the terms of the
Apache v2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See
the license for the specific language governing rights and limitations under the license. You can view a copy of the license at:
<Capital_install_location>/docs/legal/apache_2.0.pdf. Portions of this software may be subject to W3C License. You can
view a copy of the W3C License at: <Capital_install_location>/docs/legal/w3c_2002.pdf. Xerces-J 2.8.1 may be subject to
the following copyrights:
© 2001 World Wide Web Consortium, (Massachusetts Institute of Technology, Institut National de Recherche en
Informatique et en Automatique, Keio University). All Rights Reserved. This program is distributed under the W3C's
Software Intellectual Property License. This program is distributed in the hope that it will be useful, but WITHOUT ANY
WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.
-------------------------------------
This software application may include JFreeChart version 1.0.10 third-party software. JFreeChart version 1.0.10 is distributed
under the terms of the GNU Lesser General Public License v3.0 and is distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing rights and
limitations under the license. You can view a copy of the GNU Lesser General Public License v3.0 at:
<Capital_install_location>/docs/legal/gnu_lgpl_3.0.pdf. To obtain a copy of the JFreeChart version 1.0.10 source code, send
a request to [email protected]. This offer shall only be available for three years from the date Mentor
Graphics Corporation first distributed JFreeChart version 1.0.10 and valid for as long as Mentor Graphics offers customer
support for Capital Insight Version 2008.2.
-----------------------------------
This software application may include JCommon version 1.0.13 third-party software. JCommon version 1.0.13 is distributed
under the terms of the GNU Lesser General Public License v2.1 and is distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. You can view a copy of the GNU Lesser General Public License
v2.1 at: <Capital_install_location>/docs/legal/gnu_lgpl_2.1.pdf. To obtain a copy of the JCommon version 1.0.13 source
code, send a request to [email protected]. This offer shall only be available for three years from the date
Mentor Graphics Corporation first distributed JCommon version 1.0.13.
----------------------------------
This software application may include Commons-net version 1.4.1 third-party software. Commons-net v1.4.1 is distributed
under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
KIND, either express or implied. See the license for the specific language governing rights and limitations under the license.
You can view a copy of the license at: <Capital_install_location>/docs/legal/apache_2.0.pdf.
----------------------------------
This software application may include Apache Commons Virtual File System version 1.0 third-party software. Apache
Commons Virtual File System v1.0 is distributed under the terms of the Apache License version 2.0 and is distributed on an
"AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the specific language
governing rights and limitations under the license. You can view a copy of the license at: <Capital_install_location>/docs/
legal/apache_2.0.pdf.
----------------------------------
This software application may include Java Secure Channel (JSch) version 0.1.41 third-party software, which is distributed on
an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. JSch v0.1.41 may be subject to the
following copyrights:
© 2002, 2003, 2004, 2005, 2006, 2007, 2008 Atsuhiko Yamanaka, JCraft, Inc.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. The names of the authors may not be used to endorse or promote products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL JCRAFT, INC. OR ANY CONTRIBUTORS TO
THIS SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. The names of the authors may not be used to endorse or promote products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL JCRAFT, INC. OR ANY CONTRIBUTORS TO
THIS SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------
This software application may include TinyXML version 2.6.1 third-party software. TinyXML version 2.6.1 is distributed
under the terms of the zLib and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express
or implied. See the license for the specific language governing rights and limitations under the license. You can view a copy
of the license at: <Capital_install_location>/docs/legal/zlib_libpng.pdf. TinyXML version 2.6.1 may be subject to the
following copyrights:
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any
damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and
redistribute it freely, subject to the following restrictions:
The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this
software in a product, an acknowledgment in the product documentation would be appreciated but is not required.
Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.
This notice may not be removed or altered from any source distribution.
----------------------------------
This software application may include iText version 2.1.5 third-party software. iText v2.1.5 is distributed under the terms of
the GNU Library General Public License v2 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
KIND, either express or implied. See the license for the specific language governingrights and limitations under the license.
You can view a copy of the GNU Library General Public License v2 at: <Capital_install_location>/docs/legal/
gnu_library_gpl_2.0.pdf. Portions of this software may be subject to the GNU Lesser General Public License v2.1. You can
view a copy of the GNU Lesser General Public License v2.1 at: <Capital_install_location>/docs/legal/gnu_lgpl_2.1.pdf.
Portions of this software may be subject to the Apache License v2.0. You can view a copy of the Apache License at:
<Capital_install_location>/docs/legal/apache_2.0.pdf. To obtain a copy of the iText v2.1.5 source code, send a request to
[email protected]. This offer shall only be available for three years from the date Mentor Graphics
Corporation first distributed iText v2.1.5. iText v2.1.5 may be subject to the following copyrights:
THE DATA FILES AND SOFTWARE ARE PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS
OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE
COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY
SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM
LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THE DATA
FILES OR SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the
sale, use or other dealings in these Data Files or Software without prior written authorization of the copyright holder.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
Redistribution of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistribution in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the distribution.
Neither the name of Sun Microsystems, Inc. or the names of contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
This software is provided "AS IS," without a warranty of any kind. ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED. SUN
MIDROSYSTEMS, INC. ("SUN") AND ITS LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED
BY LICENSEE AS A RESULT OF USING, MODIFYING OR DISTRIBUTING THIS SOFTWARE OR ITS
DERIVATIVES. IN NO EVENT WILL SUN OR ITS LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR
DATA, OR FOR DIRECT, INDIRECT, SPECIAL, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES,
HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR
INABILITY TO USE THIS SOFTWARE, EVEN IF SUN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.
You acknowledge that this software is not designed or intended for use in the design, construction, operation or maintenance
of any nuclear facility.
Permission to use, copy, modify, distribute, and sell this software and its documentation for any purpose is hereby granted
without fee, provided that (i) the above copyright notices and this permission notice appear in all copies of the software and
related documentation, and (ii) the names of Sam Leffler and Silicon Graphics may not be used in any advertising or publicity
relating to the software without the specific, prior written permission of Sam Leffler and Silicon Graphics.
THE SOFTWARE IS PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EXPRESS, IMPLIED OR
OTHERWISE, INCLUDING WITHOUT LIMITATION, ANY WARRANTY OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
© 2005-2006 www.fontbox.org
All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of fontbox; nor the names of its contributors may be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This means you may use it for any purpose, and make any changes you like. All I ask is that you include a link back to this
page in your credits.
Are you using this icon set? Send me an email (including a link or picture if available) to [email protected]
----------------------------------
This software application may include trove4j version 2.1.0 third-party software. trove4j version 2.1.0 is distributed under the
terms of the GNU Lesser General Public License version 2.1 and is distributed on an "AS IS" basis, WITHOUT WARRANTY
OF ANY KIND, either express or implied. See the license for the specific language governing rights and limitations under the
license. You can view a copy of the license at: <Capital_install_location>/docs/legal/gnu_lgpl_2.1. To obtain a copy of the
Trove version 1.1b3 source code, send a request to [email protected]. This offer shall only be available for
three years from the date Mentor Graphics Corporation first distributed trove4j version 2.1.0. trove4j version 2.1.0 may be
subject to the following copyrights:
Permission to use, copy, modify, distribute and sell this software and its documentation for any purpose is hereby granted
without fee, provided that the above copyright notice appear in all copies and that both that copyright notice and this
permission notice appear in supporting documentation. CERN makes no representations about the suitability of this software
for any purpose. It is provided "as is" without expressed or implied warranty.
----------------------------------
This software application may include SLF4J version 1.5.8 third-party software. SLF4J version 1.5.8 is distributed under the
terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND,
either express or implied. See the license for the specific language governing rights and limitations under the license. You can
view a copy of the license at: <Capital_install_location>/docs/legal/apache_2.0.pdf. SLF4J version 1.5.8 may be subject to
the following copyrights:
© 2004-2005 SLF4J.ORG
© 2004-2005 QOS.CH
All rights reserved.
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify,
merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do
so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both
the above copyright notice(s) and this permission notice appear in supporting documentation.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE
COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY
SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM
LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the
sale, use or other dealings in this Software without prior written authorization of the copyright holder.
© 2004-2007 QOS.CH
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify,
merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do
so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both
the above copyright notice(s) and this permission notice appear in supporting documentation.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR
PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT
HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT
OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA
OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION,
ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the
sale, use or other dealings in this Software without prior written authorization of the copyright holder.
----------------------------------
This software application may include CGLIB version 2.2 third-party software. CGLIB version 2.2 is distributed under the
terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND,
either express or implied. See the license for the specific language governing rights and limitations under the license. You can
view a copy of the license at: <Capital_install_location>/docs/legal/apache_2.0.pdf. CGLIB version 2.2 may be subject to the
following copyrights:
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holders nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------
This software application may include Hibernate version 3.3.2 third-party software. Hibernate version 3.3.2 is distributed
under the terms of the GNU Lesser General Public License v2.1 and is distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing rights and
limitations under the license. You can view a copy of the license at: <Capital_install_location>/docs/legal/gnu_lgpl_2.1.pdf.
To obtain a copy of the Hibernate version 3.3.2 source code, send a request to [email protected]. This offer
shall only be available for three years from the date Mentor Graphics Corporation first distributed Hibernate version 3.3.2.
----------------------------------
This software application may include Apache Commons Collections version 3.1 third-party software. Apache Commons
Collections version 3.1 is distributed under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing
rights and limitations under the license. You can view a copy of the license at: <Capital_install_location>/docs/legal/
apache_2.0.pdf.
----------------------------------
This software application may include Java Assist version 3.9.0 third-party software. Java Assist version 3.9.0 is dual licensed
under the terms of either the Mozilla Public License or the GNU Lesser General Public License version 2.1. We elect the
GNU Lesser General Public License version 2.1. GNU Lesser General Public License version 2.1 is distributed on an "AS
IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the specific language
governing rights and limitations under the license. You can view a copy of the license at: <Capital_install_location>/docs/
legal/gnu_lgpl_2.1.pdf. To obtain a copy of the Java Assist version 3.9.0 source code, send a request to
[email protected]. This offer shall only be available for three years from the date Mentor Graphics
Corporation first distributed Java Assist version 3.9.0.
----------------------------------
This software application may include Apache log4j version 1.2.12 third-party software. Apache log4j version 1.2.12 is
distributed under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing rights and
limitations under the license. You can view a copy of the license at: <Capital_install_location>/docs/legal/apache_2.0.pdf.
Portions of this software may be subject to Apache License version 1.1. You can view a copy of the Apache License version
1.1License at: <Capital_install_location>/docs/legal/apache_1.1.pdf.
----------------------------------
This software application may include PostGreSQL jdbc version 8.4-701 third-party software, which is distributed on an "AS
IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. PostGreSQL jdbc version 8.4-701 may be
subject to the following copyrights:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the PostgreSQL Global Development Group nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------
This software application may include PostGreSQL version 8.4.2 third-party software. PostGreSQL version 8.4.2 is
distributed under the terms of the GNU General Public License version 2.0 and is distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing rights and
limitations under the license. You can view a copy of the license at: <Capital_install_location>/docs/legal/gnu_gpl_2.0.pdf.
To obtain a copy of the PostGreSQL version 8.4.2 source code, send a request to [email protected]. This
offer shall only be available for three years from the date Mentor Graphics Corporation first distributed PostGreSQL version
8.4.2. PostGreSQL version 8.4.2 may be subject to the following copyrights:
© 1983, 1987, 1988, 1989, 1990, 1992, 1993 The Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
I M P L I E D W A R R A N T I E S , I N C L U D IN G , B U T N O T L I M I T E D T O , T HE I M P L I E D W A R R A N T I E S O F
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
© 1988, 1993 The Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
I M P L I E D W A R R A N T I E S , I N C L U D IN G , B U T N O T L I M I T E D T O , T HE I M P L I E D W A R R A N T I E S O F
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
I M P L I E D W A R R A N T I E S , I N C L U D IN G , B U T N O T L I M I T E D T O , T HE I M P L I E D W A R R A N T I E S O F
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the author nor the names of other contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
I M P L I E D W A R R A N T I E S , I N C L U D IN G , B U T N O T L I M I T E D T O , T HE I M P L I E D W A R R A N T I E S O F
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
I M P L I E D W A R R A N T I E S , I N C L U D IN G , B U T N O T L I M I T E D T O , T HE I M P L I E D W A R R A N T I E S O F
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holder nor the names of contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTOR(S) ``AS IS'' AND ANY EXPRESS OR
I M P L I E D W A R R A N T I E S , I N C L U D IN G , B U T N O T L I M I T E D T O , T HE I M P L I E D W A R R A N T I E S O F
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE AUTHOR OR CONTRIBUTOR(S) BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
I M P L I E D W A R R A N T I E S , I N C L U D IN G , B U T N O T L I M I T E D T O , T HE I M P L I E D W A R R A N T I E S O F
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------
This software application may include Java 1.6 JRE version1.6 update 19 third-party software. Java 1.6 JRE version1.6 update
19 is distributed under the terms of the Sun Microsystems, Inc. Binary Code License Agreement for the JAVA SE RUNTIME
ENVIRONMENT (JRE) VERSION 6 and JAVAFX RUNTIME VERSION 1and is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing
rights and limitations under the license. You can view a copy of the license at: <Capital_install_location>/docs/legal/
sun_binary_JRE_6.pdf. Additional copyright notices and license terms applicable to portions Java 1.6 JRE version1.6 update
19 can be found here: <Capital_install_location>/docs/legal/jre/THIRDPARTYLICENSEREADME.txt
----------------------------------
This software application may include jexcel version 2.5.3 third-party software. jexcel version 2.5.3 is distributed under the
terms of the GNU Lesser General Public License v2.1 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF
ANY KIND, either express or implied. See the license for the specific language governing rights and limitations under the
license. You can view a copy of the license at: <Capital_install_location>/docs/legal/gnu_lgpl_2.1.pdf. To obtain a copy of the
jexcel version 2.5.3 source code, send a request to [email protected]. This offer shall only be available for
three years from the date Mentor Graphics Corporation first distributed jexcel version 2.5.3.
----------------------------------
This software application may include HSQLDB version 2.0 third-party software. Portions of HSQLDB version 2.0 may be
distributed under the terms of the GNU Lesser General Public License v2.1 and is distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing rights and
limitations under the license. You can view a copy of the license at: <Capital_install_location>/docs/legal/legal/
gnu_lgpl_2.1.pdf. To obtain a copy of the HSQLDB version 2.0 source code, send a request to
[email protected]. This offer shall only be available for three years from the date Mentor Graphics
Corporation first distributed HSQLDB version 2.0. Portions of this software may be subject to W3C License. You can view a
copy of the W3C License at: <Capital_install_location>/docs/legal/legal/w3c_2002.pdf. HSQLDB version 2.0 may be subject
to the following copyrights:
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
Neither the name of the HSQL Development Group nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
HSQL DEVELOPMENT GROUP, HSQLDB.ORG, OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
Neither the name of the Hypersonic SQL Group nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE HYPERSONIC SQL GROUP, OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the Hypersonic SQL Group.
----------------------------------
This software application may include ant version 1.8.2 third-party software. ant version 1.8.2 is distributed under the terms of
the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either
express or implied. See the license for the specific language governing rights and limitations under the license. You can view
a copy of the license at: <Capital_install_location>/docs/legal/apache_2.0.pdf. Portions of this software may be subject to
Apache License version 1.1. You can view a copy of the Apache License version 1.1 at: <Capital_install_location>/docs/
legal/apache_1.1.pdf.
---------------------------------
This software application may include Apache commons-lang version 2.6 third-party software. Apache commons-lang version
2.6 is distributed under the terms of the Apache version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY
OF ANY KIND, either express or implied. See the license for the specific language governing rights and limitations under the
license. You can view a copy of the license at: <Capital_install_location>/docs/legal/apache_2.0.pdf. Portions of this
software may be subject to the GNU Lesser General Public License version 2.1. You can view a copy of the GNU Lesser
General Public License version 2.1 at: <Capital_install_location>/docs/legal/gnu_lgpl_2.1.pdf. To obtain a copy of the
Apache commons-lang version 2.6 source code, send a request to [email protected]. This offer shall only be
available for three years from the date Mentor Graphics Corporation first distributed Apache commons-lang version 2.6.
---------------------------------
This software application may include Apache Commons Configuration version 1.6 third-party software. Apache Commons
Configuration version 1.6 is distributed under the terms of the Apache License version 2.0 and is distributed on an "AS IS"
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the specific language
governing rights and limitations under the license. You can view a copy of the license at: <Capital_install_location>/docs/
legal/apache_2.0.pdf.
---------------------------------
This software application may include quartz version 2.0.1 third-party software. quartz version 2.0.1 is distributed under the
terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND,
either express or implied. See the license for the specific language governing rights and limitations under the license. You can
view a copy of the license at: <Capital_install_location>/docs/legal/apache_2.0.pdf.
---------------------------------
This software application may include opencsv version 2.2 third-party software. opencsv version 2.2 is distributed under the
terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND,
either express or implied. See the license for the specific language governing rights and limitations under the license. You can
view a copy of the license at: <Capital_install_location>/docs/legal/apache_2.0.pdf. Opencsv version 2.2 may be subject to
the following copyrights:
© 2000-2006, www.hamcrest.org
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
Neither the name of Hamcrest nor the names of its contributors may be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
---------------------------------
This software application may include Apache Batik version 1.7 third-party software. Apache Batik version 1.7 is distributed
under the terms of the Apache v2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either
express or implied. See the license for the specific language governing rights and limitations under the license. You can view
a copy of the license at: <Capital_install_location>/docs//legal/apache_2.0.pdf. Portions of this software may be subject to the
Apache version 1.1 License. You can view a copy of Apache version 1.1 at: <Capital_install_location>/docs/legal/
apache_1.1.pdf. Portions of this software may be subject to W3C License. You can view a copy of the W3C License at:
<your_Mentor_Graphics_documentation_directory>/legal/w3c_2002.pdf.
----------------------------------
This software application may include XMLUnit version 1.3 third-party software, which is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. XMLUnit version 1.3 may be subject to the following
copyrights:
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
* Neither the name of the xmlunit.sourceforge.net nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------
This software application may include jetty version 4.2.27 third-party software. jetty version 4.2.27 is distributed under the
terms of the GNU Lesser General Public License v2.1 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF
ANY KIND, either express or implied. See the license for the specific language governing rights and limitations under the
license. You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/gnu_lgpl_2.1.pdf.
Portions of this software may be subject to the Apache License version 1.1. You can view a copy of the license at:
<your_Mentor_Graphics_documentation_directory>/legal/apache_1.1.pdf. Portions of this software may be subject to W3C
License. You can view a copy of the W3C License at: <your_Mentor_Graphics_documentation_directory>/legal/
w3c_2002.pdf. To obtain a copy of the jetty version 4.2.27 source code, send a request to [email protected].
This offer shall only be available for three years from the date Mentor Graphics Corporation first distributed jetty version
4.2.27.
----------------------------------
This software application may include Apache POI version 3.8 third-party software. Apache POI version 3.8 is distributed
under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
KIND, either express or implied. See the license for the specific language governing rights and limitations under the license.
You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf. Apache POI
version 3.8 may be subject to the following copyrights:
Redistribution and use of this software and associated documentation ("Software"), with or without modification, are
permitted provided that the following conditions are met:
1. Redistributions of source code must retain copyright statements and notices. Redistributions must also contain a copy of
this document.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. The name "DOM4J" must not be used to endorse or promote products derived from this Software without prior written
permission of MetaStuff, Ltd. For written permission, please contact [email protected].
4. Products derived from this Software may not be called "DOM4J" nor may "DOM4J" appear in their names without prior
written permission of MetaStuff, Ltd. DOM4J is a registered trademark of MetaStuff, Ltd.
----------------------------------
This software application may include JGraphX version 1.10.1.0 third-party software. JGraphX version 1.10.1.0 is distributed
under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
KIND, either express or implied. See the license for the specific language governing rights and limitations under the license.
You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf. JGraphX
version 1.10.1.0 may be subject to the following copyrights:
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
Neither the name of JGraph Ltd nor the names of its contributors may be used to endorse or promote products derived from
this software without specific prior written permission. Termination for Patent Action. This License shall terminate
automatically, as will all licenses assigned to you by the copyright
This software application may include PostGreSQL jdbc version 9.1.902 third-party software, which is distributed on an "AS
IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. PostGreSQL jdbc version 9.1.902 may be
subject to the following copyrights:
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the PostgreSQL Global Development Group nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
-Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
-Redistribution in binary form must reproduct the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
Neither the name of Sun Microsystems, Inc. or the names of contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
This software is provided "AS IS," without a warranty of any kind. ALL EXPRESS OR IMPLIED CONDITIONS,
REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED. SUN AND ITS
LICENSORS SHALL NOT BE LIABLE FOR ANY DAMAGES SUFFERED BY LICENSEE AS A RESULT OF USING,
MODIFYING OR DISTRIBUTING THE SOFTWARE OR ITS DERIVATIVES. IN NO EVENT WILL SUN OR ITS
LICENSORS BE LIABLE FOR ANY LOST REVENUE, PROFIT OR DATA, OR FOR DIRECT, INDIRECT, SPECIAL,
CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE
THEORY OF LIABILITY, ARISING OUT OF THE USE OF OR INABILITY TO USE SOFTWARE, EVEN IF SUN HAS
BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
Neither the name of the MiG InfoCom AB nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------
This software application may include Apache Commons HttpClient version 3.1 third-party software. Apache Commons
HttpClient version 3.1 is distributed under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the specific language
governing rights and limitations under the license. You can view a copy of the license at:
<your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf.
----------------------------------
This software application may include Jetty version 8.1.5.v20120716 third-party software. Jetty version 8.1.5.v20120716 is
distributed under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing rights and
limitations under the license. You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/
legal/apache_2.0.pdf. Portions of this software may be subject to the Eclipse License version 1.0. You can view a copy of the
Eclipse License version 1.0 at: <your_Mentor_Graphics_documentation_directory>/legal/eclipse_1.0.pdf. Portions of this
software may be subject to the Common Development and Distribution License version 1.0. You can view a copy of the
Common Development and Distribution License version 1.0 at: <your_Mentor_Graphics_documentation_directory>/legal/
cddl_1.0.pdf.
----------------------------------
This software application may include SLF4J version 1.6.1 third-party software. SLF4J version 1.6.1 is distributed under the
terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND,
either express or implied. See the license for the specific language governing rights and limitations under the license. You can
view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf. SLF4J version 1.6.1
may be subject to the following copyrights:
© 2004-2005 SLF4J.ORG
© 2004-2005 QOS.ch
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify,
merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do
so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both
the above copyright notice(s) and this permission notice appear in supporting documentation.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE AND NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE
COPYRIGHT HOLDER OR HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY
SPECIAL INDIRECT OR CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM
LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS
SOFTWARE.
Except as contained in this notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the
sale, use or other dealings in this Software without prior written authorization of the copyright holder.
© 2004-2007 QOS.CH
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation
files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify,
merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do
so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software and that both
the above copyright notice(s) and this permission notice appear in supporting documentation.
----------------------------------
This software application may include PostgreSQL version 9.2.0 third-party software, which is distributed on an "AS IS"
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. PostgreSQL version 9.2.0 may be subject to the
following copyrights:
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
I M P L I E D W A R R A N T I E S , I N C L U D IN G , B U T N O T L I M I T E D T O , T HE I M P L I E D W A R R A N T I E S O F
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms are permitted provided that the above copyright notice and this paragraph
are duplicated in all such forms and that any documentation, advertising materials, and other materials related to such
distribution and use acknowledge that the software was developed by the University of California, Berkeley. The name of the
University may not be used to endorse or promote products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE.
Development of this software was funded, in part, by Cray Research Inc., UUNET Communications Services Inc., Sun
Microsystems Inc., and Scriptics Corporation, none of whom are responsible for the results. The author thanks all of them.
Redistribution and use in source and binary forms -- with or without modification -- are permitted for any purpose, provided
that redistributions in source form retain this entire copyright notice and indicate the origin and nature of any modifications.
I'd appreciate being given credit for this package in the documentation of software which uses it, but that is not a requirement.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL HENRY SPENCER BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
© 1988, 1993
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
I M P L I E D W A R R A N T I E S , I N C L U D IN G , B U T N O T L I M I T E D T O , T HE I M P L I E D W A R R A N T I E S O F
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the project nor the names of its contributors may be used to endorse or promote products derived from
this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE PROJECT AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
I M P L I E D W A R R A N T I E S , I N C L U D IN G , B U T N O T L I M I T E D T O , T HE I M P L I E D W A R R A N T I E S O F
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE PROJECT OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
src/backend/port/dynloader/netbsd.c
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
I M P L I E D W A R R A N T I E S , I N C L U D IN G , B U T N O T L I M I T E D T O , T HE I M P L I E D W A R R A N T I E S O F
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR
I M P L I E D W A R R A N T I E S , I N C L U D IN G , B U T N O T L I M I T E D T O , T HE I M P L I E D W A R R A N T I E S O F
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
----------------------------------
This software application may include HttpComponents version 4.0.1 third-party software. HttpComponents version 4.0.1 is
distributed under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing rights and
limitations under the license. You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/
legal/apache_2.0.pdf. Portions of this software may be subject to Apache License version 1.1. You can view a copy of the
Apache License version 1.1 at: <your_Mentor_Graphics_documentation_directory>/legal/apache_1.1.pdf.
----------------------------------
This software application may include Apache Jena version 2.7.1 third-party software. Apache Jena version 2.7.1 is
distributed under the terms of the Apache v2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
KIND, either express or implied. See the license for the specific language governing rights and limitations under the license.
You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf. Portions of
this software may be subject to W3C License. You can view a copy of the W3C License at:
<your_Mentor_Graphics_documentation_directory>/legal/w3c_2002.pdf. Apache Jena version 2.7.1 may be subject to the
following copyrights:
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. The name of the author may not be used to endorse or promote products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
----------------------------------
This software application may include OAuth version Revision 1273 third-party software. OAuth version Revision 1273 is
distributed under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing rights and
limitations under the license. You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/
legal/apache_2.0.pdf.
----------------------------------
This software application may include Touchposé version 1.0 third-party software. Touchposé version 1.0 is distributed under
the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
KIND, either express or implied. See the license for the specific language governing rights and limitations under the license.
You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf.
-------------------------------------
This software application may include Jackson version 2.2.3 third-party software. Jackson version 2.2.3 is distributed under
the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
KIND, either express or implied. See the license for the specific language governing rights and limitations under the license.
You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf.
-------------------------------------
-------------------------------------
This software application may include Java Runtime Environment (JRE) version 1.7 update 51 third-party software. Java
Runtime Environment (JRE) version 1.7 update 51 distributed under the terms of the Oracle Corporation Binary Code License
Agreement for the JAVA SE RUNTIME ENVIRONMENT (JRE) VERSION 6 and JAVAFX RUNTIME VERSION 1and is
distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the
specific language governing rights and limitations under the license. You can view a copy of the license at:
<your_Mentor_Graphics_documentation_directory>/legal/oracle_binary_jre_javafx_6.pdf. Additional copyright notices and
license terms applicable to portions Java Runtime Environment (JRE) version 1.7 update 51 can be found here: <MGC
installed location>/jre/THIRDPARTYLICENSEREADME.txt
-------------------------------------
This software application may include Java Runtime Environment (JRE) version 1.8 update 5 third-party software. Java
Runtime Environment (JRE) version 1.8 update 5 distributed under the terms of the Oracle Corporation Binary Code License
Agreement for the JAVA SE RUNTIME ENVIRONMENT (JRE) VERSION 6 and JAVAFX RUNTIME VERSION 1and is
distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the
specific language governing rights and limitations under the license. You can view a copy of the license at:
<your_Mentor_Graphics_documentation_directory>/legal/oracle_binary_jre_javafx_6.pdf. Additional copyright notices and
license terms applicable to portions Java Runtime Environment (JRE) version 1.8 update 5 can be found here: <MGC installed
location>/publisher/javafx/runtime/jre/ THIRDPARTYLICENSEREADME.txt
-------------------------------------
This software application may include guava-libraries version 17.0 third-party software. guava-libraries version 17.0 is
distributed under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing rights and
limitations under the license. You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/
legal/apache_2.0.pdf.
-------------------------------------
This software application may include Apache Commons Compress version 1.8.1 third-party software. Apache Commons
Compress version 1.8.1 is distributed under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing
rights and limitations under the license. You can view a copy of the license at:
<your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf.
-------------------------------------
This software application may include jersey-media-multipart version 2.10 third-party software. jersey-media-multipart
version 2.10 is distributed under the terms of the Common Development and Distribution License version 1.0 and is
distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the
specific language governing rights and limitations under the license. You can view a copy of the license at:
<your_Mentor_Graphics_documentation_directory>/legal/ cddl_1.0.pdf.
-------------------------------------
This software application may include mimepull version 1.9.4 third-party software. mimepull version 1.9.4 is distributed
under the terms of the Common Development and Distribution License version 1.0 and is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing
rights and limitations under the license. You can view a copy of the license at:
<your_Mentor_Graphics_documentation_directory>/legal/ cddl_1.0.pdf.
-------------------------------------
This software application may include socketio version 1.0 third-party software, which is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied.
-------------------------------------
This software application may include ActiveMQ version 5.8.0 third-party software. ActiveMQ version 5.8.0 is distributed
under the terms of the Apache v2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either
express or implied. See the license for the specific language governing rights and limitations under the license. You can view
a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf. Portions of this software
may be subject to Common Development and Distribution License version 1.0. You can view a copy of the Common
Development and Distribution License version 1.0 at: <your_Mentor_Graphics_documentation_directory>/legal/cddl_1.0.pdf.
Portions of this software may be subject to Creative Commons License version 2.5. You can view a copy of the Creative
Commons License version 2.5 at: <your_Mentor_Graphics_documentation_directory>/legal/ creative_common_2.5.pdf.
Portions of this software may be subject to W3C License. You can view a copy of the W3C License at:
<your_Mentor_Graphics_documentation_directory>/legal/w3c_2002.pdf. ActiveMQ version 5.8.0 may be subject to the
following copyrights:
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
* Neither the name of the Ben Nolan nor the names of its contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any, must include the following acknowledgment: "This
product includes software developed by the MX4J project (http://mx4j.sourceforge.net)." Alternately, this acknowledgment
may appear in the software itself, if and wherever such third-party acknowledgments normally appear.
4. The name "MX4J" must not be used to endorse or promote products derived from this software without prior written
permission. For written permission, please contact biorn_steedom [at] users [dot] sourceforge [dot] net
5. Products derived from this software may not be called "MX4J", nor may "MX4J" appear in their name, without prior written
permission of Simone Bordet.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE MX4J CONTRIBUTORS BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
Neither the name of XStream nor the names of its contributors may be used to endorse or promote products derived from this
software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
* Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.
* Neither the name of the Alastair Tse nor the names of its contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions, and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions, and the disclaimer that
follows these conditions in the documentation and/or other materials provided with the distribution.
3. The name "JDOM" must not be used to endorse or promote products derived from this software without prior written
permission. For written permission, please contact <request_AT_jdom_DOT_org>.
4. Products derived from this software may not be called "JDOM", nor may "JDOM" appear in their name, without prior
written permission from the JDOM Project Management <request_AT_jdom_DOT_org>.
In addition, we request (but do not require) that you include in the end-user documentation provided with the redistribution
and/or in the software itself an acknowledgement equivalent to the following: "This product includes software developed by
the JDOM Project (http://www.jdom.org/)." Alternatively, the acknowledgment may be graphical using the logos available at
http://www.jdom.org/images/logos.
THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE JDOM AUTHORS OR THE PROJECT CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of the JDOM Project and was originally
created by Jason Hunter <jhunter_AT_jdom_DOT_org> and Brett McLaughlin <brett_AT_jdom_DOT_org>. For more
information on the JDOM Project, please see <http://www.jdom.org/>.
-------------------------------------
This software application may include select2 version 3.4.6 third-party software. select2 version 3.4.6 is distributed under the
terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND,
either express or implied. See the license for the specific language governing rights and limitations under the license. You can
view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf.
-------------------------------------
This software application may include ui-select2 version 0.0.5 third-party software, which is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied.
-------------------------------------
This software application may include Bootstrap version 3.1.1 third-party software, which is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied.
-------------------------------------
This software application may include ui-bootstrap version 0.11.0 third-party software, which is distributed on an "AS IS"
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied.
-------------------------------------
This software application may include Angularjs version 1.2.14 third-party software. Angularjs version 1.2.14 is distributed
under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
KIND, either express or implied. See the license for the specific language governing rights and limitations under the license.
You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf.
-------------------------------------
This software application may include ui-router version 0.2.10 third-party software, which is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied.
-------------------------------------
This software application may include jQuery version 1.11.1 third-party software, which is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied.
-------------------------------------
This software application may include ng-grid version 2.0.12 third-party software, which is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied.
-------------------------------------
This software application may include TableLayout version Rivision 103 third-party software. TableLayout version Rivision
103 is distributed under the terms of the Clearthought Software License and is distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing rights and
limitations under the license. You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/
legal/ clearthought_2.0.pdf.
-------------------------------------
This software application may include Apache Commons Codec version 1.6 third-party software. Apache Commons Codec
version 1.6 is distributed under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing rights and
limitations under the license. You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/
legal/apache_2.0.pdf.
------------------------------------
This software application may include Apache Commons Logging version 1.1.1 third-party software. Apache Commons
Logging version 1.1.1 is distributed under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing
rights and limitations under the license. You can view a copy of the license at:
<your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf.
------------------------------------
This software application may include Apache HttpComponents Client version 4.2.1 third-party software. Apache
HttpComponents Client version 4.2.1 is distributed under the terms of the Apache License version 2.0 and is distributed on an
"AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the specific language
governing rights and limitations under the license. You can view a copy of the license at:
<your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf
-------------------------------------
This software application may include TinyXML version 2.6.2 third-party software, which is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. TinyXML version 2.6.2 may be subject to the following
copyrights:
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any
damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and
redistribute it freely, subject to the following restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use
this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.
3. This notice may not be removed or altered from any source distribution.
------------------------------------
This software application may include Java Runtime Environment (JRE) version 1.8 Update 40 third-party software. Java
Runtime Environment (JRE) version 1.8 Update 40 distributed under the terms of the Oracle Corporation Binary Code License
Agreement for the JAVA SE RUNTIME ENVIRONMENT (JRE) VERSION 6 and JAVAFX RUNTIME VERSION 1and is
distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the
specific language governing rights and limitations under the license. You can view a copy of the license at:
<your_Mentor_Graphics_documentation_directory>/legal/oracle_binary_jre_javafx_6.pdf. Additional copyright notices and
license terms applicable to portions Java Runtime Environment (JRE) version 1.8 Update 40 can be found here:
<install_root>/edge_<version>/eclipse/jre/ THIRDPARTYLICENSEREADME.txt
------------------------------------
This software application may include Angular UI Grid version v3.0.0-rc.20 third-party software, which is distributed on an
"AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied.
-------------------------------------
This software application may include Jersey version 2.17 third-party software. Jersey version 2.17 is distributed under the
terms of the Apache version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either
express or implied. See the license for the specific language governing rights and limitations under the license. You can view
a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf. Portions of this software
may be subject to Common Development and Distribution License version 1.0 License. You can view a copy of the Common
Development and Distribution License version 1.0 at: <your_Mentor_Graphics_documentation_directory>/legal/cddl_1.0.pdf.
Jersey version 2.17 may be subject to the following copyrights:
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following
conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution.
3. Neither the name of the copyright holders nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-------------------------------------
This software application may include org.osgi.core version 4.2.0 third-party software.org.osgi.core version 4.2.0 is
distributed under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing rights and
limitations under the license. You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/
legal/apache_2.0.pdf.
-------------------------------------
This software application may include jersey media multipart version 2.17.0 third-party software.jersey media multipart
version 2.17.0 is distributed under the terms of the Common Development and Distribution License version 1.0 and is
distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the license for the
specific language governing rights and limitations under the license. You can view a copy of the license at:
<your_Mentor_Graphics_documentation_directory>/legal/cddl_1.0.pdf.
-------------------------------------
This software application may include angular-spinner version 0.6.1 third-party software, which is distributed on an "AS IS"
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied.
-------------------------------------
This software application may include spin.js version 2.1.0 third-party software, which is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied.
-------------------------------------
This software application may include pdf.js version 1.1.13 third-party software. pdf.js version 1.1.13 is distributed under the
terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND,
either express or implied. See the license for the specific language governing rights and limitations under the license. You can
view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf. pdf.js version 1.1.13
may be subject to the following copyrights:© 1990-2009 Adobe Systems Incorporated.All rights reserved.Redistribution and
use in source and binary forms, with or without modification, are permitted provided that the following conditions are
met:Redistributions of source code must retain the above copyright notice, this list of conditions and the following
disclaimer.Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following
disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of Adobe Systems
Incorporated nor the names of its contributors may be used to endorse or promote products derived from this software without
specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND
CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
-------------------------------------
This software application may include PDFBox version 1.8.9 third-party software. PDFBox version 1.8.9 is distributed under
the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
KIND, either express or implied. See the license for the specific language governing rights and limitations under the license.
You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf. PDFBox
version 1.8.9 may be subject to the following copyrights:©1990-2009 Adobe Systems Incorporated.All rights
reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that the
following conditions are met:Redistributions of source code must retain the above copyright notice, this list of conditions and
the following disclaimer.Redistributions in binary form must reproduce the above copyright notice, this list of conditions and
the following disclaimer in the documentation and/or other materials provided with the distribution. Neither the name of
Adobe Systems Incorporated nor the names of its contributors may be used to endorse or promote products derived from this
software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS
AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE
FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
-------------------------------------
This software application may include lodash version 3.10.0 third-party software, which is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied. lodash version 3.10.0 may be subject to the following
copyrights:© 2006, Yahoo! Inc.All rights reserved.Redistribution and use of this software in source and binary forms, with or
without modification, are permitted provided that the following conditions are met:* Redistributions of source code must
retain the above copyright notice, this list of conditions and the following disclaimer.* Redistributions in binary form must
reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other
materials provided with the distribution.* Neither the name of Yahoo! Inc. nor the names of its contributors may be used to
endorse or promote products derived from this software without specific prior written permission of Yahoo! Inc.THIS
SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.© 2007, Parakey
Inc.All rights reserved.Redistribution and use of this software in source and binary forms, with or without modification, are
permitted provided that the following conditions are met:* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.* Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with
the distribution.* Neither the name of Parakey Inc. nor the names of its contributors may be used to endorse or promote
products derived from this software without specific prior written permission of Parakey Inc.THIS SOFTWARE IS
PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY,
OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-------------------------------------
This software application may include Font Awesome version 4.3.0 third-party software. Font Awesome version 4.3.0 is
distributed under the terms of the SIL Open Font License Version 1.1and is distributed on an "AS IS" basis, WITHOUT
WARRANTY OF ANY KIND, either express or implied. See the license for the specific language governing rights and
limitations under the license. You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/
legal/sil_open_font_1.1.pdf. To obtain a copy of the Font Awesome version 4.3.0 source code, send a request to
[email protected].
-------------------------------------
This software application may include Chart.js version 1.0.2 third-party software, which is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied.
-------------------------------------
This software application may include Chart.StackedBar.js version 1.0.3 third-party software, which is distributed on an "AS
IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied.
-------------------------------------
This software application may include textAngular version 1.3.7 third-party software, which is distributed on an "AS IS" basis,
WITHOUT WARRANTY OF ANY KIND, either express or implied.
-------------------------------------
This software application may include angular-chart.js version 0.7.2 third-party software, which is distributed on an "AS IS"
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. angular-chart.js version 0.7.2 may be subject to
the following copyrights:© Jerome Touffe-Blin ("Author")All rights reserved.The BSD LicenseRedistribution and use in
source and binary forms, with or without modification, are permitted provided that the following conditions are met:1.
Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.2.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer
in the documentation and/or other materials provided with the distribution.THIS SOFTWARE IS PROVIDED BY THE
AUTHOR AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT
NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OFSUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.
-------------------------------------
This software application may include fontbox.jar version 1.8.9 third-party software. fontbox.jar version 1.8.9 is distributed
under the terms of the Apache License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
KIND, either express or implied. See the license for the specific language governing rights and limitations under the license.
You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf. fontbox.jar
version 1.8.9 may be subject to the following copyrights:© 2002-2007, www.pdfbox.org© 2006-2007, www.jempbox.orgAll
rights reserved.Redistribution and use in source and binary forms, with or without modification, are permitted provided that
the following conditions are met:1. Redistributions of source code must retain the above copyright notice, this list of
conditions and the following disclaimer.2. Redistributions in binary form must reproduce the above copyright notice, this list
of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.3.
Neither the name of pdfbox; nor the names of its contributors may be used to endorse or promote products derived from this
software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS
AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.© 1997,1998,2002,2007 Adobe Systems IncorporatedPermission is hereby granted, free of charge, to any
person obtaining a copy of this documentation file to use, copy, publish, distribute, sublicense, and/or sell copies of the
documentation, and to permit others to do the same, provided that: - No modification, editing or other alteration of this
document is allowed; and - The above copyright notice and this permission notice shall be included in all copies of the
documentation.Permission is hereby granted, free of charge, to any person obtaining a copy of this documentation file, to
create their own derivative works from the content of this document to use, copy, publish, distribute, sublicense, and/or sell the
derivative works, and to permit others to do the same, provided that the derived work is not represented as being a copy or
version of this document.Adobe shall not be liable to any party for any loss of revenue or profit or for indirect, incidental,
special, consequential, or other similar damages, whether based on tort (including without limitation negligence or strict
liability), contract or other legal or equitable grounds even if Adobe has been advised or had reason to know of the possibility
of such damages. The Adobe materials are provided on an "AS IS" basis. Adobe specifically disclaims all express, statutory, or
implied warranties relating to the Adobe materials, including but not limited to those concerning merchantability or fitness for
a particular purpose or non-infringement of any third party rights regarding the Adobe materials.© 1990-2010 Adobe Systems
Incorporated.All rights reserved.Redistribution and use in source and binary forms, with or without modification, are
permitted provided that the following conditions are met:Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the
distribution. Neither the name of Adobe Systems Incorporated nor the names of its contributors may be used to endorse or
promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED
BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
AD V I S E D OF T HE P OS S I B IL IT Y O F S U C H D A M A GE .© 20 0 2- 2 00 7 , w ww . f o nt b ox . o rg © 2 0 06 - 20 0 7,
www.jempbox.orgAll rights reserved.Redistribution and use in source and binary forms, with or without modification, are
permitted provided that the following conditions are met:1. Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.2. Redistributions in binary form must reproduce the above
copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with
the distribution.3. Neither the name of fontbox; nor the names of its contributors may be used to endorse or promote products
derived from this software without specific prior written permission.THIS SOFTWARE IS PROVIDED BY THE
COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.© 1995-2009 International Business Machines Corporation and others All rights
reserved.Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated
documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use,
copy, modify, merge, publish, distribute, and/or sell copies of the Software, and to permit persons to whom the Software is
furnished to do so, provided that the above copyright notice(s) and this permission notice appear in all copies of the Software
and that both the above copyright notice(s) and this permission notice appear in supporting documentation.THE SOFTWARE
IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
NONINFRINGEMENT OF THIRD PARTY RIGHTS. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR
HOLDERS INCLUDED IN THIS NOTICE BE LIABLE FOR ANY CLAIM, OR ANY SPECIAL INDIRECT OR
CONSEQUENTIAL DAMAGES, OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.Except as contained in this
notice, the name of a copyright holder shall not be used in advertising or otherwise to promote the sale, use or other dealings in
this Software without prior written authorization of the copyright holder.
-------------------------------------
This software application may include pdf.js version 1.1.13 third-party software. pdf.js version 1.1.13 is distributed under the
terms of the Mozilla Public License version 2.0 and is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
KIND, either express or implied. See the license for the specific language governing rights and limitations under the license.
You can view a copy of the license at: <your_Mentor_Graphics_documentation_directory>/legal/mozilla_2.0.pdf. Portions of
this software may be subject to Apache License version 2.0. You can view a copy of the Apache License version 2.0 at:
<your_Mentor_Graphics_documentation_directory>/legal/apache_2.0.pdf. To obtain a copy of the pdf.js version 1.1.13
source code, send a request to [email protected]. pdf.js version 1.1.13 may be subject to the following
copyrights:© 1990-2009 Adobe Systems Incorporated.All rights reserved.Redistribution and use in source and binary forms,
with or without modification, are permitted provided that the following conditions are met:Redistributions of source code must
retain the above copyright notice, this list of conditions and the following disclaimer.Redistributions in binary form must
reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other
materials provided with the distribution. Neither the name of Adobe Systems Incorporated nor the names of its contributors
may be used to endorse or promote products derived from this software without specific prior written permission. THIS
SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS
OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF
THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Index
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.
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.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.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.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.