ONE TERMINAL.
EVERY OPERATION
UNDER CONTROL.

AUTOSERVA is an industrial-operations control platform for buildings, fleets, clubs and facilities, built by VYROX INTERNATIONAL SDN BHD and powered by VYROX AI — the AI that specializes in business operation management together with IoT. It is purpose-built for ops teams that want a control-room interface, dense telemetry and 24/7 dependability.

AUTOSERVA generates a UBL 2.1 JSON payload, signs it, submits to the LHDN MyInvois sandbox or production endpoints, stores the returned UUID and sharing URL, and walks in a fallback buyer TIN (EI00000000010) for over-the-counter customers. The MSIC code list is bundled. Invoices, consolidated invoices, credit notes and refunds all flow through the same audit trail; failed validations surface in a queue for one-click retry.

Yes. We provide CSV and Excel templates for customers, units, contracts, opening balances and meter readings. Patrick walks your team through a sample import in week 1 and we run a parallel period before cutover.

Yes — four apps: customer/resident, security, staff and delivery courier. They share the same backend; access is role-controlled and changes appear live across web and mobile.

SmartFACE captures only the embedding (a vector), not raw photo storage by default; consent is captured per resident, retention windows are configurable, and admin actions on biometric data are logged. Visitors can be processed via QR pre-registration without enrolling biometrics at all.

Both. AUTOSERVA has a full GL, cashbook and reconciliation; for sites that prefer to keep AutoCount, the AutoCount Connector — a hosted middleware at safetech.org.my/VYROX-AutoCount-Connector with Bearer-token auth — supports invoice / payment / cancel / undo flows bidirectionally.

Typical sites go live in 4-5 weeks: week 1 discovery + import, week 2 configuration + training, weeks 3-4 AIoT pairing and soft-launch, week 5 cutover. Smaller sites finish faster.

Brand-agnostic. Generic IP cameras (HTTP snapshot & event ingest), MIFARE-compatible RFID smart-card readers, face-recognition cameras (SmartFACE), ANPR/LPR cameras (SmartVE), smart intercoms (SmartINTE), lift access controllers (SuperPASS-Lift), parking-lock controllers (parking_locks_config.php) + wheel-clamp module, delivery lockers and smart mirrors. Device-protocol traffic is encrypted with the SM4 32-round block cipher (sm4.php).

Both. Small (< 100 units) tenants run on a slim configuration; large tenants (1,000+ units) run multi-site with sub-accounts. Pricing scales with size.

Yes. Xendit is integrated with three confirmed payment methods: QR pay, credit/debit card, and Direct Debit. Webhook reconciliation, refund and failure handling are built-in.

The document drops into a "rejected" queue with the LHDN error code and explanation. Finance can fix the data and resubmit in one click; the original draft remains for audit.

Yes. Logo, footer, payment instructions, multi-language remarks and per-customer remarks are configurable. Reports can be exported as PDF, Excel or CSV.

Residents/staff pre-register a visitor in the app; the visitor receives a QR code via email; security scans the QR at the gate; entry is logged with photo, plate and host reference.

Yes — a public REST API surface documented at /api_doc.php covers visitor flow, EV charging deposit + session, sub-account, announcements, deposits, invoices and payments. Bearer-token auth and webhooks for payment events. Sandbox available.

Production data is hosted in Singapore with TLS in transit. Daily off-site backups with point-in-time restore for the last 30 days.

Yes — deployed across Malaysia, Singapore, Indonesia, Thailand, Vietnam and the Philippines. Tax flows are configurable per country; MyInvois is the Malaysia-specific module.

Best-effort availability monitored 24/7. Maintenance windows are scheduled out of business hours and announced via email (PHPMailer) to all tenant administrators.

Onboarding includes 2-3 live training sessions for staff plus printed quick-start guides. Resident rollout uses an email + QR-code campaign with download links to the PWA mobile apps; we monitor adoption with you for the first month.

