DMSC Committee Charter
Draft 22 June 2012
Title of Committee: Quality Measurement Standards (QMS) Committee
Responsibility:
The QMS Committee will be responsible to

Supervise the development of a set of interface specifications, namely, QMPlans, QMRules,
QMResources, QMExecution, QMResults, and QMStatistics, defining quality measurement
information within an integrated XML Schema framework called the Quality Information
Framework (QIF). The upstream and downstream activities defining and consuming the
information defined by each specification in the QIF are illustrated in Figure 1.

Ensure that QIF development is in harmony with current and future versions of the Dimensional
Measuring Interface Standard (DMIS) and the I++ DME (Dimensional Metrology Equipment)
Interface specification. QIF is not designed to replace either DMIS or I++ DME. The way DMIS
and I++ DME relate to the QIF is shown in Figure 1.

Supervise the work of the QMOnmachine and QMDirectives Working Groups (WG), which is to
advise

o
Non-DMSC standards committees defining information upstream (e.g., STEP, AS9102) or
defining information related to the QIF specifications (e.g. STEP-NC), as illustrated in
Figure 2
o
The various QIF working groups, informing them of the constraints inherent in standards
activities upstream of and related to QIF, as illustrated in Figure 2
Together with the DMSC Executive Director,
o
Act as liaison to appropriate standards organizations (e.g., ANSI, ISO, AIAG, MTConnect
Institute), to enter into Memorandums of Understanding and to submit DMSC
specifications for national and international standardization
o
Protect the intellectual property of the specifications and standards to ensure open
development and use throughout the life of the specifications and standards
A more precise definition of the scope and responsibilities of the four QIF specification-writing working
groups (QMRules, QMPlans, QMResults, and QMStatistics), the two advisory working groups
(QMOnmachine and QMDirectives), and the DMIS development working group (QMExecution) is
defined later in this document. The organizational structure, defined to facilitate this effort, is
illustrated in Figure 3. The QMS Committee will not be responsible for the detailed technical integration
of the various working groups under its supervision, which will be performed by the QIF working group,
as shown in Figure 3. The QMS Committee will be expected to resolve irreconcilable technical
differences, if ever they occur, and to perform important decisions required by the latest version of
ANSI-approved DMSC Operating Procedures.
Scope:
The scope of the work of the QMS Committee will be quality measurement information. Quality
measurement information consists of quality measurement results, any information required to
generate, process, or analyze those results, and any statistical quantities gotten from the analysis of
those results. By this definition, quality measurement information will include things like measurement
Figure 1: A CAQ system implementing the Quality Information Framework. Activities (in trapezoids)
and the QIF-integrated interface specifications (in rectangles) between the activities are shown. The
QMS committee is responsible to oversee the development of each of the interface specifications,
QMPlans, QMRules, QMResults, and QMStatistics, shown in this figure, and manage their formal
standardization. These specifications will be integrated into the Quality Information Framework
(QIF). The activities and information shown in this figure constitute what is sometimes called a
Computer-Aided Quality (CAQ) system. DMIS and I++ DME define the information on two key
interfaces within the “Execute the Measurement” activity. The scope of both DMIS and I++ DME is
dimensional metrology on CMMs. The QMS committee does not oversee the development of either
DMIS or I++ DME, but ensures that the QIF is in harmony with them. The QMExecution working
group (see Error! Reference source not found.) is responsible for DMIS.
actuals (as-measured) – including dimensional, non-dimensional, real-valued, attribute, and binary
values – measurement nominals (as-designed values), measurement tolerances, measurement process
plans, measurement equipment specifications, geometric features, geometric dimensions, and quality
control frames. The scope of the QMS Committee includes but is not limited to dimensional metrology.
At the heart of this effort is quality measurement information passed between components of
Computer-Aided Quality (CAQ) systems, such as information between measurement planning,
measurement execution, and measurement analysis activities (see Figure 1).
Quality measurement information can also flow into and out of a CAQ system, as illustrated in Figure 2.
Directives to perform quality measurements in a CAQ system can come from a variety of modern
software components, including MES (Manufacturing Execution Systems), PLM (Product Lifecycle
Management), ERP (Enterprise Resource Planning), CAD (Computer-Aided Design), QMS (Quality
Figure 2: QMDirectives and QMOnmachine working groups: The purviews of these two WGs is
illustrated in this graphic, where the QMDirectives WG monitors and advises all standards efforts
providing data downstream to a CAQ system and the QMOnmachine WG monitors and advises
machine tool standards efforts involved in quality measurement on-machine.
Management Systems), and SCM (Supply Chain Management), as shown inFigure 2. Quality
measurement results can also flow to a variety of modern software components, including QIS (Quality
Information Systems), MSA (Measurement Systems Analysis), SPC (Statistical Process Control), MES, and
SQC (Statistical Quality Control). Summary quality statistics commonly are analyzed by human experts,
either to accept/reject parts or make intelligent adjustments to the manufacturing process or part
design constraints. This flow of information is commonly either in the minds of humans, written with
pencil and paper, entered into spreadsheets, or digitized in proprietary specifications. Very few
standards and open specifications have been written to define digital versions (usually XML Schema) for
this type of information, with a few notable exceptions, for example, B2BMML1 and eAPQP2.
Background:
The development of standards and specifications in the CAQ domain has been active for many years.
The Dimensional Measuring Interface Standard (DMIS), a programming language for Coordinate
Measuring Machines (CMMs) has been in development and use for around thirty years. DMIS continues
to experience broad adoption worldwide. The development of DMIS continues under the supervision of
the QMS Committee, under the QMExecution WG, but outside the purview of the QIF WG, as shown in
Figure 3.
The interface between the execution activity and a software controller (see Figure 1) for a coordinate
measuring machine (CMM) has been defined in the I++ DME (Dimensional Metrology Equipment)
Interface, a freely available and freely implementable interface specification. I++ DME has enjoyed
broad adoption worldwide, so the QIF development effort will stay in alignment with the latest versions
of I++ DME.
Approach:
The QMS committee will adopt a holistic approach to interface standards development. In the past,
quality measurement standards and specifications have been developed in isolation, each targeting a
single interface between components within a CAQ system (see Figure 1). The quality information
framework (QIF) is different, in that it will consist of individual standards derived from common data
types and generic structures, ensuring harmony between QIF standards.
All quality information will be defined in a manner separable from any particular transport technology
and information-modeling language, so that, as transport technologies and modeling languages change,
the underlying quality measurement information can be remodeled without undue effort. Standards
development is initially expected to be XML Schema based, which will allow the standards developed to
be in harmony with schemas currently in use by a multitude of businesses worldwide.
1
B2MML is representation of the ANSI/ISA 95 family of standards (ISA95), known internationally as IEC/ISO 62264, in XML
Schema (see http://www.wbf.org/catalog/b2mml.php).
2
eAPQP is representation in XML Schema of quality information referenced in the AIAG’s (Automotive Industry Action Group)
APQP (Advanced Product Quality Planning) specification.
The committee will integrate and stay current with the relevant standards, such as ISO 10303, (e.g., STEP
AP203, AP214, AP219, AP238, and AP239), quality management standards (e.g., ISO 9001, ISO 16949,
AS9102), and open specifications and guidelines documents (e.g., I++ DME, I++ DMS3, QMD4, and APQP).
The stakeholders for the group of standards under the direction of the QMS committee will include end
users, tier suppliers, and technology providers in a broad array of business sectors including Aerospace,
Automotive, Defense, Power Generation, Nanotechnology, Electronics, Medical and Pharmaceutical,
Heavy Machinery, Marine, Plastics, and Consumer Goods.
Figure 3: DMSC Organizational Structure
Organization of the Committee and its Working Groups
Information models and interface specifications in each technical area under the supervision of the QMS
Committee will be developed by four separate working groups (WGs): QMPlans, QMResults, QMRules,
QMStatistics. QIF will itself be a specification also under the supervision of the QMS Committee. All
3
I++ DMS is a freely-available specification of measurement planning information worked on within the I++ Group,
a European consortium of automobile manufacturers.
4
Quality Measurement Data (QMD) defines quality measurement results and was worked on within the AIAG.
information common to all the sister specifications will be collected into QIF, which can be thought of as
a library of common information elements, which will be utilized by all the individual specifications:
QMResults, QMPlans, QMRules, and QMStatistics.
The QMExecution WG will be responsible to maintain and advance the DMIS standard and ensure that
DMIS is in harmony with the integrated set of QIF specifications (upstream and downstream) and I++
DME (downstream), as illustrated in Figure 1. The QMS Committee will also supervise the work of the
QMExecution WG.
Two more working groups will be under the supervision of the QMS Committee: Quality Measurement
On-Machine (QMOnmachine) and Quality Measurement Directives (QMDirectives), whose monitoring
and consulting activities are suggested in Figure 2. Neither QMOnmachine nor QMDirectives will be
responsible to develop any specifications, but will need to provide expert advice to related information
standards efforts. Relevant to QIF are several existing standards upstream to CAQ. Such standards
include ISO9001, AS9102, AP242, AP239, PPAP, ISA95, and APQP. There are a couple of existing
standards, which require the type of quality information defined in QIF Standards, namely STEP AP238
and MTConnect. A more detailed description of the work of these and all other WGs is described later
in this document.
Justification:
Properly defined and implemented, this new holistic standards framework called QIF will facilitate low
cost, low risk, and high integrity exchange of manufacturing quality measurement information anywhere
in the enterprise . Beyond cost savings, risk reduction, and improved information quality, successful
development and adoption of this framework will contribute toward a science-based approach to the
manufacture of complex, high-value, knowledge-intensive products, through the unimpeded flow of
quality measurement information in the framework. The framework will allow for the streamlined
development, integration, and support of manufacturing quality systems and components for all types
of quality measurement (e.g., dimensional, non-dimensional, binary, attribute, and variable), while
maintaining the scalability necessary to adapt to an ever-changing manufacturing quality landscape.
Working Group (WG) Descriptions:
Quality Information Framework (QIF):
Scope:
 Quality measurement results, and the information needed to generate those results,
which are common to two or more interfaces in the CAQ system (see Figure 1), including
all types of quality measurement information (e.g., dimensional, non-dimensional,
binary, attribute, and variable). For example, nominal features and tolerances as well as
traceability and statistical information are shared by two or more interfaces in the CAQ
system, and therefore will be in the scope of the QIF WG.
Out of Scope:
 Any quality measurement information unique to one interface in a CAQ system


Design and production (e.g., machining) information, since this information is (and is
being) defined within other standards groups, even though QIF will be integrated with
design and production information
Enterprise level information, e.g. orders, billings, and quality control plans
Approach: The QIF working group will work organically with all the other working groups under
the QMS Committee, so that many of the members of the various working groups are expected
to participate in the QIF WG. “Integration into QIF” means that information definitions common
to the individual specifications (for example, nominal features and tolerances) will be defined in
a separable specification called QIF.
Justification: Standards are organic entities, requiring integrated definition. The definition of
information common to several interfaces, performed by the QIF WG, will allow 1) more unified
and efficient standards development and 2) more interoperable implementations.
Deliverables: An XSD schema, a disambiguating dictionary, and implementation guidebook.
Quality Measurement Plans (QMPlans):
Scope: All product characteristic and quality management information required by quality
measurement programs to be executed on quality measurement equipment. QMPlans will
largely consist of product characteristic features and associated tolerance values and will not
include all information necessary and sufficient to create a quality program; QMPlans
specifically excludes information on measurement equipment, measurement sensors, and
feature measurement rules.
In scope:
 Non-dimensional product information, e.g., product IDs, customer information, key
