From Ascgroup

If a Service Provider does an assessment in SeeSOR, it deletes the requirement for the Service Recipient to complete that same assessment. And likewise if the Service Recipient does an assessment, it deletes the requirement for the Service Provider to perform the same assessment. Why does SeeSOR make adjustments which prevent one of the assessments from being completed for the scheduled inspection period?

SeeSOR is designed to optimize the use of resources. The general concept is that if any inspector performs an inspection at a site (using the highly objective scoring criteria of the QA Checklist in SeeSOR) then it is theoretically unnecessary to have anyone else perform the same (objective) inspection. That said, any inspector can perform any inspection without regard of the schedule. So, if desired, the Service Receiver can perform another inspection even though the item has been deleted from the Inspection Schedule because the Service Provider had already performed the inspection. The next scheduled date will be generated based on whoever performed the last inspection.

There is an exception to the above. SeeSOR does allow designating which group's inspections will affect the scheduling. In the contract's Administration Task tab, Contract Preferences, QA Plan tab (http://support.ascginc.com/Wiki/usersguide/ContractPreferences#.22QA_Plan.22_Tab) you can select which group's inspections will impact the scheduling. By un-checking the Service Provider the schedule will not be affected by inspections of any inspector in the Service Provider group. However this would mean none of the inspections performed by Service Provider's would affect the Inspection Schedule. It might be possible for the Service Recipients to perform their own schedule of inspections without using the SeeSOR Inspection Schedule. If that is possible, then the Service Provider would be the only group selected.

There is also another approach that will preserve the scheduling if the separate scheduling for Service Providers and Service Recipients is absolutely required. A separate list of sites can be created, one for Service Providers (SP) and one for Service Recipients (SR). For example, "NAS Fallon" could have a duplicate site called "SR-NAS Fallon." Service Recipients (SR's) would record all inspections against SR-NAS Fallon and Service Providers (SP's) would record all inspections against SP-NAS Fallon.