Yes. We have prebuilt importers for the common Malaysian and SEA property/club platforms — customers, units, contracts, opening balances, member tiers and access cards. Where a vendor blocks export, we work with you to extract via reports or screen-scrape, then re-import. Most migrations finish inside week 1, with a parallel-run period to confirm reconciliations match the old system before cutover.

Audit log is captured via in_syslog() / debugv_access — every meaningful change is recorded with user, timestamp and context for review.

Configurable password policy and login rate-limiting at the application level.

Hardware (cameras, readers, locks), site cabling, payment-gateway processing fees, and bespoke development of features that don't exist in the platform. Everything else — modules, PWA mobile apps, MyInvois, email delivery via PHPMailer, support — is included.

You own your data. Full data export to CSV/JSON on request. There is no exit fee.

The dashboard visualises the metrics AUTOSERVA already computes for the date range you pick: devices online, access events, overdue and collected ringgit, energy kWh, open incidents, the collection rate with aging buckets, and access events by hour. Switch between Today, This Month, Last Month and This Year and the whole console re-reads.

Both. Beyond running operations it produces tabular analytics — arrears aging, facility utilisation, vacancy/days-unoccupied, access and visitor trends, cashflow forecast, revenue summary and GL statement states — all computed with SQL aggregation over your ledger. There is no machine-learning prediction; the value is disciplined, auditable reporting, visualised on the dashboard and exportable.

Yes. Every report module supports PDF, Excel and CSV export, including invoices, statements, the aging report, facility utilisation, cashflow forecast and the dashboard figures — suitable for committee and board packs.

The arrears aging report buckets balances into current, 1-30, 31-60 and 60+ days. AUTOSERVA then runs an automated dunning cascade: an overdue reminder 7 days before the due date, the first letter on day 1 overdue, the second on day 31 and the third on day 61. You focus calls on the 60+ bucket while the system handles the rest.

Production data is hosted in Singapore with TLS in transit, daily off-site backups and point-in-time restore for the last 30 days.

The access log records every granted and denied event with method and timestamp. Plotting access by hour exposes the real commute peaks, so you roster guards and concierge to those windows instead of a flat shift, and escalate repeat overstays and denials to the incident workflow.

The figures refresh from your operational data and the IoT uptime cron. Device status, access counts and collections reflect the latest posted data for the selected range; the dashboard is a visualisation of the same numbers your reports produce, not a separate data source.

No AI or neural prediction. The cashflow forecast is SQL aggregation that projects collections by day, month and year and by revenue type from your existing ledger, read alongside the revenue summary and GL statement states. It is transparent and auditable — every figure traces back to a source transaction.

Yes — the Module Tour on this page renders faithful mock screens of the admin Things-to-Do dashboard, the invoice table with MyInvois validation, the live IoT device grid and the realtime access log, using the product's real columns, statuses and colours.

Yes. The building schematic renders your device registry as a floor-by-floor stacking plan, with a status LED on every endpoint — green for online and synced, amber for a warning or stale sync, red for offline. Click any marker to read its serial number, sub-type (SuperPASS-Door, UltraPASS-Face, SuperPASS-Lift, UltraPASS-Vehicle or IP camera), sync date and last event. Device-protocol traffic is SM4-encrypted.

Yes. The streaming access-event console replays the granted/denied log line by line — card swipes, face matches, plate reads, lift calls, relay actions and flagged strangers — with filter chips for All, Granted, Denied and Device actions. The access decision itself runs on the connected device; AUTOSERVA records, filters and audits it, and the log exports to PDF or Excel.

Yes. The metering, power-monitor and solar PV modules record instantaneous load in kilowatts, energy used per day in kilowatt-hours and PV generation. The energy gauge cluster visualises those metered figures with a 24-hour load profile. These are direct meter readings — there is no forecasting — and they export as tabular reports.

