Join us at Space-Comm Expo in London on March 11-12, 2025! Visit stand C08 for a live demo of HELIX® Ops and meet our experts to explore how HELIX® Engineering Services can support your mission. 

Managing satellite operations is complex, but with HELIX Engineering Services, space companies can now benefit from expert-led software development tailored to their exact needs. Designed to complement our HELIX suite of space software products, these services provide seamless development, integration, customisation, and scalability across the satellite lifecycle. 

HELIX products integrate software systems from construction and testing to in-orbit control and service delivery. With HELIX Engineering Services, companies gain the flexibility to extend functionality, optimise operations, and scale as needed without costly rework. 

One of our first offerings, Operations Software Development & Integration via HELIX Ops, delivers a powerful, intuitive, and cost-effective mission control environment. Our team works closely with clients to ensure smooth integration and efficient operations, even as mission needs evolve. 

“No two missions are the same, but each unique software system needs to keep pace with evolving requirements. With HELIX Engineering Services, we make sure our customers to get exactly what they need today while ensuring flexibility for tomorrow—whether that’s scaling operations, adding new capabilities, or handling unexpected mission challenges.” Richard Adams, Sales Director at Bright Ascension. 

See HELIX Ops in action at Space-Comm! Visit stand C08 to connect with our team and discover how our engineering services can help you achieve mission success. 

The challenge of scaling satellite development

Developing satellite constellations is a complex, resource-intensive endeavour. Traditional software development for satellites is often fragmented, expensive, and time-consuming, hindering innovation and efficiency. Flightkit, a modular and reusable development kit for flight software, offers a smarter approach to building satellites. By simplifying and accelerating satellite software development, Flightkit empowers satellite operators to reduce costs, shorten development timelines, and future-proof their missions.  

The challenges in traditional flight software development  

Satellite operators and developers face significant hurdles when creating and scaling flight software for modern constellations, including: 

So, how do we streamline flight software development for the modern space era? 

Enter Flightkit: A smarter approach 

Flightkit is a modular, reusable flight software development kit designed to accelerate satellite development, reduce costs, and simplify operations. Built to provide flexibility, scalability, and efficiency, Flightkit empowers satellite developers to focus on mission success rather than reinventing the wheel. 

How Flightkit transforms satellite software development 

1. Modular architecture: Faster development and reusability 

Flightkit enables developers to reuse pre-built software components instead of coding from scratch, significantly reducing development cycles. 

Impact: Teams using modular software architectures reduce development timelines by up to 40%, accelerating go-to-market strategies. 

2. Cost-effective scalability for large constellations 

Scaling a satellite fleet requires standardisation, reliability, and easy integration. Flightkit is designed to: 

Impact: Teams can scale operations 2x faster while reducing maintenance overhead. 

3. Vendor independence and long-term flexibility 

Traditional proprietary solutions often lock developers into a single ecosystem, limiting flexibility. With Flightkit: 

Impact: Developers gain long-term strategic flexibility, avoiding costly rework. 

4. Proven reduction in time-to-market 

Long development cycles can delay launches and reduce market competitiveness. Flightkit optimises this by: 

Impact: Operators can bring missions to market up to 6 months faster, enabling them to capitalise on emerging opportunities. 

Flightkit in action

Flightkit provides value across a range of satellite missions, from small satellite programs to large-scale constellations. 

For small satellite developers – Build and deploy quickly without investing in expensive bespoke software. 

For constellation operators – Maintain software consistency across fleets, reducing operational complexity. 

For future missions – Develop scalable, adaptable software that grows with evolving mission needs. 

Why satellite developers are switching to Flightkit 

Flightkit is more than a development tool; it’s a strategic advantage for satellite developers seeking to streamline their development processes while maintaining flexibility for the future. Key benefits include: 

Scalability and adaptability – Flightkit grows with your constellation needs, ensuring consistent performance across missions. 

The future of satellite software development starts here  

As the space industry evolves, satellite developers need tools that empower them to innovate faster, scale efficiently, and remain competitive. Flightkit delivers these needs by providing a modular, cost-effective, and vendor-independent solution for flight software development. 

Whether you’re a small satellite developer or managing a large constellation, Flightkit simplifies development, reduces costs, and prepares your mission for future success. 

Ready to learn more? Schedule a demo of Flightkit today and see how it can transform your satellite development process. Contact us.

As we look ahead, 2025 appears poised to bring notable changes to the space industry. In our view, the evolving landscape is characterised by a gradual blurring of boundaries between traditional space organisations and so-called ‘NewSpace’ companies. This shift reflects a growing focus not just on increasing the number of spacecraft in orbit, but on fostering a more interconnected, efficient, and commercially sustainable ecosystem spanning the entire value chain, from upstream to downstream. 

The evolution of ‘NewSpace’: Does the term still hold value? 

The term ‘NewSpace’ has long represented innovation, agility, and risk-taking in the space sector. However, as the industry matures, the boundaries between traditional and NewSpace players are becoming increasingly blurred. Historically, NewSpace companies thrived by prioritising speed, cost-effectiveness, and rapid iteration. But as these organisations invest in higher-quality hardware and navigate growing mission complexity, they’re putting more priority on practices traditionally associated with the established sector, such as stringent quality assurance and more robust development processes—though they remain far from fully adopting traditional methods. Meanwhile, traditional players are responding to competitive pressures by embracing faster timelines and leaner operational models. This convergence highlights a shift towards a “middle ground” where efficiency and adaptability are critical for success. 

In this context, while ‘NewSpace’ might still serve as a shorthand for certain approaches, its practical relevance is waning. What truly matters is not whether a company identifies as NewSpace or traditional, but how effectively it operates within this evolving spectrum—delivering value, driving innovation, and meeting the increasingly complex demands of the space-based value chain. 

What lies ahead in 2025? 

2025 promises to usher in a new growth phase for the space industry. Instead of focusing primarily on expanding the number of spacecraft and exciting cutting-edge technology in orbit, the emphasis will shift toward optimising the value chain and addressing customer needs holistically. This shift will present both challenges and opportunities for NewSpace companies and traditional players alike. 

Key challenges: 

  1. Aligning with end-user needs: Companies will need to move beyond isolated solutions and offer integrated capabilities that resonate with downstream market demands. 
  1. Commercial sustainability: Securing funding and revenue streams will increasingly depend on demonstrating clear value propositions to customers and investors. 
  1. Managing complexity: As missions grow more intricate, balancing innovation with reliability and cost-effectiveness will become essential. 

Opportunities for growth: 

  1. Value chain integration: Businesses that can seamlessly connect upstream development and operations with downstream service delivery capabilities will be well-positioned to thrive. 
  1. Customer-centric innovation: By focusing on the practical applications of space technology—from Earth observation to IoT and beyond—companies can unlock new revenue streams and foster deeper customer engagement. 

Efficiency and collaboration: Partnerships and ecosystem-based approaches will play a vital role in enhancing operational efficiency and enabling more ambitious missions. 

HELIX®: Connecting the dots across the value chain

At Bright Ascension, we envision HELIX® to play a significant role in this industry transformation.  

