Using JMP Live to Run Your Business (2025-US-30MP-2523)

Hi, I'm Jed Campbell. I'm the Systems Engineer for the US Rocky Mountain Territory, and I'm joined by Scott.

Yep, and I'm Scott Allen. I'm the SC that covers the Ohio Valley region of the US. Really happy to be here today with Jed to present some interesting JMP Live use cases. We're going to talk about how you can use JMP Live to run your business.

But before we start that presentation, I do want to make sure we acknowledge Yasmin Hajar and Clovis Weisbart, who have been also contributing to this project, and many of the case studies, dashboards that we'll be talking about today. They were very instrumental in creating as well.

Just to give a quick background, JMP Live is collaborative analytics software for sharing knowledge across an enterprise. If you're not familiar with it, JMP Live really allows JMP users to share their JMP reports with others. And just like in JMP, those reports are interactive and dynamic. One really nice thing about JMP Live is that those reports are accessible to those that don't have JMP licenses. And this really facilitates collaboration and knowledge sharing across many different departments, many different groups, and facilitates all those problem-solving and collaboration efforts that they might have.

During this presentation, our goal is to really show how we can unlock the full potential of JMP Live with customized dashboards, reports, and workflows. We're going to show a lot of different reports and dashboards, and many of these are enhanced by the use of JMP scripting language, JSL. We were putting these together. The group was really challenging ourselves to push the limits of both JMP and JMP Live to show what is possible.

The case studies that we're going to go through today, we're going to do these in the context of a fictional company called Helios. Helios is a manufacturing organization. It sells a wide variety of products, manages many customer relationships and supplier relationships. They have business operations and sales teams throughout the US, and they have an R&D and product development group that's working on next-generation projects and products.

The case studies we're going to talk about today, the first case study that we'll talk about is how you can keep track of key business processes across different groups and departments with automatically refreshing dashboards. The next case study that we're going to talk about is showing how you can use JMP Live as a centralized library for technical documents, where you can go from JMP reports all the way to context-rich technical documents. Then for the third case study, we're going to show how you can demonstrate maybe a problem-solving workflow, going from a critical issue to a resolution and using root cause analysis or doing that root cause analysis all in JMP Live, dashboards and reports, and workflows.

All right, with that introduction, I'm going to pass things back over to Jed.

Thanks, Scott. I want to take just a minute here and walk through a couple of these automatically refreshing dashboards that this company Helios uses. Essentially up here in this upper left-hand corner, we've got… This is a dashboard for manufacturing, and we can see that over the last little while, the manufacturing group has maybe had a couple of hiccups with their production, and they've decided that since they're forecasting quite a bit of extra demand coming up soon, that they would fill that with some overtime.

This is just a way for them to track the things that are important to this group, and every group at Helios has their own dashboard. One thing to maybe call to your attention is they've been focusing recently on OEE, so they have this mandate to start tracking and improving that. But I think maybe another more important aspect of this is they can use this to manage not just the overall trends of their organization, but they can do it for the day-to-day things, too.

Here's just a little automatic dashboard. Again, when I say automatic, this refreshes automatically. They just use this to do a resource allocation for their six different production lines. They can see who's ahead and behind and maybe move some staffing and send help when it's necessary. That would be a manufacturing dashboard. Maybe a procurement group would have a similar dashboard, but completely different and customized for them. A nice thing about these dashboards is that they're all interactive. We can take, for example, maybe some of our efficiency opportunities, and we can see where those opportunities lie within the supplier scorecard rankings. We can also have an amount of interaction with this, and we can tangle with it. What's selected in one report is in the other, and so that's really nice for them to be able to do that. They can adjust these reports as needed and interact with them.

They can also have a daily stand-up meeting, and this is just fed from a spreadsheet. Daily stand-up meeting in their organization. This is just a nice place for them to come together really quickly, have a daily huddle, and discuss things that may be hitting specific issues. The supply chain might be able to say, "Hey, main supplier has been stocked out of this super important widget, and we've got it sourced from somebody else, but it's going to be double the normal cost. So that's going to affect both cost and delivery." Manufacturing might say, "Okay, we had a chemical spill, and we need some help from safety." So they just use this as part of their daily running-their-business type aspects.

