Imaging Opportunities Report |
Purpose
This report is intended to facilitate discussions about if, when and how Computing & Communications should provide and centrally support a document image storage and retrieval system for the administrative offices of the University of Washington.
Background
Over the past five years, several departments have considered imaging applications. Some have launched substantial projects to define requirements, calculate costs and benefits, and meet with vendors. Most of these projects have stalled at one point or another, frequently due to the expense of commercially available imaging systems. None of the organizations within the scope of this report have demonstrated a favorable financial return on investment for a departmental imaging system. Some believe imaging is justified based on broader criteria, but they have not acquired or installed solutions yet.
In Fall, 1994, the Student Loan Office was prepared to purchase an imaging system. The chosen application was a proprietary LAN-based product, which did not fit in well with the University’s technical vision. In the interest of ending up with the best overall solution, the Student Loan Office delayed their project while Computing & Communications considered alternatives that could meet departmental requirements for imaging within the long-term technical direction of the University.
Key elements of that direction include:
In order to determine whether or not such a system could be justified, it was necessary to inventory the potential applications of such a system and to estimate the costs. This report is the result of that analysis.
Methodology
In cooperation with Records Management, a series of questions was assembled to evaluate the applicability of imaging to any given set of files. Interviews were held with people familiar with each of the major record series maintained by administrative departments. A screening process identified which files are good candidates for centrally administered imaging and which are not. Combined with additional departmental objectives and constraints, the list put into a recommended implementation order.
Scope
This report addresses the imaging requirements of administrative offices on the upper campus which would normally be supported by Computing & Communications. Included are most of the offices in Business and Finance and Student Affairs. Excluded are the medical centers, academic departments and self-sustaining units. Scope was further restricted to consideration of systems which have broad applicability as opposed to highly specialized application software, such as Resumix. There are certainly opportunities in these other areas which could provide additional benefits.
Candidate Applications
Top Candidates
Record Series Name |
Remarks |
Order |
Benefit |
Ready |
Student Loan Records |
The analysis is already done and the department is eager to start. Files are used by multiple offices with both X terminals and PCs. Files are active for many years but are not archival. |
1 |
A |
1 |
Direct Student Loans |
The analysis is already done and the department is eager to start. Files are used by multiple offices with both X terminals and PCs. Files are active for many years but are not archival. |
2 |
A |
1 |
Pending Grant Files |
Files are source for other record series. Combination of electronic documents and paper documents. All related files should be converted as one project. |
3 |
B |
2 |
Awarded Grant Files (Grant and Contract Services) |
Comes from Pending Grant File. Nearly identical to file stored by Grant and Contract Accounting. Information used by multiple offices. Combination of electronic and paper documents. |
4 |
A |
2 |
Grant and Contract Award File (Grant and Contract Accounting) |
Comes from Pending Grant File. Nearly identical to file stored by Grant and Contract Services. Information used by multiple offices. Combination of electronic and paper documents. |
5 |
A |
2 |
Denied Grant File |
Comes from Pending Grant File. Combination of electronic and paper documents. |
6 |
B |
2 |
Invoices |
Largest potential benefit based on volume and users from different offices. Significant impact on work flow must be addressed, as well as massive storage requirements. |
7 |
A |
2 |
Undergraduate Admissions |
Used by many people. Some documents should be migrated to electronic forms. Could be integrated with financial aid and other student files. |
8 |
B |
2 |
Financial Aid Records |
Used by many people. Some documents should be migrated to electronic forms. Could be integrated with admissions and other student files. |
9 |
B |
2 |
Payroll Records |
Could be integrated with Personnel, Benefits, and other employee files. Confidentiality and work flow issues must be resolved. Some forms could become electronic. |
10 |
B |
2 |
Personnel Records |
Could be integrated with Payroll, Benefits, and other employee files. Confidentiality and work flow issues must be resolved. Some forms could become electronic. |
11 |
B |
2 |
Benefits Folders |
Could be integrated with Personnel, Payroll, and other employee files. Confidentiality and work flow issues must be resolved. Some forms could become electronic. |
12 |
B |
2 |
News Clippings |
Distributed to multiple departments. Desire OCR and full text searching. Copyright issues need to be addressed. Should obtain electronic source for most documents. |
13 |
B |
2 |
Graduate School Admissions |
Must incorporate electronic transcripts from nationwide project called "Speed." Could be used widely in the distributed admissions process. Files become graduate student files on admission. |
14 |
B |
2 |
Graduate Student Files |
Files come from graduate admissions files. Could be used by departments. |
15 |
B |
2 |
Scholarship Files |
Currently keep two copies of files sorted differently for convenience. |
16 |
B |
2 |
Capital Projects Files |
Massive volume and large document sizes must be addressed. Copies are held in multiple offices for convenience. |
17 |
B |
3 |
Purchasing Records |
The requisitions should all be stored electronically and only the attachments should be imaged. The system must tie them together for convenient access. |
18 |
B |
3 |
Secondary Candidates
Record Series Name |
Explanation |
Order |
Benefit |
Ready |
Transcripts |
Infrequent access, and becoming more infrequent as records get older. Department is prepared to pay service bureau to scan onto CD-ROM for convenience. |
20 |
C |
1 |
Positive Time Report |
Should become electronic once the authorization issues can be resolved. |
20 |
C |
2 |
Canceled Checks |
Very rare access since all the information is available on-line. |
20 |
C |
2 |
Exception Time Reports |
Should become electronic once the authorization issues can be resolved. |
20 |
C |
2 |
Liability - Auto and General Files |
Small group of users, small number of highly confidential files. |
20 |
C |
3 |
Police Case Files |
Highly confidential files, strong departmental bias against central systems, copies are kept by Seattle police. |
20 |
C |
3 |
Worker's Compensation |
Small number of users, small number of highly confidential files. |
20 |
C |
3 |
Liability - Professional Claims |
Small number of users, small number of highly confidential files with variable retention. |
20 |
C |
3 |
Endowment Files |
Small number of archival files with potentially broad reference value. May be more appropriate for UWIN or other distribution mechanism in addition to retaining paper copies. |
20 |
C |
3 |
Poor Candidates
Record Series Name |
Explanation |
Order |
Benefit |
Ready |
Equipment Information Card |
Should continue to migrate to electronic form. |
99 |
E |
|
Property Activity Request (1024) |
Should be migrated to electronic form. |
99 |
E |
|
Long Distance Bills |
Should obtain software to prepare end-user documents from electronic data and should stop storing paper or microfiche copies of end-user documents. |
99 |
E |
|
Centrex Bills |
Should obtain software to prepare end-user documents from electronic data and should stop storing paper or microfiche copies of end-user documents. |
99 |
E |
|
Cost Transfer Invoices |
Should continue migration to electronic form. |
99 |
E |
|
ISD's |
Should continue migration to electronic form. |
99 |
E |
|
Journal Vouchers |
Should be migrated to electronic form. |
99 |
E |
|
Cash Transmittals |
Should be migrated to electronic form. |
99 |
E |
|
Grant and Contract Financials |
Should be eliminated by making information available on-line. |
99 |
E |
|
Certification Reports |
Should be eliminated by making information available on-line. |
99 |
E |
|
Travel Expense Vouchers |
Should be migrated to electronic form. |
99 |
E |
|
A/R Invoices |
Should be eliminated by making information available on-line. |
99 |
E |
Architecture
A generic electronic document storage and retrieval system will meet the business needs of most of the candidate departments. The only high-level requirements are to scan, index, store, search for, display and print business documents. The architecture presented here is designed to meet those requirements within the technical environment of the University.
This architecture is modular, so that any piece of it may be replaced without impacting the overall system. If a new browser becomes available, it can be used without affecting the storage, indexing, or searching modules. If the indexing database is changed, the software used for scanning and displaying images will not be affected. And if the volume of data for a given site justifies an optical jukebox, only the image server would need to be changed.
By keeping the index server separate from the image server, document searches can be very fast. It also makes it possible to use common tables in the indexing of different record series. For example, a single employee table storing name, employee number, and social security number could be used to validate entries into the benefits, personnel, and payroll image files. All three keys could be used to search for a document even though only one key was entered when the document was stored.
Scanning
Each department will do their own scanning using an appropriately sized scanner for their application. Off-the-shelf scanning software will be used to capture the images and store them in an industry standard format on a network host. Custom-developed routines will be used to index and store the images. The indexing can be done separately from the scanning, allowing greater flexibility.
Storage
Images will be stored on httpd servers and the index will be stored separately in a database that can be searched using Willow. All required storage software is already in use at the UW.
Retrieval
Users can search the database based on pre-defined keys using Willow. They can bring up descriptive fields and thumbnails to help them identify which document they want. Then they can select a document for retrieval, which is passed to either Mosaic or Netscape on their computer for display. All required retrieval software is already either in use or in development at the UW.
Costs for Top Two Sites (Six Record Series)
Item |
Cost Basis |
Student Loans |
Grants & Contracts |
First Year Total |
|
1 |
Image Server Host |
$5000 per host |
$5,000 |
$5,000 |
$10,000 |
2 |
Image Server Disk |
$3000 per 9 gigabytes |
$9,000 |
$15,000 |
$24,000 |
3 |
Scanner |
$5000 for fast scanner |
$5,000 |
$5,000 |
$10,000 |
4 |
Scanning Station |
$3000 for HW and SW |
$3,000 |
$3,000 |
$6,000 |
5 |
Backup Tape Drive |
$2000 per 8mm drive |
$4,000 |
$6,000 |
$10,000 |
Total Hardware and Purchased Software: |
$26,000 |
$34,000 |
$60,000 |
||
6 |
Development Time |
$4000 per month |
$12,000 |
$4,000 |
$16,000 |
7 |
First Year Support |
$4000 per month |
$36,000 |
||
Total Projected First Year Costs: |
$112,000 |
Benefits
It is extremely difficult to accurately predict the benefits of an imaging system. Each of the departments that have evaluated imaging have developed their own estimates of benefits as part of their reports. Excerpts from Payables and Accounting Operations and Student Loan Office reports are included as appendices. Those estimates do not include some of the key benefits, such as the real value of increased office space and decreased legal exposure due to lost documents.
One crucial benefit of implementing imaging technology centrally in the near future is the decreased risk of multiple departments implementing multiple different and incompatible imaging systems on their own. Over half of the top candidates, and a good number of the other candidates, have already seriously evaluated imaging technologies. At least three offices (Student Loans, Purchasing and Accounts Payable, and the Registrar) have already met with vendors. Many more have spoken with vendors and reviewed vendor literature. One is considering purchasing a CD-WORM drive to experiment and another plans to contract with a service bureau before the end of the current biennium. Furthermore, industry trends indicate that imaging will continue to grow and spread in coming years.
If Computing & Communications does nothing with imaging, it is easy to imagine ten incompatible departmental imaging systems in place on campus within five years. By that time, some of the vendors may already be out of business, some of the proprietary applications may no longer be supported, and C&C will not have the skills to maintain these systems.
On the other hand, if C&C provides strategic direction and support for departmental imaging requirements ahead of time, then most departments will wait for the centrally supported solution. Five years from now, the University will have imaging systems aligned with the technical vision and skilled resources to maintain them.
© 1995-1997, University of Washington, All Rights Reserved