Management Digital Ops System

Management Digital Ops System is a business workspace for operational and commercial performance. It was designed to give leadership and operational teams a shared view of dry bean trading, factory KPIs, targets, OKRs, NPS and impact data—without relying on disconnected spreadsheets and ad-hoc reports.

Commercial, operational and impact numbers lived in different systems and routines. Purchasing, factory performance, targets and OKRs could not be reviewed in one place, and offline or delayed source systems made reporting fragile. Access needed to be controlled by role, with authentication that matched how the organisation already works.

The work started with the decisions the organisation needed to make—not with a dashboard template. Trading, factory operations, targets and performance management were mapped as connected domains. A local operational store was designed so the workspace could remain useful even when upstream systems were unavailable, with synchronisation from the field platform for locations, farmers, purchasing cooperatives, payments and evacuations.

Management Digital Ops System is organised as a hub of workspaces: dry bean operations, commercial factory reporting, season and monthly targets, and OKR performance. Role-based access, Google authentication and authenticator MFA sit in front of the product. An admin layer covers users, settings and operational monitoring. The architecture is a closed-loop path from source systems, through a PostgreSQL store and REST API, into the workspace used by operators and leadership.

• Factory KPI monitoring
• Dry bean purchasing
• Targets and performance
• Field platform integration
• OKRs and KPIs
• NPS and impact reporting
• Role-based access
• Google authentication
• MFA

Teams can review trading, factory performance, targets and OKRs in one governed workspace rather than assembling the picture from separate files and tools. Access, authentication and auditability are part of the product rather than an afterthought.

Operational analytics only holds if the data layer can survive source-system interruptions. Role design and authentication need to be decided with the workspace itself—not bolted on after the dashboards look finished.