From Ascgroup
Attachment function is designed to allow maximum freedom for users (with appropriate privileges) to upload, overwrite and remove supporting documentation into the system. This report assist in the tracking and administration of the system to detect new uploads and changes that have taken place. Backups are maintained of the attachments (as scheduled by the System/database Administrator so restoration of unwanted changes can be made by exception. This level of passive oversight of the attachment capability is designed to facilitate the maximum use of the complete documentation of all findings recorded in SeeSOR.
Attachments provides the list and history of all attachments that are currently or have been previously used in SeeSOR. This report provides the line item and the function to which the report is/was attached. The report also shows the path and the user, date and actions that have been performed.
Current Effort and Fixed Effort reports use the “Area of Expertise” designation and “Time to Inspect” entries in the QA Plan along with the current frequency (the “current” frequency is automatically adjusted based on the scoring criteria settings and the High/Low settings of the QA Plan). Knowing the frequency and time to inspect the requirement allows SeeSOR to calculate the total effort to perform scheduled inspections. Adding analysis of the “Area of Expertise” allows SeeSOR to project the level of effort to perform inspections by skill of the inspectors.
Comparisons by skill can allow for the optimal manpower planning or can perform the basis for making decisions on where to direct the limited resources that are available for inspection at any given time.
Fixed Effort can be used to augment the Inspection Schedule by allow inspectors of a particular “Area of Expertise” to schedule to accommodate a fixed time in advance. This is necessary since fixed inspections are by nature restrictive on when they can be performed.
Monitoring Resource Requirements provides a summary of the range of the inspection requirement. The report provides the level of resources required based on the various scenarios based on the assumption that all inspections are at the Normal frequency, Increased frequency (poorly performing), or Decreased frequency (highly performing). This report can show the tradeoff associated with improving performance to reduce the cost if inspection.
The SeeSOR Transaction Log shows history of the changes to the database with regards to SOR (Requirements) modifications, SOR Deletions, Inspection Results Deletions, and Inspection Result Modifications. All of these actions offer a potential for the unintentional or erroneous loss or revision of data. The use of Transactional Logging is a user decision but best IT practice dictates that Transaction Logging should always be on.
The Transaction Log of the SOR Modifications and SOR Deletions represents and documents the full history of the Contract.