HELIX is an integrated, modular platform covering the end-to-end lifecycle of satellite development, operations and space-based data or service delivery. It tackles critical challenges across the entire space sector value chain: upstream, involving the development and operation of space systems; midstream, focused on delivering and managing space-based services; and downstream, where space services are used to provide actionable insights and applications. By seamlessly connecting and streamlining operations across these sectors, HELIX addresses long-standing gaps, reduces complexity and significantly lowers the total cost of missions. 

HELIX embodies the principles that the industry is likely to prioritise in 2025 and beyond: efficiency, adaptability, and customer-driven value. In a world where the space sector’s centre of gravity is shifting toward the middle, HELIX provides the tools needed to stay ahead of the curve and unlock the full potential of the space industry value chain. 

The future of space: A unified vision 

As the space industry continues to evolve, the key to success will lie in connecting the dots—between technology and customer needs, innovation and practicality, and upstream and downstream value. The convergence of traditional and NewSpace approaches signals a move toward a more collaborative, integrated, and efficient future. 

With solutions like HELIX leading the charge, 2025 could mark the beginning of a new era for the space industry, where efficiency and connectivity drive growth and enable humanity to achieve its most ambitious goals in space. The question is no longer what separates NewSpace from the traditional sector, but how we can work together to master the challenges and opportunities of this exciting new chapter. 

Contact us for more information or to schedule a demo.

Cut costs, boost efficiency, and scale with confidence

 

Managing satellite constellations has never been more complex. Flightkit, developed by Bright Ascension, provides a ground breaking software solution that simplifies operations, reduces costs, and prepares your constellation for the future.

Why chose Flightkit?

Save more, do more

    • Reduce development costs with reusable software frameworks and modular architecture.

    • Minimise operational expenses with seamless flight and ground system integration.

    • Eliminate inefficiencies caused by fragmented tools and workflows.

 

Simplify your process

    • Accelerate time to launch with ready-to-deploy software modules.

    • Streamline workflows by integrating all aspects of flight and ground operations into a single, cohesive solution.

    • Ensure smooth scaling and compatibility with future missions.

 

Future-proof your constellation

    • Vendor-independent design for flexibility and adaptability.

    • Scale with ease, managing constellations of any size.

    • Focus on growth, knowing Flightkit evolves with you.

See Flightkit in action

Find out how Flightkit can revolutionise your satellite projects. Get in touch today!

REQUEST A DEMO OR SPEAK TO AN EXPERT:

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

We are returning once again to the Ignite Space 2025 event, organised by the UKSA. Ignite Space is a dynamic and interactive event designed specifically for SMEs within the UK space sector.

Brought by the UK Space Agency, Ignite Space will act as a catalyst for commercial success, creating opportunities for SMEs to engage with new customers, collaborators and investors within the UK space industry and its supply chain.

Our team will bring an interactive demo of our upcoming HELIX suite and will be showcasing the products included in the suite that are set to re-shape the space software industry. Learn how to develop your mission faster and cheaper and help it grow and evolve efficiently with our current and upcoming products and solutions.

Join us on Stand 1 on 5-6th of February at the National Space Centre in Leicester. Visit the Ignite Space 2025 website to reserve your spot by booking your free ticket.

Visiting Space Tech Expo in Bremen?

Don’t miss the perfect opportunity to get an interactive demo of our upcoming HELIX suite, discover what products are included and how HELIX is going to re-shape the space software industry.

Learn how to develop your mission faster and cheaper and help it grow and evolve efficiently with our current and upcoming products and solutions.

Join us on Stand D25 in Hall 4 on 19th-21st of November or book a meeting today with our sales team: enquiries@brightascension.com. 

For much of the space industry’s history, missions have been designed around individual spacecraft.

A spacecraft has a payload.

A ground segment controls it.

A mission team operates it.

Data is collected, processed and delivered to its intended users.

The architecture can be complex, but the boundaries are relatively clear.

That model is changing.

Modern space missions increasingly involve constellations of spacecraft, multiple payloads, distributed ground infrastructure, cloud computing, communications networks and downstream applications.

Different systems may be supplied by different organisations and operate across different technology environments.

Increasingly, the value of the mission comes not just from what each individual system can do, but from how effectively the systems work together.

This is the idea behind a systems-of-systems approach.

And it has important implications for how scalable space systems need to be designed.

What is a system-of-systems?

A system-of-systems is an architecture made up of multiple independent systems that work together to provide capabilities that would be difficult or impossible for any one system to provide alone.

Each individual system can have its own purpose, architecture, owner and development lifecycle.

When connected, however, they can contribute to a larger capability.

In space, examples might include:

  • Multiple satellites working as a constellation
  • Spacecraft and different payloads operating together
  • Multiple ground stations supporting a fleet
  • Flight and ground software interacting across a mission
  • Spacecraft, ground and cloud computing working as a distributed architecture
  • Multiple sensing and communications systems supporting a common service
  • Space-based infrastructure feeding data into terrestrial applications

The individual components remain important.

But the overall value increasingly comes from their interaction.

Why is the industry moving towards systems-of-systems?

Several trends are pushing the space industry in this direction.

Constellations are increasing the number of spacecraft contributing to a service.

Payloads are becoming more sophisticated and generating more data.

Onboard processing is allowing spacecraft to make more decisions locally.

Cloud technologies are expanding the computing and storage available on the ground.

AI is creating new ways to process data and support mission decisions.

Downstream applications increasingly expect information from multiple sources rather than a single spacecraft.

These developments create opportunities to combine capabilities in new ways.

Instead of relying on one spacecraft or one technology, organisations can increasingly build services from multiple systems.

This can improve resilience, flexibility and capability.

But it also introduces a new level of architectural complexity.

The value is in the connections

A systems-of-systems architecture is more than a collection of systems.

Its value comes from the interactions between them.

Consider an Earth observation service.

A satellite collects imagery.

An onboard processor identifies relevant information.

The spacecraft transmits selected data.

Ground infrastructure processes it further.

Cloud infrastructure performs additional analysis.

An AI model identifies patterns.

The resulting information is delivered to a customer application.

No single component provides the complete service.

The capability emerges from the chain of interactions.

That means the connections between systems can become just as important as the systems themselves.

Scaling individual systems is not enough

One of the challenges of systems-of-systems architectures is that individual systems can scale successfully while the overall architecture struggles.

A satellite manufacturer can increase spacecraft production.

A cloud provider can increase computing capacity.

A ground operator can increase available infrastructure.

A software team can increase the capabilities of its platform.

But if those systems cannot interact effectively, increasing the capacity of one part does not necessarily increase the capacity of the whole.

This is a key characteristic of complex architectures.

The constraint often appears at the boundaries.

As more systems are connected, the number of interactions increases.

That can create bottlenecks in integration, data exchange, operations and maintenance.

Fragmentation becomes more significant at scale

Fragmentation is manageable when systems operate independently.

It becomes much more consequential when those systems need to work together.

A single mission may contain multiple software environments.

A constellation may include different spacecraft generations.

Ground infrastructure may come from several suppliers.

Payloads may have their own software and data formats.

Downstream applications may require information from multiple sources.

Each individual system may be well designed.

The problem is what happens between them.

