MOX Metrology Process Studio (MPS) Demo

Welcome to this demonstration of the Box neurology process Studio or MPS as we like to call it I'm Kurt Casto I'm the designer of the NPS software architecture box MPS is the technical part of the mock system it's used to design and execute the calibrations there are two principal kinds of documents in MPS data sheets these are the templates for calibrations that include the test points specifications Instructions and optionally automation scripting to automate the calibrations and then there are calibration documents these are the actual recording of measurement data performed during calibrations and that data is

saved as a calibration document box MPS uses a Microsoft SQL Server database to storage data optional you can also save these as files there are two ways to launch MPS either directly or if you're using MOX CMS when you go to perform a calibration Within MOX CMS there's an option to have it launch NPS with the appropriate datasheet template and everything loaded ready to perform the calibration however if you don't have MOX CMS or you're just going to be designing data sheets or something like that you can just launch MPS directly which is what we're

going to do now so we'll click on its icon to launch MPS and then we'll go ahead and log into MPS using our CMS authentication as a CMS user If you want to perform a calibration in MPS the first thing you'll want to do is open an existing datasheet template and you do that by going up here to file datasheet template open template from DB and this brings up our datasheet document selector and then we can actually choose a data sheet using one of several criteria we can look it up by model manufacturer description a

key thing about data sheets is that what you're working with Them you'll be saving them as files but eventually you'll approve them into the database assuming you have permissions to approve them if not you give them to somebody else to approve and then once they're in the database they can be used to perform calibrations so we'll go ahead and just search by model number so we'll enter 77 and then when I type something in and I either hit enter or click on the search button it will show me all the data sheets that start with

What I selected or you can choose other things like exact match or contains so if I select this data sheet it loads the data sheet this is the calibration Channel editor and it's asking me to provide a test number and an asset ID now once again if you're actually using MOX CMS then you don't have to do all this process we just did manually you would just launch the calibration from CMS and then it would automatically open the appropriate data sheet and fill out All of the information here for you I'm just going to go

ahead and cancel this we're not going to actually perform a calibration right now just going to show you some things about MPS so there are two principal modes in MPS there's the calibration mode which you see here and comes up by default and then appear under mode and you can also come up here and select the design node and in the design mode this is where we would actually construct the data sheet and All of its test points and there are various Tools in here to do that but we'll talk about these tools in more

detail in a later part of the demonstration while you're working with data sheets what you'll normally do is you will save them as files so import export the file if you come back the next day and you continue working on the data sheet you'll import it from a file and then eventually when the data sheet is completed if you have the necessary Permissions or you can send a datasheet file to someone else that has the necessary permission and they can approve it into the database when you do approve a data sheet you would just go

to file datasheet template approve template to DB and then you can either approve it as a revision or approve it as a new document let's switch back to the calibration mode and let's actually execute a calibration launched from CMS this is CMS and as I said this is not a CMS demo we're just storing what we need to do to demonstrate performing a calibration lunch for CMS this is the work order view in CMS and I've got an work order opened here for a digital multimeter so we're going to launch this calibration in MPS to

actually perform the calibration I right click and I choose launch MPS this will actually launch the MPS application MPS was launched the appropriate data Sheet was loaded and it filled out the test number and the asset ID and the other make model information so we'll go ahead and hit OK to begin that calibration this particular data sheet is an automated data sheet and you can always tell that because in the step number field here you see these teal regions these are all places where I can start the automation scripting from and you can also see

the button appear to start the automation scripting and we'll Just actually start at the DC voltage test the first thing I need to do is tell it about the calibration standard I'm using now this particular data sheet is set up with one calibration standard a calibrator and you can see down here below I have four different calibrators to choose from so I'm going to go ahead and start with the selected fluke 5522 calibrator we'll enter the asset ID for that and when I hit enter if you're using MOX CMS it Will automatically go off the

CMS and look up that particular asset ID and get the due date for me and when I hit yes you can see it fills in the due date once I've set up my standards I can go ahead and just turn off this view of this workspace and in MPS your primary workspace tools are always on this right side whether you're in calibration mode or design mode I'm going to go to view and then I'm going to uncheck the developer workbench so it turns that off That allows me to see more as I said this is

an automated data sheet and we're going to use that to record a couple of data points we'll stop it after it records a couple of data points just in the interest of time let's go ahead and hit our run button and this will start the automation script running these are my instructions and here's an image of how to actually connect the equipment let's hit continue and as I said we'll just take let it Take a couple of data points and then we'll hold it and you can see this little status indicator over here just shows

what it's doing mostly it's spending its time you know waiting for stabilization and whatnot I'm going to go ahead and hit alt you can see as we were taking our measurements our as found values were being filled in here in the datasheet template and then some other information this is a conformance diagram and then In this channel status column you see we've got this box that's divided into two halves the top half is as found and the bottom half is ass left indicating that the green meaning that our as found values were intolerance and the

white and the as left indicating we haven't taken or captured as left data yet MPS is a multi-channel system you can actually perform calibrations on multiple instruments at the same time that would be applicable to something Like thermocouples where you have three or four thermocouples in the bath at the same time in which case you can open multiple channels and then you would see a set of boxes for each of those channels here one of the key things about MPS is that you can change calibration standards at any time during the calibration if we had

gone through and taken all of our as found data we have two options after that if everything was in tolerance and we're Not going to adjust then we can come up to copy as found as left and just have it copy all of the aspound data into the as left measurements however we're going to choose as left and then I'm going to go back to view here and I'm going to bring up my developer workbench again and this time we're actually going to choose a different standard to take our as left with so I can

illustrate a few things to you for the as left data recording I'm going to choose the fluke 5500 calibrator we select the 5500 here and then we hit use selected instrument and then we're going to enter the asset ID for the fluke 5100 now I should tell you that the fluke 5500a really is a good bit less accurate than the other standards in here and it's really not a good choice for this calibration however I have it in here for demonstration purposes because this is going to let me illustrate some other things So let's go

ahead and turn off our workspace view again let's come back up and choose our DC voltage tests and now we're in as left mode so let's collect just a few as left data points again the same thing in the interest of time we'll just collect a few points and you can see as this is running you can see the conformance diagram being updated as we go and then this section over here the tolerance percent what this is let me go ahead and hold this This is just telling me the percentage of the tolerance consumed so

now we'll go ahead and bring our developer workbench back up our workspace and then I'm going to actually choose standards used measurements made this is going to give me detailed information about the measurements that were made for this test point a key point in MPS is that it's largely test Point Centric and what I mean by that is whenever I choose different test points you can see that Whether it be this section or this section up here or this over here gets updated with whichever test point I'm on so everything is pretty much driven by

the currently selected test point one thing I want to point out here is if you notice this section at the top up here showing detail for our as found and as left measurements but you'll notice a difference for our as found and as left measurements for our as found measurement we have our tolerance is not Guard banded but are as left tolerance was automatically guard banded and this is again why I wanted to use that fluke 5500 for demonstration purposes because of the 5500 you can see it's t-u-r is only 2.5 to 1. and its

