Our JMP Live Adoption Journey: An Engineer-Led Path From Pilot to Scale (2026-US-30MP-2937)

Hello. If you're viewing this recording, you may be hoping to become a JMP Live Expert, but I want you to become a JMP Live Influencer. My name is Kevin Gaffney, and I am an accidental JMP Live Expert. How did I end up here? Well, I've been in the process development and manufacturing phase for 25 years of my career, spanning all the way back to the late '90s with Motorola in the Six Sigma days. Throughout that entire journey, JMP has been an important tool by my side. I'm very excited about the new capability of JMP Live that I believe will transform the way that I communicate with my engineering teams within Medtronic.

I never thought that I'd say the world needs more influencers. However, as we attempt to scale up JMP Live within Medtronic, it's apparent that without the influencer skillset on our team, the analysts and the JMP doers won't be able to ensure that JMP Live is sustainably deployed in our organization. My expectation for you as an audience is threefold, depending on your role in your organization. First, if you are potentially a JMP Live lead, I hope that you take advantage of what I have learned over the last year and a half while trying to deploy JMP Live, and that you are able to craft a JMP Live adoption project that has a higher probability of success. If you are a JMP Live influencer, I hope that you recognize the unique role that plays on a team, and that you're able to help the analysts secure this important capability for your organization.

Thirdly, if you work for JMP, I hope that you're able to understand some of the difficulties and opportunities that customers have with scaling up JMP Live, and you're able to continue to refine the way that you work with companies for JMP Live pilot programs to ensure the highest possibility of success for your customers.

My talk has four basic points. The first is going to be a one-slide runback of what I presented at last year's Discovery Conference, which was what I viewed as the value proposition of JMP Live. Next, I'll give you a one-slide overview of what I mean when I'm describing a pilot-to-scale effort this year. Third, and the largest portion of the talk, will be demonstrating what it means to scale up JMP Live from an administrator point of view, so that you can see what type of skills, what type of activities you may need to specifically plan for and make decisions before you engage in a pilot to ensure success.

I have to say here, the intent of this was to be a live demonstration of the JMP Live ecosystem, but due to cybersecurity reasons and all of the information that is exposed when viewing a JMP Live portal, I decided that I needed to do this as slides. I hope that you're still able to take away the feel and the way to manage the JMP Live tool.

Lastly, I'll end up with one slide, which is primarily a reference for you to take away after the presentation that has bullet points for you to consider whether you are going to be a JMP Live lead, a JMP Live influencer, or perhaps a member of a JMP Systems Engineering support team. This was the core point of my presentation last year. In my world as a process engineer, there are essentially 11 basic steps that I go through. I believe that any engineer, regardless of your role in the organization or what type of system you're trying to optimize, would recognize these 11 steps. Now, connecting to a data source such as a sensor or manufacturing equipment is outside the scope of JMP use cases, so I don't talk about that. But the remaining 10 steps are in the JMP sweet spot, all the way from downloading the data, all the way through the robust tools to optimize your system.

However, historically, one area that's been a challenge for me as a JMP user was the tasks of publishing my reports to my customers and potentially even automating alerts to them, so that I didn't have to be a middleman in updating reports and letting them know that something interesting was happening. This is where JMP Live fits in. When I learned about the JMP Live capability and saw it in action for the first time, I immediately saw the value in how this one capability would now enable this entire workflow to be within my span of control, and I wouldn't need to leave the JMP ecosystem to accomplish these tasks, and I certainly wouldn't need to engage other cross-functional team members to parse out individual tasks along this workflow. The fact that I could keep this workflow within the JMP ecosystem, and my customers could see and feel the way that I was using JMP, I hypothesized, would allow me to accelerate engineering outcomes, avoid software proliferation, and minimize infrastructure burden.

This was the hypothesis that we asked leadership to help us explore two years ago, using statistical process control as a use case. I believe we were wildly successful. We were able to demonstrate that we could cut a deployment project schedule in half, we could reduce the number of cross-functional engineers needed by about half, and we could eliminate about $10,000 from a single process SPC deployment, due to the elimination of hardware and software licenses, all by using JMP Live for that SPC deployment team. This was successful, and the leadership continued to invest in refining our pilot activities, as well as purchasing an enterprise-level license for us to scale up across the organization.

What does scaling up of JMP mean within Medtronic? Well, first, you have to understand our starting point is that we have 500 JMP users. About 50 of those users are JMP Pro users, and all of our user base is what I would consider high-level, data-science-minded type of engineers. We also are a very large corporate entity that has very siloed responsibilities across different IT organizations, across engineering teams, et cetera. A large portion of what I'm going to describe to you should be understood through the lens of that type of organizational responsibility.

