02 - Notes from team meeting 6 Nov 2014

Phone meeting 6 Nov 2014 11am EST

Present:

Bob

Arnaud

Paddy

Bob:

Surprised to hear we are looking out 18 months rather than 9 months.

Arnaud:

Suggests a draft/progress min svc recommendations report this summer.

Bob:

Gary's session summarizing WTIC research. Jim Evans came up with a good idea: come out with "Consumer Reports" of wx technology in the cockpit. Could be done by the FAA or by an independent organization such as AOPA or it could be self-supporting. That may be what sticks in terms of min svc recommendations. I'm not sure how much we have to justify what we come up with, but it will likely have to be a joint effort with the Tech Ctr (or something). 

So I'm not sure there is a whole lot of writing with this. 

Arnaud disagrees.  Sees a lot of paper for this. We've learned a lot of things. In any case, seems this isn't going to happen in the current period of performance.

Arnaud:

Emphasis away from info and capabilities and towards decision support. What should we be preparing for the 19 Nov meeting?

 - Several DS topics that we can present as options:

    o Alerting - by having the system highlight or show when conditions fall below a configured min

    o Trending - show how conds are changing with a single view on the map with thumbs up/down and a click-through to see how things are evolving over time.

    o Crosswinds at airports

    o Build up something akin to FWHT that builds up a path and looks at the grid cells. Bob said we could do it with sfc stations. A thinks it might be easier to do with a grid. 

(some discussion on this last topic - turb alerts project for WTIC, etc)

Documentation/Presentation Development will mostly fall on Paddy for the 19th

What do we want to prepare?

 - Pictures that are easy for people to understand what we are talking about

 - Conceptual and not a mockup

 - Bob would like to see some feedback from the pilots about the UI

 - Go through the ideas and start to flesh them out. How would we implement them with what we have and in the time we have.

How do we aggregate pcs of info and display them? Non-decoded records. Data freshness. Are improving conditions as important as deteriorating conditions?

Are these things worth to research and implement?

Any of the details/questions might be helpful to provoke discussion.

Not sure pilots will give us any answers. Just buy-in. Bob would like to get their other-experts opinion here, but leave Gary with the decision-making.

Bob: Gridded data vs point data. Conceptual? Are you going to an airport or are you flying through the space between the airports.

Rob Aeodgeion -- Boeing optimal path through 3D space to avoid hazards. Bob's 

get me outta here tool. Meaty topic to chew. But one we would like to present as part of our documentation.

Bob: So far we haven't been casting our mind in the day in the life of a pilot. preflight, takeoff inflight landing. We've been talking cruise. Not takeoff and landing. What if we break it up and ask the question "if you were going to design a tool for this phase of flight, what would you do?" ?

Arnaud: A lot of the HEMS users have tool set to animation loop. 2 hrs in the past to now. Gives a qualitative sense of where the clouds are going. Value in having animation mode that's going forward in time, with where thunderstorm is going to move, and where is my location going to be. Move the ownShip location out into the future.

Runway winds

 - map of runways with winds plotted on them --> takes out the number of variables the pilot has to put together in their mind

 - 1-min data showing min, max, direction variability over last hour

 - Could carry this out via a mockup for the eval

 - Even could use a powerpoint rather than displaying it via the mobile tool.

Wallrunning desirement - access to the 1-minute obs. This may be one of the technology gaps we talked about with Gary yesterday.

How to move forward?

 o Let's go ahead with the meeting on the 19th. Action: Bob

 o Propose general notions first.

 o Then present our specific ideas.

 o