<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.3 20210610//EN" "JATS-journalpublishing1-3-mathml3.dtd">
<article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:ali="http://www.niso.org/schemas/ali/1.0/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" article-type="research-article" dtd-version="1.3" xml:lang="EN">
<front>
<journal-meta>
<journal-id journal-id-type="publisher-id">Front. Commun. Netw.</journal-id>
<journal-title-group>
<journal-title>Frontiers in Communications and Networks</journal-title>
<abbrev-journal-title abbrev-type="pubmed">Front. Commun. Netw.</abbrev-journal-title>
</journal-title-group>
<issn pub-type="epub">2673-530X</issn>
<publisher>
<publisher-name>Frontiers Media S.A.</publisher-name>
</publisher>
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">1732098</article-id>
<article-id pub-id-type="doi">10.3389/frcmn.2025.1732098</article-id>
<article-version article-version-type="Version of Record" vocab="NISO-RP-8-2008"/>
<article-categories>
<subj-group subj-group-type="heading">
<subject>Original Research</subject>
</subj-group>
</article-categories>
<title-group>
<article-title>Optimization of cloud resource demand forecasting and investment decisions in the context of digital transformation</article-title>
<alt-title alt-title-type="left-running-head">Chen et al.</alt-title>
<alt-title alt-title-type="right-running-head">
<ext-link ext-link-type="uri" xlink:href="https://doi.org/10.3389/frcmn.2025.1732098">10.3389/frcmn.2025.1732098</ext-link>
</alt-title>
</title-group>
<contrib-group>
<contrib contrib-type="author">
<name>
<surname>Chen</surname>
<given-names>Zhuolin</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Conceptualization" vocab-term-identifier="https://credit.niso.org/contributor-roles/conceptualization/">Conceptualization</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Project administration" vocab-term-identifier="https://credit.niso.org/contributor-roles/project-administration/">Project administration</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Writing &#x2013; review &#x26; editing" vocab-term-identifier="https://credit.niso.org/contributor-roles/Writing - review &#x26; editing/">Writing - review and editing</role>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Tang</surname>
<given-names>Yuanchun</given-names>
</name>
<xref ref-type="aff" rid="aff2">
<sup>2</sup>
</xref>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Supervision" vocab-term-identifier="https://credit.niso.org/contributor-roles/supervision/">Supervision</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Writing &#x2013; review &#x26; editing" vocab-term-identifier="https://credit.niso.org/contributor-roles/Writing - review &#x26; editing/">Writing - review and editing</role>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Wu</surname>
<given-names>Fei</given-names>
</name>
<xref ref-type="aff" rid="aff1">
<sup>1</sup>
</xref>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Methodology" vocab-term-identifier="https://credit.niso.org/contributor-roles/methodology/">Methodology</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Writing &#x2013; review &#x26; editing" vocab-term-identifier="https://credit.niso.org/contributor-roles/Writing - review &#x26; editing/">Writing - review and editing</role>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Wang</surname>
<given-names>Xujing</given-names>
</name>
<xref ref-type="aff" rid="aff3">
<sup>3</sup>
</xref>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Formal analysis" vocab-term-identifier="https://credit.niso.org/contributor-roles/formal-analysis/">Formal Analysis</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Validation" vocab-term-identifier="https://credit.niso.org/contributor-roles/validation/">Validation</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Visualization" vocab-term-identifier="https://credit.niso.org/contributor-roles/visualization/">Visualization</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Writing &#x2013; original draft" vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-original-draft/">Writing - original draft</role>
</contrib>
<contrib contrib-type="author" corresp="yes">
<name>
<surname>Xia</surname>
<given-names>Minghui</given-names>
</name>
<xref ref-type="aff" rid="aff3">
<sup>3</sup>
</xref>
<xref ref-type="corresp" rid="c001">&#x2a;</xref>
<uri xlink:href="https://loop.frontiersin.org/people/3254563"/>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Data curation" vocab-term-identifier="https://credit.niso.org/contributor-roles/data-curation/">Data curation</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Formal analysis" vocab-term-identifier="https://credit.niso.org/contributor-roles/formal-analysis/">Formal Analysis</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Writing &#x2013; original draft" vocab-term-identifier="https://credit.niso.org/contributor-roles/writing-original-draft/">Writing - original draft</role>
</contrib>
<contrib contrib-type="author">
<name>
<surname>Wang</surname>
<given-names>Ziren</given-names>
</name>
<xref ref-type="aff" rid="aff3">
<sup>3</sup>
</xref>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Investigation" vocab-term-identifier="https://credit.niso.org/contributor-roles/investigation/">Investigation</role>
<role vocab="credit" vocab-identifier="https://credit.niso.org/" vocab-term="Writing &#x2013; review &#x26; editing" vocab-term-identifier="https://credit.niso.org/contributor-roles/Writing - review &#x26; editing/">Writing - review and editing</role>
</contrib>
</contrib-group>
<aff id="aff1">
<label>1</label>
<institution>Digitalization Department, State Grid Fujian Electric Power Company</institution>, <city>Fuzhou</city>, <country country="CN">China</country>
</aff>
<aff id="aff2">
<label>2</label>
<institution>Economic and Technical Research Institute, State Grid Fujian Electric Power Company</institution>, <city>Fuzhou</city>, <country country="CN">China</country>
</aff>
<aff id="aff3">
<label>3</label>
<institution>Department of Economics and Management, North China Electric Power University (Baoding)</institution>, <city>Baoding</city>, <country country="CN">China</country>
</aff>
<author-notes>
<corresp id="c001">
<label>&#x2a;</label>Correspondence: Minghui Xia, <email xlink:href="mailto:2549621915@qq.com">2549621915@qq.com</email>
</corresp>
</author-notes>
<pub-date publication-format="electronic" date-type="pub" iso-8601-date="2026-01-07">
<day>07</day>
<month>01</month>
<year>2026</year>
</pub-date>
<pub-date publication-format="electronic" date-type="collection">
<year>2025</year>
</pub-date>
<volume>6</volume>
<elocation-id>1732098</elocation-id>
<history>
<date date-type="received">
<day>25</day>
<month>10</month>
<year>2025</year>
</date>
<date date-type="rev-recd">
<day>23</day>
<month>11</month>
<year>2025</year>
</date>
<date date-type="accepted">
<day>11</day>
<month>12</month>
<year>2025</year>
</date>
</history>
<permissions>
<copyright-statement>Copyright &#xa9; 2026 Chen, Tang, Wu, Wang, Xia and Wang.</copyright-statement>
<copyright-year>2026</copyright-year>
<copyright-holder>Chen, Tang, Wu, Wang, Xia and Wang</copyright-holder>
<license>
<ali:license_ref start_date="2026-01-07">https://creativecommons.org/licenses/by/4.0/</ali:license_ref>
<license-p>This is an open-access article distributed under the terms of the <ext-link ext-link-type="uri" xlink:href="https://creativecommons.org/licenses/by/4.0/">Creative Commons Attribution License (CC BY)</ext-link>. The use, distribution or reproduction in other forums is permitted, provided the original author(s) and the copyright owner(s) are credited and that the original publication in this journal is cited, in accordance with accepted academic practice. No use, distribution or reproduction is permitted which does not comply with these terms.</license-p>
</license>
</permissions>
<abstract>
<p>With the rapid advancement of digital transformation, enterprises face escalating challenges in cloud resource allocation due to dynamic workloads and substantial capital investments. Existing forecasting models often overlook the impact of corporate digital maturity, leading to suboptimal investment decisions and resource inefficiencies. This study proposes an integrated framework combining an ARIMAX forecasting model with a multi-constraint optimization approach. We incorporate a quantified Digital Transformation Index (DTI) as an exogenous variable and develop a cost-minimization investment model under constraints including resource gaps, leasing ratios, alert thresholds, and budget limits. Simulation experiments using Alibaba Cloud cluster data demonstrate that the proposed model achieves a CPU load prediction error (MAPE) of less than 5%, with a statistically significant DTI coefficient (p &#x3c; 0.01). The optimal investment strategy utilized 93.67% of a $2.22 million budget, achieving a leasing ratio below 45% while maintaining a 67% resource utilization safety threshold. We employed Mean Absolute Percentage Error (MAPE) for forecasting accuracy and Net Present Value (NPV) for cost evaluation, selected for their relevance to operational and financial performance in cloud resource management.</p>
</abstract>
<kwd-group>
<kwd>ARIMAX model</kwd>
<kwd>cloud resource forecasting</kwd>
<kwd>digital transformation</kwd>
<kwd>decision support systems</kwd>
<kwd>optimization techniques</kwd>
</kwd-group>
<funding-group>
<award-group id="gs1">
<funding-source id="sp1">
<institution-wrap>
<institution>State Grid Fujian Electric Power Company</institution>
<institution-id institution-id-type="doi" vocab="open-funder-registry" vocab-identifier="10.13039/open_funder_registry">10.13039/100017221</institution-id>
</institution-wrap>
</funding-source>
<award-id rid="sp1">52130N24000U</award-id>
</award-group>
<funding-statement>The author(s) declared that financial support was received for this work and/or its publication. This research was funded by Economic and Technology Research Institute of State Grid Fujian Electric Power Company, grant number 52130N24000U.</funding-statement>
</funding-group>
<counts>
<fig-count count="13"/>
<table-count count="16"/>
<equation-count count="17"/>
<ref-count count="28"/>
<page-count count="18"/>
</counts>
<custom-meta-group>
<custom-meta>
<meta-name>section-at-acceptance</meta-name>
<meta-value>IoT and Sensor Networks</meta-value>
</custom-meta>
</custom-meta-group>
</article-meta>
</front>
<body>
<sec sec-type="intro" id="s1">
<label>1</label>
<title>Introduction</title>
<p>With the rapid advancement of digital transformation, enterprises are actively adopting cloud technologies to transform their production, operations, and management processes. The exponential growth of business data has led to escalating pressure on cloud platforms, pushing resource allocation to the point of saturation. Simultaneously, cloud infrastructure construction requires substantial capital investment. Without scientific planning, unplanned expansion may result in compromised quality and financial waste. Therefore, systematic investigation of cloud resource load forecasting techniques and optimization of investment strategies are critical for enhancing operational efficiency and achieving sustainable development.</p>
<p>Existing studies have explored the impact of digital transformation. For instance, <xref ref-type="bibr" rid="B15">Pan et al. (2025)</xref> demonstrated that digital transformation significantly enhances corporate productivity, particularly in state-owned enterprises and the central and eastern regions of China (<xref ref-type="bibr" rid="B15">Pan and Hu, 2025</xref>). <xref ref-type="bibr" rid="B22">Xing et al. (2025)</xref> revealed varying sensitivities to pricing and data service benefits among manufacturing participants in industrial internet platforms (<xref ref-type="bibr" rid="B22">Xing et al., 2025</xref>). <xref ref-type="bibr" rid="B6">Li (2025)</xref> emphasized that developing digital management systems is key to gaining competitive advantages in the era of IoT and telematics (<xref ref-type="bibr" rid="B6">Li, 2025</xref>). These findings underscore the profound influence of digital transformation on modern enterprises&#x2019; operational frameworks.</p>
<p>In resource forecasting, scholars have explored a variety of prediction techniques and models, which are mainly divided into two categories: time series analysis and machine learning. Time series methods, such as the ARIMA model and exponential smoothing, excel at capturing the linear trends and periodic characteristics of cloud resource utilization, making them particularly suitable for scenarios with abundant historical data and stable operational patterns. For example, Calheiros et al. achieved 91% accuracy in predicting web server loads using ARIMA, validating its effectiveness in cloud environments (<xref ref-type="bibr" rid="B1">Calheiros et al., 2015</xref>). Mi et al. applied quadratic exponential smoothing to predict the number of user requests, and then estimated virtual machine resource requirements (<xref ref-type="bibr" rid="B13">Mi et al., 2011</xref>). Machine learning approaches, such as SVM and LSTM, demonstrate significant advantages in handling large-scale, high-dimensional cloud resource data by automatically extracting complex nonlinear relationships, often yielding higher prediction accuracy. For instance, Gao et al. designed a dynamic resource scheduling scheme based on the ant colony algorithm, optimizing the load balancing and energy consumption management in cloud computing platform (<xref ref-type="bibr" rid="B2">Gao, 2015</xref>). Additionally, Zhang et al. leveraged a deep belief network (DBN) for cloud resource demand prediction, improving accuracy through input-output relationship analysis (<xref ref-type="bibr" rid="B26">Zhang et al., 2017</xref>).</p>
<p>In the field of investment optimization, Zhang systematically categorized macro-asset allocation theories into five types: (1) return-risk balance, (2) return-only, (3) risk-only, (4) investor utility maximization, and (5) integration of economic cycles with subjective judgment (<xref ref-type="bibr" rid="B25">Zhang and Zhang, 2017</xref>). The study further analyzed the characteristics and limitations of each category. From the perspective of financial management and cost-effectiveness, Li compared four equipment allocation models&#x2014;self-owned procurement, financial leasing, operating leasing, and hybrid leasing&#x2014;providing actionable insights for enterprises in cost control, risk mitigation, and decision optimization (<xref ref-type="bibr" rid="B5">Li, 2022</xref>). Additionally, Liu et al. explored optimal choices among financing leases, operating leases, and outright purchases in fixed-asset allocation by constructing cash flow models (<xref ref-type="bibr" rid="B10">Liu et al., 2010</xref>).</p>
<p>Existing studies indicate that corporate digital maturity significantly influences cloud platform development and exhibits a strong correlation with cloud resource demand. However, current literature on cloud resource allocation has predominantly overlooked this linkage, resulting in a critical research gap in cloud infrastructure investment strategies. To bridge this gap, our study incorporates corporate digital maturity as a critical exogenous variable into a cloud resource demand forecasting model. Furthermore, by analyzing business growth trends and existing cloud resource configurations, we comprehensively investigate investment decision optimization during cloud platform upgrades, with a focus on comparing the economic viability of third-party cloud service leasing versus self-built data centers.</p>
<sec id="s1-1">
<label>1.1</label>
<title>Contributions of this study are threefold:</title>
<p>
<list list-type="bullet">
<list-item>
<p>Theoretical: We introduce a multidimensional Digital Transformation Index (DTI) as an exogenous variable in cloud resource forecasting, bridging the gap between digital maturity and IT resource planning.</p>
</list-item>
<list-item>
<p>Methodological: We develop an integrated ARIMAX-predictive optimization framework that combines forecasting with multi-constraint investment decision-making.</p>
</list-item>
<list-item>
<p>Practical: The model provides enterprises with a scalable, budget-aware investment strategy for cloud platformexpansion, validated through real-world simulation.</p>
</list-item>
</list>
</p>
</sec>
</sec>
<sec id="s2">
<label>2</label>
<title>Related works</title>
<p>The existing body of research on cloud resource management can be broadly categorized into two interconnected streams: (1) predictive modeling of resource demand, and (2) optimization of investment and allocation strategies. A review of recent literature (2020&#x2013;2025) reveals distinct evolutionary trends and prevailing research gaps in both domains.</p>
<sec id="s2-1">
<label>2.1</label>
<title>Advancements in cloud resource forecasting</title>
<p>Recent studies in cloud resource forecasting demonstrate a clear paradigm shift from traditional statistical methods towards sophisticated deep learning, hybrid optimization, and privacy-preserving computational frameworks. For instance, Wang et al. proposed a BO-LSTM model that integrates Bayesian optimization with marketing variables to enhance the accuracy of point forecasts (<xref ref-type="bibr" rid="B20">Wang and Chen, 2025</xref>). Similarly, Sania Malik et al. developed a hybrid FLNN model (FLGAPSONN) that combines Genetic Algorithm and Particle Swarm Optimization, enabling concurrently prediction of multiple resource metrics (e.g., CPU, memory) and demonstrating superior performance on Google cluster traces (<xref ref-type="bibr" rid="B12">Malik et al., 2022</xref>). In the realm of data privacy, Stefanidis et al. designed MulticloudFL, a federated learning framework that supports accurate distributed predictions without centralizing sensitive data (<xref ref-type="bibr" rid="B17">Stefanidis et al., 2023</xref>). Other innovations include the use of spiking neural networks (MASNN) by Karpagam et al. to capture temporal symmetries in resource usage, and the DimAug-TimesFM approach by Yang et al., which employs data augmentation to improve the robustness of long-horizon forecasts under conditions of data scarcity (<xref ref-type="bibr" rid="B4">Karpagam and Kanniappan, 2025</xref>; <xref ref-type="bibr" rid="B24">Yang et al., 2025</xref>).</p>
<p>While these studies represent significant progress in model architecture, optimization algorithms, and learning paradigms, they predominantly focus on technical and data-driven factors, largely overlooking the intrinsic impact of corporate digital maturity&#x2014;a critical business driver that systematically influences IT resource consumption patterns. A summary of representative forecasting studies is provided in the upper part of <xref ref-type="table" rid="T1">Table 1</xref>. This oversight establishes a salient research gap, which our study aims to address by introducing a quantified Digital Transformation Index (DTI) as an exogenous predictive variable.</p>
<table-wrap id="T1" position="float">
<label>TABLE 1</label>
<caption>
<p>Research summary of forecasting and investment models.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Domain</th>
<th align="center">Study</th>
<th align="center">Core contribution</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td rowspan="5" align="center">Cloud resource forecasting</td>
<td align="center">
<xref ref-type="bibr" rid="B19">Wang (2025)</xref>
</td>
<td align="center">BO-LSTM model with Bayesian optimization for point forecasting</td>
</tr>
<tr>
<td align="center">
<xref ref-type="bibr" rid="B12">Malik et al. (2022)</xref>
</td>
<td align="center">FLGAPSONN hybrid model for multi-resource prediction</td>
</tr>
<tr>
<td align="center">
<xref ref-type="bibr" rid="B17">Stefanidis et al. (2023)</xref>
</td>
<td align="center">MulticloudFL for privacy-preserving federated forecasting</td>
</tr>
<tr>
<td align="center">
<xref ref-type="bibr" rid="B4">Karpagam and Kanniappan (2025)</xref>
</td>
<td align="center">MASNN using spiking neural networks for temporal patterns</td>
</tr>
<tr>
<td align="center">
<xref ref-type="bibr" rid="B24">Yang et al. (2025)</xref>
</td>
<td align="center">DimAug-TimesFM for robust few-shot long-horizon forecasting</td>
</tr>
<tr>
<td rowspan="4" align="center">Investment &#x26; allocation</td>
<td align="center">
<xref ref-type="bibr" rid="B16">Serban and Dedu (2025)</xref>
</td>
<td align="center">MDE model for multi-objective portfolio</td>
</tr>
<tr>
<td align="center">
<xref ref-type="bibr" rid="B14">Nalewaik (2025)</xref>
</td>
<td align="center">Advocates MCDM for capital projects beyond pure cost</td>
</tr>
<tr>
<td align="center">
<xref ref-type="bibr" rid="B18">Su (2020)</xref>
</td>
<td align="center">&#x201c;Predict-then-optimize&#x201d; with GARCH and dynamic allocation</td>
</tr>
<tr>
<td align="center">
<xref ref-type="bibr" rid="B9">Liu (2023)</xref>
</td>
<td align="center">Synergistic configuration of different capital forms</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="s2-2">
<label>2.2</label>
<title>Evolution of investment and resource allocation models</title>
<p>Parallel developments in investment optimization and resource allocation reflect a trend toward multi-objective, predictive, and synergistic decision-making frameworks. Serban and Dedu introduced a Mean-Deviation-Entropy (MDE) model for portfolio optimization, simultaneously balancing return, risk, and diversification&#x2014;exemplifying the shift from single-to multi-criteria optimization (<xref ref-type="bibr" rid="B16">Serban and Dedu, 2025</xref>). Echoing this trend, Nalewaik (2025) emphasized the need in capital project planning to move beyond traditional cost-benefit analysis by integrating social value and resilience through Multi-Criteria Decision-Making (MCDM) methods (<xref ref-type="bibr" rid="B14">Nalewaik, 2025</xref>). The integration of forecasting into dynamic allocation is another key trend. Su, for example, utilized GARCH models for financial forecasting and developed dynamic weight allocation algorithms to track the efficient frontier in real-time, establishing a &#x201c;predict-then-optimize&#x201d; methodological paradigm (<xref ref-type="bibr" rid="B18">Su, 2020</xref>). Furthermore, the concept of synergistic resource configuration has gained traction. Liu, in the context of state-owned capital allocation, highlighted that optimal resource deployment requires the integration of different capital forms and the coordination between incremental and capital, a principle that profoundly informs the hybrid &#x201c;lease-or-build&#x201d; model in cloud resource strategy (<xref ref-type="bibr" rid="B9">Liu, 2023</xref>). Key contributions in this domain are summarized in the lower part of <xref ref-type="table" rid="T1">Table 1</xref>.</p>
<p>Despite these theoretical and methodological advances, a significant synthesis is lacking. Specifically, there remains no unified model that seamlessly integrates demand forecasting (e.g., as in Su&#x2019;s approach), multi-objective trade-offs (e.g., following Serban and Nalewaik&#x2019;s frameworks), and synergistic resource configuration (e.g., informed by Liu&#x2019;s concept) to systematically address the core cloud investment dilemma of &#x201c;leasing versus self-building&#x201d;.</p>
</sec>
</sec>
<sec sec-type="methods" id="s3">
<label>3</label>
<title>Methods</title>
<p>This study proposes an integrated framework for cloud resource demand forecasting and investment optimization, comprising four main steps:<list list-type="simple">
<list-item>
<p>&#x2022; Quantify the enterprise&#x2019;s digital maturity to compute a Digital Transformation Index (DTI).</p>
</list-item>
<list-item>
<p>&#x2022; Forecast dynamic cloud resource demand using an ARIMAX model with the DTI as an exogenous variable.</p>
</list-item>
<list-item>
<p>&#x2022; Diagnose real-time resource utilization and trigger optimization alerts against predictive thresholds.</p>
</list-item>
<list-item>
<p>&#x2022; Formulate and solve a constrained optimization model to determine the cost-minimal investment decision.</p>
</list-item>
</list>
</p>
<p>The overall workflow is illustrated in <xref ref-type="fig" rid="F1">Figure 1</xref>.</p>
<fig id="F1" position="float">
<label>FIGURE 1</label>
<caption>
<p>Model operation flowchart.</p>
</caption>
<graphic xlink:href="frcmn-06-1732098-g001.tif">
<alt-text content-type="machine-generated">Flowchart outlining a digital transformation process starting with quantifying the enterprise digital transformation index. It then forecasts cloud resource demand, monitors and triggers scaling against thresholds, and asks if criteria are met. If yes, it establishes a minimum-cost decision model considering resource gaps, alert thresholds, leased ratios, and budget limitations, to generate an optimal investment strategy. Ends with the &#x22;End&#x22; node.</alt-text>
</graphic>
</fig>
<sec id="s3-1">
<label>3.1</label>
<title>Digital maturity quantification and exogenous variable design for ARIMAX modeling</title>
<p>Enterprise cloud resources exhibit a strong correlation with digital transformation progress within organizations. Critical resource fluctuations&#x2014;such as in computing power, storage, and bandwidth&#x2014;are closely tied to advancements in enterprise digital maturity (<xref ref-type="bibr" rid="B14">Zhong, 2018</xref>). Furthermore, digital transformation necessitates operational realignment of business processes and significantly reshapes cloud resource allocation strategies and usage patterns.</p>
<sec id="s3-1-1">
<label>3.1.1</label>
<title>Digital maturity assessment framework</title>
<p>To assess enterprise digital maturity, this study introduces a four-dimensional evaluation framework, detailed in <xref ref-type="table" rid="T2">Tables 2</xref>, <xref ref-type="table" rid="T3">3</xref>. The framework is structured around four core dimensions&#x2014;technological application, data capability, business integration, and organizational adaptation&#x2014;from which 12 quantifiable secondary indicators are derived. The Analytic Hierarchy Process (AHP) and expert scoring methods are applied to assign weights to these sub-indicators, enabling the calculation of a composite Digital Transformation Index (DTI). The DTI is calibrated against an industry benchmark of 100, with values above this threshold indicating superior digital maturity in enterprises.</p>
<table-wrap id="T2" position="float">
<label>TABLE 2</label>
<caption>
<p>Enterprise digital maturity evaluation indicator system.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Primary dimension</th>
<th align="center">Secondary indicator</th>
<th align="center">Indicator description</th>
<th align="center">Weight</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td rowspan="3" align="center">Technical infrastructure (B1)</td>
<td align="center">Cloud computing<break/>Investment ratio (C1)</td>
<td align="center">Cloud service procurement cost/Total IT budget &#xd7; 100%</td>
<td align="center">0.35</td>
</tr>
<tr>
<td align="center">Server virtualization rate (C2)</td>
<td align="center">Number of virtual servers/Total physical servers &#xd7; 100%</td>
<td align="center">0.25</td>
</tr>
<tr>
<td align="center">Proportion of cloud-native<break/>Applications (C3)</td>
<td align="center">Number of applications based on microservices or container technology/Total applications</td>
<td align="center">0.40</td>
</tr>
<tr>
<td rowspan="3" align="center">Data-driven capability (B2)</td>
<td align="center">Data middle platform coverage (C4)</td>
<td align="center">Number of business systems connected to the data middle platform/Total systems</td>
<td align="center">0.30</td>
</tr>
<tr>
<td align="center">Real-time data processing volume (C5)</td>
<td align="center">Daily average real-time API calls (&#xd7;10<sup>4</sup> times)</td>
<td align="center">0.35</td>
</tr>
<tr>
<td align="center">Data storage growth Rate(C6)</td>
<td align="center">Monthly average new data storage volume (TB)</td>
<td align="center">0.35</td>
</tr>
<tr>
<td rowspan="3" align="center">Business digital<break/>Integration (B3)</td>
<td align="center">Online transaction<break/>Ratio (C7)</td>
<td align="center">Online order volume/Total order volume &#xd7; 100%</td>
<td align="center">0.40</td>
</tr>
<tr>
<td align="center">Remote work<break/>Penetration Rate(C8)</td>
<td align="center">Number of employees using cloud collaboration tools/Total employees &#xd7; 100%</td>
<td align="center">0.30</td>
</tr>
<tr>
<td align="center">Intelligent system<break/>Deployment count (C9)</td>
<td align="center">Number of AI or BI-powered digital tools deployed</td>
<td align="center">0.30</td>
</tr>
<tr>
<td rowspan="3" align="center">Organizational<break/>Adaptability (B4)</td>
<td align="center">Digitally skilled<break/>Employee Ratio (C10)</td>
<td align="center">Number of certified digital talents/Total employees &#xd7; 100%</td>
<td align="center">0.50</td>
</tr>
<tr>
<td align="center">Agile development team ratio (C11)</td>
<td align="center">Number of teams adopting DevOps or Scrum/Total teams</td>
<td align="center">0.30</td>
</tr>
<tr>
<td align="center">Maturity of digital<break/>Decision-making<break/>Systems (C12)</td>
<td align="center">Expert rating (1&#x2013;5 points, 5 being the highest)</td>
<td align="center">0.20</td>
</tr>
</tbody>
</table>
</table-wrap>
<table-wrap id="T3" position="float">
<label>TABLE 3</label>
<caption>
<p>Primary dimension weight allocation.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Primary dimension</th>
<th align="center">Weight</th>
<th align="center">Rationable</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">Technical infrastructure (B1)</td>
<td align="center">0.35</td>
<td align="center">Physical foundation for digital transformation, directly determines cloud resource capacity</td>
</tr>
<tr>
<td align="center">Data-driven capability (B2)</td>
<td align="center">0.30</td>
<td align="center">Data as core digital asset, drives business decisions and resource demand</td>
</tr>
<tr>
<td align="center">Business digital integration (B3)</td>
<td align="center">0.25</td>
<td align="center">Reflects digital penetration into core operations, directly impacts resource volatility</td>
</tr>
<tr>
<td align="center">Organizational adaptability (B4)</td>
<td align="center">0.10</td>
<td align="center">Supporting capability with indirect influence on resource requirements</td>
</tr>
</tbody>
</table>
</table-wrap>
<sec id="s3-1-1-1">
<label>3.1.1.1</label>
<title>Indicator selection justification</title>
<p>Each secondary indicator in the DTI framework was selected based on its established linkage to cloud resource demand, as supported by prior IT and digital transformation literature. The justifications are organized by primary dimension:<list list-type="simple">
<list-item>
<p>&#x2022; Technical Infrastructure (B1): Indicators C1-C3 directly reflect the scale, modernization level, and architectural paradigm of the IT environment. Higher investment in cloud computing (C1), server virtualization (C2), and cloud-native applications (C3) is intrinsically linked to increased and more dynamic consumption of computing, storage, and network resources.</p>
</list-item>
<list-item>
<p>&#x2022; Data-Driven Capability (B2): Indicators C4-C6 measure the intensity of data utilization. Broader data middle platform coverage (C4), higher real-time data processing volumes (C5), and accelerated data storage growth (C6) are key drivers demanding robust, scalable storage, memory, and computing power.</p>
</list-item>
<list-item>
<p>&#x2022; Business Digital Integration (B3): Indicators C7-C9 quantify the digitization of core business operations. An increasing online transaction ratio (C7), remote work penetration (C8), and deployment of intelligent systems (C9) generate sustained and variable loads on cloud platforms by translating business activity directly into IT workload.</p>
</list-item>
<list-item>
<p>&#x2022; Organizational Adaptability (B4): Indicators C10-C12, while having a more indirect influence, capture the enterprise&#x2019;s capacity for continuous digital innovation. A higher ratio of digitally skilled employees (C10) and agile teams (C11), coupled with mature digital decision-making systems (C12), fosters an environment where new digital initiatives are rapidly developed and deployed, thereby driving evolving and less predictable resource demands over time.</p>
</list-item>
</list>
</p>
</sec>
<sec id="s3-1-1-2">
<label>3.1.1.2</label>
<title>AHP-expert scoring method</title>
<p>The weights for both primary and secondary indicators were determined through an integrated AHP-Expert Scoring Method to ensure a rational and consensus-driven weighting scheme. The procedure was conducted as follows:<list list-type="simple">
<list-item>
<p>&#x2022; Expert Panel Formation: A panel of 15 experts was assembled, consisting of 5 senior IT architects, 5 digital transformation strategists, and 5 enterprise cloud solution managers, each with over 10&#xa0;years of relevant industry experience.</p>
</list-item>
<list-item>
<p>&#x2022; Pairwise Comparisons: Each expert performed pairwise comparisons for indicators at the same hierarchical level (e.g., B1 vs. B2; C1 vs. C2 under B1) using the standard Saaty&#x2019;s 1&#x2013;9 scale.</p>
</list-item>
<list-item>
<p>&#x2022; Consistency Verification: The consistency ratio (CR) was computed for each expert&#x2019;s judgment matrix. Matrices with a CR &#x3e; 0.1 were considered inconsistent and were returned to the respective expert for reassessment, thereby ensuring the logical reliability of individual inputs.</p>
</list-item>
<list-item>
<p>&#x2022; Weight Aggregation and Calculation: The validated individual judgment matrices were aggregated into a final group matrix using the geometric mean method. The final weights for each indicator, as shown in <xref ref-type="table" rid="T1">Tables 1</xref>, <xref ref-type="table" rid="T2">2</xref>, were obtained by calculating the principal eigenvector of the aggregated matrix. All resulting weights exhibited a high level of consistency (CR &#x3c; 0.1), confirming the reliability of the expert judgments and the overall weighting scheme.</p>
</list-item>
</list>
</p>
</sec>
</sec>
<sec id="s3-1-2">
<label>3.1.2</label>
<title>Exogenous variable generation for ARIMAX modeling</title>
<p>The composite score for digital transformation maturity is derived using <xref ref-type="disp-formula" rid="e1">Equation 1</xref>:<disp-formula id="e1">
<mml:math id="m1">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>D</mml:mi>
<mml:mi>T</mml:mi>
<mml:mi>I</mml:mi>
</mml:mrow>
<mml:mi>t</mml:mi>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munderover>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>1</mml:mn>
</mml:mrow>
<mml:mn>4</mml:mn>
</mml:munderover>
</mml:mstyle>
<mml:msub>
<mml:mi>&#x3c9;</mml:mi>
<mml:mi>k</mml:mi>
</mml:msub>
<mml:mstyle displaystyle="true">
<mml:munder>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mo>&#x2208;</mml:mo>
<mml:msub>
<mml:mi>B</mml:mi>
<mml:mi>k</mml:mi>
</mml:msub>
</mml:mrow>
</mml:munder>
</mml:mstyle>
<mml:msub>
<mml:mi>&#x3c9;</mml:mi>
<mml:mrow>
<mml:mi>k</mml:mi>
<mml:mi>i</mml:mi>
</mml:mrow>
</mml:msub>
<mml:msub>
<mml:mi>x</mml:mi>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:math>
<label>(1)</label>
</disp-formula>where.<list list-type="simple">
<list-item>
<p>
<inline-formula id="inf1">
<mml:math id="m2">
<mml:mrow>
<mml:msub>
<mml:mtext>DTI</mml:mtext>
<mml:mi mathvariant="normal">t</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Composite score of digital transformation maturity at time t.</p>
</list-item>
<list-item>
<p>
<inline-formula id="inf2">
<mml:math id="m3">
<mml:mrow>
<mml:msub>
<mml:mi mathvariant="normal">&#x3c9;</mml:mi>
<mml:mi mathvariant="normal">k</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Weight of the k-th primary dimension (k &#x3d; 1,2,3,4).</p>
</list-item>
<list-item>
<p>
<inline-formula id="inf3">
<mml:math id="m4">
<mml:mrow>
<mml:msub>
<mml:mi mathvariant="normal">&#x3c9;</mml:mi>
<mml:mtext>ki</mml:mtext>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Weight of the i-th secondary indicator under the k-th primary dimension.</p>
</list-item>
<list-item>
<p>
<inline-formula id="inf4">
<mml:math id="m5">
<mml:mrow>
<mml:msub>
<mml:mi mathvariant="normal">x</mml:mi>
<mml:mtext>it</mml:mtext>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Normalized score of the i-th indicator at time t, scaled to the interval [0,100].</p>
</list-item>
<list-item>
<p>
<inline-formula id="inf5">
<mml:math id="m6">
<mml:mrow>
<mml:msub>
<mml:mi mathvariant="normal">B</mml:mi>
<mml:mi mathvariant="normal">k</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Set of secondary indicators belonging to the k-th primary dimension.</p>
</list-item>
</list>
</p>
<p>For the raw score <inline-formula id="inf6">
<mml:math id="m7">
<mml:mrow>
<mml:mover accent="true">
<mml:msub>
<mml:mi mathvariant="normal">x</mml:mi>
<mml:mtext>it</mml:mtext>
</mml:msub>
<mml:mo>&#x223c;</mml:mo>
</mml:mover>
</mml:mrow>
</mml:math>
</inline-formula> of each specific indicator, Z-score normalization or linear transformation is applied to rescale it into the [0, 100] interval.</p>
<sec id="s3-1-2-1">
<label>3.1.2.1</label>
<title>Calculation example</title>
<p>For instance, consider a hypothetical enterprise at a specific time <italic>t</italic>. Its normalized scores <inline-formula id="inf7">
<mml:math id="m8">
<mml:mrow>
<mml:msub>
<mml:mi>x</mml:mi>
<mml:mrow>
<mml:mi>i</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula> and the predetermined weights are as follows:</p>
<p>B1(Weight &#x3c9;<sub>1</sub> &#x3d; 0.35): C1 &#x3d; 70, C2 &#x3d; 60, C3 &#x3d; 50.</p>
<p>B2(Weight &#x3c9;<sub>2</sub> &#x3d; 0.30): C4 &#x3d; 40, C5 &#x3d; 55, C6 &#x3d; 65.</p>
<p>B3(Weight &#x3c9;<sub>3</sub> &#x3d; 0.25): C7 &#x3d; 80, C8 &#x3d; 30, C9 &#x3d; 20.</p>
<p>B4(Weight &#x3c9;<sub>4</sub> &#x3d; 0.10): C10 &#x3d; 50, C11 &#x3d; 40, C12 &#x3d; 60.</p>
<p>The DTI score is calculated using <xref ref-type="disp-formula" rid="e2">Equation 2</xref>:<disp-formula id="e2">
<mml:math id="m9">
<mml:mrow>
<mml:mtable columnalign="center">
<mml:mtr>
<mml:mtd>
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>D</mml:mi>
<mml:mi>I</mml:mi>
<mml:mi>T</mml:mi>
</mml:mrow>
<mml:mi>t</mml:mi>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.35</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mn>0.35</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mn>70</mml:mn>
<mml:mo>&#x2b;</mml:mo>
<mml:mn>0.25</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mn>60</mml:mn>
<mml:mo>&#x2b;</mml:mo>
<mml:mn>0.40</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mn>50</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x2b;</mml:mo>
<mml:mn>0.30</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mn>0.30</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mn>40</mml:mn>
<mml:mo>&#x2b;</mml:mo>
<mml:mn>0.35</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mn>55</mml:mn>
<mml:mo>&#x2b;</mml:mo>
<mml:mn>0.35</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mn>65</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x2b;</mml:mo>
</mml:mrow>
</mml:mtd>
</mml:mtr>
<mml:mtr>
<mml:mtd>
<mml:mrow>
<mml:mn>0.25</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mn>0.40</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mn>80</mml:mn>
<mml:mo>&#x2b;</mml:mo>
<mml:mn>0.30</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mn>30</mml:mn>
<mml:mo>&#x2b;</mml:mo>
<mml:mn>0.30</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mn>20</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x2b;</mml:mo>
<mml:mn>0.10</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mn>0.50</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mn>50</mml:mn>
<mml:mo>&#x2b;</mml:mo>
<mml:mn>0.30</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mn>40</mml:mn>
<mml:mo>&#x2b;</mml:mo>
<mml:mn>0.20</mml:mn>
<mml:mo>&#xd7;</mml:mo>
<mml:mn>60</mml:mn>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>54</mml:mn>
</mml:mrow>
</mml:mtd>
</mml:mtr>
</mml:mtable>
</mml:mrow>
</mml:math>
<label>(2)</label>
</disp-formula>
</p>
</sec>
<sec id="s3-1-2-2">
<label>3.1.2.2</label>
<title>Time-Series Dataset Generation</title>
<p>The above process generates a synchronized time-series dataset, given by <xref ref-type="disp-formula" rid="e3">Equation 3</xref>:<disp-formula id="e3">
<mml:math id="m10">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mfenced open="{" close="" separators="|">
<mml:mrow>
<mml:mi>D</mml:mi>
<mml:mi>T</mml:mi>
<mml:mi>I</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mi>t</mml:mi>
</mml:msub>
<mml:mrow>
<mml:mfenced open="" close="}" separators="|">
<mml:mrow>
<mml:mrow>
<mml:mo>,</mml:mo>
<mml:mi>t</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>1</mml:mn>
<mml:mo>,</mml:mo>
<mml:mn>2</mml:mn>
<mml:mo>,</mml:mo>
<mml:mo>.</mml:mo>
<mml:mo>.</mml:mo>
<mml:mo>.</mml:mo>
<mml:mo>,</mml:mo>
<mml:mi>T</mml:mi>
</mml:mrow>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:math>
<label>(3)</label>
</disp-formula>
</p>
<p>This dataset aligns temporally with cloud resource demand data to support subsequent analytical modeling.</p>
</sec>
</sec>
</sec>
<sec id="s3-2">
<label>3.2</label>
<title>Dynamic cloud resource demand forecasting with integrated digital maturity metrics</title>
<p>In the process of enterprise digital transformation, changes in cloud resource demand are jointly influenced by historical usage patterns and digital operational capabilities. This study employs an ARIMAX model, incorporating quantified enterprise digital transformation indicators as exogenous variables, to establish an integrated forecasting framework that combines technological development and business needs. Unlike the ARIMA model, which relies solely on historical data, the ARIMAX model integrates the DTI, enabling it to capture cloud resource demand fluctuations in complex scenarios (e.g., traffic peaks and resource auto-scaling) more accurately. This approach significantly enhances the capability of the model to analyze and predict dynamic cloud resource demands.</p>
<sec id="s3-2-1">
<label>3.2.1</label>
<title>Basic principles of the model</title>
<p>The ARIMAX model extends the traditional ARIMA framework by incorporating exogenous variables. The general form of an ARIMAX (<italic>p, d, q</italic>) model is given by <xref ref-type="disp-formula" rid="e4">Equation 4</xref>:<disp-formula id="e4">
<mml:math id="m11">
<mml:mrow>
<mml:mo>&#x2205;</mml:mo>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>B</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:msup>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>B</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mi>d</mml:mi>
</mml:msup>
<mml:msub>
<mml:mi>y</mml:mi>
<mml:mi>t</mml:mi>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mi>&#x3b8;</mml:mi>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>B</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:msub>
<mml:mi>&#x3f5;</mml:mi>
<mml:mi>t</mml:mi>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:mstyle displaystyle="true">
<mml:munderover>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mi>m</mml:mi>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0</mml:mn>
</mml:mrow>
<mml:mi>M</mml:mi>
</mml:munderover>
</mml:mstyle>
<mml:msub>
<mml:mi>&#x3b2;</mml:mi>
<mml:mi>m</mml:mi>
</mml:msub>
<mml:msub>
<mml:mi>x</mml:mi>
<mml:mrow>
<mml:mi>t</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mi>&#x3f5;</mml:mi>
<mml:mi>t</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
<label>(4)</label>
</disp-formula>where.</p>
<p>
<inline-formula id="inf8">
<mml:math id="m12">
<mml:mrow>
<mml:msub>
<mml:mi>y</mml:mi>
<mml:mi>t</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula> denotes cloud resource demand metrics, such as CPU utilization, memory usage, or network traffic.</p>
<p>
<inline-formula id="inf9">
<mml:math id="m13">
<mml:mrow>
<mml:mo>&#x2205;</mml:mo>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>B</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:math>
</inline-formula> and <inline-formula id="inf10">
<mml:math id="m14">
<mml:mrow>
<mml:mi>&#x3b8;</mml:mi>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>B</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:math>
</inline-formula> represent the autoregressive and moving average polynomials, respectively.</p>
<p>
<italic>B</italic> denotes the backward shift operator.</p>
<p>
<inline-formula id="inf11">
<mml:math id="m15">
<mml:mrow>
<mml:mi>d</mml:mi>
</mml:mrow>
</mml:math>
</inline-formula> is the differencing order applied to achieve stationarity.</p>
<p>
<inline-formula id="inf12">
<mml:math id="m16">
<mml:mrow>
<mml:msub>
<mml:mi>&#x3f5;</mml:mi>
<mml:mi>t</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula> is a white noise sequence.</p>
<p>
<inline-formula id="inf13">
<mml:math id="m17">
<mml:mrow>
<mml:msub>
<mml:mi>x</mml:mi>
<mml:mrow>
<mml:mi>t</mml:mi>
<mml:mo>&#x2010;</mml:mo>
<mml:mi>m</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula> corresponds to the quantified enterprise digital transformation level, acting as the exogenous variable in this study.</p>
<p>
<inline-formula id="inf14">
<mml:math id="m18">
<mml:mrow>
<mml:msub>
<mml:mi>&#x3b2;</mml:mi>
<mml:mi>m</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula> denotes the coefficient for the exogenous variable lagged by m periods, reflecting the direction and magnitude of the impact of digital transformation on cloud resource demand.</p>
</sec>
<sec id="s3-2-2">
<label>3.2.2</label>
<title>Model construction process</title>
<sec id="s3-2-2-1">
<label>3.2.2.1</label>
<title>Step 1 stationarity test</title>
<p>The ARIMA model requires the time series data to be stationary. Typically, the Augmented Dickey-Fuller (ADF) test is employed to assess the stationarity of the cloud resource demand series {y<sub>t</sub>}. The test begins with the null hypothesis that the series is non-stationary (i.e., it contains a unit root). After computing the test statistic, it is compared against standard critical values. If the null hypothesis is rejected, the series is deemed stationary; otherwise, differencing is applied iteratively until stationarity is achieved. This process determines the optimal differencing order <italic>d</italic>.</p>
</sec>
<sec id="s3-2-2-2">
<label>3.2.2.2</label>
<title>Step 2 model order determination</title>
<p>For the stationary series, the Autocorrelation Function (ACF) and Partial Autocorrelation Function (PACF) plots were analyzed to tentatively identify the autoregressive order <italic>p</italic> and moving average order <italic>q</italic>. The ACF plot helps identify the influence of past values, while the PACF plot helps identify the direct effect of a specific lag. The following standard guidelines were followed:<list list-type="simple">
<list-item>
<p>&#x2022; A tailoring off ACF and a sharp cutoff in PACF after lag <italic>p</italic> suggest an AR(p) model.</p>
</list-item>
<list-item>
<p>&#x2022; A sharp cutoff in ACF after lag <italic>q</italic> and a tailoring off PACF suggest an MA(q) model.</p>
</list-item>
<list-item>
<p>&#x2022; If both ACF and PACF tail off, a mixed ARIMA (<italic>p, q</italic>) model is indicated.</p>
</list-item>
<list-item>
<p>&#x2022; The Akaike Information Criterion (AIC) was subsequently used to compare models with different (<italic>p, q</italic>) combinations, and the model with the lowest AIC was selected for its optimal balance of goodness-of-fit and parsimony.</p>
</list-item>
</list>The formulas for calculating ACF and PACF are given in <xref ref-type="disp-formula" rid="e5">Equations 5</xref>, <xref ref-type="disp-formula" rid="e6">6</xref>:<disp-formula id="e5">
<mml:math id="m19">
<mml:mrow>
<mml:mi>A</mml:mi>
<mml:mi>C</mml:mi>
<mml:mi>F</mml:mi>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x3d;</mml:mo>
<mml:msub>
<mml:mi>&#x3c1;</mml:mi>
<mml:mi>k</mml:mi>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mi>C</mml:mi>
<mml:mi>o</mml:mi>
<mml:mi>v</mml:mi>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:msub>
<mml:mi>y</mml:mi>
<mml:mi>t</mml:mi>
</mml:msub>
<mml:mo>,</mml:mo>
<mml:msub>
<mml:mi>y</mml:mi>
<mml:mrow>
<mml:mi>t</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
<mml:mrow>
<mml:mi>V</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>r</mml:mi>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:msub>
<mml:mi>y</mml:mi>
<mml:mi>t</mml:mi>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:mfrac>
</mml:mrow>
</mml:math>
<label>(5)</label>
</disp-formula>
<disp-formula id="e6">
<mml:math id="m20">
<mml:mrow>
<mml:mi>P</mml:mi>
<mml:mi>A</mml:mi>
<mml:mi>C</mml:mi>
<mml:mi>F</mml:mi>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>&#x3d;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mi>C</mml:mi>
<mml:mi>o</mml:mi>
<mml:mi>v</mml:mi>
<mml:mrow>
<mml:mfenced open="[" close="]" separators="|">
<mml:mrow>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:msub>
<mml:mi>z</mml:mi>
<mml:mi>t</mml:mi>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mover accent="true">
<mml:msub>
<mml:mi>z</mml:mi>
<mml:mi>t</mml:mi>
</mml:msub>
<mml:mo>&#xaf;</mml:mo>
</mml:mover>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
<mml:mo>,</mml:mo>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:msub>
<mml:mi>z</mml:mi>
<mml:mrow>
<mml:mi>t</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mover accent="true">
<mml:msub>
<mml:mi>z</mml:mi>
<mml:mrow>
<mml:mi>t</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#xaf;</mml:mo>
</mml:mover>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
<mml:mrow>
<mml:msqrt>
<mml:mrow>
<mml:mi>V</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>r</mml:mi>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:msub>
<mml:mi>z</mml:mi>
<mml:mi>t</mml:mi>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mover accent="true">
<mml:msub>
<mml:mi>z</mml:mi>
<mml:mi>t</mml:mi>
</mml:msub>
<mml:mo>&#xaf;</mml:mo>
</mml:mover>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:msqrt>
<mml:msqrt>
<mml:mrow>
<mml:mi>V</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>r</mml:mi>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:msub>
<mml:mi>z</mml:mi>
<mml:mrow>
<mml:mi>t</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:mover accent="true">
<mml:msub>
<mml:mi>z</mml:mi>
<mml:mrow>
<mml:mi>t</mml:mi>
<mml:mo>&#x2212;</mml:mo>
<mml:mi>k</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#xaf;</mml:mo>
</mml:mover>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:msqrt>
</mml:mrow>
</mml:mfrac>
</mml:mrow>
</mml:math>
<label>(6)</label>
</disp-formula>
</p>
</sec>
<sec id="s3-2-2-3">
<label>3.2.2.3</label>
<title>Step 3 model validation</title>
<p>After the initial model construction, the residual sequence is tested for white noise properties. This is assessed by examining the ACF and PACF plots of the residuals. If the majority of autocorrelation and partial autocorrelation coefficients lie within the confidence intervals, the model is considered to have effectively captured the information of data. Otherwise, the parameters <italic>p</italic> and <italic>q</italic> are adjusted for re-fitting. Upon successful validation of the ARIMA (<italic>p,d,q</italic>) model, the quantified enterprise digital transformation indicators are incorporated as exogenous variables, forming the ARIMAX (<italic>p,d,q</italic>) model.</p>
</sec>
<sec id="s3-2-2-4">
<label>3.2.2.4</label>
<title>Step 4 series forecasting</title>
<p>Once a valid ARIMA (<italic>p,d,q</italic>) model was established, the DTI time series was incorporated as an exogenous variable <inline-formula id="inf15">
<mml:math id="m21">
<mml:mrow>
<mml:msub>
<mml:mi>x</mml:mi>
<mml:mi>t</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula> forming the final ARIMAX (<italic>p,d,q</italic>) model. The model parameters (AR, MA, and exogenous coefficients) were then estimated using the maximum likelihood method. Forecasted values <inline-formula id="inf16">
<mml:math id="m22">
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>f</mml:mi>
<mml:mi>o</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula> are generated by applying the predefined autoregressive (AR), differencing (I), and moving average (MA) rules.</p>
</sec>
</sec>
</sec>
<sec id="s3-3">
<label>3.3</label>
<title>Real-time cloud resource utilization diagnosis and optimization triggering</title>
<sec id="s3-3-1">
<label>3.3.1</label>
<title>Business-critical threshold specification</title>
<p>The safety threshold for resource utilization is determined using <xref ref-type="disp-formula" rid="e7">Equation 7</xref>, based on business criticality.<disp-formula id="e7">
<mml:math id="m23">
<mml:mrow>
<mml:msub>
<mml:mi>r</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mfrac>
<mml:mn>1</mml:mn>
<mml:mrow>
<mml:mn>1</mml:mn>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mi>k</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:mrow>
</mml:mfrac>
</mml:mrow>
</mml:math>
<label>(7)</label>
</disp-formula>where.</p>
<p>
<inline-formula id="inf17">
<mml:math id="m24">
<mml:mrow>
<mml:msub>
<mml:mi>r</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Safety threshold for the i-th resource utilization.</p>
<p>
<inline-formula id="inf18">
<mml:math id="m25">
<mml:mrow>
<mml:msub>
<mml:mi>k</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Safety buffer coefficient for the i-th resource (0&#x3c; <inline-formula id="inf19">
<mml:math id="m26">
<mml:mrow>
<mml:msub>
<mml:mi>k</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula> &#x2264;0.5).</p>
<p>For critical services (e.g., real-time transaction processing, customer support), <inline-formula id="inf20">
<mml:math id="m27">
<mml:mrow>
<mml:msub>
<mml:mi>k</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula> is typically set to 0.3&#x2013;0.5 to ensure stability. For non-critical services (e.g., data archiving, historical analysis), <inline-formula id="inf21">
<mml:math id="m28">
<mml:mrow>
<mml:msub>
<mml:mi>k</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula> is set to 0.1&#x2013;0.2 to balance cost and risk. For example, setting <inline-formula id="inf22">
<mml:math id="m29">
<mml:mrow>
<mml:msub>
<mml:mi>k</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mn>0.4</mml:mn>
</mml:mrow>
</mml:math>
</inline-formula> establishes a safety threshold <inline-formula id="inf23">
<mml:math id="m30">
<mml:mrow>
<mml:msub>
<mml:mi>r</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2248;</mml:mo>
<mml:mn>0.71</mml:mn>
</mml:mrow>
</mml:math>
</inline-formula> , implying a 29% resource buffer.</p>
<p>This threshold <inline-formula id="inf24">
<mml:math id="m31">
<mml:mrow>
<mml:msub>
<mml:mi>r</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula> triggers scaling actions when monitored utilization exceeds predicted capacity limits.</p>
</sec>
<sec id="s3-3-2">
<label>3.3.2</label>
<title>Predictive threshold activation mechanism</title>
<p>Utilizing the demand forecasts <inline-formula id="inf25">
<mml:math id="m32">
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>f</mml:mi>
<mml:mi>o</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula> generated by the ARIMAX model (<xref ref-type="sec" rid="s3-2">Section 3.2</xref>), real-time resource utilization is evaluated against the safety threshold <inline-formula id="inf26">
<mml:math id="m33">
<mml:mrow>
<mml:msub>
<mml:mi>r</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>. The optimization procedures are initiated when the condition specified in <xref ref-type="disp-formula" rid="e8">Equation 8</xref> is met.<disp-formula id="e8">
<mml:math id="m34">
<mml:mrow>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>f</mml:mi>
<mml:mi>o</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>c</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>n</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:mfrac>
<mml:mo>&#x2265;</mml:mo>
<mml:msub>
<mml:mi>r</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
<label>(8)</label>
</disp-formula>where.</p>
<p>
<inline-formula id="inf27">
<mml:math id="m35">
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>f</mml:mi>
<mml:mi>o</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Predicted demand for the i-th resource.</p>
<p>
<inline-formula id="inf28">
<mml:math id="m36">
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>c</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>n</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Total provisioned capacity of current devices for the i-th resource.</p>
<p>If the condition is met, meaning the predicted demand ratio exceeds the safety alert threshold, then resource i is determined to face a risk of supply shortage in the future period, triggering an expansion alarm or an architecture optimization requirement for resource i. If the condition is not met, the water level of resource i is safe, and immediate expansion is not required.</p>
</sec>
</sec>
<sec id="s3-4">
<label>3.4</label>
<title>Predictive-driven investment optimization under operational constraints</title>
<sec id="s3-4-1">
<label>3.4.1</label>
<title>Objective function</title>
<p>The objective function focuses on minimizing the total cost <inline-formula id="inf29">
<mml:math id="m37">
<mml:mrow>
<mml:msub>
<mml:mi>C</mml:mi>
<mml:mrow>
<mml:mi>t</mml:mi>
<mml:mi>o</mml:mi>
<mml:mi>t</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>l</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>, integrating both leasing and purchasing costs. As shown in <xref ref-type="disp-formula" rid="e9">Equation 9</xref>:<disp-formula id="e9">
<mml:math id="m38">
<mml:mrow>
<mml:mi mathvariant="italic">min</mml:mi>
<mml:mo>&#x2061;</mml:mo>
<mml:msub>
<mml:mi>C</mml:mi>
<mml:mrow>
<mml:mi>t</mml:mi>
<mml:mi>o</mml:mi>
<mml:mi>t</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>l</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x3d;</mml:mo>
<mml:mo>&#x2211;</mml:mo>
<mml:mrow>
<mml:mfenced open="(" close=")" separators="|">
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#xd7;</mml:mo>
<mml:msub>
<mml:mi>P</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>p</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>h</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#xd7;</mml:mo>
<mml:msub>
<mml:mi>P</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>p</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>h</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:mfenced>
</mml:mrow>
</mml:mrow>
</mml:math>
<label>(9)</label>
</disp-formula>where.</p>
<p>
<inline-formula id="inf30">
<mml:math id="m39">
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Leased quantity of the i-th resource.</p>
<p>
<inline-formula id="inf31">
<mml:math id="m40">
<mml:mrow>
<mml:msub>
<mml:mi>P</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Unit leasing price of the i-th resource.</p>
<p>
<inline-formula id="inf32">
<mml:math id="m41">
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>p</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>h</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Purchased quantity of the i-th resource.</p>
<p>
<inline-formula id="inf33">
<mml:math id="m42">
<mml:mrow>
<mml:msub>
<mml:mi>P</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>p</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>h</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Unit purchasing price of the i-th resource.</p>
<p>The objective is to minimize the total cost by optimizing the proportion of leased and purchased resources.</p>
</sec>
<sec id="s3-4-2">
<label>3.4.2</label>
<title>Unified constraint framework</title>
<p>To ensure rational and feasible resource allocation, the following constraints are defined:</p>
<p>Constraint 1 Resource Demand Forecast Constraint. As shown in <xref ref-type="disp-formula" rid="e10">Equation 10</xref>:<disp-formula id="e10">
<mml:math id="m43">
<mml:mrow>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mi>l</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>p</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>h</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2265;</mml:mo>
<mml:msub>
<mml:mi>X</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
<label>(10)</label>
</disp-formula>where.<list list-type="simple">
<list-item>
<p>
<inline-formula id="inf34">
<mml:math id="m44">
<mml:mrow>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Load allocated to leased equipment for the i-th resource.</p>
</list-item>
<list-item>
<p>
<inline-formula id="inf35">
<mml:math id="m45">
<mml:mrow>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>p</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>h</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Load allocated to purchased equipment for the i-th resource.</p>
</list-item>
<list-item>
<p>
<inline-formula id="inf36">
<mml:math id="m46">
<mml:mrow>
<mml:msub>
<mml:mi>X</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: <inline-formula id="inf37">
<mml:math id="m47">
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>f</mml:mi>
<mml:mi>o</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2212;</mml:mo>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>c</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>n</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>
</p>
</list-item>
</list>
</p>
<p>This constraint ensures that resource allocation meets the minimum demand requirement, preventing service disruptions due to underestimation.</p>
<p>Constraint 2 Resource Supply Constraint (Water Level Alert Line). As shown in <xref ref-type="disp-formula" rid="e11">Equation 11</xref>:<disp-formula id="e11">
<mml:math id="m48">
<mml:mrow>
<mml:mfrac>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>f</mml:mi>
<mml:mi>o</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>c</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>n</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>p</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>h</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:mfrac>
<mml:mo>&#x2264;</mml:mo>
<mml:msub>
<mml:mi>r</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
<label>(11)</label>
</disp-formula>
</p>
<p>This constraint enforces the safety margin <inline-formula id="inf38">
<mml:math id="m49">
<mml:mrow>
<mml:msub>
<mml:mi>r</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula> derived from business-criticality analysis (<xref ref-type="sec" rid="s3-3-1">Section 3.3.1</xref>), ensuring buffer resources for demand volatility.</p>
<p>Constraint 3 Natural Number Constraint. As shown in <xref ref-type="disp-formula" rid="e12">Equation 12</xref>:<disp-formula id="e12">
<mml:math id="m50">
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2208;</mml:mo>
<mml:mi>N</mml:mi>
<mml:mo>,</mml:mo>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>p</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>h</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2208;</mml:mo>
<mml:mi>N</mml:mi>
</mml:mrow>
</mml:math>
<label>(12)</label>
</disp-formula>
</p>
<p>Ensures non-negative resource allocation, aligning with practical requirements.</p>
<p>Constraint 4 Cloud Leasing Cap Constraint. As shown in <xref ref-type="disp-formula" rid="e13">Equation 13</xref>:<disp-formula id="e13">
<mml:math id="m51">
<mml:mrow>
<mml:mfrac>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>p</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>h</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:mfrac>
<mml:mo>&#x2264;</mml:mo>
<mml:msub>
<mml:mi>r</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
<label>(13)</label>
</disp-formula>where.<list list-type="simple">
<list-item>
<p>
<inline-formula id="inf39">
<mml:math id="m52">
<mml:mrow>
<mml:msub>
<mml:mi>r</mml:mi>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Maximum allowable ratio of leased resources to total resources.</p>
</list-item>
</list>
</p>
<p>This prevents over-reliance on leasing, which could inflate long-term costs.</p>
<p>Constraint 5 Budget Constraint. As shown in <xref ref-type="disp-formula" rid="e14">Equation 14</xref>:<disp-formula id="e14">
<mml:math id="m53">
<mml:mrow>
<mml:msub>
<mml:mi>C</mml:mi>
<mml:mrow>
<mml:mi>t</mml:mi>
<mml:mi>o</mml:mi>
<mml:mi>t</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>l</mml:mi>
</mml:mrow>
</mml:msub>
<mml:mo>&#x2264;</mml:mo>
<mml:msub>
<mml:mi>C</mml:mi>
<mml:mrow>
<mml:mi>b</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>d</mml:mi>
<mml:mi>g</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:math>
<label>(14)</label>
</disp-formula>where.</p>
<p>
<inline-formula id="inf40">
<mml:math id="m54">
<mml:mrow>
<mml:msub>
<mml:mi>C</mml:mi>
<mml:mrow>
<mml:mi>b</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>d</mml:mi>
<mml:mi>g</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
</mml:msub>
</mml:mrow>
</mml:math>
</inline-formula>: Total budget for cloud platform construction (Ensures costs remain within the approved budget.).</p>
</sec>
</sec>
</sec>
<sec id="s4">
<label>4</label>
<title>Simulation experiments</title>
<sec id="s4-1">
<label>4.1</label>
<title>Experimental setup</title>
<p>To evaluate the effectiveness of the proposed model (<xref ref-type="sec" rid="s3">Section 3</xref>), we conducted simulation experiments using the publicly available cluster dataset <italic>cluster_trace_v2018</italic> from Alibaba Cloud. The detailed cluster parameters in this dataset are summarized in <xref ref-type="table" rid="T4">Table 4</xref>.</p>
<table-wrap id="T4" position="float">
<label>TABLE 4</label>
<caption>
<p>Dataset parameter information.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Column name</th>
<th align="center">Type</th>
<th align="center">Description</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">container_id</td>
<td align="center">String</td>
<td align="center">Container&#x2019;s unique ID</td>
</tr>
<tr>
<td align="center">machine_id</td>
<td align="center">String</td>
<td align="center">Machine hosting the container</td>
</tr>
<tr>
<td align="center">time_stamp</td>
<td align="center">Bigint</td>
<td align="center">Time stamp</td>
</tr>
<tr>
<td align="center">cpu_util_percent</td>
<td align="center">Bigint</td>
<td align="center">CPU utilization percentage</td>
</tr>
<tr>
<td align="center">mem_util_percent</td>
<td align="center">Bigint</td>
<td align="center">Memory utilization percentage</td>
</tr>
<tr>
<td align="center">mem_gps</td>
<td align="center">Double</td>
<td align="center">Memory bandwidth usage rate</td>
</tr>
<tr>
<td align="center">disk_usage_percent</td>
<td align="center">Double</td>
<td align="center">Disk space utilization percentage</td>
</tr>
<tr>
<td align="center">disk_io_percent</td>
<td align="center">Double</td>
<td align="center">Disk I/O utilization percentage</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>The dataset encompasses operational data from 4,000 servers, including both online application containers and offline computational tasks. To simplify the experimental process, we used CPU utilization data from two randomly selected containers on one machine to simulate the daily average operational states of containers a and b in Company A&#x2019;s current infrastructure, resulting in 1,922 data points (<xref ref-type="bibr" rid="B21">Xie and Dong, 2025</xref>).</p>
<p>Container a had 2,954 CPU cores, whereas Container b featured 14,378 CPU cores. The CPU usage trends for containers are shown in <xref ref-type="fig" rid="F2">Figure 2</xref> (Container a) and <xref ref-type="fig" rid="F3">Figure 3</xref> (Container b).</p>
<fig id="F2" position="float">
<label>FIGURE 2</label>
<caption>
<p>Time Series of Simulated Daily Average CPU Utilization for Container a.</p>
</caption>
<graphic xlink:href="frcmn-06-1732098-g002.tif">
<alt-text content-type="machine-generated">Line graph depicting CPU utilization percentage over time from January 1 to January 9, 2018. The utilization fluctuates between 20% and 100%, showing multiple peaks and troughs throughout the period.</alt-text>
</graphic>
</fig>
<fig id="F3" position="float">
<label>FIGURE 3</label>
<caption>
<p>Time Series of Simulated Daily Average CPU Utilization for Container b.</p>
</caption>
<graphic xlink:href="frcmn-06-1732098-g003.tif">
<alt-text content-type="machine-generated">Line graph showing CPU utilization percentage from January 1, 2018, to January 8, 2018. The utilization fluctuates between 30% and 80%, with several peaks and dips.</alt-text>
</graphic>
</fig>
<p>As shown in <xref ref-type="fig" rid="F2">Figures 2</xref>, <xref ref-type="fig" rid="F3">3</xref>, both Containers a and b currently operate in a high-utilization mode. Since they are critical for the enterprise&#x2019;s real-time business operations, the enterprise must allocate sufficient resource reserves. The safety buffer coefficient is set to <italic>k &#x3d; 0.5</italic>, resulting in a water level alert threshold of 0.67 for both containers. This indicates a clear need for capacity expansion. To ensure the continuity of daily operations and mitigate risks from extreme events, simulation-driven investment analysis is conducted to expand the capacity of Containers a and b.</p>
</sec>
<sec id="s4-2">
<label>4.2</label>
<title>Implementation framework</title>
<sec id="s4-2-1">
<label>4.2.1</label>
<title>Data partitioning and environment</title>
<p>The dataset was partitioned such that the first 80% of the data was used as the training set, and the remaining 20% was allocated to the test set (<xref ref-type="bibr" rid="B6">Li et al., 2025</xref>; <xref ref-type="bibr" rid="B8">Liang et al., 2023</xref>). We conducted simulation experiments using Python 3.13. The hardware configuration details for this experiment are summarized in <xref ref-type="table" rid="T5">Table 5</xref>.</p>
<table-wrap id="T5" position="float">
<label>TABLE 5</label>
<caption>
<p>Experimental environment Configuration.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Hardware Configuration</th>
<th align="center">Specifications</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">CPU</td>
<td align="center">Intel core i5-1135G7</td>
</tr>
<tr>
<td align="center">Memory</td>
<td align="center">8&#xa0;GB</td>
</tr>
<tr>
<td align="center">Storage</td>
<td align="center">512&#xa0;GB PCIe NVMe SSD</td>
</tr>
<tr>
<td align="center">Operating system</td>
<td align="center">Windows 11 64-bit</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="s4-2-2">
<label>4.2.2</label>
<title>Digital maturity quantification</title>
<p>The Digital Transformation Index developed in this study is designed to capture the dynamic evolutionary nature of corporate digitalization processes. Since the cluster dataset used in this experiment covers only the period up to early 2018, we extended the evaluation of digital transformation levels from 2018 to 2020 by incorporating enterprises&#x2019; historical development paths and external environmental analyses. This method ensures both logical consistency in the research design and realism in the decision-making context. The resulting assessments not only supply exogenous variables for the subsequent ARIMAX model but also offer a contextual foundation that more accurately reflects actual transformation phases for investment decision simulations.</p>
<p>Building on the methods in <xref ref-type="sec" rid="s3-1">Section 3.1</xref>, <xref ref-type="table" rid="T6">Table 6</xref> summarizes the quantitative results of digital transformation maturity and contextual insights for the enterprise.</p>
<table-wrap id="T6" position="float">
<label>TABLE 6</label>
<caption>
<p>Quantitative results of enterprise digital maturity.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Time</th>
<th align="center">Composite score (100-point scale)</th>
<th align="center">Key milestones and driving factors</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">2018&#x2013;01</td>
<td align="center">32</td>
<td align="center">Traditional enterprise phase<break/>- IT infrastructure primarily on-premises with basic OA systems<break/>- Cloud computing accounted for 12% of IT budget.<break/>- Data storage was decentralized and lacked unified management</td>
</tr>
<tr>
<td align="center">2018&#x2013;02&#x2013;12</td>
<td align="center">34 &#x2192; 38</td>
<td align="center">Initial progress<break/>- Migrated partial business systems to Alibaba cloud ECS, increasing server virtualization rate from 15% to 25%<break/>- Deployed basic BI tools for monthly sales data visualization<break/>- Organizational structure remained unchanged; &#x3c;10% of employees had digital skills</td>
</tr>
<tr>
<td align="center">2019&#x2013;01</td>
<td align="center">40</td>
<td align="center">ERP system Migration<break/>- Replaced on-premises ERP with Alibaba cloud RDS, improving database management efficiency by 30%</td>
</tr>
<tr>
<td align="center">2019&#x2013;02&#x2013;06</td>
<td align="center">42 &#x2192; 45</td>
<td align="center">Continued advancement<break/>- Launched Alibaba cloud CRM, achieving 40% customer data digitization<break/>- Conducted employee training, raising certified digital staff to 15%<break/>- Business processes remained offline-centric, and digital integration had seen limited progress</td>
</tr>
<tr>
<td align="center">2019&#x2013;07</td>
<td align="center">52</td>
<td align="center">Strategic transformation<break/>- Released Three-year digital transformation plan with initial investment of $11.10 million<break/>- Partnered with Alibaba cloud to build a data middle platform<break/>- Initiated cloud-native refactoring, increasing containerized applications from 5% to 20%<break/>- Established an agile transformation task force</td>
</tr>
<tr>
<td align="center">2019&#x2013;08</td>
<td align="center">55</td>
<td align="center">Data middle platform phase 1<break/>- Integrated data from 6 core systems (e.g., supply chain, production)<break/>- Real-time API calls exceeded 50,000/day</td>
</tr>
<tr>
<td align="center">2019&#x2013;09&#x2013;12</td>
<td align="center">58 &#x2192; 63</td>
<td align="center">Rapid implementation<break/>- Deployed Alibaba cloud AI customer service (replaced 30% manual agents)<break/>- Adopted DevOps, reducing R&#x26;D cycles by 40%<break/>- Piloted data-driven decision-making (expert score: 2 &#x2192; 3)</td>
</tr>
<tr>
<td align="center">2020&#x2013;01</td>
<td align="center">70</td>
<td align="center">Pandemic-driven Acceleration<break/>- Full remote work via Alibaba cloud DingTalk (daily video meetings increased by 500%)<break/>- Cloud expenditure rose to 30% of IT budget.</td>
</tr>
<tr>
<td align="center">2020&#x2013;02&#x2013;06</td>
<td align="center">72 &#x2192; 76</td>
<td align="center">Deep integration<break/>- IoT data integration enabled real-time production monitoring<break/>- AI inventory optimization improved turnover rate by 25%<break/>- Matrix organizational structure adopted (40% agile teams)</td>
</tr>
<tr>
<td align="center">2020&#x2013;07&#x2013;08</td>
<td align="center">78 &#x2192; 80</td>
<td align="center">Ongoing improvement<break/>- Deployed hybrid cloud architecture with unified resource management<break/>- Digital training coverage reached 80% (35% certified staff)<break/>- Data-driven KPIs integrated (expert score: 4)</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="s4-2-3">
<label>4.2.3</label>
<title>Cloud demand forecasting in digital transformation</title>
<sec id="s4-2-3-1">
<label>4.2.3.1</label>
<title>Model order identification and validation</title>
<p>To determine the optimal parameter combination for the ARIMAX model, we first conducted stationarity tests and correlation analysis on the CPU utilization time series for Containers a and b. <xref ref-type="fig" rid="F4">Figures 4</xref>, <xref ref-type="fig" rid="F5">5</xref> present the Autocorrelation Function (ACF) and Partial Autocorrelation Function (PACF) for Container a, respectively, while <xref ref-type="fig" rid="F6">Figures 6</xref>, <xref ref-type="fig" rid="F7">7</xref> display the corresponding functions for Container b.</p>
<fig id="F4" position="float">
<label>FIGURE 4</label>
<caption>
<p>ACF plot for Container a.</p>
</caption>
<graphic xlink:href="frcmn-06-1732098-g004.tif">
<alt-text content-type="machine-generated">Residual ACF plot with 95% confidence intervals. The plot shows autocorrelations at different lags, with most points falling within the confidence band, indicating no significant autocorrelation in residuals.</alt-text>
</graphic>
</fig>
<fig id="F5" position="float">
<label>FIGURE 5</label>
<caption>
<p>PACF plot for Container a.</p>
</caption>
<graphic xlink:href="frcmn-06-1732098-g005.tif">
<alt-text content-type="machine-generated">Partial autocorrelation function (PACF) plot with residual values plotted against lags from zero to twenty. Most values fall within the blue shaded 95% confidence interval, indicating no significant autocorrelation.</alt-text>
</graphic>
</fig>
<fig id="F6" position="float">
<label>FIGURE 6</label>
<caption>
<p>ACF plot for Container b.</p>
</caption>
<graphic xlink:href="frcmn-06-1732098-g006.tif">
<alt-text content-type="machine-generated">Residual autocorrelation function (ACF) plot displaying residuals with 95% confidence intervals. The plot shows data points primarily within the shaded confidence region, indicating minor autocorrelation except at lag zero where it reaches one.</alt-text>
</graphic>
</fig>
<fig id="F7" position="float">
<label>FIGURE 7</label>
<caption>
<p>PACF plot for Container b.</p>
</caption>
<graphic xlink:href="frcmn-06-1732098-g007.tif">
<alt-text content-type="machine-generated">Residual PACF plot with 95 percent confidence intervals shows lag values on the x-axis and correlation values on the y-axis. Most points fall within the shaded confidence band.</alt-text>
</graphic>
</fig>
<p>From the ACF and PACF plots, both containers&#x2019; sequences exhibit significant autocorrelation structures. Based on these characteristics and the Akaike Information Criterion (AIC), we identified the optimal ARIMAX model orders as:</p>
<p>Container a: <italic>p &#x3d; 1, d &#x3d; 0, q &#x3d; 1</italic>.</p>
<p>Container b: <italic>p &#x3d; 1, d &#x3d; 0, q &#x3d; 1</italic>.</p>
</sec>
<sec id="s4-2-3-2">
<label>4.2.3.2</label>
<title>Model diagnostic tests</title>
<p>To verify the adequacy of the ARIMAX (1,0,1) model specification, we performed Ljung-Box white noise tests, presented in <xref ref-type="table" rid="T7">Tables 7</xref>, <xref ref-type="table" rid="T8">8</xref>.</p>
<table-wrap id="T7" position="float">
<label>TABLE 7</label>
<caption>
<p>Ljung-box test results for container a ARIMAX (1,0,1) model.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Lag order</th>
<th align="center">Test statistic</th>
<th align="center">p-value</th>
<th align="center">Critical value (95%)</th>
<th align="center">Conclusion</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">10</td>
<td align="center">72.9853</td>
<td align="center">0.2067</td>
<td align="center">18.3070</td>
<td align="center">White noise</td>
</tr>
<tr>
<td align="center">15</td>
<td align="center">150.3713</td>
<td align="center">0.3739</td>
<td align="center">24.9958</td>
<td align="center">White noise</td>
</tr>
<tr>
<td align="center">20</td>
<td align="center">291.7002</td>
<td align="center">0.0525</td>
<td align="center">31.4104</td>
<td align="center">White noise</td>
</tr>
</tbody>
</table>
</table-wrap>
<table-wrap id="T8" position="float">
<label>TABLE 8</label>
<caption>
<p>Ljung-Box Test Results for Container b ARIMAX (1,0,1) Model.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Lag order</th>
<th align="center">Test statistic</th>
<th align="center">p-value</th>
<th align="center">Critical value (95%)</th>
<th align="center">Conclusion</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">10</td>
<td align="center">27.8180</td>
<td align="center">0.7652</td>
<td align="center">18.3070</td>
<td align="center">White noise</td>
</tr>
<tr>
<td align="center">15</td>
<td align="center">79.5531</td>
<td align="center">0.6996</td>
<td align="center">24.9958</td>
<td align="center">White noise</td>
</tr>
<tr>
<td align="center">20</td>
<td align="center">155.4244</td>
<td align="center">0.6411</td>
<td align="center">31.4104</td>
<td align="center">White noise</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>Additionally, the residual statistics for both containers are provided in <xref ref-type="table" rid="T9">Table 9</xref>.</p>
<table-wrap id="T9" position="float">
<label>TABLE 9</label>
<caption>
<p>Residual statistics for ARIMAX (1,0,1) models.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="left">Container</th>
<th align="left">Mean</th>
<th align="left">Standard deviation</th>
<th align="left">Skewness</th>
<th align="left">Kurtosis</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="left">A</td>
<td align="left">6.47</td>
<td align="left">202.66</td>
<td align="left">&#x2212;0.44</td>
<td align="left">5.23</td>
</tr>
<tr>
<td align="left">B</td>
<td align="left">3.31</td>
<td align="left">798.84</td>
<td align="left">0.99</td>
<td align="left">2.94</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>All Ljung-Box test p-values exceed the 0.05 significance level, indicating that the residual sequences of both models are white noise, thus confirming model adequacy. Although Container a&#x2019;s residuals show slightly elevated kurtosis (5.23), it remains within acceptable limits.</p>
</sec>
<sec id="s4-2-3-3">
<label>4.2.3.3</label>
<title>Exogenous variable significance</title>
<p>In the forecasting model for Container a, the exogenous variable DTI exhibited a statistically significant coefficient of 943.1211 (p &#x3d; 0.001), indicating a strong positive impact on cloud resource demand. A comparable trend was observed in the model for Container b.</p>
</sec>
<sec id="s4-2-3-4">
<label>4.2.3.4</label>
<title>Forecasting implementation</title>
<p>We employed the ARIMAX model to train and forecast the load time series for Container a and Container b individually. The results of the training are illustrated in <xref ref-type="fig" rid="F8">Figure 8</xref> (Container a) and <xref ref-type="fig" rid="F9">Figure 9</xref> (Container b).</p>
<fig id="F8" position="float">
<label>FIGURE 8</label>
<caption>
<p>ARIMAX Model Forecast vs. Actual Observed CPU Load for Container a.</p>
</caption>
<graphic xlink:href="frcmn-06-1732098-g008.tif">
<alt-text content-type="machine-generated">Line graph titled &#x22;ARIMAX: Container(a) CPU Cores Prediction&#x22; showing CPU core usage over time from January 1 to January 9, 2018. The blue line represents training data, the orange line depicts true values, and the green dashed line indicates predicted values. Usage peaks around January 3 and January 7, with noticeable drops, especially on January 6 and January 8.</alt-text>
</graphic>
</fig>
<fig id="F9" position="float">
<label>FIGURE 9</label>
<caption>
<p>ARIMAX Model Forecast vs. Actual Observed CPU Load for Container b.</p>
</caption>
<graphic xlink:href="frcmn-06-1732098-g009.tif">
<alt-text content-type="machine-generated">Line graph showing CPU core usage prediction from January 1 to January 8, 2018. The blue line represents training data, the orange line indicates true values, and the green dashed line denotes predicted values using the ARIMAX model. CPU usage fluctuates, with significant variations observed throughout the period.</alt-text>
</graphic>
</fig>
<p>To guarantee resource adequacy, the maximum values from the operational load predictions were selected following the model&#x2019;s application. The top five largest values for Containers a and b, sorted in descending-rank order, are presented in <xref ref-type="table" rid="T10">Table 10</xref>.</p>
<table-wrap id="T10" position="float">
<label>TABLE 10</label>
<caption>
<p>Forecast model output values.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">No.</th>
<th align="center">Container a (cores)</th>
<th align="center">Container b (cores)</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">1</td>
<td align="center">2,663</td>
<td align="center">9,958</td>
</tr>
<tr>
<td align="center">2</td>
<td align="center">2,651</td>
<td align="center">9,877</td>
</tr>
<tr>
<td align="center">3</td>
<td align="center">2,640</td>
<td align="center">9,376</td>
</tr>
<tr>
<td align="center">4</td>
<td align="center">2,631</td>
<td align="center">9,248</td>
</tr>
<tr>
<td align="center">5</td>
<td align="center">2,626</td>
<td align="center">9,221</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
</sec>
<sec id="s4-2-4">
<label>4.2.4</label>
<title>Forecasting performance comparison: ARIMAX vs. ARIMA</title>
<p>To validate the predictive accuracy enhancement achieved by the proposed ARIMAX model, a comparative analysis was conducted against the traditional ARIMA model. Utilizing the same training and testing datasets for both containers, we evaluated the forecast performance through error distribution analysis and statistical metrics.</p>
<sec id="s4-2-4-1">
<label>4.2.4.1</label>
<title>Visual error distribution analysis</title>
<p>The forecast error distributions for both models are visually compared in <xref ref-type="fig" rid="F10">Figures 10</xref>&#x2013;<xref ref-type="fig" rid="F13">13</xref>, providing insights into the prediction accuracy across different modeling approaches.</p>
<fig id="F10" position="float">
<label>FIGURE 10</label>
<caption>
<p>Forecast Error Distribution of the ARIMAX Model (Container a).</p>
</caption>
<graphic xlink:href="frcmn-06-1732098-g010.tif">
<alt-text content-type="machine-generated">Histogram of forecast error distribution titled &#x22;Forecast Error Distribution(a).&#x22; The x-axis represents forecast errors ranging from negative one thousand to seven hundred fifty, and the y-axis shows frequency. A red dashed line indicates zero error, while a green dashed line marks the mean error at 6.4703. The highest frequency is near zero error.</alt-text>
</graphic>
</fig>
<fig id="F11" position="float">
<label>FIGURE 11</label>
<caption>
<p>Forecast Error Distribution of the ARIMA Model (Container a).</p>
</caption>
<graphic xlink:href="frcmn-06-1732098-g011.tif">
<alt-text content-type="machine-generated">Histogram showing forecast error distribution. The x-axis represents forecast error ranging from negative one thousand to one thousand, and the y-axis shows frequency up to sixty. A red dashed line marks the zero error, and a green dashed line indicates a mean error of thirty-three point one eight zero one.</alt-text>
</graphic>
</fig>
<fig id="F12" position="float">
<label>FIGURE 12</label>
<caption>
<p>Forecast Error Distribution of the ARIMA Model (Container b).</p>
</caption>
<graphic xlink:href="frcmn-06-1732098-g012.tif">
<alt-text content-type="machine-generated">Histogram depicting forecast error distribution with frequency on the y-axis and forecast error on the x-axis. Bars show a roughly normal distribution centered around zero. Red dashed line represents zero error, and a green dashed line indicates a mean error of 3.3127.</alt-text>
</graphic>
</fig>
<fig id="F13" position="float">
<label>FIGURE 13</label>
<caption>
<p>Forecast Error Distribution of the ARIMA Model (Container b).</p>
</caption>
<graphic xlink:href="frcmn-06-1732098-g013.tif">
<alt-text content-type="machine-generated">Histogram showing the distribution of forecast errors with frequencies on the y-axis and forecast errors on the x-axis, ranging from negative three thousand to three thousand. A red dashed line represents zero error, and a green dashed line indicates the mean error at negative 5.4614. The data is approximately normally distributed.</alt-text>
</graphic>
</fig>
<p>Container a Performance:</p>
<p>
<xref ref-type="fig" rid="F10">Figure 10</xref> illustrates the error distribution of the ARIMAX model for Container a, showing errors concentrated around zero with minimal dispersion.</p>
<p>
<xref ref-type="fig" rid="F11">Figure 11</xref> displays the corresponding error distribution for the ARIMA model, revealing more scattered errors with greater variance.</p>
<p>Container b Performance:</p>
<p>
<xref ref-type="fig" rid="F12">Figure 12</xref> presents the ARIMAX model&#x2019;s error distribution for Container b, demonstrating similar concentration around zero.</p>
<p>
<xref ref-type="fig" rid="F13">Figure 13</xref> shows the ARIMA model&#x2019;s error distribution for Container b, exhibiting comparable dispersion patterns to Container a.</p>
</sec>
<sec id="s4-2-4-2">
<label>4.2.4.2</label>
<title>Statistical significance</title>
<p>The consistent reduction in mean error across both containers (approximately 54%&#x2013;55% improvement) provides strong evidence for the superior predictive capability of the ARIMAX framework. This enhancement can be attributed to the incorporation of the Digital Transformation Index as an exogenous variable, which captures the systematic influence of enterprise digital maturity on cloud resource demand patterns.</p>
<p>The concentrated error distribution around zero in the ARIMAX models (<xref ref-type="fig" rid="F10">Figures 10</xref>, <xref ref-type="fig" rid="F12">12</xref>) indicates reduced bias and variance, confirming the model&#x2019;s ability to more accurately track actual resource utilization trends compared to the traditional ARIMA approach (<xref ref-type="fig" rid="F11">Figures 11</xref>, <xref ref-type="fig" rid="F13">13</xref>).</p>
</sec>
</sec>
<sec id="s4-2-5">
<label>4.2.5</label>
<title>Resource expansion constraints</title>
<p>Given that both Containers a and b support real-time business-critical services (e.g., transaction processing), we set the safety buffer coefficient <italic>k &#x3d; 0.5</italic>, consistent with the upper range recommended in <xref ref-type="sec" rid="s3-3-1">Section 3.3.1</xref> for high-criticality workloads. This sets the water level alert threshold at 67% of total capacity. The minimum expansion requirement is derived from the safety threshold condition using <xref ref-type="disp-formula" rid="e15">Equation 15</xref>:<disp-formula id="e15">
<mml:math id="m55">
<mml:mrow>
<mml:msub>
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>c</mml:mi>
<mml:mi>u</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>n</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:mi>L</mml:mi>
</mml:mrow>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>p</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>h</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2265;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:msub>
<mml:mi>Q</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>f</mml:mi>
<mml:mi>o</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
<mml:mrow>
<mml:msub>
<mml:mi>r</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>a</mml:mi>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>t</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
</mml:mrow>
</mml:mfrac>
</mml:mrow>
</mml:math>
<label>(15)</label>
</disp-formula>
</p>
<p>For Container a, the minimum scaling requirement is calculated by substituting the relevant parameters into <xref ref-type="disp-formula" rid="e16">Equation 16</xref>:<disp-formula id="e16">
<mml:math id="m56">
<mml:mrow>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>p</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>h</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2265;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mn>2663</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mn>0.67</mml:mn>
</mml:mrow>
</mml:mfrac>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>2954</mml:mn>
<mml:mo>&#x2248;</mml:mo>
<mml:mn>1021</mml:mn>
</mml:mrow>
</mml:math>
<label>(16)</label>
</disp-formula>
</p>
<p>For Container b, the minimum scaling requirement is calculated by substituting the relevant parameters into <xref ref-type="disp-formula" rid="e17">Equation 17</xref>:<disp-formula id="e17">
<mml:math id="m57">
<mml:mrow>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>l</mml:mi>
<mml:mi>e</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2b;</mml:mo>
<mml:msub>
<mml:mi>L</mml:mi>
<mml:msub>
<mml:mrow>
<mml:mi>p</mml:mi>
<mml:mi>r</mml:mi>
<mml:mi>c</mml:mi>
<mml:mi>h</mml:mi>
<mml:mi>a</mml:mi>
<mml:mi>s</mml:mi>
<mml:mi>e</mml:mi>
</mml:mrow>
<mml:mi>i</mml:mi>
</mml:msub>
</mml:msub>
<mml:mo>&#x2265;</mml:mo>
<mml:mfrac>
<mml:mrow>
<mml:mn>9958</mml:mn>
</mml:mrow>
<mml:mrow>
<mml:mn>0.67</mml:mn>
</mml:mrow>
</mml:mfrac>
<mml:mo>&#x2212;</mml:mo>
<mml:mn>14378</mml:mn>
<mml:mo>&#x2248;</mml:mo>
<mml:mn>485</mml:mn>
</mml:mrow>
</mml:math>
<label>(17)</label>
</disp-formula>
</p>
<p>The expansion is subject to a total budget of $2.22 million and a constraint that leased resources constitute no more than 50% of the total added capacity. This leasing cap balances operational flexibility with long-term cost control. For the economic evaluation, purchased equipment is amortized over a 10-year service life, consistent with the typical useful life of enterprise server hardware, and future costs are discounted at an 8% rate, reflecting the standard cost of capital in the Chinese IT sector (<xref ref-type="bibr" rid="B27">Zhang et al., 2024</xref>). The market-quoted CPU leasing prices for Containers a and b are provided in <xref ref-type="table" rid="T11">Table 11</xref>.</p>
<table-wrap id="T11" position="float">
<label>TABLE 11</label>
<caption>
<p>Leased CPU Expansion Pricing for Containers a and b.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Category</th>
<th align="center">Container a</th>
<th align="center">Container b</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">Specification code</td>
<td align="center">AMD compute c7a</td>
<td align="center">mysql.n4.xlarge.2c</td>
</tr>
<tr>
<td align="center">CPU (cores)</td>
<td align="center">2</td>
<td align="center">8</td>
</tr>
<tr>
<td align="center">Memory (GB)</td>
<td align="center">4</td>
<td align="center">32</td>
</tr>
<tr>
<td align="center">Reference price</td>
<td align="center">$171.12/year</td>
<td align="center">$2,843.30/year</td>
</tr>
<tr>
<td align="center">Total cost NPV (8%, 10)</td>
<td align="center">$1,148.23 &#xd7; Q</td>
<td align="center">$19,078.78 &#xd7; Q</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>When expanding Containers a and b via self-built servers, refer to the detailed specifications listed in <xref ref-type="table" rid="T12">Table 12</xref> (Container a) and <xref ref-type="table" rid="T13">Table 13</xref> (Container b).</p>
<table-wrap id="T12" position="float">
<label>TABLE 12</label>
<caption>
<p>Container a server setup cost breakdown (per unit).</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Category</th>
<th align="center">Setup</th>
<th align="center">Specification</th>
<th align="center">Unit cost (USD)</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td rowspan="4" align="center">Hardware</td>
<td align="center">Server</td>
<td align="center">Inspur NF5468M6 (Motherboard, PSU, NIC, GPU, etc.)</td>
<td align="center">8,321.78</td>
</tr>
<tr>
<td align="center">CPU</td>
<td align="center">2 &#xd7; Intel Xeon Gold 6348 (28 cores/socket)</td>
<td align="center">2,080.44/socket</td>
</tr>
<tr>
<td align="center">Memory</td>
<td align="center">128&#xa0;GB DDR4</td>
<td align="center">138.70/16&#xa0;GB</td>
</tr>
<tr>
<td align="center">Storage</td>
<td align="center">960&#xa0;GB SSD &#x2b;3 &#xd7; 8&#xa0;TB HDD</td>
<td align="center">SSD: 277.39<break/>HDD: 416.09/disk</td>
</tr>
<tr>
<td align="center">Software</td>
<td align="center">Linux OS</td>
<td align="center">Management tools</td>
<td align="center">6,934.81/year</td>
</tr>
<tr>
<td rowspan="2" align="center">Human &#x26; deployment</td>
<td align="center">Labor cost</td>
<td align="center">4 FTEs</td>
<td align="center">66,574.20/year</td>
</tr>
<tr>
<td align="center">Deployment</td>
<td align="center">One-time cost</td>
<td align="center">6,934.81</td>
</tr>
<tr>
<td align="center">Total cost NPV (8%)</td>
<td align="left">&#x200b;</td>
<td align="left">&#x200b;</td>
<td align="center">453,652.77 &#x2b; 61,651.05&#xd7;Q</td>
</tr>
</tbody>
</table>
</table-wrap>
<table-wrap id="T13" position="float">
<label>TABLE 13</label>
<caption>
<p>Container b Server Setup Cost Breakdown (Per Unit).</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Category</th>
<th align="center">Setup</th>
<th align="center">Specification</th>
<th align="center">Unit cost (USD)</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td rowspan="4" align="center">Hardware</td>
<td align="center">Server</td>
<td align="center">Lenovo ThinkServer WR3220 G2 (Motherboard, PSU, NIC, GPU, etc.)</td>
<td align="center">2,219.14</td>
</tr>
<tr>
<td align="center">CPU</td>
<td align="center">2 &#xd7; Intel Xeon Gold 6348 (28 cores/socket)</td>
<td align="center">2,080.44/socket</td>
</tr>
<tr>
<td align="center">Memory</td>
<td align="center">64&#xa0;GB DDR4</td>
<td align="center">138.70/16&#xa0;GB</td>
</tr>
<tr>
<td align="center">Storage</td>
<td align="center">4 &#xd7; 4&#xa0;TB SATA SSD</td>
<td align="center">693.48/disk</td>
</tr>
<tr>
<td align="center">Software</td>
<td align="center">MySQL enterprise edition</td>
<td align="center">Management tools</td>
<td align="center">1,386.96/year</td>
</tr>
<tr>
<td rowspan="2" align="center">Human &#x26; deployment</td>
<td align="center">Labor cost</td>
<td align="center">5 DBAs</td>
<td align="center">83,217.75/year</td>
</tr>
<tr>
<td align="center">Deployment</td>
<td align="center">One-time cost</td>
<td align="center">6,934.81</td>
</tr>
<tr>
<td align="center">Total cost NPV (8%)</td>
<td align="left">&#x200b;</td>
<td align="left">&#x200b;</td>
<td align="center">562,223.81 &#x2b; 19,017.79&#xd7;Q</td>
</tr>
</tbody>
</table>
<table-wrap-foot>
<fn>
<p>All hardware and software costs are based on 2018 market quotes from Alibaba Cloud and major server vendors. Labor costs are estimated based on industry averages for IT, operations.</p>
</fn>
</table-wrap-foot>
</table-wrap>
</sec>
<sec id="s4-2-6">
<label>4.2.6</label>
<title>Genetic algorithm optimization implementation</title>
<p>This study employs a Genetic Algorithm (GA) to solve the mixed-integer nonlinear programming problem, primarily based on the following considerations: all (<xref ref-type="bibr" rid="B3">Huang, 2024</xref>; <xref ref-type="bibr" rid="B23">Xu et al., 2023</xref>) problem variables are integers, aligning with GA&#x2019;s discrete variable handling characteristics; the constraint conditions include nonlinear relationships, making traditional linear programming methods difficult to apply directly; global search capability is required to avoid converging to local optima; and the problem scale is moderate, suitable for population-based intelligent optimization methods.</p>
<sec id="s4-2-6-1">
<label>4.2.6.1</label>
<title>Parameter configuration</title>
<p>To ensure algorithm convergence and solution quality, the genetic algorithm parameters were configured as shown in <xref ref-type="table" rid="T14">Table 14</xref> after multiple experimental trials and debugging:</p>
<table-wrap id="T14" position="float">
<label>TABLE 14</label>
<caption>
<p>Genetic algorithm parameter Configuration.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="left">Parameter Category</th>
<th align="left">Parameter Name</th>
<th align="left">Parameter Value</th>
<th align="left">Parameter Description</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td rowspan="2" align="left">Population parameters</td>
<td align="left">Population Size</td>
<td align="left">200</td>
<td align="left">Number of individuals per generation, balancing search efficiency and computational cost</td>
</tr>
<tr>
<td align="left">Variable dimension</td>
<td align="left">4</td>
<td align="left">Number of optimization variables (Q_z1, Q_m1, Q_z2, Q_m2)</td>
</tr>
<tr>
<td rowspan="4" align="left">Evolution parameters</td>
<td align="left">Maximum Iterations</td>
<td align="left">500</td>
<td align="left">Algorithm termination condition, ensuring sufficient convergence</td>
</tr>
<tr>
<td align="left">Selection function</td>
<td align="left">Stochastic uniform</td>
<td align="left">Maintains population diversity</td>
</tr>
<tr>
<td align="left">Crossover function</td>
<td align="left">Scattered</td>
<td align="left">Specialized crossover method for real-valued encoding</td>
</tr>
<tr>
<td align="left">Mutation function</td>
<td align="left">Adaptive feasible</td>
<td align="left">Maintains algorithm exploration capability</td>
</tr>
<tr>
<td rowspan="2" align="left">Constraint parameters</td>
<td align="left">Constraint Tolerance</td>
<td align="left">1 &#xd7; 10<sup>&#x2212;6</sup>
</td>
<td align="left">Constraint satisfaction accuracy</td>
</tr>
<tr>
<td align="left">Penalty factor</td>
<td align="left">Adaptive</td>
<td align="left">Penalty coefficient for constraint violation handling</td>
</tr>
<tr>
<td rowspan="2" align="left">Variable Bounds</td>
<td align="left">Lower Bound vector</td>
<td align="left">[0, 0, 0, 0]</td>
<td align="left">Minimum values of decision variables</td>
</tr>
<tr>
<td align="left">Upper Bound vector</td>
<td align="left">[300, 20, 10, 20]</td>
<td align="left">Maximum values of decision variables</td>
</tr>
<tr>
<td align="left">Special constraints</td>
<td align="left">Integer constraints</td>
<td align="left">[1,2,3,4]</td>
<td align="left">All variables are integers</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="s4-2-6-2">
<label>4.2.6.2</label>
<title>Constraint handling mechanism</title>
<p>For the nonlinear constraints in the problem, the algorithm employs a penalty function method. The degree of constraint violation is transformed into penalty terms added to the objective function, ensuring the search process consistently moves toward the feasible region. Specific constraints include seven inequality constraints related to production capacity, efficiency, proportional allocation, and budget.</p>
<p>Through the aforementioned parameter configuration and algorithm design, the genetic algorithm can effectively search for the global optimal solution within the complex feasible solution space, providing a reliable theoretical basis and numerical results for subsequent decision analysis.</p>
</sec>
</sec>
</sec>
</sec>
<sec sec-type="results" id="s5">
<label>5</label>
<title>Results</title>
<sec id="s5-1">
<label>5.1</label>
<title>Optimal resource configuration</title>
<p>The computational results are tabulated in <xref ref-type="table" rid="T15">Table 15</xref>.</p>
<table-wrap id="T15" position="float">
<label>TABLE 15</label>
<caption>
<p>Cost-optimal expansion Configuration.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Container</th>
<th align="center">Self-built servers</th>
<th align="center">Leased units</th>
<th align="center">Total cost NPV (USD)</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">A</td>
<td align="center">10</td>
<td align="center">231</td>
<td align="center">1,335,405.09</td>
</tr>
<tr>
<td align="center">B</td>
<td align="center">9</td>
<td align="center">0</td>
<td align="center">733,383.96</td>
</tr>
<tr>
<td align="center">Total</td>
<td align="center">19</td>
<td align="center">231</td>
<td align="center">2,068,789.05</td>
</tr>
</tbody>
</table>
</table-wrap>
</sec>
<sec id="s5-2">
<label>5.2</label>
<title>Container-specific validation</title>
<p>The validation results for each container&#x2019;s optimal configuration are detailed in <xref ref-type="table" rid="T16">Table 16</xref>, confirming compliance with all operational constraints.</p>
<table-wrap id="T16" position="float">
<label>TABLE 16</label>
<caption>
<p>Container-specific Configuration validation.</p>
</caption>
<table>
<thead valign="top">
<tr>
<th align="center">Container</th>
<th align="center">a</th>
<th align="center">b</th>
</tr>
</thead>
<tbody valign="top">
<tr>
<td align="center">Self-built servers</td>
<td align="center">10</td>
<td align="center">9</td>
</tr>
<tr>
<td align="center">Leased units</td>
<td align="center">231</td>
<td align="center">0</td>
</tr>
<tr>
<td align="center">Total CPU cores</td>
<td align="center">3,976</td>
<td align="center">15,442</td>
</tr>
<tr>
<td align="center">Leasing ratio</td>
<td align="center">0.45</td>
<td align="center">0.00</td>
</tr>
<tr>
<td align="center">Resource threshold</td>
<td align="center">0.67</td>
<td align="center">0.67</td>
</tr>
<tr>
<td align="center">Status</td>
<td align="center">Compliant</td>
<td align="center">Compliant</td>
</tr>
</tbody>
</table>
</table-wrap>
<p>The validation confirms that both container configurations comply with all operational constraints. The hybrid model for Container a optimally balances cost-efficiency with operational flexibility, whereas the exclusive self-build strategy for Container b is justified by its stable, high-demand profile, favoring long-term cost savings.</p>
</sec>
<sec id="s5-3">
<label>5.3</label>
<title>Feasibility assessment</title>
<p>The final feasibility of the proposed investment strategy is summarized as follows:<list list-type="bullet">
<list-item>
<p>Total NPV cost: $2.07 million</p>
</list-item>
<list-item>
<p>Budget constraint: $2.22 million</p>
</list-item>
<list-item>
<p>Utilization rate: 93.67%</p>
</list-item>
</list>
</p>
<p>The genetic algorithm solution achieves a 93.67% budget utilization ($2.07M of the $2.22M ceiling), which demonstrates high cost-efficiency in practice. This near-optimal expenditure indicates that the model successfully identified a configuration that maximizes resource acquisition within the financial limit, while the slight underspend (6.33%) provides a valuable financial buffer for unforeseen contingencies or future scaling needs.</p>
</sec>
</sec>
<sec sec-type="discussion" id="s6">
<label>6</label>
<title>Discussion</title>
<p>This study developed an integrated framework for cloud resource forecasting and investment decision-making by incorporating corporate digital maturity, yielding the following core findings:<list list-type="simple">
<list-item>
<p>&#x2022; Enhanced Forecasting Accuracy: The ARIMAX model, enriched with the DTI as an exogenous variable, demonstrated a significant improvement in predicting cloud resource demand. The comprehensive DTI evaluation system, built upon four primary dimensions and twelve secondary indicators, successfully quantifies digital maturity. Simulation results confirmed that the DTI-embedded model achieves a CPU load peak prediction error of less than 5%, with the DTI coefficient being statistically significant (p &#x3c; 0.01). This robustly validates a strong correlation between an enterprise&#x2019;s digital transformation level and its cloud resource consumption.</p>
</list-item>
<list-item>
<p>&#x2022; Optimized Investment Strategy: The proposed investment model effectively addresses the core &#x201c;lease-or-build&#x201d; dilemma under budgetary constraints (<xref ref-type="bibr" rid="B11">Lu, 2024</xref>; <xref ref-type="bibr" rid="B19">Wang, 2025</xref>). By evaluating the trade-offs between self-built data centers and third-party cloud leasing, the model achieves dual objectives: optimal resource allocation and stringent cost control. The simulation experiment, conducted within a $2.22 million budget ceiling, yielded an optimal configuration of 10 self-built servers and 231 leased units for Container a, and 9 self-built servers for Container b, with a total cost of $2.07 million.</p>
</list-item>
<list-item>
<p>&#x2022; Comprehensive Framework Integration: The study presents a holistic framework that seamlessly integrates the DTI, predictive analytics, and multi-constraint optimization. The DTI systematically links strategic digital initiatives with IT resource planning. The optimization model, incorporating constraints such as budget, leasing ratios, and safety thresholds, enables a synergistic resource configuration that aligns long-term strategic goals with dynamic operational needs. This integration provides a theoretically sound and operationally viable solution for cloud resource planning in the context of digital transformation.</p>
</list-item>
</list>
</p>
<sec id="s6-1">
<label>6.1</label>
<title>Limitations and future work</title>
<p>While this study provides a novel framework, it is subject to several limitations. Firstly, the model was validated using a dataset from a single cloud provider (Alibaba Cloud). The generalizability of the findings to other cloud ecosystems (e.g., AWS, Azure) or enterprise-specific IT environments with unique workload patterns may be limited and warrants further investigation. Secondly, the DTI, though comprehensive, may not capture all facets of digital transformation equally across different industries. Future research should aim to test and calibrate this model with multi-source datasets and explore industry-specific DTI adaptations. Furthermore, the model assumes static pricing and technology, whereas incorporating real-time spot market prices and evolving hardware specifications could enhance its practical utility.</p>
</sec>
</sec>
<sec sec-type="conclusion" id="s7">
<label>7</label>
<title>Conclusion</title>
<p>This study successfully developed an integrated framework that bridges corporate digital maturity with cloud resource management. By introducing a quantified Digital Transformation Index (DTI) as a key exogenous variable into an ARIMAX forecasting model, we achieved high-precision prediction of cloud resource demand (MAPE &#x3c;5%). The subsequent optimization model, solving for a cost-minimal investment strategy under multiple operational and financial constraints, efficiently allocated resources, utilizing 93.67% of a $2.22 million budget.</p>
<p>The primary theoretical contribution lies in establishing and validating the critical link between digital maturity and IT resource demand. Methodologically, the seamless &#x201c;predict-then-optimize&#x201d; framework demonstrates significant practical utility. It provides enterprises with a scalable, economically viable, and decision-support tool for navigating cloud investment choices during digital transformation. Future work will focus on enhancing the model&#x2019;s dynamism by incorporating real-time market fluctuations and supply chain factors, thereby increasing its adaptability and robustness for real-world applications.</p>
</sec>
</body>
<back>
<sec sec-type="data-availability" id="s8">
<title>Data availability statement</title>
<p>The original contributions presented in the study are included in the article/<xref ref-type="sec" rid="s14">Supplementary Material</xref>, further inquiries can be directed to the corresponding author.</p>
</sec>
<sec sec-type="author-contributions" id="s9">
<title>Author contributions</title>
<p>ZC: Conceptualization, Project administration, Writing &#x2013; review and editing. YT: Supervision, Writing &#x2013; review and editing. FW: Methodology, Writing &#x2013; review and editing. XW: Formal Analysis, Validation, Visualization, Writing &#x2013; original draft. MX: Data curation, Formal Analysis, Writing &#x2013; original draft. ZW: Investigation, Writing &#x2013; review and editing.</p>
</sec>
<sec sec-type="COI-statement" id="s11">
<title>Conflict of interest</title>
<p>Authors ZC and FW were employed by Digitalization Department, State Grid Fujian Electric Power Company. Author YT was employed by Economic and Technical Research Institute, State Grid Fujian Electric Power Company.</p>
<p>The remaining author(s) declared that this work was conducted in the absence of any commercial or financial relationships that could be construed as a potential conflict of interest.</p>
<p>The authors declared that this work received funding from Economic and Technology Research Institute of State Grid Fujian Electric Power Company. The funder had the following involvement in the study: Supervision, Writing&#x2010;review and editing.</p>
</sec>
<sec sec-type="ai-statement" id="s12">
<title>Generative AI statement</title>
<p>The author(s) declared that generative AI was not used in the creation of this manuscript.</p>
<p>Any alternative text (alt text) provided alongside figures in this article has been generated by Frontiers with the support of artificial intelligence and reasonable efforts have been made to ensure accuracy, including review by the authors wherever possible. If you identify any issues, please contact us.</p>
</sec>
<sec sec-type="disclaimer" id="s13">
<title>Publisher&#x2019;s note</title>
<p>All claims expressed in this article are solely those of the authors and do not necessarily represent those of their affiliated organizations, or those of the publisher, the editors and the reviewers. Any product that may be evaluated in this article, or claim that may be made by its manufacturer, is not guaranteed or endorsed by the publisher.</p>
</sec>
<sec sec-type="supplementary-material" id="s14">
<title>Supplementary material</title>
<p>The Supplementary Material for this article can be found online at: <ext-link ext-link-type="uri" xlink:href="https://www.frontiersin.org/articles/10.3389/frcmn.2025.1732098/full#supplementary-material">https://www.frontiersin.org/articles/10.3389/frcmn.2025.1732098/full&#x23;supplementary-material</ext-link>
</p>
<supplementary-material xlink:href="Table2.xlsx" id="SM1" mimetype="application/xlsx" xmlns:xlink="http://www.w3.org/1999/xlink"/>
<supplementary-material xlink:href="Table3.xlsx" id="SM2" mimetype="application/xlsx" xmlns:xlink="http://www.w3.org/1999/xlink"/>
<supplementary-material xlink:href="Table4.xlsx" id="SM3" mimetype="application/xlsx" xmlns:xlink="http://www.w3.org/1999/xlink"/>
<supplementary-material xlink:href="Table1.xlsx" id="SM4" mimetype="application/xlsx" xmlns:xlink="http://www.w3.org/1999/xlink"/>
</sec>
<fn-group>
<fn fn-type="custom" custom-type="edited-by">
<p>
<bold>Edited by:</bold> <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/1677653/overview">Lukman Adewale Ajao</ext-link>, Federal University of Technology Minna, Nigeria</p>
</fn>
<fn fn-type="custom" custom-type="reviewed-by">
<p>
<bold>Reviewed by:</bold> <ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/3165392/overview">Farhan Nisar</ext-link>, Qurtuba University of Science and Information Technology, Pakistan</p>
<p>
<ext-link ext-link-type="uri" xlink:href="https://loop.frontiersin.org/people/3271505/overview">Sai Bharath Sannareddy</ext-link>, Abbott, United States</p>
</fn>
</fn-group>
<ref-list>
<title>References</title>
<ref id="B1">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Calheiros</surname>
<given-names>R. N.</given-names>
</name>
<name>
<surname>Masoumi</surname>
<given-names>E.</given-names>
</name>
<name>
<surname>Ranjan</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Buyya</surname>
<given-names>R.</given-names>
</name>
</person-group> (<year>2015</year>). <article-title>Workload prediction using ARIMA model and its impact on cloud applications&#x27; QoS</article-title>. <source>IEEE Trans. Cloud Comput.</source> <volume>3</volume> (<issue>04</issue>), <fpage>449</fpage>&#x2013;<lpage>458</lpage>. <pub-id pub-id-type="doi">10.1109/TCC.2014.2350475</pub-id>
</mixed-citation>
</ref>
<ref id="B2">
<mixed-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Gao</surname>
<given-names>C.</given-names>
</name>
</person-group> (<year>2015</year>). <source>Research and implementation of load balancing method in cloud stack platform</source>. <publisher-loc>[Harbin (China)]</publisher-loc>: <publisher-name>Harbin Institute of Technology</publisher-name>. <comment>[M.S. thesis]</comment>.</mixed-citation>
</ref>
<ref id="B3">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Huang</surname>
<given-names>W.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>Water resource allocation optimization method based on GM-VMD water demand prediction</article-title>. <source>Water Resour. Technol. Superv.</source> <volume>10</volume>, <fpage>165</fpage>&#x2013;<lpage>170</lpage>.</mixed-citation>
</ref>
<ref id="B4">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Karpagam</surname>
<given-names>T.</given-names>
</name>
<name>
<surname>Kanniappan</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2025</year>). <article-title>Symmetry-aware multi-dimensional attention spiking neural network with optimization techniques for accurate workload and resource time series prediction in cloud computing systems</article-title>. <source>Symmetry</source> <volume>17</volume> (<issue>3</issue>), <fpage>383</fpage>. <pub-id pub-id-type="doi">10.3390/sym17030383</pub-id>
</mixed-citation>
</ref>
<ref id="B5">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Li</surname>
<given-names>Q.</given-names>
</name>
</person-group> (<year>2022</year>). <article-title>Research on equipment leasing mode selection in engineering management</article-title>. <source>Port. Eng. Technol.</source> <volume>59</volume> (<issue>04</issue>), <fpage>97</fpage>&#x2013;<lpage>100</lpage>. <pub-id pub-id-type="doi">10.16403/j.cnki.ggjs20220422</pub-id>
</mixed-citation>
</ref>
<ref id="B6">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Li</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2025</year>). <article-title>Industrial digitalization guiding comprehensive enterprise digital construction framework</article-title>. <source>China Mark.</source> <volume>12</volume>, <fpage>191</fpage>&#x2013;<lpage>194</lpage>. <pub-id pub-id-type="doi">10.13939/j.cnki.zgsc.2025.12.047</pub-id>
</mixed-citation>
</ref>
<ref id="B7">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Li</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Yu</surname>
<given-names>K.</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>Y.</given-names>
</name>
</person-group> (<year>2025</year>). <article-title>Research on resource usage prediction in high-performance computing platforms based on ARIMA and LSTM</article-title>. <source>Comput. Sci.</source> <volume>52</volume> (<issue>09</issue>), <fpage>1</fpage>&#x2013;<lpage>11</lpage>.</mixed-citation>
</ref>
<ref id="B8">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Liang</surname>
<given-names>R.</given-names>
</name>
<name>
<surname>Xie</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Zhai</surname>
<given-names>Q.</given-names>
</name>
<name>
<surname>Zhang</surname>
<given-names>Q.</given-names>
</name>
</person-group> (<year>2023</year>). <article-title>Research on container cloud load prediction based on improved stacking ensemble model</article-title>. <source>Comput. Appl. Softw.</source> <volume>40</volume> (<issue>12</issue>), <fpage>48</fpage>&#x2013;<lpage>55&#x2b;100</lpage>.</mixed-citation>
</ref>
<ref id="B9">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Liu</surname>
<given-names>W.</given-names>
</name>
</person-group> (<year>2023</year>). <article-title>Research on the optimization path of capital allocation for state-owned capital investment and operation companies</article-title>. <source>Bus. News</source> (<issue>11</issue>), <fpage>151</fpage>&#x2013;<lpage>154</lpage>.</mixed-citation>
</ref>
<ref id="B10">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Liu</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Jing</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Liu</surname>
<given-names>T.</given-names>
</name>
</person-group> (<year>2010</year>). <article-title>Financial decision-making methods for leasing or purchasing fixed assets</article-title>. <source>Acc. Mon.</source> <volume>16</volume>, <fpage>15</fpage>&#x2013;<lpage>16</lpage>. <pub-id pub-id-type="doi">10.19641/j.cnki.42-1290/f.2010.16.007</pub-id>
</mixed-citation>
</ref>
<ref id="B11">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Lu</surname>
<given-names>Y.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>Investment strategies and asset allocation analysis in financial markets</article-title>. <source>Bus. Inf.</source> <volume>10</volume>, <fpage>83</fpage>&#x2013;<lpage>86</lpage>.</mixed-citation>
</ref>
<ref id="B12">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Malik</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Tahir</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Sardaraz</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Alourani</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>2022</year>). <article-title>A resource utilization prediction model for cloud data centers using evolutionary algorithms and machine learning techniques</article-title>. <source>Appl. Sci.</source> <volume>12</volume> (<issue>4</issue>), <fpage>2160</fpage>. <pub-id pub-id-type="doi">10.3390/app12042160</pub-id>
</mixed-citation>
</ref>
<ref id="B13">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Mi</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Wang</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Yin</surname>
<given-names>G.</given-names>
</name>
<name>
<surname>Shi</surname>
<given-names>D.</given-names>
</name>
<name>
<surname>Zhou</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Yuan</surname>
<given-names>L.</given-names>
</name>
</person-group> (<year>2011</year>). <article-title>A resource on-demand reconfiguration method for virtualized data centers</article-title>. <source>Softw.</source> <volume>22</volume> (<issue>9</issue>), <fpage>2193</fpage>&#x2013;<lpage>2205</lpage>. <pub-id pub-id-type="doi">10.3724/sp.j.1001.2011.04056</pub-id>
</mixed-citation>
</ref>
<ref id="B14">
<mixed-citation publication-type="confproc">
<person-group person-group-type="author">
<name>
<surname>Nalewaik</surname>
<given-names>A.</given-names>
</name>
</person-group> (<year>2025</year>). &#x201c;<article-title>A hybrid approach to benefits planning for capital projects</article-title>,&#x201d; in <conf-name>Proceedings of the 2025 IEEE European Technology and Engineering Management Summit (E-TEMS)</conf-name> (<publisher-name>IEEE</publisher-name>), <fpage>86</fpage>&#x2013;<lpage>91</lpage>. <pub-id pub-id-type="doi">10.1109/E-TEMS64751.2025.11239339</pub-id>
</mixed-citation>
</ref>
<ref id="B15">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Pan</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Hu</surname>
<given-names>G.</given-names>
</name>
</person-group> (<year>2025</year>). <article-title>Can enterprises generate new productive forces through digital transformation? An empirical study from the perspective of technological innovation</article-title>. <source>Technol. Econ.</source> <volume>44</volume> (<issue>02</issue>), <fpage>31</fpage>&#x2013;<lpage>42</lpage>.</mixed-citation>
</ref>
<ref id="B16">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Serban</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Dedu</surname>
<given-names>S.</given-names>
</name>
</person-group> (<year>2025</year>). <article-title>A scalarized entropy-based model for portfolio optimization: balancing return, risk and diversification</article-title>. <source>Mathematics</source> <volume>13</volume> (<issue>20</issue>), <fpage>3311</fpage>. <pub-id pub-id-type="doi">10.3390/math13203311</pub-id>
</mixed-citation>
</ref>
<ref id="B17">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Stefanidis</surname>
<given-names>V.-A.</given-names>
</name>
<name>
<surname>Verginadis</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Mentzas</surname>
<given-names>G.</given-names>
</name>
</person-group> (<year>2023</year>). <article-title>MulticloudFL: adaptive federated learning for improving forecasting accuracy in multi-cloud environments</article-title>. <source>Information</source> <volume>14</volume> (<issue>12</issue>), <fpage>662</fpage>. <pub-id pub-id-type="doi">10.3390/info14120662</pub-id>
</mixed-citation>
</ref>
<ref id="B18">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Su</surname>
<given-names>J.</given-names>
</name>
</person-group> (<year>2020</year>). <article-title>The implementation of asset allocation approaches: theory and evidence</article-title>. <source>Sustainability</source> <volume>12</volume> (<issue>17</issue>), <fpage>7162</fpage>. <pub-id pub-id-type="doi">10.3390/su12177162</pub-id>
</mixed-citation>
</ref>
<ref id="B19">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Wang</surname>
<given-names>Z.</given-names>
</name>
</person-group> (<year>2025</year>). <article-title>Research on factors influencing investment asset allocation efficiency of Chinese insurance companies</article-title>. <source>Mark. Wkly.</source> <volume>38</volume> (<issue>02</issue>), <fpage>42</fpage>&#x2013;<lpage>45</lpage>.</mixed-citation>
</ref>
<ref id="B20">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Wang</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Chen</surname>
<given-names>T.</given-names>
</name>
</person-group> (<year>2025</year>). <article-title>BO-LSTM-Based cloud resource consumption prediction model</article-title>. <source>Comput. Eng. De.</source> <volume>46</volume> (<issue>5</issue>), <fpage>1418</fpage>&#x2013;<lpage>1423</lpage>. <pub-id pub-id-type="doi">10.16208/j.issn1000-7024.2025.05.024</pub-id>
</mixed-citation>
</ref>
<ref id="B21">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Xie</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Dong</surname>
<given-names>Y.</given-names>
</name>
</person-group> (<year>2025</year>). <article-title>A container cloud resource prediction model based on secondary decomposition and broad learning system</article-title>. <source>Lab. Res. Explor.</source> <volume>44</volume> (<issue>03</issue>), <fpage>94</fpage>&#x2013;<lpage>100</lpage>.</mixed-citation>
</ref>
<ref id="B22">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Xing</surname>
<given-names>Q.</given-names>
</name>
<name>
<surname>Wu</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Deng</surname>
<given-names>F.</given-names>
</name>
</person-group> (<year>2025</year>). <article-title>Dependency analysis between industrial internet platforms and manufacturing participants under digital transformation</article-title>. <source>Manag. Eng.</source> <volume>39</volume> (<issue>05</issue>), <fpage>1</fpage>&#x2013;<lpage>18</lpage>.</mixed-citation>
</ref>
<ref id="B23">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Xu</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Hong</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>He</surname>
<given-names>L.</given-names>
</name>
<name>
<surname>Hong</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Zhang</surname>
<given-names>Y.</given-names>
</name>
<name>
<surname>Hou</surname>
<given-names>F.</given-names>
</name>
<etal/>
</person-group> (<year>2023</year>). <article-title>Equity and resource prediction of child health human resources in maternal and child health institutions in Guizhou province</article-title>. <source>Chin. Health Resour.</source> <volume>26</volume> (<issue>05</issue>), <fpage>582</fpage>&#x2013;<lpage>588</lpage>. <pub-id pub-id-type="doi">10.13688/j.cnki.chr.2023.230147</pub-id>
</mixed-citation>
</ref>
<ref id="B24">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Yang</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Zheng</surname>
<given-names>Q.</given-names>
</name>
<name>
<surname>Zhu</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Luo</surname>
<given-names>M.</given-names>
</name>
<name>
<surname>Hou</surname>
<given-names>Z.</given-names>
</name>
<name>
<surname>Zhang</surname>
<given-names>J.</given-names>
</name>
<etal/>
</person-group> (<year>2025</year>). <article-title>DimAug-TimesFM: dimension augmentation for long-term cloud demand forecasting in few-shot scenarios</article-title>. <source>Appl. Sci.</source> <volume>15</volume> (<issue>7</issue>), <fpage>3450</fpage>. <pub-id pub-id-type="doi">10.3390/app15073450</pub-id>
</mixed-citation>
</ref>
<ref id="B25">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Zhang</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Zhang</surname>
<given-names>L.</given-names>
</name>
</person-group> (<year>2017</year>). <article-title>A review of theoretical research on asset allocation</article-title>. <source>Econ. Dyn.</source> <volume>2</volume>, <fpage>137</fpage>&#x2013;<lpage>147</lpage>.</mixed-citation>
</ref>
<ref id="B26">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Zhang</surname>
<given-names>W.</given-names>
</name>
<name>
<surname>Duan</surname>
<given-names>P.</given-names>
</name>
<name>
<surname>Yang</surname>
<given-names>L. T.</given-names>
</name>
<name>
<surname>Xia</surname>
<given-names>F.</given-names>
</name>
<name>
<surname>Li</surname>
<given-names>Z.</given-names>
</name>
<name>
<surname>Lu</surname>
<given-names>Q.</given-names>
</name>
<etal/>
</person-group> (<year>2017</year>). <article-title>Resource requests prediction in the cloud computing environment with a deep belief network</article-title>. <source>Softw. Pract. Exper.</source> <volume>47</volume> (<issue>03</issue>), <fpage>472</fpage>&#x2013;<lpage>488</lpage>. <pub-id pub-id-type="doi">10.1002/spe.2426</pub-id>
</mixed-citation>
</ref>
<ref id="B27">
<mixed-citation publication-type="journal">
<person-group person-group-type="author">
<name>
<surname>Zhang</surname>
<given-names>J.</given-names>
</name>
<name>
<surname>Ouyang</surname>
<given-names>S.</given-names>
</name>
<name>
<surname>Wu</surname>
<given-names>H.</given-names>
</name>
<name>
<surname>Xin</surname>
<given-names>X.</given-names>
</name>
<name>
<surname>Huang</surname>
<given-names>W.</given-names>
</name>
</person-group> (<year>2024</year>). <article-title>Optimal configuration of grid-side energy storage considering distribution network reliability and operational economy</article-title>. <source>Power Syst. Autom. Equip.</source> <volume>44</volume> (<issue>07</issue>), <fpage>62</fpage>&#x2013;<lpage>68&#x2b;85</lpage>. <pub-id pub-id-type="doi">10.16081/j.epae.202312044</pub-id>
</mixed-citation>
</ref>
<ref id="B28">
<mixed-citation publication-type="book">
<person-group person-group-type="author">
<name>
<surname>Zhong</surname>
<given-names>X.</given-names>
</name>
</person-group> (<year>2018</year>). <source>Research on task scheduling algorithms in cloud computing environments</source>. <publisher-loc>[Jiangxi(China)]</publisher-loc>: <publisher-name>Jiangxi University of Science and Technology</publisher-name>. <comment>[M.S. thesis]</comment>.</mixed-citation>
</ref>
</ref-list>
</back>
</article>