Airport Info for Mactan–Cebu International Airport (CEB) with FlightLabs Airports by Filter API

Mactan–Cebu International Airport (CEB) is the gateway to the Visayas and a primary hub of Philippine aviation. As the second-busiest airport in the country, it anchors tourism, logistics, and business travel in a region that connects central and southern Philippines to major Asian cities. For developers and analysts, up-to-date airport info about CEB is mission-critical—whether you’re powering a travel app, orchestrating corporate journeys, or running airport operations dashboards. With FlightLabs, you can retrieve structured, reliable airport data for Cebu through a simple, filterable API.

In this article, we’ll show how to filter and retrieve Mactan–Cebu International Airport data using the Airports by Filter capability in FlightLabs. We’ll also walk through JSON examples, explain the key fields that matter for displays and analytics, and outline practical use cases across travel, aviation services, and logistics. You’ll see why frequent API calls lead to better decision-making, and how FlightLabs blends real-time signals, schedules, and historical context into a comprehensive picture of airport operations.

Why Mactan–Cebu International Airport (CEB) is a Critical Data Hub for Travel and Aviation

Mactan–Cebu International Airport sits on Mactan Island in Lapu-Lapu City, just across the channel from Cebu City. Its geography is strategic: CEB is the central point linking the Visayas and Mindanao with Metro Manila and wider Asia. This location enables efficient north–south connectivity and underpins tourism flows to world-class destinations like Bohol, Siargao, and Palawan via connecting flights.

Historically, the airport has evolved from a military airfield to a modern international hub. Over the past two decades, it has seen sustained infrastructure investments, culminating in the opening of a new international terminal. This development supported steady growth in passenger throughput and capacity. While traffic patterns fluctuated during global downturns, Cebu’s recovery trajectory has reinforced its position as a resilient secondary hub in Southeast Asia.

In typical years, annual passenger volumes for CEB reach into the millions and have shown long-term growth trends. The airport serves a robust mix of domestic routes across the Philippine archipelago and international destinations in East and Southeast Asia. Several airlines—including full-service and low-cost carriers—use Cebu as a base or focus city, feeding both point-to-point demand and onward connections.

Infrastructure-wise, Mactan–Cebu features multiple terminals, with dedicated areas for domestic and international operations. The runway complex supports medium to long-haul operations, while the aprons and taxiways accommodate a diverse fleet mix—from regional turboprops to narrow-body and select wide-body aircraft. Special facilities, such as domestic transfer corridors, customs and immigration zones, and modern retail spaces, contribute to efficient passenger handling and airport revenue streams.

Economically, CEB is a growth engine for Central Visayas. It stimulates tourism, supports export-oriented industries, and links Cebu’s BPO and technology sectors to regional and global partners. The airport’s connectivity underwrites hospitality, retail, and logistics ecosystems across Cebu and neighboring islands. For airlines, Cebu offers a cost-effective base near thriving leisure markets, while for logistics operators, it is a reliable point for time-sensitive cargo.

CEB also has unique operational characteristics. Seasonal tourism surges, weather variability in a tropical maritime climate, and complex inter-island schedules are practical realities. These dynamics make precise, frequent, and filtered airport information critical—your systems need to interpret terminal allocations, gates, and runway constraints alongside schedules and real-time statuses. That’s why tracking flight data at Cebu is so valuable: it guides staffing, gate planning, transfers, disruption management, and communications with travelers and partners.

With a comprehensive and filterable Airports by Filter capability, FlightLabs lets you retrieve only what you need about CEB—standardized identifiers, terminals, runway data, coordinates, and time zone—so you can consistently map airport data to operational plans. Combined with real-time flight tracking, schedules, and historical insights, this foundational airport info transforms raw signals into reliable, context-rich intelligence.

Filter and Retrieve Structured CEB Airport Data with the Airports by Filter Capability

Developers and analysts often start with verified, structured airport data. For Cebu (IATA: CEB, ICAO: RPVM), the FlightLabs Airports by Filter capability allows you to query by key identifiers and return normalized fields such as coordinates, terminals, runways, and time zone. This ensures your downstream systems have a consistent source of airport truth to align real-time and scheduled flight data.

