Replace the Current Section 4.2 with the Following

CR # Op_NomU87A Updates to Sec 4.2, Usage and Guidelines Page 1of 2

Replace the current Section 4.2 with the following:

4.2 Operations nomenclature Assignment and Usage

OpNom shall be developed using the requirements provided in this document. OpNom used by multiple International Partners (IP’s) for both systems and payloads will reside in the Operations Nomenclature document’s main volume. OpNom unique to an IP will reside in the annex of the hardware owner.

For hardware, software, and equipment, OpNom is the single, operational name given and is used to reference the item in all operational interfaces (e.g., procedures, displays, labels). The preferred method for assigning OpNom is to use complete words and does not imply creating an acronym. Acronyms or abbreviations are acceptable for some hardware and mandatory for others. The mandatory cases are denoted by two asterisks (**) in tables throughout the main volume. If the contextual use of an abbreviation or acronym is confusing, it is recommended to use complete words. Additional requirements associated with the use of acronyms and abbreviations are outlined below.

All OpNom is registered via a CR. (See Section 1.5). If an OpNom is proposed that violates the requirements or guidelines identified below, the CR should specify the violations and the rationale for the violation. If the CR is disapproved, an OpNom waiver may be requested per Section 7 or OpNom shall be changed to meet the stated requirements.

General Requirements:

1. Register operations nomenclature for every item (stowed and installed hardware) that requires crew interface. Nomenclature must be operationally relevant.

2. Each hardware item shall have at least a part number and an OpNom.

3. If abbreviations or acronyms are necessary, ensure that they are unique, commonly recognized, and easily understood by a prospective user.

4. Abbreviations found on the laptop keyboard onboard ISS do not need to be registered in the Operations Nomenclature document.

5. If an acronym or abbreviation already exists in the Operations Nomenclature document with the same meaning, no additional registration is needed to use the acronym or abbreviation.

6. Acronyms shall be in all capital letters, with the exception of those that are not part of the normal naming registration. These exceptions are identified in Section 5, Nomenclature.

7. Nomenclature for SI units of measure shall comply with the applicable document ‘Standard Practice for Use of International System of Units (SI), ASTM E380-92’. Non-SI units of measure shall be in all lowercase letters, unless this is not part of the conventional use of the unit.

8. Real words or abbreviations shall have the first character capitalized and subsequent letters in lowercase.

9. Acronyms and abbreviations shall not resemble any emergency callouts or hazards, e.g. FIRE, TOXIC, SHOCK, SHARP.

10. When developing displays and panels, use real words. Use acronyms or abbreviations only if required due to space constraints. If a standard/approved abbreviation or acronym already exists, use it before creating a new one.

11. Acronyms and abbreviations for display and panel labels shall be registered.

12. ISS Hardware labels shall follow the Operations Nomenclature.

General Guidelines:

1. Words less than 6 characters should not be abbreviated.

2. OpNom for hardware names, terms, abbreviations, and acronyms should not include punctuation such as periods, commas, hyphens, parenthesis and the ampersand. Every effort shall be utilized to avoid use of punctuation.

3. All words should be spelled out, unless the system/payload name is a real word (e.g., Ultrasound). Real words do not need to be registered in the book.

4. OpNom for hardware names should not be more than 56 characters, including spaces. This limitation is based on the size of the MIDAS OpNom field as of July 2003. OpNom exceeding 56 characters is not efficient for use on labels, within procedures, and during communications.

5. Common terms and their abbreviations and acronyms used by multiple partners will reside in the Operations Nomenclature document main volume.

6. Terms and their abbreviations and acronyms for specific hardware will reside in the Annex of the hardware owner.

7. Duplication of OpNom should not occur for hardware items that perform different functions.

8. Hardware items that perform common functions across ISS should have the same OpNom