Digital-twin bird-repellent system: 1,500 towers on one screen

A bird-hazard platform for a regional grid operator's transmission maintenance team, delivered as a data wall, a mobile app and an admin back end. An administrative map carries weather, devices, video, repellent statistics and AI alarms on one screen; open a tower and you get its record, its live camera and its current strategy — and you can change that strategy remotely.

Industry
Power grid · transmission line maintenance / bird-hazard control
System type
Operations data wall + mobile app + admin back end (browser based)
Key technology
GIS map and marker rendering · video ingest and PTZ control · AI vision alarms · remote control and strategy push · time-series data and forecasting · alarm handling workflow
Jiding's role
Requirement shaping, prototype and visual design, front and back end, device and video integration, deployment, training and maintenance
1,500Towers in scope, with 168 repellent points and 118 online
7Counties on one map: polygons, markers, heat map, forecast
5Laser modes: bird zone, open farmland, closed paddy, highway, site
45Days from prototype to launch: 1 designer, 1 front-end, 2 back-end

The Problem

Bird hazard is not "a bird on a wire". It is four different faults

The most common public question is why a bird can sit on a high-voltage conductor unharmed. The answer is simple: two points on the same conductor sit at the same potential, so there is no circuit. What causes outages is everything the bird does besides perching. Separate the four mechanisms and you know when, against which bird and with which tool a repellent device should act.

Streamer flashover: the largest share

A bird excretes from an insulator or crossarm; the wet streamer bridges the live conductor and the earthed crossarm, or forms a conductive path along the insulator surface, and it flashes over. Public industry reporting puts excrement-related faults at roughly 80% of bird-related outages, with the probability rising sharply in fog, drizzle and high humidity — which is why rainfall and humidity sit in the first row of the weather card.

Nest short-circuit: the material conducts

Magpies and crows prefer stable towers, and their nests often contain wire and wet twigs. A nest spanning two phases, or conductive material dropping between a live part and the steel, causes a phase-to-phase or earth fault. Wet nests conduct better, so nest clearing before the rainy season is a fixed maintenance task.

Body bridging: a problem of large birds

The Oriental stork is nearly a metre long with a much wider wingspan. Taking off, landing or spreading its wings, it can touch two conductors at different potentials, or a conductor and the tower, and become the circuit. These faults often injure or kill the bird, which is the real origin of the phrase "repelling birds is protecting birds".

Pecking damage: slow and cumulative

Some species peck insulators and composite parts. A single peck shows nothing; accumulated damage degrades insulation and creates a latent defect. This does not appear as a sudden outage but in equipment life and maintenance planning, and is found through inspection and image comparison.

>10%Share of transmission outages caused by birds, third after lightning and external damage
15–30%Share on sections with heavy bird activity; higher near wetlands and forests
80%Approximate share of excrement flashover within bird-related faults
Oct–AprSeasonal peak; within a day, 20:00 to 07:00

Sources: public industry reporting and commentary on DL/T 1570–2016, the Chinese standard for bird-hazard risk grading and distribution mapping. Figures describe the problem, not measurements from this project.

Why passive devices stop working. Spikes, windmills and reflective tape are fixed once installed: fixed position, fixed intensity, fixed timing. Birds adapt within weeks, and when a device ages or falls off nobody notices in time. A single ultrasonic emitter has blind spots, and wind, terrain and ambient noise all change its reach. The result is the sentence every maintenance crew knows: "cleared, rebuilt, came back". Breaking that loop takes more than a stronger device — it takes a chain where region, time window, method and effect can all be observed and adjusted.
One daily pattern worth designing around. Bird activity peaks at dawn and dusk, which is exactly when take-offs and landings on towers are most frequent; at night, poor visibility and heavy dew make a flashover harder to spot immediately. The delivery build therefore sets its two "high-pressure windows" at 06:00–08:00 and 16:00–17:00, and pushes resources into those two peaks instead of spreading them evenly across 24 hours.

The Local Constraint

In Huai'an, you cannot simply scare everything away

The build is labelled a Huai'an-specific edition, and that is not a skin with a different place name. Huai'an sits in the lower Lixiahe plain by Hongze Lake: dense waterways, continuous wetlands, and a major stopover on the migratory flyway. The birds are numerous and many are protected, so the system has to work by zone, by time window and by method — not by one switch that turns everything on.

