ODIN Logo Pilot Project Report -- Conclusions

UW ODIN project Table of Contents Previous Page Next Page

Conclusions

Most imaging systems involve proprietary software which must be maintained on all the client machines, and many require proprietary networking protocols. ODIN uses the web to get around this maintenance problem. Since all the participants in the pilot already had a web browser connected to the campus network, ODIN did not add any new requirements for client hardware, software, or networking. Over the past two years, the explosion in the web and the increasing awareness of the total costs of desktop support have confirmed the strategic choice to use the web.

Imaging systems tend to be expensive, and they are very difficult to cost-justify for small departments. Based on the measurable costs and benefits outlined above, ODIN was a sound investment which will show a positive return within 4 years. The substantial improvement in customer service and job satisfaction make it even more valuable.

Moreover, ODIN is generic enough to be expanded to many more departments for the marginal cost of adding new image servers and making small modifications.

Maintenance and expansion are not free, however. There are already over a dozen requested enhancements, and these will add to the cost. New departments may require additional changes. Each potential site should consider their potential costs and benefits before making a decision.

UW ODIN project Table of Contents Previous Page Next Page


© 1997, University of Washington, All Rights Reserved
Open Document Image Network (ODIN)
odin@cac.washington.edu
Modified: October 17, 1997