Title: Selecting an Enterprise Output Management System
1Selecting an Enterprise Output Management System
- for Xplor Chicagoland Chapter
Richard Huff September 16, 2005
2Agenda
- Madison Advisors Background
- EOMS Background
- EOMS Selection Strategy
- EOMS Selection Criteria
- Questions
3Madison Advisors Background
- Specialization in the enterprise output market
print and electronic communications - Assist organizations with selection and
evaluation decisions - Ongoing research across a variety of markets
- Objective expertise we do NOT sell hardware,
software, or integration services
4Madison Advisors Research
- Publish 2-3 Market Studies per year
- Objectively assess technology segments of
interest to our customers - Recent Market Studies
- Transactional EOMS August 2005
- Document Composition Tools December 2005
5Enterprise Output Management Systems
- EOMS Definition
- EOMS Segments
- EOMS Vendors
6EOMS Definition
- Centrally manage and control print and electronic
output from multiple sources to multiple
destinations
7EOMS Segments
- Manage batch and ad-hoc transaction-driven output
on production printers - Manage static or variable documents on production
printers - Manage desktop-created documents on office
printers
8Transactional EOMS Vendors
- ASG-Cypress
- Emtex
- Esker Software
- IBM
- Levi, Ray, Shoup
- Macro 4
- Océ
- Solimar Systems
9EOMS Selection Strategy
- Develop enterprise output strategy first
- Prioritize requirements
- Research
- Assess both product and vendor
10Enterprise Output Strategy
- What is the future direction of output within the
organization? - What are your critical applications?
- What output channels are planned for in the near
future? - Are print volumes shifting to other channels?
11Prioritize Requirements
- Invite everyone to the table
- Objectively evaluate requirements
- Primary requirements are tied to business drivers
such as cost reduction or regulatory compliance - Secondary requirements identify required
functionality
12EOMS Selection Criteria
- Functionality
- Application Interfaces
- Architecture
- Vendor
13Functionality
- Input capabilities
- Transformations
- Print management
- Workflow capabilities
- Output capabilities
14Functionality Considerations
- Where is the data stream coming from?
- Does the data stream always match the printer
capabilities? - Do all the data streams follow the same workflow
process? - Is there a need to drive fax or web channels?
15Application Interfaces
- Administrator
- Operator
- Job submission
- Remote user
16Application Interface Considerations
- Is the product managed through a single interface
or multiple interfaces? - Is the print operator interface drag-and-drop?
- How easy is it to define job tickets?
17Architecture
- Platform support
- Packaged integration
- Application programming interfaces (APIs)
- Scalability
- Reliability
18Architectural Considerations
- Which operating systems are supported or
required? - How much of the product functionality is exposed
through the API? - How many printers can the product manage from one
server?
19Vendor
- Product stability
- Product support
- Product maintenance
- Financial stability
- Market share
- Market presence
20Vendor Considerations
- What is the product history?
- How is product support provided?
- How often is the product updated?
- Is the product core to the vendors business?
- Is the vendor investing in RD?
21Product Lifecycle
Application Interfaces
Functionality
Vendor Support
Architecture
Life Time of Product
22Questions?
PO Box 369 Colleyville, TX 76034 817.684.7545 www.
madison-advisors.com
richhuff_at_madison-advisors.com