DML Specification Working Group

QIF Working Group Meeting Minutes

Volunteer Agreement You hereby agree, by your participation in any activity of this standards committee (including committee meeting attendance, email exchanges, phone conversations, or document generation), that you will not disclose any corporate confidential information or corporate trade secrets either verbally or in writing. Furthermore, any information disclosed to you in any activity of this standards committee, or disclosed to you in documents produced by this committee, will be provided to you for the sole purpose of establishing an industry-wide standard pursuant to the procedures prescribed by ANSI and ISO. You therefore agree not to use this information, or to collaborate in its use, in any manner that might suggest you have any proprietary rights to such information, such as rights to a patent, trademark, or copyright.

Meeting Date/Time: 14 December 2011/1415 - 1715 h Meeting Place: NIST, Gaithersburg, MD, Shops Conference Room Chairman: Bill Rippey, NIST Report Submitted by: Bill Rippey, NIST Date Submitted: 21 December 2011 Distribution: QIF Working Group, DMSC Board, general interested public

Agenda: 1. Pre-meeting Introduction to QIF (outside the WG meeting - see attachment) 2. Review minutes of last meeting 3. User Input on Needs 4. Strategy on QIF next steps 5. New business

Attendees (* attended by teleconference) Name Company Status Admire, Ray Lockheed Martin Member Baldwin, Jon Metrosage Observer Brown, Curtis Honeywell FM&T Member Fredricksson, Mats Mitutoyo Scandinavia Member Hayes, Eric Nikon Metrology Member Hoffman, Scott* Validation Technologies Member Horst, John NIST Member Kramer, Tom NIST Member Lane, Kyle Mitutoyo America Member Li, Liming Mitutoyo America Member Maggiano, Larry Mitutoyo Member Orchard, Nick Rolls Royce Observer Pippenger, Brian Rolls Royce Guest Rippey, Bill - secretary NIST Member, chair Saunders, Per* Rolls-Royce Observer Steele, Craig Lockheed Martin Guest Strobel, Randy* Renaissance Services Guest Tandler, Bill Multi Metrics Guest Triolo, Luca* Coord3 Guest Warndorf, Paul AMT Guest via MoU

Action Items: None were generated.

Decisions Made: No consensus decisions were made.

Recommendations: No consensus recommendations were formulated. The following items evolved during the strategy discussions:  Continue pursuit of FAI pilot project, and development of the QMPlans specification.  For QMStatistics, develop the formal business case, requirements, and scope at a near-future QIF WG meeting.  Consider the date of the next MTConnect TAG meeting, 14 Feb 2012, as a possible milestone for QIF development.  See "group discussion produced these items on strategy" in the meeting notes for a list of strategy items under consideration.

Meeting Notes:

Pre-meeting overview of QIF We took advantage of the Model-Based Engineering (MBE) & Technical Data Package (TDP) Summit being held at NIST to invite some of its attendees to the QIF WG meeting. The Summit is sponsored by NIST, Army Research Lab, and OSD ManTech. A morning session preceded the WG meeting, on "Introduction to QIF", and was not part of the formal WG meeting. See appendix A for notes on this gathering.

Review minutes of last meeting Rippey scanned highlights of the 10 pages of minutes from the 24-26 May 2011 meeting held in South Carolina as a way to introduce status of QIF and to identify items brought up. There were no corrections or additions.

User Input on Needs There was no rating of needs or consensus. Discussion included the following items. QIF support of FAI and use of QMStatistics for low volume lots/determine process capability, were seen as valuable uses of QIF. LMI wants to specify FAI AS9102a requirements, but have contractors supply the inspection results data - thus the final document would have data from multiple organizations (a good application for a data standard). One user "pain" is need to enforce consistency in inspection planning, including finding how to systemize best practices of inspection strategies - a possible role for QIF/QMPLans. Some companies use the terminology "CAV", for characteristic attribute verification. Strategy: Support of QIF by multiple solution providers (not just one) is needed to get traction. Strategy: It is likely important that total user company commitment will be needed for QIF traction, since multiple departments share data.

Strategy of QIF next steps Before the discussion began, Rippey summarized some background issues on strategy in three areas. Shopping list of possible actions: • Technical Development – Define full QIF scope – Develop detailed data model(s) – Develop application area specification documents – Validate data model(s) – Provide documentation for usage, data model semantics • Outreach – Marketing – Technical education – Persuade people/companies to adopt QIF

Previous insights on QIF strategy include: • So far we have had a small working group • How can we harness existing resources to make progress, and make sure QIF thrives. • How can we increase our working group resources? • Our documentation development competes with technological development for resources. • Will pilot projects accelerate testing, interest, proliferation? • How can we find out users' data requirements, what they are, and their priority?

Summary of unprioritized recommendations from the previous QIF strategy meeting: • Create new areas of QIF: QMRules, QMStatistics, QMResources. • Hone design requirements via use cases • Design: adopt a policy/approach for schema extensibility that maintains interoperability • Pursue FAI requirements • Generate documentation {illustrate business case, specify business case and schema requirements, document current schemas, generate ANSI document, data dictionary} • Establish liaison with ISO TC 184, the developers of AP 242 • Fully annotate schemas • Perform outreach, marketing (to get additional volunteers, expand technical usage, assess needs and applications) • Pursue ANSI and/or ISO standards • Maintain standards via SIR The group discussion produced these items on strategy. The group did not pursue consensus or prioritization. • FAI pilot and validation is high priority – Needs QMPlans spec – Establishes credibility • “QMPlans is the sexiest part of QIF.”- business case includes: capture human expertise, shows cost savings, reuse of plans, there is no competition from other interoperable formats • Goal: Appeal to users for PULL for QIF • Try SBA grants? SBIR funding? Task: demo real functionality and interoperability (not illustrate the data model) • Avoid failure. Bad publicity can impair or doom acceptance. • Show concrete evidence of saving $$ • Find how to succeed in the current economy • QMResults could complement with MTConnect (though there is competition from other formats) • Find external funding to accelerate projects • Business case for QMResults (LM) – support comparison of measurement results for different DMEs (e.g., correlation between touch trigger points and laser scanner).