PFA is above our Target 0.8 percent so MPS automatically guard banded it and where you can see our as found measurement our tur was 9.71 and our PFA was only 0.39 percent as I said about the 5500 again in the Real world you wouldn't really use a 5500 with this particular calibration if you had these better calibration standards but for demonstration purposes only it lets me illustrate some things that I need to illustrate viewing the detailed information on the right over here for the measurements made you can see we actually have two sections in here

as found and as left and each of these is showing detail about that particular measurement so for Our as found you can see the standards used which was our fluke 5522 calibrator is specifically this asset with this due date and then the tar for this was 7.6 to 1 and the accuracy of the standard was 5 microvolts specifically at 200 millivolts our set point and this is actually showing me which function and range of the 5522 calibrator was used and even the specifications for that Range and we will be talking about where all this comes

from a little later for the uncertainty model MPS has two items in the uncertainty budget here it has the measurement resolution and the calibrator that's being used in this case the fluke 5522 one thing I should tell you at this point is that everything you see in the budget here was done automatically by MPS it created these budget items and it's managing them and if we were doing sampling then It would automatically have option to insert a type a budget item for the standard deviation of the samples and we'll talk about sampling a little later

but if these test points were configured for sampling say we wanted to take five samples then another section would appear in here that would actually show the samples being taken and a graphic display of the sampling data and then the mean value of the samples would be the measured value and the standard Deviation of the samples would be added as a type a budget item in the uncertainty model and then another section that you can see displayed here is risk and in this case we have our probability of false accept and our probability of false

reject total risk and K which is essentially our guard band multiplier we're not guard banding so it's a hundred percent in the as left section it's very similar to the as found except our calibration standard Used was the fluke 5500 calibrator as opposed to the 5522 calibrator for asphalt the accuracy of the 5500 at 200 millivolts DC was 15 microvolts as opposed to 5 microvolts and then in the uncertainty model very similar to the as found uncertainty model except instead of having the 5522 calibrator automatically added to the budget it added a budget item for

the 5500 calibrator for the risk we guard Bandit The method used was the ancz540.3 MPS supports three guard band methods the NCC 540.3 the rp10 and RSS the ANSI z540.3 method will guard band just enough to return to your target PFA one of the things I hope you're asking yourself at this point is how does it know all this I told you that everything that you see in here is done automatically by MPS we didn't have to manually edit the uncertainty budgets we didn't have to manually calculate these Standards accuracies or any of this in

this demonstration I'm going to actually walk you through this process and show you how these things come to be so if we completed our calibration the next thing we would do is we would need to save our calibration in the database I'm going to come up here and click on Save Channel you can see I have some indications here some red indications indicating potential issues that I'm missing data we're going to go ahead and Hit OK just again for demonstration purposes when I come up this needs to actually be signed and there are two options

for sign sign not complete this would be if you're just quitting for the day and you're going to come back and work on it tomorrow but you want to save it in the database however if you're finished with the calibration you would do sign complete lock in order to complete the calibration in CMS the MPS calibration has to be signed completely locked so I'm going to go ahead and hit sign complete lock this is an e-signature so I have to authenticate now that the calibration is signed I'll just hit OK and then the next step

would be to go back to CMS and close out the calibration but this isn't a CMS demonstration so we aren't going to actually do that our next step is going to be to go to design mode and talk About how data sheets are built and that's how all of these automatic things that I talked about in the uncertainty model and standards accuracies and everything work we're in design mode now the next thing we're going to want to do is go to edit and enable edit mode here on the right hand side of the screen we

have our developer workspace and these are our basic editing Tools in addition to things like manually inserting test Points and copying and pasting over here we'll come back and talk about these but for our main tools we have the datasheet properties this is our datasheet document Header information like manufacturer model description specification reference that applies and then information about the calibration procedure that's associated with the data sheet we have our test Point Builder and the test Point Builder is the tool that You'll use for building most of your test points that is the quantitative test

points we have various properties about the test point for instance its specification information you can see it's .015 percent of indicated value the full scale value is 200 millivolts and the full scare full scale error is 0.04 percent test Point uncertainty this is where you actually manage the uncertainty budget now MPS by default is going to be set to Use model defaults and when you do that it's going to automatically manage the uncertainty budget for you and we'll be talking about this in a little more detail later but just know that if you have this

on everything will happen automatically you don't have to just use the automatic features you can either turn the use model defaults off and decide which automatic elements if any you want to use and also manually add other Additional budget items foreign standards this is where we actually assign calibration standards to the data sheet so here we have that one meter calibrator and then here we have these different instruments that can be the meter calibrator these are selectable options by the user at the time of calibration that we want to support if we click on this

assign Standards test Point tab this will show us the actual standard ranges assigned to the individual test point when I choose different test points you can see it's showing me the information for the test point that I currently have selected so you can see that for this test point we have one range assigned for each of these supported standard instruments so for the meter calibrator the user can select the 5700 and MPS knows that the 220 Millivolt DC range is applicable and knows what the specifications are for that range and then for the 5500 as

we talked about you can see here that tar as we mentioned before is really not an appropriate standard for this but again it's in here for demonstration purposes in red you can see that 2.5 to 1 t u r to stand out is a warning flag to you one of the things you might be asking yourselves at this point okay so we have range for each of these instruments Assigned to the test points I mean how difficult is it to do this for every test point in the data sheet this leads us to a tool

that comes with MPS called bet spec it's a system for digital instrument specifications here you can see we've got a Hewlett Packard 34401 multimeter and these are its specifications for instance if I look at voltage DC I've got you know 100 millivolt range and one Volt range a 10 Volt range so if I open one of these Ranges you can see I've got parametric limits for the range 0 to 12 volts essentially and then I have two different accuracy specifications one per 90-day specifications and one for one year here and if I click on the

90-day specification and if you look over here on the right these are the specification components for it all right so full scale is 10 it's percent of indicated value and it's percent of full scale again we can use floor error And DB logarithmic and equations if necessary for each range now I want to talk briefly about something a little more complicated which is like ac voltage because in ac voltage just like in the manufacturer's manual if you look at the specifications you know you'll see you have a hundred millivolt range but then you have sub

bands for frequency okay and that's how this works in MPS also that spec comes with MPS by the way it's not something you have to Buy separately we have I think about 650 of these that come with uh MPS and of course you can create your own the most important thing to know right now about medspec are these parametric limits for this hundred millivolts 5 Hertz 10 Hertz range you can see there are two parameters you've got the five to 120 millivolts and then 5 Hertz to 10 Hertz these Define the parametric limits for the

range and of course the first parameter is always the quantitative Parameter that's what's being measured or outputted the second to end there were more than one would be the qualifiers and the fact that this is millivolts and the qualifier is frequency makes it an AC range If This Were the other way around IF frequency were the first parameter and millivolts was the second parameter we would be talking about a frequency range because the quantitative parameter would be frequency The reason I'm going into such detail on this is this is very important to understand how MPS

