Route Processing

• 1. Should automatic selection of same editions be skipped for publishing group when running bundle, manifest and stacker? B (Client) If using publishing groups and separate publishing runs by edition (Cutoff by Edition flagged in Publication setup), when selecting an edition for bundle tops, the truck manifest or the stacker interface, all of the other publishing runs for the same edition may or may not be auto-selected, based on this parameter.

  Value
  Yes	When selecting an edition for bundle tops, the truck manifest or the stacker interface, only the publishing run flagged will be selected.
  No	When selecting an edition for bundle tops, the truck manifest or the stacker interface, other publishing runs in the publishing group with the same edition (but different products, truck departures and truck sequences) will be auto-selected.

• 2. Which days should display on the draw history/estimated draw section of the daily draw worksheet? BCP (Client) This setting determines how the draw history/estimated draw section of the daily draw worksheet is displayed.

  Value
  Consecutive Days	Consecutive days are displayed.
  Same Weekday	The same weekday is displayed.

• 3. What is the print order for the daily draw worksheet? BCP (Client) The daily draw worksheet may be printed in either AAM column or district manager order.

  Value
  AAM column	If the daily draw worksheet should be printed in AAM column order.
  District	If the daily draw worksheet should be printed in district manager order.

• 4. How many days of previous draw history for the daily draw worksheet? BCP (Client) You may request from zero to six days of previous route draw history to be printed on the daily draw worksheet. A combined total of no more than six days of draw history (previous and/or future) may be printed.

  Value
  0	Do not print route draw history on the daily draw worksheet.
  1	Print one day of previous draw history on the daily draw worksheet.
  2	Print two days of previous draw history on the daily draw worksheet.
  3	Print three days of previous draw history on the daily draw worksheet.
  4	Print four days of previous draw history on the daily draw worksheet.
  5	Print five days of previous draw history on the daily draw worksheet.
  6	Print six days of previous draw history on the daily draw worksheet.

• 5. How many days of future draw estimates for the daily draw worksheet? BCP (Client) You may request from zero to six days of future route draw history to be printed on the daily draw worksheet. A combined total of no more than six days of draw history (previous and/or future) may be printed.

  Value
  0	Do not print route draw history on the daily draw worksheet.
  1	Print one day of future draw history on the daily draw worksheet.
  2	Print two days of future draw history on the daily draw worksheet.
  3	Print three days of future draw history on the daily draw worksheet.
  4	Print four days of future draw history on the daily draw worksheet.
  5	Print five days of future draw history on the daily draw worksheet.
  6	Print six days of future draw history on the daily draw worksheet.

• 6. Should the account name or the route name/location print on the Daily Draw Worksheet? BCP (Client) This setting determines whether the account name or the route name and location are displayed on the Daily Draw Worksheet. Select “Account Name” (the default) or “Route Name.”

• 7. If rating carrier collect draw, should a rate code be required when entering draw changes? BCP (Client) If this Business Rule is set to “yes”, draw change entry and returns entry will require a rate code for carrier collect draws and returns.

  Value
  Yes	A rate code is required for carrier collect draws and returns.
  No	A rate code is not required for carrier collect draws and returns.

• 8. Are changes to the truck sequence allowed in “Enter Bundle Info”? BCP (Client) This setting determines whether the truck sequence can be changed during the publishing run. (The truck sequence is changed by rejecting the default shown in the Truck Sequence field on the Enter Bundle Info window and entering a different one.)

  Value
  Yes	The truck sequence can be changed during the publishing run.
  No	The truck sequence cannot be changed during the publishing run.

• 9. Should the export file set for multi-pack products default to 'One File Set' in 'Enter Bundle Info'? BCP (Client) This setting controls the default setting of the Create One File Set checkbox in Enter Bundle Info, which is used to combine all multi-pack editions into one set of export files.

  Value
  Yes	One File Set should be checked by default in Enter Bundle Info.
  No	One File Set should be unchecked by default in Enter Bundle Info.

• 10. Should the account’s phone number print on the bundle top? BCP (Client) The carrier’s phone number may print on the bundle tops that accompany papers the carrier receives for delivery.

  Value
  Yes	If the carrier’s phone number should print on bundle tops.
  No	If the carrier’s phone number should not print on bundle tops.

• 11. Should the subscriber’s phone number print on the bundle top? BCP (Client) The subscriber’s phone number may print on the bundle tops for subscriber-related messages that accompany papers the carrier receives for delivery.

  Value
  Yes	If the subscriber’s phone number should print on bundle tops. If the subscriber’s phone number is an unlisted number, it will not print.
  No	If the subscriber’s phone number should not print on bundle tops.

• 12. When printing stop messages, should the restart date print on the bundle top? BCP (Client) Restart dates can be entered with a stop transaction. This setting governs whether the restart date should print with the stop transaction on bundle tops, if a date has been entered.

  Value
  Yes	The restart dates should print with the stop, if available.
  No	The restart date should never print with the stop.

• 13. Should account payments print on the bundle top? BCP (Client) In order to keep carriers better informed of activity, account payment information may print on the bundle tops.

  Value
  Yes	Account payment information should print on bundle tops. Canceled payments will also print on bundle tops.
  No	Account payment information will not print on bundle tops.

• 14. Should subscriber payments print on the bundle top? BCP (Client) In order to keep carriers better informed of activity, subscriber payment information may print on the bundle tops.

  Value
  Yes	Subscriber payment information should print on the bundle tops. NSF checks and canceled payments will also print on bundle tops.
  No	Subscriber payment information should not print on the bundle tops.

• 15. Should complaints print on the bundle top? BCP (Client) Complaints may print on the bundle tops to accompany papers the carrier receives for delivery. Selected complaint codes may be defined to not print on the bundle tops.

  Value
  Yes	If complaints should print on bundle tops.
  No	If complaints should not print on bundle tops.

• 16. What label should display for complaints on the bundle tops? BCP (Client) This Business Rule allows you to set the text that will appear as the label for complaints on bundle tops. The default setting is “Complaint”.

