Keeping your JMP analyses connected and current can be challenging, especially when updates are captured in spreadsheets, emails, or handwritten notes. This presentation explores new capabilities that make it easier to move quickly from updated data to insight when managing shared data between JMP and JMP Live.

With JMP Live 19.5, data tables can be edited directly in the browser, removing the need to collect updates offline. Contributors without JMP can make meaningful changes, such as updating specification limits or adding new experiment results, right inside JMP Live. These changes flow automatically to linked reports and analyses, helping teams keep results aligned with the latest data.

Beyond basic editing, this session also looks at how the JMP Live data editor supports real-world collaboration, including permissions, column and table locking, and other features to help teams manage shared data. It will also highlight how JMP users can work with JMP Live content directly from JMP using the Toolkit add-in, making it easier to review and update shared data.

Together, these capabilities help teams manage, share, and maintain connected analyses. This session shows how to use JMP Live’s data editing feature and the Toolkit, with concrete examples that attendees can adapt to improve their own data workflows.

 

 

Hi, my name is Justin Chilton. I'm a software developer here at JMP working on JMP Live. Today, I wanted to share with you a new feature available now in JMP Live called the Data Editor. Mostly, I'm going to be showing some demos with you in JMP Live today, but I do have some slides to give us a little bit of background before we get started.

First, if you're not familiar with JMP Live at all, really, I'll let you know that it's a secure collaboration platform in your browser built to share JMP content with colleagues and bring that same interactivity to those who might not have JMP, like managers. It includes interactive features like data filters and column switchers.

But in recent years, we've added several new features, like Spaces, which help with the content organization, automated data refresh, which helps keep your data as up to date as possible, and most recently in JMP Live 19, we added control chart warning triage, which allows you to track your warnings through time. We've added a lot of new things on top of the interactivity.

You may or may not have known that we released a new version of JMP Live, 19.5, this past summer. It's a release between JMP 19 and the upcoming JMP 20. It's a feature release that's fully compatible with JMP 19. The latest release is actually running JMP 19.2, so anything that's compatible with 19.2 will work in JMP Live 19.5. This faster delivery of features allowed us to bring all these features I've listed here. But the one I'm going to talk about today mostly is the data editor.

Let's talk about the reality of how data analysis and data collection might work within an organization. Obviously, the main goal is to do some analysis. These folks might be data scientists and engineers doing this work. They all know that JMP is a great and maybe the best tool for doing this. They're very happy using JMP. But where does the data come from that they need to perform the analysis?

Probably the most common place is some automated data source. This could be a database that you're pulling from, or it could be some generated files like Excel files or CSV. JMP Live already has a lot of features, like I talked about the refresh capabilities, to get at that data. But what about the messier places that data comes from?

This might be from your operators or technicians who don't have JMP. They might have Excel, they might send you data via email, they might even write it on a sticky note or notepad. This way of collecting data is very error-prone and can get lost in translation between the operators and your analysts. This is the problem that we're trying to tackle, or one of the problems we're trying to tackle with the data editor, and one thing we'll talk about today.

Let's get right into some demos. I have a series of demos that I'll talk about, but we're going to start pretty simple. Here I have our Discovery 2026 space, and it has some reports and some folders for each demo. Let's go right into this Big Class Distribution. If you've used JMP for really any amount of time, you've probably seen an example using this Big Class table.

You might notice right off the bat that our distributions look a little bit off. So 39 out of 40 students here are in this lower bin for height, and we have one student, Jane, who has an abnormal height of 555. We might have some data integrity, data entry problem with that row. Then the same thing for age. These are supposed to be school-age children between 12 and 17, but yet Alice has an age of 31. With the data editor in JMP Live, we're able to tackle that right in JMP Live now.

Something to know about JMP Live is that all the reports are backed by data stored in JMP Live. Anytime that data gets updated, the reports downstream get updated. This is all nicely linked together, so any changes you make will affect downstream reports. This is the table in JMP Live. In version 18 and 19, you could view the data, but you couldn't edit the data. You had to download the data and then make your edits in JMP and then re-upload them to make any changes.

New in 19.5, you can click this Edit button. This enters an edit mode where you can double-click and edit the cells just like in JMP. But it is an exclusive editing session for you, so someone else can't come in and edit this table while you're working on it. Real quickly, let me switch over to another user here. I'm logged in as another user, and it shows that my main account is currently editing the file. Otherwise, there would be an Edit button here. That just shows that we prevent you from clobbering each other's changes in that way.

