Issue link: https://iconnect007.uberflip.com/i/1166358
SEPTEMBER 2019 I PCB007 MAGAZINE 59 in a single declaration to cover their business needs. There is a unique potential of the IPC- 175x series to cover various product types (electronic products, complex products, pack- aging) with various declaration types (certifi- cate or product statement, compliance decla- ration, composition declaration and laboratory report, partial and full material declarations) either for business-to-business (B2B) relation- ships, "request/reply" modes, or volunteer declaration by standard components manufac- turers ("distribute" mode). This IPC-175x harmonization initiative re- quires achieving different goals: • Implementing each standard with a modu- lar architecture based on the IPC-1751 schema as a foundation; each standard could extend an existing element, but no conflicting definition is authorized, like IPC-1754 extending elements from IPC- 1751 and IPC-1752 standards • Putting in place schema versioning and change management (traceability of changes) • Harmonizing the IPC-1752 and IPC-1754 data lists: DSL and query lists (QL) in terms of their schemas; there is no reason for an authority to publish their data lists in various formats for every standard Another issue to solve is that substance groups/categories are provided in IEC 62474 edition 1; IPC-1752A appendices B, C, and D; and AD-DSL 3.0 with a non-exhaustive list of individual substances. How can an SME com- pany representative, without a chemistry back- ground, decide if a substance not listed should be reported or not? To avoid this situation, a policy should be defined by this: • Only substances identified as belonging to a substance group/category could be reported against a list that refers to this group/category • The authority that issues a substance list is responsible to provide a unique identifier for each substance and for the substance group/category and the reportable substances that belong to the group/category This harmonization should include a defini- tion of common terms to designate the same data (substance group/category) and the stan- dard use cases. Other topics regarding data quality should also be addressed (Figure 7): • Data checks to verify some sectorial rules about the substances, materials and product data • Data traceability and authentication to be able to manage some regulations, like EU REACH authorizations • Data security (protocol for communica- tion) and supplier IP protection • Data aggregation (how data coming from different sources with different require- ments could be aggregated along the supplier chain) Effective Reporting With Standards Convergence The second stage is to build on top of the previous harmonization for better data accu- racy, regarding the convergence of the stan- dards and other recommendations for effective reporting of the product declarations. As mentioned earlier in the issues section, IPC-1752 and IEC 62474 have already achieved Figure 7: Data quality criteria.