Prospect research for pump and flow-control suppliers

A useful brief connects an application to a business activity and a possible route to market. State what you supply, which duties you want to investigate, your territory and exclusions. Decide whether the research unit is a company or a specific facility.

Published context: the European Commission’s 2019 food, drink and milk reference document describes cleaning-in-place using pumped cleaning solution, chemical dosing within cleaning-in-place, packaging/filling and process-site wastewater treatment.^[6] These are examples of industrial activities—not evidence that a particular company needs your equipment.

Our research approach: record why an account merits investigation while keeping technical fit unresolved. Do not replace missing duty information with a “suitable” label. A company’s sector can justify further research without answering which components it uses or who purchases them.

We use the following working distinctions when agreeing a targeting brief:

• Operator: the business operating the facility. Investigate the relevant site and activity; do not assume it buys components directly.
• OEM: an original equipment manufacturer building a machine or packaged system. Investigate whether relevant components form part of its offering; establish who specifies and purchases them.
• Integrator: a business combining equipment, controls or process systems. Investigate the relevant application and its role in specification, supply or commissioning.
• Contractor: a business delivering installation or works. Investigate the actual package and scope; project association alone does not establish component purchasing responsibility.

These are research labels, not exclusive company categories. One business may perform several roles. Record evidence for each relevant role rather than assigning purchasing authority from its name.

The first column identifies activities described in the reference document.^[6] The route suggestions and questions are our original research hypotheses, not source-confirmed buying routes or equipment recommendations. These food-and-drink examples illustrate the method, not our entire potential research scope.

In narrow layouts, scroll horizontally or focus the table region and use the arrow keys to read every column.

Use the matrix to write inclusion questions, not to tick off technical suitability. The cited document is a 2019 reference used for historical process context, not a current equipment-selection guide, legal instruction or proof of investment. No institution endorses DemandRange or these route hypotheses.

An industry-matched account, also called Look Alike, can meet the agreed profile without an active or upcoming project. Research that was not required is different from a bounded search that found no qualifying signal; neither proves that no project exists.

Where an evidenced development is relevant, an opportunity-signal record adds its source, date, stage and unknowns. An announcement is not an open equipment order. Our target is 90% industry-matched and 10% opportunity-signal leads, not a guaranteed mix. Exact deliverables are agreed in writing.

Two briefs, different route decisions

The briefs, businesses and evidence below are wholly fictional teaching cases, not anonymised clients or researched prospects. Evidence descriptions are stipulated for the exercise, not quotations from real sources.

Brief A — OEM component supply. Research companies building filling or cleaning-in-place systems for other businesses, including integrators assembling those systems. The supplier offers pumps and valves for investigation as components, not complete production lines. The research territory is Ireland; retain relevant Irish operations. Exclude resale-only businesses and operator-only accounts from this route. A new project is not required.

Brief B — operator maintenance. Research businesses operating food-and-drink production facilities in Ireland, recording the relevant facility within the company account. Investigate maintenance and component-renewal applications for pumps and valves, not machine-building sales. Exclude businesses working only on customers’ equipment without operating a relevant production facility. A breakdown, maintenance deadline or announced project is not required.

Both briefs also require identity, territory, existing-account and channel-conflict checks, and evidence/source-use review before account acceptance. These examples isolate the route screen: include means evidenced role and activity match; hold means a needed fact is unknown or conflicting; exclude means positive evidence contradicts the brief. A route include is not full client-profile acceptance, engineering suitability, purchasing authority or buying intent.

Work the evidence, not the business label

• Case A: Example Assembly. Its invented capability note describes building filling systems with bought-in pumps and valves for customers. Its scope statement explicitly says it does not operate a food-or-drink production facility. A: include; B: exclude. Assembly activity satisfies A; the explicit operating-scope restriction contradicts B. Calling it a “supplier” would not justify excluding it from A. Component specifications, approved suppliers and purchasing responsibility remain unknown.
• Case B: Example Works. An invented site record identifies its Irish beverage-production facility and cleaning-in-place activity. A separate scope note states that it neither builds nor integrates systems for other businesses. A: exclude; B: include. The negative assembly evidence excludes A; operating its own relevant facility satisfies B’s route screen. Maintenance arrangements, installed components and renewal timing remain unknown; operating the plant does not prove direct purchasing.
• Case C: Example Combined. Invented capability and facility notes describe both cleaning-in-place system assembly for customers and operation of its own beverage-production facility. A: include; B: include. Keep both evidenced roles on one company record; attach each activity to the relevant operation rather than counting two companies. Neither role proves the other, and neither establishes who specifies or buys components.
• Case D: Example Unresolved. An invented listing says “pump solutions and plant support”, without identifying assembly work or an operated facility. A: hold; B: hold. Obtain role-specific evidence rather than treating a missing description as a negative. If a later scope note explicitly establishes resale-only activity, with no assembly or relevant facility operation, A: exclude; B: exclude. If it instead establishes filling-system assembly for customers but leaves facility operation unknown, A: include; B: hold. These are alternative evidence updates, not simultaneous facts.