Let's get back to looking at what the updates we need to make. We noted that Alice, her age looked incorrect, and it looked like these numbers just got transposed, and it's supposed to be 13 instead of 31. Then also for Jane, the height, I think we just have one extra five in here, and that's supposed to be 55. If we were ready to commit these changes, we could save that. But let me say that we're not quite sure if we've got exactly the right data, but we don't want to lose our work.

We can click Save Draft, and this has reverted our changes. We never saved anything out for other users. It's reverted these values back to their original state. Let's say we come back later in the afternoon or tomorrow, and we're ready to commit those changes, we can come back and click Edit. Because I saved that draft, it's going to ask me if I want to restore from a draft. This happens as long as no one else has come in and made any other changes. Now, those changes to Alice and Jane are reapplied.

The other important thing to note about the data editor is that it's still using the power of JMP on the server to input and format your values. If you have range checks, list checks, or number format and date formats, those things will still get applied by JMP on the server and shown in the browser. Really, the simplest validation that I can show you in this table is trying to write some character data into a numeric column. When you do that, JMP on the server will validate that value, and you'll see an error similar to what you would in JMP.

I'll revert that, and everything looks good now, so I'm going to go ahead and save. If we take a look at the reports, it automatically triggered this distribution to be updated, and it looks much better. This looks more normal, and there's no real outliers. This is just a very quick, simple example, but a real use case where you find a data entry problem or a data integrity problem, and you're able to tackle it right here in JMP Live very simply.

Next, I have a more… Sorry, I can get to JMP. I got a more in-depth example of how you can use JMP Live for data collection. I'm going to be playing a couple of different roles. In JMP here, I'm playing the role of an analyst who's trying to do a design of experiment. In this experiment, we're trying to maximize our part strength on our assembly line, and we are able to change the oven temperature, press pressure, and the line speed as factors to try to manipulate the part strength.

If I were able to perform this experiment, the Easy DOE Data Entry tab would be a great place to save my results. But I needed my operator on the production line to perform this experiment for me, and he does not have a JMP license. But now that we have JMP Live, we can have him record his data there. Let's go ahead and export this data. I'm going to rename this table to something more useful. Take a look. This looks good. Let's publish this out to JMP Live.

One of the things that I wanted to share with you in this talk today is the new JMP Live Toolkit add-in. It's available on the JMP Marketplace. It offers a few features, but it also brings the common menu items that you might be used to under the File Publish menu that can be a little bit cumbersome to get to, and now it gives you easier access to that. For now, I'm just going to use this Publish Data to JMP Live. Then I'm going to publish new data. We're going to publish to that same Discovery folder we were looking at earlier, and I'm going to publish to this DOE folder.

We just published that one table. We can open that in JMP Live. It looks good. What I want to do is actually send a message to my operator, his name is Ethan, and say, "Can you perform this experiment for me?" Because he's the one who actually is able to enter these values in terms of finding out the results. But before I switch to the role of Ethan, I want to make sure that he has the proper permissions to be able to actually perform these operations.

We'll see that Ethan has view and download permissions under this Permissions tab. He does need data entry permission if he wants to be able to actually edit. This is a good thing to provide people who you don't want a lot of permission, don't have a lot of permission, but they do need this smaller scope of information. Now we've made sure that Ethan is good to go permission-wise. We'll switch over to Safari, and he's in dark mode, so you can tell when I'm logged in as him.

You might notice that Ethan got a notification that he was mentioned in that comment. That's a good way to use a trigger to find out that he has something to do. You can see that Justin asked him to do this experiment. We already talked about how Ethan has less permissions. He can't see the history or the refresh script settings. He can't upload data, but he does have this very specific data entry capability. He can enter edit mode.

Let's say that he performs the experiment and records a part strength of 81 for the first experiment. He saves that out. Now, anyone who has access to this data table can access these results. Right now, we don't have any reports downstream consuming this data, but we can see the results as they come along.