Next up, Scott is going to share a little bit more about how they use JMP Live for R&D.

All right. Thanks, Jed. For the second case study, I really want to show how you can improve the insights gained from JMP reports by adding context to those JMP Live reports. I'm going to do that by taking on the role of a new scientist at Helios. Maybe they've just joined the R&D group.

As a new scientist starting out, one of the first things that I might do is need to come up to speed on the technology and the project that I've been assigned. And so how would I do that? First, maybe in an organization that doesn't have JMP Live, I would go to a SharePoint location and start reading technical reports. And those technical reports might look something like this. Maybe they're PDF documents or Word documents, and they would have some title and document number. They'd show who wrote it and when. There'd be some report, some description of the experiment, some motivation for that report, and then there'd be JMP reports that might be copied and pasted in. In this case, we're looking at some capability assessment.

We would get some description about what some context to that analysis, some interpretation of those results, and some conclusions that were made. Then we might paste in some other material to support that. Finally, there's usually some references. I know in my past, when we did this, we would just drop in a JMP file and attach it to that document in case someone wanted to dig into these. But in the case of the PDF, this is just a reference that you might be able to find somewhere else on that shared drive. You might have some links to those reference documents that you can then go look up. But this is probably pretty common in how many organizations might document an experiment or a scientific study.

At Helios, though, they've got JMP Live, and maybe when they first started out, they could go into their JMP Live instance. They'd go to that R&D folder, maybe they'd look for a group, and they'd look up that project. In this case, we're looking at some capability analysis.

This is that same report, but these are those JMP Live reports now. I could go in, and I could take a look at the overall process capability. Once this loads, I can take a look at these interactive plots. And just like in standard JMP, I can highlight those data points, and they're connected back to all of the different reports that are… Okay. I want to pause. Can we cut this out?

Yeah, we can just cut this out.

Okay. Let me go back here. Let's see. I will just start back when I…

Yeah, maybe just start back from when you took the screen share back from Jed.

You want to start that far back? Okay.

Yeah. I think it'll just make the cleanest cut in the recording.

Okay, that's good. All right. Let me just get this set up again. Demoing in a web browser is pretty new. Let's see. Okay.

It's worth the extra time, though. It's really cool.

All right. I will pause and then start back in.

All right. Thanks, Jed. For the second case study, I want to show how you can improve the insights gained from JMP reports by adding context in those JMP Live reports. To do this, I'm going to take on the role of a new scientist at Helios, and maybe they've just joined the R&D group. As a new scientist starting out, I would likely need to come up to speed on the technology and the project that I've been assigned. How would I do that? Well, I would probably start looking up technical documents. Those technical documents might be PDF or Word document. They have a title, a document ID, tell you who wrote it and when. Then there'd be some description of the motivation for that experiment or that designed experiment or whatever it might have been, as well as now just JMP reports that are pasted in.

This is fine. It gives you that snapshot of the analysis and maybe the report. The pictures here are the key images to get to the conclusions that were drawn. Then we'd have some paragraphs or other context that describes that experiment and the results. We would have more JMP reports, and maybe we even have a link to that JMP table or reference links to the supporting documents or reference documents.

This is how organizations would document and experiment in a technical report if they didn't have JMP Live. At Helios, they do have JMP Live. In that case, as a new scientist in that R&D group, they might navigate to the R&D folder, and they would look at the project, in this case, some capability analysis. They can navigate these JMP reports. These are going to have the live interactive data, in this case, a capability assessment, or they can navigate back through some control charts. The really nice thing here is they don't have to go searching for that data. They can just find the data over here on the left-hand side, download that data table, and start looking at the data themselves to see if they come up with any conclusions that might be different than what had been reported.