contact, temperature, reflectance, and malleability
 Dimensional product information, e.g., geometric features, measurement features,
nominal dimensions, measurement features, and tolerance values
 Product characteristics
 Quality plan Information
 Traceability values and pointers
 Reaction plan defining corrective action, if any
 Work instructions
 CAD entity relationships
Out of scope:
 CAD storage and extraction methods (domain of manufacturing CAD design and outside
of CAQ altogether)
 Quality measurement equipment and sensor definition, but QMExecution WG will be
responsible specifying specific boundaries, which may and will constrain choice of
equipment and sensor (there appears to be no call from industry to define a standard
for equipment and sensors)
 Measurement rules (domain of QMRules WG)
 Low Level Planning or “Programming” (domain of DMIS and the QMExecution WG)
Justification: There is no single standard format for defining measurement plans at the level
above measurement programs. Measurement plans are required by quality departments to
efficiently and effectively validate conformance of manufactured goods to design specifications.
Small, medium and enterprise manufacturers suffer from the need to transpose measurement
information from one system to another. In this process, valuable time is consumed and human
mistakes are made. The need for a common information definition for measurement planning to
carry quality requirements information from one system to another is being requested by both
quality measurement systems users and their technology providers.
Specification development and implementation lifecycle:
 Identify and define relevant use cases
 Make the specification both scalable and extensible
 Define and maintain access control and versioning
 Define a business case
 Build the information model
 Define each item of information in the schema
 Define semantic constraints in natural language for each item of information
 Define semantics constraints in natural language for sets of information elements
 Define and document implementation guidelines
 Identify elements shared by other QIF specifications and refactor them into the QIF
