Provenance
Every number traces back to the system that produced it and the rule that interpreted it.
Artiplane · enterprise AI platform
Five layers. From data to executed work.
Each layer has a precise responsibility and talks to the next through versioned APIs and events. Systems remain the source of truth: Artiplane reads them, reorganises them and makes them operable by AI.
- 5layers, one model
- 35catalogued apps
- 6.060process variants
Architectural principle
Reorganise information, never duplicate it.
The first layer is the only one that touches source systems. Upper layers work on shared entities, processes and policies; every value keeps its link to the source and every write returns to systems only through authorised actions.
01Knowledge — Artiplane Bridge
Knowledge — Artiplane Bridge
Read-only connectors via API, CDC, files and events. Bridge documents applications, data, code and screens and publishes objects with lineage, permissions and freshness.
02Semantic — domain model
Semantic — domain model
The same entities held in ERP, PLM, POS and CRM are reconciled into one model (product, variant, season, stock, customer). Exposes Entity API and a semantic index.
03Organization — Process Engine
Organization — Process Engine
Versioned BPMN processes with roles, thresholds and approval gates. Every task knows which systems it uses, which data it reads and who decides.
04Orchestration — Orchestrator
Orchestration — Orchestrator
Breaks objectives into tasks and coordinates AI agents, LLMs, n8n workflows and systems with queues, retries, idempotency and human control.
05Experience — Super App
Experience — Super App
Role-based operational views combining several systems: priorities, evidence and actions ready to approve, with outcomes recorded in audit.
Documents systems, processes and data. And gives your systems a second life.
Bridge connects read-only to authorized systems and reconstructs how the company really works: applications, data, code, screens and processes. The result is a living corporate second brain that AI and people can query.
Existing systemsSAP S/4HANASAP ECCSalesforceAS/400WMSPLMSharePoint
BridgeScanning
Knowledge producedApplication mapData dictionaryAs-is processesCode and rulesScreens and flows
- 01Governed scan
Approved scope, least-privilege credentials, no writes.
- 02Documentation
Application map, data dictionary, code rules and user flows.
- 03Validation
Owners confirm gaps and answers before publication.
- 04Second brain
Validated knowledge feeds Process Engine, Orchestrators and Super Apps.
No migration.
SAP, AS/400, WMS and custom applications stay where they are. Bridge makes them understandable and usable by AI, extending their useful life.
- Stock signal
- AI analysis
- Proposal
- Approval
- ERP order
From documented processes to executed work.
The Process Engine turns knowledge into executable BPMN processes: every step knows which systems it uses, which data it reads, who decides and where AI can help.
- Real processes
Lanes, gateways and human approvals on pre-mapped Fashion models.
- Every task connected
Systems, data, roles and AI agents for each step.
- Measurable runtime
Time, cost and criticality to see where to act.
- AI where it matters
Proposals only on manual, automatable tasks.
- 6,000+
- pre-mapped processes
- 320
- preconfigured agents
- 18
- Orchestrators
Intelligence, under control.
Every action is authorized, traced and consistent with business processes.
Architecture and security- Role-based access
- Human approvals
- End-to-end audit
- SHA-256 integrity
- Encrypted storage
- Configurable retention
- AI provider of choice
- Cost control
Cross-cutting guarantees
Two rules apply in every layer.
Authorisation
No action reaches a system without permission, policy and, where required, human approval.
Inside the product
Five layers, five real screens
Select a layer to see it in the console.
Real product screens · Atelier Nova Group reference tenant
From signal to action
How the five layers work together
Example: a line’s sell-through drops in three stores. Each layer adds a piece; none duplicates data.
01
Knowledge
Bridge reads POS sales and ERP stock where they already live.
02
Semantics
SKU, size, colour and store are reconciled on the fashion model.
03
Organisation
The Process Engine triggers the reallocation process and its owner.
04
Orchestration
The Orchestrator computes the proposal with the authorised LLM and thresholds.
05
Experience
The planner sees the proposal in the Super App and approves it.
Explore the platform layer by layer.
Every layer described on this page can be navigated in the demo.