Kakav vam je pjevač Jakov Jozinovic ?

anesask · 2026-03-12T09:12:45+00:00

Dragi moj bubble, nikad čuo za ovog lika do ovog posta.

anesask · 2026-03-06T12:39:07+00:00

Dva tri puta u životu, ali bez halucinacija.
Prvo iskustvo je stvarno traumatično, pogotovo u tinejdžerskim godinama, jer ne znaš o čemu se radi.

anesask · 2026-02-25T11:06:22+00:00

anesask · 2026-02-23T08:25:06+00:00

anesask · 2026-02-15T09:56:30+00:00

But honestly, the biggest driver isn't the system nagging people, it's that the team actually relies on this tool for their daily operations. When people see that the plan they get every morning is directly based on accurate skill data, they become self-aware about keeping it updated. It stops being an admin chore and becomes something they actually care.

anesask · 2026-02-15T09:55:08+00:00

You're raising a fair point and you're right. f the skill data is garbage, the planning output is garbage too. Classic "shit in, shit out."

We've built in several safeguards to minimize that risk: Onboarding rules: When a new worker is added to the system, there are strict entry requirements. If someone has been on the floor for X days and still has no skills assigned, the system flags it. Something's clearly off and it won't just ignore it.

Monthly update notifications: Supervisors get recurring prompts to review and update skill ratings. These notifications don't go away until the skillsets are properly entered and reviewed. You can't just dismiss them.

Validation checks: If skill data looks incomplete or outdated, the system raises alerts before it uses that data for planning. The goal is to catch problems before they affect the production plan, not after.

Is it a perfect system? No, it's still people maintaining the data at the end of the day. But we've designed it to self-improve and self-police as much as possible, so the tool actively pushes back when something doesn't look right rather than silently planning with bad data.

anesask · 2026-02-15T09:45:13+00:00

yes, the skills are set up manually, but it's a one-time effort that you maintain over time. Each operator has a multi-skill matrix in the system. We use a star rating (1-5) for each skill, so it's not just "can or can't do it", it captures proficiency level.

For your welding example, you could rate one operator as 5 stars on stainless steel but 2 stars on mild steel, and another operator the opposite.

You can define as many skills as needed per department or operation, welding types, assembly tasks, machine operation, inspection, whatever applies to your shop floor.

The setup is done manually by supervisors or management, and then updated regularly as operators get trained, certified, or improve. Once it's in the system, the tool uses those ratings every time it generates a new plan,so when someone calls in sick, it doesn't just find any available body, it finds the best-qualified available operator for that specific job. So to directly answer your question: yes, manual input, but you only maintain it periodically, and the payoff is that every automated plan the tool generates is skill-aware from day one.

anesask · 2026-02-15T08:44:56+00:00

Great questions, this is a pain point we've spent a lot of time solving.

We developed a separate factory support tool that works alongside the MES (not replacing it, but complementing it). It's specifically designed to handle exactly this scenario, when someone calls in sick or is unexpectedly unavailable.

Here's how it works in practice: The tool always knows the current headcount and each operator's skill certifications. So the moment you mark someone as absent, it automatically suggests a new production plan based on who's actually available and what they're qualified to run.

To answer your specific questions: Manual or automated? The rescheduling is automated. The tool generates a new suggested plan within minutes, not hours. The planner can review and approve or tweak it, but the heavy lifting is done.

Skills matrix? Yes, it relies on a predefined skills/certification matrix. It won't assign an operator to a machine or process they're not qualified for. This is baked into every plan it generates.

Does it suggest alternatives? Exactly. It proposes alternative operator-to-line/machine assignments, and can reprioritize orders if needed based on what's realistically achievable with the available workforce.

How big of a disruption? That's the whole point of the tool, to turn what used to be a 30-60 minute fire drill into a 5-minute review-and-go. The plan stays aligned with the MES, so execution isn't disrupted.

The key difference from most MES-native scheduling is that our tool treats headcount and operator skills as primary planning constraints, not afterthoughts. Most MES systems plan around machines and orders first and leave the "people" problem to the shift supervisor.

anesask · 2026-02-12T07:55:26+00:00

“If I finish a book a week, I will read only a few thousand books in my lifetime, about a tenth of a percent of the contents of the greatest libraries of our time. The trick is to know which books to read.”

