# Antz Operations — whole-system architecture

> One system for everything a zoo owns, keeps, fixes, buys, checks and proves.
> Inventory · Warehouses · Sites · Assets · Helpdesk · Maintenance · Work orders · Procurement · Bill desk and payments · Audits (GRC) · Approvals · Tasks.
> Vision document, 18 Nov 2026. Names and numbers in examples are sample data.

---

## 0. The idea in one paragraph

Every module sits on **one shared foundation** (places, people, items, vendors, rules) and uses **the same shared engines** (approvals, tasks, schedules, checks, ledger, history, notifications). The modules themselves are thin: each one is a set of **records** with a life of their own (a ticket, a work order, a purchase request, a check). Records **link to each other** into one thread, so from any record you can walk to what caused it and what it caused. Every time a person must act, it becomes **one to-do in My work**; every time a person must agree, it is **one approval in the Approvals inbox**.

```
                    ┌──────────────────────────────────────────────┐
   PEOPLE SEE       │   My work (to-dos)   ·   Approvals inbox      │
                    └──────────────────────────────────────────────┘
                    ┌───────┬────────┬───────┬────────┬──────┬──────┐
   MODULES          │Help-  │Work &  │Assets │Inven-  │Procu-│GRC   │
   (records)        │desk   │Mainten.│       │tory    │rement│      │
                    │       │        │       │        │+ Bill│      │
                    │       │        │       │        │ desk │      │
                    └───────┴────────┴───────┴────────┴──────┴──────┘
                    ┌──────────────────────────────────────────────┐
   SHARED ENGINES   │ Approvals · Tasks · Schedules · Checks/forms │
                    │ Stock ledger · Links · History · Notify ·    │
                    │ Escalation · Cost roll-up                    │
                    └──────────────────────────────────────────────┘
                    ┌──────────────────────────────────────────────┐
   FOUNDATION       │ Places · People & cost centres · Catalogue · │
                    │ Vendors · Rules library · Animals (Antz)     │
                    └──────────────────────────────────────────────┘
```

---

## 1. Foundation — the shared masters

Five trees that every module reads. Nothing in a module re-creates them.

### 1.1 Places — where everything is

```
Group (e.g. Vantara)
└── Zoo / Organisation
    └── Site                                   e.g. Main campus, Safari park
        └── Zone / Section                     e.g. Big Cats Section, Back of house
            └── Area                           typed (see below)
                └── Spot (optional)            e.g. Night house 2, Pump bay
```

**Area types**: enclosure · building · room · kitchen · clinic / hospital · gate · yard · road · **store (warehouse)**.

A **store** is just an area of type store, with its own inside tree:

```
Store (warehouse)          kind: central | local (department) | pharmacy | kitchen | scrap yard
├── owner department       who moves stock in it
├── parent store           a local store is fed by a central store
└── Rack
    └── Shelf / Bin        where a product variant sits
```

Rules
- One place tree for the whole platform (Antz already has site → section → enclosure; operations adds buildings, rooms and stores to the same tree).
- Every record that happens somewhere carries **one place** (picked with the Drill down).
- Stations (scan kiosk, gate station, packing kiosk) are **bound to a place**.
- A place can have an **owner** (person or department) who is the default for approvals and checks there.

### 1.2 People, departments, cost centres — who

```
Organisation
├── Department                       e.g. Fabrication, Maintenance, Pharmacy, Kitchen, Stores, Finance
│   ├── In-charge
│   └── Team members
├── Cost centre                      the budget a spend is charged to; a department can spend against many
│   ├── Owner (approves up to the cost centre limit)
│   ├── Limits (cost centre limit, overrides zoo defaults)
│   └── Members (who may raise against it)
├── Management group                 approves above the zoo limit
├── Finance team                     approves POs and payments
└── Procurement team                 sources, orders, receives
```

- **Roles are bundles of permissions**, never fixed labels in the logic (`can:transfer.approve`, `can:stock.issue`).
- Permissions are granted **per zoo, per site, per store** (a store manager can move stock only in their stores).
- A person can hold several roles (George is Fabrication in-charge in Helpdesk and a raiser in Procurement).
- **Leave and delegation** live here: an approver on leave hands their queue to a named delegate.

### 1.3 Catalogue — what things are