Last year, in calendar year '25, we rolled out JMP Live to a small group of JMP superusers, specifically looking at reliability and statistical process control. We had one server, and I managed that across about 10 people in about three sites. That was successful, and this year, we are now scaling up to two servers within the US. We have two different sites that will be regionally managing their own servers. Our goal is to continue to develop use cases and continue to develop a strategy for deploying across our global manufacturing organization in a way that's in alignment with our global IT best practices.

In order for that to be successful, we need to ensure that our users, which are primarily our JMP population and their small engineering teams, are able to influence our manufacturing sites and our development programs to demonstrate the value, so that our IT organization is willing to plan for the resources, whether those are hardware resources or human resources, to help make the JMP Live growth sustainable year over year. That would be success of this pilot to scale activity, would be getting those sustainability items budgeted for calendar year '27 and beyond.

Now, JMP Live also has a very important capability to allow suppliers to connect into the enterprise license. My personal approach here is to make sure that we are internally sustainable before choosing to exercise that part of the capability, but for your organization, that may be an important thing that you pull into your pilot or to your scale. Now, I understood that JMP Live aligned very well with our global IT strategy, and so I felt confident in trying to go all the way from pilot-to-scale within a year.

If you're not so confident in what JMP Live really is capable of, or if you don't know if your organization is ready to invest in their own pilot, there is another alternative, which is to partner with JMP through the public jmp.com website, where you can learn to publish your own reports through a public portal, and you can start to understand exactly how this capability might fit into your organization. Again, what I'm about to show you from this point on is very unique to my corporate structure. With that, one of the main points to get across here is that influencers are everywhere nowadays. The need for influencers is going to be very important in what I'm about to tell you for the next 20 minutes.

This is the roadmap that I'm going to use for the rest of the discussion. I'm not going to discuss this in thorough detail at this moment. I just want to orient you to three important pieces of this roadmap, so as I go through the next slides, you are able to understand how to orient yourself to the discussion.

The first is, in my pilot and scale-up activities, there were four important populations that I needed to interact with. The first is the customer. These were the organizations that I wanted to be able to consume and interact with the JMP Live analysis without needing to have a JMP license and without needing to be a JMP user. The next is the JMP analysts, where my peers of 500 JMP users that I was hoping to bring the use cases to the JMP Live pilot and scale-up phases. There's the JMP Live superuser, which I will, from this point on, pretty much refer to as a JMP Live admin, which is the role that I played and essentially will be the most important role in the pilot and the scale-up activities.

Then there's the proper IT organization, which has very clearly defined roles in terms of owning server hardware, owning best practices, owning security, that type of activity that is necessary for JMP Live, but not technically part of the JMP Live ecosystem directly, and you'll see that as I go through the talk. The other thing you'll notice along down here on the horizontal axis, there are several arrows. Now, I refer to going from pilot to scale. In reality, our pilot phase was four unique pilot agreements with JMP. Each 90 days, each $10,000, you'll see through the story whether or not you feel like your organization would need that structure. It wasn't necessarily planned to happen that way, but it was well suited for our organization. It was well suited for how I was able to get funding over the first year. But you'll see that I consider that we were successful in our first pilot phase, and you may plan for one or more pilot phases in your activity.

However, the scale-up phase is where we went from a small group of engineers testing capabilities to actually, quote, going live, or rolling out the capability to the larger organization. Those are the activities that we're doing this year. Now, we will end this phase in calendar year '27, and that is when I need to have the IT organization aligned and have them fully budgeted to continue to support the scale-up of JMP Live on a global level. A key success statement is going to be alignment of JMP Live to what our global IT organization is trying to accomplish. Their multi-year strategy is to ensure that our manufacturing organization can monitor any manufacturing line, anytime, anywhere, from any tablet. This is exactly what I saw from JMP Live when it was introduced to me. This is why I had confidence that I could scale this up in my organization as fast as possible.

But ultimately, the long-term success of my vision is going to be by engaging JMP Live influencers to make the connection between my customers as JMP Live champions and my IT organization as the organization that will own the long-term sustainability. This is really a unique skill and unique role compared to the JMP analysts and your JMP Live administrator. With that, I'm going to now break down what was in our pilot and what is in our current scale-up activities to help you understand how you might be successful in your own pilot project.

