Enter the lift data and run the assessment. The Live model tab animates the wind and gust against this crane; the Symbols tab defines every variable; the Report tab builds a printable lifting report once submitted.
| 13.5 | Erection / alteration cap — CIG 2507 §5.1.2 |
| 14.1 | No special load case below — EN 13001-2 Table 1 |
| 17 | UK structural wind-off (38 mph) — BS 7121-5 §14.1 |
| 20 | Normal in-service design max — EN 13001-2 Table 1 |
| 28.5 | Process-crane ceiling — ISO 4302 Table 2 |
| 10 min | Return-to-service clear period — BS 7121-5 §14.1.4.2 |
Two regimes matter and must not be confused. Extreme / design winds (SBC 301, from Saudi Aramco SAES A-112) govern out-of-service storm-securing — they are 3-s gusts at 10 m for a structural return period (≈42–53 m/s) and are far above any working limit. Operational winds — the daily forecast and the crane anemometer — govern whether a lift may proceed; the dominant operational hazard is the Shamal and its dust storms.
| City | km/h | m/s | Region |
|---|
Source: SBC 301 Fig 6.4-1, adopted from Saudi Aramco SAES A-112. Use these to check the crane's out-of-service / storm configuration, not daily go/no-go.
From CIG/TCIG 2507 and the project worked examples. Each loads the inputs, runs the assessment and logs it.
Run an assessment on the Assess tab, then submit it. The signed report builds here.
Pulls the current 10-m mean wind, peak gust and direction for the selected city from Open-Meteo (keyless, CC BY 4.0). If the preview sandbox blocks outbound requests, it falls back to manual entry and still works in the deployed/downloaded app. Forecast figures are at 10 m — the engine height-corrects them to a 3-s gust at the crane. Operational go/no-go always uses the crane anemometer as the authority.
| # | Time (UTC) | Ref | Crane | Mode | m | Ap | Cw | V_lim | V_allow | Gust | Decision | State | By | Hash |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| No entries yet. | ||||||||||||||
Each entry binds the previous entry's hash; any later edit, deletion or back-dating breaks the chain and is caught on verification. Integrity flags reject implausible or out-of-bound inputs at the point of entry.