After reviewing this Network World article, I realized that Hartford Hospital's work to keep the network 'clean' should set standards for other companies.

We have a 14,000+ node network spanning much of the Connecticut area.
Our network team is only eight people who are responsible for the Infrastructure, not Servers or Desktops. When I first started, we were migrating from FDDI to ATM, and our main 'Clinical ELAN' was 4500+ nodes. We run 350+ NetWare, Unix, and Windows Servers, with Windows Desktops. Our Broadcast rate before we rolled out Windows Domain Services for this large VLAN was under 100 broadcasts/second. After we rolled out the domain, we were hitting almost 300 Broadcasts per second.

A review of the Desktop configurations via captures revealed problems with both Server and workstation configurations. When our team was done analyzing the problem, we gave the solution to our Server/Desktop teams who used Novell's ZEN to drop our Broadcast rate to an average 40 frames/sec, with IPX still enabled. We now have a Multi-GIG Nortel backbone, and our largest user segment is approximately 1600 devices.

We are running NetWare in PureIP mode, so IPX is long gone. Our average Broadcast rate on our largest user segment is eight frames/second. Even printers get adjusted to these standards.

Applications: All applications go through our team for analysis. If we see unacceptable behavior, the application is NOT allowed to go on the network without the Vendor fixing the problem. If they do not fix their application, it is not allowed onto our network. By running this so clean, our desktops are still connected at 10-half, with Modalities and Workstations connected at 100-Full or GIG. All user ports are locked to the respective speed/duplex settings to prevent negotiation issues. All ports are disabled unless activated (With required paperwork), and port recoveries are conducted on a regular basis.

We monitor our network with Plixer's WebNM, which has IpSwitch's WhatsUp embedded in it. This is visible to the NOC, and the senior IS management has access to it. So, if someone says 'The Network is Down', we say 'Check WebNM'. It usually is an authentication server that is the culprit, and WebNM will show that server on its exception page.

While I appreciate Bernie Lubitz' article in spirit, I can't help but note how easy it is to use tools such as W&G's LinkView Classic to show Management the Broadcast rates in nice, pretty graphs, use WhatsUP to show what's down, various capture programs to analyze application, and basic MS skills such as turning off Computer Browser on all clients.
Using a Desktop support tool like ZEN helps make these changes globally, including at remote sites.

Throwing bandwidth at the problem is only masking it, not fixing it.
Some time and research can do wonders to cure the problem.