Antz · Operations · Bounded contextsv1 · For review
Who owns what: the operations system sorted into contexts
Every thing in Antz operations is a card. Each card belongs to exactly one context, which owns its rules and its data. Other contexts only point at it. Approvals, tasks and the organisation sit in the middle, shared by all.
How to read the cards
The main record this context exists for
Owned here: its rules live in this context
Used here, owned by another context
What must be true, did we check it, and what went wrong?
Auditor · safety officer · policy owner
Incidentevery breakdown starts here
Audit sessionone run of a check
PolicyStandardRuleProcedure
Audit formAudit scheduleFinding
Action (CAPA)Licence and returnEvidence pack
Assetfrom AssetsStorefrom InventoryPlacefrom Places
Who is asked to do what, and has it been done?
Any staff · department in-charge
Ticketan outcome asked of a department
Department queueIssue categoryCosting lines
Tentative dateSign-offReopen window48 hours
Incidentfrom GRCAssetfrom Assets
What job is done on which asset, by whom, with what parts?
Maintenance head · technician · vendor
Work ordera planned job
Work order lineone per assetMaintenance planMaintenance visit
Maintenance typePermit to workParts usedLabour and downtime
Ticketfrom HelpdeskAssetfrom AssetsVendorfrom Procurement
What do we own, where is it, who holds it, what is it worth?
Asset owner · finance
Assetone thing, its own ID
Place assetenclosure, cold roomTag and scanAsset category
Check-out (custody)ReservationAsset transferLease
WarrantyAMCDepreciationDecommissionDisposal
GRN linefrom ProcurementPlacefrom Places
Where is everything?
Admin
Site
Zone / sectionAreaenclosure, building, roomSpot
Place ownerStationgate, kiosk
Animal, enclosurefrom Antz
0Shared kernel: used by every context
Owns no business data. Every context hands its decisions and to-dos here, and reads people and money from here.
Approvals
Approval requestApproval policyAmount band
Step and decisionDelegationApprovals inbox
Tasks
To-doMy workTeam view
Proof and stepsEscalation rule
Schedules
RecurrenceDue, missed, done late
Record thread
Link between recordsHistoryAttachmentsNotification
Who are we, who may do what, whose money is it?
Admin · finance
Person
DepartmentTeamRolea bundle of permissions
Cost centremany per departmentLimitsManagement group
What kinds of things exist, and how is each one tracked?
Domain in-charge · admin
Product
DomainCategoryTracking modeconsumable, spare, asset, service
Variant (SKU)PackageUnit of measureAttribute set
New product approval
How much do we have, where, and where did it go?
Store manager · pharmacy in-charge
Stockvariant × store × batch
Store (warehouse)Rack and shelfBatch and expiryReorder level
Item requestIssue / dispenseStock transferStock count
AdjustmentStock ledger
Productfrom CatalogueGRN linefrom ProcurementWork orderfrom Maintenance
What are we buying, from whom, at what price, and has it arrived?
Raiser · procurement team · cost centre owner
Procurement request
Request lineSourcingQuoteL1, L2, L3
PO requestPurchase orderDelivery (DC)Goods inspection
GRNVendorRate contractVendor scorecard
Productfrom CatalogueTicketfrom Helpdesk
Does the bill match what came, and has it been paid?
Accounts clerk · bill desk head · finance
Vendor invoice
Three-way matchPO × GRN × invoiceDiscrepancy
Payment requestPayment
Purchase orderfrom ProcurementGRNfrom ProcurementVendorfrom Procurement
Where the contexts hand off to each other
| From | What crosses the boundary | To |
| 1 · GRC | An incident or finding needs a department to fix something | 2 · Helpdesk |
| 1 · GRC | A fix needs a job on an asset or place | 3 · Maintenance & work |
| 2 · Helpdesk | An approved ticket needs a job | 3 · Maintenance & work |
| 2 · Helpdesk | A ticket needs something bought | 9 · Procurement |
| 3 · Maintenance & work | A job needs parts from a store | 8 · Warehousing & inventory |
| 3 · Maintenance & work | A job changes an asset's status, condition and cost | 4 · Assets |
| 8 · Warehousing & inventory | Low stock, or parts not in stock | 9 · Procurement |
| 9 · Procurement | Goods received of a consumable or spare part | 8 · Warehousing & inventory |
| 9 · Procurement | Goods received of an asset-tracked item | 4 · Assets |
| 9 · Procurement | PO and GRN, for matching the bill | 10 · Bill desk & payment |
| 4 · Assets | Breakdown, or a failed asset audit | 1 · GRC |
| 4 · Assets | End of life, or an AMC or warranty due for renewal | 9 · Procurement |
| Every context | A decision someone must make · a job someone must do | 0 · Shared kernel |
Rules of the boundaries
One owner per cardA record's rules and statuses live in one context. Others point at it by ID and never change it.
Handoffs, not shared editsA context asks another to act (raise, request, receive). It never edits the other's record.
The kernel owns no businessApprovals and tasks know who and when, not what a ticket or a PO means.
Places and people are read-onlyEvery context reads sites, stores, people and cost centres; only Places and Organisation change them.