Skip to content
Episode 2: IOT and SCADA with Dan Turner episode artwork

Nov 9, 2017 27 min

Episode 2: IOT and SCADA with Dan Turner

from Pipeliners Podcast Hosted by Pipeliners Podcast

Russel and guest Dan Turner talk about the Internet of Things and what it means in a SCADA context. They consider issues with communication and security and look ahead to how technology will change pipeline industries.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

Episode 2: IOT and SCADA with Dan Turner

0:00 27:54
of matches

Transcript Auto-generated, may contain errors

Welcome to the Pipe Liners Podcast, episode 2. The Pipe Liners Podcast, where professionals, bubblegeeks, and industry insiders share their knowledge and experience about technology, projects, and pipeline operations. And now your host, Russell Treet. Well, first off, I just want to say thanks for listening to the Pipe Liners Podcast.

We really appreciate you taking the time to listen to this episode and to show our appreciation. We want to let you know that we're offering listeners an opportunity to win a prize pack and we're offering a customized Yeti Tumbler to one listener each episode. Here's how you register to win. All you need to do is go to pipelinerspodcast.com slash win.

That's pipelinerspodcast.com slash win, W-I-N, to enter yourself in a drawing. This is our way of saying thank you for being part of the show. Well, we are really fortunate today and I'm excited, I got to tell you. This is the first kind of real episode of Pipe Liners Podcast.

We did one and it was just me talking to you about how I got this crazy idea and what we want to accomplish. And this week we start with our first guest ever, Dan Turner, who works for PTC. And I got to tell you, Dan and I go back quite a long ways. We can each tell stories on the other that probably, well, we don't want to tell them on the podcast anyways.

You have to meet us in person to get those. But I really think the world of Dan, he's one of those guys that, as I mentioned in the first episode, he's one of those guys that I've learned a great deal from. Dan knows a lot about the industry. He's been around a long time.

So Dan, if you would, tell us a little bit about yourself and your background and what you do. Okay. Thank you Russell. I appreciate the opportunity to be the first guest is a huge honor.

My background has always been instrumentation controls, which morphs from downstream to upstream into skata, instrumentation controls and measurement. That's pretty much where my motto that keeps me on track or my mission has always been reducing the cost through technology of moving the world community's energy. And we find ways to bring in technology to accomplish just that. Yeah.

And for the listeners, I got to say, Dan probably knows a whole lot. In fact, Dan's probably forgotten more about that than most of us will ever know. Dan, I asked you on in particular, I want to talk to you about the future of skata and a little bit about Internet of Things. A lot of people are asking me, well, how's that new?

How's that different? How's that any different than things we've been doing for 20 years in skata? So why don't you tell us a little bit about what you think the current state of the skata market is in skata technology and how maybe you expect to see that change in the next five to 10 years? Well, you know, after spending the last x number of decades or a few decades on the skata side of it, we watched a couple of transitions.

We watched several transitions as technology changes, we find ways to bring new technology to the bear, the burden of getting information back in and dealing with the data source, finding ways to manipulate the data source, et cetera. And for the last 10, 20 years, maybe not quite 20, we have found skata hosts to be the kind of the one tool we've used because we found a way to pull data and we found a way to pull it into the operational station. And we found the limits of how it deals with and moves that data forward. I've been paying attention to what this thing is called IoT or IoT industrial Internet of Things.

What's happening is the rest of the world is coming alive, understanding the real cool thing that's called connectivity and remote connectivity. Of course, oh man, I want to say 30 some odd years ago, that's what the skata folks were doing. The folks were doing automation and upstream midstream had to deal with a lot of these questions and used old radio technologies to pull data and then Bell to two modems and then the radio connectivity, et cetera. So we've always found a way to adopt technology once it proves to be reliable and we change with it.

