A squaring-line RFQ that lists machine features before it describes the tile going into the machine puts the supplier in the position of guessing what the equipment actually has to handle. The more useful starting question is not which squaring and chamfering configuration to request, but which incoming-tile conditions the factory can document well enough for a supplier to configure against. That sequencing decision shapes everything that follows in the requirement.
Define the Incoming-Tile Scope Before Machine Features
A squaring-line requirement becomes usable when it states what the machine will actually receive before it states what the machine should do. HSE’s guidance on buying machinery frames this as considering where and how equipment will be used and what tasks it must perform, and raising complex or custom-built needs directly with suppliers rather than assuming a standard configuration will fit. GOV.UK’s technical-specifications guidance makes the same point from the buyer side: a specification exists to give suppliers a full, shared description of the requirement, not a partial one built around a preferred design.
For a squaring line, that means the opening scope section should name the tile families the line will process, not the wheel types or machine stations the buyer expects to see. If the factory runs more than one body type, surface finish, or format family, each one that will pass through the line needs to be named as in-scope, and any family that is only a future possibility should be marked as such rather than left ambiguous. A supplier configuring around an unstated assumption may exclude a product line the factory intended to run, or oversize a feature for a product line that will never appear.
This is also where the production context belongs: which process stage the tiles arrive from, whether the intended route is wet or dry, and what output the line needs to support. These are inputs the buyer states as requirements, not results the buyer can claim in advance. A catalog description of a machine’s rated capability does not substitute for the factory’s own record of what its tiles look like coming off the prior process step — surface condition, edge state, and dimensional spread at that point are specific to the factory’s own upstream equipment and material, and no supplier’s published material can stand in for that record.
Where the scope statement mixes future possibilities into the current requirement without labeling them, the supplier proposal risks being configured for a wider or narrower range than the factory actually needs now. Separating “in scope now” from “optional or future” lets the supplier price and configure the present requirement cleanly while flagging where the design would need to change if scope expands later.
| Requirement element | Buyer-supplied content | Boundary |
|---|---|---|
| Tile families in scope | Material or product family and whether it is current, future, or optional scope | Do not assume an unlisted family is covered |
| Intended production context | Production stage, process route, wet/dry context, intended speed context, and required output | These are project inputs, not proof of achievable performance |
| Incoming variation | Observed dimensional and surface-condition range with its record source | Do not substitute nominal catalog values for factory data |
| Finished requirement | Required dimensional and edge outcome plus how it will be assessed | Leave machine architecture and achievable values for proposal and agreement |
Record Dimensional and Surface Condition Categories
Once the tile families and process context are named, the requirement needs the actual condition data behind them. ISO 10545-2 defines length, width, thickness, side straightness, rectangularity, surface flatness, and surface quality as distinct, separately measurable characteristics of a ceramic tile. That separation matters for a squaring-line requirement because a tile can be within an acceptable range on one of these characteristics while varying widely on another — a batch with consistent thickness can still show inconsistent rectangularity, and flat tiles can still carry surface-quality variation that a downstream process needs to account for. Treating these as one undifferentiated “tile condition” in the RFQ obscures which specific variation the line will need to manage.
The standard defines what is measured and how; it does not set what value is acceptable for any given production line, and a factory should not read a tolerance or acceptance threshold into a document that only defines a measurement method. What belongs in the requirement is the factory’s own observed range for each applicable category, the method used to observe it, and the sample basis behind that observation — for example, whether the recorded variation reflects a single run or a wider production history. A supplier evaluating a squaring-line configuration needs to know whether the stated numbers represent a typical condition or a boundary condition, because a configuration built around a boundary case behaves differently from one built around a typical case.
Material type, surface geometry, and visible surface condition belong in this record only to the extent they affect the squaring-line brief specifically — a factory does not need to reproduce a full quality-control profile, but it does need to flag where a surface geometry or finish interacts with how the tile will be handled, centered, or processed at the squaring stage. Where two tile families share a nominal format but differ in surface geometry, that difference can change how the incoming condition should be described, even though the dimensional category names stay the same.
Limits, inspection frequency, condition classes, and any acceptance threshold remain decisions the buyer and supplier work out together; recording an observed range is not the same as setting a project tolerance, and the requirement document should keep that distinction visible rather than letting an observed number read as an agreed limit.
| Condition category | What to provide | What not to infer |
|---|---|---|
| Length and width | Nominal formats and observed incoming variation | No universal line size range or finished tolerance |
| Thickness | Observed range by tile family | No automatic machine or wheel setting |
| Side straightness and rectangularity | Current condition data and agreed measurement method | No BASAIR correction capability or acceptance value |
| Surface flatness and surface quality | Relevant incoming observations and sample basis | No guaranteed handling or finish result |
| Material and surface geometry | Tile type, surface form, and finish context relevant to the project | No equivalence between different materials or surfaces |
Connect Incoming Conditions to the Squaring Project Interface
Naming a condition only becomes useful once the buyer can say which supplier decision it is meant to inform. A dimensional range affects handling and centering differently than it affects the squaring and chamfering scope itself; a surface-condition observation is relevant to process and wheel-matching evaluation but not to utility planning; a wet or dry route decision changes what utility interface needs to be discussed but says nothing on its own about handling. Where the requirement states a condition without tying it to the interface it affects, the supplier is left to guess which part of the configuration the buyer intended it to constrain.
This connection also has to account for how conditions combine rather than treating each one as independent. A tile that represents the largest format the line must handle is not necessarily the same tile that represents the most demanding geometry — the widest size and the most difficult edge condition can occur in different products within the same scope. A requirement that only lists the extreme value for each category separately, without noting which combinations actually occur together in the factory’s production, can lead a supplier to configure for a combined worst case that never happens, or to miss a combination that does. Recording conditions by product family, rather than as a single set of extremes across all families, keeps that combination logic visible.
The intended speed and required output belong in this section as information the supplier needs in order to evaluate what the proposed line can support — not as a specification the buyer can already state in machine terms, since the achievable relationship between input condition and line duty is what the supplier proposal is meant to establish. Where the buyer has an existing upstream or downstream process, the handoff state at each end of the squaring stage needs to be described in terms of what is currently produced and what the next stage expects to receive, so the supplier’s proposal can address the interface rather than assuming a generic connection.
For each of these points, the useful RFQ language ties the condition to a decision — handling and centering, squaring and chamfering scope, process and wheel-matching context via the diamond squaring wheels discussion, utility interface, or downstream handoff — without prescribing how the supplier should resolve that decision. This is also the stage at which the factory’s project data enters BASAIR’s configuration and quotation review: the incoming-condition records and the family-by-family combinations are what a supplier needs on hand before proposing a squaring and chamfering machine line configuration, rather than a starting assumption about which equipment family fits.
| Incoming information | Supplier decision it should inform | Confirmation needed |
|---|---|---|
| Size, thickness, and incoming geometry | Handling, centering, and squaring/chamfering scope | Proposed configuration and supported envelope |
| Material and surface condition | Process and matching-wheel evaluation | Trial or engineering basis for the proposed match |
| Wet/dry route and utilities context | Process-interface and utility discussion | Project-specific interface data |
| Intended speed and required output | Evaluation of the proposed line duty | Evidence and conditions attached to any supplier commitment |
| Upstream and downstream state | Handoff definition | Agreed inputs, outputs, and responsibility boundaries |
Separate Buyer Requirements, Supplier Proposals, and Verification Evidence
The clearest way a squaring-line requirement fails is by letting three different kinds of statement collapse into one. GOV.UK’s specification guidance distinguishes a functional or performance requirement — what the outcome needs to be — from a design description of how that outcome is achieved, and supports attaching proportionate evidence to whichever claim is being made. Applied to a squaring-line RFQ, this means the buyer’s role is to state the incoming condition and the required finished result; the supplier’s role is to propose a configuration that connects the two; and a separate, agreed layer of evidence — drawings, sample trials, measurements, records — is what will show whether the proposed configuration actually meets the stated requirement.
Where these three layers are written into the same sentence, the requirement becomes difficult to evaluate later. A desired dimensional or edge outcome is not the same as an observed incoming value, and neither is the same as a value a supplier commits to achieving — each has a different owner and a different basis. If a factory states its desired finished tolerance and its observed incoming variation in the same figure, a supplier cannot tell whether the number describes the problem or the target, and any proposal built on that ambiguity risks being evaluated against the wrong reference later in the project.
HSE’s guidance on discussing complex or custom-built machinery requirements directly with suppliers supports keeping this conversation open rather than trying to resolve it entirely inside a written document. Where a requirement includes conditions that do not map cleanly onto a standard configuration, a direct discussion about what evidence would demonstrate suitability — sample trials on the factory’s own material, measurement against the observed incoming range, or a proposed drawing showing how the interface will be handled — lets both sides agree on what “meeting the requirement” will actually mean before configuration begins.
This separation also clarifies where BASAIR’s role sits in the process: the incoming-condition data and required outcome belong to the factory, the proposed equipment and abrasive matching — including any diamond squaring wheel selection tied to the stated material and process route — belong to the supplier’s proposal, and the verification step is where both sides confirm, through trial or measurement tied to the actual material and settings, that the proposed configuration performs against the stated requirement rather than against a general or catalog description. Compliance values, safety limits, tolerances, capacity figures, and acceptance criteria are not available from general guidance or public equipment listings; they are established only through this project-specific proposal and verification stage, and a requirement document that tries to state them in advance is stating an assumption rather than a confirmed value.
Frequently Asked Questions
Q: Can we describe our incoming tiles using nominal size and thickness alone?
A: Nominal values do not describe the full incoming condition. Add the observed variation and relevant straightness, rectangularity, flatness, surface, and material information, with the measurement approach and sample basis. Those records help the supplier evaluate the actual input envelope.
Q: Should future tile families be included in the same requirement as current production?
A: Include them with a clear status: current scope, future scope, or optional scope. This makes the proposed coverage visible without implying that an untested or unlisted family is already supported by the configuration.
Q: Why record combinations of incoming conditions instead of only the largest and smallest values?
A: Separate extremes may occur on different tiles and therefore describe a combination you do not actually produce. Record relevant combinations by tile family so the supplier can assess handling, squaring and chamfering scope, wheel context, and interfaces against real production conditions.
Q: How do we avoid confusing incoming data with promised finished-tile results?
A: Keep observed factory inputs, desired finished outcomes, and supplier commitments in separate parts of the brief. Ask the supplier to propose the configuration and agree which drawings, sample trials, measurements, and records will demonstrate suitability for that input envelope and required result.
