Passenger mobile power
Self-service Power Pack™ rental and on-unit charging is designed for gates, concourses, lounges and baggage claim, so a low battery is less likely to interrupt the journey.
Airports
Intelligent Infrastructure for the World’s Busiest Spaces.
GridPulse is designed to bring connected passenger infrastructure into terminals: mobile power access, digital media, AI concierge, intelligent wayfinding and terminal analytics, proposed as one managed platform on PulseOS™.
GridPulse is the operating system for intelligent public infrastructure.
Platform capabilities
One installation. Nine terminal capabilities.
Non-aeronautical revenue potential
Rental and media inventory create a commercial line item from square footage that is currently non-revenue. Structure and share are defined in the agreement.
Digital media surface
Terminal-grade vertical displays are designed to carry scheduled, airport-approved content. Airport messaging, concession promotion and sponsor inventory are intended to run in the same loop.
AI concierge
Pulse AI™ is designed to answer passenger questions at the unit — amenities, services, terminal orientation — in multiple languages, within the content scope the airport approves.
Intelligent wayfinding
On-screen directional guidance to gates, restrooms, concessions and services, proposed for configuration against the airport's own terminal map and naming.
Multilingual support
Interface and concierge responses in multiple languages, matched to the traveller mix each terminal actually serves.
Terminal analytics
Utilisation, dwell and interaction reporting from the units themselves, intended to be delivered in aggregate and scoped by a joint privacy review.
PulseOS™ operations
One command layer intended for fleet status, content scheduling, service dispatch and reporting across every deployed unit.
GridPulse Guardian™ (optional)
An optional resilience module for continued unit operation and airport-authored messaging during defined disruption scenarios. Scope, limits and any emergency role are agreed with the airport in advance.
GridPulse is a development-stage platform. Capabilities described are designed or proposed platform capabilities. Availability at a specific site depends on the site survey, airport approvals and the final agreement.
Executive overview
Executive overview
A one-page briefing for commercial, innovation, IT, operations, concessions and passenger-experience leadership.
The problem
Passengers arrive at the terminal dependent on a device for boarding passes, identity, payment, navigation and communication. Fixed outlets and wall-mounted charging serve that need well where they exist, but they hold the passenger at one point, are typically not instrumented, and are not usually structured as a commercial or communication surface for the airport. GridPulse is proposed as a complement to existing charging provision, not a replacement for it.
The GridPulse solution
GridPulse Hub™ units combine Power Pack™ rental, a digital media surface, an AI concierge and wayfinding in one managed installation, operated centrally through PulseOS™. Passengers keep moving while charging; the airport gains a controllable communication surface and reporting on how the space is used.
Operational model
GridPulse supplies, installs, monitors and services the units. The airport provides site access, power and network availability, and approves placement and content. Commercial terms, revenue share and any airport contribution are defined in the pilot agreement.
Value to the airport
A passenger-experience improvement that is visible on day one, an additional commercial surface in existing footprint, a channel for airport and concession messaging, and terminal-level insight into dwell and interaction — all under airport content control.
Pilot structure
A defined pilot of 90–180 days with a small deployment of GridPulse Hub™ units in jointly selected positions, structured review points, and a documented decision on expansion at the end of the term.
How success is measured
A KPI scorecard agreed before launch: availability, rentals and utilisation, Power Pack™ circulation, passenger interactions, media delivery, concierge and wayfinding use, passenger feedback, service response, and commercial performance where applicable.
Expansion pathway
If the pilot meets the agreed measures, the parties move to a terminal-wide or airport-wide agreement with a phased deployment plan, extended reporting and, where relevant, Mini Hub™ units in secondary positions.
Pilot assessment
Assess a GridPulse airport pilot.
A short, confidential working session with your terminal, concessions and technology leadership to establish whether a pilot is worth scoping.
Site-fit discussion
Candidate concourse positions, passenger flow, power and network considerations reviewed against your terminal constraints.
Tailored pilot outline
A written outline of scope, placement count, timeline and success measures, drafted around your priorities rather than a fixed template.
Commercial and operational review
Ownership, servicing, staffing expectations and the commercial model reviewed together, subject to airport approval.
Pilot structure
A defined pilot, with assumptions written down.
Each item below is a starting position for discussion, not a term sheet. Placeholder assumptions are labelled and finalised in negotiation.
Pilot duration
A defined evaluation window long enough to cover seasonal variation and at least two full review cycles.
Assumption
Proposed: 90–180 days. Final term set in the agreement.
Initial deployment
A small, high-visibility footprint that can be measured cleanly and expanded without rework.
Assumption
Proposed: 1–3 GridPulse Hub™ units, subject to site survey and agreement.
Location selection
Positions chosen jointly from passenger-flow data, dwell zones, concession adjacency, power and network availability, egress and accessibility clearances, and airport aesthetic standards.
Assumption
Placements confirmed in writing after the site survey.
Installation and commissioning
Staged delivery, placement, power and network connection, PulseOS™ registration, content load, and functional acceptance walkthrough with airport representatives.
Assumption
Scheduled in airport-approved work windows.
Staff and stakeholder onboarding
Briefings for operations, customer-service and concession teams: what the unit does, how passengers use it, how to escalate, and who owns each response path.
Assumption
Session count and format agreed with airport operations.
Support and maintenance
Remote monitoring through PulseOS™, scheduled service visits, Power Pack™ replenishment, consumable replacement, and a named escalation contact.
Assumption
Response targets and service windows defined in the agreement.
Review cadence
Structured reviews against the agreed scorecard, with a written summary and an action list after each.
Assumption
Proposed: 30 / 60 / 90-day reviews, extended for longer terms.
Scale-up decision
A documented go / adjust / conclude decision at the end of the pilot, with a proposed phased plan if the parties proceed.
Assumption
Commercial structure for expansion negotiated separately.
Commercial structure is negotiable and subject to the final pilot agreement. Nothing on this page constitutes an offer, a guarantee of cost, or a commitment that the pilot is provided at no charge.
Objectives and KPIs
The pilot scorecard.
The measures below form the proposed evaluation framework. Every metric names where the data comes from.
| Metric | Definition | Data source |
|---|---|---|
| Hub availability | Share of operating hours each unit is powered, connected and able to serve passengers. | PulseOS™ telemetry |
| Charging transactions | Completed Power Pack™ rentals and on-unit charging sessions per unit per day. | PulseOS™ transactions |
| Fleet utilisation | Rentals against available bay-turn capacity across the pilot footprint. | PulseOS™ telemetry |
| Power Pack™ circulation and return rate | Packs in circulation, average hold duration, and share returned to any unit. | PulseOS™ transactions |
| Passenger interactions | Screen and interface interactions per unit per day, excluding completed rentals. | Unit interaction logs |
| Media impressions and engagement | Delivered content plays, estimated impressions and interaction with promoted content. | PulseOS™ content reporting |
| Dwell and foot traffic | Aggregate dwell and passing-traffic indicators for the immediate zone, where legally and technically supported at the site. | Airport systems and/or aggregate sensing, subject to privacy review |
| Concierge and wayfinding use | Pulse AI™ concierge sessions, wayfinding requests and top question categories. | Pulse AI™ session logs |
| Passenger feedback | On-unit sentiment prompts and any airport survey items agreed for the pilot. | Unit feedback prompt and airport surveys |
| Operational response | Service tickets raised, time to acknowledge, and time to restore service. | GridPulse service log |
| Commercial performance | Gross rental and media revenue, and share settlement, where a commercial arrangement applies. | PulseOS™ settlement reporting |
Final KPIs, measurement methodology, data-privacy terms and reporting cadence are defined jointly with the airport before launch. Metrics that depend on airport systems or third-party data are included only where the airport confirms they are available and permitted.
Scenario calculator
Model the pilot with your own assumptions.
Enter the traffic, pricing and commercial assumptions you consider realistic. The model returns low, base and high scenarios for discussion.
Illustrative monthly scenarios
| Output | Low | Base | High |
|---|---|---|---|
| Rentals per day | 6 | 18 | 30 |
| Fleet utilisation | 3.6% | 10% | 16.9% |
| Monthly rental revenue | $972 | $2,700 | $4,563 |
| Monthly media impressions | 10,800 | 18,000 | 23,400 |
| Monthly media revenue | $76 | $126 | $164 |
| Monthly gross revenue | $1,048 | $2,826 | $4,727 |
| Airport share | $105 | $283 | $473 |
| GridPulse share | $943 | $2,543 | $4,254 |
| Operating cost | $600 | $600 | $600 |
| Operating contribution | $343 | $1,943 | $3,654 |
| Payback sensitivity | 29.2 months | 5.1 months | 2.7 months |
Illustrative projections only. Outputs are calculated from the assumptions you enter and are not forecasts, guarantees or offers of revenue, savings or performance.
Illustrative projections only. Outputs are calculated from the assumptions you enter and are not forecasts, guarantees or offers of revenue, savings or performance.
Timeline
From first conversation to expansion decision.
01
Discovery and qualification
Objectives, stakeholders, terminal context, decision path and timing.
02
Site survey and technical review
Placement, power, network, egress, accessibility clearances and IT requirements.
03
Commercial and legal alignment
Pilot agreement, revenue structure, insurance, data terms and approvals.
04
Hardware configuration
Unit build, finish and branding configuration for the approved positions.
05
Content and PulseOS™ setup
Content loop, wayfinding map, concierge scope, languages and reporting access.
06
Installation and commissioning
Delivery, installation in approved windows, connection and functional acceptance.
07
Pilot launch
Go-live, staff briefing, passenger communication and baseline capture.
08
30 / 60 / 90-day reviews
Scorecard reporting, placement and content tuning, written action list.
09
Expansion decision
Joint go / adjust / conclude decision and phased plan if proceeding.
All commercial terms, placements, durations and unit counts shown are placeholder assumptions for discussion and are subject to site survey and the final pilot agreement.
Responsibilities
Who does what.
| Area | GridPulse | Airport |
|---|---|---|
| Site access | Schedules work to airport-approved windows and badging rules. | Grants access, badging and escort where required. |
| Power availability | Specifies requirements and connects at the provided point. | Provides and maintains the power supply at the agreed position. |
| Network availability | Specifies connectivity needs; supplies managed connectivity where agreed. | Confirms the network path and any security requirements. |
| Installation coordination | Delivers, installs and commissions the units. | Approves placement, timing and any floor or structural conditions. |
| Permits and approvals | Supplies documentation for submissions. | Owns and obtains airport-side permits and internal approvals. |
| Branding and content approval | Builds and schedules the content loop in PulseOS™. | Approves branding, advertisers and content categories. |
| Daily operations | Monitors fleet status and manages platform operations. | Reports on-site observations through the agreed escalation path. |
| Maintenance and service | Performs service visits, replenishment and repairs. | Provides access for scheduled and unscheduled service. |
| Physical security | Specifies securement and tamper handling. | Provides terminal security and incident reporting per airport policy. |
| Data and privacy review | Documents data collected, retention and processing. | Reviews and approves terms before launch. |
| Emergency messaging authority | Provides the technical capability to display airport-authored messages. | Retains sole authority over emergency content and activation. |
| Insurance | Maintains coverage as specified in the agreement. | Confirms required limits and certificate handling. |
| Pilot reporting | Delivers scorecard reporting on the agreed cadence. | Provides any airport-side data agreed in the privacy review. |
All responsibilities are indicative and subject to the final pilot agreement.
FAQ
Questions airport teams ask first.
01We already have charging outlets. Why does the terminal need this?
Existing outlets remain useful, and GridPulse is intended to sit alongside them rather than replace them. The difference is mobility and instrumentation: the passenger can take the power with them, and the same footprint is designed to carry a managed screen, concierge and wayfinding layer with central reporting in PulseOS™. Comparative outcomes depend on placement and are measured during the pilot.
02What is the capital and commercial structure?
GridPulse proposes a managed deployment with a defined commercial structure per site. Capital treatment, revenue share and any airport contribution are negotiable and set in the pilot agreement. We do not represent the pilot as free or zero-cost.
03What is the installation footprint and disruption?
Each unit occupies a small floor footprint at an agreed position and requires a power connection and network path. Installation is scheduled in airport-approved windows and is designed to be reversible.
04What are the cybersecurity and network requirements?
Units connect over a network path agreed with airport IT, which may be airport-provided or GridPulse-managed connectivity. We complete the airport's security review and documentation requirements before connection; specific controls are confirmed with the airport's IT team.
05How is accessibility handled?
Placement, reach and interface behaviour are reviewed with the airport during the site survey against the accessibility standards the airport applies. Final accessibility determinations rest with the airport and its consultants.
06How is privacy and analytics handled?
Reporting is designed around aggregate operational and interaction data. Any data category, retention period and processing role is documented and approved in a joint privacy review before launch.
07Who controls advertising and content?
The airport approves content categories, advertisers and creative standards. Airport and concession messaging can be scheduled in the same loop, and content can be changed or removed through PulseOS™.
08What happens with maintenance and Power Pack™ loss?
Fleet status is monitored in PulseOS™ and service is scheduled proactively. Rentals are tied to a payment method, and loss handling, replacement and any associated charges are defined in the agreement.
09What exactly does GridPulse Guardian™ do?
Guardian™ is an optional resilience module intended to support continued unit operation and display of airport-authored messages during defined disruption scenarios. It is not an emergency response system, is not a substitute for airport life-safety systems, and carries no certification claim. Scope and limits are agreed in writing.
10Can it integrate with existing airport systems?
Integrations — terminal maps, flight information, concession promotions, messaging feeds — are scoped case by case with airport IT. The pilot can run standalone and add integrations as they are approved.
11How does the pilot end if we do not proceed?
At the end of the term, GridPulse removes the units and restores the position to its prior condition, on a schedule agreed with airport operations. Removal terms are part of the pilot agreement.
Start with one terminal position.
Tell us the terminal, the passenger volume and the timeline. We will come back with a site-survey proposal and a draft pilot structure.
