This proposed standard is for anybody who creates or help create legal and related documents. It builds, and relies, on the foundation for plain language in WD 24495-1, Plain Language — Part 1: Governing Principles and Guidelines. This standard, Plain Language — Part 2 Legal Writing and Drafting, will add guidance and techniques to help authors make sure that people affected by legal and related…
Performance evaluation of treatment technologies for water reuse systems — Part 10: Guidelines for e...
This document provides guidelines for evaluating the dependability of treatment systems for water reuse. The dependability of a treatment system is evaluated mainly from the availabilities of unit processes composing the system facility to perform functional requirements related to water quality performance over a long period of time in operation.
The document specifies methodologies for both…
This document describes minimum requirements for small spacecraft.
Small spacecraft may employ untraditional spacecraft development and management philosophy. These spacecraft projects are usually budget-limited or mass-limited, which makes a single (exclusive) launch unaffordable.
The scope of this document encompasses different categories of small spacecraft — so-called mini-, micro-, nano-,…
Document management — Electronically stored information — Requirements for trustworthiness and relia...
This document specifies the implementation and operation of information management systems that stores and make available for use electronically stored information (ESI) in a trustworthy and reliable manner. Such ESI can be of any type, including “page based” information, information in databases and audio/video information.
This document is for use by any organization that uses information…
Electronic fee collection — System architecture for vehicle related tolling — Part 2: Vocabulary
This document defines terms within the field of electronic fee collection (EFC).
This document defines:
— terms within the fields of electronic fee collection and road user charging;
— terms that are used in standards related to electronic fee collection;
— terms of a more general use that are used more specifically in standards related to electronic fee collection.
This document does…
Space systems — Launch pad and integration site — Facility, system and equipment failure analysis
ISO 16159:2012 establishes procedures for the analysis of failures that occur during the acceptance testing or operation of launch pad and integration site facilities, systems and equipment. The procedures define the processes for investigating, analysing and identifying the probable causes of failures, and for developing corrective actions to preclude future failures.
The purpose of ISO 16159:…
Applications ferroviaires — Calcul des performances de freinage (freinage d'arrêt, de ralentiss...
Le présent document décrit les méthodologies de calcul des performances de freinage du matériel roulant ferroviaire.
Le présent document décrit les algorithmes et formules généraux qui utilisent des valeurs instantanées comme valeurs d'entrée pour effectuer les calculs de dimensionnement des équipements de frein et les performances de freinage, en termes de distances d'arrêt et de…
Perception de télépéage – Architecture de systèmes pour le péage lié aux véhicules — Partie 2: Vocab...
Le présent document définit la terminologie de la perception de télépéage (EFC).
Ce document définit:
— les termes des domaines de la perception de télépéage et de l'imputation pour les usagers de la route;
— les termes employés dans les normes relatives à la perception de télépéage;
— les termes plus généraux employés plus spécifiquement dans les normes relatives…
Software and systems engineering — Incident management
This document defines an incident management process and supporting documentation that can be used to manage and implement incident management within any organization, project or maintenance activity. Supporting informative diagrams describing the process and example documents are also provided.
This standard is applicable to incident management in all development lifecycle models.