Specifications include, but are not limited to: Resources include: (but not limited to) gates, parking stands, baggage carousels, staff, make-up units, ticket counters, cargo stands, ground service equipment, etc. The ability to acquire data from the Airport Operational Database, automated schedule and data uploads and some manual inputs. The Resource Management System should also provide real-time outputs with the current DFW Airport Operational Database remaining in sync with each other at all times. Optimization gate planning tool providing gate allocation capabilities and scenario analysis on infrastructure, resources, and assignment rules. Ability to run ‘what-if’ future schedule scenarios with forward looking airline schedules to analyze and best optimize resource and infrastructure capacity constraints, including but not limited to gating, hard stand, ticket counters, bussing, etc. Real-time status of gates, parking stands (non-contact gates) ticket counters, baggage carousels, staff, and baggage makeup-up belts using manual input data and data from electronic interfaces (schedule uploads) and Airport Operational Database. The tool shall allow users the ability to create and define resources and allow these resources to be managed. The Contractor shall provide an RMS system that supports other airport resources including: Allocation of Ground Support Equipment/Vehicles, Fuel Trucks, and De-Icing Vehicles. The capability shall be provided to the user to define, create, and configure these and add new resources with no or minimal software support from the Contractor. Electronic feeds of seasonal schedules. The application shall accept individual manual inputs on an as-needed basis. The tool/system should have full integration with the Safegate Docking system, either directly or through the Airport Operational Database. Ability to export aircraft and flight event data to support billing or airline payment audit processes. Ability to use future monthly or seasonal operational planning schedules to create and export flight activity counts and passenger projections for advance billing or projected revenues. Analysis of resources, such as existing gates, ticket counters, staff, and parking spots for reassignment of locations, reassignment of airlines to Airport gates and ticket counters or preferential use gates, addition of new airlines, passenger queuing at counters, and other related planning activities Ability to export a Microsoft Excel spreadsheet workbook file with 24 hours of arrival and departure flight information into a simulation database. Planning future resource utilization based on seasonal schedules and projected resource availability. Ability to save the planning schedule and then retrieve it later for further manipulation. Multiple Reference Types – The RMS shall support multiple reference types. Specifically, it shall be able to add new reference data types without additional code changes to existing application and exclusively through the User Interface. IATA & ICAO Codes – The RMS shall support both IATA and ICAO codes for data such as airlines, airport, cities, and aircraft types. Security Log-in Access Profiles – The RMS will allow for the creation of various levels of system log-in access profiles. Aside from system administrator access profiles, the system will support both user and group profiles. The System Administrator will have the capability to grant system usage and rights capability by user/group type. Aircraft-Based Tracking – The RMS shall be an aircraft-based solution and not flight-based solution. The tool/system shall be rule-based and be capable of resolving conflicts among those resources it has been deployed to manage. The Contractor will define the rules during project execution with the Airport staff to reflect the Gate Manager’s expertise. The system will allow DFW Airport staff to create new rules and edit existing rules without additional code changes or support from the Contractor. The system shall allow for nested rules and the ability to process multiple rules simultaneously to arrive at a decision. Airline updates to the RMS application shall not override terminal manager inputs unless established by specific rules establishing such. Application shall include in the user interface a real-time flight data feed. It shall be visually coded to allow the user to know which data source is being utilized and if no source is currently active. Input gate restrictions/adjacencies/rules via dropdown window by clicking a specific gate. Ability to plan by analogy based on predetermined rules and adjacency restraints. Ability to create new flights within an active day. Alerts to users of status changes and potential and actual conflicts, automated contingency options when conflicts arise