200+ species

Hongze Lake wetland hosts more than 200 bird species; the nature reserve has recorded 245, and close to a million migratory birds winter here each year. Device density and bird complexity both exceed what foot patrols can cover.

Oriental stork

A national first-class protected species with a global population under 10,000, nicknamed the giant panda of birds. It prefers to nest high, and suitable trees are scarce in the wetland, so transmission towers become the first choice — here the bird and the line are the same problem.

Three protection zones

The publicly described local practice divides the area into three zones: the core reserve bans acoustic and light repellents and uses insulated covers and artificial nests; the buffer zone combines sound and light; only the general zone uses the full toolset. A system must be configurable per zone.

That constraint changed the product design. Conventional repellent products assume stronger is better: full power, maximum volume, running around the clock. In a wetland core zone, loud sound and bright light disturb the very species the project is meant to protect. So "repelling" became a set of pushable strategies: selectable mode, adjustable intensity, controllable time window, individually sleepable devices — and the evidence is kept. Every trigger leaves a snapshot, a record and a handler, which proves the device was working and that the site was not over-disturbed.

For maintenance: from "drive and look" to "look, then drive"

At 1,500 towers, a vehicle-and-eyes round takes weeks. The system surfaces the three questions that matter today — which towers have birds, which devices are offline, which strategies fell below 90% coverage — so inspection follows signals instead of a fixed route.

For management: from "we installed devices" to "here is the effect"

Arrivals, repels, success rate and exception closure can be pulled by county, by circuit and by month. Reporting upwards no longer stops at "how many units", but answers how many arrived, how many were repelled and how much risk remains in this district this month.

Architecture

Architecture: one field layer, one platform layer, three entry points

The usual mistake in this kind of system is treating the data wall as the whole product. The wall is only the outer skin; underneath it need device ingest, a strategy engine, video and AI, and an alarm workflow. Devices, protocols and camera vendors are never uniform — that integration is where the real engineering sits.

Three layers: the field executes and senses, the platform decides and records, the entry points only present Field layer Tower terminals · solar power · 4G / 5G backhaul Laser repellent unit (line / sweep) Ultrasonic + acoustic emitters Cameras (visible light / PTZ) Radar / IR presence detection Micro weather (temp / RH / rain) Pulse / boost output (adjustable) Platform layer Ingest, decide, push, record Device ingest & twinprotocols · status · read-back Strategy enginemode · window · level · linkage AI visiondetection · confidence · snapshot Alarms & ticketsseverity · dedupe · dispatch Time seriesarrivals · repels · rate · trend Roles & auditroles · logs · sign-in history Third-party services: maps · weather · video platform · SMS Wrapped once; swapping a vendor does not touch business code Device comms: commands, state, reconnect Application layer Three audiences, three views Data wall control room · whole area · alarms loud map, video, broadcast, forecast Mobile app in the field · read status · get alarms read-only; no control from a phone Admin back end device register · repair history · users menus · access logs · feedback strategy templates · data export
Field devices only execute and sense; every decision and every trace lives on the platform. All three entry points share one API, so the same figure is not computed three times.

Why device ingest is its own layer

A site may run three or four brands of repellent units and two or three camera brands. Keeping protocol differences inside the ingest layer means upper layers only see "device ID, capability set, parameter table", and replacing hardware does not touch a page.

Why strategies live on the server

A strategy is not a switch on a screen but a rule: under which condition, do what. On the server it can link neighbouring towers, respect a time window, and be audited — who changed what, and when.

Why the wall is not a report

An operator is not there to read reports but to find out what to handle now. The wall orders information as alarms, strategy gaps, offline devices, trends, then history — and that order decides the layout.

Screen Layout

The wall: three columns, alarms always on the right

More than forty information points have to fit a 1920×1080 screen. The answer is not density but a fixed reading path: left answers "are the environment and the devices healthy", centre answers "where are the birds and the risk", right answers "what do the numbers say and what needs handling". Three questions, three columns, nothing to hunt for.

