A solar project can look excellent on a map.
The land is available.
The irradiation is strong.
The site is large enough.
The economics appear attractive.
Then engineering begins.
The terrain requires far more grading than expected.
Cable runs become longer.
A tracker layout that looked efficient on paper creates unnecessary earthworks.
The nearest grid connection has insufficient capacity.
Or the project reaches interconnection analysis only to discover that tens of millions of euros in network upgrades may be required before a single megawatt can be connected.
Kaunas-born solar software company PVcase is pushing more of those discoveries toward the beginning of the project.
Its latest product releases across PVcase Ground Mount, Roof Mount, Prospect and Yield continue a broader shift from individual solar-design tools toward an integrated engineering platform covering much more of the development lifecycle.
Ground Mount versions 2.64 and 2.65 bring new terrain optimisation, electrical-design and workflow improvements.
Roof Mount continues expanding its engineering and component-management capabilities.
Prospect is moving grid capacity and potential upgrade costs further upstream into site selection.
And Yield is increasingly using automation and artificial intelligence to remove manual engineering work.
Taken individually, many of these changes look like software features.
Together, they point toward a larger product philosophy:
find expensive engineering problems before they become expensive project problems.
Solar development starts long before panels are placed
The visible part of a solar farm is relatively simple.
Rows of modules.
Trackers or mounting structures.
Inverters.
Cables.
A connection to the electricity grid.
But reaching that point requires a long chain of engineering decisions.
Developers first have to identify viable land.
Understand topography.
Evaluate nearby transmission infrastructure.
Estimate whether grid capacity exists.
Design the plant.
Choose equipment.
Calculate cable routes.
Model energy production.
Estimate earthworks.
And repeatedly test whether the project still makes financial sense.
Historically, much of this work has been fragmented between different tools and teams.
A site-development group identifies land.
An engineering team creates the layout.
Another engineer models energy yield.
Grid specialists assess interconnection.
Information moves between CAD drawings, spreadsheets, databases and simulation tools.
Problems discovered later can force earlier work to be repeated.
PVcase has spent years building software around those individual stages.
Its recent releases increasingly connect them.
Ground Mount 2.64 attacks the terrain problem
Terrain is one of the most expensive things to misunderstand when designing a utility-scale solar project.
A perfectly regular solar layout drawn over an irregular landscape may look good in two dimensions.
Building it is another matter.
Slopes change.
Tracker rows interact with the terrain differently depending on their direction.
Some layouts require soil to be cut from high areas and used to fill lower ones.
That means earthworks.
Earthworks mean machinery, labour, time and money.
PVcase Ground Mount already automates large parts of utility-scale solar layout design, but version 2.64 introduced a particularly interesting improvement to terrain-following trackers.
Instead of creating the layout in only one direction, the software can generate alternatives from both directions and retain the arrangement requiring less cut and fill.
It sounds like a small optimisation.
Across a solar farm containing thousands of trackers, it is not.
PVcase tested the approach on real project drawings and reported reductions in combined earthworks ranging from roughly 2% to 18%, depending on the site.
The wider objective is straightforward:
let the software adapt the power plant to the land instead of unnecessarily adapting the land to the power plant.
Saving dirt can save serious money
Earthworks are a good example of why seemingly minor software decisions matter in physical infrastructure.
Moving soil does not generate electricity.
It is a cost required because of the way the plant has been designed.
Every cubic metre of unnecessary grading consumes equipment hours, fuel and construction budget while potentially increasing environmental disturbance.
For a small installation, the effect may be manageable.
For a utility-scale solar project spread across hundreds of hectares, small improvements compound.
Better terrain-following design can therefore affect both capital expenditure and constructability.
And importantly, the optimisation happens while the project still exists primarily as data and geometry.
Changing a layout inside software is cheap.
Changing a site after construction begins is not.
Ground Mount 2.65 continues removing engineering friction
Version 2.65 continues the same approach, although with less visually dramatic improvements.
The release simplifies access to PVcase’s component database and related design functions, removing an additional login step previously required for areas such as inverter sizing and QuickYield.
It also improves cable calculations across different installation arrangements.
These kinds of updates rarely make headlines outside engineering teams.
But electrical calculations are exactly the sort of repetitive work where small software inefficiencies accumulate.
Cable lengths affect material costs.
Cable sizing affects losses.
Equipment selection affects plant architecture.
And mistakes introduced during one stage can propagate into later calculations.
PVcase’s direction is increasingly to keep these decisions inside a connected engineering environment rather than forcing engineers to repeatedly export, rebuild and reconcile project information.
The component database becomes infrastructure
Another recent Ground Mount development helps explain that strategy.
PVcase has introduced a centralised component database covering solar modules and inverters.
Instead of every engineer repeatedly recreating equipment specifications, components can be selected from structured data already available inside the platform.
Ground Mount can then use those specifications for tasks such as inverter sizing.
The same component information can also flow into other PVcase products.
This may appear mundane compared with artificial intelligence or automated layout optimisation.
But engineering software becomes much more powerful when the same underlying project data survives from one calculation to another.
A module should not need to be defined differently in the layout tool, electrical model and yield simulation.
It should be the same component throughout the project.
That sounds obvious.
In complex engineering workflows, it often is not.
PVcase Yield is attacking the PDF problem
Solar engineers also spend surprising amounts of time reading datasheets.
Modules and inverters arrive with lengthy manufacturer specifications.
Electrical properties.
Temperature coefficients.
Dimensions.
Efficiency curves.
Voltage ranges.
Power ratings.
Engineers need those values for simulation and design.
PVcase Yield has introduced AI-powered datasheet parsing to automate part of that process.
Instead of manually transferring specifications from manufacturer PDFs, the system can extract relevant module and inverter information.
This is a much clearer example of artificial intelligence being applied to an engineering bottleneck.
The objective is not to have an AI invent the design.
It is to remove repetitive information extraction before the engineer performs the design.
That distinction is important.
In infrastructure engineering, the highest-value AI may often be less about replacing engineering judgement and more about removing the tedious work surrounding it.
Ground Mount and Yield are becoming one continuous workflow
Another important change is happening between design and simulation.
PVcase has introduced PVCollada 2.0, developed together with solar simulation software company PVsyst.
The format improves the transfer of project information from Ground Mount into yield simulation.
Tracker geometry and terrain information can move with the project instead of requiring engineers to manually reconstruct or realign parts of the model.
This addresses a classic problem in engineering software:
data gets lost between tools.
One program understands the terrain.
Another understands the solar layout.
Another calculates energy generation.
Another contains financial assumptions.
Every manual handoff creates an opportunity for information to disappear, become outdated or be entered incorrectly.
PVcase is gradually reducing those handoffs.
The solar plant designed by the engineer becomes increasingly capable of travelling through the development workflow as the same digital project.
Roof Mount is doing the same for commercial solar
Utility-scale solar is only part of the company’s product portfolio.
PVcase Roof Mount addresses commercial and industrial rooftop projects, where the geometric problem is very different.
Instead of designing across a landscape, engineers have to understand buildings.
Roof surfaces.
Obstacles.
Different orientations.
Structural zones.
Cable routes.
Available areas.
Mounting systems.
Recent Roof Mount releases have expanded both design automation and quality-control capabilities.
The product has gained integrations such as K2 Base project imports, pre-populated component libraries and support for additional mounting configurations such as fixed-tilt frames.
An audit tool can help identify malformed or incorrectly placed project objects.
Roof planarisation has been improved.
Cable routing has also been expanded, including better handling of cable trays.
Again, the broader theme is less interesting at the level of each individual feature than at the level of the workflow.
PVcase is trying to eliminate steps where an engineer has to manually recreate information the software should already understand.
But the most expensive problem may appear before design begins
The newest PVcase story is not only about designing solar plants more efficiently.
It is increasingly about deciding which plants should be designed at all.
A site can have excellent terrain and solar resources and still be a terrible project.
The reason may be kilometres away.
The electrical grid.
Utility-scale renewable projects have to connect somewhere.
And the apparent proximity of a transmission line or substation does not necessarily mean economically viable grid capacity is available.
A developer can spend months securing land and performing engineering work before discovering that the project requires major network reinforcement.
The result can be devastating to project economics.
This is the problem PVcase Prospect is increasingly moving upstream.
The power-first approach
PVcase describes a shift toward what it calls a power-first approach to site selection.
Instead of beginning primarily with land and then asking how the project might connect to the grid, developers can analyse grid conditions much earlier.
Potential Points of Interconnection can be evaluated against factors including available headroom, existing constraints, required upgrades and estimated cumulative upgrade costs.
That can fundamentally change which site looks attractive.
Imagine two parcels of land.
The first has slightly better terrain and perhaps cheaper land.
The second appears less attractive geographically.
But the first may require €30 million of grid reinforcement while the second can connect with relatively little additional infrastructure.
The better solar site may be the worse energy project.
The problem is that developers traditionally may not discover that until significant money has already been committed.
PVcase wants software to expose the risk earlier.
The cheapest project to abandon is the one abandoned early
This may be the most important theme connecting the company’s current product development.
Solar software is often discussed in terms of designing projects faster.
That is valuable.
But there is another form of optimisation:
discovering that a project should not be built before spending millions trying to build it.
If software can identify an uneconomic grid connection during site selection, engineering resources can move elsewhere.
If terrain analysis reveals excessive grading before the final plant layout, the design can change.
If equipment incompatibilities are caught through structured component data, electrical work does not have to be repeated.
If yield models inherit the actual terrain and tracker geometry, engineers do not need to rebuild assumptions later.
Every problem moved upstream becomes cheaper to solve.
AI has a role, but automation is the bigger story
It would be tempting to describe the current PVcase releases simply as an AI push.
That would miss much of what is happening.
Artificial intelligence is clearly entering the platform.
Yield uses AI to extract equipment specifications from datasheets.
Prospect has introduced AI-supported analysis in areas including community sentiment.
PVcase is also exploring increasingly intelligent ways to validate and interpret the information surrounding solar development.
But much of the value still comes from something less fashionable:
good engineering automation.
Generating alternative terrain-following layouts.
Calculating cables correctly.
Maintaining a component database.
Preserving project geometry between applications.
Checking whether objects are placed correctly.
Ranking possible grid connections.
These are not necessarily generative-AI problems.
They are engineering workflow problems.
PVcase’s advantage is increasingly its ability to connect both.
From Kaunas tool to global solar platform
PVcase began in Kaunas from a problem its founder David Trainavicius understood directly from solar engineering.
Designing utility-scale photovoltaic projects involved repetitive manual work inside tools that had never been built specifically around the complete needs of solar engineers.
What began as software to make photovoltaic design faster has expanded considerably.
Today the PVcase product family includes:
Prospect for site selection and early development;
Ground Mount for utility-scale solar engineering;
Roof Mount for commercial and industrial rooftop design;
and Yield for energy-production modelling.
The company says its software supports more than 4 terawatts of projects annually and is used by around 1,900 customers across more than 88 countries.
Those numbers put the latest releases into perspective.
A few percentage points less grading or a faster engineering workflow can become meaningful when software is being applied across projects measured in terawatts.
The product is becoming the workflow
The evolution of PVcase also illustrates something that happens to successful vertical software companies.
They often start by solving one painful problem exceptionally well.
Then they discover that the user’s real problem begins earlier and ends later.
Ground Mount can make solar layouts faster.
But developers still have to choose the site.
So Prospect matters.
A layout can be engineered perfectly.
But somebody still needs to understand how much electricity it will produce.
So Yield matters.
Commercial solar requires a different physical environment.
So Roof Mount matters.
Equipment data has to move between them.
Terrain has to move between them.
Electrical assumptions have to remain consistent.
Eventually, the individual application stops being the product.
The workflow becomes the product.
Finding the mistake while it is still a line on a screen
PVcase’s latest releases are not one dramatic product launch.
They represent something more incremental and perhaps more important: a mature engineering platform systematically removing uncertainty from different stages of solar development.
Ground Mount 2.64 and 2.65 improve how projects react to terrain and electrical constraints.
Roof Mount continues automating increasingly detailed rooftop engineering.
Yield is reducing manual data entry and strengthening the bridge between physical design and energy simulation.
Prospect is pushing grid feasibility and upgrade economics toward the beginning of site selection.
Together, they move more decisions to the point where changing them is still cheap.
Before the excavators arrive.
Before kilometres of cable are ordered.
Before land development advances too far.
Before an interconnection surprise destroys the economics.
Solar development will always involve uncertainty.
The weather changes.
Equipment prices change.
Electricity markets change.
Grid conditions change.
Software cannot eliminate those risks.
But it can expose more of them sooner.
And that may ultimately be the most valuable thing PVcase is building.
Not software that simply helps engineers design solar farms faster, but software that helps them discover expensive mistakes while those mistakes are still only lines on a screen.
Learn more: https://pvcase.com