Delivery sequence
Eight stages, each one closed by a result taken from your own parts
The sequence is ordered so that every decision downstream is made on a measurement taken upstream. Your own materials are marked and the parameter set that produced the mark comes back with them, before a number goes on a quote. The software is configured against your part library and your machine profiles before the system leaves the bench. The first-run validation pass runs your real artwork on your real stock before the install is signed off. Your operators learn the system by running jobs the plant was going to run anyway. Same order every time, so you know what is coming and what we need from you at each stage.
- Capability marking on your own material, returned as a result you can hold with the parameters that produced it, before anything is quoted
- The same controller-aware core that drives the industrial marking layer, written in Nelson, configured to your part library, materials and machine profiles
- Hardware, module set, software configuration, install, training and support tier priced as separate lines, so every line is read against the work it does
The engagement, stage by stage
The detail changes with the plant. The order does not. Each stage below states what happens, what you provide, and what the stage produces that the next one is built on. A production line or a multi-site programme runs the full delivery sequence instead, set out on how we deliver.
- Step 1
Scoping call
Thirty to forty-five minutes, usually by video call. What you make, how it is produced today (sent out, partly in-house, or a mix), and the volumes that genuinely move the case. What you provide: your product range, your current process, and production numbers as they actually run rather than as they are remembered.
Why it matters: The numbers taken here size everything after them, so they are taken from your production record at the start rather than corrected three stages later.
- Step 2
Product and volume review
The specific products, substrates and run sizes that would move through the system, alongside the floor space, power supply and team capacity around it. What you provide: photos or samples of representative products, your typical order sizes, and the seasonal and growth pattern in the volume.
Why it matters: Hardware and modules are sized against the products you actually run, including your busiest month rather than a generic average of it.
- Step 3
Capability marking on your own materials
Before anything is quoted, test marks and test cuts are run on your actual stock rather than on a showroom sample: how the substrate reacts to the energy put into it, the parameter set that holds the result, and the finish under the conditions you name. What you provide: physical samples of the materials you would be running. The marked samples come back to you with the parameters that produced them.
Why it matters: A machine specification sheet states what a head does. This states what your substrate does under the beam, and it puts a measured result in your hands before a number is written on a quote. Coated, anodised and mill-finish stock behave differently enough between suppliers that the parameter set is established on the batch you actually buy rather than on the material name.
- Step 4
System design and itemised quote
A proposal listing the recommended hardware, the module set, the software configuration, the install plan, the training plan, warranty options, the support tier and the total price as itemised line items. Where the work carries a machine readable code, the proposal states the symbology and the accept grade with it: Data Matrix generated to ISO/IEC 16022 and graded per ISO/IEC 15415, linear symbologies per ISO/IEC 15416, accepted at the grade the scanner class in your operation supports. What you provide: sign-off or feedback, and any change to the brief that surfaced during review.
Why it matters: Itemised pricing shows what each module and each service earns, so a line that does not earn its place comes off before the quote is signed.
- Step 5
Build and configuration
Once approved, the hardware is ordered through the relevant distributor, the modules are built, and the software is configured against the part library, the materials and the machine profiles confirmed earlier. What you provide: final artwork, part files, or the job data the software configuration composes from.
Why it matters: Configuring the software before install rather than during it makes day one about proving the system in your space instead of building it there.
- Step 6
Delivery and install
Physical setup, calibration, extraction and safety setup where the install calls for it, software install on the operator machines, and a first-run validation pass on your real materials and your real artwork. Class 4 laser safety is enclosure, interlocks, beam containment and a rated safety circuit, specified to ISO 11553-1, IEC 60825-1, IEC 60204-1 and ISO 13849-1, and it sits in the install specification rather than beside it as an accessory. What you provide: the floor space and power confirmed during scoping, and access for the install team. The install closes when the system is producing parts to specification.
Why it matters: Validating on your actual jobs before the team leaves means the first thing your operators run is not the first thing that ever came off the machine.
- Step 7
Operator training on real jobs
Your team learns the system by running jobs that were going into production anyway, covering normal operation, common troubleshooting, material handling and routine maintenance, until they run it without us in the room. What you provide: operator time, ideally the same people across the training period. At least two operators go through it, and the procedure they end up following is written during the sessions rather than after them, so what lands in the handover pack is the way your plant actually runs the job.
Why it matters: Training on live work is what transfers. It is the difference between a team that runs the system and a team that watches someone else run it.
- Step 8
Support and expansion
At handover you hold the documented setup, the saved machine profiles, a materials database populated with what you actually make, the operator procedure, the support tier scoped during the engagement, warranty documentation and software updates for the life of the system. Updates are fetched from a signed version manifest and every download is verified against a published SHA-256 checksum before installation. What you provide: a heads-up when the product range moves, so the next scope is planned rather than reacted to.
Why it matters: A parameter set that is written down is recovered rather than rediscovered, and a new product family becomes a parameter set rather than a rebuild.
The core the system is configured on, published raw
The figures below are lifted straight from the core, unedited. A business system is that core configured to your parts, which is why this page and the engineering pages quote the same numbers rather than two sets of them.
A business system usually drives a controller the plant already owns, or one bought off a distributor's shelf, so the output side is where that configuration shows first. Power scaling alone is four quantisations of the same physical intent: an internal 0 to 10000 range mapped onto the GRBL $30 value read live off the controller at connect time, the Marlin 0 to 255 integer, Smoothieware 0 to 1.0 at four decimal places, and Generic 0 to 1000. Ruida runs as an external bridge and is labelled alpha. A golden fixture suite holds emitted machine output stable across three dialects, 42 fixtures across two images and seven processing variants, with a conformance validator checking output against the dialect rules, so a change to the geometry engine cannot silently change what your machine does after an update.
Raster work is built on colorimetric physics rather than a brightness slider: bilinear resize to target DPI, sRGB to linear luminance using the Rec.709 coefficients 0.2126R plus 0.7152G plus 0.0722B, percentile clipping at the 0.5th and 99.5th, auto levels, exposure, contrast around the 0.5 midpoint, gamma, and emission with serpentine rows, 2.5 mm overscan for velocity stabilisation and inline power quantised into 50 steps. We treat the image as a light source, not as a picture. A head decelerating into a corner deposits more energy per millimetre than a head at cruise, which is what burns corners, so power is modulated against actual velocity, and the software reads the machine's own $30 and $31 registers at connect time and queries $110 and $111 to derive the effective maximum feed rate. Constant power is not a constant result, and the software asks the machine what it can do rather than assuming it.
The heat map preview draws the generated toolpath colour coded by power rather than the source artwork, so a setting is judged on screen instead of on the workpiece. The stop system has three levels, and the recovery sequence soft resets, flushes buffers, drains the controller boot chatter, verifies status, clears alarms and restores the user origin. Stopping a laser is easy. Bringing it back to a known coordinate frame afterwards is the engineering, and it is the difference between a stopped job and a scrapped part.
Where the boundaries sit, written into the proposal
The scope is settled on paper at design stage, so what each side owns is fixed before the build starts rather than negotiated during the install.
What every engagement carries
Every system ships with install, calibration, a first-run validation pass on your own jobs, operator training on live work and a support tier scoped before commissioning. The system is sized against the volumes measured at the product and volume review, so it holds your busiest month without being specified for a plant you do not run. Every module and every service is quoted as its own line, and each line is read against the work it does.
- Install, calibration, operator training on your own jobs and an ongoing support tier are inside every system, scoped and priced as their own lines
- The systems already running the business keep the job, the batch and the code. The system reads them and puts the identifier on the part, so the plant keeps one source of truth
- Sizing follows the volumes measured at the product and volume review, and the sizing decision is shown with the numbers it was made on
- Where the arithmetic on a module comes out flat against your run rate, that is stated with the numbers attached at design stage, and the choice is yours to make with the cost in front of you
Three to twelve weeks from the first call to parts on site
Standard hardware with a standard module set sits at the faster end of that range. Custom modules, imported hardware lead times and site preparation move it out, and the three drivers are named against your engagement rather than averaged into a single figure.
The proposal carries a dated timeline built on the lead times quoted by the distributor on the day it is written. Imported hardware moves, and when a date moves it reaches you the day we hear it, with the revised sequence beside it rather than an apology attached to the original one.
What each stage closes on
Every stage produces an artefact you keep and the next stage is built on: a marked sample with the parameter set that produced it, a written specification, a validated first run on your own artwork, and a documented handover.
Read the engineering
The same core, the same physical engineering and the same published envelope sit behind a business system and behind an industrial marking line.
Start here
The controller-aware core
Dialect-neutral motion output, the raster and vector pipelines with their tolerances, the heat map preview and the machine profile system, at engineering depth.
Modules and rigs
Conveyors, rotaries, fixturing and jigs, extraction and filtration, safety enclosures and interlocks, vision alignment, and marking heads added into a cutter you already own.
Engineering specifications
The published operating envelope: the material matrix with its engineering notes, the source selection matrix, symbol grading and the measured speed model.
The full delivery sequence
Twelve steps from the first call to a signed-off marking line, with feasibility before specification and acceptance criteria written before the build.
Book a scoping call
Thirty to forty-five minutes. Bring your product range, the volumes as they actually run, and the materials you would put through the system. Post a sample ahead of the call and the marked result is on the table with its parameter set when we talk. Everything after that follows the same eight stages, in order.
Last updated August 21, 2026