TRUSTED FACTORYFLOW
Architecture from enterprise systems to the factory floor.
Data, identity and execution boundaries through logical, deployment and sequence views.
Logical diagram with distinct flows
Blue: API/command · Orange dashes: events · Green dashes: telemetry · Light-blue dots: Core–Edge · Red dots: safety may block
Responsibility layers and cross-cutting safeguards
01Channels and clientsAdmin Portal · Warehouse Mobile App · Supervisor Dashboard ·
ERP/MES Clients · Partner/Vendor APIs · BI/Analytics
Clients↓02Access and securityWSO2 API Management / API Gateway · Routing / mediation /
security policies · OAuth2 / OIDC / mTLS · Rate limiting /
schema & signature validation · Keycloak users / groups /
clients · MFA / step-up / authorization / sessions↓03Business coreFacility & Layout · Master Data: SKU / UOM / barcode /
route-map · WMS Inbound / Inventory / Outbound · Warehouse
Optimization · Line-side Replenishment / eKanban · Production
& Kitting · Configuration / Rules / Approval↓04Execution and roboticsWCS orchestration & execution steps · Routing / dispatch /
traffic / deadlock · Fleet Management · Robot Mission Control ·
Robot Cell & Cobot / PLC handshake · Device / PLC Adapter ·
Exception / Recovery / Maintenance Diagnostics↓05Events and integrationKafka Topics · Outbox / Inbox · Schema Registry (Avro / JSON
under contract) · Retry topics / DLQ / Replay · Event lineage /
consumer monitoring · ERP/MES sync / vendor robot adapters · OT
adapters / external APIs / webhooks↓06Data and analyticsMariaDB per service / domain · Operational Read Models · Object
Storage · Audit Trace Store · Reporting & Analytics / KPI ·
Operational Data Mart · Backup & DR Vault↓07Edge and OT operationsFactory Edge Runtime · Local Queue / Cache / Replay / Conflict
· AGV / AMR · Cobot / Robot Cell · PLC / Machines / Conveyor ·
Scanner / Printer / Scale / Vision / Sensors · OT monitoring /
SIEM integration↓
01 / Channels and clients
Present role-specific entry points and business context.
| Responsibility | Detail |
|---|---|
| Input | Sessions, scans, enterprise requests and report queries. |
| Output | Scoped requests via the gateway and authorized read models. |
| Owner | Channel application owner; business data remains domain-owned. |
| Boundary | No secrets or direct PLC commands in browser clients. |
02 / Access and security
Authenticate actors and enforce layered authority.
| Responsibility | Detail |
|---|---|
| Input | Identity, token, API subscription, tenant/site and object. |
| Output | A scoped call or auditable denial. |
| Owner | IAM, gateway administrators and domain authorization owners. |
| Boundary | Subscription and MFA do not override object rights or field safety. |
03 / Business core
Own warehouse facts, tasks and production logistics.
| Responsibility | Detail |
|---|---|
| Input | Orders, master data, quality gates and confirmed execution. |
| Output | Reservations, tasks, movements and business confirmation. |
| Owner | WMS Inventory owns stock; WMS Task owns warehouse tasks. |
| Boundary | A robot event alone cannot update stock without WMS validation. |
04 / Execution and robotics
Translate intent into constrained execution.
| Responsibility | Detail |
|---|---|
| Input | Released task, route, capability, recipe and safety state. |
| Output | Execution orders, missions/jobs and reconciled outcomes. |
| Owner | WCS owns execution; Fleet owns missions; Cell owns jobs/recipes. |
| Boundary | One dispatch/traffic authority per integration profile; adapters do not own business data. |
05 / Events and integration
Exchange versioned events and integrate enterprise/vendor systems.
| Responsibility | Detail |
|---|---|
| Input | Committed changes, callbacks and integration messages. |
| Output | Validated events, retry/DLQ records and lineage. |
| Owner | Producers own event meaning; consumers own processing/reconciliation. |
| Boundary | Kafka delivery is not business completion; replay requires deduplication. |
06 / Data and analytics
Preserve domain records, projections and evidence.
| Responsibility | Detail |
|---|---|
| Input | Transactions, telemetry, audit and attachments. |
| Output | Scoped reports, read models, packages and tested restore points. |
| Owner | Service DB owners, data stewards and evidence custodians. |
| Boundary | Read models are not masters; retention, hold and export authority remain explicit. |
07 / Edge and OT operations
Execute locally under delegated policy and connect physical equipment.
| Responsibility | Detail |
|---|---|
| Input | Approved commands, policies, device signals and checkpoints. |
| Output | Callbacks, local queues, replay batches and conflicts. |
| Owner | OT/Edge operators and device controllers under field safety. |
| Boundary | Edge is not a second stock master; safety can block authorized commands. |
Five distinct flows
| Flow | Meaning |
|---|---|
| Synchronous API/command | Request/ACK do not establish physical completion. |
| Asynchronous event | Outbox → Kafka → inbox; deduplicate and check versions. |
| Telemetry / callback | Check origin, ordering, version and freshness. |
| Core ↔ Edge | Checkpoint, replay and conflict quarantine; never overwrite the master. |
| Safety signal | May block a command after business authorization. |
Workspace–architecture matrix
| Workspace | Layers | Objects/events | Evidence |
|---|---|---|---|
| Factory Operations Center | 1,2,4,5,6,7 | Alert, incident, assignment, shift, handover, RCA/CAPA | Actor, acknowledgement/assignment time, reason, event references, recovery decision and handover record. |
| Warehouse & Production Logistics | 1,2,3,4,5,6,7 | ASN/PO, LPN/HU, SKU, lot/serial, stock, reservation, warehouse task, material call, kit, quality hold | Source/destination scans, quantities/lots, quality results, reservations, adjustment decisions and stock movements. |
| Automation & Robotics | 1,2,3,4,5,6,7 | Execution order/step, route reservation, traffic zone, robot, mission, cell job, recipe | Command/version, dispatch conditions, ACK, callbacks, recovery decisions and task–mission–cell references. |
| OT, Edge & Asset Reliability | 2,4,5,6,7 | Device, adapter profile, PLC signal, Edge node, replay batch, sync conflict, asset, LOTO/permit | Offline window, checkpoints, replay/conflict decisions, support session, permit/LOTO and verification. |
| Platform, Integration & Lifecycle | 1,2,3,4,5,6,7 | API client, endpoint, mapping profile, event schema, outbox/inbox, DLQ message, replay job, release | Contract/version, mapping diff, test result, approval, replay lineage and release/rollback record. |
| Governance, Commercial & Compliance | 1,2,3,5,6,7 | Tenant, role/scope, approval, entitlement, usage record, billing export, audit event, evidence package | Authority at action time, approval chain, before/after, usage source, manifest/hash and export register. |
Core / Site / Edge deployment
Reference design schematic, not a statement of production deployment.
Supply and confirmation sequence
Reference design schematic, not a statement of production deployment.
Identity and trust boundary
Reference design schematic, not a statement of production deployment.