Skip to content

Manufacturing execution

Generated from the architecture model

This page is rendered from model/**/*.yaml by tools/docs_model during mkdocs build. Edit the YAML, not this page; hand-written design lives on the linked service, platform and plane pages.
Vertical MES
Prototype reference MES prototype (ConnectSoft.DesignPrototypes)
Managed edition Managed (D33, D34)
Data residency on-prem or tenant-region (D31)
Catalog Examples catalog · Vision-to-Production path for this vertical

Business problem

Work orders, machines and quality data are disconnected; traceability of a batch takes days.

Product intent

Work orders, routing, machine integration, quality checks and batch genealogy with an on-prem profile.

What the Factory makes different here: on-prem topology with the same contracts; machine events through inbound connectors.

Vision-to-Production path for this vertical

Step Factory platform Agents Blueprints
Vision and product plan Agent Mesh, Control plane Enterprise Architect Agent, Integration Architect Agent vision
Architecture and domain Template & Library (BC-02) Enterprise Architect Agent service, module, integration, database
Experience Template & Library, Factory Studio UX track UX Designer Agent, Frontend Developer Agent —
Recipe and generation Template & Library (BC-15), Agent Mesh, Tools & MCP Enterprise Architect Agent, Integration Architect Agent, Backend Developer Agent, QA Agent, Infrastructure Architect Agent module plan from the context map
Quality Observability (BC-22), DevOps / GitOps QA Agent test
Delivery and provisioning DevOps / GitOps (BC-23, BC-24), Runtime Cloud (BC-25) DevOps Agent, Infrastructure Architect Agent infrastructure
Operations Product Fleet Operations (BC-35..37) — handover, objectives, rollouts, incidents, off-boarding

Delivery workflows exercised: deployment-and-observability-workflows.

Generated product shape

C4Context
    title Manufacturing execution system context
    Person(user, "Users", "MES users and operators")
    System_Ext(factory, "ConnectSoft AI Factory", "generates, delivers, provisions and operates the product")
    System_Boundary(product, "Manufacturing execution") {
        System(ctx_Orders, "Orders", "work orders, routing")
        System(ctx_Execution, "Execution", "operations, machine events")
        System(ctx_Quality, "Quality", "checks, nonconformances")
        System(ctx_Genealogy, "Genealogy", "batches, lots, traceability")
    }
    Rel(user, ctx_Orders, "uses through the product gateway GW-07")
    Rel(factory, ctx_Orders, "descriptor, health, rollouts, incidents, off-boarding")
Hold "Alt" / "Option" to enable pan & zoom

Bounded contexts

Context Responsibility Published events
Orders work orders, routing OrderReleased
Execution operations, machine events OperationCompleted
Quality checks, nonconformances NonconformanceRaised
Genealogy batches, lots, traceability BatchClosed

Modules and templates

Module Template Notes
Microservice ×4 connectsoft-microservice
Worker (machine ingestion) connectsoft-microservice
Shop-floor shell connectsoft-blazor-shell
Every product also gets the SaaS foundations (tenants, editions, entitlements, billing, metering) and the product host shape (descriptor, health, operations handover) unless it is a library-only product.

Prototype reference

MES prototype in ConnectSoft.DesignPrototypes shows the intended screens; the UX track (U1–U4) maps prototype destinations to the UX model's screens with keep, merge, rename, retire or new decisions.

Operations as a managed product

Managed through enrolled pools or self-operated on-prem.