Overview

This chapter contains high-level information about working with Capital Project.

Introduction to Capital Project

Capital Project is the application used to administer projects and their designs for the Capital suite of applications. A project is usually an automotive or aerospace product line and acts as the top-level container for all designs and data comprising that product line.

Once created, a project can have data added from many Capital applications — for example, electrical schematic designs from Capital Logic, topological diagrams from Capital Integrator, and harness designs from Capital Harness Classic or Capital HarnessXC / ModularXC.

Data within a project is organized into designs — versionable data containers whose contents can be copied as needed. A design is usually created per sub-system of a product line, and contains diagrams created in one of the design applications (system/wiring diagrams from Capital Logic, harness diagrams from Capital HarnessXC / ModularXC, topological diagrams from Capital Integrator).

Hierarchy: Project → Designs → Diagrams.

After a project is created, it can be opened in the design applications (Capital Logic, Capital Integrator, Capital HarnessXC / ModularXC) to create the required diagrams for its designs. The Open Project facility in those applications shows the same project list as Capital Project (unless the system administrator has imposed project access restrictions via Capital User).

User Access Rights in Capital Project

Access to Capital Project functionality is managed in the Capital User application. See the Capital User User Guide for details on creating user accounts and assigning roles/permissions.

Application Memory Allocation

You can specify the maximum amount of physical memory (on the client computer) that each Capital application is permitted to use during operation.

• To set different amounts per application: use the Edit Capital Configuration dialog box (accessed from the Capital Launcher).
• To set the same amount for all applications: either use Edit Capital Configuration (same value for each app), or start the launcher from a command line with an -appmx parameter.

Note: if you use the appmx launcher argument, the Memory Allocation (MB) column in Edit Capital Configuration is dimmed (disabled).

Sub-topics: Changing the Application Memory Allocation Using Edit Capital Configuration, Changing the Application Memory Allocation Using Command Line Parameters.

Object Model Integrity

To ensure database integrity, Capital can validate data object models (components, designs, nets, etc.) automatically when changes are made. Validation errors are reported in a warning dialog and written to the event log; the triggering action is aborted so an invalid object model is never written to the database (preventing data corruption).

Validation level is set in clientprops.xml (in the config sub-directory of the Capital install directory):

<validation level="VALUE"/>

VALUE options:

• NONE — no validation performed.
• LOW — validation on import, save, and design generation. Otherwise none, unless an exception is raised (then also on export and load).
• MEDIUM — validation on import, export, load, save, and design generation. Otherwise none, unless an exception is raised (then also on object modification).
• HIGH — validation on load, save, import, export, design generation, and object modification.

Optional arguments can be added to the validation statement, e.g.:

failureStopsExportValidation="true"
exceptionIncreasesLevel="true"
exceptionTriggersValidation="true"

• failureStopsValidation: false = validation continues after a failure is detected; true = validation stops after a failure.
• failureStopsExportValidation: false = export continues after a failure; true = export stops after a failure.
• (Additional similarly-named arguments control behavior when exceptions are raised, per the same pattern — increasing the effective validation level or triggering validation on exception.)

Project Browser Tree

The Project Browser tree sits on the left of the Capital Project application window and provides access to functionality:

• System node — functionality for setting values/preferences at system level (shared across all projects). See "System-Level Data".
• Projects node — functionality for editing individual projects. See "Project".

Note: a project must be opened to become visible in the browser tree (see "Opening an Existing Project").

Filtering the Browser Tree: enter a string in the filter field at the bottom of the tree (next to the Enter Filter String icon) to show only nodes whose labels contain that string. Click the Clear Filter String icon to restore all nodes.

Diagram Language Translation

Diagrams can be displayed, printed, and published with text rendered in any given language using a language database stored as part of system data — enabling multi-language service documentation. Capital Project supports translatable strings for design descriptions and default names. See "Diagram Language Translation" in the Capital Design Tools – Common Functions User Guide for full details.

Support of Federal Aviation Regulations (FAR) Part 25 Subpart H EWIS Requirements

A document on the Capital community explains, at a general/high level, how Capital products can help customers address FAR Part 25 Subpart H Electrical Wiring Interconnection System (EWIS) requirements. It is informational only — not an implementation/deployment recommendation, and Siemens makes no warranties regarding it.

Product Excellence Program

The Product Excellence Program collects anonymous, voluntary usage data (installation details, features used, usage patterns) to help Siemens Digital Industries Software improve products. It can be toggled in System Preferences. It is designed to protect user privacy and the IP created through use of Siemens software; data is analyzed in aggregate across many users to surface usage-pattern insights.