SDA’s Space Network: Optical Interoperability and Supplier Competition

1. What to read when new satellites arrive

On October 10, 2026, the U.S. Space Force’s Space Development Agency (SDA) announced delivery of 21 Northrop Grumman-built Tranche 1 (T1) transport satellites. Initial capability is planned from 2027.^[1]

The question raised by this news is how a new manufacturer’s satellites communicate with those made by other manufacturers. More suppliers can expand purchasing and supply choices. But if information cannot pass to a neighbouring satellite, separate networks organised around individual manufacturers may remain. Alongside the ability to put equipment into space, the work of bringing different equipment into the same network becomes important.

Interoperability means that equipment or systems made by different companies can work together. Yet the word alone cannot describe every state of connectivity. Following common design rules, exchanging data between a particular pair of terminals, and delivering the required data through several connections involve different things to verify. This article uses those distinctions to examine the meaning of procurement from several suppliers.

This launch cannot establish that a particular company’s share price will rise or that communications costs around the world will fall. It raises a narrower question: competition in communications equipment depends on the partners a product can connect to and the effort needed to verify those connections, as well as satellite production volumes. Common design requirements developed for military use can inform assessments of components, test equipment and communications software. Profitability and civilian adoption require separate evidence.

2. What past testing reveals beyond manufacturers’ names

The U.S. Government Accountability Office’s (GAO) January 28, 2026 report observed that demonstrated Tranche 0 links between SpaceX and York satellites used Tesat terminals on both sides as of July 2025. Different satellite manufacturers need not mean different terminal implementations. That observation cannot establish a current shortfall.^[2]

That distinction changes how procurement should be read. Several prime contractors can suggest that every relevant technology comes from several sources. But separate finished-product companies may share the components or software supporting a connection, leaving a narrower area of competition. Conversely, demonstrated communication between different terminal implementations can support a broader pool of future suppliers. The important question is which implementations were paired, rather than how many company names appeared.

An announcement of a successful test becomes more informative when it identifies the equipment at the other end, the software version and the test environment. A link between a company’s own terminals is progress in product development, but does not establish the extent to which competing products can replace them. Success with one combination cannot automatically be extended to others. Readers should ask which choices the test opened up, rather than how emphatic its promotional language was.

This makes supplier diversification in defence equipment more concrete. Being able to manufacture the same device in a different factory differs from being able to choose a differently designed device. The former diversifies manufacturing locations; the latter concerns design and implementation choices. Both have value and cannot substitute for each other in a single measure. Knowing which connections can be preserved when equipment is replaced makes the practical meaning of diversification easier to assess.

Related reading: Orbital weapons and infrastructure

3. How much does a standard make common?

SDA’s Optical Communications Terminal (OCT) Standard 3.1.0, dated March 31, 2023, specifies physical and synchronisation/coding layers. It requires version identification and the derivation and implementation of requirements specific to each design. Spacecraft-bus and network interfaces are not directly specified; that does not make their requirements optional.^[3]

A standard lets different manufacturers retain their own designs while aligning the promises they must share with a connection partner. Making every internal design identical restricts development freedom. Sharing too few rules can require individual adjustments for each connection. The boundary between common requirements and choices left to suppliers helps determine how readily they can compete and how much integration work remains.

When comparing specifications, buyers should match requested requirements to the work included in a price. Even projects requesting the same inspection have different cost breakdowns if the buyer supplies the test equipment in one case and the supplier provides it in another. Comparing totals alone obscures why an offer looks cheaper. Reading competition in communications equipment requires knowing which tasks are being purchased alongside the product.

Responsibility for inspection work also affects comparability among suppliers. Ordering under aligned conditions makes price differences easier to read. Where alignment is impossible, explaining why and identifying additional tasks still helps comparison. Checking whether an equipment price includes inspection and investigation support may reduce the need to order unexpected work after delivery.

4. Look beyond the arrival of light when reading a connection test

When reading combination tests, align what counts as success and how many trials were conducted. Reporting one successful trial differs from reporting all repeated trials. Both can communicate technical progress, but the former alone cannot be used to calculate repeatability. Before judging the result, check the subject measured and the scope reported.

