Sales Planning Workbook

January 03, 2007

Emtex Software Inc.

901 Yamato Rd Suite 120
Boca Raton, FL 33431
(561) 241-7229

Intentionally left blank

Table of Contents

Instructions
Mainframe
Print Jobs
Operations
Printers
Network Infrastructure
Server Software
Server Hardware
Support

I
II
III
IV
V
VI
VII
VIII
IX

Instructions

Complete the questions listed on the following pages in as much detail as possible. Use space provided to
insert all answers, comments, and explanations. The document was constructed using text wrapping
tables in order to preserve section pagination so enter as much information as necessary. Some sections
contain charts to enter data, feel free to insert or delete rows as required.
Once the questionnaire has been completed attach the following documents and return to the address
below.
Graphical Floor Plan of Print Room
o Printer locations
o Inserter locations
o Power drops with voltage and amperage, existing and planned
o Network drops, existing and planned
o Operator consoles , existing and planned
Network Diagram
o Topology
o Routing equipment
o Switching equipment
o IP implementation with addresses and netmasks
Mailing Address
Emtex Software Inc.
Attn: Kevin Tondreau
901 Yamato Rd Suite 120
Boca Raton, FL 33431

Email Address
mailto:ktondreau@emtexusa.com
OR

Mainframe
Is there a Mainframe? JES2/JES3
Is TCP/IP running on the customers system?
Does the customer have a system or LPAR
set aside for testing?
Does the customer have a mainframe
administration/operation?
(Software installation, updates)
Does the customer use: PSF, XPAF, MVS
Download, etc.?
Does the customer employ channel
extension? If so, please describe.
Special Instructions/Notes:
None.

II

Print Jobs
What is the daily average number of jobs
printed?
What is the typical retention time of jobs in
the print queue?
Describe how jobs are divided among PDLs.
(percentage per PDL) (AFP, Xerox,
Postscript, PDF and PCL)
Are any jobs delivered by a means other
than JES? (LPR, FTP, etc.) If so, how and
what type of hosts?
As new jobs are created what PDL will be
used?
Does the customer print live checks? If so,
is their a security mechanism?
Can sample data files be sent for testing?
Resources
How many resource libraries does the
customer use currently?
How often are resources updated?
How are updated resources transferred to
print devices?
Can the customer provide an archive of all
resources to Emtex? If so, what mediums
are available?
Does the customer have source code for
compiled objects such as Form Definitions,
Page Definitions, Job Description Libraries,
Overlays, Page Segments, Forms, Images, or
Logos?
Special Instructions/Notes:
None.

III

Operations
What is the current process operators use
to manage there work?
Does the customer utilize accounting
information? If so, what are the uses?
Special Instructions/Notes:
None.

IV

Printers
What are the types and quantities of printers the customer has installed currently?
Specify Printer ID, Controller, PDL, Connectivity, and Features/Options. (add rows as
necessary)
Printer ID

Controller

PDL

Connectivity

Features/Options

Does the customer have plans to add,

upgrade, or replace any printers in the next
90 days?
If additions, upgrades, or replacements are planned, please Specify Printer ID, Controller,
PDL, Connectivity, and Features/Options. (add rows as necessary)
Printer ID

Controller

Special Instructions/Notes:
None.

PDL

Connectivity

Features/Options

Network Infrastructure
Is the customers network infrastructure
built upon Ethernet?
Is the infrastructure capable of Gigabit
connectivity?
Is the infrastructure capable of integrating
additional subnets for data input, consoles
and control, and print data?
Does the customer have specialized
network security concerns? (elaborate in
detail)
Special Instructions/Notes:
None.

VI

Server Software
Sun Solaris, Oracle, Veritas Volume Manager,
and Windows XP / 2003 will be installed on
various components within Emtexs
solution, does this present any issues for
the customer?
Special Instructions/Notes:
None.

VII