• 17. Should multiple-day complaints generate separate messages when the date range includes the most recent delivery date? BCP (Client) You can generate a separate bundle top message for the current complaint of a multiple-day complaint, with the remaining complaints included in another message. If all of the complaints are for previous dates, then only one message is created.

  Value
  Yes	A separate message should be generated for the current complaint of a multiple-day complaint.
  No	Only one message should be generated for a multiple-day complaint.

• 18. Should returns print on the bundle top? BCP (Client) Returns may print on the bundle top (all returns that have not previously appeared on the bundle top will print).

  Value
  Yes	If returns should print on bundle tops.
  No	If returns should not print on bundle tops.

• 19. Should bundle detail print for each advance section when printing bundle tops for the main publishing run? BCP (Client) Bundle detail may be printed for advance sections. If this rule is set to “yes”, the standard bundle size, number of standard bundles, and key bundle size will be printed on bundle tops for each advance section of the newspaper, as well as the insert mix and total draw. To print advance section detail, the Business Rule Do you run advance processing by section? , below, must be set to “yes”.

  Value
  Yes	Bundle detail will be printed for advance sections.
  No	Bundle detail will not be printed for advance sections.

• 20. Should draw adjustments print on the bundle top? BCP (Client) Draw adjustments may print on the bundle top (all draw adjustments that have not previously appeared on the bundle top will print).

  Value
  Yes	If draw adjustments should print on bundle tops.
  No	If draw adjustments should not print on bundle tops.

• 21. Should a reminder message print for holding vacation packs each day the subscriber is on vacation pack? BCP (Client) Subscribers may elect to keep their subscription active while on vacation. If they do, the carrier or District Manager holds their newspapers for them until they return. This setting controls whether messages should print on the bundle top each day reminding carriers which subscriptions should be held for vacation packs.

  Value
  Yes	Reminder messages should print for vacation packs.
  No	Vacation pack messages should only print on the first day.

• 22. When truck is a relay, should the supplying truck be included on the bundle top? BCP (Client) The supplying truck for a relay truck can be included on bundle tops and truck manifest, and the exports for those options, based on this in the next parameter.

  Value
  Yes	The relay supplying truck will be included on bundle tops.
  No	Only the relay truck will be included on bundle tops.

• 23. When truck is a relay, should the supplying truck be included on the truck manifest? BCP (Client)

  Value
  Yes	The relay supplying truck will be included on the truck manifest.
  No	Only the relay truck will be included on the truck manifest.

• 24. What is the print order for bundle tops? BCP (Client) Bundle tops are typically printed in ascending or descending truck departure order, and within each truck by ascending or descending drop order. Truck departure order is the order in which trucks leave the dock, and drop order is the order in which routes are dropped off from a truck. Bundle tops can also be sorted by edition or depot, but this is less common.

  Value
  Ascending Truck	Bundle tops will sort in ascending truck departure order and, within each truck, in ascending drop order.
  Depot Depart Drop	Bundle tops will sort in alphabetical depot order and, within each depot, in depot drop order.
  Descending Drop	Bundle tops will sort in ascending truck departure order and, within each truck, in descending drop order.
  Descending Truck	Bundle tops will sort in descending truck departure order and, within each truck, in descending drop order.
  Edition Depart Drop	Bundle tops will sort by edition. Within each edition, they will sort in ascending truck departure and ascending drop order.

  To illustrate the different sort orders, assume the departure sequence is truck A, then B, then 100, and the drop order within these trucks is:

  Truck	Drop	Route	Edition for route	Depot	Depot Drop Order
  A	10	240	Metro	30Mnd	100
  	20	270	Metro	20Slr	20
  	30	A36	Metro	20Slr	50
  B	10	280	City	30Mnd	80
  	20	310	Metro	Extra	30
  100	10	400	City	80Bst	150
  	20	430	City	20Slr	340
  	30	410	City	30Mnd	45

  The order in which the bundle tops will be printed with each of the five possible settings is:

  
• 25. Should a minimum bundle size be used? BCP (Client) Bundles may contain a specified number of papers, but a minimum bundle size will be requested to accommodate “hand tied” bundles if you set this rule to “yes”.

  Value
  Yes	If a minimum bundle size should be used.
  No	If there is no minimum bundle size.

• 26. When printing bundle tops to different spool files by truck, should exception bundles be included in the truck file? BCP (Client) Based on this Business Rule, you can print the exception bundles at the end of each spool file when different spool files are created by truck.

  Value
  Yes	Include exception bundles at the end of each spool file.
  No	Do not include exception bundles in the truck file.

• 27. When bundle messages for a route exceed one page should the remaining messages appear at the end of the spool file? BCP (Client) This Rule allows newspapers to limit bundle tops to one page by separating any messages that would cause the bundle top to exceed one page and place them at the end of the spool file.

  Value
  Yes	Limit bundle tops to one page.
  No	Do not limit bundle tops to one page.

• 28. What type of bundle tops should be printed separately? BCP (Client) “Hand-tie” bundles are bundles where the total paper draw is less than the minimum. It may be necessary to print bundle tops for hand-tie bundles separately (after the standard and key bundle tops) if bundle tops are attached automatically to standard-size bundles, necessitating special handling of hand-tie bundles. “Special” bundles apply only with the InsertPlus module. Some bundles will not have inserts and require special handling in the mail room. It may be necessary to print bundle tops for special bundles separately (after the standard and key bundle tops).

  Value
  Hand-tie	Hand-tie bundles should print separately.
  Special	Special bundles should print separately.
  Both	Both hand-tie and special bundles should print separately.
  None	Neither hand-tie or special bundles should print separately.

• 29. Should an additional spool file be created for each route when bundle tops are processed? BCP (Client)

  Value
  Yes	Individual bundle top files will be created for each route, as well as the full bundle top file. The file for each route will contain the same types of information that are included in the full file, and the product ID and route ID will be appended to the file name entered in View/Print.
  No	Only the full bundle top file will be created.

• 30. Which document setup should be used when creating additional files by route for bundle tops? BCP (Client)

