IT for Alberta's Oil & Gas Industry: Cybersecurity, OT/IT Convergence, and Field Connectivity in 2026

Alberta's oil and gas sector is in active expansion. The Canadian Association of Energy Contractors projects 5,709 wells to be drilled in 2026 a three percent increase over 2025 supporting approximately 85,000 direct and indirect jobs across the province. New pipeline infrastructure, LNG export capacity milestones, and the federal government's designation of energy projects as matters of national interest are driving investment across the upstream, midstream, and oilfield services segments.

Behind every active well site, pipeline operation, and energy services company is a technology infrastructure that determines whether operations run smoothly or grind to a halt. And in 2026, that technology infrastructure faces a threat landscape that is materially different from even three years ago.

The convergence of operational technology (OT) and information technology (IT) the connecting of formerly isolated industrial control systems to corporate networks and the internet has created attack surfaces that the energy sector has never previously had to defend. The Canadian Centre for Cyber Security explicitly identifies the energy sector as a high-value target for state-sponsored threat actors and ransomware groups. And the consequences of an IT or OT security failure in oil and gas are not just financial they extend to operational safety, environmental liability, and regulatory standing.

This guide is written specifically for Alberta's oil and gas SMBs: the independent operators, oilfield services companies, engineering consultancies, and midstream operators that form the backbone of the province's energy sector. It covers the specific IT challenges this sector faces, the security architecture required to address them, and how a managed IT provider with energy sector experience can help you operate with confidence.

The Unique IT Landscape of Alberta's Oil & Gas Sector

Two Worlds That Were Never Meant to Be Connected: OT and IT

For decades, the technology that runs a wellsite, a pipeline, or a processing facility operational technology (OT) was physically isolated from the corporate IT environment. SCADA (Supervisory Control and Data Acquisition) systems, programmable logic controllers (PLCs), distributed control systems (DCS), and industrial sensors operated on proprietary protocols and dedicated networks, deliberately air-gapped from the internet.

The business case for OT/IT convergence is compelling: real-time production data flowing into corporate ERP systems, predictive maintenance analytics reducing costly unplanned downtime, remote monitoring eliminating the need for on-site personnel at unmanned facilities, and cloud-based operations platforms giving management visibility across distributed assets.

The security consequence is severe: every connection between OT and IT systems every data pipeline, every remote access capability, every cloud integration is a potential attack path from the corporate IT environment into systems that control physical infrastructure. A ransomware attack that reaches an OT environment is not just a data loss event. It can trigger operational shutdowns, environmental incidents, and safety emergencies.

The Attack Surface Specific to Energy SMBs

Alberta's oil and gas SMBs face a combination of attack surface exposures that are unusual compared to other industries:

