Author
Abstract
The adoption of technology in large infrastructure projects is accelerating due to new cybersecurity threats and increased demands for operational resilience and user‐based financing. Additionally, the rapid growth of public cloud, virtualization services, and Artificial Intelligence has promoted the concept of IT as a service. This shift means that the challenge is no longer just leveraging technology, but also competing to recruit and retain the highly specialized talent and skills needed to manage these services and tools. Whether infrastructure projects are delivered by the public sector or in partnership with a private entity, establishing the right policies to build internal talent for developing, deploying, and operating technology—or even to monitor a third party if they decide to outsource a critical component—is a significant challenge. Establishing a shared services organization (SSO) helps retain internal expertise and promotes collaboration among transportation infrastructure stakeholders to deliver standardized services. This study discusses how the factors identified in the research literature as critical to the success or demise of an SSO have influenced the fate of three case studies where large infrastructure projects have implemented an SSO to mitigate the risk associated with outsourcing their core technology. 由于新的网络安全威胁以及对运营韧性和基于用户的融资需求的不断增长, 大型基础设施项目中技术的应用正在加速。此外, 公有云、虚拟化服务和人工智能的快速发展推动了“IT即服务”理念的发展。这种转变意味着挑战不再仅仅是如何利用技术, 还包括如何招募和留住管理这些服务和工具所需的高度专业化的人才和技能。无论基础设施项目是由公共部门交付还是与私营实体合作, 制定正确的政策来培养内部技术开发、部署和运营人才, 甚至在第三方决定外包关键组件时对其进行监控, 都是一项重大挑战。建立共享服务组织(SSO)有助于留住内部专业知识, 并促进交通基础设施利益攸关方之间的协作, 以提供标准化服务。本文探讨了研究文献中确定的对SSO成败至关重要的因素如何影响三个案例研究的命运。这三个案例研究中的大型基础设施项目都实施了SSO, 以降低核心技术外包带来的风险。 La adopción de tecnología en grandes proyectos de infraestructura se está acelerando debido a las nuevas amenazas a la ciberseguridad y al aumento de la demanda de resiliencia operativa y financiación basada en el usuario. Además, el rápido crecimiento de la nube pública, los servicios de virtualización y la Inteligencia Artificial ha impulsado el concepto de TI como servicio. Este cambio implica que el desafío ya no reside únicamente en aprovechar la tecnología, sino también en competir para reclutar y retener el talento y las habilidades altamente especializadas necesarias para gestionar estos servicios y herramientas. Ya sea que los proyectos de infraestructura sean ejecutados por el sector público o en colaboración con una entidad privada, establecer las políticas adecuadas para desarrollar el talento interno necesario para el desarrollo, la implementación y la operación de la tecnología, o incluso para supervisar a un tercero si decide subcontratar un componente crítico, constituye un desafío importante. Establecer una Organización de Servicios Compartidos (OSC) ayuda a retener la experiencia interna y promueve la colaboración entre los actores de la infraestructura de transporte para ofrecer servicios estandarizados. Este artículo analiza cómo los factores identificados en la literatura de investigación como críticos para el éxito o el fracaso de una SSO han influido en el destino de tres estudios de caso donde grandes proyectos de infraestructura implementaron una SSO para mitigar el riesgo asociado a la externalización de su tecnología principal.
Suggested Citation
Download full text from publisher
Corrections
All material on this site has been provided by the respective publishers and authors. You can help correct errors and omissions. When requesting a correction, please mention this item's handle: RePEc:wly:crtinf:v:7:y:2026:i:1:n:e70013. See general information about how to correct material in RePEc.
If you have authored this item and are not yet registered with RePEc, we encourage you to do it here. This allows to link your profile to this item. It also allows you to accept potential citations to this item that we are uncertain about.
We have no bibliographic references for this item. You can help adding them by using this form .
If you know of missing items citing this one, you can help us creating those links by adding the relevant references in the same way as above, for each refering item. If you are a registered author of this item, you may also want to check the "citations" tab in your RePEc Author Service profile, as there may be some citations waiting for confirmation.
For technical questions regarding this item, or to correct its authors, title, abstract, bibliographic or download information, contact: Wiley Content Delivery (email available below). General contact details of provider: https://doi.org/10.1002/(ISSN)2693-3101 .
Please note that corrections may take a couple of weeks to filter through
the various RePEc services.