• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Allegro X Capture CIS
  3. How did an engineer nuke an entire Variant setup in a CIS...

Stats

  • Replies 2
  • Subscribers 43
  • Views 477
  • Members are here 0
More Content

How did an engineer nuke an entire Variant setup in a CIS project?

Robert Finley
Robert Finley 3 months ago

9 board revisions.  742 parts. 

We create a lot of groups because operations/marketing wants to know what each subcircuit costs in parts.

(on top of the usual US/EU/whatever RF part value changes.)

I feel nauseous...

Guess that three day build will be wasted.   I don't have a BOM.

  • Sign in to reply
  • Cancel
Parents
  • rg13
    rg13 3 months ago

    Are these 9 different variants of this design? If it is so, then Variant BOMs can be created for all 9 variants.

    With quantity and cost mentioned in part DB, cost of complete design parts can be estimated.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • rg13
    rg13 3 months ago

    Are these 9 different variants of this design? If it is so, then Variant BOMs can be created for all 9 variants.

    With quantity and cost mentioned in part DB, cost of complete design parts can be estimated.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
  • Robert Finley
    Robert Finley 3 months ago in reply to rg13

    I misspoke.  All of my Variant Groups are gone.  All Variants are gone.

    All parts now back in the common folder.

    Is there a way to go to an older sch in SVN and transfer just the PartManager groups between DSNs?

    It just happened again this morning.

    59 part manager groups.  Gone.  More upset over that than losing the variant data.

            

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information