How asasii licensing works
One system in the authority's own environment, from the application form to the compound issued in the field.

A day at the authority on asasii licensing
From the morning's applications to what was issued in the field by the end of the day.
- 08:30
The morning's applications
Application forms, identity documents and attachments are read once, validated and routed. Only the exceptions wait for an officer.
- 09:30
An application is approved
A licensing officer assesses it and approves it with its conditions. The approval is logged with who made it and what they saw.
- 10:30
An applicant checks
The applicant sees where the application has reached, without a call to the licensing counter.
- 11:15
A compound in the field
An enforcement officer issues it from a handheld rather than a book, with the evidence attached at the point of issue.
- 12:30
A renewal at the counter
The licence is renewed against the same record that holds its conditions and its inspections.
- 14:30
An inspection
The inspection record is kept against the licence, not in a separate file.
- 15:30
A compound is paid
The payment is held with the offence record and the evidence, and settlement reconciles back to the revenue records without a separate return.
- 17:00
What was issued, and where
Supervisors see the day's compounds and summonses and where they were issued, on the day rather than at the end of the month.
Who it's for
Four groups of people, working from the same licence and offence records.

Applicants and licence holders
Where the application has reached, without a call.

Licensing officers
The exceptions and the decisions, not the keying in.

Enforcement officers
Compounds from a handheld, with the evidence attached.

Management and audit
What was issued today, and evidence produced as it runs.

Where it runs
In the authority's own data centre or cloud account, whichever its residency and outsourcing position requires. The deployment target is a configuration of the same product, so keeping the data inside the authority does not cost it features. idataraya installs it, hardens it and keeps it current, and the authority's team holds the keys, the backups and the data.
It works beside asasii ledger for collections, asasii pos at the counter and kiosk, and asasii procure for the vendor portal. Revenue systems, accounting packages and identity services already in place stay where they are, and idataraya integrates asasii licensing with them.
Our servicesSee it on your own licences
Send us the licences and permits you issue, how applications and compounds are handled today, and the tender document if there is one. An engineer replies with a pilot plan, an integration plan and a proposal.