Search and false-positive checklist

1. Write the evidence question first. For A, try Ireland filling system builder or Ireland cleaning system integrator; for B, try Ireland beverage production facility. These are exploratory query prompts, not tested filters, measured demand or promises of search performance.
2. Inspect the result’s purpose. A product catalogue, equipment shop or “request a price” page is not proof of a customer role. Equally, selling equipment does not rule out building systems. Find the activity evidence behind the label.
3. Use negatives cautiously. Terms such as shop, retail or used equipment may help explore noise, but do not blanket-exclude supplier, manufacturer or maker: that can discard the OEMs and integrators sought in A. Compare a filtered search with an unfiltered version; treat exclusions as hypotheses, not record-level evidence.
4. Check the entity and operation. Does the evidence concern this company, a customer, a group affiliate or an old project? Separate supplier delivery from facility operation. Conflicting scope claims stay on hold until resolved; an older role description does not establish the current role.
5. Keep the audit trail and limits. In the existing supplier-fit worksheet, separate source/date, observed activity, route reasoning and next verification. Record a route include in the reasoning; keep the full account decision on hold while required checks remain open. Check applicable source and item-use conditions before reuse; public visibility is not permission. Leave duty conditions, compatibility, procurement responsibility, current demand and package availability unresolved unless specifically evidenced. Do not convert this exercise into technical or legal clearance.

A treatment-site reference is a starting point for a question, not a component customer. For pump and flow-control research, use the map below to separate the organisation that owns an asset from the organisations that operate it, design changes, deliver works, maintain equipment and select suppliers. This is an original decision aid: the labels are working research distinctions, not legal definitions or a description of any real contract.

If the evidence mentions an industrial discharge, use the trade-effluent boundary check and research handover before assigning an equipment opportunity.

Choose one site or system, one defined scope and one phase for each map. A company may hold several responsibilities; a responsibility may be shared. Keep the company account stable while adding separate role records. Do not carry a historical installation role into a present maintenance or purchasing claim.

Download the blank water/wastewater buyer-route worksheet (CSV). Download the four fictional cases (CSV). The cases below are wholly fictional. No current package, accessible buyer, buying intention, technical suitability or permission to contact anyone is established.

For each relationship, keep the source observation, its scope and your interpretation separate. The following evidence suggestions are questions to investigate, not claims that those records exist or can be reused.

1. Facility ownership — who is evidenced as owning the relevant asset?

Identify the asset, attributed organisation and source scope. Ask whether an ownership statement concerns the facility, land, equipment or a group company. A project sponsor, site address or logo is not enough for this research decision. Ownership does not fill the operator or supplier-selection fields.

2. Operation — who performs the day-to-day operating scope?

Look for a site-specific operating responsibility and its period. Separate a facility operator from a service provider visiting the site. A corporate water-sector description leaves the operating relationship unknown. An operator label does not establish that equipment is bought directly.

3. Design — who defines, develops or approves the relevant scope?

Record the actual design task: an overall requirement, detailed design, an interface or an approval. Keep design authorship, technical approval and commercial supplier selection as separate relationships. A design role for the works does not automatically extend to every component.

4. Physical delivery — who supplies, installs, connects or commissions what?

Split these verbs. Evidence of installing a supplied assembly need not identify who bought it; evidence of supplying an assembly need not identify its installer. A contractor’s association with the site leaves the precise delivery boundary unresolved until a scope is evidenced.

5. Maintenance — who services the asset, and who provides spare parts?

Record routine service, fault response and spare-component responsibility separately where the evidence permits. Ask whether a maintenance description includes parts, labour only, or neither explicitly. Do not invent a renewal date, failure or spare-parts requirement.

6. Supplier selection — who can nominate, approve and place the order?

Use separate fields for commercial supplier selection, approval restrictions and order placement. Record who can choose the supplier for this scope, not merely who appears on a project page. If an approval list or purchasing relationship is not evidenced, leave it unknown. Selection evidence for an old package does not establish access to a new one.

Keep facility ownership and operation as separate fields even when the same organisation is evidenced for both. Never infer either from physical presence at a site. Keep component supply distinct from buying components into a larger system.

