Scan Service Model and Requirements

Transcription

1 June 27, 2007 wd-mfdscan Working Draft The Printer Working Group Scan Service Model and Requirements Status: Interim Abstract: Network print devices have evolved to support additional multifunction services, in particular scan service. When network scan devices are installed in local office or enterprise networks, they need remote service, device, and job management capabilities so that administrators, operators, and end users can monitor their health and status. In addition, such network scan devices need remote job submission capabilities so that operators and end users can create scan jobs without depending entirely on local console interfaces. This document defines a semantic model and requirements for service, device, and job management and job submission for these network scan devices Copyright 2007, Printer Working Group. All rights reserved.

2 Copyright (C) 2007, The Printer Working Group. All rights reserved. This document may be copied and furnished to others, and derivative works that comment on, or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice, this paragraph and the title of the Document as referenced below are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Printer Working Group, a program of the IEEE-ISTO. Title: Scan Service Model and Requirements The IEEE-ISTO and the Printer Working Group DISCLAIM ANY AND ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED INCLUDING (WITHOUT LIMITATION) ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. The Printer Working Group, a program of the IEEE-ISTO, reserves the right to make changes to the document without further notice. The document may be updated, replaced or made obsolete by other documents at any time. The IEEE-ISTO and the Printer Working Group, a program of the IEEE-ISTO take no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. The IEEE-ISTO and the Printer Working Group, a program of the IEEE-ISTO invite any interested party to bring to its attention any copyrights, patents, or patent applications, or other proprietary rights, which may cover technology that may be required to implement the contents of this document. The IEEE-ISTO and its programs shall not be responsible for identifying patents for which a license may be required by a document and/or IEEE-ISTO Industry Group Standard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Inquiries may be submitted to the IEEE-ISTO by at: info@ieee-isto.org The Printer Working Group acknowledges that the IEEE-ISTO (acting itself or through its designees) is, and shall at all times, be the sole entity that may authorize the use of certification marks, trademarks, or other special designations to indicate compliance with these materials. Use of this document is wholly voluntary. The existence of this document does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to its scope. Copyright 2007, Printer Working Group. All rights reserved. Page 2 of 27

