Europe's Spaceport selected Iterative Engineering to improve the payload preparation process

Krzysztof Gąsior from Iterative Engineering
Krzysztof Gąsior CEO @ Iterative Engineering

An Exciting time for us! We have been selected to work on the Proof of Concept system for Launch Campaign Information and Request Management at Guiana Space Center (CSG) operated by French Space Agency (CNES).

Project Motivation

Currently, there is no tool for creating, tracking or tracing a service request during the launch campaign period. Requests are made verbally, by email or by message, making it challenging to follow-up and track.

To improve the experience of launch operators, payload customers and the spaceport staff during future launch campaigns, CSG plans to introduce a digital platform providing a service catalogue and facilitating processing and tracking of raised requests.

Project Scope

While the PoC is supposed to showcase the feasibility of digitizing the process, it has concretely outlined functions and requirements. The outcome shall be operational and is intended to become a backbone for further developments, covering core concepts such as:

  • Exposing the CSG services catalogue to simplify raising payload processing requests
  • Increasing request traceability for both the customer and the staff
  • Improving stakeholder’s experience by integrating the request lifecycle within a single tool
  • Streamlining campaign management by providing supporting workflows for typical activities

Sequence for processing customer request

Winning Bid

According to feedback, the following features of our proposal convinced the CSG team to select our offer from almost a dozen competitors:

  • comprehensive approach - we have conducted domain and requirement analysis, based on which we proposed a technical solution along with a clear execution plan,
  • attention to detail - we have put a lot of effort into domain discussions and questions through the bid preparation process,
  • alignment with outlined goals - our offer had elements directly addressing all mentioned goals and motivations.

Before we started working on the bid, we had discussed how to approach it, as while we were actively exploring the space industry for some time already, it was really the first (!) tender we were taking part in. The conclusion was that first and foremost we need to prove (to them and ourselves) that we have a deep understanding of WHY they want to do it, WHAT they actually need and HOW can we deliver it.

Broader Picture

To achieve that, we started by analysing the payload preparation process, its surroundings and how it fits into the bigger picture. This very quickly led us to learn more about the launch campaign structure, different stakeholders and phases of that process. The exploration involved reading Launch Operator User Manuals, NASA and ESA publications and various other materials on the subject of launch planning, conducting and post operations. Obviously, we were focusing on the payload preparation process, but the research involved getting an understanding of the other aspects as well.

Launch site at CSG

For instance, it is important to understand the launch campaign structure at CSG which consists of:

  • The launcher campaign - initially focused on rocket assembly and launchpad preparations, followed by payload integration and finally assembly.
  • The spaceport preparation campaign - focused on ensuring ground facilities (such as radars, telemetry systems, etc.) at the Spaceport are 100% able to support the flight.
  • The spacecraft (payload) preparation campaign - focused on ensuring that the payload is 100% prepared for the launch and that it is fully functional. Covering aspects such as:
    • placing the satellite in a clean zone,
    • filling the satellite with propellant using specific equipment,
    • installation of satellite check-out consoles and ground mechanical equipment,
    • integration of separately shipped elements,
    • fitting the payload adaptor.

All of the above are performed independently by different teams, but are carefully synchronised to ensure that all the components are ready in time for the final integration and launch date.

Another example of an important aspect impacting the process is the variety of the payload setups. Different options have different implications on the spacecraft stakeholder teams impacting communication requirements. Specific configurations also require specific services and adequate operations during the preparation process.

Broader Picture - various payload setups Broader Picture - various payload setups

During this process, we have identified many more relevant aspects which were extremely helpful for further requirements analysis and outlining the proposed solution sketch.

Submission Outline

Once we felt confident with our research we moved to preparing an outline of the proposal. The really good idea was to actually ask the CSG Team for confirmation on their expectations of proposal contents as we have quickly confirmed that the structure we proposed was relevant (as the tender did not define it). We ended up with the following scope:

  • WHY US - with general info about our company
  • COMMERCIAL - with an executive summary of the offer focused on scope and commercials such as quotes, commitments and promised outputs.
  • TECHNICAL SUBMISSION - covering:
    • Broad Outlook - research on the broader picture of the process, different stakeholders and analogies
    • Requirements Analysis - review supplied requirements and discuss how to approach them
    • Offer Scope Definition - define and describe offered deliverables being a core and possible options extending it
    • Sketch of a Solution - showcase & example of proposed solution based on outlined requirements
    • Execution Plan - describe the plan for project execution
  • ATTACHMENTS - evidence of experience and skills, case studies, certificates etc.

Having a clear and confirmed outline with a subsequent structure helped us greatly, as we used it as a plan for preparing the full contents of the bid.

Requirements Analysis

So the next thing to do was requirement analysis (both functional and non-functional) to ensure we are capable of addressing all of the required and potentially some of the optional tasks. This involved discussing things like:

  • potential impact on the process,
  • review & reflection on expected functionality and how to provide it,
  • identifying use cases & workflows,
  • mapping of requirements to components & modules,
  • discussing ergonomic requirements and how to approach them.

This led to conclusions on key requirements:

  • process information is captured and available,
  • oversight & insights are available at a glance,
  • means of automation are available and configurable.

It also allowed us to group functional requirements around different perspectives, which then served as a starting point for drawing the sketch of a solution.

Requirement Analysis - functions grouped by different perspectives Requirement Analysis - functions grouped by different perspectives

Sketch of a Solution

Once the analysis was ready and we felt like we knew WHY and WHAT we moved into the HOW section drawing out potential solution describing:

  • conceptual & system architecture,
  • data model
  • integration with CSG systems,
  • PoC perspective vs Long term perspective,
  • used technologies

but most importantly we also drew a number of mockups & workflow which visually show what could be the outcome addressing specified needs.

Solution Sketch - sample dashboard design Solution Sketch - sample dashboard design

Execution Plan

Finally, we contextualized the solution in a detailed execution plan defining timelines, actions and outputs of various steps we have identified as required (or useful) to deliver the final outcome:

  • Commencement
  • Workshop & Scope Alignment
  • Design Process
  • Development Process
  • Training & Documentation Process
  • Deployment & Verification Process

Execution Plan - planned project timeline Execution Plan - planned project timeline

Additionally, we also discussed Team Structure and its changes over time through the following phases explaining their responsibilities.

Progress sneak peek

So as we announce the good news the project is actually already ongoing and for the last few weeks we have been refining the initially proposed design & architecture.

Design & Analysis - sneak peek on design improvements P1 Design & Analysis - sneak peek on design improvements

Together with CSG Team we have gone through a number of detailed domain discussions about various aspects of the process and the specific environment characteristics in order to confirm scope and functional expectations, touching on subjects like:

  • Current approach to request management
  • Spaceport and Spacecraft Stakeholders’ structures and its impact on the process
  • Workflows needed to support various types of requests
  • Details of Service Catalogue offering

Stay tuned for further updates! :)

Project implementation has already started Project implementation has already started

By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.