It combines four panels on one board: a device mini-map of every endpoint colour-coded online, warning or offline; a live alarms list from the incident workflow; an energy strip with instantaneous load, today's kWh and PV generation; and access-throughput counters for granted, denied, plate-read and face-match events. Every figure is one AUTOSERVA already computes — device status from the IoT uptime cron, alarms from the incident workflow, energy from the meter modules and counts from the access log — and it all exports to PDF or Excel.

Ask VYROX AI is an operational-intelligence assistant: you pick a preset operator question and it returns the report AUTOSERVA already produces — the 60-plus aging bucket, which devices are offline, energy spent this month, or the MyInvois batch ready to validate. It surfaces and automates real SQL aggregations and queued jobs. It does not forecast the future and it does not invent accuracy or confidence scores; every answer traces back to a source query.

It is a cron-driven rules engine, not AI. Auto-billing issues management-account, sinking-fund, maintenance-fee and rental invoices on the 1st; the dunning cascade fires an overdue reminder 7 days before due and letters at day 1, 31 and 61; member auto-renewal raises a renewal invoice about 30 days before expiry; a device-heartbeat job pings every IoT endpoint each minute; and amenity auto-stop plus expired-booking cleanup run continuously. Every rule is deterministic, scheduled and written to the audit log.

AUTOSERVA sits at the centre of a hub-and-spoke ecosystem: MyInvois/LHDN for UBL 2.1 e-invoice validation, Xendit for QR, card and Direct Debit payments, the AutoCount Connector for bidirectional ERP sync, brand-agnostic IoT hardware (RFID, face, plate, intercom, lift, parking-lock), HERE Maps for courier and staff routing, and a public REST API at /api_doc.php with Bearer-token auth and webhooks.

The Security Monitor is a live access-throughput board: a chart of access events bucketed by hour across the day (so the morning and evening commute peaks are visible), a streaming list of the latest granted, denied and flagged events with location and device serial, and KPI summary cards for events today, granted, denied and devices online. Every figure is read from the access log and the IoT uptime cron; the chart is a visualisation of those metrics, not a forecast, and it exports as a tabular report.

The GL statement carries the full posting lifecycle: processing, posted, unposted, deposits, advances, refund-request, refund-approved and refunded. You filter the statement by any of these states, and a running balance recomputes down the visible rows. Cash Book is kept separate from the GL. Every line traces back to a source transaction and the whole statement exports to PDF or Excel.

For a SuperPASS-Door controller you enter the controller name (the label shown in the Access-devices list), the number of doors supported (the relay count), the controller serial number (printed on the device, used for SM4-encrypted pairing) and the installed property. The dialog opens over a blurred backdrop; once the controller checks in, its heartbeat appears in the device registry.

Submission resolves to one of three states. Submitted means the UBL 2.1 document is in progress with LHDN and awaiting validation. Invalid means LHDN rejected it with an error code (for example a tax-type mismatch or a missing buyer TIN, which falls back to the walk-in TIN EI00000000010); the document drops into a retry queue for a one-click fix and resubmit. Valid means it cleared, carrying the green LHDN Validated e-Invoice UUID stamp with the UUID, buyer TIN, MSIC code and validation timestamp.

Yes. The financial report module produces revenue by service line — maintenance fee, sinking fund, carpark rental, facility bookings, access cards, EV charging and late-payment interest — with gross, discount, SST tax, paid and outstanding columns and a totals row, alongside arrears aging buckets (current, 1-30, 31-60 and 60+ days). It is SQL aggregation over your ledger with no machine-learning prediction, and it exports to PDF or Excel for the committee or board pack.

Six stages over roughly 4–5 weeks: Discovery (scope and hardware list), Data import (CSV/Excel templates and bulk owner import), Configuration (GL codes, billing, tax, RBAC), AIoT pairing (commission devices over the SM4-encrypted protocol, verify heartbeat), Soft-launch (parallel run against the legacy system to reconcile) and Cutover (AUTOSERVA becomes the system of record, with a monitored resident/staff rollout).

