The Iridium Next Project · The Iridium NEXT system – Simulations Overall simulation tools have...

1

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.

Template : 83230347-DOC-TAS-EN-005

The Iridium NextProject

2018, December 11th

Olivier DENIZART

2

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.


83230909-D

OC

-TA

S-F

R-0

02

3

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.

Template : 83230347-DOC-TAS-EN-005Ce document ne peut être reproduit, modifié, adapté, publié, traduit d'une quelconque façon en tout ou partie,

ni divulgué à un tiers sans l'accord préalable et écrit de Thales Alenia Space - © 2013, Thales

IRIDIUM – the background

� Iridium : a Satellite-based Personal Communication Services system

� The existing system Iridium Block1 :

• Operated by Iridium Communications Inc. since 1999,

• The only communications network to cover 100% of the earth - including the poles

• Provides worldwide reliable communication from anywhere to anywhere on the

planet

� In particular where landline or mobile phone connections are unavailable, unreliable or overburdened

• Independent of other terrestrial infrastructures

4

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.



Services:

Handheld services

Broadband services

Targeted applications:

Personal communications handheld services that completely bypasses the terrestrial communications system

Asset tracking

Broadband connectivity service: Maritime, Aircraft, Helicopter and Land

IRIDIUM Next – the Mission

5

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.



Feeder link

30/20 G Hz

X - links

23 G H z User links

1.62 G Hz

Teleports (o r Ka

- band term inals

)

�Global fully meshed network relying on Ka-band* inter-satellite links

The Iridium NEXT system constellation & radio coverage

Constellation6 orbital planes with (11+1) satellites /plane

Circular inclined (86°) orbits, 780 km altitude

Orbit period # 100 mn* 20/30 GHz

6

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.


ni divulgué à un tiers sans l'accord préalable et écrit de Thales Alenia Space - © 2013, ThalesRef.:

Multi-spot L-band* coverage

# 400 km spot-beam

Satellite visibility # 10 mn

Satellite hand-off every 5 mn

Spot-beam hand-off every 50 sec.

* 1.6 GHz

The Iridium NEXT system constellation & radio coverage

7

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.



IRIDIUM Next : what are the specific challenges, compared to other satellites projects?

� Applicable constraints:

• The space environment: vibrations during launch, thermal, radiations,….as usual….

• The lifetime: no repair in orbit, 15 years lifetime, …as usual…

• + …minimized cost per satellite, multiple launch by clusters of 10 satellites, short production cycle, complex in-orbit

operations to seamlessly insert the IR Next satellites into the existing, ageing constellation without service interruption

� As per state of the art,

• these constraints are usually dealt with by applying to each satellite Flight Model a stringent test program (Proto-

Flight, then Acceptance level), and implementing Hi-Rel components

� For Iridium Next a specific way forward had to be invented:

• 1. Characterization and qualification of COTS components

• 2. Reinforced IVVQ management involving comprehensive qualification testing and satellite characterization

during the PFM program, and then implementation of a fast rate production cycle

• 3. Intensive implementation of system modelling and simulation campaigns for design validation and preparation

of operations

8

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.


� TAS in charge of the global system design

• The overall system � From Design, IVVQ to in orbit delivery

Encompassing ground segment upgrade designSpecification of the CFEDesign of scheduling algorithms to be implemented in the Iridium existing planning suite

• The constellation and its deployment� The 81 satellites to build

Design – AIT – productionLaunch campaignLEOP & IOTIn orbit insertion in the constellation

� The on board softwareRouting, radio resource management and allocation, call establishment, handoversPayload and bus command and controlSpecification – development

• Support to operationOperational procedure design, development and validation

Support on site during all launches period

The Iridium NEXT system – Architecture & Prime Contractor role

� Iridium in charge of the ground segment development

• Develop, validate or procure, deliver to system IVV and install on site all ground segment elements

Iridium Next Satellite Control centerTeleport new modem (SL & FL)Upgrade of the TeleportUpgrade of the network (TPN)BB terminal

• Billing and services segment

• Operate the constellation Under TAS control until SV insertionWith TAS support all through launchesphases

9

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.


▌ The satellite critical features:

� On board processing• Router

Circuit management

Connexion management

Radio Resource managementand allocation to users

• Optimized WF in Ka band

� Active Antenna

� Very compact design• Thermal constraints

Iridium Next : Main technical Challenges

10

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.



10Antennas accommodated on platform

L band to user

Ka Band to GW

Ka Band to GW

The Iridium NEXT system – the satellite design

11

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.



The Iridium NEXT system – Architecture – ASW/OBP Segment

