Episode 04: How TriSystems Uses IEC 61499 and UniversalAutomation.org to Upgrade Offshore Platforms | UAO Goes Live: The Future of Automation

Description

In this episode of UAO Goes Live, discover how TriSystems Engineering leverages IEC 61499 and UniversalAutomation.org to modernize offshore oil and gas platforms in Southeast Asia. Learn how open automation enables hardware independence, portability, and interoperability, helping overcome obsolescence challenges and extend system lifespan. This real-world use case demonstrates how plug-and-produce architectures, low-power edge computing, and OPC UA connectivity deliver flexibility and resilience for remote operations.

About UniversalAutomation.org (UAO)

UniversalAutomation.org (UAO) is an independent non-profit organization dedicated to transforming industrial automation through open standards and shared source technology. The association manages the reference implementation of a shared runtime execution engine based on the IEC 61499 standard, enabling true interoperability between hardware from multiple vendors and portability of automation software applications.

By providing a ready-to-use, vendor-neutral runtime environment, UniversalAutomation.org empowers companies to build flexible Industry 4.0 architectures, accelerate digital transformation, and maximize return on investment (ROI) through software reusability and hardware independence.

The development of this runtime is governed by shared source principles, ensuring long-term compatibility and collaborative innovation. Members—including end users, OEMs, system integrators, and technology vendors—work collectively to create a global ecosystem for plug-and-produce automation solutions.

UniversalAutomation.org is growing rapidly as more organizations adopt open automation to overcome vendor lock-in, enable IT/OT convergence, and support greenfield and brownfield projects. Academic institutions are also leveraging this technology to train the next generation of automation engineers.

Companies and institutions that want to lead the future of industrial automation, develop next-generation control systems, and participate in a global open automation community are invited to join UniversalAutomation.org.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Transcription

