# Create Components

Components are used for identifying systems that require regular maintenance. Components are organized in a hierarchical structure starting on the top level with the ship/site, going down to the smallest sub-component requiring individual maintenance planning. Within the component structure you can define components that have a dedicated running hours counter that will be made available later on the in the Counter List for central updating running hours. For sub-components you can decide if they use their own running hour counter or if they will inherit running hour information from the parent component.

Components will be created in the Components view by clicking the New button.

In the component editor - beside details like maker/supplier names, serial numbers and other essential details - you can use the Maintenance Jobs tab for defining the maintenance jobs to be planned for the selected component.

The system offers different types of maintenance jobs:


Recurring Job (Interval)	Maintenance jobs that need to be executed and repeated in a given interval
Single Job	Single jobs define a job that needs to be done only once in the lifetime of a component. Usually this will be used for maintenance jobs that need to be executed during the first months and years of the lifetime of a component.
Sequence	Sequences define a list of different maintenance jobs that need to be executed in a given sequence.
Manually Planned	Unlike jobs scheduling via pre-defined intervals, manually planned jobs due dates will be set manually. When reporting a manually planned job, the system will also ask for the next due date.

Those types will be offered after clicking the New button.

A maintenance job is defined with the following procedure:

Job Title: Select a job code from the job code list by clicking the "..." button.
Assign who will be responsible for executing the job.
Decide if the job depends on the current running hour counter or if you want to use calendar based planning.
Define the interval for the job execution.
Optional: you may also enter the date of last execution if the maintenance job was already executed and reported in another system.

# On Demand Jobs

While creating a maintenance job you have also the option to define a job as an on demand job. On demand jobs can be used for describing a maintenance task via job code and job description and provide this information whenever such a task needs to be executed.

On demand jobs will also be used for being triggered through external sources. If the system is interfaced with a condition monitoring system, certain alarms raised in the condition monitoring system will be used for putting an on demand job on the job schedules list with a given due date depending on the severity of the alarm. Another option is to have on demand jobs triggered via a job sequence.

# Job Sequences

Job sequences will be used for planning certain maintenance tasks that need to be executed in a certain sequence. Job sequences will be created by defining the number of sequence steps and assigning a pre-defined maintenance task to each step. For each step it can also defined after what period (calender days or counter depending) the job sequence step becomes due. Each step in the sequence can have a different interval and interval type (calender depending jobs and counter depending jobs can be mixed).

As a job sequence can be created also for already running equipment it is always necessary to define the next sequence step to be executed. Per default this setting is set to 0 - preventing the automatic planning of related maintenance tasks. For new equipment set the initial step to 1.