• Operator: use this label only for the evidenced operating relationship. A maintenance-research brief may make this role relevant, but direct purchasing remains a separate question.
• Contractor: name the delivery scope and phase. A civil-works-only description is different from an expressly evidenced equipment-procurement responsibility. Do not invent a subcontract route around an excluded direct package.
• Integrator: record what is combined and which interfaces or assembly tasks belong to the business. Distinguish assembling a system from choosing its component suppliers. Integration work with customer-supplied equipment leaves component purchasing elsewhere or unresolved.
• Equipment supplier: distinguish manufacture, distribution and resale where evidenced. A catalogue establishes an offering only within its actual scope; it does not by itself establish operation, integration or installation. A supplier may also assemble systems, but record that second role separately rather than assuming or excluding it.

These labels are not mutually exclusive. For this method, the basic record is organisation → responsibility → asset/scope → phase → evidence. A company-wide capability can support a capability question; it cannot, by itself, assign that responsibility on a particular site or package.

Keep the route decision narrower than the buyer claim

Investigate means a supported relationship fits the stated research question and there is a named next check. Hold means a required relationship is missing, conflicting or unusable. Out of scope requires positive evidence against the selected brief. These are our research decisions, not procurement statuses, a qualification score or approval to pursue work.

Apply two gates independently: does the role fit the research brief, and is supplier-selection authority evidenced for the exact scope? A role can pass the first while the second remains unknown. Package availability and buyer accessibility are additional unknowns, not automatic consequences of either gate. Keep full-account acceptance held while required identity, territory, exclusion or source-use checks remain open.

All organisations, sites, records and evidence descriptions in these cases are invented teaching material. They are not real prospects, anonymised clients, actual notices or source quotations. All sites are stipulated as fictional Republic of Ireland sites; no actual dates or URLs exist. In every case, current package availability and buyer accessibility are unknown.

Case W-A — operation without ownership or parts purchasing

An invented scope card says Fictional Water Operator A operates Site A but does not own it. Its separate maintenance card assigns routine servicing to A and states that spare components are supplied by the owner and that A does not place those orders. The owner’s identity and supplier-selection process are not given.

Decision: investigate A for an operator-and-maintenance research brief. It is out of scope for a brief requiring A itself to place spare-component orders under the described arrangement. The owner’s identity, equipment compatibility, spare timing and the owner-side buyer route remain unresolved. Ask for the responsibility boundary, not a presumed purchasing contact.

Case W-B — physical delivery with explicitly excluded equipment choice

An invented works record says Fictional Delivery Contractor B installs a customer-supplied pump assembly at Site B. Its stipulated scope excludes design, equipment procurement and ongoing maintenance. The client’s identity is not supplied.

Decision: investigate B if the brief seeks installation contractors; out of scope for a brief seeking component purchasers for this exact works scope. The installation record does not identify the owner, operator, designer or selector. Do not convert the customer-supplied assembly into a live purchasing requirement or a new subcontract package.

Case W-C — integration and component ordering, but constrained selection

An invented responsibility schedule says Fictional Systems Integrator C assembles a treatment-control package at Site C, designs its interfaces and orders incorporated components. A separate stipulated restriction says the equipment supplier must be nominated by the customer; C may not substitute one. Neither facility operation nor ongoing maintenance is described.

Decision: investigate C for a system-integration research brief. It is out of scope for a route requiring C to choose a new component supplier independently: placing the order does not satisfy the selection condition. Hold any alternative route through customer nomination until that relationship is established. The nominating customer’s identity, nominated supplier, detailed approval scope, current arrangements and accessible buying route remain unknown. This exercise does not make any component suitable for the package.

Case W-D — equipment sales are not an operating role

An invented business-scope note says Fictional Equipment Supplier D resells complete spare assemblies, explicitly performs no site operation or installation, and does not integrate customer systems. Its catalogue refers to water and wastewater applications, but identifies no installed asset, client or package.

Decision: out of scope for an operator or integrator brief; investigate only for a separately agreed equipment-supplier or channel question. The catalogue provides no candidate operating site and no component-buyer relationship. Do not add a fictitious end user to complete the map. Whether D purchases components rather than complete assemblies remains unknown.

Contrast: A separates operation from ownership and ordering; B separates installation from equipment procurement; C separates ordering from supplier choice; D separates an equipment offering from the customer’s operating activity. Changing the brief changes the route decision—not the stipulated evidence.