• 31. Which document setup should be used when creating additional files by route for route lists? BCP (Client) These two Business Rules identify the document setup to be used when creating individual route reports in addition to the standard report. The settings of these Business Rules identify the filename format and file path for these reports. Valid settings are those documents that have been set up in the “iServices Distribution” document area in Document setup.

• 32. Which document setup should be used when creating additional files by route for carrier mail export? BCP (Client) This setting identifies the document setup to be used when separating the carrier mail export into separate files by route so that they can be viewed on the Routes tab in iServices Distribution. This setting identifies the filename format and file path for these files. Valid settings are those documents that have been set up in the “iServices Distribution” document area in Document setup.

• 33. Which document setup should be used when creating additional files by route for route labels? BCP (Client) This setting identifies the document setup to be used when creating an additional route label file for each route. This setting identifies the filename format and file path for these files. Valid settings are those documents that have been set up in the “iServices Distribution” document area in Document setup.

• 34. Which document setup should be used when creating additional files by route for previous delivery labels? BCP (Client) This setting identifies the document setup to be used when creating an additional previous delivery label file for each route. This setting identifies the filename format and file path for these files. Valid settings are those documents that have been set up in the “iServices Distribution” document area in Document setup.

• 35. What is the “label” for “hand tie” bundles? BCP (Client) “Hand-tie” bundles are bundles where the total paper draw is less than the minimum bundle size. Such bundles are also called “illegal” bundles, rolls, etc. This option allows these bundles to be called by a user-defined name. This name prints on the bundle tops and truck manifest. The default is “Illegal”.

• 36. What is the default key bundle print option? BCP (Client) This determines the default setting of the Print Key Bundles Only? prompt in Publishing | Carrier/Dealer | Enter Bundle Info. This default print option may be changed when entering the bundle information.

  Value
  Always	Bundle labels will be printed only for key bundles.
  Never	Bundle labels will be printed for all bundles (key and standard).
  Route	The key bundle option defined for each route in the truck sequence file should be used to determine whether a key bundle only or a bundle top for each bundle should be printed.

• 37. If all bundles are the standard size, should a key bundle be created? BCP (Client) If the key bundle has the same number of papers as the standard bundles, the key bundle can be counted as a standard, as governed by this setting. For example, say the standard bundle size is 30 and a route has a draw of 120. If this rule is set to “no”, the bundle tops will still record 3 bundles of 30 and 1 key of 30; if it is set to “yes”, however, the bundle tops will record 4 bundles of 30.

  Value
  Yes	A key bundle top should be produced even if all bundles are the standard size.
  No	Produce only standard bundle tops if all bundles are the standard size.

• 38. Should a message print on the bundle top when an office pay subscription goes into grace? BCP (Client) A message may be displayed on the bundle top when an office pay subscriber reaches their expiration date and goes into their grace period.

  Value
  Yes	Print a message on the bundle top when a subscriber enters their grace period.
  No	Do not print a message.

• 39. Should bundle tops always print on the same side of paper? BCP (Client) If bundle tops always print on the same side of the paper, the bundle tops can be easily burst in units containing an even number of pages. For example, some clients use a large paper cutter to cut the top perforation of the bundle tops—this results in every other page being a bundle top (see example). This does not conserve paper, however, if that is a concern.

  Value
  Yes	If bundle tops should always print on the same side of the paper. If the messages require more than one page, a blank page will separate the bundle tops.
  No	If bundle tops should print consecutively, regardless of the side of the paper on which they begin.

  

• 40. Should bundle top messages print on a separate page? BCP (Client) If bundle top messages print on the same page as the bundle top information, they will be exposed when bundles are dropped at the drop location. Confidential subscriber information, such as names, phone numbers, and vacation plans, is therefore available to any passer-by. If bundle messages begin printing on page two of the bundle top, this information will not be visible until the bundle is opened by the carrier.

  Value
  Yes	If bundle top messages should begin on page two of the bundle top.
  No	If bundle top messages should begin on page one of the bundle top.

• 41. Should the expire date print with the subscription transaction messages on the bundle top? BCP (Client) The expire date may be printed with other transaction information for office pay subscribers.

  Value
  Yes	The expire date should print with subscription transaction messages.
  No	The expire date should not print with subscription transaction messages.

• 42. Should messages print on the first key bundle top or the first standard bundle top? BCP (Client) Some newspapers print carrier messages on the first standard bundle top, while others have their carriers look on the key (odd) bundle top for messages.

  Value
  Key	Messages should print on the key bundle top.
  Standard	Messages should print on the first standard bundle top.

• 43. If a route requires additional advance sections, should a separate bundle top be printed for the advance section? BCP (Client) Advanced processing can be done for special sections of the paper that are delivered to carriers prior to the publishing date. The draw for advanced publishing is only an estimate, and when the actual draw is calculated on the publishing day the draw for any additional advance sections that need to be distributed to a given route will print on the bundle tops. This setting governs whether the additional draw for advanced sections (known as “updraw”) is printed on a separate bundle top.

  Value
  Yes	Print additional advanced draw on a separate bundle top.
  No	Print additional advanced draw with other bundle information.

  If Yes:

  • 44. Should the separate bundle tops for the advance sections be in a separate spool file? BCP (Client) If separate bundle tops are printed for advance section updraw, the advance section bundle tops can be printed along with the regular bundle tops or in a separate file, depending on how this rule is set.

    Value
    Yes	Print advance section bundles to a separate file.
    No	Advance section bundles should print with the regular bundle tops.

• 45. On combined publishing days, should one bundle top be produced for routes that deliver to both products? BCP (Client) If you have more than one publication, you may have some routes that deliver multiple pubs. In the case where two publications are combined on a publishing day, this setting determines whether one bundle top prints for multi-pub routes, or a separate bundle top for each publication delivered by the route. In order to print on a single bundle top, the route must be on the same truck and truck sequence for both publications, and have the same district and (if you have InsertPlus) the same inserts. See Specifics, Publication Combine for more information about combined publications. This rule not only affects bundle tops, but also route delivery lists, the truck manifest, and daily draw worksheets. If a single bundle top prints for the route, the route will also print as a single line on these reports.

  Value
  Yes	A single bundle top should print for routes that deliver more than one of the publications in a combined publishing run.
  No	Multiple bundle tops should print for routes that deliver more than one of the publications in a combined publishing run.

