estec - European Space Agency

Prepared by Roland Trautner Reference ESA-HRE-PROSPECT-IRD-0001 Issue I1 Revision 0 Date of Issue 26/03/2018 Status Issued Document Type IRD

Distribution

ESA UNCLASSIFIED - For Official Use

estec European Space Research

and Technology Centre Keplerlaan 1

2201 AZ Noordwijk The Netherlands

T +31 (0)71 565 6565 F +31 (0)71 565 6040

www.esa.int

PROSPECT Science Operations Center Interface Requirements Document

Page 3/40 PROSPECT SOC-IRD Date 26/03/2018 Issue I1. Rev 0


Reason for change Issue Revision Date

Issue 1 Revision 0 Reason for change Date Pages Paragraph(s) Initial issue 26/03/2018 all All



Table of contents:

1 DEFINITIONS ................................................................................................................................. 5 2 REFERENCE DOCUMENTS ............................................................................................................. 6 2.1 Normative Documents ....................................................................................................................................................... 6 2.2 Informative Documents ..................................................................................................................................................... 7 3 INTRODUCTION ............................................................................................................................. 8 3.1 Purpose and Scope .............................................................................................................................................................8 3.2 Structure of the Document ................................................................................................................................................ 9 3.3 Mission Phases ................................................................................................................................................................. 10 3.4 SOC Activity Phases .......................................................................................................................................................... 11 3.5 SOC Architecture and Interfaces ..................................................................................................................................... 12 3.6 SOC Data Flows ................................................................................................................................................................ 14 3.6.1 PROSPECT Data Flow for Operations and related Support ........................................................................................ 14 3.6.2 PROSPECT Data Flow for Archiving ............................................................................................................................ 16 3.6.3 PROSPECT Data Flows – Types and Timing ............................................................................................................... 17 3.6.4 PROSPECT elements in L-27 SOC ................................................................................................................................ 19 4 PROSPECT OPERATIONS SUPPORT REQUIREMENTS ................................................................. 20 4.1 On-Site Operations Support Requirements ................................................................................................................... 20 4.2 Remote Operations Support Requirements .................................................................................................................... 21 4.3 PROSPECT Knowledge Management Requirements ..................................................................................................... 21 5 PROSPECT ON-SITE SCIENCE OPERATIONS CENTER REQUIREMENTS ..................................... 22 5.1 PROSPECT Telemetry and Telecommand Databases .................................................................................................... 22 5.2 General PROSPECT SOC Hardware / Software Requirements ..................................................................................... 23 5.3 PROSPECT Quicklook Data Processing Software Requirements .................................................................................. 24 5.4 PROSPECT Operations Planning Software Requirements ............................................................................................ 25 5.5 PROSPECT Data Product Requirements ........................................................................................................................ 27 6 PROSPECT REMOTE SCIENCE OPERATIONS CENTER REQUIREMENTS ..................................... 28 6.1 Remote PROSPECT SOC Hardware Requirements ...................................................................................................... 28 6.2 Remote PROSPECT SOC Software Requirements ........................................................................................................ 28 6.3 Remote PROSPECT SOC Communication Requirements ............................................................................................ 28 6.4 Ground Reference Model Requirements ........................................................................................................................ 29 7 VERIFICATION AND VALIDATION REQUIREMENTS ................................................................... 30 8 PROSPECT SOC DELIVERABLES AND RELATED REQUIREMENTS ............................................... 31 8.1 Export Requirements ....................................................................................................................................................... 31 8.2 SOC Deliverables .............................................................................................................................................................. 31 9 REQUIREMENTS ON RUSSIAN PARTNERS .................................................................................. 33 9.1 SOC Infrastructure, Software and Databases ................................................................................................................. 33 9.2 Reporting, Provision of Information / Data ................................................................................................................... 34 9.3 Operations Planning ........................................................................................................................................................ 35 10 APPENDIX A: MINIMUM CONTENTS FOR PROSPECT USER MANUAL ........................................ 36 11 APPENDIX B: MINIMUM CONTENTS FOR SOC SOFTWARE USER MANUALS .............................. 39 12 ACRONYMS .................................................................................................................................. 40

Page 5/40 PROSPECT SOC-IRD Date 26/03/2018 Issue 1 Rev 0


1 DEFINITIONS

The following paragraphs provide definitions that support the correct understanding of the specified requirements. PROSPECT Project The PROSPECT Project comprises ESA and ESA’s contractors, and persons / entities that have a formal relation with ESA within the framework of PROSPECT. PROSPECT User Group (PUG) The PROSPECT User Group/Science Team constitutes the body of scientists and experts from a range of disciplines who are selected to represent the scientific community in its operation of PROSPECT to achieve the projects’ science objectives. PUG also includes the teams and entities that provide the data pipelines for creating the PROSPECT data archive products. Quicklook Data For the purpose of this document, quick look data shall be defined as all telemetry data that is potentially needed for analysis of system/instrument health, assessment of the correct execution of command sequences and successful execution of foreseen measurements. Specifically, Quicklook data production includes generation of files and adequate visual representation for

• Time series of any and all TM parameters • Time axis in instrument acquisition sequence / SCET / UTC (in case auxiliary data for time

conversion is available) • Uncalibrated science data products (images, spectra, time series, etc.) • Calibrated engineering data (display in SI units) • Limited processing of data as needed for analysis and assessment

“Adequate representation” shall mean display of image data as an image, spectral data as a spectrum, time series as a 2D graph with axis description, etc.



2 REFERENCE DOCUMENTS

2.1 Normative Documents Normative References (NR) are fully applicable in their entirety to this document and are listed below as dated or undated references. These normative references may be cited at appropriate places in the text. For the explicit, dated or versioned, references, subsequent amendments to, or revisions of, any of those references do not apply to this document. The version of any other references to be used is given in the list of documents constituting the contractual baseline. [NR1] IKI workstation hardware description, to be provided in PROSPECT Phase C. [NR2] ALT Linux - http://www.altlinux.com/ [NR3] deleted [NR4] Telemetry and Telecommand Database Format Definition; to be provided in

