Glossary

Event Network Glossary

The terms that come up in every scope conversation, defined in plain language. Use it so organizers, production partners, venues, and payment vendors are all working from the same definitions — and so nothing important gets lost in the gap between AV language and network language.

Critical Operations Overlay: LGL's lead deliverable: a segmented LAN with wired drops for payments, registration, production, and staff operations, deployed behind the venue circuit. It supplements venue connectivity where permitted and never bypasses venue exclusivity. The “overlay” runs on top of the building's existing infrastructure for the event window.
Event Network Risk Assessment: The entry engagement. It validates venue rights and authorization feasibility, maps critical systems, drafts the segmentation design and data-responsibility assumptions, and returns a written scope — before any circuit orders or freight.
Segmentation: Dividing one physical network into isolated logical lanes so traffic in one cannot reach another. At events this separates payment, production, registration, attendee, contractor, and management traffic so a problem or an unknown device in one zone cannot affect the others.
Security zone: A defined segment of the network with its own boundary, access rules, and place in the responsibility matrix. LGL's standard zones cover payment, registration, production, attendee, contractor, and management.
Wired-first: The principle of putting anything the event depends on — payments, registration, encoders, production control — on a wired connection rather than shared, contended wireless. Wireless is engineered deliberately where it belongs, such as general attendee access.
Dual-WAN: Two independent upstream internet paths so that if one fails, traffic continues on the other. LGL deploys dual-WAN where the venue permits; where it does not, an approved single underlay with a defined failover plan is used instead.
Underlay: The upstream connectivity beneath the event network — the carrier fiber/DIA, terrestrial, cellular, or satellite circuits that provide internet to the site. LGL procures dedicated, redundant upstream circuits rather than reselling commodity bandwidth.
Failover: The automatic switch from a failed path or device to a backup so service continues. A failover is only trusted once it has been tested; LGL verifies failover lands inside its target window during the pre-opening acceptance test.
Demarc (demarcation point): The physical point where the venue's or carrier's responsibility for connectivity ends and the event network's begins — the handoff. Defining the demarc clarifies who owns what and is captured in the venue's site record.
Pathway: The routes — risers, conduits, trays, and approved cable runs — through which network cabling may travel in a venue. Pathways are venue-controlled; using them requires authorization and sometimes house or union labor.
RF coordination: Planning the use of radio frequencies so that the many wireless systems at an event — attendee Wi-Fi, production radios, microphones, intercom — do not interfere with one another. It is how wireless is used safely where wired is not an option.
Data responsibility: Which systems on the network can store, process, transmit, or otherwise touch payment or attendee data — and who is accountable for each. Good segmentation keeps that set small by isolating payment traffic from everything else; LGL operates transport-only, so the cardholder and attendee data itself never touches or is stored by us.
Cardholder data (CHD): Payment-card information such as the primary account number and related data elements. LGL operates at the transport layer and, by default, does not store, process, or retain cardholder data — it moves it, segmented and monitored, between the systems that own it.
Transport layer: The level at which LGL operates: moving data reliably and securely across the network, rather than inspecting, logging, or storing its contents. This is why LGL's accountability is for the network and transport it operates — not for the vendor applications that ride on it.
NOC (Network Operations Center): The remote team and tooling that monitor the event network in real time, watching for failures and alerting onsite engineers. Monitoring runs from setup through teardown.
Pre-opening acceptance test: A documented, repeatable test run before go-live that confirms segmentation holds, WAN failover lands inside its target window, critical-system redundancy is live, and monitoring is reporting. Its first-run pass rate is a metric LGL holds itself to, with a clear go/no-go owner.
SLA (Service Level Agreement): A contract that defines the level of service a provider commits to — typically availability targets, response times, and remedies if targets are missed. When reviewing any vendor's SLA, check what layer it actually covers: an SLA scoped to network transport says nothing about the uptime of the payment, registration, or streaming applications riding on it, which remain those vendors' responsibility.
Severity-1 incident: The highest-priority class of incident — a connectivity or security event with the most serious impact on the event. Severity-1 counts, mean-time-to-failover, and availability and failover performance against the targets defined for the event are tracked as components of whether the accountability promise was kept.
Venue network passport: A reusable site record for a venue capturing its demarc, pathways, RF environment, carrier options, and labor jurisdiction. It lets the same network be deployed predictably the next time an event returns to the building and is part of the data that compounds over time.
Deployment pod: A pre-labeled, standardized kit of network equipment, tactical fiber, runbooks, and configs that can be shipped and stood up fast at any venue. Standardizing into pods is what lets LGL arrive and deploy a proven, segmented network quickly.
Venue exclusivity: A venue's right to designate who may provide certain services on its property — often the house telecom or technology provider owning the building's circuit, riser cabling, and pathways. LGL supplements exclusive circuits where permitted and never bypasses exclusivity.
Venue authorization: The venue's written permission to operate a supplemental overlay network behind its circuit for the event. LGL treats it as a hard qualification gate: no non-cancellable spend before authorization is in hand.
White-label delivery: Delivering the network operations layer behind a production or AV partner's contract, so the end client sees one integrated show package. White-label delivery through production and AV partners is LGL's primary year-one channel.
Responsibility matrix: A document that allocates who is responsible for what across the venue, partner, organizer, payment vendor, and LGL — connectivity, segmentation, payment handling, escalation, and data responsibility. It replaces finger-pointing with named ownership and accompanies every engagement.
Contribution margin: Event revenue minus direct costs — circuit lease, field labor and travel, equipment depreciation and rental, and venue commissions. It is LGL's core go/no-go gate for whether an engagement is economically sound, with fleet utilization as the underlying driver.

Want the concepts in context? The Segmentation Standard Overview, the Venue Authorization Guide, and the Data Responsibility & Segmentation Guide show how these terms work together on a real deployment.

Speak the same language as your network operator

We run and stand behind your event's mission-critical network — setup to teardown — so registration, payments, production and streaming stay connected.

Request Event Network Risk Assessment Back to Resources