• 46. Should bundle tops include additional products? BCP (Client) Carriers may deliver Targeted Marketing products or other publications along with the regular newspaper. If so, it is useful to have the bundle tops list the other products that should be delivered on the bundle top. This setting determines whether bundle tops should list the other products being delivered with the newspaper. See Deliverable for more information.

  Value
  Yes	TM products delivered with a publication should be listed on the publication’s bundle tops.
  No	No TM products should be listed on bundle tops.

• 47. Should a draw comparison print on bundle tops? BCP (Client) Bundle tops can print a draw summary that compares the route’s draw in the current month to the draw in the same month last year. A “year to date” comparison between this year and last year is also included. The comparisons list the average draw, quantity change, and percent change.

  Value
  Yes	A draw comparison should print on the bundle tops.
  No	No draw comparison should print.

• 48. When printing route lists on bundle tops, should the subscriber billing method be included? BCP (Client) This Business Rule determines whether the subscriber’s billing method is included on the route delivery list that is printed on bundle tops.

  Value
  Yes	The subscriber’s billing method will be included in the route list on bundle tops.
  No	The subscriber’s billing method will not appear in the route list on bundle tops.

• 49. Should bundles for relay trucks be printed at the drop point for the relay truck? BCP (Client) A relay truck is one which receives bundles from another truck. Bundle tops print in drop order, so bundle tops for a relay truck might print in between other drops on a truck. Or, all relay truck bundle tops can print after the other bundles on the truck. For example, say truck A drops route 09, route 10, relay truck B, and route 11, and relay truck B in turn drops routes 40 and 50. This setting would govern whether bundle tops for routes 40 and 50 printed between routes 10 and 11, or after route 11.

  Value
  Yes	Bundle tops for relay trucks should print between other drops on the truck, in drop point order.
  No	Bundle tops for relay trucks should print after the other drops on the truck.

• 50. When an account has multiple routes at the same drop point should they be combined on the bundle, manifest and stacker? BCP (Client) This setting allows you to combine draw quantities on bundle tops, truck manifest and the stacker interface when a single distribution drop point contains multiple routes for the same product, carrier, edition, and insert mix.

  Value
  Yes	Routes should be combined on bundle tops, truck manifests, and the stacker interface.
  No	Routes should not be combined.

• 51. What bundle information should display on the bundle tops in large print? BCP (Client) Bundle tops contain some information, such as the total draw for the route, in large print. This setting determines whether the standard bundle size or the number of standard bundle tops to be dropped at the route displays in large print. If the bundle size or number of standards does not display in large print, it will still appear on the bundle tops, but in normal print.

  Value
  Bundle Size	The standard bundle size should display in large print.
  Number of Standards	The number of standard bundles should display in large print.

• 52. Should a truck banner label print before each truck on the bundle tops? BCP (Client) A banner page may print for each truck, before the truck’s route bundle tops, based on this setting. The page will contain the word “TRUCK” and the truck ID in large print. Each truck in the truck sequence will receive a banner. The exception is relay trucks—if bundle tops for relay trucks are printed at the drop point of the relay truck (as determined by the above rule), no truck banner will print.

  Value
  Yes	A banner should print for each truck before the bundle tops.
  No	No truck banners should print.

• 53. Should the truck display on the bundle top in large print? BCP (Client) As mentioned in the previous rule, bundle tops can display some information in large print. This setting determines whether the truck that drops the bundle tops at the route should display in large or regular print.

  Value
  Yes	The truck should display on the bundle top in large print.
  No	The truck should display on the bundle top in regular print only.

• 54. What is the print order for the truck manifest? BCP (Client) The truck manifest may be printed in either ascending or descending truck departure order.

  Value
  Ascending Truck	If the truck manifest should print in ascending truck departure order.
  Descending Truck	If the truck manifest should print in descending truck departure order.

  For example, assume the truck departure order is:

  Truck	Order
  A	10
  B	20
  100	30
  16	40

  If Ascending Truck is selected the truck manifest will be printed in order of A, B, 100, 16. If Descending Truck is selected, the manifest will be printed in order of 16, 100, B, A.

• 55. Should the edition print on the truck manifest? BCP (Client) This defines whether or not the edition should print on the truck manifest.

  Value
  Yes	Print the edition on the truck manifest. It will appear under the route.
  No	Do not print the edition on the truck manifest.

• 56. Should the truck manifest include additional products? BCP (Client) Targeted Marketing products may be dropped at the same time as the newspaper. In this case, it would be helpful to include the TM draw on the manifest as well as the newspaper. See Deliverable for more information.

  Value
  Yes	Print the TM product on the newspaper truck manifest.
  No	TM products should not print on the newspaper truck manifest.

• 57. Should a column to record returns print on the truck manifest? BCP (Client) This defines whether or not a blank column should be allowed on the truck manifest to record the number of returns picked up by the truck driver.

  Value
  Yes	A column should be allowed for recording returns on the truck manifest.
  No	A column should not be allowed for recording returns on the truck manifest.

• 58. Should the standard bundle size print as a message on the truck manifest when bundle sizes are defined at truck level? BCP (Client) This setting defines whether the standard bundle size will appear as a message on the Truck Manifest when the bundle size option is set to “truck”.

  Value
  Yes	The standard bundle size will be printed on the Truck Manifest when bundle size is defined as “truck”.
  No	No bundle size message will be printed.

• 59. When a truck’s relays have bulked draw and bundle sizes match, should bundle count and key size be recalculated? BCP (Client) If a relay parent has children trucks that bulk draw, the relay parent can include the actual draw or the bulked draw for the child truck when calculating the parent’s total draw, based on this parameter. If the actual draw is included, the draw is recalculated when totalling the parent truck’s draw.

  Value
  Yes	The draw is recalculated when determining the total draw for the parent truck, using the actual draw of the children trucks.
  No	The draw is not recalculated, and the totals on the parent truck will match the relay’s truck totals.

