attachment

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v = "urn:schemas-microsoft-com:vml" xmlns:o = "urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word" xmlns:st1 = "urn:schemas-microsoft-com:office:smarttags"><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>MFD Alerts Spec Update Available</TITLE> <META content="MSHTML 6.00.2900.2873" name=GENERATOR><o:SmartTagType name="PostalCode" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType name="State" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType name="City" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType name="place" namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType> <STYLE>@font-face { font-family: Wingdings; } @font-face { font-family: MS Mincho; } @font-face { font-family: Tahoma; } @font-face { font-family: Arial Narrow; } @font-face { font-family: @MS Mincho; } @page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman" } A:link { COLOR: blue; TEXT-DECORATION: underline } SPAN.MsoHyperlink { COLOR: blue; TEXT-DECORATION: underline } A:visited { COLOR: blue; TEXT-DECORATION: underline } SPAN.MsoHyperlinkFollowed { COLOR: blue; TEXT-DECORATION: underline } P { FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto } SPAN.EmailStyle18 { COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply } DIV.Section1 { page: Section1 } OL { MARGIN-BOTTOM: 0in } UL { MARGIN-BOTTOM: 0in } </STYLE> </HEAD> <BODY lang=EN-US vLink=blue link=blue> <DIV>This is part 2 of the Xerox proposal to be discussed at the meeting on Thursday.</DIV> <DIV> </DIV> <DIV class=OutlookMessageHeader dir=ltr align=left>-----Original Message----- From: Silver, Thomas [mailto:Thomas.Silver@xerox.com] Sent: Wednesday, June 14, 2006 6:21 AM To: Bergman, Ron Subject: RE: PMP> MFD Alerts Spec Update Available </DIV> <DIV class=Section1> Hi Ron,<o:p></o:p> Sorry for the delay. Enclosed below are some comments related to section 11 MFP Faults Analysis (Informative) that I promised to send to you during our last phone conference:<o:p></o:p> <![if !supportLists]>(1)     <![endif]>Section 11.1.1 � need to add a new enum called ‘subunitInternalCommunicationFailure(39)’ as suggested within my previous proposal<o:p></o:p> <![if !supportLists]>(2)     <![endif]>Section 11.1.3 � need to add a new enum called either ‘scannerLocked(?)’ or ‘subunitLocked(?)’ to account for a locking fault for scan carriages<o:p></o:p> <![if !supportLists]>(3)     <![endif]>Section 11.1.3 � need to add the already defined ‘subunitTimingFailure(37)’ enum<o:p></o:p> <![if !supportLists]>(4)     <![endif]>Section 11.2.1 � need to add the already defined ‘subunitMemoryExhausted(34)’ enum<o:p></o:p> <![if !supportLists]>(5)     <![endif]>Section 11.2.1 � need to add a new enum called ‘subunitInternalCommunicationFailure(39)’ as suggested within my previous proposal<o:p></o:p> <![if !supportLists]>(6)     <![endif]>Section 11.2.3 � need to add a new enum called ‘noDialTone(?)’ or something similar to account for phone line-related faults<o:p></o:p> <![if !supportLists]>(7)     <![endif]>Section 11.2.4 � need to add a new enum called ‘noDialTone(?)’ or something similar to account for phone line-related faults<o:p></o:p> <![if !supportLists]>(8)     <![endif]>Section 11.2.4 � need to add a new enum called ‘scanError(?)’ or something similar to account for scanner-related failures during an outbound FAX job<o:p></o:p> Regards,<o:p></o:p> Tom J<o:p></o:p> <o:p> </o:p> <DIV>                                                                                                                 Systems, Solutions, & Device Compliance Engineering Mgr. Global Technology & Offering Development Xerox Global Services 800 <st1:City w:st="on">Phillips</st1:City> Road, <st1:State w:st="on">MS</st1:State> 111-02J, <st1:place w:st="on"><st1:City w:st="on">Webster</st1:City>, <st1:State w:st="on">NY</st1:State> <st1:PostalCode w:st="on">14580</st1:PostalCode></st1:place> Column K10, Office 7712 thomas.silver@xerox.com 8*222-7219 / 585-422-7219 <o:p></o:p>  <o:p></o:p> "This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient(s) please contact the sender by reply e-mail and destroy all copies of the original message.  Thank you."<o:p></o:p></DIV> <DIV> <DIV class=MsoNormal style="TEXT-ALIGN: center" align=center> <HR tabIndex=-1 align=center width="100%" SIZE=2> </DIV> From: pmp-owner@pwg.org [mailto:pmp-owner@pwg.org] On Behalf Of Bergman, Ron Sent: Tuesday, June 13, 2006 6:39 PM To: pmp@pwg.org Subject: PMP> MFD Alerts Spec Update Available<o:p></o:p></DIV> <o:p> </o:p> The MFD Alert Groups Specification has been updated per the comments from the 2006/6/8 teleconference.  The document can be found at:<o:p></o:p>         <A href="ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-mfp-alert-groups10-20060612.pdf">ftp://ftp.pwg.org/pub/pwg/pmp/wd/wd-mfp-alert-groups10-20060612.pdf</A> <o:p></o:p> The only item missing is the addition of the Requirements section.  I will have a proposal for this part available early next week for review in the PWG face-to-face meeting on June 15.  A phone bridge will be available for those who are unable to attend.<o:p></o:p>         Ron Bergman         PWG MIBS Chairman <o:p></o:p></DIV></BODY></HTML>