Irish industrial OEM account research: from component to build operation

Write a route hypothesis: “We supply [component family]. We want to investigate businesses performing [build operation] on [equipment or system family] in [territory]. The question is whether [specific component-related responsibility] belongs to that business.” This is a question to test, not a claim that the component is used or suitable.

For an Irish brief, specify whether the relevant build operation must occur in the Republic of Ireland, anywhere on the island, or whether supplying customers there is sufficient. Keep the location of the work separate from a sales office or registered address. Use the industrial ICP brief for territory, exclusions and account-acceptance rules; this guide adds the component-to-build map, not another general inclusion checklist.

An equipment family is not an installed base. A build capability is not a production schedule. Record one-off, repeat-build or series-production arrangements only when separately evidenced; do not use “OEM” as shorthand for own design, a factory, recurring orders or purchasing authority.

Treat these as questions about a defined offering and operation, not mutually exclusive classifications of a whole company:

• Equipment brand: under whose name is the equipment offered? A named offering does not establish who designs or physically builds it.
• Assembler or integrator: what parts or subsystems does the business actually combine, wire, mount or test? Name the work and its location; do not transfer the capability to every product in its catalogue.
• Reseller: is this offering a supplied complete product? That fact need not rule out separate assembly work elsewhere in the same business.
• Contract builder: does the business perform a specified build for another party? Keep the supplied design, component provision and ordering arrangement separate. Contract-build work does not establish design ownership or freedom to substitute suppliers.

A single company may have several supported dimensions for one offering and different dimensions for another. Record a separate map for a different equipment family, operation or phase, while keeping the same company identity. Use the manufacturing discovery guide to resolve company, brand and site relationships. Use the distributor guide when resale and channel capability, rather than build work, is the actual question.

The following three maps are invented teaching hypotheses. They are not engineering recommendations or descriptions of normal equipment construction. Each starts with a proposed connection, then uses a stipulated observation to narrow the next research question.

Map A — enclosure hardware and a labelling-machine build

Supplier hypothesis: investigate enclosure hinges and latches in a fictional bench-labelling machine's enclosure-assembly operation. This does not establish that any particular hinge or latch is appropriate.

Invented observation A1: Fictional Machine Builder A assembles the machine from an enclosure and a base at a workshop in the Republic of Ireland. A separate invented card A2 says it offers the finished machine under its own brand. A1 supports the physical build and location; A2 supports the brand dimension. Neither card establishes who makes the enclosure, own design, production frequency, hinge choice or ordering responsibility.

Narrow map: component family → enclosure within bench-labelling machine → machine assembly by A; enclosure build and hardware provision unresolved. The useful next question is “Does A obtain enclosure hardware separately, or receive a supplied enclosure kit?” Look for a permitted, scope-specific build or supply description; do not ask a researcher to reverse-engineer a photograph.

Map B — sensor brackets and a conveyor subassembly

Supplier hypothesis: investigate sensor-mounting brackets in a fictional conveyor subassembly. Keep bracket geometry, materials, interfaces and suitability unassessed.

Invented observation B1: Fictional Contract Builder B assembles conveyor subassemblies in the Republic of Ireland to a customer's supplied drawings. Card B2 says the customer supplies the bracket kits and B performs mounting only for this work. B is an assembler and contract builder for this scope; equipment branding and design ownership remain unresolved.

Narrow map: bracket family → conveyor subassembly → mounting supplied kits by B → bracket provision outside B's stated task. This is useful build-operation research, but it does not support a direct bracket-ordering route to B for that arrangement. The customer is not identified: do not invent its identity or treat it as an available alternative buyer. A separate manufacturing-fixture question about B's workshop would require its own map.

Map C — tube fittings and two different activities

Supplier hypothesis: investigate tube fittings in an invented liquid-dispensing frame. No fluid, pressure, material or connection compatibility is established.

Invented observation C1: Fictional Equipment Business C resells a complete dispensing module. Card C2 separately states that C builds supporting frames in the Republic of Ireland and mounts modules supplied complete. Neither card describes opening the modules or assembling their internal fluid circuits.

Narrow map: fitting family → internal module circuit → internal circuit-build operation unknown; frame assembly is a different operation. Do not turn the supported frame work into evidence that C buys the module's internal fittings. Research the exact boundary of C's frame work if relevant; otherwise keep the internal-component route unresolved. Reseller and assembler are both valid dimensions here, but neither answers this component question.

Continue Map A only with three further fictional cards. These are additional stipulations, not real sources. The point is to discover what crosses the build boundary, rather than to give A a higher score.