Layout: left "environment and devices", centre "space and risk", right "numbers and events" Digital-twin bird-repellent system Area-wide bird situation 2026.06.09 14:00 Area overview towers 1,500 · points 168 Standard sensors 168 total · 118 online · 98% AI vision 10 total · 8 online · **** Strategy watch 18 towers below 90% coverage Weather 7 days · rain · humidity · wind 15° 06/10 clear 25°C06/11 cloudy 28°C 06/12 rain 26°C06/13 storm 29°C rain 15mm · RH 55% · NE force 4 Device status no.  device       state   arrivals 1   tower 1     normal   10 2   tower 2     normal   15 3   tower 3     fault    9 4   tower 4     normal   15 5   tower 5     normal   15 6   tower 6     normal   4 7   tower 7     normal   9 ● Visual feeds tower 1tower 2 tower 3tower 4 Huai'an · 7 counties · tower markers · heat map · forecast T1T2T3 T4T5 layers: base / markers heat map / forecast toolbox: add / edit remove / faults export data wetland view Repellent broadcast 95% repels     100 arrivals   100 repelled  100 success   95% zones 1 / 3 / 5 06-08  16-17 Trend / risk forecast by county · by circuit · by month AI alarms 1  T1  device fault    open  06/12 2  T2  obstruction     open  06/12 3  T3  obstruction     done  06/12 4  T4  device fault    done  06/12 5  T5  obstruction     done  06/12 6  T6  obstruction     done  06/12 1 2 3 4 5 6 7
Redrawn from the 1920×1080 delivery build: ① four overview cards ② weather ③ device list ④ visual feeds ⑤ county map with layer toolbar ⑥ broadcast and forecast ⑦ AI alarm feed.

Why 1,500 and 168 sit side by side

1,500 is the tower register that defines scope and responsibility; 168 is the number of installed repellent points, of which 118 are online and 98 healthy. Scope alone suggests full coverage; online counts alone hide the gap. Placed together, the shortfall is visible — which is why the strategy card raises its own alarm when 18 towers fall below 90% coverage.

Why alarms sit bottom right

On a dark wall the eye lands on the central map first, then sweeps sideways. The alarm feed sits bottom right because it needs to be scanned, not to shout: genuinely urgent events pop up and push to mobile. A fixed position, a rolling list and red for open items beat a blinking screen, and avoid alarm fatigue.

Why four map layers

The base map answers "where", markers answer "which device", the heat map answers "where are the birds", and the forecast layer answers "what happens next". Four layers for four questions; switching is cheaper than stacking everything, which usually means nothing is legible.

Why weather gets a whole block

Bird behaviour tracks weather: rain, humidity, visibility and wind change both perching and flight, and they change how well laser and acoustics work. Weather sits top left so the operator knows what kind of day it is before reading any number.

One Tower

Open one tower: record, picture and control in a single panel

The wall answers "how is the area doing"; the panel answers "what do we do about this one". Click a marker and the full site appears: which circuit it sits on, who maintains it, what strategy it runs, what went wrong before, and what the camera sees right now. This is where maintenance work actually happens.

Device detail panel: device number and ID, district, address, circuit, maintenance crew with call button, repellent strategy and boost toggle, linkage radius options of none, 300 and 1,000 metres, bird pressure low medium high, five laser modes, a statistics chart, control buttons for deferral, fault report, sleep and start, and a live video pane with a PTZ pad and zoom slider
Device detail (delivery build with demo data): identity and strategy on the left, video and PTZ on the right, controls at the bottom. Look, judge and act without leaving the panel.

What a device record has to hold

None of these fields are decorative. Each answers a question that comes up on site: who to call, whether a parameter was changed, whether linkage fired, how heavy the bird pressure is here.

FieldExampleWhy it must exist
Device number / IDTower 1 / 00000152The number is what crews say on site, the ID is the system key. Tickets, alarms and repair history all align on it.
District / addressDistrict 1 / Jinhu, Huai'anDecides who responds, which county figures it lands in, and which protection zone applies.
Circuit500 kV line #3Bird-hazard accountability and outage impact are both counted per circuit.
Maintenance crew / contactCrew Wang / one-tap callAn alarm is useless without a person, and it has to be this tower's owner, not a general duty line.
Strategy / boostBase strategy / onBase is the norm; boost is a temporary step-up for a heavy period. Kept separate so it can be rolled back.
Linkage radiusNone / 300 m / 1,000 mOne unit covers little. Neighbouring towers acting together create a repellent band.
Bird pressureLow / medium / highA human-assigned risk level for the section; drives thresholds and inspection frequency.
dB range / frequency range10–100 / 10–100Intensity and band of the acoustic output. This is a recipe, not a volume knob, because birds adapt to a fixed band.
Pulse rateper minuteSets the rhythm of stimulation. Too dense speeds up adaptation; too sparse never disturbs.

