Linking job order number to histroized tag history

Ignition
,
1

Hello everyone,
I am struggling to find a way to filter tags history based on job order number, so the thing I want to do is basically we will have a job number for each production run and we are historizing line information on Change, the problem is I only find one record of the job order number where I cant do any kind of trends or graphs with this way. and how to link production tag history to a simple memory tag.

thanks

2

Correct me if i am not understanding your question correctly, you have a bunch of tags you want to associate with a job number, but when you query your history you only get the job number tag?

If that’s accurate there are a couple ways to go about it. You could do a little database manipulating to associate your job number tag with its fellow tags for the production run. And i cant believe i am saying this but it also may be a job for transaction groups.

3

Hi
I don’t get it

4

bare with me guys I hope I can explain the point better, there is a job number for a production run prior to start producing that patch, we define certain parameters to that job number like length of the product and and the temperature profile of the extruder machine. Now when the production starts all the production data should link to that specific job number(for now its a memory tag but later it will be polled from an api). later on I want to do some trends and tables filtered by job number. currently when I am historizing the job number memory tag it will only reflect one time on the database which prevent me to associate production data to that job number.

I hope I have explained it correctly

5

I really dont know if transaction group can do it, is it possible to create a table per job number ?

6

I think I got it. I’m not sure whether an identifier can be associated with a batch of historized data, but I may have an alternative solution depending on your answer to the following question:
Can several jobs run at the same time ? Can they overlap or blend ?

If the answer is no, you could create a new table containing start time and end time of each job/batch, and retrieve historized data based on those.

7

As hinted above, you need two or three queries. One or two to find the job number in history, and the next job number after it. With those results, you have the timestamps to supply to the rest of your history queries.