For example, a combination may communicate once but require the same preparation and manual adjustment every time. That does not necessarily make it easy to repeat. Tests that re-establish a connection under different conditions can reveal whether adjustments can be reduced. This is not an argument for multiplying tests indiscriminately. What matters is knowing what changed, what remained fixed and which conditions the reported result covers. Success-rate comparisons also require attention to the denominator. The number of combinations tested and the number of trials within one combination produce measures with different meanings. The former informs the scope verified; the latter informs repeatability under those conditions. Percentages with different denominators cannot establish which equipment is superior. A number accompanied by its conditions is more useful than a headline number alone.

These distinctions allow buyers to assess high performance separately from ease of integration. Excellent peak performance may coexist with expensive adjustment to other suppliers’ equipment, making another choice reasonable for some uses. Conversely, easy connection does not compensate for inadequate performance. Assessing an actual combination, rather than putting technologies into a single ranking, helps procurement from several suppliers work in practice.

5. A pairing table makes the scope of competition visible

Our first analytical framework is a table of terminal combinations. Rows and columns identify implementations; each intersection records what was tested. Tests within the same implementation, between different implementations, and combinations for which results are unknown remain separate. The figure in this article is a hypothetical explanatory example, not a pass/fail table for SDA equipment. An entry marked unverified means missing information, not failure.

With three implementations, there are three pairs of different types if direction is ignored. Four implementations produce six pairs. Actual verification need not be completed with that number of tests: reversing transmission and reception, changing software versions or changing modes can expand the scope. The numbers in the figure do not forecast performance. They show why more candidates also create more combinations to manage.

It would also be premature to conclude that more suppliers always mean higher costs. Common test procedures and reusable records could reduce the cost of checking another combination. Realising that benefit requires conditions governing what can be reused. If nobody determines whether a shared component name is sufficient or whether software versions and settings must also match, reuse may become little more than omitted verification.

The table also helps assess entry by a new supplier. The value of adding a company depends on how many existing implementations it can connect to. A verified connection with just one existing implementation can still be a meaningful first step. Failure to connect to everything immediately does not make entry worthless. Equally, that first step should not be advertised as universal compatibility. The demonstrated scope should define the scope of competition being described.

6. From a successful pair to communication through a network

SDA’s NEBULA Standard 3.05 addresses network rules including satellite-to-satellite and space-to-ground communication. The document is dated September 25, 2024; SDA describes issuing the updated standard that November. Its scope differs from the OCT terminal standard. The document’s existence does not establish test results for the latest satellites.^[4]

Our second analytical framework separates a connection between two points from communication through several connections. Suppose A exchanges data with B and B with C. Moving information from A to C adds a decision at B about where to pass that information. Consistent forwarding behaviour at the intermediate device allows separate connections to be used as a single path.

Buyers need more than a terminal’s highest rate. Relevant behaviour can include choosing among routes, prioritising traffic when communication is congested and continuing to deliver required data after a route changes. Where results are unpublished, those questions remain open. It is possible to recognise progress in individual links while waiting for further explanation of network behaviour.

As network requirements add work, the relationship between terminal sellers and integrators also changes. Terminal companies must explain how their products behave; integrators must verify how combinations behave. One party’s achievement does not remove the other’s task. Clear connection boundaries also help prevent the parties from simply shifting responsibility for additional work onto each other.

7. SG Group View: Where standardisation can create price competition

Our third analytical framework separates the parts that common requirements make contestable from those where suppliers can retain their own improvements. Shared connection rules may reduce situations in which a customer is tied to one supplier simply because of its communications partners. Customers can then compare mass, power consumption, manufacturing consistency and support for testing. Common requirements provide a basis for comparison without requiring identical products.

That change brings both benefits and burdens to suppliers. There may be less room to retain customers through a proprietary connection method alone, while opportunities to supply other companies’ satellites may expand. More potential customers become orders only if the product fits their designs, passes testing and meets delivery requirements. A declaration of compliance with a public standard is insufficient to calculate the size of the market.

Customers face additional choices too. A cheap terminal may increase total deployment costs if its combinations require substantial testing effort. A more expensive terminal is not always cheaper in the end either. Product price and the additional cost of verifying a connection should be compared separately. A statement that a product has been tested needs to identify the partners and conditions involved.

