Information technology (IT) systems at airports range from those found in any enterprise organization (e.g., email, word processing ) to those found exclusively or predominantly at airports (e.g., FIDS, BHS). Large airports tend to have the resources (money and staff) to manage these systems in-house that smaller airports typically don’t.
In addition, the staff at smaller airports may be unaware of alternative IT delivery systems, as well as lack the in-house expertise to evaluate these options and/or the understanding of far reaching considerations to determine who should be providing oversight, management, and day-to-day operations (i.e., in-house or outsourced) of IT systems.
Little research has been done to assist those smaller airports with understanding the range of IT related options, including delivery methods, and the benefits and risks associated with providing the oversight, management, and day-to-day operations of those systems whether in-house or outsourced.
The objective of this research is to provide guidance for medium, small, and non-hub airports with limited budgets and resources on: (1) evaluating alternative IT delivery methods and types of provider options (in-house vs. outsourced), and (2) associated best practices.
Typical IT systems include:
- Infrastructure (e.g., LAN/WAN/Internet/telephone)
- Passenger processing systems (e.g., FIDS/BIDS/BHS/common use)
- Security systems (e.g., CCTV/access control)
- Office automation systems (e.g., email, word processing/website)
- Enterprise back-office systems (e.g., finance, asset management, SMS)
- Life safety systems (e.g., fire alarm/paging)
Status: This has been published as ACRP Report 128: Alternative IT Delivery Methods and Best Practices for Small Airports.
