Antz · Operations · System mapv1 · Proposal

How Antz operations fit together

Seven modules run on one set of sites, warehouses, people and vendors. Something breaks or is needed, the work is done, parts come from a warehouse or are bought, and the bill is paid. Every decision goes to one approvals inbox, and every job to one task list.

Example used on this page

Cold Room 2 chiller stops cooling

Reported as an incident · ticket to Maintenance · work order on the chiller · thermostat from the Central store · a relay is bought · received, billed, paid.

1 · Incidents Breakdowns, and audits that find problems (GRC) 2 · Helpdesk A ticket asks a department to fix it 3 · Work orders The job is done; planned maintenance repeats 4 · Warehouses Stock is kept, issued and moved between stores 5 · Procurement Request, quotes, PO, delivery, goods received 6 · Assets Each thing at a site: tagged, held, maintained 7 · Bill desk Invoice matched to PO and GRN, then paid anyone · auditor department in-charge technician · vendor store manager procurement team asset owner bill desk · finance Raise Approved Parts Low stock Received Fix needs a work order directly Needs something bought Repairs and services Bought: registered and tagged Bill Breaks down, or fails a check End of life, or contract due: replace or renew EVERY MODULE ABOVE USES Approvals · one inbox Cost, spend, PO, payment, write-off, disposal. Limits: department → zoo → management. Tasks · My work Every time someone must act, it is a to-do that opens the work and closes by itself. Built on Sites and places Warehouses, racks People and cost centres Catalogue Vendors Rules (GRC)

Each module: who acts, what happens, and what Antz does by itself

ModuleWhoWhat happensApprovalAntz does it automatically
1 · IncidentsGRC · incidents and auditsAnyone · auditorA breakdown is reported as an incident. Planned audits check places, assets and stores. Problems found need a fix.Closing a serious incidentSends audit to-dos on schedule · turns a failed answer into a finding · escalates critical ones.
2 · HelpdeskTicketsDepartment in-chargeThe department costs the fix and gives a date, then starts it once approved.The cost, by limitRoutes to the right approver by the amount · reopens within 48 hours.
3 · Work ordersWork & maintenanceTechnician · vendorDoes the job on an asset or place, records parts and time. Planned maintenance runs on a schedule.Go-ahead, permitCreates planned visits · flags missed ones · puts the cost on the asset.
4 · WarehousesInventoryStore managerKeeps stock by store, rack and batch. Issues to people and jobs, moves stock between stores.Controlled items, write-offsEvery movement updates stock · warns at low stock · earliest expiry first.
5 · ProcurementBuyingProcurement teamTurns a request into quotes, a PO, a delivery and goods received.Spend, then PO by FinanceRoutes the spend by cost centre limit · keeps vendor scores.
6 · AssetsAsset registerAsset ownerEvery machine, vehicle and built place: where it is, who holds it, its cover and its history.Decommission, disposalWarns before AMC and warranty expire · adds up the cost of each asset.
7 · Bill deskBill desk and paymentBill desk · FinanceMatches the vendor invoice to the PO and goods received, then pays.PaymentFlags a bill that does not match · tracks what is waiting to be paid.
ApprovalsSharedApproversOne inbox for every decision across the modules.—Picks the approver by amount and type · escalates when late.
TasksSharedEveryoneOne My work list for everything someone has to do.—Creates the to-do, links it to the work, closes it when done.
Antz · Operations architecture · 18 Nov 2026Example names and data