Thank you all for joining this demo session today and for giving us the opportunity to share our ideas for Dyno’s digital transformation journey.
This is not just my idea or our team’s idea. I’m sure many of these thoughts have already crossed your mind, and we’ve probably discussed them on multiple occasions. With our joint hands, we’ve simply tried to frame those ideas into something tangible. What we’ll show you today is just the foundation — a starting point from which we can build. Over time, the shape may evolve, but the foundation will remain strong and intact.
What we’re presenting is more than a platform — it’s a vision for Dyno to stay ahead in a digital-first service economy by reducing waste, anticipating problems, and strengthening customer relationships. It’s a path to greater efficiency and smarter, more connected services and may give Dyno a greater milage in future.
With that, let’s dive into the structure of the project followed by the demo to show you how this transformation can come to life.
Thank you for taking the time to walk through this demo with us today.
What we’ve shared is just the beginning of how Dyno can leverage digital transformation to unlock new value — reducing waste, anticipating challenges, and strengthening customer relationships.
We’re excited about the possibilities this platform can bring, and we look forward to working together to make this vision a reality.
Your feedback and ideas will be critical as we move forward, so we truly welcome your thoughts and questions.
Thank you once again — and we’re eager to hear what you think.
Today I’d like to walk you through our new smart routing solution and the business rules that drive it.
At a high level, this solution answers three questions for every working day:
·Which jobs should we do first?
·Which engineer should do each job?
·How can we do that in a way that is realistic, fair to engineers, and delivers on customer promises?
·
To do that, we’ve built two core capabilities:
·First, the assign‑jobs engine, which automatically assigns work to engineers for a given day. It looks at job priority, SLA time windows, engineer skills, working hours, travel time, and current workload. It will try to fully complete each job where possible, and, if you enable it, it can also schedule short “attendance‑only” visits when full completion can’t be achieved within the promise time.
·Second, the analyze‑routing view, which doesn’t change any assignments, but explains them. It shows, per engineer, how many jobs they have, how much time they’ll spend working and travelling, how well those jobs match their skills, and whether they are underloaded, optimal, or overloaded. It also highlights unassigned jobs and suggests where to rebalance work.
Under the hood, every decision the engine makes is governed by clear, business‑oriented rules:
·Emergencies first – true emergency jobs go to the fastest, properly skilled engineer who can realistically attend or complete within the SLA.
·Skills over convenience – no job is given to someone who doesn’t have all the required skills, even if they are closer or less busy.
·Realistic days – the system avoids overloading engineers beyond a sensible margin on top of their working hours.
·Transparent trade‑offs – when we can’t complete everything, and you choose to allow it, the engine will still send someone to attend, and it records that clearly in both the job description and the audit log.
·
In today’s demo I’ll show:
1.How we call the assign‑jobs endpoint with a set of jobs and engineers, and what the assignment output looks like.
2.How we use the analyze‑routing endpoint to review those decisions: which engineer got which jobs, why, and how balanced the day is across the team.
3.How the key rules, such as emergency handling, attendance‑only visits, and workload balancing, appear in real scenarios.
The goal is to give you confidence that the system is not a black box. It’s applying a set of rules you can understand, explain, and adjust, so that routing becomes predictable, auditable, and aligned with your business priorities.