Juniper Premium Analytics Dubai

A cloud-based Juniper Mist subscription for organizations that need deeper historical analysis, client-to-cloud network observability, business intelligence and structured reporting across wired, wireless, WAN, security and location data.

Direct answer: what is Juniper Premium Analytics?

Juniper Premium Analytics is a licensed cloud service within the Juniper Mist environment. It is designed for organizations that need more than short-term operational dashboards: it adds deeper reporting, long-term historical analysis, richer cross-domain visibility and the ability to work with combinations of Mist data sets and, where supported, external data sources. The service is mainly used by network, security, operations and line-of-business teams that want to understand trends over weeks or months rather than examining only the latest incidents.

Organizations should consider it when they already use Juniper Mist services, when they need historical SLE and utilization analysis, when WAN or wired/wireless reports must be retained for management review, when location or visitor analytics have a business purpose, or when scheduled reporting is required. The most important factor to confirm before purchase is the exact licensing scope: which organization, sites, data domains, Juniper services and reporting requirements must be covered, and for what subscription period.

FourTeck can help translate those requirements into a quotation scope, identify the dependencies that should already exist in the Juniper Mist environment, and distinguish Premium Analytics from the standard analytics already available with certain Mist cloud services.

Why Premium Analytics exists in the Juniper Mist architecture

Modern enterprise networks generate more operational information than a team can interpret from isolated device screens. Wireless access points expose radio and client behavior; switches reveal port, PoE and traffic conditions; WAN platforms provide application and path-quality information; security systems produce event data; and location services can produce occupancy or engagement signals. The practical challenge is not simply collecting this information. It is retaining enough history, organizing it consistently and presenting it in a form that supports decisions.

Juniper Mist already includes analytics capabilities with several cloud services. Those built-in views are useful for day-to-day operations, but Juniper documents standard analytics retention as limited to 30 days. Premium Analytics is intended for organizations that need to look further back, compare time periods, examine longer trends, create more granular reports and combine data in ways that are useful for planning and governance. Juniper documentation describes Premium Analytics as providing up to 13 months or more of stored historical data, depending on the service and subscription terms.

That difference changes the type of questions a business can answer. A 30-day view can show whether a recent office move created a Wi-Fi problem. A longer history can reveal whether the same area has shown recurring demand patterns across a quarter, a busy season or a full annual cycle. A short data window can show that a WAN circuit was congested last week. A longer one can help determine whether the congestion reflects growth, a recurring application peak or a temporary event.

Premium Analytics should therefore be viewed as an observability and decision-support subscription rather than a replacement for core assurance, switching, wireless or WAN services. The quality of the analytics depends on the underlying telemetry and services feeding the Mist cloud. A buyer should first identify the decisions the business wants to make, then confirm that the necessary network and location data sources are available.

Premium Analytics versus standard Mist analytics

The important procurement point is that Premium Analytics does not make every possible data source appear automatically. The underlying Mist services, device telemetry, location capabilities and any integration path must exist and be correctly configured. The subscription expands what the organization can analyze; it does not replace the source systems that produce the data.

Core analytics domains

Long-term data is the central buying reason

The most obvious difference between Premium Analytics and the standard analytics experience is historical depth, but the business value comes from what that extra history enables. Thirty days may be sufficient for a helpdesk team investigating a recent client issue. It is often insufficient for capacity planning, quarterly service reviews, seasonal retail analysis, campus usage studies, WAN growth analysis or a year-over-year operational conversation.

A longer history allows a team to ask whether a problem is new or recurring. It can separate one unusual week from a genuine trend. It can provide evidence for budget requests by showing that a site repeatedly approaches capacity. It can help explain whether experience degradation follows application growth, user-count growth, new device types, site changes or a recurring business event.

Retention requirements should still be discussed explicitly. “Up to 13 months or more” is a service capability statement, not a substitute for a formal data-retention policy. Organizations with legal, regulatory or internal governance requirements should confirm the precise retention, export, access and deletion behavior applicable to their subscription and region before treating the analytics platform as a compliance archive.

From network telemetry to a management decision

A useful analytics deployment begins with a question, not a dashboard. For example, a network manager might ask whether wireless capacity at a Dubai headquarters is sufficient for the next twelve months. The team can then identify relevant data: client count, application demand, traffic, service-level history, access-point load and location by site or floor. Premium Analytics helps preserve and organize that information over a longer period so the answer is based on evidence rather than a single snapshot.

