1) The document discusses engineering the Galileo satellite navigation system to provide services. It explains that Galileo will be a large, complex service system requiring systems engineering from both a technical and service provision perspective. 2) It provides an overview of the Galileo program, including its objectives to provide positioning, navigation and timing services. The system architecture and timeline for deploying the full constellation and providing early services by 2014 is also summarized. 3) Managing Galileo involves taking an integrated approach considering both the system development and ongoing service provision processes. Service management draws upon standards like ITIL to focus on delivering value to users through committed services.

1. Engineering the Galileo
Services Exploitation Phase
Dr. ing. Marco LISI
European Space Agency
Special Advisor of the European Commission
International Workshop on "GNSS technologies
advances in a multiconstellation framework“
SOGEI, Roma, 23rd April 2013
Navigation solutions powered by Europe

2. Objectives




To explain what a service oriented, large and
complex system means;
To present the Galileo present status and the
preparation to its Early Services phase;
To describe the engineering activities needed
for the provision of Galileo services;
To suggest that beyond the obvious
technological and technical challenges, a
service provision perspective opens new and
interesting fields to systems engineering.

3. What is a service system?


Service (or service-oriented) systems are
systems meant to provide value-added
services through the use of technology (mainly
communications and computer technologies);
A “service system” has been defined as a
dynamic configuration of people, technology,
organizational networks and shared information
(such as languages, processes, metrics,
prices, policies, and laws) designed to deliver
services that satisfy the needs, wants, or
aspirations of customers.

4. Characteristics of Service Systems
 Large and complex systems
 Software intensive (several million lines of code)
 Capabilities-based rather than platform-based
 Organization and governance (human factor)
 Technical performance is a prerequisite for

production and delivery of services, not a final
objective
Requirements related to operations, in addition to
technical ones, assume a very high relevance:
Quality of Service (QoS)
Reliability, Availability, Continuity
Maintainability
Safety
Security
4
Flexibility
Expandability
Interoperability
Resilience

5. Products vs. Services
 Cars
 Highways
 Trains
 Railways
 Stations
 Parking areas
 Aircrafts
 Airports
 Ships
 Etc.
5

6. Large and Complex Systems (1/2)
A large and complex system is a system composed
of a large number of interconnected elements, often
developed and deployed worldwide, which interact
dynamically, giving rise to emergent properties
Examples of complex systems for civil applications
include:
 global satellite navigation systems
 air traffic control systems
 railway control systems
 space systems such as the International Space Station or space




transportation and exploration vehicles
surveillance, Earth observation and Homeland security systems
electric power distribution systems
telecommunication systems
complex computer networks, including Internet.
6

7. Large and Complex Systems (2/2)
A complex system often integrates existing
systems (or parts of them) in an overall largescale architecture containing a large number of
interfaces and implementing multiple modes of
operation, in a highly dynamic environment
Large and complex systems require extensive
logistics and maintenance support capabilities
Large and complex space-based systems (e.g.
Galileo) are conceived to be in service for a long
time; in this case the evolution of the system (upgradings and modifications) has to be taken into
account from the beginning.
7

8. Project/System Multiple Perspectives
8

9. Specifying a Service System
 Functional and technical performance:
•
System Requirements Document (SRD)
 Operational requirements and scenarios:
•
Concept of Operations (CONOPS) document
 Expected service behavior and non-functional
performance:
•
Service Level Agreement (SLA)
 A typical SLA defines Key Performance
Indicators (KPI’s) and Key Quality Indicators
(KQI’s), with target values and target ranges to
be achieved over a certain time period.
9

10. Concept of Operations (CONOPS)
10

11. Galileo Program essentials
Galileo is Europe's initiative for a state-of-the-art
global navigation satellite system, providing a
highly accurate, guaranteed global positioning
service under civilian control
While providing autonomous navigation and
positioning services, Galileo will at the same
time be interoperable with GPS and GLONASS,
the two other global satellite navigation systems
The fully deployed Galileo system will consist of
30 satellites and the associated ground
infrastructure.
11

12. The Galileo System

13. GALILEO: a Large and Complex ICT System
...
Direct C-band Up-links
for Integrity
Constellation - 30 MEO Satellites
Total: 5 S-band heads
Total: at least 31 C-band heads
13 m antenna
Mission C-band Up-link
(Nav/Integ/SAR/NRS/PRS)
TT&C S-band Up-link
5 combined Galileo Up-links Sites
(global coverage)
Mission C-band Up-link
(Nav/Integ/SAR/NRS/PRS)
+ 4 dedicated Mission Up-links
Sites
SDDN
MDDN/ ULS Network
ERIS
ERIS - External Regional Integrity Systems
GCS - Galileo Control System
GMS - Galileo Mission System
GSS - Galileo Sensor Stations
Ground Control and Mission Segments Facilities
MDDN - Mission Data Dissemination Network
NRS - Navigation Related Service
to
external
Service
Providers
and other
entities
Galileo Control Centre 2 (GCC2)
(geographical redundant)
PRS - Public Regulated Service
SAR - Search And Rescue
SDDN - Satallite Data Dissemination Network
TT&C - Telemetry, Tracking and Telecommand
Galileo Control Centre 1 (GCC1)
ULS - Up-Link Station
MDDN/ GSS Network
Elements of GCS and GMS
Elements of GMS
~ 40 GSS
13
Elements of GCS

14. The Galileo “System of Systems”
14

15. The Galileo Timeline

16. Galileo Implementation Plan

17. Galileo System Architecture

18. Galileo Service Centers in Europe

19. Galileo Stations for Early Services

20. Galileo Services

21. Galileo Services Provision Timeline

