Strategy, Economics and Digital Transformation

Introduction

Mobile computing has moved from being a communication capability to becoming an organisational platform. Smartphones, wireless broadband, cloud services, edge computing, Internet of Things (IoT) devices, artificial intelligence (AI), and private networks now influence how firms produce, sell, govern, and deliver services. Consequently, mobile technology decisions cannot be evaluated only through coverage, throughput, latency, or device specifications. They require an integrated assessment of strategic alignment, economics, risk, regulation, sustainability, standards, suppliers, service quality, and organisational change.

For an enterprise, a mobile investment may involve spectrum access, radio and core infrastructure, devices, applications, cloud and edge resources, cybersecurity, data platforms, skills, and operating processes. The central managerial question is not simply “Which technology is fastest?” but “Which combination of capabilities creates measurable and defensible value under uncertainty?”

This chapter develops frameworks for answering that question. It examines mobile technology roadmaps, techno-economic evaluation, spectrum policy, standards, vendor selection, service-level agreements (SLAs), platform ecosystems, and digital transformation. The chapter adopts a post-graduate perspective: technical feasibility is treated as necessary but insufficient, while assumptions, externalities, uncertainty, governance, and implementation capability are explicitly considered.

Learning Objectives

By the end of this chapter, the reader should be able to:

1. Formulate a mobile technology roadmap linked to organisational strategy and measurable outcomes.

2. Apply discounted-cash-flow, total-cost-of-ownership, and sensitivity-analysis methods to mobile investments.

3. Explain the strategic importance of spectrum policy, standards, interoperability, and ecosystem control.

4. Design criteria for vendor selection and mobile-network SLAs.

5. Evaluate platform ecosystems, lock-in, cybersecurity, privacy, and sustainability risks.

6. Analyse how mobile technologies support enterprise digital transformation.

7. Critically assess contemporary developments such as 5G private networks, edge computing, open network architectures, and AI-enabled operations.

1. From Technology Adoption to Strategic Capability

A technology becomes strategically significant when it changes an organisation’s ability to create value, manage risk, or compete. A mobile network may reduce field-service time, enable real-time production control, or provide a new customer channel. Its strategic value therefore depends on the relationship among technology, processes, people, data, and business models.

A useful distinction is between technology adoption and digital transformation. Adoption introduces a tool into an existing process; transformation redesigns processes, decision rights, customer relationships, and sometimes the business model around digital capabilities. Replacing paper forms with a mobile application is adoption if the underlying approval process remains unchanged. It becomes transformation when mobile data is integrated with workflow automation, analytics, inventory systems, and performance management to redesign service delivery.

A mobile capability may create value through:

• revenue growth, such as mobile commerce or location-based services;
• cost reduction, such as automated inspection and reduced travel;
• quality and safety improvement, such as real-time monitoring;
• resilience, through connectivity diversity and remote operations;
• customer experience, through personalised and continuous interaction; and
• innovation, through access to developer and partner ecosystems.

The resource-based view suggests that technology produces sustained advantage when it is valuable, difficult to imitate, and supported by complementary organisational resources. Connectivity alone is usually imitable. Proprietary data, integrated workflows, skilled personnel, trusted brands, and effective governance may be more difficult to reproduce. The dynamic-capabilities perspective adds that firms must sense opportunities, seize them through investment, and transform their asset base as conditions change.

These perspectives caution against equating technical novelty with strategic value. A 5G deployment may be justified in a factory with strict mobility, reliability, and local-processing requirements, but not necessarily in an office where existing Wi-Fi and public cellular service meet the requirements.

2. Strategy Formulation and the Mobile Technology Roadmap

A roadmap is a time-phased statement of capabilities, dependencies, investment decisions, and target outcomes. It is not merely a list of products or release dates. A credible roadmap connects four layers:

1. Strategic outcomes: growth, productivity, resilience, inclusion, safety, or sustainability.

2. Business capabilities: mobile workforce management, asset visibility, remote control, customer engagement, or secure collaboration.

3. Technical capabilities: radio access, spectrum, identity, devices, applications, APIs, cloud, edge, and data analytics.

