The machine differentiation between same type machines is based on the communications connection (IP address) so I assume that I would have a set of descriptions for each machine, and the IP address is mapped to that description. So when they view a given machine (IP address), the machine info should be presented as part of the page. That will include the job being run at that time. Each IS machine makes bottles for two inspection lines, there are 3 types of inspection machines on each line. A Side Wall Inspector, Base and Finish (sealing surface) inspector and a Rotational Inspector steps the bottles through 5 stations 3 of which rotate the bottle to do various inspections. (this is my favourite machine). The data stream I sampled to the list is from a Rotational Inspector. But the data from all of the machines is in the same format, and the other machines in the plant generate data in about the same format also.
As to moving people from one view to another, I went through that when the utilities moved from paper to hardened laptops in their service vehicles, initially they all wanted the same thing, reproduce the paper on a screen (yea the paper was more or less copies of 3270 screens), but we showed them we could do so much more and it was not long before they were asking for the kitchen with the dishwasher tossed in. In many cases we started out just using some modified form of 3270 like screen to keep certain sectors happy, but then we started adding all of the neat stuff they have today, maps, all kinds of customer data. My first trip to the NW was to do a job with PGE. On that trip I never saw the light of day, got up and walked across the street from the hotel to the customer location, it was dark, when we went home it was dark. Oh and wet... It was in Feb. But later on I came out when we fielded the system and I got to see the Portland area in the day. I was the radio guy made sure the customer did not get sold two cans and a string. On Tue, Jun 24, 2014 at 8:32 AM, Rich Shepard <[email protected]> wrote: > On Tue, 24 Jun 2014, Chuck Hast wrote: > > > I want this to be the basis for all of the data capture from all of the > > different types of machines, since they all use a similar format to > output > > data, I should be able to with small modifications re-use most of it from > > machine to machine. Once I have that going then I will look at what I can > > put the binary stream to use for, or if it is faster to process, perhaps > > look at moving to it. > > Chuck, > > This is where table normalization and relational integrity come to your > aid. One table for 'machines' holds all attributes that distinguish one > machine from the other. It's separate from the tables for 'bottles' or > other > discrete types of information you want to capture, store, and analyze. > > > I will obtain some screen shots of the present form in which the data is > > presented, I will probably try to replicate those screens initially and > > then take request and recommendations, and try to add them in or do > > screens that add the high request items. > > You're going to use a different tool so the 'form' might very well look > different. It was often difficult to convince folks moving from paper to > digital that the data input form on the screen did not need to look just > like the pieces of paper they used. In fact, usually the paper format was > incompatible with database tables. > > > Does the list allow attachments or is it best just to put the images > > in a public dropbox directory and give the URL to it? > > No. Yes. Do the latter. > > Rich > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > -- Chuck Hast -- KP4DJT -- Glass, five thousand years of history and getting better. The only container material that the USDA gives blanket approval on. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