With those comparisons available, entrants can compete on how readily their products can be verified, as well as on price. Clear settings documentation, good test records and responsive problem investigation may reduce customers’ integration work. Conversely, poor documentation can slow adoption even when the equipment itself works. That value is difficult to see in production-volume headlines but matters to purchasing decisions.

Related reading: Defence procurement and industrial investment

8. Can common testing also help smaller suppliers?

In an explanation dated October 14, 2020, the U.S. Naval Research Laboratory (NRL) described its role in establishing a hardware/software-in-the-loop test environment to verify optical interoperability among multiple satellites for SDA. This is background on testing arrangements, not an announcement that a particular 2026 terminal has passed.^[5]

A shared test environment can reduce the burden of assembling a separate connection partner for each company. A small supplier entering the space market may need substantial capital if it must fund customer-specific tests on top of product development. Published conditions and access to the required equipment can make preparation easier. Without knowing access terms or waiting times, however, ease of participation cannot be established.

As testing becomes common, the choice of test conditions matters more. Conditions tailored to one existing product could unfairly disadvantage a new design. Looser conditions could leave problems in real combinations. Separating requirements that protect performance from those that mandate a particular construction method helps preserve both design freedom and reliable communication.

Sharing results also requires boundaries. Explaining problems can reduce repeated mistakes, but unrestricted disclosure of proprietary designs could weaken incentives to recover development investment. Common information need not include every internal detail. Connection conditions, methods of interpreting results and information needed to reproduce a problem should be organised alongside confidentiality limits.

9. What must be checked again when versions change?

SDA’s resources page describes its intention to use OCT 3.2.0 as the Tranche 3 standard of record, with selected terminals using 4.0.0, and a policy of compatibility with previous versions. These are procurement intentions, not verified implementations.^[6]

A version change can create demand for new functions and for continued connections with existing products. Replacing everything with the latest version can conflict with the value of continued use of installed equipment. Older equipment remaining usable does not necessarily mean that it can use every new function. Compatibility descriptions should therefore keep the ability to connect separate from available functionality.

Manufacturers may need to develop and verify changes while continuing to support existing customers. Prolonged support for an older version can prevent development staff and test equipment from being devoted entirely to new products. Supporting several versions can be a selling point, but also expands the maintenance burden. The number of versions alone proves neither superiority nor inefficiency.

Customers want to know which previous checks a modification affects. Focusing tests on affected areas could avoid repeating unrelated work, but that judgement requires traceable change records. Linking the specification version, implementation version and version-specific results rarely makes a spectacular technology headline. In procurement where equipment remains in use for years, that management work is also a competitive condition.

10. Whose estimate includes connection testing?

When reading company estimates, distinguish terminal design, manufacturing, verification with a partner and verification after a change. This is a way to avoid omitted comparison items, not an estimate of the latest contract’s costs. If component prices decline while verification work moves into another line item, total purchasing costs will not necessarily fall by the same proportion. A cheap product and a cheap deployment are different propositions.

Suppose a connection problem cannot initially be attributed to either device. Investigation requires cooperation from both parties. Counting only one party’s hours biases a cost comparison. Adequate common test records could narrow the search for a cause. Their value should be assessed by comparing resolution time and reproduction work across similar cases. Actual hours and percentage savings should be assessed from comparable measurements. If the supplier bears verification costs under a contract, additional work may reduce its profit. If the buyer pays separately, procurement expenditure may rise. Neither arrangement makes the problem disappear. The relevant questions are who bears necessary work and how ordered changes are treated. Actual responsibility must be checked in the individual contract.

To look for the effect in financial results, explanations of development expenditure, testing costs and profitability are more useful than converting a satellite count directly into revenue or profit. If optical terminals are only a small part of a company, a group-wide margin cannot readily reveal terminal-business performance. Our financial-statements guide provides a foundation for separating earnings and cash. Assessing supplier returns on this delivery requires additional cost and contract information.

Related reading: Read connected financial statements

11. How effects could reach the global components industry

