1. Issue/Revision:. Reference: Status: Issued ESA UNCLASSIFIED - For Official Use ESTRACK KPI for Network Service accounting & Performance measurement Martin UNAL 11/11/2014

2. Martin UNAL | ESOC | 11/11/2014 | Slide 2 ESA UNCLASSIFIED - For Official Use KPI FOR NETWORK SERVICE ACCOUNTING

3. Martin UNAL | ESOC | 11/11/2014 | Slide 3 ESA UNCLASSIFIED - For Official Use KPI for Network Service accounting Policy –The income is realized through a charging mechanism called: ESA/HSO Charging Policy –The charge is traded in the currency “Units of Service” UoS are not identical with neither tracking nor support times –This section of the presentation describes how the UoS are derived

4. Martin UNAL | ESOC | 11/11/2014 | Slide 4 ESA UNCLASSIFIED - For Official Use ESA Network Service accounting Policy 1.“UoS is the tracking time, adjusted by taking into account the pre- and post pass activities” Application #1 –UoS are derived from the tracking duration, i.e. BOT/EOT times. In order to compensate for pre- and post pass activities, the following rules are applied: –Each support with a tracking duration of one hour or less is calculated as one hour utilization. –Example: A tracking support of 15 minutes is considered as one hour utilization –For each support with a duration of more than one hour, one additional hour is added to the figure –Example: A tracking support of 1hour 15 minutes is considered as 2hours and 15 minutes utilization

5. Martin UNAL | ESOC | 11/11/2014 | Slide 5 ESA UNCLASSIFIED - For Official Use ESA Network Service accounting Policy 1.“UoS is the tracking time, adjusted by taking into account the pre- and post pass activities” Application #2 (continued) –The individual UoS of each individual support are summed up to give the total service duration and rounded to the next integer hour per reporting period, giving the UoS for the period. –As some supports may not include tracking activities, such supports’ UoS are calculated based on their actual support duration (EOA-BOA)

6. Martin UNAL | ESOC | 11/11/2014 | Slide 6 ESA UNCLASSIFIED - For Official Use ESA Network Service accounting Policy 2.“Ground station passes requested by a customer will be charged for. These could be operational passes or test passes.” 3.“Partially successful passes with interruptions or gaps are charged like fully successful ones” 4.“When, for reasons not determined by mission support requirements (e.g. antenna maintenance), a mission is assigned an antenna bigger than normally required or an external service needs to be procured, the mission will be charged for its nominal antenna.” 5.“If for ESTRACK internal reasons, (e.g. unplanned antenna downtime due to failure) missions are forced use an external, non-core station the mission is charged the rate of a comparable internal ESTRACK core station”

7. Martin UNAL | ESOC | 11/11/2014 | Slide 7 ESA UNCLASSIFIED - For Official Use ESA Network Service accounting Policy 6.“If for reasons outside ESTRACK a mission wants to use an external station, e.g. to have extended coverage during critical operations, the full cost of this external support is charged to the mission” 7.“If missions cancel scheduled passes less than 3 days (4 weeks for deep space terminals) before the planned execution, such passes will be charged for.” 8.“If missions schedule a station but do not use it, the unused time is charged”

8. Martin UNAL | ESOC | 11/11/2014 | Slide 8 ESA UNCLASSIFIED - For Official Use TT&C SERVICE PROVIDERS PASS REPORTING TOWARDS ESA

9. Martin UNAL | ESOC | 11/11/2014 | Slide 9 ESA UNCLASSIFIED - For Official Use XML-based Pass Report format #1 The pass report format to be exchanged between Service Providers and ESA is XML. The XML schema is defined in a XSDDefinition and depicted in below XCD scheme representation: ELEMENTD ESCRIPTION R EQUIRED D ATA T YPE ReferenceIdentifier Reference identifier of the schedule as provided by ESA in the schedule request. Different for each pass. Optional xs:string PassReportIdentifier Customer internal reference for each pass report Optional xs:string Spacecraft Spacecraft which was supported Mandatory: See applicable support ICD between the Agency and the Service Provider xs:string, enumerated

10. Martin UNAL | ESOC | 11/11/2014 | Slide 10 ESA UNCLASSIFIED - For Official Use XML-based Pass Report format #2 ELEMENTD ESCRIPTION R EQUIRED D ATA T YPE GroundStation Ground Station (site) from which support was provided Mandatory: See applicable support ICD between the Agency and the Service Provider xs:string, enumerated Terminal Terminal (antenna) from which support was provided Mandatory: See applicable support ICD between the Agency and the Service Provider xs:string, enumerated StartSupport Date and time (UTC) of the effective start of the activity Mandatory: yyyy-mm-ddThh:mm:ssZ Actual start support time xs:dateTime StartTrack Date and time (UTC) of the effective start track of the pass Mandatory: yyyy-mm-ddThh:mm:ssZ Actual start track time xs:dateTime StartUplink Date and time (UTC) of the effective start of uplink Optional: yyyy-mm-ddThh:mm:ssZ Actual start uplink time xs:dateTime

11. Martin UNAL | ESOC | 11/11/2014 | Slide 11 ESA UNCLASSIFIED - For Official Use XML-based Pass Report format #3 ELEMENTD ESCRIPTION R EQUIRED D ATA T YPE EndUplink Date and time (UTC) of the effective end of uplink Optional: yyyy-mm-ddThh:mm:ssZ Actual end uplink time xs:dateTime EndTrack Date and time (UTC) of the effective end track of the pass Mandatory: yyyy-mm-ddThh:mm:ssZ Actual end track time xs:dateTime EndSupport Date and time (UTC) of the effective end of the activity Mandatory: yyyy-mm-ddThh:mm:ssZ Actual end support time xs:dateTime Remarks Additional Information as free text as required Optional: True or False xs:string PassSuccessful Pass Success criteria to be applied are defined in the respective contract between the agency and the service provider Optional: True or False xs:boolean