PROSPECT Phase C. [NR5] Software, ECSS-E-ST-40 C, latest version.

[NR6] Software product assurance, ECSS-Q-ST-80C Rev.1, latest version. [NR7] Joint Implementation Plan for the ESA Contributions to the LUNA-RESURS-

1 Lander (Luna-27) Mission, MON-JIP-LR-1(L)-00000, latest Issue. [NR8] PROSPECT Data Product Requirements, HRE-PROSPECT-IRD-0002, 03

2018. [NR9] PROPSPECT Hardware, Software and Data Deliverables Lists, ESA-HRE-

LUNA-DL-0002, latest Issue. [NR10] Ground systems and Operations, ECSS-E-ST-70, latest version, tailored to

project needs.

http://www.altlinux.com/



2.2 Informative Documents Informative References (IR) are applicable to this document only when specifically called up in the text with references to specific parts of the document that are to be applicable. Otherwise the documents below are listed for information and as an aid for understanding. For the explicit, dated or versioned, references, subsequent amendments to, or revisions of, any of those references do not apply to this document. Other Informative References are listed for information and as an aid for understanding. [IR1] PROSPECT User Group/Science Team Terms of Reference, to be provided in

Q3 2018. [IR2] PROSPECT Deliverable Items and Services List, PROSPECT Phase C/D/E

RFQ package, 03 2018. [IR3] PROSPECT Bilateral Interface Control Document (B-ICD), ESA-HRE-

PROSPECT-IF-0002, latest version. [IR4] PROSPECT System Requirements Document, ESA-LEX-PRO-SRD-0001, RE-

PROSPECT-IF-0002, latest version.



3 INTRODUCTION

3.1 Purpose and Scope The PROSPECT package, which is part of the Russian Luna-27 spacecraft payload, will drill into the subsurface in the lunar polar regions where the regolith is expected to contain water ice and other cold trapped volatiles in unknown quantities. The PROSPECT operations will be planned, commanded, and monitored in the Luna-27 science operations center located at IKI, Moscow. External sites will support these processes in particular during later (routine) operations phases The purpose of this document is to identify the relevant requirements to the PROSPECT project that need to be complied with for the conduct of related mission operations. The document defines all requirements related to the major deliverable items needed at the Luna-27 Science Operations Centre at IKI for the preparation and execution of the Luna-27 payload operations. It also presents the operations requirements for PROSPECT that need to be met in order to be ready for supporting operations at launch. The ability to meet these requirements at launch shall be demonstrated at each of the reviews planned during the PROSPECT design and implementation phases. In addition, this document also specifies requirements to Russian partners (IKI, being responsible for the L-27 science operations planning) in chapter 9. Additional PROSPECT related requirements to Russian partners are defined in [NR7], [NR9] and [IR3]. The signature of Russian partners of this document confirms that the requirements to European industry stated in this document are correct and are covering the Luna-27 SOC needs for PROSPECT, and that the requirements in chapter 9 are accepted. It is understood by the signatories that the requirements and descriptions provided in this document represent IKI best knowledge at the time of signature and may be subject to change, as IKI will have to further refine and agree requirements, specifications and contract terms and conditions with NPOL. Such changes will be captured in future document versions.



3.2 Structure of the Document This document is structured as follows:

• Chapter 3 provides an overview on various aspects of the PROSPECT science

operations center • Chapter 4 provides the general operations support requirements • Chapter 5 provides the requirements for the PROSPECT contributions to the

Moscow/IKI based L-27 science operations center (“on-site” elements) • Chapter 6 provides the requirements for the remote PROSPECT operations center

that is expected to support operations planning activities during the later phases of the L-27 mission

• Chapter 7 provides verification and validation requirements for the SOC elements • Chapter 8 addresses deliverables and related export requirements for the SOC • Chapter 9 addresses requirements towards Russian partners • The remaining chapters provide additional specific information and generic

information such as acronyms



3.3 Mission Phases The Mission Phases of the Luna-27 mission are defined as follows (simplified for the purposes of this PROSPECT SOC-IRD):

Mission phases and events printed in bold indicate the phases where PROSPECT is expected to be operated.

Phase Starting event Ending event Main intermediate events Pre-Launch LV on launch pad

Removal of LV umbilical from launch pad

Launch Removal of LV umbilical from launch pad

Completion of engine burn / arrival in 180km TBC parking orbit

LV lift-off, and Fregat burn

Parking Orbit Completion of engine burn / arrival in 180km TBC parking orbit

Engine burn for entering Transfer Orbit

Transfer Orbit Completion of engine burn / arrival in 200 x 3500 km TBC transfer orbit

Engine burn for entering Lunar Transfer Trajectory

Early Cruise Phase Engine burn for entering Lunar Transfer Trajectory

Start of spacecraft check-out

Trajectory correction 1

Spacecraft Check-out

Start of spacecraft check-out

End of spacecraft check-out

Checkout of S/C system, limited payload checks (TBC)

Continuation of Cruise

Completion of Spacecraft Composite checkout

Start of intensive orbit determination activities for targeting DM deployment

Trajectory correction 2

Lunar Approach Start of intensive orbit determination activities for targeting DM deployment

Engine burn completion / arrival in 100km parking orbit

Several TCMs TBC

Lunar orbit Phase Arrival in 100km parking orbit

Start of de-orbit burn

Several orbit correction manoeuvres TBC

L-27 Descent and Landing

Start of de-orbit burn

Landing completed (confirmation via C-band)

Detailed DL sequence.

Landing Platform Commissioning

Landing completed End of Landing Platform Commissioning

Lander systems and payload commissioning

Lander Science Operational Phase

End of Landing Platform Commissioning

End of Landing Platform operational life on Lunar surface

Payload operations



3.4 SOC Activity Phases The sequence of SOC activity phases are defined as follows:

SOC activity phase Start / end Science operations center development and validation phase

Start of C/D1 contract to completion of validation

Pre-landing operations rehearsal phase

Between completion of validation and spacecraft launch

Checkout phase From launch to checkout completion

Initial PROSPECT science operations phase