A second example is WAN planning. A business may have several branches with different carrier links and application mixes. A one-day utilization view might not show the problem because the site experiences heavy demand only during month-end processing or a recurring video event. Historical link and application quality information can make the pattern visible. That does not automatically prove that the circuit must be upgraded; policy, application behavior, routing, local switching and user demand may all need to be examined. The analytics narrows the investigation.

A third example is facilities or engagement analysis. A campus, showroom, hospitality property or retail environment may want to know how people use different zones over time. Where supported location services are deployed, longer-term dwell, visit and movement information can support planning. The interpretation must account for privacy policy, device behavior, sampling, coverage design and the fact that observed devices are not necessarily a perfect measure of people.

These examples illustrate why Premium Analytics should be scoped around business decisions. A buyer who purchases the service simply because “more analytics” sounds attractive may underuse it. A buyer who identifies five recurring questions that cannot be answered reliably with the standard data window has a much clearer adoption case.

Reporting, filters and scheduled delivery

The practical goal is to reduce manual reporting effort without creating a stream of reports that nobody acts on. A well-scoped Premium Analytics rollout normally defines report owners, review cadence, thresholds or questions, and an escalation or planning action for each recurring report.

Third-party and non-Mist-managed data: where it helps

Juniper positions Premium Analytics as capable of ingesting and reporting on selected data from Juniper devices and supported third-party sources that are not directly managed by the Mist cloud. This capability can be important in mixed-vendor environments or when a business wants to correlate network information with external business or location data. The phrase “third-party ingestion,” however, should not be interpreted as universal compatibility with any platform or data format.

Before a quotation is finalized, the buyer should identify each external source by vendor, platform, data type and intended analytical outcome. A useful integration statement is specific: “We need to compare visitor traffic by zone with point-of-sale transaction periods,” or “We want a unified report that includes non-Mist network device data.” An unbounded requirement such as “connect all our monitoring tools” is too broad to size or validate.

Integration also raises ownership questions. Who maintains the data feed? What happens if a third-party API changes? How often is the data updated? Is the source normalized sufficiently for meaningful comparison? Does the data contain personal, regulated or commercially sensitive information? The analytics subscription may provide a technical capability, but a reliable business workflow requires governance around the data that enters it.

For procurement, request validation of each intended external integration instead of assuming support. If external data is optional rather than central to the project, it may be sensible to begin with native Juniper Mist data and add integrations after the organization has established reporting discipline.

Role-based access and who should see the analytics

Premium Analytics supports role-based access behavior in the Mist environment. Juniper documentation explains that users with organization-wide privileges can view analytics across the organization, while site-restricted roles are limited to their permitted sites. Those restrictions can apply not only to what a user sees on a dashboard, but also to data downloads and scheduled reports.

That distinction matters when the analytics audience expands beyond the network team. A facilities manager may need occupancy information for selected sites but not organization-wide network visibility. A regional IT team may need its own sites without access to another country or business unit. A helpdesk role may need enough information to identify recurring issues but not broader governance data. The subscription should therefore be paired with an access design that reflects job responsibilities.

Organizations should avoid solving access problems by exporting large reports and distributing them informally. Scheduled delivery is convenient, but a report sent by email can move data outside the controls of the analytics portal. The access review should cover both interactive dashboard permissions and the downstream handling of exported or scheduled material.

For a new deployment, create a small role matrix before activation. List the user groups, the sites they need, the dashboards they need, whether they can download data, and whether they can schedule deliveries. This exercise frequently reveals that licensing is only one part of the rollout; operational ownership and information governance are equally important.

Licensing and activation considerations

Premium Analytics is a licensed service rather than a feature that appears automatically for every Juniper Mist organization. Juniper instructs customers to obtain a subscription through their account team or partner and activate it for the relevant Mist organization. Trial access is also documented through the Juniper Mist support process, with organization information and requested reports used as part of the request.

A buyer should not assume that one generic license description answers all commercial questions. Subscription terms, entitlement scope, renewal timing and any dependencies should be confirmed on the quotation. The organization should also decide whether the service is being introduced for a short evaluation, a specific project, or as a continuing part of network operations. Those scenarios lead to different success criteria.