Speaker #0
Universalautomation.org, it's about sharing a technology, a shared runtime execution engine.
Speaker #1
We believe the game change in automation because we have first one technology which is based on the IEC 64999, which is the standard which aims at decoupling hardware and software.
Speaker #0
Hardware itself is becoming very, very performant in terms of processing CPU power,
Speaker #2
and the future is more and more about software. This approach is really a winning approach. Because it's very very flexible, you develop the application once and you can reuse in each different configuration.
Speaker #3
That's exactly what Universal Automation and 61499 enables, because it brings a new formalism for developing software, which is object-oriented in nature and which allows deployment of a distributed hardware for the actual final control system. So let's say that it's a marriage made in heaven.
Speaker #4
So if I want to make more conscious decisions based on my business data, which also comes from the automation level, I need universal automation to get this data in an efficient way and with the right engineering efforts on the level when I can do and run the analytics.
Speaker #0
Offers are available not just from Schneider Electric with EcoStruxure Automation Expert, but also from Advantech, from Stahl, from ESA in Italy and from other companies.
Speaker #5
Advantech is growing really, really fast. And I believe if you want to keep on growing in the next future, you need to be able to innovate. When I see Universal Automation approach, it is exactly the way of innovation we need to go with.
Speaker #6
Most of our customers from Process Automation are pretty conservative, so never change a running system. But now we see a new generation coming up, what is used to new technologies. And they are open to test, to try these new functionalities. And I think most of them pretty well understand the advantages on this. I'm doing this now for 20 years, and I think over the years, this is the most exciting changes.
Speaker #2
And from my experience, I see that in the IT, for example, there has been a big revolution. And I expect the same in automation. I don't know when it will happen, probably takes a little bit of time, but probably a revolution will come.
Speaker #1
Hi everybody, good morning, good day to all of you. wherever you're based. My name is Greg Boucault and I'm the Chief Marketing Officer for universalautomation.org. Today I have the pleasure to welcome you in this new session of the UAO goes live. We have been through the introduction of the association what are this goal its goal and its mission so feel free to watch again our videos which are can be found on either our linkedin page or our youtube channel today i have the pleasure to welcome megatz general manager from the company Tri System and Megal will go with us through a use case that they have done, that Tri System has done using the technology. So please give a warm welcome to Megat. Hi Megat.
Speaker #7
Hi.
Speaker #1
So let's jump onto your introduction to give you plenty of time to introduce us to your company and your use case.
Speaker #7
Sure. Thank you, Greg. My name is Magad Shamsul. I'm the General Manager for TriSystem Engineering. So TriSystem is a system integrator. We've been doing system integration since 1994. We have been deploying 1131 systems since then. So we are the leading provider of products and engineering solutions specifically for oil and gas and petrochemical industry. But we have been expanding our market, not only oil and gas and petrochemical, we are looking at power and general industry as well. We offer state-of-the-art solutions to our customers, safety systems. process control system, software solutions, packages, process packages, fire protection, filtration, combustion, pneumatic hydraulics. We have about 160 people in the company. 85% is engineer. Myself is also an engineer. I'm a mechanical engineer but I've been doing this automation for more than 20 years. We have been doing deploy projects I think in our customer references, probably hundreds. But we don't stop on delivery. We offer the after sales as well. So like maintenance and on and upgrade. So we have maintenance contract. We have price agreement with our customers. So with the track record of a successful project, in fact, they don't remember the, our customer don't remember the product that we deliver. They remember our name as the system integrator that that deploy the system. So we are very committed on delivering projects and support and service the customer. We are based in Malaysia but we want to expand or we are currently expanding our reach out to Southeast Asia. So if you look at the map, we have here Malaysia and then we have Indonesia, Thailand, Vietnam, Myanmar and Philippines. So this is me. I'm the general manager for sales and marketing. So this is our key board of directors and key management. Yeah, let me go straight to the cases, the use cases. So, we have deployed this system, PAK8000, back in 2012. So, it's been more than 10 years operationally. Unfortunately, this PAK8000 has obsolescence issues. So we are being asked by our customers, how we want to solve this officer search issue. And because of that, because we have a contract, so we are providing them with, from the last 10 years, our support. And we send our engineers to do maintenance and so on. So we make sure the system is operational and well maintained. And any issue they can just call us, we'll send our engineers and make sure that the system uptime is there. But with this current issue with this PAD 8000, so we are proposed to upgrade this to another platform. So we have looking at solutions that can solve this issue. So we were looking at that. IC61499. And here we found we can answer these key questions that being asked to us by our customer. So the thing is that we don't want to change the cabinet. This is offshore platform, it is located remotely, it is not easy for us to access these facilities. You need to take a boat. to go there so we don't want to do a major job so you just change the component inside the existing cabinet recertify them because it's a hazardous area so we need to recertify the control cabinet to a zone two a zone two means that it is for suitable for hazardous area and then we we need to also maintain the similar power requirement The system that we are providing the last 10 years only consumed 300 watts. Actually, it's less than 300 watts, but 300 watts is what they gave us. The actual system running is about 160 watts. This system is running purely using solar power and a battery system. 61499 we can offer a longer lifespan to tackle the opposition issue and improve the total cost of ownership. So we are not obliged or we're not fixed to one hardware provider. We can play with any hardware that complies to IEC 61499. So the same functionality that the current system running on 1131. will be running with the same function on IEC 61499. And the pilot project that we are proposing to our customer is for the smallest platform. So the platform has seven offshore platforms. So I just show you the picture. So this is the cluster of the offshore platforms. All these seven platform clusters have our system and we are proposing to upgrade only this as a small platform called this G. And what we are proposing now is we're going to remove the PACK8000 hardware and put in right now we are choosing the Modicon M580D PACK redundant CPU. We're going to remove the I.O. and we're going to put the back-off I.O. modules integrated with I.S. So if you see here, we don't have I.S. barrier. The I.O. is integrated with I.S. And here we had this Kingfisher RTU unit and we're going to upgrade it with the Aviva EDS running on the Moxa Edge computer. So the whole system here is running at about 160 watts low power, but it will manage to help us in the offshore process, which is quite simple. It is a well-heeled platform. The well-heeled platform task is to bring out oil from the platform. but the system is basically what it does is it helps in what we call it the enhanced oil recovery so the system will help us in terms of how much gas or how much gas we need to inject in the well to bring up more oil so it's connected to a smart system whereby this smart system knows how much gas you need to inject in the oil field and to bring up oil, more oil out from the ground. So actually when we put the system back in 2012, by 2013 and 2014 it already pay back, they already got their money back. and it already served since then and now they feel that the life of the platform can be more extended because they see there's more oil that they can extract from this field. Hence, the importance of the system to be robust so we can take to make sure that the system is, we'll call it, don't have this obsolescent issue and so on so we can maintain the system probably another 10 years so this is the architecture from the picture you just showed just now this is the architecture that we propose to our customer so we see here we have this back off i o to take the pressure transmitter temperature transmitters, flow transmitters, and it goes to a switch, a managed switch. And then we have put two controllers, the D-PAC and 580. This is an engineered redundancy that we provide to this customer. And here we have our small edge computer that consumes about 4.5W running on Linux. this would be our, we call it the... edge data store or data buffering in case of the radio is they have problem and this platform running on the digital dmr digital model radio currently we have probably 100 mbps when we did back in 2012 we only had two mbps of internet or communication bandwidth, but they already upgraded it. So we get more bandwidth and with this more bandwidth, we can send good data, good high fidelity data. Before this, it was, I think the data fidelity is not that fine. But with the more bandwidth, with the more computing power that we have, we can do that. But the problem is radio link, if it rains, it will have issues with communication. So that's why we have a local hardware here to do the data buffering. But if you see here, this yellow line is all the control network is on OPC UA. The communication with the IO is on Modbus. TCP and the I.O. is on the ring network in case of failures. But we provide a ring network to enhance the reliability of the I.O. So the system here, so the cabinet, the system is here and this is the devices connected to the system it has hard wire as well as Modbus serial and Modbus internet TCP IP communication. We also connected to the charge controller. The charge controller is for the offshore solar system. And then from here, it goes to a radio link. The control network goes to radio link to the control DMR, which goes to the mother platform. and then we have converted it to the fiber optic and the fiber optic here will go to the control room, the CCR, is where in the, what they call it, the LQ, the living quarters. And this control network will be connected to our new EWS, which we're going to put together with the IC61499. compliance software, EcoStruxure Automation Expert. From this seven platform, we only upgrade one. So probably the plan is maybe three years or four years or five years to upgrade all these seven platform. But it will have currently this platform is running on the old protocol, the DNP3 protocol. So now we have a mix of OPC UA and DNP3 protocol, which is fine. We have tested it. It works. And for the start, only one platform will have 61499 with OPC UA. And we need to also add the connectivity to the Pi system, the Pi or IVVAR Pi system at this platform. Currently, it's using the MP3 Pi interface. Now we need to add the OPC UA connector to this Pi server so that we can get the data. But also, we do control. as well. So we send the set point from this PI server back to the platform and the platform control system will open the valve for the gas injection. The system is actually how to get the set point. The system is actually communicating with somebody or what they call it the engineer in the customers HQ. So the customer HQ would have an application software that they can intelligently look at the data that our system brings in and they can intelligently tell how much gas they want to inject in which particular well to get more oil. so in short um previously probably um the engineer need to go to the off offshore and do this calculation in in offshore so now he can sit in the office comfortably and do the simulations and then they can just put in the numbers and this number will come back to the offshore via this network and the control system will be able to adjust how much gas that they need to be injected in each particular well on this control system that we provided. So that's a bit of the local storage that we put. It's running as a lightweight storage system. It's Aviva Edge Datastore running. So we are going to use OBC UA and it will be connected to the PI server. And this is very lightweight. It only consumes, I will be putting in the hardware on Linux. So here we're going to put in the Moxa hardware running on Linux, I think, 11. And then with an ARM processor. So, in short, this is our use case. I'll be happy to take any questions from the floor.
Speaker #1
One question for myself is that I see that the whole system that you have is very distributed and how do you see that the technology, especially the 649 has helped you towards this this modeling of your application?
Speaker #7
Yeah, so 649, so the IEC standard would help us in case of, let's see, so the problem statement here, sorry, let me get back to this. The problem statement here is that we need to support the lifespan of the system to tackle the citizens issue, right? Right. So IC6149. is I think the answer because it doesn't have to be specified to what hardware that we use and probably this is something that we will ask in case if let's say we don't get this Deepak M580 anymore can I put another hardware from Stahl or Phoenix Contact yeah it can be because if we can have the hardware right now doesn't matter i as long as it's certified to it61499 yeah so oh if if if and and you and you see here we have many platforms here and as long as all the um hardware is certified and it doesn't matter i can get it can be like this platform can can be using um hardware from vendor a uh this hardware vendor b and venice so doesn't matter it it it will work it definitely will work um and the application doesn't change so i guess this is something that the customer wants the customer wants um that the system um is robust and they don't have to spend more money when, let's say, some hardware obsolete.
Speaker #1
Yes. So really this hardware and software independence to help in terms of, let's say, resilience maybe of supplying of products on one side and the other side to kind of push away the risk of end of life as we know it today. Yes. That's very good and that's what we are as Universal Automation.org pushing as values for the technology that we are supplying. So it's great to see that the customer as well, the one using the technology is also seeing that. I am switching to another question which is coming from LinkedIn, from Mudassir. Are there any bottlenecks or shortcomings?
Speaker #7
of the 649 where can be improved so do you have any um any feedback on that so yeah one thing that that um when when I presented this to Schneider um this hardware here is is not a product redundancy means that this deepak in 580 is just a single unit but because of this platform it's it's critical to have a redundant unit because it's far it's not easy to go and it's it's uh and we need to put a redundant system yes so we have uh one thing that with six one four nine nine i'm sure in the future uh there were come up with this redundancy but currently we are doing an engineered redundancy basically from from our engineering and we already tested it and we already demo to our customer it works um if let's say this one controller fail the other controller will take over but it requires some unique um integration that that we do so that's one shortcoming that that we face um during this uh just this case and and also um the io redundancy as well so there's kind of an engineered redundancy that we do um internally to to ensure that um if let's say uh an io card fail um we need to get another io to take over so um yes that's that's uh the the problem, the issue that I have when I did this. So I think I'm sure there is, in the future, there is a solution to this.
Speaker #1
Yes, yes. I mean, the technology in itself is always being improved and new features are added to the technology. That's the goal of the of the association in itself to gather those let's say feature requests and put them into the technology so that they can grow as well step by step with the needs of the different users. One thing which maybe happened in between your use case and now is that the newest version of the technology now embarks high availability. which could have been a great help for you in your cases but yeah i said it's evolving and it's all let's say features which are coming uh with the time and with the requests uh from the from the different users sure
Speaker #7
um yeah yeah just to add um i mean there is um schneider had offered me the redundancy on the ipc um the computer but the issue is that um my my problem with this is the power um i i only have 300 watts to play with um so we we need to have um maybe in the future the hardware that that um have um low power like this um like this total system we calculated is about 160 watts
Speaker #1
and it works it will work and you will serve the purpose and and I think that could be in fact a great way to make an appeal to technology vendors in fact because if we have more technology vendors which have such a product on which we could deploy the technology with with for example the higher availability so we can use it this could be a great functionality for you or a great opportunity what do you think
Speaker #0
Yes, definitely. If the technology or the OEM, the vendor that can look at each use case, I'm sure. If let's say it is for a gas pipeline or a remote application, even for oil and gas where we have a diverse similar like this, where we are depending on telecommunication to link the controller together and and we are doing an application whereby we we need the telecom we need the controller we need the the io all that can be packaged i'm sure there's a lot of application in the world that have a similar requirement like this.
Speaker #1
Yeah and that's a perfect point because I mean when we speak about vendors we do not speak only about traditional let's say PLC vendors but we also include that's why we use the board more technology vendors because we see IPCs, we see RTUs, we see managed switches, we see in fact a lot of products which are embedding a CPU on which the runtime could be ported onto. So that's a wide variety of product and of possibilities to embark the technology.
Speaker #0
Sure. Like for example, this IPC only consumes 4.5 watts and it does the work for data buffering.
Speaker #1
Yeah. So if we have some Moxa people that's... That's a great appeal to them to join the association so we could we could put the runtime onto their platform. Good. I see we have another question coming from from LinkedIn. Let me put it here from Colanda. Are you expecting the same application developed for this platform to be reused for the remaining platforms as well in the future?
Speaker #0
Yes, because the application is similar. It's for, as mentioned, is for the, they call it the EOR application. Not much change. The only thing that is fixed is the wellhead and the sensors. It's the same sensors. The application probably, if we do one, it will be similar to other location as well. And we can deploy it without going to the offshore platform. Let's see if I see the architecture here.
Speaker #1
So,
Speaker #0
yeah, I see the architecture here. You have this engineering station here and we can deploy to all the other six platforms without having to go there. I mean, we can do the engineering and we can deploy it via the telecommunication link. and it's done, it's possible.
Speaker #1
So we see here even an application with using wireless telecommunication in between. Yeah. So yeah, that's very impressive. Good. I see no other questions for now. So maybe one last question to you, Megat. What would you say to... Because we have seen for this application, okay, you have used... Schneider Electric for the co-editancy that you did it yourself and so on. But in general what would you say to all the technology vendors out there which are looking for their next generation of product and maybe of automation as well? Do you have something that you want to to tell them regarding your situation?
Speaker #0
So basically we are system integrator. We build systems to customers. Our customer is the end user that uses it for an application. As a system integrator, we look for the best solution and sometimes there are some specific requirements coming from customers that we need to think and we need to look at the technology. what technology that available in the market. So and As a system integrator, we are responsible. The sole responsibility of deploying the system to the customer is us. This is the beauty with IC61499. Because the IC61499 is very centric to system integrator, which we like. And what we want to tell to the provider of the technology is that sometimes talk to us. we probably have some ideas for the technology vendors to develop the hardware and probably the software um to for us to deploy more um iec 61499 systems yes
Speaker #1
thank you for your last uh last command megatz uh we reached the the end of this uh of this session of uo goes live So just to give to all our viewers just an outlook, we will have the next next uEgoz live coming quite soon so please stay tuned and have a look on our LinkedIn and YouTube channel to check when it will be. So here are the details if you want to get in touch with with Megat from TriceSystem if you are having any project in Southeast Asia. that you want to look for a system integrator to support you in implementing the technology, please use our member, use Megat and TriSystems and they will be happy to welcome you. Any last words, Megat?
Speaker #0
Yeah, I would like to thank you for having this session. I appreciate the time given to me to do this. presentation. I'm happy we have done this.
Speaker #1
Yeah, thank you. Thank you, Megat. Thank you for your support. And thank you to all the viewers who could make it or maybe will watch it afterwards. And please stay tuned for the next session of YoYo Girls Live. Thank you and bye, everyone.