Server Hardware
Does the customer want to supply the
required hardware
(Emtex will provide a detailed specification)
Can a rack mounted solution be deployed;
does the customer have adequate space for
an additional rack? Would the customer
like the equipment installed in existing
racks?
(19 standard 4 post)
Due to channel and/or SCSI connectivity,
Intel PC/Server hardware is traditionally
installed in close proximity to the attached
print device. Does this present any issues
for the customer?
(Specifically, OPSBD and VIP)
Redundant and Test Systems
Does the customer wish to purchase a test
system? (HW cost only, SW license free)
Does the customer wish to purchase a spare
print driver? (OPSBD or VIP)
Special Instructions/Notes:
All specifications for hardware devices will be supplied upon acceptance of final proposal.

VIII

Support (General)
Will Emtex support be allowed VPN or dialin access?

IX

Training
What is the customers practice surrounding
the training of their employees? (vendor
trained or train the trainer)
How many operators will require training?
How many administrators will require
training?
How many shifts will require training?
What are the experience levels of the
customers prospective operators and
administrators?
Special Instructions/Notes:
None.

FSE Schematic Explanation

Assumptions
Assumptions were made as follows:
Data Types: AFP, LCDS/Metacode, PS, and PCL data are required output to target print devices.
Data Delivery: Mainframe TCP/IP connectivity was assumed as well as similar connectivity to a UNIX data set submitter.
Output Data Types: Assumed at the conceptual level that all devices would be enabled to print their native PDLs (IPDS, LCDS/Metacode, PS,
and PCL) and output PDF for Filenet Viewing.
Control, Accounting, and Resources (CAR): The design implements decentralized device and job control while promoting centralized
accounting and resource management.
Explanation
With these assumptions in mind, the FlexServer Enterprise implementation, illustrated in the diagrams above, utilizes the following components.
o FlexServer Enterprise resides on a Sun Solaris platform configured for Cold Fail-Over with redundant modular components.
FlexServer (as illustrated) receives data via Unix host (jopsdt) and via direct socket connection from JES3 host via Emtexs JES2/JES3
Stripper. During the queuing process FlexServer checks the incoming datastream for required resources and places the job on Resource
Hold if any are missing. If the required resources are present, conditional processing occurs based on predefined Mapping Rules then
the job is submitted to the FlexServer Queue. Jobs may be automatically (Automatic Work Selection AWS) or manually distributed to
specific PDL capable devices within the enterprise.
o JES Stripper: Delivers data sets from the mainframe JES spool to FlexServer for processing, queuing, and printing.
o om_lpr/om_doc: Enables the printing of PS/PCL data sets to PS and PCL capable devices using the industry standard LPR protocol.
This has been enhanced in om_doc to retrieve jobs status, via SNMP, from Xerox Docutech devices.
o OPSBD 1 - 5: Provides a transfer medium for LCDS/Metacode datastream over TCP/IP to channel attached LCDS/Metacode native
devices.
o VIP 1 2: Integrates with FlexServer via a robust API and enables the transformation of AFP/LCDS/PS/PCL data sets and streams to
PDF. VIP also incorporates the technology, VDD2IPDS to drive both cut sheet and continuous form print devices.
o Console: The FlexServer Graphical User Interface (GUI) may be distributed throughout the enterprise allowing decentralized device and
job control.

Reference
Xerox DP 180 Printers.
LCDS and Metacode data are passed directly from FlexServer via OPSBD providing centralized resource
management and accounting. PS data is passed directly from FlexServer.
FlexServer Required
Modules:
om_xerox (w/ OPSBD)
om_lpr/om_doc

Delivers LCDS/Metacode datastreams to native Xerox Printers. Connects directly to EPS/Common

Controllers or via OPSBD for channel attached controllers.
Permits transfer of PS/PCL data to control units capable of receiving lpr (protocol) input. om_doc enhances
this delivery method by monitoring status and accounting from Xerox NPS Controllers via SNMP.

