Working With Designs

This chapter covers how to work with designs (the versionable data containers held within a project) in Capital Project. It has 14 sub-topics, summarized below by documented purpose given the chapter's scope.

Design

A design is a versionable data container within a project, usually created per sub-system of a product line. It holds 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). Designs can have their contents copied as required and are the primary unit of work opened by designers in the design applications.

Design Revision

Covers design revisioning — creating and managing successive versions of a design over time, preserving history and enabling comparison/rollback between revisions.

Effectivity

Covers Effectivity — metadata that controls when/where a design object is applicable (e.g., by date, serial number range, or build), used to manage which variant of an object is "in effect" for a given context.

Engineering Change Order

Covers Engineering Change Orders (ECOs) — the formal mechanism for tracking and managing approved changes to a design, typically tying together the affected objects, justification, and revision history for a change.

Applicable Options

Covers determining/filtering which Option values (see Options in "Working with Projects") apply to a given design or design object, used in conjunction with Option Configuration and Option Expression to resolve which content is active.

Evaluated Design

Covers "evaluating" a design against a specific set of option/configuration selections (or a Build List) to materialize the concrete variant of that design implied by those selections.

Design Folder

Covers Design Folders — a organizational container used to group related designs within a project's browser tree, for organizational/navigational purposes.

Comparing Objects and Their Properties in Design Revisions or Build Lists

Covers the comparison tooling used to diff objects and their properties between two design revisions, or between two Build Lists, to identify what changed.

Design Rule Check Descriptions

Covers the reference descriptions of Design Rule Check (DRC) rules applicable to designs — used to validate designs against defined rules/constraints (see also "Rules and Constraints" in System-Level Data).

Import and Export of Designs

Covers the mechanisms for importing designs into a project and exporting designs out of a project (e.g., for transfer between installations, environments, or archival).

Saving Backup Copies of Designs

Covers the procedure for manually saving a backup copy of a design, distinct from the automatic Auto-Recovery mechanism (see "Auto-Recovery of Data after a Crash" in System-Level Data).

Restoring a Design from a Backup Copy

Covers the procedure for restoring a design from a previously saved backup copy, reverting it to that saved state.

Derivative Harness Design

Covers Derivative Harness Designs — a mechanism for creating a new harness design derived from an existing one, typically to represent a variant while retaining traceability to the source design.

Capital Harness Designer LD Integration

Covers integration points between Capital Project and Capital Harness Designer LD (Logical Design), relevant to how logical harness design data is represented and managed within the project/design structure.