Now, for the sake of time, let's say that we've completed all 16 of the responses, and we filled out all of our entries, and we save. Ethan's job is done. He has entered these values into JMP Live. He hasn't had to deal with emails or notepads, and he can also utilize the mechanisms in the comments to say that he's all done with all of the experiment. Let's switch back over to my other account, Justin. He also got a notification saying that Ethan replied to my comment. Here when I go to the table, I can see where Ethan responded.

This looks good, but now we want to do some analysis on that, and that's where we need to go back into JMP. I'm just going to close down a few of these things. This data is no longer the latest data, so we'll go ahead and close that. We're done with this DOE. The JMP Live Toolkit, one of the features is to Open from JMP Live. This enables me to open any data table or report from JMP Live right from within JMP.

We were working in this DOE folder, and I want to open this Part Strength DOE. I'm going to click Open. This downloads the table with all of Ethan's responses, and everything looks good there. Since we made this with Easy DOE, we do have the model script that we can run, and it has the pre-populated factors and interactions that we want. We'll just run that, and we can look at the model that was produced. We can play around with the profiler.

But we really want to get this out there as a rough draft, so people can start reviewing it. I'm going to go ahead and publish this report to JMP Live. I'm going to publish a new report, and it's going to automatically choose the last place I was working. That's good. Then I'll take the default title and everything. That looks good.

Because we downloaded this data from JMP Live, it's able to find the data source actually on JMP Live and know that this is the table that we're working with. It also knows that the data is exactly the same as it is on the server. We're not updating the data unnecessarily, nor are we creating any duplicates. We'll go ahead and publish that. We just created the new report. Let's take a look at that.

Everyone who has access to this can now go take a look at it. Everything is interactive just as it was in JMP that you might be used to. Now that that's out there, I actually want to make some additional updates. Maybe this was the next day or so when I had some more ideas about what we wanted to do. Now that we're back in JMP, since I already had this open, that's fine. But if I had come back the next day, I could have used the toolkit to open the report and the data together to reproduce this.

One thing that I want to do under the Prediction Profiler is find our… the main thing we're trying to do is find the best factors for our part strength. I'm going to do maximize desirability. That's going to calculate the best combination of factors there and set them. Then I also under Factor Settings want to append settings to table. That's going to take these settings here, and it's going to add them to our table. I want Ethan to do one more validation run so we can verify that that combination is actually truly the best.

We just had some updates. I'm going to sync those changes. Then the last thing I'm going to do under the top level red triangle menu is Save Columns and Save the Predicted Values. If we go back to our table, we can see the effect that these changes have had. We have one new row with our optimal factors and a missing value for that for Ethan to add. Then we also have predicted part strength. That will give us an idea when we get the result whether it's in line with our expectation.

We're almost ready to publish this back up with the updates we made. But one thing that I could have done before, but I'm going to do now, is standardize the attributes and lock these factors. In JMP, you're able to lock columns so that you prevent them from being edited. These locks can be easily removed in JMP, but in JMP Live, they're not removable without opening in JMP. This is a good way to prevent people with data entry access only to a data table from being able to modify those columns. If we want to prevent Ethan from messing with the factors, we can do that.

To update the report and the data, we can publish the report, and it will do both. But we want to choose Replace an Existing Report. Since it was the last report I worked with, it's right there. We'll keep everything the same. Then again, on the Configure Data step, it's actually still matched up our table to the original table, but this time it knows that the data is not the same and that we've made some additional updates. It's going to suggest that we update the data on JMP Live. That's exactly what we want to do.

Let's go ahead and replace. You can see we updated both there. We can look at our report, and we can see it has those factors values that we set. Then, if we look at the data, it's also going to have that additional row and that additional column. When we go into edit mode, you're going to notice that these three columns that are locked are not editable, but the other columns are. That's just another tool in your tool belt for managing your data when it's being edited on JMP Live.

That was my most in-depth example, but a good example of how you can collect data in JMP Live and have it affect downstream reports immediately. I have three other demos that I'm going to run through, and my goal here was to show you some of the newer features in JMP Live along the way. The next one I'm going to show is Semiconductor Capability of Process Screening.

Process screening is newly interactive in JMP Live 19. When you select the rows on the left, the corresponding control chart show on the left, and you get the same hover help that you do in any interactive chart in JMP Live. But what we're really concerned with today is the data behind these reports. Let's go ahead and look at this data table.

