Addendum No. 4

MARYLAND AVIATION ADMINISTRATION

OFFICE OF PROCUREMENT AND MATERIALS MANAGEMENT

ADDENDUM No. 4 to

DRAWINGS

for

CONTRACT NO.: MAA-CO-26-001/ MAAMC-26-014

Design, Installation and Support of Airport Data, Information Display and Management Systems at

BALTIMORE/WASHINGTON INTERNATIONAL THURGOOD MARSHALL AIRPORT

(dated) October 16, 2025

IMPORTANT: Bidders must acknowledge receipt of this Addendum. Please sign and date the attached

“Acknowledgement of Receipt”. All documents must be fully executed at the time the Bid is submitted.

All information contained herein shall form a part of this Addendum.

The MDOT MAA encourages Contractors to return the Addendum Acknowledgement attached to this

Addendum No. 4.

This Addendum forms a part of the Contract Documents and modifies the original Proposal Documents dated October 16, 2025.

This Addendum No. 4 consists of 1 page and the following attachments:

1. Attachment No. 1 - Pre-Proposal Meeting Minutes

2. Attachment No. 2 – Pre-Proposal PowerPoints

3. Attachment No. 3 – Pre-Proposal Attendee List

4. Attachment No. 4 – Site Inspection Attendee List

5. Attachment No. 5 – Questions & Answers

6. Attachment No. 6 – Plan Holders List

7. Attachment No. 6 - Addendum No. 4 Acknowledgement Form

Addendum Date: December 10, 2025

Proposal Due Date: January 13, 2026; 1:00:00 p.m. local time

Proposal Due Location: Bids must be submitted via eMMA:

https://emma.maryland.gov

END OF ADDENDUM No. 4 https://emma.maryland.gov/

PRE-BID SCRIPT

Good morning. I am Monica Queen with the Maryland Aviation Administration (MAA)

Office of Procurement and Materials Management. I would like to welcome you to today’s pre-proposal web conference meeting for Contract MAA-CO-26-001/ MAA-MC-26-014

Design, Installation and Support of Airport Data, Information Display and Management

Systems at Baltimore/Washington International Thurgood Marshall State Airport. I am the

Procurement Officer for the project and your sole point of contact. Please mute your mic until you need to speak.

AGENDA – SEE SLIDE NUMBER 3

Today we will discuss the procurement process, followed by the project scope of work, Minority Business Enterprises subcontracting requirements and general and operations security requirements. Should you have questions during this Pre-Proposal Meeting, please announce your name and company before asking your question. We ask that you follow up with all questions in writing after this Pre-Proposal Meeting.

With me today are members from MAA Consultant Team, Office of Civil Rights and Office of

Airport Security.

I will allow each presenter to introduce themselves:

Thank you.

We encourage networking during these meetings; therefore, I will introduce each company that submitted an RSVP to this Pre-Proposal Conference. When you hear your company’s name, please introduce yourself, briefly advise if you plan to bid as a prime or sub, your capabilities and if your company is a certified MBE/DBE.

If I did not introduce your company, please introduce yourself at this time.

(Introductions)

Anyone else? Thank you all!

I will briefly explain the procurement process for this project.

This Procurement is being conducted in accordance with COMAR 21.05.03 Procurement by Competitive Sealed Proposals, known as the Request for Proposals (RFP) Process.

The RFP consists of two Volumes. Both volumes may be downloaded via eMaryland

Marketplace Advantage (eMMA). The Bid Number on emma is BPM053667. The website for eMMA is https://emma.maryland.gov

Contract drawings are available by request electronically, please contact Monica Queen at 410-

859-7004 or email mqueen6@bwiairport.com.

All proposals must be submitted on the price proposal forms provided in Volume II of the proposal documents.

RFP Process.

1. Submittal. An Offeror should submit a separately sealed package as stated in GI-1.02 for each requested proposal. Each envelope should be labeled as Technical Proposal or Price

Proposal, as applicable, and include the RFP title and number, name and address of the

Offeror, and the closing date and time for receipt of the proposals on the outside of the package.

PROPOSAL FORMAT

a. Title Page

b. Table of Contents

c. Evaluation Criteria

i. Overall Technical Solutions

ii. Offeror/Contract Team

iii. Key Staff

iv. System Features and Functionalities

v. Responses of Owner Questionnaire

vi. In-Person Interview/Live Demonstration

vii. Project Goals & Management Approach

viii. Maintenance Plan

ix. Supplemental Information

x. Confidentiality of Proposal (if Applicable)

xi. Disclosure of Interest

xii. Conflict of Interest Affidavit

xiii. Bid/Proposal Affidavit

xiv. MBE Form A

xv. MBE Form B

xvi. Living Wage Affidavit

xvii. Financial Responsibility

Technical and Price Proposals are due December 3, 2025, no later than 1:00:00

Positively no Proposals will be accepted after 1:00:00 pm on December 3, 2025.

To submit a proposal all offerors must first register on eMaryland Marketplace Advantage

(eMMA). Registration is FREE!

Technical Proposals will be opened in eMMA on December 3, 2025.

Price proposals will not be opened until after the evaluation of the technical proposals is complete.

mailto:mqueen6@bwiairport.com

To receive a contract award, a vendor must be registered on eMMA.

Any questions posed and responded to at this meeting will be included in the minutes of this meeting.

Any questions posed from Offeror’s after this meeting shall be submitted in writing, preferably by email, to my attention at mqueen6@bwiairport.com

The cut-off for receipt of all Offerors questions is November 3, 2025 – 1:00:00 pm.

The minutes of this meeting and all responses to questions will become a part of an Addendum for this procurement.

Moving forward, members of our Consultant Project Manager team are here to provide an overview of the project scope. Please introduce yourself as you present.

PROJECT OVERVIEW – Jim Davis

Monica requests that all questions be electronically submitted to MAA for distribution.

Any Questions?

As a reminder, following this meeting please submit your questions in writing to mqueen6@bwiairport.com to receive the official response which will be included in the upcoming addendum.

Moving forward, there is an 7% MBE Subcontractor Participation Goal for MAA-CO-26-001

AND 0% MBE PARTICIPATION FOR MAA-MC-26-014. The MAA encourages all bidders to seek opportunities for participation by minority businesses.

Mr. Brett Harrell from the Office of Civil Rights will address the

MBE participation goal in more detail.

Security Requirements – Jeffrey Miller Airport Security

If you’re going to work in the Secured Identification Display Area (SIDA), Secured

Area, or Sterile Area, you’re going to need a BWI Thurgood Marshall identification badge. This is a TSA requirement. It usually takes about two weeks to complete the badge process. We do a fingerprint-based FBI Criminal History Records Check

(CHRC) and a Security Threat Assessment (STA). For the STA the applicants name is run through a number of different databases to see if your name is on any lists. When

CHRC and STA are approved, your Authorized Signer will receive an email informing them to send you to the Badge Office for a badge.

If you are going to be working in the Federal Inspection Service building, you will need to apply to Customs Border Patrol (CBP) for a Customs Seal. CBP performs its own background check, and the Authorized Signer receives an email when it is approved.

You are advised to badge as many people on your team as you can. Someone without a badge may be escorted by someone who has Escort Authority, but the person performing the escort cannot work. Their only job is to watch the employees being escorted. One person with Escort Authority may escort up to five (5) unbadged employees.

If you need to operate a vehicle on the airfield, you must take the test to get an Airfield

Operator’s Permit. You must pass this test with a score of 80 or better. You may repeat this test three times. If you don’t pass it, you will not be driving at BWI Thurgood

Marshall. Additionally, your vehicle will need a decal, which requires an inspection of the vehicle. The decals are issued by the Office of Airport Operations.

Any Questions?

If you joined late or did not have an opportunity to introduce your company, please do so now.

Thank you for your interest and good luck with your proposal.

Pre-Bid Meeting 10/23/2025

MAA-CO-26-001 & MAA-MC-26-014

Design, Installation and Support of Airport Data, Information Display and Management Systems at

BWI Thurgood Marshall Airport

Housekeeping Items

• Remain on Mute to minimize background noise

• Click the Raise Hand button to ask question or comment

• When speaking, please identify yourself and your company

• This meeting is being recorded

Mute Button Raise Hand

Agenda

➢ Introductions: Monica Queen

➢ Technical Proposals Due Date: December 3, 2025– 1:00:00 pm

➢ Price Proposals Due Date: December 3, 2025- 1:00:00 pm

➢ Questions Due: November 3, 2025 – 1:00:00 pm mqueen6@bwiairport.com

➢ Anticipated Addendum : Week of November 10, 2025

➢ Project Description: Jim Davis

➢ MBE Goal: Pamela Turner

➢ Security Requirements Jeffrey Miller

➢ Open Floor for Questions mailto:ldangerfield@bwiairport.com

RFP PROCESS

This Procurement is being conducted in accordance with COMAR

21.05.03 Procurement by Competitive Sealed Proposals, known as the (RFP) Process.

The RFP consists of two Volumes. Both volumes may be downloaded via eMaryland Marketplace Advantage (eMMA). The Bid Number on emma is BPM053667. The website for eMMA is https://emma.maryland.gov

Contract drawings are available by request electronically, please contact Monica Queen at 410-859-7004 or email mqueen6@bwiairport.com

All proposals must be submitted on the price proposal forms provided in Volume II of the proposal documents.

RFP PROCESS

Responses to the RFP. Found in GI-1.07

1. Submittal. An Offeror should submit a separately sealed package as stated in GI-1.02 for each requested proposal. Each envelope should be labeled as Technical Proposal or

Price Proposal, as applicable, and include the RFP title and number, name and address of the Offeror, and the closing date and time for receipt of the proposals on the outside of the package.

2. Proposals shall only be accepted via the State’s internet-based electronic procurement system eMMA.

PROPOSAL FORMAT

a. Title Page

b. Table of Contents

c. Evaluation Criteria

i. Overall Technical Solutions

ii. Offeror/Contract Team

iii. Key Staff

iv. System Features and Functionalities

v. Responses of Owner Questionnaire

vi. In-Person Interview/Live Demonstration

vii. Project Goals & Management Approach

viii. Maintenance Plan

ix. Supplemental Information

d. Confidentiality of Proposal (if Applicable)

e. Disclosure of Interest

f. Conflict of Interest Affidavit

g. Bid/Proposal Affidavit

h. MBE Form A

i. MBE Form B

j. Living Wage Affidavit

k. Financial Responsibility

Technical Proposals are due December 3, 2025, no later than 1:00:00

Positively no Proposals will be accepted after 1:00:00 pm on December 3, 2025.

To submit a proposal all offerors must first register on eMaryland

Marketplace Advantage (eMMA). Registration is FREE!

Technical Proposals will be opened in eMMA on December 3, 2025.

Price proposals will not be opened until after the evaluation of the technical proposals is complete.

In order to receive a contract award, the offeror must be registered on emma.

Questions

Any questions posed and responded to at this meeting will be included in the minutes of this meeting.

Any questions posed from Offerors after this meeting shall be submitted in writing, preferably by email, to my attention at mqueen6@bwiairport.com

The cut-off for receipt of all Bidder questions is November 3, 2025– 1:00:00 pm

The minutes of this meeting and all responses to questions will become a part of an Addendum for this procurement.

TECHANICAL OVERVIEW

JIM DAVIS

MBE Goal

• Speaker: Pamela Turner, Compliance Officer

• Office of Civil Rights and Compliance

MAA-CO-26-001

MBE Goal: 7% VSBE Goal: 0%

MAA-MC-26-014

MBE GOAL: 0%

By submitting a response to this solicitation, the offeror agrees that this percentage of the total dollar amount of the contract will be performed by a verified minority business enterprise (MBE).

SECURITY REQUIREMENTS

• JEFFREY MILLER, AIRPORT SECURITY

PROGRAM MANAGER

QUESTIONS

Please announce your name and your firm before asking your question.

MAA-CO-26-001 & MAA-MC-26-014

Design, Installation and Support of Airport Data, Information Display and Management Systems

Technical Overview

OCTOBER 23, 2025

Scope Overview

• Two Contractual Elements

– MAA-CO-26-001 consists of the design and installation of the Airport Data, Information Display and Management Systems (DIDS)

– MAA-MC-26-014 consists of a 5-year full-service maintenance agreement

• Design and Installation Contract

– Includes preparation of full design documents

– Includes installation, programming, testing, commissioning of the EVIDS, AODB, and RMS

• Design and Installation Contract – Three Primary Components:

– Electronic Video Information Display Systems

(EVIDS)

– Airport Operational Database (AODB)

– Airport Resource Management System (RMS)

EVIDS Scope

Public-Facing Video Displays

• Flight/Gate/Baggage Information Displays (MUFIDS)

• Advertising, Wayfinding

• Displays Behind Ticket Counters

Non-Public Video Displays

• Back Office Display System (BODS) – MAA offices and administrative spaces (add alternate)

• MAA Administrative Conference Room Videoconferencing / Audiovisual Systems (add alternate)

Content Management System (CMS)

• Central repository for all video content

• Mechanism for various MAA stakeholders to review and approve content

• Must integrate with AODB to obtain and display required real-time data (flight information, weather, emergency messages, etc.)

*Please review the RFP document for a complete description of the EVIDS scope *

Hardware and Infrastructure Key Items

• Upgrading some existing 42” flat panel monitors to 55”

• Upgrading some flat panel display banks to large-format direct-view LEDs

• Existing stainless steel mounting structures will require custom modifications in many locations to accommodate new displays

• Existing network cabling infrastructure is insufficient to serve new system – new CAT6A cabling from nearby communications rooms to displays is required

• Some electrical circuiting may be required depending on change in electrical load

• These items must be captured in the design documentation to be prepared by the selected proposer

*Please review the RFP document for a complete description of the EVIDS scope *

Display and Equipment Locations Include:

• BWI airport terminal

• Martin State Airport

• 991 Corporate Blvd MAA Offices

• Field Shop

• Auto Shop

• MAC Building

• Kaufmann Building (1500 Amtrak Way) Rental Car Facility

• MARC/Amtrak Station

*Please review the RFP document for a complete list of locations*

System Transition and Hand-Off

• Phasing plan must be submitted detailing transition from existing EVIDS to selected proposer’s system

• Coordination with incumbent vendor required

• Successful bidder responsible for minimizing disruption to customer service and airport operations

*Please review the RFP document for a complete list of transition requirements*

AODB Scope

• Clearinghouse for airport and airline schedules, plans, operations, human resources and physical assets

• Incorporates an enterprise service bus (ESB) or similar function

• Requires extensive integration with numerous MAA, airline, tenant and external systems and data sources

• Specific integration with EVIDS to provide flight, gate, baggage and other information for display on EVIDS screens, etc.

• Specific integration with RMS to incorporate gate/ticket counter assignments etc.

• Proposers must fully describe the system architecture in the proposal and clearly identify whether it is cloud-based, on-premises, or a hybrid solution

*Please review the RFP document for a complete description of AODB scope*

AODB Scope

• Required AODB system integrations include, but are not limited to:

– Airline web feeds / data feeds (multiple airlines)

– Amtrak service feed

– PASSUR

– OAG Flightview

– Civix ABRM

– AtlasIED Paging/Public Address system

– Collins Common Use System

– Skyfii/Crowdvision checkpoint wait time system

– MAA, BWI and other relevant websites

– Capability to integrate with future gate information system, resource management system, and billing/revenue system (ABRM)

– Other systems as specified in the RFP document

*Please review the RFP document for a complete description of AODB system integrations*