Different interfaces need to be integrated.

Different assumptions need to be aligned.

Different data structures need to be understood.

Different operational models need to work together.

As the number of systems increases, these interactions can become increasingly difficult to manage.

This is why fragmentation and systems-of-systems architecture are closely connected.

Interoperability is the foundation

If systems-of-systems architectures depend on interaction, interoperability becomes fundamental.

But, as discussed in our article on space systems interoperability, interoperability is about more than connecting systems.

A system needs to be able to understand and use the information produced by another system.

This becomes increasingly important as more processes become automated.

Imagine multiple spacecraft contributing to a common mission.

Each spacecraft may report its own status.

A ground system may need to determine which spacecraft can perform a particular task.

An operations platform may need to coordinate those resources.

A downstream application may then need to understand the outcome.

If the systems use different definitions, assumptions or contexts, the technical interfaces may function while the wider process still fails.

At systems-of-systems scale, preserving meaning across boundaries becomes critical.

Systems-of-systems need information, not just data

There is an important difference between data and useful information.

A spacecraft can transmit telemetry.

A ground system can receive it.

But to make a decision, the receiving system needs to understand what that telemetry represents and how it relates to the wider mission.

This is why semantics and context become increasingly important as architectures become more distributed.

The challenge is not simply:

Can System A communicate with System B?

It becomes:

Can System B understand what System A is telling it well enough to act on that information?

That distinction may become particularly important for AI-driven and autonomous operations.

Automated systems cannot reliably coordinate complex activities if the information they receive lacks sufficient context.

AI makes systems-of-systems more powerful — and more demanding

AI can provide significant value within individual systems.

It can help process imagery, identify patterns, optimise operations and support decision-making.

But the greatest opportunities may come when AI can operate across multiple sources of information.

Imagine an AI system able to combine:

  • Spacecraft telemetry
  • Payload data
  • Weather information
  • Ground station availability
  • Orbital information
  • Communications constraints
  • Historical mission data

The resulting intelligence could potentially support decisions that would be difficult for any individual system to make.

But this requires those sources to be accessible and understandable.

If information remains trapped within separate silos, AI is limited by the boundaries of the systems around it.

In this sense, interoperability becomes an enabler of AI.

The more effectively systems can share meaningful information, the greater the potential for higher-level intelligence across the architecture.

Edge computing adds another layer

The same principle applies to edge computing.

Processing information onboard a spacecraft can reduce latency, manage bandwidth and enable faster decisions.

But once processing is distributed between spacecraft, ground infrastructure and cloud environments, the mission becomes more interconnected.

An onboard processor may identify an event.

The ground system may need to respond.

A cloud platform may perform additional analysis.

An operator may need to review the result.

A downstream customer may need access to the information.

The processing may happen in different places, but the mission needs to function as one system.

This is another reason why edge computing and interoperability need to develop together.

Systems-of-systems do not mean one giant system

A common misconception is that creating a systems-of-systems architecture means trying to integrate everything into one enormous platform.

That is not necessarily desirable.

Independent systems can provide important advantages.

Different organisations can innovate independently.

Specialist technologies can be introduced without redesigning the entire architecture.

Customers can choose between suppliers.

New capabilities can replace older ones.

This diversity can create resilience and reduce dependence on a single technology provider.

The objective should therefore not be to eliminate independence.

It should be to make independent systems able to cooperate effectively.

Avoiding the vertical integration trap

One way to simplify system integration is to bring everything under one organisation.

Vertical integration can provide significant advantages.

A single organisation can control the interfaces, architecture and development process.

This can reduce immediate integration friction.

But there can also be trade-offs.

A tightly integrated technology stack can make it harder to introduce external innovation.

It may reduce supplier diversity.

It can create dependence on a particular technology environment.

And optimisation within one organisation does not necessarily produce the best outcome for the wider ecosystem.

For an industry that depends on diverse suppliers and rapid technological development, maintaining the ability to combine independent capabilities remains valuable.

The challenge is therefore to achieve coherence without requiring uniformity.

Designing for systems-of-systems from the beginning

Systems-of-systems architectures require a different approach to system design.

Instead of thinking only about the capabilities of individual components, architects need to consider how those components will interact.

Important questions include:

  • What information needs to cross system boundaries?
  • How will that information be represented?
  • How will systems understand its meaning?
  • Which capabilities need to remain independent?
  • Which capabilities should be shared?
  • How can new systems be introduced?
  • How can existing systems evolve?
  • What happens when one component is replaced?
  • How can security be maintained across different environments?

These questions need to be considered throughout the system lifecycle.

Interoperability cannot simply be added at the end.

Modularity becomes increasingly important

Systems-of-systems architectures need to accommodate change.

A spacecraft may be replaced.

A payload may be upgraded.

A ground provider may change.

A new AI capability may be introduced.

A different cloud environment may be required.

If every change requires significant redesign across the entire architecture, scalability becomes difficult.

Modularity provides another approach.

Systems can retain their independence while interacting through defined infrastructure and information structures.

This means components can evolve without necessarily forcing the entire architecture to change with them.

The result is a more adaptable system.

The role of reusable software infrastructure

Software is increasingly becoming the layer that connects these systems.

Hardware provides capability.

Software defines behaviour.

Interfaces allow systems to interact.

Infrastructure provides the common foundations that allow those interactions to happen consistently.

This creates an opportunity to move away from building every mission as an entirely independent software environment.

Reusable infrastructure can provide common capabilities while leaving space for mission-specific development.

This is particularly important when systems-of-systems architectures need to support many different missions and technologies.

The infrastructure does not need to dictate what every system does.

It needs to make it easier for those systems to work together.

Building scalable systems without eliminating diversity

The space industry’s diversity is one of its strengths.

Different organisations bring different technologies, expertise and approaches.

New companies can introduce capabilities that established suppliers may not develop.

Customers can choose technologies that fit their requirements.

Systems-of-systems architectures can build on that diversity rather than trying to remove it.

The key is creating enough common infrastructure for those systems to interact effectively.

That means standardising where standardisation creates value.

It means providing common interfaces where they reduce integration effort.

And it means preserving the information and context required for systems to understand each other.

The objective is not a single technology stack.

It is an ecosystem that can work together.

From spacecraft to space ecosystems

As the industry matures, the concept of a mission is becoming broader.

A mission may no longer be defined by one spacecraft.

It may involve a network of space assets, ground infrastructure, computing resources, communications systems, software platforms and downstream applications.

The boundary between the individual systems becomes less important than the capability created by the network as a whole.

This creates enormous opportunities.

But it also means that scalability can no longer be considered only at the component level.

The industry needs to consider how entire architectures scale.

How easily can another spacecraft be added?

How easily can a new payload be integrated?

How easily can a new supplier participate?

How easily can a new application consume the resulting data?

How easily can the system adapt when technology changes?

These are systems-of-systems questions.

The next challenge is infrastructure

Building more capable spacecraft is only part of the challenge.

Building more powerful processors is only part of the challenge.

Developing better AI models is only part of the challenge.

The wider opportunity lies in connecting these capabilities.