4. Execution mechanisms: funding, governance, skills, suppliers, procurement, testing, and change management.

Roadmap development should begin with a baseline. The baseline records current coverage, performance, asset age, application dependencies, security posture, operating costs, contracts, and user pain points. Requirements should then be expressed in measurable terms. For example, “high reliability” is inadequate; “99.95% monthly service availability for priority telemetry, excluding approved maintenance windows” is more useful, provided the measurement method is agreed.

A practical roadmap normally contains the following stages:

2.1 Opportunity and problem definition

Identify business problems rather than beginning with a preferred technology. Interview operational users, customers, security teams, finance, legal specialists, and network operators. Define the affected process, baseline performance, target performance, constraints, and consequences of failure.

2.2 Feasibility and options analysis

Compare alternatives such as public cellular, Wi-Fi, private cellular, satellite, fixed connectivity, or hybrid designs. Consider technical performance, geographic scope, spectrum availability, integration effort, security, operational maturity, and cost.

2.3 Pilot and evidence generation

A pilot should test the riskiest assumptions, not merely demonstrate that equipment works. It may test indoor propagation, device battery life, handover behaviour, application latency, integration with identity systems, or the ability of operations staff to manage incidents.

2.4 Scale and institutionalisation

Scaling requires standard architectures, procurement agreements, monitoring, training, support processes, asset management, and governance. A successful pilot may fail at scale if device logistics, application support, or spectrum coordination has been ignored.

2.5 Renewal and retirement

Roadmaps must include decommissioning. Legacy networks create cybersecurity exposure, duplicated costs, and scarce specialist dependence. Retirement decisions should account for safety systems, contractual obligations, archived data, and migration testing.

A roadmap should use decision gates. At each gate, the organisation reassesses benefits, cost, risk, readiness, and alternatives. This prevents sunk-cost reasoning from forcing an unattractive project to continue.

3. Techno-Economic Evaluation

3.1 Total cost of ownership

Total cost of ownership (TCO) estimates the full economic burden of an option over its analysis period. A general form is:

TCO = C_initial + C_network + C_devices + C_software + C_operations + C_integration + C_compliance + C_exit − S_residual

where each C term is a cost category and S_residual is the residual or salvage value at the end of the period. Costs should include acquisition, installation, spectrum or subscription fees, energy, maintenance, licences, training, cybersecurity, insurance, support, replacement, and decommissioning. The equation is an accounting framework rather than a universal valuation formula; categories must be defined consistently and double counting avoided.

TCO is useful for comparing alternatives with similar benefits, but it does not measure timing or risk. A low-cost option can be economically inferior if it produces benefits later or has a high probability of disruption.

3.2 Net present value

Net present value (NPV) accounts for the time value of money:

NPV = −I_0 + Σ from t=1 to T of (B_t − C_t)/(1+r)^t + V_T/(1+r)^T

Here, I_0 is the initial investment at time zero, B_t is benefit in period t, C_t is operating cost in period t, r is the discount rate per period, T is the analysis horizon, and V_T is terminal value. All monetary values must use the same currency and price basis. The discount rate should reflect the organisation’s opportunity cost of capital and, where appropriate, project-specific risk. Inflation must not be mixed inconsistently: nominal cash flows require a nominal discount rate, while real cash flows require a real discount rate.

If NPV is positive under the selected assumptions, the investment is expected to create value relative to the benchmark represented by the discount rate. NPV is not proof of success; it is conditional on forecasts, scope, and risk assumptions.

3.3 Worked economic example

An enterprise considers a mobile workflow system. The initial investment is $480,000. It expects net benefits of $180,000 at the end of each year for three years. Assume a discount rate of 10% per year and no terminal value.

NPV = −480,000 + 180,000/1.10 + 180,000/(1.10)^2 + 180,000/(1.10)^3

The present values are approximately $163,636, $148,760, and $135,236. Therefore:

NPV ≈ −480,000 + 447,632 = −$32,368.

