Maintaining Schedule 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.

Whilst schedule jobs similar to template jobs, they are used to schedule automatic production or internal job registration using the system scheduler and batch processor, and can also be used to interactively create draft jobs which are then enacted into registered production or internal jobs.

A sample within a schedule job is known as a stream sample, often because they come from one particular stream within a production process.

Schedule jobs are scoped by laboratory as they contain details about samples collected during a specific production process.

Process

These steps outline the registration of a schedule job and its stream samples:

  • Create the schedule job in CCLAS 6.

  • Update the job with the header details, biofields, samples and test details. Any sample group remains in unexpanded form.

  • Add samples and tests to the template job. Samples created within a template job are deemed template samples.

  • Specify the execution schedule.

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

Creating a Schedule Job

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

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_SCHEDULE_JOB_NAME_SYNTAX application preference is used to set a default syntax for the Job Name Syntax Code for a schedule 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. It may be advantageous to create a dummy client for schedule jobs, for example, INTERNAL_CLIENT or DEFAULT_CLIENT, or the schedule job could be set up with a specific client. The client may contain project attributes such as Project Code that allow for the grouping of related schedule jobs.

Refer to Maintaining Clients.

Since the schedule job's details are used as defaults for any destination registered job when a registered job is created from the schedule job, the choice of adding information at this point depends upon whether it is a fixed value or needs to be edited for each target registered job. For example, Priority may always be 7 days, or Authorisation Group could be the same for all target registered jobs in the laboratory.

Upon Creating Schedule Jobs

Upon schedule job creation:

Create a schedule job

Configuring Automatic Addition of QC Samples in Target Jobs

Automatic running of an update QC process on a target job can be configured in schedule job.

When a target job is created by the system running a CCBSJGEN batch job after a schedule is executed in the system scheduler for sample registration from a schedule job, or a draft job is created from a schedule job, or a production job is created by enacting a draft job, then the draft or production job inherits the source job's Auto Append QC setting. After a production or internal job is created from a schedule job, or when additional samples are added to an existing production job from a schedule job, if this setting is checked, then an update QC process is run automatically.

If this process is run, it acts upon all registered samples including any registered QC samples (those that have a QC Source of 1), that is, those registered along with the unknown samples or those added by duplicating unknown samples (where the schedule or draft sample's No. of Duplicates > 0 or sample scheme's No. of Replicates > 0).

Configure automatic running of an update QC process for a target job of a schedule job

Configuring Automatic Generation of Paperwork

Automatic generation of paperwork and labels for a target job can be configured in the schedule job.

When a target job is created by the system executing a CCBSJGEN batch job after a schedule is executed in the system scheduler for sample registration from a schedule job, or a draft job is created from a schedule job, or a production job is created by enacting a draft job, then the draft or target registered job inherits the source job's Is Auto Paperwork setting. After a production or internal job is created from a schedule job, or when additional samples are added to an existing production job from a schedule job, if this setting is checked, then job paperwork and labels are generated automatically. This process involves the following steps:

  • If the related paperwork or labels report requests exists, then all reports are cleared from it. (This does not include the clearing of previously generated reports.) If the related paperwork or labels report request does not exist, then it is created.
  • For each paperwork and labels in the production or internal job where Reportable is selected, then the paperwork and labels is added as a report to the appropriate report request (the related report request of Type Paperwork, or the related report request of Type Labels for the job), and each report request sample's Reportable is set to the corresponding sample's Generate Paperwork setting.
  • The reports are generated for the related paperwork and labels report requests.

Configure automatic generation of paperwork and labels for a target job of a schedule job

Maintaining Scheduled Execution Times

The key thing to specify with a schedule job is the actual schedule.

A valid schedule comprises the Scheduled Months and Scheduled Times, and either the Scheduled Weeks and Scheduled Days, or the Scheduled Days of Month.

Update schedule details for a schedule job

Scheduled future events for a schedule job can be viewed.

Upon executing the schedule job:

  • If the schedule job is currently unscheduled but no future events exist, then no CCBSJGEN scheduled tasks are created in the MSESCH—Schedule application.

  • If the schedule job is currently scheduled and future events are created or made active, then the system checks if the new future events are within the 10 already created CCBSJGEN scheduled tasks in the MSESCH—Schedule application, and if they are, then creates new schedule jobs for the new future events and deletes any schedule jobs beyond those first 10.

  • If the schedule job is currently scheduled and future events are deleted or made inactive, then the system checks if the future events that are deleted or made inactive are within the 10 already created CCBSJGEN scheduled tasks in the MSESCH—Schedule application, and if they are, then deletes those schedule jobs.

    Refer to Execute a Schedule in the System Scheduler for Sample Registration from a Schedule Job and Terminate a Schedule in the System Batch Queue for Sample Registration from a Schedule Job.

View and manage scheduled future events for a schedule job

What to do Next

Refer to Creating Stream Samples within a Schedule Job