The first steps that you can see here in our roadmap now actually happen before you even engage in the pilot activity, and that is securing the server hardware according to your on-premises server requirements and setting up your storage structure, again, in line with your own organizational activities. Now, JMP does provide some guidance on initial criteria for setting up your servers. We found that we had to quickly iterate and upscale both our original server construction and our storage construction. I would encourage for you not to look at the current JMP guidance and just say, "I'll do the minimum." You should probably choose something more than the minimum to start out with. Specifically, where we ended up right now is a server with 16 cores and 16 GB of memory, and our storage structure as a separate storage for our database, compared to where the authentication layer and the actual application, JMP Live, lives. We learned those lessons very quickly.

Then the next thing that we ran into was that there are four different applications that need to be installed on the server and activated. It's not like if you have used the JMP and JMP Pro trial licenses, it's not as if you just download those to your laptop, and then they're instantly running.

There's a significant amount of configuration with security layers and authentication layers that really have to be constructed, which I'll talk about in a moment. Making sure that you have certificates and then making sure you understand how service accounts and application services work through three different services is really important for your JMP Live admin to plan properly. Once you have all that, then you actually have operational software that you can start configuring within the JMP Live ecosystem.

Now, the first piece of software that you'll need to configure is the Keycloak application. Although this has the JMP Live realm or header in it, it's really not what I would consider part of the user experience for JMP Live. This is something that you'll need to make a choice. How extensively are you going to integrate your authentication layer with your initial pilot? You can do it through single sign-on, which is more pleasant for your customer and easier on the admin in terms of time, or you can individually configure users in your authentication layer. Because we were concerned with the speed of getting the portal up and running to our customers, we chose to actually configure the users individually.

Initially, it was going to be 10 to 20 users in our pilot phase. It takes just a few minutes. There's only one screen of just a few fields that you need to configure. That's the route we went here and lived with that for our pilot phases. If you go the single sign-on route, there are many different types of security and configurations you need to be concerned with. You really need to get IT involved. This is their area of expertise with the tools they use that aren't really exposed to an average engineer in an organization. We put that off to the scale-up phase. You can see here in the dashed orange line. We did that in the scale-up phase, and it worked just fine for us.

Once you get all of the authentication configured, now you're actually able to go into what I call the JMP Live app or the portal that your customers would see. On the left-hand side is what the portal looks like. You, as a JMP Live admin or the superuser, will have a special tool. Your customers will see the Home tab and the Spaces tab, but you will have the Admin tab.

This is where the magic happens, and where the bulk of the rest of the conversation lies: what is the administrator doing within JMP Live? There are 12 submenus here that you need to be concerned with. They all have an importance at a different phase of your pilot and your scale-up. I'm not going to touch on all of them, just the ones that were critical to get us to that level of scale-up success. You'll see a variety of different ways that we navigated these.

The first submenu is the server submenu. This is really just a review. Going back to our roadmap in the lower right-hand corner, you can see this dashed orange box. We already set up most of, or if not all, of these items when we installed the software and got it operational on the server. This is really just a summary of all those settings. But it's nice to know that this is here and what all of these terms are, so that you don't have to continually log directly onto your server to do some light troubleshooting or system confirmation.

The most important part of the administration, in terms of initial success for your customers, is the user configuration. Now, I mentioned that the Keycloak application is where you set up the authentication of users. That's step one. But step two is to actually configure the user within the JMP Live ecosystem or portal, so that they can actually see and publish the portal. Again, there's really not a whole lot of complicated choices you have to make here, but it is something that you have to know. It's not enough just for the users to log in. You then have to do one more step of configuration. That's this step here. Notice here that this took us about half of our pilot time. Our first pilot was 90 days. It took us about 45 days just to get to this point where someone else besides me as the administrator could actually see the portal. That's a huge portion of your pilot time. I'll come back to how you might want to mitigate some risk there in the last slide.

Now, I'm going to move away from the administrator view of JMP Live to your customer and your analyst view of JMP Live. You can see here that what I'm showing now is the Home tab. In the Home tab is where you will see all of the reports that are available to your customers.

It's at this point that you may be able to consider your pilot a success. This is where I considered our pilot a success because we were able to demonstrate to our leadership that our engineers were able to publish their own statistical process control reports, and a customer without JMP could actually see those reports. That was success for us. You can see here, we gave ourselves a little gold ribbon there in our roadmap. That was about, like I said, just about halfway through our pilot phase. But really, there's a whole bunch of other capability that is really important to my JMP analysts and customers. Before we exited the true pilot phase and invested in the corporate enterprise-level license, we wanted to test a few more capabilities. Those capabilities revolve around the ability to automatically refresh reports and send out automated notifications to customers. I refer to that as making the data pipeline connections, which JMP has always had a very robust capability to do, and most of the JMP users in my organization are able to make those pipeline connections on their own at their desktop. But we needed to demonstrate how this could be done and automated within JMP Live.