~1 TFLOP Processing

Capability in each box

12

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.



Overall schedule

12

Baseline Deployment &

Acceptance

2 0 0 7 2 0 0 8 2 0 0 9 2 0 1 0 2 0 1 1 2 0 1 2 2 0 1 3 2 0 1 4 2 0 1 5 2 0 1 6 2 0 1 7

Baseline System Development

Block 1 services

Satellite

Proto-flight

Model

Testing

Low Rate

Production

Full rate Production &

Launches

Baseline On Ground Validation

System Definition and

global offer

System & Deployment of NEXT

services

13

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.



The Iridium NEXT system – Simulations

�Overall simulation tools have been key assets for design to cost and therefore to win the initial competition against US major companies

�Development of complex simulators has been required

• For the initial design and to avoid oversizing in mass and power (critical for a satellite).

• All along the design phase to assess the mission performance

� Taking into account Radio Astronomy bands constraints

• To recover from various Project contingencies, for example when

� Segment/Equipment performance was not in line with the initial specification and to support/ justify segment/equipment NC acceptance

� Segment/Equipment functional behavior was not nominal : e.g. Bk1 Terminals do not behave as defined at the hand-off between beams

14

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.



� System performances & Segment performances are closely interrelated

• e.g. Main Mission Antenna (MMA) performances and system performances :

�MMA Beams shap �� System coverage

�EIRP & G/T �� System Link Budgets

�System Traffic profile (capacity) �� MMA Thermal simulations & Reliability simulations

• e.g. OBP modem perfomance �� System Link budgets

The Iridium NEXT system – Simulations

15

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.



�During Project execution, extensive efforts have been devoted to M&C/FDIR modeling, which has played an essential role in the

System IVVQ strategy

► Positive ROI:

• Implementation of incremental deliveries , as a way to synchronize the different software releases content with AIV needs, allowed for efficient and pragmatic schedule control

• Only a few “design bugs” have been left and were solved during M&C/FDIR tests

► Positive effects have been obtained even before the start of the testing sequence

• Share a common technical referential within engineering teams • Better dialogue between distant teams (geo or specialties) and with the customer• Easier brainstorming around technical design of M&C/FDIR

• Ensure a good level of completeness - Systematic approach• Ensure consistency between components specs & I/F specs

The Iridium NEXT system – Functional Modeling

16

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.



The Iridium NEXT system – System IVV

�Key challenges

• Demonstrate the interoperability of the NEXT System with existing Bk1 System

• Perform the integration and validation of the System M&C

• Perform the integration and validation of the System Services

09/12/2018

16

Perform the validation of the NEXT waveforms

Perform the validation of the NEXT EBBS Services

NIST

Fully Representative Functional System

Not suitable for Radio performance tests

Close to the Experts

Not Fully Representative

ISTB

17

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.


▌ Production of 81 satellites

� 10 SV every 2 months

� Production site in Phoenix Az

• Sub : OATK

• 5000 equipment sent

• “zone franche” created in Phoenix

� Chain production organization

• Island organization

� Bus integration

� PL integration

� Mating

� Functional and performance

� Thermal tests

� System end to end tests

� Storage and packing

Iridium Next : Main Production Challenges

18

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.


▌ SV Launch and deployment per 10

� Acquisistion – power on – stabilizationtransfer from injection to storage planof 10 SV in parallel

� SV very close one to the others

� Challenging Flight Dynamics

� No place for mistake !

▌ SV insertion in the constellation

� “Slot swap” : Collocation of 1 new next SVand 1 BK1 SV to be replaced

� Link “handover”

� BK1 service switch off / Next services switch on

Iridium Next : Launch and in-orbit Operations requirements

View from Falcon 9 launcher – ejection of 9th SV – 5 other SV can be seen

19

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.


▌ BK1 Continuity

Seamless transition between Block 1 and Iridium Next means:

� BK1 in orbit Network continuity

• inter SV XL BK1/Next compatibility

• Routing continuity : Next to support BK1 protocols

� BK1 Services continuity

• Iridium terminals / SV interface continuity : physical layer / protocol /timings

• Iridium GWs / SV interface continuity

• No in orbit service dry run capability – direct insertion in service

▌ But, in addition, Iridium Next allows Iridium services to evolve toward broadband

� Next network is more capacitive

• More capacitive XL between 2 Next SV

• More capacitive FL between Next SV and Teleport

� Next SV/user interface must allow to allocate more resource to a terminal

• Introduction of broadband services

Iridium Next : Operational Challenges

20

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.


Program IVV & Development plan