• Remote and unmanned facilities: Well sites, compressor stations, and pipeline monitoring points operated remotely connected by cellular or satellite networks create exposure points that are difficult to physically secure and monitor
• Third-party and contractor access: Oilfield services companies, engineering contractors, and equipment vendors routinely require access to client systems and networks each representing a potential supply chain compromise vector
• Legacy OT systems: Industrial control systems often have operational lifespans of 15 to 25 years. Many systems in active operation predate modern cybersecurity awareness and cannot run endpoint security software or receive security patches
• Field device proliferation: IoT sensors, SCADA RTUs, and connected field equipment have multiplied the number of network-connected devices most of which were not designed with security in mind
• IT/OT integration points: Data historians, remote access platforms (often using standard RDP or VPN), and cloud data lakes that aggregate field data are the seams where OT and IT environments touch and where attackers focus
• Level 0 (Field): Sensors, actuators, and physical devices direct measurement and control of the physical process
• Level 1 (Control): PLCs, RTUs, and control devices that execute field device instructions
• Level 2 (Supervisory): SCADA systems and DCS that monitor and manage Level 1 systems
• Level 3 (Operations): Manufacturing execution systems and data historians that aggregate operational data
• Level 4/5 (Enterprise/External): Corporate IT systems and internet-facing services
• Asset inventory: You cannot secure what you don't know exists. A complete inventory of OT assets including legacy systems, embedded controllers, and field devices is the foundation. Many energy SMBs have significant undocumented OT infrastructure.
• Vulnerability management for OT: Standard patch management tools are often incompatible with OT systems. Patching cycles are longer, vendor validation is required, and some systems cannot be patched at all. Compensating controls network isolation, monitoring, application whitelisting must substitute for patch-based vulnerability management.
• OT-specific monitoring: Standard SIEM and EDR tools do not understand industrial protocols (Modbus, DNP3, OPC-UA, EtherNet/IP). OT-specific monitoring tools like Claroty, Dragos, or Nozomi Networks passively monitor industrial traffic for anomalies without disrupting production systems.
• Incident response for OT: A ransomware response plan for an energy company must account for OT environment scenarios including the decision framework for whether to shut down production systems proactively versus attempting to contain the IT-side incident while maintaining production. This decision should be made in advance, not during a crisis.
• Endpoint detection and response (EDR): Deploy EDR on all Windows and macOS endpoints office and field. EDR's behavioural monitoring detects lateral movement and ransomware deployment activity before it reaches the encryption stage.
• Mobile device management (MDM): Field tablets and smartphones should be enrolled in MDM to enforce encryption, remote wipe capability, and application controls.
• Patch management: Office endpoints should be patched monthly at minimum. Field devices that return to office networks should be patched and scanned before reconnecting.
• Removable media controls: USB drives used extensively in field environments to transfer data and firmware are a common malware vector. USB access should be restricted to approved devices only, with logging.
• LTE/5G cellular: The primary connectivity choice for most Alberta field sites within cellular coverage. Modern LTE and 5G networks provide sufficient bandwidth for SCADA data, remote monitoring, and business communications. Dual-carrier configurations using two different carriers on failover provide resilience against single-carrier outages.
• Satellite: Required for sites beyond cellular coverage remote wilderness locations, northern Alberta, offshore or near-offshore applications. Low Earth Orbit (LEO) satellite services have dramatically improved latency and bandwidth for remote industrial applications. Latency-sensitive SCADA protocols may require protocol optimization in satellite environments.
• Private LTE/CBRS: Larger operators and multi-well pad developments increasingly deploy private LTE networks using licensed spectrum providing carrier-independent, high-performance connectivity across a defined geographic area with greater security and reliability than shared public networks.
• Microwave/point-to-point radio: For sites with line-of-sight to a repeater or hub location, licensed or unlicensed microwave links provide high-bandwidth, low-latency connectivity at lower recurring cost than cellular.
• SCADA and historian platforms: Inductive Automation Ignition, OSIsoft PI (now AVEVA PI), Wonderware, and Yokogawa CENTUM are common in Alberta. Data historian integration with corporate reporting requires careful OT/IT boundary management.
• Production accounting: Quorum Business Solutions, P2 Energy Solutions, and Enertia Software are purpose-built for Canadian energy production accounting with integration requirements to corporate ERP and regulatory reporting systems.
• Field data capture and mobile: Mobile applications for field data collection, daily production reporting, and inspection workflows typically running on Android or iOS tablets with MDM enrollment and offline capability for low-connectivity environments.
• Drilling and completions management: Directional drilling software, wellbore planning platforms, and completions management tools used by drilling programs and oilfield services contractors.
• ERP: SAP, Microsoft Dynamics 365, and Oracle NetSuite are common among larger SMBs and mid-market operators. Integration between ERP and production systems is a common IT challenge.
• Project management: Oil and gas construction projects pipeline segments, facility expansions, well programs require robust project management platforms. Microsoft Project, Procore (common in construction-adjacent projects), and industry-specific tools.
• Document management and regulatory filing: Alberta Energy Regulator (AER) submissions, Environmental Protection and Enhancement Act (EPEA) compliance documentation, and National Energy Board filings require document management systems with version control and audit trail capability.
• HSE (Health, Safety, and Environment) platforms: Safety observation reporting, incident management, competency management, and permit-to-work systems often cloud-based with mobile field access requirements.
• Alberta Energy Regulator (AER): Electronic submission of production data, well reports, and environmental compliance documentation. AER's Digital Data Submission platform requires specific software and connectivity standards.
• Canada Energy Regulator (CER): Federal oversight for interprovincial pipelines and major energy facilities with its own electronic filing and incident reporting requirements.
• EPEA compliance: Environmental Protection and Enhancement Act documentation requires traceable records of monitoring data, emissions reporting, and incident response with specific retention and accessibility requirements.
• TSB reporting: Transportation Safety Board requirements for incident reporting from pipeline operators with mandatory notification timelines.
• Production shutdown decision: At what point in a cyberattack does the organization proactively shut down production systems to prevent OT compromise? Who makes that decision, and based on what criteria? This decision has material financial consequences and cannot be made well under crisis conditions without prior planning.
• Safety system integrity: If a cyberattack potentially affects safety systems emergency shutdown systems, fire and gas detection, pressure relief controls regulatory and safety obligations may require specific notification and response actions.
• AER incident reporting: The Alberta Energy Regulator requires notification of cybersecurity incidents that affect operations. The timeline and content of required notifications should be documented in your incident response plan.
• Environmental incident protocols: A cyberattack that causes loss of operational control affecting pump systems, valve controls, or monitoring systems could trigger environmental incident obligations under EPEA.
• Insurance and liability considerations: Energy sector cyber insurance policies typically include specific requirements for incident documentation, notification timelines, and evidence preservation that differ from general commercial cyber policies.
• Scenario 1 — Ransomware in the corporate IT environment: Billing, email, and ERP systems encrypted. Production systems unaffected but connectivity to corporate network disrupted. Decision: maintain production while isolating corporate environment, or shut down OT connections proactively?
• Scenario 2 — SCADA workstation compromise: A field SCADA workstation displays signs of compromise. Unknown whether the attacker has lateral access to control systems. Decision: isolate the workstation and accept loss of remote monitoring visibility, or maintain connectivity while investigating?
• Scenario 3 — Vendor supply chain compromise: A firmware update from a trusted OT vendor is discovered to contain malicious code. The update has already been deployed to multiple field sites. Decision: shut down affected field systems for remediation, or implement compensating controls while maintaining operations?
• Scenario 4 — Field connectivity failure: Primary and backup connectivity to multiple well sites fails simultaneously. SCADA data is unavailable. Physical dispatch is required. Decision: what is the emergency response procedure for extended loss of remote monitoring?
• Calgary and Edmonton presence: Our Calgary and Edmonton offices serve Alberta's energy corridor directly. We provide on-site support across the province not remote-only service from a distant city.
• In business since 2012: Over 13 years of IT experience includes supporting organizations with distributed field operations, industrial technology environments, and complex multi-site architectures.
• SOC2 certified: Our operational controls are independently audited a relevant credential for energy companies with regulatory compliance requirements and supply chain security obligations.
• B-Corp certified: Our commitment to operational integrity extends to the clients we serve. In an industry where operational credibility matters, working with a certified responsible business reflects on your own standards.
• 24/7 internal staff, never outsourced: Our monitoring and support team operates around the clock with our own engineers not a third-party NOC. For field operations that run 24/7, your IT support does too.
• 5-minute response guarantee: In an industry where production downtime is measured in thousands of dollars per hour, a five-minute escalation response is not a minor differentiator. It is the difference between a contained incident and an extended outage.
• Security-first architecture: GAM Tech's managed services platform includes EDR, 24/7 security monitoring, immutable backup, and network segmentation guidance as standard components. Energy sector clients get a security architecture appropriate to their risk profile.
• Project packs included: OT network assessments, SD-WAN deployments, and field connectivity projects are project-based work. GAM Tech's managed services contracts include project packs so this work proceeds without separate budget negotiations.
• National coverage with local presence: Calgary, Edmonton, Red Deer, Vancouver, Victoria, Toronto, Ottawa, and Montréal. For energy companies with multi-province operations pipeline operators, exploration companies active in BC and Saskatchewan we provide consistent service across jurisdictions.
  
  