1. Set the brief. Record the supply role, territory, inclusion condition and exclusions. State whether you are mapping an enduring capability or a particular site/package responsibility.
2. Set the unit. Use a map ID for one site/scope/phase and a responsibility-record ID for one organisation-to-role relationship. Reuse the company ID across roles; do not count a contractor-integrator twice.
3. Record only supported links. In each relationship field, distinguish evidenced, explicit negative, unknown, conflicting and not assessed. Attach an evidence ID to every positive or negative finding. An unknown is not a negative.
4. Keep evidence chains separate. For another source, copy the record with the same map and company IDs but a different evidence ID. Do not compress conflicting descriptions into a confident composite.
5. Apply source-use and decision gates. A visible page is not a reuse licence. Keep restricted or unresolved source-derived assertions out of reusable delivery. A role match is still not a purchasing mandate or full-account acceptance.
6. Write the unresolved question. Name the relationship needed to change the decision. Leave technical suitability, package availability, buyer accessibility and buying intention unknown unless separately assessed with appropriate evidence and authority.

The CSV is a blank section,field,value,guidance template, not an automated score. All value cells start empty. Import and paste as text; do not enable formula interpretation for source content. No names of people, contact details, confidential customer lists or non-public tender documents belong in this educational worksheet.

Use the existing tender-triage guide for a notice/lot question and the food activity-and-place guide for a manufacturing segmentation question. This map adds the responsibility boundary between an account role and supplier selection; it does not replace those guides. Nothing here grants outreach permission, source rights, GDPR clearance or technical approval.

Trade-effluent worksheet: turn a discharge reference into the next research action

If an account note mentions trade effluent, use the existing blank buyer-route worksheet (CSV) before adding an equipment claim. The output is a short research handover: what is supported, what stays unknown and which check comes next. This is our original account-research method, not a discharge classification, permit assessment or technical specification.

Use the existing fields: put the facility in site_or_asset_reference; identify the stream and route question in scope_and_phase; record only the supported discharge or treatment observation in permitted_observation. Name its supported fields in supported_field_names and retain unresolved boundaries in limitations_and_conflicts. Use a separate record for a different evidence chain. Put the next check and its stopping rule in next_relationship_question. Leave unrelated responsibility fields unknown or not assessed rather than completing them from a discharge reference.

1. Anchor the observation. Reuse the company and map IDs above. Identify the operating facility, the described stream and its stated destination separately. An unspecified sewer connection leaves the stream unresolved; a group address leaves the facility relationship unresolved. Do not fill either gap from the industry label.
2. Keep the boundary observations independent. Label the discharge route, physical interface and any on-site treatment separately in your observation; use another record where the evidence chain changes. Keep ownership, operation, maintenance and supplier selection in the existing responsibility fields. A supported destination does not complete those fields.
3. Attach the evidence to the exact field. Use the existing evidence ID, URL, publication date, retrieval time and source-use checks. If another source supports treatment rather than the route, make a separate evidence record with the same map ID. Preserve conflicting records; do not turn a permitted discharge description into a statement about installed equipment or present activity.
4. Choose the next check, not a readiness score. Write one unresolved question and the kind of site-specific evidence that could answer it. Set a review boundary: what will be checked and what result will leave the claim on hold. Missing evidence is an unknown, not proof of absence.

Two fictional practice decisions. All facilities and observations here are invented. For a food-production research brief, Fictional Facility A has a stipulated operating-site match and a note explicitly linking its process stream to a public sewer. Retain it for account-fit review; record the route only. Treatment, maintenance responsibility and equipment demand remain unknown. Fictional Facility B has only a group-level address and an unspecified sewer connection. Hold the site and stream attribution. Reject either account only for an evidenced mismatch with the brief, not simply because its treatment arrangements are unknown.

Keep three decisions separate: account fit against the written brief; support for the discharge observation; and any separately researched project signal. Use not assessed—not required when project research was outside scope. Use no qualifying signal found in the recorded search only after that bounded search was actually completed. Neither means that no project exists.

Copy this handover into your research brief

“We supply [range] for [applications] and want company-level research in [territory], excluding [criteria]. For [company/map ID], the evidence supports [field and observation]. It does not establish [unknowns]. Keep account fit [decision and reason]; keep project evidence [status]. Next, check [question] using [source category], within [review boundary]. If unresolved, hold [specific claim], without silently excluding a matching company.”

A handover is ready for a scoped research enquiry when another reviewer can identify the supported field, the unknown and the next check. It is not buyer readiness. Share the range, territory, exclusions and unresolved research questions—not confidential customer lists or personal contacts. Use the water-investment guide for programme-to-project interpretation and the PRTR guide for dataset boundaries. This worksheet provides no permitting, procurement, engineering or legal advice and no authority to contact an organisation.

The EPA's openly licensed Remedial Action List catalogue describes public water supplies for which corrective action is required.[15] That gives a starting supply-level evidence frame. It does not identify the company from which a pump supplier could win work. We have not extracted or verified a current list of individual supplies.

