1.1
Functional Requirements
Functional requirements describe the software capabilities that must be present for the user to carry
out the services provided by the selected system.
#
F7.1
F7.1.1
Functional Requirements
Response/
Respondent
Resource Management Capabilities
The solution must have the ability to record / manage key asset
information related to gate management. This includes:
 Identify assets associated with gates (boarding bridge,
etc.)
 Flag asset as active or down
Choose an
item.
Record maintenance information associated with the asset
(scheduled maintenance, expected time of out-of-service, etc.)
F7.2
Gate Scheduling Management
F7.2.1
The solution must have the ability to provide a Gate downtime
notification (disabled gate).
Choose an
item.
F7.2.2
The solution must be able to create short-term, long term and
day of operation allocation plans for any number of Gates,
stands and remote parking positions.
Choose an
item.
F7.2.3
The solution must display Gate assignments in a graphical format
that can be expanded to allow the user to see a visual layout of
the flights arriving and departing from the various gates.
Choose an
item.
F7.2.4
The graphical representation for each flight must include
scheduled, actual and estimated arrival and departure times,
flight number, Aircraft Type, Tail Number- if available.
Choose an
item.
F7.2.5
Real-time changes to any flight must be instantly reflected on
the graphical displays.
Choose an
item.
F7.2.6
The solution must show each carrier with a unique user defined
color, the flight number and the flight also spans the time based
on boarding or un-boarding times.
Choose an
item.
F7.2.7
The solution must provide the ability to schedule “What-if”
scenarios and retain them for Future use.
Choose an
item.
F7.2.8
The solution must be able to import the OAG feed for forward
looking Seasonal schedules (generally 6 months out) into the
“What-If” tool for use in building seasonal plans.
Choose an
item.
F7.2.9
The solution must be able to track all aircraft tows including the
scheduling of tows from remote locations.
Choose an
item.
#
Functional Requirements
Response/
Respondent
F7.2.10
The solution must be able to display Flight time data, including
Scheduled, Estimated and Actual. (STA, ETA, ATA, STD, ETD and
ATD)
Choose an
item.
F7.2.11
The solution must be able to lockdown a gate or set of gates for
a user defined period of time and use, without being overwritten
by airline feeds.
Choose an
item.
F7.2.12
The ability to lockdown gates must be an attribute of Sign-on
roles and profiles.
Choose an
item.
F7.2.13
The solution must have a special relation calculation for gate
proximity. To allow mixing of aircraft sizes at side by side gates.
Note: This is a ‘Does it Fit’ tool.
Choose an
item.
The solution must be able to quickly display the aircraft attribute
information associate with each gate or system of gates, such as:
 Types of aircrafts that are allowable at any gate.
 Noise critical aircraft within the Gate Management
System.
Choose an
item.
F7.2.15
The solution must provide the ability to auto-trim gate
assignments.
Choose an
item.
F7.2.16
The solution must have the ability to administer remote
overnight parking assignments/usage.
Choose an
item.
F7.2.14
F7.3
Extreme Event Management (Irregular Operations)
F7.3.1
The solution must provide the ability to View, Update, Schedule
and Modify gate, check-in counters, stands, and remote parking
assignments for extreme events or weather.
Choose an
item.
F7.3.2
Through GMS, the DIA can view use of all gates within the airport
and provide recommended gate changes across any/all
jurisdictions
Choose an
item.
F7.4
Application Logic and Business Rules
F7.4.1
The solution must provide administrative capabilities to define
and modify business rules without a need to modify base code.
Choose an
item.
Choose an
item.
F7.4.2
Rules management (change, remove, add) can be performed by
the DIA, without the need of vendor involvement. As such, the
Rules module shall be equipped with management tools,
including:
 Ability to report on active rules in the system, including
interdependencies between the rules.
 Change management log
#
Functional Requirements

