Machining Job Management System

We thought you might find it interesting to hear how we have approached some projects, from initial awareness of the problems to a completed system.

We’ll start with an engineering company, in Burton on Trent, who manufactures engine parts (mainly gears and shafts).

They had no Job Management System whatsoever. How they attempted to manage their shop was by having two whiteboards. One on the shop floor, one in the main office. On these whiteboards, they had a list of parts and quantities of how many were either in stock (completed) or on the final section. An employee would physically count each part and update both whiteboards.

One of the problems with this approach, is they had no idea when a particular part had a stock quantity of 10, for example. Just now, yesterday, last week? Unless they spoke with the person who’d updated the whiteboards, they had no idea!

We’d seen enough. We proposed a web based system, using sqlite as the database.

The screenshot below shows the Jobs page. As you can see, we have Job Number, Part, Order Date, along with the stages parts go through (from raw material to stock). Items that ended up being scrapped also needed tracking (last column).

In the Order QTY column we put in some visual indicators. The green tick shows that the job is complete. All items are either delivered, in stock, or scrap. The bin icon indicates that at least one part was scrapped. This shows on the delivery note for the customer to sign.

In the Part column, the photo icon shows whether we have a photo of the part, also for the delivery note.

The next screenshot show how a job is moved from location to location. The idea was, you start with a quantity in Material which then moves through the shop, eventually ending up with all parts being Delivered. Parts could be split, so as shown below, 6 items are on Grinding, 4 items have been Delivered. Once at least one part moves to Delivered a delivery note can be generated.

There is a lot more that could be written about this project, but that should give you an idea about our methodology. If you’d like a demo of the system, please contact us