Control is not four buttons. It is a chain that leaves a trace

Six actions on site

  • Start / sleep: sleep is for maintenance, work at height and temporary closures — not "power off"
  • Pulse adjust: tune the rhythm to the current bird situation, effective on push
  • Boost: a short step-up during migration peaks or repeated triggers
  • Strategy settings: mode, dB and frequency ranges, linkage radius
  • Report fault: one tap creates a repair ticket carrying the device ID and a site photo
  • PTZ and zoom: eight directions plus zoom, so one camera covers three approaches

Every push must answer three questions

Who changed it — operator, time and IP go to the log. What it became — a parameter snapshot is pushed, not "a switch was flipped". Whether the device agreed — the platform reads the value back after the command and shows the reported value, not the typed one.

These look like back-office details, but they decide whether crews can trust the system. Without read-back, "on" may only mean "the command left"; without a log, nobody can say who enabled sound and light in the core zone, or when.

An easily missed decision: video lives with the strategy. When an alarm fires, the first thing an operator does is look. If video sits in another system, another window and another device search, the alarm is effectively dead. So live picture, PTZ, strategy and history share one layer: see, judge, act — without switching screens.

Strategy

Five laser modes: repelling is a recipe, not a switch

The same unit does entirely different work in different places. Beside a paddy it deters birds after the grain; beside a highway the beam must not distract drivers; on an industrial site it has to protect people as well as equipment. So the system makes the mode selectable, the intensity a range, and the timing a condition — not one on/off switch.

ModeTypical sitingStrategyMain constraint
Bird zoneWetland edges, flyways, dense tower sectionsRepel-first: wide sweep, sensitive triggering, stronger at dawn and duskCore reserve needs lower intensity or physical protection instead
Open farmlandPaddies, wheat fields, aquaculture pondsFollow the farming calendar: denser at sowing and harvest, low-level otherwiseMust not interfere with farm work or people
Closed paddyContinuous paddy, controlled-water polder areasLinked to water level and the farming cycle, closed-loop, fewer wasted triggersRequires alignment with local farming schedules
HighwayLine crossings, ramps, bridge sectionsLimit beam height and angle, keep it out of the driver's field of viewMust not distract drivers
Industrial siteSubstation surroundings, parks, warehousesProtect people and equipment, define no-beam zones, lower power at nightDense human activity; needs interlocks and signage

Mode names come from the delivery build; parameter ranges are calibrated on site and are not published here.

Intensity: dB range

Louder is not better. Excessive sound pressure invites complaints and speeds up adaptation. The system pushes a range (for example 10–100) and the device varies within it, so one intensity is never repeated long enough to become background.

Band: frequency range

Species differ in sensitivity, and a fixed band stops working within weeks. An adjustable range keeps the stimulus irregular — the industry's standard way of delaying habituation.

Rhythm: pulse rate

Measured per minute. Dense while a bird is settling, lower once it moves off. This is the most "feel"-dependent parameter, so crews tune it per device on site rather than applying a global value.

Linkage: why 300 or 1,000 metres

One unit has a limited reach, and a bird driven off often just moves to the next tower. A linkage radius makes neighbouring towers act together, forming a repellent band. 300 m suits closely spaced towers in general zones; 1,000 m suits open flyway sections. Too wide a radius has a cost: a false trigger sets off a whole row and becomes a nuisance.

Coverage: why the 90% line

The strategy card does not count devices; it counts how many towers fall below 90% strategy coverage — the share of required hours in which the strategy actually ran. A device that is online but running the wrong strategy is not installed in any useful sense. That line separates "fitted" from "working".

Alert Loop

194 exceptions: every cell has an owner

With many devices, the risk is not too few alarms but too many to read. Each exception becomes one traceable row: what type, what state, when it fired, who handled it, how. One row, one small closed loop.

