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

Issue/Revision: .

Reference:

Status: Issued

ESA UNCLASSIFIED - For Official Use

ESTRACK KPI for Network Service accounting & Performance measurement

Martin UNAL

11/11/2014

Martin UNAL | ESOC | 11/11/2014 | Slide 2


KPI FOR NETWORK SERVICE ACCOUNTING



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



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




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)




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”




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”



TT&C SERVICE PROVIDERS PASS REPORTING TOWARDS ESA



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:

ELEMENT DESCRIPTION REQUIRED DATA TYPE

ReferenceIdentifier

Reference identifier of the schedule as provided by ESA in the schedule request. Different for each pass.

Optional

xs:string

PassReportIdentifierCustomer internal reference for each pass report

Optionalxs:string

Spacecraft

Spacecraft which wassupported

Mandatory:See applicable support ICD between the Agency and the Service Provider

xs:string, enumerated





GroundStation

Ground Station (site) from which support was provided



Terminal

Terminal (antenna) from which support was provided



StartSupportDate and time (UTC) of the effective start of the activity

Mandatory:yyyy-mm-ddThh:mm:ssZ Actual start support time

xs:dateTime

StartTrackDate and time (UTC) of the effective start track of the pass

Mandatory:yyyy-mm-ddThh:mm:ssZ Actual start track time

xs:dateTime

StartUplinkDate and time (UTC) of the effective start of uplink

Optional:yyyy-mm-ddThh:mm:ssZ Actual start uplink time

xs:dateTime





EndUplinkDate and time (UTC) of the effective end of uplink

Optional:yyyy-mm-ddThh:mm:ssZ Actual end uplink time

xs:dateTime

EndTrackDate and time (UTC) of the effective end track of the pass

Mandatory:yyyy-mm-ddThh:mm:ssZ Actual end track time

xs:dateTime

EndSupportDate and time (UTC) of the effective end of the activity

Mandatory:yyyy-mm-ddThh:mm:ssZ Actual end support time

xs:dateTime

RemarksAdditional 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





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 number Optional xs:unsignedLong

NumberOfFramesReceived

Number of frames received

Optional xs:unsignedLong

NumberOfFramesLost

Number of frames lost


NumberOfCommandsReceived

Number of commands received


NumberOfCommandsRadiated

Number of frames radiated

xs:unsignedLong



XSD Visual Representation

<<XML Schema View>>

<<Uplink>>

<<Track>>

<<Support>>

<<ReportDetails>>



KPI FOR ESTRACK PERFORMANCE MEASUREMENT



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



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)



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:

FAILURE CATEGORY EXPLANATION

G/S - Back-End e.g. CORTEX, TMTCS, IFMS, Ranging System, ESU

G/S - Front-End e.g. Mechanical, Electric, FEC, LNA, U/L Amp., BUS Converters

G/S - LAN Comms & Voice e.g. Local Switches, Routers

G/S - Other / Unknown i.e. any other equipment or unknown failure located @ G/S

G/S - Personnel / Processes e.g. Local Operations, Config. Control, Test and Validation

G/S - Power e.g. Onsite, Commercial

G/S - Local M&C e.g. STC, CSMC, M&C




The following Failure Categories are defined for Operations Control Centre related service outages:


OCC - Data Link Control e.g. NCTRS

OCC - Engineering Support e.g. Validation, Tailoring, Config. Control, Release Mgmt.

OCC - File Transfer e.g. FIDES, GFTS, OVNCTRS, JNCTRS, LFTM

OCC - LAN Comms & Voice e.g. Voice-Loop, Switches, Routers, Connected Hosts, Firewall

OCC - Other / Unknown i.e. any other equipment or unknown failure located @ OCC

OCC - Personnel / Processes i.e. Remote Operations (ECC, OM Team)

OCC - Remote M&C e.g. STC-OWS, CSMC-Remote Node

OCC - Scheduling e.g. EPS, ESS, MOIS, EOCR, Scheduling Office

OCC - WAN Comms e.g. Switches, Routers, Leased Lines, MPLS, ISDN




The following miscellaneous Failure Categories are defined :


External e.g. External Supplier, RFI, Weather Conditions, Occultation

Flight Dynamics e.g. Ephemeris Data, FD Transfer System

Mission/Customer e.g. S/C, MCS, MPS, NIS, FCT

Security P1/2/3/4 i.e. Priority 1 Security Incident



Service Performance

Successful Service Delivery refers to the amount of service, where the three main operations services (TLM, TLC and RNG) were provided without service outages.

“Service Performance” refers to the ratio of “Service Outage” versus the total Service Volume

• Variants may show only the operations services provided from a specific resource, provided to a specific customer or focus on a single operations service.



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.

Documents

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