As space systems become more distributed, the industry needs infrastructure that allows diverse technologies to participate without requiring every component to be rebuilt or replaced.

That infrastructure needs to support interoperability, modularity and scalability.

It needs to allow systems to evolve independently while still contributing to a larger capability.

And it needs to reduce the friction that currently exists between different parts of the space supply chain.

The future of scalable space systems is therefore not about building one perfect system. It is about making many capable systems work together.

Explore the wider challenge

The move towards systems-of-systems is part of a much broader shift in the space industry.

In Unlocking the $1T Opportunity: Solving Fragmentation in the Space Supply Chain, we explore how fragmentation, bespoke software and disconnected technologies can constrain scalability — and why interoperable software infrastructure could help unlock the next phase of space industry growth.

HELIX and systems-of-systems

HELIX® is designed to provide software infrastructure that helps diverse systems work together across the space mission lifecycle.

Its modular architecture supports capabilities across flight, payload, ground and mission operations, while allowing organisations to adopt individual components rather than requiring an entire technology stack to be replaced.

This provides a foundation for building systems-of-systems architectures while retaining the diversity and flexibility of the wider space supply chain.

Discover how HELIX supports scalable, interoperable space systems 

We are delighted to announce that we have become a member of Space4Climate, an organisation representing the UK’s world-leading Earth Observation expertise and global collaborations regarding climate data.

With over 50 software deployments in orbit, we know that the effective delivery of downstream solutions, space-based insights and analytics requires a deep understanding of the upstream processes involved in satellite construction, deployment, and operations. This unique expertise enabled us to develop tailored solutions for a variety of sectors on the ground, such as Earth observation and climate monitoring, that seamlessly integrate with satellite systems, optimise data collection processes, and deliver actionable insights to end users.

Space4Climate is a stakeholder-led and funded community, chaired by the UK Space Agency, that promotes the role of space in underpinning climate policy, action and services, enabling and encouraging the use of trusted climate data and the development and take-up of climate services and products. Already involved in climate mission work with Space4Climate members through the SOLSTICE project, we are bringing to the table our end-to-end software expertise for faster, more efficient and seamless data delivery.

“We are honoured to become a part of Space4Climate and collaborate with leading UK space organizations to help advance climate science, monitoring and research,” said Richard Adams, Sales Director at Bright Ascension.

“Joining the network underscores our commitment to connecting the dots between upstream satellite development and downstream space-based solutions on the ground”.

As space systems become more capable, they are also becoming more connected.

Modern missions increasingly bring together spacecraft, payloads, ground systems, communications networks, data processing platforms and operational services from different suppliers and technology domains. Constellations may combine multiple spacecraft generations, different payloads and evolving ground infrastructure. New capabilities may need to be introduced without replacing everything that is already in operation.

This creates a fundamental challenge:

How do you make increasingly diverse systems work together without making the overall system increasingly difficult to manage?

Interoperability is a key part of the answer.

But interoperability is often treated as a relatively simple technical problem: define an interface, agree a protocol and make sure systems can exchange data.

In reality, scalable interoperability requires something more.

Systems need to exchange information and understand what that information means in context.

What is interoperability in space systems?

At its simplest, interoperability is the ability of different systems, components or organisations to work together effectively.

In a space mission, this could mean:

  • A spacecraft communicating with a ground station
  • A payload providing data to a processing system
  • Mission control interacting with multiple spacecraft
  • Different spacecraft sharing operational information
  • Ground systems passing data between different processing environments
  • Multiple suppliers contributing components to the same mission architecture

Interfaces, APIs, protocols and messaging standards all play an important role.

But technical connectivity is only the first layer.

A system can successfully receive a message and still be unable to use it correctly.

That is where the difference between connectivity and interoperability becomes important.

Connectivity is not the same as interoperability

Imagine two systems exchanging a message that says:

“Availability: 10:00–12:00.”

The message has been transmitted successfully. The interface works. The data format is valid.

But what does “availability” mean?

Does it refer to:

  • The spacecraft being available for an imaging task?
  • A ground station pass?
  • A communications link?
  • An operator being available?
  • Processing capacity?
  • A payload being ready to collect data?

If the receiving system interprets the information differently from the system that produced it, the technical connection exists — but effective interoperability does not.

This distinction becomes increasingly important as missions involve more systems and more autonomous decision-making.

The challenge is no longer simply moving information between systems.

It is preserving the meaning, context and intent of that information as it moves between them.

Why does interoperability matter for scalable space systems?

Space systems are becoming more diverse.

Missions are incorporating increasingly capable payloads, more onboard processing, software-defined architectures, cloud technologies and new approaches to sensing and communications.

At the same time, spacecraft and ground infrastructure are rarely designed and replaced as one system.

Different components may come from different suppliers. Systems may have different development cycles. Software may be upgraded independently. New spacecraft may need to operate alongside earlier generations.

This diversity is valuable.

It enables competition, innovation and access to new technologies.

But it also creates more potential points of friction.

Every boundary between systems creates another place where information can be lost, misunderstood or require manual intervention.

As the number of systems increases, those interactions can become one of the biggest constraints on scalability.

The interoperability challenge gets harder as systems grow

A single mission can often accommodate a degree of bespoke integration.

Engineers can understand the systems involved, define the interfaces and build the necessary connections.

But consider what happens when the system expands.

A constellation introduces more spacecraft.

A new payload is added.

A second ground provider is introduced.

A different processing environment is required.

A new customer needs access to the data.

An existing spacecraft is upgraded.

Each change introduces additional interactions.

The challenge isn’t necessarily the individual components.

It is the relationships between them.

This is one reason why systems can scale internally while becoming increasingly difficult to integrate at the boundaries between different systems.

The more diverse the architecture becomes, the more important interoperability becomes.

APIs and standards are important — but they are not enough

Standards, APIs and common protocols are essential building blocks for interoperability.

They provide agreed ways for systems to communicate and reduce the need for every integration to be developed from scratch.

But technical standards alone cannot eliminate every integration challenge.

Two systems can use the same protocol while interpreting the information differently.

Likewise, two systems may exchange perfectly valid data but lack the context required to make an effective decision.

This becomes particularly important in increasingly automated space operations.

If software is expected to coordinate activities across multiple systems, it needs more than access to data.

It needs to understand what that data represents.

Interoperability therefore needs to operate at more than the interface level.

It needs to extend into the information and semantic layers of the system.

Why semantics and context matter

Consider a mission where multiple systems need to coordinate access to a spacecraft.

One system might report that the spacecraft is “available”.

Another might understand availability to mean that the spacecraft is not currently executing a command.

A third might interpret it as being available for a specific payload activity.

All three systems may be technically functioning correctly.

Yet the difference in interpretation can create operational problems.

This is a relatively simple example, but the same principle applies across increasingly complex architectures.

As more decisions become software-driven, systems need to understand not just what information has been received, but what that information means.

That is particularly important when systems need to make decisions automatically.

Interoperability becomes even more important with AI

The growth of AI and machine learning in the space sector makes interoperability more important, not less.

AI can help process large datasets, identify patterns, optimise operations and support decision-making.

But AI systems are only as useful as the information and context available to them.

