Case notes.

Situation → approach → resolution. One example is delivered work, anonymized; two are typical engagements — a description of how we handle them, not delivered work. Each example carries its label, with no names and no numbers.

Case notes.

Creative studio · delivered work

A studio with huge files

Situation: A creative studio works with large files: everyone has access to everything, the archive is scattered, and nobody has proven the backup with a restore.
Approach: A review of the NAS, folder structure and rights — no changes. Then a project structure with per-team access; MIODATA designed the backup architecture, and we monitor it daily.
Resolution: Files are seen by the right people, the archive has order, and the backup is known to restore — a test restore was performed and recorded. We still administer the studio.

Typical engagement · how we handle it

A company with no internal IT

Situation: Nobody owns IT: whoever is free handles the breakdown, nobody checks the backup, and nothing says how anything was set up.
Approach: Takeover starts with an inventory and documentation, without a single change. Then a help desk as the one place to report to, servers and backup under monitoring, and a test restore.
Resolution: One owner for IT and one address for everything; a backup proven by a test restore; a monthly report management can read. This describes our procedure, not delivered work.

Typical engagement · how we handle it

The render dies on the last frame

Situation: Batch renders stop without a clear cause, a node is up but jobs won’t start, and the farm sits unused after hours.
Approach: A no-change review of the farm: software and plugin versions per node, Deadline pools and priorities, asset paths, the license server. Then version alignment and a night queue.
Resolution: The same versions on every node, jobs scheduled by deadline, and a farm that actually works overnight — with a version list that is kept up to date. This describes our procedure, not delivered work.

AI and software examples live on the MOYAGRID site; infrastructure and security examples on the MIODATA site.

Start with an IT health check.

We look at your systems — servers, backup, network or the farm — and write a concrete assessment: what’s fragile, what’s slowing you down and what’s worth fixing first. The review changes nothing, and the report stays yours even if we don’t continue.

Book an IT health check

No sales pitch. Just engineers.