Production data is hosted in Singapore with TLS in transit. Access is governed by a 34-plus-bit role-based privilege set, and every meaningful change is captured in an audit log via in_syslog() and the debugv_access table. Device-protocol traffic uses the SM4 32-round block cipher; SmartFACE stores embeddings rather than raw photos with per-resident PDPA consent; MyInvois documents validate against LHDN before send; and daily off-site backups give point-in-time restore for the last 30 days.

Yes. AUTOSERVA runs an accept/reject approvals workflow for posted payment batches, booking change requests, lease move-in handovers, visitor pre-registrations and refund requests. Each decision updates the relevant ledger or status and is written to the audit log for review.

Yes. The asset and fleet monitoring grid lists every monitored endpoint — door readers, face cameras, lift controllers, vehicle gates, power meters, IP cameras and the solar PV inverter — with a status LED, a seven-day uptime sparkline, uptime percentage and last-sync time. Filter by health bucket (online, warning, offline) to triage what needs attention first. Status is read from the IoT uptime cron (check_iot_up.php) and exports to PDF or Excel.

Yes. The PLC and relay control panel lets an authorised operator toggle lighting zones, the main gate, the loading-bay shutter, the sump pump and façade signage. Commands ride the SM4-encrypted device protocol, are governed by role-based privileges, and every toggle — manual or auto-rule — is written to the audit log with operator, timestamp and reason. Safety-critical interlocks such as the fire-trip circuit are locked out of the panel.

The incident command timeline replays the full chain: detection by the device-heartbeat job, escalation and paging of the on-call engineer via PHPMailer, operator acknowledgement that opens an incident (state New to Processing), the relay or field response, recovery when the device reports healthy, and close (Processing to Completed) with a resolution note. Time-to-ack and time-to-resolve are tracked, and the whole chain is retained in the audit log for the post-incident review.

It is a live multi-channel tap, not a prediction. Power readings, access events, climate readings and device heartbeats arrive interleaved over the MQTT broker and you can filter to a single channel. A sparkline shows the building load profile in kilowatts. Every figure is a direct meter or device reading that AUTOSERVA already records — there is no forecasting and no invented confidence scores — and it exports as tabular reports.

It is the clean board the night officer leaves for the morning crew: a system-status grid (API, database, MQTT broker, cron queue, MyInvois link and last backup), a device-heartbeat summary of online, warning and offline endpoints, and a live audit feed of recent operator actions captured by in_syslog() and the debugv_access table — relay toggles, posted payments, closed incidents, issued visitor passes and validated MyInvois batches, each with operator and timestamp.

The operator console is the everyday staff workspace. A left module sidebar groups Operation Insights, Security Monitor, Customer Accounts, Cash Book, General Ledger, Reports and Suppliers (plus the admin items), each with a red count badge that hides when zero. A title bar carries the page name, a centred date-range pill with presets — Today, Yesterday, This Month, Last Month, This Year, Last Year and Custom Time Frame — and a New-device button. The centre card is the registered Access-devices list (No., Created, Serial No., Label and row actions) and the right panel is the management Things-to-Do queue. Lists export to PDF and Excel.

The list shows No., Created (in d-MMM-YYYY form), Serial No., Label and a row-actions affordance. The registered device sub-types are SuperPASS-Door door controllers, UltraPASS-Face face-recognition readers, SuperPASS-Lift lift controllers and SecurityGPT-Stranger stranger-detection units. A footer toolbar offers PDF, Excel, Print and Settings export buttons, a Showing X to Y of N devices counter and Previous/Next pagers.

The queue surfaces items awaiting management action: card-access applications pending approval, face-recognition access applications pending approval, vehicle-plate-recognition access applications pending approval, visitors who have overstayed, and posted payments pending management verification. Each row carries a View action and rows auto-hide when their count is zero, so the operator only sees live work.

