Need advice on network web analytic solution specs

considerations and recommendations?

[kilatzin]

I'm starting work on a memo describing a grand vision for a multiple website analytic solution that's accessible from different office locations across the country. Standard setup of two network servers: one for archiving weblogs, the other for the software. I know I'm describing a somewhat sketchy scenario, but what technical and marketing considerations do you feel should be accounted for in a "grand picture" document?

If a home-grown solution is not an option, what network commercial solutions would you recommend? Here's a little of what I know so far: Our IT department is only giving access to the weblogs, no cookies will be considered in this solution. Our servers are Windows iis, no apache. Archival space for weblogs is projected to house 1 years worth of data.

Any starting points you can point out would be greatly appreciated.

Thanx!

[cgrantski]

The missing part for me is --- what do you want to have in the analysis?

Unless it's something pretty simple, and unless you really know the ins and outs of sessionizing and so forth, I think your company would save a lot of money by getting a package. I hope I'm not insulting you by saying this might be more complicated than you want to take on.