The Pre-Start module in FieldInsight helps you manage routine checklists for your equipment and internal assets, such as plant and vehicles.

With Pre-Start, you can:

To enable and use the Pre-Start feature, follow the steps below to configure your account and assets correctly.

Make sure you are logged in to FieldInsight using a Scheduler account.

Under Settings > Asset Manager > Assets > System Fields > Scheduler section, set the following fields to Visible:

Displays the following fields on the Asset Information page and the Test (Execution) page:

It also displays the following fields on the Test (Configure) page:

If you mark this field as Required, users will not be able to save:

Go to the Settings > Asset Manager > Assets > System Fields > Mobile section and set the following field to Visible:

This displays the following fields on the Asset Information page and the Test (Execution) page:

If this field is marked as Required, users will not be able to save an internal asset or test without entering:

Once the system fields are configured, the next step is to make sure your internal assets are set up correctly.

Filter the assets by selecting:

Then click Search.

Verify that all assets that should be internal appear in the list.

To review an asset:

Make sure this is ticked to mark the asset as internal.

Make sure the asset has the correct Asset Type assigned.

The following fields can be left blank if Runtime is not marked as required in System Fields:

These fields will also sync with the most recent Pre-Start record logged.

You can click the Edit button beside the Runtime Unit of Measure field to manage your UoMs, including:

Once your asset details are verified, the next step is to make sure your Service Tests and Pre-Start Tests are configured correctly.

Make sure you have already created your Service Tests.

Open any service test and verify the following fields:

Make sure the test type is Service Test.

Check that the service test is linked to the correct asset type or asset types.

Enter or verify the service interval that determines when this test becomes the next service test due.

Select or verify the correct Unit of Measure for the service test.

Make sure this is unticked.

You can click + Add Test to create additional Service Tests if needed.

From the Test Templates page, make sure you have already created your Pre-Start Tests.

Open any pre-start test and verify the following fields:

Make sure the test type is Pre-Start Test.

Check that the pre-start test is linked to the correct asset type or asset types.

Make sure this is ticked.

You can click + Add Test to create additional Pre-Start Tests if needed.

To make it easier to monitor runtime and service schedules, customise the Assets List page.

Click the column settings icon in the top-right corner of the Assets List page.

From there, you can:

Make sure the following columns are visible:

The Difference value is calculated by subtracting the Asset Runtime from the Next Service Test Service Due At value.

Example:

This value is used to help define the asset’s Runtime Status.

Click on any Runtime value from the Assets List page.

A pop-up window will appear, allowing you to customise your Runtime Statuses.

Once configured, return to the Internal Assets List page.

You should now be able to see the Runtime Status for each internal asset.

To successfully set up the Pre-Start feature, make sure you: