Insight implementation - all at once or piecemeal???

[KENAT]

Apologies for a rather general question but from peoples experience which is the better way to approach an Insight Implementation, all at once dumping in all (relevant) existing data or piecemeal, just new projects/products initially and old projects/products as they come to be worked on.

We have about 30000 – 35000 files, in a fairly poor state, to put into insight. An implementation was started almost a year ago but stalled on the amount of effort required to tidy up the data before putting it into Insight. In fact while this wasn’t the only issue the person in charge of the implementation has since resigned!

It would appear that a colleague and I are being given the task to complete the implementation.

From what we know we’re inclined to think a properly managed all at once approach will be more beneficial. However, our line managers believe that the Vice Presidents will balk at the likely cost and think a piecemeal approach would be more likely to be approved.

Any insight on this (excuse the pun) would be appreciated.

Appologies if this is the wrong forum but I didn't see Insight listed separately.

Thanks,

Ken

 

[BillMcReynolds]

Ken, we are in a similar position. We clearly need to implement a document management solution - probably Insight, but don't have the resources to get it done. We are a small engineering group (3 seats) and don't have anyone to assign to this that I think would be able to successfully swing it. I attended an Insight Implementation seminar last September and they emphasized the importance of having organized assemblies as being critical to the succes of Insight implementation. Unfortunately, we aren't there. I think the only way we are likely to make Insight work is to pay someone to help clean up our CAD info and help us organize Insight.

I have talked to people from Expert NetCAD and a couple of VAR's, but I don't really have any idea how good a job they would do.

 

[swertel]

Bill, where are you located? I may be able to help or reference someone in your part of the globe.

Ken, piecemeal is the only way, but sadly a very difficult way for Insight.

The first step, as Bill states, is to clean up your CAD data. (The biggest misconception of PDM or document management systems is that they'll solve you document control problems. If you SOPs are not up to date, the system will only automatic your problems or not work at all.) Once your CAD data is clean, and Insight Connect has plenty of tools to do that, then upload a pilot project into Insight. This project has to be completely self contained because files managed by Insight cannot have links to files outside of Insight. Choose a pilot project that has no shared files with another product line. Doing it this way gives you a chance to actually work in Insight without jeopardizing your entire organization and keeps you from having to duplicate efforts in and out of Insight.

Good luck. You can reach me privately through my website

http://www.wertel.eng.pro

if you need some more help not worth sharing in these public forums.

--Scott

For some pleasure reading, try FAQ731-376

 

[KENAT]

Unfortunately most of our products are not 'self contained' and cannot easily be made that way. Most are evolutionary developments of earlier designs and share a lot of components, also we have a 'common hardware' file which pretty much everything draws on.

We've done one pilot project on Insight (I say we, I had nothing to do with it) but it was about the smallest simplest thing we make and it was brand new, I don't think it used components from previous systems.

Our company doesn't have real, enforced SOPs (yes I know chicken before the egg/horse before the cart) so no real help there, we are trying to implement some but it's not easy. Also the implementation has already been started & insight setup, we're just trying to finish it off and actually get the data in there. I don't know how much if any scope we have for changing its basic set up.

Because of the issue of shared files we're thinking the best think is to spend a few months outside of insight tidying up the existing data (using the tools available which I'm being led to believe aren't as powerful/useful as sometimes made out) and then putting it into Insight all at once.

By tidying up data I mean determining what actually needs to go into insight (I'm pretty sure we can lose some of the 35000 files); renaming files (both because of the character limits & our lack of common naming scheme until recently); address duplicated names ; fixing broken links and anything I've forgotten.

Before tidying up we'd have at least some procedures/requirements in place & enforced so it isn't a repeating circle and all new data is insight ready from the start.

Now does it make more sense to do it 'all at once'.

 

[swertel]

Sounds to me that 'all at once' is your only option.

The good thing about Insight, it really helps clean up your data. If you turn all the error checking on that prevents you from uploading data that isn't "fixed" then only the good data that is completely correct will be inserted into Insight. Everything that remains is deletable. Even if you decide not to continue using Insight, at least your data got cleaned out and you can download everyting out of Insight and back into WinFS.

--Scott

For some pleasure reading, try FAQ731-376

 

[KENAT]

Swertel

Thanks for the response, it kind of backs up what I was thinking.

Bill good luck, hope your implementation goes more smoothly than ours.

Ken

 

[KENAT]

Well,

Turns out I needn't have worried. The decision has been made for us that it is to be done piecemeal.

Whether it's actually possible or not doesn't seem a concern.

Anyone know where I can get fairy dust or a genie in a lamp.

Seriously though if anyone has any suggestions on how we might manage having most existing work outside of Insight but new stuff in that would be great. We have a few ideas but they all seem to involve upsetting at least one other department!

Ken