AJAEXCAFM

Report it once. Follow it to fixed.

AJAEX CAFM puts every site's faults, planned work and paperwork on one record. Each request starts from the place it happened, and whoever raised it can follow it. Hosted in the UK.

app.ajaexplatform.com/service-desk/manage
AJAEX service desk, Manage Requests: logged service requests with readable ID, title, created and updated times, service category and class, priority, and location

Why teams trust AJAEX

IBM Silver Business Partner
TRIRIGA expertise in support, configuration, integrations and upgrades.
UK-hosted
Hosted on AWS in London (eu-west-2).
Cyber Essentials certified
AJAEX LTD, October 2026.
Request history, built and being tested
Updates and notes kept on each request.
IBM Silver Partner

The problems we solve.

  1. Ten clients. One system. Each sees only theirs.

    Run every contract with its own service agreement, priorities and response and fix times. Each job is measured against the agreement it runs under.

  2. Report it once. Follow it to fixed.

    Every site raises faults in one place, starting from the site, building, floor or space. Whoever raised it can follow it on self service instead of ringing.

  3. The paperwork is the defence. Know where every site stands.

    Each kind of place and equipment carries the checks it must meet and the documents that meet them. AI reads uploads and a person checks them before they count.

  4. Your asset register shouldn’t be a spreadsheet on someone’s desktop.

    Site, building, floor, space, asset: one list everyone works from. Requests, planned work and their history hang off the same record.

  5. We bought a CAFM. We use the helpdesk.

    Shape the catalogue, fields, workflow and service levels yourselves, starting with the jobs you already do. Change them again when the estate changes.

  6. Priced on your sites, not your headcount.

    Add engineers and requesters without adding licence lines. You get a tailored quote for the sites and modules you use.

    Export your data. No lock-in.

A clear view of property, assets and work.

Every request, task and document hangs off the estate record. Pick any asset and you can see where it is, what is planned, what is open, the agreement it runs under and the evidence behind it.

Example recordProperty hierarchy
  1. SiteNorthgate Campus
  2. BuildingBuilding A
  3. FloorFloor 3
  4. Space3.14 East corridor
  5. AssetFire door, FD30FD-A-3.14
Everything linked to this asset
APlannedDue 14 Nov

Quarterly fire door check

Job plan
Fire door inspection
Last done
14 Aug 2026
BRequestIn progress

Door not closing fully

Raised
Service desk
Assigned
Hard FM team
CAgreementWithin SLA

Hard FM, Building A

Response
4 hours
Fix
2 working days
DEvidenceChecked

Fire door inspection report

Reviewed by
Compliance lead
Valid to
Aug 2027
Illustrative data. Names, dates and service levels are set by your organisation.
AJAEX service desk location step: search by site, building, floor or space, find nearby, or scan a QR code
In the product. A request starts from a place. People search the estate by site, building, floor or space, or scan a QR code.

AOne maintenance plan

Planned and reactive work share the same assets and history. Job plans stay linked to the estate record, not a separate spreadsheet.

BWork with its context

Requests and work tasks carry their site, space and asset, so the right team knows where to go and what it is working on.

CThe agreement on the job

Priorities, response times and fix times sit on the work itself, measured against the agreement it runs under.

DEvidence on the record

Requirements for each place and asset sit beside their documents. AI reads uploads, and a person checks them before they count.

Built for teams who run many sites.

FM contractors

Every client contract on one system, each with its own service agreement, priorities and response and fix times.

Multi-site estates

Every site reports faults in one place, and the work is followed on one queue.

Public-sector estates

See what each site has to answer for, and the documents that answer it.

AI with oversight

Help where it helps. Stop where it shouldn't.

Not a chatbot bolted onto CAFM. Useful on the day-to-day work, always under rules your operations team own.

  1. You set the rules

    Priorities, approvals and what must be recorded: your team keeps control.

  2. AI works inside those rules

    It helps with triage, documents and checks. It does not freestyle across your estate.

  3. People stay in the loop

    Anything unsure or high-risk goes to review before live records change.

Configure AJAEX CAFM.

AJAEX CAFM brings shared records, configurable workflows, access controls and change history (in testing) together. Your team can shape catalogues and rules around the operation, with a history of each change.

  1. Shape the catalogues and fields you need.

  2. Set the workflow and the SLAs.

  3. Set the rules your team will work to.

  4. Change again when the estate changes, with a clear history.

Also from AJAEX

Also from AJAEX

AJAEX Field

An app for your engineers, in build, with a demo ready to show. We build the connector to your CAFM for you.

ajaex.com/field
AJAEX Field work list, showing sample data.

AJAEX Pulse

An AI workspace for your team, trialled internally. Ask about early access.

ajaex.com/pulse

Next step

Book a short demo. We send a tailored quote.

  • Priced on sites and modules, not per user.
  • UK-hosted on AWS London (eu-west-2).
  • Phased rollout: start with the area that hurts most.

AJAEX LTD, Unit 15 Attenburys Lane, Timperley, Altrincham, England, WA14 5QE. IBM Silver Business Partner.