Parking Software

Question: Is the system cloud-based, or can it be deployed in a municipal data center?

Answer: The architecture is hybrid. Central management can run in the cloud, and the full platform can also be deployed on-premise in a municipal data center. Critical data can stay on institutional servers, and data ownership remains with the municipality.

Question: Does entry/exit operation stop during an internet outage?

Answer: No. With the Edge Controller architecture, plate recognition, barrier control, and transition logs continue in offline mode. Accumulated records are synchronized automatically when connectivity returns.

Question: How long can the system run during power outages?

Answer: Standard installations include at least 2 hours of UPS backup. For critical locations, 4-6+ hour capacities can be provided. Depending on load profile, optimized 3 kVA online UPS setups can support longer operation windows.

Question: How are backup and disaster recovery implemented?

Answer: The platform supports daily incremental backups, weekly full backups, and instant snapshots. Backups can be stored in municipal infrastructure or Turkey-based data centers, with optional automatic transfer to the municipality IT unit.

Question: Which technical controls are used for data security?

Answer: Data in transit is protected with SSL/TLS, and data at rest is encrypted at AES-256 level. Access is restricted through role-based permissions and tracked with timestamped audit logs.

Question: How many barriers per site and how many parking facilities centrally?

Answer: Stable operation has been validated in single-site scenarios with 10 active entry/exit barriers. On the central side, simulations and load tests were performed up to 10,000 parking facilities.

Question: What is the barrier command latency and high-traffic performance?

Answer: Barrier commands are processed at millisecond-level latency. Edge processing, queue management, and load balancing reduce central dependency during peak traffic, with support for at least 25 FPS processing.

Question: What is the LPR (license plate recognition) accuracy level?

Answer: In field conditions, Turkish plates target 98%+ accuracy and can reach up to 99.8% with correct camera configuration. Foreign plate recognition performance is typically 90%+.

Question: Is plate recognition reliable at night?

Answer: Yes. IR-assisted night vision, anti-glare optics, and correct field positioning provide strong low-light performance. Optional dual-camera validation further reduces error rates.

Question: What are the concurrent user and vehicle capacities?

Answer: Single-site scenarios with 100,000+ active vehicle records have been tested. The platform runs on clustered architecture; user limits are not hard-coded and scale with server resources.

Question: Can debt, subscription, and blacklist checks work without internet?

Answer: Yes. Field transactions are stored in the local database, and debt/subscription/blacklist checks continue offline. Once connection is restored, data reconciliation runs automatically.

Question: Can existing plate debt records be migrated to the new system?

Answer: Yes. Migration is supported via CSV, Excel, or API. The process includes validation, duplicate detection, format standardization, and data cleansing.

Question: Is it compatible with existing barriers, turnstiles, and cameras?

Answer: Yes. The open protocol approach supports dry contact, RS485/TCP-IP, ONVIF, and RTSP-based integrations. A pre-install inventory analysis is performed and a compatibility report is prepared.

Question: How does the licensing and update model work?

Answer: The commercial model is finalized contractually per project. A perpetual one-time licensing approach can be combined with maintenance/support coverage, while committed core updates are managed under the agreed scope.

Question: How detailed are revenue and payment reports?

Answer: Daily, monthly, yearly, and custom date-range reports are available with parking-lot and staff breakdowns. Cash, card, QR, mobile, and subscription collections are tracked separately and exported as PDF, Excel, or CSV.

Question: What integration options are available for accounting systems?

Answer: REST API is the primary method. SOAP/web services and file-based integrations (JSON/XML/CSV) are also supported when required. Daily batch transfer, real-time transaction transfer, and bi-directional reconciliation can be implemented.

Question: How are revenue leakage and unauthorized exits detected?

Answer: Entry-exit plate matching, manual barrier-open logs, camera-transaction matching, and suspicious transaction reports run together. Immutable logs provide full retrospective auditability.

Question: How are compliance, data ownership, and retention handled?

Answer: Data ownership belongs to the relevant institution. Operations are designed for KVKK-aligned compliance processes, and retention rules are configured by policy and regulation. At end-of-retention, deletion/anonymization/destruction actions are logged.

Question: What is the support and scaling approach in production?

Answer: For software incidents, 24/7 remote support is provided with priority handling for critical cases. The modular architecture enables stepwise expansion by adding parking sites, cameras, barriers, and server resources.