A CMM projected circle report can support approval when it documents a defined constructed location relationship, but its displayed diameter is not automatically evidence of a physical bore size. Before approving a result, identify the input feature, target plane, alignment, construction method, reported property, software version, and the exact drawing criterion the result is meant to evaluate.
Start with the approval question, not the report label
“Projected circle” sounds like a simple dimensional result. In a report review, it is better treated as a software-created entity whose relevance depends on the question being asked. A buyer should not approve or reject a part merely because a report contains a circle, a diameter, and a pass/fail color.
The first decision is whether the drawing or assembly need concerns:
- the intended projected location of a feature;
- the actual size of a bore or other physical feature; or
- a relationship observed in a physical assembly condition.
Those are separate inspection objectives. They can require different alignment choices, measurement strategies, evaluation methods, and report outputs. A constructed circle may be useful for the first objective while being unsuitable for the second or third.
What a projected circle is in a CMM report
A projected circle is a constructed mathematical feature. It is created in inspection software from defined inputs and a projection operation. It is not necessarily a circle directly measured on the part at the reported location.
For one documented implementation, PC-DMIS 2023.2 describes projecting an input feature’s centroid onto a plane; when no plane input is provided, the current workplane is used. That documented command assigns the projected-circle diameter as four times the probe diameter. That is version-specific software behavior, not a universal rule for CMM software and not evidence that any particular factory owns or uses that software. PC-DMIS 2023.2 documentation
The practical implication is direct: a displayed constructed diameter can be an attribute of the construction method, rather than a measurement of the bore wall, the hole’s fitted diameter, or the functional opening available to a mating component. It must not be treated as interchangeable with physical bore diameter without an agreed measurement and evaluation method.
A report reviewer should therefore ask, “What was constructed, from what, on which plane, and why?” before asking whether the dimension passes.
Four concepts that should not be merged
Confusion often starts when different geometric ideas receive the same informal label. Keep these concepts separate during drawing review and report approval.
Mathematical projected circle
This is the constructed reporting feature. Software derives it from an input and a projection definition. Its purpose may be to express an intended location on a target plane. The report should identify it as constructed and make its parent inputs traceable.
Actual oblique section
An oblique section is the real intersection produced when a plane cuts a physical cylindrical or conical surface at an angle. The resulting profile may not behave like the software’s constructed projected circle. A report should not label one as the other without stating the evaluation method.
Orthogonal projection outline
An orthogonal projection outline is the shape represented by viewing or projecting geometry perpendicular to a plane or direction. It can be useful in design communication, but it is not automatically a direct CMM measurement feature or a physical section.
Projected GD&T tolerance zone
A projected tolerance zone is a drawing-defined control concept. It should be evaluated according to the stated drawing requirement, datum reference frame, and agreed interpretation. A constructed circle in a report does not, by itself, establish that the relevant projected tolerance-zone requirement has been evaluated correctly.
These distinctions are not semantic. They decide whether a reported diameter means anything for the buyer’s acceptance question.
A decision framework for buyers and supplier-quality teams
Use the intended function to select the evidence. Do not begin with the operator’s available report template.
If the target is an intended projected location, a constructed result may be appropriate. For example, a hole center may need to correspond to a reference plane used by downstream layout, fixture planning, or mating-feature location. The buyer should request clear traceability from the constructed point or circle to the input feature and target plane.
If the target is actual bore size, require evidence from an agreed measurement and evaluation of the physical bore. The report should identify the feature evaluated, the applicable size requirement, and the relevant result. A constructed projected-circle diameter is not a substitute merely because the report uses a circle symbol or diameter field.
If the target is a physical assembly relationship, define the assembly condition. The question may involve a constrained part, a fixture, a mating component, a pin, a seal, or an interface plane. The required evidence may be a controlled assembly check, an agreed fixture-based evaluation, or another method tied to the functional condition. Do not assume a free-state constructed result proves assembly fit.
The National Physical Laboratory’s guide abstract is a useful reminder that CMM strategy should be connected to drawing requirements and that projection-related measurements, alignment, geometry, surface condition, and other inspection conditions can affect results. It supports planning discipline, not a blanket acceptance rule. NPL CMM measurement strategies
The minimum report record for approval
A buyer does not need a long program printout to make a disciplined review possible. The report package should, however, make the constructed result unambiguous. Ask for these items whenever a projected circle affects approval:
- input feature identification and its feature type;
- the target plane used for the projection;
- coordinate alignment and datum reference used for the report;
- construction type, clearly marked as constructed rather than directly measured;
- software name and version when the construction behavior affects interpretation;
- reported property being reviewed, such as constructed location or displayed diameter;
- drawing criterion the output is intended to address;
- part number, drawing revision, part identification, and inspection status;
- any agreed fixture or constrained condition; and
- reviewer disposition when the result is informational rather than an acceptance characteristic.
This record separates provenance from appearance. It also prevents a common dispute: one party thought a report value was bore size while the other party used it only to locate a projected center.
A practical workflow for approving a projected-circle result
- Read the drawing callout and functional intent. Identify whether the requirement controls actual feature size, projected location, or an assembly relationship. If the drawing is ambiguous, pause approval and request an engineering interpretation rather than asking metrology to solve a design-definition gap.
- Classify the report entity. Confirm whether the circle is directly measured, fitted from measured points, section-derived, or constructed by software. A constructed entity needs its parent features and operation stated.
- Verify the reference condition. Review the target plane, coordinate alignment, datum references, and any fixture condition. A projected location without its reference condition cannot be reliably compared with a drawing intent.
- Match the reported property to the criterion. A center location might address a projected-location question. A constructed diameter might be only a software property. Actual bore size needs actual size evidence obtained through the agreed evaluation.
- Check version and method dependence. When construction behavior affects the meaning of a result, retain the software version and method description in the approval record. Do not extrapolate a documented behavior from one release to all programs or software packages.
- Make the disposition explicit. Mark the result as acceptance evidence, supporting information, or not applicable to the criterion. If a deviation or clarification is needed, keep it linked to the drawing revision and approval decision.
Hypothetical report-review examples
Consider a hypothetical drawing review requiring the projection of a specified feature centroid onto a named plane. A constructed center can support that question if its inputs and operation match the requirement. It must not silently become the point where an angled bore axis pierces the plane: those are different constructions. The displayed constructed diameter still requires a separate relevance check before anyone compares it with a bore-size limit.
In a different hypothetical case, a buyer wants to know whether a pin will enter an opening after the component is located in an assembly fixture. A projected center report may help diagnose location, but it does not alone demonstrate clearance, interference, or insertion behavior. The buyer should define the assembly condition and the evidence required for that condition.
A third example involves an angled bore with both a size callout and a positional requirement. One report page may legitimately contain different outputs for different purposes: direct or fitted size evidence for the bore, a positional evaluation tied to the datum framework, and a constructed projected result for an agreed reference-plane discussion. The reviewer should not collapse these outputs into one “hole passed” statement.
Buyer guide: decision criteria before an RFQ or first article
Define the acceptance characteristic first. State whether each critical item is actual size, location, orientation, profile, a projected relationship, or an assembly condition. Identify the governing drawing revision and the datum framework. If the concept depends on a reference plane away from the physical feature, describe that plane and its relationship to the part coordinate system.
Then define the evidence level. For an informational construction, a clear annotated report may be enough. For an acceptance characteristic, specify the evaluation method, result format, required traceability, and who has authority to interpret an ambiguity. For an assembly relationship, explain whether the part is inspected free-state, constrained, or with mating hardware.
For components that need dedicated inspection support, see CNC Parts for Measurement Fixtures. The fixture itself should not be assumed to resolve a drawing-definition issue; it should implement a condition already agreed by engineering and quality.
RFQ questions to include
- Which drawing callout is the projected-circle output intended to support?
- Is the output acceptance evidence or informational geometry?
- What input feature and target plane must be identified in the report?
- Which alignment and datum reference frame govern the result?
- Is an actual bore-size result also required, and what evaluation is agreed?
- Is inspection free-state, constrained, or assembly-based?
- Must the construction method and software version be retained with the report?
- Which part identifiers, drawing revision, and approval fields must appear on the submission?
Red flags during report review
Treat the following as reasons to ask for clarification, not automatic evidence of part failure:
- a diameter value with no indication that it is constructed;
- a constructed circle used as the only proof of actual bore size;
- no stated target plane or alignment;
- a pass/fail result disconnected from a drawing criterion;
- software-generated terminology that has not been agreed in the inspection plan;
- an assembly-fit claim based only on a free-state geometric construction; or
- a report revision that does not identify the part or drawing revision.
Compact approval checklist
Before approval, confirm the functional question, drawing criterion, feature inputs, target plane, alignment, construction type, software version where material, reported property, and evidence required for actual size or assembly behavior. If any item is missing, classify the projected-circle result as incomplete for that decision until it is clarified.
How SUUXIANG can support clearer inspection planning
For a drawing-based CNC part or precision mold component, share the drawing, relevant model, critical callouts and requested report with SUUXIANG. Discuss your project with the intended inspection question clearly identified.
Frequently asked questions
Does a CMM projected-circle diameter prove the actual bore diameter?
No. A projected circle can be a constructed software entity. Its displayed diameter must be tied to the construction definition before it can be interpreted, and it should not be presented as physical bore-size evidence unless the agreed evaluation actually measures and reports that requirement.
What should a buyer ask for when a projected center is used for approval?
Ask for the input feature, target plane, alignment, construction type, reported center property, software version where relevant, and the drawing criterion the result supports. Also state whether the result is acceptance evidence or supplemental information.
Can one report evaluate bore size and projected location?
Potentially, but they should be reported as distinct characteristics with distinct methods and criteria. The actual-size result needs an agreed physical-feature evaluation; the projected-location result needs traceable construction and reference conditions.
Is a projected circle the same as an oblique section of a hole?
No. An actual oblique section concerns the physical intersection of a plane and a surface. A mathematical projected circle is software-constructed. Their geometry, purpose, and reporting meaning can differ.
What if the drawing does not say whether the requirement is projected or actual?
Do not let the report format make that decision. Request clarification from the responsible engineering authority, document the agreed interpretation, and then define the inspection evidence that answers it.