← All team briefs
PROPOSED INTERNAL WORKING BRIEF / Delivery & systems

Technology & Data
Connect the guest journey to a resilient operating system.

Define the F&B technology architecture and stadium integration requirements. Hardware, software and relevant platforms require Client approval; no supplier is selected by this brief.

View the Global Big Picture →

Working direction for the Milano bid. Named owners, resources and the final solution still require confirmation.

THE QUESTION TO ANSWER

Which technology solves a service problem, and how does it integrate?

Define the F&B technology architecture and stadium integration requirements. Hardware, software and relevant platforms require Client approval; no supplier is selected by this brief.

01 / Integration architecture

Connect POS/cashless payments, ordering, inventory, kitchen/fulfilment, CRM/data and stadium reporting. Define data flows, interfaces and responsibilities.

Required internal output

System diagram, integration/data requirements and procurement/approval matrix.

02 / Guest-facing options

Assess mobile pre-order and geolocated collection, premium in-seat delivery, digital menus in IT/EN/ES, wait-time displays and smart-fridge/automated retail pilots.

Required internal output

Options by zone and use case; dependencies, inclusion considerations, cost inputs and measurable pilot criteria.

03 / Control & resilience

Specify testing, service support, network/payment failure procedures, data/privacy review and safe content control for prices, allergens and availability.

Required internal output

Testing and fallback plan; data governance and menu-content approval workflow.

IDEAS TO DEVELOP · NOT AN AGREED SOLUTION
  • Separate ordering from collection capacity: an app can increase congestion if production and pickup are not designed together.
  • Test dynamic pricing within Client-approved rules and a clear fan-value policy; model the effect before committing to deployment.

Bring to the bid

Technology architecture + zone-by-zone option matrix + interface and testing plan.

Decision this enables

Choose technologies to include in the base concept, pilot or defer, with clear ownership and approval.

Ready when

Menu-board procurement/install stays with Client oversight; operator programming is approval-controlled. Fallbacks and lifetime cost are included.

Handoff & dependencies

E15 specifies information; Operations specifies service; BUILT specifies physical interfaces; Client ICT and Legal confirm integration and controls.

Named owner: to confirmFirst pass: G1 / challenge at G2Final: G3, then G4 release

Response mapping: Exhibit A §05(ii); Exhibit B §1D–E; Exhibit F; RFP technology objectives.

EXPECTED SUBMISSION FROM THIS TEAM

The minimum bid-ready package.

Use this as the proposed structure for the first working submission. The substance matters more than the number of slides or pages. Confirm the owner, effort and scope before committing the final offer.

  • A system architecture diagram connecting POS, payments, ordering, fulfilment, stock, menu content, CRM/data, dashboards and stadium platforms.
  • A technology option matrix by venue zone: service problem, proposed solution, guest benefit, integration, support and lifetime-cost implications.
  • A responsibility schedule identifying selection/approval, procurement, installation, configuration, data ownership and ongoing support.
  • A test/pilot and fallback plan, including approved content changes, accessibility, network/payment interruption and operational recovery.
ILLUSTRATIVE MILANO APPLICATION

What a useful first response looks like.

For mobile pre-order, map the full transaction from menu availability and payment through production, pickup notification, collection and reconciliation. Identify who changes stock availability and prevents orders exceeding fulfilment capacity. Compare the proposition with a conventional service baseline; a new ordering channel should only enter the proposed solution if it improves the whole service journey.

RESOLVE BEFORE DEVELOPING THE DETAIL

Questions the team must close.

  • What stadium app, payment, CRM, network and IPTV decisions have already been made?
  • Which integrations, data controls and Client approvals are mandatory?
  • How will each service continue safely and accurately when connectivity or a component fails?
READY FOR THE INTEGRATED REVIEW

Bring a reviewable proposal.
Make assumptions visible.

Include the proposed recommendation, supporting evidence, unresolved inputs and the decision required from the wider team.