Griani.Net

In production

ComPilot

Commissioning an industrial plant is a long chain: construction hands over, commissioning verifies, quality certifies, the client accepts. ComPilot holds the whole chain in one system, instead of shared folders and spreadsheets that quietly fork into two versions.

Type
Multi-tenant SaaS
Sector
Industrial plant engineering
Technology
Laravel 11, MySQL
Languages
Italian, English

The problem

A plant in commissioning has thousands of activities to verify and sign off, spread across dozens of people and several companies. The question that blocks everyone is always the same: where do we actually stand?

The answers usually live in different places: signed ITRs in a folder, outstanding items in a spreadsheet someone updates in the evening, certificates in the QA manager's inbox, the schedule in Primavera P6 that nobody on site ever opens. Every progress meeting starts with half an hour of reconciling numbers.

ComPilot puts all of it on the same data layer: signing an ITR updates progress at the same moment, and the percentage site management sees is the real one, not a figure rebuilt by hand.

Modules

What is inside.

ITR

Inspection & Test Records: filling in, verification and sign-off, with status always visible by discipline and by system.

Punch List

Outstanding items in categories A, B and C with sequential numbering, full status history and filters that stay where you set them.

PAC / FAC

Provisional and final acceptance: gathering requirements, checking them and issuing the certificate.

Handover

Construction to commissioning transfer with checklists, an approval flow and signatures locked into the record.

QA/QC

Quality certificates with a draft → submitted → approved flow, eight certificate types and expiry alerts.

Daily Report

Daily site report: work carried out, crews on site, hours, open issues.

Plant Progress

Progress by system and subsystem, with a PDF export ready for the meeting.

Schedule import

Activities imported from Primavera P6 (.xer) and Microsoft Project (.xml), re-synced with every new revision.

Milestones

Contractual deadlines and intermediate targets, with their status always in view.

Notifications

In-app bell and email for the events that matter, without burying people who are not involved.

Projects and people

Projects, staff records and per-user access: everyone sees only the sites they belong to.

Administration

Roles and permissions customisable per company, subscription plans with limits, plan upgrade requests.


Platform

Multi-tenant from day one

Every client company has its own isolated data, its own users and its own roles. Whoever administers the platform sees the whole picture; whoever works on a site sees that site only.

  • System roles plus custom roles defined per company
  • Fine-grained permissions on sensitive actions, such as signing a handover or approving a certificate
  • Per-user access: assign a user to specific projects and those are the only ones they see
  • Subscription plans with limits on projects and users, dropping to read-only on expiry
  • Traceability: who did what and when, on the objects that have to stand up to scrutiny

Documents ready to hand over

Handovers, QA/QC certificates, plant progress and punch lists come out as laid-out PDFs carrying the signatures collected in the system. These are the documents that end up in the final project dossier, not courtesy printouts.

Contact

Do you need something like this?

ComPilot comes from industrial commissioning, but the platform underneath — projects, approval flows, signatures, documents, permissions — carries any structured technical process. If yours looks like this, we start from here instead of from nothing.

  • Emailinfo@griani.net
  • Based inItaly — working remotely across Europe
  • LanguagesItalian, English

Sign in to ComPilot