is actually going to use this information to find suitable ranges for calibration standards or you automatically so now that you know a little bit about medspec what you should know is that these are all bet spec instruments that are assigned to the data sheet here we have our if we pop back to the DC standards we've got our calibrator and Of course supported medspec instruments that can be the calibration standard the user can select at the time of calibration one of the primary uses for these metspec instruments are as calibration standards in MPS and that's

what they're used for the most however if you have a metspec instrument you can also use it to build the data sheet for it in MPS in the test Point Builder there's a button where I can choose a metspec range and have it load the test Point Builder to actually create test points using the metspec instruments specifications another important factor when you're using medspec instruments as calibration standards in MPS is that NPS and medspec have a units of measure conversion system built into it if for instance I have a test point that was .005 volts

and here I have a range that covers five millivolts then it's not a problem because MPS will automatically convert between volts and millivolts the Same thing applies to my frequency band that's this is uh 10 Hertz here but if the frequency in the MPS test point was specified is 0.01 kilohertz it wouldn't matter because it can convert between those now that doesn't sound like such a big deal but it gets more involved when you get into things like a degree C and degrees F which are also no problem because it can automatically convert those MPS

has a tool that's available both Actually in MPS and medspec a units converter so if I actually choose for instance length and I choose meters and then I choose foot okay you can see one meter is 3.2 whatever feet and if I enter 2 meters I see two feet this tool is Handy to use but the reason I'm showing it to you is just to illustrate how MPS does these conversions in real time if I go to temperature and I choose degree C and Then I choose degrees F as a Target and if I choose

25 degrees C you can see that that's 77 degrees F and this is happening all the time in the background I won't get into a lot of detail on units of measure but there is actually a unit of measure management system built into netspec metspec manages the units of measure for the mock system that that's all I'm going to say about this this is uh too detailed for our demo but just know that this exists and you can Add your own units of measure as well so the encounter some uncommon unit of measure and you

want to add add it as a unit of measure you can certainly do that and then the last point on medspec is just a reminder about these parameters that I was telling you because this is involved in something I'm going to show you in a bit about how MPS can Auto assign medspec ranges so now that you're familiar with medspec And we've talked about instrument ranges assigned to test points let's talk about how this is done so what I'm going to do is I'm actually going to pick a series of test points so these DC

voltage test points and I'm going to tell MPS to forget everything it knows about these standards one thing before I do this you'll notice that you know we have our t-a-r-s-t-u-r-semus and PFA and pfr and All of that stuff so when I hit yes you'll notice that all of that is gone and the reason that all of that is gone is there's no information about the calibration standards so consequently there's no information about them automatically being put in the uncertainty model so now the question is how do I actually assign these ranges from the different

instruments how difficult is that well there's an auto assign tool here When I click on this for the test points or test points that I have selected or optionally all test points if I was doing a simple say DMM and I just wanted it to assign the standards for all the test points at once I could do that but here we're just going to work with the selected ones now here we just have one calibration standard a meter calibrator and I'm going to select that and that by default selects all the instruments which I wanted

to do so now when I do This and hit OK let me tell you what's going to happen for each test Point that's in here it has its own parameters here in this case there's just one parameter for this last test point which is the Thousand Volt range right so it's a thousand volts when I hit OK what's going to happen is starting with the first test point MPS and and the first calibration standard instrument here MPS is going to Look at every range in this instrument and find every range that's a parametric match so

essentially DC One parameter for voltage and then for every range that's a parametric match it will calculate the accuracy actually at that specific set point using the spec components stored in the best spec range once it's done that for each of the ranges that are a parametric match it will choose the most accurate and assign it then it will do that for these other Three standards and then it will go on to the second test point and repeat the process so on and so forth for each of the selected test points so when I hit

OK you can see it's done now it's automatically selected appropriate ranges for each of those and then now you'll notice I've got my tars back my t-u-r-gmus pfas and pfrs when I look at my test Point uncertainty budgets now you can see that the 5522 calibrator is in The uncertainty budget automatically and if again if I go back to the standards you can see that's because the 5522 is the currently selected standard if I choose the 5500 a you'll notice first off that this test Point its tolerance right now is not guard banded because the

5522 is selected when I select this standard the 5500 as the selected standard you can see that it automatically guard banded all Of these test points and now when I look at the test Point uncertainty budget you can see that the 5500 is now in there instead of the 5522 the blue line that you see here is actually an influence chart it's just showing the relative weight of items in the uncertainty budget now one other quick thing while we're here for the uncertainty is just to talk a little bit more about these uh options For

the uncertainty model as I said we're using model defaults if we click on edit for the uncertainty budget and I choose turn off use model defaults then you can see that I can change which of these options automatically appear in the budget and the other one is a repeatability from resolution this is one of three ways that you can do repeatability in MPS and when you would use this is essentially if you have no Other information you want to include a repeatability item but you have no real data to support it so this would essentially

put in a repeatability item using a one count of the measurement resolution and it's just essentially like measurement resolution but you know with a different label and then the measurement samples this is what I was talking about when we were in calibration mode if this test point is configured for sampling at the time of Calibration the standard deviation of the samples will get added as a type a budget item MPS also supports the the use of degrees of freedom that's optional you also have two different types of uncertainty models you have budget items which is

by far the most common type and then you also have multiple test Point measurement equations which we'll talk about later once you turn off use model defaults Then you can also manually add budget items so you can add additional budget items and we're going to come back and do that in a later example so I won't talk about that now so now that we've assigned all of our ranges for this standard we're going to take it up a notch by showing you what happens if you use two standards at the same time so I'm going

to come here to my advantage standards and I'm actually going to add another instrument And I'm going to call it the monitoring DMM normally in the real world if you had a monitoring DMM or a calibrator you'd only be really using one the other as the quantitative standard but maybe if we were doing something we were monitoring an output with a DMM and you know applying a value with the calibrator or something like that so now I'm going to add a metspec instrument and I'm going to tell it to import a matte spec instrument we're

Going to use our eight and a half digit dmms because this is a pretty accurate DMM okay and so we'll hit OK that was our fluke 8508 so let's add another one for the Hewlett-Packard 3458 to heal a Packard or Agilent or whatever they're called this week so let's go ahead and select that uh what you choose would actually be what you calibrate yours to so if you calibrate them to one year specs then choose one Year all right so now I've got those two standards but you can see that in my auto assigned standards

I just have the meter calibrator so now if I also want to assign to these same ranges that we have selected those monitoring dmms that I just go back to Auto assign oh just pick the monitoring DMM because I already have assignments for that so now I pick the monitoring dmms hit OK And now you can see that I have two instruments and for now for the monitoring dmms I have a range for those as well but now you'll notice that I have a just one of them is selected and of course needless to say

only one instrument for each standard can be selected at any given time so you're only using one if you needed two calibrators and you would have two standards okay when I do that so you can see I've got the 3458 currently selected And the 5500 currently selected and now if I look at my test Point uncertainty budget you can see that there are actually two budget items in here for calibration standards the 5500 and the 3458 all right so that's just how you do multiple standards as well so now that we have our standards set