For a proof of value, define a small set of reports and a representative group of sites. If the objective is historical trend analysis, remember that a newly activated service may not instantly provide a complete year of historical context for every desired data source. Confirm what historical data is available, when collection begins for the required data set, and when enough history will exist to judge the use case.

For production adoption, align subscription renewal with the business process that depends on the analytics. If a quarterly capacity review or annual planning cycle uses Premium Analytics, the renewal owner should understand the operational consequence of losing access. Subscription lifecycle management belongs in the same service inventory as the underlying Mist cloud subscriptions.

Important dependency: Premium Analytics is not a stand-alone monitoring appliance

There is no physical Premium Analytics box to install in a rack. It is a cloud subscription that derives value from the network, location and business data available to the Juniper Mist environment. A quotation should therefore be checked against the existing architecture. If the organization expects a wireless dashboard, confirm the relevant wireless service and devices are present. If it expects wired analytics, confirm the switch telemetry and assurance architecture. If WAN reporting is required, confirm the WAN data source and supported service. If location or engagement analytics are expected, validate the location-service prerequisites.

This dependency is also why two businesses can purchase the same Premium Analytics subscription and obtain very different practical value. The organization with clean site structure, consistent naming, appropriate assurance subscriptions, complete telemetry and defined reports will usually obtain more useful analytics than an organization with fragmented data and no reporting process.

Sizing the requirement before requesting a Dubai quotation

Analytics subscriptions are easier to quote accurately when the buyer describes the environment in operational terms. Start with the Juniper Mist organization and the sites that matter. Record whether the project covers one Dubai office, multiple UAE branches, a regional network or a global organization managed from the UAE. The geographic label affects operational ownership, but the technical scope is determined by the sites, services, devices and data sets that must be analyzed.

Next define the network domains. Does the requirement cover wireless only, or wired and wireless? Is WAN experience part of the reporting objective? Are security trend reports required? Is location or engagement insight required? Are there non-Mist devices or external business data sources that must be included? Each answer changes the validation work needed before purchase.

Then define the audience. Count the teams that will use the analytics and identify their access boundaries. A central network engineering team, regional operations group, helpdesk and facilities team may all need different views. User count alone is not the only question; role design and site access matter because the wrong permission model can expose irrelevant or sensitive information.

Finally define the reporting outcome. List the dashboards or recurring questions that justify Premium Analytics. Examples include monthly wireless service review, WAN quality trend analysis, application growth reporting, switch utilization review, audit history, inventory planning, occupancy analysis or visitor engagement studies. For each report, identify frequency, owner, audience and decision. This turns the conversation from “we need analytics” into a scope that can be verified.

FourTeck can use this information to prepare a more precise quotation discussion and identify gaps that should be clarified with Juniper before the subscription is ordered.

Buyer-fit matrix

Wireless analytics: decisions beyond a live dashboard

Wireless teams often begin with operational questions: why did a client fail to connect, why is an application slow, or why did a service-level metric degrade? Juniper Mist assurance tools are designed to help with those immediate questions. Premium Analytics adds value when the team needs to understand the pattern around the problem. A recurring degradation across the same floor, time period, SSID or client category is a different planning problem from a single incident.

Long-term wireless analysis can support capacity planning by showing trends in connected clients, traffic, applications and service levels. It can help a business distinguish organic growth from a temporary peak. It can also support comparison between sites. If one branch consistently has a different client mix or service profile from similar branches, the data can direct an engineering review toward RF design, local demand, cabling, switching, WAN connectivity or policy.

Premium reporting can also expose device operating-system and manufacturer trends in supported reports. These insights may help identify changes in the endpoint population that affect support planning. A rise in a particular device class does not by itself prove a network issue, but it can provide context when performance changes coincide with an endpoint rollout.

Wireless security analytics can add longer context around supported rogue or RF threat information. This is useful for trend analysis, but should not be confused with a complete security operations platform. The security team should define which wireless findings will be monitored in Premium Analytics and how they integrate with the broader incident, logging and threat-management process.

For Dubai offices, hospitality venues, schools, healthcare environments, retail properties and campuses with substantial Wi-Fi dependence, the strongest business case is usually not “more graphs.” It is the ability to connect long-term service behavior to expansion, workspace usage, application demand and recurring operational events.

