Q&A IQSMS connector
Virginie Pilić
Web Manuals Team
If you have any questions regarding the IQSMS connector, feel free to interact with other users or even our ASQS partner!
0
Comments
Hi,
We're starting to use the IQSMS connector. However, I was surprised to see that the two systems handle the regulation chapter structure differently.
In Web Manuals, we must connect all chapter numbers from our manuals to the parent regulation used in IQSMS in order to make the two systems match. Then, during an audit in IQSMS, we can click the crown and select from list the references that apply to each regulation item and subitems (a), (b), (c), (1), (2), , (ii) etc.
In dialogue with ASQS support, I got the following feedback:
****
This happens because we have two levels (chapter and subchapter), but WebManuals has N-levels and therefore can split up way more. Unfortunately, there is nothing that can be done on our end about it. If WM would use our internal IDs (there is another provider that does that), they could link to specific questions instead of only headlines. but of course only if we have split those questions into multiple ones. Recently WM started to load regulation data from us, maybe they are developing something in this regard.
****
In summary, given the way it works in IQSMS, the list we get by clicking the connector crown may become very extensive, and in the end, it may take some valuable time trying to find the applicable references.
I wonder whether there is any improvement planned to make the connector more precise.
Remarkable timing!
We have a meeting with ASQS today on this precise topic. This has been an ongoing discussion for a while and discussed also during Go Digital.
Happy to share the outcome of this meeting!
Hej,
During yesterdays meeting it was agreed that we will update the API available to ASQS.
In the API request combine the regulations in a similar manner as handled in IQSMS. Once implemented in our API, ASQS will update to use this new functionality (a few iterations are of course expected).
From a time perspective we agreed to target Q2 for this change and first synch to coordinate development resources is scheduled for beginning of May.
Please sign in to leave a comment.