12. Martin UNAL | ESOC | 11/11/2014 | Slide 12 ESA UNCLASSIFIED - For Official Use XML-based Pass Report format #4 ELEMENTD ESCRIPTION R EQUIRED D ATA T YPE PassCharged Whether the pass may be charged to the agency is defined in the respective contract between the agency and the service provider Mandatory: yyyy-mm-ddThh:mm:ssZ Time of file generation xs:boolean ReportTime File creation time Optional xs:dateTime OrbitNumber Orbit numberOptional xs:unsigned Long NumberOfFrames Received Number of frames received Optional xs:unsigned Long NumberOfFrames Lost Number of frames lost Optional xs:unsigned Long NumberOfCommands Received Number of commands received Optional xs:unsigned Long NumberOfCommands Radiated Number of frames radiated xs:unsigned Long

13. Martin UNAL | ESOC | 11/11/2014 | Slide 13 ESA UNCLASSIFIED - For Official Use XSD Visual Representation >

14. Martin UNAL | ESOC | 11/11/2014 | Slide 14 ESA UNCLASSIFIED - For Official Use KPI FOR ESTRACK PERFORMANCE MEASUREMENT

15. Martin UNAL | ESOC | 11/11/2014 | Slide 15 ESA UNCLASSIFIED - For Official Use Scope of Reporting The scope is limited to the ESTRACK service boundary, i.e.: from the entry point of the Mission Control System to the Spacecraft including communications and Operations Control Centre installations

16. Martin UNAL | ESOC | 11/11/2014 | Slide 16 ESA UNCLASSIFIED - For Official Use Definitions - Services and Service Outages Operations Services Service Outage Interruptions or failures in providing committed main operations services (i.e. TLM, TLC and RNG) Quantified by the number of outages and the cumulated length of the outages The impact of an outage on the customer is NOT a criterion! Telemetry service (TLM) Telecommand service (TLC) Radiometric Data services (RNG) Radio Science Experiment service (RSI) Delta-Differential One Way Ranging (DDOR) Special Operations (SPE)

17. Martin UNAL | ESOC | 11/11/2014 | Slide 17 ESA UNCLASSIFIED - For Official Use Definitions - Service Outage Failure Categories #1 Service Outage are grouped by location of the root-cause in Failure Categories. The following Failure Categories are defined for Ground Station related service outages: F AILURE C ATEGORY E XPLANATION G/S - Back-Ende.g. CORTEX, TMTCS, IFMS, Ranging System, ESU G/S - Front-Ende.g. Mechanical, Electric, FEC, LNA, U/L Amp., BUS Converters G/S - LAN Comms & Voicee.g. Local Switches, Routers G/S - Other / Unknowni.e. any other equipment or unknown failure located @ G/S G/S - Personnel / Processese.g. Local Operations, Config. Control, Test and Validation G/S - Powere.g. Onsite, Commercial G/S - Local M&Ce.g. STC, CSMC, M&C

18. Martin UNAL | ESOC | 11/11/2014 | Slide 18 ESA UNCLASSIFIED - For Official Use Definitions - Service Outage Failure Categories #2 The following Failure Categories are defined for Operations Control Centre related service outages: F AILURE C ATEGORY E XPLANATION OCC - Data Link Controle.g. NCTRS OCC - Engineering Supporte.g. Validation, Tailoring, Config. Control, Release Mgmt. OCC - File Transfere.g. FIDES, GFTS, OVNCTRS, JNCTRS, LFTM OCC - LAN Comms & Voicee.g. Voice-Loop, Switches, Routers, Connected Hosts, Firewall OCC - Other / Unknowni.e. any other equipment or unknown failure located @ OCC OCC - Personnel / Processesi.e. Remote Operations (ECC, OM Team) OCC - Remote M&Ce.g. STC-OWS, CSMC-Remote Node OCC - Schedulinge.g. EPS, ESS, MOIS, EOCR, Scheduling Office OCC - WAN Commse.g. Switches, Routers, Leased Lines, MPLS, ISDN

19. Martin UNAL | ESOC | 11/11/2014 | Slide 19 ESA UNCLASSIFIED - For Official Use Definitions - Service Outage Failure Categories #3 The following miscellaneous Failure Categories are defined : F AILURE C ATEGORY E XPLANATION Externale.g. External Supplier, RFI, Weather Conditions, Occultation Flight Dynamicse.g. Ephemeris Data, FD Transfer System Mission/Customere.g. S/C, MCS, MPS, NIS, FCT Security P1/2/3/4i.e. Priority 1 Security Incident

20. Martin UNAL | ESOC | 11/11/2014 | Slide 20 ESA UNCLASSIFIED - For Official Use Service Performance

21. Martin UNAL | ESOC | 11/11/2014 | Slide 21 ESA UNCLASSIFIED - For Official Use Service Performance - Technical Outage vs. Service Outage The following example illustrates the difference: MissionX is scheduled from 10:00z to 20:00z at Kourou (i.e. committed service volume) A technical defect at the stations interrupts the support at 11:00. MissionX is provided with a replacement support from another Ground Station as of 11:30z to 20:00z The problem is cleared and Kourou is back to nominal at 18:00z. The technical outage at Kourou lasts from 11:00z to 18:00z:  7 hours technical outage The service outage to MissionX lasts from 11:00 to 11:30z:  0.5 hours service outage.