If military optical-communications procurement grows, the first effects would reach the equipment producers and suppliers supporting manufacturing and testing. Optics, electronics, assembly, software and testing involve different skills. Knowing that a company participates does not identify the activity from which it earns revenue. Country-level component procurement or the size of the overall market cannot be derived from the published spacecraft count.

Common requirements may let development for one customer be reused for another. Reuse can spread the same development investment across more products. Different spacecraft designs and test conditions can still require additional work, however. The value of a shared specification should be read through three separate questions: which designs can be reused, what work must be added and which customers can actually buy the product.

Supply-chain effects can extend beyond product sales to test-equipment suppliers and services that combine different devices. One-off equipment delivery differs from work repeated after design changes. Even recurring work may later be taken in-house by the customer. A need for repeat tests should not be treated as proof of permanent revenue.

Wider economic effects become stronger if technologies and equipment can also be used in other markets. Expansion into civilian communications or other countries’ procurement requires use-specific conditions and customer approval. Military-standard compliance alone does not determine commercial success. This launch provides no basis for a direct change in world growth or inflation. Supply-chain analysis should follow actual orders through inventory and investment rather than skip those links.

Related reading: Supply chains, delivery times and inventory

12. Connections with allies also have non-technical boundaries

Common technical specifications help companies in different countries understand the same design target. But participation and access to particular data are separate decisions. Customers determine who can receive what; owning equipment capable of communicating does not confer information-access rights. The delivery does not establish approval to connect with a particular country or a new export authorisation.

That boundary matters when assessing international business opportunities. A product may meet specifications while procurement participation conditions and approvals still require work. Conversely, permission to participate does not advance delivery if the product fails its connection tests. Checking technical and participation conditions separately avoids counting every company able to read a public standard as an actual supplier. Data-related work also requires care about how much is shared for interoperability. Problem investigation needs records, but decisions about who receives their contents remain a separate management matter. Clear explanations of tests do not require broad publication of confidential information or intellectual property. Designs that connect readily need to be considered alongside procedures that protect information.

International importance is not confined to a network’s cross-border geography. More suppliers able to understand specifications and pass tests could change purchasing negotiations. Continued dependence on one implementation could instead concentrate bargaining power there. Participation conditions and connection evidence help determine which outcome emerges. Our article on warfare in the AI era provides broader context, not a source of pass/fail results for individual optical terminals.

Related reading: Warfare in the AI era Full article requires paid access

13. What market announcements reveal—and what numbers they do not

Investors reading the next company announcement should ask what was tested and which customers’ designs can use it, as well as the total value of orders. Evidence of compatibility with a new combination may support a broader sales opportunity. Repeated verification of an existing combination under the same conditions can provide evidence of consistency. Both can be valuable, but the latter does not have the same meaning as an expanded customer opportunity.

On April 27, 2026, General Atomics announced that, following government verification at MIT Lincoln Laboratory’s testbed, it would progress to flight-hardware production and demonstration in the separate Enterprise Space Terminal programme. Results from this separate programme cannot establish performance for other equipment.^[7]

When comparing such announcements, distinguish a company’s account, the customer’s confirmation and the testing organisation’s explanation. Each source has a different scope and responsibility. A company’s description of technical progress may be real while its revenue implications still require other information. Company statements need not be ignored, but they should not be treated as having filled every gap relevant to an investment decision.

Valuation involves both expectations about future orders and costs and expectations already embedded in the share price. Progress ahead of expectations may support a higher assessment; progress exactly as expected may change little. The day’s market response requires trading data; individual-security valuation requires separate company and price evidence. Returning to valuation fundamentals helps prevent technical progress from being turned directly into a claim that a stock is cheap.

Related reading: Using equity valuation ratios

14. Several suppliers are not always the best immediate choice

A reasonable counterargument is that using one implementation can accelerate connection verification. Additional suppliers create more parties and combinations to coordinate. Urgent procurement can have reasons to prioritise combinations already shown to work. Recognising the value of multiple suppliers does not require downgrading success with a shared implementation. The question is whether future choice is included when comparing short-term simplicity.