• 60. What “label” should print for advanced sections? BCP (Client) During the publishing run, any additional draw needed for sections distributed in advance will print on the Truck Manifest and Press Room Report. This setting determines the label this advanced draw will print under. The default is “ADVANCE”.

• 61. On the Truck Manifest and Press Report, should only advance section up-draws print? BCP (Client) If you distribute advanced sections, the advance draw will often be different from the actual draw of the publishing run. If the advance draw for a route is less than the actual draw, this will print on the Truck Manifest and Press Room Report, so that extra advanced sections can be distributed. This setting determines if advanced draw also prints in the case where the advanced draw is greater than the actual draw. This may be useful, for example, if your drivers collect advanced sections from routes that have extra draw and redistribute them to routes that need more sections.

  Value
  Yes	Only routes that need more advanced sections should print.
  No	Routes with extra advanced sections should print.

• 62. Should route service draw be reported separately on the press room report? BCP (Client) This setting allows the service draw portion of home-delivery route draw to be reported as a separate category within each route type.

  Value
  Yes	Service draw should be reported as a separate category on the Press Room Report.
  No	Service draw should not be broken out separately on the Press Room Report.

• 63. What is the format for chute? BCP (Client) This setting indicates that chute IDs are either Numeric (the default) or Alphanumeric.

• 64. What is the maximum length for chute? BCP (Client) This setting determines the maximum length of chute IDs (the default is 2).

• 65. What is the default counter/stacker equipment? BCP (Client) Circulation can export draw information to a file, which can then be imported into a counter/stacker machine. Indicate here the brand of counter/stacker you use, or enter “NONE” if you will not export information to your counter/stacker. If using “File Map,” file mapping will determine the stacker format. Ferag

  File Map

  HALL

  iDab

  KANSA

  Muller Martini

  NONE

  QUIP

  QUIPP2

  WinLincs Note:

  • All of the stacker interfaces require a separate license fee to use. Contact the Naviga Support Center for more information.

• 66. Which day is considered the first day when determining the value for day of week number in the stacker interface? BCP (Client) This setting allows sites to set a day other than Sunday as the first day of the week. The default value is Sunday.

• 67. If using the Ferag stacker and File Map, should illegal bundles be separated? BCP (Client) When using a stacker interface file map for Ferag, the key bundle can appear first on its own line, followed by the standard/bulk lines.

  Value
  Yes	Key and standard bundles should be exported separately to Ferag.
  No	Key and standard bundles should not be exported separately to Ferag.

• 68. When using the WinLincs format for the Stacker Interface, should illegal bundles be combined? BCP (Client) When using the WinLincs format, illegal bundles can be combined into one entry or listed on separate lines, based on this Rule.

  Value
  Yes	Combine illegal bundles into one entry.
  No	List illegal bundles on separate lines.

• 69. In what order should the route labels print? BCP (Client) The route labels may print in delivery sequence or subscription ID order within a truck and route. If the route assigned to the subscription is an override route (not assigned to the address), then the delivery sequence order may not be used.

  Value
  Delivery sequence	Print route labels in truck, newspaper route, newspaper delivery (walk) sequence order.
  Subscription	Print route labels in truck, newspaper route, subscription ID order.

• 70. What is the distribution class used for mixed delivery routes? BCP (Client) You may have some routes that are mixed mail/carrier delivery. For example, a route at the edge of your market area might be mail Monday through Saturday, but carrier delivered on Sunday, when the mail isn’t delivered. You identify a route as a mixed delivery route by assigning it to the mixed distribution class. You identify the mixed distribution class here.

• 71. Which master table should be used to determine the label group for subscriptions both mail and route delivered? BCP (Client) Subscribers on a mixed delivery route will be mail delivered at least one day a week. The label group can be determined based on the Zip code (the normal method for mail subscribers) or by delivery schedule. Indicate which method to use for assigning the mail label group.

  Value
  ZipLabelGroup	Use the subscriber’s Zip code to assign the label group.
  DeliveryScheduleDays	Use the subscriber’s delivery schedule to assign the label group.

• 72. For how many days into the future should pending draw be automatically updated by End Publishing Run? BCP (Client) The pending draw for a publishing date is the estimated draw, taking both processed and unprocessed transactions into consideration. This is generally the most reliable way to estimate draw, but the calculations take extra time because the system is “peeking” at unprocessed transactions. Pending draw can be calculated manually (in Update Pending Draw) or automatically, when you run End Publ Run. If you would like pending draw to be updated automatically by End Publ Run, enter the number of days into the future for which pending draw should be calculated. If you do not want pending draw updated automatically, leave the setting defaulted to “0”.

• 73. Which single copy demographic identifies the home delivery route used to deliver NIE papers? BCP (Client) If a setting is entered for this rule (i.e., it is not blank), an NIE export file will be produced during each end publ run that contains the product, account, route, run date, and draw total. The file will be saved in /dti/exchange and will be named nieroutes<productID>.d. This file can then be imported into an external NIE application for billing. This rule can be set to any single copy demographic question that has been set up.

• 74. Which subscription demographic identifies the postal routing code? BCP (Client) An optional 3-character postal routing code can be used with the Wamac Inkjet file map after the city ID. This Business Rule identifies the demographic that contains this routing code. The full code, including the postal routing code, is: [6-character Zip]{space}{space}[11-character city]{space}[3-character routing code].

• 75. Is the rack draw managed at the outlet level within Bellatrix, but at a “group” route level within DTI? BCP (Client) Note:

  • The Bellatrix interface requires a separate license fee to use. Contact the Naviga Support Center for more information.

  Bellatrix is an automated newspaper rack system. If you interface information to Bellatrix, this setting determines whether racks are set up at the “group” level in Circulation, as opposed to the “outlet” level (individual racks). In the Bellatrix import file, groups must be placed in the Route Number field, whereas outlets must be in the Outlet field. If the Rack/Dealer field is set to “1” (indicating a rack), Circulation will look at this setting to determine whether it should try to match the group or outlet with a Circulation route when interfacing draw, returns, and draw adjustments. Note that you can have multiple records for the same group in the import file—Circulation will keep a running tally for the group. Also note that groups in Bellatrix can be no more than three digits—this means that the corresponding routes in Circulation must be no more than 3 characters, if you keep information at a group level.

  Value
  Yes	Rack information will be kept at the Bellatrix group level in Circulation.
  No	Rack information will be kept at the Bellatrix outlet level in Circulation.