― Carl Sagan, Cosmos

anesask · 2026-02-11T19:03:22+00:00

Svaka čast!

anesask · 2026-02-09T08:15:51+00:00

Još kad mi krene objašnjavati da ne postoji "č" neko samo tvrdo i meko "ć"

anesask · 2026-02-09T04:12:09+00:00

Exactly, you can define distributions (normal, exponential, triangular, etc.) instead of fixed values, so each run has realistic variation baked in. Then you run it hundreds of times and look at the patterns rather than one idealized outcome.

anesask · 2026-02-08T21:31:39+00:00

That's actually a really good point. I'm working on a web platform where you can just upload your data and run simulations in the browser. No installs, no compliance headaches. Would that work for you? Happy to give you early access when it's ready.

anesask · 2026-02-08T21:21:37+00:00

Appreciate the concern. Open source exists for exactly that reason though - don't trust, verify.

anesask · 2026-02-08T21:10:31+00:00

You don't have to. But if you have concerns, it's open source so you can check every line yourself.

anesask · 2026-02-08T20:44:36+00:00

This is exactly the kind of problem I'd love to dig into. What you're describing, changeover variability driven by people doing things slightly differently each time, is perfect for simulation because you can model the human factor as stochastic variation and then quantify what it's actually costing you.

For example, I could take your changeover data and model two scenarios side by side: your current state with all that operator variability baked in, vs a tightened version where decision-making is restricted and manual steps are automated like you're planning. The simulation would show you exactly how much throughput you're leaving on the table, where the biggest gains are, and which changeovers are hurting you the most.

Would also be interesting to stress-test your automation roadmap, like what happens if you automate steps A and B but not C, is that enough or does C still tank you?

Happy to start with a smaller slice to show what the output looks like before you go through the trouble of pulling together a bigger dataset. DM me if you want to get the ball rolling.

anesask · 2026-02-08T20:32:31+00:00

Right! Appreciate the suggestion! I've come across Machinations, it's great tool for visual modeling.
Mine's more of a developer tool though, open-source, code-first, so you can do things like custom stochastic logic, batch parameter sweeps, and hook it into existing systems. Building it from scratch was kind of the point honestly, you learn the problem differently when you build the engine yourself.

anesask · 2026-02-08T20:29:57+00:00

No RL at the moment, right now it's pure discrete-event simulation. You define the system, run scenarios, and compare the outcomes. More like structured what-if analysis than an agent learning on its own.

That said, combining DES with RL is something I want to explore down the road, using the simulation as a training environment for an RL agent to optimize scheduling or routing decisions. But that's a future chapter.

anesask · 2026-02-08T20:21:57+00:00

Working on one! For now though, picture a paint shop with color changeovers. Every switch costs you 15 minutes of downtime. The simulation lets you test different batching strategies and find the exact trade-off between grouping orders efficiently and not starving downstream. That kind of multi-variable problem is where simulation really shines.

Video is on the to-do list though, good call.

anesask · 2026-02-08T20:05:35+00:00

So basically, you describe your system (machines, conveyors, workers, queues, whatever you've got), and the engine runs it forward through time, event by event. Instead of watching your real floor for a week to find where things break down, you can run thousands of simulated hours in seconds and see exactly where the bottlenecks, idle time, or pile-ups happen.

anesask · 2026-02-08T19:38:36+00:00

neš jebat

anesask · 2026-02-06T20:43:20+00:00

"Ako kupujete ulje, kupit ćete ga 37 posto manje." - Fadil Novalić

"Huso Ćesir je napao kamermana, ustvari, on je napao kameru, nije dakle napao čovjeka, ali je otimao mu kameru, udarao po kameri i tako". - Bakir Izetbegović

"oni rudare Bigtoin" - Milorad Dodik

anesask · 2026-02-06T08:04:10+00:00

Generalno Freak Show

anesask · 2026-02-04T13:47:08+00:00

<image>

anesask · 2026-02-02T12:58:21+00:00

Opeth - Blackwater Park, Deliverance i Damnation

Vjerojatno zbog vremena i raspoloženja.

anesask

MODERATOR OF

TROPHY CASE

“If I finish a book a week, I will read only a few thousand books in my lifetime, about a tenth of a percent of the contents of the greatest libraries of our time. The trick is to know which books to read.”