CCREGNSCHM—Job Scheme Detail

Processes associated with this form
Screen flows
  • Submit—Validate and save the changes.
  • Refresh—Reload the original data. Any changes made since the last submit are lost.
Header

  • Job Name

    The name of the job. Display only.

  • Scheme Code

    The code of the scheme on the job. Display only.

  • Scheme Version Number

    The version number of the scheme on the job.

  • Workflow Status

    The status of the job scheme indicating the stage it is at in its life-cycle. Display only. This can be:

    • Not Started

    • Started

    • Analysed

    • Released

    • Completed.

  • Composite QC Status

    The composite QC status of the job scheme indicating the status of the underlying analytical results. Display only.

  • Composite Specification Status

    The composite specification status of the job scheme indicating the status of the underlying analytical results against all sample specifications. Display only.

Primary Details Tab

The primary details of the job scheme.

  • Report Name

    The reportable name of the job scheme. Defaults to the scheme version's Report Name, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.

  • Report Sequence

    No functional use in CCLAS. Represents the sequence of the job scheme in a certificate report, with respect to other job schemes, to override registered scheme sequence, from the enabled-scope scheme when an org-scheme scheme is registered on a lab-scope sample. For use by SQL scripts when using DSC reporting.

  • Report Description

    The reportable description of the job scheme. Defaults to the scheme version's Report Description, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.

  • Include in Job QC

    Indicates whether the job scheme is included in an update or overwrite QC process. Defaults to the inverse of the scheme version's Batch Across Jobs flag, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample. Note that a sample scheme's Include in Job QC check box always defaults to checked.

    For a sample to be included in an update QC process on a job scheme, the job scheme's Included in Job QC must be selected and the sample scheme's Include in Job QC must be selected. Note that a sample scheme's Include in Job QC check box is cleared by the system once the sample scheme is included in a update QC process.

    For a sample to be included in an overwrite QC process on a job scheme, the job scheme's Included in Job QC must be selected and the job's Workflow Status must be Registered or Not Started. In this process, existing QC samples are deleted, and the sample scheme's Include in Job QC check boxes are all re-checked, then the same process as update QC runs.

  • Auto-validate

    No functional use in core CCLAS. Represents a default for the same flag for scheme version analytes. The flag on the scheme version analyte is used by the cascade engine.

  • Laboratory Code

    The code of the laboratory subcontracted to prepare/analyse the sample schemes. A subcontract laboratory may be selected from the drop-down list that contains active laboratories that are members of the laboratory group defined by the SUBCONTRACT_LABS application preference, excluding the current laboratory. Click the field hyperlink to display the CCLBRT—Search Laboratory screen, select the appropriate value and click Select and Return to populate the field with the selected value. Note, however, that the selected value is validated against the laboratories contained in the drop-down list on submit. Defaults to the scheme version's Default Sub Contract Lab Code, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.

  • Price Code

    The price code that links a costed or priced scheme to a price schedule, where the scheme's Price Type is Scheme-Based, Sample-Based or Unit-Based. That is, they are the master codes for invoiced or costed entities. A price code may be selected from the drop-down list that contains active price codes in scope with a Price Type of Scheme-Based, Sample-Based or Unit-Based, as configured in the CCPRCCODE—Price Code application. Click the field hyperlink to display the CCPRCCODE—Search Price Code screen, select the appropriate value and click Select and Return to populate the field with the selected value. Defaults to the scheme's Price Code, from the enabled-scope scheme when an org-scope scheme is registered on a lab-scope sample.

  • Fixed Base Price

    The optional fixed base price for the job scheme, thereby overriding any price determined from a price book when invoiced. Only applicable where the scheme's Price Type is Scheme-Based, Sample-Based or Unit-Based. Entered as a real number that can be a portion of the currency, for example, $10.636.

    If a fixed price is added to any job scheme or job scheme analyte, then each related sample scheme's Package Price Code and sample scheme analyte's Package Price Code is cleared.

  • Fixed Block Price

    The optional fixed block price for the job scheme, thereby overriding any price determined from a price book when invoiced. Only applicable where the scheme's Price Type is Scheme-Based, Sample-Based or Unit-Based. Entered as a real number that can be a portion of the currency, for example, $10.636.

    If a fixed price is added to any job scheme or job scheme analyte, then each related sample scheme's Package Price Code and sample scheme analyte's Package Price Code is cleared.

  • Number of units

    The number of units for the job scheme, used to determine the job scheme pricing, for example, number of hours a particular task took, or number of kilometres travelled. Only applicable where the scheme's Price Type is Unit-Based.