The idea that one supplier removes all uncertainty also has limits. Products from the same company can require verification when versions, settings or associated equipment change. A shared manufacturer’s name does not justify ignoring those changes. The useful comparison is not an abstract choice between one company and several. It is the work needed to use the intended combination and the changes that remain possible later.

Another counterargument is that strict common requirements can make new designs harder to adopt. Prioritising connections with installed equipment may constrain how new functions are used, while protecting existing customers’ ability to continue operating. The appropriate choice depends on the purpose. Reasons to preserve compatibility and reasons to test new functions separately should be explained in relation to the use case and time constraints.

Concerns that common testing slows development also deserve a concrete answer. Testing that reduces real adjustment could prevent later rework; testing unrelated to actual use may add burden without the same benefit. Test counts should not stand in for quality. It is more useful to ask which uncertainty a test reduced and which decision it informed. This article does not treat procurement from multiple suppliers as unconditionally superior.

15. What evidence would change this analysis?

Comparable results for different optical-terminal implementations would make connection choices easier to assess. Results across versions would also help if their scope were clear. The products involved must be identified. Success by equipment unrelated to the new satellites should not be imported as an estimate of unpublished performance for those spacecraft.

Comparative evidence that reusing test work reduced the time or cost of checking an additional combination would support the economic case for standardisation. Conversely, substantial customer-specific modification despite shared specifications would weaken expectations of savings from reuse. Subjects and conditions should be aligned. Comparing an intrinsically difficult project with an easy one cannot establish that standardisation alone caused the cost difference.

Records of an actual supplier replacement that preserved communication with existing partners would also be important. They would show whether procurement options had moved beyond a paper possibility. Continued dependence on one implementation would weaken assessments of competition based solely on the number of finished-product manufacturers. If requirements or uses changed at the same time as equipment, a simple before-and-after comparison would not establish the cause.

Useful evidence need not be entirely favourable. An explanation of a combination’s problem, its cause and its scope can inform subsequent testing and procurement. Blaming a company name without understanding the cause gives readers little basis for deciding what must change. Our analysis is conditional: connection verification can support competition. If evidence increasingly shows those conditions are not met, the outlook should be revised.

16. Track connection partners as well as spacecraft counts

Relevant follow-up includes tests across implementations, explanations of test conditions, data transport within the network and responses to changes in standards. Adding satellites can provide an opportunity to expand those connections. Without anticipating unpublished achievements, accumulating evidence about verified combinations helps reveal how much procurement competition has been realised.

Military effects cannot be obtained by converting a communications technique directly into superiority on a particular battlefield. Evidence about data, mission requirements and operating conditions is also needed. Optical-terminal interoperability is one supporting condition. Connection demonstrations alone cannot estimate combat capability or missile-defence success rates. Technical progress in communication and results for a particular mission remain separate subjects.

Connections with the world economy may first appear in procurement choices, reused development work, testing activity and company costs. Expansion into civilian uses or international supply chains depends on further orders and verification. Military-communications news need not be inflated into a sweeping economic shift. Seemingly small specifications and testing conditions can matter by changing which companies can sell and who performs integration work.

The questions to retain are straightforward. Alongside the number of companies involved, which implementation connected with which partner, under which conditions? Can that verification be reused for the next product? More evidence answering those questions makes space-communications competition more tangible. Spacecraft counts, manufacturers’ names and standards’ names should be assessed together with connection evidence, rather than on their own.

FAQ

Primary sources and verification scope

1. SDA — Fourth orbital plane delivery 2026-10-10
2. GAO — GAO-26-107085: observations primarily from 2025 2026-01-28
3. SDA — OCT Standard 3.1.0 (document date) 2023-03-31
4. SDA — NEBULA Standard 3.05 (document date; updated-standard issue November2024) 2024-09-25
5. NRL — Interoperability testing role 2020-10-14
6. SDA — Resources: future-procurement OCT3.2.0/4.0.0; page publication date unknown Checked2026-10-12
7. General Atomics — Company announcement for the separate EST programme 2026-04-27
8. SDA — Third launch and 63 T1 spacecraft on orbit 2026-07-16

Event/announcement dates, document dates and retrieval dates are distinguished. Hypothetical diagrams and counts illustrate concepts and do not estimate equipment results, costs or combat capability.