bulinorotto
Guest
I asked those who follow me. in principle the product can be encapsulated. on some more widespread software are directly integrated the less popular are encapsulated.
if you need more, I'll give you direct reference
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
if you need more, I'll give you direct reference
dallaz
Guest
1) the quickest solution is to copy the entire project folder, and make changes, as already suggested by others. ties are based on the relative path, so if the files are inside a folder, all ties are maintained. at the end of the project you can delete unused versions, and keep only the main milestones. the cost of memory in €/gb falls continuously, so the solution is easy to implement. It also calculates the time you save, because you don't have to redefine the connections.
2) change only the single file, making a backup copy of the file and changing the one currently mounted, makes sense if you do not introduce any feature related to other parts.
this means no assembly cut and no feature that creates links between the modified part and other parts.
This is because if you had to "go back", your backup copy may not have the ids of the various geometries you told in the new features, and in fact you would have broken links. this applies to any feature-based cad.
rest of the idea that solution 1 is safer and faster than 2.
3) toptron, through programming bees can interface with plm
4) there are modules that could help you in the editing process, helping you reduce the number of tests, such as the advanced deformation module.
in these last two cases, the best thing would be to contact the reference business and illustrate your process, so you know the details and advise yourself to the best.
Good weekend!
2) change only the single file, making a backup copy of the file and changing the one currently mounted, makes sense if you do not introduce any feature related to other parts.
this means no assembly cut and no feature that creates links between the modified part and other parts.
This is because if you had to "go back", your backup copy may not have the ids of the various geometries you told in the new features, and in fact you would have broken links. this applies to any feature-based cad.
rest of the idea that solution 1 is safer and faster than 2.
3) toptron, through programming bees can interface with plm
4) there are modules that could help you in the editing process, helping you reduce the number of tests, such as the advanced deformation module.
in these last two cases, the best thing would be to contact the reference business and illustrate your process, so you know the details and advise yourself to the best.
Good weekend!
TECNOMODEL
Guest
at mold level is a method that works, with several limits but at the end it works.1) the quickest solution is to copy the entire project folder, and make changes, as already suggested by others. ties are based on the relative path, so if the files are inside a folder, all ties are maintained. at the end of the project you can delete unused versions, and keep only the main milestones. the cost of memory in €/gb falls continuously, so the solution is easy to implement. It also calculates the time you save, because you don't have to redefine the connections.
2) change only the single file, making a backup copy of the file and changing the one currently mounted, makes sense if you do not introduce any feature related to other parts.
this means no assembly cut and no feature that creates links between the modified part and other parts.
This is because if you had to "go back", your backup copy may not have the ids of the various geometries you told in the new features, and in fact you would have broken links. this applies to any feature-based cad.
rest of the idea that solution 1 is safer and faster than 2.
3) toptron, through programming bees can interface with plm
4) there are modules that could help you in the editing process, helping you reduce the number of tests, such as the advanced deformation module.
in these last two cases, the best thing would be to contact the reference business and illustrate your process, so you know the details and advise yourself to the best.
Good weekend!
the problem arises if you work on something that is not a mold and use some assemblies/components on multiple projects.
by making the copy you will have n copies of the same set/component scattered for the server without any connection.
then, practical example, I go to introduce a change in a set/component that must always be realized in that way in the future. Well, when I have to reuse that modified component, I will have to remember which project this modification was made.
then arrives the day when a colleague will go to use that component for a new project, first of all he must have been informed of the change, then he will have to remember the thing and go fishing from the folder in which the component has been modified.
in my view is a bad way of working.
dallaz
Guest
In this case the context is a little different (first we talked about versioning within the same order, while in the second example we are talking about subaxis/components to be used in several projects).
idea basethe reusable components I would copy them in a separate folder, thus creating a custom library, which you can also put on the network.
when you need to use those components or assemblies within a commit, you can add them using "add duplicate" (This creates a copy of the components within the project folder, Slogata from the master).
If you know that the master must be modified from a certain moment on, you can update the file inside the library. In this way the whole team can access the updated version, and keep a certain order.
attention: using the command aggiungi instead of adding duplicates, create a direct connection to the file in the library. in this case, if in the future you will go to edit the file, this may cause recalculations when you go to open an old project.
advanced designlibrary with parameterized components (main rates or setup).
library with components created as a catalog.
in all cases, the main concept is to have a unique place where to deposit files to reuse. these files become part of your business knowledge, and will be kept up to date over time, always making a backup of old revisions, so you can know the story of a component.
idea basethe reusable components I would copy them in a separate folder, thus creating a custom library, which you can also put on the network.
when you need to use those components or assemblies within a commit, you can add them using "add duplicate" (This creates a copy of the components within the project folder, Slogata from the master).
If you know that the master must be modified from a certain moment on, you can update the file inside the library. In this way the whole team can access the updated version, and keep a certain order.
attention: using the command aggiungi instead of adding duplicates, create a direct connection to the file in the library. in this case, if in the future you will go to edit the file, this may cause recalculations when you go to open an old project.
advanced designlibrary with parameterized components (main rates or setup).
library with components created as a catalog.
in all cases, the main concept is to have a unique place where to deposit files to reuse. these files become part of your business knowledge, and will be kept up to date over time, always making a backup of old revisions, so you can know the story of a component.