RMS Scope (Add Alternate #4)

• System shall manage MAA-controlled resources including:

– Ticket counters

– Gates

– Baggage makeup conveyors

– Baggage breakdown carousels

– Remote parking stands

• The selected proposer will be responsible for all interface design / interface control documentation

*Please review the RFP document for a complete description of RMS system requirements*

Maintenance Contract

• 5-Year full-service maintenance agreement

• Includes provisions for additional system upgrades/expansions and routine repairs

• Includes two, two-year renewal options

• Includes a service level agreement (SLA) for maintenance and repair / technical support services

*Please review the RFP document for a complete description the Maintenance Contract*

Technical Evaluation Criteria

• Offeror/Contract Team

• Key Staff

• Overall Technical Solution

• System Features and Functionality

• Responses to Owner Questionnaire

• In-Person Interview/Live Demonstration

• Project Goals & Management Approach

• Maintenance Plan

• Supplemental Information

• Economic Benefits to the State

*Please review the RFP document for a complete description AODB system integrations*

Technical Evaluation Criteria

Highlights

• The MAA is looking for innovative solutions that will provide best-in-class features, functionality and aesthetics and support the evolving needs of a major Cat X airport

• The proposed system/platform’s response to connectivity loss and unavailability of external data sources, cybersecurity posture, and upgrade roadmap are important factors

• Energy-efficient display solutions will receive additional consideration (see RFP Appendix B)

• The AODB will serve to enable the MAA’s technology growth and advancement for years and even decades to come

• The RMS will allow MAA to optimize allocation of common-use resources

*Please review the RFP document for a complete description of technical evaluation criteria *

1. Summary Meeting title Pre-Proposal Meeting MAA-CO-26-001/MAA-MC-26-014 Attended participants 63 Start time 10/23/25, 9:50:54 AM End time 10/23/25, 11:14:04 AM Meeting duration 1h 23m 10s Average attendance time 55m 18s

2. Participants Name First Join Last Leave In-Meeting DurationEmail Role Monica Queen 10/23/25, 9:50:56 AM 10/23/25, 11:02:23 AM 1h 11m 26s MQueen6@bwiairport.com Organizer Gerald Libercci 10/23/25, 9:51:00 AM 10/23/25, 11:01:55 AM 1h 5m 51s g.libercci@HatzelandBuehler.com Presenter Sheldon Reynolds 10/23/25, 9:51:08 AM 10/23/25, 10:57:15 AM 1h 6m 7s SReynolds@bwiairport.com Presenter Jim Davis 10/23/25, 9:51:13 AM 10/23/25, 11:02:00 AM 1h 10m 47s JDavis@burns-group.com Presenter Pamela Turner 10/23/25, 9:51:15 AM 10/23/25, 11:07:45 AM 1h 16m 29s PTurner2@bwiairport.com Presenter Gina King 10/23/25, 9:51:28 AM 10/23/25, 11:01:58 AM 1h 10m 29s GKing4@bwiairport.com Presenter Carolina Seldes 10/23/25, 9:52:51 AM 10/23/25, 11:02:16 AM 1h 9m 24s carolina.seldes@itnovaconsulting.com Presenter Margaret Owo 10/23/25, 9:54:05 AM 10/23/25, 10:57:51 AM 1h 3m 45s MOwo@bwiairport.com Presenter Rosemary Phillips 10/23/25, 9:54:29 AM 10/23/25, 11:02:08 AM 1h 7m 38s RPhillips5@bwiairport.com Presenter Steve Moody 10/23/25, 9:55:02 AM 10/23/25, 11:02:00 AM 1h 6m 58s smoody@infax.com Presenter Emma Harding 10/23/25, 9:55:51 AM 10/23/25, 11:02:18 AM 1h 6m 26s Emma.Harding@sita.aero Presenter Tony Chapman 10/23/25, 9:56:42 AM 10/23/25, 9:56:44 AM 1s tony.chapman@a-ice.aero Presenter Tony Chapman 10/23/25, 9:56:47 AM 10/23/25, 11:02:01 AM 1h 5m 14s Presenter Luke Harris - Glenelg Construction (Unverified) 10/23/25, 9:57:14 AM 10/23/25, 11:01:49 AM 1h 4m 35s Presenter Taylor Studds 10/23/25, 9:57:20 AM 10/23/25, 11:02:01 AM 1h 4m 40s taylor.studds@datalytixglobal.com Presenter David Elfers (Unverified) 10/23/25, 9:57:52 AM 10/23/25, 11:02:11 AM 1h 4m 18s Presenter Heidi Harvey 10/23/25, 9:58:12 AM 10/23/25, 11:02:04 AM 1h 3m 52s Heidi.Harvey@Bluum.com Presenter Stacey Jr Armstead 10/23/25, 9:58:15 AM 10/23/25, 10:47:41 AM 49m 25s SArmstead@bwiairport.com Presenter Jeffrey Miller 10/23/25, 9:58:51 AM 10/23/25, 11:02:07 AM 1h 2m 13s jmiller2@bwiairport.com Presenter Jonathan Tabak 10/23/25, 9:59:16 AM 10/23/25, 11:01:38 AM 1h 2m 22s tabak@copopt.com Presenter Brandy Bailey 10/23/25, 9:59:17 AM 10/23/25, 11:02:05 AM 1h 2m 48s brandy.b@synectmedia.com Presenter Meghan Jones 10/23/25, 9:59:30 AM 10/23/25, 11:02:06 AM 1h 2m 36s mjones@ArtofContext.onmicrosoft.com Presenter Greg Senkiw 10/23/25, 9:59:38 AM 10/23/25, 11:01:57 AM 1h 2m 19s Presenter Colleen Hamilton 10/23/25, 9:59:42 AM 10/23/25, 11:02:08 AM 1h 2m 26s chamilton@ArtofContext.onmicrosoft.com Presenter Priscilla Jebanesan 10/23/25, 9:59:44 AM 10/23/25, 10:59:02 AM 59m 17s Pjebanesan@bwiairport.com Presenter Shad 10/23/25, 9:59:50 AM 10/23/25, 11:02:08 AM 1h 2m 17s shad@goapron.com Presenter Dillon Keppel 10/23/25, 9:59:56 AM 10/23/25, 11:02:11 AM 1h 2m 15s dillon@goapron.com Presenter Jeffrey Kautz 10/23/25, 10:00:01 AM 10/23/25, 11:02:05 AM 1h 2m 4s Jeffrey.Kautz@sita.aero Presenter Louis Bullock - SQN Systems (Unverified) 10/23/25, 10:00:09 AM 10/23/25, 11:01:59 AM 1h 1m 50s Presenter Alex Rincon 10/23/25, 10:00:16 AM 10/23/25, 11:02:08 AM 1h 1m 52s Alex.rincon@itnovaconsulting.com Presenter Chad Leqve 10/23/25, 10:00:19 AM 10/23/25, 11:02:02 AM 1h 1m 42s leqve@copopt.com Presenter John Starczewski 10/23/25, 10:00:21 AM 10/23/25, 11:02:10 AM 1h 1m 49s john.starczewski@scala.com Presenter Mark Mayfield (Unverified) 10/23/25, 10:00:24 AM 10/23/25, 11:02:04 AM 1h 1m 40s Presenter Marco Labricciosa 10/23/25, 10:00:31 AM 10/23/25, 10:16:41 AM 16m 9s marco.labricciosa@a-ice.aero Presenter Celso Rodriguez 10/23/25, 10:00:38 AM 10/23/25, 11:02:03 AM 1h 1m 24s celso.rodriguez@radianttech.net Presenter Bryson Threatt (Unverified) 10/23/25, 10:00:38 AM 10/23/25, 10:12:30 AM 11m 51s Presenter Benjamin Danklefsen 10/23/25, 10:00:39 AM 10/23/25, 11:02:08 AM 1h 1m 28s benjamin.danklefsen@adbsafegate.com Presenter Grant Decker (Unverified) 10/23/25, 10:00:45 AM 10/23/25, 11:01:33 AM 1h 48s Presenter read.ai meeting notes (Unverified) 10/23/25, 10:00:46 AM 10/23/25, 11:06:09 AM 1h 5m 22s Presenter Joe Scott 10/23/25, 10:00:52 AM 10/23/25, 11:02:04 AM 1h 1m 11s joe.scott@poppulo.com Presenter Anna Shultz 10/23/25, 10:00:59 AM 10/23/25, 11:02:04 AM 1h 1m 4s acassella@minengineering.com Presenter Gavin Evetts 10/23/25, 10:01:03 AM 10/23/25, 11:02:02 AM 1h 59s gavin.evetts@adbsafegate.com Presenter Matthew (Unverified) 10/23/25, 10:01:18 AM 10/23/25, 11:01:59 AM 1h 41s Presenter Claudio Ferrari 10/23/25, 10:01:24 AM 10/23/25, 11:02:13 AM 1h 48s claudio.ferrari@a-ice.aero Presenter Tim Laughlin 10/23/25, 10:01:54 AM 10/23/25, 11:02:08 AM 1h 13s tlaughlin@ArtofContext.onmicrosoft.com Presenter Denise Hughes 10/23/25, 10:02:06 AM 10/23/25, 11:02:02 AM 59m 55s Denise.Hughes@sita.aero Presenter Jignesh Patel 10/23/25, 10:02:32 AM 10/23/25, 10:30:55 AM 28m 22s JPatel@nitisys.com Presenter Joseph Hiett 10/23/25, 10:02:35 AM 10/23/25, 11:02:07 AM 59m 32s Joseph.Hiett@sita.aero Presenter Jamie Powell (Unverified) 10/23/25, 10:02:35 AM 10/23/25, 11:02:00 AM 59m 24s Presenter Joe Reese 10/23/25, 10:03:05 AM 10/23/25, 10:56:52 AM 53m 46s JReese2@bwiairport.com Presenter Gina Marie Paquette 10/23/25, 10:03:35 AM 10/23/25, 11:02:04 AM 58m 29s GinaMarie.P@synectmedia.com Presenter Matteo Ulissi 10/23/25, 10:03:39 AM 10/23/25, 11:02:10 AM 58m 30s matteo.ulissi@a-ice.aero Presenter Jeff Phebus 10/23/25, 10:05:09 AM 10/23/25, 10:22:52 AM 17m 43s j.phebus@HatzelandBuehler.com Presenter Niharika Kalla 10/23/25, 10:05:21 AM 10/23/25, 10:16:49 AM 11m 27s Niharika.k@uvsit.net Presenter Rodrigo V. (IDS) (Unverified) 10/23/25, 10:06:10 AM 10/23/25, 11:02:05 AM 55m 55s Presenter Tuan Vu (Unverified) 10/23/25, 10:06:24 AM 10/23/25, 10:06:44 AM 19s Presenter Sarah Dunn 10/23/25, 10:06:29 AM 10/23/25, 11:14:04 AM 1h 7m 35s sarah.dunn@scala.com Presenter R & D Conference Room (Unverified) 10/23/25, 10:06:36 AM 10/23/25, 11:02:29 AM 55m 52s Presenter Bryson Threatt 10/23/25, 10:09:16 AM 10/23/25, 11:02:09 AM 50m 41s bryson@goapron.com Presenter LAY, MEREDITH 10/23/25, 10:10:14 AM 10/23/25, 11:01:00 AM 50m 46s ml7791@att.com Presenter Monica Mukheja 10/23/25, 10:13:08 AM 10/23/25, 11:02:01 AM 48m 52s monica.mukheja@ampcus.com Presenter Edmund Chandlee (Unverified) 10/23/25, 10:20:51 AM 10/23/25, 11:02:04 AM 41m 12s Presenter Vishal Patel 10/23/25, 10:21:12 AM 10/23/25, 10:27:40 AM 6m 27s VPatel@nitisys.com Presenter

MAA-CO-26-001 Vendor Questions and Responses

Vendor Question Response

1. Is the display volume for the project - do we know how many displays will need to be managed for the entire scope of the project and locations specified in your presentation?

A display schedule is provided on sheet S001 in the supplemental drawings. An inventory of existing displays will be posted to eMMA with this addendum.

2. Are all the MBE form numbers, processes etc that were mentioned in the call documented in the RFP?

All MBE forms and processes (Forms A–D, VSBE

Addendum, Corporate Diversity Addendum) are included in Volume II, Part IV – Proposal Bond, Mandatory Affidavits, MBE Forms, and Pricing

Documents.

3. Is the RMS mandatory, if its optional is there an existing RMS that we have to interface to

The RMS is not stipulated as optional in the RFP.

Vendors shall provide an RMS as part of their proposal per RFP section GI-1.03 Description of Project. There is no existing RMS at BWI.

4. What is the process for requesting airside access

Additional airside visits will not be provided prior to submission of bids as stipulated in Addendum 1 and as communicated during the pre-proposal conference on

10/23/2025.

5. Is the AODB and RMS required to handle all the flights operating at the airport, or only those using the common use displays with the arrival/departure information for those other flights (southwest, United etc) coming from other sources ?

The AODB and RMS shall manage flight information for all flights operating at the airport, with integration to sources such as OAG/FlightView and individual airline systems.

6. As the RMS is optional is there an existing

RMS that we have to interface to, should the replacement not be contracted. What is the process for requesting airside access

See response to questions 3 and 4.

7. What is the process for requesting airside access

See reponse to question 4.

8. As a first-time bid for BWI I am requesting a

2-week extension for deadlines for questions and some preliminary dates. Additionally, if the BWI team is open to offering an additional walkthrough we would be extremely grateful for the opportunity.

MAA may add an addiitonal site visit.

9. Questions are due to the procurement office by November 3, when will BWI provide the addendum with answers to the questions?

Please refer to this addendum.

10. Would BWI consider a 3 week extension to the due date of December 3?

Please refer to this addendum.

11. Can BWI confirm that this is an electronic submittal? Section GI 1.07 references seperately sealed envelopes.

Proposals are submitted electronically via eMaryland

Marketplace at Advantage (eMMA). If you require help please contact the eMMA helpdesk.

12. Will there be a third party development source to take the provided Flight

Information and display it on the Public

MAA website?

The selected proposer will be responsible for coordinating with MDOT MAAs webmaster responsible for maintenance of the public MAA website to determine the format and method of interface.

13. Will the vendor be looking for messages sent to a queue, a flatfile of data, or can they extract data from the AODB API?

The RFP allows integration via API or feed as part of the AODB interface; the specific transfer method is not mandated.

14. Is OAG FlightView used as the primary source of all flight information at the airport?

Yes. OAG/FlightView Subscription Services are listed as a required data integration source.

15. Is the OAG FlightView feed directly connected to any integrations that are currently being used at the airport? If yes, which ones?

The selected proposer will be required to integrate their system with OAG/FlightView in order to obtain flight data for ingestion by the AODB. Other integrations will be coordiated with the selected proposer.

16. Would you consider using FlightAware for flight data instead of OAG?

No. OAG FlightView is an existing subscription held by MAA that will be maintained.

17. Does ESRI Indoor Mapping Wayfinding support AIDX integrations if not what is the preferred protocol?

The requirement for direct integration with ESRI Indoor

Mapping is being removed from the RFP via addendum.

18. Will there be a third party development source to take the provided Flight

Information and send it to a database or display it on the Information Display System for Crowdview?

The proposer is responsible to develop the required interface between the Crowdvision/Skyfii system and information display system and determine the appropriate data format / protocol.

19. Will the vendor be looking for messages sent to a queue, a flatfile of data, or can they extract data from the AODB API?

Refer to response on question 13.

20. Is this referring to host connectivity? This question requires context in order to respond.

Specify RFP section/paragraph being referred to.

21. Is all flight data coming from a single source of truth such as an OAG or Flightaware feed and not directly from each airline?

Correct; the system shall integrate with

OAG/FlightView as the primary source while allowing other feeds (e.g., airlines, PASSUR).

22. What is the make and model of thed Tugman units being used at the ariport for first bag/last bag?

This information will be provided in a forthcoming addendum.

23. Does AtlasIED Paging support AIDX integrations if not what is the preferred protocol??

AtlasIED Paging does not directly support AIDX;

Interface documentation is available from ATLASIED and integration is the responsibility of the Vendor.

24. Who are the curreent BHS vendor(s) and do they supoport AIDX Integrations?

The current BHS vendor at BWI is Daifuku:

https://www.daifuku.com/us/solution/list/baggagehandli ng/

25. Is there an external system that requires integration to get the train information to display at the airport or is this simply flight information out to the trainstation??

Vendor is responsible to obtain train schedule information from publicly available sources for integration with / display by the vendor's system.

26. The title assumes that only a feed is necessary, how will the third party vendor want to receive the data? 1) Message sent to a queue for consumption, 2) A flat file sent to a file drop location, Can the third-party vendor pull the data from an AODB provided API?

