Stats

  • State Not Answered
  • Replies 1
  • Subscribers 43
  • Views 3232
  • Members are here 0
More Content

Set up intersecting BOM variants in Capture CIS?

AB_1717461526428

I have an OrCAD Capture CIS project with several BOM variants, where the variants are dependent on some properties (like Function and Type shown in the example below). However, certain combinations of these properties (i.e. Function #1 and Type #2) require additional parts. I figured I can add a separate group of Function1 and Type2, but this feels sloppy because my project has a lot of BOM variants and groups, so I'd have 7 of these "unique combination" groups which would make it difficult to keep track of parts.

Is there a way to integrate these combinations? Or a way to "layer" the groups somehow, so one takes priority over another?

Running OrCAD Capture CIS 17.4-2019 S020

  • Robert Finley
    0

    I love/hate variant manager.  As a side note, I requested enhancements Cadence won't consider for their roadmap.   Case #46765092

    I create groups for stuff and no-stuff as when editing the schematic, I can move the part from common to a stuff/no-stuff group but I can't assign the no-stuff flag outside of part manager, but I can assign that part to a group from the schematic view, which causes extra steps: make the sch changes, go to part manger, nostuff parts are already in a folder named, put a real folder name on it, merge that group with the stuff folder and it's ready to be verified with variant view.  Ugly process but it's accurate.

    Anyway, to export a variant BOM, every single part needs to be explicitly declared in a variant having one or more groups. 

    If one of your groups has an alternate but missing a part or two groups have a duplicate part, you can't run the BOM report for that variant if a "?" shows up in Part Manager. 

    This company uses Variants for marketing requests for a cost breakdown for each feature/circuit block.   I set up discrete groups and variants for each block.  Makes future changes a bit easier to implement and report. 

    Until Cadence gives us a way to have a negative group in a variant (all parts no-load), I have to maintain copies of the circuit block groups and set no-stuff on the parts in this block.  If a part is added to the populate, but its missing from the remove group, I won’t be able to export a circuit-block variant BOM.

    No matter how complicated ugly I make Part Manager, it pays off when the sudden demand pops up for a production configuration that skips an entire feature, like WiFi.

Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.