7. Writing Field-developed Applications › 7.2 Deciding What the Application Must Do › 7.2.2 Reports Needed › 7.2.2.1 Exception Reports

7.2.2.1 Exception Reports

Exception reporting provides a diagnostic filter that enables
you to focus on specific problems or potential problem areas.
The exception reporting concept holds that, using trends from
past performance, you can predict when a potential problem
will occur.

CA MICS exception reporting is described in chapter 2 of the
CA MICS Standard Reports Guide.

In designing your field-developed application, identify
notable exceptions using these guidelines:

o  An exception is the occurrence of a processing anomaly,
   including missing an objective.

o  The exception must be able to be detected by the data
   source and the logic to detect the exception must be able
   to be expressed in SAS system code.

If your FDA is measuring the subsystem in throughput rates,
like units of things processed per minute or hour, objectives
are easy to set.  In the UNP example, the number of messages
processed per minute may be a good throughput measure on
which to base objectives.  An exception could be coded for
failing to meet a minimum throughput objective.