From landing until end of activities related to 3rd Lunar day operations; includes commissioning plus daily wake-up and survival preparation operations; includes 3 science operations periods that each include

• science operations preparation period • science operations period • science operations analysis period

Extended PROSPECT science operations phase

From end of initial science operations phase to end of S/C science operations; includes daily wake-up and survival preparation operations; includes TBD science operations periods that each include

• science operations preparation period • science operations period • science operations analysis period



3.5 SOC Architecture and Interfaces The following figures illustrate the interfaces and envisaged integration of PROSPECT SOC elements (on-site = in Russia; off-site = in Europe) and operations team with the overall L-27 SOC and operations team. One element, the secure link between remote PROSPECT Science Operations center and IKI, may be part of the SPECTRUM package.

Fig. 1: High level overview of L-27 ground segment architecture, role of SOC ICD, and role of PROSPECT science operations center

This document provides the requirements towards the PROSPECT science operations center elements. Compliance to these requirements will be documented and agreed via the SOC-ICD, which will be signed by both ESA and Russian partners / IKI. The following figure illustrates the concept for the envisaged integration of the PROSPECT science operations team with the L-27 science operations team



Fig. 2: Overview of expected L-27 science operations team structure and integration of PROSPECT operations team with L-27 science operations team



3.6 SOC Data Flows During the PROSPECT operations phase, but also before (SOC and data pipeline development and validation phase) and after (archiving phase) different types of data will have to be generated, transmitted, processed, and stored / archived. The following chapters provide a conceptual overview on these data flows.

3.6.1 PROSPECT Data Flow for Operations and related Support PROSPECT operations are expected to be supported from 2 possible locations: either from a PROSPECT SOC that is co-located as part of the overall Luna-27 SOC at IKI (on-site), or (in later mission phases) from a remote SOC that provides identical functionality but is connected via a secure link to the overall Luna-27 SOC (expected to be a SPECTRUM CFI to PROSPECT). The following figures show the basic operations architectures for these 2 cases. At any one time only one PROSPECT SOC is active. These are functional representations (not fully corresponding to an actual physical implementation and the actually implemented types of services and protocols etc.).

Fig. 3a: Overview of expected data flows for supporting PROSPECT science operations with active co-located PROSPECT SOC



Fig. 3b: Overview of expected data flows for supporting PROSPECT science operations with active remote PROSPECT SOC

During operations, 2 different categories for data flows are identified:

• Data flows that are subject to real time requirements (used within the TM assessment / operations planning loop during the operations phases)

• Data flows that have more relaxed timing requirements (background data assessment / processing, archive product generation, PR data, long term planning related data etc.; interaction with PUG)

Functions and data flows that are subject to real-time requirements (that need to be performed in support of operations planning and –execution within a defined and limited time) are expected to reside within the L-27 and PROSPECT SOCs (red and blue boxes in Fig. 3a and 3b), or use dedicated secure communication links of adequate bandwidth and availability / reliability. Other data flows, including science and engineering support for mid-term or long-term planning, PR, and other non-time-critical data traffic are expected to use secure links via internet (VPN, secure FTP, or similar).



3.6.2 PROSPECT Data Flow for Archiving

Fig. 4: Overview of expected data flows for PROSPECT data archiving; note in this example the PROSPECT operations are located at the off-site PROSPECT-SOC.

Data required for archiving includes all raw PROSPECT TM data, calibration information, auxiliary data from the L-27 spacecraft, and other relevant information. Raw (uncalibrated) telemetry data will be delivered directly to the PSA for archiving (typically once a dataset corresponding to a period of operations, like a Lunar day, is complete). At appropriate times / intervals, data is provided to the leads / operators of data pipelines (expected to be part of PUG). After a TBD data processing / proprietary period, calibrated archive quality data (several data levels, including calibrated data and higher level data products) is delivered to the Planetary Science Archive (PSA).



3.6.3 PROSPECT Data Flows – Types and Timing The following table provides an overview on the key data flows, including some information on expected timing. Data flows that are subject to real-time requirements are represented in bold.

Data type Generated by Sent from Sent to when Remarks

PROSPECT TM data

+ Luna-27 spacecraft

auxiliary data

IKI L-27 Sci

Ops Team

IKI L-27 Sci

Ops Center /

DDS

Active

PROSPECT

Ops center

On availability Needs to include time conversion data,

S/C temperatures, S/C attitude /

orientation, other TBC

Validated command

sequences and

Quicklook data /

PROSPECT status

information

PROSPECT

Ops team

Active

PROSPECT

Ops center

IKI L-27 Sci

Ops Center

Compliant with IKI Sci Ops

Center Req.

Part of operations planning loop

(iterative development)

PROSPECT quick look

data + available S/C

auxiliary data

PROSPECT Ops

team

Active

PROSPECT Ops

center

PUG operations

support team

(external)

As needed / background mirror

process via SFTP (TBC)

PUG operations support team assesses /

evaluates data, provides feedback and inputs

to Ops team via email / telecons

Final transmitted

command sequences

PROSPECT Ops

team

Active

PROSPECT Ops

center

PUG data

processing

sections

After completion of monthly

operations period

Simple / quick processing expected (short

archive product generation time)

Raw PROSPECT TM

data + preliminary set of

S/C auxiliary data

PROSPECT Ops

team

Active

PROSPECT Ops

center

ESAC archive

component


operations period

To be archived in a simplified form, mainly

for the purpose of safe long-term storage

Raw PROSPECT TM

data + preliminary set of

S/C auxiliary data

PROSPECT Ops

team

Active

PROSPECT Ops

center

PUG data

processing

sections


operations period

PUG data processing sections then generates

archive products for ESAC

Updated sets of S/C

auxiliary data

PROSPECT Ops

team

Active

PROSPECT Ops

center

PUG data

processing

sections

After availability of updated

auxiliary data

Expected at several times during the mission,

not synchronized with operations periods

Calibrated PROSPECT

science data and

engineering data

PUG data

processing

section leads

PUG data

processing

section

ESAC archive

component

After TBC proprietary period;

before publication of derived

results; after reception of

updated auxiliary data