At a high level, you filter by IATA or ICAO to target CEB precisely. The response includes a predictable schema containing airport identifiers, location attributes, time zone information, terminal listings, runway details, and operational context like weather. Using a single field like IATA is ideal for quick lookups in your travel app, while adding ICAO can bolster disambiguation in enterprise data lakes and analytics pipelines.

Here is a representative curl request to retrieve Mactan–Cebu airport data. Replace YOUR_API_KEY with your key. You can obtain an API key by visiting https://www.goflightlabs.com and creating an account.

curl -G "https://www.goflightlabs.com/airports" \
--data-urlencode "access_key=YOUR_API_KEY" \
--data-urlencode "iata=CEB"

The API returns clean, structured JSON. Below is an example tailored to CEB following the FlightLabs Airport Information schema.

{
"success": true,
"data": {
"airport": {
"iata": "CEB",
"icao": "RPVM",
"name": "Mactan–Cebu International Airport",
"location": {
"lat": 10.3133,
"lon": 123.9820,
"city": "Lapu-Lapu City",
"country": "Philippines"
},
"timezone": "Asia/Manila",
"terminals": [
"T1",
"T2"
],
"runways": [
{
"length_ft": 10827,
"width_ft": 148,
"surface": "asphalt",
"designator": "04/22"
}
],
"weather": {
"temp_c": 30,
"visibility_km": 8,
"wind": {
"speed_kts": 10,
"direction_deg": 140
}
}
}
}
}

Each field serves a clear operational purpose. The iata and icao codes anchor joins across your data model. The location block supports map markers, distance calculations, and regional analytics. The timezone ensures proper conversion between UTC timestamps and local time, essential for departure boards and trip planners. The terminals and runways arrays inform gate/stand planning logic and aircraft performance constraints. Weather adds near-term operational context for flow control and disruption analysis.

For ongoing operations, the best practice is to call the Airports by Filter capability repeatedly whenever you initialize a session, refresh metadata caches, or load new destinations. Frequent calls ensure you always have the most up-to-date terminal mappings, runway configurations, and airport-level context—vital for accurate live tracking, schedule alignment, and post-operational reporting.

To explore the broader FlightLabs platform, including real-time tracking and scheduled flights, visit https://www.goflightlabs.com. After you secure your API key, you can combine airport info with flight statuses and timetables for a unified operational view at CEB.

Why FlightLabs Delivers the Most Complete API for Mactan–Cebu (CEB)

When your apps depend on accuracy at CEB, the depth and timeliness of your airport and flight data defines the end-user experience. FlightLabs provides strong coverage for Cebu’s domestic and international operations, with rich fields that surface terminals, runway designators, and weather context alongside core identifiers. This comprehensive coverage aligns with the airport’s role as a mixed-use hub serving leisure, corporate, and connecting traffic.

Data freshness is equally important. Cebu’s schedule can shift due to operational dynamics, and terminal assignments may change during the day. Frequent FlightLabs calls provide ongoing visibility into updates, preserving display consistency and alerting workflows. Receiving standardized fields in predictable schemas means your systems can autonomously process changes without manual intervention.

CEB has unique characteristics—regional turboprop operations for inter-island hops and narrow-body aircraft for trunk routes. FlightLabs captures this diversity through real-time flight tracking, routes, and schedules that reflect aircraft type patterns and operational realities. Layering Airport Information with flight status data helps you infer peak times at terminals, gate utilization pressure, and runway sequencing workloads.

Several special data points stand out for Cebu:

• Timezone alignment (Asia/Manila): Critical for displaying local times and computing layover durations across Philippine domestic networks.
• Terminal segmentation (T1 and T2): Useful for guiding passengers, staffing allocations, and lounge planning.
• Runway 04/22 attributes: Essential for operational analytics and fleet pairing decisions in schedule models.
• Weather context: Supports short-term demand–capacity balancing and OTG (on-time gate) predictions.

Accuracy and timeliness are not abstract benefits; they translate to fewer missed connections, better traveler communications, and more reliable SLA adherence. By consistently pulling airport and flight data, your systems stay aligned with Cebu’s day-of-operations realities, reducing error risk and improving passenger and partner satisfaction.

In particular, FlightLabs’ strength is its interoperability across endpoints. You start with Airports by Filter to lock down CEB identifiers and structure. Then you enrich the picture with Real-time Flight Tracking, Flight Schedules, and Flight History. This multi-endpoint orchestration is especially effective at CEB, where domestic feeders, international arrivals, and weather conditions vary over the day. The more often you call, the better your model reflects what’s happening on the ground.

