0:06 Hi, my name is Lisa Richter. I'm the
0:07 director of industry outreach and growth
0:11 for CSIA. Welcome to this master class.
0:13 Before we get started, a quick word
0:16 about CSIA. Probably most of you here
0:18 today are familiar with the association,
0:21 but if you are not, all you really need
0:24 to know that it's CSIA's mission to help
0:25 system integrators build better
0:28 businesses. How do we do that? Well, for
0:30 starters, we have a team of volunteer
0:34 system integrators who crowdsource a
0:37 best practices manual to help SI scale
0:40 their businesses. In fact, the BP manual
0:42 released the latest version about a year
0:45 and a half ago, and they are already
0:47 planning and working on the next
0:50 version. CSA is also about to launch a
0:53 new learning hub, which is a way for our
0:55 members to help their team members get
0:58 up to speed quickly with system
1:00 integrator specific
1:03 um courses and training um around the
1:05 business that we think will be super
1:07 helpful for our members. Um, CSA also
1:09 offers a certification program and other
1:11 resources including professional
1:13 development, learning from peers, and
1:16 access to professional services like
1:18 insurance and legal and finance who
1:21 really understand the SI's unique
1:24 business needs. For our partner members,
1:27 CSA offers an ecosystem to grow your SI
1:29 programs, understand your customer pain
1:32 points, monitor industry trends, and
1:34 share your thought leadership. With
1:36 thousands of qualified integrators and
1:39 suppliers, the CSIA Industrial
1:41 Automation Exchange helps system
1:43 integrators, industry suppliers, and end
1:46 users connect and do business. For
1:48 system integrators and partners, it
1:50 provides a platform to support your
1:52 content and SEO marketing efforts,
1:54 position yourself as a thought leader,
1:55 and nurture prospects during their
1:59 complicated buyers journey. If you are
2:01 not currently a member, now is a great
2:03 time to join. Membership provides you
2:06 and your entire team a full lineup of
2:08 virtual events and other re resources
2:11 from accounting to sales to operations
2:14 365 days per year. It also means you and
2:17 your team can attend the CSIA conference
2:20 because this annual in-person event is
2:23 members only. A quick word about the
2:25 conference. Uh we um if you are
2:27 attending the welcome reception will be
2:30 on the Tuesday evening and uh it's kind
2:33 of a beachy theme. So, a reminder to
2:35 pack your Hawaiian shirt or as like my
2:37 boss likes to say, your loud shirt.
2:40 We'll see what happens. If you want to
2:42 just get a flavor of CSIA and its
2:43 members, I encourage you to listen to
2:45 the Talking Industrial Automation
2:48 podcast. CSIA members talk all things
2:50 industrial automation, and it's a great
2:52 way to hear what your peers are up to.
2:55 One last housekeeping note before I turn
2:57 it over to today's speakers. If you have
3:00 a question, please use the Q&A feature
3:02 in Zoom. um that just helps us stay
3:05 organized and uh the session is being
3:07 recorded and you will get a link to a
3:10 recording in the next few days. At this
3:11 time I would like to turn it over to
3:32 I hope you can see my screen.
3:36 Yep, you're good. Thank you. So, welcome
3:41 from our side as well. Uh, we wanted to
3:44 focus on these emerging technologies and
3:47 specifically bring in a perspective of a
3:49 system integrator on these technologies.
3:52 So I am together joined with Timothy
3:55 triplet uh president of core and
3:58 technologies who will join me during
4:01 this pro this process and share with you
4:04 his inputs of the project and the
4:08 perspective there going forward uh I
4:10 would like to emphasize
4:12 emphasize
4:15 that we will talk about OPAF open
4:19 process automation forum the Texas ALM
4:21 project. That's where Timothy takes over
4:24 and why they selected an OPA system. I
4:27 will then step in again with the focus
4:32 on the IS-1 plus and the focus that it
4:34 can be used in the classified areas in
4:37 the hazardous area and then Timothy will
4:40 again provide an input on uh what the
4:43 current status is and then we can have a
4:47 Q&A. So what is open process automation
4:50 forum? This is a forum as you can see up
4:54 over here. A lot of the end users, a lot
4:59 of the uh vendors and now a lot of the
5:02 integrators have joined to come together
5:06 to put forward this technology. It is a
5:09 industry. It's a it's a it's a part of
5:12 developing an indust industry standard
5:15 which will be based on the current
5:17 standards so that you are adding on and
5:21 improving on what is already available
5:24 but ensuring that they are interoperable
5:26 and they
5:30 are meeting up to the requirements of
5:33 the OPASS uh standard. So this is the
5:36 typical architecture what you see over
5:38 here. It is
5:42 uh comprising here of the OPAS products
5:45 itself. But in the blue what you see
5:48 here are your legacy devices or
5:51 equipment if I can call them and then
5:54 you have the relevant gateways which
5:56 will allow you to communicate to the
5:59 OPAS connectivity framework. As I
6:01 mentioned earlier, this is a standard of
6:03 standards. So, we are working with a lot
6:06 of standard development organizations,
6:09 the OPC foundations, the DMTF and
6:12 various others where we are working with
6:16 them to update, improve, add on, uh add
6:19 value to that and develop and integrate
6:21 those standards into an overall open
6:25 process automation standard.
6:28 today's ecosystem you have the
6:31 automation vendor could be a PLC a DCS
6:34 and then a system integrator like you
6:37 putting together the solution based on
6:41 the end user your customer our customers
6:44 applications your expertise of the
6:49 industry of the equipment your your uh
6:52 your expertise of the processes to
6:55 implement and execute which is also a
6:58 very important part of the expertise you
7:01 carry and then even the possibility to
7:04 maintain it over a period of years. So
7:07 this is your current uh ecosystem and
7:12 what OPAS is trying to do is build up
7:15 something very similar. You are still in
7:18 the middle of the game but then you have
7:21 separate hardware suppliers and software
7:24 suppliers. Part of the story is that you
7:27 will be able to have an interoperable
7:30 system and interoperable systems would
7:33 give you the flexibility of using
7:36 multiple hardware vendors and multiple
7:39 software vendors. It also gives you the
7:43 facility that you would be able to use
7:46 softwares and then port the applications
7:48 you have developed from one hardware to
7:51 another. So a lot of the capabilities
7:54 are brought in by these two vendors uh
7:57 segment. Now it is not necessary they
7:59 need to be separate. They can be all
8:01 one. You could have the hardware vendor
8:04 also providing the software component as
8:07 well and then uh as an integrator you
8:10 are implementing it uh down the way and
8:12 uh installing it at the end users
8:15 facility. Service providers basically
8:19 are providing the service from a product
8:21 life cycle perspective. You are
8:23 providing support during the operations
8:26 at the plant. So that could be another
8:29 role uh which is part of the ecosystem
8:31 which you could be
8:35 implementing. How are we developing the
8:39 standard? the ecosystem. You as a system
8:42 integrator, the vendors and of course
8:45 the end users. You all have user
8:47 stories. You have experiences with your
8:51 current installations. And you are
8:53 wanting a change. You want something
8:55 different. What are your expectations?
8:57 You would be building it up and sending
9:02 it over to Opaf over user stories.
9:04 we can develop use cases out of that and
9:06 probably then even a system integrator
9:11 is providing a use case or even the uh
9:14 vendors are putting up the requirements.
9:17 All of these boil down into the
9:19 standards. They are
9:22 being discussed. They are being
9:25 evaluated and then they are being also
9:29 generated as profiles as certification
9:32 requirements and then they are being
9:35 implemented into a standard. So that is
9:39 how the industry voice drives the OPAS
9:42 standard. We would welcome all of you
9:44 all to join us in this role if you all
9:49 want to join OPath. Uh contact me. Uh
9:51 you'll have an email id down the way
9:54 where we can then get you connected to
10:00 OPath. Standards are going to enable
10:03 functionality. What you see right now is
10:05 the standards which have evolved over
10:08 the period of some 2017 if I remember
10:10 correctly. First version was with
10:12 interoperability. Then was the base
10:15 configurations, function blocks,
10:17 configuration, portability and then we
10:20 these are in the works as of now.
10:22 Application portability, orchestration,
10:26 physical platform. So it's an evolving
10:30 standard. Is it done? No. Is it ready to
10:33 be implemented? Yes. The version 2.1 is
10:36 ready for you to implement a test bed.
10:39 is be ready for you to implement a pilot
10:42 project and even actually commercialize.
10:44 This is what we are going to show you a
10:46 commercialization of the project. So
10:49 that is the
10:53 uh workflow that we have within the uh
10:56 forum of what we have to do to finish the
10:57 the
11:00 standard. Of course it is a continuous
11:01 improvement project. So it'll we'll keep
11:04 on updating improving as what we learn
11:07 from these implementations and what we
11:09 need to adapt and improve.
11:10 improve.
11:15 COPA so OPath is a standards development
11:18 organization. OPAF will not go out and
11:21 market. These are the OPAF members who
11:23 have come together
11:29 to market the OPAS based solutions. So
11:30 together with C plane together with
11:33 collaborative system association with
11:37 currently these integrators woodsis
11:39 burrows and others and then the
11:42 component suppliers we are putting
11:46 together industry proven uh devices
11:48 along with uh the capabilities of system
11:52 management of C plane and CSI and then
11:54 also the system integration teams which
11:57 are there. Again, you're most welcome to
12:01 join the uh COPA group. Uh you do you
12:06 would be able to then take the uh active
12:10 role in developing uh solutions for your
12:17 customers. It was of course built on the
12:20 open standard. The opath standard is
12:23 ensures high availability applications.
12:27 Definitely it is intrinsically secure
12:30 capable of remote management and then
12:32 the cost factor which is the most
12:35 attractive is not only the cost factor
12:37 at the time of your capital purchase but
12:40 also as a total cost of ownership you
12:43 will see definitely a lot of savings there.
12:50 Texas&M project. This is the first uh
12:54 commercial project from COPA and I will uh
12:56 uh
13:08 okay thank you Robbie explain to you
13:12 Timothy I have you have control.
13:14 Okay, very good. Appreciate that,
13:18 Robbie. And I would like to um advance
13:27 now. And I am trying to do
13:31 that. Ah, there we go. Okay. Yes. So the
13:36 this project is the auto is for
13:40 Texas&M nuclear engineering. They are a
13:42 ranked number one in undergraduate
13:46 nuclear engineering programs, number two
13:48 in graduate nuclear engineering
13:50 programs. It's home to one of the
13:52 largest university research
13:55 reactors. It has a strong partnership
13:58 with national labs, department of
14:01 energy, other industry leaders and well
14:05 supported by the state of Texas.
14:08 They have formed a advanced center for
14:12 advanced small modular and micronuclear
14:15 reactors under the Texas&M engineering experiment
14:22 station with the goal of advancing the
14:24 nations and the states leadership in
14:28 advanced nuclear technology.
14:30 As a part of their ongoing research,
14:32 they are investigating control
14:34 technologies to facilitate the
14:38 deployment of small modular reactors and micro
14:39 micro
14:43 reactors. Uh, and why now? Because
14:46 nuclear has been around a long
14:50 time. Why now? There's a um if you'll
14:53 switch to the next uh slide there,
14:58 Robbie, I'll can give it a try. But um
15:06 go. There are some some diverse and
15:08 challenging environments out there. One, remote
15:09 remote
15:13 power when in areas that that are not
15:22 military applications where you need
15:25 power, secure power in a in an area that
15:28 just doesn't have power. Now emergency
15:31 response a hurricane wipes out the um uh
15:36 the power sources in say Haiti or some
15:39 place like that. A small modular reactor
15:42 could be quickly deployed to that
15:45 location and reconnected to the grid to restore
15:47 restore
15:50 power. AI data centers. I'm sure this
15:55 hasn't missed your attention that AI is
15:59 a massive hog of energy for the for the
16:02 training centers and such.
16:04 So those uh the companies that are
16:07 putting up these multi-billion dollar
16:10 projects would like to have the power
16:13 source right next to them so they don't
16:21 u systems that they don't have control
16:24 over to provide power for their data
16:27 centers. Uh the micro reactors uh are
16:29 particularly useful in space exploration
16:31 where you need something that has that
16:35 compact form factor, easily transported,
16:38 reliable, long life span well over 10
16:41 years without refueling. Uh all of that
16:45 is is really attractive for space
16:49 exploration also which is um
16:53 accelerating uh along with the AIS.
16:57 So there's a definite need for the
17:00 um for nuclear
17:05 powerly small modular reactors that have
17:08 gone through sufficient training,
17:11 testing, evaluation.
17:15 uh as opposed to the old way we we our
17:17 industry in the United States first
17:20 started off with um each nuclear power
17:25 plant was huge and custom and so each
17:29 one had to reinvent the wheel. But with
17:32 small modular reactors, you you've got
17:35 the design worked out and you can if you
17:39 need more power, you just put in more
17:42 small modular reactors. So you just
17:44 increase the number of them. It's like
17:48 having instead of a one cylinder engine,
17:50 now you've got an eight cylinder, a 16
17:54 cylinder engine. each one contributing
17:57 uh equally to the to the mix which also
17:59 increases reliability and lots of other
18:03 other positive factors. So the future
18:06 for nuclear power is going to be in a
18:14 reactors and let's see if there's next
18:19 slide. Yes. Okay. So&M part of their uh objective
18:22 objective
18:24 is to um [Music]
18:26 [Music]
18:31 um because the the small modular and
18:33 micro reactors are going to be often
18:36 times in locations where there isn't a
18:40 large staff to support it to train to
18:44 operate it and such. There's a need for
18:46 autonomous control.
18:47 for remote
18:50 management and of course when you start
18:52 talking about remote management
18:56 especially now cyber security becomes a
18:58 critical critical
19:02 factor. So their objectives were to
19:06 answer these uh challenges to be a
19:08 remote management autonomous control and cyber
19:10 cyber
19:13 security. So if you'll advance to the
19:19 Robbie. So they established a control test
19:20 test bed
19:23 bed
19:26 to prove out the technologies that are
19:31 critical for these reactors long term.
19:34 So they they created a relatively simple
19:37 as you can see the side the the control
19:42 unit and test bed on the right and is
19:45 small but as you know the control
19:48 technologies to control a small process
19:53 and a large process are the same basic
19:56 technologies. So starting with the P
19:58 Pnid they they have a couple of
20:01 different loops. The power generation if
20:04 you see on the left side the the heater
20:07 instead of doing this with nuclear power
20:11 they're using uh electrical power as the heating
20:12 heating
20:17 source but to maintain some fees some
20:21 um as much of the feel of a real nuclear
20:27 reactor. The control rods is a actuator
20:32 that its position determines how much uh
20:34 how fast the nuclear reaction is
20:36 happening and how much heat is generated
20:39 by the reactor. So in this case the
20:41 position of that control
20:44 rod affects the power generation from
20:48 the electrical uh to the heater. So it's
20:51 uh they try and make this as realistic as
20:51 as
20:55 possible without exposing the uh the
20:58 students to dealing with nuclear
21:03 sources or the for the research
21:07 here. The test this particular test bed
21:10 u not yeah stay focused on the one
21:14 before Robbie if you would please. U yes
21:16 there you go. Okay. So this test bed
21:21 uses water. Um but just to assure you&m
21:23 is also quite active in the areas of
21:27 molten salt and and other um aspects of
21:30 the nuclear generation but this
21:33 particular test bed is strictly focused
21:37 on on the control aspect of it. And on
21:40 the right the picture of the system the
21:44 black cabinet is the uh copa 500 the
21:46 control systems
21:48 uh the rest of it is there is the
21:51 process and the electrical um
21:53 connections. Okay now to the next one Robbie.
21:56 Robbie.
22:00 So having designed the the
22:03 experiment the next question was what
22:05 control system we're going are we going
22:07 to use? I mean, there's a variety of
22:11 standard control systems um uh available
22:13 out there, but they wanted something
22:19 that was modern, open, and could be the
22:21 very best at helping them reach their
22:25 research objectives with cyber security,
22:28 reliability, rapid iteration uh of the
22:32 design. So they can make changes, test
22:36 them out, do modeling and iterate over
22:39 and over again. So they needed that was
22:41 important to them uh to have high
22:44 compute and data capability uh a remote
22:47 management capabilities for
22:51 it. And so when it all boiled down the
22:55 the Copa 500 was was an obvious choice.
22:59 The stall IO is very flexible and
23:02 proven. The Cotus control is as is a de
23:05 facto standard for IEC
23:09 61131. The ignition HMI also very well
23:13 established uh and from a from a a good
23:17 company with good support. the Azrock um
23:20 uh industrial computer and this
23:25 leverages all off offtheshelf type of um
23:29 technology. So these components are not
23:32 expensive especially compared to uh a
23:39 DCS vendor or even the the uh normal um
23:41 smaller PLC system
23:46 suppliers. A super micro um the terrific
23:50 capabilities as far as um the computer, the
23:51 the
23:55 OCF communications platform which is or
23:59 technology which is a particular uh
24:01 implementation of
24:04 OPCUA related to open process
24:07 automation. uh Cflame provided this
24:11 system management which is um what makes
24:14 the whole system work and makes it um
24:16 reliable and practical long term for
24:18 support and a Cisco
24:22 switch a nice package. So okay now if we
24:26 can go to the next slide um
24:31 Robbie okay and this is just um uh we
24:34 won't belabor this but this is the exact
24:39 models of the um stall equipment that we
24:43 chose for the IO it it need met our
24:46 project needs well it's very
24:49 flexible so next uh next slide Robbie I
24:52 know you'll talk more about that
24:54 And so this
24:59 identifies the COPA 500 a typical small
25:01 system design
25:04 uh the components and where where those
25:08 reside like the bottom bottom black sort
25:14 of box there is the um uh that's the the
25:18 um the main compute for advanced process
25:22 control and modeling. Uh the
25:26 um the style equipment is uh is there
25:29 sort of in the middle the the orange and
25:32 blue chunks there that handles the
25:34 interface to the real world on that
25:39 mixed rail above that. Uh the DCN uh the
25:43 Azelock is on the the right side.
25:46 uh as you're looking at it on the right
25:49 side, power supply, switch uh is all
25:54 there uh and uh uh it makes for a very
25:57 nice um system and it's fully
25:59 integrated. That was um that was of
26:00 particular interest to us. We weren't
26:02 interested in
26:05 researching how to build an OPA system.
26:07 We were interested in researching what
26:10 it can do and how you can use it best.
26:13 So, the KOPA 500 provided a really nice
26:16 package of a fully integrated OPA
26:20 product. Um, and it's uh we know that
26:22 it's already been pre-integrated and
26:26 tested and so it is a robust
26:29 implementation of OPA.
26:32 We wanted to give OPA a really good uh
26:36 chance to to show what it can do and we
26:39 didn't want it to be hampered by our
26:42 mislication or
26:44 u missing something or overdoing or underdoing
26:56 something. Okay. So now um Ravi if you
27:03 you. Thank [Music]
27:05 [Music] you.
27:07 you.
27:11 And here we go. uh give you all a a
27:14 brief background about stall in case you
27:17 don't know and also on the iOS
27:20 particularly how it is available with
27:25 solutions.
27:30 Uh yeah so we are founded in 1876 I may
27:34 look old but I'm not that old. It's uh
27:38 companies with uh lot of the electronics
27:41 uh involvement electrical products and
27:43 then we also do and build complete
27:47 solutions uh in the sense that uh in the
27:51 in the IECX world uh they need a
27:54 certified workshop who can do it. Here
27:58 in the NEC world you have the UL698 and
28:00 all which allows you to build and
28:03 certify the complete solution. We can
28:06 also do trainings and then we also do
28:09 hazardous area uh evaluations and
28:12 services related to that based in
28:15 Germany and uh accessible all over the
28:18 world. uh somewhere around 18 operating
28:22 subsidiaries and beyond that about 5960
28:33 344.1 million euros with uh
28:37 1,743 employees across the globe. Uh
28:40 small company, small but nimble. We were
28:43 able to learn the opportunities of uh
28:47 these new emerging technologies and be
28:48 part of
28:51 it. We are available across a complete
28:54 portfolio of the electrical lighting and
28:58 hazardous area automation products. Uh
29:02 it is good enough certified for NECX and
29:08 ICX. So triple certified nearly 90 95
29:11 percent of the products maybe a few
29:13 percent where we may need two different
29:16 products to satisfy the individual certification
29:18 certification
29:20 requirements. That's what we call the
29:24 automation wall. Uh we have your barrier
29:28 isolators over here the IO's and then we
29:30 have Ethernet APL switches and then the
29:34 power supply for that wireless access
29:38 points fiber optics for hazardous area.
29:40 Yes, fiber optics also in the hazardous
29:44 area can be a source of ignition because
29:47 it is a concentrated form of energy. So
29:50 you need to be careful there. uh control
29:54 solutions, purge uh grounding devices
29:59 again uh handling the static energy that
30:01 comes into play when you're transferring
30:04 uh um raw material from one tank to
30:08 another HMIs and then the cameras for
30:11 monitoring the process areas. So we
30:13 nearly fit into
30:16 the control layer and then the field device
30:17 device
30:20 level. We've been doing this for the
30:24 last 30 years. In fact, uh the uh
30:28 iteration from 2000 onwards has been
30:34 consistently the same. Uh so you have uh
30:36 I would say a a very good form fit
30:38 factor which allows you easy
30:42 replacements. uh very early in the uh
30:48 1997 we implemented the Profus DP RS485
30:51 standard which we then donated to the
30:54 Profibus International organization. We
30:58 were the first to use in 2009 the fiber
31:02 optic uh opis standard which allows us
31:06 to run fiber optics into hazardous area
31:09 without a conduit just a regular fiber
31:14 optics maybe an armored cable and we are
31:16 now getting ready for the next 30 years
31:21 over the span of uh next few years when
31:24 the technologies evolve and we are ready
31:28 with uh the way forward on what the
31:30 industry is looking
31:33 for. That's what I was talking about. So
31:36 this was the old uh versions if I can
31:39 call them uh from 2000 onwards. And uh
31:42 this is the latest version. You can see
31:45 the drail and the bus rail remains the
31:48 same. The IO modules here with a red
31:51 handle. I can remove this one, put a new
31:54 one in and it runs in a minimum uh
31:59 capability uh mode. Uh the CPUs the form
32:01 fit factor and the connection to the bus
32:04 rail remains the same. So you can
32:07 replace an old CPU power supply
32:10 combination with a new CPU and still run
32:13 the old IO modules if you would like. So
32:16 a lot of combinations available. The
32:20 zone one day one devices are certified
32:22 as such because they are certified. You
32:26 don't need a purged enclosure. You don't
32:28 need an explosion proof enclosure. You
32:31 can put it in a standard Nema 4X or an
32:34 EXE enclosure. These are all intrinsic
32:37 safe communication uh bus in the back.
32:40 So you can implement hot swapping and
32:43 then of course the flexibility of using
32:46 either detachable terminals and uh screw
32:47 terminals over
32:50 there. That's the socket if you would
32:53 like to have uh from the perspective a
32:57 three slot but also a four slot. More
33:00 importantly, you have the capability to
33:02 select protocols here. Specifically, if
33:05 you're using it as a remote IO connected
33:09 to the traditional uh PLC and DCS
33:13 networks over Profy bus uh profet,
33:17 Modbus uh TCP IP, Modbus RTU or Ethernet
33:20 IP, you can select the port over here.
33:23 And then if you have the RS485, you can
33:26 select the addresses over here. That's
33:29 how simple and easy it is. Good enough
33:34 for minus40 to 167° F or 75° C
33:38 installation. Uh you can use either this
33:40 three slot version or the four slot
33:42 version on your right where you will
33:44 have redundant CPU and redundant power
33:46 supply as
33:48 well. The
33:51 IO's some very good features over there.
33:54 We all know that project engineering
33:56 goes until the time you have installed
33:59 and commissioned your panel. At the last
34:01 minute, you always have a requirement of
34:03 one additional input or one wire is
34:05 going in another panel and not in this
34:08 panel. So very
34:11 flexible multi-function configurable IO
34:15 signals. The discrete or the digital IO
34:17 module I can configure it as input
34:20 output. NAMO discrete inputs whatever I
34:23 like. The analog input module I can
34:26 configure it as input output port to 20
34:30 0 to 20 with heart without heart with
34:33 alarms. I can also have a temperature
34:35 module which can be either an RTD or a
34:38 thermouple or a PT00. So you could
34:41 configure these if you have them as
34:43 spare channels and then you can you can
34:47 configure them uh at as at a late stage
34:50 of your project as you go along and you
34:54 realize uh you need to add something
34:57 more. Uh the temperature ratings are
35:03 minus 40F to 167F or 75 C. At that high
35:06 temperature you are now able to offer an
35:07 extended lifetime because the
35:10 electronics is much more capable. This
35:13 15 year is just a theoretical
35:16 calculation. We have customers with 25
35:19 30 years installation who say hey this
35:22 is working reliably and I don't want to
35:25 change it. I definitely don't have a
35:27 happy sales team who would love to have
35:30 customers buying products day in and day
35:33 out. But then uh that is not Stal's
35:36 philosophy. We would definitely like the
35:39 customers to have a low total cost of
35:41 ownership. Uh additional status
35:44 information. This is very very uh
35:48 creative if I can say uh that it is able
35:51 to detect that hey I'm running in an
35:55 extreme temperature beyond the spec or I
35:59 was supposed to have 1 million on off uh
36:02 uh states and now you're crossing that 1
36:05 million onoff states uh you this all
36:09 could affect my electronics life and uh
36:12 I'm giving you an alarm one year before
36:15 I drop dead and let you know, hey, keep
36:18 a spare ready, plan a shutdown so that
36:21 you can replace me without having to do
36:24 a unplanned shutdown. So that's a very
36:28 good feature. Uh we talked about
36:30 artificial intelligence or machine
36:33 learning. This is something of where the
36:36 electronics inside with the sensors are
36:38 realizing what is the environment around
36:42 it, how good it is and how bad it is and
36:44 how it is going to affect its lifetime.
36:46 So, uh that's really a very good
36:50 feature. Uh enhanced diagnostics. Uh
36:52 each of the IO channels have the
36:56 capabilities of line fault detect. So if
36:58 your field signals from the IO terminal
37:01 to the field device are broken or short
37:04 circuit, you will get a local alarm, a
37:07 red LED over here and also an alarm on
37:10 your asset manager or on your
37:13 HMIs. The devices are optimized for zone
37:17 one, zone 2. Uh basically you are able
37:21 to do 16 channels per discrete module
37:23 and eight channels per analog or
37:25 temperature module. especially if there
37:27 are two wires
37:30 100% backward compatible and then of
37:32 course it's very much cost efficient
37:34 because of the high IO
37:37 density that's a range for the zone one
37:39 day one hot swappable IO modules
37:42 intrinsically safe outputs these are the
37:44 four and eight channel versions because
37:46 they have to drive a lot of power but
37:48 then I have the digital input output
37:50 which is soft configurable I can
37:53 configure it as input or output the 16
37:56 channel version, the analog universal,
37:59 the temperature. This is an interesting
38:02 digital output module with a solenoid
38:04 valve built into it. So, I don't need a
38:07 separate valve station. I don't need a
38:10 separate IO station. I can run it on the
38:13 same remote IO station or an extended IO
38:15 station. And this would be your output
38:18 to drive high voltage, high current
38:21 capabilities. Same for zone 2 div 2. The
38:25 only advantage here is that I have uh
38:28 non-incentive or non-intrinsically safe
38:32 inputs available here. So you in our
38:35 world here in div 2 in the NAC div2
38:39 world end users would prefer to use a
38:42 non-intrinsically safe or non-incentive
38:45 field devices and uh the IO's are
38:48 capable of such an
38:51 interface for the non-intrinsically safe
38:53 or the non-incentive
38:56 uh IO modules and field devices we can
39:00 offer IO redundancy like we had for the
39:03 CPU redundancy. Uh, one major capability
39:07 is that these IO modules aren't talking
39:11 to the CPU. So, you actually don't have
39:15 to go to the DCS CPU or the PLC CPU. The
39:19 IO CPU is uh voting where to take the
39:22 data from if one drops dead and the
39:24 second takes over. And then it is also
39:27 alerting you in uh at the HMI or the
39:29 alarm manager that hey one of the IO
39:32 modules is dead. You better replace
39:35 it. A sample construction specially I
39:38 wanted to show you this valve island and
39:41 the IO island all together. It's a div
39:43 one installation. This is the only
39:45 conduit here and then this is the
39:48 complete enclosure uh in a name of
39:52 4X. Again here the IS and the nonIS and
39:54 a different construction in a 1200
39:57 by,000 mm you could do anywhere between
40:04 signals. Okay, that was all about the
40:08 IO's but what are we doing for OPAS? So
40:11 uh with the newer hardware and the capability
40:13 capability
40:18 uh to have an open OS system like Linux,
40:21 we were able to implement three
40:26 versions. We have this DCN IO which only
40:30 has an OPCUA based OPAS server. It talks
40:33 the op open communication framework or
40:36 the open connectivity framework
40:38 information model which can then be
40:40 accessed by the DC and computer or the
40:45 ACP. So that is acting like a remote IO
40:47 but not with the traditional
40:51 profuset Ethernet IP but with OPA
40:54 server. This is the -40 version. Then we
40:59 also have the capability to embed the
41:03 IC61131 in this case codices uh which
41:05 you can implement which is part of the
41:09 OPAS uh group and then you could also
41:13 implement IEC 61499 runtime which is the
41:16 universal automation which can also
41:18 which is nothing but distributed control
41:20 or an eventdriven based programming
41:24 unlike the IC 61131 which is a
41:26 sequential uh sequence-driven
41:30 programming uh standard. Uh though the
41:34 languages in 61499 are similar to what
41:35 uh you use in
41:37 61131. The
41:40 61131 standard as you would all know is
41:44 the same standard that is used by most
41:46 of all the PLC
41:49 uh companies for their IDE for the
41:52 engineering tool. uh it is only that
41:55 they customize it add some value add
41:59 features and then u uh customize it for
42:04 their hardware. So uh if you do know the
42:06 any of the ladder programming function
42:09 blocks or sequential function blocks and
42:11 all that you could still do those
42:15 programmings on a codis platform or on a
42:18 61499 UAO platform.
42:19 platform.
42:24 Opas has been in play since 2016 2017
42:27 since the association with open group.
42:31 Uh Exxon Mobile built the first test bed
42:33 and has also implemented the first
42:35 lighthouse. That's what you see is an
42:38 image of one of the IO panels. 90% of
42:41 the IO counts were with stall's IS-1
42:46 plus extended IO and uh the selection of
42:51 the IO's was by the plant by the by the
42:55 actual user who want who wanted a more
42:58 sturdy G3 compliant configurable IO
43:01 where they have all those flexibilities
43:04 like the flexibility opas standard
43:08 provides. So that is what is now running since
43:09 since
43:11 2024. Some of the other test beds which
43:13 were built by Schneider which were built
43:16 by Intel and demonstrated at the NAMO general
43:17 general
43:20 assembly in
43:24 2023. What we see as an opportunity and
43:26 this is for the embedded solutions which
43:29 I talked about uh earlier and of course
43:32 there are the OPA solutions as well. the
43:35 OPA server solutions you could do
43:37 migration green field from legacy
43:40 systems in a do div to zone to zone one
43:43 projects a lot of your com uh you are
43:46 providing support or are international
43:48 companies where you would be deploying
43:52 projects uh in the ATEX IEC world so we
43:56 could support you here ideally 100 to
43:59 150 IO points please note this is not
44:01 good for safety systems or fire and gas systems
44:02 systems
44:05 OPAF doesn't cover safety. It is only to
44:08 the it is only limited to the control
44:10 system. And then additionally same
44:14 styles I use are not rated for
44:17 safety. Not good enough for robotic
44:19 machine control or a conveying system.
44:21 It is good for a process industry
44:25 application. So again uh please be aware
44:28 of these uh limitations from a
44:32 perspective of using our
44:36 hardware. I get back to Tim and uh he
44:40 shares with you the uh the current
44:44 status of the Texas&M project. All yours
44:46 Tim I'll continue to uh scroll through
44:49 as you tell me.
44:51 Okay. I do appreciate that Robbie. Uh
44:55 yes and uh I appreciate your your
44:58 comments about point counts like 100 150
45:01 point counts and such. Just to be sure
45:03 the audience is clear on
45:06 this opass
45:09 um open process automation
45:14 systems can scale way beyond that up to
45:17 you know large large systems. uh what
45:20 people would normally think of as a DCS
45:21 type of of
45:25 application. So it's a uh it's a highly scalable
45:26 scalable
45:30 system with um the distributed DCNS each
45:34 DCN handling its particular area
45:36 geographical or functional area where
45:40 where that's been assigned. So for&M
45:43 this application uh this was a one of
45:45 the the smaller
45:49 applications and also from a um systems integrator
45:51 integrator
45:55 perspective it is the
45:57 um open process
45:59 automation particularly as it scales to
46:02 larger systems the system integrator
46:06 role varies from what traditionally it
46:08 might have been when you get into the
46:12 size of like the DCS type size of
46:14 systems and such. Often times the
46:19 supplier, the vendor would um sort of
46:22 politely nudge the system integrator out
46:25 of the way and take responsibility for
46:28 the entire system and require that in
46:31 order for them for them to guarantee and
46:35 warrant their system. But now with OPA,
46:39 the systems integrator uh is in a really
46:41 good position all the way through the
46:43 project because he's essentially he's an
46:45 extension if he's if he's doing his job
46:50 well, he's an extension of the end user
46:52 that just a knowledgeable extension of
46:56 them and it becomes a very trusted um
46:58 part of their of their company even
47:00 though he's not physically in the
47:02 company. So I have clients that we've
47:04 been working with for well over 30
47:07 years. Uh and it's because of that
47:10 relationship and trust. Now at A&M on
47:13 this the OPA what we
47:15 um where the status is right now is the
47:17 test bed is complete. The control system
47:19 is connected. They're developing the
47:22 control applications now against a
47:25 digital twin. They're um they're quite
47:27 happy with the system. the ability to
47:31 rapidly iterate has been demonstrated uh
47:34 and that they can choose whatever tool
47:36 works best for them in their particular
47:40 application uh Python, mat
47:46 lab skill sets that recent graduates and
47:49 researchers have developed as a part of
47:51 their normal course development and
47:55 learning. So this OPA fits really well
47:57 with those. They don't have to conform
48:01 to a specific vendor's rigid here's how
48:05 you talk to us and you won't talk any
48:07 other way. Uh the tools and libraries
48:10 are there is still some maturing
48:12 happening. it is doesn't affect the
48:14 functionality directly the core
48:18 functionality but I see that the tools
48:22 the suppliers uh continue to enhance and
48:26 improve uh the libraries and tools so
48:30 it's it's not as mature as say a
48:34 uh a DCS or a one of the other PLC's
48:38 that is um very slowm moving so there's
48:41 a the pro positive part of this is it's
48:46 a very fastly fast to um to develop in particular
48:47 particular
48:52 uh I want to also add that while it's a
48:55 solid technology uh which with
48:57 application to many projects
49:02 uh it is it offers a lower cost than
49:04 conventional approaches even on the
49:06 small scales which was was surprising it
49:09 was eye openening to me uh and it is
49:10 seeing good accept acceptance with the
49:13 enduser community at ARC. It was very
49:15 well received at Arc by the end users
49:18 there. They were excited by the progress
49:21 that uh some of the early adopters were
49:24 seeing and the success they were having.
49:26 Uh there are some new concepts as a
49:28 systems integrator. There are some new
49:31 concepts such as the GDS
49:34 um and the OCF communications, how those
49:37 are done, how those are configured and
49:42 how they uh they are intelligent enough
49:44 that sometimes you as a systems
49:46 integrator you think I've got to
49:50 configure this down to the last detail.
49:53 But the GDS and OCF handle a lot of the communication
49:55 communication
49:59 and that you would normally do it and it
50:01 just it just sort of works in the
50:04 background. Um someone like uh like a
50:07 Macintosh versus a Windows a few decades
50:11 ago with the where the Mac just just
50:13 worked where the Windows required lots of
50:14 of
50:18 attention. But as we get those um as we
50:21 hit those copa and stall both been very
50:23 supportive and rapidly addressed any
50:25 information gaps where we didn't
50:28 understand the system fully or an&m to not
50:30 not
50:32 um the flexibility of the style IO Ravi
50:35 presented that very well that was a a
50:37 selling point for their the choice of
50:40 them out of uh other suppliers that
50:42 could have provided the IO style offered
50:45 a particularly attractive package
50:48 Because at the time we were designing
50:51 the system, the&m didn't know exactly
50:53 what type of sensors and what type of
50:55 signals they'd be using. The fact that
50:58 the thermouple card can handle all the
51:01 different types of thermouples, RTDs,
51:04 um was a plus that the digital IO could
51:08 be configured input, output, whatever.
51:11 That was all um a
51:14 plus from the system. One of the things
51:17 we did learn uh as as a systems
51:21 integrator uh part since you're
51:23 you're taking responsibility for the
51:27 system, it's very important that you understand
51:28 understand
51:31 uh and reduce the risk of have I got
51:34 everything I need in this price and when
51:36 we estimate here's how much this is
51:39 going to cost. uh the Copa 500 provided
51:42 a particularly attractive package and
51:45 that we didn't have to worry do I have
51:47 everything I need in there? Have I
51:49 missed a component? Have I missed some
51:53 software package or anything? It was all there.
51:54 there.
51:59 Um that um um that was uh that was a
52:01 plus from a systems integrator
52:04 perspective and long-term as cyber
52:06 security because threats are
52:09 continuously emerging. This isn't like a
52:12 normal world where you put in a system
52:14 and you're not going to change it for 30
52:16 years. you put in a system
52:19 today, it is likely to have cyber
52:21 security initiatives that need to be
52:24 rolled out to it at some point. The fact
52:26 that we're working with
52:31 COPA, we know that they have already
52:34 pre-verified and tested the cyber
52:36 security initiatives that need to be
52:39 rolled out so to flush out any
52:40 incompatibilities and make sure
52:44 everything is is smooth. So that was um
52:47 that was a big big um learning thing
52:50 from our perspective to realize this is
52:52 a little bit of a different world. If
52:59 Robbie. Okay, these are some of the
53:02 higher level control that's being done
53:08 in the um compute package. um uh and it
53:12 is things that is looking at uh
53:16 regarding autonomous control and since
53:18 most system integrates most systems
53:21 integrators don't really get into this
53:23 but they trust me there is a lot going
53:26 on in the world of autonomous control
53:29 and the development there that the
53:32 researchers love the the capabilities of
53:34 the of the system. If you'll go to the
53:36 next slide, uh
53:39 Robbie, so this is this is sort of where
53:41 we sit right now. the the system is
53:46 installed um and it has put&m in a great
53:50 position to continue their research uh
53:53 into a variety of autonomous control
53:57 technologies and is um
53:59 uh helping them address the critical
54:04 aspects of SMR small modular reactor
54:06 control enabling faster and better
54:08 development of clean nuclear power which
54:12 is the benefit of us all. Uh and that's
54:16 where we are today. Um we've had some
54:17 wonderful learning opportunities during
54:21 this uh in Copa and and uh Style have
54:23 always been there to provide good
54:26 support and help us with any area where
54:29 we had a little information gap that we
54:32 needed to um properly apply the system.
54:37 And that's uh that's it for me.
54:40 Thank you uh Timothy. Uh these are our
54:44 contact details. Uh we would be happy to
54:46 receive any inputs from you and if there
54:51 are any questions uh right now or later.
54:53 So I do have a couple questions. Sorry
54:55 I'm I'm buttoning in. Um a couple
54:57 questions came in from the audience. You
54:59 may have addressed them. Um but just to
55:02 be perfectly clear uh the first question
55:05 is can other IO module vendors other
55:09 than stall be used with OPA?
55:12 Uh definitely possible. Uh it is a
55:16 matter of asking your preferred vendor
55:19 if uh they have the op they are opath
55:21 aligned or they have the opt
55:24 certification which will come in place
55:27 uh soon. uh from a copa membership. Yes,
55:31 there is uh Phoenix already there uh and
55:34 star but uh typically down the way uh it
55:37 will be an open platform for other IO
55:40 vendors also.
55:43 Yes. And we have Go ahead. Go ahead. I
55:45 was just going to say we have uh in some
55:47 of our other projects we have actually
55:50 used the the Phoenix contact since they
55:53 are part of the of the ETH ecosystem. We
55:55 have used them in the past. uh but this
55:57 particular project stall just uh the
56:00 flexibility built into their package was
56:02 really attractive and so we went with
56:04 stall for this one.
56:06 So this one might be a little bit out of
56:08 context because it came in while you
56:09 were talking about something else but it
56:12 says what are they using for digital twin?
56:14 twin?
56:19 Ah okay that is for Texas&M. Yeah. Yes.
56:23 Yes. That is a um um
56:28 that is where we passed it over to&m and
56:31 they're the ones that um uh that are
56:34 actually doing that. Uh otherwise I I
56:36 would I would just tell you what they're
56:38 they're doing but and because it is a
56:40 university so they are very open about
56:42 what they're they're doing. This is not
56:45 like oh this is proprietary they're not
56:47 going to tell anybody. It's just that I
56:49 don't have the ability to answer it
56:50 clearly, but if someone will reach out
56:54 to me, I can get them in contact with&m
56:58 uh researchers to uh answer that
57:00 question for them. Awesome. So, I have
57:02 one final question before uh we do the
57:06 final slides and that is
57:09 uh as system integrators, what do they
57:13 we need to get started?
57:15 Well, the first thing definitely is to
57:18 build a test bet as I would say get your
57:21 hands dirty, experience the technology,
57:24 experience the plug and play and uh once
57:27 you are sold out then of course uh you
57:30 will never go back to a legacy system at
57:33 least that is what OPath is all about
57:35 and uh I'm sure uh that will give you
57:38 that confidence to also uh talk to your
57:40 customers about it. So building a test
57:43 bed will be the first step over there
57:46 and uh you can join copa you can join
57:49 opath and uh you can learn more of the
57:52 technologies you can share your stories
57:54 what experiences you have from the test
57:57 bed or otherwise and uh we would be
58:01 happy to take those inputs in at
58:04 awesome thank you all right so I'm just
58:07 going to wrap things up here um my
58:09 colleague will put up some slides for me
58:12 as I go through my last little bit here.
58:15 On behalf of C Go ahead. No, I said
58:18 thank you from our side. Yeah.
58:20 On behalf of CSA, I would like to thank
58:21 our speakers Robbie and Timothy for this
58:23 informative discussion and thank you to
58:25 our staff for sponsoring the event and
58:28 of course thank you for attending. Um,
58:30 and that's a wrap. Please bookmark the
58:32 CSA events calendar so you don't miss
58:34 any upcoming events and um, have a great day.
58:37 day.