Logan Stinger: Welcome everybody to this week's Redis weekly webinar.
Logan Stinger: We're so glad that you get to join us, whether you're watching us now or later on demand. Thank you for taking the time out of your day to learn a little bit more about Red List integrations. I'm joined here today by Logan singer. He's our CTO. He literally does 5 million things here at Red List from managing the complete architecture of our products, spearheading our AI stuff and
Logan Stinger: also helping me when my computer shows me weird messages that I don't understand. Just this morning he was on a call, and he helped me
Logan Stinger: with computer things. So literally, he sees the whole scope. Everything tech. Logan is literally our genius. So thank you for being here today. Logan. Thanks for having me Ray.
Logan Stinger: So Logan's gonna talk a little bit about our integration. So I'm going to pass it over to him and Logan, I'll let you take it away alright. Thank you.
Logan Stinger: Yeah. I'm excited to be able to share the integration capabilities with you. That red list has
Logan Stinger: 1st off. Like to talk a little bit about
Logan Stinger: why it's important. We know that
Logan Stinger: many of the organizations that we work with are, you know, large enterprises that have existing erp systems or are already connected to IoT devices, sensors, other things within their facilities that are providing them insights, and as we.
Logan Stinger: as we scale our facilities and our operations, we tend to start accruing more and more software systems that we need to look into to investigate. Why, we're seeing certain alerts or problems, or simply just to track work.
Logan Stinger: time off requests there. There's a lot of needs to be able to coordinate and consolidate all of that data, and red list tries to simplify your. You know your daily work by aggregating all of those different systems into a single point of record, to give you a holistic view of your asset health.
Logan Stinger: And really, that's what we're striving for at Red List, just to make sure that we we help you keep your assets healthy, and the best way to do that is to give you a complete picture of everything that might be affecting your assets.
Logan Stinger: We have several types of integrations that are available to us.
Logan Stinger: Out of the box, though the the basic type is IoT data where we're gathering information sent from sensors. This would be vibration temperature tank fill levels as well as several other types of integrate indicators that you may be getting from your devices.
Logan Stinger: We also can integrate with Erp Cms systems as well as accounting software
Logan Stinger: within red list, we can track the the products used on a given work order. The cost of those products, the amount of time spent by certain employees doing certain activities. All of that's important to feed back to your Erps and accounting software for billing purposes
Logan Stinger: as well as scheduling purposes. You know, if we can see that a particular route or set of work in actually took your your employees 4 h where you typically have that scheduled for 2 h or 8 h, we can start giving you recommendations on how to adjust that to properly schedule and maximize your efficiency.
Logan Stinger: We also integrate with oil analysis labs.
Logan Stinger: This is important to again give you that holistic view of of assets that have oil health.
Logan Stinger: And as you're pulling those samples and sending them off to your oil analysis labs, we can stream that data right into red list
Logan Stinger: and automatically trigger actions based off of the values that you see there.
Logan Stinger: So why do we have these different integrations? I
Logan Stinger: touched on that briefly at the beginning. But I'd like to.
Logan Stinger: I could go a little more in depth when when we're talking asset health
Logan Stinger: it's important to be able to to
Logan Stinger: see all the data points in one screen and redlist gives us the the ability to view and our our whole facility. In a single screen we can build out an asset map. Lay out all of our assets on that asset map.
Logan Stinger: link the the integrations to our asset health and have them trigger, asset health events, and then you can quickly look at your your asset map and see you know your little red and green throughout your facility, and then drill into them to see what? What is affecting that asset? Health, whether you've got overdue work orders.
Logan Stinger: regularly scheduled activities that that aren't getting completed on time, or IoT devices or other 3rd party party systems that are just letting you know that there's there's issues with your assets
Logan Stinger: and having that all in one place just makes it easier for you to
Logan Stinger: schedule the needed work to get things fixed helps you avoid costly shutdowns and and lets you focus on what truly matters. And that's your expertise in maintaining this equipment rather than hunting down and and trying to figure out what each of these different systems are telling you
Logan Stinger: from a single point of view.
Logan Stinger: also just helps avoid double entry. You know, Lot, we've ran into lots of customers who currently have different systems that they perform work in one system, and then they have to go type in what they did into another system. And we we want to avoid that. We want to make make
Logan Stinger: the job as easy as possible for each of your employees, so that they do not have to fight with the tools.
Logan Stinger: So we strive to make integrations that serve you.
Logan Stinger: I mentioned that we have some that are just out of the box. IoT data is pretty straightforward, you know whether it's a push from your IoT provider or a pull from red list.
Logan Stinger: We're simply collecting data, dumping it into the red list system, letting our our AI tools analyze that as well as letting you configure the alerts and notifications that you'd like to receive, and the work that you'd like to be performed when those those actions. When when that data comes into the system.
Logan Stinger: oil analysis data is very similar. There's not a lot of
Logan Stinger: user feedback that we need when you tell us who your oil analysis provider is. We simply connect to their Apis pull in the data and you get to see that oil analysis report that you're used to seeing right inside of Red List with a little bit
Logan Stinger: more dynamic flair to it. You get longer history. You get to drill in and and see Indi. Individual points over time kind of see trend lines. And and again, it's pretty straightforward to build. Not a lot of of user communication that's needed
Logan Stinger: erps, Cmms's and accounting software, on the other hand, is a a bit more complicated.
Logan Stinger: We have some out of the box
Logan Stinger: workflows that get most companies, 80% of the way there, you simply click, connect, and and turn it on. And certain data fields from red list will flow over to your sap environment. However, we've we found that most sap environments are configured a little bit differently. Different custom fields, different data stored in in non standard fields. And we.
Logan Stinger: we work with you to make sure that integration is optimized for your data needs and and business workflow. And there's no one integration that's going to fit every one of our customers.
Logan Stinger: And so for for those larger integrations, there's usually just additional development time where we work with you and your it teams to get that set up and working the way you need it to. Very much a a custom integration for you at at that point.
Logan Stinger: We wanna make sure that we do that as efficiently as possible as I mentioned, and out of the box integration can be up and running as in as little as 3 min, probably less. In some cases the the majority of that time is going to be getting the Api key from your provider.
Logan Stinger: For these IoT devices
Logan Stinger: or oil analysis labs. Typically, that's all you need is to reach out to them. They'll provide you with an Api key. Some of them. Just use your credentials that you would use to log into their site. You can. You can just plug those in the red list. We'll show that here in a little bit.
Logan Stinger: But again, those are those are type. In that Api Ikey hit, connect, and your your data is flowing.
Logan Stinger: However, those larger integrations can be much more complex. As I mentioned, it did take us 3 years to create an integration to an Erp system for one of our customers, and that's not a success story. Nor is it standard. But there's a lot of reasons for why that that happened. And number one. It really is just
Logan Stinger: the the buy in at all levels of your organization. Oftentimes you've got a business department who really wants
Logan Stinger: a new tool red list, for example. But in order to be valuable. They want red list integrated with their Erp system.
Logan Stinger: which we can do. And so we, you know, we, we begin this process of getting this integration set up for them to find out that their I/O that their It team, has different initiatives for the year, and they really haven't slated time to do that integration and to help with the work. And so the turnaround time becomes very, very time consuming. You know, we may send an email asking clarification or questions about something.
Logan Stinger: And it it may take several weeks before we get a response. And in this case, that's that's what happened. They were. They were working with a 3rd party development team that also had a lot of other projects. They were only
Logan Stinger: only hiring them for certain days of the week to do this project, and depending on our timeline and their timeline things, just didn't always match up. And so there was just this lengthy turnaround time to get that set up.
Logan Stinger: It was very disappointing for all parties. I mean.
Logan Stinger: they're happy now it's set up, it's running, it's working, which is great, but
Logan Stinger: you know that's something that really should have taken us, you know, less than a month to get up and running for them.
Logan Stinger: Actually, we would love to jump in a little bit here because I I was actually the Csm of this
Logan Stinger: specific client while this integration was being set up, not for the full 3 years, but for a portion of it, and it was so interesting to be on a call with the the manager of the end user.
Logan Stinger: and that person would go in to the Erp system, and then they go into Red List, and they compare the data frequently, and they'd come to me and say, Why is this specific piece of information flowing into this field? This is the wrong field.
Logan Stinger: and then I'd go on to the it meeting with the with the Erp integration and bring that information to them. And the It team's response was to say, well, this is actually where it's supposed to go. So a lot of disconnects. And it's it's hard to get all of those people on the same page. And an it team is in a different state from the site that was actually using red list at the time.
Logan Stinger: So even though it takes some time and research and effort, it's definitely well worth getting to all stakeholders within your own organization on the same page when it comes to
Logan Stinger: that integration.
Logan Stinger: And getting that clear workflow diagram approved by everyone, because it it does cause a lot of pain when not everyone's on the same page.
Logan Stinger: Yeah, thanks, Ray.
Logan Stinger: It's also important to note that
Logan Stinger: kind of every integration is is living. We find that as we start integrating with these systems, people's
Logan Stinger: people's ideas expand and they they start getting additional
Logan Stinger: additional ideas about what can be done once they see data flowing. And so they they ask for additional updates and tweaks. This also just adds to the timeline, which is totally fine. It's very, very normal for us to be agile in our development processes and and make the the adjustments and changes that that are needed.
Logan Stinger: but also, that's a fairly normal thing, just
Logan Stinger: from the fact that you are using software that is continually evolving as well. And you know, E. Sap, for the most part, has been pretty static for a lot of years, but they do have an active development team. From time to time they roll out new features. You may want some of those new features pulled into red list, and vice versa. Redlist is always
Logan Stinger: always updating. You know we release every 2 weeks new feature sets, and there may be additional capabilities and data capture that you want fed back into your Erp. And so we we recognize that there's there's never such thing as a done integration when it comes to these Erps, and we we just continually adapt and evolve that over time with you.
Logan Stinger: Alright. We'll give a quick demo of the integration hub, so you can see how this works, and some of the capabilities there. How easy it is to set up. I'll switch over to
Logan Stinger: to our integration hub.
Logan Stinger: And when you, when you 1st come into Red List
Logan Stinger: you'll access the integration Hub under admin integration. Hub.
Logan Stinger: again, this is not available for everybody. It's it's based off permissions. And who has access to connect these?
Logan Stinger: You're presented 1st with an Integration Gallery. These represent some of the out of the box integrations that we have, as well as some that are, you know, 80% of the way there that we? We just need to spend some time with you and your team to to get it all the way there.
Logan Stinger: The 1st 3 up at the top are things that are more native to red lists. Red AI. Our our co-pilot, is something that an admin just needs to turn on. There's no key or anything that is needed it. It's just in here as a way as a security gate for your admin to control.
Logan Stinger: just because there are some additional costs that can come with with using AI,
Logan Stinger: the others red list. Api. This is the way for you to generate an Api key that you can provide to your internal it team, or to a 3rd party provider who might be building an integration for you that connects to Red list
Logan Stinger: and web hooks. This is just your ability to pipe data as actions. Various actions are performed inside of Red List. You can subscribe to those and and farm out the data feeds to your your web hook subscriber and take action on those.
Logan Stinger: The others are our 3rd party systems that we integrate with.
Logan Stinger: and for several of them. All you have to do is hit, connect
Logan Stinger: type in your username and password
Logan Stinger: hit, connect, and the integration, you know, you'll get a little spinning wheel, and then it'll tell you, success integrations been connected and your data starts flowing into red list
Logan Stinger: for others, some of the more complicated ones.
Logan Stinger: You're gonna get a little message letting you know that this is something you're gonna need to work with your Csm team to figure out.
Logan Stinger: And that's because we want to make sure that we, we custom build that workflow for you to meet your business needs
Logan Stinger: others. Take an Api key, as I mentioned before, you'll get that Api key from your your sensor provider and just plug it in here, and it'll do the same thing as the oil analysis connect that, and the data will start flowing
Logan Stinger: in this specific account. We've put together a demo integration from a vibration data provider. They are pushing data into red list via our public Api. So they appear over here on the left as a connected integration.
Logan Stinger: As data starts flowing, you can find the data that's tied to this integration under our IoT devices.
Logan Stinger: Here you can search and filter to find the particular device that you're interested in, or particular integration. If you've got more than one that's connected. And you can see the state of those integrations
Logan Stinger: in this specific case. You know, the integration is named vibration data.
Logan Stinger: Keeping things simple for this webinar.
Logan Stinger: And then there are 2 devices
Logan Stinger: that are broadcasting data to the red list system, one of those devices we have already connected to an asset inside of the red list system, and the other one shows is unlinked. And that's because we don't know where this device is located.
Logan Stinger: This is common. When we 1st connect an integration you have. You've already worked with your sensor provider to name the locations that these devices are connected to the names of those assets or locations don't always map one to one with how you've set up your red list device
Logan Stinger: or your your red list system. And so we need you to come in here and do a manual mapping if the names are the same. If, for example, in the 3rd party system, you had named this 0 5, 3, 4, 3, 1, which is the id of the asset in red list. Then the link would automatically be performed with you, and there's no additional work needed.
Logan Stinger: But by clicking on this record you get a simple modal where we we choose the asset out of the red List system. There's only one to choose from. For this demo account, you can choose a specific component on that asset. If there is one.
Logan Stinger: we could say that this specific device is tied to the elevator. If we wanted to.
Logan Stinger: And then there's also a way to map the indicators.
Logan Stinger: And that's because some of these IoT devices send out rather obfuscated
Logan Stinger: indicator names. You may get something sdx. 0 1 sdx. 0, 2. And when you reach out to your provider and ask them what that means. They may tell you. Sdx. 0. 1 is the field that contains the battery information, and Sdx. 0 2 is the field that contains the the vibration data. And so we allow you to create the internal field in Red list.
Logan Stinger: Give it a name that is familiar to you, specify what type of data is inside of that field, whether it is
Logan Stinger: whether it's a numeric data type or a text type.
Logan Stinger: And in some cases you can map those directly to asset fields. For example, our GPS providers, we have a GPS location on our assets and for mobile equipment that moves around. You can say, this GPS device actually needs to update a particular asset field that can only be mapped if it is a GPS coordinate type which this one is not
Logan Stinger: so I can't map that there. But once you've set up your indicators and identified which device
Logan Stinger: the this which asset this device is connected to. Then you can use that to create workflows.
Logan Stinger: And again, workflows is just your way of telling your team what needs to happen when certain indicator values are received by the Red List system.
Logan Stinger: and a workflow is created.
Logan Stinger: I'll just edit this one so we can see how this is set up. You give it a name. I've called this one injection molding machines dash vibration alerts, I specified. It's for all locations. I don't care which one of my devices. Is sending this data. It applies to all of them.
Logan Stinger: We can see a similar thing on on the next page with equipment. This is where you can filter down and say
Logan Stinger: this rule that I'm going to create, and the actions that it's going to perform are only applicable. If I am looking at a specific asset. So, for example, if if the device linked to this injection molding machine sends me these readings, then I want to do the following things. That can be that can be important if you do have
Logan Stinger: the same type of device linked to a hundred different pieces of equipment. But there are different thresholds for each of those pieces of equipment, and that may be by asset, class, asset type, or a particular asset
Logan Stinger: where you know for asset a. If the vibration is more than 2 g's or 2 per second.
Logan Stinger: then I want to
Logan Stinger: to create a certain certain workflow where for another asset, you know it may not be a problem until it becomes 4G's or 6 G's, or something larger from a from an alert standpoint.
Logan Stinger: Once we've set this up, then we go to rules.
Logan Stinger: Rules are where we can choose the indicator that is sending the data.
Logan Stinger: So in this case.
Logan Stinger: this alert data, it's actually just a text string that it sends because the the parameters have already been set up on the the sensor provider side, where we've told it that for this particular asset
Logan Stinger: it's only critical. If a certain threshold is set, and so it'll just send the text to us, warning caution critical.
Logan Stinger: And so we can say, if the vibration data is equal to the text string critical.
Logan Stinger: then I want to perform the following actions, you can do and and or rules. Here again, this device doesn't send more than the 2 different things. And so it doesn't really make sense. But you could also create an action for battery level as a separate workflow. If you want to create a task to go, change the battery in a sensor, once the battery reaches a certain threshold.
Logan Stinger: and we could see that here if we did vibration data, we do have different operators now, because battery level is a number value. And so we can say if that number is less than. And we know for these sensors they're supposed to be sending 3.5 volts. Anything less than 3.2 volts indicates that the battery is getting getting to the point where the sensor is going to stop functioning.
Logan Stinger: And so we could create the rule like that.
Logan Stinger: Once you've created your rule, you go to actions.
Logan Stinger: and I've configured 2 actions for this particular workflow. The 1st one is an alert action. We're given the option between sending an email sending a text or sending an in app notification. You can do all 3 if that's what you'd like.
Logan Stinger: And we've said that we want all employees that have the role of vibration analyst will get these alerts.
Logan Stinger: and I want them to get the alert every time the IoT device sends it to me
Logan Stinger: again, it's important. You understand your IoT devices. If they are sending data every 15 seconds, you could end up with a lot of emails or text messages over the course of a couple of hours. As you're waiting for someone to fix the problem.
Logan Stinger: And so in those cases, we have the ability to say I have an Sla that if an alert from a sensor comes in, my guys need to investigate it within 4 HI can come in here and say, Trigger, when I get that alert, and then don't trigger again for another 4 h.
Logan Stinger: and then that'll give my time. My team adequate time to go, respond to the alert and fix it, and if I see another alert, then I know that my team either missed their Sla, or they failed to fix the problem adequately. And and it's still triggering.
Logan Stinger: We can add additional rules. That's what I've done here. We can continue to add more this action type is a
Logan Stinger: a task. I want it to have a title of injection. Molding machine, alert.
Logan Stinger: do immediately placed on a specific board. These are all user creatable. You can create any any number of boards with any names that you want.
Logan Stinger: I've also assigned it to the vibration analyst role, so they'll by default be, have visibility into the the tasks on this board that are for them.
Logan Stinger: And I've specified that there's a particular form that they are supposed to fill out
Logan Stinger: in order to close out this task.
Logan Stinger: So when they, when they see the task on their board on their mobile device, and they hit complete task. A form is gonna pop up. They're gonna be asked to fill in the questions that are asked on that form in order to say that they properly investigated the the alert, and went through the steps that were needed to to resolve that alert.
Logan Stinger: And then there's some some rules here as well. For how often you want that.
Logan Stinger: And once we've set that up, data.
Logan Stinger: data starts flowing alerts start getting triggered, and we should be able to go over to the Maintenance board and see those again. I said this went to a particular board, so we'd have to look at the IoT alert management board.
Logan Stinger: and we can see that I've got some alerts that are that are past due, that I have not yet addressed
Logan Stinger: again, demo account. So previous data in here notifications
Logan Stinger: I don't have any that are that are unread, but I did at 1 point 14 days ago, have a notification in there, letting me know that I had a task that was ready for me to do.
Logan Stinger: and that
Logan Stinger: that in a nutshell covers our integration hub and kind of highlights, its capabilities. There are more capabilities that are coming. We're constantly evolving and adding to this. There will be more more workflows that you'll be able to configure. And as I mentioned, we are letting AI kind of analyze this data, and so soon you'll be able to ask AI questions about it.
Logan Stinger: Also, we do have custom reporting for each of these for this specific
Logan Stinger: vibration data integration. We've created just a simple report.
Logan Stinger: And these are these are generally custom built for you. We have some out of the box based off of some of our our canned integrations that you can choose.
Logan Stinger: but we can also work with you to understand the data coming off of these sensors that you have and build a custom dashboard that will give you kind of a full full picture of how often you know that IoT provider is is actually triggering alerts.
Logan Stinger: All right.
Logan Stinger: Think that, concludes the demo.
Logan Stinger: So I don't know if there's any questions that we'd like to answer, if anybody has any, they'd like to submit.
Logan Stinger: I think we do have a couple. The one is, how quickly. Can I expect to see a change in my erp if I make a change in Red List? So I'm a technician. I'm out in the field. I, you know, complete a task on my phone, and I submit an inspection with that task.
Logan Stinger: When do I see that information? Go back to my Erp?
Logan Stinger: Yeah, that's a great question. Because red List does have web hooks. We, we build these integrations to be real time from a red list to erp standpoint. And so as that activity takes place in Red List, there's usually only
Logan Stinger: you know, about a 5 second lag to get that data into your Erp. Now, that is, that is dependent on your Internet connection. You know, Ray said. If I'm out in the field, you may not have Internet connection. And so that data may not appear in your Erp until you get back to a good Wi-fi signal where that data can leave your mobile phone, get up into the Red List Cloud, which will then trigger that that flow of data back into your Erp.
Logan Stinger: Got another question here. If a customer has their own server.
Logan Stinger: not a cloud server, but one that's on site. Can we integrate with that on-site server?
Logan Stinger: Yeah, the answer to that is
Logan Stinger: a little font. In short, the answer is, maybe not. Every legacy system or on site server is
Logan Stinger: is open to to the Internet. There may not be Apis or or gateways that we can use to talk to that server. We would need to work with your it team to understand what the capabilities of that that software you're using are.
Logan Stinger: some of the some of the bigger names, you know. Sap, we we do have some onsite sap connectors, but there is more work involved for your I your it team to enable that, you know, open port through your own firewall, make sure that we we can communicate with with that system. So it again, it's a maybe
Logan Stinger: sometimes. Yes, sometimes. No.
Logan Stinger: Okay.
Logan Stinger: And then we have another question here.
Logan Stinger: if the integration hub doesn't show a specific IoT provider or lab oil analysis lab, can we integrate with them?
Logan Stinger: Yeah, that's a great question. Most
Logan Stinger: oil analysis labs use what they call a a Lims system to process their data. And most of these limb systems are are fairly modern today and have Apis available to them
Logan Stinger: connecting to a new lim system is generally a pretty you know, short order task for us. We we can build those in in as little as a day, depending on the complexity of the
Logan Stinger: the Apis that we're working with, you know. Some some may take a little longer, but in general we we can be up and running in less than a week with almost any of the limb system or IoT providers. In fact, some of the the more simple IoT providers we build those integrations in just a matter of hours and can have them connected for you.
Logan Stinger: Okay, awesome. I think that's all of our questions for today.
Logan Stinger: So I think we've got some calls to action to anybody watching.
Logan Stinger: If you are a current Red List customer and you have an integration that needs to be set up.
Logan Stinger: Please contact your Csm.
Logan Stinger: we we wanna make sure that you can do as much as possible, have as much power as possible to be successful in the Red List system. So so make sure that you call your Csm or or someone that you know at Red List to get that started.
Logan Stinger: And then you can also try our Diy demo. If you're interested in red list, you're looking at using it as a potential solution at your site. We do have on our one of our websites a diy demo that lets you go in and look around all of the web application. It doesn't have mobile application fun, functionality just yet. But you can do anything that you want to in there. You can tour the entire software, should you wish to.
Logan Stinger: And then, if you're a current customer, or maybe you're about becoming a current customer, and you have some questions about an integration that maybe doesn't exist yet. Feel free to talk to our product team. Our product team loves receiving feedback about what they can do to make the software the best that it can. So you can do that by emailing product, get redlist.com, and they are really quick to respond to you.
Logan Stinger: Hey?
Logan Stinger: I think that is it for our webinar today. Thank you, Logan, for doing this for us. That joined, and anyone that is watching. We hope you have a wonderful rest of your day.
Logan Stinger: Thank you.