Working with Projects

This chapter details how to create, edit, and work with projects in Capital Project Manager. Topics covered:

• Project
• Release Level
• Options
• Module Code Maintenance
• SBOM Pattern Management
• Default Object Names
  • Specifying Default Object Names for a Project
• Advanced Naming
• Object Type Information
• Usage Definition
• Preferred Component
• Option Configuration
• Option Expression
• Build List
• Design Abstraction
• Code Translation
• Change Policy
• Dataset
• Importing Library Component Data
• Importing Symbol Data
• Project Template
• Shared Object
• Configuring the Cleanup and Stopping of ANS Tagging for a Project Group

Summary of key concepts:

• Project — the top-level container for a set of related designs; creation, properties, and management.
• Release Level — versioning/maturity-state tagging for projects or designs (e.g. draft, released).
• Options / Option Configuration / Option Expression — the options-management framework used to define variant configurations of a design (e.g. build options that drive which components/wiring are included), including expressions for conditional logic.
• Module Code Maintenance — administration of module codes used to classify/identify design modules.
• SBOM Pattern Management — management of Software/System Bill of Materials patterns.
• Default Object Names / Specifying Default Object Names for a Project / Advanced Naming — configurable naming conventions and templates applied automatically to new design objects.
• Object Type Information — metadata describing object types available in the system.
• Usage Definition — definitions describing how components/objects are intended to be used within designs.
• Preferred Component — mechanism for designating preferred parts/components for selection.
• Build List — a list defining which options/variants are included in a particular build of a product.
• Design Abstraction — levels of abstraction supported for representing designs (e.g. logical vs. physical).
• Code Translation — translation of internal codes to human-readable or export-specific representations.
• Change Policy — rules governing how and when changes to project data are permitted.
• Dataset — named collections of data associated with a project.
• Importing Library Component Data / Importing Symbol Data — workflows for bringing part-library and symbol data into a project.
• Project Template — reusable templates for quickly creating new projects with predefined structure/settings.
• Shared Object — objects that can be shared and reused across multiple projects/designs.
• Configuring the Cleanup and Stopping of ANS Tagging for a Project Group — administrative configuration for Automatic Nomenclature System (ANS) tagging cleanup behavior across a group of projects.

(This is a chapter-landing page; each bullet links to its own detailed topic page in the source documentation.)