Why Energy Companies Are Attractive Ransomware Targets

The energy sector's attractiveness as a ransomware target comes down to two factors: operational criticality and payment capacity. Production shutdowns are enormously costly an unplanned operational disruption at a mid-sized Alberta producer can cost tens of thousands of dollars per hour. Ransomware groups understand this math and set their demands accordingly.

The 2025 attack on a major North American pipeline operator demonstrated the cascading consequences of a ransomware attack that notably did not even reach the OT environment. The operator shut down pipeline operations proactively out of concern that the ransomware could spread. The business interruption cost, fuel supply disruption, and regulatory consequences ran into hundreds of millions of dollars.

For Alberta's smaller producers and oilfield services companies, the scale is different but the dynamic is the same. An operator managing 50 wells cannot afford to be offline during peak production. An oilfield services company that loses access to its scheduling, dispatch, and billing systems loses revenue every hour the incident persists.

Cybersecurity Architecture for Alberta Energy SMBs

OT Network Segmentation: The Foundation of Industrial Cybersecurity

The starting point for any energy sector cybersecurity program is network segmentation establishing defensible boundaries between the OT environment, the corporate IT environment, and external networks.

The Purdue Model (ISA/IEC 62443 standard) provides the foundational architecture:

Proper segmentation means that traffic between levels is tightly controlled by industrial firewalls or data diodes and that direct connectivity between the corporate network and Levels 0–2 is eliminated. An attacker who compromises the corporate IT environment should encounter a true security boundary before reaching control systems.

