11 KiB
Snippets pour l'assistant LibreDesk
Base de connaissances de l'assistant LibreDesk (Admin → AI → Snippets) : un snippet par section ##, le titre en titre, le corps en contenu, à coller à la main. En anglais (D-023) : l'assistant répond dans la langue du client. Glossaire du product owner : target, reference, point ; jamais de cause affirmée, « consistent with ».
Sources : partie 1 des guides docs/<domaine>/guide/, labeling/familles.md, labeling/connaissances/ (chaîne de mesure, cycle thermique, trous), FAQ AIMsight 1.5 (autonomie). Ni nom de station, ni nom de client, ni tension brute (clients). À refaire quand ces sources changent.
Ces snippets décrivent des phénomènes : le client ne voit pas encore les couleurs du jour de la maquette « System Summary ». La FAQ AIMsight complète (installation, cibles, export, alarmes) s'importe à part, une question par snippet, ou par « Import from URL » si elle est en ligne.
How AIMsight measures displacement
An AIMsight station is a camera that watches targets (prisms or reflectors) fixed on a structure. For each measurement, it finds every target in the image and records its position.
The camera itself moves a little: wind, sun, temperature. To remove this, the station also watches reference targets, placed on ground or structures assumed not to move. From the references, it estimates the camera's own movement and subtracts it. The result is the corrected displacement of each target, shown on the curves.
So a change on a curve can come from three places: the target really moved; something disturbed the view (weather, an object, light); or the correction from the references was disturbed (a reference hidden or poorly visible). The camera image of the same moment is the best way to tell them apart.
Why are my displacement curves not flat?
Most of the time, a spike, a short jump, noise or a gap on the curves is not a movement of the structure. It is a moment when the measurement should not be trusted. Typical causes:
- poor visibility: rain, fog, condensation on the camera window, low light, a dirty lens;
- heat shimmer: hot air makes the image tremble on warm days;
- something in front of a target: a vehicle, a train, a plant, snow, a spider web;
- a reference hidden or poorly visible, which shifts several targets at once;
- the normal daily expansion and contraction of the structure with temperature.
A real movement of the structure is rarer, but it happens. It usually looks different: a jump that lasts, or a slow drift that does not come back. When in doubt, check the camera images of that moment, and contact AIMsight support.
Rain, fog, condensation and low light
When visibility drops between the camera and the targets (rain, fog, condensation on the window, low light at dawn or dusk, a dirty lens), all targets are seen less well at the same time. The curves become noisy, show spikes, or some values are missing because the station rejected them.
This is not a movement of the structure. The values in that period should not be trusted. They return to normal when visibility comes back. The camera images of that period usually show the cause.
If poor visibility comes back every day, or never clears, the camera window or the targets may need cleaning: contact AIMsight support.
Heat shimmer (atmospheric turbulence)
On warm, sunny days, hot air rising between the camera and the targets (for example above a road or a sunlit surface) makes the image tremble. This is the same effect as the shimmer seen above a hot road.
On the curves, it shows as fast noise during the warm hours, often stronger at midday, and calm at night. It is not a movement of the structure. AIMsight can reduce this effect by combining a series of images for each measurement; on strong days some noise remains.
Something in front of a target
A vehicle, a train, a construction machine, a plant, snow, an animal or a spider web can hide one or a few targets, while the others stay normal. The hidden target's curve then shows a spike, a short jump, or missing values for the time the object stays there: a single measurement for a passing vehicle, weeks for a growing plant.
This is not a movement of the structure: ignore that target's curve for that period. The camera image of that moment usually shows the object. If the object stays (vegetation, a parked vehicle, snow on the target), it has to be removed on site for the target to be measured again.
A jump that comes back
A jump that returns to the previous level after some time is, in most cases, not a movement of the structure. Common causes are something passing in front of a target, a reflection, a moment of poor visibility, or a reference that was briefly hidden or poorly visible: the camera correction is then computed without it, and several targets shift together until it is seen again.
What makes such a jump harmless is the return to the previous level. A jump that does not come back is a different case: see "A jump or a drift that lasts".
Daily waves: the structure expands and contracts
Many structures expand when they warm up during the day and contract at night. The curves then show a wave that rises and falls with the temperature, day after day. The camera and its support also move with temperature; most of that is removed by the correction from the references.
This is normal and needs no action. A typical sign: at the same temperature, the target comes back to the same position. A change that follows the seasons slowly can also be thermal.
What is not explained by temperature, or does not come back when the temperature does, should be looked at: see "A jump or a drift that lasts".
A jump or a drift that lasts
A jump that stays at its new level, or a slow drift that keeps going, can be a real movement of the structure. It can also come from the measurement: a reference that moved, a changed configuration, or a correction that is no longer well constrained. The data alone cannot always tell them apart.
What helps: whether the camera images of that moment show anything unusual (weather, an object, work on site); whether several targets move together, and how; whether other monitoring on site saw something.
Such a change should never be dismissed. Contact AIMsight support with the station, the targets and the dates: they look at the images and the measurement details with you. If the structure is safety-critical, follow your own alert procedure without waiting.
A target that is almost never measured
A target whose values are missing or rejected most of the time, every day, in all weather, usually has a problem of its own: it is dirty, damaged, turned away from the camera, partly covered, or its configuration needs to be redone. Its neighbours are measured normally.
Ignore that target's curve until it is fixed. Check the camera image: is the target still visible, clean and facing the camera? Then contact AIMsight support to clean, realign or reconfigure it.
No data at all for a period
When all curves of a station are missing for a period, the station did not send measurements for that time. This does not always mean the station stopped:
- the most recent hours may just not be synchronised yet, and appear later;
- a gap at the same time on several stations points to a common cause outside the station (transmission or reception), not to the station itself;
- a gap can also come from a loss of power or of the 4G connection.
Measurement, transmission and display are separate steps. AIMsight support can tell which one failed from the station's own metrics. Contact them if a gap lasts, comes back, or if the latest data is several hours old.
Station power: battery and solar panel
An AIMsight station runs on an internal battery, charged by a solar panel or by mains power. With a typical measurement every 15 minutes, a full battery lasts about five days without any charging (indicative; it depends on configuration, weather and battery condition).
A full battery alone is not enough: what matters is whether the energy received each day covers what the station uses. A single cloudy day, where the battery does not fully recharge, is normal. Several days in a row without a full recharge (for example in winter, with snow on the panel, or shade), or a mains station losing its power supply, will end in night-time shutdowns if nothing changes.
When the battery runs too low, the station shuts down to protect itself and starts again once it has recharged enough. Contact AIMsight support if the station stops at night, or if poor charging lasts more than three days.
4G transmission
The station sends its measurements over 4G, typically every 15 minutes. A few missing sends in a day are common and harmless. If the station is silent for many hours, it may have lost its 4G connection, or its power: check both.
A weak signal does not mean lost data: a station at the edge of the coverage area can transmit everything. The signal is an indication, not an alarm.
Losing the connection does not necessarily mean the station stopped measuring; it may continue while powered. Remote alarms (email, SMS, cloud notifications) cannot be relied upon while the connection is lost. Contact AIMsight support if the station stays silent, or if missing sends repeat day after day.
Station disk space
The station stores its measurements and images on its own disk. What matters is how much free space remains, and how fast it fills up.
When free space gets low (below about 20 %), or the disk would be full within about two months at the current rate, there is still time to act: AIMsight support should be told. Below about 10 %, or full within two weeks, contact support now. These thresholds are provisional.
Station overheating
The station contains a small computer that processes the images. If it gets too hot, it slows down to protect itself. The limit is the maximum temperature given by the manufacturer (97.5 °C).
If it reaches it, the station may have measured less or more slowly during that time: contact AIMsight support. If no temperature was measured at all, the station may have been off: check its power first.
What AIMsight's diagnosis can and cannot say
AIMsight shows evidence: the curves, the camera images, the station's own measurements. From these, it can say that an observation is consistent with a cause (rain, a passing vehicle, a hidden reference, thermal expansion). It does not claim a cause it cannot prove, and the final judgement on the structure belongs to the client and the engineers in charge.
A missing value does not mean the station stopped, and a quiet curve does not prove nothing moved during a gap. When the evidence is not enough, AIMsight says so and looks further.
Réglages proposés pour l'assistant (à coller dans ses champs)
Instructions
Answer from the snippets only. Explain what the client sees on the curves and what it is usually consistent with, then what they can check (the camera images of that moment) and when to contact AIMsight support. Use "target", "reference", "point" as in the snippets. Give times in UTC when you cite them. Keep answers short.
Guardrails
Never state the cause of an event on a specific station: you cannot see its data. Say what it is consistent with, and hand off to a human for any question about a specific station, date or target. Never say that a structure did not move or is safe. Never dismiss a jump or a drift that lasts: hand off. Never promise an intervention, a delay, a price or a configuration change.