If information is trapped inside disconnected systems, AI may only have access to part of the operational picture.

That can limit the quality of the decisions it can support.

This creates an important distinction:

AI can make individual systems more intelligent. Interoperability helps make the wider system more connected and context-aware.

The two therefore need to develop together.

As AI moves closer to the edge and more processing takes place onboard spacecraft, the ability to move meaningful information between flight, payload, ground and cloud environments becomes increasingly important.

Interoperability and the rise of systems-of-systems

The space industry is moving towards increasingly distributed architectures.

Instead of treating a spacecraft as a completely isolated system, future missions may involve interconnected networks of spacecraft, payloads, ground infrastructure, communications services, cloud platforms and downstream applications.

These are effectively systems-of-systems.

The value of the overall architecture comes from the interaction between its constituent systems.

That makes interoperability fundamental.

If individual systems cannot exchange and interpret information effectively, the benefits of connecting them are reduced.

This is also why simply adding more capability to individual systems does not necessarily create a more capable overall architecture.

The connections between systems matter just as much as the systems themselves.

Designing for interoperability from the beginning

Interoperability is often treated as an integration activity that happens towards the end of development.

That approach can work for a small number of relatively stable interfaces.

It becomes much harder when systems need to evolve over time.

Designing for interoperability from the beginning means considering:

  • How information will move between systems
  • What that information means
  • Which systems need access to it
  • How context is preserved
  • How interfaces can evolve
  • How new components can be introduced
  • How existing systems can continue operating as the architecture changes

This does not mean standardising everything.

In fact, excessive standardisation can restrict innovation and limit the ability to adopt new technologies.

The objective should instead be to create flexible infrastructure that allows diverse technologies to work together.

Interoperability should enable diversity, not remove it

One of the strengths of the space supply chain is its diversity.

Different companies can specialise in spacecraft, payloads, software, communications, data processing and downstream applications.

New technologies can enter the market without requiring the entire industry to adopt a single architecture.

Trying to solve interoperability by forcing everything into one technology stack risks losing some of those advantages.

A better approach is to provide an infrastructure layer that can accommodate diversity.

That allows organisations to continue developing specialised capabilities while reducing the integration burden between them.

In other words:

The goal of interoperability is not to make every system the same. It is to make different systems work together effectively.

Building scalable space systems

As the space industry grows, the number and diversity of systems involved in missions will continue to increase.

More spacecraft.

More payloads.

More data.

More processing.

More software.

More suppliers.

More applications.

That growth creates enormous opportunities, but it also increases the complexity of the interactions between systems.

Interoperability provides a way to manage that complexity without removing the diversity that drives innovation.

The future of scalable space systems therefore depends not simply on building more capable individual components, but on creating architectures in which those components can work together effectively.

Connectivity moves information. Interoperability gives that information meaning across system boundaries.

And as space systems evolve from individual missions towards increasingly connected systems-of-systems, that distinction will become critical.

Explore the wider challenge

Interoperability is one part of a much larger challenge facing the space industry.

In our whitepaper, Unlocking the $1T Opportunity: Solving Fragmentation in the Space Supply Chain, we explore how fragmentation across the space supply chain affects scalability, efficiency, security and long-term growth — and why software infrastructure could provide a path towards a more connected space ecosystem.

Where HELIX fits

Interoperability is also a fundamental principle behind the HELIX® software ecosystem.

Rather than requiring every mission component to come from a single supplier or forcing organisations into a closed technology stack, HELIX is designed to provide an open, modular infrastructure layer that helps diverse hardware and software components work together.

This allows organisations to adopt the capabilities they need while retaining flexibility as missions evolve.

Discover how HELIX can help build more interoperable and scalable space systems.

We are taking part in this year’s ESA Industry Space Days event on 18-19th September.

Meet us on Stand C12 for a perfect opportunity to learn more about Flightkit Foundation, the early version of our next generation flight software. Flightkit Foundation is designed to make your software development even faster, simpler and cheaper. It’s packed with features that are powerful yet simple to use.


But the best part is – Flightkit is only the beginning. It sets the foundation for the entire HELIX suite that will allow you to join up all space software systems together – from upstream development and operations, right down to delivery of actionable insights and applications for virtually any company on the ground that can benefit from space-based data or services.

Join us at the ISD 2024 to get an interactive demo of the HELIX suite, discover what sort of products are included and how HELIX is going to re-shape the space software industry.

Pre-book a meeting with Andrew, our Commercial Director, to find out more about how we can help you develop your mission faster & cheaper and help it grow and evolve efficiently with our current and upcoming products and solutions. Send us a message on enquiries@brightascension.com to meet the team and learn more.

We are pleased to announce the formalisation of another Memorandum of Understanding (MoU) with ERETS Space, an in-space debris removal service provider. This strategic partnership signifies a significant expansion of our global footprint and underscores our commitment to driving innovation and collaboration across borders. 

ERETS, a pioneering UK startup with an R&D division in Australia, specialises in in-space debris removal services and seeks to leverage Bright Ascension’s innovative space software technology in order to establish a tailored VAR (value-added reseller) partnership in the region. This partnership not only strengthens our presence in the Australian market but also aligns with the vision of fostering international cooperation to address critical challenges in the space industry.

The agreement supports our Software and Integration Partner Programme, a strategic initiative, aimed at supporting the our ongoing HELIX suite expansion and developing collaboration with commercial entities across the global space sector. Targeting both software and hardware technology providers, the Programme offers diverse avenues for generating new business opportunities and driving revenue growth.

“We are excited to start the new journey with ERETS in the Australian market,” said Richard Adams, Sales Director at Bright Ascension. “By merging our expertise, we are expanding our global footprint and driving a positive change within the space industry, helping make spacecraft development substantially cheaper, faster and simpler. This partnership will also offer perspective customers access to additional and fully-integrated mission opportunities such as automating operations or space-based data delivery for actionable insights and intelligence through our upcoming HELIX suite of software products.”

“We are thrilled to announce our partnership with Bright Ascension to leverage their innovative space software,” said Dr Abhiram Nair, CEO of Erets Space. “This collaboration is a significant step forward in our mission towards sustainability in space. The advanced capabilities of Bright Ascension’s software will be helpful in our mission to track and remove space debris, ensuring safer and more efficient space operations. We believe this partnership will be fruitful in numerous ways, paving the path for a more sustainable and responsible approach to space exploration.“

Space missions are rarely identical.

Different spacecraft have different hardware. Payloads have different requirements. Missions operate in different environments, with different constraints, objectives and operational models.

So it is understandable that software development in the space industry has traditionally been highly customised.

When a mission has a specific requirement, engineers build software to meet it.

For an individual mission, this can make perfect sense.

The challenge emerges when bespoke software becomes the default solution for capabilities that are common across many missions.

As spacecraft, constellations and space-based services scale, continually rebuilding the same underlying capabilities can introduce significant cost, complexity and integration challenges.

The question is not whether space software should ever be bespoke. It is where bespoke development creates value — and where reusable infrastructure makes more sense.

Why is so much space software bespoke?

Space is a demanding software environment.