In practice, many Alberta energy SMBs have informal or nonexistent OT/IT segmentation the SCADA workstation is on the same network segment as the office computers, connected to the same switch, with the same internet access. This is not an acceptable security posture in 2026.

Securing Remote Access in Field Environments

Remote access to field systems is operationally essential for most Alberta energy operators. SCADA operators need to monitor and control remote facilities. Maintenance engineers need diagnostic access to PLCs and control systems. Corporate management needs production data. This access creates risk.

Minimum requirements for secure remote access in an energy environment:

1. Multi-factor authentication on all remote access: No single-factor (password-only) access to any system connected to OT networks. This applies to VPN concentrators, remote desktop gateways, and SCADA web interfaces.
2. Privileged access management: Access to OT systems should be role-based, time-limited, and logged. Vendor and contractor access should be provisioned only for the duration of specific work and revoked immediately upon completion.
3. Encrypted communications: All remote access traffic should be encrypted in transit. Unencrypted protocols (Telnet, FTP, HTTP) should be disabled on any system accessible from outside the immediate network segment.
4. Dedicated jump servers: Remote access to OT systems should route through a dedicated jump server or bastion host in the DMZ never directly from the internet to OT network systems.
5. Continuous session monitoring: Remote access sessions to OT systems should be logged and monitored. Anomalous access patterns off-hours access, access from unexpected geographies, unusual commands should trigger alerts.
   
   

SCADA and Industrial Control System Security

Securing SCADA and ICS environments requires different tools and approaches than securing standard IT environments:

Endpoint Security for Field and Office Environments

An Alberta oil and gas company's endpoint environment spans office workstations, field laptops for engineers and technicians, tablets used for field data collection, and potentially rugged computing devices at wellsites and compressor stations.

Core endpoint security requirements:

Field Connectivity: Keeping Remote Sites Online

The Connectivity Challenge Unique to Oil and Gas

No other industry in Alberta presents the combination of geographic distribution, remote location, and operational criticality that characterizes oil and gas. A producer managing wells scattered across the foothills, the Peace River region, and the oil sands faces connectivity challenges that have no direct equivalent in urban professional services.

Field connectivity for oil and gas SMBs needs to solve three distinct problems: reliable data transmission from remote field sensors and SCADA RTUs, secure remote access for monitoring and control, and business communications (email, VoIP, video, file access) for field staff at well pads and drilling camps.

Connectivity Options for Remote Sites

The right connectivity solution depends on site location, data volume requirements, latency sensitivity, and available infrastructure:

Software-Defined WAN (SD-WAN) for Multi-Site Operations

Alberta energy operators managing multiple field sites, regional offices, and a corporate head office in Calgary or Edmonton benefit significantly from SD-WAN architecture. SD-WAN aggregates multiple connectivity types (cellular, satellite, broadband) into a unified, centrally managed network with automatic failover, traffic prioritization, and centralized security policy enforcement.

For an oilfield services company with a Calgary office, an Edmonton yard, and active job sites across central Alberta, SD-WAN means consistent security policy across all locations, centralized visibility into network performance, and automatic failover when a field site's primary connection goes down without requiring an IT technician to drive to the site.

Network Monitoring for Distributed Environments

Field connectivity issues often manifest as subtle performance degradations before they become outages. A SCADA system that is intermittently dropping data points, a VPN that is experiencing packet loss, or a cellular connection that is routing through an unexpected path these are early warning signs that a trained monitoring system catches and a reactive IT model misses entirely.

