In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |   qad.com



  •     QAD Glossary

  • Planning an Auditing System
    Every environment has unique record-keeping requirements. Before you begin setting up the auditing functions, consider creating:
    A detailed data retention plan including details such as:
    A detailed list of the types of information you need to audit
    A detailed list of the database tables that contain information you need to audit
    A system resource and hardware plan with disk space and system resource availability
    A maintenance schedule for planning when new audit databases are created and brought online
    An information retention plan detailing how long auditing information is kept online for reporting purposes
    An archive plan detailing when audit databases are taken offline and where they are stored
    Consider the following points:
    The number of database tables you maintain information for and the number of audited transactions occurring on your system are directly related to the system resource usage and availability. These factors directly affect maintenance requirements and administrative overhead.
    If you plan to use Electronic Signatures functionality, the frequency with which you will archive signature records can have a significant impact on whether you set up signature-specific databases or simply use the same databases for both audit trails and signature archives.
    The information that is important to you may reside across multiple database tables. Additional research is required to find all the database tables containing this information.
    Depending on which modules you are licensed to use, some tables in the database are not used and can be disregarded.
    For research purposes, you should be familiar with the Progress Database Dictionary and the Entity Diagrams and Database Definitions reference guides.
    Some environments, such as in the medical industry, have very specific and stringent electronic information retention regulations; make sure you are familiar with any regulations or standards in your specific industry or region.
    For additional security, you may want to store offline audit databases on read-only media such as CD-ROMs.