Translation of Objects When

Generating Diagrams Using Templates (Prototypes)

When you use Capital Schematic Generator for Systems Integrator to generate partitioned diagrams using a template (prototype) design, the system translates various types of objects in particular ways.

Prototype Diagram Matching

You can use any wiring design (and its diagrams) as a template (prototype) when generating wiring diagrams. The template design can:

• Have been generated previously from any topological design using Capital Schematic Generator for Systems Integrator.

• Have been created manually in Capital Logic Designer without using Capital Schematic Generator for Systems Integrator.

Template (Prototype) Generated by Capital Schematic Generator

for Systems Integrator

The system works out which wiring diagrams from the template design to use. It does this using the following algorithm:

1. Checks for the existence of diagram properties on the template diagram that matches with the functional diagrams. Any matched diagrams are not considered in the following steps. Note Capital Schematic Generator for Systems Integrator creates two properties on any diagrams that it generates. These properties are Functional Diagram and Logical Design. These are the properties used in the first step. For example, a wiring diagram has a property Functional Diagram=Diagram1 and the wiring design has a property Logic Design=Functional power design.

2. Attempts to use internal base IDs to match the remaining template diagrams with the remaining functional diagrams. Any matched diagrams are not considered in the next step.

3. Uses diagram names to match the remaining template and functional diagrams. Note If there are unmatched functional wiring diagrams, the system creates corresponding wiring diagrams with no template.

Template (Prototype) Created Manually in Capital Logic Designer

In order to use a design that you have not generated previously using Capital Schematic Generator for Systems Integrator, you must add a property to the design. The property must be called SOURCE_PLANE_ID but can have any value. By adding this value, you enable the selection of this design in the Prototype field when generating diagrams. Without doing this, it is not available for selection.

You must also associate a functional diagram with each diagram in the template wiring design. You can do this by either:

• Naming the template diagrams so that the names follow the pattern [FunctionalDesignName]:[FunctionalDiagramName]. This creates an association between the template diagrams and the functional diagrams.

Or

• Adding the following two properties to the template diagrams: Logical Design Specify the name of the functional design with which you want to associate the template diagram.

Functional diagram Specify the name of the functional diagram with which you want to associate the template diagram.

Structural Matching of Prototype Paths

When finding the content to be replicated using a prototype, the system first determines the paths to be compared between the prototype diagram and the newly generated diagram. A path is the physical content that corresponds to a functional signal. After the system finds the prototype path to be replicated for a path in the generated wiring diagram, the internal content of the path is matched using base ids.

If internal content item (a wire or splice) has a match, it uses the layout from the prototype, otherwise, it ignores the prototype for that path and uses the net for a guided layout or routes from scratch between the end points of the path.

The systems also uses option expression information on the wires to correctly match paths. When there is no harness level/configuration information or if there are no matches using harness levels, the system picks path pairings deterministically.

For example:

There is a prototype path like this:

Figure 345: Structural Matching of Prototype Paths: Prototype Path

When the system generates a new wiring diagram using this as a prototype, the system attempts to match the ends of the path (PIN 1 on P1, PIN1 on P2 and PIN1 on P3) with path ends on the generated diagram. If there is no match, the system ignores all content within the path (splices and wires) when prototyping.

In this example, the ends match with the connectivity in the generated diagram:

Figure 346: Structural Matching of Prototype Paths: Generated Diagram

With the structural match of the path ends, the system can match the internal content based on the connection ends. It then traverses the path content. As there has been a re-synthesis in the Capital Systems Integrator design, the internal content is not matched using base ids or names.

In this example, the system looks for WIRE1 in the generated path starting from PIN1 on DEV1. In the prototype path, PIN1 of DEV1 and SP1 are both connected to the wire so the content between these two (WIRE1) is a structural match for WIRE4.

The structural match means that the system uses an algorithm that determines which joints are similar in the prototype path and the generated path.

Figure 347: Structural Matching of Prototype Paths: Structural Match

In this screenshot, the left side is the prototype and the right side is the generated diagram. The colored arrow lines indicate how the system has determined the similar joints. It identifies the edges to be mapped based on this information and uses the matched edges as prototypes. WIRE1 is matched with and used for WIRE4, WIRE3 for WIRE5, and WIRE2 for WIRE6.

