Wow, anyone wants to touch on that topic? Let’s just say having ‘in the Cloud’ means that the IPSaaS (Infrastructure, Platform & Software) are all in the cloud for all the supply chain parties. Given that, how do we provide the visibility service in the cloud? In a service economy, knowledge is exchanged together (and applied) via a service to co-create value. If we take this line of service-dominant logic marketing thinking, then the service is accomplished by the existing of a visibility platform (VP) and the on-demand need of a supply chain party to gain a current snapshot of the supply chain. The knowledge of what to see is beneficial (the user) and the knowledge of how to gain that view (the technology) are being exchanged and visibility is created. Obviously, the user can access SaaS in the cloud to ‘express’ (as we have a drag-and-drop interface in the VP) the view needed, and the app that composes the accesible data and information in the RFID-IS and ERP-IS (please see previous posts) can exist also in the cloud. MapReduce may play a role in accessing the RFID-IS as it is likely to be a pool of distributed data sets (not necessary all database – or there could be NoSQL databases). I am not sure if ‘in the cloud’ requirement imposes any design issue on the visibility service? Will see once I know how to characterized the visibility service. For example, would ‘perishability’ be a characteristic? That is, a visibility service can be reused if the perishability can be tweeted. More later.