Luft- og romfartsteknikk

This document belongs to the documents going along with EN 9200 relating to Project Management Specification. The aims of this document are as follows: - to specify/remind the concept of (Need) Technical Specification (N)TS; - to define the principles and conditions for drawing up, approving, using and updating a (N)TS; - to propose a template of (N)TS. The template identifies topics and types of related requirements to be covered in a (N)TS without being completely exhaustive or mandatory. It is due to be analysed like a check-list and tailored according to the type of the product of interest, the context of the bodies involved and the contractual details. The principle of drawing up a (N)TS applies to both tangible and intangible products (e.g. services). The customer/supplier relationship addressed by these principles may also apply within a single organization. The concepts of customer and supplier are discussed in this document without distinction between internal or external relationship. This document implements and adapts EN 16271 to the context, in order to meet the specific needs of the aeronautical field and more generally the needs of other fields. This document is more explicit about certain aspects of ISO/IEC/IEEE 29148 dedicated to requirements engineering, such as the responsibility for drawing up a (N)TS on a contractual basis and also the process of drawing it up within a programme (stages and milestones). It also supplements the technical specification framework proposed by ISO/IEC/IEEE 29148, in particular with requirements relating to safety of operation and result assurance. The relationships existing between Functional Performance Specification (FPS) and (N)TS for expression of needs are given in Annex A.

The document defines the requirements for the interfaces of simulation models between simulation environments.

This activity will be the update of EN16603-20-06 (published 2014). This activity was started in ECSS to implement as urgent classified Change Requests.

1.1 Purpose: The Observing System Data Message (OSDM) is a standard message format to be used in the exchange of optical telescope, laser ranging station, and radar (observing systems) information between Space situational Awareness (SSA) data providers, owners/operators of observing systems, and other parties. These messages can inform SSA data providers, which are the consumers of observing system output data, on the parameters of the observing systems. The OSDM standard will: a) enable consistent data exchange between observation data providers and SSA systems; b) facilitate data exchange automation and ingestion of observation data from different providers; c) facilitate SSA system architecture performance simulations; and d) provide a quick way to estimate the expected performance from one observing system. 1.2 Applicability: The Observing System Data Message standard is applicable to all SSA activities, especially Space Surveillance and Tracking (SST) and near-Earth objects (NEO), and other fields where the acquisition of astrometric and photometric data plays a role (e.g. space debris, observational astronomy). The standard contains a message designed to contain observing system parameters exchanged between producers and consumers of astrometric and/or photometric data. These data include observing system name, location, type (optical/radar), operator and tracking/survey performance. The OSDM is suitable for both manual and automated interaction, but will not contain a large amount of data. The message is self contained and can be paired with several Tracking Data Messages (TDM – specified reference [1]), FITS images (specified in reference [2]), or other formats containing the observation data. The OSDM standard only applies to the message format, structure and content. The exchange method is beyond the scope of the standard, and it is due to be specified in an ICD, though an ICD is not always required. The methods used to produce the data in the message are also beyond the scope of the standard. 1.3 Document structure: Clause 5 provides an overview of the OSDM. Clause 6 described the structure and content of the 'keyword = value' (KVN) version of the OSDM. Clause 7 described the strucuture and content of the XML version of the OSDM. Clause 8 describes the data and syntax of OSDM messages, in both KVN and XML. Annex A lists agreed values for some of the OSDM keywords. Annex B presents some examples of OSDMs.