JSON Examples: CEB Airport Info, Real-Time Status, and Schedules

CEB Airport Information (Filtered by IATA)

Use the Airports by Filter capability to retrieve a precise, standardized document for Mactan–Cebu International Airport. The response mirrors the structure shown earlier and is suitable for metadata initialization, map overlays, and static references in your apps.

{
"success": true,
"data": {
"airport": {
"iata": "CEB",
"icao": "RPVM",
"name": "Mactan–Cebu International Airport",
"location": {
"lat": 10.3133,
"lon": 123.9820,
"city": "Lapu-Lapu City",
"country": "Philippines"
},
"timezone": "Asia/Manila",
"terminals": ["T1","T2"],
"runways": [
{
"length_ft": 10827,
"width_ft": 148,
"surface": "asphalt",
"designator": "04/22"
}
],
"weather": {
"temp_c": 30,
"visibility_km": 8,
"wind": {
"speed_kts": 10,
"direction_deg": 140
}
}
}
}
}

Key fields to note:

• iata / icao: Use both for robust joins and disambiguation.
• timezone: Always convert scheduled and actual times correctly.
• terminals: Populate passenger guidance and gate/stand logic.
• runways: Feed operational analytics and performance planning.
• weather: Provide situational awareness and disruption signals.

Real-time Flight Tracking Example for a CEB Route

After anchoring your airport metadata, expand into live operations. Track in-flight movements connected to CEB—identify status, estimated arrivals, and current position. Below is a realistic schema following FlightLabs’ real-time structure.

{
"success": true,
"data": {
"flight": {
"iata": "5J580",
"icao": "CEB580",
"number": "580",
"status": "en-route",
"departure": {
"airport": "MNL",
"scheduled": "2024-03-20T04:40:00Z",
"actual": "2024-03-20T04:55:00Z",
"terminal": "3",
"gate": "130"
},
"arrival": {
"airport": "CEB",
"scheduled": "2024-03-20T06:10:00Z",
"estimated": "2024-03-20T06:18:00Z",
"terminal": "T1",
"gate": "12"
},
"position": {
"latitude": 11.5600,
"longitude": 122.9500,
"altitude": 34000,
"speed": 470,
"heading": 165
}
}
}
}

Important operational fields:

• status: en-route, delayed, landed, etc.—drive alerts and ETAs.
• scheduled/actual/estimated: compute delays and forecast arrival readiness.
• terminal/gate: synchronize passenger flows and ground handling.
• position: enables map overlays and arrival countdowns.

Flight Schedule Example with CEB as Destination

Schedules give you the planned baseline for O&D (origin/destination) and connectivity analysis. The example below follows FlightLabs’ schedule schema with CEB as arrival.

{
"success": true,
"data": {
"schedules": [
{
"flight_number": "5J571",
"departure": {
"airport": "MNL",
"scheduled": "2024-03-20T02:40:00Z",
"terminal": "3"
},
"arrival": {
"airport": "CEB",
"scheduled": "2024-03-20T04:10:00Z",
"terminal": "T1"
},
"aircraft": {
"type": "Airbus A320",
"registration": "RP-C3271"
},
"airline": {
"name": "Cebu Pacific Air",
"iata": "5J"
}
}
]
}
}

Practical fields to monitor:

• flight_number + airline: pair with real-time statuses to track punctuality.
• departure/arrival scheduled: align displays, transfer buffers, and staffing.
• aircraft type: predict turnaround times and gate demand at CEB terminals.

Business Use Cases at CEB: Turning Structured Airport Data into Outcomes

Travel Apps and Passenger Communications

For consumer travel apps, accurate CEB metadata and live statuses power trusted trip timelines. Use the Airports by Filter capability to fetch terminals and time zone, then combine with real-time tracking to show local ETAs, terminal directions, and gate status. Notifications fire when arrival estimates change, reducing gate confusion and missed connections.

Frequent API calls refine your accuracy. Repeatedly querying schedules and live statuses for the next 2–6 hours at CEB keeps alerts precise during peak periods. For partners, expose an internal API that mirrors FlightLabs fields, preserving consistency across web, mobile, and kiosk interfaces.

