**Appendixes**

Appendixes to the SPS User\'s Guide cover a variety of subjects of
interest to the SPS user.

Appendix A. Using VMS provides a basic introduction to VMS for the user.

Appendix B. Troubleshooting lists frequently asked questions (FAQs)
asked to SPS Support Center staff and covers other common problems
covered in SPS.

Appendix C. Getting Help details how to contact the SPS Support Center
and lists all of the Help screens within the application.

Appendix D. SPS Menu Flow illustrates the flow from SPS menus (see
Chapter 7) to screens in graphical form.

Appendix E. SPS Bin Assignment Worksheets contains sample copies of all
bin assignment worksheets (introduced in Chapter 10) used for planning
sort programs at one site.

Appendix F. Steps to Creating Any Sort Program provides the list from
Chapter 11 of steps for any sort program.

Appendix G. CIN Labeling Priority, Conditions, and Values

Appendix H. Next Handling

Appendix I. ICS Special Bins provides additional information and
examples on the ICS rej/5D and the ICS ID tag high bins for BCSs.

Appendix J. Other Resources provides a list of other documents that the
user may find helpful.

# Appendix A. Using VMS

Open Virtual Memory System (OpenVMS) is an interactive virtual memory
operating system used on each National Directory Support System (NDSS)
Alpha. The user will enter commands and execute VMS functions with the
Digital Command Language (DCL). These functions include:

-   Finding a loadable

-   Checking the size of a directory

-   Displaying the contents of a file on a terminal and on hard copy

-   Printing files, including SPS Release Notes

    When the user enters commands, the VMS system reads them and
    translates them, enabling functions to be executed. \[This appendix
    will only explain some basic functions for using VMS. For more
    information, see the *NDSS OpenVMS Reference Manual*.\]

## Logging on the VMS System {#logging-on-the-vms-system .unnumbered}

Before logging on to VMS, make certain that the terminal is plugged in
and is on.

At the prompt where the cursor appears, press **\<Return\>** until the
*Username* prompt appears. Enter a user name and press **\<Return\>**.
The user name should consist of 1 to 12 characters.

The system will prompt the user for a password. Enter a password and
press **\<Return\>**. The password should consist of 1 to 31 characters.

If the user logs on successfully, the DCL prompt (\$) will appear. The
DCL prompt (\$) is necessary for the user to perform an action in VMS.

## Understanding a DCL Command {#understanding-a-dcl-command .unnumbered}

The user will execute VMS functions with DCL commands. DCL commands have
a structure in which several parts fit together in a specific order to
make a command. The following explanations and examples help to define
the elements that can be used to make up a DCL command. In each example,
the element being discussed is printed in bold.

Verb In the command line, the verb specifies the action to be taken.

\$ **TYPE**

Keyword A keyword can be used in conjunction with the verb to further
specify the action to be taken. Each command has its own set of keywords
that are recognized by the system.

\$ SHOW **DEFAULT**

Parameter The parameter receives the action of the verb. A parameter is
a value such as file specifications, queue names, logical names, or
other values.

\$ TYPE **SCF_LIST.DAT**

Qualifier A qualifier describes or modifies the action taken by the
verb. A qualifier in a command line is preceded by a slash (/).

