The owner of the system should provide clear requirements of what the system should do and should define what constitutes “maintainability” of the system. This places a burden on the owner of the system to consider the full life-cycle of the system. <\/p>\n
1. You need good design documentation. <\/p>\n
2. All source code should be well-documented. <\/p>\n
3. Coders should be trained on the techniques used and mentored, <\/p>\n
4. The use of “templates” helps ensure that coders and maintenance alike are familiar with routine functions. <\/p>\n
5. The HMI should provide clear indication of faults and interlocks. <\/p>\n
6. The HMI should provide clear indication of equipment statuses. <\/p>\n
7. Any code that is hidden must “work as advertised”. This means that it must be completely and unambiguously documented for all inputs, outputs, statuses, and configurations. It must be thoroughly tested and warranted by the vendor, <\/p>\n
8. All code should be well-tested. (I have found that the first line of defense is to simply read the code!) <\/p>\n
Post-Startup
\n1. The owner should have a change-control procedure to manage modifications. <\/p>\n
2. All users and maintenance support personnel should have adequate training. Training needs to be periodically refreshed as it can become stale through lack of use.<\/p>\n","protected":false},"excerpt":{"rendered":"
The owner of the system should provide clear requirements of what the system should do and should define what constitutes “maintainability” of the system. This places a burden on the owner of the system to consider the full life-cycle of the system. <\/p>\n
1. You need good design documentation. <\/p>\n
2. All source code should be well-documented. <\/p>\n
3. Coders should be trained on the techniques used and mentored, <\/p>\n
4. The use of “templates” helps ensure that coders and maintenance alike are familiar with routine functions. <\/p>\n
5. The HMI should provide clear indication of faults and interlocks. <\/p>\n
6. The HMI should provide clear indication of equipment statuses. <\/p>\n
7. Any code that is hidden must “work as advertised”. This means that it must be completely and unambiguously documented for all inputs, outputs, statuses, and configurations. It must be thoroughly tested and warranted by the vendor, <\/p>\n
8. All code should be well-tested. (I have found that the first line of defense is to simply read the code!) <\/p>\n
Post-Startup
\n1. The owner should have a change-control procedure to manage modifications. <\/p>\n
2. All users and maintenance support personnel should have adequate training. Training needs to be periodically refreshed as it can become stale through lack of use.<\/p>\n","protected":false},"author":0,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[67],"tags":[],"class_list":["post-13976","post","type-post","status-publish","format-standard","hentry","category-iacdrive_blog"],"_links":{"self":[{"href":"http:\/\/iacdrive.com\/index.php?rest_route=\/wp\/v2\/posts\/13976","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/iacdrive.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/iacdrive.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"replies":[{"embeddable":true,"href":"http:\/\/iacdrive.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=13976"}],"version-history":[{"count":0,"href":"http:\/\/iacdrive.com\/index.php?rest_route=\/wp\/v2\/posts\/13976\/revisions"}],"wp:attachment":[{"href":"http:\/\/iacdrive.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=13976"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/iacdrive.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=13976"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/iacdrive.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=13976"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}