But the downside to this is there's really no context for these reports. So what we have in this PDF document is really a lot of description. It tells a story. It tells a narrative for that experiment. The JMP reports, while they give you all the information about the data, you lose that narrative. Fortunately, at Helios, they have some folks that are really interested in pushing the envelope and doing more with JMP Live. What they've done is they've created a hybrid. They've created a technical document that also has live JMP reports. Fortunately, as that new scientist, I can go into that R&D folder. I can go to a project list and find the project that I was assigned, and that happened to be this tire tread formulation. I can see who sponsored it, who the team lead might be, a little description of that project.

Then I can go right to the project report that has all the different technical documents. In this case, I'm going to go back to that capability analysis report. And now I've got the best of both worlds. I have a technical narrative document, looks very much like a PDF or Word document, and I can scroll through this. I can read some introduction. I know now who's written that report.

Now all of these are live JMP reports. They're interactive, just like in a JMP table. You can see I highlighted the points up there, and they're going to show up in these control charts. I can highlight points in any of my control charts, and they're going to highlight in the other charts because they're all linked back to the same table in JMP Live.

This is really giving us that best of both worlds. Now we can type some context and tell that narrative, and then drop in the JMP Live or the JMP charts that are most relevant to that narrative.

Just like in maybe another report, we can have a list of references. In this case, if I'm reading this report, and I want to learn more about this. I can see that this is some pre-manufacturing capability analysis, some formulation, and I want to learn how they develop that formulation. I can click the link to that formulation, and now I'm going to go to maybe a screening design report that tells me when it was written, who wrote it, and what the motivation for this project was, get some Graph Builder reports, as well as my interactive profiler to find out how that optimal formulation was created. And then in my reference section… Maybe in the body, I just put that Profiler, but then in the reference section, I'm appending all those full fit model reports. Any of those JMP reports that you would normally just copy-paste into a Word document, you can instead embed in this narrative document.

All right. I think as a scientist that's coming up to speed, I'd feel much more comfortable in this world where I can access both those JMP reports and the narrative surrounding them.

There's a few other things that we can do that Helios has done in this case. The R&D Management group is tracking all of their projects in a dashboard as well. So they can take a look at their R&D budget. They can see their spend. Maybe they can see an overview of their projects and the budget versus actual. They might have budget details as well that show the surplus or overspend per month just to see how those projects are progressing.

Helios has really come up with some really interesting ways to leverage JMP Live reports. I think there's two other things that I wanted to show here really quick.

One of those is maybe… In this case, I've got four files, and so it would probably be pretty easy to find the one that I want. But if I didn't know where that file was, we've indexed these by keyword, so I can just go in here and look for maybe this product number. Maybe I need to look for product number 44-J. Now I can search and go directly to projects, and I've indexed these either by author name or a brief description of that project. That makes it really easy.

The other thing that I can do is I can send a comment. I can say, "@Jed, hey, check this out. What do you think?" Now I can get Jed to comment on this report and let me know what he thinks about this. A really interactive way now to share information on these JMP Live reports.

All right. I think that's all I wanted to talk about when it comes to this style of report. So I'm going to hand things back over to Jed, who's going to finish up with the third case study.

Thanks, Scott. Well, if you're being serious about wanting my feedback, I really, really like the idea of combining the history and the interactive report. I don't know if I had a dollar for every time in my career, I was looking for something that someone did and couldn't find it, I'd have a lot of dollars. So I really like the direction that Helios has taken on this.

Okay. Changing gears a little bit. I'd like to walk through a case study. This case study is really just showing how JMP Live is used in normal businesses to drive the business. We're going to see a problem pretty early on, and then we're going to do a quick diagnosis and a response to that problem. And I've got a bunch of tabs already open. Now, Scott has already shown us a little bit of how to navigate. So I'm going to take a shortcut here, and we're going to go fairly quickly, but we'll go through finding the problem today, and then we'll transform fast-forward in time to tomorrow, and then sometime around two weeks from now. Just to stay found, I want you to notice that every time I move my mouse up here, that means I'm opening a new report.