specification
 Create sample QMPlans files for dissemination and testing
 Create a specification and implementation guideline document
 Generate/utilize implementation (file) validation tools
 Conduct pilot tests at user and vendor facilities
 Conduct conformance and public interoperability tests on vendor implementations
 Define conformance certification criteria
Deliverables: An XSD schema with all necessary semantic constraints, an implementation
guideline document, sample QMPlans files, QMPlans conformance test utility, and QMPlans
conformance criteria.
Quality Measurement Rules (QMRules):
Scope: For each possible feature type on a part, QMRules will define the information elements
required to fully specify and constrain the measurement on that feature type. The information
elements will include things like measurement point density, measurement path constraints,
sensor types, and measurement throughput constraints.
In scope:
 Product measurement path and sampling method for each product feature type
 Product measurement constraints and requirements
 Rule ID and corporate ownership
 Throughput constraints
Out of Scope:
 GD&T definitions
 Exhaustive sensor and DME descriptions
Justification: There is no single standard format for defining measurement rules required by
quality departments. Quality system users are often unable, in a multi-vendor environment, to
define and apply a consistent rule set independent of the particularly vendor system employed
for a given measurement. These same users currently suffer an uncertainty about the quality of
the measurement results coming from these different systems. In this process, valuable time is
consumed and human mistakes are made. Both quality measurement systems users and their
technology providers are requesting standard measurement rules definitions.
Specification development and implementation lifecycle:
 Identify and define relevant use cases
 Make the specification both scalable and extensible
 Define and maintain access control and versioning
 Define a business case
 Build the information model
 Define each item of information in the schema
 Define semantic constraints in natural language for each item of information
 Define semantics constraints in natural language for sets of information elements
 Define and document implementation guidelines
 Identify elements shared by other QIF specifications and refactor them into the QIF