Several PUG sections expected (engineering

data, MS, imaging, PP/density, volatile

modelling, other). Proprietary period for a

dataset starts at end of operations period

(TBC)

Higher level calibrated

PROSPECT data

PUG data

processing

section leads,

science

community

PUG data

processing

sections,

PROSPECT data

archive users

ESAC archive

component

Source data from privileged

access: TBC proprietary period

Source data from archive: no

deadline / restrictions

Some products based on privileged access

requested from PUG (3D image products,

mineralogy maps, volatile abundance data,

video, etc.)



Table 1: Overview of expected data types and rough timing for PROSPECT operations and data archiving



3.6.4 PROSPECT elements in L-27 SOC The following figure illustrates the PROSPECT elements that will be provided by ESA/the PROSPECT consortium and integrated in the Luna-27 Science Operations Center.

Fig. 5: PROSPECT elements (light blue) integrated in Luna-27 SOC The PROSPECT elements that need to be integrated in the Luna-27 SOC include

• PROSPECT operations team members • PROSPECT software elements for data processing, storage/access, operations

planning, data analysis • PROSPECT representative hardware for supporting operations planning • PROSPECT kinematic models for supporting operations planning • PROSPECT operations resource calculation module

The corresponding requirements are provided in the following chapters.



4 PROSPECT OPERATIONS SUPPORT REQUIREMENTS

The following requirements define the needed provision of services for PROSPECT operations. SOC-1000 The PROSPECT science operations center development and validation phase shall be part of

PROSPECT phase C/D. SOC-1003 The initial PROSPECT pre-landing operations rehearsal phase shall comprise 3 days (TBC) between L-

27 mission launch and landing. SOC-1005 The initial PROSPECT science operations phase shall comprise 3 terrestrial months. This phase

includes any in-flight tests & checkout, and commissioning activities after landing. SOC-1010 The extended PROSPECT science operations phase shall comprise 9 (TBC) terrestrial months following

the initial PROSPECT science operations phase. SOC-1020 The PROSPECT science operations periods shall comprise 10 (TBC) successive Earth days per Lunar

day. SOC-1030 The PROSPECT science operations preparation periods shall comprise 2 successive Earth days

preceding the science operations periods. SOC-1040 The PROSPECT science operations analysis periods shall comprise 2 subsequent Earth days following

the science operations periods. SOC-1050 The PROSPECT project shall provide 24/7 operations support during PROSPECT science operations

periods. SOC-1060 The PROSPECT project shall provide support during normal working hours for the preparation and

analysis periods (TBC). SOC-1070 Operations support shall include PROSPECT health checks, quick look data analysis, operations

planning, planning optimization, command sequence compilation / simulation / optimization / verification and validation / dispatching, contributions to operations related discussions, engineering support including support to debugging, FDIR and FDIS, and other tasks as assigned by the ESA-appointed responsible operations manager(s).

4.1 On-Site Operations Support Requirements The following requirements define the required provision of services for PROSPECT operations at the IKI science operations center in Moscow. SOC-2000 PROSPECT on-site operations support shall be provided at the assigned science operations center

premises at IKI, Moscow (TBC). SOC-2010 PROSPECT on-site operations support shall include

• On-site presence and support at SOC premises during the operations center test and validation (system verification tests) by ProSEED and ProSPA personnel as required by ESA



• On-site presence and support at SOC premises during the initial science operations phase by 2 subsystem specific persons at any time (1 person for ProSEED subsystem, 1 person for ProSPA subsystem)

• Work shifts with overlap of 2 hours (TBC) for briefing / handover from the person on duty to the successor (N persons covering 24h per subsystem)

SOC-2020 During on-site operations, work shall take into account inputs from off-site (remote) contributors

including authorized personnel from LDO, OU, and PUG.

4.2 Remote Operations Support Requirements The following requirements define the required provision of services for PROSPECT operations to the IKI science operations center in Moscow from a remote location in an ESA member state). SOC-3000 PROSPECT shall establish an operations center capability in an ESA member state(s) for providing

remote operations support. The location shall be selected based on a trade-off that includes short-term availability of required operational, scientific and technical expertise, suitable infrastructure (including accommodation, communications, data processing), suitable facilities (including those for operation and maintenance of GRM elements and other relevant hardware), laboratory facilities as needed, cost (for setup, operation, and decommissioning), and locally available expertise with operation of payloads and management of related aspects.

SOC-3100 PROSPECT remote operations support shall be provided during the extended science operations phase. SOC-3110 The PROSPECT remote operations support shall be provided at the selected remote SOC premises. SOC-3120 PROSPECT remote operations support shall include

• Presence and operations support as required during remote operations center test and validation (system verification tests) by ProSEED and ProSPA personnel as required by ESA

• Presence and operations support during the in-orbit checkout phase by ProSEED and ProSPA personnel as required by ESA

• Presence and operations support during the extended science operations phase by ProSEED and ProSPA personnel as required by ESA

• Shift work and overlaps for briefing / handover from the person on duty to the successor as required by ESA

4.3 PROSPECT Knowledge Management Requirements The following requirements define the required management of knowledge within the PROSPECT project for the purposes of science operations. SOC-3500 The PROSPECT project shall ensure the continued availability of operational experience in PROSPECT

operations from previous project phases (laboratory testing, field testing, qualification) for supporting the science operations phase.

Comment: This must include appropriate documentation (documents, test reports / experimenter’s handbooks, images, video) from relevant test activities on representative hardware. It should also include participation of experienced personnel in the operations planning and as part of the operations team.



5 PROSPECT ON-SITE SCIENCE OPERATIONS CENTER REQUIREMENTS

The following requirements define required products, deliverables, and functions for PROSPECT operations.

5.1 PROSPECT Telemetry and Telecommand Databases SOC-4000 PROSPECT shall provide a telecommand database in TBD format [NR4] as well as documentation

comprising all PROSPECT telecommands, which contains TBD information including • Data packet formats • Data fields and parameters and their digital number formats • Allowed parameter ranges

