How is the project assessed?
Software does not replace the production process in a lean initiative. Choose an observable loss such as waiting, rework, downtime or delayed information first. Agree how to record and compare it with the operational team.
Manual observation, machine counts and event records can support the same analysis. Definitions must remain consistent across shifts. A report is valuable because of the decision it supports, not the number of charts it contains.
Keep the baseline, trial and review separate. Product mix and shift changes can affect results, so an improvement cannot automatically be attributed to software. Build the scope from the loss definition and collection plan.
Example system flow
- 01Loss definition
- 02Shop-floor record
- 03Comparison
- 04Improvement decision
Information for technical review
- Loss to measure
- Shifts and product mix
- Baseline and decision owner
Capacity, timing, compatibility and price are defined in the technical offer after samples, site data and scope are reviewed. This page does not make unverified performance or certification claims.
Related solutions
Questions before a project
Will it work with our existing system?
The team reviews machines, PLCs, software and interfaces. Compatibility, connection responsibility and additional hardware are defined in the technical offer; universal compatibility is not assumed.
Can we start with a pilot or trial?
Start with a limited task and acceptance criteria. Samples or site data define the trial, measures and next decision. Pilot availability and terms are agreed for the specific project.
Does installation stop production?
Connections and safety requirements may need a planned stop or test window. Agree the schedule with production and maintenance teams; zero downtime is not guaranteed.
How are capacity and price determined?
Product or load samples, target flow, conditions and integration scope are reviewed. The final configuration and commercial offer are based on these inputs.
How are data and software interfaces planned?
Define data sources, interfaces, permissions, retention and recovery responsibilities. On-site or cloud deployment is assessed against the customer environment.
What is the service and maintenance scope?
Discuss maintenance access, training, spares and remote support in the offer. Coordination with STU Servis is available through the group; warranty and response commitments require a written scope.
Your project enquiry
Send your contact and project details. Your enquiry is saved in the private enquiry system and a reference is shown on this page.