Under these assumptions, the project does not meet a 10% required return. Its simple payback period is 480,000/180,000 = 2.67 years, but payback ignores discounting and benefits after payback. Management might revise the design, negotiate lower implementation costs, include defensible benefits not previously counted, or reject the investment. The correct response is not to alter the discount rate merely to obtain a positive result.

3.4 Benefits realisation and uncertainty

Mobile benefits are often distributed across departments. A field application may reduce travel for operations, improve billing for finance, and improve customer satisfaction for sales. A benefits register should identify the owner, baseline, target, measurement method, timing, dependency, and confidence level for every material benefit.

Uncertainty can be addressed through:

• sensitivity analysis, changing one assumption at a time;
• scenario analysis, evaluating coherent combinations such as high growth, supply disruption, or regulatory change;
• break-even analysis, finding the value at which an investment becomes economically neutral; and
• real-options reasoning, valuing the flexibility to delay, expand, abandon, or switch after learning from a pilot.

A pilot has option value when it is inexpensive relative to the cost of an irreversible full deployment and produces information relevant to a major decision. However, option arguments should not become an excuse for indefinite experimentation without decision criteria.

4. Spectrum Policy, Standards, and Interoperability

Spectrum is a finite public resource managed through national regulation and international coordination. Policy objectives commonly include efficient use, competition, public safety, coverage, affordability, innovation, and avoidance of harmful interference. Regulators may assign spectrum through auctions, administrative licensing, shared-access frameworks, unlicensed allocations, or combinations of these methods.

Spectrum decisions have strategic implications. Exclusive licences can provide predictable interference conditions but may concentrate market power. Unlicensed access lowers entry barriers but requires contention management. Shared or local licensing can support industrial private networks, although coordination and device availability may be more complex.

Important policy questions include:

• Who may access the band and under what technical conditions?
• How are incumbent users protected?
• What obligations apply to coverage, quality, emergency communications, or wholesale access?
• Are licence terms long enough to justify investment?
• How are cross-border interference and public-interest requirements handled?

Standards reduce uncertainty by defining interfaces, protocols, security procedures, and conformance expectations. Cellular standards developed through global partnership processes have enabled multi-vendor interoperability and economies of scale. Standards, however, do not guarantee complete interoperability. Optional features, proprietary extensions, certification differences, and implementation quality can still produce dependence on one supplier.

A sound procurement specification should distinguish:

• mandatory standards conformance;
• tested interoperability requirements;
• performance requirements under defined conditions;
• security and update obligations; and
• open interfaces required for future migration.

Standards should not be selected solely because they are new. The relevant question is whether the standard has a mature ecosystem, available devices, credible security support, and a roadmap compatible with the enterprise’s investment horizon.

5. Vendor Selection and Service-Level Agreements

Vendor selection is a socio-technical decision. Price is only one criterion. A robust evaluation considers technical fit, lifecycle economics, security, interoperability, resilience, delivery capability, financial stability, support quality, sustainability, and exit feasibility.

A weighted decision model can clarify judgement. Let the score for vendor j be:

S_j = Σ from i=1 to n of w_i x_ij

where w_i is the weight assigned to criterion i, x_ij is the normalised score of vendor j on criterion i, and the weights sum to one. This model assumes criteria can be represented on comparable scales and that the decision maker accepts a compensatory trade-off: a weakness in one criterion may be offset by strength in another. Non-compensatory requirements, such as legal compliance or minimum cybersecurity controls, should be treated as pass/fail gates rather than hidden within a weighted score.

Evaluation criteria may include:

• functional and radio performance;
• total cost over the contract period;
• standards and API openness;
• security architecture, vulnerability response, and software supply-chain controls;
• local support and spare-parts capability;
• data location and privacy compliance;
• energy efficiency and equipment lifecycle;
• disaster recovery and business continuity; and
• termination assistance and data portability.

An SLA converts expectations into measurable commitments. It should define service scope, measurement points, reporting frequency, maintenance windows, incident priorities, response and restoration targets, remedies, exclusions, escalation, audit rights, and change control. Typical metrics include availability, latency, packet loss, throughput, coverage, incident response time, mean time to restore, and security-notification time.