In this example, the complete path content matches and so the complete path is used as a prototype and replicated.

The following examples show how the software behaves in different scenarios:

Prototype Path Example 1

The prototype has the path:

Figure 348: Prototype Path Example 1

And the generated diagram has a path like this:

Figure 349: Prototype Path Example 1: Generated Diagram

In this case, the system matches WIRE6 with WIRE2 and WIRE5 with WIRE3.

WIRE4 matches with WIRE1 : INLINE : WIRE12.

Therefore, the schematic route of WIRE1, J200.PIN1 and WIRE12 are used as the route for WIRE4.

Prototype Path Example 2

This example uses a different Capital Systems Integrator design to previous examples.

A functional Capital Logic Designer design is mapped to a Capital Systems Integrator design with no inlines and splices. You generate the first wiring design:

Figure 350: Prototype Path Example 2

The Capital Logic Designer design is associated with a second Capital Systems Integrator design. This design contains an inline and a splice as additional items:

Figure 351: Inline and Splice

When Capital Schematic Generator for Systems Integrator is invoked on this design using the first generated diagram as a prototype, the newly generated diagram is as follows:

Figure 352: Prototype Path Example 2: Generated Diagram

Prototype Path Example 3

A prototype is as follows:

Figure 353: Prototype Path Example 3

The generated wiring diagram contains a path like this:

Figure 354: Prototype Path Example 3: Generated Diagram

In this case, there is a complete structural match and the whole prototype is used.

Prototype Path Example 4

When there is a partial content match, part of it may be matched structurally. For the non-matching content, guided layout/routing is used.

The system has generated a wiring diagram as follows:

Figure 355: Prototype Path Example 4

The functional diagram is changed such that some devices are replaced and the wiring is re-synthesized in Capital Systems Integrator. The new functional diagram is as follows:

Figure 356: Prototype Path Example 1: New Functional Diagram

The system has added the new devices DEV6 and DEV7.

When Capital Schematic Generator for Systems Integrator is run again, the path DEV1 > WIRE1 > SP1 > WIRE3 > DEV3 matches structurally.

The other path from DEV7 to DEV6 does not have a match in the prototype. For this path, the system uses the functional diagram as the guide for layout and the standard guided layout rules apply.

Prototype Path Example 5

This example is concerned with center-strip splices. A prototype has two center-strip splices:

Figure 357: Prototype Path Example 5

The generated design has three wires for the same signal with two splices:

Figure 358: Prototype Path Example 5: Three Wires for Same Signal

It is not possible to use a prototype in this case even though it can be said that there is a structural match. This is because the system cannot map multiple generated objects to a single prototype object.

As in all examples, when a prototype cannot be used, the system uses the schematic route of the prototype to place the generated objects.

Prototype Path Example 6

This example is concerned with splices and multiterms.

Figure 359: Prototype Path Example 6

Given the prototype and generated diagram above, WIRE201 uses the schematic route of WIRE200 > SP1 > WIRE201 from the prototype. WIRE202 uses the schematic route of WIRE200 > SP1 > WIRE202.

Prototype Path Example 7

The topological design has different harnesses for LHD and RHD configurations for a signal from an associated functional diagram.

The functional diagram looks like this:

Figure 360: Prototype Path Example 7: Functional Diagram

It contains a signal COND1.

The topological diagram looks like this:

Figure 361: Prototype Path Example 7: Topological Diagram

There are different harnesses for LHD and RHD configurations.

There is a prototype (template) wiring diagram that the system has generated for both the LHD and RHD configurations together:

Figure 362: Prototype Path Example 7: Prototype for both LHD and RHD Configurations

The system has changed the names of the inline connectors (J3x to J3, P7x to P7 and so on).

The new, generated wiring diagram looks like this:

Figure 363: Prototype Path Example 7: Generated Diagram for LHD and RHD Configurations

The prototype matching uses structure and option expressions rather than object names. This means, the prototype inlines are matched correctly.

Mapping Using Base IDs and Names

The mapping algorithm uses a mixture of matching based on base IDs and name attributes of harness end objects (such as, devices) and structural matching for the inner content and connectivity.

Devices, harness connectors and their pins are matched using base IDs or names:

• First the system matches by base ID (some devices and connectors find a match with this rule).

• Then, for unmatched devices and connectors, the system matches by name.

The system follows a different approach for pin matching:

• If the device or connector is matched by base ID, all of its pins are matched by base-ID where possible.

• If the device or connector is matched by base ID and a pin cannot be matched by base ID (such as connector pins deleted and recreated in Capital Systems Integrator with the same name), the pin is matched by name.

• If the device or connector is matched by name, all of its pins are matched by name.

Base IDs or names are not used for matching harness plugs.

Structural matching is used to map wires, splices and inlines.

Shared

Object Revisions

If a Capital Schematic Generator for Systems Integrator diagram is generated as a multi-design then shared objects are likely to be created. Subsequent runs of Capital Schematic Generator for Systems Integrator will, wherever possible, re-use the original shared objects. However if the criteria listed below is not matched then a new revision of a shared object will be created. The system uses the following criteria for matching:

1. Base I.D. matches

2. Names match

3. Every property in the generated diagrams should have a property in the shared designs with the same value, that is, shared objects can have more properties.

4. Attribute values (if they exist) must match Option Expression

Analysis Model

Part Number

Customer Part Number

Customer Name

Supplier Part Number

Supplier Name

Number of Device Connectors (Devices only)

5. Generated pins also must have a matching pin in the shared design, that is, the shared pinlist can have more properties. For each pin: pin 1, pin 2, pin 3, pin 4 and so on must match

6. For inline connectors - the mating must match.

7. For connectors

• backshells (if they exist) must match For the backshell: 1, 2, 3, 4, must match.

Note

In both single and multi design mode, the pinlist is promoted to shared, if it is instance of composite symbol.

Example of Connector Matching

Consider the following example diagrams where an LHD Configuration Wiring Design (see Figure 366) is used as a template (prototype) for generating an RHD Configuration Wiring Design (see Figure 367):

Figure 364: Connector Matching Example: Associated Functional Design

Figure 365: Connector Matching Example: Topological Design

Figure 366: Connector Matching Example: Template (Prototype) LHD Configuration Design

Figure 367: Connector Matching Example: Generated RHD Configuration Design Using LHD Configuration Design as Prototype

The RHD device DEV1 has a different base ID and option expression from the LHD device named DEV1. Despite the different base IDs and option expressions, name matching (without expression) identifies the DEV1 in the Template (Prototype) LHD Configuration Design as a prototype for RHD DEV1.

However, the RHD connector P3 does not match the LHD connector P1 either by base ID or name. The system therefore uses device pin association to treat P1 as a prototype for P3.

By matching P3 with P1, the path or WIRE1 from the template is used as the prototype for WIRE2.

Resolution of Name Collisions During Prototype Mapping

If multiple devices in the generated design have the same name, one of the generated devices is mapped to all the devices with the same name in the prototype design. The remaining generated devices do not use any prototype. Any name collisions for harness plug connectors and unmated connectors are resolved in the same way.

Generation of Pins on Symbols

Capital Schematic Generator for Systems Integrator generates a pin on a symbol only if the pin is used on the Capital Systems Integrator diagram. That means, any pins from the symbol that are not used in the Capital Systems Integrator diagram are not added to the symbol instance in the generated wiring diagram.

When Capital Schematic Generator for Systems Integrator creates a wiring diagram, if it uses a prototype containing symbols and those symbol instances have insufficient pins for the newly synthesized wiring, then a new symbol instance is created for the additional pins.

Capital Schematic Generator for Systems Integrator does not add additional pins to symbol instances already existing in a prototype diagram.

Note

You can prevent the creation of a new symbol instance by adding the required pins to the prototype wiring diagram prior to running Capital Schematic Generator for Systems Integrator.

Parent Topic:

Capital Schematic Generator for Systems Integrator

Capital Systems Integrator User Guide, 2512.2606

Unpublished work. © 2026 Siemens