Pour les architectes usine connectee, IT et OT

Architecte usine connectee

Les machines publient via MQTT. Le contexte ERP arrive par REST. Les agents IA se connectent via MCP. Chaque point d'integration est type, documente et deploye comme service Docker-natif en edge — propriete de l'usine, pas du fournisseur.

check_circle
Inspecter la topologie edge
check_circle
Tracer les contrats de donnees
check_circle
Verifier les points d'integration
flag
Deployer un service custom

A Single Pane of Glass

Explore the Unified Namespace directly from the architect view. Search live MQTT topics, inspect machine paths, and watch the factory data model breathe.

Reconnecting…·0 topics
Waiting for the first messages…
Connected to the factory broker. Topics will appear here as data starts flowing.

Typed Control Plane

Integrate through a typed control plane, not a pile of ad hoc endpoints. PREKIT uses a standard OpenAPI surface as the metadata and discovery layer.

  • check_circleAuto-generated clients from the OpenAPI schema for typed integrations.
  • check_circleSignal discovery by semantic contract instead of hardcoded topic guessing.
  • check_circleSystem elements, permissions, annotations, and service inventory live behind one API.

Relevant for ERP, MES, historian, and partner applications that need discovery before subscription.

GET /api/v1/signals/?implements_contract=EdgeExecutionContext
{
  "results": [
    {
      "name": "execution-context",
      "data_type": "json",
      "implements_contract": "EdgeExecutionContext",
      "topic": "alp/v1/_Metric/factory/conching/unit-04/execution-context"
    }
  ]
}
smart_toyDemandez n'importe quoi a l'usine

Assistant technique en direct

Utilise la meme usine en direct, ERP, topologie et surface d'outils MCP curee qui alimente l'assistant public.

Gouvernance et identite

La meme plateforme qui ouvre l'usine controle egalement qui peut voir, publier et modifier quoi.

fingerprint

IAM

Keycloak avec OAuth2 / OIDC

policy

RBAC

Controle d'acces par roles et par namespace ISA-95

key

Namespaces

souscrire / publier / lire / ecrire

vpn_lock

mTLS

Confiance entre services

workspace_premium

PKI privee

Certificats emis par Smallstep

Modele de securite
roles:
  - prekit_admin
  - prekit_editor
  - prekit_viewer
namespace_scopes:
  - subscribe
  - publish
  - read
  - write
  - annotate
  - delete
mqtt_auth:
  - certificate-based
  - keycloak tokens
service_to_service:
  - mTLS
  - private PKI

Contrats semantiques

Les contrats semantiques preservent le sens de l'execution a travers l'ERP, les machines et les agents.

EdgeExecutionContextVALIDE

Published on the signal’s normal PREKIT _Metric topic. The contract lives inside Metric.value_json.

Discover via GET /api/v1/signals/?implements_contract=EdgeExecutionContext

event_type: execution_start
asset_id: 4
lot_nr: 23018
timestamp: 2026-04-04T07:42:18Z
source: plc_auto
order_nr: 992
step_id: 2
operator_id: OP-17
context:
  recipe: Dark 78%
  shift: A

Deployer des services personnalises dans le namespace

deployed_codeDocker

PREKIT genere des deploiements Docker Compose a partir du YAML edge. Les services personnalises sont declares dans la specification du noeud, enregistres dans l'inventaire de services, et peuvent publier leurs propres ServiceDetails dans la meme architecture.

custom_services:
  - name: chocolate-ai-copilot
    service_type: agent
    description: Partner-provided orchestration service

# declared in node YAML
# added via docker-compose.override.yaml
# registered into PREKIT service inventory

Comment PREKIT le rend inspectable

  • check_circleGenerate: `prekit generate <node>` renders the compose package.
  • check_circleRegister: service name and `service_type` are added to PREKIT’s service inventory.
  • check_circleObserve: architecture metadata and KPIs let the service appear in the architecture layer.
  • check_circleGovern: mTLS, PKI, and namespace rules apply across the same runtime.

Inspectez cette pile avec votre propre integration en tete

Cette usine reste publique a dessein. Si vous souhaitez comparer votre propre connecteur, service ou flux d'agent avec le meme contexte en direct presente ici, utilisez cette demo comme point de reference.

Contacter Alpamayo