Skip to content

Frequently asked questions

The questions licensing departments, enforcement units and auditors ask about applications, compounds and document intake, before a proposal.

Licensing and enforcement

Can applicants see where their application has reached?

Yes. Applicants can see where their application has reached, from submission through assessment to approval. That removes a large share of the calls a licensing counter fields every day.

Where are inspection records kept?

Against the licence, rather than in a separate file. The conditions set at approval, each renewal and each inspection record sit with the licence they belong to, so a licence renewed at the counter is renewed against the same record.

How are compounds and summonses issued and settled?

They are issued in the field and at the counter, and in the field officers raise them on a handheld rather than writing them in a book, with the evidence attached at the point of issue. The offence record, the evidence and the payment against it are held in one place, and supervisors see what was issued and where on the day. Settlement reconciles back to the authority's revenue records rather than arriving as a separate return.

Document intake and audit

What does the document intake do?

Applied AI reads application forms, identity documents and supporting attachments once, validates them and routes them. Only the exceptions reach an officer, so an intake backlog no longer depends on how fast a person can key it in. Every extraction is recorded with the input it saw.

How can an auditor check what the system decided?

Every extraction is recorded with the input it saw, so a supervisor or auditor can check the decision rather than trust it. Approvals and changes to a record are logged with who made them and what they saw. That evidence is produced as the system runs, rather than assembled from logs when someone asks.

Deployment and the agreement

Where does it run, and can our other systems talk to it?

In the authority's own data centre or cloud account, whichever its residency and outsourcing position requires. idataraya installs it and keeps it current, and the authority's team holds the keys, the backups and the data. Revenue systems, accounting packages and identity services stay where they are, and idataraya integrates asasii licensing with them. It works beside asasii ledger for collections, asasii pos at the counter and asasii procure for the vendor portal.

How does a rollout start?

From the specification the authority issues, including the parts about documentation, handover and support. Anything in it that will not work in practice is raised during clarification, rather than found at user acceptance testing. asasii licensing then goes live in one office or one district before the authority commits a department.

What does the yearly agreement cover?

Releases, patches, the customisations made for you, monitoring, severity-based response and restoration targets, and the changes needed as policy and process move. Hosting stays with you. It covers the years after go-live rather than ending with a warranty, and idataraya is staffed to meet the maintenance obligations the tender document sets.

Still have a question?

Send it with the licences you issue and the number of applications a year, and an engineer replies within one working day.