iec co news sydney, australia – september 2007 rémy baillif iec technical officer

22

Post on 21-Dec-2015

216 views

Category:

Documents


1 download

TRANSCRIPT

Page 1: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer
Page 2: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

IEC CO NEWS

Sydney, Australia – September 2007

Rémy Baillif

IEC Technical Officer

Page 3: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

3

IEC in numbers

IEC family (members + affiliates) Number of technical committees Number of working groups Number of experts Number of pubs. in catalogue Number of pubs. issued in 2006 Conformity assessment systems Valid certificates Regional offices (HQ in Geneva)

68 + 76 = 144

178

approx. 1 100

approx. 9 000

5 613

497

3

100 000

4

Updated on 2007-02-28

Page 4: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

4

Rights of IEC Participants

FullMembers

Associate Members Affiliates

May submit votes on all TC/SC and Council

documents via electronic voting system

May submit votes/ comments on documents of 4 selected TC/SCs via electronic voting system

May not vote

May submit comments on all TC/SC and Council

documents

May submit comments only on TC/SC documents

but not on Council documents

May submit comments on the documents of 10 selected TC/SCs by e-

mail

Fully participate in international

standardization activities

Limited participation of countries with limited

resources

A type of participation, but not membership

Page 5: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

5

Time limits for the development of standards

availability of working draft (if not supplied with the proposal): 6 months

availability of committee draft: 12 months

availability of enquiry draft: 24 months

availability of approval draft: 33 months

availability of published standard: 36 months

justification for late projects

maximum 5 years

Page 6: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

6

System Approach in IEC Standardization (AC/37/2006)

The SMB is asking TCs and SCs to adopt a “System Approach” in their standardization work, thus enabling greater interaction to take place between committees

A practical example of a system approach might be that of improving a car braking system. Besides the composition of the brake pads themselves there are other elements that need to be taken into consideration: other car components, weather conditions, road surfaces, the driver, etc. All these factors have an influence on one another : interactions to be considered.

Page 7: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

7

System Approach in IEC Standardization (cont.)

The opposite to a System Approach is often termed “Silo Effect”

It describes a lack of communication and common goals between departments in an organization

In IEC terms, thinking by way of systems promotes collaboration and reciprocity between committees, while minimizing conflicts

Page 8: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

8

Example: Buildings – Technical Equipment

power supply

heatingair-condition

ventilation

sanitary

data network

alarm devices

lightingautomation

overall technicalsystem

Page 9: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

9

System Approach in IEC Standardization (cont.)

To minimize energy costs for the building, it is necessary to take into account the entire system and not simply individual components

A system is more than the “sum” of its components

The market expects and demands a single system even if this actually consists of different devices

One supplier responsible for the whole systemcoordinating the integration of many components

Page 10: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

10

System Approach in IEC Standardization (cont.)

Key words relevant to a single system approach are:

Integration: the horizontal functions of the system are intended to be perceived as an integrated feature

Interoperability: the components of different suppliers are intended to be interchangeable

Compatibility with new components

Guarantee of investment: investment in the system is intended to be guaranteed during the whole life cycle even after exchanging single components

Page 11: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

11

System Approach in IEC Standardization (cont.)

Adopting a system approach entails first identifying the role that a TC plays in the chain of events.

Is this a traditional product function, that is, one where the TC plays the role of supplier or a system function where its role is more that of customer?

Defining one’s place in the supply chain is all important when it comes to establishing the relationship between elements.

In a contemporary context, one must be aware that each and every one of us is a customer of someone else.

Page 12: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

12

System Approach in IEC Standardization (cont.)

Roles and responsibilities TC/SC with System

function

TC/SC with Product function

Lack of existing product standard – inform TC/SC with product function

Use product standard properly referenced when available

Cross-referencing of relevant standard – send draft to TC/SC in question

Use same classification, designation and coding found in the product standard

Do not introduce new classification, requirements without prior discussion with the TC/SC system function

TC/SCs with system and product functions to synchronize activities to work efficiently together

Create a dialogue

Page 13: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

13

System Approach in IEC Standardization (cont.)

Necessary action items for each TC and SC that need to be set up in establishing a clear relationship in terms of customer/supplier are:

- Set up appropriate means of dialogue – liaisons, liaison officers, joint working groups, etc.

- Include this system approach relevance in the Strategic Policy Statement (SPS) – before the end of 2007

- Review regularly – TC and SC plenary meetings with a written or verbal report

Page 14: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

14

IEC Patent Rights Policy (AC/10/2007)

Common IEC, ISO, ITU Patent Rights Policy developed by the WSC

Today, it is difficult to develop technical standards without implicating patents. On the other hand, the interests of end-users has to be taken into account. Therefore a balance must be found.

This policy should encourage industry to share its intellectual property with implementers of standards on a reasonable basis knowing that their interests will be protected.

Page 15: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

15

IEC Patent Rights Policy (continued)

Disclosure of Patent rights – those participating in standards development work, should draw the attention to relevant patents or pending patents as early as possible

Meetings – where appropriate a TC/SC chairman should remind participants of the above at each meeting

Form – a form for making patent declarations is now available on the IEC website

Database – a list of all patent declarations received by IEC is available on the IEC website.

Page 16: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

16

IEC Patent Rights Policy (continued)

3 cases when a patent has been disclosed:

- The patent holder is willing to negotiate licences free of charge with other parties on a nondiscriminatory basis on reasonable terms and conditions.

- The patent holder is willing to negotiate licences with other parties on a non-discriminatory basis on reasonable terms and conditions.

- The patent holder is not willing to comply with one of the above provisions; in such case, the IEC standard shall not include provisions depending on the patent.

Page 17: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

17

IEC Patent Rights Policy (continued)

All drafts submitted for comment shall include on the cover page the following text: “Recipients of this draft are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation.”

An IEC publication for which no patent rights are identified during the preparation thereof, shall contain the following notice in the foreword: “Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO [and/or] IEC shall not be held responsible for identifying any or all such patent rights.”

Page 18: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

18

IEC Patent Rights Policy (continued)

An IEC publication for which patent rights have been identified during the preparation thereof, shall include the following notice in the introduction:

“ IEC draws attention to the fact that it is claimed that compliance with this document may involve the use of a patent concerning (…subject matter…) given in (…subclause…).

IEC takes no position concerning the evidence, validity and scope of this patent right.

Page 19: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

19

IEC Patent Rights Policy (continued)

The holder of this patent right has assured the IEC that he/she is willing to negotiate licences under reasonable and non-discriminatory terms and conditions with applicants throughout the world. In this respect, the statement of the holder of this patent right is registered with IEC.

Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights other than those identified above. IEC shall not be held responsible for identifying any or all such patent rights.”

Page 20: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

20

Transitional period (AC/27/2007)

The SMB considered that transitional periods for the adoption by member countries of IEC safety publications to define a suitable transitional period from the use of the old to the new edition could be provided on an informative basis.

During the transitional period, both editions of publications concerned will be available.

The use of transitional periods is optional and only for safety publications.

To ensure that there is coherence between the transitional period and maintenance cycle.

Page 21: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

21

Transitional period (continued)

NOTE The attention of National Committees is drawn to the fact that equipment manufacturers and testing organizations may need a transitional period following publication of a new, amended or revised IEC publication in which to make products in accordance with the new requirements and to equip themselves for conducting new or revised tests.

It is the recommendation of the committee that the content of this publication be adopted for implementation nationally not earlier than X months/years from the date of publication.

Page 22: IEC CO NEWS Sydney, Australia – September 2007 Rémy Baillif IEC Technical Officer

Thank you for your attention.Any questions?