❌

Normal view

Survey links three capabilities with Indonesian welfare-data integration

21 October 2026 at 23:09

A survey-based study of 246 village-level social welfare data operators found that business architecture, cross-organizational collaboration and technological readiness were positively and statistically significantly associated with perceived e-government integration impact in two Indonesian regencies. The research, focused on Gunung Kidul and Bangkalan, examined organizational, institutional, relational and technological capabilities associated with social welfare data integration. Governance and leadership and information policy did not show statistically significant direct relationships with perceived integration impact in the pooled sample.

The authors analyzed the survey with partial least squares structural equation modeling. In their framework, e-government integration impact, or EGII, represents perceived improvements in information, system and service quality, responsiveness and public trust. E-government integration scope, or EGIS, describes the breadth of integration across data, applications, electronic communication and knowledge-sharing processes.

EGII was strongly associated with EGIS, meaning that operators reporting more favorable perceived integration outcomes also tended to report broader integration. Because this was an observational analysis of survey responses, the results establish statistical relationships rather than causal effects. The findings identify three capabilities with significant direct relationships to EGII in the pooled model: business architecture, cross-organizational collaboration and technological readiness.

The evidence does not provide operational definitions for these constructs, but the results show that their measured levels were associated with respondents’ assessments of e-government integration outcomes. By contrast, governance and leadership and information policy had no statistically significant direct relationships with EGII in that analysis. This absence of a detected direct relationship does not establish that the two factors are unimportant or that they operate only through indirect pathways, because the supplied findings do not report such indirect effects.

A regency-based robustness analysis found that some relationships were sensitive to local implementation conditions. Significant differences between Gunung Kidul and Bangkan were reported for the technological-readiness-to-EGII relationship and the EGII-to-EGIS relationship. The geographic comparison therefore cautions against assuming that the same capability relationships apply uniformly across the two regencies, although it does not identify the specific local practices responsible for those differences.

Its direct contribution is to show which measured interoperability capabilities were associated with perceived integration impact in the surveyed population, alongside evidence that some relationships varied between the two regencies.

Subject of Research: Survey-based analysis of interoperability capabilities for social welfare data integration in two Indonesian regencies

Article Title: Determinants of E-government interoperability capabilities for social welfare data integration in Gunung Kidul and Bangkalan Regencies, Indonesia

Article References: Fikri, R., Purnomo, E. P., Pribadi, U., Mohamed, A. M., & Mohammad, N. B. (2026). Determinants of E-government interoperability capabilities for social welfare data integration in Gunung Kidul and Bangkalan Regencies, Indonesia. Discover Sustainability. https://doi.org/10.1007/s43621-026-04608-5

Image Credits: AI Generated

DOI: 10.1007/s43621-026-04608-5

Keywords: social welfare data, e-government, interoperability, Indonesia, PLS-SEM, technological readiness, cross-organizational collaboration, business architecture, digital governance, public services, Determinants, capabilities

How a 1975 Book Explained Computers and How They Worked

By: RHP
18 October 2026 at 02:27
In 1975, computers were enormous machines housed in dedicated rooms, surrounded by cabinets, cables, magnetic tape reels, and equipment that looked more like science fiction than the technology found in most homes today. A book titled How a Computer System Works offered readers a way to understand these complicated machines, explaining their components and showing […]

The $690 billion cloud spending spree

16 October 2026 at 10:00

Every quarter, I look at the capital expenditure numbers coming out of the major cloud providers, and every quarter, they manage to surprise me. This time, though, we’ve crossed into territory that’s genuinely hard to process. The five biggest US cloud and AI infrastructure providers (Microsoft, Alphabet, Amazon, Meta, and Oracle) have collectively committed to spending between $660 billion and $690 billion on capex in 2026, nearly doubling what they spent just a year ago.

Amazon leads the pack with a projected $200 billion, most of it directed at data centers and AI compute. Alphabet has committed $175 to $185 billion, up from $91 billion in 2025. Microsoft is tracking toward $120 billion or more, having already spent $37.5 billion in a single quarter. Meta is at $115 to $135 billion, and Oracle is targeting roughly $50 billion. For context, four companies alone plan to invest about $630 billion, a 62% increase from the record $388 billion they spent in 2025.