Required VIP Modules:

None

IBM IP4000 Printers.

Any delivered datastream will be transformed to IPDS by driving VIP server. FlexServer still provides
centralized resource management and accounting.
FlexServer Required
Modules:
om_emtex
Required VIP Modules:
AFP2VDD, XRX2VDD, PS2VDD,
PCL2VDD
VDD2IPDS

Delivers LCDS/Metacode/AFP/PS/PCL datastreams to to VIP for transform to IPDS

Input components that transform native PDLs to Emtexs proprietary virtual format.
Output component that transforms Emtexs proprietary virtual format to IPDS and drives the print device.
IPDS device connectivity may be established via Ethernet, 370 Channel, or SCSI (WD).

Oce PageStream Printers.

Any delivered datastream will be transformed to IPDS by driving VIP server. FlexServer still provides
centralized resource management and accounting.
FlexServer Required
Modules:
om_emtex
Required VIP Modules:
AFP2VDD, XRX2VDD, PS2VDD,
PCL2VDD
VDD2IPDS

Delivers LCDS/Metacode/AFP/PS/PCL datastreams to to VIP for transform to IPDS

Input components that transform native PDLs to Emtexs proprietary virtual format.
Output component that transforms Emtexs proprietary virtual format to IPDS and drives the print device.
IPDS device connectivity may be established via Ethernet, 370 Channel, or SCSI (WD).

Xerox DT6135 Printers.

PS/PCL data is passed directly from FlexServer
FlexServer Required
Modules:
om_lpr/om_doc
Required VIP Modules:
None

Permits transfer of PS/PCL data to control units capable of receiving lpr (protocol) input. om_doc enhances
this delivery method by monitoring status and accounting from Xerox NPS Controllers via SNMP.

4635MX Printers.
LCDS and Metacode data are passed directly from FlexServer via OPSBD providing centralized resource
management and accounting. PS data is passed directly from FlexServer.
FlexServer Required
Modules:
om_xerox (w/ OPSBD)
om_lpr/om_doc

Delivers LCDS/Metacode datastreams to native Xerox Printers. Connects directly to EPS/Common

Controllers or via OPSBD for channel attached controllers.
Permits transfer of PS/PCL data to control units capable of receiving lpr (protocol) input. om_doc enhances
this delivery method by monitoring status and accounting from Xerox NPS Controllers via SNMP.

Required VIP Modules:

None

DP92c Printers.
PS/PCL data is passed directly from FlexServer
FlexServer Required
Modules:
om_lpr/om_doc
Required VIP Modules:
None

Permits transfer of PS/PCL data to control units capable of receiving lpr (protocol) input. om_doc enhances
this delivery method by monitoring status and accounting from Xerox NPS Controllers via SNMP.

FlexServer Enterprise Components

Features:
Central Resource Storage --RAID Array(in-rack)
Multiple Ethernet Adapters
Required
Components:
Enterprise QM
om_xerox (w/ OPSBD)

Delivers LCDS/Metacode datastreams to native Xerox Printers. Connects directly to EPS/Common Controllers or
via OPSBD for channel attached controllers.

om_lpr/om_doc

Permits transfer of PS/PCL data to control units capable of receiving lpr (protocol) input. om_doc enhances this
delivery method by monitoring status and accounting from Xerox NPS Controllers via SNMP.

om_peer

Allows communication between multiple FlexServers in either a peer to peer or client\server configuration.

om_emtex
jopsdt

Command line utility used to submit data of any type to the FlexServer queue. Allows submitter to specify an
existing configuration file or create at submission on the command line. Java technology allows the component to
be executed on any platform/OS.

FlexTrack

A FlexServer Snap-In that bar-codes the unique job identifier to each jobs header and trailer pages. These
barcodes may be read or scanned at various stations providing job status information to the accounting database.
FlexTrack works on a job basis not mail piece.

FlexAlert