Flight software has to interact with specific hardware. Mission operations need to account for individual spacecraft and payload configurations. Ground systems need to support particular operational workflows. Communications, data handling and processing requirements can vary significantly between missions.

These factors naturally encourage custom development.

There is also a historical reason.

Space missions have often been developed as individual projects rather than as repeatable technology platforms.

Software is therefore designed around the requirements of a specific spacecraft, mission or customer.

That approach can produce highly capable systems.

But it can also mean that software developed for one mission has limited reuse on the next.

The result is a cycle of repeated development.

A new mission starts.

A new set of requirements is defined.

Software is developed or adapted.

Interfaces are created.

Systems are integrated.

The mission launches.

And when the next mission arrives, much of the process begins again.

Customisation is not the problem

It is important to distinguish between mission-specific software and bespoke implementations of common capabilities.

There will always be aspects of a mission that need to be unique.

A spacecraft may have a novel payload.

A mission may require a new operational concept.

A customer may need a specialised application.

These are legitimate reasons to develop new software.

The problem occurs when teams also have to build foundational capabilities from scratch.

For example, common requirements can include:

  • Hardware abstraction
  • Command and telemetry handling
  • Data management
  • Communications interfaces
  • Mission operations
  • Scheduling
  • Monitoring
  • Configuration management
  • Software deployment
  • Ground-to-flight communication

When every mission implements these capabilities independently, engineering effort is repeatedly spent solving similar problems.

That is where bespoke software can become a scalability problem.

The hidden cost of building everything from scratch

The cost of bespoke software is not limited to the initial development project.

Custom software creates a lifecycle commitment.

Once a system is deployed, it needs to be:

  • Tested
  • Maintained
  • Updated
  • Integrated with other systems
  • Secured
  • Documented
  • Supported as hardware and mission requirements change

A capability that initially appears inexpensive can therefore become considerably more expensive over the lifetime of a mission.

This becomes particularly significant when a company moves from one spacecraft to a constellation.

Software development effort that was manageable for a single mission can become a major operational burden when repeated across dozens or hundreds of spacecraft.

The challenge is not simply developing more software.

It is maintaining consistency while allowing the system to evolve.

Why scaling a constellation changes the equation

Scaling a space system introduces repetition.

Instead of one spacecraft, there may be dozens.

Instead of one payload configuration, there may be several.

Instead of one ground system, multiple operational environments may need to work together.

Instead of one software release, teams may need to manage software across an entire fleet.

At this point, software architecture becomes increasingly important.

If every spacecraft or mission is treated as a completely independent software project, scaling can multiply engineering and operational effort.

Reusable software components can change that equation.

Instead of rebuilding foundational capabilities for every mission, organisations can reuse proven infrastructure and focus engineering effort on the capabilities that genuinely differentiate the mission.

Reuse does not mean every mission has to be identical

One common concern about reusable software is that it could restrict flexibility.

Space missions are too diverse for every spacecraft to operate in exactly the same way.

But reuse does not require uniformity.

A modular software architecture can provide common foundations while allowing mission-specific capabilities to sit above them.

Think of it as separating infrastructure from innovation.

The infrastructure provides capabilities that many missions need.

The application layer provides the functionality that makes an individual mission different.

This creates a more sustainable balance between standardisation and flexibility.

The integration problem

Bespoke software can also increase the number of interfaces that need to be managed.

A mission might involve flight software, payload software, mission control, ground infrastructure, communications systems and data processing.

If each component has been developed independently, integrating them can require significant engineering effort.

The problem becomes even more pronounced when components come from different suppliers.

Every integration boundary becomes another place where assumptions need to be aligned.

Interfaces need to be defined.

Data needs to be mapped.

Different behaviours need to be understood.

Testing needs to account for the interactions between systems.

And when one component changes, the potential impact on the others needs to be assessed.

This is one of the ways that fragmentation increases the cost of space system development.

The individual components may work perfectly well.

The complexity emerges between them.

Bespoke software can create technical debt

Repeated custom development can also create technical debt.

Over time, organisations may accumulate multiple generations of software, different frameworks, inconsistent interfaces and mission-specific implementations.

Each individual decision may have been reasonable at the time.

But collectively, these decisions can make the overall architecture harder to evolve.

This can create a situation where engineers spend increasing amounts of time maintaining existing infrastructure rather than developing new capabilities.

For a growing space business, that can become a significant constraint.

Engineering capacity is finite.

Time spent rebuilding infrastructure is time that cannot be spent developing differentiated capabilities.

What should be reusable?

The answer is not to standardise everything.

Instead, organisations should look for capabilities that are:

Common enough to reuse.

Stable enough to provide a foundation.

Important enough that rebuilding them repeatedly creates unnecessary cost.

These capabilities can form an infrastructure layer underneath mission-specific applications.

The exact boundary will differ between missions and organisations.

But the principle remains the same:

Reuse the infrastructure. Innovate where it matters.

This allows engineering teams to spend more of their effort on the parts of the mission that create genuine differentiation.

Reusable software can accelerate time to orbit

One of the biggest advantages of reusable infrastructure is that it can reduce the amount of software that needs to be developed, tested and integrated for every new mission.

This can have a direct impact on development timelines.

Rather than starting from a blank architecture, teams can begin with established capabilities and adapt them to the mission.

That can reduce duplicated engineering effort and make development more predictable.

It can also allow teams to learn from previous missions.

Improvements made to the underlying infrastructure can potentially benefit multiple missions rather than remaining locked inside a single project.

This creates a different development model.

Instead of:

Mission → software → launch → repeat

organisations can move towards:

Infrastructure → mission-specific development → launch → improve → reuse

That shift becomes increasingly valuable as the number of missions grows.

Reuse and interoperability need to work together

Reusable software alone does not solve the wider integration challenge.

Software components still need to work with other systems.

A reusable flight software component that cannot interact effectively with the ground system, payload or operational environment may simply move the integration problem elsewhere.

This is why reuse and interoperability need to be considered together.

Reusable infrastructure provides common capabilities.

Interoperability allows those capabilities to work across system boundaries.

Together, they can reduce the amount of bespoke engineering required to connect different parts of a mission.

This becomes particularly important as missions evolve towards increasingly distributed systems-of-systems.

What about AI and new technologies?

The same principle applies to emerging technologies.

AI, onboard processing, cloud computing and software-defined systems are creating new possibilities across the space industry.

But introducing new technology does not remove the need for a strong software foundation.

In some cases, it can increase it.

More capable systems create more data, more software dependencies and more potential interactions.

AI may require access to information from multiple systems.

Onboard processing may need to coordinate with ground infrastructure.

Cloud environments may need to interact with mission operations.

As capabilities increase, the underlying architecture needs to accommodate that complexity.

The goal should therefore not be to eliminate innovation in favour of standardisation.

It should be to create infrastructure that makes innovation easier to integrate.

From bespoke missions to scalable platforms

The space industry is moving towards a more repeatable model of space system development.

Constellations, commercial missions and growing downstream demand all place greater emphasis on cost, time-to-market and operational scalability.

That makes the traditional project-by-project software model increasingly difficult to sustain.

The answer is not to eliminate mission-specific development.

It is to stop rebuilding the same foundations unnecessarily.