Metrics must be operationally meaningful. “99.9% availability” permits approximately 8.76 hours of unavailability in a 365-day year if measured continuously. The calculation is 365 × 24 × 0.001 = 8.76 hours. The SLA must state whether planned maintenance, force majeure, customer-caused faults, or access restrictions are excluded. It should also specify whether availability is measured at the access point, application endpoint, or complete service chain. A network can meet a radio availability target while the application remains unusable because of identity, cloud, or integration failure.

Service credits alone may be inadequate for safety-critical or revenue-critical services. Contracts may require corrective-action plans, independent audits, redundancy, service improvement obligations, or termination rights. SLAs should be aligned with business impact rather than arbitrary technical numbers.

6. Platform Ecosystems and Strategic Dependence

A mobile platform ecosystem includes device manufacturers, operating-system providers, network operators, cloud providers, application developers, system integrators, advertisers, regulators, users, and data intermediaries. Value often increases with network effects: more users attract developers, and more applications attract users. Complementors contribute innovation, while platform owners control interfaces, certification, distribution, identity, payment, and data access.

The ecosystem creates benefits such as rapid innovation, broad device choice, and specialised services. It also creates risks:

• vendor lock-in, when migration costs become prohibitive;
• data lock-in, when data formats or histories cannot be exported usefully;
• identity dependence, when one provider controls authentication or account recovery;
• platform policy risk, when access rules or revenue shares change; and
• concentration risk, when a small number of suppliers become systemic dependencies.

Architectural responses include open APIs, documented data models, containerised workloads where appropriate, multi-sourcing, portability testing, escrow or continuity arrangements, and separation of data ownership from application hosting. Multi-cloud or multi-vendor strategies are not automatically superior: they can increase complexity, duplicated skills, integration cost, and security exposure. The appropriate strategy depends on the criticality of the service and the cost of credible exit.

7. Risk, Governance, and Sustainability

Mobile programmes face technical, commercial, regulatory, operational, cyber, social, and environmental risks. A risk register should state the event, cause, consequence, likelihood, impact, owner, existing controls, treatment, and review date. Risk scoring is useful for prioritisation but should not imply precise probabilities when evidence is weak.

Cybersecurity controls should follow the system lifecycle. They include asset inventory, secure identity and authentication, least privilege, encryption, secure configuration, patch management, vulnerability disclosure, logging, monitoring, incident response, backup, and recovery testing. Mobile and IoT deployments are especially exposed to lost devices, insecure applications, rogue endpoints, weak credentials, supply-chain compromise, and long-lived equipment that cannot be patched.

Privacy governance requires purpose limitation, data minimisation, transparency, lawful processing, retention controls, access rights, and protection against inappropriate inference. Location data can reveal sensitive behaviour even when names are removed. AI systems using mobile data additionally raise concerns about bias, explainability, model drift, surveillance, and accountability. Human oversight should be proportionate to the consequences of automated decisions.

Sustainability analysis should consider the complete lifecycle: raw materials, manufacturing, transport, energy during operation, maintenance, reuse, and disposal. A newer network may reduce energy per transmitted bit but still increase total consumption if traffic and equipment density grow. Claims should therefore use defined boundaries and functional units. Relevant measures include energy per device-year, energy per gigabyte under a specified workload, equipment reuse rate, embodied carbon, and electronic-waste recovery. Sustainable procurement should require supplier reporting, repairability, upgrade support, and responsible end-of-life handling.

Governance should establish decision rights. A programme board may approve investment, an architecture authority may control technical standards, a security function may set mandatory controls, and business owners may accept residual operational risk. Governance that is too weak permits uncontrolled fragmentation; governance that is too rigid can prevent legitimate innovation.

8. Enterprise Digital Transformation with Mobile Technologies

Transformation generally requires more than deploying connectivity. A useful capability stack includes:

1. Connectivity: public cellular, private cellular, Wi-Fi, satellite, or hybrid access.

2. Compute and storage: cloud, on-premises, and edge resources.

3. Data and integration: APIs, event streams, identity, master data, and analytics.

