Inventor General Discussion

Inventor General Discussion

Reply
*Dotson, Sean
Message 1 of 8 (59 Views)

Request for Project Files

59 Views, 7 Replies
12-10-2002 08:58 PM
I tried this a few years ago but the user base was much smaller and I'm not
sure very many people understood projects back then. Well the user base and
software has grown a lot since then so let's try again....

I hear from a lot of users that the main thing missing form most project
documentation is real life examples. We've all shared parts of our project
structure at one time or another but I'd like to ask everyone to post (or
email me) their project files with a brief description of what you do (e.g.
custom one-of-0a-kind machines or 1000 variations of the same widget) and
why you structured the project the way you did.

For example:

______________________________________
[Project Defaults]
MultiUser=None
UseRelative=TRUE
ThirdParty=FALSE
v=0

[Included Path File]

[Workgroup Search Paths]
Assy=.\Workgroup\Assembly
Details=.\Workgroup\Details
Parts=.\Workgroup\Parts
Purchase=.\Workgroup\Purchase
PDF=.\Workgroup\PDF
AutoCAD2D=.\Workgroup\AutoCad2D
RefData=.\Workgroup\Ref Data

[Library Search Paths]
Iparts=i:\iparts6
_Iparts=.\Workgroup\iPartChildren

This is my project files structure used for my custom one-up machines. I
break down the Workgroup paths as I like to have one touch access to the
folders from the hyperlinked pane on the left. I divide files by file type
with further subdividing part files into custom machined parts and purchased
parts. The RefData folder is where I keep linked spreadsheets, decals and
other linked objects. I keep ipart children on a project specific basis as
I feel it makes the project more portable.
__________________________________________

That's it. I wanted to collect them all the put them together in a document
so that new users (heck even experienced users) could take a look and maybe
gain some insight as to how people structure their projects. If someone
builds similar designs to that of your they could pick up some suggestions
on how to structure their projects.

For those of you who don't know you can view your project (.ipj) files in
notepad and then cut and paste into here or an email. Feel free to change
the project names or fold names if you want to protect your designs'
privacy.

Thanks,
--
Sean Dotson, PE
http://www.sdotson.com
Check the Inventor FAQ for most common questions
http://www.sdotson.com/faq.html
-----------------------------------------
Distinguished Contributor
accu-cad
Posts: 339
Registered: ‎09-09-2003
Message 2 of 8 (59 Views)

Re: Request for Project Files

12-10-2002 09:12 PM in reply to: *Dotson, Sean
As a business I have seperate projects for each IV and Autocad job. Sending you each individual ipj would not seem benificial. Each just points to the location to where the files for that particular file reside. Library parts are on common paths for every project.

As a on-sight subcontractor I can send you how the cleint sets up there project files and there file structure. Do you need the whys relating to their ISO proceedures?
*Dotson, Sean
Message 3 of 8 (59 Views)

Re:

12-10-2002 09:16 PM in reply to: *Dotson, Sean
Just a brief description of the logic behind it as
I have given in the example above.  Just select one that seems the most
descriptive.  Some people will just have a workspace and that's it (and
sometimes that all you need).

 

I'm just trying to collect them so people can have
real world examples for which they keep screaming..

--

Sean Dotson, PE

href="http://www.sdotson.com">http://www.sdotson.com

Check the Inventor
FAQ for most common questions

href="http://www.sdotson.com/faq.html">http://www.sdotson.com/faq.html

-----------------------------------------


style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
As
a business I have seperate projects for each IV and Autocad job. Sending you
each individual ipj would not seem benificial. Each just points to the
location to where the files for that particular file reside. Library parts are
on common paths for every project.

As a on-sight subcontractor I can send you how the cleint sets up there
project files and there file structure. Do you need the whys relating to their
ISO proceedures?

*Hinterhoeller, Richard
Message 4 of 8 (59 Views)

Re: Request for Project Files

12-10-2002 09:42 PM in reply to: *Dotson, Sean
Sean:

Attached please find the ipj's of my current project. Some of the names
have been changed to protect the privacy of the individuals.

______________________________________
1206 Active Project.ipj

[Project Defaults]
MultiUser=FALSE
UseRelative=FALSE

[Included Path File]
Included Pathfile=c:\Projects\Inventor Path Files\Standard.ipj

[Workspace]
Workspace=c:\Projects\CD 5\1206 Active Project

[Local Search Paths]
;1130=c:\Projects\CD 5\1130 Past Project 1
1177=c:\Projects\CD 4\1177 Past Project 2
1180=c:\Projects\CD 3\1180 Past Project 3
;1191=C:\Projects\CD 3\1191 Past Project 4
1193=C:\Projects\CD 5\1193 Past Project 5
1204=C:\Projects\CD 5\1204 Past Project 6
1202=C:\Projects\CD 5\1202 Past Project 7
______________________________________

