Thats what I am looking at.
So far, it is just on the ac app, the components by altitude are now really only used for situational awareness, as it tells you if the headwind, tailwind, or crosswind components by altitude band exceed the ac max. You could just use the worst case, but that is not always the best solution.
You are correct, getting this uploaded to the FMS is quite the endeavor, and thus for now, is only for situational awareness. I am curious on the systems that can upload the data automatically, just how effective that is.
The ac app shows any windshear, and at what altitude, showing the headwind/tailwind change at the specific altitude.. (adding wake turbulence to this mix) Currently, this is only a situational awareness warning for the flightdeck. That being said, there are attempts being made to supply this data to the onboard windshear advance warning system, to augment the algorithms, and help make that system more accurate. As we are all aware, there are many times these systems dictate a GA, when it is not necessary.
ATC will have this capability on their version of the app as well, to see if an individual aircraft needs to use a different runway. The app shows all of the inbound ac, headwind/tailwind, crosswind and windshear are shown by altitudes in 1000 increments from 5000 down to 1000, then 500 feet for the procedure. All inbound ac are calculated by their respective limits, and a warning is shown if any winds exceed ac max.
The windshear level, and perhaps wake turbulence, will also be part of the ATC app, to provide a distinct windshear warning by altitude.
Glad to know that the data is useful to the flightdeck, and is considered decent and accurate! Thanx!