Account requirement
Record the customer type, building application, security objective, approval path and the operating outcome expected after handover.
End-user project baseline
Turn the customer requirement into an issued specification.
This route is for downstream teams selling to, and delivering for, an end user—not for regional stock or channel coverage. The brief should connect the use case, commercial proposal, site conditions and accountable handover party.
Commercial proposal
State the selected product line, door or unit count, option set, demonstration requirement, budget frame and planned decision date.
Site and system boundary
Confirm door construction, power, cabling and the systems in scope: intercom, lock, reader, controller or property platform.
Delivery ownership
Name the party responsible for installation, configuration, site tests, end-user training and post-handover support.
Pre-installation review
Confirm the interfaces before final pricing and site release.
A dealer needs a proposal that can be presented accurately; an integrator needs a configuration that can be commissioned. Confirm the selected SKU, firmware, topology and external platform before the scope is committed.
NetworkConfirm Ethernet, PoE or Wi-Fi topology, VLAN ownership, addressing policy and responsibility for switch configuration.
Access layerConfirm reader format, Wiegand or OSDP wiring, controller capacity, relay logic, exit devices and the door-hardware interface.
PlatformsRecord any SIP PBX, ONVIF VMS, BMS, PMS or API dependency, the required data flow and the integration owner.
Operating modeDefine online, offline or hybrid operation, remote administration, credential issue and expected behaviour during network or power failure.
Project handover file
The document set follows the selected configuration from proposal to acceptance.
Selection record
Selected configuration, finish, accessories, coverage and the site assumptions on which the commercial offer is based.
Technical set
Applicable mechanical drawings, wiring or power data, network notes and protocol guidance confirmed for the selected SKU.
Commissioning record
Test scope, installer responsibilities, user training requirements and the acceptance documents required by the project owner.
Dealer & integrator pathway
Specify, install and support smart access projects.
For technical teams that need clear product fit, integration details and a practical handoff from project discovery to deployment.
Discuss Your ProjectProject-ready support
Move from specification to delivery with fewer gaps.
System fit
Clarify building type, door count, residents, credential method and required platform integrations before selecting a model.
Technical package
Wiring diagrams, CAD cutout templates, SIP/Wiegand/OSDP/ONVIF integration notes and commissioning checklists provided per model.
Deployment support
Installer training, commissioning review, warranty scope and after-sales ownership aligned before the first delivery.
API & SDK access
SDK and API documentation available for qualifying integration projects under NDA. Confirm the platform, protocol and use case in the initial inquiry.
Technical resources
Documentation available for projects.
Mechanical drawings
CAD drawings and DXF door cutout templates for panel, flush and surface mount configurations.
Wiring & power
2-wire, 4-wire and IP cabling schematics, power supply requirements and PoE specifications per model.
Protocol integration
SIP (RFC 3261), ONVIF Profile S/T, Wiegand 26/34, OSDP v2 and dry-contact relay notes confirmed by SKU.
Project brief
Send the details that affect the solution.
A complete brief allows the technical team to confirm product fit, documentation and pricing in the first response rather than a round of clarification questions.
1
Country & building
Country, building type and estimated door or unit count (min 10 doors recommended).
2
New build or retrofit
Confirm existing wiring, conduit and door hardware for retrofit projects.
3
Product functions
Video intercom, smart lock or access control functions required.
4
Network topology
Ethernet, Wi-Fi, PoE switch, VLAN, SIP PBX, VMS or offline operation.
5
Integrations
Platform integrations: SIP PBX, VMS, lift controller, PMS, Wiegand or API.
6
Delivery plan
Target delivery date, sample plan, installer training and warranty expectations.
FAQ
Project specification questions
Project pricing is reviewed from 10 doors or units. State the building application, door count and product line in the brief. Sample or pilot orders can be supplied at standard pricing before a larger site roll-out is agreed.
SIP (RFC 3261) integration notes and ONVIF Profile S/T documentation are available for qualifying models. Provide the model, firmware version and target platform before selection; integration scope is SKU-specific and must not be assumed across the range.
SDK and API documentation is available for qualifying projects under NDA. State the platform, intended data exchange and project scale in the brief. Access is assessed against a defined project scope, not issued for open-ended evaluation.