healthetech intranet

Company calendar. Note site-wide and topic-specific footer information (per responsible department), site search function, portal-style dynamic content, and flexible navigation. Site is Linux, Apache, MySQL, and PHP (LAMP). It runs on a dual processor Intel server with RAID 0 (mirroring).
Human resources information page.
Human resources forms page. The search for a particular document could be quite confusing, so the site search feature (htdig) was configured to search the contents of the PDF, Word, and Excel files, so that if you didn't know what a document's title was, you might still find it using the content within.
Humor and events page. Had a quote of the day feed, virtual bubble wrap (it was a HealtheTech thing to pop bubble wrap whenever we got a package that had it), and pictures from the frequent parties.
The suggestion form used a Perl (CGI) back end, and got mailed directly to Human Resources.
The first thing anyone ever did when they went to the main page for the IT department was to look for the trouble ticket system (since that's all they thought they were good for), so I went them one better by making that the content of the main page of the IT section and wrapping the content around it. This section contained links to all the things that IT personnel would find useful.
One of the printers had a web-based interface, which was helpful in troubleshooting problems. It became an easy matter for an IT person to pull up the monitor from its handy link on the intranet site, see if the toner or paper was getting low, identify a paper jam, and fix the problem.
This was a document request form handled by the QA department. Since all documents related to their medical device products had to follow certain procedures because of FDA regulations, document control was key. This form tied into a MySQL database, which kept a running total of all the requests and their status.
The Sales and Marketing department was in charge of logos, product brochures, and any collateral material related to the devices or software. Having these items readily available on the intranet cut down on email and phone requests for them.
They also kept version-specific information available about each of the products so that support of older products was still possible, and the marketing history of the pieces were not lost.