One thing that I'll point out before we look too deeply is that this data table is locked, and that's because the table was locked when it was saved in JMP. You're able to lock and unlock tables in JMP, but the useful thing about that in JMP Live is that you're able to prevent anyone, even people with data entry access, from editing the table. That's just another preventative measure you can take if you don't want something to be edited directly.

This table, it has a lot of semiconductor data. We have lot 1, and we have lot 2 here at the bottom. We currently only have 240 rows. If we look at the settings for this table, it's set up as a simulated database query. I won't go too much into the details, but it's referencing this Selected Lots table here in the script and then also here in the data tables list. Anytime this Selected Lots table updates, it will trigger this one to be updated as well. Let me go ahead and take a look at that.

These really small tables are super easy to work with in JMP Live. If I edit this, I can simply add new rows. This didn't come up in our previous examples, but you can add rows within tables in JMP Live. I want to say lot 03. Because this table is referenced by the other table, when I save it, it's going to automatically trigger this main Semiconductor Capability table to be updated. You can see now that we have 355 rows, and we have lot 3 at the bottom. That's a way that you can use linked tables together in conjunction with the data editor to create a workflow that works for you.

The next example I have is using Control Chart Builder. I mentioned before, it's one of our big new features in JMP Live 19. Control Chart Builder in JMP Live, if you click on the warning, you're actually going to get this warning panel on the side. This gives you the ability to set a status of open, investigating, or addressed for each individual warning in your chart. You can also assign them to individual people or groups of people. We'll close that for now. That information is going to be tracked along with this warning over time.

But we're really concerned about the data here. One different thing about this control chart is that it's a short run control chart. That means that it has product statistics. Product statistics can be calculated by JMP, but it's also able to be referenced by a data table. This might be something that you want to iterate on and tinker with. Let's go take a look at that product statistics table, and it's a pretty small table as well.

Let's say that we want to make some updates to our targets, and we'll say that we want this target for product A to be 20 and the target for product B to be 22. When we save that, we can again look at our downstream reports and see that that is automatically updating, which is great. But we see that we have now two warnings. This one is new because our lower control limit shifted this to be out of control. But this point here looks like the same one we had before, but is now showing as open instead of investigating.

Now, the old warning did not disappear. It just got invalidated. That's because the centered weight for that point was previously -3.23, and it's now -3.5. This is just something you have to watch out for when you're changing anything that's going to affect your control limits. JMP Live is going to force you to remake a previously made decision on something that has shifted. This example just shows how you can use these small tables that might be used as part of certain platforms, and those things are good candidates for managing and editing them on JMP Live.

Then I just have one more example for us using the Word Cloud that's part of the Text Explorer platform. Here I have a table of manufacturing operator incidents. Right now, the Word Cloud isn't really saying that anything is standing out. But let's say that we're using JMP Live actually as the data collection mechanism for recording these incidents. Say we had a new incident that we wanted to record. I can add a row at the end here. This one happened on Press 2 on Shift B, and it had excessive vibration and noise near the press.

When we save that, once again, our downstream reports are going to be updated. Immediately when this is finished refreshing, you can see the immediate impacts of adding that new data, we now see that noise, press, and vibration are the most common words that seem to come up in these incidents. Another example of how you can use the data editor for data collection.

Let's shift back to our slides here. I have one more slide to talk about how data analysis and the data collection can work once you have JMP Live set up at your organization. Of course, you still have your data analysis to do, done by your scientists and engineers. They still love JMP. They just love JMP Live, too. They're able to publish to JMP Live and share with their colleagues.

We have what we talked about today. That's the manual data collection, operators and technicians. They actually are able to access JMP Live as part of the license agreement for JMP Live without the additional cost of getting a full JMP license. Much easier for them to get JMP Live once it's set up at your organization. You also are still going to have your automated data collection, and we talked about how these automated refresh scripts can help access that data, and JMP Live just helps in keeping things up to date.

The whole original concept of JMP Live was for sharing your analysis, and this is just an added benefit, bringing in management and other analysts, having good visibility over all of your reports in JMP Live. That was an overview of how you can use the data editor, and hopefully that's helpful for you. That's all I had, and thank you for your time.

0 Comments
Presented At Discovery Summit 2026

Presenter

Skill level

Beginner
  • Beginner
  • Intermediate
  • Advanced
Published on ‎07-15-2026 03:39 PM by Community Manager Community Manager | Updated on ‎10-30-2026 03:34 PM

