Frequently asked questions
The questions property owners, committees and developers ask about maintenance, access and handover, before a proposal.
Maintenance and bookings
How are work orders and planned maintenance recorded?
Against the equipment and the location. A request from a tenant, a resident or staff is assigned and tracked to closure, and planned preventive maintenance is held against the same equipment. What broke, who attended, when and under which contract are one record, so warranty and contract performance are answerable.
How do facility bookings work?
Function rooms, courts, the pool and the hall are booked against the rules the community sets: entitlements per parcel, deposits, blackout periods and cancellation. Residents book through the resident portal in asasii ledger, and each booking is held against their parcel, so bookings stop being a logbook and a dispute about who asked first.
Access and handover
Do we have to replace the barriers, access control or intercoms we have?
No. Barrier systems, access control and intercoms already installed stay where they are, and so does the building management system. idataraya integrates asasii facilities with them, so a change in the register reaches the gate.
How do access cards follow the register?
Resident cards are held against the parcel and driven by the register in asasii ledger. When a tenancy changes, the card is deactivated because the register changed, not because someone remembered. Visitors, deliveries and contractor permits are held against the lot or parcel too.
How are defects handled after vacant possession?
Vacant possession, key collection and the defect liability period run as one workflow. Each defect a purchaser raises is assigned to the responsible contractor and tracked to closure, and the developer sees what is outstanding by block, by contractor and by age. At handover, defects and warranties carry across to the management office rather than being re-entered.
Ownership and the agreement
What happens to our records when the managing agent changes?
They stay with the property. The asset list, the work order history and the maintenance record are held in the property's own environment, not in the agent's system. A change of agent becomes a change of access, not a rebuild from scanned files.
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. It works beside asasii ledger and asasii parking, and a documented API lets the property's other systems or a third party read work orders, assets, bookings and access records 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, and the changes needed as tenancies turn over and assets are added. Hosting stays with you. It is a fee, not a subscription.
Still have a question?
Send it with the property and the number of lots or parcels, and an engineer replies within one working day.