3 About the IEEE-ISTO The IEEE-ISTO is a not-for-profit corporation offering industry groups an innovative and flexible operational forum and support services. The IEEE Industry Standards and Technology Organization member organizations include printer manufacturers, print server developers, operating system providers, network operating systems providers, network connectivity vendors, and print management application developers. The IEEE-ISTO provides a forum not only to develop standards, but also to facilitate activities that support the implementation and acceptance of standards in the marketplace. The organization is affiliated with the IEEE ( and the IEEE Standards Association ( 73 For additional information regarding the IEEE-ISTO and its industry programs visit: About the Printer Working Group The Printer Working Group (or PWG) is a Program of the IEEE-ISTO. All references to the PWG in this document implicitly mean The Printer Working Group, a Program of the IEEE ISTO. The PWG is chartered to make printers and the applications and operating systems supporting them work together better. In order to meet this objective, the PWG will document the results of their work as open standards that define print related protocols, interfaces, data models, procedures and conventions. Printer manufacturers and vendors of printer related software would benefit from the interoperability provided by voluntary conformance to these standards. In general, a PWG standard is a specification that is stable, well understood, and is technically competent, has multiple, independent and interoperable implementations with substantial operational experience, and enjoys significant public support. Contact information: The Printer Working Group c/o The IEEE Industry Standards and Technology Organization 445 Hoes Lane Piscataway, NJ USA MFD Web Page: MFD Mailing List: mfd@pwg.org 95 Instructions for subscribing to the MFD mailing list can be found at the following link: Members of the PWG and interested parties are encouraged to join the PWG and MFD WG mailing lists in order to participate in discussions, clarifications and review of the WG product. Copyright 2007, Printer Working Group. All rights reserved. Page 3 of 27

4 Contents 1 Introduction Terminology Conformance Terminology Scan Service Terminology Requirements Rationale of the Requirements Out of Scope for Scan Service Use Cases Usage Scenario Descriptions...8 The following usage scenarios have been considered for support by the scan service model: Use Case UML Diagrams (Should we include these?) Design Requirements Scan Service Object Model Scan Job Ticket Life Cycle Scan Job Ticket Life Cycle Diagram Scan Job Ticket Life Cycle Description Scan Service Model Overview Scan Service Model Diagram Scan Service Model Description Scan Service Theory of Operation Scan Service Interfaces Basic Scan Service Operations Administrative Scan Service Operations Scan Job Template Manager Operations Conformance Requirements PWG and IANA Registration Considerations Internalization Considerations Security Considerations References Normative References Informative References Author s Address Change Log Copyright 2007, Printer Working Group. All rights reserved. Page 4 of 27

5 Figures Figure 1 Use Case 1 Diagram Figure 2 Use Case 2 Diagram Figure 3 Use Case 3 Diagram Figure 4 Use Case 4 Diagram Figure 5 Use Case 5 Diagram Figure 6 Use Case 6 Diagram Figure 7 Use Case 7 Diagram Figure 8 Use Case 8 Diagram Figure 9 Use Case 9 Diagram Figure 10 Use Case 10 Diagram Figure 11 Use Case 11 Diagram Figure 12 Use Case 12 Diagram Figure 13 Use Case 13 Diagram Figure 14 Use Case 14 Diagram Figure 15 Scan Job Ticket Lifecycle Diagram Copyright 2007, Printer Working Group. All rights reserved. Page 5 of 27

6 Introduction This document specifies the PWG abstract model of the scan service of a multifunction device (MFD). The model includes requirements and definitions of the data and functional architectural elements and the operation model for the usage of the scan service and device of a multifunction device (MFD) installed either in a local or enterprise network environment. The scan service semantic model supports both walk-up scan frommfd s front panel, and remote scan from a client PC or workstation without operating the front panel. The model also supports document on-ramp scanning for enterprise workflow applications that may store scanned images internally or to a remote server/repository. When shared by a workgroup using different functions of the MFD, the model supports interruption of a large scan job to perform a higher priority or small print job, or vice versa. For multi-document batch scanning, the model can support automated scanning of a stack of documents separated by a scan instruction sheet for each document. When necessary, the model can be extended to support security services that protects against unauthorized use of the scan service or access of scanned imaged data. This document focuses on the specification of job submission and job management abstract semantics for MFD scan service in network environment. Currently service, device, and job management and job submission protocols for these network MFDs are fragmented and proprietary. A standard for scan service, device, and job management and job submission for these network MFDs would benefit both the imaging industry and the user community Terminology This section defines terminology used throughout this document Conformance Terminology Capitalized terms, such as MUST, MUST NOT, REQUIRED, SHOULD, SHOULD NOT, MAY, RECOMMENDED and OPTIONAL, have special meaning relating to conformance as defined in RFC 2119 [RFC2119] Scan Service Terminology Scan Job Parameters The set of values the Scan Service inputs from the end user, each value is to realize a property or attribute of an instance of the Scan Job Template. Scan Job Ticket A data object that contains processing and description properties of a scan job such as source, destination, image processing, image format, and image compression parameters and settings. The content of a scan job ticket is configured by user through a scan client UI or created from a Scan Job Template. Scan Job Template A data object that contains pre-configured contents of a type of scan ticket. The template could be prepared by a system administrator for other end users or by an end user him/herself, and stored in the MFD or a remote system. Default Scan Job Template An instance of the Scan Job Template contains the default value of each property defined in the template. Scan Job A scan image acquisition object created and managed by the Scan Service that captures the images of document originals and output document data in an appropriate format for storing in the MFD, client PC, or a remote system. Copyright 2007, Printer Working Group. All rights reserved. Page 6 of 27

7 Scan Service The process of converting paper documents, photographic film, photographic paper or other Hard copy documents to digital images, then store them at a storage location. Scan Device A device that provides scan service. Document Repository A data storage area, in the MFD or an external system, where digital documents are stored. Mailbox A specific type of document repository resident in MFD that serves as a private document storage area for a specific user. Scan Document The document object that is managed by the Scan Service and contains the metadata and the scanned image data of the paper document being scanned. Document Data The imaging data in certain document or file format that is the final output of the Scan Service before being sent or stored in a document repository. Scan Intent The preferences of the end user for the processing and description properties of a scan job. Scan Client An application used by a person who walks up to the MFD with a scan intent, or invoked at a remote system used by an end user with his/her scan intent. [Others TBD] Requirements This section provides the basis for defining the semantic model and requirements of the scan service of a MFD. 3.1 Rationale of the Requirements Scan is the fundamental function next to printing in many compound services of a MFD such as a digital sending, coping, and faxing. Therefore it is essential to define the scan service model and requirements. 3.2 Out of Scope for Scan Service The basic scan service model defined in this document will be able to support many enterprise scan applications. However this document does not specify any application specific semantics. Hence the followings are out of scope for this document: 1) Semantics of any compound services, e.g. Scan-To- , Scan-To-Fax, or Scan-To-Print. 2) Semantics of any workflow protocol, i.e., sequencing and coordination of jobs across multiple services. 3) Semantics of any service management of job operations for MFDs that are not directly network connected. 4) Semantics of any new document formats to be implemented in network MFDs, i.e., alternatives to TIFF, JPEG, etc. Copyright 2007, Printer Working Group. All rights reserved. Page 7 of 27