Explanation:

Obviously 1206 is my current project. It resides in the path
c:\Projects\CD 5\. The \CD 5\ folder is for back-up purposes. Once
folder CD 5 gets too full (this week?) I'll add another CD folder to
Projects.

Commonly used paths go in the included Path File 'Standard.ipj', listed
and described below.

Whenever possible I re-use existing components from similar projects. I
consider having the same file in two locations to be bad practice, so
any related paths are listed under Local Search Paths. If, as it turns
out, I no longer need one of these paths, hide it using the ;, but I
leave it in the ipj just in case I change my mind.

______________________________________
[Project Defaults]
MultiUser=FALSE
UseRelative=FALSE

[Included Path File]

[Local Search Paths]
TemplatePath=c:\Library\Inventor\R6 Templates
SteelPath=c:\Library\Inventor\R6 Templates\Steel
iTest=C:\Library\iTest
iFastener=C:\Library\iFastener
iParts=C:\Library\iParts
______________________________________

I don't really need any of the paths in Standard.ipj to function.

However, my templates need occasional tweaking, I'm always adding sizes
of steel (I know, I should be using Steel Creator) to my SteelPath and
Inventor will be long gone before I've finished creating iParts and
iFasteners. iTest is where I crash & burn with my iPart development
until the files are ready for prime time.

For the aforementioned reasons, I like to keep these paths handy.

Richard


Sean Dotson wrote:
> I tried this a few years ago but the user base was much smaller and I'm not
> sure very many people understood projects back then. Well the user base and
> software has grown a lot since then so let's try again....
>
> I hear from a lot of users that the main thing missing form most project
> documentation is real life examples. We've all shared parts of our project
> structure at one time or another but I'd like to ask everyone to post (or
> email me) their project files with a brief description of what you do (e.g.
> custom one-of-0a-kind machines or 1000 variations of the same widget) and
> why you structured the project the way you did.
>
> For example:
>
> ______________________________________
> [Project Defaults]
> MultiUser=None
> UseRelative=TRUE
> ThirdParty=FALSE
> v=0
>
> [Included Path File]
>
> [Workgroup Search Paths]
> Assy=.\Workgroup\Assembly
> Details=.\Workgroup\Details
> Parts=.\Workgroup\Parts
> Purchase=.\Workgroup\Purchase
> PDF=.\Workgroup\PDF
> AutoCAD2D=.\Workgroup\AutoCad2D
> RefData=.\Workgroup\Ref Data
>
> [Library Search Paths]
> Iparts=i:\iparts6
> _Iparts=.\Workgroup\iPartChildren
>
> This is my project files structure used for my custom one-up machines. I
> break down the Workgroup paths as I like to have one touch access to the
> folders from the hyperlinked pane on the left. I divide files by file type
> with further subdividing part files into custom machined parts and purchased
> parts. The RefData folder is where I keep linked spreadsheets, decals and
> other linked objects. I keep ipart children on a project specific basis as
> I feel it makes the project more portable.
> __________________________________________
>
> That's it. I wanted to collect them all the put them together in a document
> so that new users (heck even experienced users) could take a look and maybe
> gain some insight as to how people structure their projects. If someone
> builds similar designs to that of your they could pick up some suggestions
> on how to structure their projects.
>
> For those of you who don't know you can view your project (.ipj) files in
> notepad and then cut and paste into here or an email. Feel free to change
> the project names or fold names if you want to protect your designs'
> privacy.
>
> Thanks,
> --
> Sean Dotson, PE
> http://www.sdotson.com
> Check the Inventor FAQ for most common questions
> http://www.sdotson.com/faq.html
> -----------------------------------------
>
>
Distinguished Contributor
rllthomas
Posts: 2,068
Registered: ‎12-10-2003
Message 5 of 8 (59 Views)

Re: Request for Project Files

12-11-2002 12:18 AM in reply to: *Dotson, Sean
We do things a little bit differently. We have assemblies between 50 and thousands of pieces. In the past we would have up to 8 people working on a single project but these days and the state of the Telecom industry we only have 8 designers stateside so we pretty much go at it alone on our projects. Each project has a directory on a network drive which we set as our workspace. We then have a library in another location of non-proprietary components (connectors, iPart fasteners and PEMs etc). Only iParts go in a library path though (because of the _ to specify member locations), all our other library parts are listed as a workgroup search path. We have 1 file for everyone that lists these and is used as in included project file for the main one that is specific to each project. Why not use library search paths? Because the users were too frustrated with the assembly wanting to be resolved everytime a file was created then moved to the library later. Why not create them in the library? Because I might model and try to fit 10 connectors before I ever find one that really fits. I don't want all 10 in the library because they aren't all going to be assigned one of our part numbers and have an item master put up on them. So our project file has the main directory as the workspace, and included file for library stuff that is really a workgroup search path. Then to top it all off every directory under our workspace is specified as a local search path. Yes I know everybody says that is not necessary but I have proven many times that some presentation files won't load properly unless we do that. Finally if I reference files from some other project I put that directory in as a local search path - Rich Thomas
*Gwin, Hal
Message 6 of 8 (59 Views)