▌ System Engineering & IVVQ have been a pillar of global system versioning and then of program success.

▌ It is a pillar of the global program IVV strategy

� Implement a lean approach : Start development and test on given features while engineering is still on going

� Organize at each level the development sequencing on a common framework

• Ease the realization of inter segment pre-integration� Induce natural incremental IVV

• the first increment becoming a test assets when the second is tested

• the high priority features are thus under test and use for a long time and are stabilized

System modeling

System Features Features <= Steps

Mapping

=

Prioritization

System Versions

Flow down :

Equipment versions

Flow back in program Schedule

ScheduleKey steps

of the program

21

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.


▌ Prioritization of the system features through identification of both L1st launch time essential features and

other features criticality to allow progressive and representative testing (AIT and system IVV), under the

authority of the IVVQ Manager, who directly reports to the Project Manager

• P0 : the features allowing to safely launch and put in orbit a SV + all on board HW perfo and BK1 compatibility +P0+ : the features allowing to build a transport network in orbit

• P1 : BK1 most critical telecom services for the customer

• P2 : BK1Less critical telecom services

• P3 : BK1 services still under deployment

• P4 : Next broadband

▌ Direct impact on the program

� Prioritization allowed to put in standby P4, P3 engineering and start P0 engineering

� Nota : IVV retroaction on system engineering would have been more difficult if IVVQM had been under the SEM

▌ We feared at first that this approach might worry our customer :

� Are they planning for failure? - Why is our business their last priorities?

� But it was welcomed and Iridium willingly participated to this definition

Program IVV & development plan

22

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.


▌ Early deriskings : all opportunities to implement pre-integration test have been seized

� Not only on critical interfaces but on all possible features

• because even a simple interface becomes blocking when not tuned at the start of the verification test phase

� SV - terminal compatibility

• Very early RF recoding of real Iridium BK1 signals – provided to OBP as test vectors

• OBP / Terminal pre-integration (SKR premises)

� Proto OBP, V0 of the on board SW with very preliminary functionalities and a real terminal

� TAS and US experts together – SW, MW, FW real time tuning

� => first call on an Iridium Next OBP – basic compatibility secured 4 years before 1st launch

� SV – Teleport FL

• Test vector definition -RF signal recording and exchanges => interface clarification

• OBP / TP modem pre-integration

� with SKR and Iridium modem provider

� => early discovery of weaknesses that could be cured with great efforts but in time for L1

� HPL / OBP+ASW : Over the Atlantic test labs interconnection

• Development of a Spacewire / Ethernet bridge

• HPL / PL integration with Iridium/Aireon and TAS team in remote

• => system test phase directly OK –� …

Program IVV – Iridium Next lessons learnt – early derisking

23

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.


▌ IVV Management tools

� On top of a ROADMAP (the strategy)– we built our “GPS system” : the IVV KPIs

� These KPIs allowed to extrapolate the IVV trajectory and not only to track IVV progress

• The KPIs allowed to predict the schedule trend

• Based on the IVV efficiency extrapolation

� Defined test efficiency

� Projected it on future resources availability

� Provided new end date

� Allowed early decision to correct the situation

Program IVV – Iridium Next lessons learnt

24

This

do

cum

en

t ma

y n

ot b

e re

pro

duc

ed

, mo

difi

ed

, ad

ap

ted

, pub

lish

ed

, tra

nsla

ted

, in

an

y w

ay,

in w

ho

le o

r in

p

art

or d

isclo

sed

to

a t

hird

pa

rty

with

out

the

prio

r writ

ten

co

nse

nt o

f Th

ale

s-

© T

ha

les

2017

All

righ

ts re

serv

ed

.


▌ This approach allowed us to be

� More flexible : able to adapt to the issues, constraints

� Quicker : in the decision making

� More efficient : in the realization (no unproductive test phase)

Program IVV – Iridium Next lessons learnt

Drive the PDV

Versioning : common priorities across the program

Quick decision across PMO in time of need

Have a Strategy : a

map

IVV strategy is a global risk analysis and justification of

needed tests

Quick reconfiguration capability

Create Early derisking

RDV

Provide early developers capability to benchmark the design

Build early integration with all the experts

Detect early –secure shedule

1 IVV Team Develop customer visibility and TRUST

Limit acceptance phases – allow more flexibility

Predictive KPI

Derive what we are able to do into where we are going

Early and efficient decision on IVV

The Iridium Next Project · The Iridium NEXT system – Simulations Overall simulation tools have...

Documents

Transcript of The Iridium Next Project · The Iridium NEXT system – Simulations Overall simulation tools have...