RoHS and REACH compliance

[mkne]

I introduced Part-DB to a co-worker which is currently dealing with the topics of RoHS and REACH compliance of our parts and products. I proposed the possibilities of parameters and/or tags to label parts as RoHS/REACH compliant.
My observations are the following and I would love to hear if other Part-DB users have the same need and maybe different solutions/ideas to solve the problem:

• Digikey imported parts lack the RoHS and REACH information despite being available in the section "Environmental & Export Classifications" on the website of a part as "RoHS Status" and "REACH Status" Is this info not available via the API? Or is it just not mapped/used in Part-DB?
• Mouser imported parts still don't have parameters. On their webpage for the part there is a Product attribute "RoHS"
• Octopart imported parts seem to have a RoHS parameter
• I can view the tags column in the parts list but not in the BOM? Might this be possible to also display the tags in the BOM-List? If not why not?

[mkne]

I will update this list with the Information as soon as I have them.

Info provider	Parameter name RoHS	Parameter name REACH SVHC	Parameter name China RoHS
Digikey	ProductDetails.Classifications.RohsStatus	ProductDetails.Classifications.ReachStatus	xxx
Mouser	SearchResponseRoot.SearchResults.Parts.MouserPart.ROHSStatus	SearchResponseRoot.SearchResults.Parts.MouserPart.REACH-SVHC.[0]	xxx
element 14/Farnell	keywordSearchReturn.products.rohsStatusCode	keywordSearchReturn.products.attributes.attributeLabel = " SVHC"	xxx
Octopart/Nexar	rohs	reachsvhc	china_rohs
OEMSecrets	stock.compliance.rohs	xxx	xxx
LCSC	RoHS	xxx	xxx
Reichelt	RoHS	xxx	xxx
Pollin	-	-	-
TME	Data.ProductList.Certificates="ROH"	xxx	xxx

'xxx' = not yet found or searched for in API doc or on the info provider's website
'-' = not available (even not found on the website of a part, maybe only available in the datasheet pdf)

[electronics4fun]

As there is not only one status for RoHS, does it make sense that you use the Parameters for that? Which BOM do you mean? The BOM from Projects?

[mkne]

Are there different BOM? Yes, I created projects to use BOMs. Sometimes I imported KiCAD BOM or manually mapped CSVs and sometimes I just created the BOM in Part-DB. I have already seen that for some parts it says RoHS-Status = Y-EX (which might mean exception or exemption).
Parameters was my first idea as the imported parts from Octopart, OEMSecrets, Farnell had parameters for RoHS and some also for REACH SVHC. But the disadvantage is that a user would have to explicitely look into the parameters tab and as the parameters are named differently depending on the info provider it's not as obvious as having a tag clearly showing Non RoHS or SVHC which I can also filter very easily and put a link in the form http://partdb/parts/by_tag/Non%20RoHS on my start page.

[electronics4fun]

In the end you need something where you can qualify your part regarding REACH, RoHS and maybe other stuff.
If it is sufficient that you check RoHS, REACH and others manually and then decide if the part is okay for production, then take a look into the following.
In #1041 at "3. Custom part status". Would that help you? In our case we check for the value in "Custom part status" and if the part is not qualified it will not show up in Altium. For KiCad that needs adjustments

[mkne]

@electronics4fun Thank you for your input. I had another discussion with my colleague who is responsible for this regulatory stuff.
We might do it now the following way: I will set the status of all parts to "review needed" and then we will manually check all parts and add a tag "RoHS compliant" and "Not RoHS compliant" (or similar) and if it contains a SVHC also a tag "SVHC".
From a data management point of view I don't like having two tags that are just a negation of each other. But having a tag "Not RoHS compliant" makes it more obvious that this part is not allowed for new development and only for spare parts or development purposes. (For this purpose the "custom part status" might be really useful)
Nevertheless, it would be useful to have the information as parameter if the info provider offers this information via its API. Mapping this information during import to a common field would be even better. But as long as "Custom part status" is not available in the release version of Part-DB, I guess we will take that route with the tags. I just miss the option to see the tags in the BOM, so that would be another argument for "Custom part status" if this would be available as column in the BOM. On the other hand, I think this information does not really belong into a BOM. I had a quick look into the source but I don't understand enough of PHP, Twig and Symfony to find where I would have to change the code to add a column to show up in the BOM.