What drawings help a supplier quote an intercom or access control project?

Provide a simple site or floor plan showing entrances, doors, lifts, apartment count, cable route, network points and the location of any existing equipment. Marking unknowns is better than presenting an outdated drawing as final.

B2B Access Control RFQ Checklist: 12 Inputs That Prevent Rework

Most quotation delays are not caused by a slow factory. They start with an RFQ that names a product category but leaves the project boundary open: “smart lock for apartments,” “video intercom with app,” or “access control for 1,000 doors.” Different suppliers then price different systems, and the comparison becomes a spreadsheet of unit prices with no shared scope.

A useful RFQ is not a long specification written before the design is known. It is a short, honest project brief that tells the supplier what is fixed, what is preferred and what is still unknown. The 12 inputs below are enough to start a technical and commercial review without pretending the design is already final.

The 12 inputs to include in a B2B RFQ

#	Input	Send this information	It changes
01	Application	Apartment, villa, office, hotel, public building or mixed use	Product family, user workflow and environmental requirements
02	Scale	Units, doors, entrances, floors, sites and rollout phases	Architecture, quantities, server scope and deployment plan
03	Entry topology	Pedestrian gates, lobby doors, parking, lifts and secondary entrances	Door stations, controllers, readers and visitor paths
04	Credential method	PIN, RFID, fingerprint, face, mobile, QR or a mixed policy	Hardware choice, privacy review and fallback operation
05	Existing infrastructure	2-wire bus, Ethernet, PoE, RS-485, Wiegand, OSDP or new cabling	Retrofit feasibility, accessories and installation labor
06	Power and environment	Supply, lock type, load, IP rating, temperature and mounting conditions	Electrical design, enclosure and field accessories
07	Interface requirements	SIP, ONVIF, API, lift, PMS, BMS, app or third-party platform	Integration effort, firmware and test responsibility
08	Network ownership	Customer LAN, dedicated VLAN, cloud, local server or hybrid	Addressing, cybersecurity review and support boundary
09	Destination route	Country, importer, intended use and known certification requirements	Documentation, radio approvals and available configuration
10	Brand scope	Standard supply, white label, OEM, ODM, packaging and app branding	MOQ, tooling, artwork, firmware and approval steps
11	Validation plan	Sample quantity, site test, acceptance criteria and required documents	Sample schedule, engineering time and release decision
12	Commercial plan	Target quantity, annual forecast, launch date, Incoterm and spare policy	Lead time, price basis, production allocation and after-sales plan

Separate fixed requirements from open decisions

Mark each line in the RFQ as confirmed, preferred or to be proposed. For example, “PoE to each entrance” may be confirmed, while “mobile app” is only preferred until the property operator decides whether residents or guards will manage credentials.

This simple label prevents a common procurement error: treating a supplier suggestion as a contractual requirement in one quote and as an optional feature in another. It also gives the supplier permission to propose a lower-risk architecture when the original request is not yet technically closed.

What a useful drawing looks like

You do not need a fully coordinated construction drawing to start an RFQ. A marked-up PDF or simple plan is enough if it shows the items that change the system boundary:

Every entrance, door, lift lobby and vehicle gate in scope.
Approximate distance or cable route between field devices and the control point.
Existing equipment that must remain, be replaced or be integrated.
Network and power points, with unknown locations labeled as unknown.
Unit count, apartment types and rollout phases for multi-site work.

Marking an uncertainty is more professional than hiding it. The quote can then carry an explicit assumption and a clear site-survey requirement.

Interfaces need names, not just acronyms

“ONVIF compatible” or “SIP supported” is not enough to compare two bids. State what the interface must do: video discovery in a VMS, two-way call setup, door release, event push, lift authorization or credential synchronization. For ONVIF access-control work, identify the expected profile and client behavior; ONVIF publishes separate profile scopes for access control and video functions, so the profile boundary should be part of the test plan.

The same principle applies to Wiegand, OSDP, RS-485 and API integrations. Name the direction of data, the event that must be exchanged and who supplies the test endpoint. This is where a short technical call before quotation can save weeks of email clarification.

RFQ rule of thumbEvery requested feature should answer one of three questions: what must the user do, what must the system exchange, or what evidence proves acceptance. If it answers none of them, it is probably a marketing label rather than a quote requirement.

MOQ, lead time and certification belong in the same conversation

MOQ is not a universal number. A standard product order, white-label packaging, an OEM firmware change and a new ODM design consume different production and approval resources. Ask the supplier to separate:

Standard product quantity and price basis.
Branding or packaging minimums.
Engineering or tooling charges, if any.
Sample availability and sample lead time.
Mass-production lead time after approval.
Certification or documentation included in the quoted scope.

Include the destination at the first request. A compliance route can affect the product variant, label, radio configuration and documentation pack. Adding it after the price is agreed creates avoidable rework.

How to compare the returned quotes

Normalize the replies into the same columns before choosing a supplier. At minimum compare hardware scope, firmware or app scope, licenses, integration responsibility, certification evidence, samples, packaging, spare parts, warranty, delivery term, payment term and exclusions. Ask each supplier to state assumptions on the quote itself.

If two quotes still cannot be compared, the problem is usually not the price. It means one of the 12 inputs is still open. Close that input, issue a revision number and request a refreshed quotation.

A concise RFQ opening you can reuse

Subject: [Project] [Country] — [Product scope] RFQ, [quantity] unitsApplication: [building type and user workflow]. Scale: [units / doors / sites]. Interfaces: [SIP / ONVIF / OSDP / API]. Existing infrastructure: [cabling and equipment]. Destination: [country and certification route]. Commercial target: [sample date, launch date, quantity and Incoterm]. Please separate standard supply, OEM or branding scope, sample lead time, mass-production lead time, documents and exclusions.

That opening gives a supplier enough context to ask useful questions. For a formal submission, use the full 12-point checklist and attach the drawing, device schedule and acceptance requirements.

FAQ: B2B access control RFQs

No. A model number identifies a starting product, but it does not define the building topology, interfaces, power conditions, quantity, certification route or rollout. Send the project inputs together with the preferred model or product family.

Standard supply uses an existing configuration. OEM or white-label work may add branding, packaging, firmware, app, tooling or certification tasks, so the commercial threshold and lead time depend on the agreed scope and production plan.

Include the destination and intended application before quotation. Certification, radio approvals, importer evidence and project documentation can change the available hardware, test plan and commercial route.

Provide a simple site or floor plan showing entrances, doors, lifts, apartment count, cable route, network points and the location of existing equipment. Marking unknowns is better than presenting an outdated drawing as final.

Compare like-for-like scope: hardware, firmware, licenses, cloud or server responsibility, certifications, sample tests, packaging, spare parts, warranty, delivery terms and exclusions. The lowest unit price is not comparable if integration or documentation scope is missing.

Interface reference: ONVIF Profile A and ONVIF Profile C. For a project-specific quote, submit the completed brief through the RFQ page.