A second real source illustrates a different unit. The EPA's River Abstraction Pressures metadata says an abstraction-point pressure may relate to drinking-water supply or to agricultural or industrial facility abstraction.[14] A point in that dataset is therefore not, by itself, an accepted company account. This article uses only the published catalogue description, not underlying map features, operator records or site findings.

Keep the relationships explicit: natural water resource → abstraction point → receiving facility or supply → evidenced organisation → role for the defined scope. The arrows represent questions requiring evidence, not an assumed chain. A map location does not fill the organisation field; a named organisation does not establish component selection.

Everything in this relationship exercise is invented. All organisations are fictional company entities, with no personal contacts.

ID-01

Stipulated observation: Resource RES-A feeds point ABS-A, which serves SITE-A and SITE-B.

Research treatment: Keep one resource, one point and two site identifiers. None is an account identifier.

ID-02

Stipulated observation: Point ABS-B also serves SITE-B, from distinct resource RES-B.

Research treatment: Add the second resource/point relationship; do not create another company because the site has another source.

ID-03

Stipulated observation: Separate identity evidence attributes operation of both sites to ORG-A for the review period.

Research treatment: Keep one organisation linked to both sites and all relevant observations. Do not infer procurement authority.

ID-04

Stipulated observation: A further document names ORG-B as designer for SITE-A only; operation is not stated.

Research treatment: Retain the narrow design relationship. Do not overwrite ORG-A's operating role or call ORG-B the buyer.

ID-05

Stipulated observation: A nearby point ABS-C has no evidenced receiving site or operator.

Research treatment: Hold the links. Do not fill them from proximity or a similar company name.

Within the fiction, the identified operator is one organisation, despite multiple sites and abstraction points. ORG-B remains a separately evidenced design participant, not an automatically accepted account. Neither the operator count nor the participant count is a count of accepted prospects: acceptance still depends on the agreed role, territory, exclusions and evidence-use rules.

Use stable identifiers for each unit and one row for each relationship. Record its source, period, role wording and verification outcome. A source can support a point-to-site connection while leaving the site-to-organisation connection unknown. Do not discard the first relationship merely because the second is held.

For a company-based brief, deduplicate accepted records by verified company identity only after the required links and account checks close. For a facility-based brief, retain separate facility rows but do not describe their total as companies. No assumption about licensing aggregation rules, pump duty, installed equipment or engineering suitability is made here.

Use this completed structure when commissioning research that begins with a corrective-action observation. It is deliberately narrower than a general account-acceptance checklist.

Source frame

What the buyer should specify: Issuer, exact item reference, version, capture date, date labels and intended reuse. A source family's reputation is not item-level permission.

Supply/project unit

What the buyer should specify: The precise supply, asset or works reference. State whether the source actually identifies works or only a regulatory concern.

Account route

What the buyer should specify: Operator, designer, delivery organisation or maintenance provider to investigate; leave unevidenced roles blank.

Allowed interpretation

What the buyer should specify: An attributed corrective-action observation within its stated period; not an equipment requirement or buying signal by default.

Missing stage

What the buyer should specify: Which project decision, scope definition or procurement fact would change the research decision.

Exclusion rule

What the buyer should specify: Existing accounts, channel conflicts, wrong territory and out-of-scope delivery roles; name the review status rather than assuming clearance.

Rights hold

What the buyer should specify: Which source items cannot enter customer-facing copy until their exact rights are resolved.

Return format

What the buyer should specify: Separate the observed fact, relationship evidence, commercial hypothesis, unresolved field and next check.

Fictional dual-source handoff: card REG-A records a corrective-action requirement for supply SUP-A. Card TXN-A describes a supplier portal that displays invoices and purchase orders. Neither card names a current component procurement or proves a route by which a new supplier can access it. The source types answer different questions; placing them side by side does not create a missing project link.

A usable return is: “Retain the regulatory observation at supply level. Treat the transaction-system card as administrative context only. Hold the commercial route pending a source connecting the specified works, responsible organisation and relevant procurement scope. No present package availability, registration eligibility or permission to contact anyone is established.” All details in that return are hypothetical, not a description of a real portal.

The smallest next validation is a dated, supply-specific works or procurement reference that can actually be linked to the observation. If no such connection is found within the agreed review, return the missing link—not a guessed buyer. Once a notice exists, move to the eTenders relevance guide; do not repeat notice triage here.

Bring the completed attachment and supplier application brief to a scoped research enquiry. Use the account-research sample for the separate inclusion decision. A resolved relationship makes evidence more usable; it does not establish demand.

Use this original exercise alongside the existing review workflow. Keep one evidence thread for one facility and one issue, preserving source references, stated dates, access times and coverage limits. Record the signal decision separately from account fit. This exercise describes no regulator’s rules or real project.