Keeping your JMP analyses connected and current can be challenging, especially when updates are captured in spreadsheets, emails, or handwritten notes. This presentation explores new capabilities that make it easier to move quickly from updated data to insight when managing shared data between JMP and JMP Live.

With JMP Live 19.5, data tables can be edited directly in the browser, removing the need to collect updates offline. Contributors without JMP can make meaningful changes, such as updating specification limits or adding new experiment results, right inside JMP Live. These changes flow automatically to linked reports and analyses, helping teams keep results aligned with the latest data.

Beyond basic editing, this session also looks at how the JMP Live data editor supports real-world collaboration, including permissions, column and table locking, and other features to help teams manage shared data. It will also highlight how JMP users can work with JMP Live content directly from JMP using the Toolkit add-in, making it easier to review and update shared data.

Together, these capabilities help teams manage, share, and maintain connected analyses. This session shows how to use JMP Live’s data editing feature and the Toolkit, with concrete examples that attendees can adapt to improve their own data workflows.

 

 

Hi, my name is Justin Chilton. I'm a software developer here at JMP working on JMP Live. Today, I wanted to share with you a new feature available now in JMP Live called the Data Editor. Mostly, I'm going to be showing some demos with you in JMP Live today, but I do have some slides to give us a little bit of background before we get started.

First, if you're not familiar with JMP Live at all, really, I'll let you know that it's a secure collaboration platform in your browser built to share JMP content with colleagues and bring that same interactivity to those who might not have JMP, like managers. It includes interactive features like data filters and column switchers.

But in recent years, we've added several new features, like Spaces, which help with the content organization, automated data refresh, which helps keep your data as up to date as possible, and most recently in JMP Live 19, we added control chart warning triage, which allows you to track your warnings through time. We've added a lot of new things on top of the interactivity.

You may or may not have known that we released a new version of JMP Live, 19.5, this past summer. It's a release between JMP 19 and the upcoming JMP 20. It's a feature release that's fully compatible with JMP 19. The latest release is actually running JMP 19.2, so anything that's compatible with 19.2 will work in JMP Live 19.5. This faster delivery of features allowed us to bring all these features I've listed here. But the one I'm going to talk about today mostly is the data editor.

Let's talk about the reality of how data analysis and data collection might work within an organization. Obviously, the main goal is to do some analysis. These folks might be data scientists and engineers doing this work. They all know that JMP is a great and maybe the best tool for doing this. They're very happy using JMP. But where does the data come from that they need to perform the analysis?

Probably the most common place is some automated data source. This could be a database that you're pulling from, or it could be some generated files like Excel files or CSV. JMP Live already has a lot of features, like I talked about the refresh capabilities, to get at that data. But what about the messier places that data comes from?

This might be from your operators or technicians who don't have JMP. They might have Excel, they might send you data via email, they might even write it on a sticky note or notepad. This way of collecting data is very error-prone and can get lost in translation between the operators and your analysts. This is the problem that we're trying to tackle, or one of the problems we're trying to tackle with the data editor, and one thing we'll talk about today.

Let's get right into some demos. I have a series of demos that I'll talk about, but we're going to start pretty simple. Here I have our Discovery 2026 space, and it has some reports and some folders for each demo. Let's go right into this Big Class Distribution. If you've used JMP for really any amount of time, you've probably seen an example using this Big Class table.

You might notice right off the bat that our distributions look a little bit off. So 39 out of 40 students here are in this lower bin for height, and we have one student, Jane, who has an abnormal height of 555. We might have some data integrity, data entry problem with that row. Then the same thing for age. These are supposed to be school-age children between 12 and 17, but yet Alice has an age of 31. With the data editor in JMP Live, we're able to tackle that right in JMP Live now.

Something to know about JMP Live is that all the reports are backed by data stored in JMP Live. Anytime that data gets updated, the reports downstream get updated. This is all nicely linked together, so any changes you make will affect downstream reports. This is the table in JMP Live. In version 18 and 19, you could view the data, but you couldn't edit the data. You had to download the data and then make your edits in JMP and then re-upload them to make any changes.

