Car park management for commercial property
Plate recognition at every lane, season parking billed from the lease, and every ringgit settled into the property's own account. No concession, no revenue share, no cash on site.
- Cashless lanes
- The plate is the ticket. Public vehicles pay by plate or QR.
- Season parking from the lease
- Billed as one line on the tenant's rent invoice.
- Settled to your account
- Host to host with the bank, reconciled automatically.
- Owned outright
- The software, the equipment and the data stay with the property.
From the lane to the tenant's invoice
Everything the car park does, on one set of data.
- Cashless lanesThe plate is the ticket, and public vehicles pay by plate or QR.
- Season and tenant parkingAllotments from the lease, billed as one line on the rent invoice.
- Operations consoleEvery lane live on one screen, with every exception in order.
- Management consoleMonth to date, receivables, approvals and a rate simulator.
- Payments and settlementSettled to the property's account and reconciled automatically.
- IT and device estateEvery device on one console, and a group view across properties.
A day at the car park on asasii parking
From the first season holder at the barrier to the season parking on the rent invoice.
The first season holder
The lane reads the plate and the barrier lifts. Season, tenant and booked vehicles never stop.
A visitor drives in
The plate is the ticket, so there is nothing to take, keep or lose at the entry barrier.
A tenant validates a visitor
The tenant validates the visitor's parking against the company account.
A barrier fault
The exception queues by severity on the operations console, with its lane, its cause and how long it has waited.
The line drops
The lane controller keeps reading plates and lifting the barrier for recognised vehicles, and syncs every session when the line returns.
The evening exit
Visitors pay by plate or QR without leaving the car. Four in ten vehicles never stop at the barrier.
Collections reconciled
Settled host to host into the property's account and matched to the bank statement automatically.
Season parking billed
One line on each tenant's rent invoice, e-invoiced through MyInvois under the property's tax number.
Built for commercial property
Shopping malls, office towers, mixed-use developments and property groups.
Shopping malls
Public, tenant and staff parking, visitor validation and event bookings.
Office towers
Season parking from the lease, billed on the rent invoice, with visitor validation.
Mixed-use developments
Several user groups sharing one car park, each billed the right way.
Property groups
Every site on one platform, each with its own lanes and account.
Ownership, not a concession
The property buys a system and keeps everything it produces. idataraya is paid to build, customise and maintain the platform, not a share of what the car park earns.
| Topic | A concession | asasii parking |
|---|---|---|
| Who keeps the collections | The operator, less a share to the property | The property, settled to its own account |
| Who owns the software and equipment | The operator, removed when the contract ends | The property, from day one |
| Who owns the data | The operator, a report on request | The property, export is a button |
| Where it runs | The operator's systems | The property's own environment |
| Tenant parking | A separate arrangement, separately billed | From the lease, on the rent invoice |
| What it costs | A percentage of revenue for the life of the contract | A system, plus a yearly fee with defined response times |
| Adding a site | A new negotiation | Its own lanes and account on the same platform |
Security and Malaysian compliance
The questions procurement and audit ask, answered in the platform.
Security and data overview- MyInvois e-invoicing
- Season parking e-invoiced under the property's tax number.
- PDPA 2010
- Plate images and personal data stay in the property's own environment.
- PCI DSS
- Card data stays with the acquirer and never touches the platform.
- Single sign-on and MFA
- On every console, with roles scoped by site and function.
- Audit trail
- Every action recorded with the previous value and kept for seven years.
- Integration
- A documented API for sessions, passes and settlements.
Installed and maintained by idataraya
asasii parking runs in the property's own cloud account or data centre. idataraya installs it, hardens it and keeps it current, and the property's team holds the keys, the backups and the data.
- Response times by severity, measured monthly
- Monitoring from within the property's environment
- A technician on site within the agreed window
- Spare devices and preventive maintenance visits
Questions property owners ask
About the lane, the money and the agreement.
What happens at the lane when the network drops?
The lane controller keeps a persistent session with the platform and continues to read plates, drive the display and open the barrier for recognised vehicles on its own. When the line returns it syncs every session it handled. Nothing at the lane depends on a single server being up.
Do we have to replace the barriers we have?
Usually not. A lane needs an asasii LPR controller and a barrier the controller can drive. Most existing high-speed barriers qualify; the lane survey in the proposal lists which do and which do not.
How is season parking billed to tenants?
From the lease. Each tenancy carries an allotment derived from its lettable area. Registered plates up to the allotment are recognised at the lane; extra vehicles are charged at the season rate once the property approves them. Parking appears as a line on the tenant's regular invoice, e-invoiced under the property's tax number.
Where does the money settle, and who reconciles it?
Collections settle host to host with the acquiring bank into the account the property nominates. The platform matches the bank statement to sessions automatically, and finance reads a reconciled report. There is no cash anywhere in the system.
Is the platform in scope for our PCI assessment?
No. Card data is taken by the acquirer's terminals and gateway and never touches the platform. The property's PCI scope stays where it already is.
Where does it run, and can our other systems talk to it?
In the property's own cloud account or data centre. idataraya installs it, hardens it and keeps it current, and the property's team holds the keys, the backups and the data. A documented API lets the property's finance system, building management system or a third party read sessions, passes and settlements and post what they need to.
What does the yearly agreement cover?
Software updates, the customisations made for you, monitoring, severity-based response and restoration targets, preventive maintenance visits, spare devices held for the site and on-site attendance within the agreed window. Hosting stays with you. It is a fee, not a share of collections.