GAM Tech's 24/7 monitoring platform includes network performance monitoring for all managed endpoints and connectivity links alerting our team to anomalies before they affect operations, and providing historical performance data to support capacity planning and troubleshooting.

IT Applications for Oil & Gas Operations

The Technology Stack of an Alberta Energy SMB

While every organization's stack is unique, Alberta's oil and gas SMBs typically operate some combination of the following systems each of which has specific IT support, integration, and security requirements:

Production and Operations Software

Business and Corporate Systems

Regulatory IT Requirements for Alberta Energy Companies

Alberta energy operators operate under a layered regulatory framework with specific technology and data management implications:

IT infrastructure that supports regulatory compliance must include: reliable access to regulatory submission platforms, document management with appropriate retention and audit trail capability, and backup systems that ensure compliance records are recoverable in the event of a system failure.

Incident Response Planning for Energy Sector Operations

Why Energy Companies Need a Sector-Specific Response Plan

A generic IT incident response plan is inadequate for an oil and gas operation. The energy sector introduces unique considerations that must be pre-planned:

Tabletop Exercise Scenarios for Energy Companies

Effective incident response planning for oil and gas SMBs requires scenario-specific tabletop exercises:

GAM Tech Differentiators: Managed IT for Alberta's Energy Sector

Alberta's oil and gas industry requires a managed IT partner with specific capability not a generalist provider who has never seen a SCADA system or supported a distributed field operation. Here is what GAM Tech brings to energy sector clients:

Frequently Asked Questions: IT for Alberta's Oil & Gas Industry

What is OT/IT convergence and why does it matter for Alberta energy companies?

OT/IT convergence is the integration of operational technology (industrial control systems, SCADA, PLCs) with information technology (corporate networks, cloud platforms, ERP systems). Historically isolated, OT systems are increasingly connected to corporate IT environments and the internet to enable remote monitoring, predictive analytics, and operational efficiency. This connectivity creates cybersecurity risks that did not previously exist attack paths from corporate IT networks into industrial control systems that directly manage physical infrastructure. For Alberta energy companies, a successful attack on OT systems can mean production shutdowns, environmental incidents, and safety emergencies with consequences far beyond a typical IT breach.

How should an Alberta oil and gas company segment its OT and IT networks?

The ISA/IEC 62443 standard and the Purdue Model provide the foundational architecture for OT/IT segmentation. The core principle is that industrial control systems (PLCs, RTUs, SCADA systems) should be isolated from corporate IT and internet-facing systems by industrial firewalls or data diodes that enforce strict traffic controls between levels. In practice, this means eliminating direct connectivity between office workstations and control system networks, routing all remote access through dedicated jump servers in a secured DMZ, and monitoring traffic at OT/IT boundary points. Many Alberta energy SMBs have informal or nonexistent segmentation this is the highest-priority security gap to address.

What connectivity options are available for remote Alberta well sites and field facilities?