Re: Request for Project Files

12-11-2002 12:25 AM in reply to: *Dotson, Sean
Can we e-mail to you direct to save space and bandwidth on the newsgroup?

--
Hal Gwin
Mechanical Designer
Xenogen
*Dotson, Sean
Message 7 of 8 (59 Views)

Re:

12-11-2002 12:54 AM in reply to: *Dotson, Sean
Certainly...

--
Sean Dotson, PE
http://www.sdotson.com
Check the Inventor FAQ for most common questions
http://www.sdotson.com/faq.html
-----------------------------------------
"Hal Gwin" wrote in message
news:4736ACE6BFA4B8EF354BE0DB3853DD33@in.WebX.maYIadrTaRb...
> Can we e-mail to you direct to save space and bandwidth on the newsgroup?
>
> --
> Hal Gwin
> Mechanical Designer
> Xenogen
>
>
*Carr, Jimmy
Message 8 of 8 (59 Views)

Re: Request for Project Files

12-11-2002 10:37 AM in reply to: *Dotson, Sean
Screamer here :smileyhappy:
Hey, your workflow is a LOT like mine. Just taking a look helps some. Let
me think through this a bit and I will try to offer up a similar scenario
that gives me problems from time to time. Dennis' rewrite is also good. I
always set up .ipjs, but without exception, before the project is completed
I have resolution problems. I end up with such a mix of file types I'm
trying to track, and to top it off I usually have to pass it off to the
other engineer for completion and she has her own way of seeing the world.
We end up with a lot of folders for organizing the project and sometimes an
assembly or part might be saved outside of this sub. Lots of times it comes
down to the resolution of a file that is staring IV in the face and it won't
open.

Thanks for taking another stab at this Sean.

"Sean Dotson" wrote in message
news:28C11E6985AAE962E86A1DD4ACE1552C@in.WebX.maYIadrTaRb...
> I tried this a few years ago but the user base was much smaller and I'm
not

> sure very many people understood projects back then. Well the user base
and
> software has grown a lot since then so let's try again....
>
> I hear from a lot of users that the main thing missing form most project
> documentation is real life examples. We've all shared parts of our
project
> structure at one time or another but I'd like to ask everyone to post (or
> email me) their project files with a brief description of what you do
(e.g.
> custom one-of-0a-kind machines or 1000 variations of the same widget) and
> why you structured the project the way you did.
>
> For example:
>
> ______________________________________
> [Project Defaults]
> MultiUser=None
> UseRelative=TRUE
> ThirdParty=FALSE
> v=0
>
> [Included Path File]
>
> [Workgroup Search Paths]
> Assy=.\Workgroup\Assembly
> Details=.\Workgroup\Details
> Parts=.\Workgroup\Parts
> Purchase=.\Workgroup\Purchase
> PDF=.\Workgroup\PDF
> AutoCAD2D=.\Workgroup\AutoCad2D
> RefData=.\Workgroup\Ref Data
>
> [Library Search Paths]
> Iparts=i:\iparts6
> _Iparts=.\Workgroup\iPartChildren
>
> This is my project files structure used for my custom one-up machines. I
> break down the Workgroup paths as I like to have one touch access to the
> folders from the hyperlinked pane on the left. I divide files by file
type
> with further subdividing part files into custom machined parts and
purchased
> parts. The RefData folder is where I keep linked spreadsheets, decals and
> other linked objects. I keep ipart children on a project specific basis
as
> I feel it makes the project more portable.
> __________________________________________
>
> That's it. I wanted to collect them all the put them together in a
document
> so that new users (heck even experienced users) could take a look and
maybe
> gain some insight as to how people structure their projects. If someone
> builds similar designs to that of your they could pick up some suggestions
> on how to structure their projects.
>
> For those of you who don't know you can view your project (.ipj) files in
> notepad and then cut and paste into here or an email. Feel free to change
> the project names or fold names if you want to protect your designs'
> privacy.
>
> Thanks,
> --
> Sean Dotson, PE
> http://www.sdotson.com
> Check the Inventor FAQ for most common questions
> http://www.sdotson.com/faq.html
> -----------------------------------------
>
>
Post to the Community

Have questions about Autodesk products? Ask the community.

New Post
Need installation help?

Start with some of our most frequented solutions or visit the Installation and Licensing Forum to get help installing your software.