ETSI STF279 010
Page 2
ETSI STF 279/010
European Telecommunications Standards Institute
STF 279
Source: Chris Cant (Telegen Limited)
Title: Proposals relating to the EN Requirements Table
Date: 13 March 2005
Document for: Discussion
Agenda item:
Executive Summary
It is proposed that an Annex containing the EN Requirements Table should become a mandatory part of the all ETSI Harmonised Standards (HSs) related to the R&TTE Directive. It should become one of the mainthe major vehicles for ensuring closer consistency between ETSI HSs. It should remove ambiguities and contradictions between essential requirements and their tests and it should classify tests unambiguously between those comprising “essential radio test suites” and the “other test specificationssuites”.
It is proposed to simplify the format, and to address particular TCAM criticisms of existing standards which involve including additional information.
This paper presents an alternative format for this important part of future HSs. The paper is intended to stimulate discussion within the STF and with the OCG R&TTE SC in the hope that a final structure can be agreed at the next meeting of the latter body.
1. Discussion
The EN-RT is viewed as one important key to improved consistency and clarity of ETSI’s HSs relevant to the R&TTE Directive. This document proposes a number of changes to the current EN-RT format (as shown in Appendix 1 to the present documendocument)t while Appendix 2 indicates the proposed replacement format.
The STF emphasises that the suggestions in this paper are intended to stimulate discussion rather than to be considered the last word on the subject,
2. Principal changes proposed for discussion
2.1 Changed name for table
To emphasise the changed structure and to give a clear indication that the format and content has changed, it is for discussion whether to adapt a new name for the table appearing in Annex A of HSs or whether to retain the EN-RT name to preserve continuity of references to it. The rather clumsy suggested name, which better describes the content is, HS Requirements and Test Specifications Schedule (HS-RTSS).
2.2 Changes to introductory text
The purpose of the Annex is extended to include references to test Specifications and shows the correspondence between each Essential Requirement and its Test Specification.
It permits references to clauses in other documents rather than to clauses in the HS itself. This is intended to make the document more user friendly and to avoid references to Clause x.y in the HS where that clause merely refers to another clause in a referenced document.
The concept of “Unconditional” or “Conditional” requirements has been introduced to replace “Mandatory” or “Optional” in view of some previous comments about the fact that an “Optional Essential Requirement” has a strange ring to it.
The indication whether each Test Specification is part of the Essential Radio Test Suite(s) or whether it is anof the Other Test SpecificationSuite.
2.3 Table A1
The indication of which Article of RTTE justifies the requirements is moved to the head of the table as this seems the more logical place as an introductory remark rather than an appendage.
New column headings are proposed to clarify the content of the columns and to provide for additional information in the table. In particular this includes major headings addressing the “requirement”, its “conditionality”, its corresponding “test specification” and whether the test forms part of the ERTS.
3. General points
It is suggested that the format of the Annex A to HSs, should be confirmed by the Board so that its format shall be subject to the ETSI Drafting Rules allowing the Secretariat to ensure it is rigorously observed in future HSs and revisions to existing ones.
Appendix 1 to ETSI STF279 zzz010: The original template for Annex A
Annex A (normative):
The EN Requirements Table (EN-RT)
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the EN-RT proforma in this annex so that it can be used for its intended purposes and may further publish the completed EN-RT.
The EN Requirements Table (EN-RT) serves a number of purposes, as follows:
- it provides a tabular summary of all the requirements;
- it shows the status of each EN-R, whether it is essential to implement in all circumstances (Mandatory), or whether the requirement is dependent on the supplier having chosen to support a particular optional service or functionality (Optional). In particular it enables the EN-Rs associated with a particular optional service or functionality to be grouped and identified;
- when completed in respect of a particular equipment it provides a means to undertake the static assessment of conformity with the EN.
Table A.1: EN Requirements Table (EN-RT)
EN Reference / EN <xxx xxx> / CommentNo. / Reference / EN-R (note) / Status
1 / <4.2.1> / <Limits for parameter 1>
2 / <etc.> / <etc.>
3
<etc>
NOTE: <This<These> EN-R<s> <is<are> justified under Article <X> of the R&TTE Directive.
Guidance note: Select the one item under the relevant Article covered by the present document and amend the Note appropriately.
Key to columns:
No Table entry number;
Reference Clause reference number of conformance requirement within the present document;
ENR Title of conformance requirement within the present document;
Status Status of the entry as follows:
M Mandatory, shall be implemented under all circumstances;
O Optional, may be provided, but if provided shall be implemented in accordance with the requirements;
O.n this status is used for mutually exclusive or selectable options among a set. The integer "n" shall refer to a unique group of options within the EN-RT. A footnote to the EN-RT shall explicitly state what the requirement is for each numbered group. For example, "It is mandatory to support at least one of these options", or, "It is mandatory to support exactly one of these options".
Comments To be completed as required.
Appendix 2 to ETSI STF279 zzz010: Proposed new template for Annex A
Annex A (normative):
HS Requirements and Test Specifications Schedule (HS-RTSS)
Notwithstanding the provisions of the copyright clause related to the text of the present document, ETSI grants that users of the present document may freely reproduce the HS-RTSS proforma in this annex so that it can be used for its intended purposes and may further publish the completed HSRTSS
The HS Requirements and Test Specifications Schedule (HS-RTSS) in Table A1 below serves a number of purposes, as follows:
- it provides a statement of all the essential requirements in words and by cross reference to a specific clause in the present document or to a specific clause in a specific referenced document;
- it provides a statement of all the test procedure corresponding to those essential requirements by cross reference to specific clause(s) in the present document or to a specific clause(s) in specific referenced document(s);
- it qualifies each requirement to be either:
· Unconditional – meaning that the requirement applies in all circumstances, or
· Conditional – meaning that the requirement is dependent on the supplier having chosen to support optional functionality defined within the schedule;
- in the case of Conditional requirements, it associates the requirement with the particular optional service or functionality;
- it qualifies each test procedure to be either:
· Essential: meaning that it is included with the Essential Radio Test Suite and therefore the requirement shall be demonstrated to be met in accordance with the referenced procedures;
· Other: meaning that the test procedure is illustrative but other means of demonstrating compliance with the requirement are permitted;
- when the schedule is completed in respect of a particular equipment including the testing outcomes, including a completed version of Table A1 it provides a means to assert the “presumption of conformity” with the HS.
Table A.1: HS Requirements and Test Specifications Schedule (HS-RTSS)
Harmonized Standard EN <en_noThe following essential HS requirements and HS test specifications are relevant to the presumption of conformity under Articles <art> of the R&TTE Directive
Essential RequirementHS Requirement reference / HS Requirement Conditionality / HS Test Specification
No / Description / Reference: Clause No / U/C / Condition / E/O / Reference: Clause No / Observations
1
2
3
<etc>
Key to columns:
Essential Requirement:
No A unique identifier for one row of the table which may be used to identify an essential requirement or its test specification.
Guidance Note: Allocated sequentially
Description A textual reference to the Essential Requirement
Reference: Clause Number Identification of clause(s) defining the essential requirement in the present document unless another document is referenced explicitly
Guidance Note: If reference made to another document, this reference shall be included in the list of references in the present document and that reference shall either bear a specific date or a specific version number.
Conditionality:
U/C Indicates whether the requirement is to be unconditionally applicable (U) or is conditional upon the suppliers claimed functionality of the equipment (C)
Condition Explains the conditions when the requirement shall or shall not be applicable for a requirement which is classified “conditional”
Guidance Note: Either use a short description such as “if power control implemented” or a note which is amplified at the foot of the table
Test Specification:
E/O Indicates whether the test specification forms part of the Essential Radio Test Suite (E) or whether it is one of the Other Test Specifications Suite (O)
NOTE: All tests whether whether “E” or “O” are relevant to essential requirements and must be performed with satisfactory outcomes to allow a presumption of conformity. Tests designated “E” collectively make up the Essential Radio Test Suite; those designated “O” make up the Other Test Suite. For those requirements for which no test specification applies are designated “X”
Reference: Clause Number Identification of clause(s) defining the test specification in the present, document unless another document is referenced explicitly. Where no test is specified (that is, where the previous field is “X”) this field remains blank.
Observations: Remains blank in the HS but is available for use for users of the standard to record the outcome of tests against each requirement.