Wired analytics: port, client and infrastructure planning

Switching infrastructure is frequently reviewed reactively. A port fails, a powered device loses service, a VLAN is missing, or an uplink reaches an uncomfortable utilization level. Those incidents deserve immediate troubleshooting, but they do not always reveal whether a broader design issue exists. Historical analytics can help identify repeated conditions and compare infrastructure behavior across sites.

A network team can use longer-term wired reports to examine usage and performance trends at the switch or interface level where the relevant data is available. This can support questions such as whether access-switch density is appropriate, whether uplink demand is changing, whether certain sites exhibit unusual traffic patterns, or whether power-delivery observations correlate with endpoint growth.

The interpretation should remain engineering-led. A high-utilization port may be normal for a backup system. A low-utilization link may still be critical for resilience. A PoE pattern can be affected by endpoint schedules. Analytics provides evidence, but topology, business criticality and design intent determine the action.

Mixed-vendor environments require additional validation. Juniper documentation describes Premium Analytics ingestion and reporting from Juniper and third-party network devices not managed by the Mist cloud for applicable use cases. That does not mean feature parity with natively managed devices. Confirm exactly what data can be ingested from each required platform and whether it is sufficient for the intended report.

For procurement, describe the existing switch estate by vendor and management model rather than merely stating the number of switches. A native Mist-managed Juniper deployment and a heterogeneous legacy environment may have the same device count but very different integration requirements.

WAN analytics and application quality

WAN complaints are often difficult because users describe application symptoms rather than network metrics. “The ERP system was slow” or “video quality dropped” can be caused by link congestion, loss, routing, application behavior, endpoint conditions, security processing or a service outside the enterprise network. Historical WAN quality data gives the network team a stronger basis for correlation.

Juniper lists link and application quality-of-experience visibility among Premium Analytics capabilities. Over time, these data sets can help teams compare sites, circuits, applications and recurring periods. That can support carrier discussions, SD-WAN policy review, bandwidth planning and post-change validation. A business that is considering a circuit upgrade should ideally establish whether the demand pattern is sustained and whether quality problems coincide with utilization or another factor.

Historical data is also useful after a network change. If a branch receives a new circuit, policy or WAN edge design, the team can compare the service pattern before and after the change. The comparison should use equivalent periods where possible. Comparing a quiet holiday week with a peak operating week may produce a misleading conclusion even if the dashboard is accurate.

For multinational organizations managed from Dubai, regional variation matters. Different branches may have different carriers, latency to applications, local internet breakout, business hours and traffic mixes. The analytics design should preserve those site differences rather than reducing every location to one organization-wide average.

A Premium Analytics purchase is therefore most valuable when WAN reporting is connected to a decision process: carrier review, capacity planning, policy optimization, application migration, branch redesign or service-level governance.

Location, occupancy and engagement analytics

Juniper Mist analytics can extend beyond traditional network operations. Where the correct location services and data are deployed, Premium Analytics can support analysis of visits, dwell time, movement between zones, occupancy and related engagement patterns. These capabilities can be valuable because network infrastructure is present throughout physical spaces and can provide a consistent data foundation for operational planning.

In a retail environment, the question might be whether particular zones receive sustained traffic or whether visitor behavior changes during campaigns. In hospitality, teams may examine common-area usage and service demand. In an office, occupancy patterns can support discussions about workspace utilization. In education, long-term movement or occupancy information may support facilities planning. In healthcare, any use should be carefully aligned with privacy, security and operational policy.

These analytics require cautious interpretation. A device observation is not always equivalent to a unique person. Modern endpoint privacy behavior, multiple devices per person, disabled radios and coverage differences can affect counts and patterns. A good deployment defines the metric precisely and treats it as a decision signal rather than an unquestionable census.

Privacy governance is equally important. Before location-related analytics are used for employee, visitor or customer analysis, the organization should involve the appropriate privacy, legal and information-security stakeholders. Define the legitimate purpose, data access, retention, reporting audience and any notice or consent obligations that may apply.

The technology is strongest when the business asks a measurable question and understands the limits of the data. It is weakest when broad claims such as “track everyone everywhere” replace a well-defined analytics objective.

Operational governance: turning reports into repeatable action