up here another thing that we would probably do is we would want to actually look at our standards to see if they're All really a good fit for this calibration so again as we said our fluke 5500 here in the real world you know we would look at this and say you know I've got a 5700 and 18 to 1 a 55 20 at 9.5 to 1 a 55.22 at 7.6 to 1. if I have those standards there's no reason that I would actually want to do a calibration with a 5500 unless we didn't have

these other standards so what I would do then in in this being the real world now is I would choose the 5500 and I would just tell it to delete this instrument all together so now when I delete this instrument it actually gets removed from all the test points in the data sheet so now if we go back and look you can see we just have the three calibrators now as options this is kind of a good tool if you have a standard that you not sure if it's going to be okay or not you

can just add it and try it if it doesn't have the necessary accuracy then you can just Delete it so you also have the option again to come up here to View and turn off the developer workbench and then you can see more information over here above the standard so you can see that there's a green indicates that everything is good the red indicates with these little yellow marks indicates potential problems and we'll get into the detail on this but just know that if you see that then that's just your indicator to click on That

test point and then go back to your developer workbench and then you can look and see that there are issues with that particular test point next up we're going to take a look at some of the advanced uncertainty modeling features you can see I've loaded another data sheet that just has some different examples of uncertainty stuff that I want to show the status sheet is really just used for demonstration purposes it has a lot of Different kinds of test points that illustrate different things about uncertainty budgeting you can see that for this test point that

we have two gray budget items and these are the automatically added budget items and we have three items that are in Black these are manually added budget items and the labels here are just for demonstration purposes to illustrate what they are in the real world we would use real practical descriptions in the Uncertainty budget editor we have the use model defaults turned off we have some of our automatic items still checked so those are being put in automatically like the measurement resolution and the assigned standards now with the used model defaults turned off we have

editing tools show up here for actually managing the budget items manually we have three types of manual budget items added one is just a general budget item And one is manual repeatability which is the second way to do repeatability actually the second and third ways and a manual standard you don't really have to use metspec instruments for standards you can assign standards manually also if you want to have a standard that's going to show up you want it for some reason to be included in your tur and uncertainty budget but not in the tar then

you can manually add a standard instead of assigning it to the test Point standards assigned to a test point would be included in the tar and standards assigned this way would not let's take a look at just a generic manual budget item I can either click on the edit button or else just double click on it and it brings up the uncertainty budget item editor in the error Source description we would give it the proper name for the budget item again we're just using demo names here manual budget item and then you would Enter the

error limit then you would choose an error limit distribution and this includes uh the more common normal probability distributions and of course you can also choose custom probability if you have something other than the standard ones that you're using you also have other things like Rayleigh rectangular triangular u-shaped rectangular for resolution you choose the appropriate distribution and then it Calculates the K factor for you and then the standard uncertainty is going to be the error limit divided by the K factor and that gives us our k equals one value now you also would enter in

the type either a or b or optionally you can leave it blank if you're using degrees of freedom this is where you would enter the degrees of freedom and optionally you can also enter a sensitivity coefficient the default is 1.0 next is manual repeatability this Particular budget item is just like our other one except we're using the repeatability tool and this gets to my point about the two other ways to do repeatability the first one I talked about being having it just put in and automatically repeatability from resolution item which is essentially one count at

the measurement resolution you can also create your own just by doing it like a regular budget item but MPS also includes a reliability tool if you Have actual reliability data then you can enter the reliability data from your reliability study for the test point in here and then you can indicate the number of values used for each item so if these are averages of five or something then you would put in five and then you can have it calculate the budget item for you the repeatability uncertainty and it will automatically calculate degrees of freedom and

all of that we'll just hit Cancel here and then I'll hit cancel for this and then also for a manual standard now there's also a tool for this you can of course just put in an error limit choose a distribution just like a regular budget item but there's also an error limit tool that you can use for this and so the error limit tool has two Master modes it has one if you want to do it from a metspec instrument and these are actually separate from the normal Calibration standard ones so you can choose a

metspec instrument that isn't in your list of calibration standards for the datasheet you can add those here and it has the same feature to Auto assign or you can manually assign ranges either way and then it will compute for you the error limit based on that and the set point information as we previously discussed the way it would do for a regular instrument range assignment Optionally you can also just manually enter specification elements like you would for a test point or a metspec range and then have it calculate the error limit from that all right

again I'm just going to hit cancel cancel another type of test Point uncertainty budget is the multiple test Point equation as I told you about earlier um said we'd come back to it now we're here so rather than display conventional Budget items you can see that this looks different this is going to use the input from other test points and a measurement equation to derive its uncertainty budget now the way this works is in this case we have volume and we have another one per area that just uses length and width volume you can see

its length width and height and there are three test points and the three test points you can see have just conventional uncertainty Budgets what's unique about these test points is that they have a bookmark name so you can see the length one it has a name called length the width has a name called width and the height has a name called height and in the mtpe for instance for volume where we're using all three of those we have a measurement equation so if we look at the measurement equation now those unique names I was telling

you like length width and height Those are actually become variables in the equation so the equation for volume is length times width times height now the inputs for these at the time at design time when you're building the data sheet are the nominal values for the test points at the time of calibration they're going to be the measure values so when you're taking as found value this would be the as found value for length the as found value for width in the asbound value for height And they get applied to this equation and then MPS

will also calculate the sensitivity coefficients using partial derivatives from the three input test points you also have the option to use optional correlation with these to correlate these different uncertainty budgets together so if we click on the correlation tool you can see we have a correlation Matrix here for our length width and height by our length width and Height if I click on one of these then you can see that the measurement correlation analysis will always have the variable one will be essentially this one the width and then the variable 2 would be length in

this case right it's this one by that one so one is length so width and length and then these are the budget items that are in there and MPS will automatically associate the budget items in the correlation Matrix And we won't really get into detail in this here in the demonstration but just know that if you don't want to go this far with doing an actual correlation analysis for the inputs you could always do like this one does which you noticed that this has a and a which means they're derived by analysis and this one

has M it's set manually so you can always click on the manual entry for one of the items and just enter a correlation value if you want to do that Another really cool feature for the uncertainty system is the ability to generate an uncertainty analysis report so if we click on this button up here we can decide to do this for either just the currently selected test point or all test points and I'll pick all test points it generates a report that shows me information about the uncertainty budgets for all the test points so you

know if you get audited and the Auditors wants to see information about the test Point uncertainty analysis then you can generate this report you can also put in Rich Text comments both at the data sheet level and for individual test points if you want I'm not going to demonstrate that I think you get the point and so at the top we have information about the datasheet document itself and then for each of the test points in the data sheet it shows the test Point here if we come down and look for Instance at this test

