Cross-redundancy checks

In this case, the integrity of each file is verified by comparing the cross-redundancy check (CRC) of the installed file with the checksum of the original file recorded on the installation master. Modified or corrupt files have different checksums and are, thus, detected by the verification program. Verification reports include a list of missing, changed, and identical files. 

In view of the conflict between the reliability and the cost of adding more hardware, it is sensible to attempt to use the dissimilar measured values together to cross check each other, rather than replicating each hardware individually. This is the concept of analytical i.e. functional) redundancy which uses redundant analytical (or functional) relationships between various measured variables of the monitored process e.g., inputs/outputs, out-puts/outputs and inputs/inputs). Figure 3 illustrates the hardware and analytical redundancy concepts. 

With few exceptions, each chapter is designed to be a stand-alone work. Inherent in this design is a body of information that is reproduced and redundant throughout each chapter. Each chapter is comprehensive in a diagnostic sense, which should limit the need to do extensive cross-checking to other chapters. Each section is punctuated by key diagnostic points that summarize the section and that serve as a rapid summary reference for the most important points in that section. 

Redundancy—Redundancy should be planned according to operational requirements. On the one hand, some level of redundancy of information is required so operators can cross check displayed information however, on the other hand, too much redundant information can increase operator workload through distraction. 

Is maintenance of diverse/redundant channels staggered at such an interval as to ensure that any proof tests and cross-checks operate satisfaetorily between the maintenance ... 

---