IT Infrastructure for Residential Site Management: IP Cameras, Elevator IoT, and Dues Systems
Summary: An integrated IT infrastructure and KVKK compliance guide for IP cameras, elevator IoT, dues collection, and resident management systems in residential complexes.
Summary: IT infrastructure in residential site management becomes meaningful when IP cameras in common areas, elevator IoT links, dues collection systems, resident request/issue management platforms, and 5651-compliant common-area Wi-Fi are designed as an integrated whole. The classic setup — dues tracked in Excel, fault tickets written in the doorman's notebook, camera recordings on a local disk — leaves you without documentation in a KVKK audit and without follow-through on a resident complaint. A correctly designed IT infrastructure merges these three flows in one panel and cuts a site manager's day from 8 hours to 3.
In a residential site, a resident wakes up to an elevator alarm ringing all night, calls the doorman, the issue is passed to the manager in the morning, the manager calls the elevator company — the chain takes 12 hours. The dues collection report is pulled from Excel, but a resident who paid at 23:00 still appears on the "debtors" list the next morning. In a KVKK audit, pointing to the filing cabinet in the doorman's office as the answer to "where and how long do you store resident data?" is no longer a valid answer.
In this article we cover integrated IT architecture for IP cameras, elevator IoT, dues systems, and resident management platforms — aimed at residential site managers, apartment-block managers, and property management firm owners. Our target scale is residential sites and housing developments with 50-1,000 units.
Five Different Systems in Site Management
A modern residential site has five core systems that look independent on paper but should actually work as one.
1. Dues and Collections System
Per-unit dues calculation, payment tracking, late-payment alerts, invoices and collection reports.
2. Resident Requests and Fault Management
Residents submitting requests to management, status tracking, assigned personnel, and resolution-time measurement.
3. Security and IP Cameras
Cameras at the site entrance, common areas, parking, and inside elevators (within legal limits).
4. Elevator and IoT
Elevator fault/maintenance alerts, common-area heat/smoke sensors, remote meter reading.
5. Common-Area Wi-Fi (if applicable)
Wi-Fi in lobby, pool, social facilities — 5651-compliant logging is mandatory.
Managing these five systems from a single panel dramatically speeds up the site manager's day-to-day operations.
Dues and Collections System
Tracking dues in Excel works up to about 50 units; beyond that, the error rate climbs and resident complaints start.
Typical Dues Software Features
- Per-unit dues calculation (proportional to m² or fixed)
- Automatic invoicing (monthly/quarterly)
- Online payment integration (credit card, wire transfer, EFT)
- Automatic late-fee calculation
- Resident profile (contact info, unit size, tenant/owner)
- Annual audit report
- Residents see their own dues history (resident portal)
Online Payment Integration
Popular integrations at SME scale: iyzico, Param, ipara, Garanti BBVA Virtual POS. The resident logs into the portal, pays by card, and the system marks the payment automatically.
Per PCI-DSS, card data is not stored on your side; the payment provider's tokenization handles it.
Doorman/Manager Collection Mode
Some residents still pay in cash or in person. The software should include a "doorman collection" mode: the doorman enters the payment, a receipt is generated, and the resident gets an SMS notification. This minimizes "I paid but it does not show" disputes.
Resident Request and Fault Management System
Instead of "the sink is leaking" notes in the doorman's book, a centralized request system:
Request Flow
- Resident opens a request via portal/app
- The system auto-categorizes (water, electrical, elevator, security, etc.)
- Management sets priority (urgent/normal/low)
- Assigned personnel are notified
- Personnel update the status (en route, started, completed)
- Resident confirms completion and rates with a satisfaction score
Benefits
| Classic | Modern |
|---|---|
| Requests are passed verbally, forgotten | Every request is logged and traceable |
| Status is unknown, residents call repeatedly | Residents track it themselves in the app |
| Resolution time is not measured | Average resolution-time report |
| Management performance is subjective | Objective satisfaction scores |
| Annual general meetings turn into arguments | Data-backed performance report |
Annual General Meeting Report
The year-end management report shown to residents:
- Total request count (by category)
- Average resolution time
- Resident satisfaction score
- Most problem-prone areas
- Cost analysis
This report answers "management does nothing" complaints with data.
IP Camera System
Cameras are the eyes of site security. A correct design has to balance KVKK and technical considerations.
Recommended VLAN Structure
A typical segment structure for a site network:
| VLAN | Purpose |
|---|---|
| 10 | Management (switches, routers, APs) |
| 20 | Management office (computers, printers) |
| 30 | Dues/resident software server |
| 40 | IP cameras + NVR |
| 50 | Elevator IoT, heat sensors |
| 60 | Common-area Wi-Fi (lobby, pool) |
| 70 | Guest Wi-Fi (if any) |
The camera VLAN has restricted internet access (only for cloud backup). NVR access from the management office is role-based; residents under no circumstance get access.
Camera Placement Rules
What to watch for from KVKK and privacy perspectives:
- ✅ Site entrance, parking, lobby, elevator cabin (limited), common areas
- ⚠️ Garden, children's playground (heightened sensitivity for children's data)
- ❌ Angles that directly view apartment doors (neighbor privacy)
- ❌ Apartment balconies, windows
- ❌ Toilets/showers, changing rooms
- ❌ Recording neighboring buildings or public roads (unless there is a lawful basis)
An Informational Notice Is Required
A "recording in progress" sign must be posted at the site entrance and inside the elevator. The privacy notice must be shared with residents at the annual or extraordinary general meeting.
Retention Period
- Standard corridor/lobby: 30 days
- High-value areas (parking, storage): 60-90 days
- Post-incident evidence archive: 2+ years (immutable)
When the retention expires, the recordings are deleted automatically; no manual action from the manager is needed.
Elevator IoT and Sensor Systems
IoT connectivity is becoming standard in modern elevators.
Typical Elevator IoT Data
- Elevator call counts (by day/hour)
- Fault/warning codes (real time)
- Maintenance reminders (statutory cycles, wear)
- Emergency button signal (someone trapped inside)
- Door open/close counter
- Motor temperature, vibration data
IoT Network Architecture
Elevator IoT devices live on a separate VLAN (we recommend VLAN 50). Internet access is restricted to the manufacturer's cloud (Otis One, KONE Care, etc.). No access to the IoT devices from the internal network — a one-way design.
Other IoT Sensors
- Remote water meters: LoRaWAN or NB-IoT, per-unit consumption tracking
- Heat/smoke sensors: Parking, storage, social facilities
- Door/window sensors: Social facilities, pool lockers
- Air quality sensors: Parking exhaust tracking (mandatory in new buildings)
All these devices must be strictly segmented to keep "Mirai"-style IoT botnet attacks from reaching the site network.
Common-Area Wi-Fi and 5651
If Wi-Fi is offered in common areas such as the lobby, pool, social facility, or children's playground, the 5651 obligations fall on the site management.
Obligations
- Access logs must be kept for two years
- User authentication (SMS code, resident's ID, etc.) is mandatory
- Logs must be signed and tamper-proof (TIB-approved logger or cloud service)
- You must be able to produce records within 30 minutes during an audit
Practical Solution
Cloud-based 5651 services make sense at site scale: a monthly cost of TRY 500-1,500, no hardware to buy, deployment in a few hours. A hardware logger is TRY 30,000-100,000 up front + annual maintenance.
For resident Wi-Fi, one-time authentication via Turkish ID or resident number; for guests, an SMS code.
Resident Data and KVKK
Site management processes residents' Turkish ID, name, address, contact info, property status, and payment data. Under KVKK it is the data controller.
VERBİS Registration Obligation
Site managements that meet certain criteria (employee count, annual revenue, etc.) are required to register with VERBİS. Failing to register carries the risk of administrative fines.
Privacy Notice
A privacy notice that lays out residents' rights and how their data is processed:
- Which data is processed (Turkish ID, contact, payment, camera, IoT, etc.)
- For what purposes (dues collection, security, legal obligation)
- How long it is retained
- Who it is shared with (the cleaning company, the elevator maintenance company, etc.)
- Residents' rights and the contact channel
Data Processor Agreements
The dues software provider, the camera cloud provider, the elevator IoT company — a data processor agreement must be signed with each of them. Otherwise, KVKK breach liability falls directly on the site management.
What Yamanlar Bilişim Offers
End-to-end support areas sized to site management:
- Dues and resident management software selection
- IP camera network design and KVKK compliance
- Elevator IoT integration and network segmentation
- Common-area Wi-Fi design + 5651 logger
- Resident portal and mobile app infrastructure support
- Technical support for the KVKK privacy notice
- VERBİS guidance
- Resident-data backup + immutable archive
Frequently Asked Questions
Conclusion
IT in site management is no longer optional; it is mandatory. When these five systems — from dues collection to resident requests, from IP camera privacy to elevator IoT — are integrated correctly, the site manager's operational load drops, resident satisfaction becomes measurable, and KVKK and 5651 obligations are met in a controlled way.
At Yamanlar Bilişim, we design solutions that match your site's scale, existing infrastructure, and management model — turning the service quality residents expect into a system that your manager can run easily.
Frequently Asked Questions
My site is small (30 units) — are all these systems still necessary?
At small scale, a simple dues software + basic camera system can be enough; it is not necessary to install every component. However, 5651 compliance (if Wi-Fi is offered) and the KVKK privacy notice do not depend on size — the legal obligations are the same for every site management. A small site means less work to do, but not zero.
My elevator company wants an IoT connection — is that a problem?
The ideal approach: the elevator IoT on its own VLAN (managed by you, the site IT) with internet access restricted to the manufacturer's cloud. If the manufacturer wants access to the entire network, do not accept — good vendors respond positively to a separate VLAN and controlled access.
A resident claims a camera points into their apartment — what do I do?
This is a KVKK violation claim and must be taken seriously. Immediate action: (1) verify the angle of the named camera, (2) correct the angle or remove the camera if needed, (3) respond in writing to the resident. Camera angles should be reviewed every year at the general meeting and recorded in the minutes. Camera angles that infringe on neighbor privacy can become a complaint to the KVKK Authority.
A resident who paid online says they were charged twice — what is the fix?
The dues software's payment integration must be idempotent — the same transaction must be rejected on the second attempt. If a double charge did occur, an automatic refund request can be opened from the payment provider's (iyzico, Param, etc.) panel. The annual audit should monitor a double charge report; if the count is high, the software should be updated.
Can I offer site Wi-Fi without a 5651 logger?
No. Law 5651 imposes logging obligations on access providers (anyone offering Wi-Fi — cafés, hotels, sites included). Offering Wi-Fi without a logger creates administrative and criminal liability. A cloud 5651 service covers this obligation at a monthly cost of a few thousand TRY.
A resident has requested delete my data — what do I do?
Under Article 11 of KVKK, residents have the right to request deletion. However, data with statutory retention (collection records, the books of account — 10 years) cannot be deleted. Other data (contact info, expired camera recordings, etc.) must be deleted, and the resident must receive a written response within 30 days. The cleanest approach is to prepare a documented procedure for full deletion.
Author
Serdar
Yamanlar Bilişim Expert
Writes content on IT infrastructure, cybersecurity, and digital transformation at Yamanlar Bilişim. Get in touch for any questions.
Professional Support
Get help on this topic
Let's design the Industry IT Solutions solution you need together. Our experts get back to you within 1 business day.
support@yamanlarbilisim.com.tr · Response time: 1 business day
Keep Reading
Related Articles
Contract Archive and KVKK Architecture for Fleet-Leasing Companies
Contract archives, driver-data KVKK alignment, e-signature integration, and site-to-site VPN for branches in fleet and car-rental companies.
Endpoint Security on Doctor and Clinic Computers: An EDR Playbook
Choosing EDR for doctor workstations in clinics and private practices, extra controls for endpoints carrying patient data, and a USB policy.
OT/IT Network Separation in Manufacturing: A Practical Architecture for SME Factories
Separating OT (operational technology) and IT (information technology) networks in manufacturing, PLC/SCADA segmentation, and industrial firewall architecture.