Teamcenter saving to files not "checked out"

[Bluewolf]

We're working in NX 6 with Teamcenter 8. What is the setting in TC or NX that will only allow users to save files that they have checked out? Currently if a file is not checked out by someone else or released so that it is locked, then any user who may make an accidental change to it is able to save to it even though this user did not check it out and only wanted it for background. Please no work arounds or rules to set up that would need to be distributed and taught to the entire group. We have a lot of new users who are struggling as it is and that problem would still be subject to human error. This "no saving non checked out files" needs to be set to a defualt in the system.

Thanks in advance.
J

 

[looslib]

It should be! Are you sure you are really saving the modified files that are released? Only someone with admin rights should be able to do that. All normal users should not be able to save a released file.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[Bluewolf]

That's what I thought. I can work on a model and save it to TC without ever checking it out. I'm just a designer so can't do any fixes because I don't have administrator privileges. I got the impression the Siemens people told out IT people "that's just the way it is" and I can't prove them wrong. If I could put the fix in front of their face maybe they would believe me.

 

[ewh]

Currently if a file is not checked out by someone else or released so that it is locked...

The OP is looking for a document control system for un-released files.

"Good to know you got shoes to wear when you find the floor." - [small]Robert Hunter[/small]

 

[cowski]

If you change a file and it is not released or checked out to anyone else, the system will implicitly check it out to you. You now have the right to save the file. I have worked for 2 different employers that use TC and that is the behavior of both systems. I assume it is the default behavior of TC.

 

[Bluewolf]

Cowski,
The system doesn't automatically check it out to the designer but it will save it. Just to be sure I took a simple model we had on file and made sure it was not checked out to me or anyone else. I put a simple hole in it, saved it and closed it. When I reopened the file the hole was there and it was still not checked out to anyone. We would not want the files to auto check out to the designer if it was saved. We have thousands of components in the powerpack (engine) alone and one person could tie up to many systems.

 

[cowski]

Yes, that is what is known as an 'implicit' checkout. If nobody has the file checked out to them, you are free to make changes. When you go to save the file, the system will check the file out, save it and check it back in (if the group the user belongs to would have permission to check the file out). It does this behind the scenes without user intervention.

one person could tie up to many systems

I'm not sure I understand what you mean here. Could you elaborate?

 

[Bluewolf]

I'm not sure of the total function of "implicit" checkout. Regardless, we don't want accidental saves on files that are not checked out to the user doing the modeling. The user only checks out files they intend to modify and those are the ones they should be able to save. Again, we have many newbies to NX and TC and accidents have been happening.

 

[looslib]

From a PDM admin view point, I don't have a problem with an unreleased file being implicitly checked out and in on save. I do have a problem if this happens with a released file.
Is there a setting that can be set so all check-outs are explicit?


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[Bluewolf]

Released files are not being saved over, only files that are checked out and not checked out. Years ago I worked on TC's predecessor, Iman, and unless we had a file checked out it would not save it. This was a safety feature to avoid accidental changes to models that someone didn't own but were possibly using as background.

 

[cowski]

What type of accidents?
If they don't want to modify a file, why are they making changes to it?

I'm not sure if there is a setting to make all check outs explicit, if there is one you will have to get admin priviledges to change it. An alternative fix would be to customize the 'save' function to perform a 'save work part only' instead.

 

[looslib]

In Windchill, we can load a part into Wildfire in released or unreleased state. If we make a change to that part, it will ask if we want to check it out or continue without checking out. Released files are set so they cannot be checked out except by an admin. To change a released file, it must first be revised and then checked out.

NX will mark any file last modified in an older version of NX as modified. So the OP could have modified files that the system wants to save even if he doesn't want to.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[SDETERS]

Looslib did you ever find the answer to this post? Thanks

 

[looslib]

I'm not using TC, so I don't know what options are available.
In Windchill, the system will ask me if I want to check out any part that I download before allowing a change.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli

 

[SDETERS]

Oopps sorry Looslib I did not look close enough I thought you started this thread. It was bluewolf.
So Bluewold did you find an answer to this thread? Thanks

 

[gbangs]

File -> Customer Defaults… Teamcenter Integration for NX – General tab
Check-out Policy
Automatic (Implicit upon modification) Manual (Explicit – must specifically Check-out with available options ie; File -> Utilities… Check-out Modified Parts, or Right-click file in ANT and Check-out)

Group, is this correct? Is this what you were looking for? You'll need to edit the Site preferences for "Global" use if it is.

Gary Bangs

http://www.lawrencepumps.com

 

[Bluewolf]

I never did find a solution and got so tied up in other projects that I was unable to pursue it further. I also got a little peeved at cowski's comment "What type of accidents? If they don't want to modify a file, why are they making changes to it?"
Apparently he lives and works in a perfect world where s**t doesn't happen.
gbangs,
Not sure if those settings would allow only checked out files to be saved and ignore any "non" checked out file. Accidental over saves have not been as prevalent in the group lately as more of the designers are getting comfortable with NX and Teamcenter after migrating from ProE and Intralink. We don't always check out the files we are accessing for one reason or another such as if it's just models being used for background. The problems would occur because all you have to do is something simple like change the color of a part/assembly (just for visual clarity or whatever reason) that you are using for background and NX considers it modified and will save the file to TC even if that file is not checked out by the designer. Does anyone know if those settings gbangs provided would accomplish what I am looking for?
Thanks for the help.
J