22. The Galileo Service Center

23. Prerequisites for Providing Early Services
Early Services impose significant constraints on all
key Galileo actors, in order to:
 Ensure early and continuous operation of
Galileo system
 Ensure early and continuous operation of the
GSMC for handling security events
 Ensure early provision of user interfaces, e.g.
to service centres
 Ensure proper definition and implementation
of service validation activities
 Ensure proper and timely definition of liability
regimes

24. Galileo Open Service (OS)
Characteristics
Free of charge positioning, navigation and timing
information
Galileo Open Service is fully interoperable with GPS
Users
Mass-market applications (i.e. smartphones, in-car
navigation)
Additional applications such as timing, surveying,
farming, fleet management, passenger information
systems …
Next steps
Provide early Galileo Open Service from 2014
Autonomous and continuous service available when
the full constellation is deployed
Open Service (OS)
Freely accessible service for
positioning and timing

25. Galileo OS – Early Service in 2014
Because of the reduced constellation deployed by 2014, the
OS early service will not provide a standalone service
Signals will be available for users and will provide benefits
when combined with GPS or other constellations, by
providing
 good ranging accuracy
 online monitoring of OS SIS and timely isolation/flagging
of any OS SIS which are not reaching minimum
performance levels
EC/ESA/GSA currently defining the performance
commitment for early services
Number of signals available and positioning accuracy will
increase with the deployment of additional satellites
Full autonomous PVT performance will be declared at FOC

26. Galileo OS – Phased introduction
Phased approach tied to infrastructure deployment
The early service milestone in 2014 will be
linked to a minimum deployed infrastructure
configuration to be defined as part of the
service requirements derivation and gap
analysis.
The autonomous service milestone in 2016
is planned with a more complete constellation
and with fully deployed ground infrastructure.
This will allow declaration of an autonomous
early service, with performance parameters
that will improve with further satellite
deployments, up to FOC.

27. Ground infrastructure for early OS
Galileo user helpdesk facility will be available already in
October 2012.
 operated under the supervision of the GSA
Galileo Service Centre (GSC) is being set up in Madrid
 provides interfaces to all users of Galileo OS (as well as CS)
 support to receiver manufacturers
 support to service providers
Main system operations (GMS / GCC) are ensured until
2016
 preparations for operations after 2016 are proceeding
Galileo Reference Centre (GRC) - Independent
performance monitoring centre is being established

28. Current Galileo Governance

29. Galileo Integrated Approach
The provision of Galileo services will be a process
well distinct from the Galileo system development &
acquisition process;
A Service Management specific process, including
methodology, best practices and organization, is
required;
However, system (acquisition) and service
(provision) have to proceed together, in a
coordinated and well harmonized manner;
An integrated approach is required, with a systems
engineering perspective covering both system and
service related aspects.

30. Galileo Development & Acquisition Process
Assets
(Satellite Constellation, GCC’s,
GCS, GMS, GDDN, etc.)
Galileo System
Requirements
Galileo
System
Galileo System
Performance &
Operations
People
Processes
(ESA Project Team,
Subco’s, EC, GSA, etc.)
(Engineering Board, VCB,
CCB, CM, Ops
Procedures, etc.)

31. Galileo Service Provision Process
Assets
(Galileo System, GSC, GPEC, etc.)
Galileo
Services
Requirements
Galileo
Services
Galileo
Services
Provision
People
Processes
(EC, GSA, ESA Support,
Member States, Services
Providers, Operators, etc.)
(Services Validation, KPIs
Monitoring, Security
Monitoring, Helpdesk, etc.)

32. What do we mean by "service"?
By the term “service” we mean the guaranteed
and committed delivery of a capability to a
community of potential customers/users;
In the delivery of a service, the focus is more on
the “commitment” (continued over time) than on
the “technical performance” (provided that the
service delivered is useful and responds to a
minimum set of guaranteed technical
requirements).
32

33. Service Management
Service Management is a set of specialized organizational
capabilities for providing value to users/customers in the form
of services;
These organizational capabilities include all the processes,
methods, functions, roles and activities that Service Providers
uses to enable them to deliver services to their customers;
The inputs to Service Management are the resources and
capabilities that represent the assets of the Service Provider.
The outputs are the services that provide value to users;
The focus of Service Management is on the service delivery
process which is different from a system development and
acquisition process (focussed on technology and technical
performance);
From the Service Management viewpoint technologies and
technical performance are means, not final objectives.

34. What is ITIL?
ITIL (Information Technology Infrastructure Library)
is a public framework (and a “de facto” standard)
that describes Best Practices in IT Service
Management;
Although originally conceived and developed for ITbased services, the ITIL methodology and practices
are applicable to the management of a generic
service provision process;
The Galileo service provision organization will have
as its main and essential asset what can be seen as
a large and complex ICT system (network based,
computational intensive, software intensive);
ITIL could therefore be a good reference for the
Galileo Service Management definition.

35. Service Lifecycle (ITIL Standard)

36. The ITIL Process Model

37. Conclusions
 After a development, initial procurement and

In-Orbit Validation phase, Galileo is proceeding
with the procurement and in-orbit deployment
of the full constellation and will start providing
Early Services by the end of 2014;
Large and complex service systems, such as
Galileo, need a very collaborative integration of
systems engineering, operations engineering
and service management, with special
attention to operational, governance and
Integrated Logistic Support aspects.

38. Traditional
Chinese
Thai
Gracias
Thank
You
Russian
Arabic
Spanish
Obrigado
Brazilian
Portuguese
English
Danke
Grazie
Korean
Italian
Simplified
Chinese
Japanese
Merci
German
French