For example, a finite capacity scheduling application can be seen as a smart device that reads a plan from some other device (planning in the cloud perhaps, but for the sake of this argument we don't particularly care) and delivers a production schedule to whomever wants it. Of course, the plant needs it but so may certain sales tools used by consultants, who want to give customers up-to-date information on the expected delivery of their order. In the case of IIoT-based design, it is not the job of the scheduling software designer to decide who will gain access to each information and data set, but rather to define what information may come out and get into an application, and what operational behavior it implies. This is the public view of a smart connected asset (in this case, a piece of software).