Technology · how it is built

Five layers, one loop, no generated math.

For the technical evaluator and the press: what MARBIM is, where the arithmetic lives, how a factory’s data is kept to itself, and where the system runs.

Architecture

Inside MARBIM, at full depth.

The model is one layer of five. Everything numeric runs through fixed formulas the factory can audit; everything written is a draft until a named person approves it.

01
DATA ENGINE
Verified garment corpus
Tech packs, POs, LCs, challans and test reports, cleaned and labelled by people who have read thousands of them. Units are normalised on the way in: gsm, kg, dozens, pcs, cartons.
02
MARBIM CORE
Small language model
Built only for garments. It reads the Bangla-English mix of a real factory floor and turns paperwork into named fields, each with a confidence and a link to the line it came from.
03
KNOWLEDGE GRAPH
Styles, buyers, materials
Every style, buyer, supplier and material is a node. A new tech pack lands next to the last three from the same buyer, so the draft starts from history, not from a blank form.
04
DETERMINISTIC CALCULATORS
the difference
Consumption, costing, CM — math is never generated
Fabric consumption, costing and CM minutes run through fixed formulas the factory can audit line by line. MARBIM fills the inputs; it never invents the arithmetic.
05
PROPOSE → APPROVE
Nothing saves without a person
Every output is a draft until a named person with the right to that record presses approve. The stamp — who, when, and exactly what they saw — is permanent.
The trust loop

Propose → approve → commit, as a sequence.

The only actor that can move a record into the factory is a named person. MARBIM and the calculators prepare; the system commits only after the approval; the audit stamp is permanent.

Document
MARBIM
Calculators
Named person
System
Audit
Document → arrives
PDF, XLSX, photo or email body — Bangla, English, or both
MARBIM → reads → drafts
named fields · confidence per field · source line per value
Calculators → compute
consumption, costing, CM through fixed, auditable formulas
Named person → reviews → approves or edits
only someone with the right to that record can press approve
System → commits
the record enters the factory database — not before
Audit → stamps
who · when · what they saw · audit id, permanent
Data isolation

Your factory’s data trains no one else’s model.

One tenant per factory
Your data lives in its own schema with row-level security. No query from another tenant can reach it, by construction rather than by policy.
FACTORY_PRIVATE by default
Nothing you upload is used to train a model for anyone else. The verified corpus that trains MARBIM is separate from your live records.
Your keys, your exit
Every record is exportable in open formats at any time. Leaving is a download, not a negotiation.
Deployment

Works on the factory’s own infrastructure.

Cloud or on-premise
Runs hosted, or on the factory’s own servers inside the compound when the buyer’s audit or the owner’s preference demands it.
The line keeps running
Floor screens record through a dropout and sync when the connection comes back. Bundle cards and hourly output never wait for the internet.
Phones first
The owner’s view and the exceptions feed are built for a mid-range Android on 4G, because that is what is in the pocket at 21:44.
Bangla + English

Two languages, one record.

Bangla and English, mixed
A challan written half in Bangla, a WhatsApp note with English numbers — MARBIM reads both in one pass. Operator screens are in Bangla; commercial documents stay in English.
Numbers stay Western
Invoices, LCs and bank documents use Western digits, so the system does too. Bangla labels sit beside them; the digits never change shape.
Units are first-class
gsm, kg, dozens, pcs, cartons and minutes are typed, not strings. A quantity without a unit is flagged, never assumed.
MARBIM proposes. Your people approve.