Tim Bass
09-07-2008 12:30 AM
The other day I was thinking that I should write about specific situation models and by coincident Marc Adler pens
CEP and Shoplifting.* In Marc’s post, Marc begins to model shoplifting as if shoplifting is “market data,” with Level 1 to Level 4 shoplifting “quotes” - the natural approach for a brilliant guy from Citi.***In reality, this model does not work very well, and I’ll touch on a few reasons why today.
Marc’s initial shoplifting*model in his post*is based on John Colapinto’s concepts of*matching a pattern of customer movements in the store with their estimated patterns of shoplifting behavioral patterns.*** Marc’s asks how Coral8 might address this.** We are not ready to seek a vendor solution.* We do not yet have a workable detection model.
As indicated above,*I don’t think the example situation cited by*John and Marc*is a viable model for automated processing.*** Tracking the behavior of customer’s movements, by machine, would require some very sophisticated image processing technology that would be too expensive compared to any possible loss at most retails stores.*** This type of behavioral pattern recognition. in retail stores,*is performed by people (security personnel), not machines, observing people.**
To develop a machine pattern recognition application to detect retail shoplifting we need to build detection models that*are economically feasible.* If we are going to use a model of shoplifting pattern recognition versus anomaly detection, we need to define the objects we must track.**
In the most simple model, we have merchandise-objects.** Stores normally (physically) track*merchandise-objects only at the exit/entry points of the store using some electromagnetic proximity detection technology.** In this model, the detection configuration is a combination of simple alerting with humans waching*the store (”minding the store”).*** This is not complex event processing.
However, if we added another object to our model, the customer-object, then we start to get more “complex,” but we have not defined “complexity” yet because we have not defined the object properties, the possible states of the objects, and the relationships between the objects that are the basis for estimated situations.
Hence, model building is constrained by available resources, simple economics and risk (cost-benefit).* If we are detecting shoplifting in Walmart the cost-benefit model for implementing an automated shoplifting detection system would be different than at a top diamond store on 5th Avenue in NYC.** Protecting loss at a weapons-grade uranium respository follows a different model than protecting loss at a handicraft shop, naturally.
Like Marc, I find models to automatically detect shoplifting interesting, so permit me to close with a general discussion of shoplifting in the context of my reference model.
One approach would be do*determine what objects will be represented*in our model.** For example,*if we are going to track merchandise, we need to model the*”merchandise-object”.* If we are*going to track people, we need to define the properties of this “person object.”* If we are going to*represent the store layout, we need to define all these objects (store-object, table-object, shelf-object,*entry-object and so forth).**The model can*get “complex” quite quickly.*
Editorial Note:* An object-oriented approach greatly assists complex model building because*we*can benefit from OO properties such as encapsulation and polymorphism.* For example, we can define a basic “person object class” and then create superclasses of this object for “customer-object”, “manager-object”, “or criminal-object.”
Generally speaking, each object we define will require*a state-model, for example, in Marc’s example of a customer moving around the store, we*would need to model the possible states (customer at the entrance, at*table 1, at table 2, at shelf 1, in the bathroom, at the cashier, etc.)* Indeed Marc, this is complex event processing if we have modelled multiple objects and defined object-object relationships that indicate*situations of*interest.** For example, customer-object at table2 where merchandise-object*has the property of *”very expensive, high risk” and then customer-object changes state to “in bathroom”.* Of course, we need more key indicators, but you get the idea.
Right now, I am typing from the
Taste from Heaven Vegetarian Restaurant in Chiang Mai and my battery is running low.* The owner of this excellent restaurant also runs the
Elephant Nature Park, a non-profit organization advocating and acting on behalf of the rights of the mighty elephants in Thailand.* Would be great if we could also automatically detect the situation of “elephant abuse” by poachers and other crimes against nature.** Time to get back to my delicious mushroom salad, Northeastern Thai style.
As always, thanks for reading, time for me to get back to eating!
*
Source...