A scalable approach separates the common from the unique.

Common capabilities can be delivered through reusable, modular infrastructure.

Mission-specific software can then build on top of that foundation.

This allows organisations to retain the flexibility that space missions require while reducing the engineering burden associated with repeated development and integration.

Building software that scales with the mission

The next generation of space systems will not be defined only by how capable individual spacecraft become.

They will also be defined by how efficiently those capabilities can be developed, integrated and operated at scale.

Bespoke software will continue to have an important role where missions genuinely require something different.

But the industry does not need to reinvent its software foundations for every spacecraft.

The opportunity is to make the underlying infrastructure reusable, modular and interoperable — so engineers can focus on building what makes each mission different.

That is how software can become an enabler of scale rather than another constraint on it.

Explore the wider challenge

Bespoke software is just one part of the fragmentation challenge facing the space supply chain.

In Unlocking the $1T Opportunity: Solving Fragmentation in the Space Supply Chain, we explore how fragmented technologies, bespoke development and siloed systems affect scalability, interoperability, efficiency and the long-term growth of the space industry.

How HELIX approaches reusable space software

HELIX® is designed around the principle that space organisations should not have to rebuild their software foundations for every mission.

Its modular architecture provides reusable capabilities across flight, ground and mission operations, while allowing organisations to integrate mission-specific functionality where it is needed.

This creates a foundation that can evolve with the mission rather than requiring the entire software architecture to be rebuilt each time requirements change.

Discover the HELIX software ecosystem.

ONBOARD COMPUTERS

AAC Clyde Space Kryten OBC

Raspberry Pi Zero W

Endurosat OBC

Gaisler GR712 (limited)*

GomSpace Nanomind A3200 and Z7000*

ISISPACE iOBC*

NanoAvionics Payload Controller 1.5*

Xiphos Q7 and Q8*

BeagleBone Black OBC*

Skylabs NANOobc*

Many other Linux-based OBCs*

OPERATING SYSTEMS

Linux

FreeRTOS

OFF-THE-SHELF SUBSYSTEMS

AAC Clyde Space EPS and Battery*

Satlab SRS3 S-Band Transceiver*

Cubecom XTX X-Band Transmitter*

Honeywell HMC5883 Digital Compass

Silicon Sensing CRM200 Single-channel gyro

Texas Instruments TLV2548 ADC

Cubespace ADCS

Endurosat S-Band transceiver

PNI RM3100 Geomagnetic sensor*

TI TMP100 & LM70 Temperature Sensor*

Cypress S25FL512S NOR Flash*

Invensense MPU3300 3 axis gyro*

NXP SC161S740/50/60 SPI/12C to UART & GPIO*

Cypress FM33256B FRAM+ RTC*

ISISpace iMTQ magnetorquer*

Safran STIM210 gyro*

COMMUNICATION PROTOCOLS

ECSS Packet Utilisation Standard (PUS)

CCSDS Space Packet Protocol

CubeSat Space Protocol

CCSDS TM Space Data Link Protocol

CCSDS TC Space Data Link Protocol

CCSDS Space Data Link Security, for AES256 encryption and SHA256 authentication

*May require additional updates and testing.

After months of hard work, we’re excited to launch our first product in the HELIX suite: Flightkit Foundation Edition, the early version of our next generation flight software. Flightkit Foundation is designed to make your software development even faster, simpler and cheaper. It’s packed with features that are powerful yet simple to use.


But the best part is – Flightkit is only the beginning. It sets the foundation for the entire HELIX suite that will allow you to join up all space software systems together – from upstream development and operations, right down to delivery of actionable insights and applications for virtually any company on the ground that can benefit from space-based data or services.


We are running a Flightkit demo session at the Small Satellite Conference in Utah on August, 7 – don’t miss your chance the find out all the details and be the first to get your hands on the early version of Flightkit. Register here and visit Booth 227 for details.

_______________________________________

HELIX Flightkit is our brand-new development environment for the fast and simple assembly of spacecraft flight software. With over 50 successful software deployments in orbit and 12 years of industry experience, we understand the critical need for reliable, affordable, and rapidly developed onboard software. HELIX Flightkit takes this expertise to new heights by introducing significantly simplified design processes, enhanced tooling, faster build system and an improved workflow. Crucially, Flightkit is HELIX-ready, ensuring seamless and hassle-free integration with upcoming ground-based HELIX products for testing, spacecraft control, service delivery, and access to space-based insights and analytics.

The newly released version of HELIX Flightkit Foundation is only the beginning of an exciting journey. It includes a starter library of software components and select hardware support, but its functionality and design lay the groundwork for building robust flight software that is future-proof, adaptable, and scalable to evolve alongside mission requirements. Additionally, we developed a schedule of updates and follow-up releases to enhance HELIX Flightkit Foundation functionality and expand the built-in library, support for hardware subsystems and the knowledge base of further tutorials and feature guides.

Furthermore, we are gearing up for further HELIX products launches, including ground-based software products slated for early release in the coming months, along with further HELIX Flightkit editions to support missions with more complex needs.

We are taking part in this year’s Farnborough International Airshow on 22nd-26th July.

Meet us on Space Scotland Stand 4100 in Hall 4 for a perfect opportunity to get a interactive demo of our upcoming HELIX suite, discover what sort of products are included and how HELIX is going to re-shape the space software industry.

Join us on the stand or re-book a meeting with Richard, our Sales Director, to find out more about how we can help you develop your mission faster & cheaper and help it grow and evolve efficiently with our current and upcoming products and solutions.

Send us a message on enquiries@brightascension.com to meet the team and learn more.

We are thrilled to announce that we are taking part in the GEOINT 2024 Symposium from May, 5th to 8th in Kissimmee, Florida.

This is the first time we are attending an event of this scale within the geospatial and Earth observation sector and we plan to showcase our upcoming HELIX suite of satellite software solutions, particularly focussing on midstream and downstream services and activities. Our upcoming HELIX Apps and Infinity products are specifically designed to improve the delivery of space-based insights and analytics to make it significantly faster, simpler and cheaper.

With over 50 software deployments in orbit, we know that the effective delivery of downstream solutions, space-based insights and analytics requires a deep understanding of the upstream processes involved in satellite construction, deployment, and operations. We believe this unique expertise sets us apart and allows us to create solutions that seamlessly integrate with satellite systems, optimise data collection processes, and deliver quick and cost-effective actionable insights to our clients’ customers.

We invite all attendees to visit our Booth 336 at the GEOINT 2024 Symposium for more details and a hand-on demo of our upcoming HELIX family of space software products, that offer a comprehensive solution to address the entire lifecycle of space operations, from design and deployment to data analysis and application delivery.

“GEOINT 2024 is an ideal platform for us to showcase our upcoming HELIX solutions for delivering fast and simple space-based insights and analytics.”

Richard Adams, Sales Director at Bright Ascension

“With our extensive heritage and experience in the space industry, coupled with our unique expertise in the upstream processes, we are excited to engage with geospatial and Earth observation professionals and demonstrate how our innovative technologies can transform their operations, drive efficiency, and unlock new opportunities,” continued Richard Adams.

