Property and leases
Keep the portfolio, its leases and the work it needs in view.
- Property tenure, floor area and UPRN
- Lease records, renewals and key dates
- Portfolio reporting and estate CSV imports
From estate records to service delivery.
Know which place or asset needs attention, who owns the work and which agreement applies. AJAEX CAFM connects the records your teams use to plan, deliver and review the service.
Start with the estate. Keep the work connected.
Know which property, place or asset the work belongs to. Bring its requests, job plans and tasks into view with the service agreement, responsibility and supporting documents.
Know the estate
Keep property, lease, site and asset records together, so the work has a clear location and context.
Plan and deliver the work
Bring reactive requests and planned maintenance into work tasks. Your team generates due work from schedules and assigns the people doing the job.
Keep the work history
Track progress, notes and supporting documents on the work record, with the service agreement and site context attached.
The tools to keep your estate working.
Property, maintenance and service delivery share the records and controls that keep the estate's work connected.
Service desk
Give the desk the location, service and customer context it needs to handle each request.
- Find requests and keep context in view
- Service shortlist for the agent to confirm
- Priority and routing on the record
Guided request intake
Start with who or where; structure the request before it enters the queue.
- Person- or place-first logging
- Structured read-back before submit
- Caller and location context kept with the request
Assets and PPM
Estate, asset, schedule, and job history connected.
- Site-to-asset hierarchy
- Planned maintenance schedules
- Due work generated when the desk asks
Service agreements
Each customer's priorities, response times, and fix times, applied to the work.
- Priority tables for each agreement
- Response and fix clocks on each task
- Due soon and breached shown
Documents and evidence
Documents become structured records instead of files people have to chase.
- Documents on the estate record
- Compliance position by site and portfolio
- AI reading, checked by a person
Workflow and rules
Business logic stays visible, configurable, and auditable.
- Status-driven workflow
- Approval and segregation rules
- Rules you configure, with a history
Data and integrations
Connect the systems around your estate, and take reports out.
- Public API
- CSV and Excel export from reports
Dispatch
Choose who does the work, plan the visit window, and move tasks between servicing companies.
- An assignee and My tasks for each engineer
- A planned window for each visit
- Load view by work group and person
See who has the work.
Assign work tasks, set planned visit windows and review the load by work group or person. Open the task lists behind the counts to see the work and its service-level risk.
Good service starts with context.
Guided request logging can start with who or where (person, place, then problem), with a structured read-back before the request enters the queue. The film is actual product UI with demonstration data.
Bring the work into focus.
Find a request in the queue and keep context beside it, then open the full record with status in view. Product screens use demonstration data. The AI step is illustrative.
AI suggests. Your team decides.
Practical help at the service desk: AI can suggest options while human review stays in the flow. Product screens use demonstration data. The AI step is illustrative.
Governed AI
AI with oversight, not a chatbot.
Users are not left chatting with a model. AJAEX loads the right record, context, rules, and response schema for the task. The AI checks the work, returns structured output, and the workflow decides whether it can proceed or needs human review.
Shortlist a request
The desk uses site, contract, location and available services to shortlist options. The agent confirms: nothing auto-applies without a person.
Process a certificate
Document reading extracts key fields from an uploaded document. A person checks what was read before it counts.
Keep AI use bounded
Your administrator sets how many AI calls each visit to Log a request may make. Once it is spent, the desk carries on without asking again.
AI transaction record
No memory. No broad API access. The record shows what was sent, what came back, and what happened next.
- 01Scope the record, user, site, and allowed capabilities.
- 02Load the approved rules for this exact action.
- 03Send bounded context to the selected AI capability.
- 04Store input, output, model, route, and confidence.
- 05Write back only through review, workflow, or approval controls.
Human oversight stays in the loop.
Low-confidence, incomplete, or risky outcomes can be stopped for review before they affect live records.
Connect the work across your operation.
Property, assets, maintenance and service delivery share their records and history. Explore the modules behind each part of the operation and the standard each one exists to complete.
The controls are part of the product.
Audit, access, residency, and AI transparency are not separate consultancy workstreams.
Change history (in testing)
Every record, comment, document, status change, AI transaction, and correction has a traceable history.
AI transparency
Inputs, model, route, output, confidence, and review outcome are visible on the transaction record.
Data residency
Hosted on AWS in London (eu-west-2).
Controlled access
Users only see the records, sites, services, and capabilities available to their role and context.
See the operating model on your scenarios.
Bring one messy workflow: a service request, a planned maintenance regime, or a compliance pack. We will show how it becomes rules, transactions, review, and evidence.