Scan services with SOAP
One group at Xerox had implemented a system to utilize SOAP technology to process scans from a Xerox WorkCentre to various web services, enabling almost unlimited possibilities. However, the UI was based on an implementation model, and the complexity of the product made it suitable only to the highly trained. Furthermore, it didn't integrate well into the other pre-existing services already well know on Xerox devices.
Legacy technology
Our existing Network Scanning service allowed a scan to be sent to a single server on the network for processing based on parameters sent with the job.
SOAP technology
The SOAP model allows multiple processing by one or many services that can be chained together and communicate to each other.
The implementation model
Without a specific user-centered design approach, engineers often resort to exposing the implementation to the user. In most cases, the implementation does not match the mental model a non-technical user has.
I set out to apply user-centered design principles to the service and make it usable for all office users. I recognized that the technology being used was a good choice for enabling new functionality both from Xerox and third parties.
The user-centered model
I proposed that the service be better integrated into key services, allowing new functionality to existing services.
Transforming Copy
Integrating the technology into our flagship Copy service, enabled a new Transform feature. This feature could send a copy off-box to a web or network service for processing then print the results like a normal copy.
For instance, you could walk up with a document in Japanese and make a copy in English.
Or, you could direct the copy to come out of a different machine on your network (perhaps to utilize different features like color capability from a black and white copier).
Mailbox/File cabinet
One useful capability of the SOAP enabled service allowed scans to be sent to folders or mailboxes on a machine and they were automatically processed by one or more services before reaching their final destination.
The UI allows simple settings to direct the workflow of the document moving from input attributes, transformations, advanced settings and to output destinations
Document attributes (to trigger different outcomes depending on the source or other attributes of the document)
Transformations (to process the document in some way such as translation or OCR)
Output settings (the final destinations of the document such as email to me, print, file at server…)
