[333] in Enterprise Print Delivery Team
DOST's Printing System Requirements
daemon@ATHENA.MIT.EDU (David F Lambert)
Tue Jun 27 16:23:46 2000
Message-Id: <10006272024.AA08345@MIT.EDU>
Date: Tue, 27 Jun 00 16:22:13 EDT
From: David F Lambert <LAMBERT@MITVMA.MIT.Edu>
To: Enterprise Printing Delivery Project Team <printdel@MIT.EDU>
Rocklyn,
You asked about our (DOST) reqs at a recent meeting. Here's what
we identified and is included in the Business Analysis Report (BAR)...
-Dave
o Electronic forms (overlay forms)
- tool for creating & maintaining electronic forms
- in house forms design and maintenance support
- in house "broker" for significant forms design work &
document management services
- forms control and authorization (both electronic & preprinted)
o Post processing services
- separate
- shrinkwrap or staple
- burst & decollate
- deliver
o User authentication
o Robust queue management (cancel, reorder queue, redefine copies,
flush (kill active file), drain (stop printer after current
file), hold (delays printing of a file), delete a queued
file, reroute file to different destination printer); distributed
queue management to authorized & authenticated users
o Chargeback/cost allocation mechanism
o Usage audit trails (for tracking lost output, etc.)
o Robust printer management
- restart
- backspacing
- start on page 'n'
- forwardspacing
- ability to query printer status
o Printing "features"
- file "jogging" (offset output files)
- support for duplex & multiple logical pages on a physical page
- support for color & highlight printing if required
o Support for MICR printing
o Special handling procedures & processes for confidential output
o Ability to verify & use valid delivery addresses
o Automatic print routing based on delivery address, file size,
time of day, required form, etc. (equivalent to VM's ROUTER)
o Archive/retrieval for reprint capabilities
o Provisions for business continuity (disaster recovery printing)
o Support for network attached printers
o Support for impact printers
o Header & trailer pages for centralized print including unique job
number, username, delivery address, file size, cost, etc.
o Appropriate operational documentation
o Appropriate end-user documentation
o Accepts print files via multiple paths including offline tapes
o Must support Postscript