An analytics platform can create excellent dashboards and still fail to improve the network if nobody owns the result. Before activating Premium Analytics, assign an owner to each major report family. Network operations may own wireless and wired service reports; WAN engineering may own application-quality analysis; security may own relevant threat trends; facilities or business operations may own approved location use cases.

Define a review cadence that matches the decision. Real-time incident response belongs in operational tools and assurance workflows. Premium historical analysis is better suited to weekly service reviews, monthly trend discussions, quarterly planning and post-change comparisons. A report that is reviewed too frequently may create noise; one reviewed too rarely may miss the opportunity to act before a capacity problem becomes urgent.

Decide what constitutes an actionable finding. A trend report should not merely be “interesting.” If client growth passes an agreed planning level, begin a capacity review. If a site repeatedly underperforms its peers, open an engineering investigation. If application-quality degradation recurs during the same business process, correlate it with WAN and application teams. If occupancy data shows a sustained shift in space usage, route it to the facilities process.

Keep a record of actions taken because of the analytics. This provides an internal measure of value. If the organization cannot identify decisions influenced by the service after several review cycles, the issue may be adoption, report design or an unclear business case rather than the technical platform.

This governance discipline is especially useful during renewal. Instead of asking whether users liked the dashboards, the organization can ask which operational or planning decisions were improved by the historical data.

Security, privacy and data-handling questions

Because Premium Analytics aggregates operational and potentially location-related data, it should be included in the organization’s normal cloud-service security review. The review should cover administrator access, role assignment, authentication, scheduled report recipients, exported files, data-retention expectations and the sensitivity of each data source. If third-party data is ingested, include that flow in the review.

Role-based access reduces unnecessary visibility when it is configured correctly, but organizations should periodically review roles. People change jobs, sites are reorganized and temporary project access can become permanent by accident. Treat analytics privileges as part of the same joiner, mover and leaver process used for other management systems.

Scheduled reports deserve special attention because they can leave the portal. A PDF or CSV sent to a distribution list may be retained in mailboxes, forwarded or copied into other systems. Define whether the information is operational, confidential, personally relevant or subject to retention rules before enabling broad distribution.

For location and engagement analytics, privacy analysis should begin before deployment rather than after reports are created. Determine the intended purpose, the minimum data required, who needs access and how long information should remain available. Technical possibility should not be treated as automatic permission to use every available data point.

Buyers with formal regulatory or residency requirements should request the current Juniper service documentation and contractual information that applies to their tenant and region. Product marketing summaries are not a substitute for a legal or compliance assessment.

Typical Dubai and UAE use cases

When Premium Analytics may not be the first purchase

Premium Analytics is not automatically the right first step for every Juniper Mist customer. If the immediate problem is that the network lacks appropriate assurance subscriptions, devices are not managed consistently, site data is incomplete or the team has not defined its operational dashboards, those foundations may deserve attention first. More historical data will not correct missing telemetry or an unclear management model.

A small environment with straightforward needs may find that the standard analytics included with its existing Mist services are sufficient. If the team rarely needs to look beyond the standard retention window and does not require advanced trend, custom or scheduled reporting, the premium subscription may add limited practical value. That conclusion should be based on real reporting requirements rather than the size of the company alone.

Similarly, an organization seeking a dedicated security information and event management platform, a long-term legal archive, a generic business-intelligence warehouse or universal cross-vendor observability should not assume Premium Analytics is a direct substitute. It is optimized around Juniper Mist and supported network/location analytics use cases. Other platforms may still be required for broader enterprise data or security functions.

The best evaluation question is simple: which recurring decisions are currently difficult because the organization lacks enough history, correlation or report flexibility? If the answer maps closely to supported Juniper Mist analytics domains, Premium Analytics deserves serious consideration. If the answer belongs mainly to another discipline, evaluate the appropriate platform rather than forcing the requirement into a network analytics service.

Comparison with nearby Juniper Mist capabilities

Juniper Mist is a portfolio of cloud services rather than one monolithic license. This matters because buyers sometimes compare services that actually solve different layers of the problem. Wi-Fi Assurance focuses on wireless service experience and operations. Wired Assurance focuses on campus switching experience and visibility. WAN Assurance addresses WAN experience. Marvis provides AI-driven operational assistance. Location services support location-related use cases. Premium Analytics sits across these sources to provide deeper, longer-term analysis and business insight where the required data is available.

