Issue link: https://iconnect007.uberflip.com/i/1166358
SEPTEMBER 2019 I PCB007 MAGAZINE 69 Previous chapters have presented a proposal for the content or what should be the unique cross-sector standard. Here this is a matter of defining how to establish such a standard or standards: • IPC-175x committees should become more global in their way of working with a two- level organization, including regional com- mittees like the European Proactive Alli- ance that works with the global committee that should be more global with onsite meetings distributed in all regions: Ameri- cas, Europe, and Asia every four months, for example • For IEC 62474 to be used broadly beyond the electrotechnical product sector, liai- sons with other product sectors need to be approved so that non-electrotechnical industry representatives can participate in the validation team and maintenance team. With IEC 62474 requirements, the three other elements in the IEC 62474 database (the declarable substances and declarable substance groups, the refer- ence substances, and the material classes) would remain specific to the electrotech- nical sector; any sector could define their specific features on top of the common body • If IPC-1752 or IPC-1754 are to be used broadly as data exchange standards, these standards must be available at no cost to solution providers. The IEC 62474 data ex- change requirements are included in the IEC 62474 database, which is available on- line free of cost • If IPC-1752 or IPC-1754 standards are to be used, IPC as an organization should commit to long-term support of standard- ization support activities, such as what is a core activity of the IEC central office The governance model presented in Figure 14 would need to adapt to more sectors being represented and influence the standard devel- opment. The European Proactive Alliance (PA) that gathers dozens of sectors represented by their European trade associations is one exam- • Capabilities to develop other deliverables that would prepare the final international standard: technical specifications (TS), publicly available specification (PAS), and technical report (TR) Pros of IPC and IEC standard development procedures include: • IPC standard committees are fully open to any person of interest • IPC represents mostly the electronics/ electricals sectors with the IPC-1752 data exchange format standard, but IPC has started to open up to other sectors with aerospace, defense, and heavy equipment that have developed the new IPC-1754 da- ta exchange format for complex products in their sectors • IEC has an expedited process using valida- tion teams to update referenced databases, which can be updated quickly, generally within three months (versus the time to change a standard itself, which can take over two years) • IEC works globally with well-distributed meetings in all regions Cons of IPC and IEC standard development procedures include: • IPC is North America-centric with ANSI procedure and U.S. on-site meetings that result in less attendance from European and Asian persons • IEC is working with IEC/ISO rules with an organization of global, regional, and local committees with representatives at each level designated by the countries; it is not open at all • IEC mainly represents the interests of the electrotechnical sector; TC111 commit- tee and national committees like UF111 in France are not so accessible to other sectors representatives, but different orga- nizations can get liaison status. Participa- tion to the national committee (like UF111 under AFNOR in France) could require an expensive fee