Linked Schemes Tab

A linked scheme is where the analysis is performed on the same racks of samples.

Linked job schemes share the same samples, including QC samples and rack layout, and limit which job scheme can be opened to enter weights and volumes:

  • When appending or overwriting QC samples for a job, linked job schemes are processed such that the QC masks used are from the first linked job scheme to determine the QC samples and rack layout, which is then applied to the linked job schemes.

  • QC sample additions or deletions are synchronised when modifying QC samples in a job scheme.

  • Only the first linked job scheme is allowed to be opened after searching for workbooks with weight/volume mode.

  • Job scheme links default to the linked scheme relationships contained within the master scheme, when both schemes are registered on the job.

  • When an org-scope scheme is registered on a lab-scope job, the master scheme from where linked scheme relationships are determined is the enabled-scope scheme.

  • The first linked job scheme is determined by the 'from' and 'to' linked scheme relationships between the job schemes, such that, the 'from' job scheme is deemed the first linked job scheme, regardless of where it is registered in the job. Where more than one scheme link relationship is in play, that is, multiple 'from' linked job schemes exist in the job, then the first (by job scheme registration sequence) is used as the first linked job scheme. Examples: Where a job has schemes A, B and C registered in that sequence, and linked job schemes A-->C and B-->C exist, then A is the primary 'from' linked job scheme as it is registered before B. Where a job has schemes C, B and A registered in that sequence, and linked job schemes A-->C and B-->C exist, then B is the primary 'from' linked job scheme as it is registered before A.

A job's linked scheme relationships default from the scheme's linked scheme relationships, where the schemes are registered on the job., from the org-scope scheme when an org-scope scheme is registered on a lab-scope sample.

  • Linked From

    The parent scheme within the linked scheme relationship.

  • Linked To

    The child scheme within the linked scheme relationship.

  • Name

    The name of the scheme associated with the linking.

Notes Tab

Notes associated with the job scheme.

Report Header/Footer Tab

The content of the report header and footer for the job scheme.

Status Tab

The current status of the job scheme.

  • Workflow Status

    The status of the job scheme indicating the stage it is at in its life-cycle. Display only. This can be:

    • Not Started

    • Started

    • Analysed

    • Released

    • Completed.

  • Composite QC Status

    The composite QC status of the job scheme indicating the status of the underlying analytical results. Display only. This can be:

    • Not Tested

    • Not Required

    • Pass

    • Failure.

  • Composite Specification Status

    The composite specification status of the job scheme indicating the status of the underlying analytical results against all sample specifications. Display only. This can be:

    • Not Tested

    • Not Required

    • Pass

    • Failure.

  • Required On

    The date-time at which the job scheme's results must be reported.

  • Possible On

    Although this should be the possible date-time at which the job scheme's results can be reported, based on the longest duration of job scheme analysis, currently this is the same as Required On. Possible On can be updated if the date-time provided is valid and the date-time is later than the Received On (or Received On is not defined), otherwise an error message displays upon submit. If Required On is changed, Possible On changes to match it.

  • # Samples in Job Scheme

    The number of samples, including QC samples, in the job scheme.

  • # Unknowns in Job Scheme

    The number of unknown samples in the job scheme.

  • Last Activated On

    No functional use in core CCLAS.

  • Activated By

    No functional use in core CCLAS.

  • Started On

    The date-time at which the job scheme was started, that is, when the job scheme's Workflow Status became Started.

  • Analysed On

    The date-time at which the job scheme was analysed or completed preparation, that is when the job scheme's Workflow Status became Analysed.

  • Released On

    The date-time at which the job scheme was released, that is, when the job scheme's Workflow Status became Released.

  • Validated On

    No functional use in core CCLAS.

    Tip: Personalise the form to display the job scheme's Completed On instead, which is the date-time at which the job scheme was completed, that is, when the job scheme's Workflow Status became Completed.

  • Validated By

    No functional use in core CCLAS.

    Tip: Personalise the form to display the job scheme's Completed By instead, which is the code of the user who completed the job scheme.