Guides
What is Aligia?
An AI-based project management system for technically complex projects – schedule, engineering, budget and portfolio in one system.
Overview
Section titled “Overview”Aligia is an AI-based project management system for technically complex projects, developed by GreenVee GmbH. This means undertakings such as solar parks, wind farms, substations, the expansion of low- and high-voltage grids or the rollout of charging stations, where many trades, interfaces and dependencies come together.
In Aligia, schedule, engineering, budget and portfolio come together in one system. An AI assistant takes over the routine work.
Why a dedicated system is needed for this becomes clear when you look at everyday life in such projects.
The problem Aligia solves
Section titled “The problem Aligia solves”Project-related employees lose on average 8.7 hours per week to administrative work: gathering status reports, transferring data, updating dates. That is 22 % of working time. Of 40 hours per week, 31.3 hours remain for what people were actually hired for: the project.
What that costs
Section titled “What that costs”A model calculation for a company with 20 project-related employees:
| KPI | Value | Calculation |
|---|---|---|
| Administrative time per employee | 8.7 h/week | 22 % of 40 hours per week |
| Positions that do nothing but administration | 4.4 | 20 × 8.7 h ÷ 40 h |
| Labour cost of administration | around €370,000/year | 20 × €85,000 full cost × 22 % |
Source of the 8.7 hours: Stepstone Group, 2024, survey of 5,800 employees. Values rounded.
Where the time is lost
Section titled “Where the time is lost”The problem runs through every level of a company. Status travels upwards by hand, queries and re-planning travel downwards.
Operations lead (department)
- No real-time overall picture: An overview only exists through manual collection. Decisions are made on the basis of data that is 2–4 weeks old.
- Report factory instead of leadership: Department and PMO produce reports instead of projects. That is pure overhead.
- Resource conflicts become visible too late: Overbookings are only noticed when projects are already delayed. Firefighting instead of prevention.
Portfolio manager (portfolio)
- Prioritization by gut feeling: There are no uniform criteria. The wrong projects tie up budget and people.
- Status reports are manual work: Everyone delivers their own format. That costs several person-days per cycle, every month anew.
- Data is scattered: Budget, actual costs and progress live in three different worlds. Corrective action only happens once the money is gone.
Project manager (project)
- Duplicate reporting: The same status is created as a slide, as Excel and as e-mail. That costs 0.5–1 day per week.
- The plan lives somewhere other than the work: The project manager is the human sync between three systems.
- Resource commitments are not reliable: Availability is only learned by asking around. The result is constant re-planning.
Project operative (execution)
- Unclear what is due today: Tasks come from four channels, with contradictory priorities. Time seeps away in context switching.
- Triple status upkeep: Hours, ticket, e-mail – the same information is entered three times. That costs 15–30 minutes per day.
- Constant interruptions: “How far along are you?” Focused work becomes the exception.
At every level a person manually produces a state that the system should already know.
Why this is so
Section titled “Why this is so”The cause lies not with the people but with the tools.
- Every transfer is a source of error: Whatever moves by hand from one system to another will sooner or later be transferred incorrectly. The consequences are days of delay and wrong purchases.
- Engineering is missing: Standard project management tools do not model engineering. Trades, interfaces and plant structures therefore end up in separate systems, disconnected from plan and budget.
- Problems become visible too late: When a date slips, the consequences for the critical path often only show up once it gets expensive.
Six systems in one day: why an AI assistant alone is not enough
Section titled “Six systems in one day: why an AI assistant alone is not enough”On a normal day, a project manager in plant engineering works in six systems: PM tool, ERP, PLM, e-mail, calendar, chat.
An AI assistant that only knows one of them can do nothing in five sixths of the working day. It is just another window.
| Share of working time | What for |
|---|---|
| 19 % | Searching for information |
| 28 % |
Most of that is searching and transferring between systems. That is exactly where the reach of an AI without integration ends.
How Aligia solves this
Section titled “How Aligia solves this”Aligia takes over precisely the work that today gets stuck between the systems. Plan, engineering, budget and resources live in one system; the remaining tools are connected via interfaces.
AI assistant connected to all systems
Section titled “AI assistant connected to all systems”Aligia AI is not just another window. The assistant is connected to the existing systems via interfaces (including MCP) and synchronizes data in both directions. That way it works exactly where most time is lost today: searching and transferring.
- Hand off routine work: Phase planning and team assignment are handled by specialized sub-agents.
- Instructions in natural language: for example “Create the project Charging Stations Rhine-Main with three phases and create the first work packages.”
- Control stays with the team: Before execution, Aligia checks every instruction against the data model. It is only carried out after approval.
One system instead of many tools
Section titled “One system instead of many tools”Plan, engineering, material, budget and reports live in one place. A status is maintained once and is current everywhere, instead of being created in parallel as a slide, Excel and e-mail. Whoever works in the project finds their tasks in one place instead of in four channels. What is no longer transferred by hand cannot be transferred incorrectly either.
Real-time overall picture instead of report factory
Section titled “Real-time overall picture instead of report factory”The current state of all projects is visible at all times, without anyone having to collect it. Instead of compiling reports, everyone sees the current project status directly in Aligia. Decisions are made on the basis of current data instead of data that is 2–4 weeks old.
Planning in real time
Section titled “Planning in real time”Schedule, critical path and resources adapt live as soon as something shifts. Resource planning shows the workload of every team, so overbookings are noticed before a project falls behind. Baselines show plan against actual at any time.
Portfolio with clear criteria
Section titled “Portfolio with clear criteria”Projects are prioritized across the board by benefit, risk and success forecast instead of by gut feeling. Budget, actual costs, ROI and progress stand side by side. Aligia detects resource conflicts between projects automatically.
Engineering as a digital twin
Section titled “Engineering as a digital twin”Trades, interfaces, plant structure and material flow are directly linked to the project plan, procurement and budget. Every change in the technical structure immediately affects dates, costs and resources.
What changes for each level
Section titled “What changes for each level”| Role | Today | With Aligia |
|---|---|---|
| Operations lead | Overview only by collecting, data 2–4 weeks old, conflicts noticed too late | Real-time overall picture, resource conflicts visible early |
| Portfolio manager | Prioritization by gut feeling, data in three worlds, several person-days per reporting cycle | Uniform criteria, budget and progress in one place, current status visible at all times |
| Project manager | 0.5–1 day per week of reporting, human sync between three systems | Status maintained once and visible at all times, reliable resource planning |
| Project operative | Tasks from four channels, 15–30 min per day of duplicate status upkeep | Tasks in one place, status entered once |
What it pays off
Section titled “What it pays off”With 20 project-related employees, around €370,000 in labour costs per year are lost to administration. If Aligia takes over just one third of that, the company recovers around €120,000. Together with avoided days of delay and wrong purchases, that is around €184,000 per year.
| Item | Amount per year |
|---|---|
| Savings: one third of administrative time | around €120,000 |
| Avoided days of delay and wrong purchases | around €64,000 |
| Total benefit | around €184,000 |
Conservatively calculated, values rounded.
What Aligia is not
Section titled “What Aligia is not”Aligia is project management software. It steers projects and does not replace the specialist systems companies already work with.
- Not a CAD system: Design and technical drawings stay in the existing tools. Aligia models the technical structure needed to steer the project.
- Not an ERP: Accounting and inventory management stay in the ERP system. Aligia uses budget and material data to plan and steer projects.
- Not an AI that acts on its own: The AI assistant executes nothing without approval. Every instruction is only carried out once an employee has confirmed it.
- Not a simple task tool: Aligia is built for technically complex projects, not for simple to-do lists.
The product
Section titled “The product”Aligia runs in the cloud on European servers and is GDPR-compliant. It is used in the browser or as an app, connected to existing systems via interfaces.