Skip to main content
NOVYRON

DELIVERY WORK

Selected delivery work, shown in engineering detail

We document delivery work in one consistent format: operating context, challenge, inputs, system boundary, workflow and outcome. Client identities, site details and performance figures remain confidential unless publication is approved.

PROJECT 01MANUFACTURING

Digital twin of an automated packaging cell

CONTEXT
High-volume packaging cell: two robots, conveyors, vision check, manual end-of-line
CHALLENGE
A planned product changeover threatened throughput; physical trials would cost production days
INPUTS
Cell layout, cycle and takt data, PLC signal logs, demand profiles
SYSTEM
Simulation & Twin module; scenario runs for three layout / buffer options
WORKFLOW
Model → validate against recorded weeks → compare scenarios → virtual commissioning of the selected option
OUTCOME
Commissioning-risk reduction; changeover decision made on evidence, parameters handed to the floor pre-validated
SIMULATION & TWINRelated solution

ARCHITECTURE

Twin architecture: layout and cycle data from CAD and PLC logs, plus demand data from the historian, feed a twin running three scenarios. The twin produces a comparison of units per hour, utilisation and queueing, and a validated parameter set handed to the floor.

RESULTS SHOWN AS CATEGORIES · QUANTITATIVE CLAIMS REQUIRE WRITTEN EVIDENCE

PROJECT 02MANUFACTURING · QUALITY

Visual inspection on a high-mix component line

CONTEXT
Component line with frequent changeovers and dozens of active part variants
CHALLENGE
Manual inspection missed intermittent surface defects; no structured record per unit existed
INPUTS
Multi-camera streams, part specifications, historical reject samples, synthetic data for rare classes
SYSTEM
AI Perception with review queues; Guidance gates for borderline lots
WORKFLOW
Detect with confidence per unit → queue low-confidence frames for QA verdicts → verdicts feed evaluation → weekly quality reports
OUTCOME
Quality consistency; every unit carries an audit-ready inspection record
AI PERCEPTIONGUIDANCERelated solution
PROJECT 03INTRALOGISTICS

Orchestrating a mixed robot fleet with the WMS

CONTEXT
Warehouse zone with AMRs from two vendors, a picking arm and conveyor handoffs
CHALLENGE
Vendor systems didn't coordinate; handover failures stalled lanes and every exception needed three consoles
INPUTS
Robot vendor APIs, WMS task queue, conveyor PLC signals, zone map
SYSTEM
Robotics Orchestration with vendor-neutral adapters; Guidance for exception approval
WORKFLOW
WMS task → dispatch across fleet → live state per participant → exceptions pause to safe state → operator resolves from one console, logged
OUTCOME
Coordination reliability; exceptions resolved in minutes from a single console
ORCHESTRATIONRelated solution

ARCHITECTURE

Orchestration architecture: WMS tasks, two vendors of AMR fleet, and a picking arm with conveyor PLC all connect to one orchestrator holding states and handovers. It drives a single live operations console and routes exceptions into a defined safe state.

VENDOR NAMES ILLUSTRATE INTEGRATION SURFACE, NOT ENDORSEMENT

CLIENT CONFIDENTIALITY

Client identities and sensitive site details are withheld unless publication is approved. Quantitative results are shown only when they can be supported and released; otherwise we state the verified outcome category.

Bring us your operating context

Share the process, interfaces, constraints and target outcome. We will use the same structure to frame a technical discussion.

Discuss a ProjectSee the five modules