Skip to content
Treblesys

Manufacturing & Industrial

Software that runs on the shop floor as well as in the office.

We build production, quality and planning tools for manufacturers whose processes live in machine outputs, paper travellers and an ERP that was configured a decade ago. The job is to connect all of that without stopping the line.

Discuss your projectSee related work

Constraints we build around

  • OT/IoT data from PLCs, CMMs and test equipment via OPC UA, MQTT and file exports
  • On-premise or hybrid hosting for sites where the network is segregated or air-gapped
  • Integration with ERP and MES systems (SAP, Dynamics, Epicor and others)
  • Traceability and audit requirements under ISO 9001, AS9100 and IATF 16949
  • Rugged devices, working offline, and usage that follows the shift pattern
  • Deployments scheduled around production, each with a rollback plan that doesn't stop the line
An engineer working at an automated production machine

What we hear

What people in this sector tell us on a first call.

  1. 01

    Data trapped in machines and paper

    CMMs, PLCs and test rigs all produce data, and inspection sheets and travellers are still on paper. Turning either into a report means someone sitting down and re-typing it.

  2. 02

    Customer paperwork as a bottleneck

    Certificates of conformance, inspection reports and traceability packs are put together by hand for every batch. The parts are finished and on the pallet, and the shipment is waiting on the paperwork.

  3. 03

    An ERP the shop floor doesn't use

    The ERP handles orders and stock. The shop floor runs on whiteboards, spreadsheets and whoever has been there longest. Planning, capacity and quality all live outside the system of record.

  4. 04

    Constraints most software teams have never met

    Air-gapped networks, on-premise servers, ruggedised devices, gloves, dust and shift patterns. Software designed for an office fails quietly in a factory, and the operators go back to paper without telling anyone.

What we build

The kinds of systems this sector tends to need.

  • Quality and inspection systems

    Capture inspection results from machines and operators, apply the acceptance rules, and generate certificates and reports from the same data. The traceability chain stays intact from raw material through to shipment.

  • Shop-floor data capture and dashboards

    Operator terminals and tablets for job status, downtime, scrap and OEE, feeding live dashboards and the ERP directly, with no whiteboard in between.

  • Document automation

    Pulling data out of PDFs, scanned inspection sheets and supplier certificates using OCR and LLMs. A person checks whatever the extraction isn't sure about, and the paperwork stops being a typing job.

  • ERP, MES and machine integration

    Integrations with SAP, Dynamics, Epicor and similar systems, plus OPC UA, MQTT or file-drop connections to the equipment, built to cope with networks that aren't always online.

  • Planning and scheduling tools

    Finite capacity scheduling, work-order sequencing and material visibility built around the constraints your planners already know about and the ERP's own scheduling module ignores.

  • Customer and supplier portals

    Order status, drawings, certificates and quality documents that customers can fetch for themselves, and supplier onboarding and document submission that doesn't run on email chains.

Related work

A project from this sector.

All case studies
Manufacturing & IndustrialSample

Automating quality reports and certificates for a precision manufacturer

A precision components manufacturer supplying aerospace and medical customers put together every certificate of conformance and inspection report by hand, from CMM outputs, paper inspection sheets and supplier certificates. We built a system that pulls the data out automatically, so QA engineers check values instead of typing them, and produces the customer paperwork in minutes where it used to take hours.

of QA engineer time saved per week across the team
~25 hrs
of QA engineer time saved per week across the team
fewer transcription errors found in customer paperwork
~80%
fewer transcription errors found in customer paperwork
certificate turnaround, down from two to three days
Same day
certificate turnaround, down from two to three days
Read the case study
Robotic arms on a car body assembly line

Questions

Questions that come up before a first project.

Ask us directly
Can you work with our ERP and machine data?

Yes. We integrate with ERPs through their APIs, database views or file interfaces, and with equipment through OPC UA, MQTT, serial or file-drop outputs. Before designing anything we run an integration audit to confirm what each system can expose in practice, because the documentation is often optimistic.

Our network is locked down. Can this run on-premise?

It can. We design for on-premise, hybrid or cloud deployment depending on what your IT and security people will allow, and use containerised services so the same software runs in any of them. Where the network is segregated, the whole thing runs on a box in the server room and cloud doesn't come into it.

How reliable is AI-based document extraction for quality records?

Good enough to take away most of the typing, provided a person still checks the output. We pair OCR and LLM extraction with confidence scoring, validation rules and a review step for anything uncertain, so QA engineers spend their time approving values instead of transcribing them. Every approved value stays traceable to the document it came from.

Relevant services

Other industries