This is the perimeter — the place where OpenEPCIS meets the rest of the enterprise. Operators ask the AI assistant natural-language questions about what's in the event store. All of this lives in the Business edition.

Object storage is pluggable. Any S3-compatible store and Azure Blob are first-class options, so the same captured EPCIS document can be archived to whatever the customer's environment already uses — AWS S3, on-prem object storage, Azure — without standing up a separate bucket or rewriting the capture pipeline.

The AI assistant is intent-routed rather than free-form. A prompt is classified into one of a small set of intents — EPCIS query, Digital Link resolution, vocabulary lookup, general chat — and dispatched to a typed handler that returns structured data (a translated query, a resolved URL, a vocabulary record) alongside the natural-language answer. The default model is local Ollama, so there's no third-party LLM dependency unless the customer wires one up explicitly.

The same discipline that the rest of the platform follows applies here too: an S3 file backfill, an AI-translated query — all of them go through the same validation, hashing, Digital-Link normalisation, tenant scoping and role enforcement that direct REST traffic gets. Integrations don't bypass the conformance contract; they're additional ways into it.

Capabilities by edition

See also

• Architecture → Authentication — how partner-facing services plug into the platform's identity model.
• Modules → EPCIS Events — where inbound documents end up.
• Roadmap — additional EDI envelope formats and a retrieval corpus for the AI assistant are pending.