point you can see it's a 10 volt test point this is the tolerance the taroter and emu and then you know we've got some notes here and then it actually shows the uncertainty budget items these are the descriptions the error limits the error limit distributions types etc etc and here's the combined uncertainty of those are uncertainty confidence the effective degrees of freedom we're using degrees of freedom in this case the coverage Factor and the expanded uncertainty of course when you use degrees of freedom the coverage factor is modified based on that uh degrees of freedom

okay and then our risk information so in this case we're not guard banded so it's just showing our standard PFA and pfr using the design tolerance now if we go to another test Point that's guard banded such as this test point you can see it's actually guard Banded and then for this one we actually in the risk it also shows the risk with the design tolerances and the risks with the guard band tolerances and the guard band method used so if we look at our volume test point which was a multiple test Point equation you

can see it looks a little different same basic information about the test point but then here instead of a budget it's showing our input test points and that information about that including the Sensitivity coefficients of the inputs and then it includes our correlation Matrix two of these three are actually done by analysis so the analyzes for each of those is also shown here now one of the neat things about this report is that this is all rich text so you can just copy this content and you you can paste it into word or whatever you

want to do or if you want to send somebody an email specifically about one of these test points you can do that here's an Example I highlighted this and copied it and then we can go into word and just paste that so another feature for the uncertainty modeling is a lot of times you have a series of test points like this where the uncertainty budgets are all very similar right you're going to have essentially the same budget items when you're doing manual budgets but the you know the error limits let's say are going to be

different you can select the test point and then you can Come up here and copy that uncertainty budget and then you can go to another test point and paste that uncertainty budget like so and then you can go in and just manually edit the error limits for them it just helps save a lot of times you don't have to manually re-enter this all this information next up we're going to talk about calibration history analysis in MPS so I've loaded a data sheet for a Hewlett Packard 34401 digital multimeter and I've loaded the calibration history for

it here you can see this is all the actual measurement history for this data sheet now when I click on different test points as with everything else in MPS you can see as I move down through different test points I'm seeing the measurement history for that particular test point across the x-axis here is time so this being the oldest calibration these being The most recent the center line being the nominal or set point value and the red line up here is the upper tolerance limit and this is the lower tolerance limit so one of the

key factors is that MPS actually has document identifiers in the test point that get applied to measurements that are made you have an unbreakable link between measurements made and the source test Point that's how MPS knows how to associate all this measurement data with This particular test point if I just want to see as found data I can come up here and just uncheck as left and now I only see my aspound measurement data you can also filter for instance by asset ID and then now I can look at the calibration history for just different

specific assets so when I choose those test points also you can do it by who actually did the calibration and this is useful sometimes for physical dimensional type equipment Where you have different people maybe their technique might be better than others so you can look for issues associated with that we can also do interval analysis for this particular calibration and I'll do it for this asset I have selected by the way we were looking at approved by you notice these are all like user 11 different user events because this is a demonstration database so we

don't have real people's names in here so again going back Picking an asset and then we'll go to interval analysis report and it's asking me if I want to include measurement history I'll say yes and hit OK and then this report comes up and this is showing me what my current configuration settings are my reliability Target my minimum and maximum allowed calibration intervals by interval change confidence and and for the instrument as a whole in this case I Just have six calibrations and the average interval again just one thing I need to mention as we

go forward that this is a demonstration database and a lot of the data that's in here is really old and it's kind of interrupted and so you see like the 512 days that's based on the interval between calibration so again this demo database is going to be kind of spotty for that our average here is 512 days or longest interval is 720 and then the number in Tolerance was six and observe reliability is one hundred percent and the recommend ended interval is 512 days this is using the A3 interval analysis model so with those settings

the threshold for increasing the interval is pretty high and six samples is probably not enough to do it even though there are no out of Tolerance so this is also showing me my apparent reliability my upper and lower Confidence limits the average number of tests per year and then for every individual test point in the data sheet it's also going to show me an independent analysis just for that one test Point as though it alone was a sole document having interval analysis performed on it here it's showing me the actual measurement history for that particular

test point and what the purpose of doing this for individual test points is is that you might find That you have a situation where your recommended interval is shorter than it could be and that may be contributed just by a couple of test points so you may have a couple of test points that have a disproportionately high failure rate or low reliability in which case if you could do something with those test points some type of limited calibration it or derate the specifications for it or something you might very well be able to lengthen the

interval for the whole Thing and that's the type of information that you would look for in the calibration analysis within MPS there's another tool called the mock statistics minor that actually performs interval analysis on all of your data sheets in the background and will produce summary reports when you would come in here and look at it in MPS as if you spot something in one of those reports and you want to take a deeper dive into it that's when you would come in here and Look at the detail up next is the calibration history analysis

execute range usage report this is an advanced form of reverse traceability now what I've done I loaded an actual calibration this time instead of a data sheet for a fluke 5700 calibrator we're looking at one of the test points from that calibration at 200 millivolts at one kilohertz now the as found data here is eight parts per million minus eight Parts per million and the tolerance is 130 so it's not even close to being out of Tolerance but we'll assume for the purposes of demonstration that it was now one of the things that we would

need to do is we would now need to look and see how was that calibration this particular range of this calibration standard used in the performance of other calibrations I'm going to tell it to execute a range usage report when I click on the execute range usage report So I'm going to tell it to include a test Point specifications also and then run the report now what this report shows and let me make this a little bigger this report is a MOX instrument range utilization report specifically for asset S1 to 01687 it's a fluke 5700

EP calibrator with 5725 for the ac voltage function 220 millivolts at 40 Hertz to 20 kilohertz range for this period of time and what this report is going to show me Are all of the calibrations that used this specific range of this specific asset of this calibrator in this time period and what that's going to allow me to do is to see if there's any potential impacts from this failure what this section is showing me here is this is these are calibrations that were performed and again you know this is demo data right so we're

looking at 2010 that kind of thing these are the test points from this calibration that used This range of this standard and this is showing me the as found and as left measured values the what the calibration tolerance was and what the actual test ratio was 600 to 1 so you know again unless the standard was really way off it's not going to have an impact so I can look at and I won't go through a lot of these in the interest of time to just so you can look at different uh calibrations that were

performed and make the appropriate assessment All right so I will hit close next I'm going to talk just briefly about the boxes statistics binder this is I mentioned a little while ago is the tool that does the actual data mining on mass so this tool also comes with MPS and what its purpose is is to actually mine your database for all MPS data sheets and to perform interval analysis on all the data store the summary results from those analyzes in a database that you can view reports on to Find for instance items that have recommended

Cal interval changes and all of that and if you have MOX CMS it also performs the same analysis on make models in CMS and the CMS one differs from MPS and that it's really just based on the essentially go no-go condition of the calibration as a whole so before you run the analysis for the first time you'll want to go into Administration and you'll want to configure the Interval analysis settings and this is just telling it uh you know interval change confidence reliability Target etc etc I won't go into detail in this so let's just

go ahead and start this running and I'll talk a little more about it while it's running we're running the MPS analysis right now so for every data sheet in the databases opening that and then it's looking at all of the measurement history it's loading all the measurement history in Memory and then it's doing an analysis for the entire essentially make model so it does one analysis using all of the data from all calibrations and then in memory is sub filters and does separate analyzes for individual assets using only the data from those particular assets and

