OEE Development - Reading and writing between 2 Databases

Ignition
,
1

Hi Guys, I'm Developing an OEE system for a customer where i'll have ignition connected to PLC's in the plant for each line, as well as to a database (or import CSV/Excel) which is generated by software the company is currently using for creating their schedule.

I'm planning on taking this data (Customer, order no, product, units to be produced, which line its assigned to) and combining it with the data from the machines (running status, pulse on each cycle) and using it to create an OEE and a display on a machine schedule in Perspective that adapts to how the machine is running and how long it will take to finish the order, based on how it is currently performing

My question is what is the best way to implement storing this data to the main ignition database and performing the calculations required for the OEE and schedule. It'll be my first time doing proper database work with ignition so i'm looking to be pointed in the right direction.

In my head, I imagine having a table in my main database that will take in each order and what line it is assigned to from their existing system to keep order records, then move this onto the current process of the line when it is due and take in the machine details. Then once it is finished the order it will move it to a 'completed order' table with how the machine performed and update the OEE of the machine with time stamps. I'm just not entirely sure how to perform these interactions and calculations.

The customer will also want to be able to look through these records and see OEE/Orders of the past day, month year etc for each machine.

Any help is greatly appreciated!

Thanks.

2

If you are not already comfortable with how this is done, you probably should consider just buying Sepasoft's OEE package.

OEE is not rocket science, but getting all the moving parts in a solution to work properly together can be quite the engineering burden.

1 Like
3

Unfortunately spending the money on Sepasofts package isn't an option for us. I think if i could get a brief explanation i can manage the rest. would it be better to do the calculations and store on the database side or do it in ignition and store in tag history and pull the records from it?

4

I would store events and schedules in the database, and calculate live status in gateway memory, perhaps as expression tags.

That's the problem. It isn't a brief explanation.