Push Visibility (original post: June 28, 2011)

Push Visibility refers to supply chain visibility (SCV) that is ‘pushed’ to the user’s web browser. The supply chain in question is RFID-enabled. For this discussion, SCV is the visibility of business processes across the supply chain, and it is argued with that visibility, performance in general improves. Data made available by these processes are somehow available in some form for the construction of a visibility template on the fly. Visibility delivered as the user would like to ‘see’ (e.g., out-the-door data of all parties are now visible – pushed). Yet, in certain situation, the raw data should not be made available to protect privacy. Yet, the determination of how the raw data should be ‘shown’ depends on who the user is with respect to the privacy domain of the supply chain. Thus, the raw data must be ‘massaged’ before it is delivered to the user on the fly. The article ‘AjaxScore: A Platform for Remotely Monitoring the Client-Side Behavior of Web 2.0 Application’ by E. Kiciman & B. Livshits of Microsoft Research in ACM Transactions on The Web 4 (4), 2010, discusses on the fly instrumentation of code sent to a user for monitoring purposes would fit the bill on how, in one instance, that privacy can be protected without the omission of a piece of data (reducing the clarity of visibility). The raw data will be ‘morphed’/’changed’ to a certain characteristics to protect the privacy of the data owner and yet the resulting visibility is only ‘gracefully degraded’ (from fault tolerant computing!!). What do you think?

There are new concepts and terms that require further clarification. Would a visibility ontology do? or ‘killing a chicken with a big bad butcher chopper’? Disclaimer: Ok, the word ‘bad’ has no implication.

Leave a Reply