It is a single live operations screen with three auto-refreshing log boards side by side: Intrusion Detection Logs (stranger and loitering flags), Physical Access Logs (card swipes, face matches and lift calls marked Granted or Denied) and Digital Access Logs (QR-key scans). Each board carries its own running counter that climbs as events arrive, and a Search History action opens the access-log archive with date-range presets. The access-status legend defines Pending Activation, Expired, Invalid QR Code, Wrong Entrance and No Record. Every entry is a recorded fact, not a score or prediction.

The Incident Reports list shows No., Submitted, Property, Reporter, Category, Title and Outstanding (Day), filterable by the workflow tabs Pending Acknowledgement, Processing and Resolved (states New, Processing and Completed). Open any incident to read its time-stamped detail timeline from submission through acknowledgement, dispatch, response, recovery and close. The list exports to PDF and Excel.

Yes. The lighting record is a custom log table with the columns ID, Timestamp, Relays, By type and By user, where each row shows a strip of relay dots (lit for on, dark for off) beside the channel name and whether an automation rule or an operator toggled it. A relay control panel lets an authorised operator flip lighting zones, the main gate and the loading-bay shutter; each toggle rides the SM4-encrypted device protocol, is role-gated, and is written to a timestamped command log. Safety interlocks such as the fire-trip circuit are locked out.

Yes. The Cash Book renders monthly receipts as a stacked bar chart — cash receipts stacked against online payment-gateway collections — alongside a report table that breaks the same figures out by month with cash, online-gateway and total columns. On this page the chart is drawn as inline SVG so it stays readable with JavaScript off. Every figure is a SQL aggregation over recorded receipts, exportable to PDF and Excel; nothing is forecast.

Yes. The parking bay registry lists every bay with Type, Lot Number, Block, Level, Zone, Unit and User, paired with an occupancy board colour-coded for Available, Occupied, Reserved and EV-charging. The delivery-locker wall shows each door keyed by Door No., coloured amber for a parcel pending pick-up and green once collected, with a records list carrying Door No., To Unit, Customer Name, Customer Mobile No., Rider Mobile No. and Status. Both export to PDF and Excel.

Both live in one device registry. The IP-cameras screen carries the real columns No., Created, Name, IP Address and Type, and the same page is where UltraPASS-Vehicle plate-recognition cameras are registered — so a row's Type tells you whether it is a plain IP-Camera or an ANPR unit. A monitor wall shows each camera tile with its label, IP and type. The image decode and plate read run on the camera; AUTOSERVA names, registers and audits the endpoints, and the list exports to PDF and Excel.

EV charging is billed by the minute. The charging-session board carries the real columns — Customer, Parking Lot, Start Time, End Time, Rate (rendered as an amount per minute), Billing Amount and Status. While a car is plugged in, the End Time cell reads Still charging with a live elapsed timer and the Billing Amount accrues at rate divided by sixty per second; a Stop action ends the session. Completed sessions show the end time, duration and final amount, and can be Completed or Deleted. A separate charger-hardware registry links each physical charger to its EV lot by Device ID, Server and Port.

Each access method is a settings catalog: Card Access Type, Face Recognition Type, Vehicle Plate Recognition Type and Integrated Smart Access Type, all sharing one shape — the type label, Description, Deposit, Charge, Frequency and Status. The add/edit form sets the deposit and charge, links the type to parking, and grants the access-control surfaces: SuperPASS-Door Access Control, SuperPASS-Lift Access Control (which can be scoped to the floor where the user's property is located) and UltraPASS-Vehicle Access Control for plate-based vehicle entry. UltraPASS-Vehicle is a real product label that coexists with the Vehicle Plate Recognition feature naming.

The Smart Mirror is a self-running lobby wallboard. It shows a live clock and weather header, real-time occupancy counters for the GYM and Game Room, and panels for Announcement, Notification, a To Do List with a count badge, a system Status badge and a Water Usage strip of recent daily consumption. Every panel reads the same operational data the staff console computes; on this page the clock ticks client-side and the figures are illustrative.