Naming – Accelerator as System

Table of content

Note

Example

Before Naming Convention change

Naming Convention change, part 1

Naming Convention change, part 2, Accelerator as System

Note

Already available ESS names are unchanged and remain.

Change of rules for ESS to be applied for names ahead.

Example

1) 2)

System structure Device structure System structure Device structure

Before Naming Convention change

Area structure need to be part of ESS name (Subsection).

Device structure need to be part of ESS name (Device Type).

if mnemonic available for highest level in Area Structure (Super section), it's considered as OFFSITE

if mnemonic available for highest level in Area Structure (Super section), it's used in Device Name

ESS names

A2T-010PRL:RFS-PRLTap-054

if mnemonic available for Super section, then made part of ESS name

Acc-A2T-010PRL:RFS-PRLTap-054

Naming Convention change, part 1

System structure need to be part of ESS name (System or Subsystem).

Device structure need not to be part of ESS name (Device Type)

ESS names

A2T

A2T-010PRL

A2T:RFS-PRLTap-054

A2T-010PRL:RFS-PRLTap-054

if mnemonic available for System Group, then made part of ESS name

Acc-A2T

Acc-A2T-010PRL

Acc-A2T:RFS-PRLTap-054

Acc-A2T-010PRL:RFS-PRLTap-054

Jira

NT-278 ESS Naming Convention - Update

Naming Convention change, part 2, Accelerator as System

System structure need to be part of ESS name (System Group, System or Subsystem).

Device structure need not to be part of ESS name (Device Type)

if OFFSITE names/rules not considered then Accelerator as a System available as

ESS names

A2T

A2T-010PRL

A2T:RFS-PRLTap-054

A2T-010PRL:RFS-PRLTap-054

or

Acc

Acc:RFS-PRLTap-054

For this, rules to be changed such that System Group mnemonic not part of of ESS together with System,	Subsystem mnemonics.

As understood, it is not to be possible to have ESS names

Acc-A2T

Acc-A2T-010PRL

Acc-A2T:RFS-PRLTap-054

Acc-A2T-010PRL:RFS-PRLTap-054

Rules may be changed without OFFSITE names being removed. In either case, OFFSITE names to be	considered differently. One implication is that implementation to be changed such that no more OFFSITE	names may be created. Another implication is change of UI as result. Some changes, e.g. filtering in UI, to be	done after OFFSITE names removed.

Main requirement

no more OFFSITE names to be created

Preferable requirement

OFFSITE names removed

Jira

NT-279 ESS Accelerator as System

2020-06-11T10:32:24.524211080