PCB007 Magazine

PCB007-Sept2019

Issue link: https://iconnect007.uberflip.com/i/1166358

Contents of this Issue

Navigation

Page 66 of 113

SEPTEMBER 2019 I PCB007 MAGAZINE 67 • A user interface for persons to post their declarations already established under a data exchange format • An online editor for the supplier represen- tative to build their declarations • Web services or a similar mechanism for system-to-system communication between supplier IS and their customers as a re- quester of their declarations Legal authorities (like ECHA) should offer similar services for companies to perform their "business to authorities" (B2A) duties. Objectives for Standard Development Process On IPC and IEC/ISO sides, approval process- es identifying several phases for developing the standard; the corresponding milestones to get approval and states of the standard com- pletion are pretty well-defined. This is the core process and a prerequisite in any quality systems like ISO9001. This is not enough to reach a good maturity level in standard devel - opment. We could consider a data exchange format in exchange markup language (XML) as a piece of software; then, referring to ca- pability maturity models for software devel- opment (CMMi [10] or SPICE [11] ), we should add more support processes to the repository to achieve a good quality of the standard and side pieces of it: • Configuration manage- ment: All of the pieces that work together for a given version of the standard, in- cluding internal documen- tation (for development committee members) and external documentation (for end users) • Change management: Managing all change re- quests and incident reports and keeping track of which ones have been implement- ed for a given version of the standard • Requirement management: Keeping track of the initial needs and their changes over time to know why the standard is like this at a given time Without these support processes in place, deployment of the standard would be diffi- cult because the knowledge about it would be reserved to only the development committee members, which represents a small number of persons and companies regarding the potential number of end users. Objectives for Standards Governance Existing materials and substances in arti- cles (and raw materials) data exchange stan- dards—IPC-175x and IEC 62474—have de- fined their governance models according to their current scope: the single sector for IPC- 1752 and IEC 62474, or two sectors for the IPC-1754 (Figure 14). IPC has adopted an ANSI-like procedure and governance model for developing their stan- dards: IPC Standardization Procedures (last version: October 21, 2015) that complies with ANSI Essential Requirements: Due process re- quirements for American National Standards. That means for the IPC-175x standards de- velopment: • Dedicated development committee (2-18x) for each of the IPC-175x standards that Figure 14: Current governance model for developing standards.

Articles in this issue

Archives of this issue

view archives of PCB007 Magazine - PCB007-Sept2019