Considerations for Working with Concepts

Concept designs typically evolve in the following ways:

• From ideas and formal requirements;

• From existing concepts or concept templates (using Save As);

• As independent concepts, which contribute to detailed design requirements of prototypes and future products.

Create a Concept

Create a concept from the ground up for sole concept ownership, and to define concept structures that can fulfill specific ideas and requirements.

Create a Concept Using Save As

Use Save As to create a copy of the original concept and its proposal, with the following benefits:

• Reuse specific concept versions;

• Select a different concept type from the original;

• Retain or remove content details of the original concept, including structure, attachments and designs, requirements, relationships, and team;

• Retain or remove content details of the original proposal, including cost, revenue, resources, attachments, relationships, and projects.

Note:

You can copy concept attributes only if the source and target concept types match.

Delete a Concept

When you delete a concept, all data and relationships concerning the concept removed are irrecoverable from the application.

Apart from the concept itself, the deleted concept data includes:

• Concept structure;

• Product proposal;

• Attachments at concept and component level;

• Links to designs, bidirectional relationships, top-level requirements, and items;

• Solution alternatives;

• Concept team.

Note:

You can only delete the highest concept version, until you reach version 1; and only then can you delete the whole concept.