Comment: The IKI science operations center will provide the environment for verification and validation of PROSPECT commands with respect to compatibility with the spacecraft and its status. PROSPECT is expected to perform a pre-validation. SOC-4010 PROSPECT shall provide a telemetry database in TBD format [NR4] as well as documentation

comprising all PROSPECT telemetry, which contains TBD information necessary for health monitoring including

• Data packet formats • Parameters and their digital number formats • Allowed parameter ranges • Calibration curves • Information on applied compression method / standard (if any) • Required actions and procedures when parameters are out of the allowed range (FDIR / FDIS

actions and procedures) Comment: The IKI science operations center will provide functions for basic health monitoring of the L-27 payloads (detailed health monitoring of PROSPECT is a responsibility of the PROSPECT team). This will be performed by IKI systems (hardware / software). PROSPECT needs to provide all relevant data on PROSPECT telemetry parameters. SOC-4020 The PROSPECT TM/TC databases shall be delivered in multiple issues in line with the SOC

development schedule provided by ESA based on the IKI SOC requirements.



5.2 General PROSPECT SOC Hardware / Software Requirements SOC-5000 PROSPECT Quicklook, Operations Planning, and Data Generation Software shall be designed to run on

two PROSPECT SOC workstations [NR1]. Comment: IKI will provide 2 workstations at the L-27 science operations center which are dedicated for running software provided by PROSPECT for supporting operations. SOC-5010 The PROSPECT SOC workstations should be utilized as follows:

• 1 WS for PROSPECT operations planning and ProSEED data analysis / diagnostics / Quicklook data generation, processing, and storage

• 1 WS for ProSPA data analysis / diagnostics / Quicklook data generation, processing, and storage

SOC-5020 The PROSPECT consortium shall define the number and resolution of required screens for the IKI-

provided workstations. SOC-5030 PROSPECT SOC software shall be executable on workstations running a Linux operating system [NR2]. SOC-5040 For the development, maintenance, as well as for PA & QA of PROSPECT SOC software, the ECSS

software and other engineering standards shall apply [NR5, NR6, NRX]. SOC-5050 PROSPECT SOC software shall be developed in line with a classification of individual software modules

according to their criticality. SOC-5060 PROSPECT SOC software shall use standards and formats for data interchange, databases, procedures

and protocols that are established for ESA ground segment systems unless other standards and formats are imposed by IKI requirements. In case established standards and formats would lead to unjustifiable complexity, cost or development effort, an effective alternative shall be proposed.



5.3 PROSPECT Quicklook Data Processing Software Requirements

The IKI L-27 science operations center will provide workstations for hosting PROSPECT Quicklook data processing software in order to support effective operations planning. SOC-6000 PROSPECT shall provide executable (no source code) Quicklook data processing, visualization and

analysis software to support L-27 science operations. SOC-6010 Quicklook data processing, visualization and analysis shall support the confirmation that previously

planned and executed operations have been completed successfully. The time from data availability on the server to Quicklook data display shall be less than 10 seconds (TBC) for all data types.

SOC-6020 Quicklook data processing, visualization and analysis software shall be executable on PROSPECT SOC

hardware [NR1] and OS software [NR2]. SOC-6030 Quicklook data processing, visualization and analysis software shall support interfacing to IKI provided

telemetry data servers. SOC-6040 Quicklook data processing, visualization and analysis software shall support exporting Quicklook data

products (printing, selected data in human / machine readable files). SOC-6050 Quicklook data visualization shall support the display of all types of telemetry data including parameter

time series, images and image parts, video, uncalibrated science data (unless calibration is required for assessment of operations success), calibrated housekeeping data, system state (state diagram)

SOC-6060 Quicklook data processing, visualization and analysis software shall support conversion from on-board

time to UTC and applicable time zones (CET, Moscow time) SOC-6070 Quicklook data processing, visualization and analysis software shall support data selection based on

time, data type, and sequence SOC-6080 Quicklook data processing, visualization and analysis software shall be capable of performing its

functions in the presence data gaps (missing packets) and time data discontinuities. SOC-6090 Quicklook data processing, visualization and analysis software shall be capable of confirming the

completeness of executed operations versus planned / commanded operations SOC-6100 Quicklook data products for PR purposes shall be provided on ESA request SOC-6110 A Quicklook software user manual shall be provided in line with appendix B. SOC-6120 The Quicklook data processing software shall support live monitoring of operations (display of most

recent data) as well as assessment of static datasets.



5.4 PROSPECT Operations Planning Software Requirements The IKI L-27 science operations center will provide workstations for hosting PROSPECT operations planning software for the purpose of operations planning, sequence compilation, sequence modelling and verification / validation, and dispatching sequences to the L-27 SOC infrastructure. SOC-7000 PROSPECT Operations Planning Software shall provide the functions necessary to develop operations

sequences based on PROSPECT (incl. ProSPA and ProSEED) commands. SOC-7010 PROSPECT Operations Planning Software shall provide the functions necessary to verify and validate

compiled operations sequences on PROSPECT (incl. ProSPA and ProSEED) level . SOC-7020 PROSPECT Operations Planning Software shall provide the functions necessary to manage resources

(non-volatile memory, consumables, other) on PROSPECT (incl. ProSPA and ProSEED) level. SOC-7030 PROSPECT Operations Planning Software shall provide the functions necessary to model and visualize

the resource consumption (time, power, energy, data volume, other consumables) of compiled operations sequences.

SOC-7040 PROSPECT Operations Planning Software shall support the definition of start and end markers for

parts of operations sequences that must not be changed with respect to relative timing at L-27 payload operations planning level.

Comment: for the modification of command timing supporting optimization of operations on L-27 payload level, certain parts of operations must not me modified in order to save power, preserve volatiles, or save other resources. It needs to be possible to mark such operations. SOC-7050 PROSPECT Operations Planning Software shall support the dispatching of validated operations

sequences in TBD format towards the L-27 SOC infrastructure. SOC-7060 PROSPECT Operations Planning Software shall support the dispatching of the resource consumption

model output for validated operations sequences in TBD format towards the L-27 SOC infrastructure. SOC-7070 PROSPECT Operations Planning Software shall include a dedicated PROSPECT operations resource

