Frequently asked questions on MAISO (ZMQ).
Answers on architecture, standard coverage, tenant isolation, and human oversight.
Why does MAISO (ZMQ) separate the compliance platform from the Odoo thin client?
Standards libraries, verification rules, AI pre-checks, and audit histories belong in an isolated, multi-tenant compliance layer rather than being scattered across ERP databases. The lean Odoo client displays statuses, holds, and widgets right on the record while transmitting signed events to the platform.
Does the AI in MAISO (ZMQ) make autonomous approval or hold decisions?
No. The architecture enforces strict human oversight: AI components generate only traceable review suggestions and revision drafts. Every binding approval, conditional release, or audit change requires four-eyes sign-off by quality management (QMR).
Which standards does the architecture cover?
The architectural core focuses on ISO 13485 for medical technology — including supplier qualification, purchase order approval with hold logic, lot traceability, and change control under clause 4.1.6. The underlying rule and audit engine transfers systematically to ISO 9001 processes.
How are data protection and EU AI Act requirements addressed?
The platform is designed for hosting in a German data center with strict tenant isolation (Row-Level Security), HMAC-signed webhooks, upstream PII redaction before AI calls, and technical documentation covering human oversight and audit trails.
Does MAISO (ZMQ) replace statutory certification or an external auditor?
No. Software cannot certify a business. MAISO (ZMQ) helps quality leaders check live ERP transactions continuously against documented standard rules, spot deviations early, and maintain defensible evidence for internal and external audits.