<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><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:Aptos;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:10.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
font-size:10.0pt;
font-family:"Courier New";}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}
span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Aptos",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;
mso-ligatures:none;}
@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]--></head><body lang=EN-US link=blue vlink=purple style='word-wrap:break-word'><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Aptos",sans-serif'>Jan and others,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Aptos",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Aptos",sans-serif'>If we consider a digital thread actually to be more like a traditional thread compose of many strands or fibers where each strand has a use case, rather than a monofilament line of one use case, then we gain the flexibility to characterize the wide variety of “digital thread” concepts and applications. Since I think we agree that few object systems are likely to have only one digital twin in practice, then this thread of stands orientation gives us a handle for composing digital twin specific threads as strands of a larger and more comprehensive systemic digital thread.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Aptos",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Aptos",sans-serif'>Cheers,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Aptos",sans-serif'>Richard<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Aptos",sans-serif'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Aptos",sans-serif'><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'>From:</span></b><span style='font-size:11.0pt'> step-manufacturing <step-manufacturing-bounces@steptools.com> <b>On Behalf Of </b>jan.de.nijs@lmco.com<br><b>Sent:</b> Wednesday, April 24, 2024 9:53 AM<br><b>To:</b> Rencher (US), Robert J <robert.j.rencher@boeing.com>; Martin Hardwick <hardwick@steptools.com>; step-manufacturing@steptools.com<br><b>Subject:</b> Re: [step-manufacturing] EXTERNAL: Re: [EXTERNAL] Reminder: UUIDs for the digital thread<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt'>Great discussion. Thanks for the input.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>My thinking remains that there is exactly 1 digital thread per use case. Define the use case for me, and I will tell you what the digital thread has to be. I am stuck on this idea that the thread defines which data elements are needed to implement a specific use case.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>So yes, if you agree that there are “n” use cases, then it is likely that there are “n” digital threads (although I think that there are many use cases that share the same digital thread).<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>I have a slide deck where I actually prove that point. “Simple” maintenance insights can be derived straight from an MTConnect stream. No need at all for UUID’s, part numbers, serial numbers, quality data. But just an MTConnect stream is never going to get you OEE. You need many more data elements for that. And for things like dynamic scheduling and (my favorite) causal analytics, you need many more again. There is an effort at UKentucky to look at DT’s of the cutting process to specifically quantify subsurface damage, which requires a completely different set of data elements. Again, IMO, proving the point that digital threads are use case dependent.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Jan.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><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'>From:</span></b><span style='font-size:11.0pt'> step-manufacturing <<a href="mailto:step-manufacturing-bounces@steptools.com">step-manufacturing-bounces@steptools.com</a>> <b>On Behalf Of </b>Rencher (US), Robert J<br><b>Sent:</b> Wednesday, April 24, 2024 8:31 AM<br><b>To:</b> Martin Hardwick <<a href="mailto:hardwick@steptools.com">hardwick@steptools.com</a>>; <a href="mailto:step-manufacturing@steptools.com">step-manufacturing@steptools.com</a><br><b>Subject:</b> EXTERNAL: Re: [step-manufacturing] [EXTERNAL] Reminder: UUIDs for the digital thread<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:11.0pt'>Hello Martin,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>There is a continuing discussion regarding the number of digital threads. One perspective is there is only one digital thread. This one digital thread is the system that facilitates interoperability between disparate systems across the product lifecycle. The other perspective is that there are “n” number of digital threads representing the respective workstreams or value streams utilized throughout the product lifecycle.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Both of these perspectives have advocates in the industry and both have valid arguments. From my perspective the one digital thread approach lacks the depth and detail needed to align with the utility of the one digital thread. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>I have a conflict today with PLM AG. I’ll try and jump on to this during a break.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'>Robert<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt'><o:p> </o:p></span></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-family:"Courier New"'>Dr. Robert J. Rencher, D.M.<br>Sr. Systems Engineer,</span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <br></span><span style='font-family:"Courier New"'>Associate Technical Fellow</span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <br></span><span style='font-family:"Courier New"'>Enterprise Engineering</span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <br></span><span style='font-family:"Courier New"'>The Boeing Company<br>PH: (206)295-0887</span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><br></span><span style='font-family:"Courier New"'>email: <a href="mailto:robert.j.rencher@boeing.com">robert.j.rencher@boeing.com</a></span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> </span><span style='font-family:"Courier New"'><o:p></o:p></span></p><p class=MsoNormal><span style='font-family:"Courier New"'>"Vision without effort is day dreaming, effort without vision is drudgery"</span><span style='font-size:11.0pt'> <o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt'><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'>From:</span></b><span style='font-size:11.0pt'> Martin Hardwick <<a href="mailto:hardwick@steptools.com">hardwick@steptools.com</a>> <br><b>Sent:</b> Wednesday, April 24, 2024 5:09 AM<br><b>To:</b> Rencher (US), Robert J <<a href="mailto:robert.j.rencher@boeing.com">robert.j.rencher@boeing.com</a>>; <a href="mailto:step-manufacturing@steptools.com">step-manufacturing@steptools.com</a><br><b>Subject:</b> Re: [EXTERNAL] [step-manufacturing] Reminder: UUIDs for the digital thread<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><table class=MsoNormalTable border=0 cellspacing=5 cellpadding=0 width="100%" style='width:100.0%'><tr><td style='background:white;padding:.75pt .75pt .75pt .75pt'><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 align=left width="100%" style='width:100.0%;margin-left:.75pt;margin-right:.75pt'><tr><td style='background:#910A19;padding:5.25pt 1.5pt 5.25pt 1.5pt'></td><td width="100%" style='width:100.0%;background:#FDF2F4;padding:5.25pt 3.75pt 5.25pt 11.25pt'><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><span style='font-family:"Verdana",sans-serif;color:#212121'>EXT email: be mindful of links/attachments.</span><span style='font-size:11.0pt'><o:p></o:p></span></p></div></td></tr></table><pre><span style='color:black'><br> <o:p></o:p></span></pre></td></tr></table><p>Hi Robert,<o:p></o:p></p><p>I agree there should only be one thread, but because of the digital twin composition, there is a transition between manufacturing and engineering that must be managed.<o:p></o:p></p><p>Martin<o:p></o:p></p><div><p class=MsoNormal><span style='font-family:"Times New Roman",serif'>On 4/23/2024 2:29 PM, Rencher (US), Robert J wrote:<o:p></o:p></span></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><p class=MsoNormal><span style='font-size:11.0pt'>Hello Martin,</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'>Thank you for sharing the diagram. I would suggest an alternate labeling for the engineering and manufacturing digital thread. The generalization of digital thread introduces the categorization of thread types, i.e. “engineering thread”. If the attempt is to be discrete in assigning a label to a digital thread then a descriptive label that easily identify the purpose/use of the digital thread should be used. Digital Threads align data/information with sequence(d) events/tasks/objectives. A UUID could be assigned to a digital thread to identify the discrete digital thread use event.</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'>Robert</span><o:p></o:p></p><p class=MsoNormal><span style='font-size:11.0pt'> </span><o:p></o:p></p><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-family:"Courier New"'>Dr. Robert J. Rencher, D.M.<br>Sr. Systems Engineer,</span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <br></span><span style='font-family:"Courier New"'>Associate Technical Fellow</span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <br></span><span style='font-family:"Courier New"'>Enterprise Engineering</span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> <br></span><span style='font-family:"Courier New"'>The Boeing Company<br>PH: (206)295-0887</span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'><br></span><span style='font-family:"Courier New"'>email: <a href="mailto:robert.j.rencher@boeing.com">robert.j.rencher@boeing.com</a></span><span style='font-size:12.0pt;font-family:"Times New Roman",serif'> </span><o:p></o:p></p><p class=MsoNormal><span style='font-family:"Courier New"'>"Vision without effort is day dreaming, effort without vision is drudgery"</span><span style='font-size:11.0pt'> </span><o:p></o:p></p></div><p class=MsoNormal><span style='font-size:11.0pt'> </span><o:p></o:p></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'>From:</span></b><span style='font-size:11.0pt'> step-manufacturing <a href="mailto:step-manufacturing-bounces@steptools.com"><step-manufacturing-bounces@steptools.com></a> <b>On Behalf Of </b>Martin Hardwick<br><b>Sent:</b> Tuesday, April 23, 2024 11:08 AM<br><b>To:</b> <a href="mailto:step-manufacturing@steptools.com">step-manufacturing@steptools.com</a><br><b>Subject:</b> [EXTERNAL] [step-manufacturing] Reminder: UUIDs for the digital thread</span><o:p></o:p></p></div></div><p class=MsoNormal> <o:p></o:p></p><table class=MsoNormalTable border=0 cellspacing=5 cellpadding=0 width="100%" style='width:100.0%'><tr><td style='background:white;padding:.75pt .75pt .75pt .75pt'><table class=MsoNormalTable border=0 cellspacing=0 cellpadding=0 align=left width="100%" style='width:100.0%;margin-left:.75pt;margin-right:.75pt'><tr><td style='background:#910A19;padding:5.25pt 1.5pt 5.25pt 1.5pt'></td><td width="100%" style='width:100.0%;background:#FDF2F4;padding:5.25pt 3.75pt 5.25pt 11.25pt'><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;mso-element:frame;mso-element-frame-hspace:2.25pt;mso-element-wrap:around;mso-element-anchor-vertical:paragraph;mso-element-anchor-horizontal:column;mso-height-rule:exactly'><span style='font-family:"Verdana",sans-serif;color:#212121'>EXT email: be mindful of links/attachments.</span><o:p></o:p></p></div></td></tr></table><pre><span style='color:black'><o:p> </o:p></span></pre><pre><span style='color:black'> </span><o:p></o:p></pre></td></tr></table><p>All,<o:p></o:p></p><p>We will review organizing principles for the digital thread.<o:p></o:p></p><p>Martin<o:p></o:p></p><p><img border=0 width=1114 height=717 style='width:11.6064in;height:7.4675in' id="Picture_x0020_1" src="cid:image001.png@01DA9631.D3DB75F0"><o:p></o:p></p><p style='margin-bottom:12.0pt'>Topic: UUID's for the Digital Thread<br>Time: Apr 24, 2024 09:30 AM Eastern Time (US and Canada)<br> Every 2 weeks on Wed, until May 8, 2024, 2 occurrence(s)<br> Apr 24, 2024 09:30 AM<br> May 8, 2024 09:30 AM<br> Please download and import the following iCalendar (.ics) files to your calendar system.<br> Weekly: <a href="https://iso.zoom.us/meeting/tJYudO2orjItE9yQiOKUzNMjdd9AW5UTsZsE/ics?icsToken=98tyKuCqrTguGtSctxCPRowQA4jCLPTziFhaj_pErRbKKBVJTC78MuYbE4UqJezD">https://iso.zoom.us/meeting/tJYudO2orjItE9yQiOKUzNMjdd9AW5UTsZsE/ics?icsToken=98tyKuCqrTguGtSctxCPRowQA4jCLPTziFhaj_pErRbKKBVJTC78MuYbE4UqJezD</a><br><br>Join from PC, Mac, Linux, iOS or Android: <a href="https://iso.zoom.us/j/92334009798?pwd=OXBWQUEraUVXZW9zRG55NEpRN00yQT09">https://iso.zoom.us/j/92334009798?pwd=OXBWQUEraUVXZW9zRG55NEpRN00yQT09</a><br> Password: 870003<br><br>Or iPhone one-tap :<br> US: +16465189805,,92334009798# or +16468769923,,92334009798# <br>Or Telephone:<br> Dial(for higher quality, dial a number based on your current location): <br> US: +1 646 518 9805 or +1 646 876 9923 or +1 651 372 8299 or +1 786 635 1003 or +1 267 831 0333 or +1 301 715 8592 or +1 312 626 6799 or +1 470 250 9358 or +1 470 381 2552 or +1 253 215 8782 or +1 346 248 7799 or +1 408 638 0968 or +1 602 753 0140 or +1 669 219 2599 or +1 669 900 6833 or +1 720 928 9299 or +1 971 247 1195 or +1 206 337 9723 or +1 213 338 8477 or 877 853 5247 (Toll Free) or 888 788 0099 (Toll Free)<br> Meeting ID: 923 3400 9798<br> Password: 870003<br> International numbers available: <a href="https://iso.zoom.us/u/acNgoSPTTP">https://iso.zoom.us/u/acNgoSPTTP</a><o:p></o:p></p><pre>-- <o:p></o:p></pre><pre>Martin Hardwick<o:p></o:p></pre><pre>President STEP Tools, Inc.<o:p></o:p></pre><pre>Cell: 518 253-0596<o:p></o:p></pre><pre>"The sticky tape wizards"<o:p></o:p></pre><pre>"There are billions of STEP files and millions of STEP-NC files"<o:p></o:p></pre></blockquote><pre>-- <o:p></o:p></pre><pre>Martin Hardwick<o:p></o:p></pre><pre>President STEP Tools, Inc.<o:p></o:p></pre><pre>Cell: 518 253-0596<o:p></o:p></pre><pre>"The sticky tape wizards"<o:p></o:p></pre><pre>"There are billions of STEP files and millions of STEP-NC files"<o:p></o:p></pre></div></body></html>