• 76. What is the insert mix size required by the inserting equipment? B (Client) If your newspaper uses InsertPlus, and your inserter has a minimum number of papers that must have one edition and insert combination in succession, enter that number here. For example, the inserter might have a minimum limit of 75 papers—if there are fewer than 75 papers before either the edition or the insert combination change, the papers will require special inserting. For example, with a minimum of 75, and the routes in the drop order shown below, routes 07, 27, and 15 would require special inserting.

  Route	Edition	Insert Combination	Draw
  8	Metro	08-25-0003	54
  2	Metro	08-25-0003	46
  7	Metro	08-25-0001	59
  27	Metro	08-25-0001	12
  11	City	08-25-0002	87
  15	Metro	08-25-0002	61
  3	Metro	08-25-0001	121

  • 77. What is the label for insert mixes that fall below the minimum required by the inserting equipment? B (Client) As mentioned in the previous rule, bundle tops for routes that have insert combinations that are below the minimum required by the inserter machine will print separately. A message will also appear for these routes on the truck manifest. For this rule, indicate the label that should be used in both cases—for example, “Insert Exception”.

• 78. Which days need initial subscriber messages repeated? BCP (Client) Because different carriers may deliver a single route, you may need to have messages repeated on bundle tops on certain days of the week. For example, a route may have a weekday carrier and a weekend carrier. Therefore, messages for all of the subscriber transactions that have taken place on the route in the past week should appear on the Saturday bundle tops, so that the weekend carrier will know which subscribers have started and stopped. The messages will be repeats of the initial message (they will not be labeled as reminder messages). This setting determines the days of the week that subscription transaction messages are repeated on bundle tops. Unlike most Business Rules, more than one setting (day) an be chosen (multi-select).

• 79. When should subscription reminder messages print? BCP (Client) “Reminder” messages can print on bundle tops for a given number of days after the transaction date. For example, you could have start messages appear on the start date, and on two subsequent days (see Tran Type Publication for more information). This setting determines whether the reminder days should be the subsequent publishing days, subsequent delivery days for the subscriber (determined by the delivery schedule) or the same day in subsequent weeks. To illustrate the three possible settings, let’s use the example of the Trib, which publishes seven days a week. Mr. Jones, a Mon-Fri subscriber, restarts on Friday the 5th. We have set up restarts to generate two reminder messages. The initial message will appear on Friday the 5th; the following table describes when the two reminder messages will be printed, depending on how this rule is set.

  Setting	Reminders Print On
  Next Delivery Day	Monday the 8th, Tuesday the 9th
  Next Publishing Day	Saturday the 6th, Sunday the 7th
  Next Weekday	Friday the 12th, Friday the 19th

  Value
  Next Delivery Day	Reminder messages will print on bundle tops on the next delivery day, based on the subscriber’s delivery schedule.
  Next Publishing Day	Reminder messages will print on bundle tops on the next publishing day.
  Next Weekday	Reminder messages will print on bundle tops on the same day of the week as the initial messages.

• 80. Which day’s complaints should print on the same weekday? BCP (Client) Complaints are different from other subscriber transactions in that they do not initially print on bundle tops on the transaction date (the bundle tops will already be printed for that date). Instead, they print on the next publishing day or (depending on how you set this rule) the same day as the transaction date in the following week. For example, if you set up Sunday’s complaints to print on the same weekday, a complaint entered for Sunday the 6th would print on the route’s bundle tops on Sunday the 13th. If no days should have their complaints printed on the same weekday, leave this setting blank.

• 81. Should a message recap print on bundle tops? BCP (Client) Start, stop, and other subscriber transactions that occur on a route can be printed as messages on the route’s bundle top. A recap of the day’s transactions can also print at the bottom of the bundle top, if this rule is set to “yes”.

  Value
  Yes	A recap of the day’s transactions should print on a route’s bundle tops.
  No	No recap should print on the bundle tops.

• 82. Which date should previous paper deliveries be based on? BCP (Client) Your newspaper may offer new subscribers or restarts a free paper from a day earlier in the week. For example, if a subscription starts Wednesday, you can offer the subscriber the previous Sunday’s paper. This previous paper can be delivered on the start date of the subscription, or the entry date (if final transaction processing is completed for the entry date, it will be delivered on the next publishing date). This setting determines whether the previous paper is delivered on the start date or the entry date.

  So, with the above example where the subscription starts on Wednesday, let’s say the new start is entered on Monday (after final transaction processing has been completed). The Sunday paper could be delivered separately on Tuesday (entry date option), or with the daily paper on Wednesday (start date option). If you do not offer delivery of previous papers to new starts or restarts, it does not matter how you set this rule.

  Value
  Entry Date of Start	The previous paper should be delivered on the entry date of the new start or restart (or, if final transaction processing has been run, the next publishing day).
  Start/Entry Date	The previous paper should be delivered on the start date of the new start or restart. If this date does not work, the system will use the entry date of the new start or restart.
  Start Date	The previous paper should be delivered on the start date of the new start or restart.

• 83. Should the subscriber’s name and address print for each message on bundle tops? BCP (Client) This setting determines whether the subscriber’s name and address print on bundle tops with each message if there are multiple messages of the same transaction type. For example, if a subscriber had three complaints, this setting determines whether the subscriber’s name and address are printed with each complaint.

  Value
  Yes	The subscriber’s name and address should print with each message.
  No	The subscriber’s name and address should only print with the first message if there are multiple messages for the same transaction type.

