z-logo
Premium
Architecting Technology Transition Pathways: Insights from the Military Tactical Network Upgrade
Author(s) -
Szajnfarber Zoe,
McCabe Linda,
Rohrbach Amanda
Publication year - 2015
Publication title -
systems engineering
Language(s) - English
Resource type - Journals
SCImago Journal Rank - 0.474
H-Index - 50
eISSN - 1520-6858
pISSN - 1098-1241
DOI - 10.1002/sys.21311
Subject(s) - upgrade , software deployment , evolvability , flexibility (engineering) , systems engineering , computer science , engineering , risk analysis (engineering) , operations research , business , software engineering , statistics , mathematics , evolutionary biology , biology , operating system
As engineering systems become more and more complex, technology transition increasingly involves deploying an upgraded subsystem across a legacy network. This mode of upgrade presents new challenges for systems architects concerned with maintaining value over multiple infused technical changes. This paper explores the dynamics of technology transition in path‐dependent infrastructure systems. It uses a model‐based case study of the envisioned military airborne tactical network upgrade as a basis for developing guidelines for effective transition path design. Based on the natural diffusion dynamics of the system we identified an inherent tradeoff between upgrade cycle and sustained capability levels. In other words, assuming even weakly exponential growth in demand, there is a relationship between timing of infusion and longevity of benefit. As a result, a less capable upgrade, deployed expediently can do more good than a more sophisticated upgrade that can only be integrated in the next block upgrade. In addition, by conceptualizing the transition “path” as a design lever, two dimensions of problem decomposition can be exploited to mitigate transition barriers: (1) self‐contained subnetworks can provide a proving ground for full‐system future benefits in order to mitigate stakeholder resistance; and (2) the technical system can be designed for evolvability, making it possible to stage deployment in the technical dimension as well.

This content is not available in your region!

Continue researching here.

Having issues? You can contact us here