Exception statistics panel: device number, device ID, district, address and maintenance crew at the top, then a table with index, exception type, handling state, alarm time, handling time, handler and remarks; types include obstacle, device and lidar faults; the footer shows ten rows per page and 194 records in total
Exception register (delivery build): 194 historical records for one tower, newest first, open rows in red. The same table serves as history and as a to-do list.

Three types, three routes

Obstruction: something that affects safety appears in frame — a flock, debris, machinery — and video review decides between repelling and dispatch. Device fault: the unit itself is failing, offline or losing power, so it becomes a repair ticket. Lidar fault: the detection unit misfires or sees nothing, usually calibration or obstruction. All three share one table; the type column routes them.

The remarks column carries the most information

Remarks seen in the delivery build include lidar, device alarm, false target, recovered after restart, strategy adjusted, fault cleared. Those few words separate an alarm from a fact: a real bird event, a failing device, or a model that misread the scene. Without that column, 194 records are just 194 red dots.

Five steps every alarm must walk; skip one and the record stops being trustworthy 01 Trigger radar or vision detects snapshot, ID, timestamp 02 Rank & dedupe merge a persistent target priority by zone and hour 03 Video review pan, tilt, zoom to confirm real event or false target 04 Respond remote boost or new strategy or dispatch a repair ticket 05 Archive & feed back handler, time, remark false targets tune thresholds False and missed alarms reviewed monthly; thresholds and bands retuned; next round of step 01 Step 3 is human and cannot be skipped. AI supplies a lead; a person signs the judgement — that is both accountability and the training sample for the next model.
The alarm loop. The dashed path is the feedback edge: the outcome is not the end, it is the input to the next threshold change.
About false alarms, plainly. Outdoors, light changes, rain, fog, moving vegetation and insect webs all fool vision models. Public practice shows a single model rarely reaches an acceptable false-alarm rate; the usual answer is edge screening, cloud re-check and human confirmation in three stages. This system makes "false target" a formal outcome rather than a shrug, so the rate becomes a number that can be measured and reduced.

Numbers That Matter

Numbers: three to judge the effect, four to plan the next move

Bird data is easy to turn into charts that look busy. This build keeps only what can guide an action: arrivals, repels, success rate, plus a county-by-county comparison. The four risk forecasts answer not "how was yesterday" but "where do we send people tomorrow".

Data wall with the repellent broadcast ring showing 100 repels, 100 arrivals, 100 repelled and a 95% success rate, pressure zones 1, 3 and 5, high-pressure windows 06:00 to 08:00 and 16:00 to 17:00, and a trend chart with activity, perching, nesting and flocking risk curves
Trend and risk forecast (delivery build): bars for arrivals and repels, a line for success rate; a second view swaps in activity, perching, nesting and flocking curves.

Why success rate alone means nothing

Success rate is repels divided by arrivals, and it is easy to inflate: count a false alarm as a repel, or an unconfirmed target as an arrival, and the number looks excellent. The three figures therefore always appear together, and they must reconcile with the "false target" remarks in the register. A lone 95% explains nothing.

Why pressure zones are 1, 3 and 5

These are not voltage levels but repellent intensity steps. 1 maintains, 3 steps up, 5 is the strongest, matched to bird pressure and protection requirements. Steps make accountability explicit: a core reserve can be pinned at 1, or left to physical protection only, instead of being swept up by a default "everything on".

Four risks, four actions

Activity high → inspect more often. Perching risk high → check whether repellent units are online. Nesting risk high → schedule nest clearing and baffles. Flocking risk high → start linked repelling and notify the district. Four indicators, four responses — not four decorative curves.

Two spatial views: corridor and wetland

Urban circuits are read as a corridor: repels, pressure points and windows by county and section. The wetland is read as an area: east bank, west bank and a five-kilometre band. Two spatial conventions coexist because the managing bodies and the performance measures differ.

How a forecast is used matters more than how accurate it is. These models produce a trend, not "37 birds at 14:00 tomorrow". Their real value is ranking: put the highest-risk sections of the next 24 hours at the top so a crew knows where to drive first. That is also why the forecast shares a block with the trend view, switched rather than placed side by side — history is read to judge the future, and two panels in parallel only split attention.

Mobile