Other discussion items included: • Does QMResults handle point clouds? i.e., higher order measurement entities, QMResults has a CAD model reference ID. Can it be used for comparison of touch trigger measurements to e.g., laser scanner results? (a possible QIF business case example). • Eric: Nikon is considering a common platform for reporting. How can we show Nikon development group that QMResults is desirable/attractive? Possible conference call with product manager about development benefits of QIF/QMResults? (e.g., save cost/effort/time of developing the data model)?

New Business There was energetic discussion of QIF technical design regarding the newly proposed application area of QMStatistics. As there is not yet a WG for this effort, we tabled the discussion and recommend that a near-future QIF meeting be held to refine working statements of business case, requirements, technical scope of QMStatistics. The discussion must consider issues of possible overlap with QMResults content.

Next Meeting The next physical QIF WG meeting was suggested for mid-May 2012 in South Carolina.

There was no discussion of a proposed agenda.

Appendix A - Proceedings of the Introduction to QIF morning session John Horst took the notes for this meeting.

This session was not part of the formal QIF WG meeting, since much of the information presented was background and status.

Time Subject Facilitator/Presenter 0830 Welcome, introductions, and local knowledge; state Admire / Horst meeting goals, gather meeting expectations, and proposed agenda 0900 DMSC overview Admire 0915 QIF: what it is, its potential, current status, business Rippey case, and progress 1000 AS9102 Pilot project status Admire, Rippey 1030 Break 1045 Quality Measurement on-machine (QMO) WG Status Rippey / Horst / – MTConnect + QIF activities Warndorf 1130 Quality Measurement Directives (QMD) WG Status - Horst / Maggiano PDES, LOTAR PMI, STEP AP242, CAx-IF groups – QMPlans and quality directives from CAD report and discussion 1215 LUNCH (on your own) QIF WG Meeting in the afternoon

Attendees:

Name Organization Interest Category John Horst NIST Standards Brian Pippenger Rolls Royce User Mats Fredricksson Mitutoyo Scandinavia Vendor Joe Zink (remote) Hexagon Vendor Bill Tandler Multi Metrics Vendor Curtis Brown Honeywell FM&T User Tom Kramer NIST Standards Nick Orchard Rolls Royce User Bill Rippey NIST Standards Ray Admire Lockheed Martin User Kyle Lane Mitutoyo America Vendor Liming Li Mitutoyo America Vendor Paul Warndorf AMT Standards Eric Hayes Nikon Metrology Vendor Larry Maggiano Mitutoyo America Vendor Per Saunders (remote) Rolls Royce User Scott Hoffman (remote) Metrology Integrators Vendor Randy Strobel (remote) DISCUS Software Vendor Luca Triolo (remote) Coord3 Vendor

Meeting Notes: Meeting began at 08:55AM Eastern. It ended at 1:15 PM.

DMSC Overview - Admire presented the DMSC history and summarized the activities of the current committees and working groups. His presentation is available as "2011- DMSCPresentation.pdf"

QIF Overview - Rippey presented an overview of the QIF business case, data model, and a peek at the XML schemas. His presentation is available as "IntroToQIF_2011.pptx".

FAI Pilot Project - the QMResults WG has begun a pilot project with Lockheed Martin on AS9102a first article inspection. Admire gave the status of the effort and an information flow diagram. The next steps include measuring the artifact part at LMI on two CMMs, and developing an XML schema for the AS9102a forms that is traceable to QIF schemas.

Quality Measurement on Machine (QMO) WG status - Rippey shared his slides, proposing cooperation between DMSC and MTConnect, that were presented to a recent MTConnect Technical Activities Group (TAG) meeting. The idea is that MTConnect may adopt QIF specifications for conveying quality data, to avoid developing their own specifications. To date the QMResults WG has advised Will Sobel on mapping registers from a client's machine tool inspection interface to elements of the QMResults schema.

Quality Measurement Directives WG Status - Maggiano presented status of the QMDirectives working group’s thinking about the relevance to QIF of upstream design activities, both proprietary and standards-based. One of his questions is how will the gap between MBE CAD design and downstream quality processes be bridged? A particular need is to facilitate automation of downstream inspection process planning driven by CAD and PMI - the idea of a pilot demo implementing a prototype connection from FBTol to generation of QMPlans.xml was mentioned. Larry's presentation is available as "MBE_QMD_Dec2011.pptx". The CAX implementer's forum, www.cax-if.org, is one source of information about STEP-related CAD.

General QIF discussion - There was some discussion on the current division of information into QMPlans, QMResources, and QMRules, which may need some further high level analysis. Also discussion on the need to connect information from, for example, QMResources back to the designer. Scott Hoffman argued that QIF defines all data (the “what”) in the quality measurement process, and does not define or constrain elements of the processes. --/--