Proficy 2025 Webinar Series_Proficy Historian: Hybrid Data Management at Scale | GE Vernova
Hello everyone. Welcome to Proficy 2025, our annual leadership Strategy and Product Launch webinar series. My name is Alexis Murphy and I will be your host today.
On today's webinar, we'll be talking about the many exciting new features Historian 2025 for Cloud and Windows have in store for this year, including enhancements to Cloud scalability, SaaS capability, a Cloud for producer and consumer, security and usability enhancements. And beyond. Before we get into the fun stuff, I want to be sure to mention that today's event may include Forward-Looking statements. The information presented is intended to be an outline of general product direction, and it should not be relied on in making a purchasing decision. Now for some housekeeping.
You should all see an interface with some buttons at the bottom of your screen. They look like the ones on the right side of the slide. Here. Please send any questions you have through that orange chat bubble button through the purple envelope button. You can contact our team.
The blue paperclip button is our most important, as it's where you'll find relevant content and resources related to today's webinar. Through that Orange Person icon, you can connect with today's presenter and senior Product Management leader Brian Johnson. If you need technical assistance. Please reach out through the orange question mark button.
Though most issues can be resolved by just refreshing your browser. Last, please share your feedback with us. We have the checklist button there where you can send us your challenges, your initiatives. We're using this information to really build our products collaboratively with your insights, so we thank you for anything you can pass along. With that, I'd like to introduce today's speaker, Brian. Brian is the Product Manager for Proficy Historian.
Historian Cloud and the future Proficy Data Hub at GE Vernova Proficy Software and Services. He is a certified Agile Product Owner and has worked in product development and product management for a decade. He has a passion for driving digital transformation and new technology adoption, with a focus on cloud technologies. Technology as a catalyst for growth and changes an area he finds particularly interesting.
Brian has an undergraduate degree from Harvard University and Certificate in Digital Transformation from Cornell University. With that, I'd like to, bring Brian in to take us through today's presentation. Take it away, Brian. All right. Hey, everybody.
Thank you, Alexis, for that really great intro. It's great to see everybody here today and be able to share what's new within Historian. I think we've made a lot of great updates for 2025.
And I think by the end of this afternoon, everyone will be really excited to, to see what's going on and to look at the future of where we're going with not only the Proficy Portfolio, but but also Proficy Historian. So to start off and again, make sense to talk about what is going on within the portfolio, right. What are the key things that we're looking to do.
And you know, where have we gotten ourselves in the last year. Right. You can see that where Gartner Magic Quadrant leader, and then where we really focusing right. Plant to enterprise scale Historian is one of those things that really focuses here. Right. Being able to get your data from anywhere that it lives, or where it's created up to a centralized solution. And we'll talk a lot about that today during this, this time period.
Effective operations to anywhere data, insights to transformation. This is really super important. And realistically, one of the things that I constantly think about when I'm thinking about Historian is how do I help you as our customer, get your data from where it's created to and actual insight that you can use to drive your business forward? And this is super important to me, as I think it is to all of you as well. And then supporting sustainability goals and sustainability is becoming a much more prevalent, everyday factor in our lives. And. Right.
And it's a great thing to support and to understand how we can make our business more green and and how we can really help the environment as we as we go forward here within time. So Proficy is a fully functional portfolio across a manufacturing operation. So something deeply to consider. Plant floor to cloud through the enterprise right.
This is where the hybrid portion of Historian comes from. When we think about how the portfolio is is actioning either hybrid or cloud direct? Many of our tools, whether it's production automation, are more software with Smart Factory or plant that's on prem, historians specifically. And then our AI and also illusions, whether it's ops hub or, seasons, really, we're all coming on board with the cloud messaging and, and giving you as a customer the option of where you would like your data to live, whether it's in a safe environment or, a cloud environment that you own, or even if you want to keep some of your data on prem, you have the availability to do that with prophecy. And then to move a portion of it to the cloud to leverage both cost savings and, throughput and collaboration. And having teams across the globe being able to work on the same data to to leverage not really good insights from it. So really very exciting time to look at the Proficy Portfolio and to see what each of these tools will be able to bring to your environment, whether you're a current Proficy user of individual tools and need to look at others, or if you have the entire suite already.
I first of all thank you for for having the whole suite. But also we we really can leverage each tool, in, in conjunction with the others to make it a much better experience for you as a user. So really exciting things coming from the Proficy Portfolio in its entirety in 2025 and beyond. All right. So when I think about why folks need a Historian or what is the use case for a historian, we see a lot of different trends and challenges that are happening in the environment. And and as I'm talking to customers and working across different industry segments or, or looking at different, sections of the manufacturing industry, a lot of things become apparent, right? You can see pretty much everybody thinks that it's a great idea that we need to have analytics driven off of data that we collect.
Right? We can collect a lot of data. And Historian is especially great at that. We'll take a look in a few slides. It. What are the capabilities that we're delivering and how are we the most performant Historian on the market. But what do we do with that data is the question.
You can see 3% of data and analyzed. That's not very much at least 97% out there not being dealt with, 9% unstructured or needs interpretation. Right. How do we know what's going on there? And that's where we can look at things like unified namespace or directory services or data fabric to be able to give the structure into that data. Luckily, Historian is inbuilt with these capabilities already, so it's not something that you need to bring to the table. Additionally, if you're starting to use historian or if you're looking at Proficy Historian for a future acquisition so we can bring the structure to the data.
We have a plant model built in already. But there will be future editions for that. And as Alexis alluded to, we have a new product called the Data Hub, which will add a lot to this sort of data structure. It's really very exciting. And you'll hear more about it in the coming days. And then 40 to 80% of the data is unused.
What? Why is it unused, you might say. Well, it's because of this, right? None of it's tagged or analyzed. A very small part of it needs interpretation. We know it's there, but we don't know what it's telling us. Could there be some really great gems of information in here? Yes.
Could there be more here? Yes, absolutely. But how do we get there? And that's really the question. And so when I think in terms of like historian, we have really fast, very efficient data storage. But my goal is to be able to get all of your data out to an analytic, whether it's from our own portfolio with operations over or otherwise, out into one that you're already using today. We have the capability to do that. And I want, at the end of the day, for you as a customer, to get all of the insight possible from your data.
Digitization seems to be central to these outcomes. You know, when when Alexis gave my intro, she had talked about how I have a specialization in digital transformation, and I think that's a challenge that all of us are facing on a day to day basis. Right? We are we're moving at the speed of technology, and that's as fast as we can as it comes to comes to fruition. We should be adopting it, or at least looking into how do we better ourselves with technology. Right? The key pieces of the puzzle that we see, like data governance, for example. How do you do that? Well, you need to leverage different tools, right? If you are currently keeping track of data points or information on spreadsheets, you can move to a tool like a traditional industrial historian, like Proficy Historian to give you that digitization.
Right. Bring things up. Give the opportunity for folks across silos to work on that data. Make it democratized so that it's not just one person's data or one group's data.
Right? Maybe it's useful for many folks. And as we bring on different things like new security, infrastructure upgrades or change management and employee training, these are all the things that we should consider right? When you think of bringing your data either to the cloud or to a digital solution, security should be top of mind. And with Proficy Historian, we're increasing every year our security capability, and we leverage an internal red team to do penetration testing against all of the most modern threats to limit our attack surface, and to make sure that at the end of the day, only the folks that need to have access to your data have that access. So this is super important to me as well to make sure that, you know, folks that are using history and are able to sleep at night, not wondering if there are bad actors being able to access their data, because the answer is they're not able to. We continuously test and as new and different exploits come available or are made known to us, we test and we we issue patches as best as possible.
So very, very important. The security measure change management and employee training. Right. We have put a lot of work in the last few years and you'll see today a lot more work happening.
And this will be a consistent feature of historians that we're adding and improving to the UI and UX, because there's an increasing expectation of our customers that it should be easy to use, and then it should be intuitive. And and as newer and younger folks are coming into the workforce, I think it's exceedingly important that we have these things available for them. Right. If we think of a a TikTok or Instagram like UI experience, I want to deliver that for them and you'll see changes coming to our UX. We've done a lot of work this year and we'll continue to do so. So a lot of these things and as you're considering a move to a digital solution, these are the pieces of the puzzle that you as a customer will need to to address as well.
And we stand ready to help you do that with prophecy. Historian. You might say, Brian, that's that's really that's awesome. We're we're moving in that direction as a, as a company or as an organization. We, we really like what you're saying, and it resonates with us. But
what kind of challenges and barriers are we facing or what are you seeing in the environment. So when I talk to analyst firms or or other folks in the marketplace or I'm, you know, and all of my customers as well, we see a few different things come up frame. Data quality is a big one. I've talked a lot now about analytics. And how do we get to that point where you have the most data, pushing into your analytics and being able to get that fullest picture of what's going on. But to get there, data quality is a primary thing we need to look at, right? We need to know what it is. We need to make sure it's happening there.
Historian has features to make sure that the data you're getting is only the best quality data. And if you're not getting the best quality data, you have ways to triage that and to make sure that it's happening. Resistance to change. We're talking about digitization.
That's that's a huge change for some organizations or for some folks within organizations. And we'll see this that, you know, I've often heard we've always done it that way. Now, is that a good solution? Maybe not.
Perhaps we're looking to change the way we're doing things and moving in a direction of bringing in a software vendor like prophecy to make operations smoother for you to to drive your organization and operations into the future. Is is really super important. Missing data.
This teams up with data quality. So there are a lot of things there. Cybersecurity risk. We talk about data silos.
We're going to talk about on a side in a few moments. And manual inputs, things like user error. Right. How many of us have ever been working on a really long stream of data, or making a really complex list and having to write it down and we miss one data point, or we miss one aspect of that list, and we have when we double check, we found out, oh, we missed. We have to go back and figure out where the problem was.
Right? If we're limiting manual inputs, we get a much better result. And using the collectors that are automatically collecting from different data sources, whether it's mQTT or this year, Kafka, with our producer and consumer, we limit the amount of manual input that you have to do as a customer or as a functionary within the manufacturing environment. And by limiting the manual inputs, we make it much easier to have better data quality, to break down the cybersecurity risk, to have less missing data. It's really a part of all of it.
And then all of these other things compliance, scalability, outdated infrastructure, all of these things are solved by transforming bringing digitization into your process using a tool like Proficy Historian that's purpose built to make sure that all of these things are taken care of from the default. So you don't have to think about it as a as a customer of the system. So really very important stuff that we're thinking about here and trying to make it as easy as possible for our customers to be able to come in and solve a lot of problems with the fastest time to value on the market, which is really super important.
Siloed context. Right. We alluded to this in the last slide, but it's one of those things that it happens even if we're not meaning for it to happen. Right. Groups work independently. I've worked in several different roles and product over my, my career, and I've seen that time and time again where individual groups, even if they sit adjacent to one another on the same floor, they might have different representations of the same data. Because what's important to Group A is not exactly the same as what's important to group B.
How do we drive that out of the process? Right. Lack of production context need to know business context. It's different for everybody, right? If you're a quality engineer you need different data than a production planner. It's it's a fact of the operation and the business that we're in. But how do we drive that down? How do we break down those silos, being able to have a matrix, that Proficy Historian provides where you can have data kept at the plant level, you're then able to bring data up to the enterprise level, right. What folks up here, enterprise planner and point manager, IT engineer, they all need different data or different slices of the same data that makes sense to them.
That's presented in a format that they understand. And we can do that by being able to collect as much data as possible, but something like Proficy Historian and then to drive it through to the enterprise level, where executives in the C-suite CIO, for example, CEO, CTO, they will all have a view that they're looking for to understand that they're collecting the right data and that it means the most of them, that they can accomplish the necessary parts of their role because they have the data that they need. And this is super important because you can do this all with one tool. You don't need one tool for the plant, one tool for the enterprise. You can do all of this with Proficy historian. So it's it's really a powerful tool.
If you're looking at sort of simplifying or flattening your architecture. It's a tool that we can bring to bear there right now. When you think about translation of business versus production situational, but if the data is there not a problem, you can look at it as much as you need. And, you know, we have the tools, like I said before, operations, to give a view to everybody that needs it.
And if you can be different on a use case by case basis. So really something to investigate. And if today you're facing challenges with sort of complicated architecture or a whole bunch of different tools that maybe don't work together super well, we can use Proficy Historian to solve those problems and to flatten the architecture and to give you a single interface to work through. So not only does it lessen your training burden, but it makes everything worthwhile. And then at that point, you're able to work with a single vendor, which I think is super important as well.
Inconsistent configurations. This feeds back to the one of those first slides that we looked at, right? Challenges and barriers. Where does the data come from? Site 1st May have the same information that's like two and three, maybe the same as site one. But if they're collecting the same data and it's done by different admins on different days, perhaps they're named different things, right? But the Historian data stored as tags and each tag is named.
But that name doesn't have to be the same at site one as it is at site two, as it is a site three, and that can cause a problem, but we're introducing tools to make sure that that problem goes away. You can see as the different sources of data, whether it's sober SQL or our Rest API endpoints or otherwise bring the data in. We're going to harmonize it across all of the plants with an historian to make sure that we're able to give you the best possible view, and that you have plant models and different things available so that you can feed. If site one is your first site, and you build site to you, or acquire site to, you're able to bring that in and say, okay, we have a model already, we can just deploy it. We know what's there.
We know the hardware that's going to be in the plant. We know the data points we need to collect. Let's just make it simple and then from there, right, it covers your old sources. It covers your it sources.
It makes all of the things work better together and make it much simpler for you as a customer to rationalize your data footprint and to understand what's going on there, which I think is really, really important. And you can see across the number of connections that we have, these are just a few, right? These are just the common protocols, whether it's coming from an ERP or a PLM system. Do you need windchill grants? Maybe. Can we bring it all together? Yes. You know warehouse management system.
This is super important to some folks. If you need to ship a lot of things in a hurry, it's important to have all this data. Right. And all of this ties back to what's going on in your plant systems. And we can aggregate it all together in the cloud or on prem, on windows or wherever you need it to be.
With a so it's super important to think of these things and to understand what your data footprint looks like. What systems do you need to bring together right nonstandard and legacy sources? I think we all have a little bit of legacy in our environment, but it's important to be able to rationalize it and bring it to the future and make it as efficient as possible for you to understand where the data is coming from or what it's telling you. So just one way that we're able to work through, if you're using prophecy according to the drive this out of your process, right. Let's make inconsistent consistent. And at that point we get a much better result. All right.
The road to transformation. So Proficy Historian only really excels or is applicable to this sort of section. Here. These first two pieces. So data collection and consolidation has been on the market for 35 or 40 years at this point.
It's been used in many, many industries, whether that's traditional manufacturing or discrete manufacturing or process manufacturing or grid applications. Right. We have a lot of customers in the energy generation space or the energy transmission space. We apply to all those use cases in a very specific format. And it's because of the way that we're able to collect the data and consolidated, which as we go forward in time here, we're adding new and different ways to do that, right.
We have a system of collectors that are available. There's there's over 20 at this point, and you can use classic protocols like old ADB or others. We have our platform, IGS, that connects to any of the head units on the market.
And lets you bring in data from your PCs across hundreds of protocols, or you can use newer things like M2. You know, last year we became fully sparkplug B compliant. This year we're moving forward with an empty producer or a publisher so that you can take your data in that format and get it out of history and, and send it to another tool to analyze it or to to get more functionality out of it.
Right. We're adding our Kafka producer and consumer because there's been a demand for that sort of high speed data interface. And then the pub sub model that we get with Kafka so that you're able to look at different topics of data and make sure that you're only alerted to the ones that you really care about in your function. You don't have to sort through all of the different tag values within history. So a lot of different things there. Consolidation.
This is a good application for a Historian in the cloud. When you think about where do we keep our data, how much is it going to cost us to keep it there? Are we using it or do we not need it right away? Right. If you're making these considerations, cloud is an excellent option to take because we can keep a little bit of data close by.
If you're in a regulated industry or otherwise. If you want a month to month, six months, a year of data on your factory floor, you can keep it there and send the rest of your your data five, ten, 15, 20 years up to the cloud where you get low cost, very efficient storage. Right? So and then you're able to scale as necessary. You can grow, you can shrink if you have a facility that is sold, for example, and you need to send all those records from Historian to the new owner.
Not a problem. We can do that. So between data collection and consolidation and contextualization, this is where Historian will excel. We have other portfolio tools that we talked about at the beginning where analysis and analytics with our seasons platform visualization and control between our data seasons and operations of and then information broadcast, it's all out there, right? We can get from collection to information broadcast, send the data out and the insights to people who need to know. Right. Seamless transfer and information to and from the plant for an enterprise systems.
The data is there. We need to send it someplace else to give it value. So we're able to do that within the Proficy Portfolio. Really very cool. So we're breaking silos, building a data model, making informed decisions.
Right. Who wouldn't want more information at the time of making a decision? Right. We want to be as as informed as possible. Sometimes it's important to make the best decisions, but other times it's important to consider every possible element before making a decision with Historian on the other tools and prophecy. We make it so that you can make these decisions just like that, right? And then increase situational awareness and interoperability.
Super, super important concepts that we support with this awesome. All right. So you may be saying Brian, this is all really super exciting.
Where do we go from here. Right. We're seeing a ton of information come in different concepts within digital transformation and data management happening right now. What should we care about from our customer perspective. Right. What are you seeing from the as the product manager of Proficy Historian, we're seeing all the things hybrid cloud, right.
One of the key concepts for 2025, according to CIO magazine, is a cloud first approach for your digital footprint. Maybe that's not right for everybody. It's right for some of us.
But in the absence of that, you could embrace a hybrid cloud approach where, like I just said, you're able to keep some data on prem and you send the rest up to the cloud. The storing is specifically architected to do that, and it's becoming more so as we go forward. You'll see different pieces of the puzzle, you know, in a future slide here of what we're doing on the cloud for 2025. And it's becoming a stronger and stronger product. And the best part is you get the same Historian that you know and love, whether it's on the cloud or on prem.
So there's no loss of functionality. And it's really super cool because it gives you a lot more flexibility, and you can choose when and where to access it. And once you're on cloud, it makes it very easy for teams across the world to collaborate and make sure overhead, they're very, very low, which is really very cool. Centralized data lakes. More and more of us are delving into data science hiring teams, data scientists, prompt producers, different folks that are looking at the challenges of having a ton of data. How do we bring it together? Right.
Protocols within Proficy 2025, like Kafka, will give us the ability to send information to data lakes. We also have Parquet file export that's coming to our windows platform, and it's been on cloud for a few years now where you have very efficient file management storage that you can send in the data lakes and leverage your time series data on top of your Kronos data or your ERP data, or anywhere else. It's coming from quality systems. You can bring it all together and and it makes it much better because then you have a much more informed decision making process insights, right? Making the data available to any tool that you need to to be able to build the models that you need to build to understand what's going on in your environment, or to predict where a future might be right. Are you going to have downtime? What are the changes like in the grid space? Looking at green energy specifically one.
What is the wind speed? Will we be able to generate enough megawatts from this wind farm to understand what's there? Right. We have customers doing that today with Historian looking at, you know, how do they predict for the future using the data that they have today and then bringing in other sources like weather data and different things? It's really, really cool and really exciting to see that that's the direction that folks are taking it. Security.
I think we've talked about that already, really super important, but making sure that we're always on the forefront of delivering best in class security is one thing that's super important to me. And then low-code no code solutions. Training burden on new solutions is extremely hard, and I don't think anyone should have to become a front end developer to be able to get the insight they need to get from their data, right. We should all be able to build a metric, an easy to use tool.
We're lucky to have operations hub that makes this possible for us. So you can connect your Historian data and then be able to send it to Operations Hub. Click and drag move metrics around and build a really, really informational, really interactive, very easy to understand dashboard that can be easily changed for every level of the organization. And it's mobile compliant. So you can carry around in your pocket and look at it whenever you need to. It's really, really super cool what we're doing within the portfolio and how Historian is able to leverage these capabilities to give you that sort of best in class experience, where you get the best out of your data because you're able to store a ton of it, store it where you need to act, and interact with it as you need to, and then get the information out that you need to get out of it.
It's super exciting. And I think as we talk about the newer features in 2025, I think everyone will be excited with me. Hopefully. So this is sort of an overview. Let's say, okay, we think there's promise in properties or in Brian, but where does it sit within the portfolio? How does it help me if I'm already a Proficy customer for one of our automation products, Escada? I think for simplicity, if you're already in any customer, maybe you need a historian. We're really central to the portfolio, and you can see we work across the levels, right? Whether it's up into cloud, we help you bridge OT and IoT networks.
We have the data where we have it, and then it works with all the other products. Right. We can get it into a data lake. We can send it to analytic tools. We can leverage other tools, schedule our new Proficy product, Proficy seasons. We've talked about that being able to drive analytics and move us in the direction of a closed loop control type interface, which is really, really super cool. But Historian is the heart of the portfolio, and that we store all of the data created by the other products and give you a place to leverage it.
So coming off of the platform into other products and for sure into historian, which when you start to think about it, if you want to use any of the other Proficy products, why wouldn't you use Rapids Historian? We're built to work with the other tools. We do it natively. All of our connections are very simple. You don't have to go through any extra technical overhead or, confusing protocol setup to make it work, right? Once you've got one Proficy products, whether it's Historian, you can add others, or if you've got others, you can easily bring Historian into the puzzle and start to flesh out your environment and have that full service experience, which is really very exciting.
Cloud Historian this is where we start to see how is the data kept in a hybrid format? What do we get when we want? When we use a high performance, whether we use cloud or we use on prem or we use a hybrid, you can see Historian works on site. You can have immense data flowing in other external data sources. I mean, we we work with paid Historian or even historian or other historians on the market or any third party source. We have ways to bring the data in. So you're not you're not necessarily have to rip and replace when using Historian for for prophecy, you're able to make it additive to what's going on in your world today. You can do single or multi-site industrial, right? This is one example of a plant, but site two could have the same site three could have the same site four could have the same.
And then you're always able to keep it on sync. You can send it up to the cloud. You can move the data out using the parquet files that I mentioned before. To a data scientist.
And one of the cool parts of once you're in the cloud right today, where the only solution for a Historian that's able to be natively deployed on any cloud infrastructure, no, no one else has this capability, right? If you're already a cloud user with AWS, not only do you buy down your requirements for using their platform, but we deploy natively from the marketplace. So you click one button, we start to deploy within an hour. The Historian is fully deployed at the end. Within the time of getting a cup of coffee. Your Historian deploys, you're then able to add collectors and start to move forward. And you get your your data and bring it into history.
Other things that you get when you move to the cloud. Zero downtime upgrades. How important is this for us when you think about taking a facility offline, or being able to have the time and space to do these upgrades right? We have customers where it takes years to do that because of the footprint that they're working in and the fact that they have to shut down lines and every time a line goes down, we know it costs money, it cost time, and it's hard. But with cloud, that's no longer a problem. Availability and always on, right? If you have access to the internet when you're using a cloud service, whether it's AWS or Microsoft Azure, it's always there for you. As long as you have a device in your pocket that will connect to the internet, you have access to your data.
And it's a it's a concept that many of us use today. If you use Gmail or Apple Mail, those things aren't stored on device. Mostly.
Some of it is, but a lot of it reaches up to their cloud footprint for for Google or the Apple ecosystem. And and it's the same with your manufacturing data, right? It'll move to the cloud. It will be there. It's very, very secure. You get replication by default with cloud where your data will be put in two places automatically.
So if there's a disaster, the disaster recovery plan is already there. It's easy to be action. So you always have access to the data and then multi-site like we show here. If your footprint has multiple facilities, using Historian on Cloud is an easy option to say, well, we'd like to get the best out of all of our facilities and be able to get one centralized sort of view of what's going on down here. And it's easy to do that with the cloud, right? Aggregation across the universe.
That's what we're talking about. And then scalability. We have a feature coming in Q2 of this year that will re-architect how the historian, archiver and collector relationship happens to make sure that you get as much Historian as you need, when you need it, and as fast as you need it to be, which is really super exciting. So a lot of development coming in the cloud space worlds.
And I think it's really super exciting to think where we can go on top of what we've done today. So really driving down limitations when it comes to your industrial data and how we can manage it. Right. This should be very exciting for many folks on this call and being able to leverage it. Please reach out to me after this if you need more information or are looking for sort of more, more or less benefits or for a complete architecture, we can definitely dig in. I look forward to it.
So now that we've covered sort of the general capabilities of the historian, where does it go? Where do we go from here? Right. Historian 2025, the latest release being released for windows, the end of Q1 cloud works a little differently, where we will deliver quarterly updates for you because of the the availability of the zero downtime upgrade, we can deliver much more finite packs of of functionality within the cloud. Historian. And because of the way that it's it's uses a Kubernetes container to deploy. We don't need you to shut down your facility.
You can just deploy the newest feature pack every quarter, and the containers handle all of the switchover. So from a user benefit perspective, they'll never know that you've done an upgrade, except that they'll get new and different functionality and and be able to leverage more and more capability. So really very exciting there. So you can see security and encryption enhancement. Security is always top of mind when we think about where we need to go with the story and what's important. So keeping it to that, making sure that we're always pushing forward encryption in today's day and age is very, very important.
And we're leveraging the newest standards to make sure that that happens. Data hub support. By the end of this year, we'll have support for our new product called Data Hub, where you'll be able to leverage that data fabric and unified namespace and other features to aggregate your data from the plant floor up to a centralized solution. And at the end of the day, you won't have any, necessity to understand where the data came from, will be able to serve you your data from any of the products, because we're using the data model and and making it much easier for you to interact, for the folks that are experienced with Pi's asset framework, it's a very similar development to that. So the Proficy answer there.
Kafka mQTT a new ways to interact with different protocols. Kafka is very cool because it's very high speed data. It has a storage function within the broker. It functions very similar to me in that it leverages a broker to to bring data and move it around, but it's very fast. It gives you that pub sub model so you can publish to the the Kafka interface.
You can subscribe to different topics of data within Kafka, and then you're able to leverage the speed that it brings. It's much faster than many other collectors that we have UX enhancements. We've done a lot of work with our team to make sure that specifically, our configuration hub is the easiest to use on the market, and that will continue to deliver new and different features for you, like canned reports or saved queries or other things in in line with ease of use. Right? Trying to limit repetitive tasks.
If you're coming in on a Monday morning and you're the admin for story, and I don't want you to have to run through a whole bunch of queries to check what's going on, or to look at a whole bunch of trends to make sure that tags are collecting, that you're not getting bad data from over the weekend, that sort of thing. I want it to be as easy to interact with as possible, and to give you the most value in your day, where you can quickly look, understand what's going on, and move on to better value, to Historian is becoming a SAP solution. So by Q3, we will deliver our cloud based Historian on a GE managed tenant very similar to what we have with our smart factory cloud solution for folks that are similar for are familiar, they're you won't have to work with infrastructure anymore.
We'll get you out of that game. We'll manage all the infrastructure for you. You will get the benefit of the analytics in the data storage. So it will be based on AWS cloud. It will be in a G on tenant and you want to longer have to manage your hardware.
You'll sign up with us and you'll get all of the Historian that you know and love without the overhead or burden of having to order new hardware or maintain hardware or patch operating systems or anything like that. So this is a giant win. And then like we talked about scalability on cloud. So when you combine both of these we'll have one of the most powerful historians on the market in terms of scalability. What we can deliver for you as a customer and and where you can take your data to get insights into to move forward. Really, really super exciting for 25.
Now this is just the big key features. There are quite a few more that it would take me all day to go through, but if folks are out there want to have a conversation, please reach out to me and we can go through the entire feature list. I think it's really a very exciting release for us, and it's really setting us up for the future in an excellent way. And because of what we've built in here, there's really, really great customer benefit, and I think you'll see the difference when you start to use it. So please sign up for your story in 2025.
I want to give a few examples of functionality here so that we can understand what we're talking about, right? Kendra reports. If you're familiar with our configure up, up or configure platform, this is what it looks like. It is the most modern interface we have based off of HTML5. For folks that maybe are using the old web admin today or even better, the trend client, this is much cooler, much easier to use, much more performant. And it gives you multiple different ways to interact with data. You can see on the left hand side, you're able to have all of your historian data alarms and events configuration templates.
This is a list that we added last year. We're continuing to enhance that. You can see canned reports now current values. So hopefully the tags tags that maybe aren't producing any data. This would be an important one. No no data tags.
Collect your data quality. Very high quality data is important. And being able to have the highest quality data at the click of a button and understanding where your gaps are, it makes it much easier to try scoring. We're also coming forward with, proactive notifications that will be based off of these sort of tag tag, reports so that you're no longer reactive. As an admin.
You can be proactive, you can understand that there's an issue and you can start to drive, corrective action before other folks downstream from in the process understand that there's an issue. So you can see all of it here available to you. Whether your Historian model, all your collectors, your tags, your data source, you can manage your entire historical system from this one screen, and it adds across the top to make sure that you can follow the breadcrumb trail back of where you've been and what you've looked at it. It works really, really well, and it makes working with Historian much easier. And in my opinion, having worked through all the different systems and different ways to interact with historians, this is my favorite.
So it's really a great, usability boost for, for our customers. All right. You can see the interface for our Kafka producer and consumer.
It looks very similar to what we just saw because it's based in configure. So as we go forward, we'll continue to add new tools and capabilities that can be managed through configure. Because centralization I think is important. Right. You don't want to have to go to multiple different guises to make sure that you can do the different things. With an historian, we're giving you one.
You can stay there, but you can see you're able to add Kafka details. So it's got two topics. And here map with the schema. So you're able to say, okay, within my historian I've identified where I need to go. I'm able to then come in and look at what attributes read, write Historian fields that come off of the different tag values. Substation, device type, device ID, timestamp.
Very important within historical quality. Very important in the process. And you can see we represent it in the Avro schema. So Avro is the most popular schema that we've researched or understood with Kafka. So it's the one we've chosen to to utilize.
I would look for any feedback on that as well. If folks are looking for new or different things, I'm always open to new suggestions, but this will be the first implementation of the Kafka consumer and producer, and it really gives you that opportunity to have very, very high speed data transfer, to publish and subscribe to different options. So the producer is a publisher in sort of classic terminology. The consumer is what we would consider a collector. We're just using the Kafka nomenclature here. So this is a really super awesome development in terms of historian and your ability to choose the way that you interact with your data or the way that you collect your data.
Right. I want to give you as many options as possible as a customer. And this is another great one. So we've heard a good amount of customer demand, customer demand for this. And the folks that we've shown it to so far in, in demos before the release have been really excited with the, the possibility to work with the data and to get new and different things with it. So really very exciting. There.
Grafana is another tool for data analysis. You can see here. It gives you a very fast way to look at data as well. Right. Complex calculations are supported by Python. I think we've had customers come recently where we're looking at multiple levels of calculation, to derive a result from his Orien data model, that future looking or otherwise, it's it's become very important to have an option for customers that are looking to do very, very advanced analytics.
Within Historian itself, you can see both on prem and cloud, on the fly calculation tags created in sort sorted Historian for faster performance. And then it's a plugin so it natively streams the historian, the data from Historian into the Grafana interface. It's super cool data visualization with streaming data and alert mechanism. This is very cool. So streaming data means we can work in real time. So we're no longer just historical.
If we're using Grafana, we are an actual real time system and then alerting if something goes away. We didn't expect to. We're able to understand what's going on there, right. You can see here this is a pretty simple trend. I think anyone who's worked with Historian has seen a trend before. But what will you do here? If you're outside of a deadman, you'll get notified if something stops.
You'll get notified if there's any issue outside of the sort of where you've defined. For the data to flow, you'll be notified. It's really very impressive what the team has done. And this is just another tool that we can leverage in the Historian environment to make sure that we're understanding what the data is telling us.
And as we see more and more complex calculations coming from our customers, it gives us a good way to give you an easy way to get the data that you need or the insights that you're looking to get from your data. So really very important, very cool. All right. And you can see here please scan this QR code. This will be my last slide. So you can scan the QR code here and and bring you into our website to start to talk about digital transformation.
And I also look forward to having a conversation with everybody here and, and understanding the challenges that you're facing or different things that are going on where we can help. Or if you have new or different ideas for historian, please feel free to message me. So thank you very much.
2025-03-17 05:43
