<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#ffffff" text="#000000">
<u>Attendees</u><br>
Martin Hardwick, STEP Tools, USA <br>
David Loffredo, STEP Tools, USA <br>
Fred Proctor, NIST, USA <br>
Fiona Zhao, NIST,/New Zealand<br>
David Odendahl, Boeing, USA <br>
Bengt Olsson, Sandvik, Sweden <small><br>
</small>Larry Maggiano, Mitutoyo, USA<br>
Leon Xu, Boeing, USA <br>
Mikael Hedlind, KTH, Sweden<br>
Chris Pfeifer CCAT, USA<br>
Anna Valente, ITIA-CNR, Italy<br>
Sid Venkatesh, Boeing, USA<br>
Magnus Lundgren, KTH, Sweden<br>
Simon Frechette, NIST, USA<br>
John Horst NIST, USA<br>
Rich Morihara, Boeing, USA<br>
Paul Huang, Army, USA<br>
Charles Stirk, PDES, Inc.<br>
B E Lee, NIST/Postech, Korea<br>
Joao Carlos E. Ferreira, Universidade Federal de Santa Catarina,
Brazil <br>
Alberto J. Álvares, Universidade de Brasilia, Brazil<br>
John Michaloski, NIST, USA<br>
<div dir="ltr" align="left"><big><font color="#000000"><span
class="387451413-22062010"><font size="2"><big>Mike McGlauflin, NIST,
USA</big></font></span></font></big></div>
<div dir="ltr" align="left"><big><font color="#000000"><span
class="387451413-22062010"><font size="2"><big>Rob Garwood, Sandvik
Coromant, USA</big></font></span></font></big></div>
<div dir="ltr" align="left"><big><font color="#000000"><span
class="387451413-22062010"><font size="2"><big>Joe Fritz, STEP Tools
Inc., USA</big></font></span></font></big></div>
<div dir="ltr" align="left"><big><font color="#000000"><span
class="387451413-22062010"><font size="2"><big>Matthew Byrne,
University of Michigan/Boeing, USA</big></font></span></font></big></div>
<div dir="ltr" align="left"><big><font color="#000000"><span
class="387451413-22062010"><font size="2"><big>Shawn Moylan, NIST, USA</big></font></span></font></big></div>
<div dir="ltr" align="left"><big><font color="#000000"><span
class="387451413-22062010"><font size="2"><big>Rob Ivester, NIST, USA</big></font></span></font></big></div>
<div dir="ltr" align="left"><big><font color="#000000"><span
class="387451413-22062010"><font size="2"><big>Al Jones, NIST, USA</big></font></span></font></big></div>
<div dir="ltr" align="left"><big><font color="#000000"><span
class="387451413-22062010"><font size="2"><big>Jeff Haller, Veritas
CNC, USA</big></font></span></font></big></div>
<div dir="ltr" align="left"><big><font color="#000000"><span
class="387451413-22062010"><font size="2"><big>Eric Whitenton, NIST, US</big></font></span></font></big><font
color="#000000"><span class="387451413-22062010"><font face="Arial"
size="2">A</font></span></font></div>
<br>
<u>Telephone Attendees</u><br>
Vincent Marchini, Ameritech, USA<br>
Per-Arne Carlsson, Volvo, Sweden<br>
<br>
<u>Apologies for Absence</u><br>
Aydin Nassehi, U.Bath, UK<br>
Stephen Newman, U.Bath, UK<br>
Alain Brail, AlBavis, France <small><br>
</small>Thomas Breunung, Walter AG, Germany<br>
Anglea Albus, TDM Systems, Germany<br>
Bob Erickson, Pratt & Whitney, USA<br>
<br>
The Boxy part was machined in Steel by NIST and they were able to show
predicted tool wear for the pocketing operations.<br>
<br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/Boxy.mov">ftp://ftp.steptools.com/private/NIST/Presentations/Boxy.mov</a><br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/STEP_Tool_Life_NIST.ppt">ftp://ftp.steptools.com/private/NIST/Presentations/STEP_Tool_Life_NIST.ppt</a><br>
<br>
The following were agreed to be the successes of this round.<br>
<br>
1. We were able to use the setup placements defined by STEP-NC to allow
the operator to use the same coordinates for each setup by normalizing
the coordinates of each setup to match the fixturing.<br>
2. We were able to use the workplan/workingstep structure of a STEP-NC
program to rapidly and intelligently optimize the feeds and speeds of a
program to meet the requirements of the tool and the machining schedule.<br>
<br>
Magnus Lundgren of KTH gave a demonstration and discussion of how the
Boxy data was built using Mastercam. Martin Hardwick gave a
demonstration of how a STEP-NC data set was prepared for machining
using the STEP-NC Explorer. <br>
<br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/Boxy_MasterCAM_and_ST-Explorer_Tutorial.pdf">ftp://ftp.steptools.com/private/NIST/Presentations/Boxy_MasterCAM_and_ST-Explorer_Tutorial.pdf</a><br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/STEPNC_Explorer_and_Boxy.ppt">ftp://ftp.steptools.com/private/NIST/Presentations/STEPNC_Explorer_and_Boxy.ppt</a><br>
<br>
There was considerable discussion of how to make STEP-NC data more
portable and interoperable. There was general agreement that helping
the operator to understand the "real" tool requirements was a key
issue. The STEP-NC program contains a precise description of the tool
that "worked" for the operator that designed the program, but does not
contain any data to indicate which attributes of the tool are required
for successful machining and which attributes can be varied without
consequences. Fred Proctor of NIST agreed to develop an information
model for documenting the requirements so that they can be used to
control tool selection in future applications. We agreed that the
requirements should match ISO 13399 properties so that the tool
selection can be performed automatically, and that the simple display
of the advice was equally important so that an operator can be given
help when deciding what tools to order before machining a new part.<br>
<br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/toolreqs-v4.txt">ftp://ftp.steptools.com/private/NIST/Presentations/toolreqs-v4.txt</a><br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/Katrineholm_Feautures_and_Flow_simulation_100602.pdf">ftp://ftp.steptools.com/private/NIST/Presentations/Katrineholm_Feautures_and_Flow_simulation_100602.pdf</a><br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/physical_cutting_tools-made_simple.ppt">ftp://ftp.steptools.com/private/NIST/Presentations/physical_cutting_tools-made_simple.ppt</a><br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/Endmill_examples.pdf">ftp://ftp.steptools.com/private/NIST/Presentations/Endmill_examples.pdf</a><br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/MILLING_TOOL_PARAMETERS_DOCUMENTATION.DOC">ftp://ftp.steptools.com/private/NIST/Presentations/MILLING_TOOL_PARAMETERS_DOCUMENTATION.DOC</a><br>
<br>
We further discussed developing a schema to return tool advice from the
tool vendor when a tool has been selected. This advice should include
the attributes required to determine chip load and expected tool wear
so that the enterprise can plan how to use the tool and optimize the
STEP-NC program appropriately.<br>
<br>
We discussed Mil Standard 31000. This standard is used to determine the
technical data that a contractor must deliver to the DoD when building
a system and is in the process of being updated. Consideration is being
given to requiring the contractors to deliver information about the
manufacturing processes used to create the system. STEP-NC AP-238 is
standard that can be used to describe such information and the Army is
interested in evaluating its suitability for Mil Standard 31000.<br>
<br>
We discussed traceability and process monitoring. A STEP-NC program can
add value to process results by describing the operation, feature and
cutting tool being used to machine a part when an event happens during
machining. We agreed that there are three kinds of information that we
would like to correlate against a STEP-NC program. Discrete events such
as an operator change or a fire alarm. Continuous events that
correspond to the progress of the STEP-NC program and continuous events
that do not correspond. The former follow the same encoding as the
STEP-NC data so that if measurement values have been captured at the
start and end of a tool path, then a value can be computed for the
middle of the path. The latter are not correlated because they vary at
random during the machining and include properties such as sound and
machine vibrations but an analyst would still like to know what was
happening to the sensor during the machining of that path.<br>
<br>
Several users would like to be able to capture process results in the
context of STEP-NC programs using OPC calls or MT Connect. We developed
a schema that will allow these results to be added to a STEP-NC data
set so that web applications can use the Modular Foundry Language API
and STEP Resource Locatiors (STRL's) to extract information about the
process and correlate it with information about the product and process
being machined.<br>
<br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/Traceability.txt">ftp://ftp.steptools.com/private/NIST/Presentations/Traceability.txt</a><br>
<br>
We discussed the requirements for closed loop machining. After much
discussion, a schema was outlined that will allow points and axes in
the STEP-NC program to be modified using the difference between the
as-designed and as built geometry of a part or assembly. Martin
Hardwick and Fiona Zhao will refine this scheme and propose a revised
information model at a future meeting.<br>
<br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/STEP_closed_loop.ppt">ftp://ftp.steptools.com/private/NIST/Presentations/STEP_closed_loop.ppt</a><br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/dm_feature_harmonization.doc">ftp://ftp.steptools.com/private/NIST/Presentations/dm_feature_harmonization.doc</a><br>
<br>
We discussed tolerance tracking. The Boxy part contains many workpieces
showing the state of the part before and after each machining step.
Many of these parts are toleranced and users and applications would
like to be able to track the evolution of the tolerances at each stage
of the machining. Two solutions were discussed. The first solution
allows a tolerance to be modeled on multiple workpieces. This solution
will require changes to the STEP resources and it will be challenging
to implement. A second solution modifies the ARM of AP-238 to allow for
the tracking of tolerances, datums and surface finish requirements
between workpieces. This solution can be implemented by a combination
of intelligent software on or off the CNC control and user interfaces.<br>
<br>
We discussed operator notes. STEP-NC AP-238 allows designers to mark up
a part using the presentation information enabled by AP-203 e2 and
AP-214 e3, and it allows a list of operator instructions to be defined
for each setup. However, it does not let an operator create messages
with useful information for other operators such as note to be sure to
clean of the chips at the end of this operation. These messages need to
be placed in context where other operators can see them and they need
to be associated with an operation so that they are not all displayed
at once. <br>
<br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/Other_new_models.txt">ftp://ftp.steptools.com/private/NIST/Presentations/Other_new_models.txt</a><br>
<br>
We reviewed the AP-214 Machine Tool Model.<br>
<br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/Manufacturing_resource_modelling_2010-06-17.pdf">ftp://ftp.steptools.com/private/NIST/Presentations/Manufacturing_resource_modelling_2010-06-17.pdf</a><br>
<br>
We reviewed the Technical Corrigendum for AP-238 edition 1 and
discussed the options for creating an Edition 2.<br>
<br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/stepnc_e2_20100618.ppt">ftp://ftp.steptools.com/private/NIST/Presentations/stepnc_e2_20100618.ppt</a><br>
<br>
We discussed the date, location and content of the next demonstration.
Ideas included machining Boxy, or a new part, at an Army location in
late October or early November, and machining a new mill turn part in
Sweden in March or June. The users would like to show CAM to CAM data
exchange, process monitoring, tolerance tracking, automated tool
selection and closed loop machining.<br>
<br>
An archive has been made of all the material submitted and you are
encouraged to visit to get more information on all these topics.<br>
<br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/">ftp://ftp.steptools.com/private/NIST/Presentations/</a><br>
<br>
Pictures can be found in the following subdirectory.<br>
<br>
<a class="moz-txt-link-freetext" href="ftp://ftp.steptools.com/private/NIST/Presentations/Pictures/">ftp://ftp.steptools.com/private/NIST/Presentations/Pictures/</a><br>
<br>
Respectfully submitted<br>
<br>
Martin Hardwick<br>
Team Leader STEP-Manufacturing<br>
President STEP Tools, Inc.<br>
Professor and Acting Head of Computer Science, RPI<br>
<br>
Action Items<br>
----------------<br>
Fred Proctor to develop Tool Requirements Model<br>
US Army to determine if Rock Island, Picatinny or Watervliet Arsenal
can be the location of the next machining demonstration<br>
Martin Hardwick and Fiona Zhao to develop a next iteration of the
closed loop machining model<br>
John Michaloski and STEP Tools to develop process monitoring model and
interfaces<br>
KTH and Sandvik to consider requirements for a Mill Turn demonstration.<br>
Boeing, STEP Tools and Sandvik to consider requirements for an
automated tool selection demonstration.<br>
</body>
</html>