Purpose
As for SRs, clients may request visual inspection requests (IR) remotely
and may compile the list of areas to be inspected themselves. Alternatively
labclerks may do it for them
They do so using an existing inspection template (IT) or build
it from scratch
On the date of the survey, the labtechnician prints the IR, and
uses it on-site – she captures any data required, ie visual
scores, onto the printed IR. The latter functionality can in the
future be automated thru the use of PDAs
Back at the lab, inspection results are captured into the system.
Like SRs, IRs go through verification and publication status changes
executed by the labmanager
Visual inspection statuses
Due, Inspected, To be verified, Verified, Published
Use case
Role players: client, labclerk, labtechnician, labmanager
the role player navigates to the client’s ‘Visual
inspections’ page
or is led to
she clicks [add new]
the same client status checks and workflows are carried out as specified
for ARs
SR header properties are put together exactly like for ARs, see
paragraph CC results and invoicing
of others and the corresponding page in the wire frame model
any existing SR can be saved as survey template (ST) for future
use
for the SR to be created from an existing ST, the plant for the
survey must be provided since the template contains the survey
surfaces areas per site
created from and IT, the IR will have many fields completed,
but the role player may edit, add or delete some of the information
she saves the IR
like for ARs a notification of the pending inspection is posted
to lab staff: clerks, technicians and managers
the role player to execute the request, prints it and sets off
to the plant/farm
she captures data available on-site firstly on paper
and when back at the lab, into the LIMS
the system calculates averages, ratings and interpretations
Role players enter any ad hoc remarks as required
she submits the IR for verification
the labmanager receives a notification to verify or retract the
IR
the labmanager retracts, or verifies and publishes the results
once verified, clients see results data
in publication, the results are e-mailed/faxed to the requestor
and her recipient list
the publication includes:
inspection ID
client address & contact details
cc list
inspected by (automatically logged)
order no
the responsible manager
the responsible microbiologist (automatically logged)
date requested (automatically logged)
date/time inspection started
date/time inspection completed
date/time published (automatically logged)
calculates scores
interpretation tables
blobs like: visual assessment score ratings, hygiene efficiency
rating
remarks
Prices and Price summary, incl.
travel costs
inspection charges
Purpose
Visual inspections and assessments at the same client are often
only slight alterations of a standard document. To automate this,
it is best to keep these inspection templates in the system and
allow users to modify them at runtime
Similar to survey templates, inspection templates are also saved
in the system per client and plant /farm
Use Case – Creating / Editing an inspection template
Role players : labclerk, labtechnician, labmanager, client
Much like for Surfaces:
the role player selects the areas to be inspected from a list
maintained for the client
on her pages
she selects an inspection interpretation to be associated
with the inspection
she selects any text insertions to be associated with the inspection
|
