The call comes at 6:15 a.m. from your plant manager in Mississauga. Three scanners are down on the packing line. The spare bin is empty. The OEM says the next repair shipment is four weeks out. Meanwhile, your Brampton plant has six working spares sitting in a storage room that nobody in Mississauga knows about.
This isn’t a device problem. It’s a lifecycle visibility problem, and it’s costing you more than the repair tickets suggest.
Siemens’ True Cost of Downtime 2024 report found Fortune Global 500 manufacturers lose approximately US$1.4 trillion annually to unplanned downtime—11% of annual revenue. Not every minute of that comes from a failed handheld. But you know from experience that a single dead scanner on a packing line can cascade into a missed truck cut-off within 30 minutes.
This post walks through the evaluation criteria that separate a manufacturing-grade device lifecycle management program from a generic IT services contract—structured around what actually matters on a plant floor for Canadian manufacturing organisations managing rugged device fleets, not what looks good in a slide deck.
Why manufacturing puts unique stress on device lifecycle planning
A Zebra MC9300 rated for 2,000 tumbles onto concrete at 1.5 metres will meet that spec. But the spec doesn’t account for the combination of drops, vibration from conveyor proximity, chemical exposure from cleaning protocols, temperature cycling between a 35°C production floor and a -25°C freezer, and the accumulated abuse of three shifts running 24/7.
In manufacturing, the failure mode isn’t a single event—it’s cumulative wear that compresses a five-year amortisation cycle into three years or less.
The distinction between rugged and non-rugged matters here, but not in the way procurement usually frames it. VDC Research benchmarks annual failure rates for non-rugged devices in industrial settings at 30–50%, versus approximately 4.6% for rugged large-form-factor devices. That sounds like rugged wins—until you do the math on a 500-device fleet. Even at 4.6%, you’re looking at 23 unplanned failures per year requiring immediate response. Each one is a production station waiting for IT to solve a logistics problem.
The components that drive 80% of manufacturing repair tickets—batteries, scanner exit windows, charging contacts, display glass, and hand straps—are rarely budgeted as recurring OpEx line items. They’re treated as “accessories” in procurement but as “emergencies” on the plant floor.
Here’s what actually happens: a battery that’s been through 400 charge cycles doesn’t fail dramatically. It starts holding 70% capacity, then 60%. The night-shift worker compensates by charging more frequently, which accelerates degradation. By the time the device won’t hold a charge through a full shift, you’re three months past the point where proactive replacement would have prevented the incident. A lifecycle management program that doesn’t track battery cycle counts and proactively replace at ~80% capacity is just waiting for a Monday morning failure.
Equipment failure causes approximately 42% of unplanned manufacturing downtime. IT devices don’t get tracked alongside CNC machines and conveyor systems—but they should. A scanner is production equipment. When it fails, the line doesn’t slow down. It stops.
The spare pool gap that stops production lines
When a forklift-mounted terminal fails on a receiving dock, the dock doesn’t slow down—it stops. If no configured spare exists on-site, the line supervisor’s options are: cannibalise a device from another department, call IT and wait, or run manual paper processes that introduce errors downstream.
In practice, “spare pool” in most manufacturing operations means a drawer of devices in various states—some charged, some not, some running last year’s software build, none enrolled in MDM. That’s not a spare pool. That’s a graveyard with a few survivors.
The functional definition of a spare is specific: charged, running current OS and software, enrolled in MDM, configured with your Wi-Fi credentials and business applications, and tracked by location. A device that meets four of those five criteria still costs you 30–60 minutes of setup time when a worker needs it urgently.
The industry benchmark for mission-critical manufacturing lines is 10–15% of fleet held as pre-configured spares, distributed by plant rather than centralised at headquarters. For a 500-device fleet across four plants, that’s 50–75 spares positioned where failures actually occur—not 60 units sitting in a GTA warehouse that can’t reach your Winnipeg plant until Thursday.
Canadian depot and support infrastructure—the first evaluation filter
Most rugged device OEM repair depots are located in the United States. Zebra’s primary North American depot routes through Buffalo Grove, Illinois. Honeywell’s runs through Charlotte, North Carolina.
For a Canadian manufacturer, that means every repair shipment crosses the border twice—adding 5–10 business days of transit, CBSA customs documentation, and potential surtax exposure. A “3-day depot repair” becomes an 8–12 day absence from the plant floor.
This isn’t an abstract sovereignty argument. It’s a logistics cost that compounds with every repair ticket.
Honeywell publishes that off-contract repairs cost up to 3× more on average and take 4–5 weeks without a guaranteed turnaround, versus 2–5 days under a Plus or Comprehensive plan. For a Canadian plant routing repairs through a US depot without a service contract, realistic turnaround is 6–8 weeks—over a full month of lost productivity from a single device.
The cross-border repair problem compounds during peak production periods. Canadian manufacturers running seasonal surges—food processing in harvest months, building products in spring—can’t afford to have 15% of their fleet sitting in a US depot queue. A provider with a Canadian depot eliminates the border variable entirely.
Here’s what actually happens when a device ships to a US depot: CBSA reviews it on the way out. The depot receives it 2–3 days later. Repair takes 3–5 days under contract. Then the device sits in the shipping queue, clears US export, crosses back into Canada, clears CBSA again, and reaches your plant 2–3 days after that. The “3-day repair” just consumed two weeks—and that’s the optimistic timeline with no customs holds.
Bilingual support as a procurement requirement, not a feature
Bill 96 amendments to Quebec’s Charter of the French Language affect workplace device interfaces, training materials, and helpdesk interactions. For manufacturers with plants in Quebec, a lifecycle management provider that cannot deliver French-language helpdesk support, French portal interfaces, and French documentation is non-compliant—not just inconvenient.
This isn’t a service level question. It’s a procurement filter. If a provider can’t support your Quebec plants in French, they can’t support your Quebec plants. Period.
The 24/7 dimension matters too. A Quebec plant running night shifts needs French-language support at 2 a.m., not during Toronto business hours. Ask every provider on your shortlist: what percentage of your helpdesk staff are fluent French speakers, and what’s your French-language coverage outside 9–5 Eastern?
OEM authorisation and parts access: what “partner” actually means
Every VAR in Canada will tell you they’re a Zebra partner. The question is what tier.
A Premier Solutions Partner has access to OEM parts inventory, LifeGuard for Android security patches, device firmware, and technical escalation paths that a standard reseller does not. When your MC9300 needs a scanner engine replacement, the difference between an authorised part and a grey-market substitute is the difference between a reliable repair and a device that fails again in 90 days.
Zebra OneCare Essential offers 3-business-day repair turnaround with comprehensive coverage including accidental damage and wear and tear. OneCare Select adds 24/7 phone support and next-business-day “like-new” replacement preloaded with your custom image. These OEM service plans set the baseline—a lifecycle management provider should meet or exceed these SLAs, not fall below them.
The invisible risk sits with security patching. Zebra LifeGuard for Android security patches is tied to OEM partnership tier. A provider without the correct authorisation level cannot push LifeGuard patches to your fleet—meaning your devices fall behind on security updates even if your MDM is configured correctly.
Here’s what actually happens: you run a quarterly security audit and discover your MC9300 fleet is three patches behind on Android security updates. Your MDM is configured correctly. Your provider says they pushed the updates. But LifeGuard patches don’t flow through standard MDM channels—they require OEM-authorised access. Your provider didn’t have the tier to access them. Now you have a fleet of devices with known vulnerabilities that have been accumulating for nine months.
Ask every provider: what is your Zebra partnership tier? What is your Honeywell partnership tier? Can you push LifeGuard patches directly to enrolled devices?
The repair-vs-replace decision framework for industrial devices
A plant manager brings you a Honeywell CK65 with a cracked display and a degraded battery. The device is 30 months into a 36-month warranty. Repair cost estimate: $380. Replacement cost: $1,800.
The instinct is to repair.
But the device hits end-of-support in 14 months. The battery will need replacing again in 8. And the repair doesn’t reset the warranty clock. The actual decision requires more context than the repair quote provides.
VDC Research found that lost productivity per device failure event averages 50–80 minutes, and productivity loss accounts for up to 41% of total mobile device TCO. The repair cost is the visible number. The productivity cost of repeated failures on a device approaching end-of-life is the hidden number that changes the math.
The problem isn’t making the wrong call on one device. The problem is making the same wrong call repeatedly because nobody is tracking the pattern.
A practical threshold for Canadian manufacturing fleets
The common industry threshold: if repair cost exceeds 50–60% of replacement cost, or if the device is within 12 months of OEM end-of-support, replace rather than repair.
But this threshold only works if someone is tracking repair history per device, warranty expiration dates across the fleet, and OEM end-of-support timelines—which brings us back to lifecycle visibility.
Here’s what actually happens: a device cycles through three repairs in 18 months—$280, $340, $410. Each repair made sense individually. The $280 repair on a $1,800 device? Obviously repair. The $340 repair six months later? Still below threshold. The $410 repair? Now you’ve spent $1,030 repairing a device worth $1,800 new, and it’s still running an OS version that goes end-of-support in four months.
Nobody made a bad decision. But nobody aggregated the repair history to see the pattern emerging after the second incident. A lifecycle management program with serial-level repair tracking catches this before you’ve sunk $1,000 into a device that should have been replaced after repair number two.
The most expensive repair decision in manufacturing isn’t the one that costs $500. It’s the one where the cumulative cost never gets calculated until the device finally dies for good.
The criteria above address the infrastructure, the authorisations, and the decision frameworks. But none of them matter if you can’t answer a basic question: how many devices do you have, where are they, and what state are they in?
Multi-plant device visibility—seeing the whole fleet in one place
The question “how many MC9300s do we have, where, on what OS, under what warranty?” should take 30 seconds to answer.
In most Canadian manufacturing operations with 3+ plants, it takes 3+ days—if it can be answered at all. Asset tags live in one spreadsheet, MDM console data in another, warranty records in a third, and the actual physical location of devices in nobody’s system.
Statistics Canada’s Survey of Advanced Technology found 74.9% of Canadian manufacturing enterprises adopted at least one advanced technology in 2022—among the highest rates in the economy. Canadian manufacturers are technology-forward. But technology adoption without lifecycle visibility creates a growing fleet of unmanaged assets. More devices without more governance equals more risk.
The hidden cost of poor multi-plant visibility is duplicate purchasing. Without a consolidated inventory, Plant A buys 20 new scanners while Plant B has 12 serviceable units sitting in a storage room from a cancelled project. At $1,500–$2,000 per rugged device, that’s $18,000–$24,000 in unnecessary CapEx—repeated across every budget cycle where nobody has a single source of truth.
Here’s what actually happens: your Mississauga plant manager requests 15 replacement TC52s because “we’re always short.” Finance approves the PO because the request seems reasonable. Six months later, someone audits the Calgary plant and finds 11 TC52s in a drawer—8 of them still under warranty, none of them enrolled in MDM. The Mississauga purchase wasn’t fraudulent. It was rational given the information available. The problem is that the information available was incomplete.
Manufacturing CapEx intentions for 2025 are up 15.5% to $38.4 billion—the largest growth among all sectors. With that much capital flowing into manufacturing, every dollar spent on devices that fail prematurely, sit untracked in storage rooms, or get replaced unnecessarily is a dollar that didn’t deliver its intended return.
What a lifecycle visibility portal should actually show you
A portal that shows serial numbers isn’t visibility. It’s a list.
Manufacturing-grade lifecycle visibility means: every device’s serial, physical location (by plant, by department, by shift), assigned user, warranty status and expiration, cumulative repair history, current OS and patch level, MDM enrollment status, and lifecycle stage (active, spare, repair, decommission).
Role-based access is non-negotiable. Operations sees plant-level data. IT sees enterprise-level data. Finance sees TCO and spend. The plant manager in Thunder Bay shouldn’t need to scroll through 3,000 devices across 8 plants to find the 180 that matter to her.
The portal requirement most manufacturers miss in evaluation: historical trending. Knowing you have 47 devices in repair today is useful. Knowing that repair volume has climbed 34% over the last two quarters—and that 60% of those repairs are battery-related on devices purchased in 2022—is actionable. That’s the intelligence that drives a proactive battery replacement program before you have 47 simultaneous failures next quarter.
SLA design for plant-floor reality, not office IT
An SLA that guarantees next-business-day response works fine for a laptop in a corporate office.
On a production line running three shifts with a 2 a.m. changeover, “next business day” means the night shift and the following morning shift run without the device. That’s 16+ hours of degraded operations from an SLA that technically wasn’t breached.
Aberdeen Research estimates average unplanned manufacturing downtime cost at approximately US$260,000 per hour. Even a fraction of that hourly cost—say $2,000 for a single packing line running at reduced capacity—dwarfs the cost of a properly designed spare pool and advance-exchange SLA.
The SLA question isn’t “what’s your turnaround time?” It’s “what happens at 11 p.m. on a Saturday when my Brampton plant needs a replacement?”
Most providers will answer with their standard SLA language. The manufacturing-grade answer is specific: “A pre-configured spare ships from our facility within X hours, arrives by Y service level, and we have phone support available at Z hours to troubleshoot before shipping if the issue might be resolvable remotely.”
Tiered SLAs by site criticality
Not every plant needs 4-hour advance exchange.
A manufacturer with 8 plants might designate 2 high-volume sites as Tier 1 (24-hour advance exchange, 24/7 helpdesk), 4 mid-volume sites as Tier 2 (next-business-day exchange, 16/5 helpdesk), and 2 low-volume sites as Tier 3 (3-day depot, business-hours helpdesk). This tiered model controls cost while protecting the operations that generate the most revenue.
Here’s what actually happens when you don’t tier: you either overpay for 24/7 support at plants that run single shifts, or you underpay and discover the gap at 6 a.m. when your highest-volume plant needs help and nobody’s answering.
The SLA detail most manufacturers miss in evaluation: what’s the geographic exclusion list? A provider promising next-business-day exchange nationally needs to specify which postal codes are excluded. A plant in Thunder Bay or Prince George has different logistics realities than one in the GTA or Montreal corridor. Ask for the exclusion list before you sign.
Secure decommissioning and the compliance dimension
A manufacturer decommissions 200 Zebra tablets after a fleet refresh. The tablets touched production scheduling data, employee shift records, and quality inspection photos tied to customer orders. They’re stacked in a storage room “pending disposal.”
Six months later, nobody has wiped them. The plant manager donates them to a local charity.
That’s a PIPEDA breach waiting to happen—and the manufacturer is liable, not the charity.
The Privacy Commissioner’s guidance is explicit: organisations that collect personal information are responsible for its protection throughout the information lifecycle, including destruction. PIPEDA-related offences carry potential fines up to $100,000 per individual affected by a security breach. The cost of certified data erasure per device is trivial compared to the potential liability of a single unwiped device reaching the wrong hands.
For manufacturers with Quebec operations, the stakes escalated in September 2023. Quebec Law 25 carries administrative monetary penalties of up to $10 million or 2% of worldwide turnover. Device decommissioning is not an IT housekeeping task. It’s a board-level compliance obligation.
The decommissioning detail that separates a real program from a checkbox: chain-of-custody documentation. A certificate of data erasure tells you the data was wiped. Chain-of-custody documentation tells you who had the device, where, at every step from the plant floor to final disposition. For a PIPEDA audit, the chain-of-custody is what the commissioner’s office actually asks for.
Here’s what actually happens without chain-of-custody: an auditor asks you to demonstrate that 200 decommissioned tablets were properly sanitised. You produce 200 certificates of erasure. The auditor asks: “How do you know these certificates correspond to those specific tablets? Where were they between when they left the plant floor and when they reached the disposal facility? Who had access during that window?” If you can’t answer, the certificates prove nothing.
How PiiComm approaches lifecycle management for Canadian manufacturing
The criteria above describe what a manufacturing-grade lifecycle management program should look like. The question is which providers in Canada can actually deliver against them.
OEM service plans from Zebra (OneCare) and Honeywell (Service Made Simple, Comprehensive) cover repair and advance-exchange for their own devices, and they’re a legitimate baseline. Carrier-managed programs from Bell, Rogers, and TELUS handle smartphone and tablet fleets well. But for manufacturers running mixed Zebra/Honeywell fleets across multiple plants with 24/7 shifts, the gap between an OEM warranty program and a managed device lifecycle program serving manufacturing operations becomes operationally significant.
PiiComm is one provider built specifically for this gap—managing 500,000+ devices across thousands of locations in manufacturing, transportation and logistics, retail, healthcare, government, and warehouse and distribution. The capabilities below connect directly to the evaluation criteria in this post.
Canadian infrastructure behind every service level
PiiComm operates its own Canadian staging and depot facilities, a 24/7 bilingual (English/French) service desk staffed in Canada, and in-house certified technicians—eliminating the cross-border repair logistics problem described earlier. No core operational function is outsourced or offshored.
For a manufacturer with plants in Quebec, Ontario, and Alberta, this means repair routing stays domestic. No CBSA queues. No 5–10 day transit penalty. No customs documentation adding friction to every ticket.
OEM partnerships that affect parts access and patch delivery
PiiComm holds Premier partnership with Zebra Technologies (highest partner tier), along with Honeywell and Samsung partnerships. This means access to OEM parts, LifeGuard security patches, and technical escalation—the authorisation-level distinction covered earlier that determines whether your devices stay current on security updates or fall behind despite proper MDM configuration.
Spare pool management sized to plant criticality
PiiComm’s spare pool program pre-stages configured replacement devices in Canadian facilities for same-day shipping. Replacements ship before the broken device is returned—addressing the spare pool gap that causes the line-down scenarios described earlier.
Spare pools are sized to plant criticality, typically 5–15% of fleet for mission-critical lines. The replacement that arrives isn’t factory-default. It’s configured with your MDM profile, applications, and Wi-Fi credentials—operational within minutes of powering on, not 30–60 minutes of setup time on the plant floor.
Fleet-wide visibility through the AIM portal
PiiComm’s AIM (Asset Intelligence Manager) portal provides the multi-plant, role-based device visibility outlined earlier—serial-level tracking, repair history, warranty status, OS/patch level, and lifecycle stage across all locations. Operations sees plant-level data. IT sees enterprise-level data. Finance sees TCO and spend.
The portal tracks non-assetised items too—batteries, cases, chargers, hand straps—the components that drive 80% of repair tickets but rarely appear in traditional asset management systems.
Secure decommissioning with chain-of-custody documentation
Data erasure certified to NIST 800-88 standards with per-device certificates and chain-of-custody documentation from plant floor through final disposition—the compliance standard described in the decommissioning section, aligned with PIPEDA and Quebec Law 25 requirements. This is certified secure decommissioning with chain-of-custody documentation, not a checkbox on a service agreement.
When the alternatives are sufficient: For manufacturers with a single-OEM fleet and straightforward repair needs, Zebra OneCare or Honeywell Comprehensive plans may be enough. For those whose primary need is smartphone fleet management, carrier-managed programs from Bell, Rogers, or TELUS are a reasonable starting point. The managed mobility partner model—where PiiComm operates—addresses the complexity that emerges when you’re running mixed-OEM rugged fleets across multiple plants with 24/7 operations and Canadian compliance obligations.
What good looks like—a manufacturing lifecycle management checklist
Before you issue an RFP or take a vendor call, benchmark against these criteria. A provider that meets all of them is operating at manufacturing grade. A provider that meets half is selling you an office IT program with an industrial label.
Infrastructure and operations
- Canadian depot and helpdesk operations (not just a Canadian sales office)
- 24/7 bilingual (EN/FR) service desk
- Authorised OEM service partner status (Zebra Premier, Honeywell equivalent)
Spare pool and SLA
- Pre-staged spare pool sized to plant criticality (5–15% of fleet)
- Advance-exchange SLA with defined geographic coverage and exclusion list
- Tiered SLA options by site criticality
Visibility and tracking
- Serial-level multi-plant inventory portal with role-based access
- Repair-vs-replace threshold policy with per-device repair history tracking
- Battery health monitoring and proactive replacement program
Technical capability
- MDM administration capability (SOTI, 42Gears, or equivalent—certified, not just integrated)
- OEM-authorised access to security patches (Zebra LifeGuard, Honeywell equivalents)
Compliance and financials
- NIST 800-88 certified data erasure with chain-of-custody documentation
- Per-device-per-month or DaaS pricing model available (OpEx flexibility)
- Canadian manufacturing references available for peer conversations
Questions to ask every provider on your shortlist
These questions will expose whether a provider has real manufacturing lifecycle capability or is paper-positioning:
- Where is your repair depot physically located? (Not your sales office—your depot.)
- Where are your helpdesk staff physically sitting, and what percentage are fluent French speakers?
- What is your Zebra partnership tier? Can you push LifeGuard patches directly to enrolled devices?
- What is your standard spare pool ratio recommendation for a 500-device manufacturing fleet running three shifts?
- Walk me through what happens when a device fails at 2 a.m. on a Saturday at our highest-volume plant.
- What is your geographic exclusion list for next-business-day advance exchange?
- Can you show me a sample chain-of-custody document from device collection through final disposition?
- What does your portal show for per-device repair history, and how far back does it go?
- How do you handle mixed Zebra/Honeywell fleets under a single contract?
- Can you provide references from Canadian manufacturing operations similar to ours?
The providers who understand manufacturing will welcome these questions. The ones who don’t will talk around them.
Ready to evaluate your current approach against these criteria? Talk to a managed mobility specialist about your manufacturing fleet—no obligation, just a clearer picture of where the gaps are and what it would take to close them.
Frequently asked questions
What spare pool ratio should a Canadian manufacturer maintain for rugged devices?
For mission-critical production lines running multiple shifts, maintain 10–15% of fleet as pre-configured spares distributed across plants. For single-shift or lower-criticality operations, 5–8% is sufficient. Spares must be charged, running current software, enrolled in MDM, and tracked by location—a drawer of old devices is not a spare pool.
How long should a rugged device repair take in Canada?
Under a managed service contract with a Canadian depot, expect 3-business-day depot repair or next-business-day advance exchange for critical devices. Without a Canadian depot, add 5–10 days for cross-border transit. Off-contract OEM repairs average 4–5 weeks—unacceptable for any production-critical device.
When should a manufacturer replace a rugged device instead of repairing it?
Replace when repair cost exceeds 50–60% of replacement cost, when the device is within 12 months of OEM end-of-support, or when cumulative repair costs over the device’s life exceed 80% of a new unit. This decision requires serial-level repair history tracking—without it, you’re guessing.
What should a multi-plant device visibility portal show?
At minimum: every device’s serial number, physical location by plant and department, assigned user, warranty expiration, cumulative repair history, current OS and patch level, MDM enrollment status, and lifecycle stage. Role-based access is essential—Operations needs plant-level views, IT needs enterprise views, Finance needs TCO reporting.
What Canadian privacy regulations affect device lifecycle management in manufacturing?
PIPEDA requires documented data destruction on end-of-life devices containing personal information—with mandatory breach reporting since 2018. Quebec Law 25 adds penalties up to $10 million or 2% of worldwide turnover. Manufacturers need per-device NIST 800-88 erasure certificates and chain-of-custody documentation to demonstrate compliance in an audit.
How do I evaluate whether a lifecycle management provider has real Canadian operations?
Ask three specific questions: Where is your repair depot physically located? Where are your helpdesk staff physically sitting? Can you provide French-language support for Quebec plant workers? A Canadian sales office is not Canadian operations. Look for Canadian-domiciled depot facilities, Canadian-staffed technicians, and 24/7 bilingual service desk capability.
Can a single lifecycle management provider handle both Zebra and Honeywell devices?
Yes—this is a primary advantage of a managed mobility provider over individual OEM service plans. Look for providers with authorised partner status across multiple OEMs and the ability to manage mixed fleets under a single contract, portal, and SLA. Managing two separate OEM contracts doubles the administrative burden without improving outcomes.
What does device lifecycle management cost per device per month for manufacturing?
Pricing varies by fleet size, device type, SLA tier, and services included. The relevant comparison isn’t the per-device fee versus zero—it’s the managed fee versus the fully loaded in-house cost including IT labour, repair logistics, spare pool capital, downtime, and compliance risk. VDC Research consistently finds managed approaches deliver 15–40% lower TCO over 3–5 years.
Not sure where your fleet stands? Start with a device fleet assessment—understand what you have across your plants before evaluating providers. A clearer picture of your current state makes every subsequent conversation more productive.
The question underneath the checklist
Every criterion in this post comes back to one question: when your next device fails at 6 a.m. on a Monday before a product launch, what happens?
The answer determines whether your packing line keeps moving or stops. Whether your shift supervisor improvises with paper processes or swaps in a configured spare. Whether your IT team spends the week on strategic projects or on shipping logistics and RMA paperwork.
The evaluation process isn’t about finding a provider with the longest feature list. It’s about finding one whose operational infrastructure—spare pools, depot locations, service desk staffing, OEM authorisations—matches the geography, tempo, and compliance obligations of your plants.
Canadian manufacturing productivity has work to do. The $38.4 billion flowing into manufacturing capital this year deserves better than devices sitting in US depot queues, spare drawers full of unconfigured units, and decommissioned tablets stacked in storage rooms waiting to become compliance findings.
The devices on your plant floor are production assets. Manage them like it.