• 84. Should route messages be deleted if there is no net effect to the carrier? BCP (Client) This setting determines whether messages should be retained (for printing on bundle tops, truck manifests, etc.) if there is no change for that subscriber. For example, if a Sunday-only subscriber stops on Tuesday and then, on Friday, decides to start again, there is no net change for Sunday, and printing the start and stop messages will just confuse the carrier. If this rule is set to “yes”, neither message would print on the bundle top.

  Value
  Yes	Delete messages if there is no net affect to the route’s draw.
  No	Do not delete messages, even if there is no net affect.

• 85. Can advance publishing runs be started while transaction processing is being run? BCP (Client) An advance publishing run may be started while Transaction Processing is being run for the publication. If this happens, the actual draw figures may be changing while the advance draw figures are being calculated, resulting in less accurate advance draw. Based on your publishing processes and how accurate you need the advance draw, you may or may not want to allow this.

  Value
  Yes	Circulation will allow advance runs to be started while Transaction Processing is being run for the same publication.
  No	Advance runs cannot be started if Transaction Processing is being run for the same publication.

• 86. How many days prior to and including a bonus day delivery should messages be automatically created for a carrier? BCP (Client) “Bonus days” are days on which the subscriber receives the paper even though it is not a normal delivery day. For example, as part of their subscription, a weekend-only subscriber might get the paper on New Years, even though New Years is on a Monday. Bonus day messages may or may not print on bundle tops, depending on whether the reason code for the BonusDay transaction has Print On Bundle set to “y”. However, the bonus day message will print, regardless of the reason code, if the BonusDay transaction was created within a certain number of days of the bonus date, as defined here. So, for example, if the reason code is set not to print on a bundle top, but this rule is set to 5 and a subscriber starts 4 days before a bonus date, a bonus day message will print on the bundle top for that subscriber on the bonus date. The default is zero.

• 87. What is the threshold for creating future start messages? BCP (Client) When a route has a large number of new starts in the future, it may be helpful to print the pending starts on bundle tops so that the carrier can be prepared for the increased activity. Circulation has the ability to list new subscribers that will start on the next publishing day on bundle tops, if the number of starts equals or exceeds the number entered here. For example, if this is set to 5, and a route has 7 new starts on the next publishing day, the 7 new subscribers would have future start messages print on the bundle top. However, if the route only had 4 new starts on the next publishing day, there would be no future start messages. If all starts for the next publishing day should print on your bundle tops, set this rule to 1; if the next day’s starts should never print, set the rule to zero (the default).

• 88. Do you round draw for advance sections? BCP (Client) To make it easier for distribution personnel to handle advance sections, some newspapers use only standard bundles for bulked routes; key bundles are either rounded up to become an additional standard, or rounded down (dropped from the run). This rule determines whether advance draw for bulked routes may be rounded. If you set it to “yes”, a rounding model will need to be specified when entering bundle information for an advance run.

  Value
  Yes	Advance draw for bulk routes may be rounded.
  No	No rounding will occur.

• 89. Do you run advance processing by section? BCP (Client) Advance publishing runs can be opened for each section, or one run may be active for all sections. If each section publishes independently, advance draw will be kept at the section level. Otherwise, the advance draw will be the same for all sections. If you want only one advance publishing run per day and product, and would like all sections to have the same draw, enter “no” here. On the other hand, if you would like each section to have its own advance draw and separate advance run, enter “yes”.

  Value
  Yes	Each section should have its own advance run.
  No	One advance run will include all sections.

• 90. Should advance draw by section detail print on the truck manifest instead of updraw for the main publishing run? BCP (Client) If you set this rule to “yes”, draw by section information will appear on the truck manifest. A paper section recap at the drop and truck levels will also be added to the truck manifest.

  Value
  Yes	Advance draw section detail will appear on the truck manifest.
  No	Advance draw section detail will not appear.

• 91. When combining routes at a drop level, must the summary route on the manifest have draw or a driver alert? BCP (Client) This setting determines whether a route with zero draw prints on the truck manifest, if a carrier’s routes are combined at the drop level and it is the first route. Note that if the first route has a driver alert (that the route no longer has draw), the first route will still display on the manifest regardless of the Business Rule.

  Value
  Yes	If the first route has no draw for the date, that route will not display on the manifest. Instead, the first route that does have draw will display.
  No	The first route for the drop will always print on the manifest, even if it has no draw for the date.

• 92. Should the advance section detail reprint on the publishing manifest if it was combined with a final on an earlier date? BCP (Client) If advance section detail prints on the regular truck manifest for an earlier date (based on the Combine with Final On field in Advance Enter Bundle Info), the detail can also print on the regular manifest for the actual publishing day, based on this parameter. For example, if a Sunday advance run section was distributed on Friday and detail for the Sunday section printed on the Friday regular manifest, the advance section detail would print again on the Sunday regular manifest if this Business Rule is set to “yes”.

  Value
  Yes	Advance detail should appear on the final manifest for the publishing date, even when combined with the final manifest on an earlier date.
  No	Advance detail should not appear on the final manifest for the publishing date, if combined with the final manifest on an earlier date.

• 93. When combining routes at a drop level, should a recap of the routes display for the drop on the Truck Manifest? BCP (Client) If you set this rule to “yes”, a recap will appear on the truck manifest that displays routes at the drop level when routes are combined. The draw amount and bundle sizes will be displayed for each route.

  Value
  Yes	A route recap will appear on the truck manifest.
  No	A route recap will not appear.

• 94. How many days do you want to retain delivery deadline override records? BCP (Client) Enter the number of days you want to retain delivery deadline override records. The default is 999 days.

• 95. What is the ‘label’ for depots? BC (Client) Depots are warehouses where newspapers for a large number of routes are dropped off and arranged. Carriers then come to the depot and pick up the papers for their routes. As different newspapers have different names for depots (“distribution center”, “warehouse”, etc.), you can define the name to use for depots here. This name will appear on invoices and bundle tops if they are sorted by depot. The default is “Depot”.

