A few thoughts, chaps. .. .(a) any fool can run a computer program with minimal training. .. .(b) any fool with a bit more training can do the AFM analysis graphically. .. .(c) none of it is much use unless the obstacle data is sound .. this is a major problem. For those who would subcontract the work, it might be prudent to invigilate just what the contractor does in this regard ... are you happy with the approach taken ? .. where does the data come from ? ... what is done to check for system errors ? ... can you defend it in court after the accident ? ... does it make sense operationally ?. .. .(d) what are you doing about on-going monitoring of obstacle changes external to the airport operator's reporting ? .. remembering that the takeoff goes out a LONG way .... does your contractor do an acceptable job in this regard ?. .. .(e) does the contractor (or, indeed, the in-house group) either include, or seek guidance from, appropriate pilot people ? .. so that the escape procedures make sense from the viewpoint of pilot workload and sensible cockpit operational management ?. .. .(e) is the turn around adequate for the need ? .. this is ALWAYS a problem, potential or real, with contracted support .. and that applies even with the best intentions and efforts by the contracting organisation.. .. .... but the main concern is ... if it all turns to custard .... who gets the blame ?