specification
 Create sample QMRules files for dissemination and testing
 Create a specification and implementation guideline document
 Generate/utilize implementation (file) validation tools
 Conduct pilot tests at user and vendor facilities
 Conduct conformance and public interoperability tests on vendor implementations
 Define conformance certification criteria
Deliverables: An XSD schema with all necessary semantic constraints, an implementation
guideline document, sample QMRules files, QMRules conformance test utility, and QMRules
conformance criteria.
Quality Measurement Results (QMResults):
Scope: Scope will consist of quality measurements of dimensional and non-dimensional entities.
The actual measurement values will be both numerical and non-numerical (attribute or binary).
Measurement results will not only include raw measurement values, but also summary
statistical or derived results (e.g., cylinder radius with standard deviation). Measurement results
will also include description of the algorithmic means (e.g., least squares) by which the derived
results are calculated. All necessary nominal (as designed) target values will also be included to
allow reanalysis, if required. Any other information relevant to one or more measurements will
also be in scope, information such as the shift, the equipment operator’s name, the ID and
feature of the item measure, the date & time of the measurement, etc.
Out of scope: Measurement results straight out of the measurement sensor are not in scope
(e.g., RS232 formatted numerical values). Only after these results are filtered, transformed,
and/or collated with other related measurements and quality information, such as part IDs and
operator name, will they be in the scope of QMResults WG.
Approach: The QMResults WG will represent the detailed quality measurement results
information in XML Schema, to allow computer-readability, transportability, ease of
implementation, ease of integration, and low cost of implementation. The QMResults WG will
utilize much of the information defined by the QIF WG and will work in concert with them.
Because of the broader scope to include all quality measurement results and relevant quality
information, the approach of this development is expected and desirous to include users and
vendors outside of the traditional dimensional metrology sector.
Specification development and implementation lifecycle:
 Identify and define relevant use cases
 Make the specification both scalable and extensible
 Define and maintain access control and versioning
 Define a business case
 Build the information model
 Define each item of information in the schema
 Define semantic constraints in natural language for each item of information
 Define semantics constraints in natural language for sets of information elements
 Define and document implementation guidelines
 Identify elements shared by other QIF specifications and refactor them into the QIF
