Opening Two Restaurant Concepts in a Complex Airport Environment
Client
Olive & Finch Collective
Location
Denver International Airport
Concepts
Bar Finch & Little Finch
Bearheart Role
IT Project Lead
Airport openings require more than a standard technology playbook
The Challenge
Carrying proven standards into a new environment
Olive & Finch Collective planned to open two concepts at Denver International Airport: a full-service restaurant with a 24-hour self-service grab-and-go component, and a barista/grab-and-go concept. Bearheart had already supported the group through three restaurant openings, and the client wanted the same technology standards in the new locations.
The airport added a new level of complexity. Requirements called for digital signage and self-service kiosks, and the table-service operation needed a POS database and hardware deployment built around a new service model. Infrastructure, connectivity, access, deliveries, and approvals all depended on airport teams and approved contractors. With no opportunity for friends and family events, the systems had to be right before opening day.
What We Found
More stakeholders, more dependencies
The project involved far more stakeholders and dependencies than a typical restaurant build. Airport contractors handled cabling outside the leased space while different contractors worked inside it. Internet and television had to meet airport standards and be coordinated with the network operations team, and the life safety team had unique service interruption requirements for TV and sound. Security and transportation procedures added time to receiving equipment, escorting vendors, and getting technicians onsite.
The real risk was not a technical failure. Missed dependencies could delay the opening and affect the guest experience, revenue, and the group’s reputation with airport stakeholders.
What We Changed
One IT lead for every airport relationship
Bearheart served as IT project lead for both concepts, owning the relationships with airport IT, the network operations team, construction teams, tenant management, service providers, installers, and technology vendors.
Bearheart coordinated technician access, onsite coverage, deliveries, vendor escorts, infrastructure sequencing, and scheduling. Where airport requirements demanded it, we adjusted the standard approach, including the internet service model, television provider, digital signage, self-service kiosks, audio-visual, and use of the airport’s MPLS network to connect cameras in remote storage locations.
The Impact
A flawless IT launch for both concepts
Both concepts opened with a flawless IT launch despite the volume of unique requirements and stakeholders. The client’s leadership stayed focused on restaurant operations while Bearheart managed the technology, airport coordination, and vendor dependencies.
The project also kept the technology stack consistent with the group’s previous locations while making the changes airport operations required, so the client benefited from a partner that already knew its systems, standards, and priorities.
The Takeaway
Plan for an airport, not a standard build
Airport restaurants have significant revenue potential, but they are not simply a standard build in a more complicated location. Access restrictions, specialized contractors, approvals, expensive services, limited storage, and interdependent schedules all change how the project must be planned.
Restaurant groups should budget substantially more coordination time for airport technology work, and account for internet, television, airport-provided cabling, conduit, equipment storage, and vendor access early.
With little room to test through friends-and-family events, technology has to work on opening day. Experienced IT leadership absorbs the coordination burden, catches dependencies before they become delays, and protects the guest experience from day one.
A task that takes one hour in a conventional opening may require closer to three hours in an airport.
Submit Inquiry
Planning an airport or new property opening?
Bring Bearheart in early. We’ll map the dependencies before they become delays.