Skip to content

Planner

The car should move once, not four times.

Planner proposes a repair date from the work's complexity, the specialisation it needs and the capacity you actually have, then sequences the tasks so a waiting customer's car is not shunted between bays and technicians.

A concept repair-day sequence for sample order 4471: four tasks run back to back on Bay 2, with the specialist step called out before the planned collection. Positions show the order of work, not measured capacity or performance.

Best fit
Workshop foreman · Service advisor · Technician · Service manager
Operational job
Sequence each order's work by dependency, competence, bay capacity and real availability so the vehicle moves less and promised collection times reflect the current plan.
What you get
A capacity plan with work dependencies, assigned technicians and collection times.

The problem

A plan made by hand optimises for the planner, not for the car.

A wall chart filled in booking order leaves a vehicle waiting for a specialist, moving to another bay and waiting again. Planner reads the dependencies between tasks so the sequence serves the vehicle and the customer waiting for it.

1

Competence-aware allocation

Work is assigned according to what each person is qualified to do, not to who happens to look free.

2

Everyone sees what is next

Employees know what needs doing on an order and when, from the same live sequence.

3

The day can change

Advice and assistance are part of the workflow, while the plan adapts instead of being rebuilt every morning.

How the plan is built

Four inputs, one sequence, adapted all day

Select an input to see what Planner weighs before it proposes the date and the order of work.

Complexity and specialisation, not just duration

An hour of diagnostics and an hour of bodywork are not interchangeable, and the plan reflects that.

The ideal repair date is proposed from what the work involves and the capacity the workshop genuinely has that week.

In
Order items, estimated durations, complexity and required specialisation
Omnetic
Matches the job to eligible time, bays and skills
Out
A proposed date the work can actually fit

Capabilities

All planning at your fingertips

All twelve capabilities named by the current Planner product, grouped by the decision they support.

Automatic date proposal

The ideal repair date from complexity, specialisation and capacity.

Task dependencies

Every connection between an order's requirements handled.

Uninterrupted scheduling

Waiting-customer activities follow on without gaps.

Competence-based allocation

Resources assigned according to what each person is qualified for.

Working-time rules

Responsibilities and working time set per person and respected.

Absences

Planned holidays and unavailable periods excluded from the plan.

Operational re-planning

Planned repairs adapt as the situation develops.

Real-time changes

Any change takes effect immediately for everyone.

Order status

Open and closed work visible to everyone looking at the plan.

Movement limiting

Fewer moves from bay to bay and technician to technician.

Company-wide planning

Work planned across the company with permission-aware visibility.

Preparation work included

Sales preparation competes honestly for the same bays.

By role

Who this changes the day for

Workshop foreman

Stops rebuilding the day at eight in the morning and sees the consequence of every override immediately.

Service advisor

Promises a collection time the plan supports and hears about a delay before the customer does.

Technician

Knows what is next and why it is theirs without waiting for manual allocation.

Service manager

Sees where capacity goes, including preparation work generated by sales.

Platform & data connections

What the plan reads

Workshop

The order and its items, including the dependencies between them.

Warehouse

Whether the parts a task needs will be there on the proposed day.

Time-keeping

Working time, absences and the competences each technician holds.

Reporting

Preparation work and workshop capacity on the same operating view.

System relationship

Planner in the connected product system

The sequence needs the order and its dependencies, real working time and competence, the parts a task needs and the other work competing for the same resources.

Outcome & proof

What we can and cannot claim yet

1

Fewer car movements and no idle gaps

A mechanical consequence of the scheduling logic, described rather than quantified.

2

The maximum effectiveness of your business

No throughput or utilisation gain is published without evidence.

3

The source H1's second paragraph

Broken source copy about benefits and pensions was not carried over.

4

Planner customer story

Slot reserved. Throughput per bay before and after would be the natural proof.

Questions foremen ask

Secondary product demonstration

One car, one uninterrupted sequence

Tasks follow dependencies, capacity and competence so the vehicle does not bounce between bays.

Review Planner
Order 4471 · waitingBay 2
08
08:00Diagnostics · Král
08
08:30Brakes · Král
09
09:42Service · Král
11
11:30Recall · Beneš, certified

Bring one busy Thursday

Your real bookings, your real technicians. We will plan it and show how many times each car would have moved.

See the planner
  1. The bookings

    One busy day with promised times and the work behind each promise.

  2. The people

    Technicians, competences, working hours and known absences.

  3. The constraints

    Bays, parts and task dependencies that make the day possible.