Richard Adams (left), Sales Director at Bright Ascension, and Brenton Smith (right), Chief Technology Officer at Nominal Systems

We are thrilled to announce the signing of a Memorandum of Understanding with Nominal Systems, a provider of digital twinning simulation systems. The agreement signifies the beginning of a collaborative effort to integrate our respective systems and offerings in order to provide an enhanced end-customer value proposition.

As part of the agreement, both parties commit to effective and efficient collaboration to find ways to leverage the integrated offering and provide greater value to customers than the sum of their parts. On top of this foundation, we will explore further commercial pathways, including value added reseller partnerships across Australia, Europe, and the United States. This strategic alliance will enable both parties to tap into new markets and unlock growth opportunities globally.

The agreement aligns with our Software and Integration Partner Programme, a strategic platform for developing collaboration with commercial entities across the global space sector. Embracing both software and hardware technology providers, the programme offers diverse avenues for generating new business opportunities and driving revenue growth. It is designed to support our anticipated market release of the innovative HELIX suite of software products. HELIX promises to streamline spacecraft software development, operations, service and end-user insights delivery processes, providing faster, simpler and significantly more cost-effective solutions.

“We are thrilled to to sign this strategic partnership with Nominal Systems.”

Richard Adams, Sales Director at Bright Ascension

“This collaboration marks the beginning of an exciting journey towards mutual success, and we are committed to leveraging every opportunity to drive innovation delivered by our HELIX suite and provide added value to customers across the world,” said Richard Adams.

“We are excited to partner with Bright Ascension on this impactful collaboration.”

Brenton Smith, CTO of Nominal Systems

“Through the integration of our sophisticated digital twinning technology, we aim to significantly improve the testing and operational efficiencies of satellite systems. This partnership is not only a stride towards mutual success but also underscores our dedication to delivering state-of-the-art solutions that address the dynamic demands of the global space industry.“

Bright Ascension’s HELIX suite of space software products

We are thrilled to announce the successful closure of a £2.25M investment round through a convertible loan from Scottish Enterprise, Capital for Colleagues (C4C) and other investors in the company.  This is a significant step forward in our journey towards bringing the innovative HELIX products to market. The funds include £1.5M previously secured in October 2023 as a bridging loan from C4C, alongside Bill Ainscough, and TJ Morris Limited, existing shareholders in the company. The bridging loan transitions into a convertible loan as part of the current funding round.

The investment is a true testament to our commitment to re-shaping the New Space software landscape through our ground-breaking technology and development of the next generation HELIX suite of satellite software products. HELIX promises to streamline spacecraft software development, operations, service and end-user insights delivery processes, providing faster, simpler and significantly more cost-effective solutions.

To support the continued advancements in HELIX development, foster strategic guidance and direction, and nurture investor relationships, we recently welcomed John Baughn as the new Executive Chair of the Board. John brings to the team over 40 years of invaluable experience in managing space operations and telecommunications organisations. His expertise encompasses sales strategy, business development, and customer service, making him a valuable addition during this pivotal growth stage. We are pleased that Ken Naismith, our current Executive Chair, will remain on the Board as a Non-Executive Director.

“I am delighted and honoured to be taking on the chairmanship for Bright Ascension at this very exciting point in time and looking forward to helping steer the company towards a very successful future,” said John Baughn, Executive Chair of the Board at Bright Ascension.

The investment marks a pivotal moment, building on our recent commercial successes. We have experienced a boost in new customer acquisition, resulting in a notable increase of 50% in the first half year sales compared to the same period in the previous financial year. This strong performance underscores the effectiveness of our strategic initiatives and our growing prominence in the market to maximise the upcoming HELIX launch.

“This funding injection not only provides us with the necessary financial resources but also serves as a vote of confidence in our technology and commercial strategy.”

Peter Mendham, CEO at Bright Ascension

“With this support, we are well-positioned to accelerate the final stages of development and market release of our innovative HELIX products.”

Alistair Currie, Chief Executive of Capital for Colleagues commented: “We are extremely pleased to see this enhancement of the Bright Ascension team and further endorsement of the company’s technology and commercial strategy. Bright Ascension is now positioned to accelerate the final stages of development and market release of its innovative HELIX products.”

Bright Ascension’s HELIX suite of space software products

We are thrilled to announce the signing of a Memorandum of Understanding with Third Planet Orbital Ltd, a supplier of off-the-shelf functionally standardised small satellite buses. The agreement commits both companies to pool our expertise and resources in order to identify and pursue promising opportunities within the fast-growing New Space industry. Together with Third Planet Orbital, we will form the foundations of a standardised integrated software and hardware platform.

Leveraging our combined skills and capabilities, the partnership aims to improve access to functionally standardised satellites for payload and mission operators. Our modular software directly supports Third Planet Orbital’s approach for establishing a robust, repeatable and resilient supply chain. The use of pre-existing and pre-validated libraries accelerates integration of hardware independently of the customer critical path.

The integration promises to streamline customers’ development activities, delivering cost-effective and off-the-shelf solutions that are mission ready at launch and realise revenues early. Moreover, it enables effortless access to a wider and well-integrated space software infrastructure through our upcoming HELIX suite of products, ranging from managing ground operations to delivering space-based services and transforming them into value-added insights and applications.

The agreement aligns with our Software and Integration Partner Programme, which supports the HELIX software suite expansion and serves as a strategic platform for developing collaboration with commercial entities across the global space sector. Embracing both software and hardware technology providers, the programme offers diverse avenues for generating new business opportunities and driving revenue growth.

“We are thrilled to embark on this transformative journey with Third Planet Orbital.”

Peter Mendham, CEO at Bright Ascension

“By combining our strengths, we aim to offer a substantially cheaper, better and easier access to spacecraft development, which also comes with pre-existing and tightly integrated mission growth opportunities, such as automation of operations or space-based data delivery for further insights and intelligence, provided through our upcoming HELIX suite of software products,” said Peter Mendham.

“The opportunity presented by the space sector is enormous and our job is to make it as easy as possible for payload users to become mission ready.”

Third Planet Orbital CEO Miles Ashcroft

“If we are to Simplify Time to Mission Success, then our satellite buses must be accessible and operate consistently out-of-the-box. It is a vital component of what we do, and how we help our customers is to have competent software on board our buses. Bright Ascension gives us that confidence to go to market knowing our customers can concentrate effort on their payloads and operations,” said Miles Ashcroft, CEO at Third Planet Orbital.

Third Planet Orbital are exhibiting at Space-Comm Expo in Farnborough, UK, on 6-7th March. Visit Stand K37 for more details and a hand-on demo of our upcoming HELIX family of space software products.

We are taking part in this year’s Paris Space Week on 12-13th March 2024.

Send us a meeting request through the event platform to catch up with Richard, our Sales Director, and find out more about how we can help you develop your mission faster & cheaper and help it grow and evolve efficiently with our current and upcoming products and solutions.

With only a few weeks before the launch of our HELIX suite of products, it’s a perfect opportunity to get a interactive demo and find out what HELIX is, what sort of products are included and why it is going to re-shape the space software industry.

To arrange a meeting, either send us a request via the event portal or message enquiries@brightascension.com