Features · 02 / 06

Fleet control

Decide what to launch and on which machine, and stop the defect before it happens.

« What goes next, and on which machine? »

What it changes

  • Launch in a few clicks

    You drop the file, DMEOS® offers the machines able to print it, and you pick one.

  • The wrong spool is stopped

    If the loaded material does not match the file, the print does not start and the operator sees why.

  • No print goes unnoticed

    A print started directly on the machine, outside DMEOS®, is detected and written to the log.

Bridge production queue: for each job, the file, the machine, the operator who submitted it, the material, the nozzle and the progress.

The features, by use

  • Three-step drop

    Drop, pass the available checks, choose the machine.

  • Three dispatch modes

    Optimised production, balanced wear, or signed manual.

  • Eligible machines only

    Material, capabilities, maintenance, arming: every exclusion has its reason.

  • Controlled material

    Wrong material: the job does not start.

  • Fleet calendar

    Maintenance, trials, downtime: work is shifted, never lost.

  • Workshop hours

    Open days, closed days, dated exceptions.

  • Segregated ordering parties

    Each one sees only their own jobs, enforced by the server.

  • Production queue

    Board, list, history: everything waiting, running or finished.

  • No invisible print

    A launch outside DMEOS® is detected and logged.

  • Notifications and webhooks

    Events go out to your tools, when you allow it.

  • Bed cleared first

    Nothing new before the signed harvest.

  • Automatic re-arming

    After a compliant harvest, the machine becomes available again.

  • Order closed on good partssoon

    It only ends once the compliant quantity is harvested.

  • Part-machine quarantinesoon

    Two failures: the pair is blocked, maintenance is alerted.

  • Ambient envelopesoon

    Out of range, the print waits, then resumes.