```
Domain                      Pharmacy · Maintenance · Housekeeping · Safety · Kitchen · IT · Vehicles
└── Category                (with an attribute set, tracking mode, batch/expiry on or off)
    └── Product             the template: name, generic, manufacturer, UOM, flags
        └── Variant (SKU)   e.g. Gloves M, Saline 500 ml, Steel bar 12 mm
            └── Package     purchase unit × multiplier to stock unit (Box of 100 = 100 each)
```

Each category has a **tracking mode**, which decides how its items live in the system:

| Tracking mode | Each unit is… | Lives in | Example |
|---|---|---|---|
| **Consumable** | a quantity, optionally by batch and expiry | Stock (store × variant × batch) | medicines, gloves, paint, feed |
| **Spare part** | a quantity, but consumed onto an asset's work | Stock, then the asset's cost | pump seals, filters, bulbs |
| **Asset** | an individual thing with its own ID and tag | Asset register | chiller, vehicle, laptop, tranquilliser gun |
| **Service** | nothing held | Only on requests, POs, contracts | AMC, repair labour, pest control |

This one switch is what joins Inventory, Assets and Procurement: **everything is bought from the same catalogue**, and the tracking mode decides where it lands on receipt.

Shared masters under the catalogue: UOM, product forms, generic names, salts, drug class, manufacturers, storage conditions, attributes, attribute sets, asset categories, condition values, ID types (serial, RFID, QR), maintenance types (with criticality), service categories, issue categories.

### 1.4 Vendors — who supplies

- One vendor master: name, contacts, GST, address, **categories supplied**, external or internal (internal = another department leasing or servicing).
- Each vendor collects: rate history (every quote, won or lost), rate contracts, open lines, receipts with on-time and quality ratings, **scorecard**.
- The same vendor can be a **supplier** (PO), a **service provider** (work order, AMC) and a **buyer** (disposal).

### 1.5 Rules library — what must be true (GRC Define)

```
Policy  →  Standard (own, CZA, FSSAI, …)  →  Rule (requirement)  →  Procedure (steps)
                                              │
                                              └── tested by: check questions, assessments
Licences and returns (deadlines) · Training and competency (who may do which risky task)
```

Rules reach every other module: a **cold room rule** is tested by a check, a **maintenance procedure** is attached to a maintenance plan, a **permit-to-work rule** gates a work order, a **controlled-drug rule** gates a pharmacy issue.

### 1.6 Living subjects — from Antz

