tag:blogger.com,1999:blog-4922736527622150204.post4451972652421581576..comments2022-04-13T15:53:49.336-07:00Comments on DBDOC News: Has Recent Work Introduced Errors? Geoff Michaels, P. Eng.http://www.blogger.com/profile/08106776449998803700noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-4922736527622150204.post-39419561789631758402017-01-10T18:08:51.573-08:002017-01-10T18:08:51.573-08:00Thanks, Andrew. You have validated our overkill on...Thanks, Andrew. You have validated our overkill on errors:<br /><br />1. Report them so that you have a chance to fix them before they cause problems.<br />2. Back them up with Error Markers, so that they are visible when somebody is trouble-shooting or fault-finding or simply engineering.<br /><br />We focus on errors as well as navigation simply because no competent engineer could stomach the errors that Composer and WinCAD do not detect. <br />Geoff Michaels, P. Eng.https://www.blogger.com/profile/08106776449998803700noreply@blogger.comtag:blogger.com,1999:blog-4922736527622150204.post-56843902702584586122017-01-10T17:08:09.148-08:002017-01-10T17:08:09.148-08:00DBDOC is the only tool I have that provides a back...DBDOC is the only tool I have that provides a back stop for any errors that I introduce. I recently added a new input block for an off-module value. It went in okay. Two days later I was phoned and sent details of a value that was no longer changing and was confusing the operators. The process engineer's go to tool was DBDOC. An error marker was noted on the CAD sheet and all of this info sent to me. A frozen exception report had been created by my work due to a second import of the same off-module value. An easy fix once found but this should have been picked up by the native ABB/Bailey tools we have. DBDOC to the rescue yet again. Thanks.Anonymoushttps://www.blogger.com/profile/09534332193155163423noreply@blogger.com