Let's say, for example, and I'm getting ahead of myself. But let's say I wake up in the morning and I have an email from JMP Live that says, "Hey, this yield control chart went out of control. And I know that the yield control chart…" By the way, I'm going to play the persona here of just maybe a quality engineer at Helios. So I get this email and I know the yield control chart is… That's the overall company yields, and so I'm a little bit scared from that. But I go into work and I pull up that control chart and I see, yes, our yields have tanked overnight. That's pretty scary. I need to get on that and get a solution going pretty quickly. So the next report that I pull up is just the Process History Explorer. This is in JMP Live. Again, it automatically refreshes. All these reports automatically refresh.

I can look at this Process History Explorer, and it'll tell me that, well, Base Component 15 seems to be the problem component, the biggest problem. If I drill down to Base Component 15 and dynamically refresh that, I can see that it's actually when we're running Base Component 15 in production line 1. I can compare that to the other production lines that are getting somewhere around 80-67% yields versus 66% yields.

Right away, without having to open a report or carry a database or do anything besides just use my browser, I know what the problem is. So I grab my laptop and I head up to Production Line 1 on the shop floor, and I start talking with them, and they say, "Oh, we're so glad you showed up because we just can't get this thing to work. Everything's broken." And they say that they're pretty sure they started a new raw material lot of Base Component 15 last night.

I pull up this next report, which is just a Production Lot Viewer. I can look at that, and I can drill down to Base Component 15 here, and I can confirm that and say, "Yeah, it looks like we had one of these base components 15s released into production just yesterday.

By the way, we're filming this in late August, if you're watching this in the future.

One of these was just released, and so I have got to the cause very quickly. I don't know root cause yet, but something about this Base Component 15, this new lot is causing production to go haywire. I pull up the quality information. We have an incoming quality group, and they measure some critical characteristics of Base Component 15. Looks like there are five of them. I can grab…

Now, these last two lots seem kind of suspicious. I mean, they're not out of control. I can scroll through all of our different characteristics. And I see that, well, X3 is really high. It's in spec, but it's just barely in control. And X1 is also in spec, but barely in control. I think, well, that's awfully suspicious. And I realized that maybe I probably should have started by looking the combined metrics portion of this report. A model-driven multivariate control chart is a mouthful to say, but it's a great way to look at lots of variables at once. And had I looked at that, I would have seen immediately that there was a problem. I'm already maybe thinking of changing my standard approach to solving problems and maybe changing the procedure for quality to we're going to look at this model-driven multivariate control chart regularly, and we're going to see this a problem before it hits production. We're going to be ready for it.

There's maybe Countermeasure 1 that we're going to take as a company. But I've got my laptop in my hands. I'm in production still, and now I'm pretty sure that this component has some problems. And I need to talk with the procurement group because I'm pretty sure I'm going to have to quarantine a lot of this. We're going to pretend that Scott is the procurement person. So I walk to his desk and I see, luckily, that he's available. I say, "Scott, we've got a problem with Base Component 15. Do we have enough of this to tie this by for a little while? Because I think I need to talk with a supplier." And he says, "Yeah, it's been really popular. It's been getting more popular. But our inventory for this is, we strive for about a month's worth of inventory on it because it's a high runner in case there are problems like this. So yeah, I think we can." He does a little napkin math and says, "Yeah, we're pretty good."

The two of us update that spreadsheet that feeds the 9:15 Daily Huddle, and we go to the Daily Huddle much more prepared than having been caught flat-footed by manufacturing, for example, saying, "Hey, yields are bad." We already knew about it. We already addressed it. We're already working to solving the problem, and we can inform the entire organization that we're working on it. Not only that, we might need a little bit of help finding a few remnants of these components just in production in various locations.

During that daily huddle, we can pull up a dashboard for resource allocation, and we can see that there are two production lines that have an extra person each. Maybe we repurpose one of them for half the day to help find these components.