About UAO Goes Live: The Future of Automation

UAO Goes Live brings the conversations from our popular LinkedIn Live series directly to your favorite podcast platform. Each episode explores the world of open, interoperable automation powered by IEC 61499. Join industry leaders, innovators, and experts as they share real-world applications, success stories, and insights that are shaping the future of industrial automation.

Whether you are an engineer, a technology leader, or simply passionate about the next wave of automation, this podcast is your go-to source for cutting-edge discussions, practical knowledge, and thought leadership.

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

About UAO Goes Live: The Future of Automation

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Description

About UniversalAutomation.org (UAO)

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Transcription

Speaker #0
Universalautomation.org, it's about sharing a technology, a shared runtime execution engine.
Speaker #1
We believe the game change in automation because we have first one technology which is based on the IEC 64999, which is the standard which aims at decoupling hardware and software.
Speaker #0
Hardware itself is becoming very, very performant in terms of processing CPU power,
Speaker #2
and the future is more and more about software. This approach is really a winning approach. Because it's very very flexible, you develop the application once and you can reuse in each different configuration.
Speaker #3
That's exactly what Universal Automation and 61499 enables, because it brings a new formalism for developing software, which is object-oriented in nature and which allows deployment of a distributed hardware for the actual final control system. So let's say that it's a marriage made in heaven.
Speaker #4
So if I want to make more conscious decisions based on my business data, which also comes from the automation level, I need universal automation to get this data in an efficient way and with the right engineering efforts on the level when I can do and run the analytics.
Speaker #0
Offers are available not just from Schneider Electric with EcoStruxure Automation Expert, but also from Advantech, from Stahl, from ESA in Italy and from other companies.
Speaker #5
Advantech is growing really, really fast. And I believe if you want to keep on growing in the next future, you need to be able to innovate. When I see Universal Automation approach, it is exactly the way of innovation we need to go with.
Speaker #6
Most of our customers from Process Automation are pretty conservative, so never change a running system. But now we see a new generation coming up, what is used to new technologies. And they are open to test, to try these new functionalities. And I think most of them pretty well understand the advantages on this. I'm doing this now for 20 years, and I think over the years, this is the most exciting changes.
Speaker #2
And from my experience, I see that in the IT, for example, there has been a big revolution. And I expect the same in automation. I don't know when it will happen, probably takes a little bit of time, but probably a revolution will come.
Speaker #1
Hi everybody, good morning, good day to all of you. wherever you're based. My name is Greg Boucault and I'm the Chief Marketing Officer for universalautomation.org. Today I have the pleasure to welcome you in this new session of the UAO goes live. We have been through the introduction of the association what are this goal its goal and its mission so feel free to watch again our videos which are can be found on either our linkedin page or our youtube channel today i have the pleasure to welcome megatz general manager from the company Tri System and Megal will go with us through a use case that they have done, that Tri System has done using the technology. So please give a warm welcome to Megat. Hi Megat.
Speaker #7
Hi.
Speaker #1
So let's jump onto your introduction to give you plenty of time to introduce us to your company and your use case.
Speaker #7
Sure. Thank you, Greg. My name is Magad Shamsul. I'm the General Manager for TriSystem Engineering. So TriSystem is a system integrator. We've been doing system integration since 1994. We have been deploying 1131 systems since then. So we are the leading provider of products and engineering solutions specifically for oil and gas and petrochemical industry. But we have been expanding our market, not only oil and gas and petrochemical, we are looking at power and general industry as well. We offer state-of-the-art solutions to our customers, safety systems. process control system, software solutions, packages, process packages, fire protection, filtration, combustion, pneumatic hydraulics. We have about 160 people in the company. 85% is engineer. Myself is also an engineer. I'm a mechanical engineer but I've been doing this automation for more than 20 years. We have been doing deploy projects I think in our customer references, probably hundreds. But we don't stop on delivery. We offer the after sales as well. So like maintenance and on and upgrade. So we have maintenance contract. We have price agreement with our customers. So with the track record of a successful project, in fact, they don't remember the, our customer don't remember the product that we deliver. They remember our name as the system integrator that that deploy the system. So we are very committed on delivering projects and support and service the customer. We are based in Malaysia but we want to expand or we are currently expanding our reach out to Southeast Asia. So if you look at the map, we have here Malaysia and then we have Indonesia, Thailand, Vietnam, Myanmar and Philippines. So this is me. I'm the general manager for sales and marketing. So this is our key board of directors and key management. Yeah, let me go straight to the cases, the use cases. So, we have deployed this system, PAK8000, back in 2012. So, it's been more than 10 years operationally. Unfortunately, this PAK8000 has obsolescence issues. So we are being asked by our customers, how we want to solve this officer search issue. And because of that, because we have a contract, so we are providing them with, from the last 10 years, our support. And we send our engineers to do maintenance and so on. So we make sure the system is operational and well maintained. And any issue they can just call us, we'll send our engineers and make sure that the system uptime is there. But with this current issue with this PAD 8000, so we are proposed to upgrade this to another platform. So we have looking at solutions that can solve this issue. So we were looking at that. IC61499. And here we found we can answer these key questions that being asked to us by our customer. So the thing is that we don't want to change the cabinet. This is offshore platform, it is located remotely, it is not easy for us to access these facilities. You need to take a boat. to go there so we don't want to do a major job so you just change the component inside the existing cabinet recertify them because it's a hazardous area so we need to recertify the control cabinet to a zone two a zone two means that it is for suitable for hazardous area and then we we need to also maintain the similar power requirement The system that we are providing the last 10 years only consumed 300 watts. Actually, it's less than 300 watts, but 300 watts is what they gave us. The actual system running is about 160 watts. This system is running purely using solar power and a battery system. 61499 we can offer a longer lifespan to tackle the opposition issue and improve the total cost of ownership. So we are not obliged or we're not fixed to one hardware provider. We can play with any hardware that complies to IEC 61499. So the same functionality that the current system running on 1131. will be running with the same function on IEC 61499. And the pilot project that we are proposing to our customer is for the smallest platform. So the platform has seven offshore platforms. So I just show you the picture. So this is the cluster of the offshore platforms. All these seven platform clusters have our system and we are proposing to upgrade only this as a small platform called this G. And what we are proposing now is we're going to remove the PACK8000 hardware and put in right now we are choosing the Modicon M580D PACK redundant CPU. We're going to remove the I.O. and we're going to put the back-off I.O. modules integrated with I.S. So if you see here, we don't have I.S. barrier. The I.O. is integrated with I.S. And here we had this Kingfisher RTU unit and we're going to upgrade it with the Aviva EDS running on the Moxa Edge computer. So the whole system here is running at about 160 watts low power, but it will manage to help us in the offshore process, which is quite simple. It is a well-heeled platform. The well-heeled platform task is to bring out oil from the platform. but the system is basically what it does is it helps in what we call it the enhanced oil recovery so the system will help us in terms of how much gas or how much gas we need to inject in the well to bring up more oil so it's connected to a smart system whereby this smart system knows how much gas you need to inject in the oil field and to bring up oil, more oil out from the ground. So actually when we put the system back in 2012, by 2013 and 2014 it already pay back, they already got their money back. and it already served since then and now they feel that the life of the platform can be more extended because they see there's more oil that they can extract from this field. Hence, the importance of the system to be robust so we can take to make sure that the system is, we'll call it, don't have this obsolescent issue and so on so we can maintain the system probably another 10 years so this is the architecture from the picture you just showed just now this is the architecture that we propose to our customer so we see here we have this back off i o to take the pressure transmitter temperature transmitters, flow transmitters, and it goes to a switch, a managed switch. And then we have put two controllers, the D-PAC and 580. This is an engineered redundancy that we provide to this customer. And here we have our small edge computer that consumes about 4.5W running on Linux. this would be our, we call it the... edge data store or data buffering in case of the radio is they have problem and this platform running on the digital dmr digital model radio currently we have probably 100 mbps when we did back in 2012 we only had two mbps of internet or communication bandwidth, but they already upgraded it. So we get more bandwidth and with this more bandwidth, we can send good data, good high fidelity data. Before this, it was, I think the data fidelity is not that fine. But with the more bandwidth, with the more computing power that we have, we can do that. But the problem is radio link, if it rains, it will have issues with communication. So that's why we have a local hardware here to do the data buffering. But if you see here, this yellow line is all the control network is on OPC UA. The communication with the IO is on Modbus. TCP and the I.O. is on the ring network in case of failures. But we provide a ring network to enhance the reliability of the I.O. So the system here, so the cabinet, the system is here and this is the devices connected to the system it has hard wire as well as Modbus serial and Modbus internet TCP IP communication. We also connected to the charge controller. The charge controller is for the offshore solar system. And then from here, it goes to a radio link. The control network goes to radio link to the control DMR, which goes to the mother platform. and then we have converted it to the fiber optic and the fiber optic here will go to the control room, the CCR, is where in the, what they call it, the LQ, the living quarters. And this control network will be connected to our new EWS, which we're going to put together with the IC61499. compliance software, EcoStruxure Automation Expert. From this seven platform, we only upgrade one. So probably the plan is maybe three years or four years or five years to upgrade all these seven platform. But it will have currently this platform is running on the old protocol, the DNP3 protocol. So now we have a mix of OPC UA and DNP3 protocol, which is fine. We have tested it. It works. And for the start, only one platform will have 61499 with OPC UA. And we need to also add the connectivity to the Pi system, the Pi or IVVAR Pi system at this platform. Currently, it's using the MP3 Pi interface. Now we need to add the OPC UA connector to this Pi server so that we can get the data. But also, we do control. as well. So we send the set point from this PI server back to the platform and the platform control system will open the valve for the gas injection. The system is actually how to get the set point. The system is actually communicating with somebody or what they call it the engineer in the customers HQ. So the customer HQ would have an application software that they can intelligently look at the data that our system brings in and they can intelligently tell how much gas they want to inject in which particular well to get more oil. so in short um previously probably um the engineer need to go to the off offshore and do this calculation in in offshore so now he can sit in the office comfortably and do the simulations and then they can just put in the numbers and this number will come back to the offshore via this network and the control system will be able to adjust how much gas that they need to be injected in each particular well on this control system that we provided. So that's a bit of the local storage that we put. It's running as a lightweight storage system. It's Aviva Edge Datastore running. So we are going to use OBC UA and it will be connected to the PI server. And this is very lightweight. It only consumes, I will be putting in the hardware on Linux. So here we're going to put in the Moxa hardware running on Linux, I think, 11. And then with an ARM processor. So, in short, this is our use case. I'll be happy to take any questions from the floor.
Speaker #1
One question for myself is that I see that the whole system that you have is very distributed and how do you see that the technology, especially the 649 has helped you towards this this modeling of your application?
Speaker #7
Yeah, so 649, so the IEC standard would help us in case of, let's see, so the problem statement here, sorry, let me get back to this. The problem statement here is that we need to support the lifespan of the system to tackle the citizens issue, right? Right. So IC6149. is I think the answer because it doesn't have to be specified to what hardware that we use and probably this is something that we will ask in case if let's say we don't get this Deepak M580 anymore can I put another hardware from Stahl or Phoenix Contact yeah it can be because if we can have the hardware right now doesn't matter i as long as it's certified to it61499 yeah so oh if if if and and you and you see here we have many platforms here and as long as all the um hardware is certified and it doesn't matter i can get it can be like this platform can can be using um hardware from vendor a uh this hardware vendor b and venice so doesn't matter it it it will work it definitely will work um and the application doesn't change so i guess this is something that the customer wants the customer wants um that the system um is robust and they don't have to spend more money when, let's say, some hardware obsolete.
Speaker #1
Yes. So really this hardware and software independence to help in terms of, let's say, resilience maybe of supplying of products on one side and the other side to kind of push away the risk of end of life as we know it today. Yes. That's very good and that's what we are as Universal Automation.org pushing as values for the technology that we are supplying. So it's great to see that the customer as well, the one using the technology is also seeing that. I am switching to another question which is coming from LinkedIn, from Mudassir. Are there any bottlenecks or shortcomings?
Speaker #7
of the 649 where can be improved so do you have any um any feedback on that so yeah one thing that that um when when I presented this to Schneider um this hardware here is is not a product redundancy means that this deepak in 580 is just a single unit but because of this platform it's it's critical to have a redundant unit because it's far it's not easy to go and it's it's uh and we need to put a redundant system yes so we have uh one thing that with six one four nine nine i'm sure in the future uh there were come up with this redundancy but currently we are doing an engineered redundancy basically from from our engineering and we already tested it and we already demo to our customer it works um if let's say this one controller fail the other controller will take over but it requires some unique um integration that that we do so that's one shortcoming that that we face um during this uh just this case and and also um the io redundancy as well so there's kind of an engineered redundancy that we do um internally to to ensure that um if let's say uh an io card fail um we need to get another io to take over so um yes that's that's uh the the problem, the issue that I have when I did this. So I think I'm sure there is, in the future, there is a solution to this.
Speaker #1
Yes, yes. I mean, the technology in itself is always being improved and new features are added to the technology. That's the goal of the of the association in itself to gather those let's say feature requests and put them into the technology so that they can grow as well step by step with the needs of the different users. One thing which maybe happened in between your use case and now is that the newest version of the technology now embarks high availability. which could have been a great help for you in your cases but yeah i said it's evolving and it's all let's say features which are coming uh with the time and with the requests uh from the from the different users sure
Speaker #7
um yeah yeah just to add um i mean there is um schneider had offered me the redundancy on the ipc um the computer but the issue is that um my my problem with this is the power um i i only have 300 watts to play with um so we we need to have um maybe in the future the hardware that that um have um low power like this um like this total system we calculated is about 160 watts
Speaker #1
and it works it will work and you will serve the purpose and and I think that could be in fact a great way to make an appeal to technology vendors in fact because if we have more technology vendors which have such a product on which we could deploy the technology with with for example the higher availability so we can use it this could be a great functionality for you or a great opportunity what do you think
Speaker #0
Yes, definitely. If the technology or the OEM, the vendor that can look at each use case, I'm sure. If let's say it is for a gas pipeline or a remote application, even for oil and gas where we have a diverse similar like this, where we are depending on telecommunication to link the controller together and and we are doing an application whereby we we need the telecom we need the controller we need the the io all that can be packaged i'm sure there's a lot of application in the world that have a similar requirement like this.
Speaker #1
Yeah and that's a perfect point because I mean when we speak about vendors we do not speak only about traditional let's say PLC vendors but we also include that's why we use the board more technology vendors because we see IPCs, we see RTUs, we see managed switches, we see in fact a lot of products which are embedding a CPU on which the runtime could be ported onto. So that's a wide variety of product and of possibilities to embark the technology.
Speaker #0
Sure. Like for example, this IPC only consumes 4.5 watts and it does the work for data buffering.
Speaker #1
Yeah. So if we have some Moxa people that's... That's a great appeal to them to join the association so we could we could put the runtime onto their platform. Good. I see we have another question coming from from LinkedIn. Let me put it here from Colanda. Are you expecting the same application developed for this platform to be reused for the remaining platforms as well in the future?
Speaker #0
Yes, because the application is similar. It's for, as mentioned, is for the, they call it the EOR application. Not much change. The only thing that is fixed is the wellhead and the sensors. It's the same sensors. The application probably, if we do one, it will be similar to other location as well. And we can deploy it without going to the offshore platform. Let's see if I see the architecture here.
Speaker #1
So,
Speaker #0
yeah, I see the architecture here. You have this engineering station here and we can deploy to all the other six platforms without having to go there. I mean, we can do the engineering and we can deploy it via the telecommunication link. and it's done, it's possible.
Speaker #1
So we see here even an application with using wireless telecommunication in between. Yeah. So yeah, that's very impressive. Good. I see no other questions for now. So maybe one last question to you, Megat. What would you say to... Because we have seen for this application, okay, you have used... Schneider Electric for the co-editancy that you did it yourself and so on. But in general what would you say to all the technology vendors out there which are looking for their next generation of product and maybe of automation as well? Do you have something that you want to to tell them regarding your situation?
Speaker #0
So basically we are system integrator. We build systems to customers. Our customer is the end user that uses it for an application. As a system integrator, we look for the best solution and sometimes there are some specific requirements coming from customers that we need to think and we need to look at the technology. what technology that available in the market. So and As a system integrator, we are responsible. The sole responsibility of deploying the system to the customer is us. This is the beauty with IC61499. Because the IC61499 is very centric to system integrator, which we like. And what we want to tell to the provider of the technology is that sometimes talk to us. we probably have some ideas for the technology vendors to develop the hardware and probably the software um to for us to deploy more um iec 61499 systems yes
Speaker #1
thank you for your last uh last command megatz uh we reached the the end of this uh of this session of uo goes live So just to give to all our viewers just an outlook, we will have the next next uEgoz live coming quite soon so please stay tuned and have a look on our LinkedIn and YouTube channel to check when it will be. So here are the details if you want to get in touch with with Megat from TriceSystem if you are having any project in Southeast Asia. that you want to look for a system integrator to support you in implementing the technology, please use our member, use Megat and TriSystems and they will be happy to welcome you. Any last words, Megat?
Speaker #0
Yeah, I would like to thank you for having this session. I appreciate the time given to me to do this. presentation. I'm happy we have done this.
Speaker #1
Yeah, thank you. Thank you, Megat. Thank you for your support. And thank you to all the viewers who could make it or maybe will watch it afterwards. And please stay tuned for the next session of YoYo Girls Live. Thank you and bye, everyone.