if you're using CMS it links to CMS also to do a make model as I talked about for calibrations in CMS but it's very similar to how the MPS one works And we won't get into the the details of the differences in the analyzes in this demo I'll go ahead and just stop this so I just wanted to give you a sense of what it does and it does listen to background so you would essentially start this and then go about your business and just let it run the whole thing if you have a data

sheet with one year specifications at a separate data sheet for 90 day specifications then it's going to be separate analyzes for Both of those so you know it's apples and apples whereas with CMS it's based on the make model it's the more simple conventional type of interval analysis where it's just go no go for any calibration in the make model you can come up here to reports and then you can choose either to view CMS analysis reports or MPS analysis reports and choose the type of report you want so in this case Delta Cal interval

summary this is going to be a Report about recommended interval changes and then you can sort it um you know many different ways for instance by make model and you can also use these filters to tell it only show me items that have at least five samples and or where the recommended interval Delta is greater than 10 days if we actually do this report and I'll make this a little bigger so you can see it you'll see we have an interval analysis Report that looks kind of similar to what I showed you in the calibration

history analysis at MPS only uh difference is that we're going to get multiple different data sheets showing up in here so you can see this first one is for a preset torque wrench 60 pound feet and it's going to show me essentially that same type of information average interval longest interval number of tests number intolerance and observe reliability and A recommended interval and if it's green that means that it's an interval lengthening if it's red that means it's recommended and shortening it this item here for this 100 PSI GE grade 3A pressure gauge this actually

shows an example of how this report might guide you into going into MPS and bringing up the data here we actually have it recommending the interval will be shortened we've got average interval is 321 days the longest interval was 364. Number of tests where 60 but of those 13 of them were out of tolerance so consequently you know we have an observed reliability of 78.333 percent and we have uh 246 day recommended interval now if I wanted to go and investigate this particular one further maybe look at the different test Point information and all that

stuff that's where I would go back into MPS and bring up this data sheet and load the calibration history And then dive into the the more detailed report there so this is just an example of how you would use this report to actually help you assess your situation with calibration intervals other important features in MPS include Administration you can configure MPS to set your particular uncertainty model targets and things like that your uncertainty confidence and various other settings and configurations that control different behaviors in MPS You can manage users you know create users grant them

access MPS is a permissions based system so users need to actually have permissions to do different things in the system and you control all of that by managing users and having roles and assigning users to roles MPS as a full audit logging system so every time you approve a data sheet as a either a new data sheet or a revision of an existing one there are audit log entries made the same thing For a metspec instruments you know when you approve those into the database and you can do audit reports on all of that stuff

the next up we're actually going to build a data sheet from scratch so the first thing I want to do is I want to go to file datasheet new template we're going to have a new empty data sheet and I'm going to want to go to my design mode we're already in edit mode when we do a New data sheet so I don't have to select that and now we're ready to create a new data sheet the first step in creating our new data sheet would actually be to edit all of this document header properties

if I click on edit here this is where I would come and put in my manufacturer model number description spec references spec reference is critically important because when somebody comes back to view this later Or audit it you need to know where these specifications came from and then calibration procedure information and if you have our CMS system if you purchase the CMS system you can actually link this to procedures in CMS and it'll fill out this information for you there's other sections in here but we aren't going to get into that and I'm also not

going to fill this out for now just to save time you don't need to see me type in fluke Yada yada so the next step will be to actually create the test points for our data sheet and that takes us to the test Point Builder there are a few different kinds of test points there are manually created test points and those would be for things like just labels or simple test points where it's essentially a go no-go type of scenario or pass fail type of scenario where we're just going to type information in but the

vast majority of your test points will be Created using these specifications as a base in the test Point Builder first we'll create a couple of manual test points just so you can see how that's done the first thing I might want to do is just add a label to say that this is going to be our DC voltage tests and then the next test point that I want to have might be a pass fail type test point you know we'll call that display Tests and then for a pass fail type test point you need to

have something in the nominal value and actually if I turn off my developer workbench here you can actually see our test Point configuration so you can see the first test point it doesn't recognize that is really being anything because it's really just a label but for this one let's put in a pass as the nominal value and then for the tolerance as soon as I entered one character in The tolerances It recognized it as being a simple text type of test point and a simple text type of test point just means it's not quantitative at

the time of calibration the user can enter a value and there'll be a check box to indicate if that meant pass or fail now if I actually finish what I was doing here and I just include the words pass and fail and it doesn't matter what order they're in it could be fail pass you know past Dash fail whatever but if the words pass and fail are in the tolerance then now MPS recognizes that as a specifically a pass or fail type test point which would allow me to actually enter measure values of P or

F for pass or fail when I actually do the measurements now that we've done that we'll create our actual quantitative test points using the test Point Builder so in all of our examples so far we've been talking about electrical type Equipment a lot so let's make our actual data sheet here be a pressure gauge and just do something different so what I'm going to do is I'm going to tell it I'm going to use multiple test points we're going to specify several test points all at once and these are all going to be entered as

fixed points for our pressure gauge it's going to be 150 psi gate so it's going to be 25 psi 50 75 100 125 150 and then 125 100 75 50 and 25 back down I need to enter my unit to measure I happen to know that it's PSI so I can just enter that however you should only type them in if you really know it and the truth is that when you work with the system uh you know you do pressure gauges all the time you're going to know them if you don't know the units

of measure you're not positive about the units of measure you Have a couple of tools here to help you one is just to look up for the units of measure if I typed in PSI also if you're doing more complicated test points with multiple parameters like an amplitude and a frequency and you're not sure how to do that again it's always done the same way so once you get used to it you'll just probably type them in but there's a wizard here to help you with that right so you can add additional qualifier parameters and

It'll help you set them up and everything but we don't need to do that now we want to enter our number of decimal places that we want to have for our tolerances and nominal value so I'm going to enter two decimal places then we select the tolerance display format the default is low to high which is you know 99.1 to 100.9 that type of thing or plus or minus units this gets used a lot with uh dimensional stuff right where it's plus or minus one micro Inch we'll just go with our standard low to high

the specification type is going to be either symmetrical asymmetrical or one-sided if I choose symmetrical that means I just need to enter one spec value because the high and the low are the same if I choose asymmetrical then I can specify a different low specimo tolerance specification and high tolerance specification and if I choose just one-sided then I Can use one of my operands so greater than you know 10 millivolts or 100 PSI or whatever it is but we're just going to use symmetrical for our pressure gauge which is common for our spec components because

this is pressure we're going to be using percent of indicated value only you can use any of these in combination and the reason for the question marks here is because this could be percent or PPM so either percent or PPM of IV percent or PPM of Full scale a floor error in the floor error would be uh plus or minus a unit of measure or like you know one count that type of thing plus or minus DB if we choose that then we can specify whether it's you know linear volt amp or power it's just

