It still amazes me just how complex this project is.
We wrote the software for mixture sensitizer calculations twice. We had two completely different approaches. One was to adjust the classification itself depending on the different cutoffs in the regions the SDS was being displayed.
We got it working but didn't like adjusting the classification. Multiple classifications for the same mixture felt wrong. What would an injured worker think of software design which hid a hazard in one region but displayed it in another? It didn't feel right to simply say those regions classify things differently. Finally, it didn't fit with our aim to harmonize regulations themselves. We eventually felt the "best practice" from a non-chemist viewpoint would be to classify per the most rigorous cutoff and fully inform SDS users about the scenario with a disclaimer.
Developed by Belis Enterprise and we are so delighted. It includes the word you can see above which says what the software does and the symbolism is exactly right.
The first question here about access to data came from a globally significant company. It wasn't difficult to answer because of discussions with (and a ticket from) a solo operator. It seems no matter who you are, access to data is a universal issue.
We presented SharedSDS publically for the first time at Hazmat 2015 in Sydney on 16 June. Afterwards, nine or ten people approached me with congratulations. One said it is a "brilliant" concept but most were favourably impressed if slightly less effusive! A few asked specific questions. I'll only deal with two here and save the others for subsequent blog posts.
I have been preparing a paper on SharedSDS for presentation at Hazmat 2015 in Sydney in June. The paper is more or less finished and I have covered everything I want to say. The paper's title is Taming the monster. Quite dramatic for a mostly technical paper. Having raised expectations I now need some electricity.