Response/
Respondent
Error checking capabilities
F7.4.3
The solution must have a Field level data attribute
‘normalization’ and ‘validation’. If invalid data is entered the
solution must be able to catch the error before it is written to
the database.
Choose an
item.
F7.4.4
The solution must provide the ability to designate read-only
attributes.
Choose an
item.
F7.4.5
The solution must be able to create and adjust business rules
that govern gates, check-in counters, stands and remote parking
positions.
Choose an
item.
F7.4.6
Rules for “trumping” or prioritization of flight information
coming in from various feeds can be set up for any data field.
This provides the ability to determine the correct process for
updating data fields with the most accurate information.
Choose an
item.
F7.5
Data formatting and Integration
F7.5.1
The solution must be able to handle standard ACI-FMS or AIDX
data schema.
Choose an
item.
F7.5.2
In general, system shall support SOAP, XML, and Web Service
based integration
Choose an
item.
Choose an
item.
F7.5.3
System shall be able to notify external systems when information
is added/updated/deleted. This notification shall be done
through industry standard SOAP 1.1 web service calls.
Notifications shall be customer-configurable (destination endpoints, trigger conditions, data mapping, etc.).
F7.5.4
System shall be able to accept updates from external systems.
These interfaces shall use industry standard SOAP 1.1 web
services.
Choose an
item.
F7.5.5
Web service interfaces (both inbound and outbound) shall
incorporate SSL encryption, WSSE SAML-based authentication and utilize role-based authorization.
Choose an
item.
F7.5.6
The exposed web services shall expose Web Service Discovery
Language (WSDL) files to facilitate building client connections to
them.
Choose an
item.
Choose an
item.
F7.5.7
The solution must have a demonstrated ability for integration
capabilities with a wide range of “industry standard” interfaces,
including:
 FAA NextGen – CDM
o Saab Sensis Aerobahn® - surface management
system.
#
Functional Requirements





Response/
Respondent
o ATC Flight Strips
o Others
IATA Type B (SITA)
CUTE/CUPPS (Control of FIDS, check-in counters, and
gates)
Baggage reconciliation, handling
Billing
Others
Note: The actual integration of the two systems will come in a
future project.
F7.5.8
F7.6
The solution must be able to ingest all data metrics currently
used by Aerobahn, FAA and all airlines.
Choose an
item.
Architectural and Hardware
F7.6.1
The solution must have a method for Load balancing.
Choose an
item.
F7.6.2
The solution must provide the ability to archive data.
Choose an
item.
F7.7
System Security
F7.7.1
Security for the solution must be profile/role based; DIA will not
accept single sign-on.
Choose an
item.
F7.7.2
The solution must be AD/LDAP Compatible.
Choose an
item.
1.2
User Requirements
The user requirements represent what the end-users of the system want the system to accomplish and
how they should be able to interact with the system.
#
User Requirements
Response/
Respondent
U7.2.1
The solution must provide the ability for the user to define the
archive criteria.
Choose an
item.
U7.2.2
The solution must have an admin tool to make business rules
changes at any time.
Choose an
item.
Choose an
item.
U7.2.3
The admin tool must be able to administer –
 Preferred gates from which an airline operates
 Define the hierarchy of data from sources (i.e. FAA,
Aerobahn, Airlines…)
 Types of aircraft per gate
 What Stop bars are available per gate
 Estimated taxi times
 What stand goes with what door
 Define access to FIS (Customs)
 Customized views of the Gant chart screen (an ability to
create a view of user defined gates)
 Ability to customize what data is visible on Gant chart for
each flight.
The solution must have the ability to display all gate areas
graphically through an “airport map view” option. Key features
include:
 Include all DIA controlled areas including gates and
remote parking stands.
Choose an
item.
U7.2.4
Include all non DIA-controlled areas, but distinguished by color
or some other differentiating feature.

U7.2.5
The solution must be able to provide logic that will help
fill in gate assignments based on a user defined flight
schedule.
Choose an
item.
U7.2.6
The solution must have the ability to import existing gate
management data into the new database, through a user
verified means, to ensure the quality of data imported. This
ability includes all flight operational data and Rules.
Choose an
item.
U7.2.7
Integration of existing data into the new process must be
seamless in order to maintain existing gate assignments and
control over daily operations.
Choose an
item.
1.3
Non Functional Requirements
These are requirements that may relate to areas of the system such as Performance, Scalability,
Security, and Persistence.
#
Response/
Respondent
The solution must follow an appropriate Multiple platform
methodology. (i.e. development, test, production)
Choose an
item.
The solution must have an intuitive and user friendly Graphic
User Interface (GUI). Vendor selected will conduct the following:
 Provide evidence of best practices in GUI (ex. User never
navigates more than three layers deep, widget selection,
standard keys, color, error handling, etc.).
 Define GUI standards to apply across all user screens
 Get DIA buy-in on standardization process
 Conduct end-user workshops to define main user screen
types (vendor to include minimum of 10 screen types in
proposal)
 Draft an actual case for each screen and prepare
prototype for DIA review and approval
Choose an
item.
NF7.3.3
The solution must be designed with intent to reduce and where
possible, eliminate users from entering or mistyping information,
including having Calendar date menus for date selection where
applicable.
Choose an
item.
NF7.3.4
Training and materials must be provided to a minimum 1 DIA
SME, including User and Admin guides:
Choose an
item.
NF7.3.1
NF7.3.2
1.4
Non Functional Requirements
Maintenance and Support Requirements
These are requirements that may relate to areas of system maintenance and support requirements.
#
Maintenance and Support Requirements
Response/
Respondent
NF7.4.1
The System must have an effective means for testing version
updates and patches prior to go-live installation. Fall-back
methods must be in place to allow system to resume previous
version operations if a problem is encountered.
Choose an
item.
NF7.4.2
Maintenance outages must be limited to overnight hours (01000400).
Choose an
item.
#
Maintenance and Support Requirements
Response/
Respondent
NF7.4.3
The solution can have no more than 2 hours of downtime due to
failure in 90 continuous days.
Choose an
item.
NF7.4.4
Response time to problem calls…
Choose an
item.
NF7.4.5
Customer Service is of prime importance. Vendor should have
the following:
 Product User Group
 Proven history of successful customer service
 Well defined customer service plan, including escalation
issues
Choose an
item.
2 Reporting Requirements
This section will include details about functional reporting requirements previously documented,
including the lay-out and print-out of the report’s header and footer sections
#
R8.1
Reporting Requirements
Response/
Respondent
Gate Management Reporting and Logs
Canned Reports – System shall be delivered with at least 10 DIAdefined canned reports. Examples includes the following:
 Report for Finance group to audit accurate airline billing
for gate, stand and remote parking.
 Gate Availability Report for Properties use
 First / Last / Peak arrivals report for Commercial Group
use
Choose an
item.
R8.1.2
Easy to Use Reporting Tool – System comes equipped with easyto-use reporting tool, such as Crystal Reports, for use by DIA
personnel.
Choose an
item.
R8.1.3
Input into BAM – System can supply predefined data to be fed
into DIA BAM.
Choose an
item.
R8.1.4
The solution must include a Record change log when the
schedule has been modified (by who and when).
Choose an
item.
R8.1.5
Airline Stand Summary - Numerical count of stand usage for
arrival/departure by airline and type aircraft.
Choose an
item.
R8.1.6
Airline Summary - Numerical count of arrival/departures by
airline.
Choose an
item.
R8.1.1
#
Reporting Requirements
Response/
Respondent
Choose an
item.
R8.1.7
Flight activity - Detailed list of each flight operation.
R8.1.8
INOP - Detailed list of each stand that was inoperative including
length of time the asset was down or is forecasted to be down
(based on PM cycles).
Choose an
item.
R8.1.9
Tow Tracking - Detailed list of each flight that was towed
to/from a remote parking location.
Choose an
item.
R8.1.10
Remote Parking Log - Detailed list of all aircraft parked on a
remote pad or gate belonging to another airline. Must include
Time in, Time out, from gate, airline, tail number, Date out, To
Location, and user added Comments.
Choose an
item.