8 Use Cases Usage Scenario Descriptions The following usage scenarios have been considered for support by the scan service model: Create Scan Job Template A user uses a template management application at PC or from MFD UI to create Scan Job Template(s) for himself or for other users, and store the template(s) in a repository (in MFD or a remote system). Copyright 2007, Printer Working Group. All rights reserved. Page 8 of 27

9 Copyright 2007, Printer Working Group. All rights reserved. Page 9 of 27

10 Figure 1 Use Case 1 Diagram Walk-Up Scan Pre-Created Scan Job Template A user walks up to a MFD, places his/her document on platen or ADF, selects a pre-created Scan Job Template from UI, then scans the document. Scanner User Place Document on Scanner Select Scan Job Template Scan Document Figure 2 Use Case 2 Diagram Walk-up Scan and Send Document to Storage - A user walks up to a MFD, places his/her original paper on the platen, enters his scan job ticket identification and then pushes the start button. The default job template is copied into a transient scan job template. The scan job template which was pre-created by an administrator (could be for a security reason) may then optionally be used to modify the transient job template which may be a copy of a default job template. When the user pushes the scan button, a scan job is created and bound to the scan job ticket, and the document on the platen is physically scanned. When scan document is complete, it is sent to a specified document repository (in MFD or a remote system). Copyright 2007, Printer Working Group. All rights reserved. Page 10 of 27

11 Figure 3 Use Case 3 Diagram Scan from PC and Store Document in Repository Same as but after the paper is placed on the MFD, the user control all scanning operations from his/her desktop PC using scan application. No start button needs to be pushed at the MFD. Copyright 2007, Printer Working Group. All rights reserved. Page 11 of 27

12 265 Scanner PC User Remote Document Repository Place document on scanner Default job template is copied into a transient scan job template. Run Scan Application This operation is optional. Modify transient san job template Select Scan Parameters Create Scan Job Scan Job Ticket is bound to the Scan Job. Start Scan Implicit Add Scan Document The scanner is instructed to scan the physical document. Close Scan Job: Cause scan job to be scheduled immediately. Document is scanned into image data and becomes Scan Job's Document. Set Scan Job Status to Complete. Query Scan Job completion status Send Scan Document Send Scan Job Completion Status. 266 Store Document: Send Scan Document to Remote Document Repository or Store Document in Scanner. 267 Figure 4 Use Case 4 Diagram 268 Copyright 2007, Printer Working Group. All rights reserved. Page 12 of 27

13 Scan Document to and Retrieve from an Internal Mailbox A user walks up to a MFD, scans a job. The job is stored in his/her MFD mailbox. The user then goes back to his/her PC to retrieve the scan job from the mailbox in the MFD. Scanner User PC Default job template is copied into a transient scan job template. This optional operation includes selection of a mailbox. Create Scan Job. Scan Job Ticket is bound to the Scan Job. Place document on scanner Modify Transient Scan Job Template (with mailbox selected) Push Start Button Add Scan Document: The scanner is instructed to scan the physical document. Close Scan Job: Cause the scan job to be scheduled immediately. Scan physical document(s). Document is scanned into image data and becomes Scan Job's document. Scan Job Documents are stored in Mailbox in Scanner. ISSUE: Is that part of the use case outside the scope of the Scan Service definition? Set Scan Job Status Run Scan Application to Complete. Query Scan Job Completion Status Select mailbox Get List of Scan Documents Select Document in mailbox Get Scan Document (mailboxid, DocmentID) Figure 5 Use Case 5 Diagram Walk-up Scan and Discover Storage - Copyright 2007, Printer Working Group. All rights reserved. Page 13 of 27

