← Services

Software Services — Product

Ligava EDMS

Every great industrial project begins with an idea. But it takes shape through thousands of documents.

Ligava EDMS is a multi-user engineering document management system built for plant engineering — a controlled home for every drawing, specification and revision a project produces, from first issue to final handover.

The problem it solves

On a live project, documents multiply faster than anyone can track them: revisions circulate by e-mail, folders fork into “final” and “final_2”, and sooner or later someone builds from a superseded P&ID. The error surfaces on site — where it costs the most.

One principle above all

Originals are never modified and never silently overwritten. Every change enters the archive as a new revision, and every revision stays traceable — forever. One unbroken thread runs through the labyrinth of project documentation, from first issue to final handover.

A place for everything

A six-level hierarchy gives every document exactly one home — from the client at the root down to the single file of a single revision, with an optional plant/unit level for multi-skid projects. No duplicates, no orphans, no parallel truths.

  1. Client
  2. Project
  3. Plant / Unit
  4. Document type
  5. Revision
  6. File

From draft to issued

Every file moves through a six-status approval cycle that mirrors how plant documentation is really validated. The colored badge on the tree tells the story without opening the file.

  1. Draft
  2. Internal review
  3. Client review
  4. Approved
  5. Issued
  6. Archived

Traceability, made visible

Document types are linked by FEEDS / IMPACTS relationships: an upstream document feeds the ones built on it, and a change impacts them downstream. When a new revision lands, the links tell you which documents to look at — before the change reaches the site.

FEEDS / IMPACTS links between document types — a revision upstream, its impact visible downstream

What it does

  • Controlled vault

    Check-out / check-in with exclusive locking: a working copy on your disk (editable offline), the official file untouched until a verified check-in — and only you can check it back in.

  • Revisions with responsibility

    Every new revision requires a reason and records who prepared, checked and approved it. Identical files are caught by SHA-256 before they become pointless revisions.

  • Search everywhere

    Quick-open search (Ctrl+K): file name, code, title or tag — results in real time, across every client and project.

  • Dependency map

    FEEDS / IMPACTS relationships between document types — defined once, reused in every project, from process narrative to as-built. See what a change touches before it reaches the site.

  • Full traceability

    Immutable audit trail, project timeline and evolution report ready to paste into a client e-mail, and a KPI dashboard with live counts per workflow status.

  • Multi-user by design

    Five predefined roles — from Administrator to Viewer — with per-permission fine-tuning, for a whole team on one shared archive.

Technical foundations

  • PostgreSQL database — one shared source of truth; physical files live outside the database, in managed, secure storage.
  • SHA-256 fingerprint on every file — integrity verified, duplicates caught automatically.
  • Desktop application, multi-user over the local network — your documents never leave the company.
  • Multi-site synchronization — a sync queue propagates every operation across connected sites, tolerant of working offline.
  • Modular by installation — three predefined profiles (Base, Engineering, Enterprise) or a custom combination; the Core module is always active.
  • Fully localized interface — Italian and English, switchable at any time.

Roles & modules

Five predefined roles map onto how a project team actually works — every permission individually adjustable. Three module profiles shape what an installation includes; a custom combination is always possible.

Roles

  • Administrator

    Full access — runs the installation and its permissions.

  • Document Controller

    Keeper of the archive — guides every file from draft to issued.

  • Engineering

    The producing role — check-out, work, check-in, revise.

  • Project Manager

    The project view — status and progress without opening a file.

  • Viewer

    Read-only — consults the archive, never changes it.

Module profiles

  • Base

    The ready-made profile to start from.

  • Engineering

    The ready-made profile shaped for engineering work.

  • Enterprise

    The ready-made profile for the whole organization.

The Core module is always active — whichever profile you choose.