About UAO Goes Live: The Future of Automation

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

About UAO Goes Live: The Future of Automation

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Embed

You may also like

Description

About UniversalAutomation.org (UAO)

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Transcription

Speaker #0
Universalautomation.org, it's about sharing a technology, a shared runtime execution engine.
Speaker #1
We believe the game change in automation because we have first one technology which is based on the IEC 64999, which is the standard which aims at decoupling hardware and software.
Speaker #0
Hardware itself is becoming very, very performant in terms of processing CPU power,
Speaker #2
and the future is more and more about software. This approach is really a winning approach. Because it's very very flexible, you develop the application once and you can reuse in each different configuration.
Speaker #3
That's exactly what Universal Automation and 61499 enables, because it brings a new formalism for developing software, which is object-oriented in nature and which allows deployment of a distributed hardware for the actual final control system. So let's say that it's a marriage made in heaven.
Speaker #4
So if I want to make more conscious decisions based on my business data, which also comes from the automation level, I need universal automation to get this data in an efficient way and with the right engineering efforts on the level when I can do and run the analytics.
Speaker #0
Offers are available not just from Schneider Electric with EcoStruxure Automation Expert, but also from Advantech, from Stahl, from ESA in Italy and from other companies.
Speaker #5
Advantech is growing really, really fast. And I believe if you want to keep on growing in the next future, you need to be able to innovate. When I see Universal Automation approach, it is exactly the way of innovation we need to go with.
Speaker #6
Most of our customers from Process Automation are pretty conservative, so never change a running system. But now we see a new generation coming up, what is used to new technologies. And they are open to test, to try these new functionalities. And I think most of them pretty well understand the advantages on this. I'm doing this now for 20 years, and I think over the years, this is the most exciting changes.
Speaker #2
And from my experience, I see that in the IT, for example, there has been a big revolution. And I expect the same in automation. I don't know when it will happen, probably takes a little bit of time, but probably a revolution will come.
Speaker #1
Hi everybody, good morning, good day to all of you. wherever you're based. My name is Greg Boucault and I'm the Chief Marketing Officer for universalautomation.org. Today I have the pleasure to welcome you in this new session of the UAO goes live. We have been through the introduction of the association what are this goal its goal and its mission so feel free to watch again our videos which are can be found on either our linkedin page or our youtube channel today i have the pleasure to welcome megatz general manager from the company Tri System and Megal will go with us through a use case that they have done, that Tri System has done using the technology. So please give a warm welcome to Megat. Hi Megat.
Speaker #7
Hi.
Speaker #1
So let's jump onto your introduction to give you plenty of time to introduce us to your company and your use case.
Speaker #7
Sure. Thank you, Greg. My name is Magad Shamsul. I'm the General Manager for TriSystem Engineering. So TriSystem is a system integrator. We've been doing system integration since 1994. We have been deploying 1131 systems since then. So we are the leading provider of products and engineering solutions specifically for oil and gas and petrochemical industry. But we have been expanding our market, not only oil and gas and petrochemical, we are looking at power and general industry as well. We offer state-of-the-art solutions to our customers, safety systems. process control system, software solutions, packages, process packages, fire protection, filtration, combustion, pneumatic hydraulics. We have about 160 people in the company. 85% is engineer. Myself is also an engineer. I'm a mechanical engineer but I've been doing this automation for more than 20 years. We have been doing deploy projects I think in our customer references, probably hundreds. But we don't stop on delivery. We offer the after sales as well. So like maintenance and on and upgrade. So we have maintenance contract. We have price agreement with our customers. So with the track record of a successful project, in fact, they don't remember the, our customer don't remember the product that we deliver. They remember our name as the system integrator that that deploy the system. So we are very committed on delivering projects and support and service the customer. We are based in Malaysia but we want to expand or we are currently expanding our reach out to Southeast Asia. So if you look at the map, we have here Malaysia and then we have Indonesia, Thailand, Vietnam, Myanmar and Philippines. So this is me. I'm the general manager for sales and marketing. So this is our key board of directors and key management. Yeah, let me go straight to the cases, the use cases. So, we have deployed this system, PAK8000, back in 2012. So, it's been more than 10 years operationally. Unfortunately, this PAK8000 has obsolescence issues. So we are being asked by our customers, how we want to solve this officer search issue. And because of that, because we have a contract, so we are providing them with, from the last 10 years, our support. And we send our engineers to do maintenance and so on. So we make sure the system is operational and well maintained. And any issue they can just call us, we'll send our engineers and make sure that the system uptime is there. But with this current issue with this PAD 8000, so we are proposed to upgrade this to another platform. So we have looking at solutions that can solve this issue. So we were looking at that. IC61499. And here we found we can answer these key questions that being asked to us by our customer. So the thing is that we don't want to change the cabinet. This is offshore platform, it is located remotely, it is not easy for us to access these facilities. You need to take a boat. to go there so we don't want to do a major job so you just change the component inside the existing cabinet recertify them because it's a hazardous area so we need to recertify the control cabinet to a zone two a zone two means that it is for suitable for hazardous area and then we we need to also maintain the similar power requirement The system that we are providing the last 10 years only consumed 300 watts. Actually, it's less than 300 watts, but 300 watts is what they gave us. The actual system running is about 160 watts. This system is running purely using solar power and a battery system. 61499 we can offer a longer lifespan to tackle the opposition issue and improve the total cost of ownership. So we are not obliged or we're not fixed to one hardware provider. We can play with any hardware that complies to IEC 61499. So the same functionality that the current system running on 1131. will be running with the same function on IEC 61499. And the pilot project that we are proposing to our customer is for the smallest platform. So the platform has seven offshore platforms. So I just show you the picture. So this is the cluster of the offshore platforms. All these seven platform clusters have our system and we are proposing to upgrade only this as a small platform called this G. And what we are proposing now is we're going to remove the PACK8000 hardware and put in right now we are choosing the Modicon M580D PACK redundant CPU. We're going to remove the I.O. and we're going to put the back-off I.O. modules integrated with I.S. So if you see here, we don't have I.S. barrier. The I.O. is integrated with I.S. And here we had this Kingfisher RTU unit and we're going to upgrade it with the Aviva EDS running on the Moxa Edge computer. So the whole system here is running at about 160 watts low power, but it will manage to help us in the offshore process, which is quite simple. It is a well-heeled platform. The well-heeled platform task is to bring out oil from the platform. but the system is basically what it does is it helps in what we call it the enhanced oil recovery so the system will help us in terms of how much gas or how much gas we need to inject in the well to bring up more oil so it's connected to a smart system whereby this smart system knows how much gas you need to inject in the oil field and to bring up oil, more oil out from the ground. So actually when we put the system back in 2012, by 2013 and 2014 it already pay back, they already got their money back. and it already served since then and now they feel that the life of the platform can be more extended because they see there's more oil that they can extract from this field. Hence, the importance of the system to be robust so we can take to make sure that the system is, we'll call it, don't have this obsolescent issue and so on so we can maintain the system probably another 10 years so this is the architecture from the picture you just showed just now this is the architecture that we propose to our customer so we see here we have this back off i o to take the pressure transmitter temperature transmitters, flow transmitters, and it goes to a switch, a managed switch. And then we have put two controllers, the D-PAC and 580. This is an engineered redundancy that we provide to this customer. And here we have our small edge computer that consumes about 4.5W running on Linux. this would be our, we call it the... edge data store or data buffering in case of the radio is they have problem and this platform running on the digital dmr digital model radio currently we have probably 100 mbps when we did back in 2012 we only had two mbps of internet or communication bandwidth, but they already upgraded it. So we get more bandwidth and with this more bandwidth, we can send good data, good high fidelity data. Before this, it was, I think the data fidelity is not that fine. But with the more bandwidth, with the more computing power that we have, we can do that. But the problem is radio link, if it rains, it will have issues with communication. So that's why we have a local hardware here to do the data buffering. But if you see here, this yellow line is all the control network is on OPC UA. The communication with the IO is on Modbus. TCP and the I.O. is on the ring network in case of failures. But we provide a ring network to enhance the reliability of the I.O. So the system here, so the cabinet, the system is here and this is the devices connected to the system it has hard wire as well as Modbus serial and Modbus internet TCP IP communication. We also connected to the charge controller. The charge controller is for the offshore solar system. And then from here, it goes to a radio link. The control network goes to radio link to the control DMR, which goes to the mother platform. and then we have converted it to the fiber optic and the fiber optic here will go to the control room, the CCR, is where in the, what they call it, the LQ, the living quarters. And this control network will be connected to our new EWS, which we're going to put together with the IC61499. compliance software, EcoStruxure Automation Expert. From this seven platform, we only upgrade one. So probably the plan is maybe three years or four years or five years to upgrade all these seven platform. But it will have currently this platform is running on the old protocol, the DNP3 protocol. So now we have a mix of OPC UA and DNP3 protocol, which is fine. We have tested it. It works. And for the start, only one platform will have 61499 with OPC UA. And we need to also add the connectivity to the Pi system, the Pi or IVVAR Pi system at this platform. Currently, it's using the MP3 Pi interface. Now we need to add the OPC UA connector to this Pi server so that we can get the data. But also, we do control. as well. So we send the set point from this PI server back to the platform and the platform control system will open the valve for the gas injection. The system is actually how to get the set point. The system is actually communicating with somebody or what they call it the engineer in the customers HQ. So the customer HQ would have an application software that they can intelligently look at the data that our system brings in and they can intelligently tell how much gas they want to inject in which particular well to get more oil. so in short um previously probably um the engineer need to go to the off offshore and do this calculation in in offshore so now he can sit in the office comfortably and do the simulations and then they can just put in the numbers and this number will come back to the offshore via this network and the control system will be able to adjust how much gas that they need to be injected in each particular well on this control system that we provided. So that's a bit of the local storage that we put. It's running as a lightweight storage system. It's Aviva Edge Datastore running. So we are going to use OBC UA and it will be connected to the PI server. And this is very lightweight. It only consumes, I will be putting in the hardware on Linux. So here we're going to put in the Moxa hardware running on Linux, I think, 11. And then with an ARM processor. So, in short, this is our use case. I'll be happy to take any questions from the floor.
Speaker #1
One question for myself is that I see that the whole system that you have is very distributed and how do you see that the technology, especially the 649 has helped you towards this this modeling of your application?
Speaker #7
Yeah, so 649, so the IEC standard would help us in case of, let's see, so the problem statement here, sorry, let me get back to this. The problem statement here is that we need to support the lifespan of the system to tackle the citizens issue, right? Right. So IC6149. is I think the answer because it doesn't have to be specified to what hardware that we use and probably this is something that we will ask in case if let's say we don't get this Deepak M580 anymore can I put another hardware from Stahl or Phoenix Contact yeah it can be because if we can have the hardware right now doesn't matter i as long as it's certified to it61499 yeah so oh if if if and and you and you see here we have many platforms here and as long as all the um hardware is certified and it doesn't matter i can get it can be like this platform can can be using um hardware from vendor a uh this hardware vendor b and venice so doesn't matter it it it will work it definitely will work um and the application doesn't change so i guess this is something that the customer wants the customer wants um that the system um is robust and they don't have to spend more money when, let's say, some hardware obsolete.
Speaker #1
Yes. So really this hardware and software independence to help in terms of, let's say, resilience maybe of supplying of products on one side and the other side to kind of push away the risk of end of life as we know it today. Yes. That's very good and that's what we are as Universal Automation.org pushing as values for the technology that we are supplying. So it's great to see that the customer as well, the one using the technology is also seeing that. I am switching to another question which is coming from LinkedIn, from Mudassir. Are there any bottlenecks or shortcomings?
Speaker #7
of the 649 where can be improved so do you have any um any feedback on that so yeah one thing that that um when when I presented this to Schneider um this hardware here is is not a product redundancy means that this deepak in 580 is just a single unit but because of this platform it's it's critical to have a redundant unit because it's far it's not easy to go and it's it's uh and we need to put a redundant system yes so we have uh one thing that with six one four nine nine i'm sure in the future uh there were come up with this redundancy but currently we are doing an engineered redundancy basically from from our engineering and we already tested it and we already demo to our customer it works um if let's say this one controller fail the other controller will take over but it requires some unique um integration that that we do so that's one shortcoming that that we face um during this uh just this case and and also um the io redundancy as well so there's kind of an engineered redundancy that we do um internally to to ensure that um if let's say uh an io card fail um we need to get another io to take over so um yes that's that's uh the the problem, the issue that I have when I did this. So I think I'm sure there is, in the future, there is a solution to this.
Speaker #1
Yes, yes. I mean, the technology in itself is always being improved and new features are added to the technology. That's the goal of the of the association in itself to gather those let's say feature requests and put them into the technology so that they can grow as well step by step with the needs of the different users. One thing which maybe happened in between your use case and now is that the newest version of the technology now embarks high availability. which could have been a great help for you in your cases but yeah i said it's evolving and it's all let's say features which are coming uh with the time and with the requests uh from the from the different users sure
Speaker #7
um yeah yeah just to add um i mean there is um schneider had offered me the redundancy on the ipc um the computer but the issue is that um my my problem with this is the power um i i only have 300 watts to play with um so we we need to have um maybe in the future the hardware that that um have um low power like this um like this total system we calculated is about 160 watts
Speaker #1
and it works it will work and you will serve the purpose and and I think that could be in fact a great way to make an appeal to technology vendors in fact because if we have more technology vendors which have such a product on which we could deploy the technology with with for example the higher availability so we can use it this could be a great functionality for you or a great opportunity what do you think
Speaker #0
Yes, definitely. If the technology or the OEM, the vendor that can look at each use case, I'm sure. If let's say it is for a gas pipeline or a remote application, even for oil and gas where we have a diverse similar like this, where we are depending on telecommunication to link the controller together and and we are doing an application whereby we we need the telecom we need the controller we need the the io all that can be packaged i'm sure there's a lot of application in the world that have a similar requirement like this.
Speaker #1
Yeah and that's a perfect point because I mean when we speak about vendors we do not speak only about traditional let's say PLC vendors but we also include that's why we use the board more technology vendors because we see IPCs, we see RTUs, we see managed switches, we see in fact a lot of products which are embedding a CPU on which the runtime could be ported onto. So that's a wide variety of product and of possibilities to embark the technology.
Speaker #0
Sure. Like for example, this IPC only consumes 4.5 watts and it does the work for data buffering.
Speaker #1
Yeah. So if we have some Moxa people that's... That's a great appeal to them to join the association so we could we could put the runtime onto their platform. Good. I see we have another question coming from from LinkedIn. Let me put it here from Colanda. Are you expecting the same application developed for this platform to be reused for the remaining platforms as well in the future?
Speaker #0
Yes, because the application is similar. It's for, as mentioned, is for the, they call it the EOR application. Not much change. The only thing that is fixed is the wellhead and the sensors. It's the same sensors. The application probably, if we do one, it will be similar to other location as well. And we can deploy it without going to the offshore platform. Let's see if I see the architecture here.
Speaker #1
So,
Speaker #0
yeah, I see the architecture here. You have this engineering station here and we can deploy to all the other six platforms without having to go there. I mean, we can do the engineering and we can deploy it via the telecommunication link. and it's done, it's possible.
Speaker #1
So we see here even an application with using wireless telecommunication in between. Yeah. So yeah, that's very impressive. Good. I see no other questions for now. So maybe one last question to you, Megat. What would you say to... Because we have seen for this application, okay, you have used... Schneider Electric for the co-editancy that you did it yourself and so on. But in general what would you say to all the technology vendors out there which are looking for their next generation of product and maybe of automation as well? Do you have something that you want to to tell them regarding your situation?
Speaker #0
So basically we are system integrator. We build systems to customers. Our customer is the end user that uses it for an application. As a system integrator, we look for the best solution and sometimes there are some specific requirements coming from customers that we need to think and we need to look at the technology. what technology that available in the market. So and As a system integrator, we are responsible. The sole responsibility of deploying the system to the customer is us. This is the beauty with IC61499. Because the IC61499 is very centric to system integrator, which we like. And what we want to tell to the provider of the technology is that sometimes talk to us. we probably have some ideas for the technology vendors to develop the hardware and probably the software um to for us to deploy more um iec 61499 systems yes
Speaker #1
thank you for your last uh last command megatz uh we reached the the end of this uh of this session of uo goes live So just to give to all our viewers just an outlook, we will have the next next uEgoz live coming quite soon so please stay tuned and have a look on our LinkedIn and YouTube channel to check when it will be. So here are the details if you want to get in touch with with Megat from TriceSystem if you are having any project in Southeast Asia. that you want to look for a system integrator to support you in implementing the technology, please use our member, use Megat and TriSystems and they will be happy to welcome you. Any last words, Megat?
Speaker #0
Yeah, I would like to thank you for having this session. I appreciate the time given to me to do this. presentation. I'm happy we have done this.
Speaker #1
Yeah, thank you. Thank you, Megat. Thank you for your support. And thank you to all the viewers who could make it or maybe will watch it afterwards. And please stay tuned for the next session of YoYo Girls Live. Thank you and bye, everyone.

