In the first article we were looking for the real purpose of the document, whereas here, the author takes us on a quest for the deeper meaning of the objects that are going to be tracked by the system.
You will notice that this study uses the terms customer order, object on order, vehicle and truck. This is done on purpose: it doesn’t really matter what the tracking object is, the original customer order like the FO-order, or the real truck or bus by chassis number, or a spare frame, or CKD (Completely Knocked Down truck), or an extra order for equipment, or an engine…
Or a washing machine for that matter. The author clearly tries to tell us that this is a generic system, fitted for all, although probably at the time of writing was not aware of the word generic. I especially like the term object on order, although I don’t immediate link it to a truck-factory, which was probably the original purpose of using the term after all.
The goal of my PPOCOTS series is to write the ultimate blurb, one sentence, a synthesis of the entire 17 page document, with no loss of info, and of course, no redundant info either. So far I have: “A PPOCOST is a system to track objects on orders in a generic way”.
Next episode: something about processes.