14 A user walks up to a MFD, places his/her original paper on the platen, and inputs his /her authentication information, and then selects scan-to-folder function. The scan service discovers a document repository and/or sub-folder that he/she has write permission, and show the repository list on the front panel. A user selects a repository or sub-folder and then pushes the start button. The scanner gets Scan Policy Template from the target repository, and scans the original document. When scan document is complete, it is sent to a specified document repository. Scanner User Remote Document Repository Place document on scanner Display the repository list on the front panel. Select ScanToFolder Discover a Document Repository Select Target Repository Query the Scan Policy Template Document is scanned into image data and becomes Scan Job's Document. Reply the Scan Policy Template Push start button Set Scan Job Status to Complete. Query Scan Job completion status Send Scan Document Send Scan Job Completion Status Figure 6 Use Case 6 Diagram Walk-Up Scan, with Pre-selected Scan Template and Policy Template Overwrite Copyright 2007, Printer Working Group. All rights reserved. Page 14 of 27

15 An accounting firm requires scanned images in specific document format, image resolution, and stored in specific remote repository. Pete as an employee of the accounting firm walks up to the MFD and selects the administratively pre-created Scan Job Template that matches the requirements. The template could be stored in the MFD or the external server/ repository. In some locations of the firm, employees are restricted to certain usage of the scan services. To avoid user s mistake in template or scanning feature selection, the scan service is instructed to automatically apply the Company s Scan Policy template to the User Preference template for creating the scan ticket of the job. When the user pushes the scan start button, a scan job is created by associating the scan job ticket with the scan image data. The scan job is then processed. He then goes back to his desk and has his scan job retrieved from the repository Figure 7 Use Case 7 Diagram Copyright 2007, Printer Working Group. All rights reserved. Page 15 of 27

16 Walk-Up Batch Scan A company needs to scan a stack of paper documents. To automate the process, a control sheet that contains instructions for each scan job is placed on the top of each document. The admin selects batched scan. The scan service automatically scans the control sheet of each document first and OCR the scanned control sheet to obtain and set the scanning parameters for the document. At this point, a scan job ticket for the document is created, filled with the scan settings obtained from the previously scanned control sheet image. A scan job is then created and associated with the scan ticket. The rest of the document sheets are then scanned according to the instructions on the control sheet. This process continues until all documents stacked on the paper-feed tray are scanned. Scanner Admin Remote Repository Place a stack of paper documents on Scanner Admin inserts a scan control sheet on top of each document before placing the stack of documents on Scanner. Select "Batch Scan" Step 1: Scan the control sheet of a document Scan Documents Step 2: Create Scan Job Ticket from the control sheet image data by OCR. Step 3: Creat Scan Job and Scan Document sheets. Step 1-4 are repeated in sequence until all document sheets are exhausted. Step 4: Store Scan Document Scan Document Complete Store Scan Document Figure 8 Use Case 8 Diagram Copyright 2007, Printer Working Group. All rights reserved. Page 16 of 27

17 Workflow On-Ramp Scanning Harry has a workflow on-ramp MFD that can identify a target workflow application. From the menu of MFD UI, he can simply select travel to scan receipts from travel into the company s Travel Expense Accounting workflow application, or select Health to scan medical receipts into Health Accounting workflow application Figure 9 Use Case 9 Diagram Copyright 2007, Printer Working Group. All rights reserved. Page 17 of 27

18 Finding Scan Job Storage Location A user had previously scanned an important document, but forgot where it s stored. He brings up the MFD UI and gets a list of scan destinations to locate his scan job, and then all detailed information on the job including where the job is stored. Scanner User Get List of Document Repositories Select Document Repository Search Scan Document (keywords) Select Scan Document (DocumentID) Display Scan Document Information Details (DocumentID) Figure 10 Use Case 10 Diagram Copyright 2007, Printer Working Group. All rights reserved. Page 18 of 27

