Iec 60870 6 701 1998

NORME INTERNATIONALE CEI IEC INTERNATIONAL STANDARD 60870 6 701 Première édition First edition 1998 08 Matériels et systèmes de téléconduite – Partie 6 701 Protocoles de téléconduite compatibles avec[.]

Exigences pour TASE.1

Il n'y a pas d'exigences pour TASE.1 en dehors de celles spécifiées dans la déclaration de conformité fournie par la CEI 60870-6-502.

Exigences pour les couches supérieures

Le protocole de présentation doit être capable de supporter l'option "Default Context Name"

(nom du contexte de défaut) Le protocole de session utilisé doit être de la version 2.

LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU.

ROSE ISO/IEC 9072 ACSE ISO/IEC 8649, 8650

Connection oriented mode session ISO/IEC 8326, 8327

The ISPICS requirements lists for TASE.1, ROSE, ACSE, Presentation, and Session are given in annex A.

For each implementation claiming conformance to this part of IEC 60870 an appropriate set of

PICSs shall be made available stating support or non-support of each option identified in this part of IEC 60870.

There are no TASE.1 requirements besides those specified in the conformance statement given in IEC 60870-6-502.

The presentation protocol shall be able to support the Default Context Name option The session protocol used shall be version 2.

Généralités

This appendix outlines the requirements for TASE.1, ROSE, ACSE, Presentation, and Session in tabular format, referencing the proforma PICS of the basic standards The tables are designed to provide precise specifications of the requirements In the event of arbitration or conflict, this appendix takes precedence over Article 6 of the current standard.

In the "PICS proforma Reference" column of the tables in this annex, as well as in the lists of condition expressions within these tables, the proforma PICS tables from the baseline standard are referenced The first letter identifies the specific proforma PICS.

The characters from the second character up to the slash (/) serve as a reference to a specific paragraph in the annex of the PICS proforma that includes the relevant table The number following the slash indicates the line number within that table.

Classification des exigences

Tout au long de la présente annexe, pour spécifier le niveau du support pour chaque dispositif la classification suivante est utilisée:

• Init-CR: Initiator Conformance Requirement (exigence de conformité de l'initiateur)

• Resp-CR: Responder Conformance Requirement (exigence de conformité du répondeur)

La colonne "Base" reflète les définitions et les spécifications de la norme de base appropriée.

Chaque entrée dans cette colonne est choisie dans la liste suivante:

The device is mandatory, meaning its syntax and procedures must be implemented as specified in the core standard However, it is not required to be used in every instance of communication unless explicitly mandated by the core standard.

The implementation of any device marked as "optional" is at the discretion of the implementer If an optional parameter is supported, the syntax must be implemented; however, it is up to the implementer to decide whether to implement the procedure.

Quand l'entrée "Base" contient deux classifications séparées par une virgule, elles renvoient respectivement aux capacités d'entrées et de sorties.

This annex outlines the requirements for TASE.1, ROSE, ACSE, Presentation, and Session through tables that reference the base standard PICS proforma, providing a clear specification of these requirements In the event of any arbitration or disputes, this annex will take precedence over clause 6 of the standard.

The tables in this annex reference the base standard PICS proformas in the PICS proforma reference column and the lists of conditional expressions below the tables, with the first letter indicating the specific PICS proforma.

The characters following the second character up to the solidus indicate a specific subclause in the annex of the PICS proforma that includes the relevant table, while the number after the solidus denotes the corresponding row number within that table.

Throughout this annex, to specify the level of support for each feature, the following classification is used:

• Init-CR: Initiator Conformance Requirement

• Resp-CR: Responder Conformance Requirement

The "Base" column reflects the definitions and specifications in the appropriate base standard.

Each entry in this column is chosen from the following list:

The feature is mandatory, meaning its syntax and procedures must be implemented as outlined in the base standard However, it is not necessary for the feature to be utilized in every instance of communication unless explicitly required by the base standard.

Optional features, indicated by "o," are left to the discretion of the implementation regarding their inclusion While the syntax for these optionally supported parameters must be implemented, it is up to each implementation to decide whether the associated procedures are also executed.

Where the base entry contains two classifications separated by a comma, these reference the sending and receiving capabilities, respectively.

La colonne "F/S" montre les exigences de la présente norme fonctionnelle Chaque entrée dans cette colonne est choisie à partir de la terminologie suivante:

The term "supported" refers to any device marked with "m," which may be either mandatory or optional according to the base standard This device must be implemented in accordance with the syntax and procedures specified in the base standard or this ISP by all implementations claiming compliance with the standard However, it is not required for the device to be utilized in every instance of communication unless mandated by the base standard or specified by this profile.

Optional support means that the implementation of any device marked as "o" is at the discretion of the implementer If an optional parameter is supported, the syntax must be implemented; however, it is up to the implementer to decide whether to implement the procedure.

Conditionally supported devices marked with "c" must be supported under the specified conditions outlined in this standard If these conditions are not met, the device falls outside the scope of this standard.

• excluded (exclu); x: tout dispositif marqué "x" est exclu du présent profil, c'est-à-dire qu'une implémentation doit se comporter comme si le dispositif n'était pas implémenté;

Devices marked with "i" are considered outside the scope of the current standard and can be disregarded, meaning they are not subject to compliance testing.

PDU supportés doit être implémentée, même si les procédures ne le sont pas (le récepteur doit, par exemple, être capable de décoder la PDU);

The term "not applicable" refers to any device marked with a "-", indicating that it is not defined within the given context This often includes parameters that are not part of the specific PDU being considered The presence of "not applicable" devices primarily arises from the format of the ISPICS requirement lists.

Quand l'entrée F/S contient deux classifications séparées par une virgule, ces références sont respectivement les capacités d'émission et de réception.

The "Status" column provides the classification found in the PICS proforma of the basic standard: 'o' indicates optional, 'c' signifies conditional, and 'o.n' denotes optional with at least one of the marked items selected.

On peut trouver les définitions des items conditionnels dans les PICS proforma respectifs.

Quand l'entrée "Statut" contient deux classifications séparées par une virgule, elles s'appliquent respectivement à l'émission et à la réception.

La colonne "Profil" donne les exigences du présent profil Chaque entrée dans cette colonne est choisie dans la liste suivante: m: support obligatoire c: support conditionnel

The "F/S" column reflects the requirements of this functional standard Each entry in this column is chosen from the following terminology:

• supported; m: any feature denoted by "m" is mandatory or optional in the base standard.

All implementations claiming conformance to this document must support the specified feature, including its syntax and procedures, as outlined in the base standard or this ISP However, the use of this feature in every communication instance is not mandatory unless required by the base standard or explicitly stated in this profile.

Features marked as "o" are optionally supported, meaning that while the syntax must be implemented, it is up to each implementation to decide whether to include the corresponding procedures.

TASE.1

La CEI 60870-6-504 [3] étant un rapport technique de type 2 et non une norme, aucune exigence complémentaire relative à la présente version de la CEI 60870-6-701 n'est formulée.

En cas de besoin, cet article sera mis à jour ultérieurement en tenant compte des évolutions de la CEI 60870-6-502 et de la CEI 60870-6-504 [3].

ROSE

Pour l'utilisation de TASE.1, le système doit supporter la correspondance de ROSE sur RTSE.

Aucune exigence supplémentaire à celles nécessaires à la mise en oeuvre de ACSE telle qu'elle est spécifiée à l'article A.5 n'est demandée.

ACSE

Référence PICS Mécanisme du protocole Init-CR Resp-CR proforma Base F/S Base F/S

A.A.7/4 Support d'exploitation de la Session V2 o m o m

Tableau A.2 – Capacités de l'initiateur/répondeur

Référence PICS Capacité Init-CR Resp-CR proforma Base F/S Base F/S

This document is licensed exclusively to MECON Limited for internal use in Ranchi and Bangalore, as provided by the Book Supply Bureau It is important to note that the optional items must include at least one of the marked selections, while certain aspects fall outside the defined scope.

Where the profile entry contains two classifications separated by a comma, these reference the sending and receiving capabilities, respectively.

Since IEC 60870-6-504 [3] is a technical report type 2 but not a standard, there are no TASE.1 particular requirements for the present version of IEC 60870-6-701.

If necessary, this clause will be revised in the future according to the IEC 60870-6-502 and

For the use of TASE.1, the system shall support the mapping of ROSE onto RTSE.

There are no other extra statement requirements than those needed for the ACSE implementation as specified in clause A.5.

PICS proforma Protocol mechanism Init-CR Resp-CR reference Base F/S Base F/S

PICS proforma Capability Init-CR Resp-CR reference Base F/S Base F/S

A.5.3 APDU supportées en mode normal

Tableau A.3 – APDU en mode normal

Référence PICS APDU Statut Profil proforma Init-CR Resp-CR

A.5.4 Paramètres supportés en mode normal

Référence PICS AARQ Statut Profil proforma Init-CR Resp-CR

A.A.10.1/5 Invocation-id de l'AE appelant o, m i i

A.A.10.1/9 Invocation-id de l'AP appelé o, m i i

A.A.10.1.10 Invocation-id de l'AE appelé o, m i i

Référence PICS Paramètre AARE Statut Profil proforma Init-CR Resp-CR

A.A.10.2/5 Invocation-id de l'AE répondeur o, m i i

PICS proforma APDU Status Profile reference Init-CR Resp-CR

PICS proforma AARQ Status Profile reference Init-CR Resp-CR

PICS proforma AARE parameter Status Profile reference Init-CR Resp-CR

Référence PICS Paramètre RLQR Statut Profil proforma Init-CR Resp-CR

A.5.5 Formulaire du nom de la syntaxe du titre AE

Tableau A.9 – Choix du formulaire du nom de la syntaxe du titre AE

Référence PICS Formulaire de syntaxe Emission Réception proforma Base F/S Base F/S

A.A.11/2 Formulaire 2 (Object Id et Integrator) o m m m

PICS proforma RLRQ parameter Status Profile reference Init-CR Resp-CR

PICS proforma RLRQ Parameter Status Profile reference Init-CR Resp-CR

A.5.5 AE title syntax name-form

Table A.9 – AE title syntax name-form alternatives

PICS proforma Syntax form Sending Receiving reference Base F/S Base F/S

A.A.11/2 Form 2 (Object Id and Integrator) o m m m

Présentation

Référence PICS Nom des items Statut Profil proforma Init-CR Resp-CR

P.A.5.2/2 Unité fonctionnelle gestion du Presentation

The support level of the PPDU parameters must align with the selection of functional units for the session and the support level of the SPDU parameters.

Tableau A.11 – PPDU Connect Presentation (connexion de présentation) (CP)

P.A.7.1/4 Liste de définition du contexte de présentation o i i

P.A.7.1/5 Nom par défaut du contexte o m m

P.A.7.1/8 Exigences utilisateur de la session o m m

PICS proforma Name of item Status Profile reference Init-CR Resp-CR

P.A.5.2/2 Presentation Context management functional unit o i i

P.A.5.2/3 Presentation Context Restoration functional unit o i i

The level of support for PPDU parameters shall be coherent with the choice of session functional units and the level of support of the SPDU parameters.

Table A.11 – Connect Presentation PPDU (CP)

Tableau A.12 – Connect Presentation Accept (acceptation de connexion de présentation) (CPA)

Référence PICS Nom de l'item Statut Profil proforma Init-CR Resp-CR

Tableau A.13 – PPDU Connect Presentation Reject (rejet de connexion de présentation) (CPR)

P.A.7.3/2 Liste de définition de contexte de présentation o i i

P.A.7.3/4 Résultat par défaut de contexte o i i

Tableau A.14 – PPDU Abnormal Release User (libération utilisateur anormale) (ARU)

Tableau A.15 – PPDU Abnormal Release Provider (libération fournisseur anormale) (ARP)

Table A.12 – Connect Presentation Accept (CPA)

Table A.13 – Connect Presentation Reject PPDU (CPR)

Table A.14 – Abnormal Release User PPDU (ARU)

Table A.15 – Abnormal Release Provider PPDU (ARP)

Tableau A.16 – PPDU Presentation Data (présentation de données) (PD)

General

This annex outlines the requirements for TASE.1, ROSE, ACSE, Presentation, and Session through tables that reference the base standard PICS proforma, providing a clear specification of these requirements In the event of any arbitration or dispute, this annex will take precedence over clause 6 of the standard.

The reference column in the PICS proforma tables and the accompanying lists of conditional expressions indicate the specific tables from the base standard PICS proformas, with the first letter denoting the particular proforma.

The characters following the second character up to the solidus indicate a specific subclause in the annex of the PICS proforma that includes the relevant table, while the number after the solidus denotes the corresponding row number within that table.

Classification of requirements

Throughout this annex, to specify the level of support for each feature, the following classification is used:

• Init-CR: Initiator Conformance Requirement

• Resp-CR: Responder Conformance Requirement

The "Base" column reflects the definitions and specifications in the appropriate base standard.

Each entry in this column is chosen from the following list:

The feature is mandatory, meaning its syntax and procedures must be implemented as outlined in the base standard However, it is not necessary for the feature to be utilized in every instance of communication unless explicitly required by the base standard.

Any feature marked as "o" is optional, meaning its implementation is at the discretion of the developer While the syntax for these optional parameters must be included, it is up to each implementation to decide whether to actually implement the associated procedures.

Where the base entry contains two classifications separated by a comma, these reference the sending and receiving capabilities, respectively.

La colonne "F/S" montre les exigences de la présente norme fonctionnelle Chaque entrée dans cette colonne est choisie à partir de la terminologie suivante:

The term "supported" (supporté) refers to any feature marked with "m," which may be either mandatory or optional according to the base standard This feature must be implemented in accordance with the syntax and procedures specified in the base standard or this ISP by all implementations claiming compliance with the standard However, it is not required for the feature to be utilized in every instance of communication unless mandated by the base standard or specified by this profile.

Optional support means that the implementation of any device marked as "o" is at the discretion of the implementer If an optional parameter is supported, the syntax must be implemented; however, it is up to the implementer to decide whether to implement the procedure.

Devices marked with "c" must be supported under the conditions specified in this standard If these conditions are not met, the device falls outside the scope of this standard.

• excluded (exclu); x: tout dispositif marqué "x" est exclu du présent profil, c'est-à-dire qu'une implémentation doit se comporter comme si le dispositif n'était pas implémenté;

Devices marked with "i" are considered outside the scope of the current standard and can be disregarded, meaning they are not subject to compliance testing.

PDU supportés doit être implémentée, même si les procédures ne le sont pas (le récepteur doit, par exemple, être capable de décoder la PDU);

Devices marked as "not applicable" indicate that they are not defined within the given context, such as parameters that do not belong to the specific PDU in question The presence of "not applicable" devices primarily arises from the format of the ISPICS requirements tables.

Quand l'entrée F/S contient deux classifications séparées par une virgule, ces références sont respectivement les capacités d'émission et de réception.

The "Status" column provides the classification found in the PICS proforma of the basic standard: 'o' indicates optional, 'c' signifies conditional, and 'o.n' represents optional with at least one of the marked items selected.

On peut trouver les définitions des items conditionnels dans les PICS proforma respectifs.

Quand l'entrée "Statut" contient deux classifications séparées par une virgule, elles s'appliquent respectivement à l'émission et à la réception.

La colonne "Profil" donne les exigences du présent profil Chaque entrée dans cette colonne est choisie dans la liste suivante: m: support obligatoire c: support conditionnel

The "F/S" column reflects the requirements of this functional standard Each entry in this column is chosen from the following terminology:

• supported; m: any feature denoted by "m" is mandatory or optional in the base standard.

All implementations claiming conformance to this document must support the specified feature, including its syntax and procedures, as outlined in the base standard or this ISP However, the use of this feature in every communication instance is not mandatory unless required by the base standard or explicitly stated in this profile.

Features marked as "o" are optionally supported, meaning that while the syntax must be implemented, it is up to each implementation to decide whether to include the corresponding procedures.

Features denoted by "c" will be conditionally supported only if the specified conditions in this standard are met; otherwise, these features fall outside the standard's scope.

• excluded; x: any feature denoted by "x" is excluded in this profile, i.e an implementation shall behave as if the feature is not implemented;

Any feature labeled as "i" is considered outside the scope of this document and can be disregarded, meaning it will not undergo the profile conformance test Nevertheless, the syntax for all parameters of supported Protocol Data Units (PDUs) must be implemented, even if the associated procedures are not; the receiver must still be capable of decoding the PDU.

• not applicable; -: any feature denoted by "-" is not defined in the context where it is mentioned, e.g a parameter which is not part of the respective PDU The occurrence of

"not applicable" features is mainly due to the format of the tables in the ISPICS requirements list.

Where the F/S entry contains two classifications separated by a comma, these reference the sending and receiving capabilities, respectively.

The status column reflects the classification to be found in the base standard PICS proforma: o: optional c: conditional o.n: optional with at least one of the marked items being selected

The definitions of conditional items may be found in the respective PICS proformas.

Where the status entry contains two classifications separated by a comma, these apply to the sending and receiving capabilities, respectively.

The profile column reflects the requirement of this profile Each entry in this column is chosen from the following list: m: mandatory support c: conditional support

This document is licensed exclusively for internal use by MECON Limited in Ranchi and Bangalore, and it has been provided by the Book Supply Bureau The selection is optional, requiring at least one of the items marked as "i" to be chosen, which falls outside the specified domain.

Quand l'entrée "Profil" contient deux classifications séparées par une virgule, elles s'appliquent respectivement à l'émission et à la réception.

La CEI 60870-6-504 [3] étant un rapport technique de type 2 et non une norme, aucune exigence complémentaire relative à la présente version de la CEI 60870-6-701 n'est formulée.

En cas de besoin, cet article sera mis à jour ultérieurement en tenant compte des évolutions de la CEI 60870-6-502 et de la CEI 60870-6-504 [3].

Pour l'utilisation de TASE.1, le système doit supporter la correspondance de ROSE sur RTSE.

Aucune exigence supplémentaire à celles nécessaires à la mise en oeuvre de ACSE telle qu'elle est spécifiée à l'article A.5 n'est demandée.

Référence PICS Mécanisme du protocole Init-CR Resp-CR proforma Base F/S Base F/S

A.A.7/4 Support d'exploitation de la Session V2 o m o m

Tableau A.2 – Capacités de l'initiateur/répondeur

Référence PICS Capacité Init-CR Resp-CR proforma Base F/S Base F/S

This document is licensed exclusively to MECON Limited for internal use at the Ranchi and Bangalore locations, and it has been supplied by the Book Supply Bureau It is important to note that the option marked as "o.n" is optional, provided that at least one of the specified items is selected, while "i" indicates items that are outside the scope of this license.

Where the profile entry contains two classifications separated by a comma, these reference the sending and receiving capabilities, respectively.

Since IEC 60870-6-504 [3] is a technical report type 2 but not a standard, there are no TASE.1 particular requirements for the present version of IEC 60870-6-701.

If necessary, this clause will be revised in the future according to the IEC 60870-6-502 and

For the use of TASE.1, the system shall support the mapping of ROSE onto RTSE.

There are no other extra statement requirements than those needed for the ACSE implementation as specified in clause A.5.

PICS proforma Protocol mechanism Init-CR Resp-CR reference Base F/S Base F/S

PICS proforma Capability Init-CR Resp-CR reference Base F/S Base F/S

A.5.3 APDU supportées en mode normal

Tableau A.3 – APDU en mode normal

Référence PICS APDU Statut Profil proforma Init-CR Resp-CR

A.5.4 Paramètres supportés en mode normal

Référence PICS AARQ Statut Profil proforma Init-CR Resp-CR

A.A.10.1/9 Invocation-id de l'AP appelé o, m i i

A.A.10.1.10 Invocation-id de l'AE appelé o, m i i

Référence PICS Paramètre AARE Statut Profil proforma Init-CR Resp-CR

PICS proforma APDU Status Profile reference Init-CR Resp-CR

PICS proforma AARQ Status Profile reference Init-CR Resp-CR

PICS proforma AARE parameter Status Profile reference Init-CR Resp-CR

Référence PICS Paramètre RLQR Statut Profil proforma Init-CR Resp-CR

A.5.5 Formulaire du nom de la syntaxe du titre AE

Tableau A.9 – Choix du formulaire du nom de la syntaxe du titre AE

Référence PICS Formulaire de syntaxe Emission Réception proforma Base F/S Base F/S

A.A.11/2 Formulaire 2 (Object Id et Integrator) o m m m

PICS proforma RLRQ parameter Status Profile reference Init-CR Resp-CR

PICS proforma RLRQ Parameter Status Profile reference Init-CR Resp-CR

A.5.5 AE title syntax name-form

Table A.9 – AE title syntax name-form alternatives

PICS proforma Syntax form Sending Receiving reference Base F/S Base F/S

A.A.11/2 Form 2 (Object Id and Integrator) o m m m

P.A.5.2/2 Unité fonctionnelle gestion du Presentation

The support level of the PPDU parameters must align with the selection of functional units for the session and the support level of the SPDU parameters.

Tableau A.11 – PPDU Connect Presentation (connexion de présentation) (CP)

P.A.7.1/5 Nom par défaut du contexte o m m

Presentation

P.A.5.2/2 Presentation Context management functional unit o i i

P.A.5.2/3 Presentation Context Restoration functional unit o i i

The level of support for PPDU parameters shall be coherent with the choice of session functional units and the level of support of the SPDU parameters.

Table A.11 – Connect Presentation PPDU (CP)

Tableau A.12 – Connect Presentation Accept (acceptation de connexion de présentation) (CPA)

Tableau A.13 – PPDU Connect Presentation Reject (rejet de connexion de présentation) (CPR)

P.A.7.3/2 Liste de définition de contexte de présentation o i i

P.A.7.3/4 Résultat par défaut de contexte o i i

Tableau A.14 – PPDU Abnormal Release User (libération utilisateur anormale) (ARU)

Tableau A.15 – PPDU Abnormal Release Provider (libération fournisseur anormale) (ARP)

Table A.12 – Connect Presentation Accept (CPA)

Table A.13 – Connect Presentation Reject PPDU (CPR)

Table A.14 – Abnormal Release User PPDU (ARU)

Table A.15 – Abnormal Release Provider PPDU (ARP)

Tableau A.16 – PPDU Presentation Data (présentation de données) (PD)

Tableau A.17 – Version de protocole de session

Tableau A.18 – Unités fonctionnelles de session

Table A.16 – Presentation Data PPDU (PD)

Tableau A.21 – Transfert normal de données

Tableau A.22 – SPDU associées au service "Kernel" (noyau)

S.A.7.1.2/5 Data transfer (transfert de données) (DT) m m m

Tableau A.23 – SPDU Connect (connexion) (CN)

S.A.8.1.3/1 Exigences utilisateur pour la session User m m m

S.A.8.1.3/4 Dépassement de capacité de données i i i

Table A.22 – SPDUs associated with the Kernel service

Tableau A.24 – SPDU Accept (accepté) (AC)

S.A.8.4.3/2 Exigences utilisateur pour la session m m m

Tableau A.25 – SPDU Refuse (refus) (RF)

S.A.8.5.2/2 Exigences utilisateur pour la session

Tableau A.26 – SPDU Finish (finir) (FN)

Tableau A.27 – SPDU Disconnect (déconnexion) (DN)

Tableau A.28 – SPDU Abort (abandon) (AB)

Tableau A.29 – SPDU Data Transfer (transfert de données) (DT)

Table A.29 – Data transfer (DT) SPDU

PICS proforma Name of tem Status Profile reference Init-CR Resp-CR

[1] CEI 60870-6-1:1995, Matériels et systèmes de téléconduite – Partie 6: Protocoles de téléconduite compatibles avec les normes ISO et les recommandations de l'UIT-T –

Section 1: Contexte applicatif et organisation des normes

Section 501: Définitions des services TASE.1

Section 504: Conventions d'utilisation de TASE.1

[4] ISO/CEI 10000-1:1995, Technologies de l'information – Cadre et taxonomie des profils normalisés internationaux – Partie 1: Principes généraux et cadre de documentation

[5] ISO/CEI 10000-2:1995, Technologies de l'information – Cadre et taxonomie des profils normalisés internationaux – Partie 2: Principes et taxonomie pour profils OSI

[1] IEC 60870-6-1:1995, Telecontrol equipment and systems – Part 6: Telecontrol protocols compatible with ISO standards and ITU-T recommendations – Section 1: Application context and organization of standards

[2] IEC 60870-6-501:1995, Telecontrol equipment and systems – Part 6: Telecontrol protocols compatible with ISO standards and ITU-T recommendations – Section 501:

[3] IEC 60870-6-504:1998, Telecontrol equipment and systems – Part 6: Telecontrol protocols compatible with ISO standards and ITU-T recommendations – Section 504:

[4] ISO/IEC 10000-1:1995, Information technology – Framework and taxonomy of

International Standardized Profiles – Part 1: General principles and documentation framework

[5] ISO/IEC 10000-2:1995, Information technology – Framework and taxonomy of

International Standardized Profiles – Part 2: Principles and taxonomy of OSI Profiles

The IEC is committed to providing the highest quality standards and values your feedback to ensure we meet your needs Please take a moment to answer the questions below and send your responses via fax to +41 22 919 03 00 or mail them to the address provided Thank you for your participation!

Fax to: IEC/CSC at +41 22 919 03 00

Thank you for your contribution to the standard-making process.

LICENSED TO MECON Limited - RANCHI/BANGALORE FOR INTERNAL USE AT THIS LOCATION ONLY, SUPPLIED BY BOOK SUPPLY BUREAU. number of the standard: (e.g 60601-1-1)

Q2 Please tell us in what capacity(ies) you bought the standard (tick all that apply).

I am the/a: purchasing agent R librarian R researcher R design engineer R safety engineer R testing engineer R marketing specialist R other

(tick all that apply) manufacturing R consultant R government R test/certification facility R public utility R education R military R other

Q4 This standard will be used for:

(tick all that apply) general reference R product research R product design/development R specifications R tenders R quality assessment R certification R technical documentation R thesis R manufacturing R other

Q5 This standard meets my needs:

(tick one) not at all R nearly R fairly well R exactly R standard is out of date R standard is incomplete R standard is too academic R standard is too superficial R title is misleading R

I made the wrong choice R other

Q7 Please assess the standard in the following categories, using the numbers:

(6) not applicable timeliness quality of writing technical contents logic of arrangement of contents tables, charts, graphs, figures other

Q8 I read/use the: (tick one)

English text only R both English and French texts R

Q9 Please share any comment on any aspect of the IEC that you would like us to know:

The CEI aims to provide you with the highest possible standards To ensure we continue to meet your expectations, we kindly request some information from you Please take a moment to complete the questionnaire below and return it to us by fax.

+41 22 919 03 00 ou par courrier à l’adresse ci-dessous Merci !

Centre du Service Clientèle (CSC)

Nous vous remercions de la contribution que vous voudrez bien apporter ainsi à la Normalisation Internationale.

Centre du Service Clientèle (CSC)

Q2 En tant qu’acheteur de cette norme, quelle est votre fonction?

(cochez tout ce qui convient)

Je suis le/un: agent d’un service d’achat R bibliothécaire R chercheur R ingénieur concepteur R ingénieur sécurité R ingénieur d’essais R spécialiste en marketing R autre(s)

(cochez tout ce qui convient) dans l’industrie R comme consultant R pour un gouvernement R pour un organisme d’essais/ certification R dans un service public R dans l’enseignement R comme militaire R autre(s)

Q4 Cette norme sera utilisée pour/comme

This article outlines various aspects of product development and evaluation, including reference works, product research, specifications, submissions, quality assessments, certifications, technical documentation, theses, and manufacturing The effectiveness of these elements can range from not at all to perfectly, indicating varying levels of success in achieving desired outcomes.

Q6 Si vous avez répondu PAS DU TOUT à

Q5, c’est pour la/les raison(s) suivantes:

The standard requires revision due to its incompleteness and overly theoretical nature Additionally, it is perceived as superficial, and the title may be misleading There may also be concerns about making the right choice regarding its application.

Q7 Veuillez évaluer chacun des critères ci- dessous en utilisant les chiffres

(2) au-dessous de la moyenne,

(4) au-dessus de la moyenne,

(6) sans objet publication en temps opportun qualité de la rédaction contenu technique disposition logique du contenu tableaux, diagrammes, graphiques, figures autre(s)

Q8 Je lis/utilise: (une seule réponse) uniquement le texte franỗais R uniquement le texte anglais R les textes anglais et franỗais R

Q9 Veuillez nous faire part de vos observations éventuelles sur la CEI:

Tiêu đề	IEC 60870-6-701:1998 Telecontrol Protocols Compatible with ISO Standards and ITU-T Recommendations
Trường học	University of International Standardisation Studies
Chuyên ngành	Electrical Engineering
Thể loại	Standards Document
Năm xuất bản	1998
Thành phố	Geneva

Định dạng
Số trang	46
Dung lượng	278,59 KB