Skip to content

Architecture

How is Qynetic architected?

Qynetic Edge reads machine signals at the site. The platform keeps each event with its source and timestamp so the same record can be used for shift reports, quality analysis and traceability.

  1. 01

    Machines

    metrology · systems

  2. 02

    Connectors

    Qynetic Edge

  3. 03

    Canonical core

    Canonical model · events · provenance

  4. 04

    Modules and agents

    Factory Director

  5. 05

    People approve

  • Multi-tenant hierarchy

    Organisation → site → area → machine. A user may belong to several organisations and sites; nothing assumes one company, one factory, one machine type or one process. Sites own their time zone, locale and units.

  • Canonical manufacturing model

    Machines, tools, programs, articles, characteristics, measurements, quality events, offsets and maintenance are modelled once, independent of vendor. Internal identifiers are UUIDs; external identifiers and provenance are kept separately.

  • Connectors and Edge

    Connectors translate vendor protocols into canonical events and run in the cloud or in Qynetic Edge inside the factory network, which connects outbound only.

  • Factory Director

    The demo sorts example recommendations by severity and confidence. Each item shows its supporting records so the shift team can decide what to investigate.

  • APC safety pipeline

    APC separates a recommendation, a proposed correction and a verified physical change. A policy check may reject a proposal or require review. An approved proposal still needs a commissioned machine writer and readback to establish that the machine changed.

  • API-first

    Qynetic exposes a versioned API (/api/v1) whose contracts are independent of the database schema, so integrations keep working as the platform evolves.

  • Observability

    To trace a delay, compare the source timestamp, when available, with the observation time in Edge and the receipt time in Qynetic. Check the local queue and any rejected events before interpreting a quiet dashboard as an idle machine.

How a tool correction file is approved

  1. Offset request
  2. Current offsets
  3. Limit checks
  4. Named approval
  5. File hand-off

Approval applies to the reviewed values. A separately commissioned local writer and a readback are needed to verify any change at the machine.

The event envelope

Every ingested or generated fact is wrapped in a consistent envelope, regardless of source:

Follow one finished part

A mill has counted 40 parts. Follow the next one through a connection loss and a retry.

Machine counter
40
Events queued on Edge
0
Parts added in Qynetic
0

Edge takes 40 as the starting value. The first reading establishes a baseline for this counter.

event_id / event_type
Unique id and a type such as measurement.recorded
tenant_id / site_id
Which organisation and site own the event
source / source_id
Which integration, edge node, user or agent produced it
entity_type / entity_id
What the event is about
occurred_at / received_at
When it happened at the source and when Qynetic received it
schema_version
So payloads can evolve safely
payload / metadata
The data, plus provenance such as transformed and confidence

Book a call about your factory

Tell us what you make and which machines you run, and we will walk through how Qynetic fits. If you would rather get news and early access, join the waitlist.