This question requires context in order to fully respond.

Specify RFP section/paragraph being referred to. Refer to response on question 13 for general feedback.

27. Will Flight Information be the only data that is necessary to be provided in this feed?

This question requires context in order to fully respond.

Specify RFP section/paragraph being referred to.

28. Are the displays in the consolidated rental car facility for flight data?

Refer to sheets CRCF and S001 in the supplemental drawings.

29. Confirm VOIP is not in scope for Airport

Data and Information Display Systems

Confirmed, VoIP is not in scope for this RFP.

30. Are these specific configurations part of the post award?

Yes.

31. Who is responsible for providing the network switches MDOT MAA or the contractor?

MDOT/MAA will provide the network switches required for this system. The proposer shall be responsible to coordinate with MDOT IT.

32. To ensure complete understanding of all RFP requirements, can the 3-page limit for

Appendix A be increased?

Appendix A itself shall be completed as provided without modification, and is not included in the page limit. The explanation for deviation from the RFP requirements / technical specifications may be increased to 5 pages. Note, you may reference other portions of your response from within this section if further elaboration is required.

33. Please clarify whether to use FINANCIAL

PROPOSAL or PRICE PROPOSAL

The RFP uses Price Proposal terminology (Volume II, Part IV, Section 7: Price Proposal. Price Proposal is the correct language.

34. Please clarify the due dates listed Refer to this addendum for due dates for Price Proposal and Technical Proroposal.

35. A. Please confirm whether the 24×7 requirement in Sec. 3.8.A.5 is limited to telephone/remote support, or if Sec. 2.05 TS-

2(A) page 182 intends to require 24×7 on-site support. B. If 24×7 on-site is not intended, please confirm that on-site coverage is limited to the hours listed in TS-

2(B): • Mon–Fri: 7:30 AM–4:30 PM • Sat–

Sun: 7:30 AM–4:30 PM Are holidays included in these shifts? C. If 24x7 onsite support is intended, how many technicians are required per shift? Is overlap/handover time expected?

TS-2 section 2.05 refers to the Service Level Agreement provisions. In order for MAA to request on-site support on a 24x7 basis (namely, outside of the hour specified in

TS-2), the selected proposer must provide telephone support 24x7 in accordance with specification 270000-

3.8.A.5. On-site staff only need to be physically present during the days/hours listed in TS-2. Holidays are included in these shifts. One technician is sufficient.

The vendor is responsible to determine if shift overlap is required in order to provide continuous on-site coverage during the hours specified.

36. The drawings show 5 bag belts. Are there currently not 6 bag belts?

Bag claim 0 on the lower level of the A/B connector was recently constructed and will be added in a forthcoming addendum to include BIDS displays. An additional addedum to follow.

37. Can we assume that ESB layer will be only used to integrate between DIDS solution <-> external systems? Are any different integrations considered for the future?

The ESB layer is defined as the integration point between the AODB / flight information / resource management systems and external systems, enabling current and future integrations with all required systems.

Refer to the "Airport Operational Database (AODB)" paragraph in section GI-1.03 section of the RFP as well as specification 274216-1.3.E.

38. Can reports be provided through a solution like Power BI or Microsoft SQL Reports?

Yes. The RFP allows use of generic reporting tools as part of the RMS reporting function.

39. Does the requirement for Open-Source software for the purposes of integration cover the entire codebase? Is it acceptable to leverage open source libraries, technologies, and flight information standards where possible?

The requirement for the ESB to be open-source will be removed via addendum. An additioanl addendum to follow.

40. Is the EVIDS bidder required to provide an interactive wayfinding application, or is it just to display a QR code on the screen that passengers can scan to access another app?

See response to quesiton 17. The QR code shall link to a static "you are here" image that informs passengers of their current location on an airport terminal plan to assist them in navigating the airport. Additional addendum to follow.

41. There is no screen in that area now. There are 2 additional bag belts there. Is the intention to have monitors at all the belts?

Bag claim 0 on the lower level of the A/B connector will be added in a forthcoming addendum to include BIDS displays; however, this is one additional baggaeg carousel, not two. If A/B is not the area being referred to in the question, please clarify. Additional addendum to follow.

42. The terms and conditions of the RFP would be negotiated to consider their applicability and scope relating to the specific products and services we are offering. We have historically reached mutually agreeable terms. There are some references to certain regulations that may not apply to the services we are providing

The offeror is required to provide all products and services itdentified in the RFP. MAA will discuss negotible terms with the recommended awardee.

43. There are various sections covering the term and termination rights that should be clarified

The language identified in the RFP is standard language.

44. We would like to discuss and clarify the provisions on intellectual property protections covering both sides

Please clarifiy your question.

45. We would be interested in discussing the several indemnifications in the RFP to clarify the scope and application of those indemnifications. We would propose an industry standard liability cap as part of such indemnity

The language identified in the RFP is standard language.

46. Further, the applicability and scope of the provided standard and general provisions should be discussed

The language identified in the RFP is standard language.

47. Due to the scope and complexity of this project, we are respectfully requesting an extension of the due date until 12/19/25.

Please refer to this addendum.

48. Does the airport require Cat6 or Cat6a for the project?

CAT6. Additional information will be provided on an upcoming addendum.

49. While making modifications, replacing power or low voltage cabling is it acceptable for a bank of displays to be down for up to

48 hours?

Refer to specification 274216 paragraph 1.3.D.1.g.

Proposers are required to submit a phased construction schedule. The proposed phasing strategy will be evaluated as part of the overall proposal.

50. Where are the display device controllers

(DDCs) located? It was difficult to determine at the walkthrough if the units are integrated

OPS units, video extender receiver or some sort of onboard operating system

Existing DDCs are to be removed as part of the demolition scope. The system to be furnished under this contract does not need to utilize the same type / form factor DDC as the existing.

51. Due to the challenge of determining final pricing in sufficient time to acquire a proposal guaranty based upon its value to determine the guaranty amount, will MAA consider removing the Proposal Guaranty from the requirements?

No.

52. Please provide a use case for the interface with the Collins Aerospace CUSS Kiosk

The interface with the self-service portion of the Collins

Aerospace platform is for the purposes of accurate flight information being provided to passengers and for synchronization of data among all connected systems.

The AODB will become the primary source of flight information for all systems including the Collins

Aerospace CUSS.

53. Please confirm that the use case for Collins

CUPPS interface is to access a Web based application from the Collins desktop

See response to question 52. Similarly to the self-service functions, the data required to be exchanged with the CUPPS function of the Collins VMUSE platform should originate from and be shared to the

AODB to be furnsihed by the selected proposer.

54. Regarding project personnel who are, by this

RFP, required to be "100% available during the construction phase on site". Please confirm that this means they are available to come onsite and not necessarily on-site when they have no scheduled activities

Confirmed.

55. Does the airport operate a virtual server center which can be utilized for these systems? If yes, can the airport provide required resources (server and database OS, hypervisor, load balancers, etc.)?

No; it is the responsibility of the vendor to provide the necessary cloud, hybrid, or on premises server infrastructure required to support the solution.

56. Will the airport be responsible for proper disposal of the existing electronic equipment?

It is the responsibility of the vendor to properly dispose of existing equipment/materials. The selected proposal shall coordinate with MDOT/MAA for required paperwork and processes.

57. Does the ESRI indoor map include longitude/latitude or some other means to geolocated a FIDS bank?

See responses to questions 17 and 40.

58.

Is the ESRI indoor map accessible via URL?

See responses to questions 17 and 40.

59. How many conference rooms require this equipment. We could not locate them on the

Supplemental drawings

Conference room quantity is as specified on the bid tabulation form, Alternate 2. Refer to RFP specification section 274216-1.3.F for materials / items required in each conference room.

60. What is the square footage of the are to be provided as a test lab?

Proposers shall provide a minimum required square footage in order to meet the requirements stipulated in

RFP specification section 274216-2.3.K. The MAA will provide such a space.

OFFICE OF PROCUREMENT & MATERIALS MGMT

PLAN HOLDERS/BIDDERS LIST

CONTRACT NO: MAA-CO-26-001/MAA MC 26-014

TITLE: Design, Installation and Support of Airport Data and Information Display Systems

PRE-BID DATE: October 23, 2025 @ 10:00 AM – Via TEAMS

BID DUE DATE: January 13, 2026 @ 01:00 PM (Subject to Change via Addenda)

BID OPEN: January13, 2026 @ 01:05 PM – Via TEAMS

Name Company Email Phone

Tony Chapman

AJC Aviation

Tony@ajcaviation.com

(847) 850-9949

Whitney Harvey

Zach Varwig

Faith Group, LLC zach@faithgroupllc.com

C. 618-531-7012

O. 314-991-2228

Heather Maranto

Glenelg Construction, Inc hmaranto@glenelginc.com

301-703-4397

Gerald Libercci

Hatzel & Buehler, Inc g.libercci@hatzelandbuehler.com

410-862-1001 x7560

Greg Senkiw

International Display

Systems, Inc.

Greg@idspids.com

(P) 937-293-3118

(F) 937-293-4646

Brian Harper

Steve Moody

Infax bharper@infax.com

404-281-9330

Lindsay Kittel

Integrated Infrastructure

& Communications

Systems lindsay.kittel@mcdean.com

214.288.4731

Celso Rodriguez

RADIANT

TECHNOLOGY

GROUP INC

Celso.rodgriduez@radianttech.net

678-990-7925

Addendum No. 4

Page i of i

ACKNOWLEDGEMENT OF RECEIPT

of

ADDENDUM No. 4

10 December 2025

ADDENDUM

for

CONTRACT No. MAA-CO-26-001/ MAA-MC-26-014

Design, Installation and Support of Airport Data, Information Display and Management Systems at

Baltimore/Washington International Thurgood Marshall Airport

(dated) October 16, 2025

The undersigned acknowledges that Addendum No. 4 dated 10 December 2025 to Maryland Aviation

Administration Technical Provisions for Contract No. MAA-CO-26-001/ MAA-MC-26-014 has been received by the undersigned and will be incorporated in all copies of said Technical Provisions in the possession of the undersigned.

It is understood that all proposals submitted in response to MAA-CO-26-001/ MAA-MC-26-014 will be presumed to be based upon full knowledge of the contents of Addendum No. 4.

(Company name)

By: ________________________________________________

(Signature-Authorized Official)

(Title)

(Date)

IMPORTANT

NOTE: PLEASE SIGN AND DATE THE “ACKNOWLEDGEMENT OF RECEIPT” AND

RETURN VIA EMAIL TO MQueen6@bwiairport.com IMMEDIATELY.

mailto:MQueen6@bwiairport.com