Really the whole IoT question, I see a stack of individual tools that have learned how to work nicely together to fill in if you were to look at the IoT model, all of these tools find a way to connect all of these different goals within what the IoT model is. And that's really what I'm seeing. I'm finding tools coming from other industries, the rest of the business world now that they're trying to connect everything, all of a sudden they're building tools that also apply to where we are, our traditional market of skata. Is IoT a small change?

Is it something slightly different than skata or is it a complete rethink of what we classically think of and pipeline operations of skata? You know, it's really skata for the enterprise in a sense. If you think of it that way, you know what, I agree with you, man. I think that nails it.

I think it's actually a quantum leap. I'm a guy who likes to think about the history of technology, right? So, you know, up until really until Windows started to begin to proliferate and some of these simple HMI tools began to be released on Windows, skata was a dark art that existed in a room by itself with specialized engineers and big computers and they brought all this data up and they put it on screens and they did their magic, but that didn't go anywhere. With modern or modern skata tools, it's easy to get the data up into the host, you know, at the enterprise level into the server farm.

It's easy to move that data around. And I guess what I'm seeing is that Internet of Things is taking that and rather than first needing to get the data up to the enterprise and then scattered around, now what we're looking at is, no, we're going to scatter the data all the way from the endpoint. Yeah. Yeah.

Does that make sense? Does that line up with what you think? And we're just in the very beginning of it. As always, we're going to end up with a legacy issue to deal with and how to take today's technology and patch it into the everything connected world.

But what's running out is very fast is the manufacturers of our devices, things, controllers, things in the field are going to come straight from the factory with that connectivity and it's going to change the way data flows, it's going to change the way we access that data. And so the things that we do today will be how we deal with the legacy stuff a few years from now. And that's just getting data flowing. Now how do you connect all these other things that you mentioned?

Yeah. And that's why I say, you know, if you look above, let's step above the skata host and you look at all of these different departments with all the different functions in midstream or upstream or downstream and they're all running very fast, have been running very fast to get their individual little block of application solution solved. And in doing so, you don't have time to really meet with everybody else and say, well, what shall we call this one thing? And so everybody calls the same one thing something different, which creates as part of the contributor to what I call everybody calls silos.

You know, one of the things I'm saying, historically, the issue was about connectivity and the money was spent on connectivity. Well, connectivity is getting to be less of the technical challenge. You know, the cost of communications is coming down. Skata systems are, you know, in terms of the host are becoming open.

Now there's this issue of data value. You know, if I'm getting data once a minute, is that same data more valuable if I get it once a second or once every hundred milliseconds, you know, is there greater frequency of the data, does it have more value? I know that one of the things that we've talked about in our company is having very high rate data changes how you do leak detection. You know, if I'm doing leak detection behind the skata system at the host level and I'm dealing with one minute or five minute data, things that are hard to model or hard to see in the data get easy to see if I'm looking at data every hundred milliseconds.

To me, that's a big, big change. The other thing, and you were talking about this and that is if I were to go and build a skata system using state of the art tools, I'm going to have to watch the data. I'm going to wire an instrument up to a field device, a PLC, a flow meter, an RT or something. And then I'm going to have to name that point in that field device.

And then I'm going to bring that data up to a skata host and I'm going to have to name that same data element in the skata host. And probably the syntax is different. And then I'm going to need to get that data out of the skata host. If it's a meter information, I might need to get it to accounting or if it's operations information, I might need to send it over to engineering or I might need to send that data into a hydraulic model that's performing leak detection and all of those places, that same data point is going to have a different name.

One of the things I see in IOT, and that's radically different than what we're doing is skata, is I name the element at the field device, at the edge of the network, and then everybody just goes and grabs that data point versus having to rename it and hook it up. Maybe that's an oversimplification, but to me that seems like that's a big, big change if that's really the case. You know, I don't think it's oversimplification at all because all of a sudden this data is going to be available to whoever needs it. It's not going to be chokehold or held by a single silo.