New in 19.5, you can click this Edit button. This enters an edit mode where you can double-click and edit the cells just like in JMP. But it is an exclusive editing session for you, so someone else can't come in and edit this table while you're working on it. Real quickly, let me switch over to another user here. I'm logged in as another user, and it shows that my main account is currently editing the file. Otherwise, there would be an Edit button here. That just shows that we prevent you from clobbering each other's changes in that way.

Let's get back to looking at what the updates we need to make. We noted that Alice, her age looked incorrect, and it looked like these numbers just got transposed, and it's supposed to be 13 instead of 31. Then also for Jane, the height, I think we just have one extra five in here, and that's supposed to be 55. If we were ready to commit these changes, we could save that. But let me say that we're not quite sure if we've got exactly the right data, but we don't want to lose our work.

We can click Save Draft, and this has reverted our changes. We never saved anything out for other users. It's reverted these values back to their original state. Let's say we come back later in the afternoon or tomorrow, and we're ready to commit those changes, we can come back and click Edit. Because I saved that draft, it's going to ask me if I want to restore from a draft. This happens as long as no one else has come in and made any other changes. Now, those changes to Alice and Jane are reapplied.

The other important thing to note about the data editor is that it's still using the power of JMP on the server to input and format your values. If you have range checks, list checks, or number format and date formats, those things will still get applied by JMP on the server and shown in the browser. Really, the simplest validation that I can show you in this table is trying to write some character data into a numeric column. When you do that, JMP on the server will validate that value, and you'll see an error similar to what you would in JMP.

I'll revert that, and everything looks good now, so I'm going to go ahead and save. If we take a look at the reports, it automatically triggered this distribution to be updated, and it looks much better. This looks more normal, and there's no real outliers. This is just a very quick, simple example, but a real use case where you find a data entry problem or a data integrity problem, and you're able to tackle it right here in JMP Live very simply.

Next, I have a more… Sorry, I can get to JMP. I got a more in-depth example of how you can use JMP Live for data collection. I'm going to be playing a couple of different roles. In JMP here, I'm playing the role of an analyst who's trying to do a design of experiment. In this experiment, we're trying to maximize our part strength on our assembly line, and we are able to change the oven temperature, press pressure, and the line speed as factors to try to manipulate the part strength.

If I were able to perform this experiment, the Easy DOE Data Entry tab would be a great place to save my results. But I needed my operator on the production line to perform this experiment for me, and he does not have a JMP license. But now that we have JMP Live, we can have him record his data there. Let's go ahead and export this data. I'm going to rename this table to something more useful. Take a look. This looks good. Let's publish this out to JMP Live.

One of the things that I wanted to share with you in this talk today is the new JMP Live Toolkit add-in. It's available on the JMP Marketplace. It offers a few features, but it also brings the common menu items that you might be used to under the File Publish menu that can be a little bit cumbersome to get to, and now it gives you easier access to that. For now, I'm just going to use this Publish Data to JMP Live. Then I'm going to publish new data. We're going to publish to that same Discovery folder we were looking at earlier, and I'm going to publish to this DOE folder.

We just published that one table. We can open that in JMP Live. It looks good. What I want to do is actually send a message to my operator, his name is Ethan, and say, "Can you perform this experiment for me?" Because he's the one who actually is able to enter these values in terms of finding out the results. But before I switch to the role of Ethan, I want to make sure that he has the proper permissions to be able to actually perform these operations.

We'll see that Ethan has view and download permissions under this Permissions tab. He does need data entry permission if he wants to be able to actually edit. This is a good thing to provide people who you don't want a lot of permission, don't have a lot of permission, but they do need this smaller scope of information. Now we've made sure that Ethan is good to go permission-wise. We'll switch over to Safari, and he's in dark mode, so you can tell when I'm logged in as him.

You might notice that Ethan got a notification that he was mentioned in that comment. That's a good way to use a trigger to find out that he has something to do. You can see that Justin asked him to do this experiment. We already talked about how Ethan has less permissions. He can't see the history or the refresh script settings. He can't upload data, but he does have this very specific data entry capability. He can enter edit mode.

Let's say that he performs the experiment and records a part strength of 81 for the first experiment. He saves that out. Now, anyone who has access to this data table can access these results. Right now, we don't have any reports downstream consuming this data, but we can see the results as they come along.

