Messages

1

General Board / Instance Diagram from Block Diagram

« on: June 12, 2024, 01:09:36 am »

Hello all,
First, thanks for any guidance in advance, this forum has been really helpful.
I have a number of variants of an assembly.
I have a block diagram of a generic version.
Each assembly uses different part numbers (modeled as instance on generic block)
These assemblies are considered a module, built from assemblies, that are built from components (ends up being a dozen BDD and IBD to define the whole)
I'd like to copy the block diagrams and be able to use the IBDs as well, but generate all instances.
They all follow the same BDD/IBD definition, but some of these end up with requirements that are not common across all assemblies, so I'd like to be able to bring full definition to each variant.
I would like to be able to go in and define all part names and values without doing this manually, especially the IBDs...
These components are not always compatible, so I can't just replace one part for a variant, for example
Any advice or a tutorial on how to do this without manually recreating every variant?

2

General Board / Re: Adding tagged values to certain elements

« on: March 27, 2024, 05:39:14 am »

I found a fairly simple way to add tags to everything in a package:

CSV Import/Export
Make sure you add the tag value to the export specification (add tagged value, select the element with that tag, add the tag as a field), when you import that file into the package (make sure you have the GUIDs) it adds those tags to all elements.

Another method I've been using is through generalization, but it can take some management...
All parts are categorized, those categories can all be categorized, say, as hardware.
Hardware can have P/N, Cost, Length, etc, allowing inheritance of those tags

3

General Board / Re: Requirements Inheritance

« on: August 20, 2023, 07:09:54 am »

Thanks Pete.
I like the idea of adding Common/Variant, as I'm currently working in Standard/Variant/Option concepts for architecture already.
I hadn't thought about actually identifying requirements this way, but I'll think about it as a way to manage regulatory requirements especially (my product has an absurd number of variance in requirements depending on the country it's sold in).
If this were one product, I'd be done.
I'm currently modeling multiple product lines that essentially fulfill a lot of the same functions into a "master model" and there is more to do at every turn.
What a cool exercise, though.
At this point I'm looking into using a matrix pulling from my architecture and requirements so I can manually copy the relationships from the "abstracted" element to the physical variant in the hope it can help keep things in order with the least amount of work.
After that, each physical product will inevitably have it's own "variant" requirements.

4

General Board / Re: Requirements Inheritance

« on: August 14, 2023, 03:03:04 am »

Thanks for the response.
I'm wondering if this difficulty came from the act of requirements management or the operation of the tool?
I'm now trying to tie the requirements to activities, which are then tied to functions, tied to solutions...
I am a novice, so while I grasp the concepts and basic use of the tool, I don't yet have the more advanced techniques down...
I'm happy to read and learn if someone knows where I can find this sort of information.

5

General Board / Requirements Inheritance

« on: August 11, 2023, 10:29:14 am »

I am modeling a product line with a number of variant products.
These variants use a generalization relationship to the product line.
There are a LOT of requirements that apply to all of the variants of this product line, while each variant has a few specific to it.
Is there any way to make sure the requirements are inherited from the "abstracted product"?
I'd like to be able to show each product's requirements, including the inherited plus the product specific.
I thought this would be fairly straight-forward, but I just can't get it to show up...