NEC used its NEXTAR NX-300L bus for two different Earth-observation spacecraft: the optical ASNARO-1 and the radar-equipped ASNARO-2. The pairing demonstrates a central principle of standardized satellite manufacturing. A common platform can support different missions without requiring the payloads themselves to be identical.
Standardization concerns the equipment, interfaces, software, and production processes that a manufacturer can reuse. Customization concerns the changes needed for a particular mission. Most commercial spacecraft occupy a position between a completely unchanged catalog product and a platform designed entirely around one instrument.
A satellite bus supplies the supporting functions described in New Space Economy’s explanation of spacecraft components. The bus provides power, computing, communications, orientation control, and thermal support. The commercial decision concerns how much of that supporting architecture can remain common when the payload or mission changes.
What Manufacturers Standardize
A standardized bus begins with an established design. Its manufacturer can reuse circuit designs, flight software, structural arrangements, test equipment, and documented procedures. Some suppliers retain a common electronics architecture across spacecraft of different external dimensions.
This reuse changes the engineering task. Instead of developing every subsystem anew, the manufacturer configures a known platform and checks the parts affected by the mission. The payload still has to connect correctly to the bus, but existing interfaces can define much of that work.
The word “standardized” can describe several levels of commonality. A supplier can use the same computer on multiple buses without making the whole spacecraft identical. Another can offer a fixed mechanical structure with alternative battery capacities. A third can manufacture a repeated spacecraft configuration for a constellation.
These approaches create different production benefits. Common electronics support repeated assembly and testing. Common structures support repeatable tooling and mechanical procedures. A repeated complete configuration allows a production team to apply the same integration sequence across multiple flight units.
Where Custom Design Enters
Customization becomes part of the platform when a payload imposes requirements outside the existing configuration. An instrument can need a larger mounting area, a different electrical supply, a particular thermal interface, or more precise control of its orientation.
Mechanical customization can preserve common electronics. Surrey Satellite Technology describes its SSTL-MINI as using its core avionics with a structure tailored to the mission and payload. This separates reusable spacecraft functions from the physical arrangement needed by the instrument.
A structural change affects more than appearance. Moving equipment changes the distribution of mass and the paths through which launch loads pass. It can also change heat transfer and the way the spacecraft responds to motion. The engineering work follows those effects.
Electrical changes have similar connections. A larger payload can require more power generation, greater storage capacity, or a different operating schedule. Changing the battery alone does not change how much energy the solar array collects during an orbit. The complete electrical system determines what operating pattern the platform can support.
Custom design concerns coordinated changes. A manufacturer can retain established equipment where it fits and modify the parts that determine the new mission’s performance.
Cost and Repeated Production
A satellite program contains development work and repeated manufacturing work. Development includes designing the configuration, analyzing its behavior, preparing software, and establishing how it will be tested. Repeated manufacturing includes producing, assembling, inspecting, and testing subsequent flight units.
A common platform allows development effort to serve more than one spacecraft. Reusing an established computer or power unit avoids redesigning that equipment for each mission. Repeated production also gives technicians a familiar assembly and inspection sequence.
Customization changes that allocation. Engineering devoted to a unique instrument interface or structural arrangement belongs more directly to the mission requiring it. If the same configuration is then ordered repeatedly, the resulting design can itself become the basis of standardized production.
Order size and design commonality are related but separate. A manufacturer can build one spacecraft using catalog subsystems. It can also produce many spacecraft based on a customer-specific configuration. The number of units does not alone establish whether the initial design was standard or custom.
The resulting cost relationship is specific to the program. Standardization reduces repeated design work where the established configuration meets the mission. A custom platform can avoid carrying equipment or capacity that the payload does not need. The useful comparison is between complete mission configurations, including the work required to integrate them.
Scheduling and Integration
An existing bus design gives a project an established starting point. Drawings, interface definitions, software, and test procedures can already exist. The supplier can focus the mission-specific work on payload accommodation and the selected configuration.
Lead time also depends on the equipment entering production. A platform assembled from standard parts still follows the procurement and manufacturing schedules for those parts. Integration begins when the necessary equipment and documentation are available.
The payload interface is a particular source of schedule coordination. The bus supplier needs the instrument’s mass properties, power demands, data connections, thermal characteristics, and operating modes. The payload team needs the platform’s interfaces and resource allocations.
These exchanges connect the two development efforts. A change in the instrument can require a change in the bus configuration, and a platform change can affect the instrument’s operating plan. Defined interfaces provide a common reference for both teams.
Performance Within a Product Family
Manufacturers can offer performance choices within a common architecture. Moog’s Meteorite configurations include versions emphasizing baseline capability, additional propulsion, or higher-performance payload support. The family approach uses related spacecraft technology to serve missions with different demands.
A configurable product can offer more than one answer to a customer’s requirements. A payload needing additional operating time can use a different electrical configuration. A mission requiring more orbital movement can use a propulsion configuration with greater capacity.
The resulting spacecraft still needs to be assessed as a complete system. Additional propellant changes launch mass. Larger arrays affect the deployed mechanical configuration. More capable equipment can draw more electricity or produce more heat.
Performance specifications describe the selected configuration rather than a collection of independent maximum values. The largest payload capacity, greatest power availability, and highest maneuvering capability do not automatically belong to one simultaneous operating condition.
Flight Heritage and Design Continuity
Flight heritage records experience with equipment or configurations that have operated in space. It can apply to a component, an integrated subsystem, or a complete platform. The distinction determines how that experience relates to a new spacecraft.
A bus can retain flight-used avionics but introduce a new structure. It can use an established structure with a new propulsion system. Both contain inherited engineering, but their new combinations involve additional integration work.
Manufacturers maintain design records so that a delivered unit can be associated with the components, software, processes, and tests used to produce it. That configuration information connects previous experience to later production.
Standardization supports this continuity because repeated units share more of their design. Customization can preserve it selectively by keeping established elements unchanged. The two methods frequently operate together within one spacecraft program.
The Customer’s Delivered Product
The distinction between standard and custom design also affects what the customer receives. A catalog bus can include defined interfaces and a limited selection of configurations. A custom development can include engineering deliverables and equipment specific to the customer’s mission.
Neither label establishes the contract’s complete scope. Payload integration, environmental testing, launch support, ground equipment, and operations can be included or supplied separately. The delivery boundary determines which organization performs each activity.
NEC’s ASNARO platform examples show the practical result of combining reuse with mission-specific equipment. An established bus supported an optical satellite and a radar satellite, preserving common supporting technology as the instruments and their observation methods changed.

Useful Books Available on Amazon

