Deployment does not start with an installation. It starts with a conversation. Together we go through the journey the material makes from the supplier to the workstation, and decide which parts of it CALS will steer. That same conversation produces the system settings, the content of the training and the measures of success.
Scoping
Training
Deployment
SupportThe questions are about how you work, not about our software. Scoping is not about choosing modules or settings. We talk about who decides what is needed, who moves the goods, and what happens when a delivery is wrong. The technical choices follow from the answers. “No” and “I’m not sure yet” are also correct answers.
Many things only surface when someone asks: whose memory the material need depends on, who actually orders the transfers, what is done about a shortage today. The whole picture is usually scattered across several heads.
Lead times and order margins are set according to where you want to get to. In the current state the answer is always “it depends”. In the target state there is a clear answer.
Suppliers, storage and logistics are gathered into one picture. Most often it is wider than it feels day to day, and it is exactly in that flow of information that the delays are created.
Specification follows a gate model. A gate either opens or it does not, and we only go through the questions that concern this project. Try it: select what describes your project.
Deployment takes from one week to a month, depending on how early in the project the scoping is started.
We go through the project, the material flow and the parties involved. We record what has been confirmed and what is still open, so that an unfinished point does not quietly turn into an assumption. The result is a description of how material moves and who does what. Scoping takes the main user hours, not days.
The content of the training comes from the scoping: each role learns their own work, not the whole system. If CALS is already familiar to you, we do not teach it again — the project-specific features are enough.
Suppliers, the warehouse partner and the logistics operator are trained as their own groups. You can run the training yourself or leave it to us.
The system is opened with the settings agreed in scoping: workspaces, locations, phases, roles and target values are in place before the first day of use. Users are invited by email, and the number of users does not affect the price, so it is worth including everyone the information helps.
Some settings are deliberately adjustable. Target values for lead times and order margins are refined once you see how the site actually works.
The support channel opens on the same day as the system. The first weeks decide whether the new way of working stays in use. Help has to arrive in minutes, not the next day.
Everyday questions are answered in the support channel: how do I record this, why is this not showing, who has access to this. Support is available to main users at the start of the project.
For further needs, further training is available: introducing new parties mid-project, changes to the process, and analysis of how the system is being used when you want to develop the way you work on the basis of the data you have collected.
Support
+358 10 327 7601
support@c4.fi
Support is available in English.
The first conversation takes an hour and already tells you a lot about where your material flow is getting stuck.