A FlexServer Snap-In that monitors a predetermined set of events and issues alerts via email, etc. once these
events have or have not occurred.

Sun Hardware:

Sun Fire V880 Server, 4 1200-MHz UltraSPARC III Cu Processors w/ 8-MB External Cache Each, 8-GB Memory, 6
73-GB 10000 RPM FC-AL Disks, DVD-ROM, 3 1500-Watt Power Supplies & Redundant Cooling Fan Trays, Solaris 8
Operating System
StorEdge 3310, Storage Array w/12 146GB Disks -1.75TB
Maintenance:
Sun Gold Maintenance 24X7 2 hour response

VIP Possible Configuration.

Features:
PDL transformation to PDF
Multiple Ethernet Adapters
Required
Components:
Core Executive
AFP2VDD

Converts AFP datastreams to Emtexs proprietary virtual format.

XRX2VDD

Converts LCDS/Metacode datastreams to Emtexs proprietary virtual format.

PS2VDD

Converts PS datastreams to Emtexs proprietary virtual format.

PCL2VDD

Converts PCL datastreams to Emtexs proprietary virtual format.

VDD2PDF

Converts Emtexs proprietary virtual format print files to IPDS and drives IPDS attached print device. Supports
Channel, SCSI (UW), and Ethernet device connectivity.

Dell Hardware:
Dell Precision 360; 2.66GHz/533 FSB,P4 Dell Precision 360 Mini-Tower 512K Full Speed Cache; 1GB,333MHz,Double Data Rate
SDRAM; 80GB Hard Drive, IDE (ATA-100); 48X/32X/48X CDRW; nVidia Quadro NVS 280, 64MB, dual VGA, Graphics Card; Dell
E172FP,Flat Panel,17 Inch Viewable Image
Maintenance:
Type 2 Contract - Same Day 4-Hour 7x24 Parts and Labor On-Site Response

Glossary
AFP2VDD

Converts AFP datastreams to Emtexs proprietary virtual format.

Console

A Graphical User Interface (GUI) distributed over a TCP/IP network enabling decentralized device and job control.

FlexTrack

A FlexServer Snap-In that bar-codes the unique job identifier to each jobs header and trailer pages. These
barcodes may be read or scanned at various stations providing job status information to the accounting database.
FlexTrack works on a job basis not mail piece.

FlexAlert

A FlexServer Snap-In that monitors a predetermined set of events and issues alerts via email, etc. once these
events have or have not occurred.
MVS/OS390/zOS host base data set transmission utility. Installs on main frame OS as a Functional Subsystem
(FSS) and delivers JES Spool print files to FlexServer.
Command line utility used to submit data of any type to the FlexServer queue. Allows submitter to specify an
existing configuration file or create at submission on the command line. Java technology allows the component to
be executed on any platform/OS.

JES2/JES3 Stripper
jopsdt

om_xerox (w/
OPSBD)

Delivers LCDS/Metacode datastreams to native Xerox Printers. Connects directly to EPS/Common Controllers or
via OPSBD for channel attached controllers.

om_lpr/om_doc

Permits transfer of PS/PCL data to control units capable of receiving lpr (protocol) input. om_doc enhances this
delivery method by monitoring status and accounting from Xerox NPS Controllers via SNMP.

om_peer

Allows communication between multiple FlexServers in either a peer to peer or client\server configuration.

om_emtex

Delivers AFP/LCDS/Metacode/PS/PCL data streams from FlexServer to VIP for transform to IPDS

PCL2VDD

Converts PCL datastreams to Emtexs proprietary virtual format.

PS2VDD

Converts PS datastreams to Emtexs proprietary virtual format.

XRX2VDD

Converts LCDS/Metacode datastreams to Emtexs proprietary virtual format.

VDD2IPDS

Converts Emtexs proprietary virtual format print files to IPDS and drives IPDS attached print device. Supports
Channel, SCSI (UW), and Ethernet device connectivity.