Registering Internal Jobs

Overview

The following types of jobs are managed by CCLAS:

Registered jobs, including production, internal and proposal jobs
Template jobs
Schedule jobs and draft jobs raised from schedule jobs.
Laboratory batch jobs which comprise samples from multiple registered jobs for a suite of tests.

An internal job is a request for analysis for one or more samples taken from internal work, that is, within the context of the laboratory, and is used for internal analysis and trailing of new methods and schemes.

Internal jobs can be used for any number of reasons but are regarded as non-paying jobs (they cannot be invoiced), but in all other ways can be processed and reported.

Internal jobs are created and primarily used by a laboratory to test setup of schemes, invoices and reports before these are used in production jobs.

Internal jobs are used also to perform analysis for another laboratory within the same organisation, where the source laboratory is invoiced upon job completion.

Internal jobs are used also to check the performance of the laboratory or in the training of new staff. When the laboratory wants to perform calibrations on instruments, or use a job to track internal work, an internal job is used so that work-in-progress and estimate job costs are not calculated.

Job Scope

Internal jobs are scoped by laboratory.

Process

These steps outline the registration of an internal job:

Create the internal job in CCLAS 6.
Update the job with the header details, biofields, samples and test details.
Print job paperwork.

The CCREGN—Job application is used to create and maintain internal jobs.

Note: Security options can be set up to permit the creation of specific job types within an organisation or laboratory.

Creating an Internal Job

Upon job creation, select the Job Type is as Internal.

Jobs have two primary identifiers: Code and Job Name.

Each job Code and Job Name must be unique within the organisation for org-scope jobs, and unique within the laboratory for lab-scope jobs.
Either select a Job Name Syntax Code to generate the job name or enter the Job Name.
The JOB_NAME_ONLY_FROM_SYNTAX application preference is used to force syntax use.
The DEFAULT_PRODUCTION_JOB_NAME_SYNTAX application preference is used to set a default Job Name Syntax Code for a production job.

Refer to:

Use a Registration Mode of New Job by Client, in which case a Client Code must be entered with an optional Project Code and Contact Code

Refer to Maintaining Clients.

Upon Creating Internal Jobs

Upon internal job creation:

The job's Job Code is generated.
The job's Job Name is generated, if required.
The system validates the Job Code and Job Name (regardless of whether it was entered by the user or generated from syntax), using the CODEVALIDATION_JOBCODE and CODEVALIDATION_JOBNAME application preferences.
The event is audited. Refer to Reviewing Operational Data Audits.
The job is opened for update. Refer to Maintaining Jobs.

Job Locks

Cost Centre

The following processes are used so that the system can assign a default cost centre based on a production job's client.

Maintaining Cost Centres—To create the cost centres.
Maintaining Clients—To create the clients and link them to cost centres, and to create client projects and link them to cost centres.
Conditions for Defaulting Job Cost Centre

Priority and Dates

Conditions for Defaulting Job Priority

The following processes are used to set a default value for a job's priority, set the working days of the week for the laboratory, and maintain holidays.

Set the DEFAULT_PRIORITY and WORKING_DAYS_OF_WEEK application preferences.
Maintaining Clients—To configure a priority for a client or client project.
Maintaining Holidays—To configure times when the laboratory does not work. This adds extra time to due dates.

If the job has a project defined, and priority is defined on the project, then the job's priority is set from there. Otherwise, if priority is defined on the client, then the job's priority is set from there. Otherwise if a default priority is set up in the DEFAULT_PRIORITY application preference, then the job's priority is set from there.

A job's priority, the defined working days of the week, and holidays, are used to determine required dates for a production job.

The AUTO_RECEIVE_JOBS application preference configures whether a job's Received Date and Received By are set automatically, or left empty for manual update.

Workflow Status

Conditions for Defaulting Job Workflow Status

Job Biofields

Conditions for Defaulting Biofields from Client Group
Conditions for Defaulting Biofields from Cost Centre
A biofield can also be flagged for automatic registration on a job.

The following processes are used so that the system can assign job and sample biofields to production jobs.

Maintaining Biofields—To create the master biofields.
Maintaining Biofield Groups—To create the master biofield groups.
Set the JOB_REG_SAMPLE_LIST_BIOFIELDS application preference.
Maintaining Client Groups—To create client groups and link them to biofield groups.
Maintaining Cost Centres—To link cost centres to biofield groups.

Job Stakeholders and Report Templates

When a job is linked to a client, the client can bring in default report templates.