Who wants the data from this one device will subscribe to that device. Here's how you subscribe to the device. All of a sudden it's going to clean up a lot of all of that planning. The harder part will be I would imagine if you have half a million devices to subscribe to, there will be a lot of work for somebody, but I see it being less work than what we're doing now by groups of people.

Yeah, no, I think that's right. I think it also raises another interesting question. And again, I'd like to talk about history, but when I first got into skata, everything about skata was in a dedicated group. They managed the devices, they managed the communications, they managed the computers, everything.

Well now, everything out to the automation device in the field, all the way back through the server forms, all of that's managed by the information technology group. It's all infrastructure. What it raises for me and a question is, is skata, is it going to get absorbed and brought into the IT infrastructure group? And does IoT make that easier for organizations to do?

It's going to be a major shift. I believe field communications and things that you plug in, let's go past the legacy. Well, actually even just go only a short time forward when you can access this data through the subscription model, it's going to be a matter of if you're the operations people with your operation station, which we call a skata host, you're going to subscribe to the data you need. Let's say you're in marketing and you're trying to do, when I say marketing, I'm talking about like a midstream and you're trying to forecast the ability to deliver on a contract, you're going to subscribe to whatever those data bits are you need.

So I think the shift will be that whole communication, that whole capability of pulling secure data from the field and delivering it to where it needs to be is going to be one layer of data flow. And then what you do with that data from there, how you send out subscriberable data to your internal customer or your external customer will be another layer of information communication, actually. And the other thing we have to wrap our brain around is now that I'm pulling my, let's say, tubing pressure or I'm pulling static pressure from a flow station, there's a lot of metadata that'll flow with that as well. And that metadata is the device, what kind of device, the health of device, the maintenance of the device, the last time it was calibrated, all of that information will also be subscribed able data going to parties of interest around that.

And one thing you hit on earlier, you have lots of data flowing, how do you know it's good data? How do you know it's reliable data? I see, you know, this whole big data thing, there will be data modeling and capturing to give validation to the data. So I won't be, yeah, this is wonderful.

I can collect, you know, a billion, you know, bits per whatever. And I've got all this data, but is it good data? You know, how are you going to wrap something, wrap it around that? Yeah.

And what is the definition of good? Yeah. Yeah. We can go on a long time on that, I think.

Good is dependent on the purpose of the data. Yeah. You know, if I need data that's repeatable, because I'm using it to control the process, that's different than any data that's accurate because I'm using it for custody transfer measurement. So there's all of that too.

But I think you made a really interesting point. And I think that's one of the things that people don't get is that part of what's going on with IoT is this idea of attaching metadata. One of the things I love about our business is we fill it full of buzzwords, you know, and you listen to somebody talk about Internet of Things and Industrial Internet of Things and you hear IoT, I IoT, big data, data analytics, predictive analytics, and that's just a handful of the terms that's used. What I find interesting about this is these are IT, kind of hardcore IT information technology concepts, the idea of metadata.

That term is well understood in the software development domain, in the data management domain. You know, there's the data in the metadata, the metadata being data about the data. So if you think of that as well, I have a pressure and that's the data and then this is the transmitter and all of its information from the manufacturer. And then this is the maintenance information about all of that.

And then of course that ties into, you know, I see them as my maintenance management systems. One of the things that's implied by Internet of Things is I'm going to tie everything together at the data level and the data starts where the data is created versus where the data is modeled in a database someplace else. Again, I think that's a pretty radically different way to think about things. So let me change the conversation a little bit if I might.

Where do you think the pipeline business is, the midstream business is with regards to utilizing this new technology that people are calling Internet of Things? Midstream is the same place downstream, the same place upstream is right now. And I say that because if we started talking to people a year and a half, two years ago, we'd had heard this term, but we were concerned about security, et cetera, because we were looking at security and our current understanding of the issue of security. There was a real slow delay in all of oil and gas.

