Automation at the machine
Handing repetitive manual operations to robots, and managing the flow around the machine.
- Loading and unloading the machine
- Control and safety logic
- Operator panel in plain language, with alarms spelled out
Robotics & Automation
Automation that starts from the process, not the robot.
Scheduling at the machine, automated warehouses, production monitoring. We start from the bottleneck, not from the robot catalogue.
Or write to us: info@ggtechnologies.sm
1997
the first project
18
years in manufacturing
900
workers in the study
Where we start
Automation fails when you buy before you understand.
You see the result six months later: an island that works beautifully on its own and does not talk to the rest of the plant.
We start from the other end. We look at where time is lost, where mistakes happen, and where a piece of data already exists but nobody reads it. Then we decide what to automate — and what to leave alone.
We know because we did it from the inside, not as suppliers: years inside the information systems of two manufacturing groups. A process scheduler that reached down to the machine itself. An automated warehouse where a light comes on at the right location, instead of sending somebody to look a code up on a list. Production monitoring taken from the machines. And a system that followed the overhead conveyors — the lines parts travel along, hanging — to organise the work orders.
Experience
Software and automation for manufacturers since 1997.
Manufacturing
Years inside production, not the occasional project: scheduling at the machine, automated warehouses, process monitoring.
Technology
Machine control and data collection sit on our DigiSense® framework.
What we do on the shop floor
From the machine on the shop floor to the service robot in the home.
Integration with embedded systems
The machine does not stay isolated: it talks to line systems and to management software.
- Machine-to-line communication
- Production data collection
- Integration with existing ERP systems
Where the process loses time
Measure before acting: where the stoppages, scrap and idle time actually are.
- Cycle-time and downtime analysis
- Batch and part traceability
- Production dashboards people can read
Service robots and home care
Robots that live in a house, not in a factory: designed to assist frail and elderly people, and driven by voice rather than by a control panel.
- Driven by voice, spoken aloud
- Integration with the home's ambient sensors
- Electronics and firmware designed in-house
How we work
We measure the line before we quote for it.
01
Measure the line
Process analysis with the people who live it daily: operators and shift leads, not just management.
02
Decide what to build
Technology chosen for the goal, not for fashion. Sometimes the answer is not a robot.
03
Install
Development, integration with what exists and rollout without stopping the plant longer than necessary.
04
Train and maintain
Maintenance, operator training and evolution over time.
FAQ
Frequently asked questions
Where do I start if I do not know what to automate?
With measurement. First we look at where the process loses time or generates scrap: the bottleneck is often not where you expect, and the right intervention costs less than the one you were about to buy.
Do I have to replace my ERP?
Almost never. Automation sits on top of the systems and flows you already run. Replacing the ERP is a project in its own right: if it is needed we say so, with an estimate of what it involves — our chief executive put one into production as head of information systems.
What does Industry 5.0 mean in practice?
That the machine serves the person working with it, not the other way round: automation where the operation is repetitive or dangerous, and readable data where a human decision is needed.
Who answers for the machine's safety?
The builder, or whoever places it on the market: the risk assessment and the marking are theirs. We do the control, the integration and the data, and we write the logic on what the assessment established, alongside whoever signs it. That is how the machine stays compliant once we have automated it.
Who owns the code at the end of the project?
The code written for your project is yours and it is handed over. DigiSense®, the framework underneath, stays ours and is licensed to you: it is the part we reuse across every project. Who owns what is written into the proposal, before anything starts.
Can I speak to one of your clients?
Our work sits under confidentiality agreements and we keep them: a supplier who shows you other people's names will one day show yours. What we can give you is easier to check than a phone call. The software we sell can be downloaded and tried for thirty days. The method is written out in our articles, with the sources listed at the foot of each one. The wearable work sits inside a peer-reviewed study with a permanent identifier of its own. And we will gladly talk about the work we have done in plants: describing the problems, not the names.
How long does a typical project take?
It depends on the process, and an estimate made sight unseen would be worth nothing. Process analysis is the first phase, its duration is agreed before we start, and it ends with a document: what to automate, in what order and at what cost. From there the quote is about your process, not about an average.