1. A3 — supplied enclosure: A receives a complete enclosure with its hinges already fitted. A's machine-build operation does not establish a separate hinge purchase. The enclosure provider's identity is not given.
2. A4 — separate base hardware: for the same machine family, A fits latches to its base access cover. The customer specifies the latch model, and A places the order for it. This is a different component scope from the supplied enclosure; preserve both observations instead of overwriting A3.
3. A5 — change control: A may not substitute that latch model without customer approval. The approval decision-maker and procedure are not identified. Ordering is supported for this latch scope, but independent model choice is expressly restricted; supplier choice and willingness to consider your range remain unknown.

The handover is therefore: “A assembles this machine family locally. Hinges arrive in a supplied enclosure; A orders the specified base-cover latch. Establish whether the order permits supplier choice and how a proposed change would be considered. No available order, technical match or access to a decision-maker is established.”

Do not generalise these cards to all A's machines or future builds. A product revision or a different subcontract arrangement needs a new scope record. An undated capability page and an old build description do not resolve which arrangement applies now.

• “It uses our component word, so it builds the equipment.” A complete-product catalogue can describe an offering without identifying the builder. Inspect the build activity rather than copying the category into an account record.
• “It designed the machine, so it chooses every bought-in part.” Even an expressly supported design task answers only its stated scope. Ask separately about component model choice, approval, supplier selection and order placement.
• “It built one machine, so it has repeat component demand.” The single observation supports that build only. Build frequency, current production and future requirements stay unknown.
• “It installs and services the machine, so it has the manufacturing component route.” Installation, servicing and original build are different operations. Record an evidenced service route separately; do not manufacture a renewal interval or installed fleet.
• “There is no component detail online, so the company cannot be relevant.” Missing detail leaves the component question open. It need not defeat a separately supported equipment-build account fit. End the agreed bounded check with the missing question, not an invented negative.

Download the blank OEM component-route CSV from the resource library. It contains neutral headers only, no example rows, contacts, formulas or automatic decisions. The worked cases stay in this article.

Use one row per fact or unresolved question, not one row per company. Give each row a unique record_id; reuse company_id and map_id for the same company and component/equipment/operation scope. Multiple rows are not multiple accounts. record_context distinguishes your working research from an explicitly labelled fictional practice copy. Keep the brief reference in brief_version.

component_family_question, equipment_family_question and operation_question describe the hypothesis, not observed facts. Use fact_name for the precise assertion being tested, such as build_activity, build_location, equipment_brand, contract_build, component_provision, model_choice, supplier_choice, approval_constraint or order_placement. Create separate rows for company identity and each material role fact; do not let the map labels stand in for evidence.

Write the narrowly supported statement in permitted_observation. Use fact_status values supported, explicit_negative, unknown, conflict or not_assessed. An explicit negative needs evidence too. Keep unknown observations empty and explain the missing check in next_question. For incompatible observations, preserve separate rows with their own evidence and a shared conflict note; do not silently pick the preferred account story.

Every row has its own evidence_reference, source_location, source_stated_date, checked_date and source_use_status. Put the exact item/section or controlled evidence identifier beside the fact it supports, not a generic homepage reference for the whole map. Use the date actually checked; leave an unstated publication date blank. Describe the applicable period or build revision in scope_and_period. Where a fact needs several sources, use separate evidence rows linked by the same map and fact name.

Check source/item conditions for the intended use before retaining content. A public page is not permission to redistribute it. If rights are unresolved, keep the observation out and record only a permitted review reference and the open rights question. Do not paste confidential drawings, bills of materials, customer lists or personal contact data. Import as UTF-8 text; do not enable spreadsheet formula interpretation for pasted source content.

research_implication is your bounded interpretation, not a qualification verdict. Put absent links and technical/commercial limits in unknowns_and_conflicts, then specify the next question and stopping_rule: what will be checked within the agreed scope, and what stays unresolved if that check cannot answer it. There is no score, automatic acceptance or promised account count.

A useful brief is: “We supply [component family] and want to investigate [equipment family/build operation] in [defined Irish territory]. Establish the performed work and component-provision boundary. Separate model choice, supplier choice, approval constraints and ordering. Leave technical suitability and current demand unassessed. Apply [agreed exclusions] and return [specified missing questions].”

DemandRange describes company-level, industry-matched research against an agreed brief; an active project is not required for that class.[1] Its methodology separates observed facts, interpretation and unknowns and does not treat either research class as automatically marketing-qualified.[2] These first-party references explain service scope only. They do not empirically validate the original method or fictional maps above.

Review the industrial account-research service, inspect the fictional account sample, then request a scoped quote. Share non-confidential range and research questions, not live customer records. This guide provides no guarantee of buying intent or marketing-qualified leads, supplier qualification, engineering or legal advice, or authority to contact anyone.

1. DemandRange: industrial account-research service and scope
2. DemandRange: research classes, evidence layers and boundaries