Animals, enclosures and species come from Antz. Operations records can be **tagged to them** (a dispense to an animal, a check per animal, an enclosure's fence repair).

---

## 2. Things held — stock and assets

Two kinds of holdings, sitting in the place tree.

### 2.1 Stock

```
Variant × Store × Batch  →  quantity on hand
                            reorder level (per variant per store)
                            value (quantity × average price)
                            nearest expiry
                            location (rack / shelf)
```

- **Every change to stock is one ledger entry**: `{type, variant, store, batch, qty ±, rate, by, at, reference record}`. The quantity is always the sum of its entries.
- Ledger entry types: opening balance · procurement receipt · purchase · issue / dispense · consumed on work order · transfer out · transfer in · return to store · return to supplier · adjustment (missing, expired, damaged) · count variance · dispatch cancel · disposal / scrap.
- **In transit (escrow)**: stock leaves the sending store at dispatch and enters the receiving store only when received.
- Stock statuses per store: in stock · low (below reorder level) · out · about to expire · expired · in transit · quarantined (failed inspection, recalled).

### 2.2 Assets

```
Asset
├── identity        ID, tag(s), scan log, photos, documents
├── what it is      product / variant (optional), asset category, model, serial, manufacturer
├── where           place (area / spot)   — and optionally a parent asset (component of)
├── who holds it    custody: a person or a place (with the place owner accountable)
├── money           purchase cost, source PO and GRN, useful life, depreciation, book value
├── cover           warranty, AMC (each with expiry and alerts)
├── health          condition, status, maintenance plans, meter readings (hours, km)
└── life history    every check-out, transfer, ticket, work order, check, cost
```

Asset status: available · checked out · leased · pending transfer · under maintenance · missing · damaged · decommissioned · pending disposal · disposed.

**Asset hierarchy**: assets can nest. A cold room (asset) contains a chiller unit (asset) which uses compressors (spare parts). Work on a child rolls cost and downtime up to the parent.

**Places and assets meet**: a place that needs maintaining (an enclosure fence, a cold room, a borewell) has a matching **place asset**, so the same maintenance, ticket and check machinery works on built places as on movable equipment.

### 2.3 How things become stock or assets

```
Goods received (GRN line)
├── tracking = consumable / spare part  → ledger: procurement receipt into the receiving store
├── tracking = asset                    → one asset per unit: ID, tag, place, custody,
│                                         warranty from the line, depreciation starts
└── tracking = service                  → nothing held; marks the service line delivered
```

---

## 3. Records — what happens

Every record has: an ID, a type, a place, a cost centre (if it spends), an owner, a status with its own lifecycle, links to other records, a history, attachments and comments.

Records fall in five families.

### 3.1 Needs — someone asks for something

| Record | Asked by | Asks for | Fulfilled by |
|---|---|---|---|
| **Ticket** (Helpdesk) | any staff, or an incident | an outcome from a department: fix, make, move, service | the department, via work, stock or procurement |
| **Item request** | department staff | items from a store | the store (issue) |
| **Asset request / reservation** | staff | use of an asset now, or for a future period | the asset owner (check-out) |
| **Procurement request (PR)** | department, store manager, pharmacy | items or services to be bought, against one cost centre | the procurement team |

**Breakdowns start as incidents.** When something breaks, it is reported as an incident (section 3.5); the incident raises the ticket or work order that fixes it. A ticket raised directly is a request for something new (make, move, install, service), not a report of failure. Supplies from a store are always an item request, never a ticket.

Ticket lifecycle: awaiting costing (departments with costing) → pending approval → approved → in progress → completed → locked after 48 hours. Side exits: rejected, cancelled, reopened within 48 hours.

### 3.2 Work — someone does something

| Record | What it is | Comes from |
|---|---|---|
| **Maintenance plan** | recurring care for an asset or place: type, procedure, checklist, who or which vendor, how often (by date or by meter) | asset setup, a rule, an AMC |
| **Maintenance visit** | one occurrence of a plan | the schedule engine |
| **Work order (WO)** | a planned job on one or more assets / places, by a person or a vendor, with parts, permit and downtime | a ticket, a maintenance visit, a finding, an incident action |
| **Task (to-do)** | the smallest unit: one person or team, one thing to do by a time, with steps and proof | every record above, and people themselves |

Work order lifecycle: draft → pending approval → approved → in progress → completed / partially completed (per asset) → closed. Side exits: rejected, cancelled.
Maintenance visit: scheduled → in progress → completed · missed (critical ones escalate at once) → rescheduled.

### 3.3 Movements — something moves

| Movement | Of | Between |
|---|---|---|
| Issue / dispense | stock | store → person, animal, work order or cost centre |
| Return to store | stock | person / department → store |
| Transfer | stock | store → store (in transit until received) |
| Adjustment | stock | store → nowhere (missing, expired, damaged) |
| Return to supplier | stock | store → vendor |
| Check-out / check-in | asset | owner ↔ person or place |
| Lease / lease return | asset | department ↔ internal or external lessee |
| Asset transfer | asset | place → place (single or bulk) |
| Gate pass | stock or asset | site ↔ outside (out for repair, returns, deliveries) |

### 3.4 Commerce — buying and paying

```
Procurement request (PR)          one cost centre, many lines, need-by, linked tickets
  └── PR line                     one variant (or a new item), quantity, estimated rate, preferred vendor
        └── Sourcing              up to 3 quotes per line, ranked L1 / L2 / L3; L1 is chosen
              └── PO request      ONE vendor, MANY lines (from many PRs); vendor and rate fixed here
                    └── Purchase order (PO)
                          └── Delivery (delivery challan, DC)     partial deliveries allowed
                                └── Goods received note (GRN)    + inspection check
                                      └── Vendor invoice          matched to GRN(s) and PO (three-way match)
                                            └── Payment request
                                                  └── Payment
```

PR line route: approved → sourcing → PO requested → PO raised → ordered → delivered / partially received → received at site → payment requested → payment approved → paid. Side exits: rejected, cancelled, closed short, sent back.

Also in commerce: **rate contracts** (pre-agreed vendor rates; items reordered automatically against them), **AMC and service contracts**, and **disposal sales** (money in).

### 3.5 Assurance — checking and proving (GRC)

| Record | What it is |
|---|---|
| **Check definition** (audit) | a form: sections, questions, answer types, scoring, critical questions, linked rules |
| **Check schedule** | which places / assets / animals / stores, how often, who, reviewer |
| **Check session** | one run: answers, photos, score, pass / fail |
| **Finding (problem)** | something not right, with severity, place, subject |
| **Action (CAPA)** | corrective or preventive action: owner, due date, proof, effectiveness check |
| **Incident** | something that happened: injury, escape, near miss, spill, theft, missing item, **every equipment or place breakdown** |
| **Outside inspection** | a regulator's visit; its findings become findings |
| **Evidence pack** | per standard and period: every rule with its checks, results, fixes |

Kinds of check that run on the same engine:

| Check | Runs on | Triggered by |
|---|---|---|
| Compliance audit | places, animals | schedule |
| **Goods inspection** | GRN lines | each delivery |
| **Asset audit / verification** | assets in a place | schedule |
| **Stock count (cycle count)** | a store, rack or category | schedule, or a variance |
| Pre-use / safety check | vehicle, equipment | each check-out |
| Work completion checklist | WO / maintenance visit | completion |
| Handover check | asset, store, enclosure | transfer of custody |

---

## 4. Shared engines

### 4.1 Approval engine — one way to agree

One engine decides **who must agree, in what order, and on what basis**, for every record type. Modules never hard-code approvers.

**An approval policy** = record type + condition + route.

```
WHEN  a record of type T is submitted (or edited after submission)
IF    condition                 amount band · category · place · cost centre · risk · severity
THEN  route                     auto | one approver | a chain of steps
      each step's approver      named person · role pool · department in-charge · cost centre owner
                                · place owner · escalation approver · management group · finance team
```

**Amount bands** (the same shape everywhere, limits set per cost centre or department, zoo defaults behind them):

```
amount ≤ department / cost centre limit          → auto-approved (or the owner)
limit < amount ≤ zoo limit                       → escalation / site approver
amount > zoo limit                               → management group
```

Engine behaviours, the same for every record:
- **Decisions**: approve · reject (reason required) · send back with a question (no changes by the approver) · approve or reject line by line.
- **Re-route** when an edit changes the amount band; resubmit returns to the same approver unless the band changed.
- **Holds**: a record can wait on another approval (a PR waits while a new product is approved into the catalogue).
- **Self-approval guard**: a raiser who is also an approver routes like anyone else.
- **Escalation**: pending for N days → the approver's manager, then the next level.
- **Delegation**: an approver on leave → their delegate.
- **One inbox**: every pending approval for a person, from every module, in one Approvals list.
- **Trail**: who decided, when, why, and which policy routed it there.

**Every approval point in the system**

| # | Record | Approval | Basis | Default approver |
|---|---|---|---|---|
| A1 | Ticket (with costing) | Cost of the job | amount bands: dept limit → site → management | department / site approver / management |
| A2 | Ticket (no costing) | Go-ahead | configured per department | site or management |
| A3 | Work order | Go-ahead, permit to work | always, or by cost / risk | maintenance head; safety officer for permits |
| A4 | Item request | Issue from store | controlled / high-value items, or above a limit | department in-charge; pharmacist for controlled drugs |
| A5 | Asset request / reservation | Use of an asset | asset category, conflicts | asset owner |
| A6 | Asset transfer | Move between places | optional, configurable | receiving place owner |
| A7 | Stock transfer | Move between stores | requester → approver → dispatcher → receiver | store owners |
| A8 | Stock adjustment / write-off | Loss, expiry, damage | value bands | store owner → finance |
| A9 | Count variance | Accept the counted quantity | value bands | store owner |
| A10 | New product | Add to catalogue | domain | domain in-charge (e.g. pharmacy in-charge) |
| A11 | Procurement request | Spend | amount bands on the cost centre | cost centre owner → escalation → management |
| A12 | PO request | Vendor and rate | always; sees L1/L2/L3 quotes | finance team |
| A13 | Invoice | Bill matches receipt | mismatch with PO and GRN is flagged, not blocked; head accepts with a reason or returns it | bill desk head |
| A14 | Payment | Release money | always, or by value | CEO / management → finance |
| A15 | Decommission | Take an asset out of use | always | asset owner |
| A16 | Disposal | Sell, scrap, donate, write off | disposal value above threshold | finance / management |
| A17 | Policy / procedure | Publish a version | always | policy owner |
| A18 | Task | Accept completed work | task flag "needs approval" | supervisor |
| A19 | Action (CAPA) | Verify it worked | always | a person other than the doer |
| A20 | Incident | Close the investigation | severity | DM / cluster in-charge |
| A21 | Sign-off | Received as asked | PR and ticket completion | raiser and approver |

### 4.2 Task engine — one way to act

Everything that needs a person to act becomes a **to-do**. To-dos sit in **My work** (today · upcoming · late · done), a **Team** view (per person, what is late) and a **Calendar**.

- A **linked to-do** opens the record it came from and **closes itself** when that work is done.
- A to-do can have steps, photo proof, a time estimate, a skip with reason, and its own approval (A18).
- Assignment: a person, a team ("anyone" claims it, or "everyone" does it), or a role at a place.

**Where to-dos come from**

| Source | To-do |
|---|---|
| Ticket | cost it · start it · complete it · sign off |
| Work order | do the job (per asset) · attach permit · record parts and time |
| Maintenance visit | do the visit |
| Check schedule | run the check |
| Finding | fix it |
| Action (CAPA) | do the action · verify it |
| Incident | investigate · approve closure |
| Low stock | raise a restock request |
| Stock transfer | dispatch it · receive it |
| PR line | source it · order it · record receipt · sign off |
| Delivery | inspect it · write the GRN |
| Invoice | match it · check it · request payment |
| AMC / warranty / licence | renew before expiry |
| Asset | return a checked-out asset · verify a found asset |
| Policy / procedure | review it · sign it · train on it |
| Any approval | decide (also shown in the Approvals inbox) |
| A person | their own to-dos |

### 4.3 Schedule engine — one way to repeat

One recurrence engine (daily · weekly · monthly · yearly · every N · custom · by meter reading · on an event) produces occurrences for:
maintenance plans · check schedules · recurring tasks · licence and return deadlines · AMC, warranty and lease expiries · reorder runs (rate-contract items) · stock counts · depreciation runs · policy review dates.

Outcomes the same everywhere: done · done late · missed · won't do (with reason) · rescheduled.

### 4.4 Check engine — one way to inspect

One form builder (sections, questions, the five input types, scoring, critical auto-fail, photo or note required, "each" questions repeated per subject) and one way to run (by subject, by question, grid). A failed answer becomes a **finding**. Used by every check in 3.5.

### 4.5 Links, history, notifications, cost

- **Links**: every record can link to others with a typed link (caused by · fulfils · uses parts from · paid by · checks · fixes). The links form the **thread** shown on every record.
- **History**: every change on every record, with who and when.
- **Notifications and escalation**: in-app and email; escalation rules per severity and per module (critical incident → DM at once; overdue by N days → manager, then the next level).
- **Cost roll-up**: every spend lands on a **cost centre**, and when it is for an asset, also on the **asset** (total cost of ownership: purchase + parts + labour + vendor + AMC − disposal value).

---

## 5. How the records link — the master graph

```
                         RULES LIBRARY
                 policy → standard → rule → procedure
                        │ tested by        │ attached to
                        ▼                  ▼
  ┌──────────── CHECK ───────────┐   MAINTENANCE PLAN ──► MAINTENANCE VISIT ─┐
  │ schedule → session → finding │                                          │
  └──────┬───────────────┬───────┘                                          │
         │ fix needs work │ fix is an action                                │
         ▼                ▼                                                 ▼
      TICKET ◄──── INCIDENT ──► ACTION (CAPA)                          WORK ORDER
         │ (broke → from incident;                                     │   │   │
         │  new need → raised)                                         │   │   │
         ├──────────────── approved, needs a job ──────────────────────┘   │   │
         │                                                   parts in stock │   │ parts not in stock
         │                                                                  ▼   ▼
         │                                       STORE ── issue to WO ── STOCK   PROCUREMENT REQUEST
         │                                         ▲          (ledger)    ▲            │
         │                                         │ low stock → restock ─┼────────────┤
         │                                         │                      │            ▼
         └──── needs items bought ─────────────────┼──────────────────────┼──► SOURCING (L1/L2/L3)
                                                   │                      │            ▼
                                                   │                      │      PO REQUEST → PO
                                                   │                      │            ▼
                                                   │                      │      DELIVERY (DC)
                                                   │                      │            ▼
                         GOODS INSPECTION (check) ─┼──────────────────────┼──── GRN
                                                   │                      │      │   │   │
                                     consumable / spare                   │      │   │   └─ service → line delivered
                                                   └──────────────────────┘      │   └─ asset → ASSET REGISTER
                                                                                 ▼
                                                                         VENDOR INVOICE (bill desk)
                                                                                 ▼
                                                                         PAYMENT REQUEST → PAYMENT

  ASSET ─ checked out / leased / transferred / audited / maintained / ticketed / depreciated / disposed
        └─ damaged or end of life → DECOMMISSION → DISPOSAL → (replacement) PROCUREMENT REQUEST

  Every record above ──► TASKS (My work)      Every approval above ──► APPROVALS inbox
  Every record above ──► COMPLIANCE (results, evidence, what is late, what failed)
```

**Link table**

| From | To | When |
|---|---|---|
| Ticket | Work order | an approved ticket needs a planned job on assets or places |
| Ticket | Item request | it only needs items from a store |
| Ticket | Procurement request | it needs something bought (the ticket must be approved first) |
| Ticket | Asset | the ticket is about an asset (optional) |
| Maintenance plan | Maintenance visit | each due date |
| Maintenance visit | Work order | the visit needs parts, a vendor or a permit |
| Work order | Stock (issue) | parts consumed, cost onto the asset |
| Work order | Procurement request | parts or a vendor service must be bought |
| Work order | Asset | status moves to under maintenance and back |
| Store (low stock) | Procurement request | below the reorder level; auto for rate-contract items |
| Procurement request | PO request → PO | after approval and sourcing |
| PO | Delivery → GRN | each delivery |
| GRN | Goods inspection | each GRN line that needs inspecting |
| GRN | Stock / Asset | received into the store, or registered as assets |
| GRN | Invoice | three-way match: PO × GRN × invoice |
| Invoice | Payment | after bill desk and finance |
| Check session | Finding | a failed answer |
| Finding | Action / Work order / Ticket | the fix |
| Incident | Action / Work order / Ticket | the corrective and preventive work |
| Incident / finding | Rule | the rule that failed; a review to-do follows |
| Asset audit | Asset | missing, damaged, wrong place |
| Stock count | Adjustment | variance accepted (A9) |
| Asset | Decommission → Disposal | end of life |
| Disposal | Procurement request | replacement |
| AMC / warranty | Work order | covered repairs go to the AMC vendor |
| AMC / warranty / licence | Procurement request | renewal (service line) |
| Any record | Task | every time someone must act |
| Any record | Approval | every time someone must agree |

---

## 6. End-to-end flows — the nine loops

### F1. Something broke (reactive)
1. A keeper reports an **incident**: the chiller in Cold Room 2 is not cooling (type breakdown, severity, place, asset, photo, immediate action).
2. Triage on the incident raises a **ticket** to the owning department (Maintenance), or a **work order** directly when the owner is Maintenance and no costing is needed. If the department costs work: the in-charge adds costing and a date.
3. **Approval A1** by amount band.
4. Approved → a **work order** on the chiller (asset → under maintenance), assigned to a technician, or to the **AMC vendor** if covered.
5. Parts: in stock → **issue to the WO** (ledger, cost onto the asset). Not in stock → **procurement request** linked to the ticket (F3).
6. Technician completes the WO with the **completion checklist**, parts and time. Asset → available.
7. Department completes the ticket; the keeper **signs off**; 48 hours to reopen, then locked. The incident closes when its tickets and work orders are done (A20 for serious ones), with root cause recorded.
8. History: the chiller's record shows the ticket, the WO, the parts and the cost. Repeated breakdowns count towards repair vs replace (F8).

### F2. Planned maintenance (preventive)
1. A **maintenance plan** on the chiller: monthly service, procedure from the rules library, checklist.
2. The schedule engine creates the **visit** and a **to-do** for the technician.
3. Visit done → checklist, readings, parts (ledger). Needs more → **work order**.
4. Not done by the due date → **missed**; critical types escalate at once.
5. Next visit is scheduled. Results feed **Compliance** (maintenance on time %).

### F3. Restock (stores)
1. A store falls **below the reorder level** → low stock → a to-do for the store manager (or an automatic PR for rate-contract items).
2. **Procurement request** prefilled with quantities to bring the store back up, against the store's cost centre.
3. **Approval A11** by amount band (cost centre owner → escalation → management). New products wait on **A10**.
4. Procurement team **sources**: up to 3 quotes per line, L1 chosen, vendor and rate fixed.
5. **PO request** (one vendor, many lines) → **A12** finance → **PO raised** → ordered.
6. **Delivery** arrives with a DC (at the gate) → **goods inspection** check → **GRN** (accepted quantities; short or damaged stays ordered).
7. Accepted quantities → **stock ledger: procurement receipt** into the store (by batch, with expiry, placed on a rack).
8. **Invoice** recorded at the bill desk, matched to PO and GRN → **A13** → **payment request** → **A14** → **paid**.
9. Raiser and approver **sign off**. Vendor scorecard updated (on time, short, quality).

### F4. Buying an asset (capital)
Same as F3 up to the GRN, then each unit of an asset-tracked line becomes an **asset**: ID and tag printed, place and custody set, warranty from the PO line, purchase cost from the invoice, depreciation starts, an **asset audit** schedule and a **maintenance plan** can start from the asset category.

### F5. Issue and transfer (stores to people)
1. A department raises an **item request** (a ticket or work order that needs items raises one too; supplies are never a ticket on their own).
2. **A4** for controlled or high-value items.
3. Store issues (**FEFO**: earliest expiry first; expired batches blocked) → ledger → cost to the cost centre; tagged to an animal or a WO where it applies.
4. Between stores: **transfer** → A7 → dispatch (stock in transit) → receive (into the same batch) → ledger both sides. Local to central = return.

### F6. Check → finding → fix (assurance)
1. A **check schedule** creates a **session** and a to-do (compliance audit, asset audit, stock count, safety check).
2. Failed answers become **findings** with severity.
3. Each finding gets a fix: an **action (CAPA)**, a **work order** (fence repair), or a **ticket** (to another department).
4. Fix done → **verified by another person** (A19) → did it work after N days?
5. Rule status updates (met / not met) → **Compliance** dashboard and **evidence packs**.
6. Stock count variance → **adjustment** after A9. Asset audit missing → asset **missing**, an incident (missing item) to find it.

### F7. Incident (something happened)
1. Anyone **reports** an incident (type, severity, place or animal, what happened, immediate action).
2. **Investigation**: root cause, corrective and preventive **actions** (to Tasks & Actions), and any **work orders or tickets** (a broken latch).
3. Root cause points at the **rule** that failed → policy or procedure review to-do.
4. **A20** closure by severity. Feeds Compliance and trends.

### F8. End of life (assets)
1. An asset is **damaged** or its repair cost and breakdowns cross a line → **repair vs replace** decision.
2. Replace → **decommission (A15)** → **disposal (A16)**: sold, scrapped, donated, written off; gain or loss against book value.
3. On disposal: AMC and warranty close, reservations cancel, replacement **PR** raised (F4).

### F9. Renewals (contracts and licences)
AMC, warranty, lease and licence **expiry alerts** (90 / 30 / 7 days) → a renewal **to-do** → a **PR with a service line** (F3 without stock) → new contract linked to the old one.

---

## 7. Who does what — people across the system

| Person | Raises | Does | Approves |
|---|---|---|---|
| Any staff (keeper, mahout, vet) | tickets, incidents, item requests, asset requests | own to-dos, checks assigned to them | — |
| Department in-charge / team | PRs, WOs, item requests | costs and runs tickets, does work | department-level tickets, item requests |
| Technician / maintenance team | WOs from visits | maintenance visits, WOs, completion checklists | — |
| Store manager | restock PRs, transfers | issues, receipts, counts, racks, reorder levels | transfers, adjustments in own stores |
| Pharmacy in-charge | pharmacy PRs | dispensing, controlled-drug register | new medicines (A10), controlled issues |
| Asset owner | asset transfers | check-out, lease, asset audits | asset requests, decommission |
| Cost centre owner | — | — | PRs up to the cost centre limit |
| Site / escalation approver | — | — | above department or cost centre limit, up to the zoo limit |
| Management group | — | sees everything read-only | above the zoo limit, payments |
| Procurement team | — | sourcing, quotes, PO requests, orders, receipts | — |
| Gate / security | gate passes | logs deliveries and outgoing items | — |
| Accounts clerk / bill desk head | — | invoices against GRNs | invoices (A13) |
| Finance team | — | payments | PO requests (A12), write-offs, disposals |
| Auditor / safety officer | checks, findings | runs checks | permits, CAPA verification |
| Admin | — | places, people, limits, masters, approval policies | — |

---

## 8. How people find it — the shape of the apps

```
Antz home
├── My work                    to-dos from every module + my own
├── Approvals                  everything waiting for my decision
│
├── Helpdesk                   Tickets · Raise · Departments' queues
├── Work                       Work orders · Maintenance plans · Visits calendar
├── Assets                     Register · Requests & reservations · Transfers · Contracts (AMC, warranty) · Disposal
├── Inventory                  Stock · Movements · Counts · Racks · Products · Dashboard
├── Procurement                Requests · Sourcing (by item, by vendor) · POs · Receipts (DC, GRN) · Vendors
├── Bill desk & payments       Invoices · Payment requests · Payments
├── GRC                        Policies & standards · Checks · Incidents · Actions · Compliance
│
└── Settings                   Places · Departments & cost centres · Approval policies · Masters · Catalogue
```

Two surfaces, one model:
- **Tablet / mobile**: raising, doing and approving in the field (tickets, to-dos, checks, receiving, issuing, scanning tags).
- **Web**: planning, sourcing, finance, reports and settings.
- **Stations**: gate (deliveries, gate passes), store kiosk (scan to issue or receive).

---

## 9. One record, followed through — example thread

```
INC-0042  Keeper reports Cold Room 2 at 9 °C (rule: "Cold storage 5 °C or less")
 └── TKT-0518  Chiller not cooling → Maintenance (costing ₹38,000 → A1 site approver)
      └── WO-0211  Chiller CH-02 repair, AMC vendor CoolTech, permit attached (A3)
           ├── ISSUE-0907  1 × thermostat from Central store (ledger, cost to CH-02)
           └── PR-26-0163  1 × compressor relay (A11 cost centre owner)
                └── POR-0081 → PO-0458 CoolTech (A12 finance) → DC-1190 → GRN-0773 (inspection passed)
                     └── INV-3321 matched → PAY-0119 (A14) → paid
 └── ACT-0077  Preventive action: add weekly temperature check to Cold Room schedule (verified after 30 days)
 └── CHK schedule updated → Compliance: rule met again from 25 Nov
```

---

## 10. Decisions (18 Nov 2026)

| # | Question | Decision |
|---|---|---|
| D1 | Ticket vs incident for a breakdown | **Always an incident.** Every breakdown is reported as an incident; the incident raises the ticket or work order. Tickets raised directly are for new needs. |
| D2 | Where approvals live | **One Approvals inbox** per person, across every module. |
| D3 | Spare parts | **Held as stock**, issued to work orders, costed to the asset. |
| D4 | Built places | **Get a place asset**, so maintenance, tickets and checks work the same as on equipment. |
| D5 | Custody of a checked-out asset | **A person or a place**; the form leads with person; a place's owner is accountable. |
| D6 | Asking a store for items | **Its own item request**, never a Helpdesk ticket. |
| D7 | Risk in GRC | **Findings only** (September ruling holds); no hazard register. |
| D8 | Invoice not matching PO and GRN | **Flagged, not blocked**; the bill desk head accepts with a reason or returns it. |
| D9 | Cost centres and departments | **Many cost centres per department**, each with its own owner and limit. |
| D10 | What becomes a task (19 Nov) | **Tasks is its own module.** Task records come only from GRC (audit, assessment, checklist, CAPA action, finding fix, investigation, read & sign / training), people (own or assigned), schedules (recurring routines) and handover / pre-use checklists. A task can carry a checklist, assessment or audit form. Steps inside tickets, WOs, PRs, GRNs and invoices are "your turn" items, approvals stay in the Approvals inbox, and AMC / warranty / licence expiry, low stock and overdue returns are **alerts**, not tasks. **My work** is one screen showing tasks, your-turn steps, approvals and alerts. Supersedes the "where to-dos come from" table in 4.2. |