What are they buying? Mostly chips, buildings, and electricity. The spending splits across the AI data center stack: GPUs and custom accelerators such as Google’s Tensor Processing Units and Amazon’s Trainium, the physical data centers themselves with their liquid cooling and high-density floors, and often the power infrastructure to run it all, including power purchase agreements and even on-site gas-fired generation where the grid can’t keep up. Roughly two-thirds of the money goes to compute, and one-third goes to facilities, power, cooling, and networking, with the power share rising every quarter.

Where the market is heading

My take on the market is that we’re in the steep part of a demand curve that has a few more solid years left in it. Short-term demand over the next two years is already firm. Every hyperscaler reports being supply-constrained rather than demand-constrained, and Microsoft is sitting on an $80 billion backlog of Azure orders it can’t fulfill, largely because of power availability. Enterprises are panic-buying cloud capacity and computing gear right now because they’re convinced the AI boom will leave the unprepared behind, and they want their infrastructure in place so they can take advantage of whatever form the transformation takes. I get it. Nobody wants to explain to their board in 2028 why they spent 2026 waiting in line.

This means hardware vendors such as Dell, HPE, and IBM, along with the hyperscalers themselves, are going to see sustained growth as long as the demand continues. Some of it is real, and some of it is fear driven, but for the vendors, it all spends the same. The shortages enterprises are seeing today for processors and RAM, along with the associated price increases and stretched lead times, will most likely persist through that window because global silicon and memory supply is being absorbed by AI clusters faster than the manufacturers can expand it.

But my long-term forecast is deliberately less rosy than the providers’ own. The build-out cycle runs three to four years from commitment to full utilization. A lot can change in the AI market in that time. Model efficiency improvements could slash compute requirements per unit of output. Enterprises may discover that their AI workloads don’t justify the cloud spend once the novelty fades. Competitive dynamics could compress pricing. By 2028 and 2029, I expect the growth rate to be real but not at the scale builders assume today, and I expect the industry to carry the weight of capacity committed in the panic phase of 2026.

Are vendors overbuilding?

Here is where I part ways with the prevailing wisdom, and where I think we need some disciplined skepticism. The thinking right now is that for every bit of data center capacity you build, someone will use it, if not the hyperscaler that owns it, then some other tenant. Given Microsoft’s $80 billion backlog, that logic holds for the near term.

But I’ve been around long enough to be suspicious of “this time is different” arguments. I watched the fiber overbuild in the late 1990s, and I watched the first cloud buildout get ahead of itself as well. The concern is that the cloud providers are getting out over their skis, building capacity for demand that may not show up at the scale they’re projecting. The revenue those investments depend on is largely speculative. If AI adoption progresses more slowly than anticipated, or if efficiency gains reduce the compute required per workload faster than expected, the return on this spending could disappoint badly. There is also the uncomfortable possibility that a meaningful share of today’s demand is circular: Enterprises and vendors may be panic-buying capacity from each other in a stack of commitments that may never consolidate into actual sustained workloads.

By the time these data centers come online—and we’re talking about capacity committed now for delivery in 2027—the growth may not be at the scale the builders are expecting. I expect many of the data centers being committed now won’t be utilized at the rates people are assuming today for 2029. That’s not a prediction of collapse. It’s an acknowledgement that the industry has seen a similar pattern before in fiber, colocation, and the first cloud buildout itself.

Advice for enterprise buyers

If you’re running enterprise IT, this cycle cuts both ways. In the near term, you’re facing higher prices, allocation limits, and longer lead times for processors, RAM, and cloud capacity. Budget accordingly, lock in what you genuinely need, and resist buying out of the fear that drives the very shortages you’re suffering from.

But in the next few years, the picture flips. Overbuilt supply means lower prices. If the providers overshoot, then cloud rates soften and less expensive data center space becomes available for enterprises that need it, including capacity for your own AI ambitions at prices that would be unthinkable today. The overbuilding that will burn the hyperscalers’ investors will create a bargain for their customers.

The playbook I recommend is the one I’ve always recommended. Architect for the cloud on your own terms, stay out of long-term capacity commitments you can’t justify with current demand, and let the providers take the utilization risk. They’re betting hundreds of billions that the demand curve keeps climbing. You don’t have to make the same bet to benefit. The oversupply, if it comes, will find you, and at a price you’ll like a lot better than today’s.

❌