First off I would like to thank you all for attending this meeting, I know that everyone is very busy but the CEO has called to our attention that we needed to coordinate and follow up on the development process of Airport CEO. A few weeks ago in a subreddit thread, a future airport CEO asked some questions and shared some ideas on what the “research” feature of Airport CEO could look like. We all agreed that it wouldn’t make any sense for an airport to research technologies, instead it seemed more logical to have some kind of system where the airport (well, the committee) could perform an analysis and “investigate” the potential of acquiring a new system or a new product.

This week we’ve implemented the first version of a procurement system where we’ve focused on the purchase of vehicles. For this reason, a vehicle depot has been implemented, it acts as a garage for the service vehicles you purchase for the airport and when they are not in use, or if they need maintenance, your staff will drive them there (don’t worry, you’ll also be able to place down individual parking spaces). There are a number of things to consider before buying something in Airport CEO, products have an initial price, a maintenance cost and a delivery time. Certain products also have different prerequisites in the shape of requiring the purchase of more basic products within the same category or having to reach certain goals or close certain deals from an operational perspective.

CEOs’ can do a lot by them selves but not everything. For investments of the larger-scale you will have to hire a Procurement Director, responsible for assisting the CEO in the purchase of more advanced products as well as negotiating deals and keeping costs down. The more skilled your Procurement Director is, the better deals you’ll get and the faster they’ll go through. We’ll likely show you a procurement screen next week!

We’re steaming ahead with the development and are moving closer to our goal. While we are working on expanding the content and sewing parts together we are also making some final adjustments to the most basic systems in the game, things that currently don’t work well enough and might disrupt gameplay. One of these systems are navigation nodes for different kinds of traffic, where we plan to rebuild the entire system and make it more reliable. The other aspect is passenger queueing (in lines or, when queueing for gates, totally unstructured), something which is very easy to do in real life but quite difficult to describe from a code perspective. Once we’ve got these parts down and done some final adjustments, we’ll be able to move into the next phase of the game development.

Thanks for your patience and for keeping up with the good work! The Committee is very happy with your contribution, let’s meet here next week for a follow-up meeting on this matter and coordinate the project further. Thank you for now.

‍