D
dksfwmcc
Hi,
I have been doing TS audits for several years with no issues, but have been asked a question regarding the name that has stumped me.
Why is it a 'Technical Standard' (TS) opposed to ISOxxxx (e.g. ISO 9001 or ISO14001)?
Below is the 'wordy' text I could find on the matter, but wondered if anyone could give a shorter reasoning knowing the background specific to TS16949?
1.1 Technical Specifications
1.1.1 Technical Specifications may be prepared and published under the following circumstances and conditions.
3.1.1.1 When the subject in question is still under development or where for any other reason there is the future but not immediate possibility of an agreement to publish an International Standard, the technical committee or subcommittee may decide, by following the procedure set out in 2.3, that the publication of a Technical Specification would be appropriate. The procedure for preparation of such a Technical Specification shall be as set out in 2.4 and 2.5. The decision to publish the resulting document as a Technical Specification shall require a two-thirds majority vote of the P-members voting of the technical committee or subcommittee. The reasons for publishing the Technical Specification, and an explanation of its relationship to the expected future International Standard, shall be given in the foreword.
When a Technical Specification is used for “pre-standardization purposes”, the following text, completed as appropriate, shall be included in the Foreword:
“This document is being issued in the Technical Specification series of publications (according to the ISO/IEC Directives, Part 1, 3.1.1.1) as a “prospective standard for provisional application” in the field of ... because there is an urgent need for guidance on how standards in this field should be used to meet an identified need.
This document is not to be regarded as an “International Standard”. It is proposed for provisional application so that information and experience of its use in practice may be gathered. Comments on the content of this document should be sent to the ...[ISO Central Secretariat or IEC Central Office]...
A review of this Technical Specification will be carried out not later than 3 years after its publication with the options of: extension for another 3 years; conversion into an International Standard; or withdrawal.”
In IEC, Technical Specifications are subject to the same maintenance procedure as IEC Standards. The final paragraph of the above text will therefore need to be replaced by the relevant information on maintenance review dates (see also IEC Supplement to the ISO/IEC Directives, 2009 and Annex A).
3.1.1.2 When the required support cannot be obtained for a final draft International Standard to pass the approval stage (see 2.7), or in case of doubt concerning consensus, the technical committee or subcommittee may decide, by a two-thirds majority vote of P-members voting, that the document should be published in the form of a Technical Specification. The reasons why the required support could not be obtained shall be given in the foreword to the Technical Specification.
1.1.2 When the P-members of a technical committee or subcommittee have agreed upon the publication of a Technical Specification, the draft specification shall be submitted in machine-readable form by the secretariat of the technical committee or subcommittee to the office of the Chief Executive Officer within 4 months for publication.
1.1.3 Technical Specifications shall be subject to review by the technical committee or subcommittee not later than 3 years after their publication. The aim of such review shall be to re-examine the situation which resulted in the publication of a Technical Specification and if possible to achieve the agreement necessary for the publication of an International Standard to replace the Technical Specification. In IEC, the date for this review shall be agreed in advance of the publication of the Technical Specification (maintenance review date).
I have been doing TS audits for several years with no issues, but have been asked a question regarding the name that has stumped me.
Why is it a 'Technical Standard' (TS) opposed to ISOxxxx (e.g. ISO 9001 or ISO14001)?
Below is the 'wordy' text I could find on the matter, but wondered if anyone could give a shorter reasoning knowing the background specific to TS16949?
1.1 Technical Specifications
1.1.1 Technical Specifications may be prepared and published under the following circumstances and conditions.
3.1.1.1 When the subject in question is still under development or where for any other reason there is the future but not immediate possibility of an agreement to publish an International Standard, the technical committee or subcommittee may decide, by following the procedure set out in 2.3, that the publication of a Technical Specification would be appropriate. The procedure for preparation of such a Technical Specification shall be as set out in 2.4 and 2.5. The decision to publish the resulting document as a Technical Specification shall require a two-thirds majority vote of the P-members voting of the technical committee or subcommittee. The reasons for publishing the Technical Specification, and an explanation of its relationship to the expected future International Standard, shall be given in the foreword.
When a Technical Specification is used for “pre-standardization purposes”, the following text, completed as appropriate, shall be included in the Foreword:
“This document is being issued in the Technical Specification series of publications (according to the ISO/IEC Directives, Part 1, 3.1.1.1) as a “prospective standard for provisional application” in the field of ... because there is an urgent need for guidance on how standards in this field should be used to meet an identified need.
This document is not to be regarded as an “International Standard”. It is proposed for provisional application so that information and experience of its use in practice may be gathered. Comments on the content of this document should be sent to the ...[ISO Central Secretariat or IEC Central Office]...
A review of this Technical Specification will be carried out not later than 3 years after its publication with the options of: extension for another 3 years; conversion into an International Standard; or withdrawal.”
In IEC, Technical Specifications are subject to the same maintenance procedure as IEC Standards. The final paragraph of the above text will therefore need to be replaced by the relevant information on maintenance review dates (see also IEC Supplement to the ISO/IEC Directives, 2009 and Annex A).
3.1.1.2 When the required support cannot be obtained for a final draft International Standard to pass the approval stage (see 2.7), or in case of doubt concerning consensus, the technical committee or subcommittee may decide, by a two-thirds majority vote of P-members voting, that the document should be published in the form of a Technical Specification. The reasons why the required support could not be obtained shall be given in the foreword to the Technical Specification.
1.1.2 When the P-members of a technical committee or subcommittee have agreed upon the publication of a Technical Specification, the draft specification shall be submitted in machine-readable form by the secretariat of the technical committee or subcommittee to the office of the Chief Executive Officer within 4 months for publication.
1.1.3 Technical Specifications shall be subject to review by the technical committee or subcommittee not later than 3 years after their publication. The aim of such review shall be to re-examine the situation which resulted in the publication of a Technical Specification and if possible to achieve the agreement necessary for the publication of an International Standard to replace the Technical Specification. In IEC, the date for this review shall be agreed in advance of the publication of the Technical Specification (maintenance review date).