Two fictional observations—and a missing-evidence test

All facilities, issues and evidence here are invented. Fictional Facility A, issue FIC-01 and references FIC-A, FIC-B and FIC-CLOSE represent no real business or public record.

• First observation: FIC-A describes an unresolved issue at this facility. Keep that dated observation; hold any pump-demand or open-package claim. Without an earlier comparable record, say “first observed in our research”, not “newly added”.
• Later observation: a complete, comparable FIC-B omits the issue. A separate stipulated FIC-CLOSE explicitly confirms the same facility, the same issue and its resolution. Retire this issue-derived signal, preserving the old record and closure reference. Future works and procurement remain unknown.
• Remove FIC-CLOSE: the signal decision changes to hold, not “resolved”. If FIC-B is only a partial extract, even apparent absence is unestablished. A failed retrieval also leaves current status unknown.

The account test is independent. If the company still satisfies the agreed industry-matched profile, retiring this signal is not a reason to discard it. Equally, retaining the company does not restore an unsupported project claim.

Handover: “For [facility/issue], [dated reference] supports [observation]. Keep account fit [decision/reason]; keep the signal [keep/hold/retire/reason]. Check [identity, coverage or closure question] next; if unresolved, hold [specific claim].” Check source-use conditions before reusing real evidence. The exercise grants no engineering suitability, buyer access or contact permission.

A useful water-account brief starts with where the relevant water enters the system. That is a different question from what the business manufactures, what pumps it owns or whether it is planning an upgrade. A food processor using purchased water and an organisation drawing from a natural source can belong in different research routes even if both describe water-intensive activities.

Eurostat's water-abstraction glossary covers the collection of groundwater and surface water for household and enterprise use in EU statistics.[7] That is a useful starting distinction for research, not an Irish licensing test or a description of an installed pumping arrangement. Use it to ask a narrower question: does the evidence connect this operation to a natural-water source, a supplied-water connection, or neither?

Choose the intake branch

An attributable source explicitly describes collection from a natural source

Research branch: Natural-source abstraction context

What to record: The stated source category and the operation it serves; do not fill in a more precise category than the source gives

Smallest useful next check: Establish which organisation carries out the described abstraction, and whether the description concerns current operation or a proposal

An attributable source explicitly describes water delivered through another supply system

Research branch: Supplied-water context

What to record: The supplied connection and the supported boundary only

Smallest useful next check: Establish the receiving site's role and the relevant internal application; do not assign upstream abstraction to it

The source says only “water use”, “water services” or a general industry description

Research branch: Origin unknown

What to record: The observation and the missing origin question

Smallest useful next check: Seek one site-specific source description within the agreed review boundary; if unresolved, keep origin unknown

These are our intake labels. They are not mutually exclusive classifications of an entire company. If evidence supports a supplied connection and a separate natural source, create separate scope records under the same company ID. Likewise, a proposed borehole and an operating supplied connection are different phases, not necessarily conflicting accounts.

Keep the engineering fields empty at this step: pump presence, pumping duty, materials, capacity and technical suitability. Mark them not assessed in the accompanying status note. Even a clear water-source description does not provide the operating conditions needed to complete them. A supplier can request research into the abstraction-side operator without asking the researcher to select a pump.

Worked intake — wholly fictional

An invented site statement for Fictional Food Plant A says its production water arrives through a supplied connection. An older invented proposal mentions investigating a borehole but does not state that it was constructed or used. Both statements are invented; there is no real site, source URL or publication date.

For a brief seeking operating natural-source abstraction accounts, put the borehole claim on hold. Record the supplied connection as the supported operating observation, with the proposal in a separate evidence thread. Do not promote the proposal to an abstraction installation and do not infer that the plant has no pumps. All five engineering fields remain blank.

The next validation is a current, attributable statement resolving whether that particular proposed source entered operation. If the bounded check cannot resolve it, retain the hold. Exclude the site from an abstraction-only shortlist only if positive evidence establishes a mismatch with that brief; unresolved origin is not that evidence. It may still qualify for a separately agreed production-operator brief.

Record and hand over: company/map ID; site; water-origin branch; exact supported observation; source URL; source publication/update date or not stated; access date; operating/proposed phase; source-use status; decision; next check and stopping rule. An enquiry can say: “Research [range/application] accounts in [territory], distinguishing natural-source operations from supplied-water users. Exclude [criteria]. Establish origin and operating responsibility; leave equipment duty and suitability unassessed.” Compare the fictional account sample before requesting a company list.