calculation module (RCM) which is suitable for delivery to IKI, for integration in the L-27 payload level operations planning infrastructure.

Comment: after validation at PROSPECT level, IKI will test, verify and validate the combination of PROSPECT command sequences with sequences for other L-27 payloads. For parallel operations of multiple instruments, adjustments in command timing etc. may be needed which may require repeated assessment of the resource consumption based on modified sequences. These need to be possible on L-27 payload level without time-consuming iterations with the PROSPECT operations team.



SOC-7080 A PROSPECT User Manual shall be provided in line with appendix A. SOC-7090 A PROSPECT Operations Planning Software user manual shall be provided in line with appendix B. SOC-7100 A PROSPECT Quicklook Software user manual shall be provided in line with appendix C. SOC-7110 The contractor shall provide a PROSPECT kinematic computer model in TBD format that supports

combined operations planning / sequence verification / collision checking for PROSPECT robotic elements and IKI-provided robotic arm.



5.5 PROSPECT Data Product Requirements This chapter provides the requirements for PROSPECT data products. SOC-8000 The PROSPECT consortium shall compile, generate and document the following data and information:

• raw telemetry data including all housekeeping and science data • calibration information for all data types covering the parameter ranges of the relevant

environment • associated documentation • other (TBC)

Comment: This data and information is needed for the generation of PROSPECT data products, including Planetary Science Archive Data Products. SOC-8010 The PROSPECT consortium shall collect, as far as available/provided, and provide as part of the project

deliverables, relevant auxiliary data needed for data interpretation, data calibration, and archiving: • time conversion information (SCET – UTC) • reference frame /position and attitude data • command history / executed operations sequence • obtained data on spacecraft environment • associated documentation • other (TBC)

Comment: This data and information is needed for the generation of data products described in Table 1, including Planetary Science Archive Data Products. SOC-8020 The PROSPECT data products shall be compliant with the requirements defined in [NR8]. SOC-8030 The PROSPECT consortium shall, as part of the operations work, compile an experimenters logbook

that provides a detailed record of the operations team’s work including results from PROSPECT health assessment, quick look data analysis, operations planning, decision processes, error analysis, FDIR/FDIS activities, and lessons learned.



6 PROSPECT REMOTE SCIENCE OPERATIONS CENTER REQUIREMENTS

6.1 Remote PROSPECT SOC Hardware Requirements SOC-9000 The PROSPECT remote operations center data processing hardware (work stations) shall be technically

representative and compatible to the on-site operations center hardware [NR1] in order to run identical executable PROSPECT Quicklook, Operations Planning, and Data Generation software.

6.2 Remote PROSPECT SOC Software Requirements SOC-9010 PROSPECT remote SOC software shall be identical to the on-site SOC software. SOC-9020 PROSPECT remote SOC software shall access the same telemetry data servers and science operations

center infrastructure at IKI that is accessed by the on-site SOC software.

6.3 Remote PROSPECT SOC Communication Requirements SOC-9030 The PROSPECT remote SOC shall be connected to the L-27 SOC in Moscow via communication links

that provide adequate levels of security, availability and reliability. Comment: The type of link to be used will be agreed with IKI. The link service may be provided as part of the SPECTRUM support package.



6.4 Ground Reference Model Requirements For supporting the PROSPECT operations, access to flight-representative hardware for IKI and for the PROSPECT operations team needs to be provided during the PROSPECT mission. SOC-9100 The PROSPECT EM and PROSPECT ground reference models (GRMs) shall be made available

(including their associated GSEs and firmware/software) in the framework of ProSPA and ProSEED operations and operations preparation in order to enable execution of compiled command sequences for test purposes, and to support debugging, operations optimization work, and other tests and experiments.

SOC-9110 The PROSPECT EM shall serve as the ground test model (GTM) / ground reference model (GRM) at the IKI-based Russian science operations center.

SOC-9120 The PROSPECT QM elements shall serve as the ground reference model (GRM) for the European / remote science operations center. The physical location of the elements (ProSEED drill, ProSPA AL, ProSPA SIS) shall be based on a trade-off that takes into account operational, technical/scientific, and cost factors.

SOC-9130 The PROSPECT GRM elements shall receive software/firmware updates as needed to keep them functionally equivalent to the flight model.

SOC-9140 It shall be possible to update the software/firmware of IKI based PROSPECT GRM elements without the need to travel to IKI (via updated software that is either provided via electronic transfer means, or software / firmware updates that are performed via execution of command sequences that are compiled by the PROSPECT consortium).



7 VERIFICATION AND VALIDATION REQUIREMENTS

SOC-9200 The PROSPECT SOC elements (both on-site at IKI and remote in Europe) shall be verified and validated in line with the SOC verification and validation requirements provided by ESA that are derived from relevant IKI requirements.

SOC-9210 A minimum of 3 System Validation Tests (SVTs) shall be planned for. Comment: Extended working hours may be required to support these tests.



8 PROSPECT SOC DELIVERABLES AND RELATED REQUIREMENTS

8.1 Export Requirements SOC-9300 PROSPECT shall ensure that all deliverable hardware, software, databases, documents and licenses

that are needed at the IKI SOC can be exported to Russia / IKI in compliance with the project schedule.

8.2 SOC Deliverables The following tables summarize the PROSPECT deliverables (hardware, software, databases, documentation, services) for the L-27 SOC as defined / described in previous chapters. Note that these deliverables are reflected in the PROSPECT Deliverable Items and Services List (DISL), [IR7] and in [NR9]. SOC-9500 PROSPECT shall provide the following ground segment related hardware: Hardware

Deliverable

ID

Description Delivery location /

destination

Delivery date

/ milestone

Comment

HW1 PROSPECT remote operations center hardware as defined in chapter 6.1

Europe / TBD Phase D2 / TBD

HW2 PROSPECT remote operations center communication infrastructure / hardware

Europe / TBD Phase D2 / TBD

HW3 PROSPECT GRM hardware and associated systems and their software as defined in chapter 6.4

IKI, Europe / TBD

