India’s parliamentary panels are obsessed with clocks. They talk about "time-bound" implementation as if the only thing standing between a nation and total orbital dominance is a calendar and a checkbook. The recent push for the Space Based Surveillance-III (SBS-III) program is a masterclass in bureaucratic delusion. It assumes that by simply accelerating the deployment of more "eyes in the sky," we are buying security.
We aren't. We are buying a massive, expensive, and increasingly vulnerable target.
The "lazy consensus" among defense analysts is that more satellites equal better intelligence. It’s a linear, 20th-century mindset applied to a 21st-century problem. The reality? More hardware in Low Earth Orbit (LEO) without a radical shift in data processing and physical defense is just orbital debris in waiting.
The Myth of the Time-Bound Advantage
The panel’s cry for "time-bound" execution is a red herring. Speed is irrelevant if you are sprinting in the wrong direction. The SBS-III program, as currently envisioned, focuses heavily on the deployment of high-resolution imaging and signals intelligence satellites. The logic is simple: see more, know more.
I have watched defense contractors burn through billions on this exact premise. They deliver the "birds," the politicians cut the ribbon, and then the intelligence community drowns in a sea of raw data they can't actually use.
The bottleneck isn't the launch schedule. It’s the latency between capture and decision. If your satellite takes a high-res photo of a troop movement but it takes six hours to downlink, process, analyze, and get to a commander’s desk, you haven't bought surveillance. You've bought a very expensive historical record.
Why LEO is a Death Trap
We are entering the era of the "Asymmetric Orbit." In the past, satellites were untouchable. Today, they are sitting ducks.
- Kinetic Kill Chains: Ground-to-space missiles are no longer experimental. They are operational.
- Directed Energy: Laser dazzling can blind an SBS-III asset for a fraction of the cost of the satellite’s fuel.
- Cyber Infiltration: The ground stations that control these "time-bound" assets are often running legacy code that is more porous than a sponge.
By rushing SBS-III into a traditional architecture, the government is centralizing risk. We are building a handful of multi-thousand-crore assets that can be neutralized by a $50,000 jammer or a $2 million missile. That isn't strategy. That's a bad bet.
The Problem With Resolution Obsession
Everyone wants "sub-meter resolution." It sounds impressive in a briefing. But in the age of deepfakes and advanced camouflage, resolution is a vanity metric.
Imagine a scenario where an adversary knows your revisit rate—the time it takes for your SBS-III satellite to pass over the same spot again. They simply move their sensitive assets during the "dark" window. If you don't have persistent, 24/7 coverage, your high-res snapshot is just a lucky guess.
To achieve true persistence with traditional SBS-III architecture, you would need a constellation size that the current budget cannot sustain. The panel wants it "time-bound," but they haven't reckoned with the math of orbital mechanics vs. the reality of the treasury.
The Distributed Alternative Nobody Wants to Discuss
Instead of building a few "exquisite" satellites, we should be pivoting to a "disposable" architecture.
The industry calls this "SmallSat Proliferation," but even that term misses the point. The goal shouldn't be to make the satellites smaller; it should be to make them irrelevant as individual units.
If you lose one SBS-III satellite in the current plan, you lose 25% of your capability in a specific sector. If you lose one node in a swarm of 500 cheap, mass-produced sensors, you lose 0.2%.
Why isn't the parliamentary panel calling for this? Because small, cheap, and redundant doesn't look good in a press release. It doesn't provide a "national pride" moment like a massive, sophisticated orbiter does. It’s harder to manage, harder to procure under current rigid defense rules, and it requires a level of software sophistication that the hardware-heavy ISRO-centric model isn't built for.
The Data Delusion
"People Also Ask" if SBS-III will make borders impenetrable. The honest, brutal answer is: No. Surveillance is a software problem, not a lens problem. We are still using humans to look at pictures. We are trying to find a needle in a haystack by hiring more people to look at more hay.
True "disruption" in space-based surveillance doesn't come from better optics. It comes from edge processing. The satellite should not be sending pictures back to Earth. It should be sending answers.
- Current Model: Satellite takes photo -> Sends 5GB file to ground -> Ground station processes -> Analyst looks at it -> Alert sent. (Time: 45 minutes to 4 hours).
- Contrarian Model: Satellite runs onboard AI -> Detects change in tank formation -> Sends 1kb text alert: "Movement detected at Coord X." (Time: 30 seconds).
The SBS-III program, as discussed by the panel, focuses on the former. It is a plan to build a faster horse while the rest of the world is developing the internal combustion engine.
The Hidden Cost of "Time-Bound"
When a government department demands "time-bound" delivery, quality and security are the first things to go.
I’ve seen this play out in the private sector repeatedly. To hit a launch window, engineers bypass rigorous radiation hardening or simplify the encryption protocols on the telemetry link. They "fix it in the next version."
But there is no "next version" in space. Once it’s up there, it’s a brick if the code fails.
Furthermore, the obsession with the "III" in SBS-III suggests a linear progression. We are iterating on a design philosophy from the 1990s. We are trying to win the last war. The next conflict won't be won by the side with the clearest pictures; it will be won by the side that can obfuscate their own movements while automating the detection of the enemy's.
Breaking the ISRO Monopoly
The elephant in the room is the procurement model. As long as space surveillance is a closed loop between one government agency and a few hand-picked vendors, it will remain slow, expensive, and fragile.
True innovation in this space is happening in startups that are willing to fail. They are testing "mesh networking" in orbit. They are experimenting with synthetic aperture radar (SAR) that can see through clouds and at night—something the panel mentions but fails to prioritize over traditional optical sensors.
If the government actually wanted a "game-changing" (to use their own tired vernacular) capability, they would stop trying to build a national champion and start acting as a venture capitalist for twenty different competing surveillance technologies.
The Sovereignty Trap
There is a loud argument that we must build every component of SBS-III domestically to ensure "sovereignty."
This is a dangerous half-truth. While we shouldn't be dependent on foreign platforms for the final product, the insistence on reinventing every wheel leads to the very delays the parliamentary panel is complaining about.
We are using 2020s money to build 2010s tech because we refuse to integrate "off-the-shelf" components that are five years ahead of our domestic equivalents. This isn't protecting national security; it's protecting a domestic manufacturing ego.
Real sovereignty comes from having a system that works when the shooting starts. A 100% "made-in-house" system that is blinded by a basic electronic warfare attack is useless.
Stop Polishing the Brass on a Sinking Ship
The parliamentary panel’s report is a symptom of a deeper malaise: the belief that "more" is "better."
We don't need a "time-bound" SBS-III. We need a complete "scrap-and-rebuild" of the surveillance philosophy.
- Move away from large, expensive platforms.
- Invest 80% of the budget into AI and edge computing, 20% into the bus.
- Assume every satellite is a temporary asset.
- Prioritize SAR and multi-spectral data over pretty pictures.
The current path leads to a high-definition view of our own obsolescence. If you want to secure the border, stop looking for better telescopes and start building a smarter network. The sky isn't falling, but our strategy is already crashing.
Forget the "time-bound" implementation. Kill the program and build something that isn't obsolete before it clears the atmosphere.