• 96. Should weight information print on the truck manifest? BCP (Client) The setting controls whether weights are shown on the truck manifest.

  Value
  Yes	The truck manifest will display, for each drop, the weight of the standard bundle, each product/route combination and the total weight for the drop. At the end of the truck details, the total weight for the truck will also be shown.
  No	Weights will not appear on the truck manifest.

• 97. Should the route name print on the truck manifest? BCP (Client) You may want the route name to be printed below the account name on the truck manifest, as shown below.

  

  Value
  Yes	The route name should appear below the account name on the truck manifest.
  No	The account telephone number will be displayed instead of the route name.

• 98. Should the truck manifest create an export file? BCP (Client) The truck manifest is one of the central documents in the publishing run. To allow greater flexibility, the data for this report can be exported to an ASCII file. This setting indicates whether the data will be exported.

  Value
  Yes	Truck manifest data should be exported to an ASCII file as part of the report generation process.
  No	No export should take place.

• 99. Should the format of the truck manifest export file name be manifest<ProductID><EditionID><DayNumber><ProcessID>? BCP (Client) This rule gives you the option to create manifest export files by publication and/or edition. If you enter “yes”, separate export files will be created with the file name of “manifest<product/publication><edition><day number of publish date><processid>”. If you enter “no”, only one export file will be created. Note that the EditionID will be included in the export file name only if the publication is publishing by edition.

  Value
  Yes	Separate export files will be created with the file name of “manifest<product/publication><edition><day number of publish date><processid>”
  No	Only one export file will be created.

• 100. What format should be used for the truck manifest export? BCP (Client) This setting determines the format to use when an export file is created for the truck manifest. “Standard” is the normal format. “Syncronex” includes only the R1 and R3 records in the export file. R1 records are for a route’s regular draw, and R3 records are for a route’s TM draw. R3 records will be included only if TM draw exists for the route.

  Value
  Standard	The truck manifest export will use the standard DTI format.
  Syncronex	The truck manifest export will use the Syncronex format.

• 101. Should the rate for single copy routes be appended to the manifest export when using the Syncronex format? BCP (Client) If you use Syncronex, set this Business Rule to “yes” if you want export the single copy rate amounts during each publishing run. These rates will be used with hand-held devices when rating returns applied against the invoice amount due.

  Value
  Yes	Export the single copy rate amounts during each publishing run.
  No	Do not include single copy rate amounts.

• 102. When routes are combined at a drop level, should routes be exported individually in the manifest export file? BCP (Client) If the Business Rule When an account has multiple routes at the same drop point, should they be combined on the bundle, manifest and stacker? is set to “Yes,” you can still export the individual route detail rather than the combined drop information in the R1 records of the truck manifest export.

  Value
  Yes	The truck manifest should export individual routes to the R1 record.
  No	The combined drop should be exported to the R1 record.

• 103. Should the delivery instructions always print on the District Manager report? BCP (Client) This setting enables delivery instructions (i.e., requests) from the occupant record to be printed on the DM report.

  Value
  Yes	Delivery instructions should always print on the District Manager report.
  No	Delivery instructions should not appear on the District Manager report.

• 104. Should an export file also be created for route messages and complaints when running the District Manager report? BCP (Client) The starts, stops, complaints and other messages appearing on the DM Report may be exported to an ASCII file, as governed by this setting.

  Value
  Yes	Export DM Report information to an ASCII file.
  No	No export should take place.

• 105. Should the complete complaint text be exported in a separate field in the District Manager Report export? BCP (Client)

  Value
  Yes	The full complaint text should be exported in a separate field.
  No	Complaint text should not be exported separately.

• 106. If rounding draw at a truck level, should the draw for relay trucks be included in the round draw calculation? BCP (Client) If advance draw is rounded, this setting determines whether parent trucks that drop to children trucks should include the draw for the children trucks in the rounding calculation.

  Value
  Yes	The draw for relays a truck drops to should be included in the round draw calculation.
  No	Only the draw for routes actually dropped by the truck should be included in the round draw calculation.

• 107. Which single copy draw classification should be exported to the stacker separately when exporting Muller Martini or Ferag? BCP (Client) This setting determines the single copy draw type that should be used when exporting the box-out quantity to Muller Martini or Ferag. Single copy draw classes must be set up previously. The default is “NONE”.

• 108. Should bundle tops print for illegal bundles? BCP (Client) This setting determines if bundle tops should be printed for illegal bundles.

  Value
  Yes	Bundle tops will be printed for illegal bundles.
  No	Bundle tops will not be printed for illegal bundles.

• 109. Should the bundle top process create an export file? BCP (Client) This setting identifies whether an export file should be generated when bundle tops are produced. The export file is in addition to the usual print file, and it uses the file map identified in the next setting.

  Value
  Yes	An export file should be generated when running bundle tops.
  No	Only the bundle top report should be generated when running bundle tops.

• 110. Which file map should be used to create the bundle top export? BCP (Client) If you are creating an export file when bundle tops are produced, enter the name of the file map to use.

• 111. Should the route label process create an export file? BCP (Client) This setting identifies whether an export file should be generated when route labels are produced. The export file is in addition to the usual print file, and it uses the file map identified in the next setting.

  Value
  Yes	An export file should be generated when producing route labels.
  No	Only the labels should be generated when running route labels.

• 112. Which file map should be used to create the route label export? BCP (Client) If you are creating an export file when route labels are produced, enter the name of the file map to use.

• 113. Should the previous delivery label process create an export file? BCP (Client) This setting identifies whether an export file should be generated when previous delivery labels are produced. The export file is in addition to the usual print file, and it uses the file map identified in the next setting.

  Value
  Yes	An export file should be generated when producing previous delivery labels.
  No	Only the labels should be generated when running previous delivery labels.

• 114. Which file map should be used to create the previous delivery label export? BCP (Client) If you are creating an export file when previous delivery labels are produced, enter the name of the file map to use.

• 115. When printing bundle tops for each bundle, should the truck bulk key bundle print after the truck's standard bundles? Default Value: Yes This setting determines whether the Bundle Tops create a single bulk key label with the key total for the bulked truck and specifies all routes on the bulked truck.