Mobile: the screen a crew needs at the foot of a tower

The wall lives in the control room; people live in the field. The app is not the wall squeezed onto a phone. It keeps only the four things that matter on site: which towers need a strategy change today, which device is faulty, what the weather is doing here, and whether an alarm has been handled. All control stays on the desktop.

Mobile home, upper part: strategy warning that tower 1 is below 90% coverage, then three status cards for area overview, standard sensors and AI vision, followed by weather and a device list
Three status cardsscope, online, cameras — a conclusion first
Mobile home, middle: device list with device name, state, arrivals and a view action, then a broadcast ring and tabs for trend and risk forecast
Devices and broadcastthe list drills into a single unit
Mobile home, lower part: four visual feed thumbnails for towers 1 to 4 and a three-tab bottom bar with home, notifications and account
Visual feedsfour rotating views, three tabs to close

The mobile home screen is cut into three segments top to bottom (demo data). The strategy warning sits at the very top: the only red banner expanded by default.

Why the warning is first

The first screen has limited space, and whatever sits first becomes "today's most important thing". Towers below 90% coverage are the gap that must be closed today, ahead of any statistic.

Why only three tabs

Home, notifications, account. Field staff do not manage registers, edit roles or export reports from a phone — that is office work. Fewer tabs means fewer mis-taps with one hand and gloves on.

Why control is not on the phone

Starting a laser, changing intensity or putting a unit to sleep touches personal and equipment safety, and needs permission checks, a second confirmation and an audit trail. That is hard to do well on a small screen, so it is not offered. One fewer entry point, one fewer class of incident.

Screens & Design Process

Screens and design: the delivery build, and how it grew

Projects like this start as grey wireframes that settle information hierarchy, then move to visuals that answer a different question: on a dark wall, at three metres, can this line be read? The four screens below are the delivery build; the three after them are wireframes from the same period. Compare them and you can see what never changed and what did.

Area-wide bird situation wall: four overview cards on top, weather, device list and visual feeds on the left, a Huai'an county map with tower markers in the centre, broadcast ring, trend chart and AI alarm list on the right
Area view · trendright column shows arrivals and repels with a success line
The same wall switched to risk view: the right column shows four curves for activity, perching, nesting and flocking risk, every other block unchanged
Area view · risksame slot, four risk curves, layout untouched
Device detail panel: identity, strategy parameters and statistics on the left; live video and PTZ on the right; six control actions at the bottom
Device detailidentity, strategy, picture and control in one panel
Exception register panel: table of exception records with type, state, alarm and handling times, handler and remarks; pagination shows 194 records
Exceptions194 records, pageable, open rows in red
Desktop sign-in page: dark blue technical background, centred panel with system name, account, password and a sign-in button above a circular light effect
Sign-inthe front door, and where the dark palette was fixed

Three wireframes, three decisions that mattered

Grey wireframes are good for structure. Set against the delivery build, the interesting part is not that it became prettier but three specific information-design calls.

Home wireframe in greyscale: weather, device list and visual feeds on the left, Huai'an map with tower labels in the centre, broadcast, trend and alarms on the right, and four tool buttons at the bottom
Wireframe · homethe three-column structure was already fixed
Device detail wireframe: device fields and strategy parameters, dB and frequency range inputs, a statistics bar chart and control buttons on the left; a video placeholder with a PTZ pad on the right
Wireframe · devicesplit layout, controls pinned to the bottom
Exception register wireframe: header fields for device number, ID, district, address and crew, a seven-column table and pagination
Wireframe · exceptionsseven columns fixed; not one was added later

Change one: cards became numbers

The wireframe's four top cards were blocks of explanatory text. The build keeps a label line and a number line with at least a 2× size difference, because operators scan the wall standing up: at three metres you read a number, not a sentence.

Change two: a table became a feed

The wireframe showed alarms as a table with a header row. The build uses a header-less, newest-first list with open items in red. A wall cannot show scrollbars, and long device names wrap in fixed columns. The list trades density for "see the latest at a glance".

Change three: layers, not more data

The wireframe map already had county polygons and tower labels. The build adds layer switching (base, markers, heat, forecast) and a toolbar instead of stacking a heat map on top of everything. Four questions, four views.