19 Disable Scan Service for Copying Anne needs to copy a lot of documents. She disables the scan service until all documents are copied, then enables the scan service when she is done. MFD User Disable Scan Service Place Document on Platen (or ADF) Create Copy Job Ticket Create Copy Job by bound to its Copy Job Ticket, then scan document into image data and print the document. Copy Document Enable Scan Service Figure 11 Use Case 11 Diagram Interrupt a Scan Job for Printing or Copying Copyright 2007, Printer Working Group. All rights reserved. Page 19 of 27

20 Harry has a small document to copy or print when a large job is being scanned by the MFD. He interrupts the scan job, copies or prints his document, then resumes the large scan job. MFD Harry User Start a large scan job MFD is busy scanning a large scan job Interrupt Scan Job Place document on platen Create Cop Job Ticket by letting user to select copy paramenters or creat one from "default" ticket. Create Copy Job from bounded Copy Job Ticket and scan the document. Create Copy Job Ticket Copy Document Print copy document. Continue scanning the large scan job. Copy Document Complete Resume Scan Job Figure 12 Use Case 12 Diagram Scan Service Discovery via LDAP or DNS Copyright 2007, Printer Working Group. All rights reserved. Page 20 of 27

21 Bill wants to discover the Scan Services available in his enterprise network, so that he can choose one in the future when he wants to submit a Scan Job. Bill wants to discover Scan Services both statically (via enterprise directories) and dynamically (via discovery protocols). Bill can statically discover Scan Services via an LDAP query to his enterprise directory that searches for instances of an LDAP Scanner schema (which represents a Scan Service or a Scan Device), similar to the industry standard LDAP Printer schema (RFC 3712). Bill can dynamically discover Scan Services by a DNS query to his enterprise DNS server that searches for instances of a DNS SRV (RFC 2782) record for Scan Service (to be registered w/ IANA) Copyright 2007, Printer Working Group. All rights reserved. Page 21 of 27

22 Figure 13 Use Case 13 Diagram Scan Service Capability Discovery MFD with scan capabilities is setup on the network. MFD has been previously discovered and is known to the application software that will query the device for capabilities. Ira wants to learn if the scan service is capable of sending his document as a PDF file to his mailbox. He would also like to know if he can password encrypt the file to be sent. From the application on his PC, Ira is able to select scan options available knowing that these will be supported. User at PC MFD Scanner Query scan service / device for capabilites List of capabilities Figure 14 Use Case 14 Diagram Use Case UML Diagrams (Should we include these?) Design Requirements Copyright 2007, Printer Working Group. All rights reserved. Page 22 of 27

23 355 4 Scan Service Object Model Scan Job Ticket Life Cycle Scan Job Ticket Life Cycle Diagram 1 MFD Imaging System * 1 MFD Imaging Service MFD * Subunits Print Service Copy Service Fax Service Other Services «uses» has a Scan Intent Managed by Manages Scan Service has CreateScanJob «uses» Walk-Up User Scan Job Template Repository (internal or external) Scan Job 1 1 has Walk-Up Scan Client Interface Internal Template Repository External T. Repostory Stored in 0..1 Document Data 1 has Scan Document Converted from Stored in 1 has Scan Job Ticket Scan Defaults has 1 1 Default Scan Job Template «traces» Is a Reference to Scan Job Parameters Create/Select «bind» «refines» Scan Job Template Creates * Stored In/ Retrieved From * * * Stored In/ Retrieved 7 From * External D. R. Internal Doc. Repository Sets 1 has a Scan Intent Imaging Job Document Repository (internal or external) Any reference to a Scan Job Ticket is either an instance of Scan Job Ticket or a reference to a Scan Job Template. Remote Scan Client «uses» Remote User 360 Figure 15 Scan Job Ticket Lifecycle Diagram Copyright 2007, Printer Working Group. All rights reserved. Page 23 of 27

