Skip to main content
K
KarenMoore1-Visitor
1-Visitor
April 26, 2011
Question

Managing Layers

  • April 26, 2011
  • 7 replies
  • 2247 views

Someone gave a presentation at PTC/User Conference several years back on
managing layers. Does anyone have that or know how I can get that
presentation? I can't find it in the archives.
Karen Moore,
Designer Sr. CAD
National Nuclear Security Administration's
Kansas City Plant
Managed by Honeywell FM&T, LLC
kmoore@kcp.com

    7 replies

    K
    KarenMoore1-VisitorAuthor
    1-Visitor
    April 26, 2011

    Yes! Thanks for the quick reply. Attached is the file.

    K
    KarenMoore1-VisitorAuthor
    1-Visitor
    April 26, 2011

    I don't have the link. The presentation is from the 2007 PTCUser World Event. I have attached the file again. Thedemos are not available which it what I was looking for.

    In Reply to Karen Moore:



    Yes! Thanks for the quick reply. Attached is the file.


    D
    dgschaefer21-Topaz II
    21-Topaz II
    April 26, 2011
    The presentation is also attached to this excellent thread on the
    subject at MCADCentral:



    P
    ptc-1412741-Visitor
    1-Visitor
    May 5, 2011
    Does anyone have experience with the RESTRUCTURE command?

    How I understand it works, is that you can tell an assembly component that it now reports to a different assembly via dragging in the model tree.

    It sounds good on paper, but I'm not exactly sure how it works. It would have to break all the relations of the ASM it reports to, and change them to the new ASM, while keeping the same physical assembly constraints.

    It also sounds too good to be true. I also suspect that it might cause havoc with Team Center Enterprise, our PDM system here.

    It would save me a lot of work, but...


    Doug Pogatetz
    Northrop Grumman Corporation



    P
    ptc-1412741-Visitor
    1-Visitor
    May 5, 2011
    Sorry for the double post...

    Does anyone have experience with the RESTRUCTURE command?

    How I understand it works, is that you can tell an assembly component that it now reports to a different assembly via dragging in the model tree.

    It sounds good on paper, but I'm not exactly sure how it works. It would have to break all the relations of the ASM it reports to, and change them to the new ASM, while keeping the same physical assembly constraints.

    It also sounds too good to be true. I also suspect that it might cause havoc with Team Center Enterprise, our PDM system here.

    It would save me a lot of work, but...

    Doug Pogatetz
    Northrop Grumman Corporation
    L
    lylebeidler1-Visitor
    1-Visitor
    May 5, 2011
    In some ways it's too good to be true; in others, it's fantastic.



    The important thing to mention is that when you say "would have to break all
    the relations of the ASM it reports to, and change them to the new ASM,
    while keeping the same physical assembly constraints." Ideally, this would
    be true, but that's not what it does*. Rather, it retains a relationship to
    the original assembly. So, for example, if I have

    1.asm

    --2.asm

    ----a.prt

    ----b.prt

    --c.prt



    And restructure it to

    1.asm

    --2.asm

    ----a.prt

    ----b.prt

    ----c.prt



    (in other words, c.prt was not a component in 2.asm, now it is)

    If I do this, and I'm using Intralink, I cannot check 2.asm back into
    Commonspace without checking in 1.asm, because 2.asm needs 1.asm to know
    where to put c.prt.



    I cannot speak to TeamCenter, as I've never used it, but from what I've
    read**, I'd hazard a guess this might indeed cause havoc with it.







    * - This may have changed in more recent versions; we're on WF3.

    ** - we're currently researching our successor to Intralink 3.4, so I've
    spend two days reading about TC & Agile & SAP with Pro/E data, and it sounds
    finicky, to say the least



    -



    Lyle Beidler
    MGS Inc
    178 Muddy Creek Church Rd
    Denver PA 17517
    717-336-7528
    Fax 717-336-0514
    <">mailto:-> -
    <">http://www.mgsincorporated.com>
    P
    ptc-1571021-Visitor
    1-Visitor
    May 5, 2011
    I'd plan ahead a little. If you create a new component in assembly mode or
    place a component in a different (higher or lower) assembly, it will
    remember the constraints when moved. If it was constrained to features or
    parts in the destination assembly, you can just move the part there and not
    have to redefine the constraints.



    Anytime you move a component from one assembly to another, it will retain
    its constraints. If the constraints are in a different location than the
    destination assembly, you will need to redefine the constraints locally if
    you don't want external references outside the assembly.



    Bill


    Terms & ConditionsCookie settingsAccessibility statement