Phase C/D1/D2, TBD



SOC-9600 PROSPECT shall provide the following ground segment related software, databases and data: Software

Deliverable

ID

Description Delivery location /

destination

Delivery date

/ milestone

Comment

SW1 PROSPECT Quicklook Data Processing Software as defined in chapter 5.4 and 6.2

IKI, ESA, Europe / TBD

Phase D2 / TBD

Executable to be provided to ESA and IKI, source code to ESA

SW2 PROSPECT Operations Planning Software as defined in chapter 5.5 and 6.2


Phase D2 / TBD

Executable to be provided to ESA and IKI, source code to ESA

SW3 PROSPECT Operations Resource Calculation Module as defined in chapter 5.5 and 6.2


Phase D1 / TBD

Executable to be provided to ESA and IKI, source code to ESA and IKI (TBC)

SW3 PROSPECT kinematic models for supporting operations planning


Phase D1/D2, TBD

Executable to be provided to ESA and IKI, source code to ESA and IKI (TBC)

DB1 PROSPECT command database as defined in chapter 5.1


Phase D1/D2, TBD

Database format to be defined at later stage

DP1 PROSPECT data products as defined in chapter 5.6

Europe / TBD, ESA

Phase C/D1/D2 /E, TBD

Database format to be defined at later stage

SOC-9700 PROSPECT shall provide the following ground segment related services: Operations Support Services

Deliverable

ID

Service description Delivery location /

destination

Delivery date

/ milestone

Comment

S1 On-site Operations Support as defined in chapters 4, 4.1, and 7.

IKI, Europe / TBD

Phase D2 / E, TBD

S2 Remote Operations Support as defined in chapters 4, 4.2, and 7.

IKI, Europe / TBD

Phase D2 / E, TBD



9 REQUIREMENTS ON RUSSIAN PARTNERS

9.1 SOC Infrastructure, Software and Databases This chapter provides requirements that need to be fulfilled in order to enable compliance by the PROSPECT consortium to requirements stated in previous chapters. RRP-0010 IKI shall provide 2 workstations [NR1] for use by PROSPECT at the IKI based PROSPECT SOC which are

running a Linux based OS [NR2]. RRP-0020 IKI shall provide screens connected to the workstations in line with PROSPECT needs. Comment: as a baseline, two screens per workstation with a resolution better than HD are assumed. RRP-0030 IKI shall provide accommodation and infrastructure for the PROSPECT SOC at IKI during the SOC test

and validation phase and during the initial science operations phase. RRP-0040 The IKI SOC shall provide basic health and functional monitoring of PROSPECT. Comment: detailed monitoring of PROSPECT health, status and operations progress is the responsibility of the PROSPECT team. RRP-0050 IKI shall provide servers for PROSPECT telemetry data access and for telecommand sequence delivery by

PROSPECT, including the network infrastructure for their connection with the PROSPECT SOC workstations.

RRP-0060 IKI shall provide remote access capability for connecting the telemetry data servers and telecommand

delivery servers to the remote PROSPECT SOC. RRP-0070 IKI shall integrate the delivered PROSPECT GRM/GTM in a suitable location and configuration so that it

can effectively support PROSPECT operations planning, test execution of sequences, and debugging of operations sequences.

Comment: it is noted that use of the GRM/GTM is expected on an ad-hoc basis for specific tests, debugging etc. under IKI responsibility with PROSPECT support where needed. RRP-0100 The IKI L-27 payload operations planning software shall integrate the PROSPECT operations resource

consumption module that will be delivered by PROSPECT. RRP-0110 The IKI L-27 payload operations planning software shall integrate the PROSPECT kinematic model that

will be delivered by PROSPECT. Comment: Interface specifications for the kinematic model will be provided by IKI in later project phases. RRP-0120 IKI shall keep the delivered PROSPECT GRM/GTM updated with latest software/firmware versions

delivered by the PROSPECT consortium, and provide update confirmations/reports to PROSPECT. RRP-0200 The IKI SOC shall use the PROSPECT TM/TC databases generated by the PROSPECT consortium for

generating telecommands to PROSPECT and for correctly handling and processing PROSPECT telemetry where needed.



9.2 Reporting, Provision of Information / Data RRP-0300 IKI shall provide ESA and PROSPECT with updates concerning the L-27 SOC status and activity planning

(infrastructure development, technical interface evolution, test and integration schedules, SVT planning, operations planning) as part of the reporting agreed in the JIP [NR7].

RRP-0310 IKI shall make available the following data to the PROSPECT operations team for supporting operations

planning and data analysis activities:

Camera images of the PROSPECT field of operations (lunar surface accessible by ProSEED);

Camera images of the surrounding landing site (to support contextual understanding of measurements);

Landing site coordinates including associated error information (to support ground based modelling of environment conditions);

RRP-0320 IKI shall make available to the PROSPECT operations team, the BUNI packets corresponding to

PROSPECT telemetry within 15 minutes (TBC) of their reception on ground. RRP-0330 IKI shall make available to the PROSPECT operations team, the information and data listed in [NR9].



9.3 Operations Planning This chapter provides requirements related to operations planning that are not covered by other requirements documents. RRP-0400 IKI shall provide information on L-27 payload and spacecraft science operations constraints to

PROSPECT. Comment: this should be done via multiple TBD means / methods, which may include presentation at operations workshops, via provided documentation, resource allocation / constraints data for operations planning, and others. RRP-0410 The IKI SOC shall integrate the PROSPECT operations planning with other L-27 instrument operations

plans with the aim of optimizing the operations in accordance with the primary science goals and the various operations constraints of the mission, also taking into account the PROSPECT success criteria [IR4].

It is noted that additional requirements for the operations of PROSPECT in the context of L-27 payload operations are defined in the B-ICD [IR3f].



10 APPENDIX A: MINIMUM CONTENTS FOR PROSPECT USER MANUAL