specification
 Create sample QMResults files for dissemination and testing
 Create a specification and implementation guideline document
 Generate/utilize implementation (file) validation tools
 Conduct pilot tests at user and vendor facilities
 Conduct conformance and public interoperability tests on vendor implementations
 Define conformance certification criteria
Justification: A couple of open specifications and one standard already exist in this space,
namely, DML (Dimensional Markup Language), QMD (Quality Measurement Data), and DMIS
(output), with DMIS (output) coming from the DMSC and the two specifications coming from the
AIAG (Automotive Industry Action Group). So why is the QMResults WG needed? DMIS
(output), DML, and QMD all address a particular niche in the Quality Measurement space,
whereas QMResults addresses a broader space. DMIS (output) is text based and has not
enjoyed wide acceptance. Finally, QMResults, together with all the other planned
specifications, takes an altogether different (i.e., integrated) approach to quality measurement
standards.
Quality Measurement Statistics (QMStatistics):
Scope: Scope will consist summary statistics, typically from multiple parts and features, of
quality measurements of dimensional and non-dimensional entities.
Out of scope: Individual raw measurement values.
Specification development and implementation lifecycle:
 Identify and define relevant use cases
 Make the specification both scalable and extensible
 Define and maintain access control and versioning
 Define a business case
 Build the information model
 Define each item of information in the schema
 Define semantic constraints in natural language for each item of information
 Define semantics constraints in natural language for sets of information elements
 Define and document implementation guidelines
 Identify elements shared by other QIF specifications and refactor them into the QIF
specification
 Create sample QMStatistics files for dissemination and testing
 Create a specification and implementation guideline document
 Generate/utilize implementation (file) validation tools
 Conduct pilot tests at user and vendor facilities
 Conduct conformance and public interoperability tests on vendor implementations
 Define conformance certification criteria
Justification: One open specification already exists in this space, namely, QMD (Quality
Measurement Data), coming from the AIAG (Automotive Industry Action Group). So why is the
QMStatistics WG needed? QMD addresses a particular niche in the Quality Measurement space,
whereas QMStatistics addresses a broader space. Finally, QMStatistics, together with all the
other planned specifications, takes an altogether different (i.e., integrated) approach to quality
measurement standards.
Quality Measurement Execution (QMExecution):
Scope: In scope is the DMIS language for programming coordinate measurement machines
(CMM) and therefore includes all information necessary to precisely and completely specify the
measurement of some item with a particular measurement device or system. The item
measured may be any quality-related characteristic, either dimensional or non-dimensional and
generating a variable, attribute, or binary value. In the case of geometrical measurements, such
a process plan will specify precise points and paths and particular measurement devices and
sensors. Sometimes this process plan has been called “a low-level measurement process plan”
or alternatively a “part program.” The methods and algorithms used to compute abstract
geometric elements (e.g., radius) from measured points may be specified in the detailed plan.
The QME WG will be responsible for maintaining the ANSI/ISO DMIS standard and ensure that it
is in harmony with the QIF specifications and the I++ DME Interface specification.
Out of Scope:
 Measurement results (measurement “actuals”), which is in the purview of the
QMResults WG
 Calibration and precise error map information for the measurement device and sensor,
