GGB Primary document · source held on file
Opening readiness is a controlled asset register — not a final-week checklist
Coded inventory database (ten storage locations, 325 coded items) + complex-wide asset register (nine location sheets, 921 line items) · restaurant complex, Oman · 2014–2015
The record
In March 2014, a hospitality operating company in Oman built its inventory database with code numbers for a property-management system — and the exported workbook shows what “ready to operate” actually means on paper. Ten storage locations, each its own sheet: dry storeroom, meat and poultry cold room, seafood cold room, vegetable and fruit cool room, dairy cold room, frozen goods, beverage store, tobacco store, general store, chemical store. Three hundred and twenty-five items coded at build, across four departments — food, beverage, tobacco, general — with code families allocated per location and headroom reserved for products not yet bought.
The covering correspondence records the method in the author’s own words: the product list built from the complex’s actual purchases, the item codes structured on the department-and-group criterion the systems vendor required, and each group’s code range allocated with future volume in mind.
The column architecture — what every item carried
| Identity | serial, item name and the packing specification — “6 × 3kg”, “24 tins × 400g” — the unit of control defined before the unit of use |
|---|---|
| Specification | brand or origin where it mattered — specification as a column, not a memory |
| Cost discipline | package cost beside derived unit cost — every later variance made readable at build |
| Ownership | department · group · location — every item owned three ways |
| The code itself | department-and-group prefixed series per location, allocated with reserved headroom for future products |
Why coding at build is an operating decision
A venue that codes its inventory before opening has decided, in advance, how it will count, cost, order and audit for years. The code architecture here — department and group criteria set by the property-management system, ranges allocated per location with growth headroom — means the operating system was being installed while the shelves were still empty. Storage rooms that carried structure before they carried stock: that is readiness as a register, not a final-week checklist.
The complex-wide asset register (April 2015) — the second record
A year on, the same operating company counted an entire hospitality complex the same way. The complex-wide inventory workbook — exported under the same instrument — carries nine location sheets across three floors and the back-of-house estate: the destination restaurant, a banquet hall, a terrace venue, every kitchen’s cooking equipment consolidated, the small-ware store, offices and furniture, security and sound equipment, staff porta-cabins, even parking and garden assets. Nine hundred and twenty-one line items, each carrying the same four-column discipline: serial, item, owning location, verified quantity.
What the two records prove together
| Location ownership | every asset owned by a named location sheet — floor by floor, front and back of house |
|---|---|
| Quantity verification | counts written per item at the time, not reconstructed later — the baseline every later variance reads against |
| Whole-complex coverage | guest floors, kitchens, stores, offices, staff accommodation and grounds in ONE register — readiness as a system, not a dining-room checklist |
| Continuity of method | the 2014 coded database and the 2015 complex register are the same discipline at two depths — code architecture first, then the physical count held against it |
Role boundaries
This control layer was built owner-side, inside the operating company, in coordination with the systems vendor that defined the coding criteria. GGB is the present-day consultancy that carries this discipline — inventory as an operating-control instrument, installed before the first guest; it claims the control architecture shown, and nothing else.
Redactions applied
The operating company, individuals and the systems vendor are not named. No item-level cost publishes — the cost columns are described, never reproduced. Product brand names are withheld; counts, code families and column architecture publish as structure.
What this document proves — and what it does not
It proves that the complex’s operating control was engineered as a coded register — locations, departments, groups, costs and growth headroom decided on paper, at build. It does not prove later stock accuracy or trading results, and it does not claim the property-management software as GGB’s work. The transferable asset is the method: it is the direct ancestor of the readiness registers and operating-control instruments GGB installs today.
Coded inventory database (30 March 2014, ten location sheets, 325 coded items) + complex-wide asset register (April 2015, nine location sheets, 921 line items) · restaurant complex, Oman · published from the source workbooks exported under the owner’s 2026-07-30 scoped mailbox authorization · entities, venue names, brands and costs withheld · published anonymised