The PROSPECT User Manual shall constitute a single, unambiguous reference for all information required by the PROSPECT users / operators and the science operations center personnel to support the development of a needed simulators, the establishment of operational databases, the production of the Operations Plans, and to implement and maintain the data pipelines for the instrument. 1. PROSPECT Definition Section 1.1. PROSPECT Definition 1.2. PROSPECT System 1.2.1. PROSPECT Description PROSPECT Description, including functional objectives, design description and operating principles 1.2.2. PROSPECT Configuration PROSPECT Configuration, including hierarchical configuration, physical configuration 1.2.3. PROSPECT Function PROSPECT Functions including functional configuration, functional description, functional block diagram, a switching diagram showing the location of the telemetry outputs and telecommand inputs and logic and circuit diagrams 1.2.4. PROSPECT Performance PROSPECT Performance including all performance data 1.2.5. PROSPECT Operations Mode PROSPECT Operations Modes including: 1.2.5.1. Nominal and Back-Up Modes Description A summary of all nominal and back-up modes, their purpose, conditions when they are used and a mode transition diagram 1.2.5.2. Nominal and Back-Up Modes For each mode a detailed description including:

• the pre-requisites needed • the resources needed • the operational constraints • mode transition operations • unit status in each mode • subsystem monitoring in the mode

1.2.6. PROSPECT Interfaces PROSPECT Interfaces including: 1.2.6.1. External Interfaces External interfaces, including power, data, control, mechanical, thermal 1.2.6.2. Internal Interfaces



Internal interfaces (between units making up the subsystem) including power, data, control, mechanical and thermal 1.2.7. PROSPECT Failures PROSPECT Failures including: 1.2.7.1. PROSPECT Fault Management and Redundancy Provisions PROSPECT fault management and redundancy provisions 1.2.7.2. PROSPECT Failures PROSPECT failures, how they are identified and the necessary recovery actions (including time criticality in each mode) 1.2.8. PROSPECT On-Board Software PROSPECT On-board Software including: 1.2.8.1. Functional Description Functional description including software task definitions, purpose, actions performed, inputs and outputs for each task, task control and scheduling information, synchronisation and datation information and software flow diagrams. 1.2.8.2. PROSPECT On-Board Software Physical Description PROSPECT on-board software physical description including ROM/RAM descriptions and memory area definitions 1.2.8.3. PROSPECT On-Board Software Operations PROSPECT on-board software operations including task monitoring, task control and error handling 1.2.9. PROSPECT Operations Procedures The PROSPECT Operating procedures shall contain:

• Detailed procedures to operate the PROSPECT • Detailed procedures required to commission and routinely monitor or periodically checkout • Detailed procedures required to operate the PROSPECT interfaces to other payload elements in

flight PROSPECT Operations Procedures (nominal and contingency) shall include:

• purpose • constraints on use • time criticality • system level pre-requisites • subsystem level pre-requisites • telemetry parameters to be monitored • special processing needed to interpret the telemetry • values expected (raw and engineering) • commands to be executed • command parameters needed • definition of calculations needed to prepare command parameters • timing between steps in the procedures • reference to recovery action at each step

1.2.10. PROSPECT Telemetry and Telecommand Data Summary Summary of PROSPECT Telemetry and Telecommand Data including: 1.2.10.1. Summary of Telecommand Summary of Telecommands



1.2.10.2. Summary of Telecommand Paramaters Summary of Telecommand Parameters 1.2.10.3. Summary of Telemetry Summary of Telemetry 1.2.10.4. Summary of Telemetry Parameters Summary of Telemetry Parameters 1.2.10.5. Summary of Software Parameters Summary of Software Parameters 1.2.11. PROSPECT Budgets PROSPECT Budgets including:

• power • data • mass • error and alignment



11 APPENDIX B: MINIMUM CONTENTS FOR SOC SOFTWARE USER MANUALS

The PROSPECT ground segment software (Quicklook software, operations planning software, resource calculation module) User Manuals shall constitute separate, unam-biguous references for all information required by the PROSPECT ground segment users / operators. SOC-UM-0100 PROSPECT ground segments software user manuals shall be compliant with [NR5], Annex H, SUM

DRD. SOC-UM-0110 The PROSPECT operations planning software user manual shall include the following specific chapters

and content:

• Operations constraints from IKI L-27 payload level operations planning as provided by IKI • PROSPECT operations planning lessons learned (this may also be organized as a separate

document that is updated after each SVT and after each operations period) • PROSPECT FDIR / FDIS manual and command sequences

SOC-UM-0120 The PROSPECT Quicklook software user manual shall include the following specific chapters and

content:

• Check lists for rapid assessment of data correctness, data completeness, and correct execution of operations

• PROSPECT Quicklook data analysis lessons learned (this may also be organized as a separate document that is updated after each SVT and each operations period)

• PROSPECT procedures for detection of anomalies and failures, including decision trees



12 ACRONYMS

AIV Assembly, Integration and Verification (on-ground) AL (ProSPA) Analytical Laboratory AP Application Process APID Application ID AUT Autonomy CCSDS Consultative Committee for Space Data Systems CET Central European Time CTR Control ESA European Space Agency ESOC European Space Operations Centre FDIR Failure Detection, Isolation and Recovery FDIS Failure Detection, Isolation and Safing FMECA Failure Mode Effects Criticality Analysis GTM Ground Test Model GRM Ground Reference Model HD High Definition (a screen format / resolution) ICD Interface Control Document IRD Interface Requirements Document ID Identification IF Interface IKI Russian space Research Institute, Moscow INFT In-Flight Testing LDO Leonardo (PROSPECT prime contractor) MOC Mission Operations Centre MTL Mission Time Line OBCP On-Board Control Procedure OU Open University (ProSPA development contractor) PACK Packet (Telecommand or Telemetry) PERP Periodic Reporting ProSEED Drill element of PROSPECT ProSPA Instrument part of PROSPECT PROSPECT The ESA project PUG Prospect User Group S/C Spacecraft SCET Spacecraft Elapsed Time SDB Spacecraft Data Base SDE Software Development Environment SIS (ProSPA) Sample Inlet System SOC Science Operations Center SRD Software Requirements Document SVT System Verification test TBC To be confirmed TBD To be determined TC Telecommand TM Telemetry UTC Universal time Coordinated