<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<p>Many thanks to Tom for sending these questions - have put some
answers into the text and made some adjustments to the slides
(attached).</p>
<p>For further discussion in the call.<br>
</p>
<br>
<div class="moz-cite-prefix">On 12/14/2016 9:14 AM, Tom Kramer
wrote:<br>
</div>
<blockquote cite="mid:585153B4.3030102@nist.gov" type="cite">
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
Hi Martin -<br>
<br>
Thanks for sending the slides in advance. I plan to join the
teleconference this morning. At 11:00 I have another
teleconference, so I hope it won't take more than an hour.<br>
<br>
I find the slides a bit confusing, particularly slide 5, which has
a diagram. Here are some questions and comments.<br>
<br>
On Slide 4<br>
--------------<br>
<br>
1. Items 3 and 5 on slide 4 refer to a CMM, but it appears that no
CMM is involved. Presumably "CMM" on this slide means "virtual
CMM" or "Smart Metrology Service". Is that correct? YES<br>
<br>
2. What sort of QIF information is being produced. Is it only
nominal touch points and actual touch points, or are features
being fitted and characteristics (tolerances) being evaluated?
Chartacterstics are being evaluated by the CMM<br>
<br>
On Slide 5<br>
--------------<br>
<br>
1. What is the function of "Smart Phones and Tablets"? Why are
"Computers" not included? REMOTE OPERATION<br>
<br>
2. Why is AP242 rather than ISO 13399 used to communicate tooling
data? Is a CAD model rather than a parametric model being
transmitted? SO THAT THE SERVER GETS A MODEL OF THE TOOL<br>
<br>
3. The Digital Twin Server presumably has a stored model of the
nominal part and constructs an as-built part. Does the AP242 arrow
going into the Digital Twin Server indicate that the Smart
Metrology Service is sending the nominal model to the Digital
Twin Server? If not, what does it indicate? AT PRESENT WE WILL BE
SENDING AP242 FROM THE SERVER TO THE CMM BUT NOT VICE VERSA<br>
<br>
4. There is nothing going into the Smart Metrology Service box.
How can it produce QIF output? Is there an MTConnect data
repository missing from the diagram from which the Smart Metrology
Service gets data? CMM WILL PRODUCE QIF FROM POINT CLOUD
ASSOCIATED TO THE SURFACES<br>
<br>
5. I don't like the word "Catalog" used to represent actual
tooling (which is what it seems to mean on the diagram). I have
always kept a distinction between (1) a catalog, which represents
models of as-designed tools and (2) an actual tooling database,
which represents tools that are actually available for use and has
as-measured data for some tool parameters -- diameter, for
example. NOT SURE I LIKE CATALOG EITHER - MAYBE TOOL PRESETTER<br>
<br>
6. Since the CNC machine is not getting any tooling data, it
appears from the diagram that the CNC Machine is not doing any
tool wear compensation in this scenario. Is that correct? PROBABLY
NOT<br>
<br>
7. Does the dotted line labeled "G-code" mean that G-code is sent
from the Digital Twin Server? YES<br>
<br>
<div class="moz-cite-prefix">On 12/14/2016 07:46 AM, Martin
Hardwick wrote:<br>
</div>
<blockquote
cite="mid:19b2c0c3-7921-4dba-26ce-4c165747d663@steptools.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=utf-8">
<p>All,</p>
<p>Here are some slides on how we can use MTConnect, STEP and
QIF to check on the results of an operation when the potential
for a tool wear issue has been identified.</p>
<p>Martin<br>
</p>
<p>On 12/13/2016 10:13 AM, Horst, John A. (Fed) wrote:<br>
</p>
<blockquote
cite="mid:DM5PR09MB1339F4D4C2CDEDE3CFBFB389F59B0@DM5PR09MB1339.namprd09.prod.outlook.com"
type="cite">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Monaco;
panose-1:0 0 0 0 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman",serif;
color:black;}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.EmailStyle20
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Hi
Martin, <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">The
DMSC is in dialog with the MTConnect Institute to
reference QIF elements when doing in-process
measurement. DMSC and MTConnect leadership has been in
dialog about this for some time. Is there any talk about
this in your group? Can we talk about this Wednesday
with your group? <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">Thanks,
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">John
Horst<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">NIST<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1
1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">From:</span></b><span
style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:windowtext">
step-manufacturing [<a moz-do-not-send="true"
class="moz-txt-link-freetext"
href="mailto:step-manufacturing-bounces@steptools.com">mailto:step-manufacturing-bounces@steptools.com</a>]
<b>On Behalf Of </b>Martin Hardwick<br>
<b>Sent:</b> Monday, December 12, 2016 8:00 AM<br>
<b>To:</b> <a moz-do-not-send="true"
class="moz-txt-link-abbreviated"
href="mailto:step-manufacturing@steptools.com">step-manufacturing@steptools.com</a><br>
<b>Subject:</b> [step-manufacturing] Proposed agenda
for December 14 conference call<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p>All,<br>
<br>
The last conference call of 2016 is this Wednesday at the
regular times - 7AM Pacific, 10AM Eastern, 3PM UK and 4PM
Europe. The contact details are repeated below for those
who do not use an electronic calendar.<o:p></o:p></p>
<p>The following agenda is proposed:<o:p></o:p></p>
<p class="MsoNormal">1. Live demonstration of virtualized
machining for a Haas mini-mill (to be held December 19).<br>
2. Proposal for an MTConnect extension to include probing
results (see below).<br>
3. Planning for the February demonstration.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Monaco",serif;color:#F4F4F4">2016-04-23T21:53:38.7964000Z|measure|features:"PNT276,PNT219"
id:"DIST19" characteristic:"3D DISTANCE"
nominal:2.6416 measured:2.64159200514476
minus:0.254 plus:0.254 deviation:0<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Monaco",serif;color:#F4F4F4">2016-04-23T21:53:41.2768000Z|measure|features:"PNT282,PNT277"
id:"DIST20" characteristic:"3D DISTANCE"
nominal:3.4544 measured:3.45440000000355
minus:0.2286 plus:0.2286 deviation:0<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Monaco",serif;color:#F4F4F4">2016-04-23T21:53:42.6184000Z|measure|features:"PNT281,PNT278"
id:"DIST21" characteristic:"3D DISTANCE"
nominal:3.4544 measured:3.45440000000355
minus:0.2286 plus:0.2286 deviation:0<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Monaco",serif;color:#F4F4F4">2016-04-23T21:53:43.4140000Z|measure|features:"PNT279,PNT280"
id:"DIST22" characteristic:"3D DISTANCE"
nominal:3.4544 measured:3.45440000000364
minus:0.2286 plus:0.2286 deviation:0<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Monaco",serif;color:#F4F4F4">2016-04-23T21:53:44.1472000Z|measure|features:"LIN11,LIN12"
id:"PERP3" characteristic:"PERPENDICULARITY"
nominal:0 measured:2.80981460321072E-11 minus:0
plus:0.254 deviation:0<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Monaco",serif;color:#F4F4F4">2016-04-23T21:53:45.0832000Z|measure|features:"PNT283,PNT223"
id:"DIST23" characteristic:"3D DISTANCE"
nominal:3.048 measured:3.04799197854405
minus:0.254 plus:0.254 deviation:0<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Monaco",serif;color:#F4F4F4">2016-04-23T21:53:47.4232000Z|measure|features:"PNT289,PNT284"
id:"DIST24" characteristic:"3D DISTANCE"
nominal:3.4544 measured:3.45440000000363
minus:0.2286 plus:0.2286 deviation:0<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Monaco",serif;color:#F4F4F4">2016-04-23T21:53:48.9208000Z|measure|features:"PNT288,PNT285"
id:"DIST25" characteristic:"3D DISTANCE"
nominal:3.4544 measured:3.45440000000363
minus:0.2286 plus:0.2286 deviation:0<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Monaco",serif;color:#F4F4F4">2016-04-23T21:53:49.9036000Z|measure|features:"PNT286,PNT287"
id:"DIST26" characteristic:"3D DISTANCE"
nominal:3.4544 measured:3.45440000000363
minus:0.2286 plus:0.2286 deviation:0<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Monaco",serif;color:#F4F4F4">2016-04-23T21:53:50.5744000Z|measure|features:"PNT284,PNT282"
id:"DIST41" characteristic:"3D DISTANCE"
nominal:19.1262 measured:19.1261999999964
minus:0.1778 plus:0.1778 deviation:0<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Monaco",serif;color:#F4F4F4">2016-04-23T21:53:51.1828000Z|measure|features:"PNT285,PNT281"
id:"DIST43" characteristic:"3D DISTANCE"
nominal:19.1262 measured:19.1261999999964
minus:0.1778 plus:0.1778 deviation:0<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Monaco",serif;color:#F4F4F4">2016-04-23T21:53:51.9004000Z|measure|features:"PNT286,PNT280"
id:"DIST45" characteristic:"3D DISTANCE"
nominal:19.1262 measured:19.1261999999963
minus:0.1778 plus:0.1778 deviation:0<o:p></o:p></span></p>
</div>
</div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Monaco",serif">2016-04-23T21:53:52.7740000Z|measure|features:"PNT290,PNT227"
id:"DIST27" characteristic:"3D DISTANCE"
nominal:2.6416 measured:2.6415920051448
minus:0.254 plus:0.254 deviation:0<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
<div>
<div>
<div>
<p class="MsoNormal"><span
style="font-size:7.5pt;font-family:"Monaco",serif;color:#F4F4F4">2016-04-23T22:01:06.7972000Z|measure|features:"PLN1"
id:"FLAT1" characteristic:"FLATNESS" nominal:0
measured:0.49999999926914 minus:0 plus:0.01
deviation:0.48999999926914<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal">Martin Hardwick<br>
Convener ISO WG15 Digital Manufacturing<br>
<br>
7AM Pacific, 10AM Eastern, 3PM UK, 4PM Europe<br>
1. Please join my meeting.<br>
<a moz-do-not-send="true"
href="https://www2.gotomeeting.com/join/285940474"><span
style="font-size:7.5pt;font-family:"Verdana",sans-serif">https://www2.gotomeeting.com/join/285940474</span></a><span
style="font-size:7.5pt;font-family:"Verdana",sans-serif"><br>
<br>
2. Use your microphone and speakers (VoIP) - a headset
is recommended. Or, call in using your telephone.<br>
<br>
Australia: +61 2 6108 4655<br>
Austria: +43 (0) 7 2088 1403<br>
Belgium: +32 (0) 28 08 4294<br>
Canada: +1 (416) 800-9295<br>
Denmark: +45 (0) 69 91 88 65<br>
Finland: +358 (0) 942 41 5781<br>
France: +33 (0) 182 880 459<br>
Germany: +49 (0) 811 8899 6901<br>
Ireland: +353 (0) 14 845 979<br>
Italy: +39 0 699 36 98 81<br>
Netherlands: +31 (0) 208 080 382<br>
New Zealand: +64 (0) 4 974 7214<br>
Norway: +47 21 03 58 99<br>
Spain: +34 931 81 6669<br>
Sweden: +46 (0) 852 503 499<br>
Switzerland: +41 (0) 435 0167 09<br>
United Kingdom: +44 (0) 207 151 1857<br>
United States: +1 (619) 550-0006<br>
<br>
Access Code: 285-940-474<br>
Audio PIN: Shown after joining the meeting</span> <o:p></o:p></p>
</div>
</blockquote>
<br>
</blockquote>
<br>
</blockquote>
<br>
</body>
</html>