html5-img
1 / 31

Technical Committee 3 INFORMATION STRUCTURES, DOCUMENTATION AND GRAPHICAL SYMBOLS

Technical Committee 3 INFORMATION STRUCTURES, DOCUMENTATION AND GRAPHICAL SYMBOLS. TC3 Workshop Structuring principles and reference designations Cape Town – 2005-10-19 3(Cape Town/MT18)5. Eirik Selvik Convenor TC3/MT18. The revision process of IEC 61346-1. A DC issued in April 2005

mindy
Télécharger la présentation

Technical Committee 3 INFORMATION STRUCTURES, DOCUMENTATION AND GRAPHICAL SYMBOLS

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Technical Committee 3 INFORMATION STRUCTURES, DOCUMENTATION AND GRAPHICAL SYMBOLS

  2. TC3 WorkshopStructuring principles and reference designationsCape Town – 2005-10-193(Cape Town/MT18)5 Eirik Selvik Convenor TC3/MT18

  3. The revision process of IEC 61346-1 • A DC issued in April 2005 • A MCR issued in July 2005 with call for membership in MT 18 • A time-schedule indicating the next edition of IEC 61346-1 in end 2007 • MT 18 intend to have its first meeting in Dec. 2005 • ISO/TC10 has indicated interest in cooperation

  4. Questionnaire results • The DC document (3/763/DC) raised 12 questions to be answered by the NCs. • The MCR (3/773/MCR) provides a summary of the answers provided

  5. CHAPTER ONE Q1: Is this overall structure and content satisfactory today? • Generally found satisfactory. • Support for merging part 4 into part 1 • JP propose splitting of part 2 • Principles • Letter codes, being maintained in a database

  6. Q2: Is the definition of the scope(s) satisfactory today? • The scope is satisfactory and need not be changed

  7. Q3: Are the applied principles for structuring adequate? • The constituency principles are quite clear • The concept of the object and its aspects need more explanations • The description of the appliance of transitions and the consequences needs to be improved

  8. Q4: Is the method for the construction of the reference designations adequate? • Generally accepted • The transitions needs better explanations

  9. Q5: Are there any vague, inappropriate or unclear basic statements in clause 4 and 5? • No, but improved wording

  10. Q6: Are the classification principles adequate? • Generally found satisfactory. • The classification used in IEC 61360 is proposed as an alternative.

  11. Q7: Do the defined classes cover the present needs? • The main classes do • There are requests for the introduction of sub-classes of IEC/PAS 62400.

  12. Q8: Are there any vague, inappropriate or unclear basic statements in Part 2? • A number of important clarifications are asked for.

  13. Q9: Should the publication (part 4) be kept as a separate part or should the content moved to Part 1? • Majority for moving it to part 1 • Some will use it in part 3 • alternatively keeping it as a separate part.

  14. Q10: Should the description of the historical development be maintained? • The historical description is considered to be of value, but possibly moved to part 1.

  15. Q11: Should the life cycle story be maintained? • Yes

  16. Q12: Should the detailed discussion of the concepts (clauses 7 to 12) be maintained? • Yes

  17. Conclusions of the MCR • The revision work needs to emphasize • Part 1: • The understanding of the object concept • The impact of the use of transitions • Unambiguous versus unique reference designations • Unambiguous = identify one object • Unique = the only identifier of an object • How to handle part 4 in part 1 • Part 2: • Clarify the class/sub-class concept • Clarify task/purpose/function oriented classes • The possibility to apply a different classification scheme, especially that of IEC 61360 • Eventually inclusion of IEC/PAS 62400.

  18. Further issues (1) • DE and ISO/TC10-DE introduces a new structure “conjoint designation” for distinguishing among different plants/factories on a common site, being common for the upper part of the three other structures • Is this a location-oriented structure on a high-level ? • The convenor has suggested in some of his earlier reports that the concept of the reference designation group should be withdrawn as it is an exception to the basic principles laid down in the publication. • Is this proposal generally supported

  19. Further issues (2) • The following annexes are to be removed(already indicated in ed. 1) • Annex E - Letter codes of IEC 750 • Annex F – Differences and similarities between the designation system defined in this standard, IEC 750, ISO 3511 and ISO/DIS 1219-2 • Are the following annexes really needed? • Annex B – Examples of transitions from one aspect to another aspect • Annex C – Example of transition from one aspect to another aspect where the latter aspect has independent representations

  20. Function-oriented decomposition Object Implementable ? Product Object Occurrence of subobject Description of subobject Subobject Subobject Subobject

  21. Decomposition and composition AP AF BF BP object with function aspect only object with both function and product aspectobject with product aspect only Function-oriented decomposition Product-oriented composition

  22. Historical background

  23. Basic requirements and properties • Annex A of IEC 61346-1 provides the basic requirement and the properties that the designation system of the publication shall fulfil. • Do the NCs agree with these requirements and properties today, or should some be removed, modified or others added?

  24. Basic requirement a) • The reference designation system should be capable of being consistently applied in all phases (i.e. design, engineering, construction, erection, operation, maintenance, commissioning, decommissioning, etc.) of the life time of a technical product. The technical product can be a plant, a system, an assembly, a part, etc. • The reference designation system shall be able to accommodate different types of information and structures important to different phases of the life time. • The reference designation system should be flexible. It should be: i) applicable in the different phases covering different needs. ii) possible to construct the reference designation from the available information.

  25. Basic requirement b) • The reference designation system shall provide the ability to identify unambiguously any single object within an overall system. • The reference designation system shall allow a reference designation to be extended both at the end and at the front of the reference designation.

  26. Basic requirements c), h) and i) • The reference designation system should be fully applicable to all technical areas. • The reference designation system should support the use of, and should be able to be implemented by, computer-aided tools for engineering, construction, operation, maintenance, etc. • A reference designation shall be applicable in combination with terminal designations, signal names and document classification codes. • The reference designation system shall contain rules for the creation of structures that enable the formulation of unambiguous reference designations. Rules for the interpretation shall also be provided.

  27. Basic requirement d) • The reference designation system shall support the incorporation of subsystems and products from multiple organizations into systems from other organizations without change to the original sub-systems and their documentation. • The reference designation system shall not contain rules and restrictions that prohibit its use within a technical area. • The reference designation system shall cover all possible use of the system that can be foreseen within all technical areas and not be restricted to a particular field.

  28. Basic requirement e) • The reference designation system shall support a representation of a system under different aspects, independently of the complexity of the system. • The reference designation system shall give the possibility to maintain a given reference designation within a system when this system is incorporated into a bigger system.

  29. Basic requirements f) and g) • The reference designation system shall support the handling of computer programs and parts of such programs as technical products. • The reference designation system should be easy to apply and the reference designations should be easy for the user to understand. • The reference designation system shall be able to describe the fact that multiple independent functions are implemented within a single product. • The reference designation system shall be able to describe different aspects (views) of the system in order to represent the complex relationship among the different objects (i.e. functions, components, devices, etc.) of the system.

  30. Basic requirement j) • A reference designation shall be applicable in combination with terminal designations, signal names and document classification codes. • The reference designation system shall not contain rules that prohibit its use in combination with terminal designations, signal names, and document classification codes. A reference designation shall be clearly distinguishable from a terminal designation, signal name and document classification code

  31. Thank you for your attention.Any questions?

More Related