PLATFORM MODULEPILOT READY

Connector & Integration Platform

Use domain-specific adapters over shared API, event, workflow, semantic mapping, retry and reconciliation capabilities.

Review module scopeRelated architecture
P06Architecture
PILOT READYMaturity
Domain-qualifiedAuthority
SCOPE

What the module does—and what it deliberately does not do.

A clear negative boundary is part of the product definition.

DOES
  • API gateway, event bus, workflow, mapping, connector contracts, degraded mode, reconciliation and exit controls.
  • Publishes explicit domain objects and version-aware interfaces/events.
  • Links business outcomes to evidence and architecture references.
DOES NOT
  • Does not replace external legal/identifier authorities.
  • Does not imply universal certification or conformity.
  • Does not make optional assurance mechanisms mandatory for all products.
OPERATING MODEL

Actors, inputs, outputs and authority remain explicit.

The module is not treated as a black box; its authority and evidence responsibilities are visible.

Actors

Connector owner · External authority/service · Platform operations · Developer

Inputs

Identity/context, versioned business data, policy inputs and external-source references as applicable.

Outputs

Versioned decision/data/evidence artifacts with correlation and provenance.

Authority boundary

Qualified by data domain; external authority is not absorbed through integration.

BUSINESS OBJECTS

Semantic objects connect UI, API, repository and evidence.

The semantic registry prevents architecture vocabulary from drifting between portals and integration contracts.

Connector & Integration Platform object mapping
IDObjectAuthorityRepository roleAPIArchitecture
OBJ-001ThingDomain-qualifiedThing MasterResolver APIP01/P03
OBJ-002ProductEconomic operator / applicable authorityThing MasterDPP APIP03/P04
OBJ-003ModelOfficial identifier domainThing MasterResolver APIP03
OBJ-004BatchOfficial identifier domainThing MasterResolver APIP03
OBJ-005ItemOfficial identifier domainThing MasterResolver APIP03/P04
OBJ-006Official IdentifierExternal / scheme authorityExternal source + alias mapResolver APIP01/P03
POLICY & EVIDENCE

Material actions are policy-versioned and evidence-linked.

Where the module changes a material state, the transition grammar applies.

Event
+
Authorized actor
+
Precondition
+
Evidence
+
Trusted time
+
Policy / profile version
=
Resulting state
INTERFACES & EVENTS

Reference contracts are versioned and publication-gated.

The public API package is a reference contract; actual deployment availability must be confirmed by release/environment.

GET /v1/connectors
POST /v1/connectors/{id}/reconcile
GET /v1/connectors/{id}/health
RELEASE GATE
SELECTINTEGRATETESTAPPROVEOPERATE

Publish support only for the exact version/profile/environment that has supporting evidence.

STANDARDS & LIMITATIONS

Mapping is not certification.

Standards are shown with status and implementation wording so reference mapping is not mistaken for assessed conformity.

Relevant standards
ReferenceStatusOJEUImpactImplementation
EN 18216:2026HARMONISEDOJEU CITEDIntegration protocol mappingMAPPED
EN 18223:2026HARMONISEDOJEU CITEDConnector/conformance modelMAPPED
EPCIS 2.0ECOSYSTEM STANDARDN/AConnector / semantic mappingTRACKED
ISO/IEC 30141:2024INTERNATIONAL STANDARDN/ADevice / integration architectureSUPPORTING
IEC 63278-1INTERNATIONAL STANDARDN/ASemantic/integration mappingSUPPORTING
RELATED MODULES

Compose capabilities without collapsing responsibilities.

Related modules are linked explicitly rather than hidden behind one monolithic platform claim.

Thing Identity & Resolver

REFERENCE IMPLEMENTATION

Resolve official identifiers, correlate aliases and extend assurance without redefining the authoritative product identifier.

Explore

Identifier Governance

REFERENCE ARCHITECTURE

Govern namespace uniqueness, persistence, collision detection, supersession and the rule that identifiers are never silently reused.

Explore

DPP Regulatory Engine

PILOT READY

Apply versioned product-group profiles, authoring controls and registry orchestration while keeping external legal authorities authoritative.

Explore
PRODUCT COMPLETENESS

From module to business outcome.

Coordinate API, event, workflow, connector, reconciliation, observability and administration without absorbing external authority.

INPUTIdentifier / policy / evidence / source status
OUTPUTSource-aware, policy-qualified result with evidence context
AUTHORITYQualified by data domain; external authority remains external
API / EVENTConnector API · events / asyncapi
EVIDENCEConnector status · retry/reconciliation trail · integration audit
MATURITYPilot ready
Open Product EcosystemView Readiness
ARCHITECTURE WORKSHOP

Turn the architecture into a scoped pilot.

Align product-group applicability, authority boundaries, portal journeys, integration contracts and evidence before committing to production claims.

Request a workshopExplore architecture