the equations the the logarithmic equation that's going to get used for that DB type or custom calculator now the custom calculator that's actually going to be based on an equation or actually it could be Multiple equations so if we add a custom calculator and I'll just load one here this particular custom calculator has an equation where V would be the input value for the the test point so if we were doing 99 millivolts this variable would get 99. so if V is greater than 500 then essentially you know we're going to add something for every

volt above 500. else zero so if it's not above 500 volts Then it's not going to have a contribution if it is then this equation will determine what that contribution is all right so I'm just going to hit cancel we're not going to use an equation for this doesn't apply to our pressure situation let's go ahead now and make our percent of indicated value so we're going to use one percent of indicated value for our test point now on these spec components you can actually use any combination of Them together right so you can add

the different ones including the equations and what it does is it will basically compute each of them individually and then the sum of all of these individual error contributions will determine the overall error for the test point but again we're just going to use our percent of indicated value now let's go ahead and append our test points but before we do that because we were Changing things with the uh one side and the upper range it turned off my multiple test points so let me turn that back on and then now let's append our test

points and the function tested is going to be pressure tests and this is just meaningless text it's going to be essentially the label for the function test itself and then the test Point step number this also is meaningless text this is really just associating it with The step number in your calibration procedure but it's just text to NPS so let's say it's going to be 4.2.1 and then over here we have some more important things for instance where is the measured value going to come from at the time of calibration obtained from direct entry one

value which is the default that means the technician is just going to enter one pressure value and that's going to be the measure value We could tell it mean of samples so for instance if we were doing a pressure gauge right and they're going to do essentially three clicks and the mean of the three clicks is going to be the measure value we could choose mean of samples and then specify how many samples are required or we can also do calculated prompt in calculated prompt is another case where we would use a custom calculator as

I showed you before let me just open Another one that would be an example of that and let's do uh Ohm's law okay so this one is going to actually when the user when it goes to do this it's going to prompt the user to enter a resistance and a voltage value and from that resistance and voltage it's going to calculate a current and the result of this uh custom calculator this equation is going to be the measured value and then again I'm not going to get into a Lot of detail on the editor and

stuff for this but you can actually view an example this is what the user would actually see pop up so instead of entering a value there would be a button they click on it when they click on the button they're going to see this form and you can put in text and stuff to describe you know the what you want them to enter all right so I'm just going to hit cancel we don't want any of that Uh we're going to go back and just choose our direct entry one value now this is another really

important thing in MPS the reference value by default use the nominal value so this is a one percent pressure gauge we're probably just going to use a pressure calibrator for this so we're going to assume whatever the pressure calibrator says is the true pressure so we'll set that to whatever our set point is and that will be what our reference value is also now In more accurate stuff or happens a lot in temperature we need to use a separate reference value so for instance in temperature you know we set the bath to 250 degrees C

but the bat's not really ever going to be 250 degrees C so we have a reference sprt in the bath with it and what the reference probe the reference thermometer indicates that's what the actual true temperature is so if we select this option then at the time of Calibration the user is going to have to before they can enter a measured value they'll have to to enter this reference value and this is another important thing about MPS because the way it works is the as found in the as left measurement are completely independent as I

showed you in our example we were doing the calibration where we use different standards the as found and as left values they can have different measurement uncertainties Etc et cetera Well they can also have different reference values and whenever you use this option when the user enters a reference value MPS will automatically recalculate the tolerance around the reference value that they entered it'll recompute the standards accuracy the e-m-u-t-u-r everything around that reference value and it can be completely independent for as found and as left measurements all right and then of course we also have the

option for a Calculated prompt right if we're doing a high accuracy current we might want them to enter a true value for resistance and a true value for voltage and the result of the equation is going to be the true value for current but again in our example a one percent pressure gauge we're just going to assume that the uh what we set the calibrator to is the nominal value so we'll just hit OK here and then here are our test points created now If I just turn off my workbench and I scroll over here

you can see that it actually put in also a human readable version of the specifications and what my four to one requirement is for the standards what happens behind the scenes let me bring my workbench back up is MPS actually keeps if I click on any of these test points let me clear the test Point Builder just so you can see we're starting from scratch if I click on any Test point and click on this test Point button it will load reload test Point Builder from the specs MPS actually embeds the atomized components of the

specification in the test point because it has to dynamically recompute this stuff all the time for instance at the type of calibration if you enter a different reference value foreign so the next thing that we would do is we need to tell it about our calibration Standards so I'm going to add a standard and this is going to be a pressure calibrator when we add these standard names you know you want them to be readable to the technician with our pressure calibrator selected we're going to come down to our metspec instruments and we are going

to add a metspec instrument and you know I didn't really mention this before but when we were in medspec but it really works the same way in medspec as it does With the MPS data sheets you know you've got this catalog that's going to look them up in the database this is going to be a CPC something or other so CPC 6050 pressure calibrator I'm going to hit OK and then now we've got that instrument selected in here so the next step is going to be to actually assign ranges of the calibrator to all of

our test points so we go to Assign standards test point and then we use our Auto assign tool here and in this case we're going to tell it to do all test points and we're going to pick our pressure calibrator and hit OK and then now if I just scroll this over a little bit you can see that we have uh our status Flags we have one standard assigned to each test point and they're green which means they all meet or Exceed are and the One requirement for uh tur so if we again looking at

this 150 psi test point we have our pressure PSIG units range 0 to 235 PSIG and here's the spec and then if we look at the uncertainty budget for it you can see that we've got our menser CPC 6050 pressure calibrator in here along with our budget item and our Measurement resolution and so at this point now we would be done with designing this data sheet if we weren't finished with it we were going to come back and work on it tomorrow we could always go into file datasheet template export template the file and actually

save this as a disk file when it's finished we would want to approve the template to the database now this is the proving the template is uh Permission based so you have to have the necessary rights to approve the template and the way this would typically work if you don't have the rights you would send this file to someone who does so they could load your data sheet from a file review it and then approve it and part of the approval process actually puts it in the database and so I can approve it as a

revision or prove it as a new data sheet this would be a new document so I created it from scratch so revision Might be if I took a data sheet for an existing like item and just modified it uh or I fixed a you know an error or something on it somebody entered a spec wrong and I'm doing that as a revision of the existing data sheet but in this case it's going to be a new one so we would click on new and then I would basically sign it and I'm not going to do

that because I don't actually want to approve this in my database but once we did then this data Sheet would be in the database and we can use it to perform calibrations having completed creating our new data sheet next we're going to talk about automation scripting in MPS automation scripting in MPS is different than in most systems in the sense that it's additive you don't have to do any type of automation scripting to do a normal calibration for instance if you're doing a data sheet for a micrometer there's really nothing to Automate right it's going

to be manual so you don't have to do any automation scripting for that if you get a new make model digital multimeter in and you create a data sheet for it and you can go ahead and start calibrating with it when you get enough of them that it's worthwhile then at any time you can take that existing data sheet and add automation scripting to it automation scripting and MPS can actually take multiple forms you could have as I Showed you when we started this demonstration an automated data sheet that is completely automated it communicates with