which is the responsibility of the “Control the Equipment” activity in Figure 1
Justification: The DMIS language is pervasive in the industry and there is therefore little call for
a radical departure from DMIS, particularly given the massive installed base of DMIS part
programs.
Approach: To get into harmony with the new
QIF approach, DMIS will need non-trivial
redefinition. After this effort, new versions of
DMIS will have to be generated as the nature
of dimensional metrology changes and
improves.
Deliverables: New versions of DMIS
submitted and approved by ANSI and ISO.
Figure 4: Activity model for machining with
standard (STEP-NC) and open non-proprietary
(MTConnect) interface languages. An older, open
specification, G Code, is increasingly being
superseded by STEP-NC, though the descriptive
scope of STEP-NC is much broader than G Code.
Quality Measurement On-Machine
(QMOnmachine):
Scope: The QMOnmachine WG will work
within active standards groups who are
developing in-process (e.g., on-machine)
quality measurement. For example, the ISO
STEP AP238 (STEPNC) is currently such an
effort. The QMOnmachine WG will work
within these groups to ensure harmony with
other working group content, particularly the
QMP and QMR WGs.
Approach: QMOnmachine WG members will
act as liaisons to these CAM information
standards groups and report to the QMS
Committee as appropriate. Metrologists having additional expertise in manufacturing
production, generally, and machining, particularly, will be most helpful in the work of the
QMOnmachine WG. As can be seen from Figure 4, the activities and interfaces do not well match
with those of CAQ systems as illustrated in Figure 1.
Justification: Computer-Aided Manufacturing (CAM) experts are understandably weak in the area
of quality measurement, but the market is increasingly calling for in-process measurement for inprocess parameter adjustment through quality measurements. This calls for involvement of
expert metrologists to advise these CAM-related standards groups in the area of quality
measurement, e.g., measurement-unique features and datums. Furthermore, the standards the
QMS Committee plans to develop will eventually be integrated with the CAM standards due to
these trends.
Deliverables: Demonstrable input to the work of the QMS Committee efforts from the CAM
standards community and vice versa.
Quality Measurement Directives (QMDirectives):
Scope: In scope are all quality measurement directives from the Enterprise through CAD, PLM,
MES, ERP, SCM, and QMS systems or software (see the QMDirectives portion of Figure 2). Initial
focus will be product design, or Computer-Aided Design (CAD), languages, whether standard,
quasi-proprietary, and proprietary, which are intended to be used downstream for planning and
executing various measurements to ensure product quality.
Approach: The QMDirectives WG will participate with all relevant CAD language development
groups including those groups working on true standards (e.g., AP203, AP214) and those groups
involved with proprietary or quasi-proprietary specifications (e.g. JTOpen, Catia, NX, ProEngineer)
to ensure harmony with other working group content. The QMDirectives WG will particularly
drive “CAD + semantic PMI” efforts, these being so important for automatic (digital) use of CAD
for downstream quality measurement. Currently there is such an effort within the ISO STEP and
PDES organizations. Members of this working group should be closely involved or aware of the
output and progress of these groups, ideally guiding those efforts to make sure quality
measurement planning requirements are address in their CAD + semantic PMI efforts. As other
Enterprise-level software systems, such as PLM, MES, ERP, and QMS, define Quality
measurement directives in digital format, the QMDirectives WG will need to join with these
efforts so that the information defined is consistent with downstream requirements for quality
measurement.
Justification: Quality Measurement Directives are the source of requirements for quality
measurements, so there needs to be a consonance between the content and format of those
directives and the requirements of CAQ systems. A working group to define those requirements
and maintain harmony between disparate standards is necessary for the QIF to succeed.
Deliverables: A set of quality measurement requirements for upstream processes such as design
and quality management and to ensure that the requirements are delivered to the correct
standards bodies and which hopefully get integrated into key standards such as AP242, ISO
16949, and AS9102.
Member Interest Categories
The QMS Committee and its working groups will seek workers from the following categories of
companies and keep the relative numbers from each category in balance as required by ANSI and DMSC
rules:


User – a company or individual using quality measurement software and equipment. Users
typically buy products from software vendors. In some cases users may develop their own
software, which is used within their company.
Vendor – a company or individual developing quality measurement software products or
equipment.

General Interest – organizations having an interest in cooperative efforts to promote
manufacturing productivity, typically government agencies, industry umbrella organizations, and
standards development organizations.
Glossary of Acronyms
 CAQ: Computer-Aided Quality
 MES: Manufacturing Execution Systems
 PLM: Product Lifecycle Management
 ERP: Enterprise Resource Planning
 CAD: Computer-Aided Design
 QMS: Quality Management Systems
 SCM: Supply Chain Management
 CAM: Computer-Aided Manufacturing
 QIS: Quality Information Systems
 MSA: Measurement Systems Analysis
 SPC: Statistical Process Control
 MES: Manufacturing Enterprise System
 SQC: Statistical Quality Control