One operational picture across every wind farm
Each turbine carries its own record: wind farm, manufacturer, model, platform, serial number and layout position. That hierarchy is the backbone of the platform, and it is why fleet filtering behaves the same way on a dashboard, a work order and a maintenance session.
The dashboard reads directly from those records. Fleet counts, turbine status distribution and the day's workload are derived from the same data the field team updates, so the numbers a manager reviews in the morning are the numbers the technicians produced.
- Fleet and wind-farm filters with an all-turbines view
- Turbine status shown as fault, maintenance or operational
- Wind-farm records with country, region, capacity, commissioning data and layout
- Company-scoped data separation between customer workspaces
Operational status that reflects real work
Aerokasix separates master data from live operational state. Lifecycle status is set by an authorised user and stays put. Operational status is derived from what is actually happening: an open corrective incident puts a turbine into fault, active maintenance work puts it into maintenance, and the turbine returns to operational when the work is closed.
That separation matters in operations reviews. Nobody has to guess whether a turbine is flagged because of a real fault or because someone edited a field during commissioning.
Designed for the roles that coordinate the fleet
The platform is built around the people who carry operational responsibility: general managers and operations directors reviewing performance, wind farm and O&M managers assigning work, site supervisors keeping the day moving, and the technicians and engineers executing it.
Role-based access control keeps the fleet view available to the roles that need it and restricts administrative configuration to the people accountable for it.