====Setting Up Maintenance====

The ARDI maintenance system uses existing ARDI properties to create the information you store in your work orders.

The only built-in properties of a work order are its name, description and ID number / code. All other properties are created as if they are normal ARDI asset properties.

As such, most first-time users will want to create a set of [[common properties]] before they enable the maintenance system.

===Choose Work Order Style===

{{:maintenance:config.png?400|}}

There are two major types of work order system - where there is usually one work order per asset to be maintained, or one work order contains many tasks, each of which may have one or more assets associated with them.

As an example, imagine it's a day for 20 routine calibrations of equipment on site. You could either....

A) Create 20 individual work orders, each one for a different asset, or
B) Create 1 work order with 20 tasks, each one for a different asset.

If you like option A, choose **One Work Order -> One Asset** from the list at the top of the addin settings page. If you prefer B, choose **One Work Order -> Multiple Tasks -> Multiple Assets**.

===Choose Data===

Next, you choose what data you want to appear in work orders, tasks and mark any special properties.

You do this by checking the check-boxes next to properties in the property names that appear in the settings list.

==Work Order Data==

Data that is attached to the Work Order will be editable when creating new work orders and will appear in the [[work orders page]]. However, it will **not** be copied onto assets, unless it's also marked as //Task Data// as well.

==Task Data==

Tasks can have additional details.

Unlike Work Order data,  data attached to the task will be copied onto assets that are part of that task. Note that if you are running in **One Work Order -> One Asset** mode, the task //is// the work order, and this checkbox simply indicates if you would like copy information from the work order directly onto assets that are used in the work order.

==Special Data==

There are also special options for specific properties in the drop-list on the right of the each property name.

{{:maintenance:settingmenudroplist.png?400|}}

These have the following effects...

^Name^Effect^
|Normal|No effect|
|Date|The job start date|
|Status|The job status|
|Bottom-Up|This follows the [[feed-up_properties|feed-up]] rules (Status automatically includes this)|
|Service|On Boolean/Digital properties, the Out-Of-Service property. On Text properties, the comment that describes //why// it is out of service.|

You should make sure that one property is set to each of the **Date, Status, Service (Digital)** and **Service (Comment)** special values.  

===Create a 'Maintainable' type===

Create a new type (somewhere in the Type hierarchy) to allow you to mark assets as maintainable. Usually, not every asset on-site is part of a maintenance system or schedule, so this gives you the freedom to only define //some// assets as a part of the maintenance system.

It also allows you set up the properties you want copied from the order/task to the asset itself.

For example, by adding **Job Status** to an asset, you'll see the status of the job on the asset itself. By adding **Job Start Date** to an asset, you'll see the date shown on the asset as well.

Your type does //not// have to be called 'Maintained' - that's just an example. However, you need to choose it from the list at the very bottom of the list in the settings for the Maintenance addon (pictured below).

{{:maintenance:maintainable.png?400|}}

===Create a 'Calibrated' Type===

Calibrations require **Range** types to be present - it specifically looks for types called **Input Range**, **Output Range** and **Display Range**, but will continue to work even if only **Input Range** is specified.

We normally suggest creating a 'Calibrated' type that contains these ranges, to mark assets that require occasional calibrations. This type does **not** need to be chosen in the settings for the addon - the calibration option will appear for assets that have Range properties associated with them.