The primary options are LTE/5G cellular (best coverage across most of Alberta's producing regions), satellite (necessary for northern and remote locations beyond cellular coverage), private LTE networks (for larger multi-well pad developments or high-security requirements), and licensed microwave links (for fixed sites with line-of-sight opportunities). Most Alberta field sites use LTE with a backup cellular connection on a second carrier for resilience. SD-WAN platforms aggregate multiple connection types and provide automatic failover, centralized management, and consistent security policy across distributed field and office locations.

What are the specific cybersecurity threats facing Alberta's oil and gas sector?

Alberta energy companies face threats from multiple directions: ransomware groups that target energy sector organizations for their high payment capacity and operational sensitivity; state-sponsored threat actors targeting Canadian energy infrastructure for intelligence and disruption; supply chain attacks through the extensive third-party vendor and contractor ecosystem common in oilfield services; and opportunistic attacks exploiting unpatched vulnerabilities in internet-exposed OT systems and VPN appliances. The Canadian Centre for Cyber Security identifies the energy sector as a priority target in its National Cyber Threat Assessment not as a theoretical risk but as an active one.

Does GAM Tech support SCADA and industrial control system environments?

GAM Tech provides managed IT services for the corporate IT environment, field connectivity, endpoint security, and cloud systems of Alberta energy companies including assessments and security architecture guidance for OT/IT boundary management. For deep industrial control system security (SCADA-specific monitoring, ICS penetration testing, PLC security), we work with specialized OT security partners. Our role is to ensure the IT environment surrounding the OT infrastructure is secured, monitored, and properly segmented which is the most common source of OT compromise. Contact us to discuss your specific environment.

What regulatory IT requirements apply to Alberta energy companies?

Alberta energy operators face IT-relevant obligations from the Alberta Energy Regulator (AER) for electronic production and compliance reporting, the Canada Energy Regulator (CER) for interprovincial pipeline operations, the Environmental Protection and Enhancement Act (EPEA) for environmental monitoring and incident documentation, and federal privacy law (PIPEDA) for any personal information handled. Bill C-8 proceeding through Parliament in 2026 as successor to Bill C-26 will introduce mandatory cybersecurity program and incident reporting requirements for designated operators in the energy sector when enacted. Your IT infrastructure and backup systems must support the specific data retention and accessibility requirements of each applicable framework.

How should an Alberta oil and gas company approach ransomware preparedness?

Energy sector ransomware preparedness requires a specific approach beyond standard SMB planning. You need: immutable backup for all corporate systems with tested RTO/RPO; a documented production shutdown decision framework that specifies when OT systems are proactively isolated; an OT/IT network segmentation architecture that limits blast radius; 24/7 endpoint monitoring and detection; a tested incident response plan that includes AER notification obligations; and cyber insurance with coverage appropriate to your operational scale. The most important step is a current-state assessment understanding what you have, what's connected to what, and where the defensible boundaries are (or should be).

What should I look for in a managed IT provider for an oil and gas company?

Look for: direct Alberta presence (not remote-only support from another province), experience with distributed multi-site architectures and field connectivity, familiarity with OT/IT security principles even if they don't specialize in ICS, 24/7 monitoring and support capability, SOC2 certified or equivalent operational controls, and an explicit security-first approach rather than break-fix reactive support. Ask specifically about their experience with remote site connectivity, their approach to OT/IT boundary security, and how they handle after-hours emergency response for production-critical incidents. A provider that has never seen a SCADA system or supported a field operation is the wrong partner for an energy sector business.

How does IT support differ for oilfield services companies versus operators?

Oilfield services companies drilling contractors, completion crews, wireline services, well testing firms have a more mobile IT model than fixed operators. Their IT challenges include supporting a workforce that moves between job sites constantly, managing equipment-connected devices and diagnostic tools across multiple client environments, operating under the IT security policies of different client operators, and maintaining business systems (scheduling, dispatch, billing, safety management) that are operationally critical but not production-control systems. The core managed IT requirements are similar endpoint security, backup, monitoring, connectivity but the implementation approach must account for the mobile and multi-client nature of oilfield services operations.

What is the minimum viable cybersecurity posture for a small Alberta energy SMB?

For a small producer or oilfield services company with 20–50 staff, the minimum viable posture is: multi-factor authentication on all accounts and remote access (no exceptions); endpoint detection and response (EDR) on all workstations and laptops; immutable offsite backup with tested recovery procedures; OT/IT network segmentation that isolates any SCADA or control systems from the corporate network; and a managed IT provider with 24/7 monitoring. This is not an exhaustive security program it is the floor below which you are accepting significant and largely uninsured risk. A current-state assessment identifies the gap between this baseline and your current posture.

Managing Alberta's Energy Sector IT Local Expertise, National Capability

Alberta's oil and gas industry runs on technology infrastructure that must be as reliable and resilient as the operations it supports. Whether you're managing a portfolio of producing wells, running an oilfield services operation, or providing engineering and consulting services to the sector, your IT environment needs to meet a standard that generic managed IT providers aren't built for.

GAM Tech's Calgary and Edmonton offices serve Alberta's energy corridor with managed IT, security, and connectivity solutions built for the operational realities of the sector. Our 24/7 internal team, SOC2 certified operations, and security-first architecture give energy sector clients the same standard of IT management that large operators apply to their corporate environments at SMB economics.

We specialize in supporting the IT environments surrounding industrial operations: corporate network security, field connectivity, OT/IT boundary management, endpoint protection, and cloud systems so your team can focus on production, not IT problems.

Contact GAM Tech's Calgary or Edmonton office at gamtech.ca to discuss your specific environment. We'll start with an IT assessment that gives you a clear picture of your current posture and the gaps that matter most.