Page 170 - Training 2019

SOP FOR PROCESSING 06MAN CODES AND OTHER ONE-OFF CODES

This SOP applies to both Engineering and Branches

The idea for 06MAN codes was introduced into Engineering where there are many single time, one off jobs. To created
specific codes for each job is time consuming and serves no purpose where the job never gets repeated and Pastel just
becomes overloaded with redundant codes which has to stay in the system for a long time before they can be deleted
and if they are deleted so does the history for some of our stats.

So, to be able to reuse these 06MAN code as an alternative to just creating new codes all the time and keeping statistical
history works well as this still all falls under Engineering. However, if the job becomes a regular, it definitely has to get
its own code for traceability.

We then have to extend this to the branches so that they can also use the same 06MAN code system. However, they
will not require as many 06MAN codes as there will only be a smaller portion of Engineering jobs in each branch. So,
we need to implement a register in each branch which Admin will manage. Each branch has a list of 06MAN numbers
(which can be increased if the need arises, bear in mind that you want in and out in one month and then dormant in
the following month, before it is used again). The process will be as follows to update the 06MAN register:

1) Job arrives from Engineering at your branch with an invoice....(see proforma as an example).

2) Admin will then log in the ENG 06MAN code on the left of the register.
3) Then log details like internal order number, TSC name and customer.
4) Then log next sequential 06MAN code available at your branch on the right.

SOP-06MANCODES – 06MAN and Generic codes
Updated 24 June 2019 Initial___________