Now, for the sake of time, let's say that we've completed all 16 of the responses, and we filled out all of our entries, and we save. Ethan's job is done. He has entered these values into JMP Live. He hasn't had to deal with emails or notepads, and he can also utilize the mechanisms in the comments to say that he's all done with all of the experiment. Let's switch back over to my other account, Justin. He also got a notification saying that Ethan replied to my comment. Here when I go to the table, I can see where Ethan responded.

This looks good, but now we want to do some analysis on that, and that's where we need to go back into JMP. I'm just going to close down a few of these things. This data is no longer the latest data, so we'll go ahead and close that. We're done with this DOE. The JMP Live Toolkit, one of the features is to Open from JMP Live. This enables me to open any data table or report from JMP Live right from within JMP.

We were working in this DOE folder, and I want to open this Part Strength DOE. I'm going to click Open. This downloads the table with all of Ethan's responses, and everything looks good there. Since we made this with Easy DOE, we do have the model script that we can run, and it has the pre-populated factors and interactions that we want. We'll just run that, and we can look at the model that was produced. We can play around with the profiler.

But we really want to get this out there as a rough draft, so people can start reviewing it. I'm going to go ahead and publish this report to JMP Live. I'm going to publish a new report, and it's going to automatically choose the last place I was working. That's good. Then I'll take the default title and everything. That looks good.

Because we downloaded this data from JMP Live, it's able to find the data source actually on JMP Live and know that this is the table that we're working with. It also knows that the data is exactly the same as it is on the server. We're not updating the data unnecessarily, nor are we creating any duplicates. We'll go ahead and publish that. We just created the new report. Let's take a look at that.

Everyone who has access to this can now go take a look at it. Everything is interactive just as it was in JMP that you might be used to. Now that that's out there, I actually want to make some additional updates. Maybe this was the next day or so when I had some more ideas about what we wanted to do. Now that we're back in JMP, since I already had this open, that's fine. But if I had come back the next day, I could have used the toolkit to open the report and the data together to reproduce this.

One thing that I want to do under the Prediction Profiler is find our… the main thing we're trying to do is find the best factors for our part strength. I'm going to do maximize desirability. That's going to calculate the best combination of factors there and set them. Then I also under Factor Settings want to append settings to table. That's going to take these settings here, and it's going to add them to our table. I want Ethan to do one more validation run so we can verify that that combination is actually truly the best.

We just had some updates. I'm going to sync those changes. Then the last thing I'm going to do under the top level red triangle menu is Save Columns and Save the Predicted Values. If we go back to our table, we can see the effect that these changes have had. We have one new row with our optimal factors and a missing value for that for Ethan to add. Then we also have predicted part strength. That will give us an idea when we get the result whether it's in line with our expectation.

We're almost ready to publish this back up with the updates we made. But one thing that I could have done before, but I'm going to do now, is standardize the attributes and lock these factors. In JMP, you're able to lock columns so that you prevent them from being edited. These locks can be easily removed in JMP, but in JMP Live, they're not removable without opening in JMP. This is a good way to prevent people with data entry access only to a data table from being able to modify those columns. If we want to prevent Ethan from messing with the factors, we can do that.

To update the report and the data, we can publish the report, and it will do both. But we want to choose Replace an Existing Report. Since it was the last report I worked with, it's right there. We'll keep everything the same. Then again, on the Configure Data step, it's actually still matched up our table to the original table, but this time it knows that the data is not the same and that we've made some additional updates. It's going to suggest that we update the data on JMP Live. That's exactly what we want to do.

Let's go ahead and replace. You can see we updated both there. We can look at our report, and we can see it has those factors values that we set. Then, if we look at the data, it's also going to have that additional row and that additional column. When we go into edit mode, you're going to notice that these three columns that are locked are not editable, but the other columns are. That's just another tool in your tool belt for managing your data when it's being edited on JMP Live.

That was my most in-depth example, but a good example of how you can collect data in JMP Live and have it affect downstream reports immediately. I have three other demos that I'm going to run through, and my goal here was to show you some of the newer features in JMP Live along the way. The next one I'm going to show is Semiconductor Capability of Process Screening.

Process screening is newly interactive in JMP Live 19. When you select the rows on the left, the corresponding control chart show on the left, and you get the same hover help that you do in any interactive chart in JMP Live. But what we're really concerned with today is the data behind these reports. Let's go ahead and look at this data table.