\$ TYPE/**PAGE** SCF.LIST.DAT

Qualifier Value Sometimes a qualifier may contain a value. Some
qualifiers accept one or more values. This value assigns a specific
quantity to the qualifier.

\$ PRINT/COPIES**=2** SPS054_RELEASE_NOTES.DOC

### Rules for Constructing a DCL Command {#rules-for-constructing-a-dcl-command .unnumbered}

When constructing a DCL command, the user must follow several rules in
order for the system to acknowledge the commands.

-   The user may use uppercase or lowercase letters when entering a DCL
    command.

-   Command verbs, command options, and parameters should be separated
    by one or more spaces. A space is not required between the qualifier
    and the command verb, parameter, or element being referenced.

-   A qualifier always begins with a slash (/), separating qualifiers
    from command verbs and parameters.

-   A comma should be used to separate elements in a parameter list.
    (For more information, see the Using the Print Command section of
    this appendix.)

## Controlling the Flow of Information in VMS {#controlling-the-flow-of-information-in-vms .unnumbered}

The \<Ctrl\> key can be used in combination with other keys to help
control the flow of the VMS system. With these key combinations, the
user can return to the DCL prompt, stop and start the flow of scrolling
text, and use other means to control the flow of information on the VMS
terminal.

For these control sequences to work, hold down the **\<Ctrl\>** key and
press the other key in the sequence. These key combinations are as
follows:

\<Ctrl C\> Pressing **\<Ctrl C\>** will cancel an image and return the
user to the system prompt (\$).

\<Ctrl O\> This is a toggle key to stop and restart the display of
output to the terminal screen. Pressing **\<Ctrl O\>** does not control
what output appears on the screen, but it does stop the output from
continuing and displays the output at its current position. With this
key combination, the user can skip over large amounts of information in
a large file.

\<Ctrl S\> This control sequence will pause the information scrolling on
the screen. This allows the user to stop a long display of information
so that the user can read it.

\<Ctrl Q\> This key combination restarts the display information on the
terminal screen once it has stopped. The information displayed will
continue scrolling from the point it was stopped.

\<Ctrl R\> Pressing **\<Ctrl R\>** displays the current DCL command
line.

\<Ctrl T\> This control sequence displays a status line for the process.
This is useful to see if the process is executing or if it has paused.

\<Ctrl Y\> This key combination will allow the user to interrupt the
image and return to the system prompt (\$). To resume the image process
use the CONTINUE command.

Depending on the keyboard being used, the user can also stop and restart
the display information by pressing either **\<F1\>** or the **\<Hold
Screen\>** key.

## Accessing a Directory {#accessing-a-directory .unnumbered}

When accessing a directory, the user must set that directory as the
default directory. To access any directory, the user must know the
system's directory structure. (For more information about the directory
structure, see a local DAS or the *NDSS OpenVMS Reference Manual*.) Once
a directory is set as the default, the user can move through the
directory by accessing subdirectories and files within it.

To access a directory, the user must use the SET DEFAULT, also
abbreviated SET DEF, command. Once a directory has been set, the user
can view the subdirectories or files in it by using the DIRECTORY, or
DIR, command at the DCL prompt (i.e., \$ DIRECTORY) and pressing
**\<Return\>**. The directory command provides the file name, type, and
version number for each file displayed. For example, to set the default
directory to the location where SPS stores the machine loadables the
user would type, \$ set def DSPS:\[SPS.loadable\]

-   The following diagram shows an example of a directory structure for
    the DSPS device, which contains the SPS directory (see Figure A-1).

![](media/image1.emf){width="5.990277777777778in"
height="5.101388888888889in"}

Figure A-1. Sample Directory Structure (for DSPS Device)

In this example, the DSPS device is the physical object on which files
are stored or written. The DSPS device contains the SPS directory,
which, serves as the root for several subdirectories. The subdirectories
displayed in this diagram (DATA, DOC, LABEL, LOADABLE, and LOG) are only
a few of the subdirectories in the SPS directory. Additional
subdirectories not pictured in this diagram (e.g., MECH.DATA) let the
user access sort program information for the various MPE.

Each subdirectory contains numerous files, some of which may be
contained in additional subdirectories. Examples from the diagram (refer
back to Figure A-1) include the following:

-   DATA.DIR provides access to numerous files containing data for SPS.

-   DOC.DIR lets the user access Postscript versions of SPS documents.

-   LABEL.DIR contains a subdirectory, DATA.DIR, where label files are
    located.

-   LOADABLE.DIR holds loadables created from SPS sort programs.

-   LOG.DIR gives access to log files.

    (Sections which follow in this appendix detail how to access the
    loadable, label file, and sort program directories, as well as how
    to print Release Notes. For more information on data files, see
    Chapter 6. For more information on log files, see Appendix B.)

### Accessing the Loadable Directory {#accessing-the-loadable-directory .unnumbered}

Loadables created from SPS sort programs are saved in the LOADABLE
subdirectory (\$ SET DEF DSPS:\[SPS.LOADABLE\]) below the SPS directory,
which can be found in the DSPS device. The user can view the list of
loadables that exist in SPS by accessing the LOADABLE subdirectory. This
command will change the default directory to the DSPS: \[SPS.LOADABLE\]
directory. To list the loadables that have been created, enter DIR at
the DCL prompt.

### Accessing the Label File Directory {#accessing-the-label-file-directory .unnumbered}

All label information populated in the Label Editor when a sort program
is created is saved in a label file. The user can list these label files
by accessing the LABEL subdirectory of the DSPS device's SPS directory.
To access these files, enter SET DEF DSPS:\[SPS.LABEL.DATA\] at the DCL
prompt and press **\<Return\>**. Once the correct subdirectory has been
accessed enter DIR at the DCL prompt and press **\<Return\>**.

### Accessing the Sort Program Directories {#accessing-the-sort-program-directories .unnumbered}

When sort programs are created for the various MPE the information is
stored in the SPS directory of the DSPS device. The sort program file is
saved in the directory path corresponding with the machine type defined
by the sort program name. The MPE and its corresponding directory path
are listed in the table below.

+------------------------+------------------+--------------------------+
| **Mail Processing      | #####            | ###                      |
| Equipment**            | ### Machine Type | ##### Corresponding Path |
+------------------------+------------------+--------------------------+
| FSM                    | A and B          | DSPS:\[SPS.MECH.DATA\]   |
+------------------------+------------------+--------------------------+
| FSM/BCR                | O                | DSPS:\[SPS.BCS.DATA\]    |
+------------------------+------------------+--------------------------+
| MLOCR                  | S, T, W, X       | DSPS:\[SPS.MLR.DATA\]    |
+------------------------+------------------+--------------------------+
| MPBCS                  | H                | DSPS:\[SPS.BCS.DATA\]    |
+------------------------+------------------+--------------------------+
| MPBCS/OSS              | R                | DSPS:\[SPS.MPB.DATA\]    |
+------------------------+------------------+--------------------------+
| DBCS/OSS               | P                | DSPS:\[SPS.DSS.DATA\]    |
+------------------------+------------------+--------------------------+
| DBCS                   | Q and V          | DSPS:\[SPS.DBC.DATA\]    |
+------------------------+------------------+--------------------------+

To access the different directories the user should first enter the SET
DEFAULT command and then enter the directory path. For example, to view
the sort program file for the FSM/BCR type SET DEFAULT
DSPS:\[SPS.BCS.DATA\] at the DCL prompt.

The user can see what directory is currently the default at any time by
entering SHOW DEFAULT at the DCL command (i.e., \$ SHOW DEFAULT) and
pressing **\<Return\>.**

### Displaying the Size of a Directory 

The DIRECTORY command can be used in conjunction with the /SIZE
qualifier to find out the size of a directory or file:

-   To find out how large a directory is, enter DIRECTORY/SIZE/TOTAL at
    the \$ prompt and press **\<Return\>**. The number of files and size
    of the directory in blocks will display.

-   To discover how large each file is within the directory, enter
    DIRECTORY/SIZE at the \$ prompt. When the user presses
    **\<Return\>**, a list of each file and its size will scroll down
    the screen.

The size of a directory does not affect the system's performance, but
users should keep directories clean by deleting old files, such as old
sort programs and loadables.

### Changing Directories Within a Device

The user can change the default directory or subdirectory at any time by
using the SET DEFAULT command. At the DCL prompt, enter the SET DEFAULT
command followed by the name of the directory to which the default
should be changed. For example, if the current default directory is
DSPS: \[SPS.LOADABLE\] and the user wants to change the directory to
DSPS: \[SPS.DATA\], the user would enter SET DEFAULT \[SPS.DATA\] at the
DCL prompt.

If a default device or directory have been changed, the user can still
return to the default device or directory set at the time that the user
logged on to VMS. To do this, use the SET DEFAULT command and specify
the LOGIN directory (i.e., \$ SET DEFAULT SYS\$LOGIN). the device and
directory accessed at the time the user logged on will be used.

## Displaying the Contents of Files

The user can display the contents of a file in two ways, by using the
TYPE command or the PRINT command. The TYPE command displays the
contents on the terminal, while the PRINT command will send the contents
of the file to the printer.

### Viewing Files on the Terminal

The user can display the contents of any text file on the screen by
using VMS's TYPE command. Enter the TYPE command at the DCL prompt,
followed by the file name (i.e., \$ TYPE FH22033U.STF). Press
**\<Return\>** and the contents of that file will be displayed on the
screen. The TYPE command cannot be used to view the contents of binary
files, which includes .ZIP Code files and loadables (.BBF, .EBF, .FBF,
etc.).

The user can also display the contents of the file one page at a time by
adding the /PAGE qualifier to the command (i.e., \$TYPE/PAGE
FH22033U.STF).

To display all versions of a specific file, use the asterisk (\*)
wildcard (i.e. \$TYPE FH22033U.STF,\*).

#### Displaying the .STF File

The contents of an .STF file, which is located in the .LOADABLE
directory, can be displayed through the TYPE command.

To access the .STF file, set the default to the .LOADABLE directory
(i.e., \$ SET DEF SPS\$LOADABLE) and enter the file name at the next DCL
prompt (i.e., \$ FH22033U.STF) and press **\<Return\>**. The contents of
the file will scroll down the screen.

### Printing Files

The user can print files using the PRINT command. This command sends a
copy of the file to the printer. In order to print a file, the user must
at least have read access to the file. This means that the file is on a
disk and in a directory which the user can read.

#### Printing a Single File

To print a single file, enter the PRINT command at the DCL prompt and
the file name (e.g., \$PRINT DPSB_REPORT). Press **\<Return\>** and the
file will be routed to the printer.

#### Printing Several Files

To print more than one file, enter the PRINT command at the DCL prompt
and the file names as a list separated by commas (e.g., \$PRINT
DPSB_REPORT, TEMP.LIST, TEST.COM). Press **\<Return\>** and all files in
the list will be routed to the printer.

#### Printing a Copy of the Release Notes

The SPS Release Notes are contained in a PostScript file in the DOC
directory. To print a copy of the SPS Release Notes from the VMS system,
the postscript qualifier must be used with the print command. The
PostScript file will use a special printing queue. To print a copy of
the Release Notes:

1.  Set the default directory to SPS.DOC (i.e., \$ SET DEFAULT
    \[SPS.DOC\]). Press **\<Return\>**.

2.  Enter PRINT/QUEUE=POST and the file name (e.g., \$ PRINT/QUEUE=POST
    SPS060_RELEASE.PS). Press **\<Return\>** and the PostScript file
    will print.

When uncertain as to which documents are available in PostScript format,
the user can enter the DIR command at the DCL prompt (\$ DIR) and press
**\<Return\>**. The files available in the .DOC directory will display.

#### Printing More Than One Copy of a File

When printing more than one copy of a file, the user should use the
PRINT command with a COPIES=*n* qualifier. In the COPIES=*n* qualifier,
*n* represents the number of copies. (The user does not have to enter
this qualifier if only one copy is being printed.) For example, if the
user wanted to print two copies of the SPS 6.0 Release Notes, the
correct command would be \$PRINT/COPIES=2 SPS060_RELEASE.PS.

## Getting Help

While in VMS, the user can obtain online information on how to use the
system with the HELP command. Enter HELP at the DCL prompt (e.g., \$
HELP) and press **\<Return\>**.

This will allow the user to view information about a DCL command or
topic. The prompt, *Topic?* will appear on the screen. The user can add
additional information at this prompt to find out more about a specific
topic. At the *Topic?* prompt, enter the desired topic (e.g., *Topic?*
PRINT) and press **\<Return\>**. Information about the topic will be
displayed on the screen.

A description of a qualifier associated with a command can be viewed by
adding the desired qualifier after the command. For example, to get a
description of the /PAGE qualifier for the PRINT command enter \$ HELP
PRINT/PAGE.

The user can view more detailed information about using the Help
function by typing in the word INSTRUCTIONS while in Help and pressing
**\<Return\>**. A HINTS feature is also available to the user for
displaying detailed information about a topic. To use the HINTS feature
type HINTS at the DCL prompt and press **\<Return\>**. This feature will
display 14 general topics, which assist the user while in VMS. Select a
topic by typing the name at the prompt and a list of commands associated
with that topic will be displayed.

## Logging Out of VMS

The user can end a VMS session at any time when the DCL prompt (\$) is
present by typing LOGOUT, or, more simply, LOG, and then pressing
**\<Return\>**. The user can only log out at the DCL prompt (\$). VMS
cannot be exited while the user compiles or executes a program, uses a
test editor, or runs a utility.

Once the user logs out, the session will end and a prompt will appear on
the screen informing the user of the date and time of the logout. The
user should log out when finished using VMS. This will prevent
unauthorized users from accessing the system and will make resources
available to the system.

# Appendix B. Troubleshooting

This appendix includes two sections of information in order to provide
the user with answers to questions about the Sort Program System (SPS).
The first section contains frequently asked questions (FAQs) asked by
users about letter mail processing in SPS. Delivery point sequencing
(DPS) and flat mail processing operations will not be covered in this
appendix. However, additional topics can be found through the Q and A
log file located on the United States Postal Service (USPS) web site. To
access these Q and A files, type in the web site address **http://
207.226.140.23/welcome.html**.

The question and answer topics covered in this appendix consist of the
following:

-   Single-pass sort programs

-   SPS sort program creation

-   SPS loadables

-   SPS files/ranges/zones/sequences

-   SPS special bins

-   ZIPMOVE

    Additional question and answer topics can be found in the Q and A
    log file, which can be accessed through the USPS web page.

    The second section contains basic information about SPS. This
    information is provided as a reference for users. This information
    covers the following categories:

-   Log files

-   Carrier Sequence Bar Code Sorter (CSBCS) log files

-   Zone size

-   Too many carriers for a sort program

-   Latest CIN list in SPS

## Frequently Asked Questions {#frequently-asked-questions .unnumbered}

### Single-pass Sort Programs {#single-pass-sort-programs .unnumbered}

**Question 1:**. Can a refresh tape containing delivery point file (DPF)
data be used to update a single-pass sort program?

**Answer:** No, it needs the National Directory Support System (NDSS)
for updating a single-pass sort program. However, it can be used for
two-pass and DPS sort programs if DPF is imported.

### SPS Sort Program Creation  {#sps-sort-program-creation .unnumbered}

**Question 1:** The user created a new LV sort program, holding out
non-DPS carriers in the First Pass. However, the user is not prompted
for how many non-DPS carrier bins or for putting them at the beginning
or the end.

**Answer:** The carrier files are older than v4.5. The user needs to
import new files.

**Question 2:** The user deleted a version A sort program and created a
new sort program. After an update, when accessing the SPS Editor, the
new program retains the old mapping that does not allow editing.

**Answer:** The user should delete the version U sort program as well
and create the sort program from scratch.

**Question 3:** The sort program will not build.

**Answer:** Check the Zone Table to see if the zone is there.

**Question 4:** When loading an old sort program, version U is good, but
version A is bad.

**Answer:** The user should copy the U version to the A version and then
the user can change it.

**Question 5:** The sort program is too large to build and it has only
one zone.

**Answer:** Combine the boxes and reduce the size of the sort program.

**Question 6:** How does a user build an international sort program?

**Answer:** Talk to the local Address Management System (AMS) office and
ask them to provide the sectional center facilities (SCFs) needed. Next,
place the SCFs in the editor by hand.

**Question 7:** If the user mapped a program and want to go back in and
re-map the program, how is that done?

**Answer:** A user has to rebuild the sort program to re-map a program.

**Question 8:** Does a switch exist in SPS to activate the certified
mail detector (CMD) bin?

**Answer:** No, but to activate the CMD bin, the user should choose a
bin other than the residue bin, which is the default.

**Question 9:** A user has a Delivery Bar Code Sorter (DBCS) Phase IV.
How many mechanical reject bins need to be used: three or four?

**Answer:** Use four, one for each tier.

**Question 10**: Can a user who builds an FV sort program assign a CMD
bin?

**Answer:** Yes. Assign the CMD bin to a separate bin; this is different
from the residue bin.

### SPS Loadables {#sps-loadables .unnumbered}

**Question 1:** The sort program will not convert to .EBF.

**Answer:** The user should create a new label file. This usually
happens when a program with a greater number of bins is copied to a
program with a fewer number of bins.

**Question 2:** The user gets an error reading,
\"SPS\$MLOCR_B:SRTPLN.L101 file not found.\"

**Answer:** The user should check the owner of the file. If it is
\[NDSS,ML\], change to \[NDSS_UIC,NDSS\].

**Question 3:** All of the loadables are corrupted. How can these be
fixed?

**Answer:** Delete the bad .EBF files. Then go into the plan, press
**\<Do\>**, and create new loadables.

**Question 4:** The user has a problem with converting an Input
Subsystem (ISS) sort program. The non-POSTNET mail is going to the
mechanical reject bin.

**Answer:** The user should build an A\* program to create the loadable
and activate some special bins.

**Question 5:** Does the Option 3 (single plan) update create a new
loadable?

**Answer:** No. This option only updates the U version of the sort
program.

**Question 6**: The user cannot add Alpha plans to the pick list.

**Answer:** The user should enter the loadable extensionthe whole
loadable name plus the extension (Example: JTV.FBF) by hand.

### SPS Files/Ranges/Zones/Sequences {#sps-filesrangeszonessequences .unnumbered}

**Question 1:** How does a user resequence the files for a zone?

**Answer:** The user cannot resequence files for a zone. Ask the local
AMS person to resequence the files.

**Question 2:** Can a user delete more than one sort program at a time
from the VMS \$ prompt?

**Answer:** No. The user should go into SPS and delete the sort programs
one at a time.

**Question 3:** The Refresh tape has some changes that are not wanted.
How can a user get the old files back?

**Answer:** Reload the old refresh tape.

**Question 4**: A sort program has some ZIP Codes that are not in its
Zone Table.

**Answer:** Check for translations in the ZIPMOVE file.

**Question 5:** How many ranges are allowed in an AS (outgoing MLOCR-B
44) sort program?

**Answer:** Ten thousand (10,000) ranges are allowed.

**Question 6:** The user tried to merge sort programs to a U version
file.

**Answer:** If the output sort program version from the merge already
exists, this version gets incorporated. The user should use a version
for the output sort program name.

**Question 7:** The residue for a zone in sort program 1 is going to a
different residue bin for another zone in sort program 2. Why?

**Answer**: The zone in sort program 1 has a ZIPMOVE translation that
translates to a zone in sort program 2.

**Question 8:** What mail goes into the no code bin?

**Answer:** The mail with a bar code that is not decoded correctly (or
is unable to be read by the machine correctly) goes into the no code
bin.

**Question 9:** For an A\*ISS sort program, the 5-digit mail is going to
other bins, as well as the A\*. The user did assign ranges to other bins
and deleted them; now, the mail is in unassigned bins. Why?

**Answer:** The A\* 5-digit residue flag should be set to **N**. Also,
the user should assign the ranges to a bin in the SPS Editor.

**Question 10:** How can a user get the same zone to update for the
CSBCS, which is a remote site, and the DBCS, which is local?

**Answer:** Create a new station with the same zone and make one R and
the other one L.

### SPS Special Bins {#sps-special-bins .unnumbered}

**Question 1:** The user received a printout, *SSI files full access not
available*. Why?

**Answer:** Another user uploaded the files from the machine and changed
the ownership of the files. The user should change the ownership to SPS
to fix it.

**Question 2:** A user goes into the Special Bin Editor and places a 005
in the no code bin; when the number reappears, it has returned to the
default of 001. Why?

**Answer:** Press **\<Return\>** after entering 005 for the no code bin
assignment

**Question 3:** Can a CMD bin be added after a sort program has already
been created?

**Answer:** No, it needs to be included during the creation of the sort
program.

**Question 4:** The no code and no read bins do not show up in the sort
program.

**Answer:** Check the .STF file. These are default values

**Question 5:** The user cannot assign the no code bin.

**Answer:** Check the .STF file. If the bin is also assigned to
something else, this bin will not appear in the SPS Editor, but will
show up in the .STF file assigned to the correct bin.

### ZIPMOVE {#zipmove .unnumbered}

**Question 1:** The sort program has multiple zones that are not in the
zone table.

**Answer:** This is not a problem; ZIPMOVE is translating the old zone
to the new zone and both are showing up in the sort program.

**Question 2:** The sort program has a duplicate ZIP +4.

**Answer:** A) The user has the old zone in the Zone Table. With
ZIPMOVE, the user only needs new ZIP Codes because ZIPMOVE translates
the old zones into the new zones.

B\) If the user has a partial ZIPMOVE for a zone and needs to use the
old zone in the zone table, then go into the Sequence Database
(Two-Pass) Editor and choose Option **2**, Display/Edit Sequence
Database 11-digit. Find the old zone and make sure the carriers that are
**not** supposed to be there are not there or do not have an asterisk
(\*). To remove an asterisk, highlight a carrier and press \<**Ctrl
A**\>.

**Question 3:** Carriers are not showing up in the sort program.

**Answer:** Look in the Sequence Database (Two-Pass) Editor and choose
option **2**, Display/Edit Sequence Database-11-digit. Look for the
missing carriers in the old and new zones. If the carriers are in
neither zone, call the local AMS. If carriers are in the zones, asterisk
(\*) them using **\<Ctrl A\>**.

**Question 4:** If a whole zone is moved to a new zone, does the old
zone have to be in the Zone Table?

**Answer:** No, it does not.

**Question 5:** The sort program contains ranges that should not be in
the program.

**Answer:** There are translations in the ZIPMOVE file. If these are not
required, have a local Density Analysis Specialist (DAS) rename the file
and let AMS know.

## Basic Information About SPS {#basic-information-about-sps .unnumbered}

This section contains basic information about SPS and can be used as a
reference by the user. The topics covered are important areas within SPS
and are often areas that users want to know more information about.

### Log Files {#log-files .unnumbered}

Log files are created every time a communications action is initiated
between SPS and the Delivery Unit Computer (DUC) or CSBCS. A log file
will be created each time one of the following communications actions is
requested:

-   Pending files are uploaded from the DUC to SPS

-   SSI files are downloaded from SPS to the DUC

-   When a End-of-Run (EOR) Report is uploaded automatically

    If a site manually requests one of the above actions then a server
    log file will be created. All transaction information that is
    retrieved through a manual operation will be saved in the server
    file.

    The log file contains information on specific transactions. This
    information includes:

-   Success or failure of the transmission

-   Start and end time of the transmission

-   Date of the transmission

-   Any greetings messages sent by NDSS

If any type of error occurs during the transaction this file will
indicate an error message. The latest information uploaded or downloaded
will be the current information in the log file. For example, if a site
uploads pending files to SPS at 10:30 a.m., this information will be
saved in the log file. However, if this site decides to download SSI
files at 12:00 p.m., then the SSI file data will overwrite the pending
file data, in the station's holding directory, created hours before. If
EOR data is then downloaded, this data will overwrite the SSI file data.
The EOR data will be held in the station's holding directory until
another download in performed.

The user may view log file information through VMS. These files are
located in the SPS directory under the LOG subdirectory, \[SPS.LOG\].
(For more information about accessing log files through VMS, see
Appendix A.)

### CSBCS Log Files

Three log files are created when CSBCS sites request the download of SSI
files through the Sunday download. One log file contains all transaction
information, but is very complex. The user should see a local DAS to
view this information.

Another log file created is modem_batch_log.dat. The user can access
this log file in order to view transaction information. For example,
this file will show the user whether or not the modem connection was
successful. The information in this log file will be printed to the
printer when requested to do so by the user.

A third log file, scheduler.log can also be accessed by the user in
order to view transaction information. This file will show the user if a
transaction was successful or unsuccessful followed by details about the
transaction.

The Sunday download is included in the weekly Refresh and performed
every Sunday at a given time. Each Sunday the previously created log
files will be overwritten with new log file information. The log files
created on Sunday will remain in the station's directory until the
following Sunday when files are again downloaded through the weekly
Refresh.

### Zone Size

Zones provide important information for creating SPS sort programs. The
zone will determine what contents are provided for building the sort
program. The size of the zone can affect how a sort program is created.

If a sort program is too large then there may not be enough bins on the
machine to sort all of the mail. When instances like this occur, the
sort program developer can break up the sort program and sort mail on
two different sort programs for one zone.

If a site contains small zones then several zones can be combined into
one sort program. This will help reduce the number of sort programs run
and will increase the efficiency of the sorting machine. This eliminates
the need for sites to merge sort programs. The user can add up to 20
zones in the Sort Program Zone Table. All mail levels and automated
machines (Machine Types H, O, P, Q, R, S, T, U, V, W, and X) can be used
when using sort programs with up to 20 zones. Mechanized Machine Types A
and B can also be used for sort programs containing up to 20 zones.

### Too Many Carriers for a Sort Program

Zones for incoming secondary sort programs contain a specific number of
carriers and at times the number of carriers exceeds the number of bins
in a sort program. If the user generates the sort program by not mapping
carriers and the number of carriers exceeds the machine capacity, the
excess carriers will be placed together in the last bin used on the
machine and that bin will be labeled *Multiple Carriers* in the Bin
Stack Label field. A message will appear briefly on the screen during
auto generation, informing the user that the excess carrier IDs and
associated ZIP Codes were placed in the last bin. The log file sent to
the printer also has the same message.

SPS looks at the zones in the Sort Program Zone Table to determine which
carriers and box sections to put on the sort program and arranges the
carriers around the machine in order in automated sort programs.

The user may also choose to map carriers for a sort program. In this
instance the user can assign combine carriers in bins which they choose
or leave carriers out of a sort program and place them in another sort
program. The final sort program will show *Multiple Carriers* in the Bin
Stack Label field if several carriers are assigned to one bin. These two
features make it very easy to make mistakes. Starting with a written
list or assigning carriers in a systematic way can help avoid multiple
assignments and scrolling through the list before exiting can identify
missed carriers.

### Latest CIN List in SPS

The most recent content identifier number (CIN) values being used by SPS
can be accessed through the Label Editor. By pressing **\<F7\>** the
user can view a list of available CINs. SPS will automatically populate
the CIN column of the Label Editor with CIN values based on the CIN
values and descriptions in this table. The use can print a copy of this
list by pressing **\<F18\>** while the CIN Table is displayed on the
screen.

# Appendix C. Getting Help

This appendix details two methods of getting help with the Sort Program
System (SPS): the SPS Support Center and SPS Help Menus.

## SPS Support Center

The SPS Support Center is available to answer questions concerning SPS.
Support Center personnel can be reached at (703) 698-5060 weekdays from
5:30 a.m. to 7:30 p.m. EST. The following is a list of information that
SPS Support Center personnel will need to understand and solve a problem
as quickly as possible. Please have this information ready before
calling.

1.  *Name, telephone number, and site*

    Have name, telephone number, and site location, including the state.

2.  *Problem previously reported*

    Has this problem been reported previously? If so, have the date and
    to whom it was reported. Keep a record of the person to whom problem
    was reported should the user need to report the problem again. Also,
    check the status of the problem.

3.  *Problem - question*

    Have all the aspects of the problem clear so that nothing will be
    left out. If any aspect of the problem is not told to the support
    person, he or she will not be able to help as efficiently as
    possible.

4.  *Start of the problem*

    When did this problem start occurring? Is this the first time or has
    it happened before?

5.  *SPS version*

    In which version of SPS is the problem occurring?

6.  *SPS username/password*

    This information is vital. Have the username and password for SPS
    ready to give to the support person.

7.  *Site TelNet information, IP address, or modem number*

    Have the site TelNet information (e.g., Tampa, FL = TAF 205), IP
    address, or modem number.

8.  *Sort program name*

    Have the sort program name, as well as the zones in the program,
    including old and new zones if ZIPMOVE. Also have the loadable name
    available if it is different.

9.  *Station name, password, ZIP, and modem number*

    Give the station name, password, ZIP Code, and modem number for
    Station Input Editor (SIE) problems.

10. *CSBCS/DUC*

    Let the support person know if the problem is at a Carrier Sequence
    Bar Code Sorter (CSBCS) or Delivery Unit Computer (DUC) site.

11. *ZIP +4 and DPS digits*

    Have ready the ZIP Code, 4-digit add-on, and delivery point
    sequencing (DPS) digits, as well as the ranges that are involved in
    the problem.

12. *Example*

    Give an example of the problem, if possible. It will help the
    support person have a better understanding of the problem.

13. *Other details*

> Have ready any other details that may assist the support person in
> understanding and solving the problem. For example, note any errors
> displayed on screen or in a log file.

## Help Menus

All of the major screens in SPS contain Help Menus. These menus list the
function keys available to the user at the screen where the menu is
accessed. Some Help Menus also define fields contained on the screen. To
access a Help Menu, press **\<Help\>** when at a screen where a Help
Menu exists.

### Zone Table Help Menu

To set up a sort program in the Zone Table, select Option **1**, Sort
Program Zone Table, at the SPS Main Options Menu.

\<Return\> Pressing this key allows the user to move the cursor through
the Zone Table's fields (e.g., from the Sort Program Name field to the
Zones Within Sort Program fields).

\<Do\> Executes the highlighted option (\[ADD\], \[CHANGE\], \[DELETE\],
or \[EXIT\]) on the option bar at the bottom of the screen.

\<Backspace\> Normally, this key erases the preceding character and
moves the cursor to the left. However, if the user presses it at the
beginning of a field, the entire field will be erased.

\<Remove\> Erases all existing data on the screen (i.e., any information
the user has entered).

\<Right Arrow\> Allows the user to move right on the option bar at the
bottom of the screen and highlight an option (\[ADD\], \[CHANGE\],
\[DELETE\], or \[EXIT\]).

\<Left Arrow\> Allows the user to move left on the option bar at the
bottom of the screen and highlight an option (\[ADD\], \[CHANGE\],
\[DELETE\], or \[EXIT\]).

\<Help\> Displays the Help Menu for the Zone Table.

\<F17\>/

\<Up Arrow\> Both of these keys will allow the user to move to the
previous field.

\<F18\> Generates a hard copy of the Zone Table file on the system
printer.

\<F19\> Generates a hard copy of the present screen on the system
printer.

\<F20\> Press this key to access the Zones Within Sort Program browser.
This browser lists all sort programs entered into the Zone Table and the
zones within each one.

\<PF4\> Repaints the screen display. This is used to clear the screen
when it becomes garbled.

\<PF1 C\> This key combination allows the user to display and edit the
carrier list, which is generated when a DPS sort program is being
created.

\<Tab\> Press this key to move to the field to the right when entering
zones in the Zones Within Sort Program fields.

### Zones Within Sort Program Browser Help Menu

The user can access the Zones Within Sort Program browser by pressing
**\<F20\>** at the Zone Table. Press **\<Help\>** to view a Help Menu
for the browser.

\<Up Arrow\> Move up one line

\<Down Arrow\> or \<Return\> Move down one line

\<Prev Screen\> Move up one "page" of the file

\<Next Screen\> or \<Spacebar\> Move down one "page" of the file

\<PF1 B\> or \<B\> Move to last line in file

\<PF1 T\> or \<T\> Move to first line in file

\<Find\> Search for an item in the file. A *Search for* prompt will
appear when this key is pressed. Enter the item being searched for in
the box provided and press **\<Return\>**. If the browser lists the item
more than once, the first occurrence of the item following the present
location of the cursor will be found.

\<Left Arrow\> Press this key to scroll the browser 20 spaces to the
left.

\<Right Arrow\> Press this key to scroll the browser 20 spaces to the
right.

\<F18\> Print the entire listing of sort program records, not just the
data visible on the screen.

\<F19\> Print the current screen.

\<F11\> or \<F14\> Exit the browser and return to the Zone Table.

### Edit Sort Program Help Menu

To edit or create a sort program, select Option **2**, Edit/Create Sort
Program, at the SPS Main Options Menu. At the Edit Sort Program screen,
the user must enter the sort program name (mail level + machine type +
zone + version).

\<Return\> This key allows the user to move the cursor through the
fields of the Edit Sort Program screen.

\<Do\> Executes the highlighted option (\[EDIT\] or \[EXIT\]) on the
option bar at the bottom of the screen. If the user presses **\<Do\>**
when **\[EDIT\]** is selected, the sort program information entered into
each field of the Edit Sort Program screen will be accepted and the user
will enter the SPS Editor.

\<Backspace\> Normally, this key erases the preceding character and
moves the cursor to the left. However, if the user presses it at the
beginning of a field, the entire field will be erased.

\<Remove\> Erases all existing data on the screen (i.e., any information
the user has entered).

\<Right Arrow\> This key moves the cursor to the right on the option bar
at the bottom of the screen so the user can select a particular option
(\[EDIT\] or \[EXIT\]).

\<Left Arrow\> Moves the cursor to the left on the option bar at the
bottom of the screen so that the user can highlight a particular option
(\[EDIT\] or \[EXIT\]).

\<F17\>/

\<Up Arrow\> Allows the user to move to the previous field.

\<F19\> Generates a hard copy of the screen on the system printer.

\<PF4\> Repaints the screen display. This is used to clear up the screen
when it becomes garbled.

\<Help\> Displays the Help Menu for the Edit Sort Program screen.

### RBCS A\* Bin Editor Help Menu

Having entered the sort program name at the Edit Sort Program screen,
the user will need to enter values in the Special Bin Editor and other
bin assignment screens. Next, sort programs for a Multiline Optical
Character Reader (MLOCR; Machine Types S, T, W, X) with an Input
Subsystem (ISS) attached will have an RBCS A\* Bin Editor where users
can assign ranges of mail with partially resolved images to Remote Bar
Coding System (RBCS) bins.

\<Insert Here\> Adds a blank line for the user to insert information.

\<Remove\> Erases the ISS bin assignment(s) from the screen.

\<Next Screen\> Scrolls the screen to the next page of data, allowing
the user to view additional ISS assignments.

\<Prev Screen\> Pressing this key returns the user to the previous page
of data.

\<Down Arrow\> Positions the cursor on the next line of data.

\<Up Arrow\> Pressing this key positions the cursor on the previous line
of data.

\<Do\> Saves the ISS bin assignments made by the user and exits out of
the RBCS A\* Bin Editor.

\<F11\> Exits out of the RBCS A\* Bin Editor without saving the ISS bin
assignments.

\<F18\> Pressing **\<F18\>** prints the ISS bin list on the system
printer.

\<F19\> Prints the screen currently visible to the user on the system
printer.

\<PF1 B\> This key combination moves the cursor to the bottom of the ISS
bin list.

\<PF1 T\> Moves the cursor to the top of the ISS bin list.

\<PF4\> Repaints the screen. This is used to clear up the screen when it
becomes garbled.

\<Return\> Pressing **\<Return\>** positions the cursor on the next line
of data.

\<F17\> Returns the cursor to the previous field of data.

\<Help\> Displays the Help Menu for the RBCS A\* Bin Editor.

### Carrier Mapping Table Help Menu

When creating incoming secondary (INS) sort programs, the user can
assign carriers to bins manually through the Carrier Mapping Table
instead of having bin assignments automatically generated. The option to
access the Carrier Mapping Table will appear before the user enters the
SPS Editor.

\<Next Screen\> The user can press this key at two places within the
Carrier Mapping Table: the carrier mapping window and the list of
residue and Business Reply Mail (BRM) bins. At both places, pressing
this key moves the cursor to the next group ("page") of bins.

\<Prev Screen\> The user can press this key at two places within the
Carrier Mapping Table: the carrier mapping window and the list of
residue and BRM bins. At both places, pressing this key moves the cursor
to the previous group ("page") of bins.

\<Find\> Allows the user to enter a search string in order to look for
desired information within the carrier mapping window.

\<PF1 Find\> Repeats the last attempted search so the next occurrance of
a string can be found.

\<Down Arrow\> Pressing the **\<Down Arrow\>** in the carrier mapping
window moves the cursor to the next carrier bin. This key can also be
used to move one line at a time through the residue and BRM bins to the
left of the carrier mapping window.

\<Up Arrow\> The user can press this key at two places within the
Carrier Mapping Table: the carrier mapping window and the list of
residue and BRM bins. At both places, pressing this key moves the cursor
to the previous bin.

\<F10\> Pressing **\<F10\>** from the carrier mapping screen displays
and removes the unused bin list from the screen.

\<F18\> Pressing this key will print the entire carrier list on the
system printer.

\<F19\> This key will print the information on the current screen on the
system printer.

\<PF1 B\> This key combination will put the user at the bottom of the
carrier list in the carrier mapping window.

\<PF1 T\> Positions the cursor at the top of the carrier mapping window.

\<PF4\> Repaints the screen. This key is used to clear up the screen
when it becomes garbled.

\<Return\> Pressing **\<Return\>** will position the cursor on the next
line of data in the carrier mapping window. This key will also move the
cursor to the next residue and BRM assignment in the list to the left of
the Carrier Mapping window.

\<Tab\> Moves the cursor between the carrier mapping window and the
residue/BRM list.

\<Help\> Displays the Help Menu for the Carrier Mapping Table.

### Automated Editor Help Menus 

The user will enter the SPS Editor after assigning bins in the Special
Bin Editor and other bin assignment screens (including, optionally, the
RBCS A\* Bin Editor for MLOCR sort programs and the Carrier Mapping
Table for INS sort programs). In most cases, the user will access the
Automated Editor.

When the user presses **\<Help\>** in the Automated Editor, one of two
Help Menus will appear: one for primary sort programs (Mail Levels A--E,
K) or one for secondary sort programs (Mail Levels F, I, J). Most of the
keys used in the Automated Editor are consistent no matter what type of
sort program is being created. However, there are a few differences
between primary and secondary sort programs.

The keys that are consistent across all mail levels are:

\<Next Screen\> Allows the user to move the cursor to the next used bin,
skipping over any unused bins in the process.

\<Prev Screen\> Allows the user to move the cursor to the previously
used bin, skipping over any unused bins in the process.

\<Insert Here\> Allows the user to insert a new line for data when the
cursor is positioned in the Bin field or in the ZIP Code Ranges field.
The user can add a new bin or ZIP Code depending upon the cursor's
location (new bin in the Bin field; ZIP Code in the ZIP Code Ranges
field).

\<Remove\> When the cursor is positioned in the ZIP Code Ranges field,
the user can delete the contents of the current line. Use this key with
caution; a removed line cannot be recreated unless the user exits the
Automated Editor without saving changes.

\<Return\> Pressing **\<Return\>** accepts input and moves the cursor to
the next line.

\<Find\> Allows the user to enter a search string in order to look for
desired information within a specific column. This function will only
search the column where the cursor is positioned (i.e., to search for a
bin, the cursor must be in the Bin field; to search for a ZIP Code, the
cursor must be in the ZIP Code Ranges field).

\<PF1 Find\> Repeats the last attempted search so the next occurrence of
the search string can be found.

\<PF1 A\> When in the ZIP Code Ranges field, the user can press this key
to display address information for the ZIP Code which the cursor is on.

\<PF1 B\> Moves the cursor to the bottom of the Automated Editor.

\<PF1 C\> Displays the range count for the current bin as a message at
the bottom of the Automated Editor. The user can press this key while in
any field.

\<PF1 D\> Pressing this key while in an MLOCR-A (Machine Types W, X)
sort program displays statistics for MLOCR-A limits. This key is only
applicable in sort programs using an MLOCR-A. It allows the user to
display the SCFs open (i.e., present in the sort program), 9-digit ptrs
used (to a maximum of 128), and the total number of ranges.

\<PF1 H\> Allows the user to change the high density bin in FSM 881
(Machine Types A and O) sort programs.

\<PF1 I\> Activates Auto Insertion mode. If the user presses this key
while in the ZIP Code Ranges field, a new line is inserted for the
current bin and the user can manually add ZIP Codes to that bin. The
user can continue to add lines to a bin by repeatedly pressing either
this key or **\<Return\>**.

\<PF1 K\> Turns off Auto Insertion mode.

\<PF1 L\> Allows the user to access the Label Editor. Pressing **\<PF1
L\>** again from within the Label Editor returns the user to the SPS
Editor.

\<PF1 O\> Allows the user to display and edit chained bins for DBCS/OCR
(Machine Type U) sort programs.

\<PF1 P\> Pages down 15 lines in the sort program. Used to avoid
repeatedly pressing the **\<Down Arrow\>**.

\<PF1 S\> Allows the user to switch the contents of the current bin with
the contents of another bin.

\<PF1 T\> Moves the cursor to the top (first field) of the screen.

\<PF1 U\> Displays all of the unassigned ZIP Codes in the zones
associated with the sort program. Pressing this key again returns the
user to the SPS Editor.

\<PF1 W\> Pressing this key while in the SPS and Label Editors will
display the next handling information for all bins assigned in the sort
program.

\<PF1 Y\> Pressing this key while in the SPS and Label Editors will
display the next handling information for the current bin in the sort
program.

\<PF1 2\> A shortcut method of manually entering ranges in the ZIP Code
Ranges field which puts the Automated Editor in a 2-character mode
(xxx99/xxxx) for a sectional center facility (SCF) specified by the
user. Pressing this key produces a prompt where the user is asked to
enter an SCF. After doing this, the user only needs to enter the last
two digits of a zone while in the ZIP Code Ranges column to enter the
range.

\<PF1 3\> A shortcut method of manually entering ranges in the ZIP Code
Ranges field which puts the editor in a 3-character input mode
(999xx/xxxx). After pressing this key in the ZIP Code Ranges field, type
an SCF and press **\<Return\>** to enter the 3-digit range for that SCF.

\<PF1 4\> A shortcut method of manually entering ranges in the ZIP Code
Ranges field which puts the editor in a 4-character input mode
(99999/xxxx). Pressing this key will produce a prompt asking the user to
*Enter a 5-digit zone for sector/segment mode*.After doing this and
pressing **\<Return\>**, the user can enter only needs to enter four
digits in the ZIP Code Ranges column to produce a range.

\<PF1 5\> A shortcut method of manually entering ranges in the ZIP Code
Ranges field which puts the editor into 5-character input mode
(xxxxx/9999). Press this key combination, enter a zone in the ZIP Code
Ranges field, and press **\<Return\>** to create a 5-digit range.

\<PF1 9\> A shortcut method of manually entering ranges in the ZIP Code
Ranges field which puts the editor into 9-character input mode
(99999/9999). Press this key combination. Enter either three, five, or
nine digits in the ZIP Code Ranges field to create a 3-digit, 5-digit,
or 9-digit range.

\<PF4\> Repaints the screen. This key is used to clear up the screen
when it becomes garbled.

\<F7\> Combines the contents of another bin with the current bin where
the cursor is located. A prompt will asking the user the number of the
bin from which ranges will be pulled. The user should enter the bin
number and press **\<Return\>**.

\<F8\> Press this key to access special tables from which the user can
make bin assignments. The actual table that appears depends upon the
mail level of the sort program.

> [Mail Level]{.underline} [Table]{.underline}
>
> A,B Automated Area Distribution Center (AADC)/Area
>
> Distribution Center (ADC) Table
>
> C,D,E City/State Table
>
> F Firm/Building Table
>
> I Postage Due Table
>
> Pressing this key again while in a special table will return the user
> to the SPS Editor.

\<F9\> Move the contents of the current bin to an empty bin. The user is
prompted to input a bin number and press **\<Return\>**.

\<F10\> Displays a list of unused bins in the sort program. The user can
highlight the desired bin with the arrow keys and press **\<Return\>**
to select it.

\<F11\> Press this key to quit the SPS Editor without saving and return
to the Edit Sort Program screen.

\<F12\> Moves the cursor from its current position to the Bin column.

\<F13\> Moves the cursor from its current position to the ZIP Code
Ranges column.

\<F14\> Saves the SPS edit session and lets the user choose whether to
exit or remain in the editor.

\<F17\> Moves the cursor to the previous field.

\<F18\> Prints the contents of the sort program. This is equivalent to
printing the long version of the sort program in the Print Sort Program
utility.

\<F19\> Pressing **\<F19\>** allows the user to print the current screen
on the monitor.

\<F20\> Moves the cursor to the next unused bin in the editor and
inserts a new line for user input.

\<Do\> Saves the current sort program and exits the user to the Edit
Sort Program screen. Also saves the U version of the sort program and
allows the user to convert the sort program to a loadable file.

\<Tab\> Pressing **\<Tab\>** will move the cursor to the next field to
the right. When the cursor is already in the far right field, pressing
**\<Tab\>** will move it to the far left field on the next line.

\<Up Arrow\> Move up one line.

\<Down Arrow\> Move down one line.

\<Left Arrow\> Move left one field character.

\<Right Arrow\> Move right one character.

\<PF1 Up Arrow\> Shifts everything up from the current bin and opens up
a new line for user input.

\<PF1 Down Arrow\> Shifts everything down from the current bin and opens
up a new line for user input.

\<PF1 Select\> This key allows the user to highlight and move selected
ranges. A prompt will ask the user to specify to which bin a range
should be moved; a range can only be moved to a bin which follows the
current bin (e.g., a range can be moved from Bin 3 to Bin 4 but not to
Bin 2). Press **\<Remove\>** to stop highlighting ranges.

\<Help\> Displays the Help Menu for the Automated Editor.

The following keys only apply in primary sort programs (Mail Levels
A--E, K):

\<Select\> Allows the user to access the Carrier Mapping Table for a ZIP
Code and assign carriers to bins. After pressing this key, the user will
have to type the desired ZIP Code before the Carrier Mapping Table will
appear.

\<PF1 F\> Allows the user to enter one or more 5-digit ZIP Codes in a
bin. When the user presses this key, the prompt *Enter 5-digit range for
bin XXX* appears, where XXX represents the bin where the cursor is
located. Enter the ZIP Codes that make up the range and press
**\<Return\>**. The new range will appear in the ZIP Code Ranges field
for the specified bin. The user can then continue adding ranges or press
**\<PF1 F\>** again to stop using this function. This key cannot be used
in INS sort programs.

\<PF1 N\> After manually entering a 5-digit ZIP Code range in the ZIP
Code Ranges field for outgoing primary (OGP), outgoing secondary (OGS),
managed mail program (MMP), sectional center facility (SCF), and
incoming primary (INP) sort programs, the user can press this key to
automatically produce data (city, state, and ZIP Code ranges) in the Bin
Stack Label and Firm/Building Name or ZIP Code fields.

> For outgoing sort programs using the AADC Table, this function will
> populate the Label Editor fields based on the ranges entered.

\<PF1 Z\> Press this key after manually entering a city or a city and
state in the Bin Stack Label field (the state must be entered as
characters 20 and 21 in the field) to quickly populate the ZIP Code
Ranges field. If the special table for the sort program (accessed by
pressing **\<F8\>**) only contains one listing matching the city name,
the ZIP Code range(s) for that city will automatically be entered in the
ZIP Code Ranges column for the user. However, if the table contains more
than one listing with the city name (e.g., Athens, GA and Athens, OH),
pressing **\<PF1 Z\>** will produce a list of all ZIP Codes for cities
with that name. The user can then type the ZIP Code(s) in the ZIP Code
Ranges field.

\<Ctrl F\> Pressing this key produces a window where the user can input
a range of ZIP Codes which will be assigned to separate 5-digit and
9-digit bins. After entering the range, the user must press **\<Do\>**
to continue.

The following keys apply in secondary sort programs (Mail Levels F, I,
J):

\<PF1 R\> When the user presses this key in the ZIP Code Ranges field,
the carrier ID and the record type for the range are displayed.

\<PF 2\> By pressing this key in the Carrier/Box Section Number field,
the user can reset the multiple carrier flag for the current bin. If the
current bin does not have multiple carriers, the prompt *This is not a
multiple carrier bin* will appear.

\<PF3\> Pressing **\<PF3\>** in the Carrier/Box Section Number field
allows the user to change the carrier flag setting for the current bin.
The user can turn the carrier flag on and off with this key.

### Condensed Editor Help Menu

When creating INS sort programs, the user has the option of assigning
ranges to bins with the Condensed Editor instead of the Automated
Editor.

\<Remove\> This key erases the carrier and ZIP Code information from the
bin where the cursor is currently located.

\<Find\> Allows the user to enter a string in order to look for desired
information.

\<PF1 Find\> Repeats the last attempted search so the next occurrence of
a string can be found.

\<PF1 A\> This key, which can only be used with \<PF1 Z\>while in the
ZIP Code Display window, allows the user to specify an add-on within a
range and shows the address information for that ZIP Code.

\<PF1 C\> Pressing **\<PF1 C\>** provides the bin count for the current
bin.

\<PF1 D\> Pressing this key while in an MLOCR-A (Machine Types W, X)
sort program displays statistics for MLOCR-A limits. This key is only
applicable in sort programs using an MLOCR-A. It allows the user to
display the SCFs open (i.e., present in the sort program), 9-digit ptrs
used (to a maximum of 128), and the total number of ranges.

\<PF1 E\> This key allows the user to view the bin label data (Bin,
Carrier/Box Number, Firm/Building Name) for the current bin and edit the
firm/building field information while present in this window. The user
must press **\<PF1 E\>** to exit the window.

\<PF1 H\> This key combination can only be used in a sort program for
the FSM 881. It allows the user to change the high density bins.

\<PF1 L\> Allows the user to access the Label Editor. Pressing **\<PF1
L\>** again returns the user to the Condensed Editor.

\<PF1 O\> Allows the user to display and edit chained bins for DBCS/OCR
(Machine Type U) sort programs.

\<PF1 S\> Allows the user to enter a bin number in order to switch the
contents of that bin with the contents of the current bin.

\<PF1 U\> Pressing **\<PF1 U\>** displays a list of the unassigned ZIP
Codes that exist for the sort program. This key is also used to exit the
unassigned ZIP Code window.

\<PF1 Y\> Pressing **\<PF1 Y\>** while in the Condensed Editor displays
the next handling information for the current bin.

\<PF1 Z\> This key combination displays the ZIP Codes for the current
bin.The user can edit the ZIP Codes for each bin within this display.

\<PF2\> By pressing this key the user can reset the multiple carrier
flag for the current bin. If the current bin does not have multiple
carriers, the prompt *This is not a multiple carrier bin* will appear.

\<PF3\> Pressing **\<PF3\>** allows the user to change the carrier flag
setting for the current bin. The user can turn the carrier flag on and
off with this key.

\<PF4\> Repaints the screen. This is used to clear the screen when it
becomes garbled.

\<F7\> Pressing **\<F7\>** allows the user to combine two bins together.
The user can pull ranges from another bin into the current bin.

\<F8\> Press this key to access the Firm/Building Table, with which the
user can make bin assignments. Pressing this key again while in the
Firm/Building Table will return the user to the Condensed Editor.

\<F9\> Allows the user to move the current bin's ranges to another bin.

\<F10\> This key displays a list of unused bins.

\<F11\> This key allows the user to exit the SPS Editor to the Edit Sort
Program screen without saving the sort program or making changes to it.

\<F14\> With this key, the user can save the sort program. The user has
the option to exit or remain in the editor.

\<F18\> Pressing **\<F18\>** allows the user to print the entire sort
program to the printer.

\<F19\> Allows the user to print only the sort program information
present of the screen.

\<Do\> Pressing **\<Do\>** saves the sort program and creates a U
version.

\<Up Arrow\> Moves the cursor up through the sort program information
one line at a time.

\<PF1 Up Arrow\> This key combination allows the user to insert
information into the editor by moving bins up.

\<Down Arrow\> Moves the cursor down through the sort program
information one line at a time.

\<PF1 Dn Arrow\> Allows the user to insert information into the SPS
Editor by moving the bins down.

\<Left Arrow\> Moves the cursor left one column.

\<Right Arrow\> Moves the cursor right one column.

\<Help\> Displays the Help Menu for the Condensed Editor.

### Special Tables Help Menu

Special tables assist the user in assigning ranges to bins. The user can
access special tables while in the SPS Editor by pressing **\<F8\>**.
One of the following tables appears, depending on the sort program's
mail level: AADC/ADC Table (Mail Levels A and B), City/State Table (Mail
Levels C, D, and E), Firm/Building Table (Mail Level E), and Postage Due
Table (Mail Level F). The same keys apply to all special tables.

\<Next Screen\> Moves the cursor to the next page of data.

\<Prev Screen\> Moves the cursor to the previous page of data.

\<Find\> Allows the user to enter a search string in order to look for
desired information within a table.

\<Down Arrow\> This key positions the cursor on the next line of data.

\<Up Arrow\> Positions the cursor on the previous line of data.

\<F8\> Press this key to exit the special tables and return to the SPS
Editor.

\<F10\> Press this key to display a list of unused bins; press it again
to remove the list from the screen.

\<F18\> This key will print the existing table on the system printer.
The table printed will depend on the mail level being used to create the
sort program.

\<F19\> Pressing **\<F19\>** prints a hard copy of the current screen on
the system printer.

\<PF1 Find\> Repeats the last attempted search so the next occurrence of
string can be found.

\<PF1 B\> This key combination positions the cursor at the bottom of the
table listing.

\<PF1 T\> This key combination positions the cursor at the top of the
table listing.

\<PF4\> Repaints the screen. This is used to clear up the screen when it
becomes garbled.

\<Return\> Pressing **\<Return\>** throughout the table listing will
position the cursor on the next entry.

\<Help\> Displays the Help Menu for the special tables.

### Unused Bin List Help Menu

When assigning ranges to bins in the SPS Editor, the user can press
**\<F10\>** to select from a list of unused bins.

\<Next Screen\> Moves the cursor to the next screen of unused bins.

\<Prev Screen\> Moves the user to the previous page of the unused bins.

\<Down Arrow\> Pressing this key moves the cursor to the next unused bin
in the list.

\<Up Arrow\> Moves the cursor to the previous unused bin in the list.

\<F10\> Pressing this key exits the unused bin list.

\<F19\> Pressing **\<F19\>** prints the current unused bin screen on the
system printer.

\<F20\> This key adds the highlighted bin in the unused bin list to the
Bin \# column in the SPS Editor.

\<Return\> Pressing **\<Return\>** adds the highlighted bin in the
unused bin list to the Bin \# column in the SPS Editor.

\<PF1 B\> This key combination moves the user to the bottom of the
unused bin list.

\<PF1 T\> Moves the user to the top of the unused bin list.

\<Help\> Displays the Help Menu for the unused bin list.

### Label Editor Help Menu

The user can press **\<PF1 L\>** while in the SPS Editor to verify and,
if necessary, edit label data.

\<Next Screen\> Moves the cursor to the next screen of the Label Editor.

\<Prev Screen\> Moves the cursor to the previous screen of the Label
Editor.

\<Return\> Accepts the desired input and moves the cursor to the next
field.

\<Find\> Allows the user to enter a search string in order to look for
desired information within a specific column.

\<PF1 Find\> Allows the user to find the next occurrence of the current
search string. This function can be used in any column of the Label
Editor.

\<PF1 B\> This key combination moves the cursor to the bottom of the
label list.

\<PF1 L\> Pressing **\<PF1 L\>** in the Label Editor will return the
user to the SPS Editor.

\<PF1 P\> Allows the user to move to the next screen display of label
information (i.e., performs the same function as \<Next Screen\>).

\<PF1 T\> Pressing this key combination moves the cursor to the top of
the label list.

\<PF1 W\> Pressing **\<PF1 W\>** in the Label Editor allows the user to
view the next handling information for all bins in the sort program.

\<PF1 Y\> Allows the user to view the next handling information for the
current bin in the sort program.

\<PF4\> Repaints the screen. This is used to clear up the screen when it
becomes garbled.

\<F7\> Pressing **\<F7\>** displays the Content Identifier Table, which
provides the 3-digit codes used to specify the mail type and mail class.

\<F8\> This key provides the user with Service Standard information for
the source SCF. This table gives the destination SCF and the service
standard values for each.

\<F9\> This key allows the user to copy information from a specified bin
to the bin where the cursor is currently present.

\<F12\> Pressing this key from any column in the Label Editor positions
the cursor in the bin field.

\<F17\> Pressing **\<F17\>** moves the cursor backward to the previous
field.

\<F18\> Allows the user to print the entire label file to the system
printer.

\<F19\> Allows the user to print the current screen containing label
file information.

\<Tab\> Pressing **\<Tab\>** moves the cursor to the next field to the
right.

\<Up Arrow\> This key allows the user to move up through the label list
one bin at a time.

\<Down Arrow\> Allows the user to move down through the label list one
bin at a time.

\<Left Arrow\> Moves the cursor one character to the left.

\<Right Arrow\> Moves the cursor one character to the right.

\<Help\> Displays the Help Menu for the Label Editor.

### Sort Program Conversions Help Menu

The Sort Program Conversions screen appears when the user selects Option
**1**, Convert Sort Programs (Upload/Download), at the Sort Program
Transfer Menu.

\<Do\> Executes the selected option (\[CONVERT\] or \[EXIT\]) on the
option bar at the bottom of the screen.

\<Left Arrow\> Allows the user to move left on the option bar at the
bottom of the screen and highlight an option (\[CONVERT\] or \[EXIT\]).

\<Right Arrow\> Allows the user to move right on the option bar at the
bottom of the screen and highlight an option (\[CONVERT\] or \[EXIT\]).

\<Down Arrow\> Moves the cursor down one line in the From and To
columns.

\<Up Arrow\> Moves the cursor up one line in the From and To columns.

\<Return\> Moves the cursor through this screen's fields (e.g., from the
From column to the To column).

\<F17\> Moves the cursor to the previous field (e.g., from the To column
to the From column).

\<Next Screen\> Scrolls the cursor to the next page of data.

\<Prev Screen\> Scrolls the cursor to the previous page of data.

\<F8\> Press this key to view the date of the last conversion and the
name of the user responsible for that conversion.

\<F10\> Accesses a directory of sort program names. The user must
provide the machine type and choose between an upload and a download
directory.

\<Remove\> Erases all existing data in all existing fields of the Sort
Program Conversions screen.

\<PF4\> Repaints the screen display. This is used to clear the screen
when it becomes garbled.

\<Help\> Displays the Help Menu for the Sort Program Conversions screen.

### Delete Sort Program Loadable Help Menu

The Delete Loadable Sort Programs screen appears when the user selects
Option **5**, Delete Loadable Sort Programs, at the Sort Program
Transfer Menu.

\<Next Screen\> Scrolls the cursor to the next page of sort program
listings.

\<Prev Screen\> Scrolls the cursor to the previous page of sort program
listings.

\<Remove\> Pressing this key erases the data from the field (either
Enter Machine Type or Enter Sort Program Name) where the cursor is
located.

\<Do\> Press **\<Do\>** after entering a machine type and sort program
name to delete the sort program.

\<F11\> Allows the user to exit this screen.

\<F19\> Prints the current screen.

\<Help\> Displays the Help Menu for the Delete Loadable Sort Programs
screen.

### Copy Sort Program Help Menu

The Copy Sort Program screen appears when the user selects Option **1**,
Copy Sort Program, at the Sort Program Utilities Menu.

\<Return\> Pressing this key allows the user to move the cursor to the
next field in the Input Sort Program Is and Output Sort Program Is
fields and enter data in those fields.

\<Do\> Press **\<Do\>** to execute the highlighted option (\[COPY\] or
\[EXIT\]) on the option bar.

\<Backspace\> Moves the cursor back one character within a field.

\<Remove\> Erases the contents of all fields on the screen.

\<Right Arrow\> Allows the user to move right on the option bar at the
bottom of the screen and highlight an option (\[COPY\] or \[EXIT\]).

\<Left Arrow\> Allows the user to move left on the option bar at the
bottom of the screen and highlight an option (\[COPY\] or \[EXIT\]).

\<F17\> Moves the cursor back to the previous field.

\<F19\> Prints the current screen.

\<PF4\> Repaints the screen display. This is used to clear the screen
when it becomes garbled.

\<Down Arrow\> Moves the cursor down through the fields.

\<Up Arrow\> Moves the cursor up through the fields.

\<Help\> Displays the Help Menu for the Copy Sort Programs utility.

### Delete Sort Program Help Menu

The Delete Sort Program screen appears when the user selects Option
**2**, Delete Sort Program, at the Sort Program Utilities Menu.

\<Return\> Pressing this key allows the user to move the cursor to the
next field in the Sort Program to Be Deleted fields and enter data in
those fields.

\<F17\> Moves the cursor back to the previous field.

\<Do\> Executes the highlighted option (\[DELETE\] or \[EXIT\]) on the
option bar at the bottom of the screen.

\<Backspace\> Normally erases the preceding character and moves the
cursor to the left. However, pressing this key when the cursor is at the
beginning of any field will erase the entire field.

\<Remove\> Erases the contents of all the fields on the screen.

\<Right Arrow\> Allows the user to move right on the option bar at the
bottom of the screen and highlight an option (\[DELETE\] or \[EXIT\]).

\<Left Arrow\> Allows the user to move left on the option bar at the
bottom of the screen and highlight an option (\[DELETE\] or \[EXIT\]).

\<Help\> Displays the Help Menu for the Delete Sort Programs utility.

\<F19\> Prints a hard copy of the current screen.

\<Down Arrow\> Moves the cursor down through the fields.

\<Up Arrow\> Moves the cursor up through the fields.

### List All Sort Programs Help Menu

The List All Sort Programs utility is accessed by choosing **3** for
Option 3 at the List All Sort Programs Menu.

\<Return\> Pressing this key allows the user to move the cursor to the
next field in the Display History of Sort Program fields and enter data
in those fields.

\<Do\> Executes the highlighted option on the option bar at the bottom
of the screen (\[DISPLAY\] or \[EXIT\]).

\<Backspace\> Normally erases the preceding character and moves the
cursor to the left. However, pressing this key when the cursor is at the
beginning of any field will erase the entire field.

\<Remove\> Erases the contents of all the fields on the screen.

\<Right Arrow\> Allows the user to move right on the option bar at the
bottom of the screen and highlight an option (\[DISPLAY\] or \[EXIT\]).

\<Left Arrow\> Allows the user to move left on the option bar at the
bottom of the screen and highlight an option (\[DISPLAY\] or \[EXIT\]).

\<Help\> Displays the Help Menu for the List All Sort Programs utility.

\<F17\> Moves the cursor to the previous field.

\<F18\> Prints a hard copy of all sort programs.

\<F19\> Prints a hard copy of the current screen.

\<F20\> Provides access to the List All Sort Programs browser. This
browser lists all sort programs that have been created, when and by whom
they were created, when and by whom any updates were made, and when and
by whom they were downloaded.

\<PF4\> Repaints the screen display. This is used to clear the screen
when it becomes garbled.

### List All Sort Programs Browser Help Menu

The user accesses the List All Sort Programs browser by pressing
**\<F20\>** at the List All Sort Programs screen. Once in the browser,
the user can press **\<Help\>** to access a Help menu.

\<Up Arrow\> Move up one line

\<Down Arrow\> or \<Return\> Move down one line

\<Prev Screen\> Move up one "page" of the file

\<Next Screen\> or \<Spacebar\> Move down one "page" of the file

\<PF1 B\> or \<B\> Move to last line in file

\<PF1 T\> or \<T\> Move to first line in file

\<Find\> Search for an item in the file. A *Search for* prompt will
appear when this key is pressed. Enter the item being searched for in
the box provided and press **\<Return\>**. If the browser lists the item
more than once, the first occurrence of the item following the present
location of the cursor will be found.

\<Tab\> Press this key to move one field to the right.

\<F17\> Go back one field to the left.

\<S\> The user can press **\<S\>** in certain fields to sort the
information in that field in ascending order.

\<F18\> Print the entire listing of sort program records, not just the
data visible on the screen.

\<F19\> Print the current screen.

\<F11\> or \<F14\> Exit the browser and return to the List All Sort
Programs screen.

### Print Sort Program Help Menu

The Print Sort Program utility is accessed by choosing **4** for Option
4, Print Sort Program, at the Sort Program Utilities Menu.

\<Return\> Pressing this key allows the user to move the cursor to the
next field in the Sort Program to Be Printed fields and enter data in
those fields.

\<Do\> Executes the highlighted option on the option bar at the bottom
of the screen (\[PRINT\] or \[EXIT\]).

\<Backspace\> Normally erases the preceding character and moves the
cursor to the left. However, pressing this key when the cursor is at the
beginning of any field will erase the entire field.

\<Remove\> Erases the contents of all the fields on the screen.

\<Right Arrow\> Allows the user to move right on the option bar at the
bottom of the screen and highlight an option (\[PRINT\] or \[EXIT\]).

\<Left Arrow\> Allows the user to move left on the option bar at the
bottom of the screen and highlight an option (\[PRINT\] or \[EXIT\]).

\<Help\> Displays the Help Menu for the Print Sort Program utility.

\<F17\> Moves the cursor to the previous field.

\<F19\> Prints a hard copy of the current screen.

\<PF4\> Repaints the screen display. This is used to clear the screen
when it becomes garbled.

### Exception Report Browser Help Menus

The user can browse one of the three types of exception reports by
selecting one of the reports at the Browse Exception Report Menu. When
browsing a report, the user can press **\<F20\>** to view an Exception
Report browser.

\<Up Arrow\> Move up one line

\<Down Arrow\> or \<Return\> Move down one line

\<Prev Screen\> Move up one "page" of the file

\<Next Screen\> or \<Spacebar\> Move down one "page" of the file

\<PF1 B\> or \<B\> Move to last line in file

\<PF1 T\> or \<T\> Move to first line in file

\<Find\> Search for an item in the file. A *Search for* prompt will
appear when this key is pressed. Enter the item being searched for in
the box provided and press **\<Return\>**. If the browser lists the item
more than once, the first occurrence of the item following the present
location of the cursor will be found.

\<Left Arrow\> Press this key to scroll the browser 20 spaces to the
left.

\<Right Arrow\> Press this key to scroll the browser 20 spaces to the
right.

\<F18\> Print the entire listing of sort program records, not just the
data visible on the screen.

\<F19\> Print the current screen.

\<F11\> or \<F14\> Exit the browser and return to the exception report.

# Appendix D. SPS Menu Flow

The Sort Program System (SPS) has many menus and screens, and the user
may find it difficult to remember how to move through them. As an aid to
the user, this appendix presents a series of charts showing the movement
from menu to menu.

The following charts are presented in this appendix:

-   Sort Program Generator Main Menu flow

-   SPS Main Options Menu flow

-   Sort Program Pick and Transfer Menu flow

-   Sort Program Management System (SPMS) Menu flow

-   Sort Program Exception Report Utilities Menu flow

    (This appendix does not give a detailed explanation of menu options;
    for more information, see Chapter 7.)

## Menu Flow for Letter Mail Processing Options {#menu-flow-for-letter-mail-processing-options .unnumbered}

The Sort Program Generator Main Menu appears as soon as the user enters
a user name and password at the SPS title screen. This menu contains
nine options, four of which are directly applicable to letter mail
processing and are covered in this guide (see Figure D-1). These options
are:

-   Option 1 Sort Program System (SPS)

-   Option 7 SPS Refresh

-   Option 8 Local AO/DBCS Configuration

-   Option 9 Sort Program Management System (SPMS)

![](media/image2.emf){width="5.722916666666666in"
height="8.210416666666667in"}

Figure D-1. Sort Program Generator Main Menu Letter Mail Processing
Options

Three of these four different letter mail processing options (Options 1,
8, and 9) leads the user to further menus. Figures D-2 through D-5
detail the flow from these menus. (Option 7 only leads the user to a
prompt for the SPS Refresh, not to a menu; for more information on this
option, see Chapter 6.)

The SPS Main Options Menu, accessed by selecting Option **1**, leads the
user to the functions necessary for creating and maintaining sort
programs. There are options for accessing the Zone Table , editing or
creating a sort program, updating incoming secondary (INS) sort
programs, transferring sort programs, and accessing sort program
utilities (see Figure D-2).

The Sort Program Pick and Transfer Menu appears when the user selects
Option **8**, Local AO/DBCS Configuration. It provides various options
for transferring sort program loadables (see Figure D-3).

By selecting Option **9**, Sort Program Management System (SPMS), from
the Sort Program Generator Main Menu, the user can access the Sort
Program Management System Menu. This menu primarily provides access to
different SPS utilities (see Figure D-4), including the sort program
exception reports (Option 1). The Sort Program Exception Reports
Utilities Menu leads the user to various options for working with
exception reports (see Figure D-5).

(Most of the chapters in this guide focus on standard SPS functions
accessed from the SPS Main Options Menu, particularly Chapters 11, 14,
and 15. For more information on transferring sort program loadables, see
Chapter 16. For more information on sort program exception reports, see
Chapter 13.)

![](media/image3.emf){width="5.518055555555556in"
height="8.120138888888889in"}

Figure D-2. SPS Main Options Menu Flow

![](media/image4.emf){width="5.447222222222222in"
height="8.182638888888889in"}

Figure D-3. Sort Program Pick and Transfer Menu Flow

![](media/image5.emf){width="5.499305555555556in" height="8.01875in"}

Figure D-4. SPMS Menu Flow

![](media/image6.emf){width="5.447222222222222in"
height="7.956944444444445in"}

Figure D-5. Sort Program Exception Report Utilities Menu

## Menu Flow for Other Options

Five other options at the Sort Program Generator Main Menu do not relate
as directly to letter mail processing (see Figure D-6). Four of them are
related to different sort program utilities: the sort program
maintenance utility (Option 2) and Sort Program Generator Utility (SPGU;
Options 3--5). The remaining option (Option 6) provides access to
Two-Pass functions and is particularly useful for delivery point
sequencing (DPS) mail. (For brief descriptions of these options, see
Chapter 7. *Sorting Mail to the Delivery Point: a DPS User\'s Guide*
covers Two-Pass functions in detail.)

![](media/image7.emf){width="5.447222222222222in"
height="8.130555555555556in"}

Figure D-6. Other Sort Program Generator Main Menu Options

# Appendix E. Sort Program Planning and Bin Assignment Worksheets

When designing a sort program, the sort program developer must make
decisions involving bin assignments. This appendix attempts to help the
user with this task by providing several documents used by one site in
the planning process and several blank bin assignment worksheets. Users
can photocopy these pages for their own planning, if desired.

## Sample Sort Program Planning Documents

The following planning documents for a sort program come from one
particular site and proved useful for that site's needs. **They are not
an attempt to impose a method of planning on other sites.** Each plant
handles sort programs differently, and what works at one site may not
work at another. The planning documents and worksheets in this appendix
only aim to provide a model that other sort program developers may find
useful.

In this example, the site has created three different types of planning
documents in Microsoft Excel for outgoing primary (OGP) sort program
AH88500A. This sort program is a Mail Processing Bar Code Sorter (MPBCS)
operation, and the Microsoft Excel file with these documents has been
given the name 8711.xls. The first three characters, "871," represent
the operation number and the last character, "1," indicates that the
sort program should be run on MPBCS machine number 1.

The site in this example has first constructed a data sheet showing
information from the label file for the sort program. This table
contains bin data presented in an eight-column format and was created in
Microsoft Excel. The label file was imported into the table (see Figure
E-1).

![](media/image8.emf){width="5.955555555555556in"
height="4.926388888888889in"}

Figure E-1. Sample Data Chart for Planning a Sort Program

In this chart, each row displays the bin number, bin label, and a
description of the bin for two different bins (e.g., the first row in
the chart contains this information for Bins 1 and 2).

The sort program developer next converted this information into a more
formal diagram spread out over two pages. The information remains the
same as the previous data sheet (see Figures E-2 and E-3).

![](media/image9.emf){width="5.186805555555556in"
height="7.288194444444445in"}

Figure E-2. First Page of Sample Bin Assignment Worksheet

![](media/image10.emf){width="5.835416666666666in"
height="7.240972222222222in"}

Figure E-3. Second Page of Bin Assignment Worksheet

This Microsoft Excel spreadsheet diagram served at this site as a
planning worksheet to develop or recreate sort programs. With a
spreadsheet like this, the sort program developer can add bin density
data in the neighboring cells, then manipulate the arrangement using
that data. Once an acceptable arrangement would be established in the
diagram, the sort program developer could build the sort program to
match the diagram, resulting in a more efficient sort program.

The sort program developer has also created bin labels in Microsoft
Excel which will be cut and pasted to the MPBCS's bins(see Figure E-4).

![](media/image11.emf){width="2.7118055555555554in"
height="7.188194444444444in"}

Figure E-4. Planned Bin Labels for Sort Program

With these labels applied to bins, the machine operators know what is
contained in each bin when they process the mail.

## Sample Bin Assignment Worksheets

The bin assignment worksheets contained in this section are blank and
may be photocopied by the SPS user. **They are provided as tools which
may prove useful to sort program developers, not as a prescription for
any site.**

The first two bin assignment worksheets are for making bin assignments
with Multiline Optical Character Readers (MLOCRs). The first worksheet
(see Figure E-5) is for MLOCRs with 44 bins (Machine Types S,W). The
second worksheet (see Figure E-6) is for MLOCRs with 60 bins (Machine
Types T, X). On each worksheet, mechanical reject mail is assigned to
the last bin in the list.

The next bin assignment worksheet (see Figure E-7) is for MPBCSs with 96
bins (Machine Types H, R).

The last bin assignment worksheet is for a Delivery Bar Code Sorter
(DBCS) with 222 bins (see Figure E-8). Mechanical reject mail occupies
Bins 219--222 and two label printers are accounted for, one between Bins
3 and 4 and one between Bins 78 and 79.

While this guide focuses on letter mail processing, worksheets have also
been provided for flat mail processing. The worksheets for the FSM 881
(see Figure E-9) and FSM 1000 (see Figure E-10) take into account the
two-sided nature of these machines. The locations of the operator's
consoles are noted, as well as the locations of the mechanical reject
bins.

![](media/image12.emf){width="5.727083333333334in"
height="7.5368055555555555in"}

Figure E-5. MLOCR_44 Bin Assignment Worksheet

![](media/image13.emf){width="4.644444444444445in"
height="8.147222222222222in"}

Figure E-6. MLOCR_60 Bin Assignment Worksheet

Figure E-7. MPBCS Bin Assignment Worksheet
![](media/image14.emf){width="6.0159722222222225in"
height="7.997222222222222in"}

![](media/image15.emf){width="7.383333333333334in"
height="5.661111111111111in"}

Figure E-8. DBCS Bin Assignment Worksheet

![](media/image16.emf){width="5.927777777777778in" height="7.65in"}

Figure E-9. FSM 881 Bin Assignment Worksheet

![](media/image17.emf){width="5.951388888888889in"
height="7.320833333333334in"}

Figure E-10. FSM 1000 Bin Assignment Worksheet

# Appendix F. Steps to Creating Letter Mail Sort Programs

The following steps briefly explain how to create any sort program for
letter mail processing. When creating a sort program in the Sort Program
System (SPS), the user will:

1.  Enter SPS. From the Sort Program Generator Main Menu, select Option
    **1**, Sort Program System (SPS). The SPS Main Options Menu will
    appear.

2.  Set up the sort program in the Zone Table. At the SPS Main Options
    Menu, choose Option **1**, Sort Program Zone Table. Enter the sort
    program name and up to 20 zones. Exit back to the SPS Main Options
    Menu.

3.  Enter the name of the sort program to be created or edited. At the
    SPS Main Options Menu, choose Option **2**, Edit/Create Sort
    Program. Enter the sort program name at the Edit Sort Program
    screen, using any letter from A--Z except U for the version. Press
    **\<Do\>** to continue creating the sort program.

4.  Enter the SPS Editor. The title screen for the SPS Editor will
    appear next. When creating incoming secondary (INS) sort programs
    (Mail Level F), the user will choose whether to use the Automated
    Editor or Condensed Editor before the title screen appears.

5.  For some incoming sort programs (Mail Levels F, I, and J), decide
    whether to use National Directory Support System (NDSS)/Address
    Management System (AMS) data for the sort program.

6.  Assign bins in the Special Bin Editor. The user can never leave a
    bin value at 0. Press **\<Do\>** when finished entering the values.

7.  If applicable, make additional bin assignments. For some incoming
    sort programs, the user may need to assign bins for residue mail,
    business reply mail (BRM), or certified mail detection (CMD) mail.
    The user may also have the option to hold out 9999 mail. Answer any
    prompts and make bin assignments as shown on the screen. Press
    **\<Do\>** when finished with each bin. For Output Subsystem (OSS)
    sort programs, assign bins in the RBCS Special Bin Editor. Press
    **\<Do\>** after entering the values.

```{=html}
<!-- -->
```
8.  For INS sort programs, decide whether to map the carriers to bins in
    the Carrier Mapping Table or have SPS automatically generate the
    sort program.

9.  With Input Subsystem (ISS) sort programs only, choose whether to
    assign ranges to Remote Bar Coding System (RBCS) bins in the RBCS
    A\* Bin Editor. These bins will be sent to the OSS for processing.
    After making any assignments, press **\<Do\>** to continue.

10. Assign ranges in the SPS Editor (Automated Editor or Condensed
    Editor), which displays bin assignments. **It is recommended that
    the user assign bins using the special tables rather than entering
    the information manually.** To use the special tables, press
    **\<F8\>**. The type of mail determines the content of the special
    tables:

+-----------------------------------+----------------------------------+
| ####### **Mail Levels**           | ####### **Editor**               |
+-----------------------------------+----------------------------------+
| A, B                              | AADC/ADC Table                   |
+-----------------------------------+----------------------------------+
| C, D, E                           | City/State Table                 |
+-----------------------------------+----------------------------------+
| F, J                              | Firm/Building Table              |
+-----------------------------------+----------------------------------+
| I                                 | Postage Due Table                |
+-----------------------------------+----------------------------------+

> The data can be viewed alphabetically or by ZIP Code. Make any bin
> assignments and press **\<F8\>** to return to the SPS Editor. Save the
> sort program at any time by pressing **\<F14\>** while working in the
> SPS Editor. This option allows the user to save the sort program
> without exiting the editor.

11. Verify the accuracy of label information. To do this, press **\<PF1
    L\>** while in the Automated Editor or the Condensed Editor. After
    reviewing the label information, press **\<PF1 L\>** again to return
    to the SPS Editor.

12. Create a U version of the sort program. When finished in the SPS
    Editor, press **\<Do\>** to save the sort program. SPS will create a
    U version of the sort program unless the user has set the option to
    download any version of a sort program.

13. Create a loadable file. Press **\<Do\>** to save the sort program
    and answer **Y** (yes) to the query about creating a loadable. Press
    **\<Return\>** to use the default loadable name or enter a new
    loadable name and then press \<**Return\>**. A loadable file is the
    file transferred to the mail processing equipment (MPE).

# Appendix G. CIN Conditions and Values

The type of mail in a bin will determine what content identifier number
(CIN) value is populated in the Label Editor. The following chart lists
the conditions in which CIN values will be assigned and to what type of
bin they will be assigned.

**TYPE OF BIN SPECIAL CIN VALUE for First CIN VALUE for First**

**CONDITIONS Class Letter Mail Class Flat Mail**

AADC single AADC CIN of 245 AADC CIN of 274

AADC combined If number of ranges in Invalid CIN of 000 Invalid CIN of
000

bin \>AADC ranges

3-digit single 3-digit CIN of 244 3-digit CIN of 273

3-digit unique city City CIN of 247 City CIN of 276

3-digit combined If bin contains ranges AADC CIN of 245 AADC CIN of 274

\< or = to the AADC

5-digit single 5-digit CIN of 242 5-digit CIN of 272

5-digit combined If bin contains ranges Mixed Zone CIN of 240 Mixed Zone
CIN of 230

from the same AADC

5-digit combined If number of ranges in Invalid CIN of 000 Invalid CIN
of 000

bin \> AADC

9-digit single Firm CIN of 167 Firm CIN of 173

9-digit combined Carrier CIN of 266 Carrier CIN of 285

Carrier/box section Carrier route CIN of 266

on first and second pass

sector/segment and DPS

Sequenced bins on first Sequenced CIN of 929

pass of sector/segment

and DPS

A hierarchy for the labeling of special bins and for assigning CINs will
be used for bins that have more than one special bin assignment. When a
sorting bin is combined with a special bin, the CIN for the special bin
will be used.

The labeling priority for special bins uses the following basic
hierarchy for all machines. The CIN priority rates 1 as the highest and
10 as the lowest.

+-------------------+----------------+---------+----------------------+
| **Labeling        | **CIN          | **CIN** | **CIN Text**         |
| Priority**        | Priority**     |         |                      |
|                   |                |         |                      |
| **of Bin Types**  |                |         |                      |
+-------------------+----------------+---------+----------------------+
| Unassigned bin    | 3              | 939     | FCM LTRS UNASSIGNED  |
+-------------------+----------------+---------+----------------------+
| Mechanical reject | 2              | 928     | FCM LTRS MECH REJ    |
| bin               |                |         |                      |
+-------------------+----------------+---------+----------------------+
| Read reject bin   | 1              | 932     | FCM LTRS READ REJ    |
+-------------------+----------------+---------+----------------------+
| Residue (9-digit) | 4              | 934     | FCM LTRS RES BC9     |
+-------------------+----------------+---------+----------------------+
| 11-D residue      | 5              | 933     | FCM LTRS RES BC11    |
| (DPS)             |                |         |                      |
+-------------------+----------------+---------+----------------------+
| BRM               | 6              | 917     | LTRS BRM             |
+-------------------+----------------+---------+----------------------+
| CMD               | 7              | 916     | LTRS ACCT/CERT       |
+-------------------+----------------+---------+----------------------+
| Late/loop         | 8              | 944     | FCM OLD              |
+-------------------+----------------+---------+----------------------+
| No improvement    | 9              | 169     | FCM NON-CODABLE LTRS |
| (9999)            |                |         |                      |
+-------------------+----------------+---------+----------------------+
| No code           | 10             | 940     | FCM NOC              |
+-------------------+----------------+---------+----------------------+

The CIN priorities for the MultiLine Optical Character Reader (MLOCR)
are as follows:

+-----------------+-----------------+-----------+----------------------+
| **Bin Stack     | **CIN           | **CIN**   | **CIN Text**         |
| Label**         | Priority**      |           |                      |
+-----------------+-----------------+-----------+----------------------+
| Non-Postnet     | 1               | 902       | FCM LTRS UNRESOLVED  |
+-----------------+-----------------+-----------+----------------------+
| 5-D RBCS        | 2               | 903       | FCM LTRS PARTIAL     |
+-----------------+-----------------+-----------+----------------------+
| ISS Reject      | 3               | 920 or    | FCM LMLM OG BACK or  |
|                 |                 |           | FCM LMLM INC BACK    |
|                 |                 | 891\*     |                      |
+-----------------+-----------------+-----------+----------------------+
| Old Tag         | 4               | 944       | FCM OLD              |
+-----------------+-----------------+-----------+----------------------+
| COA             | 5               | 948       | COA                  |
+-----------------+-----------------+-----------+----------------------+
| Jet Printer     | 6               | 922 or    | FCM LMLM OG FRONT or |
|                 |                 |           | FCM LMLM INC FRONT   |
|                 |                 | 893\*\*   |                      |
+-----------------+-----------------+-----------+----------------------+
| Ident. Error    | 7               | 947       | FCM ID TRACKING      |
+-----------------+-----------------+-----------+----------------------+
| Foreign         | 8               | 726       | LTRS BC FGN WKG      |
+-----------------+-----------------+-----------+----------------------+

\* The CIN for Mail Levels A and B is 920; for all other mail levels,
the CIN is 891.

\*\* The CIN for Mail Levels A and B is 922; for all other mail levels,
the CIN is 893.

The following special bins are for Output Subsystem (OSS) machines only.
If more than one Remote Bar Coding System (RBCS) special sort is
assigned to the same bin, the label will read *Mixed RBCS/OSS Bin*. The
CIN priorities below will be used to determine CIN assignments for each
special bin.

+--------------------+---------------+----------+---------------------+
| **Bin Stack        | **CIN         | **CIN**  | **CIN Text**        |
| Label**            | Priority**    |          |                     |
+--------------------+---------------+----------+---------------------+
| Unreadable image   | 1             | 946      | FCM NOI             |
| \[NOI\]            |               |          |                     |
+--------------------+---------------+----------+---------------------+
| Old ID tag \[OLD\] | 2             | 944      | FCM OLD             |
+--------------------+---------------+----------+---------------------+
| ID tag unreadable  | 3             | 920 or   | FCM LMLM OG BACK    |
| \[URT\]            |               |          |                     |
|                    |               | 891\*    | FCM LMLM INC BACK   |
+--------------------+---------------+----------+---------------------+
| Verify error       | 4             | 922 or   | FCM LMLM OG FRONT   |
| \[VER\]            |               |          |                     |
|                    |               | 893\*\*  | FCM LMLM INC FRONT  |
+--------------------+---------------+----------+---------------------+
| Letter misfaced    | 5             | 930      | FCM LTRS MISFACED   |
| \[MSF\]            |               |          |                     |
+--------------------+---------------+----------+---------------------+
| Double feed        | 6             | 927      | FCM LTRS DOUBLEFEED |
| \[DBF\]            |               |          |                     |
+--------------------+---------------+----------+---------------------+
| No ID tag found    | 7             | 942      | FCM NOT             |
| \[NOT\]            |               |          |                     |
+--------------------+---------------+----------+---------------------+
| No ZIP found       | 8             | 943      | FCM NOZ             |
| \[NOZ\]            |               |          |                     |
+--------------------+---------------+----------+---------------------+
| Time out \[TMO\]   | 9             | 945      | FCM TMO/ZNR/ZPR     |
+--------------------+---------------+----------+---------------------+
| ZIP not resolved   | 10            | 945      | FCM TMO/ZNR/ZPR     |
| \[ZNR\]            |               |          |                     |
+--------------------+---------------+----------+---------------------+
| ZIP partly         | 11            | 945      | FCM TMO/ZNR/ZPR     |
| resolved \[ZPR\]   |               |          |                     |
+--------------------+---------------+----------+---------------------+
| Foreign \[FGR\]    | 12            | 726      | LTRS BC FGN WKG     |
+--------------------+---------------+----------+---------------------+
| CFS Mail \[CFS\]   | 13            | 202      | CFS LTRS            |
+--------------------+---------------+----------+---------------------+
| Header only        | 14            | 928      | FCM LTRS MECH REJ   |
| \[HDR\]            |               |          |                     |
+--------------------+---------------+----------+---------------------+

\* The CIN for Mail Levels A and B is 920; for all other mail levels,
the CIN is 891.

\*\* The CIN for Mail Levels A and B is 922; for all other mail levels,
the CIN is 893.

# Appendix H. Next Handling Logic

The next handling information includes the next handling type, which
represents the mail's next level of processing. The next handling type
is determined by the bin contents of each bin. Each next handling type
is listed and described below:

MISC Miscellaneous. Mail receiving a miscellaneous next handling type is
mail that cannot be sorted by range and is sent to manual operations.
This type will always appear for special bin mail.

OGS Outgoing secondary. The mail's next processing is an OGS (Mail Level
B) sort program to breakdown separations further before being
dispatched.

SCF Sectional center facility. This type is for mail within a plant that
is to be sorted on an SCF (Mail Level D) sort program.

INP Incoming primary. Mail to be sorted on an INP (Mail Level E) sort
program. This type is also displayed for unique 3-digit city
separations.

SA Subsequent automation. This type suggests that mail be sent to an
incoming secondary (INS), sector/segment, or delivery point sequencing
(DPS) sort program.

DISP Dispatch. Last processing step for this facility.

The following chart lists next handling information for outgoing primary
(OGP, Mail Level A) and OGS (Mail Level B) label files. In this chart,
208 is used as the local SCF and 606 is used as the destination SCF.

  ----------------------------------- -----------------------------------
  **Bin Content**                     **Next Handling**

  No Ranges - RDRJ, MCRJ\...          MISC AZ20800

  ADCs - UNAS                         MISC AZ20800

  ADCs - OGS                          OGS B#20800

  ADCs - OGS, ISS/A\*                 OGS B\*20800

  ADC - Local                         MISC B#20800

  ADC - Local, ISS/A\*                MISC B\*20800

  ADC - Non-local                     DISP C#60600

  ADC - Non-local, ISS/A\*            DISP C\*60600

  3D(s) -- Local                      SCF D#20800

  3D(s) - Local, ISS/A\*              SCF D\*20800

  3D(s) - Local, Direct City          INP E#20800

  3D(s) - Local, Direct City, ISS/A\* INP E\*20800

  3D(s) - Non-local                   DISP C#60600

  3Ds - Non-local, ISS/A\*            DISP C\*60600

  3D - Non-local                      DISP D#60600

  3D - Non-local, ISS/A\*             DISP D\*60600

  3D - Non-local, Direct City         DISP E#60600

  5D(s) - Local, City State           SA F#20800

  5D(s) - Local, City State, ISS/A\*  SA F\*20800

  5D(s) - Local, Two Pass             SA G#20800

  5D(s) - Local, Two Pass, ISS/A\*    SA G\*20800

  5D(s) - Local, DPS                  SA L#20800

  5D(s) - Local, DPS, ISS/A\*         SA L\*20800

  5D(s) - Non-local                   DISP F#60600

  5D(s) -- Non-local, ISS/A\*         DISP F\*60600

  9D(s)/11D(s)                        DISP
  ----------------------------------- -----------------------------------

The type of mail processing equipment (MPE) that will be used during a
tray of mail's next processing step is determined by whether a pound
symbol (#) or an asterisk (\*) appears in the next handling information.

Next handling information containing a pound symbol (#) means that the
tray of mail will be processed on one of the following machines:

-   Mail Processing Bar Code Sorter (MPBCS, Machine Type H)

-   Delivery Bar Code Sorters (DBCSs, Machine Types Q and V)

-   Multiline Optical Character Readers (MLOCR, Machine Types W, X)

-   Multiline Optical Character Readers_B (MLOCR_B, Machine Types S, T)

    If an asterisk (\*) appears in the next handling information, MPE
    with an Output Subsystem (OSS) will be used to sort the tray of
    mail:

-   DBCS/OSS (Machine Type P)

-   MPBCS/OSS (Machine Type R)

    For all non-local Area Distribution Center (ADC) 3-digit and 5-digit
    zones, SPS will automatically assign a \# or an \* (depending on the
    sort program) in the next handling information. The site does not
    have a zone-specific sort program to sort these zones. Instead,
    these zones are separated into a sort program where they will be
    dispatched to another mail processing facility.

    For local ADC 3-digit and 5-digit zones, SPS will search the Zone
    Table using the mail level and SCF listed in the Zone Table. If a
    match is found for a zone in only one sort program, then the machine
    used in that sort program will be used for the next handling
    information. For example, if local zone 79913 is assigned to Bin 5,
    it will be searched in the Zone Table. If it is matched in only one
    sort program (e.g., FV79913B), then the letter V (for Machine
    Type V) will appear in the next handling information for that bin.
    Mail in Bin 5 will be sorted on a DBCS during its next processing.

    In contrast, if a match is not found for a zone, SPS will add the \#
    or \* symbol to the next handling information. A match is not found
    when the site either does not have a sort program for the zone or
    has more than one sort program for it. When there is more than one
    sort program, SPS does not know on which MPE the mail will be
    sorted; it just knows that the mail will be sorted on one of the
    machines under the symbol provided.

    A local SCF/zone could be a remote DBCS; it will be local but shown
    as dispatch because it is in the Zone Table.

    The following next handling information will appear in managed mail
    processing (MMP, Mail Level C) label files:

  ----------------------------------- -----------------------------------
  **Bin Content**                     **Next Handling**

  No Ranges - RDRJ, MCRJ\...          MISC CZ20800

  ADCs - UNAS                         MISC CZ20800

  ADC                                 MISC CZ20800

  3D(s) -- Local                      SCF D#20800

  3D(s) - Local, ISS/A\*              SCF D\*20800

  3D(s) - Local, Direct City          INP E#20800

  3D(s) - Local, Direct City, ISS/A\* INP E\*20800

  3D(s) - Non-local                   DISP DZ60600

  3D(s) - Non-local, Direct City      DISP EZ60600

  5D(s) - Local, City State           SA F#20800

  5D(s) - Local, City State, ISS/A\*  SA F\*20800

  5D(s) - Local, Two Pass             SA G#20800

  5D(s) - Local, Two Pass, ISS/A\*    SA G\*20800

  5D(s) - Local, DPS                  SA L#20800

  5D(s) - Local, DPS, ISS/A\*         SA L\*20800

  5D(s) - Non-Local                   DISP EZ60600

  9D                                  DISP

  9D(s)/11D(s)                        DISP
  ----------------------------------- -----------------------------------

The next handling information listed below will appear in SCF (Mail
Level D) and INP (Mail Level E) label files:

  ----------------------------------- -----------------------------------
  **Bin Content**                     **Next Handling**

  No Ranges - RDRJ, MCRJ \...         MISC DZ20800

  ADCs - UNAS                         MISC DZ20800

  ADC                                 MISC DZ20800

  3D(s) -- Local                      SCF D#20800

  3D(s) - Local, ISS/A\*              SCF D\*20800

  3D(s) - Local, Direct City          INP E#20800

  3D(s) - Local, Direct City, ISS/A\* INP E\*20800

  3D(s) - Non-local                   DISP DZ60600

  3D(s) - Non-local, Direct City      DISP EZ60600

  5D(s) - Local, City State           SA F#20800

  5D(s) - Local, City State, ISS/A\*  SA F\*20800

  5D(s) - Local, Two Pass             SA G#20800

  5D(s) - Local, Two Pass, ISS/A\*    SA G\*20800

  5D(s) - Local, DPS                  SA L#20800

  5D(s) - Local, DPS, ISS/A\*         SA L\*20800

  5D(s) - Non-Local                   DISP EZ60600

  9D                                  DISP

  9D(s)/11D(s)                        DISP
  ----------------------------------- -----------------------------------

The following next handling information will appear in INS (Mail Levels
F--O) label files:

  ----------------------------------- -----------------------------------
  **Bin Content**                     **Next Handling**

  No Ranges - RDRJ, MCRJ \...         MISC FZ20800

  ADCs - UNAS                         MISC FZ20800

  9D(s)                               DISP

  11D(s)                              DISP
  ----------------------------------- -----------------------------------

# Appendix I. Identification Code Sorting

Identification Code Sorting (ICS) is a new system designed to use the
Remote Bar Coding System (RBCS) unique mail piece ID Tag to keep
unreadable Postal Numeric Encoding Technique (POSTNET) codes in the
automated mail stream without using the Letter Mail Labeling Machine
(LMLM), and therefore reducing additional handling.

ICS requires the deployment of both hardware and software at all sites
with automated equipment.

## ICS Special Bins 

Two ICS special bins exist for all bar code sorters (BCSs) supported by
SPS, except the Martin Marietta Delivery Bar Code Sorter (MM/DBCS). The
ICS rej/5D and ID tag high (as they are labeled in the Special Bin
Editor) bins are available for all mail levels, but only for the first
pass of two-pass and delivery point sequencing (DPS) sort programs.

The ICS rej/5D special bin is designed to collect mail rejected by the
wide area bar code reader (WABCR) or mail for which the WABCR can only
get a 5-digit result. The ICS ID tag high special bin will collect ID
tag reject mail if the mail piece is riding too high through the WABCR
or because of a photocell alignment problem.

Both of these special bins will only be used when there is no
communication between the ICS system and the WABCR.

The ICS special bins are present in the Special Bin Editor for all BCSs
(Machine Types H, P, R, U, and V), except Machine Type Q. These special
bins are listed at the bottom of the Special Bin Editor, with the ICS
rej/5D bin listed before the ICS ID tag high bin (see Figure I-1).

![](media/image18.emf){width="5.750694444444444in"
height="3.5069444444444446in"}

Figure I-1. MPBCS Special Bin Editor with ICS Special Bins

### Assigning ICS Special Bins

The ICS special bins are assigned in the Special Bin Editor in the same
manner as other special bins in the editor. The ICS bins can be assigned
individual bin numbers or combined with other special bins. ICS bins are
assigned in the following manner:

-   Both ICS bins will default to the read reject bin, if they are not
    assigned individual bin numbers. If the user decides to change the
    read reject bin assignment, both the ICS rej/5D and the ICS ID tag
    high bins will default to that bin assignment.

-   If the ICS rej/5D bin is assigned a bin number other than the read
    reject bin number, the ICS ID tag high bin will default to the new
    bin assignment for the ICS/5D bin.

-   If the ICS ID tag high bin is assigned a bin number other than the
    read reject or ICS rej/5D, than this mail will be sorted to its own
    bin and the ICS ID tag high label will appear in the SPS Editor.

In Figure I-1, the ICS rej/5D special bin was changed to bin 2;
therefore the ICS ID tag high special bin assignment also changed to bin
2. If the ICS special bins were not changed, they would have been
assigned to bin 1, like the read reject bin.

If the ICS special bins are assigned to a bin(s) separate from the read
reject bin, they will appear in the SPS Editor (see Figure I-2);
otherwise they are not labeled in the SPS Editor.

![](media/image19.emf){width="5.750694444444444in"
height="3.466666666666667in"}

Figure I-2. SPS Editor Containing ICS Special Bin Assignments

### Verifying Label File Information in the Label Editor 

Once all bins have been assigned in the SPS Editor, the user should
check the Label Editor to confirm that all label information is correct.
The user should make sure that the bins assigned to ICS special bins
contain the correct information. (For more information on the Label
Editor, see Chapter 12.)

#### CIN Values and Priorities

The CIN column contains values that describe the contents of a bin. CIN
values and their text descriptions are used on a tray label to specify
the mail type. Both ICS special bins will receive a default of 945 (FCM
TMO/ZNR/ZPR) in the Label Editor (see Figure I-3).

![](media/image20.emf){width="5.750694444444444in"
height="3.5069444444444446in"}

Figure I-3. Label Editor Containing ICS CINs

A labeling and CIN hierarchy are applied to bins that contain more than
one special bin assignment. The special bins used when creating a sort
program depends on the type of machine being used. The ICS special bins
are contained within the label and CIN hierarchy for the appropriate
BCS. The ICS ID Tag High bin has the lowest labeling and CIN priority of
all special holdout bins. This means that any time the ICS ID Tag High
bin is combined with another special holdout bin, it will be considered
last for assigning a label and CIN in the Label Editor.

The ICS Rej/5D special bin also contains a low labeling and CIN
priority, but contains a higher labeling priority than the ICS ID Tag
High special bin, it will be considered last when assigning the bin's
label and CIN in the Label Editor. (For more information about CIN and
labeling priorities, see Chapter 12 and Appendix G.)

### Viewing a Mail Tray's Next Processing Step

Next handling information is available for the user to view a tray's
next processing step. Next handling descriptions are based on the mail
level and the contents of each bin. The user can access this information
using **\<PF1 W\>** and **\<PF1 Y\>**.

In the following example, the user has pressed **\<PF1 Y\>** to view the
next handling information for bin 2, which contains ICS special bins in
sort program AH79910H.

![](media/image21.emf){width="5.750694444444444in"
height="3.466666666666667in"}

Figure I-4. Next Handling Information for Bin 2 in the SPS Editor

Like other special bins assigned in a sort program, the ICS special bins
receive a miscellaneous (*MISC*) handling type. This means that the mail
could not be sorted by range and each facility will have to decide how
to further process this mail. Like read reject mail, mail sent to the
ICS special bin(s) will often proceed to manual casing.

(For more information about viewing a tray's next handling information,
see Chapter 12.)

# Appendix J. Other Resources

In addition to this guide, there are other resources that the user may
find helpful when learning about or working with the Sort Program System
(SPS). This list, however, is not an exhaustive list of the resources
available. Users may contact their local Density Analysis Specialist
(DAS) for information about the following resources or for additional
resources. Other publications may be available from the United States
Postal Service (USPS) Engineering Web site at http://eng.usps.gov.

*CSBCS Operations and Servicing Training Student Guide*, United States
Postal Service, 1995.

*Delivery Bar Code Sorter Training Program Student Guide Course
50519-01*, United States Postal Service, Management & Employee
Development, 1995.

*FIM Processing Guidelines*, United States Postal Service.

*Flats Processing Guidelines Publication 123*, United States Postal
Service, Corporate Publishing & Information Management.

*Glossary of Postal Terms Publication 32*, United States Postal Service,
Corporate Publishing & Information Management, 1997.

*M-32 Manual*, United States Postal Service.

*Managing Images and Mail Flows*, United States Postal Service, 1997.

*NDSS v5.3 Release Notes*, United States Postal Service, Software
Design, 1997.

*Postal Operations Manual*, United States Postal Service.

*Sorting Mail to the Delivery Point: a DPS User's Guide*, United States
Postal Service, Software Design, 1997.

*Sort Program Development Guide*, Pacific Area Processing &
Distribution, In-Plant Support, 1994.

*SPS-RBCS Course #50284-05 Facilitator Guide,* United States Postal
Service, In-Plant Operations, 1996.

*SPS-RBCS Course #50284-05 Student Workbook*, United States Postal
Service, In-Plant Operations, 1996.

*SPS Release Notes, v3.2* through *v6.1*, United States Postal Service,
1992--1999.

*Sort Program System Training Course #50284-00 Facilitator Guide*,
United States Postal Service, In-Plant Operations, 1997.

*Sort Program System Training Course #50284-00 Student Workbook*, United
States Postal Service, In-Plant Operations, 1997.

*USPS-NDSS OpenVMS Reference Manual*, Compaq Computer Corporation,
Network and Systems Integration Services, 1998.

*WinSSI v1.0 User\'s Guide*, United States Postal Service, Software
Design, 1998.

*WinSSI v2.0 Release Notes*, United States Postal Service, Engineering
Software Management, 1999.

# Glossary

**+4:** *See* +4 add-on.

**+4 add-on:** The four digits following the 5-digit ZIP Code.

**5-D RBCS mail bin:** This bin, which is only for MLOCR-As equipped
with ISSs, will contain partially resolved 5-digit bar coded mail.

**9999 bin:** A bin for 9999 mail that is labeled \"No Improvement\" in
the SPS Editor.

**9999 mail:** Mail, also known as no improvement mail, that cannot be
improved beyond five digits and has *9999/55* sprayed on the mail piece
as a placeholder in the Remote Bar Coding System.

**AADC:** *See* Automated Area Distribution Center (AADC).

**AADC/ADC Exception Report:** A sort program exception report that
identifies all U version outgoing primary and outgoing secondary sort
programs that do not have one or both of the following: a) a bin that
contains exactly the set of ranges associated with an AADC/ADC entry; b)
a label that contains the city and state values for that AADC/ADC entry.

**AADC Tables:** Tables for outgoing letter mail sort programs that are
accessed within SPS\'s Automated Editor. These tables contain the most
up-to-date ZIP Code ranges and city/state information for a site from
the national AADC tables.

**ADC:** *See* Area Distribution Center (ADC).

**ADC Tables:** Tables accessed within the SPS Editor that provide city,
state, and keycode data for outgoing mechanized sort programs and
outgoing automated sort programs for flat mail. These tables are
accessed within either the Mechanized Editor (for outgoing mechanized
sort programs) or the Automated Editor (for outgoing automated sort
programs for flat mail).

**Add-on:** *See* +4 add-on.

**Address Management System (AMS):** A database of all the addresses in
the nation that contains address information from Delivery Units
throughout the nation.

**Address script (ADS):** A program in the remote computer reader that
determines how handwritten addresses are processed.

**Advanced Facer Canceller System (AFCS):** Mail processing equipment
that faces, cancels, and separates all stamped originating machinable
letter mail into three mail flows for outgoing distribution operations.

**Air stop:** A three-character airport destination (e.g., IAD, DWF)
listed in the SPS Label Editor and on bin labels. It designates the
airport to which a particular bin of mail will be flown.

**Alphakey sort program:** A sort program used to sort flat mail that
does not contain a bar code on an FSM.

**Area Distribution Center (ADC):** A national distribution network that
handles the distribution and routing of all flats and non-machinable
letters. ADCs define the mail flow between facilities for all first
class flats and non-machinable letter mail.

**Associate office (AO):** A USPS remote site.

**AUTO bar code:** A bar code that is applied by customers who are
authorized to spray a bar code in the POSTNET area. This type of bar
code is preceded by the word \"AUTO\" to distinguish it from
USPS-applied POSTNET bar codes.

**Automated Area Distribution Center (AADC):** A national distribution
network that handles the transportation and routing of all machinable
letters that are processed by automation. AADCs define the mail flow
between facilities for all first class letter mail that must be
processed by automation equipment.

**Automated Editor:** The SPS Editor that is used to create and maintain
sort programs for bar coded letter and flat mail.

**Automation:** The process of sorting mail using computerized
equipment.

**Auto-update:** *See* update sort programs utility.

**Bar code:** A series of tall and short bars representing a mail
piece\'s ZIP Code and other identifying numbers. Bar codes can be used
to sort 5-digit, 9-digit, or 11-digit mail.

**Bar code reader (BCR):** A piece of equipment that reads a POSTNET bar
code on the lower right-hand corner of a mail piece.

**Bar code sorter (BCS):** Mail processing equipment that resides in the
plant and sorts letter mail, based on the POSTNET bar code, to bins as
directed by a sort program.

**Batch mode:** A mode for a process (e.g., download conversion) in
which the process occurs in the background; the user can not see any
indication of the process occurring. During this time, the user can
perform other functions in SPS.

**.BBF:** Bar code binary format. A file format that is read by FSM/BCRs
and FMOCRs.

**BCR:** *See* bar code reader (BCR).

**BCS:** *See* bar code sorter (BCS).

**Bin chaining:** A function used to assignor chain bins together in
order to prevent mail from overflowing in a bin.

**Bin sweeping:** The process of lifting mail out of the bins and into
boxes for transport to whatever kind of transportation.

**Box sort program:** A sort program used to sort incoming secondary
mail to box wall units.

**Browser:** A utility in SPS that enables the user to view and print a
listing of files connected with different SPS tables and records.

**BRM bin:** A bin for business reply mail.

**Business reply mail (BRM):** Specially printed cards and envelopes
that may be mailed without prepayment of postage. The postage and fees
are collected from the account holder when the mail is delivered to the
addressee.

**Carrier-flagged:** A state in which a bin in the Condensed Editor will
have its carrier ID's NDSS data included when the incoming secondary
sort program is updated with the update sort programs utility. By
default, bins are \"carrier-flagged\" in the Condensed Editor.

**Carrier Sequence Bar Code Sorter (CSBCS):** A small machine used in
some Delivery Units and Post Offices that was designed for processing
incoming secondary mail to the delivery point sequence.

**Carrier mapping:** A function used as part of the carrier piece count
project. When the user assigns bins to carriers in the Carrier Mapping
Table, SPS can calculate an automated piece count of the carriers
assigned in the sort program.

**Carrier Mapping Table:** A table for incoming secondary sort programs
that allows the user to map bin numbers to carriers.

**Certified mail:** A special mail service where the sender pays an
extra fee to guarantee a mail piece\'s delivery. The USPS provides the
sender with a mailing receipt and a record of delivery at the office of
address.

**Certified mail detector (CMD):** A piece of hardware attached to the
ECA/DBCS that detects certified mail.

**CFS mail bin:** A bin for mail with a change of address that can be
assigned for mail processing equipment with an OSS. Mail in this bin
will go to the Computer Forwarding System (CFS).

**CIN:** *See* content identifier number (CIN).

**City/state files:** Files that provide 5-digit ZIP Code data for SPS's
City/State Tables.

**City/State Table:** A table that contains city/state names, 3-digit
ZIP Code prefixes, and 5-digit ranges gathered from city/state files.
This table is accessed from the Automated Editor in managed mail
processing, sectional center facility, and incoming primary sort
programs.

**CMD bin:** A bin for certified mail. If the mail processing equipment
being used does not have a certified mail detector (CMD), SPS will treat
the certified mail as residue mail.

**COA bin:** A bin for MLOCR-Bs where the user can hold out mail with a
change of address (COA).

**Computer Forwarding System (CFS):** A system that places the bar code
for a new address on mail with a change of address.

**Condensed Editor:** An SPS Editor that can be used to create and
maintain single-pass incoming secondary sort programs for bar coded
mail. This bin editor displays bin information in a condensed version,
allowing the user to view more bins at once than the Automated Editor
allows.

**Content identifier number (CIN):** A 3-digit code specifying mail
characteristics (e.g., mail class, shape, sort level, and bar code
status).

**Content identifier number (CIN) table:** A table containing all the
available content identifier number values and their corresponding
content identifier number text. This table can be accessed through the
Label Editor by pressing **\<F7\>**.

**CSBCS:** *See* Carrier Sequence Bar Code Sorter (CSBCS).

**CSBCS Station PC (SPC) Management System:** The system used to create
sort programs for CSBCS sites.

**Cutoff times:** Facility operations records that provide a list of
times when mail must be ready to leave the facility in order to meet the
transportation schedule.

**Data conversion operators (DCOs):** Employees at Remote Encoding
Centers who type address information from mail piece images in order to
obtain the mail pieces\' ZIP Codes and return them to the appropriate
plant\'s Image Processing Subsystem.

**DBCS:** *See* Delivery Bar Code Sorter (DBCS).

**Decision storage unit (DSU):** A part of the Image Processing
Subsystem that stores results of an image when a bar code is found.

**Delivery Bar Code Sorter (DBCS):** Multi-tiered automation equipment,
manufactured by ElectroCom Automation (ECA) or Martin Marietta (MM),
that enables the United States Postal Service to sort letter mail to the
carrier\'s delivery sequence by using delivery point sequencing sort
programs.

**Delivery day:** The day of the week when mail is to be delivered,
usually printed on the label of a mail tray.

**Delivery point bar code (DPB) files:** Files generated from delivery
point files that contain sequence files used to create delivery point
sequencing sort programs. SPS Station Input files are applied to these
files.

**Delivery point bar codes (DPBs):** Eleven-digit bar codes that are
used to sort mail to the delivery point through delivery point
sequencing.

**Delivery point files (DPFs):** Files that are used to create two-pass
sort programs, including sector/segment and delivery point sequencing
sort programs. These files contain address information from the Address
Management System, such as street names and numbers, grouped together by
carrier ID and sequence number (i.e., the order in which the carrier
will deliver mail to addresses).

**Delivery point sequencing (DPS):** The process of automating letter
mail to the order in which carriers walk their routes.

**Delivery Unit:** The unit at a facility that delivers mail.

**Density:** *See* mail density.

**Density Analysis System (DAS):** A computerized system to collect and
analyze ZIP Code information used to increase the efficiency and
productivity of a facility's automate mail sorting and manual
distribution equipment.

**Directory Analysis Specialist (DAS):** A member of the In-Plant
Support staff that performs the weekly Refresh.

**Dispatch label:** The actual label printed out by the machine and
attached to a mail tray. Contents appearing on this label are crucial
for getting mail to its destination.

**Display label:** A liquid crystal display (LCD) that contains label
information. It is located at or above each bin on mail processing
equipment.

**Distribution records:** Facility operations records detailing where
mail will be distributed.

**Double feed bin:** Bins for mail pieces that have been keyed as
\"double\" in the OSS because one mail piece has been unintentionally
attached to another.

**Downflows:** Mail flows with residue volumes of mail that must be
processed in a later operation.

**Download conversion:** The process of converting a sort program from a
generic, or

human-readable file, to a loadable file that is read by the machine.

**DPS:** *See* delivery point sequencing (DPS).

**DPS digits:** The last two digits in an 11-digit ZIP Code, which
correspond to the last two digits of a delivery point\'s address number.

**DPS sort program:** A two-pass incoming secondary sort program that
sorts mail to the carrier\'s walk sequence.

**Due sort program:** An incoming secondary sort program used to sort
mail with postage due (e.g., business reply mail).

**Dump constant:** The number of labels that will be printed from a
machine for a given bin.

**.EBF:** Extended binary format. A file format that is read by MPBCSs
and DBCSs.

**ElectroCom Automation Delivery Bar Code Sorter (ECA/DBCS) Phase I:** A
two-sided, three-tiered machine with up to 222 bins.

**ElectroCom Automation Delivery Bar Code Sorter (ECA/DBCS) Phase
II--IV:** A single-sided, four-tiered machine with up to 222 bins.

**Extraction codes:** Site-specific codes used with Alphakey sort
programs that an FSM operator will key into a console. These codes are
composed of certain alphanumeric elements of a street address.

**Facility characteristic records:** Facility operations records showing
a facility\'s layout and floor plan information.

**Facing identification mark (FIM):** A series of vertical bars used by
automated postal equipment that identifies, orients, and separates
business reply mail, courtesy reply mail, and official mail. The bars
are located in the upper right corner of the mail pieces (to the left of
the postage area), and serve as orientation marks for the automated
facing and canceling equipment.

**.FBF:** Flat binary format. A file format that is read by FSM 881s and
FSM 1000s.

**Firm/Building Table:** A table accessed from the Automated Editor and
Condensed Editor that contains firm/building data from the Address
Management System. Thius table is for incoming secondary,
sector/segment, and delivery point sequencing sort programs.

**Flat mail:** A piece of mail that exceeds at east one of the
dimensions for letter-size mail (i.e., 11-1/2" long, 6-1/8" high, ¼"
thick), but does not exceed the maximum dimensions for flats (i.e., 15"
long, 12" high, 3/4" thick). A flat may be unwrapped, paper wrapped,
sleeve wrapped, or enveloped.

**Flat Mail Optical Character Reader (FMOCR):** An FSM with an OCR
attached for processing flat mail that does not have a bar code.

**Flat Sorting Machine (FSM):** Mail processing equipment that processes
flat mail pieces (i.e., magazines, newspapers).

**Flat Sorting Machine Bar Code Reader (FSM/BCR):** An FSM with a bar
code reader attached for processing flat, bar coded mail that can be run
on mail processing equipment.

**Foreign bin:** A bin for mail processing equipment with an OSS that
holds mail with a foreign address.

**Foreign mail bin:** A bin for mail pieces having foreign addresses
that is assigned in sort programs involving the OCR and/or ISS.

**FSM:** *See* Flat Sorting Machine (FSM).

**Function numbers:** *See* Management Operating Data System (MODS)
function numbers.

**Handwritten Address Interpretation (HWAI) System:** A component of the
remote computer reader that processes handwritten addresses.

**Header only bin:** When the OSS looks up an ID tag and cannot resolve
it, and the file comes back as only a header, the mail piece goes into
this bin.

**ICS ID tag high bin:** This bin will collect ID tag reject mail if the
mail piece is riding too high through the Wide Area Bar Code Reader or
there is a photocell alignment problem.

**ICS rej/5D bin:** A bin designed to collect mail rejected by a Wide
Area Bar Code Reader or mail for which the Wide Area Bar Code Reader
could only get a 5-digit result.

**ID tag:** A unique, orange florescent, bar/no bar identification bar
code sprayed on the back of a mail piece by the ISS.

**ID tag unreadable bin:** This bin contains mail with an ID tag that
could not be read by the OSS ID tag reader.

**Identification Code Sorting (ICS):** A system designed to use the
Remote Bar Coding System\'s unique mail piece ID tag to keep unreadable
POSTNET bar codes in the automated mail stream without using the Letter
Mail Labeling Machine, thereby reducing additional handling.

**Identification error bin (ident. error bin):** A bin for mail pieces
with errors tracked through the OCR.

**Image Processing Subsystem (IPSS):** The central computer in each
facility used to collect and store images for processing. The IPSS
manages both the processing of images captured by an ISS and the results
of the processed images.

**Incoming mail:** Mail destined for delivery within the service area of
the facility. This mail may be received from the local plant\'s service
area or from other facilities or sites of origin.

**Incoming primary (INP) sort program:** A sort program that provides
the first sort for mail received from other mail processing facilities
that is destined for local city delivery.

**Incoming secondary (INS) sort program:** A sort program that is used
to sort mail to the carrier or box section ID.

**Incoming operations:** Operations that process mail that is destined
for local delivery. This includes both turn-around mail from the
originating mail stream and incoming mail received by the plant from
other mail facilities.

**Ink jet printer (IJP):** Part of an OCR or OSS that sprays the POSTNET
bar code on a letter.

**Input Subsystem (ISS):** An interface used to collect and transmit
mail piece images to be processed by RBCS. It captures video images of
mail pieces that cannot be read by a machine and transmits them to the
IPSS. It also applies a unique florescent ID tag on the back of the mail
piece.

**Interactive mode:** A mode for a process (e.g., download conversion)
that occurs in the foreground; the user sees messages indicating the
status of the process.

**ISS:** *See* Input Subsystem (ISS).

**ISS reject mail:** Mail with flourescent ID tags that the ISS cannot
read.

**Jet printer bin:** This bin contains mail pieces sorted through OCR
and ISS sort programs that do not have a POSTNET bar code sprayed on
them.

**Label:** A printed strip of paper placed in label holders of cases,
pouches, or sacks showing destination, class or mail type, office
distribution, and routing instructions. It includes descriptive
information regarding a tray's content and mail flow for each bin.

**Label file:** *See* .LAB file.

**Labeling lists:** The contents of SPS\'s Label Editor.

**Labeling records:** Facility operating records describing the contents
of containers used to distribute mail to the correct destination.

**Label Editor:** An editor accessed from the SPS Editor that shows
information that will appear on the dispatch or printer label. It allows
the user to view, edit, and maintain labels for each bin.

**.LAB file:** A file that contains the label information for a sort
program.

**Late/loop bin:** A bin for some incoming sort programs that contains
late/loop mail.

**Late/loop mail:** Mail that has been in the system more than the
number of threshold value days.

**Letter mail:** A mail processing category of mail pieces, including
cards, that do not exceed these dimensions:11-1/2" long; 6-1/8" high; ¼"
thick.

**Letter Mail Labeling Machine (LMLM):** A machine that places a label
on mail pieces to either cover the POSTNET bar code on the front or the
ID tag on the back.

**Letter misfaced bin:** A bin for mail pieces that have been keyed as
misfaced in the OSS.

**Loadable file:** A binary file that can be read by mail processing
equipment. It contains combined information from a sort program\'s .SPS
file and .LAB file.

**Local:** A site where the Station Input software is running on the
NDSS/Alpha and the user is logged on to the Alpha.

**Local Area Network (LAN):** Cabling that allows the electronic
transfer of data.

**Log file:** A file that compares old SPS data with new SPS data.

**Logistics orders:** Instructions that tell the sort program developer
which ZIP Codes can be programmed together for a specific mail type for
each class of mail.

**Machinable mail:** Letters and flats that can be run on mail
processing equipment.

**Machine:** *See* mail processing equipment.

**Machine type:** *See* mail processing equipment.

**Machine type codes:** Letters of the alphabet used to designate each
machine type.

**Mail density:** How much mail flows to a given destination.

**Mail flow:** The movement of mail within a facility or between mail
processing facilities.

**Mail levels:** Categories that represent the mail processing
operations needed to satisfy the depth of distribution at each
processing level.

**Mail level codes:** Letters of the alphabet that represent each mail
level.

**Mail processing code (MPC):** A 1-digit code representing the type of
mail processing being used to sort the mail in a bin.

**Mail Processing Bar Code Sorter (MPBCS):** Automation equipment that
sorts letter mail, based on the bar code, to a bin based upon bin
assignments made within a sort program.

**Mail processing equipment (MPE):** Machines that use sort programs
created in SPS to sort mail to the current mail level.

**Managed mail processing (MMP) sort program:** A sort program that
provides the first sort for mail destined for outside of the local
service area but still within the logistic assignment of the Area
Distribution Center or Automated Area Distribution Center that receives
the mail.

**Management Operating Data System (MODS):** A system of accounting used
for planning and controlling activities within Post Offices. MODS
offices enter data concerning actual versus projected work hours and
workloads into MODS. This information is communicated back to Post
Offices for use in planning and projecting both work hours and mail
volumes.

**Management Operating Data System (MODS) operation numbers:** Numbers
used for mail preparation, letter mail distribution, and flat mail
distribution that identify the specific mail level and type of MPE (or
other process type) used at each point in a mail flow.

**Management Operating Data System (MODS) function numbers:** Numbers
used to identify nine major categories of business functions.

**Manual matrix sort program:** A sort program used to create an ASCII
(or text) file that people can read. Operators use this text as a chart
to manually sort mail pieces.

**Martin Marietta Corporation Delivery Bar Code Sorter (MM/DBCS):** A

single-sided, four-tiered machine with up to 220 bins.

**Mechanical reject (mech./rej.) bin:** A bin common to all mail
processing equipment that holds mechanical rejects. While each machine
has at least one of these bins, most of the time their number is fixed
(i.e., not editable by the user).

**Mechanical rejects:** Mail that is not able to be tracked properly
because of mechanical problems on mail processing equipment and cannot
be placed in its proper bin.

**Mechanized operations:** Processes that require mail processing
equipment operators to enter specific portions of a mail piece\'s
address on mechanized equipment (e.g., FSMs). Keycodes entered by the
operator are then translated into bin numbers by the sort program.

**Mechanized City/State Tables:** City/State Tables that apply to
mechanized flat mail for the FSM 881 and FSM 1000.

**Mechanized Editor:** The SPS Editor used to create sort programs for
non-bar coded flat mail.

**Mix sort program:** *See* mixed mail sort program.

**Mixed mail sort program:** An incoming secondary sort program that
sorts mail with mixed mail levels.

**MLOCR:** *See* Multiline Optical Character Reader (MLOCR).

**MLOCR A Star Special Bin Editor:** A Special Bin Editor used when
creating sort programs for an MLOCR with an ISS.

**MLOCR rejects:** Mail pieces that cannot be bar coded on the MLOCR.

**MPBCS:** *See* Mail Processing Bar Code Sorter (MPBCS).

**Multiline Optical Character Reader (MLOCR):** Mail processing
equipment designed to apply a POSTNET bar code on mail pieces that will
later be sorted on a bar code sorter.

**Multi-Position Flat Sorting Machine:** *See* Flat Sorting Machine.

**National Directory Support System (NDSS):** The system that maintains
and updates the databases and files necessary to sort mail on automated
equipment.

**National distribution networks:** Systems used by the USPS for
distributing mail on a national level. The two major distribution
networks for first class letter and flat mail processing are ADCs and
AADCs.

**National Distribution Network Logistics Directory:** A listing of
facilities that defines transportation routing distinguishing the mail
flow between facilities. This listing includes the name of each facility
and the ZIP Codes assigned to each one. Different directories apply to
different categories or classes of mail.

**NDSS:** *See* National Directory Support System (NDSS).

**NDSS Alpha:** The computer on which SPS resides.

**NDSS Refresh:** A process by which the data on the NDSS Refresh tape
is copied to the local NDSS Alpha, where the data is made available for
use by SPS.

**NDSS Refresh tape:** The 8-mm tape that contains the data needed to
create and maintain sort programs. It is sent from San Mateo Integrated
Business Systems Solutions on a weekly basis to sites around the
country.

**Next handling:** The next processing step for a tray of mail. This
information helps to create a more accurate label for the mail tray.

**No linear measurement (NLM):** A designation in the Label Editor for a
bin with an automated piece count (i.e., a bin that does not have to be
counted manually).

**No code bin:** A bin for mail without a bar code found on all DBCS and
MPBCS machines..

**No ID tag found bin:** A bin for the mail processing equipment with an
OSS that holds mail pieces for which the OSS could not find an ID tag.

**No improvement mail:** *See* 9999 mail.

**Non-machinable mail:** Letter or flat mail that normally cannot be run
on MPE and therefore is usually sorted manually.

**Non-POSTNET bin:** Mail pieces that the OCR could not read are placed
in this bin. These mail pieces have a valid ID tag but no ZIP Code
resolution.

**OCR:** *See* optical character reader (OCR).

**Old ID tag bin:** Mail with a date in the ID tag that exceeds the
expired date programmed into the OSS computer goes here.

**Old tag bin:** If the date on the ID tag exceeds the expired date
programmed into the ISS, the mail is placed in this bin.

**OpenVMS:** *See* Virtual Memory System (VMS).

**Operating plan:** A structured document outlining mail processes to be
performed and target times that an office should meet to achieve service
standards.

**Operation numbers:** *See* Management Operating Data System (MODS)
operation numbers.

**Operation support specialist (OSS):** A member of In-Plant Support who
provides operations support directly to a plant\'s staff and also is
often the sort program developer for that site.

**Operations records:** Records kept by facilities to keep create
efficient sort programs. These may include facility characteristic
records, distribution records, labeling records, cutoff times, transfer
times, and service standard records.

**Optical character reader (OCR):** A piece of equipment that scans the
delivery address of mail without a bar code, determines the correct ZIP
Code, and applies a bar code in the lower right-hand corner of the mail
piece.

**Originating mail:** Outgoing mail and local (turn-around) mail that
have their first processing in the outgoing distribution operations of a
particular facility.

**OSS:** *See* Output Subsystem (OSS).

**Outgoing mail:** Originating mail destined for delivery to other mail
facilities outside of the plant's service area.

**Outgoing primary (OGP) sort program:** A sort program that provides
the first sort for mail originating at a mail processing facility,
whether the mail is being dispatched to other facilities or is
turn-around mail for local delivery.

**Outgoing secondary (OGS) sort program:** This type of sort program is
used to sort outgoing mail that has not been finalized in an outgoing
primary sort program.

**Outgoing operations:** Operations that process mail that originates at
a plant, whether destined for local delivery (i.e., turn-around mail) or
for locations outside of the plant\'s service area. These operations
will sort the mail to both 3-digit and 5-digit separations.

**Output Subsystem (OSS):** The interface that returns ZIP Code
information from the Image Processing Subsystem to a bar code sorter\'s
computer so that it can apply a POSTNET bar code to a mail piece.

**P&DC:** *See* Processing and Distribution Center (P&DC).

**P&DF:** *See* Processing and Distribution Facility (P&DF).

**Partially resolved:** Mail pieces that receive only 5-digit results
within the ISS process.

**Pending files:** Files that are created when Delivery Unit changes are
made to SSI files. These files are applied to SSI files on the local
NDSS Alpha.

**Pick list:** A list of sort program loadable names needed for
transferring a sort program to the mail processing equipment.

**Piece count:** The number of mail pieces processed as determined by
meter, machine print out, or an actual count.

**Plant:** *See* Processing and Distribution Center (P&DC).

**Postage Due Table:** A table accessed from the Automated Editor for
Due sort programs that has postage due data for firms and buildings.

**Postal Alphanumeric Encoding Technique (PLANET) bar code:** A bar code
applied by mailers that looks like a POSTNET bar code but is used for
mail tracking instead of to sort mail.

**Postal Numeric Encoding Technique (POSTNET) bar code:** A bar code
applied by the United States Postal Service in the lower right-hand
corner on the front of a mail piece.

**POSTNET bar code:** *See* Postal Numeric Encoding Technique (POSTNET)
bar code.

**Primary operation:** An operation that aims to establish the first
level for sorting outgoing and incoming mail, and to minimize later
operations. Primary operations may involve outgoing primary, incoming
primary, sectional center facility, and/or managed mail processing sort
programs.

**Printer label:** *See* dispatch label.

**Processing and Distribution Center (P&DC):** A central mail facility
that processes and dispatches part or all of both incoming mail and
outgoing mail for a designated service area. The facility is usually
also a sectional center facility or general mail facility, but it can
also be a dedicated mail processing center with no "public" Post Office
attached.

**Processing and Distribution Facility (P&DF):** A facility that serves
the same purpose but is usually smaller than a P&DC.

**Range discrepancy report:** A sort program exception report that
identifies cases where more ranges are contained in a bin than are
associated with the AADC/ADC data.

**Range and label discrepancy report:** A sort program exception report
that identifies instances when either a bin\'s label does not contain
the city and state for an AADC/ADC entry or the bin itself does not
contain all of the ranges associated with an AADC/ADC entry.

**RBCS:** *See* Remote Bar Coding System (RBCS).

**RBCS A\* Bin Editor:** An editor for ISS sort programs where users can
assign ranges of mail with partially resolved images to Remote Bar
Coding System bins.

**RBCS Special Bin Editor:** A Special Bin Editor that appears in sort
programs for mail processing equipment with an OSS.

**Read reject bin:** A bin for read reject mail found on all mail
processing equipment except the FSM 881 and FSM 1000.

**Read reject mail:** Mail that cannot be read by mail processing
equipment.

**Remote site:** A site in which the user is logged into the station
input software running on a PC.

**Remote Bar Coding System (RBCS):** A collection of subsystems designed
to allow letter mail that is not readable by an OCR, such as script
mail, to be bar coded.

**Remote computer reader (RCR):** A component of the Remote Bar Coding
System that is designed to recognize and interpret address information
on a mail piece image and return a ZIP Code result to the Image
Processing Subsystem.

**Remote Encoding Center (REC):** The facility where data conversion
operators process mail piece images that are not resolved by the remote
computer reader.

**Residue bin:** A bin for incoming secondary sort programs that
contains residue mail.

**Residue mail:** Mail pieces bar coded with any range within the sort
program\'s zones that does not have a bin assignment.

**Resolved:** A state in which a mail piece operating through an ISS has
reached its finest depth of code---either 9-digit, 11-digit, 5-digit
unique or 5-digit Non-Automated Zones with a bar code---and finalized to
a bin.

**San Mateo Integrated Business Systems Solutions (SMIBSS):** The
center, formerly known as the San Mateo Integrated Systems Solutions
Center (SMISSC), that maintains, generates, and distributes the national
directories included on the weekly National Directory Support System
Refresh tape.

**Scheme:** *See* sort program.

**Scheme records:** Records that contain information reflecting the
planned routing of deliveries within a small geographic area.

**Secondary operation:** A mail sorting operation that focuses on mail
already sorted once in an effort to refine the sort. Secondary
operations may involve outgoing secondary, incoming secondary, mixed,
box, and/or due sort programs.

**Sectional center facility:** 1. A Postal facility that serves as the
distribution and processing center for Post Offices in a designated
geographical area, which is defined by the first three digits of the ZIP
Code of those offices. This facility may serve more than one 3-digit ZIP
Code range. 2. The first three digits of a ZIP Code.

**Sectional center facility (SCF) sort program:** A sort program that
sorts incoming mail destined for associate offices and Post Offices
within the local service area.

**Sector:** The sixth and seventh digits of a ZIP +4 code. It is a
geographic portion of a ZIP Code area or a rural route, several city
blocks or a large building, part of a Post Office box section, or an
official designation.

**Sector/segment:** *See* +4 add-on.

**Sector/segment sort program:** A two-pass incoming secondary sort
program that sorts mail in carrier case or box sequence to the ZIP +4.

**Segment:** The eighth and ninth digits of a ZIP +4 code. It is a
specific block face, apartment house bank of boxes, a firm, a floor in a
large building, or other specific location.

**Service standard:** The number of days by which a mail piece should
arrive at its destination.

**Service standard records:** Facility operations records showing the
time it takes for mail to reach its destination.

**Service standard table:** A table that contains information on the
service standard for sending mail from one city to another.

**Service standard value:** *See* service standard.

**Small Parcel and Bundle Sorter (SPBS):** Mail processing equipment
designed to sort small packages and bundles.

**SONIKS:** A training program used by the Postal Educational
Development Center to maintain scheme training. It is accessed within
SPS from the Sequence Database (Two-Pass) Editor menu.

**Sort plan:** *See* sort program.

**Sort program:** A computerized plan for assigning ZIP Codes or
keycodes to bins. Sort programs are used to sort mail to specific mail
levels based upon an individual plant\'s operations and mail flows.

**Sort program developer:** A United States Postal Service employee,
usually an operation support specialist or another member of In-Plant
Support, who creates and maintains sort programs.

**Sort program exception reports:** Diagnostic utilities that verify the
accuracy of outgoing sort program data based on national data from
Automated Area Distribution Center/Area Distribution Center Tables.
There are three types of sort program exception reports: Range
Discrepancy Reports, Range and Label Discrepancy Reports, and AADC/ADC
Exception Reports.

**Sort program name:** A designation for a sort program that consists of
eight characters expressed in the formula: mail level + machine type +
zone + version.

**Sort Program System (SPS):** A software application that serves as a
centralized resource for developing and maintaining sort programs on
both automated and mechanized MPE.

**Special Bin Editor:** A list of bins that appears in every sort
program for separating mail that cannot otherwise be sorted.

**Special handling codes:** Codes used by the machine in order to send
special handling mail pieces to the correct bins.

**SPS Editor:** The main editor involved in creating and viewing sort
programs where the user assigns ranges to bins. This editor may appear
as one of three different editors, depending upon the sort program being
created: the Automated Editor, the Condensed Editor, or the Mechanized
Editor.

**.SPS file:** A file containing a sort program.

**SPS Refresh:** A process by which a module within the SPS software
looks at directories, tables, and files, and assigns correct files to
their associated regions by matching the file with a site\'s sectional
center facility. This usually occurs during the weekly National
Directory Support System Refresh, but the user can complete it using SPS
if necessary.

**SPS Station Input (SSI) files:** Files generated from delivery point
files that are used in the Windows Station Input Editor by Delivery
Units in order to make changes to the way mail is sorted. These files
will later be applied to delivery point bar code files to create
delivery point sequencing sort programs.

**SPXFER:** The software used to transfer the loadable version of the
sort program to the mail processing equipment.

**Srtplan.LXX files:** Loadable files for MLOCR-As, where XX represents
a 2-digit number that the user enters.

**Srtplan.LXXX files:** Loadable files for MLOCR-Bs, where XXX
represents a 3-digit number that the user enters.

**Stacker:** A synonym for bin.

**Standard text format (STF) files:** The files that describe the
contents of a sort program. They contain data for sorting the mail,
including a header, range records, and bin assignments.

**Start bin:** A bin for MPBCS machines that allows the user to decide
whether to start sorting the mail with bin 2 or bin 94 on the even side
of the machine.

**.STF file:** Standard text format file. A human-readable file that
contains information from both the .SPS file and .LAB file.

**Sunday download:** A process by which SSI files are transferred to the
SPC at CSBCS sites. This process is initiated when a Sunday download
program from the SPS Refresh tape runs shortly after midnight on Sunday
morning.

**Threshold value days:** The number of days mail can be in the system
before considered late/loop mail.

**Time out bin:** This bin is reserved for mail that the OSS queried,
but did not receive results in time to spray a POSTNET bar code on the
mail piece.

**Transfer times:** Facility operations records that provide a list of
times when the transportation vehicles will deliver mail to their
destination.

**Transportation records:** Records that record the availability of
transportation modes needed in moving the mail.

**Unassigned bin:** A bin common to all mail processing equipment that
holds unassigned mail.

**Unassigned mail:** Mail with ranges that are not assigned to any bin
or bar coded with a zone that is not a part of the sort program.

**Unreadable image bin:** Mail with an unreadable address goes into this
bin.

**Unresolved:** A state in which a mail piece has incomplete ZIP Code
information (e.g., only a 5-digit ZIP Code where an 11-digit ZIP Code is
possible).

**Update sort programs utility:** A utility normally run following the
NDSS Refresh that allows the user to update single-pass incoming
secondary sort programs with data from the Address Management System.

**Verify error bin:** Mail with incomplete or poor quality bar codes is
rejected by the OSS wide area bar code reader and placed in this bin.

**Virtual Memory System (VMS):** An interactive virtual memory operating
system used on each NDSS Alpha

**VMS:** *See* Virtual Memory System (VMS).

**Wide area bar code:** A bar code applied by customers that is placed
directly above or below the address block on a mail piece.

**Wide area bar code reader:** A bar code reader that can read wide area
bar codes.

**ZIPMOVE:** A utility for delivery point sequencing, sector/segment,
and incoming secondary sort programs that allows ZIP Code data to be
moved from an old geographical division to a new one.

**ZIPMOVE file:** A file that records details about a ZIPMOVE, showing
the old zone with a from and to +4 range, the new zone with a from and
to +4 range, and the date when the ZIPMOVE was initiated.

**ZIP +4 directories:** Directories from the National Directory Support
System that are used to view local directory information, update
incoming secondary sort programs, and apply new data to SONIKS zones.
These directories are generated from the weekly National Directory
Support System Refresh.

**ZIP +4 files:** Files that contain 9-digit address information for
single-pass incoming secondary sort programs in SPS.

**ZIP Code:** A 5-digit code that represents the city and state where a
mail piece will be delivered.

**ZIP not found bin:** A bin for mail pieces for which the Image
Processing Subsystem could not obtain a ZIP Code match when comparing
the address and city/state information with information from the
national directory.

**ZIP not resolved bin:** A bin that receives mail pieces for which the
OSS requests a ZIP Code and cannot obtain a result.

**ZIP partially resolved (ZIP part. resolved) bin:** When the OSS
requests a ZIP Code for a mail piece and only obtains a 5-digit result,
the mail piece goes into this bin.

**ZIP Search:** A diagnostic utility that searches all sort programs for
a specified ZIP Code and generates a report listing the sort program and
bin assignment for each occurrence.

**Zone:** 1. The last two digits of a 5-digit ZIP Code, which together
form a number that expresses the distance that a zone rate mail piece
must travel from point of entry to point of delivery. 2. Loosely, a
synonym for a ZIP Code.

**Zone Table:** A table where the user enters the sort program name and
up to 20 5-digit ZIP Codes in order to create the sort program.