[2337] in Enterprise Print Delivery Team
Re: Why IPM vs APS
daemon@ATHENA.MIT.EDU (Rocklyn E. Clarke)
Tue Feb 26 12:15:37 2002
Mime-Version: 1.0
Message-Id: <p05010400b8a1710f4da1@[18.152.2.129]>
In-Reply-To: <200202252253.RAA19114@fort-point-station.mit.edu>
Date: Tue, 26 Feb 2002 12:15:30 -0500
To: Enterprise Printing Delivery Project Team <printdel@MIT.EDU>
From: "Rocklyn E. Clarke" <rclarke@MIT.EDU>
Content-Type: multipart/alternative; boundary="============_-1197378759==_ma============"
--============_-1197378759==_ma============
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Hello,
I'm comfy with the list. I should point out some push back we might
get on a couple of the items however:
- User friendly interface for users
A user friendly interface for the LPRng function currently in use by
APS would probably not require any more effort than we put into the
web interface to IPM.
- Retention of printed files for reprints without resubmits
Although APS does not currently retain print jobs for reprinting,
LPRng can be configured fairly easily to provide that function in raw
form. We were exploiting that capability ourselves until a few
months ago while we learned to trust the hand off from LPRng to IPM.
These are still reasonable requirements, but one could argue that
they could have been satisfied without adding IPM to our solution.
The rest of the list however is pretty compelling in my opinion.
Rocklyn
--------
At 5:52 PM -0500 2/25/02, David F Lambert wrote:
>As soon as Rocklyn checks in on the list, please do add it to the project
>notebook. I just want to hear that Rocklyn's comfy with the current list.
>
>-Dave
>
>On Mon, 25 Feb 2002 16:59:02 -0500 MEB said:
>>Looks good to me. Shall I put it up in the project notebook- maybe
>>right on the top page?
>>
>>At 4:43 PM -0500 2/25/02, David F Lambert wrote:
>>>Hi Gang,
>>>
>>>Since we've heard some secondhand grumblings about IPM vs APS, I thought
>>>it might be useful to make a list and include it on our web pages as
>>>well as in our response to Susan. Here's what Lynne & I came up with.
>>>After adding any additional comments you may have, I'd like to put this
>>>in our project notebook and include it in the note I'm drafting in
>>>response to Susan. Your quick feedback would be greatly appreciated.
>>>
>>>-Dave
>>>
>>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>>
>>>The team has received secondhand information questioning the choice of
>>>Infoprint Manager over the existing Athena Print Services. Below
>>>is a list of requirements identified during the discovery effort
>>>which is satisfied by IPM and not believed to be available with APS.
>>>
>>>Please note that a shared central printing service has requirements which
>>>are not needed or are less useful in a distributed printing environment.
>>>
>>>- User friendly interface for users
>>>- User friendly interface for operators
>>>- Ability to manage IPDS printers as well as Postscript printers
>>> to reduce overall capital costs
>>>- Support for electronic overlay forms
>>>- Page size information for queued files for print scheduling purposes
>>>- Current page count for actively printing file
>>>- Ability to start a file on page 'n'
> >>- Retention of printed files for reprints without resubmits
> >>- Ability to obtain accurate and detailed printer status information
> >
--============_-1197378759==_ma============
Content-Type: text/html; charset="us-ascii"
<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { margin-top: 0 ; margin-bottom: 0 }
--></style><title>Re: Why IPM vs APS</title></head><body>
<div>Hello,</div>
<div><br></div>
<div>I'm comfy with the list. I should point out some push back
we might get on a couple of the items however:</div>
<div><br></div>
<div> - User friendly interface for users</div>
<div><br></div>
<blockquote>A user friendly interface for the LPRng function currently
in use by APS would probably not require any more effort than we put
into the web interface to IPM.</blockquote>
<blockquote><br></blockquote>
<div> </div>
<div> - Retention of printed files for reprints without
resubmits</div>
<div><br></div>
<blockquote>Although APS does not currently retain print jobs for
reprinting, LPRng can be configured fairly easily to provide that
function in raw form. We were exploiting that capability
ourselves until a few months ago while we learned to trust the hand
off from LPRng to IPM.</blockquote>
<blockquote><br></blockquote>
<div>These are still reasonable requirements, but one could argue that
they could have been satisfied without adding IPM to our solution.
The rest of the list however is pretty compelling in my opinion.</div>
<div><br></div>
<div>Rocklyn</div>
<div><br></div>
<div>--------</div>
<div>At 5:52 PM -0500 2/25/02, David F Lambert wrote:</div>
<blockquote type="cite" cite>As soon as Rocklyn checks in on the list,
please do add it to the project<br>
notebook. I just want to hear that Rocklyn's comfy with the
current list.<br>
<br>
-Dave<br>
<br>
On Mon, 25 Feb 2002 16:59:02 -0500 MEB said:<br>
>Looks good to me. Shall I put it up in the project notebook-
maybe<br>
>right on the top page?<br>
><br>
>At 4:43 PM -0500 2/25/02, David F Lambert wrote:<br>
>>Hi Gang,<br>
>><br>
>>Since we've heard some secondhand grumblings about IPM vs APS,
I thought<br>
>>it might be useful to make a list and include it on our web
pages as<br>
>>well as in our response to Susan. Here's what Lynne &
I came up with.<br>
>>After adding any additional comments you may have, I'd like to
put this<br>
>>in our project notebook and include it in the note I'm
drafting in<br>
>>response to Susan. Your quick feedback would be greatly
appreciated.<br>
>><br>
>>-Dave<br>
>><br>
>>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<span
></span>~~~~~~~~~~~~~~<br>
>><br>
>>The team has received secondhand information questioning the
choice of<br>
>>Infoprint Manager over the existing Athena Print Services.
Below<br>
>>is a list of requirements identified during the discovery
effort<br>
>>which is satisfied by IPM and not believed to be available
with APS.<br>
>><br>
>>Please note that a shared central printing service has
requirements which<br>
>>are not needed or are less useful in a distributed printing
environment.<br>
>><br>
>>- User friendly interface for users<br>
>>- User friendly interface for operators<br>
>>- Ability to manage IPDS printers as well as Postscript
printers<br>
>> to reduce overall capital costs<br>
>>- Support for electronic overlay forms<br>
>>- Page size information for queued files for print
scheduling purposes<br>
>>- Current page count for actively printing file<br>
>>- Ability to start a file on page 'n'</blockquote>
<blockquote type="cite" cite>>>- Retention of printed
files for reprints without resubmits</blockquote>
<blockquote type="cite" cite>>>- Ability to obtain
accurate and detailed printer status information</blockquote>
<blockquote type="cite" cite>></blockquote>
<div><br></div>
</body>
</html>
--============_-1197378759==_ma============--