What did not change matters more. Fields such as dB range 10–100, frequency range 10–100 and a linkage radius of 300 or 1,000 metres survived from wireframe to delivery untouched, because they come from on-site calibration, not from a designer's imagination. Fix the structure first, skin it second — that is what keeps rework out of industrial systems.

Deliverables & FAQ

Deliverables and five common questions

The project shipped as three ends — wall, back end and mobile — plus six implementation documents. Schedule: 45 days, two weeks of testing, staffed with one designer, one front-end and two back-end engineers.

What was delivered

  • Data wall: weather, device status and detail, visual feeds, repellent broadcast, trend and risk forecast, AI alarms, wetland view, area overview
  • Map: county polygons, tower markers coloured by state, heat map, forecast layer, click-through drill-down
  • Device control: remote start and sleep, pulse adjustment, boost, strategy push with read-back, fault reporting
  • Strategy set: five laser modes, dB and frequency ranges, linkage radius, bird-pressure levels
  • Alarm loop: three exception types, handling state and owner, remarks, paged queries
  • Admin: device register and repair history, device types, users, roles, organisation, menus, base configuration, sign-in history, access logs, exception feedback
  • Mobile: three status cards, device list, broadcast, visual feeds, notifications, account
  • Third-party services: weather, maps, video and device communication, integrated and wrapped once

How it was implemented

Six delivery steps: operating manual and documentation with optional video → two training sessions, before and after launch → testing, tuning and optimisation before go-live → launch plus system and document handover → day-to-day maintenance covering uptime, code updates, database backup and server care → after-sales guidance during use. The system runs on a dedicated server.

The hard part is never the page; it is integration. Device protocols, the video platform, maps and weather each come from a different supplier with different field names. Wrapping them in the ingest layer first is what keeps the pages from being tied to any one vendor.

As agreed, no client name, pricing or hours appear here; screens are delivery builds with demo device IDs, addresses and names.

How does this relate to the spikes and baffles already on the towers?

Physical protection answers "where a bird cannot perch"; active repelling answers "a bird is here and must move on". Spikes, baffles and insulated covers are fixed once installed; laser, ultrasonic and acoustic output can change by season, by time window and by zone. The two do not compete: a core reserve relies on physical separation plus artificial nests, while corridors and general zones rely on active repelling — and the system manages the strategy and the evidence for the latter.

Why show 1,500 towers and 168 online points on the same wall?

They are two different measures. 1,500 is the register that defines scope and responsibility; 168 is the number of installed repellent points, with 118 online and 98 healthy. Scope alone suggests full coverage; online counts alone hide the gap. Placed together, the shortfall is obvious — which is exactly why the strategy card raises its own alarm.

AI detects birds — what happens with false positives?

The system supplies leads, not verdicts. Every alarm carries a snapshot, device ID, confidence and timestamp; an operator checks the video and records the outcome as a real event or a false target. False alarms are not discarded; they are kept as a formal result, counted by device and by hour, and used to retune thresholds and the model. A meaningful share of the 194 records in this build are false targets, which is why the remarks field exists.

How is remote control kept safe?

Three constraints. Permission: control actions are role-based, and start, sleep, boost and parameter changes all leave an operator and a timestamp. Interlock: sleep is tied to maintenance tickets, so a unit cannot start while someone is working at height. Visibility: every push is followed by a read-back, and the screen shows the reported value rather than the typed one. Laser units must also meet exposure-safety rules, and core reserves disable sound and light by default.

Why build a mobile app at all — is the wall not enough?

The wall is in the control room; people are in the field. During patrols, repairs and temporary closures, a crew lead needs to know which towers need a strategy change, which alarm is still open and what the weather is doing here. The app keeps reading and receiving only: three status cards, device list, broadcast, visual feeds, alarms. Control stays on the desktop, behind permission checks and a second confirmation. Doing less is what makes it hold up outdoors.

MORE CASES

More Related Cases

Digital-twin bird-repellent system
Digital TwinEcological bird repelling, visual analysis

Digital-twin bird-repellent system

A bird-hazard platform for a regional grid operator's transmission maintenance team, delivered as a ...

View Details →

View All Cases →

Planning a similar production line or enterprise system?

Start with our pricing logic, then let's talk requirements — cost structure, technology comparison and acceptance criteria, all laid out in the open.