Skip to end of metadata
Go to start of metadata

In many cases, program audits can span several work centers or even divisions.  In such cases, it might be desirable to create a flexible routing matrix that allows for last minute customization before the audit is sent on it's way.  This procedure can be complex and this article will attempt to clarify.


To enable this feature your Administrator will have to uncheck "Use vertical routing for program audits" in the Options dialog (checked by default).  See Administration for more details.

When AuditTrail detects an audit in any of the following program areas, it will trigger a flex route instead of a standard vertical route:

1000

1500

1600

2800

2900

3100

3300

3400

3900

4000

4600

4700

4900

5200

5300

5400

5700

5900

  1. Audit# (ACN) as assigned by AuditTrail
  2. Audit Date
  3. Audit Title as calculated by AuditTrail
  4. Coversheet header as created by Add Routing Matrix
  5. Routing Sequence Selector as created by Add Routing Matrix
  6. Specify the location of the audit (i.e. 600 division)
  7. Stop 1
  8. Stop 2
  9. Stop 3
  10. Flex Stop 1
  11. Stop n+1
  12. Stop n+2





Stops 1 through 3 are standard and don't change.  Typically, QA-LPO, QAS, QAO


Flex Stop 1 through n are where the user would put the customized part of the route.  For example, WCS 64e, WCS 610, WCS 620 etc.


Stops n+1 through n+x are the remaining stops that are standard for this program. For example, PROGMAN, PROGMON, QAFP, etc  *LAST stop must be Complete