One thing that I'll point out before we look too deeply is that this data table is locked, and that's because the table was locked when it was saved in JMP. You're able to lock and unlock tables in JMP, but the useful thing about that in JMP Live is that you're able to prevent anyone, even people with data entry access, from editing the table. That's just another preventative measure you can take if you don't want something to be edited directly.

This table, it has a lot of semiconductor data. We have lot 1, and we have lot 2 here at the bottom. We currently only have 240 rows. If we look at the settings for this table, it's set up as a simulated database query. I won't go too much into the details, but it's referencing this Selected Lots table here in the script and then also here in the data tables list. Anytime this Selected Lots table updates, it will trigger this one to be updated as well. Let me go ahead and take a look at that.

These really small tables are super easy to work with in JMP Live. If I edit this, I can simply add new rows. This didn't come up in our previous examples, but you can add rows within tables in JMP Live. I want to say lot 03. Because this table is referenced by the other table, when I save it, it's going to automatically trigger this main Semiconductor Capability table to be updated. You can see now that we have 355 rows, and we have lot 3 at the bottom. That's a way that you can use linked tables together in conjunction with the data editor to create a workflow that works for you.

The next example I have is using Control Chart Builder. I mentioned before, it's one of our big new features in JMP Live 19. Control Chart Builder in JMP Live, if you click on the warning, you're actually going to get this warning panel on the side. This gives you the ability to set a status of open, investigating, or addressed for each individual warning in your chart. You can also assign them to individual people or groups of people. We'll close that for now. That information is going to be tracked along with this warning over time.

But we're really concerned about the data here. One different thing about this control chart is that it's a short run control chart. That means that it has product statistics. Product statistics can be calculated by JMP, but it's also able to be referenced by a data table. This might be something that you want to iterate on and tinker with. Let's go take a look at that product statistics table, and it's a pretty small table as well.

Let's say that we want to make some updates to our targets, and we'll say that we want this target for product A to be 20 and the target for product B to be 22. When we save that, we can again look at our downstream reports and see that that is automatically updating, which is great. But we see that we have now two warnings. This one is new because our lower control limit shifted this to be out of control. But this point here looks like the same one we had before, but is now showing as open instead of investigating.

Now, the old warning did not disappear. It just got invalidated. That's because the centered weight for that point was previously -3.23, and it's now -3.5. This is just something you have to watch out for when you're changing anything that's going to affect your control limits. JMP Live is going to force you to remake a previously made decision on something that has shifted. This example just shows how you can use these small tables that might be used as part of certain platforms, and those things are good candidates for managing and editing them on JMP Live.

Then I just have one more example for us using the Word Cloud that's part of the Text Explorer platform. Here I have a table of manufacturing operator incidents. Right now, the Word Cloud isn't really saying that anything is standing out. But let's say that we're using JMP Live actually as the data collection mechanism for recording these incidents. Say we had a new incident that we wanted to record. I can add a row at the end here. This one happened on Press 2 on Shift B, and it had excessive vibration and noise near the press.

When we save that, once again, our downstream reports are going to be updated. Immediately when this is finished refreshing, you can see the immediate impacts of adding that new data, we now see that noise, press, and vibration are the most common words that seem to come up in these incidents. Another example of how you can use the data editor for data collection.

Let's shift back to our slides here. I have one more slide to talk about how data analysis and the data collection can work once you have JMP Live set up at your organization. Of course, you still have your data analysis to do, done by your scientists and engineers. They still love JMP. They just love JMP Live, too. They're able to publish to JMP Live and share with their colleagues.

We have what we talked about today. That's the manual data collection, operators and technicians. They actually are able to access JMP Live as part of the license agreement for JMP Live without the additional cost of getting a full JMP license. Much easier for them to get JMP Live once it's set up at your organization. You also are still going to have your automated data collection, and we talked about how these automated refresh scripts can help access that data, and JMP Live just helps in keeping things up to date.

The whole original concept of JMP Live was for sharing your analysis, and this is just an added benefit, bringing in management and other analysts, having good visibility over all of your reports in JMP Live. That was an overview of how you can use the data editor, and hopefully that's helpful for you. That's all I had, and thank you for your time.



Start:
Tue, Oct 20, 2026 03:30 PM EDT
End:
Tue, Oct 20, 2026 04:15 PM EDT
Key Ballroom 10
0 Kudos