Questionnaire for planning a new network

A customer would like to have a new network (encorporating several remote locations) - likely to be Windows based. I would like to present them with a questionnaire in order to capture all the necessary info required to plan and deploy the new design; things like current organisation design, geographical infrastructure, customer objectives, goals, timelines etc... I am looking for ideas, articles or URLs which will help me create this questionnaire.

Many thanks for your help.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hi omb,

Regards .. Alan
Sorry, Wrong question ...
QuickPost does it again!
SolarWinds® Network Configuration Manager (NCM)

SolarWinds® Network Configuration Manager brings structure and peace of mind to configuration management. Bulk config deployment, automatic backups, change detection, vulnerability assessments, and config change templates reduce the time needed for repetitive tasks.

There are several basic templates for network planning that I can think of.  

My concern is that you have "likely to be Windows based."  

Why is it likely, if you are going to do due diligence before making a recommendation?  Or are you going to bias your due-diligence legwork based on a perceived likelihood of a Windows-based network?

There are SO many other ways to plan a network besides the Microsoft way.  When you are talking about a WAN, you have to look at desired LAN-to-LAN functionality - file sharing, printer sharing, WAN link bandwidth, other applications that will span the WAN, whether or not web services or other thin-client technology will be applied and/or leveraged, security, reliability, uptime needs, etc.

If you are still interested in what I have to say after reading what I have said so far, let me know and I will give you guidelines that are essentially generic, meaning they are not based on the way Microsoft does things but rather on the way networking works in a well-designed heterogeneous environment.  

If all you are interested in is the Microsoft way, then say so, and I will unsubscribe to this question and let you do your own thing your own way with no further comment from me.
Mostly, plan for the following:

Number of Users (for licensing) win2k/2k3
Number of Devices (alternate licensing) win2k/2k3
Number of Workstations (for wiring/licensing) win2k/2k3
Number of Network Devices (Printers/Faxes) win2k/2k3
Type of Applications over network (eg do they use SQL server?  Does it need internet access?)
User density in physical workspace (to plan for network hardware, switches, cables, etc)

It is also very important to find out what applications they will be using on the server so the server can be properly built and configured for it (eg Web Servers dont need much actual harddrive space, but fast access times and good RAM are useful, while fileservers need bigger harddrives or RAID arrays and can have slower access times).
That is so Redmondian, to assume all of that Windows licensing should be the main part of a plan when the question is about how to devise a questionnaire including high-level things like corporate structure, geographical layout, objectives & goals, timelines, etc.
Ya sorry, I kinda answered that in a hurry.  But, you have to admit, Windows Servers will pretty much cover any corporate structure and geographical layout issues that arise.  And what are the other options?  Just Linux/Unix pretty much right?  Dont get me wrong, I like Linux myself, I use it at home, but when it comes to corporate networks, Windows is just easier to get going.  And it's pretty scalable as well.

As for objectives and goals, and timelines, those are pretty straightforward questions that should be negotiated individually (pretty much just ask them what the timeline is for this project).
Append: Oh, but I do recommend Linux/Unix Fileservers.  More stable, good security features, and they are definately not too hard to get going.
Just get you boss to learn Pine, tell him it's the best think since sliced bread.

do the name Netware ring a bell?
Pine.  Youch.  Had an admin who insisted on reading his mail in it.
Windows is easier to get going, but not cheaper to keep.  

In addition to NetWare, Macintosh, Linux and *nix (includes the various "flavors" like AIX and Solaris) there are mainframe systems based on the IBM OS/390 platform, and there are mid-size computers like the AS/400, which is a much more solid, stable and versatile server than Windows could ever hope to be.

It does NOT have to be a given that your network will all run on Windows.  Also, Windows in a WAN still sucks, even with the transitive-trust kludge on top of the old domain model they call Active Directory, because AD is not engineered for efficient use of WAN resources.  It's kinda like the Windows of directory services - rather than Windows making efficient use of the hardware, you are expected to beef up the hardware to meet the needs of the OS, and with AD, you are expected to beef up the bandwidth to meet the replication needs of the directory.
ombAuthor Commented:
Wow, thanks for all the feedback.

The customer currently has a windows network with Exchange servers, windows clients, MS Office etc... hence, my initial comment about why I thought their new network might be windows based...

ShineOn, but as you rightly say, I would like to do due diligence before making a recommendation, hence, I am very interested in the generic guidelines that you mention. We often install Linux boxes for customer's of ours that are more open-minded and not totally Microsoft orientated - unfortunately, some customers want nothing but Microsoft (shows their nativity) and would not consider any other network proposal. Personally, I am a fan of have heterogenous networks... using the best of each product...

Anyway, back to a network questionnaire... any other comments on creating a high-level network analysis/needs doc would be very welcome - thanks
Overview of how to use a needs questionnaire, with guidelines on how questions should be worded for optimum results: 
The same site has other needs analysis tools and helps
A high-level of what a consulting firm does in doing a needs analysis:
Things to consider regarding security, to add to the needs analysis:

Essentially, you want to formulate a needs analysis based on what you have already mentioned.  Include current technology status as part of the questionnaire.  You need to know physical layout of the WAN, what WAN technologies are available at each location, what the departmental structure is, what the org chart looks like, what the data flow is (for example, for a manufacturer, the flow of an order from sales through design, manufacturing and delivery, with all the points between - this must be tailored for the industry your customer participates in.  Specific corporate goals, specific departmental goals, a cross-section of a user "wish list", all that kind of stuff.  

The physical aspects - type of infrastructure, cost concerns, risk tolerance, existing infrastructure, desired results, access types, access speeds required, number and type of printers needed or desired and volume of print per printer per functional area.  Data synchronization.  Data accessibility.  Backup requirements.  Disaster recovery issues.  Power protection.  Physical security and data security wants/needs/desires/concerns.  Legal issues - HIPAA, Sarbanes-Oxley, data retention needs for IRS, for product liability, etc.

The list can get as long as you need it to.  To do due diligence you have to address everything you can possibly think of.  The first pass should be weeding out the stuff that you thought of that doesn't apply, and asking for input on additional topics of concern.  The second pass should be to determine how important each thing that still exists on your questionnaire is, to assign some type of weighting factor.  The third pass should be broken down by functional area, to cover the concerns of each department.  The fourth pass should be a consolidation of the results from the third pass, with only managers and executives reviewing and passing judgment on each item.

What you end up with after all of that is what you use to formulate your detailed proposal and executive summary.

Hope this helps.  Good luck.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Although, in Windows "defense," you wll have to include retraining and migratuon costs as factors, which tend to favor upgrade versus migrate.  However, if, say, there are no internal IT staff, and the overall scope of the change is large enough that upgrdae is about as complicated as migration, then it will matter less or not at all.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.