Production, quality and maintenance, all connected.

From the order book to the production order.

• Customers — companies and individuals, with a unique tax ID and a history that is kept when you archive them.
• Orders — their own code (PED000001), filters, and OK/NOK progress part by part. An order is ready for delivery when every part has passed.
• Production orders — group one or more orders, with one line per unit, and say which machine they run on.
• Technical report — double-click a production to review, finish or cancel it, and mark OK/NOK in bulk.

Material worked out the way the machine uses it.

Each machine chooses how its consumption is worked out. Direct, when the slicer already gives the quantity. Or an Excel-style formula, written once on the machine's record:

= cuba_largura * cuba_profundidade * altura / 1000000 * densidade * taxa_renovação

The dimensions come from the machine model and the density from the material; whatever the system does not know — here, the height and the refresh rate — becomes a field to fill in on the production. The formula accepts a decimal point or comma, ; between arguments and functions such as MIN, MAX and ROUND.

Each material has a price per kg or litre, and each consumption keeps the price of the day. Changing the formula tomorrow does not change what yesterday's production used or what it cost.

Every NOK part with its cause and its fix.

Quality is recorded in the report itself, with no separate screen. Each rejected part gets the failure code and the corrective action, from a dictionary that already has 21 failures and 23 actions with their steps — and that each company adapts.

• Failure Pareto, to see where most is lost
• OK/NOK parts over time, per machine
• Dashboard by period, compared with the previous one, and export to Excel

The next maintenance at each machine's real pace.

Preventive. A task is written once per machine model and applies to every unit. It has an interval in days, in hours, or both — and whichever comes first wins, as in the manuals: "every 250 hours or 6 months". The hours come from the productions that ran on the machine.

Predictive. Tasks that fall due when a failure repeats: three nozzle clogs and the task "unclog the nozzle" appears.

• Board per model, with one card per machine, the NOK rate and the breakdowns
• Schedule with what is overdue at the top and a warning before it is due
• Log of interventions, planned and breakdowns, which resets the task's counter

Everyone sees what is theirs to see.

• Invitations by email; each person sets their own password, which the administrator never knows
• Five default roles and 12 permissions to adjust them or create others
• The team as an org chart: drag a person to change their role
• Portuguese (Portugal and Brazil), English and Spanish; light or dark theme

Your company's data stays your company's.

• Isolation in the database — each company is kept apart by rules in the database itself, not only by the application code.
• In the European Union — application and database hosted in Frankfurt.
• Daily backups, kept for 14 days, with tested restores.
• Protected accounts — email confirmation, lockout after failed attempts and password recovery through a single-use link.
• GDPR — retention periods stated on the privacy page.

It starts with the workshop already set up.

When you register your company, Kelo comes with a catalogue of 22 technologies — additive, CNC, cutting, bending, welding and moulding — with around 48 machine models, and a complete example: a printer, a customer, an order and two productions. Explore it and delete it with one click when you no longer need it.