## Options

!!!INFO The availability of some of the options depends on activated license options.
!!!

Job Code
:   Assing a unique job code

Job Name
:   Name of job to be used in the system

Maker (optional)
:   Identifies the component maker who created the job description

Pre-Warning (days) (optional)
:   Number of days before a planned maintenance job should go in the warning state. This can be used if the execution of a maintenance job requires preparation (e.g. ordering spare parts)
Default is a pre-warning of 14 days.

Risk Assessment required before execution
:   This option identifies maintenance job that required the execution of a risk assessment before the actual execution of the maintenance job

Check for mandatory report attachments
:   If the reporting of an executed maintenance jobs requires the attachment of a document (e.g. form with measurement values) this option can be activated for checking if a file has been attached to the report. Of course it cannot be checked if the correct for was attached. The job description should provide details about the information to be added to the report.

File/Form
:   This can be used for attaching a file to the job code detail. This can be a job description in any supported file format or a form to be used for reporting measurement value in the maintenance report.

Approval/Check required after execution (optional)
:   This option can be activated if a maintenance job requires an additional approval after the maintenance report has been created. It can also be used if follow-up tasks to a maintenance job need to be tracked (e.g. receiving of oil sample reports). Via `max. days for check/approval` a due date can be defined.

Job Description
:   Entering the job description as free text is one of the available options for providing a detailed description of the maintenance job

Document References
:   The document references can be used for linking to document available in the [Documents](/HSSEQ/Document-Management/) module.

## Job Description

The system offers 3 different options for managing job descriptions.

1. Attaching a file to the job code.
1. Writing the job description as a formatted text.
1. Linking to documents in the [Documents](/HSSEQ/Document-Management/) module.

### Attaching a File

The `File/Form` option can be used for directly attaching a file to the job code definition. This file can contain a job description or a form to be used during the creation of the maintenance report.

Only one file can be attached.

### Writing a Job Description

Instead of attaching a file, the job description can also be added as a free text.

### Linking to Documents in Documents Module

Instead of writing the job description or attaching a file to the job definition, a job code definition can also contain links to documents in the [Documents](/hsseq/Document-Management/) module. Before a document can be linked to a job code, it must be first added to the Documents module.

!!!IMPORTANT
Only the usage of document references allows the fleet-wide management of job descriptions. Updates to related documents will be automatically made available to all vessels/sites that have a reference to the affected document.

Using direct file attachments or entering a free text as job description instead requires an update of every single vessel/site where an update of a job description needs to be applied.
!!!

*[PO]: Purchase Order  
*[AZA]: local folder
*[(PO]: Purchase Order  
*[RQ]: Requisition  
*[(RQ]: Requisition  
*[RfQ]: Request for Quotation  
*[(RfQ]: Request for Quotation  
*[SO]: Service Order  
*[(SO]: Service Order  
*[SQ]: Service Requisition  
*[(SQ]: Service Requisition  
*[SRfQ]: Service Request for Quotation  
*[OoB]: Open on Board  
*[(OoB]: Open on Board 
*[ART]: Average Running Time (operation hours per day) 
*[MC]: Master Contract
*[ADS]: Advantage Database Server (database engine used in previous versions of the ZeeBORN software)
*[.replic]: file extension for replication files (aka data transfer files)