The situation we usually begin with
In the office, it is clear what the company has sold and invoiced. On the shop floor and in the warehouse, information arrives late: job progress becomes known after the shift or a week later, stock figures match only the first inventory count, and the reason a batch was delayed remains in a supervisor's notebook.
Companies rarely present this as one problem. They ask about a specific system because someone said that is what should be implemented. Before choosing one, it is worth finding where information is lost, because introducing a system into an undocumented process simply moves the same gap somewhere new.
Job status is known only after the fact
Production progress is reconstructed from paper notes, a board and conversations. Delivery estimates are based on experience rather than data.
Stock levels are an estimate
The system shows one figure and the shelf another. The difference is investigated during inventory or when an item needed for dispatch runs out.
Machine knowledge exists only in people's heads
Who serviced what, what failed and what must not be done is absent from every system. A failure then costs twice: first in downtime, then in finding someone who knows what to do.
What this area covers across the Group
We begin with one part of the operation, not the entire plant. The greatest risk here lies not in the software but in its adoption by people working shifts, and that is best tested on a small scope before expanding.
Production workflow
Recording what happens to a job on the shop floor: where it is, what has been completed and what is blocking it. This layer is known as an MES, but we begin with a simpler question: do you want to learn about a delay while it is happening or after the shift?
Movement of goods and transport
Receipts, storage locations, picking and dispatch, together with planning what travels where and how. The warehouse layer is often called a WMS, but its purpose is simple: the figure on the screen should match what is on the shelf.
Machinery and maintenance
Records of equipment, inspections, repairs and failure history. This organises knowledge currently held by specific people and makes it possible to plan downtime instead of merely reacting to it.
Who leads such a project
Three Group companies share this area. The nature of the project determines which one becomes involved.
GOTOMA Software House
When software must fit the way the plant operates: implementing a manufacturing or warehouse system, integrating it with existing tools and adding functionality unavailable as standard.
GOTOMA.pl ›GOTOMA GENERAL
When the project extends beyond software: the network and hardware on the shop floor, devices for harsh environments, operational data infrastructure, multiple plants or investment financing.
GOTOMA GENERAL ›Codarius
When organised product and availability data needs to power online sales channels.
Codarius ›You do not need to decide this before speaking with us. Describe one part of the operation where information is currently lost and we will divide the work internally.
AI solutions
In manufacturing and logistics, the AI conversation usually begins with documentation, not machines. Instructions, specifications, reports and technical correspondence take considerable time to search, and this use case does not require data from machinery or shop-floor systems.
Anything involving data directly from production or the warehouse is a separate subject and a separate project. To learn more, see GOTOMA GENERAL > AI for industry and operations.
Whatever the application, we set the same boundary: the system prepares and suggests, while decisions with consequences – such as releasing a batch, approving dispatch or stopping a machine – remain with the people responsible. We treat this as a design principle, not a configuration setting.