Communications for companies and people at home across the world have improved because of email.  It is in no way streamlined since there are numerous software packages, and service providers in existance.  Company and educational institutions sometimes transition into new systems in hopes of streamlining and simplifing usage.  George Mason University is a example of a large group which was on multiple platforms, and their plan for moving to one universal email package.

George Mason University had numerous offerings for its different audiences.  To the students they offered access to a VAX systems, as well as UNIX systems.  On both of these platforms there were email applications such as:  mail, elm, and pine.  For faculty and staff they had othering offerings such as NOVELL groupwise, Microsoft exchange accounts for departments with Microsoft NT servers, and desktop software applications like Eudora for individuals without those accounts.  These were not the only email applications in use as individuals would have other software preferences.

The use of multiple email clients creates concern in terms to the accessibility, storage, translations/protocols, and the quality of support.  The support staff, field technitions, server administrators, and email administrators were having a very difficult time.  There was the dispersement of budgetary funds for maintainence, upgrades, and licensing.  In addition was the time and communication which had occur to troubleshoot where the problems where with users, and between systems.  Mulitple groups provided training on the different email systems, but students and faculty alike were having to learn multiple applications and had to have accounts on various systems.

The University created a task force which would assess the needs of the university, and test out numerous email packages.  After looking at the needs of the academic environment, five package were chosen for testing.  Volunteers and people on the task force would play with Groupwise, Exchange, Pine, Netscape, and a fifth package.  They would narrow down the choices based on user friendliness, and what the software "bells and whistles" were.  The next step would be to look at the hardware requirements and cost, and licensing.  This would be done by the department who would be purchasing the equipment and software, and supporting it.

The decision was made in favor of Netscape.  One of the reason was the ability to offer a web version, which means a website which would allow people to access their email from any system connected to the world wide web.  This would be the main form of access which students would be encouraged to use.  In addition Netscape messanger can also be setup to connect to the mail server, and copy down the account information and mail.  This option would be encouraged amoung the faculty and staff who have desktop systems assigned to them.  Another selling point on the Netscape package was the fact that they offered a Calendar option.  The calendar they offer can be made available to all other persons on the system, and allow them to view another persons itinerary and schedule meetings with them.  It would simplify the scheduling of meetings, or sharing of information.

With the decision on the package made, UCIS would then work with Netscape representatives on purchasing equipment and getting installed.  A new Memo Task Force would meet to discuss testing, concerns, rollout, and timelines.  This would go on while the technitions would be setting up the system, and creating preliminary accounts for volunteer testers.  Documentation was written and rewritten, as well as announcements to the community that this was coming.  Meeting were held with technical coordinators from each department.  Trainings were developed and tested.  These steps continue to be revised.

The migration has not been completed yet.  There new students, as well as a number of departments have been converted.  Problems are still being discovered, documented, and discussed.  A few solutions have been found, but a lot of the larger problems will have to wait until software upgrades are available, or till more of the community has been moved over to the new system and trained.