4. Applications: mobile workflows, operational technology interfaces, customer services, and collaboration tools.

5. Operating model: skills, processes, governance, incentives, and support.

Edge computing is strategically relevant when data must be processed near its source because of latency, bandwidth, privacy, resilience, or control requirements. It is not automatically cheaper than central cloud computing. Distributed infrastructure increases operational complexity and must be justified by a clear requirement.

Private cellular networks can provide managed mobility, controlled identity, and predictable coverage in industrial or campus environments. Their value depends on device support, spectrum rights, integration with operational technology, and the organisation’s ability to operate or contract the service. Public networks may be preferable where wide-area mobility, mature support, and low internal operational burden dominate.

Change management is a major determinant of outcome. Users may resist mobile workflows that increase monitoring or alter established authority. Training, participatory design, accessibility, job redesign, and feedback mechanisms are therefore technical success factors, not peripheral human-resource activities.

9. Illustrative Case: Mobile Transformation in a Regional Utility

Background

A fictional regional electricity utility operates 1,200 substations and maintains a dispersed field workforce. Technicians use paper forms and intermittent cellular access. Work orders are often entered after returning to a depot, delaying outage restoration and creating duplicate data entry.

Problem

The utility proposes rugged mobile devices, a field-service application, improved connectivity, and selected edge gateways at substations. It must decide whether to use public cellular service, a private network at major sites, or a hybrid model. The programme also has to meet cybersecurity, safety, privacy, and continuity requirements.

Analysis

The baseline identifies three major costs: technician travel caused by incomplete information, delayed restoration, and administrative re-entry. Requirements are defined as: digital work-order completion at the point of work; operation during temporary coverage loss; strong device identity; auditability; and restoration of critical communications after a local network failure.

The options team compares public cellular, private cellular, and hybrid deployment. Public cellular offers broad geographic coverage and lower internal operating complexity. Private cellular offers greater control at large substations but requires spectrum coordination, local infrastructure, and specialist support. The hybrid option uses public service for ordinary field mobility and private or local wireless coverage only where industrial requirements justify it.

The pilot deliberately tests offline synchronisation, battery endurance, ruggedness, identity integration, application response time, and technician acceptance. It does not measure only peak radio throughput. The procurement specification requires exportable work-order data, documented APIs, security patch commitments, incident notification, and termination assistance.

Approach and solution

The utility adopts a phased hybrid architecture. Devices cache authorised work packages and synchronise when connectivity returns. Critical substations receive locally managed connectivity with resilient backhaul. A central identity service applies role-based access, while the application records changes for audit. The SLA separates device support, access connectivity, application availability, and end-to-end transaction success so that responsibility is not obscured.

Benefits are assigned to accountable owners. Operations measures restoration time and repeat visits; finance measures administrative effort; safety measures completion of mandatory checks; and IT measures security and availability. A steering committee reviews the roadmap quarterly and can delay expansion if pilot evidence fails predefined thresholds.

Outcome

In this illustrative case, the principal outcome is not a particular radio technology. It is a governed service that combines connectivity, data, workflow redesign, resilience, and workforce adoption. The hybrid architecture avoids imposing private infrastructure where public service is adequate while reserving controlled local capability for sites with stronger requirements.

Learning points

1. Requirements should be expressed as business and service outcomes.

2. Pilots should test uncertainty and integration, not just technical demonstration.

3. Hybrid architecture can balance coverage, control, and cost.

4. SLAs must cover the complete service chain.

5. Benefits require named owners and post-deployment measurement.

10. Contemporary Developments and Critical Evaluation

5G and subsequent mobile evolution provide capabilities such as enhanced broadband, massive device connectivity, and support for demanding latency and reliability applications. Their strategic value varies by use case; marketing labels should not replace measured requirements. Open and disaggregated network architectures may improve supplier diversity and innovation, but interoperability testing, integration responsibility, performance assurance, and security become more demanding.

