[proi] - Released only database???

[amedina]

Using Pro/intralink 3.4 only/specifically what are the ideas around having
two databases? one would be a dynamic sandbox while the other would be for
released items only. How do you replicate from the junk database the
released items only to the other database. Specifically if you got a
family table how do you choose the items in the family? do you choose the
latest family or the latest released of each family member. How does a
family table react when the common space only has the latest released items.

besides the theoretical problems, I am wondering if this is actually done
in practice at some company right now. Was it ever done before. I know you
can replicate databases, but what I want is to pick/choose from one
database only the items that are released and I want it to magically work
without failures/missing items and such.

I'm probing for reaction to this idea or reaction to an actual install. Did
it work out? was a fiasco? was it nice first and then it became a typical
ptc fiasco later? Tell me tell me, I am all ears today.

regards,

Alfonso

PS, not that Im too interested in this so don't sell me anything please....
How has the need to filter to latest released only been addressed on
windchill 10? has it been addressed in windchill 9? I
ask rhetorically because I know out of the box these two always give you
junk in the real world applications. Just think of the thousands of files I
will have to deal with and their dependencies and parameters, how will
those play out in a move to get me pristine "latest released" items if I am
a sales rep with windchill access.

[MikeLockwood]

This is what the concept of "State" is for.


* On creation, the system assigns a lifecycle, consisting of various states and "transitions" that allow getting from one state to another (closely coupled with how you get ot the next Revision).

* Data still at the first state (e.g In Work) can be worked on but cannot be used for business purposes. Enforce this by not giving Read access at this state to those who can actually use the data for any business purpose.

* Design process(es) around how data objects have their state changed - this is the primary set of control points.

For family tables, need to make a global decision - manage individual instances or the entire family together. Managing each instance as a separate Revision works ok for the models; it's a bit complex but still works to manage all on a tabulated Drawing, but the Drawing Revision needs to go up each time any instance needs to change.

[amedina]

Its like I thought. Its silly to have two databases.

Yeah well I knew this from the beginning, I just need real ammo because a
supervisor who knows nothing of databases or intralink or pro/e was told by
a superior being of the pro/e (not intralink/pdm) inclination that we
should have two databases because that is what he thinks is best.

What this guy is not thinking is that it would take ridiculous amounts of
time from everyone to even try to keep up with changes. But this argument
is counteracted by "uhh ahh, we can automate that, can't we? I remember
someone at PTC did it once for his dog biscuit supply PDMlink database."
To which I'm thinking this guy has never had problems with family tables
and or has never paid for an oracle expert's help. Additionally, 25 years
of models, which amounts to some crazy oracle morbidly-fatning number of
parts will not all work nicely.

I put in a filter for "latest released" and even made it the default for
users who check-out.

{ITEM = '*'}:{VERSION with %PATH = 'Root Folder/LIBRARY/*' // VERSION =
%LATEST} {ITEM = '*.asm'}:{VERSION = %LATESTATRL('RELEASED_FIX')} {ITEM =
'*.prt'}:{VERSION = %LATESTATRL('RELEASED_FIX')} {ITEM = '*.asm'}:{VERSION
= %LATESTATRL('RELEASED')} {ITEM = '*.prt'}:{VERSION =
%LATESTATRL('RELEASED')} {ITEM = '*'}:{VERSION = %LATEST} {ITEM =
'*'}:{BRANCH = 'main' // VERSION = %LATEST}

But as you can see the first line says that if something is in the library
you should get only the latest rather than latest released items. Well, the
reason for this is that the library is packed with thousands of family
table parts. But each part is revised, or used to be revised individually
so you can't check out a family table that has all "latest released" items
in it. Without this, you get version conflict errors that prevent a
check-out. Otherwise the filter seems to be working OK.

However how do I patch the idea this manager has about his greatest
discovery "We have WIP parts mixed-in with Released parts?!!!" "holy cr#p
we better mobilize the army on this issue pronto". he literally thinks of
intralink as a folder where you dump the crap from your computer every day.

Maybe I should tell him that oracle has similar issues, that should fix
everything. All kidding and over-exageration aside, I will have to put
together a power point on how intralink works.

Its Friday. Happy Friday everyone. If you got any cool ideas on how to
explain what a database does, please don't hesitate to send them my way.

regards,

Alfonso