The Reference Designation System (RDS) A . - 81346
26th Annual INCOSE International Symposium (IS 2016)Edinburgh, Scotland, UK, July 18-21, 2016The Reference Designation System (RDS)A common naming conventionfor systems and their elementsHenrik BalslevSystems Engineering A/Swww.syseng.dk 45 21 68 48 67hb@syseng.dkCopyright 2016 by Henrik Balslev. Published and used by INCOSE with permission.Abstract. This paper introduces the Reference Designation System (RDS) as defined in theISO/IEC 81346 standard series. The 81346 standard is a horizontal standard within ISO andIEC, and thereby a reference document for all other international standards. RDS identifiessystems and their elements. A reference designation (a TAG number) is the output of RDS. TheTAG numbers act as labels for the system and the system elements, and are used for instant andunambiguous recognition across different kinds of documentation and labelling of tangibleproducts as well as non- tangible products such as different models in a software tool. RDS isan international “naming convention” designed for systems and their elements and a practicaltechnique to underpin a common understanding among different disciplines. The use of RDSas a fundamental system naming convention is not widely known within the INCOSEenvironment. By this paper, the author wishes to reach out to INCOSE and systemsengineering in general, so the principles of RDS is to be better understood and recognized as abasic part of systems engineering tool box. RDS provides generic principles and are applicablein more or less all technical disciplines; among these are civil engineering, mechanicalengineering, electrical engineering and software engineering. Application examples areprovided and a case example showing the economic benefit is presented.IntroductionIn the design of systems there is a need for identification of the systems and their elements.This may be done simply by naming the systems, but as complexity grows there is a need forspecific identifiers of systems and their elements. The identification ensures that the elementsof system of interest can be recognised across various models and documents by bothstakeholders and IT systems.Very often, system and system elements and their related models are not labelled at all or agiven some kind of TAG number created to carry a range of information in addition to the mainpurpose; identification. Such TAG numbers seldom comply with international rules, but areinstead company specific.The only international standard for creating unambiguous identifiers for systems and theirelements is the ISO/IEC 81346 standard series, which has a very clear scope. It defines therules for reference designation systems (RDS), where the output is reference designations (RD).
An RD is an identifier, designed to unambiguously identify systems and their elements by acombination of well-defined relations (part-of and type-of relations) and different aspects(function, product, location and type). The RD is a clear, sharp and easy-to-learn internationalnaming convention.The RD is also a TAG, whereas a TAG is not necessarily a RD. The main difference betweenany random TAG and an RD is, that the RD by default determines system types and elementrelations, whereas there is no guarantee for this when TAG’s are created without the rules from81346 applied.An important mechanism of RDS is, that RDS handles flexible system structures by multipleviews, recognized as “tree-like structures” in 81346. This means that the output RD has nofixed format, but is to be read and understood as an unlimited navigation in system structures.In contrast to RD, any random TAG often has a fixed notation, which may lead to limitations inthe design of system structures.RDS is not linked to any specific domain, but acts as a neutral provider. This means that RDShas potential applications in a wide range of industries.The RD creates a link among various models of the system(s) which are designed andengineered by a wide range of actors, and thereby creates both a common language amonghumans and among various computer systems.Background – The standard for designationsThe basic for RDS was defined by IEC 60113-2 in 1971. After this came 3 successors: IEC60750 (1983), IEC 61346 (1996) and lately ISO/IEC 81346 (2009).With the revision in 1996, the use of item/reference designations became further extended. Itwas recognised that reference designations could be used as a powerful tool for informationmanagement and systems thinking became an integral part of the standard.Information was not necessarily contained in ready-made documents, but could be fragmented,existing in different data bases, from which documents could be put together as needed(including graphical presentations). In such an environmen , it was required to use thereference designation system as a "navigation tool".Instead of "smart" economising with computing power it had become more essential todescribe things logically and straightforward in order to enhance functionality, exchangeabilityand communication. One of the important requirements was that the reference designationsshould be possible to use over the entire life cycle of the objects.In the latest edition, ISO/IEC 81346-1:2009, the rules established in the successors aremaintained, but more emphasis is put on the description of the concepts in order to enhance theunderstanding and applicability of the standard, including systems thinking.Although it can be argued about where exactly the boundaries should be, it is possible toillustrate roughly the ambitions and the scope of the revisions as in figure below:
Application domainCommon ISO/IECIEC 81346-1:2009IEC 61346-1:1996Technicalinformation ingeneralTechnicaldocumentation ingeneralIEC 60750:1983IEC 60113-2:1971Diagrams withsupplementarydocumentsLife lationMaintenance /improvementsPhase out /recycleFigure 1. Scope of reference designation standardsThe Reference Designation SystemThe introduction of ISO/IEC 81346-1:2009 defines the following (extract in italics):By applying the structuring principles, even very large sets of information in a complexinstallation can be handled efficiently.The structuring principles and the rules for reference designations provide a system that iseasy to navigate within and easy to maintain. This system provides an excellent overview on atechnical system(*) since composite structures are simple to establish and understand.The structuring principles and the rules for reference designations allow, by accepting morethan one aspect, that more than one coding principle can be applied. This technique alsoallows ‘old structures’ (that means existing structures) to be handled together with ‘newstructures’ by using multiple unambiguous identifiers.The structuring principles and the rules for reference designations support individualmanagement for the establishment of reference designations, and enable subsequentintegration of modules into larger constructs. They also support the establishment of reusablemodules, either as functional specifications or as physical deliverables.(*) Systems and systems thinking is an integral part of the standard.
Overview of the 81346 standard seriesThe ISO/IEC 81346 standard series consist of the following parts:TitleContent:IEC 81346-1 (2009)Industrial systems, Installations and Equipment andIndustrial Products – Structuring Principles andReference Designations –Part 1: Basic rules.The fundamental rules:IEC 81346-2 (2009 – under revision 2016)Industrial systems, Installations and Equipment andIndustrial Products – Structuring Principles andReference Designations –Part 2: Classification of Objects and Codes forClasses.Letter codes forclassification:ISO/TS 81346-3 (2012) Technical SpecificationIndustrial systems, Installations and Equipment andIndustrial Products – Structuring Principles andReference Designations –Part 3: Application rules for a reference designationsystem.A technical specificationused for special domains.ISO/TS 81346-10 (2015) Technical SpecificationIndustrial systems, Installations and Equipment andIndustrial Products – Structuring Principles andReference Designations –Part 10: Power plants.The industry related part of81346 applicable for powerplants.“RDS-PP”Letter codes for systems in apower ns(TAG’s)SystemsElementsComponentsSpacesContains limitations to therules provided in part 1.
ISO/DIS 81346-12 (2016 – Draft InternationalStandard)Industrial systems, Installations and Equipment andIndustrial Products – Structuring Principles andReference Designations –Part 12: Construction works and building services.“RDS-CW”The industry related part of81346 applicable for thebuilding industry.Letter codes for systems in aconstruction complex /a building.Core elements of RDSThe 81346 standard series concerns the designation of technical objects – of any given kind,but mostly recognized as systems – in structures in a well-defined manner.Basically 81346 uses relations to handle complexity:part-of relations(partitive relations)used for structuring of objectsdetermining system andelements in 81346-1type-of relations(generic relations)used for classificationof systems and componentsin 81346-2 (the letter codes)and
According to 81346, a reference designation system consists of:1A single level or multi-level structureSingle level:This is used to structure objects (systems),based on part-of relations:Multi-level:2One or more aspects of the structures%This is used to clear the content of the structure,that is to filter out information and only seespecific aspects of a system in specific part-ofrelation.Aspects are:3%Type-Product Location Function#(user defined)Numbers- #0102This is used to separate objects from oneanother.0304
Note: Preceded zeros may be used (like here)but shall have no specific meaning.05It may in addition (often) also have:4Classes in form of letter codesABTThis is used to recognize the class of object andto identify objects with similar properties.QQC The reference designation of a system and system elements are made by combining:orwith at least oneASPECTand often a LETTER CODEand a 123The reference designation identifies systems and their elements unambiguously across alldisciplines and documents, it systems etc. A reference designation is therefore a code or an
"address". It indicates where in the reference designation system an object belongs, so that anyobject of interest can be retrieved.Examples are provided in the following chapter.Syntax of RDSThe syntax of the reference designation is as shown in figure below:Single-levelreference designationPAANN.AANN.AANN.AANNPrefix / /-/#/%Prefix, space orClass letter codeSee Appendix ANumberFigure 2. Reference designation syntax [Figure from ISO 81346-12]NB! Reference designations are read from right to left, as the rightmost part of the code stringis the object of interest which is designated!Examples of reference designations are:Object (system)Reference designationDoor no. 5 (QQC5)-QQC5Wall construction no. 1 (AD1)part ofWall system no. 1 (B1)Door no. 2 (QQC2)part ofWall construction no. 3 (AD3)part ofWall system no. 1 (B1)Ventilation plant no. 4 (HF4)part ofVentilation system no. 1 (J1)-B1.AD1-B1.AD3.QQC2 J1.HF4
Switch no. 6 (SFA6)part ofLighting system no. 2 (HH2)part ofPower supply system no. 1 (HG1)part ofElectrical system no. 2 (K2) K2.HG1.HH2.SFA6The reference designation is considered to be an attribute (metadata) to any system or systemelement, which identifies the system unambiguously. Therefore, the reference designationshall be shown next to (or nearby / as a part of) the system or the element in the systemdocumentation or system model representation, and thereby creating the commonunderstanding of different views of systems and their elements - along with a commonunderstanding of which system (or element of the system) are viewed.Sub-suppliers and RDSA fundamental technique of RDS is to allow sub-suppliers to enable an RDS system which fittheir system design. As a logical consequence of this, sub-contractors are not to follow anoverall RDS “number” principle from clients, but more to be implemented as a part of a largerwhole.Therefor rule 5 in 81346-1 says “The object represented by the top node shall not be assigned asingle-level reference designation”. This ensures that sub-suppliers can maintain a stablesystem design, and keep supplier identification within documentation without adoptingdifferent TAG systems from a range of clients.Figure 3. Adaption of a system from sub-supplier into system of interest
Application of reference designations (RDS)The appliance and knowledge of reference designations varies significantly among differentdomains. Because the technique originates from the electrotechnical domain, where saferecognition and a reliable link between real-world and documentation is fundamental (forsafety reasons), the RDS is widely implemented in IT software tools for electricaldiagramming.As the application area of the 81346 standard was expanded in 2009, more and more softwaretools implements the principles, for example tools for process diagramming and modellingtools for Information Modelling. Whether an IT system adopts the RDS technique or not is aquestion of how well it can handle part-of relations in documentation and modelling andmultiple structures.The RDS mechanism is generic and not linked to any specific domain. As an example of theexpansion of the application of RDS, the RDS system has lately formed the basis for labellingof systems in the Danish building industry (wall system, roof system, HVAC system etc.),where a “common language” by means of a reliable interdisciplinary naming convention wasrequired as a safe identifier for exchange of information across disciplines and across verydifferent IT tools used for modelling and simulations.Other application areas are emerging such as oil & gas industry (off-shore), wind turbineindustry. Various plants (cement, mining, water distribution etc.) are also examples ofindustries where the RDS gains favour.The economic benefit of RDSISO has published international case studies “Economic benefits of standards vol. 1 & 2”1providing cases for economic aspects of working with international standards in a broad sense.Because RDS is based on a system mind-set, a decision to apply RDS automatically leads tosystem awareness, and thereby the door is open to apply systems engineering.In INCOSE it is recognized, that systems engineering is a point of synchronization forknowledge and any other related subject of design. What RDS offers in this point ofsynchronization is a description of the core structures, and an unambiguous naming conventionfor the systems and system elements to be used across disciplines and tools.1See references.
RDS81346Figure 4. RDS as the naming convention of systems in the point of synchronizationCaseRDS has been applied for a client acting as EPC within the construction area of large andcomplex transformer platforms for off-shore use. A design concept based on elements ofsystems engineering was implemented, as the previous designs had grown dramatically incomplexity with loss of time, quality and money as a consequence.The result was to introduce a concept based on system architecture, describing the system andsystem elements, and label this structure in accordance with RDS. The RDS now ensures astability of labels so navigation in the complex system structures are unambiguous in the fulllife cycle, from tender to design over construction and commissioning and maintenance.Real figures for the project show the dramatic impact of a clear architecture and designationwith RDS. The economic benefit becomes clear for the 2nd project and continues to increase inthe 3rd project as shown in figure 5 (below):
Figure 5: Figures from a project, implementing system engineering and RDS(reproduced by permission from Semco Maritime A/S).SummarySystems engineering has a need for a common language, which RDS can provide. Since thebasic mechanism of the common language originates from industrial systems, installations andequipment as given in the ISO/IEC 81346 standard series (RDS), the principles can be adoptedin most technical industries. A few application examples are given in appendix A.The output from RDS is the reference designation (RD). The RD is designed to create linksamong various models of the systems which are designed and engineered by a wide range ofactors, and thereby creating both a common language among humans and among variouscomputer systems.The RDS can be seen as simple yet very strong and flexible: The simplicity is based onrecognition of systems (objects) organized in type-of relations in the classification system fromwhich they are redrawn. Classes from the classification system can subsequently be combinedin any way needed in part-of relations, equivalent to organization of systems and systemelements.RDS provides a lifecycle stable code based on classification. This enables pre-coding ofobjects in software object libraries, easy letter coding which is recognizable for humans andcomputer systems, and an object oriented approach to the complexity of systems organized inpart-of relations.RDS acts as the spine for the common language among all disciplines. It is creating aninter-disciplinary understanding of systems and their constituents across actors andIT-platforms.Application of RDS in a real world case example demonstrates a significant positive impact inconsumption of hours, with up to 50% reduction by the third project.
Appendix A - Examples of applicationThis appendix shows different applications of RDS in different domains.EXAMPLE 1:RDS has been used to address the complexity of a roof (system) and its elements by means ofthe product aspect (-), determining how the system is constructed.Figure 6: Example of RDS application in the building construction domain
EXAMPLE 2:A manufacture of bearings has organized objects with common properties and designate thesetypes by means of the type aspect (%) in RDS.Figure 7: Example of RDS appliance for types of bearingsEXAMPLE 3:A quantity surveyor has organized windows with common properties and designate these typesby means of the type aspect (%) in RDS.Figure 8: Example of RDS appliance for types of windows
EXAMPLE 4:PTTTTSTT EQB1PT GQA2 BPA6 BTB3 BTA3 BTB2PTTTTS EPB1TS BTA2 HNC1 GQA1 HNC2PTM G1 QMB2 BPA4 EGB1PTPTM BPA2 BPA1 QMB1 BPA5 BPA3 BTB1 BTA1Functions in a diagram of a ventilation plant (G1) designated by means of the function aspect( ) in RDS:Figure 9: Example of RDS function aspect applied in a functional diagram
EXAMPLE 5:Spaces on a plan of level 2 in a building are designated by means of the locationaspect ( ) in RDS:Figure 10: Example of RDS location aspect applied in a building
ReferencesISO/IEC 81346-1: (2009): “Industrial systems, installations and equipment and industrialproducts - structuring principles and reference designations Part 1: Basic rules”ISO/IEC 81346-2 (2009): “Industrial systems, installations and equipment and industrialproducts - structuring principles and reference designations Part 2: Classifications of objects and code for classes”.NOTE: Under revision. CDV version is to be launched in May 2016.ISO 704 (2009): “Terminology work - Principles and methods”ISO 22274 (2013): “Systems to manage terminology, knowledge and content –Concept-related aspects for developing and internationalizing classification systems”Balslev, Henrik (2014): “Reference Designation System for Coding System Objects”,INCOSE Insight Volume 17, April 2014. Article.Economic benefits of standards. International case studies. Volume 1 & 2.International Organization for Standardization 2011-2012.ISBN 978-92-67-10556-7 & ISBN 978-92-67-10580-2.Video introduction on YouTube:RDS / 81346 - It’s all about creating a common language (12 mi
The 81346 standard series concerns the designation of technical objects – of any given kind, but mostly recognized as systems – in structures in a well-defined manner. Basically 81346 uses relations to handle complexity: part-of relations (partitive relations) used for structuring of objects determining system and elements in 81346-1 and
All Allison automatic transmission models offer comprehensive coverage with 100% parts and labor. Coverage may vary by model and by application. Contact your Allison representative for details. Y Y 1000 RDS, 1350 RDS , 2100 RDS, 2200 RDS, 2300 RDS, 2350 RDS, 2500 RDS, 2550 RDS 3000 RDS, 3500 RDS 4000 RDS
May 02, 2018 · D. Program Evaluation ͟The organization has provided a description of the framework for how each program will be evaluated. The framework should include all the elements below: ͟The evaluation methods are cost-effective for the organization ͟Quantitative and qualitative data is being collected (at Basics tier, data collection must have begun)
Silat is a combative art of self-defense and survival rooted from Matay archipelago. It was traced at thé early of Langkasuka Kingdom (2nd century CE) till thé reign of Melaka (Malaysia) Sultanate era (13th century). Silat has now evolved to become part of social culture and tradition with thé appearance of a fine physical and spiritual .
Audio Processing Transmitting RDS ENCODERS Mobile Metering fmb80 / fmb10 / rds silver Meeting your needs Audemat-Aztec and RDS The world leader in RDS/RBDS, Audemat-Aztec is pioneer in this technology. Since its inception Audemat-Aztec has been part of the RDS forum. Our RDS encoders are
CD RDS RECEIVER AUTORADIO CD RDS SINTOLETTORE CD RDS REPRODUCTOR DE CD CON RECEPTOR RDS CD RDS-EMPFÄNGER CD RDS-ONTVANGER CD RDS ПРИЕМНИК DEH-1420UB DEH-1410UB DEH-1400UB DEH-1400UBB English Nederlands Deutsch Español Italiano Français Русский FRP XD SURGXFWV ª
On an exceptional basis, Member States may request UNESCO to provide thé candidates with access to thé platform so they can complète thé form by themselves. Thèse requests must be addressed to esd rize unesco. or by 15 A ril 2021 UNESCO will provide thé nomineewith accessto thé platform via their émail address.
̶The leading indicator of employee engagement is based on the quality of the relationship between employee and supervisor Empower your managers! ̶Help them understand the impact on the organization ̶Share important changes, plan options, tasks, and deadlines ̶Provide key messages and talking points ̶Prepare them to answer employee questions
Dr. Sunita Bharatwal** Dr. Pawan Garga*** Abstract Customer satisfaction is derived from thè functionalities and values, a product or Service can provide. The current study aims to segregate thè dimensions of ordine Service quality and gather insights on its impact on web shopping. The trends of purchases have
