From Ascgroup
Contents |
Set Contract Preferences
Contract Preferences is accessed through the "Administration Tasks" functions by authorized administrators by selecting "Contract Preferences" (see below). The Contract Preferences set here are applied to the contract/project in which you are currently working. These settings will not apply to any other contract/project and must be separately configured for each contract/project.
"General" Tab
- Input Contract Name that will appear on the "Select Contract" (top right menu of the SeeSOR.NET screen) list and on all reports
- Input the Attachment file location path to where all attachments will be stored. The location should be on a server that is accessible to all users, files are uploaded and downloaded through the SeeSOR.NET interface.
NOTE: Attachments are discussed in detail elsewhere in this User's Guide. Attachments can be any type of file that is supported by the user's computer (including photos, videos, spreadsheets, PDF or even URLs or executable programs).
"QA Plan" Tab
- Select the User Group(s) who's inspections will trigger the reschedule of the next inspection. User Group(s) not selected will not effect the schedule and who's inspections will not remove a requirement from "Past Due" lists.
- Input the number of days after a Fixed Inspection date has been exceed without being inspected before the requirement is removed from the missed inspection or "Past Due" list. Once the number of days is exceeded the requirement will be rescheduled for the next time the fixed date occurs.
NOTE: Fixed dates are used for single event inspection requirements (i.e., inspect the Christmas Meal service), or services that are not performed on an on-going basis.
- Select if the QA Plan Checklist are to be sorted in order of weight (relative importance). Otherwise, the checklist will appear on screen and when printed in the order they were entered when the QA Plan was created.
"Inspection History" Tab
- Select the score (0 - 10) at or above which performance is considered above satisfactory or the range to be considered as "Good". All inspections in the Inspection Results function at or above the selected value will be highlighted in Green.
- Select the score (0 - 10) below which the performance would be considered as unsatisfactory or the range to be considered as "Poor". All inspections in the Inspection Results function below the selected value will be highlighted in Red.
NOTE (1): Remaining inspections in the Inspection Results function will be highlighted in Yellow.
NOTE (2): The baseline score that represents "acceptable" or "meets specification" must be determined before the scoring criteria of checklist in the QA Plan can be written. The value that defines "Good" should be at or above this "acceptable" value and the value that defines unsatisfactory should be below this "acceptable" value.
NOTE (3): It is generally that the "acceptable" rating be 5, this then allows five units to measure exceeds "acceptable" and five units to measure below "acceptable". It this recommendation were accepted an example of "Good" value might be 6 or 7 and a "Poor" value would be 4 or 3.
"Transaction Logging" Tab
- Select all the functions to which Transaction Logging should be applied.
It is highly recommended that all Transaction Logging options are selected as this is considered Information Assurance best practice to maintain a history of all changes to data. In cases where the SOR is contractually binding, only users with contracting authority should be authorized to change the Requirements and there should be the properly executed requisite documentation.
Return to SeeSOR.NET
Next Topic: Dashboard Overview