About UAO Goes Live: The Future of Automation

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

About UAO Goes Live: The Future of Automation

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Description

About UniversalAutomation.org (UAO)

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Transcription

Speaker #0
Universalautomation.org, it's about sharing a technology, a shared runtime execution engine.
Speaker #1
We believe the game change in automation because we have first one technology which is based on the IEC 64999, which is the standard which aims at decoupling hardware and software.
Speaker #0
Hardware itself is becoming very, very performant in terms of processing CPU power,
Speaker #2
and the future is more and more about software. This approach is really a winning approach. Because it's very very flexible, you develop the application once and you can reuse in each different configuration.
Speaker #3
That's exactly what Universal Automation and 61499 enables, because it brings a new formalism for developing software, which is object-oriented in nature and which allows deployment of a distributed hardware for the actual final control system. So let's say that it's a marriage made in heaven.
Speaker #4
So if I want to make more conscious decisions based on my business data, which also comes from the automation level, I need universal automation to get this data in an efficient way and with the right engineering efforts on the level when I can do and run the analytics.
Speaker #0
Offers are available not just from Schneider Electric with EcoStruxure Automation Expert, but also from Advantech, from Stahl, from ESA in Italy and from other companies.
Speaker #5
Advantech is growing really, really fast. And I believe if you want to keep on growing in the next future, you need to be able to innovate. When I see Universal Automation approach, it is exactly the way of innovation we need to go with.
Speaker #6
Most of our customers from Process Automation are pretty conservative, so never change a running system. But now we see a new generation coming up, what is used to new technologies. And they are open to test, to try these new functionalities. And I think most of them pretty well understand the advantages on this. I'm doing this now for 20 years, and I think over the years, this is the most exciting changes.
Speaker #2
And from my experience, I see that in the IT, for example, there has been a big revolution. And I expect the same in automation. I don't know when it will happen, probably takes a little bit of time, but probably a revolution will come.
Speaker #1
Hi everybody, good morning, good day to all of you. wherever you're based. My name is Greg Boucault and I'm the Chief Marketing Officer for universalautomation.org. Today I have the pleasure to welcome you in this new session of the UAO goes live. We have been through the introduction of the association what are this goal its goal and its mission so feel free to watch again our videos which are can be found on either our linkedin page or our youtube channel today i have the pleasure to welcome megatz general manager from the company Tri System and Megal will go with us through a use case that they have done, that Tri System has done using the technology. So please give a warm welcome to Megat. Hi Megat.
Speaker #7
Hi.
Speaker #1
So let's jump onto your introduction to give you plenty of time to introduce us to your company and your use case.
Speaker #7
Sure. Thank you, Greg. My name is Magad Shamsul. I'm the General Manager for TriSystem Engineering. So TriSystem is a system integrator. We've been doing system integration since 1994. We have been deploying 1131 systems since then. So we are the leading provider of products and engineering solutions specifically for oil and gas and petrochemical industry. But we have been expanding our market, not only oil and gas and petrochemical, we are looking at power and general industry as well. We offer state-of-the-art solutions to our customers, safety systems. process control system, software solutions, packages, process packages, fire protection, filtration, combustion, pneumatic hydraulics. We have about 160 people in the company. 85% is engineer. Myself is also an engineer. I'm a mechanical engineer but I've been doing this automation for more than 20 years. We have been doing deploy projects I think in our customer references, probably hundreds. But we don't stop on delivery. We offer the after sales as well. So like maintenance and on and upgrade. So we have maintenance contract. We have price agreement with our customers. So with the track record of a successful project, in fact, they don't remember the, our customer don't remember the product that we deliver. They remember our name as the system integrator that that deploy the system. So we are very committed on delivering projects and support and service the customer. We are based in Malaysia but we want to expand or we are currently expanding our reach out to Southeast Asia. So if you look at the map, we have here Malaysia and then we have Indonesia, Thailand, Vietnam, Myanmar and Philippines. So this is me. I'm the general manager for sales and marketing. So this is our key board of directors and key management. Yeah, let me go straight to the cases, the use cases. So, we have deployed this system, PAK8000, back in 2012. So, it's been more than 10 years operationally. Unfortunately, this PAK8000 has obsolescence issues. So we are being asked by our customers, how we want to solve this officer search issue. And because of that, because we have a contract, so we are providing them with, from the last 10 years, our support. And we send our engineers to do maintenance and so on. So we make sure the system is operational and well maintained. And any issue they can just call us, we'll send our engineers and make sure that the system uptime is there. But with this current issue with this PAD 8000, so we are proposed to upgrade this to another platform. So we have looking at solutions that can solve this issue. So we were looking at that. IC61499. And here we found we can answer these key questions that being asked to us by our customer. So the thing is that we don't want to change the cabinet. This is offshore platform, it is located remotely, it is not easy for us to access these facilities. You need to take a boat. to go there so we don't want to do a major job so you just change the component inside the existing cabinet recertify them because it's a hazardous area so we need to recertify the control cabinet to a zone two a zone two means that it is for suitable for hazardous area and then we we need to also maintain the similar power requirement The system that we are providing the last 10 years only consumed 300 watts. Actually, it's less than 300 watts, but 300 watts is what they gave us. The actual system running is about 160 watts. This system is running purely using solar power and a battery system. 61499 we can offer a longer lifespan to tackle the opposition issue and improve the total cost of ownership. So we are not obliged or we're not fixed to one hardware provider. We can play with any hardware that complies to IEC 61499. So the same functionality that the current system running on 1131. will be running with the same function on IEC 61499. And the pilot project that we are proposing to our customer is for the smallest platform. So the platform has seven offshore platforms. So I just show you the picture. So this is the cluster of the offshore platforms. All these seven platform clusters have our system and we are proposing to upgrade only this as a small platform called this G. And what we are proposing now is we're going to remove the PACK8000 hardware and put in right now we are choosing the Modicon M580D PACK redundant CPU. We're going to remove the I.O. and we're going to put the back-off I.O. modules integrated with I.S. So if you see here, we don't have I.S. barrier. The I.O. is integrated with I.S. And here we had this Kingfisher RTU unit and we're going to upgrade it with the Aviva EDS running on the Moxa Edge computer. So the whole system here is running at about 160 watts low power, but it will manage to help us in the offshore process, which is quite simple. It is a well-heeled platform. The well-heeled platform task is to bring out oil from the platform. but the system is basically what it does is it helps in what we call it the enhanced oil recovery so the system will help us in terms of how much gas or how much gas we need to inject in the well to bring up more oil so it's connected to a smart system whereby this smart system knows how much gas you need to inject in the oil field and to bring up oil, more oil out from the ground. So actually when we put the system back in 2012, by 2013 and 2014 it already pay back, they already got their money back. and it already served since then and now they feel that the life of the platform can be more extended because they see there's more oil that they can extract from this field. Hence, the importance of the system to be robust so we can take to make sure that the system is, we'll call it, don't have this obsolescent issue and so on so we can maintain the system probably another 10 years so this is the architecture from the picture you just showed just now this is the architecture that we propose to our customer so we see here we have this back off i o to take the pressure transmitter temperature transmitters, flow transmitters, and it goes to a switch, a managed switch. And then we have put two controllers, the D-PAC and 580. This is an engineered redundancy that we provide to this customer. And here we have our small edge computer that consumes about 4.5W running on Linux. this would be our, we call it the... edge data store or data buffering in case of the radio is they have problem and this platform running on the digital dmr digital model radio currently we have probably 100 mbps when we did back in 2012 we only had two mbps of internet or communication bandwidth, but they already upgraded it. So we get more bandwidth and with this more bandwidth, we can send good data, good high fidelity data. Before this, it was, I think the data fidelity is not that fine. But with the more bandwidth, with the more computing power that we have, we can do that. But the problem is radio link, if it rains, it will have issues with communication. So that's why we have a local hardware here to do the data buffering. But if you see here, this yellow line is all the control network is on OPC UA. The communication with the IO is on Modbus. TCP and the I.O. is on the ring network in case of failures. But we provide a ring network to enhance the reliability of the I.O. So the system here, so the cabinet, the system is here and this is the devices connected to the system it has hard wire as well as Modbus serial and Modbus internet TCP IP communication. We also connected to the charge controller. The charge controller is for the offshore solar system. And then from here, it goes to a radio link. The control network goes to radio link to the control DMR, which goes to the mother platform. and then we have converted it to the fiber optic and the fiber optic here will go to the control room, the CCR, is where in the, what they call it, the LQ, the living quarters. And this control network will be connected to our new EWS, which we're going to put together with the IC61499. compliance software, EcoStruxure Automation Expert. From this seven platform, we only upgrade one. So probably the plan is maybe three years or four years or five years to upgrade all these seven platform. But it will have currently this platform is running on the old protocol, the DNP3 protocol. So now we have a mix of OPC UA and DNP3 protocol, which is fine. We have tested it. It works. And for the start, only one platform will have 61499 with OPC UA. And we need to also add the connectivity to the Pi system, the Pi or IVVAR Pi system at this platform. Currently, it's using the MP3 Pi interface. Now we need to add the OPC UA connector to this Pi server so that we can get the data. But also, we do control. as well. So we send the set point from this PI server back to the platform and the platform control system will open the valve for the gas injection. The system is actually how to get the set point. The system is actually communicating with somebody or what they call it the engineer in the customers HQ. So the customer HQ would have an application software that they can intelligently look at the data that our system brings in and they can intelligently tell how much gas they want to inject in which particular well to get more oil. so in short um previously probably um the engineer need to go to the off offshore and do this calculation in in offshore so now he can sit in the office comfortably and do the simulations and then they can just put in the numbers and this number will come back to the offshore via this network and the control system will be able to adjust how much gas that they need to be injected in each particular well on this control system that we provided. So that's a bit of the local storage that we put. It's running as a lightweight storage system. It's Aviva Edge Datastore running. So we are going to use OBC UA and it will be connected to the PI server. And this is very lightweight. It only consumes, I will be putting in the hardware on Linux. So here we're going to put in the Moxa hardware running on Linux, I think, 11. And then with an ARM processor. So, in short, this is our use case. I'll be happy to take any questions from the floor.
Speaker #1
One question for myself is that I see that the whole system that you have is very distributed and how do you see that the technology, especially the 649 has helped you towards this this modeling of your application?
Speaker #7
Yeah, so 649, so the IEC standard would help us in case of, let's see, so the problem statement here, sorry, let me get back to this. The problem statement here is that we need to support the lifespan of the system to tackle the citizens issue, right? Right. So IC6149. is I think the answer because it doesn't have to be specified to what hardware that we use and probably this is something that we will ask in case if let's say we don't get this Deepak M580 anymore can I put another hardware from Stahl or Phoenix Contact yeah it can be because if we can have the hardware right now doesn't matter i as long as it's certified to it61499 yeah so oh if if if and and you and you see here we have many platforms here and as long as all the um hardware is certified and it doesn't matter i can get it can be like this platform can can be using um hardware from vendor a uh this hardware vendor b and venice so doesn't matter it it it will work it definitely will work um and the application doesn't change so i guess this is something that the customer wants the customer wants um that the system um is robust and they don't have to spend more money when, let's say, some hardware obsolete.
Speaker #1
Yes. So really this hardware and software independence to help in terms of, let's say, resilience maybe of supplying of products on one side and the other side to kind of push away the risk of end of life as we know it today. Yes. That's very good and that's what we are as Universal Automation.org pushing as values for the technology that we are supplying. So it's great to see that the customer as well, the one using the technology is also seeing that. I am switching to another question which is coming from LinkedIn, from Mudassir. Are there any bottlenecks or shortcomings?
Speaker #7
of the 649 where can be improved so do you have any um any feedback on that so yeah one thing that that um when when I presented this to Schneider um this hardware here is is not a product redundancy means that this deepak in 580 is just a single unit but because of this platform it's it's critical to have a redundant unit because it's far it's not easy to go and it's it's uh and we need to put a redundant system yes so we have uh one thing that with six one four nine nine i'm sure in the future uh there were come up with this redundancy but currently we are doing an engineered redundancy basically from from our engineering and we already tested it and we already demo to our customer it works um if let's say this one controller fail the other controller will take over but it requires some unique um integration that that we do so that's one shortcoming that that we face um during this uh just this case and and also um the io redundancy as well so there's kind of an engineered redundancy that we do um internally to to ensure that um if let's say uh an io card fail um we need to get another io to take over so um yes that's that's uh the the problem, the issue that I have when I did this. So I think I'm sure there is, in the future, there is a solution to this.
Speaker #1
Yes, yes. I mean, the technology in itself is always being improved and new features are added to the technology. That's the goal of the of the association in itself to gather those let's say feature requests and put them into the technology so that they can grow as well step by step with the needs of the different users. One thing which maybe happened in between your use case and now is that the newest version of the technology now embarks high availability. which could have been a great help for you in your cases but yeah i said it's evolving and it's all let's say features which are coming uh with the time and with the requests uh from the from the different users sure
Speaker #7
um yeah yeah just to add um i mean there is um schneider had offered me the redundancy on the ipc um the computer but the issue is that um my my problem with this is the power um i i only have 300 watts to play with um so we we need to have um maybe in the future the hardware that that um have um low power like this um like this total system we calculated is about 160 watts
Speaker #1
and it works it will work and you will serve the purpose and and I think that could be in fact a great way to make an appeal to technology vendors in fact because if we have more technology vendors which have such a product on which we could deploy the technology with with for example the higher availability so we can use it this could be a great functionality for you or a great opportunity what do you think
Speaker #0
Yes, definitely. If the technology or the OEM, the vendor that can look at each use case, I'm sure. If let's say it is for a gas pipeline or a remote application, even for oil and gas where we have a diverse similar like this, where we are depending on telecommunication to link the controller together and and we are doing an application whereby we we need the telecom we need the controller we need the the io all that can be packaged i'm sure there's a lot of application in the world that have a similar requirement like this.
Speaker #1
Yeah and that's a perfect point because I mean when we speak about vendors we do not speak only about traditional let's say PLC vendors but we also include that's why we use the board more technology vendors because we see IPCs, we see RTUs, we see managed switches, we see in fact a lot of products which are embedding a CPU on which the runtime could be ported onto. So that's a wide variety of product and of possibilities to embark the technology.
Speaker #0
Sure. Like for example, this IPC only consumes 4.5 watts and it does the work for data buffering.
Speaker #1
Yeah. So if we have some Moxa people that's... That's a great appeal to them to join the association so we could we could put the runtime onto their platform. Good. I see we have another question coming from from LinkedIn. Let me put it here from Colanda. Are you expecting the same application developed for this platform to be reused for the remaining platforms as well in the future?
Speaker #0
Yes, because the application is similar. It's for, as mentioned, is for the, they call it the EOR application. Not much change. The only thing that is fixed is the wellhead and the sensors. It's the same sensors. The application probably, if we do one, it will be similar to other location as well. And we can deploy it without going to the offshore platform. Let's see if I see the architecture here.
Speaker #1
So,
Speaker #0
yeah, I see the architecture here. You have this engineering station here and we can deploy to all the other six platforms without having to go there. I mean, we can do the engineering and we can deploy it via the telecommunication link. and it's done, it's possible.
Speaker #1
So we see here even an application with using wireless telecommunication in between. Yeah. So yeah, that's very impressive. Good. I see no other questions for now. So maybe one last question to you, Megat. What would you say to... Because we have seen for this application, okay, you have used... Schneider Electric for the co-editancy that you did it yourself and so on. But in general what would you say to all the technology vendors out there which are looking for their next generation of product and maybe of automation as well? Do you have something that you want to to tell them regarding your situation?
Speaker #0
So basically we are system integrator. We build systems to customers. Our customer is the end user that uses it for an application. As a system integrator, we look for the best solution and sometimes there are some specific requirements coming from customers that we need to think and we need to look at the technology. what technology that available in the market. So and As a system integrator, we are responsible. The sole responsibility of deploying the system to the customer is us. This is the beauty with IC61499. Because the IC61499 is very centric to system integrator, which we like. And what we want to tell to the provider of the technology is that sometimes talk to us. we probably have some ideas for the technology vendors to develop the hardware and probably the software um to for us to deploy more um iec 61499 systems yes
Speaker #1
thank you for your last uh last command megatz uh we reached the the end of this uh of this session of uo goes live So just to give to all our viewers just an outlook, we will have the next next uEgoz live coming quite soon so please stay tuned and have a look on our LinkedIn and YouTube channel to check when it will be. So here are the details if you want to get in touch with with Megat from TriceSystem if you are having any project in Southeast Asia. that you want to look for a system integrator to support you in implementing the technology, please use our member, use Megat and TriSystems and they will be happy to welcome you. Any last words, Megat?
Speaker #0
Yeah, I would like to thank you for having this session. I appreciate the time given to me to do this. presentation. I'm happy we have done this.
Speaker #1
Yeah, thank you. Thank you, Megat. Thank you for your support. And thank you to all the viewers who could make it or maybe will watch it afterwards. And please stay tuned for the next session of YoYo Girls Live. Thank you and bye, everyone.

About UAO Goes Live: The Future of Automation

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

About UAO Goes Live: The Future of Automation

Tune in and discover how UniversalAutomation.org and its ecosystem are transforming industries, one open standard at a time.

Hosted on Ausha. See ausha.co/privacy-policy for more information.

Embed