AI is increasingly used for demand forecasting, anomaly detection, radio optimisation, predictive maintenance, customer support, and security operations. AI can improve scale and responsiveness, but training data quality, false positives, model drift, explainability, and governance remain critical. Automated optimisation should include safe operating bounds, rollback procedures, monitoring, and human escalation.

Satellite-to-device connectivity, non-terrestrial networks, advanced private networks, digital twins, and programmable network interfaces may extend the role of mobile computing. Their adoption should be evaluated through the same disciplined framework: use-case value, maturity, standards, spectrum and regulatory conditions, lifecycle cost, resilience, security, and organisational readiness.

Best-Practice Checklist

A defensible mobile strategy should:

• begin with business outcomes and a documented baseline;
• compare multiple architectures, including the option of no change;
• use TCO and NPV with transparent assumptions;
• separate mandatory compliance gates from weighted preferences;
• test interoperability, migration, security, and offline operation;
• define measurable end-to-end SLAs;
• assign benefit owners and review benefits after deployment;
• include privacy, accessibility, sustainability, and workforce impacts;
• maintain exit and continuity plans for critical suppliers; and
• use pilots as evidence-generating decision gates rather than permanent experiments.

Chapter Summary

Mobile computing strategy requires integration of engineering, economics, policy, governance, and organisational change. A roadmap should connect strategic outcomes to business capabilities, technical components, and execution mechanisms. Techno-economic evaluation combines total cost of ownership, discounted cash flow, benefits realisation, sensitivity analysis, scenarios, and—where appropriate—real-options reasoning.

Spectrum policy determines access, interference conditions, competition, and investment incentives. Standards support scale and interoperability, but conformance does not eliminate proprietary dependence. Vendor selection should combine technical, economic, security, sustainability, support, and exit criteria. SLAs must define measurable service boundaries and end-to-end responsibilities rather than relying on vague promises.

Platform ecosystems generate innovation and network effects while creating lock-in and concentration risks. Digital transformation depends on connectivity plus data, applications, operating models, skills, and governance. Private cellular, edge computing, AI, and emerging network architectures are valuable only when their specific capabilities address verified requirements. Finally, responsible mobile strategy includes cybersecurity, privacy, inclusion, environmental lifecycle impacts, and accountable decision-making.

Key Terms

Techno-economic analysis: Evaluation of technical alternatives using economic value, cost, risk, and lifecycle assumptions.

Roadmap: A time-phased plan connecting strategic outcomes, capabilities, investments, dependencies, and decisions.

Total cost of ownership: The full lifecycle cost of acquiring, operating, supporting, and retiring an asset or service.

Net present value: The present value of future net cash flows minus the initial investment.

Discount rate: The rate used to convert future monetary amounts into present value.

Benefits realisation: The process of assigning, measuring, and achieving expected project benefits.

Spectrum policy: Regulatory rules governing access to and use of radio-frequency spectrum.

Interoperability: The ability of systems, products, or services to exchange and use information effectively.

Private cellular network: A cellular network dedicated to an organisation, site, or defined user group.

Service-level agreement: A contract specifying measurable service commitments, responsibilities, and remedies.

Vendor lock-in: Dependence on a supplier caused by high switching costs or limited portability.

Platform ecosystem: A network of a platform owner, users, developers, suppliers, and complementary services.

Digital transformation: Organisational change in processes, capabilities, and business models enabled by digital technologies.

Edge computing: Processing data near its source or point of use rather than exclusively in a central cloud.

Total service availability: The proportion of time that the complete user-relevant service is operational.

Risk register: A controlled record of risks, causes, consequences, owners, controls, and treatments.

Real option: The value of managerial flexibility to delay, expand, switch, or abandon an investment.

Lifecycle sustainability: Assessment of environmental and social impacts from production through disposal.

Benefits owner: The person accountable for achieving and measuring a specified benefit.

Open interface: A documented interface that supports integration and reduces dependence on proprietary mechanisms.

Review Questions

Short Answer Questions

1. Distinguish technology adoption from digital transformation.

2. What are the four layers of a mobile technology roadmap?

3. Why should mandatory compliance requirements be treated separately from weighted vendor-selection criteria?

4. Define vendor lock-in and give one method of reducing it.