Here to summarize Day 1, what was a potential crisis? It really became a manageable problem because we had access to the data, we had access to the reports, we got yields back to normal with maybe some delays, and maybe we're not actually producing the things that use component 15 yet, but at least we've addressed it a little bit. We go the rest of the day, we quarantine that material, and we've returned it to the supplier. We've started working with the supplier. In fact, we realized the problem was maybe a little bit bigger and had to quarantine more than we thought, but we're ready to move on to tomorrow.

If we fast-forward in time, we didn't get any emails because overall yields have been going really well, which is what we expect. But Scott and I are thinking we're going to meet every morning first thing. So we go over these reports, we make sure things are looking good. We look at the raw material inventory. If I look at that Base Component 15's inventory, yesterday, it was at about 200,000. We had to quarantine about half of it. Maybe that's a little bit scary. So we walk over to Clovis' desk. Clovis actually works in production planning, and he queries the database with our forecasts and says, "Well, I'm just going to make a quick graph builder of how many parts we have on the shelf and how many parts, just some forecasts of these and maybe some drop-dead dates are maybe we've got until the beginning of September until everything goes horrible."

Yeah, because it's really easy to use JMP Live, we upload this and make it auto-refresh. And that's just part of our daily check. We go to that daily meeting, and we inform people, and we say things like, "Well, it looks like it's going to be tight, but we're already working with the supplier." Manufacturing still hasn't produced anything with it. The supplier is saying they can get lots to us within two weeks, so we're cautiously optimistic. Maybe HR wants to say, "Don't forget that the company barbecue is this Friday and you should show up hungry."

We get through Day 2, and things are different. They're even better. This manageable problem has become a cross-functional team that we're using to solve the problem. It has daily status updates. Delivery is still unaffected. We don't have those new components yet, but we just keep managing this problem as daily as a team, and take a couple of minutes each day to work on it. If we fast-forward to two weeks from now, again, we haven't had any suspicious emails that show up. We know that the yields have been good, but we're still verifying it. We can look at…

What we had was a forecast, and we've populated that with actual numbers, and things were starting to get a little bit scary, but we can see that the suppliers started to deliver things maybe even a couple of days early, and that's super nice. So we've got more of these components on the shelf, and we started making some finished goods products. That means when we go to that daily standup meeting, manufacturing is saying, "Hey, we're using these in production, but we already knew that because we have these reports." And we're able to say, "Hey, we think we've solved this."

Then, if we think about the ramifications of this. Things like supplier scorecards get updated. This was the Galactic Gear Works company, fictitious company, that had this quality issue. I guess I shouldn't say "that had this issue". We had this issue because we didn't specify our spec limits properly. But it shows up in that quality score, and they get their own version of that quality score because they can log in and see that regularly. That causes that conversation to definitely happen and make sure that we don't have any other spec limit problems.

More than just that, all of the little reports and things that we use to drive our strategy are automatically updated. This Galactic Gear Work shows up as having had an issue. Again, that's going to be a catalyst for us to check our spec limits everywhere else. If we step back and think about how we've solved this problem, really, we've been able to solve the problem because we had all of this access to all this data, and it was automatically refreshing and updating. Our company strategy is informed by all of this new data that we're creating as well. Scott, what do you have to add to that?

Yeah, not much to add, Jed. But it's really good to show how many different groups can collaborate across JMP Live with automatically refreshing updates. You can start addressing issues before that trickle-down of information. You don't have to wait for a report. You can just go and get it or get an alert from it. That's really great to see. I'm going to share my screen one more time.

All right. We're going to summarize really quickly what we've seen here today. Hopefully, you've seen some ways to use JMP Live in ways that you might not have thought about before, whether it's through interactive dashboards, JMP Live workflows, or building context-rich JMP Live reports. Hopefully, you're motivated or inspired to try this on your own.

As we close out, I just want to acknowledge a few more people. I want to acknowledge Yasmin and Clovis once again for helping out with dashboard building and the use cases, and then also the Product Management group, Sarah, Dieter, and Dan, for putting together this concept of Helios and letting us really work pretty freely in this Sandbox Company to develop some of these dashboards and workflows. Thank you.