Airport Displays and Operational Dashboards

Airport teams can assemble arrival/departure dashboards anchored on CEB’s airport info. Terminals and runway attributes align with gate planning and estimated taxi times. By correlating real-time tracking with scheduled blocks, you can predict arrival banks, gate occupancy transitions, and potential delays due to flow constraints.

Making more calls per minute during busy hours leads to more reliable stands and faster reassignments. When a flight switches gate or is retimed, updated fields propagate into shift plans and turnarounds. Use standardized fields like status, terminal, and gate to power color-coded operational boards.

Logistics and Express Cargo

CEB supports time-sensitive cargo routes that feed domestic markets. Use airport info to configure your route maps and cutover windows, then apply real-time tracking to predict inbound dock readiness. Integrate weather signals to pre-stage ground crews ahead of wind or visibility impacts.

Historical flight data provides enriched performance analytics, helping planners understand typical variance by time of day. Combining airport metadata with flight history lets you detect patterns—where buffer times need adjustment, which inbound flows typically compress gate availability, and how runway conditions influence block times.

Corporate Travel Management

Corporate platforms can leverage CEB airport data to streamline traveler experiences. Terminal and gate fields guide live notifications for inbound client visits or employee trips. Schedules help plan feasible meetings with realistic slack between segments.

By increasing the frequency of status checks across key arrival windows at CEB, you ensure meeting itineraries adapt to current conditions. High-fidelity data prevents wasted hours and supports policy compliance through reliable, just-in-time alerts.

CEB Operations in Practice: Real-Time, Schedules, and History Working Together

Unifying Schedules and Real-Time at CEB

Schedules define intent; real-time data captures reality. At Mactan–Cebu, frequent inbound/outbound waves mean a few minutes of variance can cascade across gates and transfers. Fetch future flights and same-day schedules regularly, then reconcile them with real-time statuses to derive live predictions of gate occupancy and passenger flows.

When a delay surfaces in real-time tracking, compute expected knock-on effects: late aircraft arrival leads to adjacent gate conflicts or boarding delays. Having the airport’s standard terminals and runway configuration on hand reduces ambiguity in your automatic re-planning logic.

Historical Context Improves Predictions

Pull flight history for CEB routes to analyze typical late-night and early-morning behavior. Use past variability to set smarter alert thresholds for current operations. High-frequency archival calls enable better regression to norms and more resilient forecasts when faced with outliers.

FlightLabs’ structure means you can retain consistent fields across real-time and historical endpoints. This uniformity simplifies your data model and speeds up analytics—especially when tracking performance by airline, aircraft type, or terminal.

Handling Disruptions: Cancelled or Diverted Flights

Disruptions happen. For cancelled flights, status and absence of actual departure/arrival times convey the operational state. For diversions, arrival airport fields will differ from the plan, while scheduled values remain as baseline references. Train your logic on these field patterns so alerts and dashboards communicate the correct outcome.

At CEB, weather or airspace conditions can prompt diversions. Frequent calls surface the earliest authoritative signal of a status change. Monitoring adjacent airports in the Visayas amplifies situational awareness and future recovery planning.

Data Modeling for CEB: Time Zones, UTC, Terminals, Gates, and Codeshares

Time Zones and UTC

Always treat scheduled, actual, and estimated timestamps in UTC, then convert to Asia/Manila for user displays. The airport’s timezone field enables correct mapping. Avoid mixing local times across origins and destinations; standardize on UTC for storage and computation to ensure consistent delay calculations.

In passenger apps, show both local time and a “+x min delay” indicator for clarity. In operations dashboards, keep UTC prominently visible to align with airline and ATC coordination. The timezone node in the airport document is the source of truth for conversions.

Terminals, Gates, and Transfers

At Mactan–Cebu, T1 and T2 denote major flows. When pairing schedules with real-time statuses, match terminal fields to direct passengers and ground staff. Gate info often updates close to the event; frequent calls capture these changes promptly.

For transfer logic, consider minimum connecting times by terminal. You can infer pressure periods by clustering scheduled arrivals/departures per terminal and windowing them against current delays. Store terminal and gate fields with temporal validity to audit operational decisions later.

Codeshares and Airline Normalization

Codeshares mean the same physical flight appears under multiple numbers. Use the “flight iata/icao/number” trio from real-time or schedules and normalize airlines by IATA and name. This ensures displays don’t double-count flights and analytics reflect true aircraft movements.