Premium Analytics therefore complements rather than replaces the assurance services. If the business wants better day-to-day wireless troubleshooting, the core wireless assurance architecture is fundamental. If it wants a year-scale view of wireless service and client trends for planning, Premium Analytics becomes more relevant. If it wants natural-language or AI-assisted operational investigation, Marvis addresses a different requirement. If it wants visitor movement analysis, the relevant location capability must also be considered.

This portfolio view prevents a common procurement error: buying an analytics subscription while expecting it to create data that the organization is not collecting. The requirements workshop should map each desired outcome to the service that produces or analyzes the necessary information.

For an existing Juniper Mist customer, the first step is usually an entitlement and architecture review. Identify which Mist services are active, which device domains are managed, what standard analytics already provide, and which unanswered questions justify the premium layer.

A practical deployment journey

Migration and rollout considerations

Introducing Premium Analytics does not normally require the kind of cutover associated with replacing a firewall, switching core or wireless controller. The service is cloud-based, and activation occurs in relation to the Juniper Mist organization. Even so, a structured rollout is useful because the real migration is from ad hoc reporting to a standardized analytics process.

If teams currently export data manually into spreadsheets or business-intelligence tools, document those reports before changing the process. Identify which fields, time periods and calculations are essential. Premium Analytics may replace some manual work, but it may not reproduce every custom report exactly. Preserve the business requirement rather than the historical format.

Where external data sources are involved, test them separately. Validate that timestamps, site identifiers, device names and business labels align sufficiently for meaningful correlation. A dashboard can technically combine two data sets while still producing confusing results if one system calls a site “DXB-HQ” and another calls it “Dubai Main Office,” or if time zones differ.

During the first review cycle, compare Premium Analytics outputs with trusted operational references. This is not because the service should be presumed inaccurate; it is a normal implementation practice that helps teams understand metric definitions and avoid misinterpreting unfamiliar visualizations.

A successful rollout finishes with documented report owners, role assignments, subscription contacts, renewal information and a short list of decisions the analytics are expected to support. That documentation is more valuable than a large collection of screenshots.

Procurement questions that improve quotation accuracy

A Juniper Premium Analytics Dubai request becomes much easier to quote when the buyer supplies the Mist organization context and desired subscription outcome. Start with the current Juniper environment: which Mist cloud services are already licensed, which device families are managed, how many sites are in scope and whether the requirement is limited to the UAE or extends to a wider organization.

State the reason for purchasing Premium Analytics. “We need thirteen months of wireless and WAN trend reporting for quarterly planning” is much more actionable than “we need Premium Analytics.” If location analytics are required, state the location use case. If external data must be ingested, identify the exact source and desired correlation. If scheduled reporting is important, list the recipients and cadence.

Include the intended subscription term and any internal renewal date constraints. If the project is part of a larger Juniper deployment, mention the rollout schedule so analytics activation can be coordinated with the availability of source data. If the organization is evaluating the service before a larger commitment, define what a successful evaluation must prove.

For commercial comparison, make sure competing quotations represent the same scope. A lower price may reflect a different term, quantity, entitlement, support arrangement or missing prerequisite. Cloud-subscription comparisons should be normalized before a buying decision is made.

FourTeck can work from these inputs to structure the product request and clarify open licensing questions with the relevant channel before the order is finalized.

Technical and commercial checklist

Frequently asked buyer questions

Decision recap for Juniper Premium Analytics Dubai

What FourTeck needs from the buyer

For an accurate Juniper Premium Analytics quotation or consultation, send the practical details below. Exact answers are preferable, but estimates can be used as a starting point when the environment is still being assessed.

• Juniper Mist organization and administration region
• Number and names of sites in scope
• Current Wi-Fi Assurance, Wired Assurance, WAN Assurance and location subscriptions
• Wireless, wired, WAN, security, audit, inventory or location reports required
• Historical period needed for decision-making
• Third-party device or business data sources to be integrated
• User groups and site-access boundaries
• Scheduled report recipients and frequency
• Required subscription term and renewal target
• Any evaluation, migration, deployment or support requirement

Scope Juniper Premium Analytics around the decisions you need to make

Premium Analytics is most useful when the subscription is tied to a clear historical, operational or business-analysis requirement. Share your existing Mist environment, sites, required dashboards, data sources and subscription term so the licensing scope can be checked before purchase.