both the unit under test and the calibration standards via gpib rs232 USB or ethernet it can display instructions to the user display pictures you also can have semi-automated calibrations where we're communicating say with the standard but the unit under test we're going to Prompt the user to enter measured values could be process type calibrations where we're just going to do things like maybe in temperature where we're going to ask the user to enter some values perform some calculations and the result of those calculations are going to be the measured values we could be importing data

from external systems so you might have some software that generates a text file with data and you want to read in that text file and Parse it and use that as a measurement data in MPS and you can also use datasheet scripting to actually create new data sheets which I'll be showing you an example of that in this demo automation script editing and MPS is actually done in the calibration Master mode not the design Master mode as you might normally expect the reason for the automation scripting being done in the calibration Master mode is we

need access to the measurement data and Calibration channels and all of that to actually test the automation scripting so in the calibration mode over here on this tool this is the automation editor and you can see we have our script commands for these test points and our various tools here for actually editing the automation script every test point in a data sheet has what amounts to a script procedure and if you create a new data sheet they're always there but you don't have to use them and That's where you add automation commands to automate that

particular test Point most test points will have very few commands in them because usually the only thing you're doing is calling procedures and and a large data sheet I mean you may only have two or three test points that you're going to do any automation scripting on so you may only have script commands in those particular test points or it could be more complicated where you could actually Navigate through an entire data sheet doing a fully automated calibration but as I said most of what you do in the test points for the script commands is

pretty much calling procedures in other reusable script modules so here we're executing a sub procedure and we have the meter calibrator reusable script module and it has a bunch of different procedures in it that we can call so set output to parameter it's going to read Information from the set point parameters for the test point and build the actual gpib commands for the meter calibrator and then issue commands these script modules can actually be saved as independent files and reused in other data sheets going back to our data sheet here in the test Point commands

so unless script commands are very simple they'll usually have wizards to help you set their parameters in the case of like This sys image instruction command if we single execute just this one command this shows what the command does right it displays instructions and gives us a picture to display what that looks like if we double click on this command to edit it the commands have parameters and these parameters actually control properties of the command and unless they're very simple you know like just assigning a value to a variable or something the commands will usually

have Wizards to help you configure the parameters so in the case of this image instruction one it wants an instruction here I can select one of my instructions that are in the data sheet I have the editor tool here to edit the instructions if I wanted to have a second image in here let's call that figure two and we'll just choose a different one like this DC 10 amp and if I want to view that I can so then if I hit ok now it actually Updates all these parameters for me and now if I

execute this command again now you can see I have two figures in here that I can refer to in my text so that's just an example of what how commands are work and edited it's really beyond the scope of this demo to get into more detail on how automation scripting is done it would really would be a separate demonstration if you want to get into detail on that we'll wrap this up with a couple of actual examples Of automation script being used in MPS in MPS automation scripted data sheets you can always tell the various

places that you can start from by the teal over here in the step number column so that indicates a place you can run from you also know because the Run button becomes enabled there we'll go ahead and execute this data sheet for the semi-automated calibration for the fluke 77 DMM where we're going to communicate with the calibration Standard by gpib but the unit under test itself doesn't have an interface so we'll go ahead and hit run and you can see it comes up with our instruction for the pass fail test criteria to test the display

turn the uut on and check whether all display segments come on as indicated on LCD display and these instructions at MPS are RTF or Rich text format you can edit them either in the mps's RTF editor when you create the instructions or you can Edit them in Microsoft Word and paste them in so we'll go ahead and select pass and then next it's going to actually come up with my instructions and image on how to connect the equipment for the DC voltage test so I'll hit continue and then now because this is semi-automated it has

to ask me for the measured value so it's showing me what the set point is in the tolerance so let's do 2.699 And hit enter and I'm just going to Halt the script we just entered one test Point uh there's no point to continue doing this you get the idea I've loaded another data sheet the purpose of this automation scripting is to build a data sheet the first time I run the data sheet the script commands are going to prompt me for specifications for a torque wrench and then it's going to set up all the

test Points based on those specifications before I start that you can see that all of these test points are all zero nominal values zero tolerances let's go ahead and run this and my units of measure are pound feet I could select different options my full scale value let's say is going to be 250 my full scale spec is going to be zero and let's just say it's one percent of indicated value no floor error and we're going to use two decimal places and then for my Counterclockwise specification info it's going to default to the same

as clockwise and that's fine so I'll hit OK and then now is asking me for boilerplate information this is where I would put in the manufacturer like Snap On the model like you know tqs 250 or whatever it is I'm not going to actually do that in this demo just in the interest of time and you can see that it actually created all the test points here for my torque Wrench now when I actually run this data sheet scripting again now that it's created the data sheet it's now a calibration scripting it's asking me for

the three break points and it's going to fill those in so I'm doing a 50 foot pound so let's just do 49.98 49.97 and 50.01 and hit OK and again I'm just going to Halt the script here but you can see it's putting In my measured value and I could approve this data sheet once I've once I've used the scripting to create it and then now it has the automation scripting left to just do the calibrations for it okay so that's another example of using automation scripting to actually build new data sheets so one other

thing I want to point out on this data sheet before I leave it you can see that we actually have our sampling section showed up earlier in The demo I told you that when a test point is configured for sampling a section would show up here for entering the samples and here it is so that's because these particular test points are configured to take the three clicks and we're going to use the mean of the three clicks as the measure value another really powerful feature of MPS automation scripting is its ability to communicate with external

applications via com such as Excel or you can create Your own plugins to extend mps's capabilities and as long as you add a com interface to them you can communicate with those through automation scripting with MPS this example is actually just going to demonstrate MPS communicating with Microsoft Excel I'm just going to push this down here and then I'm going to go ahead and run this and when I do MPS is going to actually launch Microsoft Excel So here you can see that we have Excel basically we have its instructions telling us about how it's

going to use Excel and all that and we are not going to read all that now and then it's asking for the Excel spreadsheet that we're going to use and then now it's actually loading the Excel application and you know this takes a few seconds because Excel is a pretty big application although when it first loaded Excel you don't actually See it because Excel is visibility property is simple false so now MPS comes up and it's telling it's giving us a couple of options about how frequently we wanted to iterate this is just going to

run in a loop and it's going to pass a couple of values to excel Excel is going to use those values to do a bunch of calculations and then it's going to return three values and we're going to display those three values while it's running and then it's Just asking if we want Excel to be visible we do in this case because I want you to see what it's doing so let's hit OK let me this down here to where you can see it and now let's bring Excel back up here okay so what's going

on here is that MPS is just basically incrementing these values these two values and it's basically passing them to these two Cells in Excel Excel is doing a bunch of calculations on those values and then essentially this green value and the two black values you see here MPS is reading those values back from Excel and so you can see all this updating very very fast so the point that I wanted to make with this is that not only can NPS communicate of via com with external applications is that it does it extremely fast so that's

going to be it for our demo Thank you very much for spending time with us I look forward to working with you