When a codeshare’s gate or terminal diverges in data feeds, trust the operating carrier’s view. Cross-check with airport info and scheduled blocks to adjudicate discrepancies. Consistency becomes easier when every record ties back to CEB’s core identifiers.

Cancelled and Diverted Handling

Cancelled flights often retain scheduled times without actuals; diverted flights show mismatched arrival airport vs. the intended destination. Use status for the headline, then display the pertinent terminal/gate when the diversion airport is known. Maintaining a playbook for these conditions helps your app remain authoritative and calm during disruptions.

With more frequent API calls, you achieve earlier detection and more accurate user messaging. At CEB, where regional weather changes can be rapid, this responsiveness is a competitive advantage.

A Structured Comparison Framework for Evaluating APIs at CEB

Data Coverage and Accuracy

For Mactan–Cebu, complete coverage means robust domestic and international route representation, realistic schedules that capture bank structures, and reliable tracking of in-flight segments. Accuracy is demonstrated through consistent terminals, gate assignments, and prompt status updates. Consider how consistently airport metadata stays current, especially terminal assignments and runway details.

FlightLabs’ standardized schemas make it easier to verify and validate records for Cebu across days and seasons. This structure reduces engineering overhead and bolsters confidence in application-level outputs and analytics.

API Features and Query Flexibility

Core capabilities—real-time tracking, flight schedules, future flights, and routes—should all integrate seamlessly with Airport Information. The Airports by Filter capability enables precise lookups for CEB’s identifiers, time zone, and infrastructure details. Filter expressiveness is important, especially when you want to pivot quickly between airport, airline, and route-level queries.

Developers benefit from the clarity of FlightLabs’ JSON. Predictable fields cut onboarding time and reduce parsing complexity when building complex dashboards and alerting logic for Cebu operations.

Technical Considerations

Response consistency and schema stability are pillars for production systems. Evaluate how quickly updates propagate and whether field semantics are consistent across endpoints. Fault tolerance in your own stack is straightforward when every response uses a common structure and clear success/metadata envelopes.

FlightLabs’ reliability in delivering consistent JSON for CEB means fewer edge cases and faster time-to-value for your engineering teams and stakeholders.

Integration and Developer Experience

Ease of implementation starts with a clear data model and continues with representative examples. FlightLabs’ category pages—such as Real-time Flight Tracking, Flights Schedules, and Flight History—help teams conceptualize data flows quickly. Coupled with filterable airport info, it’s straightforward to assemble end-to-end solutions that are resilient and scalable.

Organizations can align internal standards with FlightLabs fields, making handoffs between teams smoother and minimizing transformation overhead.

Business Value and Insights

The value is realized when airport info, schedules, and live tracking coalesce into reliable outcomes: fewer missed connections, clearer passenger communications, and tighter ground operations. At Cebu, where inter-island flights intersect with international arrivals, balanced, accurate data is a differentiator. Regular, frequent calls to FlightLabs endpoints produce the most precise, actionable view of daily activity.

This approach enables tactical wins today and lays the foundation for strategic insights—trend discovery, performance benchmarking, and predictive planning specific to Mactan–Cebu’s context.

High-Frequency Data Patterns at CEB: Polling and Live Operational Awareness

Why More Calls Create Better Outcomes

In live airport environments like CEB, conditions change quickly—estimated arrival times, terminal changes, gate assignments, and even runway availability. High-frequency polling provides a tighter feedback loop, shrinking the time between an operational change and its reflection in your systems. This reduces misinformation and increases trust in your user interfaces and decisions.

For decision-makers, the difference is material: tighter polling windows translate to fewer escalations, more accurate ground handling triggers, and better crew/vehicle deployments. Your systems respond to the airport’s tempo rather than yesterday’s plan.

Coordinating Multiple Endpoints

Combine Airports by Filter, Real-time Flight Tracking, Flight Schedules, and Flight History for Cebu. Start by locking down airport identifiers and structure via airport info filters. Then, pull schedules for the day and the next window to establish expectations. Finally, stream in real-time statuses to track variance from plan and use historical patterns to contextualize anomalies.

The richer the join, the more nuanced your insights: terminal load curves, peak gate conflicts, and inbound-to-outbound pairing quality. Consistency in schemas means merges are predictable and scalable.