For group-scheme research, a name on the distribution side need not answer the upstream-source question. Geological Survey Ireland's openly licensed group-scheme metadata describes community-run schemes and distinguishes privately sourced supplies from schemes supplied through an Irish Water connection; the record attributes that background distinction to departmental information from 2017.[9] Use that historical distinction to formulate an intake question, not as a current ownership or purchasing record for any scheme.

The same metadata records an update date of 22 October 2021 and describes preliminary source-protection work, warning against relying on the maps alone for site-specific decisions.[9] A recent retrieval does not turn that material into a current supplier-selection map. No map polygons, scheme list or source-protection findings are reproduced here.

The commercial research task is to locate the handover boundary: which part of the system is actually described by the evidence you have? Reuse the existing responsibility map, but split the water system into upstream source/treatment and downstream distribution scopes before completing any role fields.

The split-scope evidence card

System and boundary

Upstream source/treatment record: Describe the evidenced source/treatment scope; identify the handover point only if stated

Downstream distribution record: Describe the evidenced receiving/distribution scope; do not assume the boundary location

Attributed organisation

Upstream source/treatment record: Enter only the organisation linked to this scope

Downstream distribution record: Enter only the organisation linked to this scope

Supported responsibility

Upstream source/treatment record: State the actual verb: for example, operate treatment, rather than “water provider”

Downstream distribution record: State the actual verb: for example, distribute water, rather than “owns the water system”

Ownership and procurement

Upstream source/treatment record: Separate questions; blank until evidenced

Downstream distribution record: Separate questions; blank until evidenced

Evidence and dates

Upstream source/treatment record: Own source URL, stated date, access date and phase

Downstream distribution record: Own source URL, stated date, access date and phase

Next validation

Upstream source/treatment record: What source would establish the missing responsibility?

Downstream distribution record: What source would establish the component-selection boundary?

A shared system name can connect the research questions without proving that one organisation performs every task. Do not copy an organisation across the card simply to finish it. Keep abstraction, treatment, distribution, asset ownership, maintenance and supplier selection as separately supported relationships within the existing worksheet.

A treatment/distribution boundary — wholly fictional

An invented scope note says Fictional Scheme B distributes water received at a specified handover point. A separate invented note assigns treatment upstream of that point to Fictional Treatment Organisation C. Neither note addresses asset ownership, valve choice, order placement or the arrangements of other schemes. No real group scheme or contract is represented.

For a valve supplier researching distribution-system responsibilities, investigate B at the distribution scope. For a treatment-system account question, investigate C only at the treatment scope. Keep each organisation's full account acceptance subject to the agreed identity, territory and exclusions checks. Neither observation supports “B buys the treatment valves” or “C chooses the distribution valves”. Reject those inferences; hold the purchasing fields.

The minimal next check is an attributable responsibility or scope statement addressing selection and ordering for the specific valve application. If the only additional evidence repeats the distribution role, the buyer-route question remains open. A later express exclusion of equipment selection would justify rejecting that route for this scope, not rejecting the organisation for all possible research briefs.

Enquiry brief: “We supply [range] for [application]. Map [system/territory] across source/treatment and distribution, recording the evidence for each organisation separately. Resolve [specific selection/ordering question] if possible within [review boundary]. Do not infer ownership or generalise a single scheme's arrangement to private or public schemes as a class.”

Water resilience is a reason to investigate a defined issue, not a diagnosis of a failed pump. The European Commission's water-policy page presents the 2025 Water Resilience Strategy around protecting the water cycle, improving water efficiency and sustainable management, and securing clean, affordable water and sanitation.[12] These are EU policy objectives. They are not findings about a particular Irish treatment plant.

That breadth helps a supplier ask a better first question. Instead of “Which pumps need replacing?”, ask “What change, if any, is actually described at this site, and which part falls within our research brief?” An efficiency study, a water-source question and a treatment-scope proposal should not be compressed into the same equipment-renewal claim.

Use an evidence-to-claim ladder

Official system-level context

Statement the research note can make: “The cited policy identifies water efficiency and resilience objectives.”

Evidence needed before advancing: An attributable site-specific observation relevant to the supplier's application

Research hypothesis

Statement the research note can make: “Investigate whether this site's published plans include a relevant water-management change.” Label this as our question, not an official finding

Evidence needed before advancing: A source identifying the site, actual issue or proposed change, date and stage

Site-specific observation

Statement the research note can make: Describe only the evidenced issue or proposal, without choosing its technical remedy

Evidence needed before advancing: A separate asset/scope description and, for a renewal claim, explicit evidence that renewal is part of the described scope

Equipment and commercial claim

Statement the research note can make: Keep renewal need, specification, budget, procurement stage and purchasing route as separate claims

Evidence needed before advancing: Evidence for each claim; engineering assessment for suitability and separate current evidence for any procurement status