Everybody equal. The beginning of this year, I can tell you that it went from a black magic strange thing that'll never happen. You know, you could even hear a little frustration of people's voices when you discussed it in regular discussion, you know, in the middle of 2016 to now there's an overall interest because people are sniffing this maybe a technological change that can really deliver some of the things that SCADA promised two, four, five years ago. But we just didn't have the connectivity.

We didn't have the ability to flow the kind of data that was required. We were fighting issues of just pulling a field in an hour of very low level kind of stuff like pressures, temperatures, flow rates, et cetera. And so we're still, I think, a little confused as a group, all of us, all of us together, every segment of oil and gas of how we're going to improve that communication. Because communication is our weak spot, but I see those changes coming at us quite quickly.

So to answer your question, I think midstream is the exact same place as the rest of oil and gases as opposed to, let's say, cities who are putting in Wi-Fi 802.11 everywhere, no big deal. You can hook your cell phone up all over the place. As you and I know, take a little drive off to many different places we could name. You have the same cell connection in the last two hours.

And so how do we pull 802.11 kind of connectivity to the well site? But as soon as that becomes not a problem, then there's the rest of this promise can be delivered. In the meantime, don't throw the baby out of the bathwater. There's a lot of the promise that can be handled on site through edge computers, et cetera.

And I think that's probably how it's going to start for all of us. Well, we'll have local hubs and spots that are doing good until we totally solve the communication side of it. I think my summary is oil and gas is insane, but I guess I have a different view of it a little bit. I don't think that we're ever going to completely solve the communications problem.

And the reason I say that is there's just going to continue to be more and more and more demand for data. And when you're operating a pipeline and you're at an interconnect and that interconnect is down in a canyon and 30 miles from the nearest cell tower, you're going to have communication issues. It's just a given. I'll talk a little bit about what an edge device is.

So simply stated, an edge device is a computer. You can think of it kind of like your cell phone that runs a Windows or iOS or Linux operating system and sits at the very edge of the network right next to the instrumentation. If I were connecting up to a legacy system, it would be sitting right next to the PLC. And it's grabbing that very high rate data and doing things with it at the edge of the network.

So what I think is going to happen is that people are going to start focusing on edge device development. Those edge devices will have applications on them and they'll start doing some kind of intelligent stuff with the data meaning I'm going to use lots of data to do analysis and then I'm going to process that data into something meaningful that I send to the host, which is going to offload some of the communications requirement on the communications infrastructure. That's one guy's theory. And be a fundamental change in security.

Oh, yeah, we haven't even talked about that. That is a huge subject with Internet things because the cost of having the data more highly integrated is I open myself up to more potential security risk. What helps us become more secure is all of a sudden that edge device becomes a quasi-firewall, if you will, because of the old-time machine learning language never leaves the field. It's also going to broaden the data flow through pipeline, if you will, because rather than sending all of that data back every second somewhere else to be computed and then sent back to the field, it'll all be crunched in the field.

But once it's now that you have that capability of crunching the data in the field, you change to a different type of interface. And that interface is written around all the current standards around using the same security apps that your online banking uses. So you've just made everything safe. Instead of Modbus, who is a wonderful protocol, not everybody agrees with me on that, but I can teach anybody, Modbus pretty quickly, but it was written in a time that we didn't even lock our houses when we leave town for a month on vacation.

What did we know about security? So it, you know, and there's the only way you can get there is through encryption and all this other chunk. Well, rather than doing all that, keep Modbus or belongs in the field and move to a higher-level interface that now is delivering relevant information as opposed to a gigabyte of data so you can figure it out somewhere else. So there's some changes that'll come along and do that from both bandwidth requirement as well as high security.

If somebody was trying to learn about Internet of Things and Inter-ustral Internet of Things, try to just get up to speed on what it is and how it works and so forth, where would you direct them to go? That's a good question. There's so many places you can go. And really, right now, you can even Google and learn it from a lot of places, but really which, since we're talking to folks from our industry, you want to look for the industrial Internet of Things, but most of the companies are coming out with tutorials.

