ISO 9001 Standard vs. Technical specification (ISO/TS 16949) - Differences?

  • Thread starter Thread starter sathis
  • Start date Start date
S

sathis

what is the difference between Standard & Technical specification ?

Why TS 16949 is not called as standard?

any inputs from your side

thanks

sathis
:thanks:
 
Elsmar Forum Sponsor
TS versus Standard

ISO comments on this matter ( found on the www.iso.ch website ) :
Quote
When speed is of the essence


ISO standards are developed according to strict rules to ensure that they are transparent and fair. The reverse side of the coin is that it can take time to develop consensus among the interested parties and for the resulting agreement to go through the public review process in the ISO member countries. For some users of standards, particularly those working in fast-changing technology sectors, it may be more important to agree on a technical specification and publish it quickly, before going through the various checks and balances needed to win the status of a full International Standard.
Unquote

So it looks like ISO TS should finally become a full standard. Or Not ?

Best regards,

Antoine
 
It should be noted here, just to either clarify or muddy the water (depending on your personal view), that not all Standards we talk about here in the Cove are issued by the International Organization for Standards (ISO) or one of its Technical Committees.

AS9100, the aersospace quality management system Standard, is issued by Society of Automotive Engineers (SAE), the premier membership society dedicated to advancing mobility engineering worldwide. www.sae.org/
 
sathis said:
what is the difference between Standard & Technical specification ?

Why TS 16949 is not called as standard?

any inputs from your side

thanks

sathis
:thanks:

It is based on the percentage of approving votes the voting committee casts. I am going on memory, but it is something like 75% yes votes make it a full standard, but 67% only achieves the official level of a Technical Spec. However, it should be noted, that TS calls itself an "international standard." I wonder what they know that we don't...?
 
Hello All:

The answer to some of the questions raised in this thread are answered in the Foreword of TS 16949. See page vii. Technical Specifications require a 2/3 approval whereas International Standards requires a 3/4 approval. I cannot recommend enough that we all read every word of each standard we use.

Also, here is my posting from one of the 3 threads from today about this issue....

Hello All:

It is my understanding that a Technical Specification is just as much as an "adopted" standard as a Technical Report or International Standard. As the following article explains, a Technical Specification may be produced based on time to market constraints or a lack of full consensus. A technical specification requires approval by 2/3 of the members of the voting committees.

Again, this is based on my understanding. I could be wrong in my answer or in my assupmtion of what the question is. Also, based on how I see the TS 16949 standard being used, it certianly appears to be an "adotped standard."

Regards, Dirk



Developing International Standards
There are good reasons why a standard takes so long to create.

Standards development isn't the most scintillating topic; it's complicated and difficult to explain in simple terms. But a basic understanding of the subject is useful, so let's take a quick look at the process used by the International Organization for Standardization and the International Electrotechnical Commission.

The key concept in developing a standard is the notion of consensus. As the ISO/IEC directives on procedures for developing standards notes: "Consensus, which requires the resolution of substantial objections, is an essential procedural principle and a necessary condition for the preparation of international standards that will be accepted and widely used. Although it is necessary for the technical work to progress speedily, sufficient time is required before the approval stage for the discussion, negotiation and resolution of significant technical disagreements."

Thus, although the market might want an internationally recognized document in a hurry, time is needed to achieve the required consensus from the ISO or IEC members involved in creating the standard. T he directives require that the following seven-stage project approach be used in developing international standards:
1. Preliminary work item stage (PWI)
2. New work item proposal stage (NWIP)
3. Preparatory stage (creating working drafts, WD)
4. Committee stage (creating committee drafts, CD)
5. Inquiry stage (for ISO creating a draft international standard, DIS, and for IEC creating a committee draft for vote, CDV)
6. Approval stage (creating a final draft international standard, FDIS)
7. Publication stage (involving the final work to publish the standard)

There are even several steps required to start work on an item. For example, the work must be within the scope of the committee and fully justified. The NWIP must be approved by a vote, either by three-month letter ballot or at a meeting of the participating committee members.

Once an NWIP is approved, the responsible committee or subcommittee assigns it to a working group (for ISO) or project team (for IEC). A project leader (convenor) is appointed to lead the group or team.
The WD and CD stages can sometimes be eliminated--for example, when a mature draft or a national standard is offered for fast-track voting at the DIS stage.

One or more WDs and, for some projects, one or more CDs will often be circulating for comments before the first CD ballot. By the end of the CD stage, the significant technical issues should be resolved.
Votes of participating committee members are required for the CD, DIS and FDIS stages. The minimum CD ballot period is three months. The minimum DIS ballot period is five months. For key TC 176 standards, both are generally five months to provide participating members (P-members) sufficient time for careful consideration. This seems like a long time between sending out a ballot electronically and expecting the vote from P-members, but we must remember that member bodies do the voting. They need time to get feedback from their individual members, and in cases where the native tongue isn't English, time must be allotted for translations.

The final FDIS approval ballot takes much less time, usually only two months. For final approval, two-thirds of the P-members must approve the FDIS, and no more than one-quarter of the total number of votes cast can be negative. Only minor editorial changes are allowed after FDIS approval.

In some cases, a document is needed faster than the standards process can deliver it, or it might not be possible to develop the full consensus needed. Recognizing these issues, ISO and IEC permit development of other types of documents for which the consensus process is significantly abbreviated.

These other types of deliverables include:
Publicly available specifications
Technical specifications
Technical reports
International workshop agreements

Participating members of ISO and IEC committees are organizations, not individuals. They're national standards bodies, members of ISO or IEC, that choose to participate in the particular committee. The member body for the United States is the American National Standards Institute, which accredits technical advisory groups (TAG) to provide its representation. Each of these TAGs has an administrator. (In the case of the TC 176 TAG, it's the American Society for Quality.)

The process is cumbersome, bureaucratic and time consuming, but this approach has proven effective in developing standards that are embraced and used by the international community to facilitate global trade on an equitable basis.

About the author
John E. (Jack) West is a consultant, business advisor and author with more than 30 years of experience in a wide variety of industries. He is chair of the U.S. TAG to ISO TC 176 and lead delegate for the United States to the International Organization for Standardization committee responsible for the ISO 9000 series of quality management standards.
 
Re: ISO Standard vs. Technical specification - What is the difference? Iso /ts 16949

Is there any other Technical Specification is there apart from ISO/TS16949.??
I think that is the one and only.

Sathis
 
Re: ISO Standard vs. Technical specification (ISO/TS 16949) - What is the difference?

Hello Sathis:

I did a quick search of ISO documents on the ISO website. I searched for "TS." There were 715 items found in the serch.

There are many Technical Specifications under ISO.
 
ISO 9001:2008 is explicitly the general requirement of customer & organiszation

ts 16949 : 2009 is the process based system .


VISHAL KIFI :thanx:
 
Re: ISO Standard vs. Technical specification - What is the difference? Iso /ts 16949

Is there any other Technical Specification is there apart from ISO/TS16949.??
I think that is the one and only.

Sathis

Sathis,

ISO/TS 29001 for the oil and gas industry is another.

John
 
Back
Top Bottom