Operational Windows for Cebu

CEB sees distinct demand waves throughout the day. Increasing call frequency during peak inbound and outbound windows increases accuracy where it matters most. Keep airport metadata handy at all times to interpret terminal-gate changes quickly and present travelers with the latest information.

For analytics teams, this same data density powers more precise after-action reviews. You’ll identify which conditions drove delays, which terminals absorbed variance well, and where scheduling can adjust to improve outcomes.

FAQs: Airport Info and Flight Data for Mactan–Cebu (CEB)

What identifiers should I use to query Cebu airport?

Use IATA CEB for most lookups and display contexts, and pair with ICAO RPVM in enterprise data stores or when disambiguation is essential. These identifiers ensure joins across schedules, real-time statuses, and historical data are reliable.

How should I handle time zones for schedules and statuses?

Store and compute times in UTC, then convert to Asia/Manila using the airport’s timezone field for user-facing displays. This preserves consistency across routes that cross time zones and avoids misalignment in delay calculations.

What fields matter most for live passenger communications?

Focus on status, scheduled vs. actual/estimated times, terminal, and gate. These drive gate directions, boarding alerts, and accurate ETAs for arrivals and pickups at CEB.

How do I deal with cancelled or diverted flights?

Use the status field for the primary signal, and interpret scheduled/actual fields accordingly. For diversions, expect the arrival airport to differ from the plan; update passenger and operations dashboards to reflect the new destination and timing.

Why should I make frequent API calls for Cebu?

Frequent calls detect terminal/gate changes, schedule shifts, and status updates sooner. The result is more precise decisions, fewer surprises, and a higher-quality experience for travelers and operations teams at CEB.

Conclusion: A Complete Strategy for CEB Airport Data with FlightLabs

For Mactan–Cebu International Airport (CEB), dependable airport info and live flight data are the foundation of effective operations, clear traveler communications, and accurate analytics. The Airports by Filter capability in FlightLabs gives you a consistent, structured snapshot of CEB—covering identifiers, coordinates, time zone, terminals, runways, and weather context. This metadata anchors your data model so everything from schedules to real-time statuses can align reliably.

What sets FlightLabs apart at Cebu is its comprehensive coverage and practical field design. From standardized airport details to granular flight status attributes—status, scheduled/actual/estimated times, terminals, gates, and live positions—you get a coherent view that translates directly into business value. Whether you’re building travel apps, airport displays, logistics dashboards, or corporate travel tools, these fields are precisely what your systems need to stay in sync with fast-moving airport operations.

Frequent API calls are essential to achieving excellence at CEB. More calls mean earlier detection of changes, more accurate predictions, and fewer operational surprises. This approach empowers proactive customer messaging, smarter gate management, tighter turnarounds, and better partnership coordination across airlines, ground handlers, and hospitality providers. By combining Airports by Filter with Real-time Flight Tracking, Flight Schedules, and Flight History, your teams create a virtuous cycle of insight—each endpoint enriching the others to reflect the airport’s real-world behavior.

Looking ahead, the ability to integrate airport metadata with delay predictions and historical trends opens new frontiers in optimization. Decision-makers can continuously refine staffing plans, buffer times, and route strategies to match Cebu’s operational patterns. With FlightLabs, you’re not just consuming data—you’re building a resilient, data-driven practice tailored to one of the Philippines’ most important aviation hubs.

Start today: visit https://www.goflightlabs.com to get your API key. Then, use the Airports by Filter capability to retrieve CEB airport info, enrich it with real-time and schedules, and deliver the reliable, high-frequency insights your users and stakeholders expect.

Related Links

• FlightLabs API Homepage
• Real-time Flight Tracking
• Flight Schedules
• Flight History
• Routes
• Civil Aviation Authority of the Philippines (CAAP)

Meta Description Suggestions

• Learn how to filter and retrieve Mactan–Cebu International Airport (CEB) data using FlightLabs’ Airports by Filter API, with JSON examples, real-time tracking, and schedules.
• Build travel and operations tools with accurate CEB airport info: terminals, runways, time zone, and live flight data via FlightLabs.
• A complete guide to Mactan–Cebu (CEB) airport data using FlightLabs: structured airport info, real-time statuses, schedules, and business use cases.