I think you're making my point, Dan, and that is that PTC is the biggest automation company you've never heard about, at least for people in the pipeline experience. When you first introduced me to these guys after in Virtual Skip where I was really amazed at the size and scale of the company and the number of things they're doing, but they're really more in the, historically more in the manufacturing space, not so much in the oil and gas space. And I guess that's your job is to help PTC move into the oil and gas and in particular the mid-stream space. That's exactly it.

Let's go back to the beginning of the conversation. My real interest peaks when I see things in technologies that I know play, the interesting thing is all the, you know, for the last couple of decades that we've known each other, as well as a lot of other people that we know we've been working on Skatohost. We know where the problems are with Skatohost. We know the issue of the dead end of data and information.

And so I started finding within this IoT framework the ability to kind of patch together and solve that loss of connectivity, that problem of data exchange, they're finding a way to pull the data together into something relevant, applying analytics for either doing simulation or predictive maintenance, I think you mentioned earlier, and finding ways to use this data in unique methods. And then the other thing that they had was a way to deal with the connected worker. And that could be simply Skato-looking hosts, screens on PCs or delivering the information back to the Skatohost for your operations people or to any of your other systems or even to the point of this augmented reality, which there's a new paper being released right now between Jim Helpleman and the folks at Harvard that's talking about the enterprise being prepared to embrace and look at augmented reality where it's going to fit into the future. Again, that may be a far stretch for a lot of us to think about some type of augmented reality device out in the field so that we can find better ways to do our jobs as a solution.

We can see things that we couldn't see before. So anyway, and all of this technology, I thought, holy smokes, I see the connectivity in oil and gas. I see where it will help our companies quite a bit. And after January 1st of this year, I recognized a lot of our thought leaders are seeing the exact same thing.

And I'm seeing a major shift in our industry. And we will learn how to use this to our best advantage as far as automation people, Skato people. But more than that, more connected within the other departments within the company before midstream production, whatever. I think this is a subject that we can talk about a lot more.

And I think Dan, one of the things that you and I share, I think both you and I would qualify as a bubby geek, meaning we have both a laptop and a hunt and rifle in our pickup truck. This is the kind of thing that while it's kind of new and people are beginning to kind of look at it, what we know is that the stuff that people's thought leaders start thinking is cool or interesting probably is going to have a material impact in our business over the next two years. I certainly see IoT that way. So with that, Dan, thank you very much for joining us and offering your thoughts.

We look forward to having you back. I appreciate it very much. I look forward to coming back after I have a little time in the field and we get some of this technology deployed talking about use cases and what it's done for people, where the rubber meets the road. I look forward to that podcast.

Yeah, that'd be awesome. We will definitely get that on the calendar some point down the road when that makes sense. That's awesome. Well, again, thank you and to all the listeners, thank you for listening to the Pipe Liners podcast.

Thank you Russell. Thank you for listening to this week's episode of the Pipe Liners podcast. I hope you enjoyed the conversation with our guest, Dan Turner and you found it valuable. So just a reminder, you should go and register to win at pipelinerspodcast.com where you can win a nice, stainless, yetty tumbler with a cool Pipe Liners podcast logo right on the side.

All you need to do is visit pipelinerspodcast.com slash win. That's pipelinerspodcast.com slash win the word WIN to enter yourself in the drawing. Again, thanks for listening and we hope to hear from you next week. Or by rating and reviewing the show on iTunes, Google Play or Stitcher.

Thanks for listening to the Pipe Liners podcast.

Frequently asked questions

How long is this episode of Pipeliners Podcast?

This episode is 27 minutes long.

When was this Pipeliners Podcast episode published?

This episode was published on November 9, 2017.

Is there a transcript available for this episode?

Yes, a full transcript is available for this episode. You can read the complete transcript on the episode page.

Can I download this Pipeliners Podcast episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.