User's Manual

Appendix A:

Optimize BFM performance

You can improve your experience with your Nuvera system by customizing the BFM’s behavior to meet

your needs and by using some relatively simple strategies to improve the quality of your output and the

overall productivity of the system. The techniques presented here should provide you with:

- improved stacking quality with better in-set registration of each sheet

- improved productivity through reduced interruption due to jamming and intermittent stacker

unloading

- improved operability by customizing stacker unloading to meet your needs

A tabular summary of the strategies is provided at the end of this document. You can refer to that as a

quick reference but taking the time to read the detailed explanations and getting a thorough

understanding of the BFM’s capabilities can provide tremendous benefit in optimizing the performance.

The following topics are covered:

• Operational summary of the Stacker

• Controlling the stack height limit

• Managing paper curl

• Use of the variable shaped tray

• Use of the bin limit setting

• Use of the scuffer

• Disabling buffering

Compiling and Stacking principles of operation

In the BFM, the act of collecting sheets of a set is referred to as compilation and the area those are

collected in is referred to as the compiler. The compiler physically can only collect the equivalent of 100

sheets of 20 lb paper. The limit compiled sheets is determined automatically based on the paper

properties. When stapling, the bin limit is equal to size of the stapled set. The BFM will collect sheets in

the compiler up to the lesser of the bin limit or size of a set and then will drop that collection set onto the

stack below.

There is an array of 3 optical sensors that are used to determine if a successful drop has occurred. At

the occurrence of a set drop, the set drop sensor array is checked. When curl is present in sheets and

building up as a stack accumulates, typically one or two of the set drop fault sensors become blocked

before all three become blocked. As each set drop occurs, the set drop array is checked and if only one

or two of the sensors are blocked, the system completes the next chunk/set that is currently in progress

(it had already started before the drop completed) and then schedules an orderly unload of the stacker at

the next chunk/set boundary. In those cases, the operator simply needs to unload the stacker, discard

nothing, and the system resumes. In dual BFM systems, the job will automatically switch to the other

available empty stacker and continue with no impact to productivity. If at the time of the drop, all sensors

are blocked, a 12-2505 set drop fault is declared. In this case the operator will need to unload the stacker

and then open the top transport clamshell and remove and discard any sheets in the compiler and any

compiled collections that remained hung up during the set drop operation. The set which failed to drop

will not be remade, only sheets left in the compiler or transports will be remade.