Do not skip the site layer because a policy mentions investment or resilience. Conversely, do not suppress a useful site proposal just because detailed pump information is absent: it may be a valid development signal under the written brief while the equipment fields remain unknown. The existing water-investment guide handles programme funding; this ladder handles the separate jump from an objective or issue to a proposed technical remedy.

Reject the renewal inference — wholly fictional

Fictional Treatment Plant D appears in an invented proposal to review continuity of water service. The proposal does not identify installed pumps, malfunctions, maintenance intervals, renewal works or an approved capital budget. The plant and proposal are invented; no real resilience finding is attributed to them.

Retain the observed stage as proposed review, if that is a qualifying signal in the agreed brief. Reject the draft sales sentence “D needs renewal pumps this year”: neither the equipment, remedy nor timing is evidenced. Write instead: “Investigate the published review's defined scope and whether it identifies an application relevant to our range.”

The smallest next validation is a site-specific scope or findings document that answers what the review concerns. A document that merely repeats “resilience” does not release the renewal claim. If it identifies a different application outside the brief, exclude that application with a stated reason. If no further scope can be established within the review boundary, hold the equipment inference while preserving any separately supported company fit.

Handover fields: official context URL and stated date; access date; separate site-evidence URL/date or blank; observed stage; hypothesis; unsupported claim rejected; next evidence question; stopping rule. Keep installed assets, failure history, maintenance schedule, budget and renewal timing unknown unless independently established. An enquiry can ask for “Irish [operator/contractor/OEM] accounts matching [application], with separately evidenced water-management developments; no inferred renewal need.” Use the industrial account-research service and scoped enquiry to define the range, territory and exclusions.

Bring your product range, preferred applications, routes, territory and exclusions, including existing accounts and channel conflicts. Use the blank supplier-fit worksheet to separate observed evidence, your interpretation and unanswered questions. It is a single-record worksheet: complete the blank value column and keep separate evidence chains distinguishable.

Our industrial account-research service explains the record fields and boundaries. The research method explains the checks. Company-level research is the default; personal contacts and outreach are not included by default. A quote request does not book coverage, meetings or sales.

Request a quote to discuss a research scope.

Selected process descriptions are summarised for context. The matrix and route hypotheses are DemandRange’s own analysis; no endorsement is implied. This 2019 reference is not current equipment-selection, regulatory or legal guidance.

Sources accessed 9 October 2026. Eurostat's glossary displays no publication date in the retrieved body; GSI's metadata is historical as described above; the Commission overview describes its 2025 strategy, not a new Irish plant finding. The decision aids and fictional scenarios are original research methods, not official classifications.

The abstraction summary is adapted from Eurostat, Glossary: Water abstraction, © European Union, under CC BY 4.0; it has been shortened and paraphrased. Eurostat is not responsible for this adaptation or the research method.[11]

The identified GSI summary contains Irish Public Sector Data (Geological Survey Ireland) licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) licence.[9][10] The water-policy summary is adapted from the European Commission, Directorate-General for Environment, © European Union, under CC BY 4.0, and has been shortened and paraphrased.[8] These identified summaries remain available under CC BY 4.0 without additional DemandRange reuse restrictions. No source institution endorses the supplier-route hypotheses.

Catalogue descriptions were checked 9 October 2026; no individual abstraction, operator or current RAL entry was researched.[14][15]

Contains Irish Public Sector Data licensed under a Creative Commons Attribution 4.0 International (CC BY 4.0) licence.[16]

The identified metadata summaries are independently paraphrased and remain available under CC BY 4.0 without additional DemandRange restrictions.[13]

The relationship exercise and enquiry attachment are original. No map, portal content, logo, third-party attachment or personal data is included, and no technical or regulatory clearance is offered.

6. European Commission, Joint Research Centre — Best Available Techniques (BAT) Reference Document for the Food, Drink and Milk Industries (2019). EUR 29978 EN / JRC118627; doi:10.2760/243911. © European Union 2019. Sections 2.1.3.2, 2.3.3.2.4, 2.1.5 and 2.1.4.1. Accessed 30 September 2026.
7. Eurostat — Glossary: Water abstraction
8. European Commission — Legal notice
9. Geological Survey Ireland — Group Scheme Preliminary Source Protection Areas Ireland (ROI) ITM
10. data.gov.ie — Open Data Licence
11. Eurostat — Copyright notice
12. European Commission, Directorate-General for Environment — Water
13. CC BY 4.0
14. River Abstraction Pressures - Dataset - data.gov.ie
15. Environmental Protection Agency Remedial Action List - Dataset - data.gov.ie
16. Open Data Licence - data.gov.ie