Space Traffic and Reports for Orbital Management

Dynamic object behaviour in a defined (spatial) area called Outer Space.

In the given context of Outer Space, traffic is the dynamic of the conjunctions of space objects with each other. And the mirror of the behaviour of space actors.

Space Traffic Reports are the analytics of the conjunctions of the objects in space in different contexts (e.g. age, owner, capabilities, distance, risk etc.) and the reflection of human activities in outer space.

In this context Space Analyses offer different services to manage

Environment
Catalogue
Conjunctions
Measurements

Service Name	Description	Application
Measurement requests Tracking	Based on a selection of space objects and the location, a service for survey and for tracking can be ordered. The delivery (download or dispatch to a platform) is a contact plan (JSON) for measurements.	STROM for SST Measurements
Measurement requests Survey	Based on a selection of space objects and the location, a service for survey and for tracking can be ordered. The delivery (download or dispatch to a platform) is a contact plan (JSON) for measurements.	STROM for SST Measurements
Notifications of overflights	Based on a selection of space objects and the location, a service for overflights can be ordered. The delivery (download or dispatch to a platform) is a contact plan (JSON) for overflights or as a list of notifications/warning/alarms in the application.	STROM for Overflights EO planning SST measurement update notification Security applications
Proximity analytics	Based on a selection of space objects, proximity manoeuvres can be notified. The delivery (download or dispatch to a platform) is a contact plan (JSON) or as a list of notifications/warning/alarms in the application.	STROM for Proximity Security applications SST measurement update notification
Manoeuvre Impact	Based on a selection of objects, a time window and manoeuvre inputs a contact plan (list of upcoming conjunctions per manoeuvre) is delivered as a JSON for further processing and/or the scenario is shown in a VR environment.	STROM for Neighbourhood Awareness
Manoeuvrability classification	Based on a selection of (payload) objects with OMMs or OEMs available for analyses, a classification per object can be provided. The delivery is a list of objects with most probable ability to fly manoeuvres.	STROM for Manoeuvrability Classification
Status modelling	Based on all (actual) available OMMs and/or OEMs the space environment is analysed and space traffic maps in different flavours are produced. The delivery is done in form of a dashboard. Based on individual settings the user could also define thresholds for notifications.	STROM for Space Environment Monitoring
Impact for planning	Based on the Space Environment Status Modelling, the user can insert additional space object(s) and can analyse the traffic impacting the own (new, simulated) objects. The service produces an overlay to the Space Environment Status Modelling showing the impact to the new simulated objects and the impact to the environment.	STROM for Space Environment Mission Planning
CDM analytics	STROM produces CDMs and the user can compare the STROM CDMs with other sources (e.g. celestrack or US DoD) to allow a better risk estimation. The service produces a list of CDM deviations between the CDM sets.	STROM for CDM Analytics
CDM KPIs	The service assigns the CDMs to objects and generates risk making KPIs per object and/or operator. These KPIs can be used for environment or object risk modelling. Note: There is a peripheral analogy to ESA MASTER but with a different set of objects and with different risk modelling approach. The service produces a list of objects with different KPIs that can be correlated to a selection of neighbourhood objects (involved in conjunctions)	STROM for Risk Assessment
Impact analytics	Taking the STROM CDMs the service correlates the CDMs to a selection of space objects to show the impact of certain object groups to the selection. The service produces lists, graphs and can issue notifications if thresholds are defined.	STROM for Impact Analytics
Visibility Intelligence	The service is enabled by selecting a check-box to get enriched observation data. The service checks the visibility of the selected objects out of the selected ground station and generates a Contact Plan. The enriched data are than available for selection. That would mean that e.g. a min V[mag] or distance to Moon can be filtered to create a first optimised contact list for further processing to order measurements.	STROM for SST Measurements
Sensor Planning	The input to the sensor planning process is the enriched Contact Plan that can be filtered for obvious filter criteria such as distance to Moon or Milky Way, or by minimum brightness. The contact plan is then taken as input to the optimisation process. The result is a Contact Plan ready for the measurement orders. This Contact Plan can then be transferred to the measurement sensor operator.	STROM for SST Measurements
Optical Measurement Data Quality	The service uses measurements closely related in time from the same object from different angles and / or ground sensors, processes them for orbit determination and then calculates the measurement error from the respective measurements. This means the measurement is enriched with measurement quality information. The data can be retrieved from the measurement point-of-view or from the ground sensor point-of-view.	STROM for SST Measurements
OMM Calculation / Orbit Determination	Based on a selection of optical measurements the operator can run an orbital determination process. The result is delivered as OMM.	STROM for SST Measurements
Historical Data Provision	To access the historical measurement archive, a two step approach is enabled: (in analogy to Earth Observation data queries): Meta data query – this is a query to the archive about the availability of data concerning the objects of interest Measurement query – based on the meta data request it is possible to access the measurement in the archive and import it into STROM for further analytics.	STROM for SST Measurements
Technical Billing	Technical billing data is generated incrementally as parts of the service order are completed. Each time a segment of the service is delivered, the corresponding billing data is created, enriched, and stored. This ensures that the billing process reflects the real-time progress and completion of the Service Transaction.	STROM Service Operations