24 Scan Job Ticket Life Cycle Description The scan job ticket life cycle begins when a scan client initiates a scan job. A scan job is initiated after an end user placed the document originals on the platen or the ADF subunit and pressed either the physical scan button on the MFD front panel or the virtual scan button from a remote scan application. A scan job ticket is either a copy of or a reference to a scan job template. A scan job template is created in four possible ways: (1) A walk-up end user uses Walk-up Scan Client Interface to create a scan job template by configuring a set of preferred values for scan job processing and description properties/attributes in the scan ticket of future scan jobs, and store it as a uniquely identifiable template in a MFD internal repository or a remote external repository system. (2) Same as (1) but instead of a walk-up end user, an organization s administrator creates scan job templates. Each scan job template is uniquely identifiable. (3) Same as (1) but instead of walk-up to MFD, the end user uses a remote scan client (a PC or workstation) to create scan job templates. Each scan job template is uniquely identifiable. (4) Same as (3) but instead of a walk-up end user, an organization s administrator uses a remote scan client (a PC or workstation) to create scan job templates. Each scan job template is uniquely identifiable. If a scan request does not include or reference a scan job template, a scan job ticket is created from the default scan job template, which is one component in the scan defaults initialized by the scan service at the start up time. Otherwise, a scan job ticket is created from a selected scan job template by a walk-up end user at the local or remote scan client application. A selected scan job template can be modified by the end user settings of the scan parameters, or other organization s policy template. Once a scan job ticket is created, it is bound to the scan job of the user by the scan service. Then the scan service manages and processes the scan job according to what user has specified in the scan job ticket that also includes what file format of the scan document data should be and to where the document data should be sent, be it an internal document repository or an external document system. The scan job ticket lifecycle ends as soon as the document data is successfully sent to its destination. ISSUE: Shouldn t we include a receipt that can be queried to determine what actually happened when the job was processed 4.2 Scan Service Model Overview 4.3 Scan Service Model Diagram 4.4 Scan Service Model Description Scan Service Theory of Operation [TBD] Copyright 2007, Printer Working Group. All rights reserved. Page 24 of 27

25 Scan Service Interfaces Below is an initial list of operations for a Scan Service. 6.1 Basic Scan Service Operations CancelJob CloseScanJob CreateScanJob ListJobs GetScannerElements GetScanJobElements RetrieveScanDocument ValidateScanTicket 6.2 Administrative Scan Service Operations Activate Deactivate Disable Enable HoldJob HoldNewJobs Pause PauseAfterCurrentJob PromoteJob (ISSUE: Is there a queue of pending jobs and how are they associated with the input document) ReleaseJob ReleaseNewJobs ReprocessJob RestartJob Resume Shutdown Startup 6.3 Scan Job Template Manager Operations DeleteTemplate GetTemplate ListTemplates PutTemplate ReplaceTemplate SetTemplateAccessRights SetTemplateExpiration Conformance Requirements [TBD] Copyright 2007, Printer Working Group. All rights reserved. Page 25 of 27

26 PWG and IANA Registration Considerations [TBD] Internalization Considerations [TBD] Security Considerations [TBD] References [TBD] 11.1 Normative References [RFC2119] S. Bradner, Key words for use in RFCs to Indicate Requirement Levels, RFC 2119, March [RFC 3712] P. Fleming, I. McDonald, Lightweight Directory Access Protocol (LDAP): Schema for Printer Services, RFC 3712, February [RFC 2782] A. Gulbrandsen, P. Vixie, L. Esibov, A DNS RR for specifying the location of services (DNS SRV), RFC 2782, February [Others TBD] Informative References [TBD] 12 Author s Address Nancy Chen Solutions and Technology Oki Data 2000 Bishops Gate Blvd. Mt. Laurel, NJ Phone: Fax: nchen@okidata.com Copyright 2007, Printer Working Group. All rights reserved. Page 26 of 27

27 Peter Zehler Xerox Research Center Webster Voice: (585) FAX: (585) US Mail: Peter Zehler Xerox Corp. 800 Phillips Rd. M/S E Webster NY, Additional contributors: Harry Lewis IBM Ira McDonald High North Walter Filbrich - Samsung Glen Petrie Epson Kei Sando Oki Data Jerry Thrasher Lexmark Craig Whittle - Sharp 13 Change Log (To be removed in final version) 05/22/2007 PZ included Use Case diagrams Copyright 2007, Printer Working Group. All rights reserved. Page 27 of 27