That was another major phase of our pilot activities. You can see here, the important thing about this phase is that this is where I had to engage three different populations simultaneously. I had to get the data source use cases from my JMP analysts. I had to engage the IT organization and get the proper firewall port connections and data repository permissions. Then I had to go back into the settings configuration within JMP Live and also the server, and I had to make sure that all of that information was properly put into JMP Live, so that it knew where to connect. Then also on the server side, I needed to make sure that my service account was presenting itself properly across our data architecture globally. All of that is pretty nuanced, and there's a lot of iteration with both your customers and IT here. This absorbs a major part of the relationship.

Once that was configured successfully, then I could back up in terms of some of the submenus in JMP Live, and I could work with, say, either the Spaces or the Groups submenus, and I could start to architect, well, what does the portal itself look like to my customer?

The other important thing about the Spaces is that this is where you will get into permissions at a user level, at a Space level, and a Group level. Just like most types of electronic systems nowadays, there's a hierarchy of permissions, and those permissions can be mixed and matched both by user as well as by the repository that they're looking at. JMP Live has several different types of very high-resolution permissions that a user can have when interacting with the JMP Live portal. For us, the reality is the average JMP analyst does all this themselves. We don't make a strong distinction at this point in our JMP Live adoption between whether you're going to download, or contribute, or admin the data, or import the data. We just allow everybody at this point to do everything. If they're already a JMP user, if they're already contributing to JMP Live use cases, they're usually already doing this stuff on their own. That's where we are, and that's why we could afford to push off really dealing with the Spaces configuration until after we had data connections and pipelines fully mapped out. But you may move this to a different spot in your evaluation.

Then lastly, our two important submenus. The Refreshing submenu allows you to see how your analysts are scheduling their refreshing. When you only have maybe five to 10 users doing this, this probably isn't that interesting of a configuration tool. However, as you scale up and as you get into the 20s, 30s, and more reports being scheduled and running in an automated fashion, we found that we had to start managing that at the admin level so that we weren't causing unneeded performance delays in the overall JMP Live experience for all of our users because the system was busy doing refreshing. While we want to democratize that and have the users making good choices with their scheduling, the JMP Live admin technically can go in here and override and micromanage the scheduling if needed. Then also, when it comes to understanding how JMP Live is performing with respect to the server capabilities, we've seen this in a couple of places now. You can see this in the server settings. You can see this if you go directly into your server, also. But again, just another summary place where JMP Live allows you to see some of the performance metrics of your JMP Live ecosystem, which is nice.

I'm not going to talk about different log structures, different ways to view how users are interacting with the system, how to make groups, notifications, all of that stuff. There are special admin rights to do that. But really, we're not at that place yet where that's becoming critical for us. Maybe that will be a future talk.

With that, I'm going to wrap up with the reference slide here and say then to my three different roles in the audience here, if you think that you will be a JMP Live pilot lead or an administrator, then you'll want to pay particular attention to these bullets here. Specifically, if you can identify your use cases and what you want to test within JMP Live and have alignment there with your funding organization, so that you can test that out in desktop JMP and make sure that you understand how you are going to do the analysis, what the reports are going to look like, how your customer is going to want to interact with it, and you'll need to test it with them in an official JMP desktop license. But doing all that and making sure you understand what success is then allows you to hit that publish button and have what you publish be immediately useful, successful to your customer without then having to wait until you've published to iterate and work out the details of what success looks like.

There are some other things, integration and the specific statistical process control features of JMP Live that I talked about in last year's presentation. If you're interested in some of these use cases, you can go to the 2025 recording. If you're an influencer here, really what we're asking for is someone to really develop that relationship with the IT organization, learn to speak their language, which was in Medtronic, it's total cost of ownership of these type of software applications, and really take the burden of the marketing and the constant communication off the shoulders of your JMP Live admin and your actual JMP analysts, and become their advocate for those organizational discussions.

Finally, if you are a JMP representative, I would like to start thinking about a different structure to the JMP Live pilot than how we experience the JMP and JMP Pro trials as users and engineers. Maybe it's somehow integrated with the public jmp.com opportunity. Maybe it's something that is scaled for the existing user base of JMP in a company. I don't know. Lots of opportunities there, but I'd like to have that conversation with someone. Definitely, I encourage customers who haven't gone through a JMP Live pilot to ask specific questions about pilot options there. With that, I'll end by asking, "How can I help you plan your JMP Live pilot more effectively?" Thank you.