DEP - Digital Enterprise Provider
    Back to DEP Scheduler
    Product tour

    Every screen, and the decisions behind them.

    Short clips from the running product and diagrams of what each screen does.

    Book a demo See pricing
    DEP Scheduler · one runDashboard + API05  ExplanationsVerdict · causes · fixes04  ResultCoverage · hours · cost03  SolverObjective climbs02  RulesNever break · weighted01  RequirementsSites · services · peopleEdit · re-plan · re-runEvery gap explained · every fix ranked
    See it work

    Four moments from one operations week, on the real product.

    Silent clips captured from the running demo. No mock-ups, no retouching.

    The Monday build

    The Monday build

    46 s

    Readiness check, run, watch the solver, open the result.

    Fix a shift by hand

    Fix a shift by hand

    55 s

    Change the person, read the warnings, decide.

    Explain an empty shift

    Explain an empty shift

    46 s

    The verdict, the causes, one gap explained.

    Re-plan from a cut-off date

    Re-plan from a cut-off date

    61 s

    Freeze before the date, rebuild after, read the diff.

    Warn, never block

    It tells you what you are about to break. Then it lets you decide.

    Manual edits show availability, qualification, overlap and hour-cap warnings. You can save an exception; the warning stays with the assignment and change log.

    1. 01

      You change a shift

      Person, date, client or times, from the calendar or the table.

    2. 02

      Review conflict warnings

      Before anything is saved.

      • Not qualified
      • Outside availability
      • Overlapping shift
      • Over the daily cap
      • Over the weekly cap
    3. 03

      Your call

      Pick someone else, or save anyway when the site has to open.

      Pick someone elseSave anyway
    4. 04

      Kept on the record

      The change log keeps the before and after, warnings, time and your note.

      1edited
    • Edit from the calendar or the table
    • "Reset to the model" restores the solver's row
    • A change log with before, after, warnings and notes
    Re-plan from a cut-off

    Re-plan from Wednesday. Monday and Tuesday do not move.

    Choose a cut-off date. Saved assignments before it stay as they are, including manual edits. Assignments on and after that date are recalculated.

    • Frozen rows come from the edited schedule
    • Frozen assignments are checked for weekly-cap and free-weekend conflicts
    • Review the result and the changed future assignments
    MonTueWedThuFriSatSun
    Cut-off

    Frozen as it stands, hand edits included

    Rebuilt from scratch

    • Kept
    • Moved
    • Added
    • Removed
    Rules and priorities

    Understand the rules behind the schedule.

    These are the demo’s current rules. We review your requirements and scope any changes before deployment.

    Never

    The solver never breaks these.

    • Put anyone on a day they are away
    • Assign a service to someone not qualified for its type
    • Give an overnight shift to someone not set up for nights
    • Put anyone on two overlapping shifts on the same day
    • Let anyone work more than 10 h in one day
    • Let anyone work more than 42 h in one week
    • Let anyone work more than 6 days in any 7
    • Leave anyone with fewer than 1 completely free weekend in a month
    • Put more people on a shift than it asks for
    Tries to

    The model balances these priorities using weights. These scores are not financial costs; changing them can change the result.

    • Fill every place−10 when one is left empty
    • Keep everyone at or under 40 h a week−150 an hour over
    • Bring everyone up to 40 h a week−70 an hour under
    • Chain a person's shifts back to back on the same day+2 a pair
    • Avoid gaps of two hours or more between a person's shifts−3 a pair
    What we tune for you
    • Review your working-hour policies
    • Map service and qualification requirements
    • Scope any travel, pairing or equipment constraints
    • Agree the optimisation priorities

    Additional rules and integrations are scoped with your team.

    Honest scope

    A scheduling brain with an explanation layer, not a workforce suite.

    If you already run a suite, DEP makes its schedule explainable rather than replacing it.

    Bring your forecast

    DEP schedules against the demand you define.

    Keep your HR system

    We integrate with the systems you have.

    One plan at a time

    Scenario comparison is on the roadmap.

    "A better schedule may exist"

    The product says so when it cannot prove optimality.

    Trust

    Built inside an industrial operator, hosted in the EU.

    EU hosting

    Azure, Germany West Central.

    Isolated per client

    Own storage, secrets, identity and login realm, on every tier.

    GDPR posture

    Logs hold identifiers and durations, never schedules.

    Full audit trail

    Every change kept: before, after, warnings, note.

    Grupo Nextenergy

    Built for operations we run ourselves.

    What's next

    Already planned, in this order.

    Nothing here is implied to exist today.

    1. 01

      Why this person?

      The rules that favoured every covered assignment.

    2. 02

      Scenario comparison

      Two runs side by side, with the delta.

    3. 03

      Route optimisation

      Connect a route-optimisation system to the services to be delivered.

    4. 04

      Explanation report

      One PDF per run, for the manager who has to justify it.

    Next step

    See your own gaps explained.

    Bring your planning requirements. We will walk through a schedule, its gaps and the decisions you can make next.