5. Why must an SLA specify the measurement point for availability?

Long Answer Questions

1. Explain how NPV, TCO, benefits realisation, and sensitivity analysis can be combined to evaluate a mobile investment.

2. Analyse the strategic effects of spectrum allocation methods on competition, innovation, and enterprise deployment.

3. Discuss the advantages and limitations of public cellular, private cellular, and hybrid architectures.

4. Explain how platform ecosystems create both innovation benefits and strategic dependence.

5. Develop a governance framework for a mobile digital-transformation programme, including cybersecurity, privacy, sustainability, and supplier management.

Analytical / Application Questions

1. An enterprise invests $600,000 initially and receives net benefits of $230,000 annually for three years. Using a 10% discount rate and no terminal value, calculate the NPV and recommend whether the investment meets a 10% required return.

2. Design a weighted vendor-selection model for a healthcare mobile-network deployment. Identify at least six criteria, assign justified weights, and state which requirements should be pass/fail gates.

3. A logistics company is considering a private cellular network for one warehouse and public cellular service for its fleet. Develop a decision analysis covering requirements, costs, risks, SLAs, data governance, and an evidence-generating pilot.

Multiple Choice Questions with Answers

Question 1

Which statement best distinguishes digital transformation from simple technology adoption?

A. Transformation always requires replacing all legacy systems.

B. Transformation redesigns capabilities or processes around digital technologies.

C. Transformation is limited to purchasing newer devices.

D. Transformation excludes organisational and workforce changes.

Correct Answer: B. Transformation redesigns capabilities or processes around digital technologies.

Question 2

What does NPV primarily account for that simple payback does not?

A. Device weight

B. Radio-frequency interference

C. Time value of money

D. Number of software users

Correct Answer: C. Time value of money

Question 3

In the chapter’s worked example, what was the approximate NPV of the mobile workflow system?

A. Positive $32,368

B. Negative $32,368

C. Positive $447,632

D. Zero dollars

Correct Answer: B. Negative $32,368

Question 4

Which item should normally be treated as a pass/fail gate rather than a compensatory weighted criterion?

A. Supplier office location

B. Optional user-interface colour

C. Legal or mandatory cybersecurity compliance

D. Preference for a supplier’s presentation style

Correct Answer: C. Legal or mandatory cybersecurity compliance

Question 5

An availability target of 99.9% over a 365-day year permits approximately how much unavailability, before contractual exclusions?

A. 8.76 hours

B. 24 hours

C. 87.6 hours

D. 0.876 hours

Correct Answer: A. 8.76 hours

Question 6

Which condition most strongly supports using edge computing?

A. The application has no data or processing requirements.

B. Processing must occur near the source because of latency or resilience needs.

C. The organisation wants to eliminate all distributed infrastructure.

D. The service requires only archival storage once per year.

Correct Answer: B. Processing must occur near the source because of latency or resilience needs.

Question 7

What is a major limitation of a weighted vendor-scoring model?

A. It cannot compare any alternatives.

B. It assumes scores are comparable and permits trade-offs among criteria.

C. It automatically proves future supplier performance.

D. It excludes all financial considerations.

Correct Answer: B. It assumes scores are comparable and permits trade-offs among criteria.

Question 8

Which is an example of data lock-in?

A. A device having a durable protective case

B. A network using encryption

C. An inability to export useful historical data from a platform

D. A service having a documented API

Correct Answer: C. An inability to export useful historical data from a platform

Question 9

What should a good pilot primarily test?

A. Only the highest advertised throughput

B. The riskiest technical, operational, and integration assumptions

C. Whether marketing material is visually attractive

D. Whether the project can avoid all governance

Correct Answer: B. The riskiest technical, operational, and integration assumptions

Question 10

Why is a hybrid mobile architecture sometimes preferable?

A. It guarantees zero operating cost.

B. It combines different connectivity models according to site and use-case requirements.

C. It removes the need for standards and security controls.

D. It ensures every site receives identical infrastructure.

Correct Answer: B. It combines different connectivity models according to site and use-case requirements.