Exporting & Importing Tactics

Developing, Editing, and View all your Tactics strategies can be completed through various Exports and Imports. All these exports and imports have validations to help notify users about issues with their attempted import.

There are 4 main types of Exports within the Tactics Module. The sections below go into each type of export and any details specific to these exports. 

Component Hierarchy Export

The Component Hierarchy Export is a simple export of the component details and their structure. This export is great for editing the component details (Description, Make, Model, Custom Fields) for large assets.

   

   

The Export has the following fields:

 

• Token
• Parent Description
• Description
• Make
• Model
• Comments
• Component Custom Fields (Optional extra fields on your components configured in the Custom Field Config)

Tactics Export

The Tactics Export contains all tactics data and supports the creation, editing, and deletion of tactics data except Component Details, for the specified location and locations below.

 

The Tactics Export has the following sheets:

 

• Components
• Component Tactics
• Replacement
• Activities
• Criticality Types (one tab for each)
• Custom Costs
• Labour
• Materials
• Symbols 
• Data Capture

Below is an example screenshot of the Activities tab. All other tabs follow a similar structure within the export.

Single Sheet Export

The Single Sheet Export contains the ability to view most tactics data in a single row. This is available to be exported and imported at a single location. The export is available for multiple locations but isn't importable.

 

The import enables you to modify and create the following data:

 

• Components
• Functions and Function Failures
• Failure Modes
• Activities
• Activity Labours
• Activity Materials
• Activity Custom Costs

Note

This Export does not show activities that aren't allocated to Component Replacements or Failure Modes.

Importing all of the possible data types outlined above is possible on a single row. To help identify different data types, the Single Sheet Export has colour-coded columns. In the screenshot below, Function Failure, Failure Mode, and Activity Data can easily be identified. 

 

The export is designed to work from left -> right and with the following work process:

1. Define the component and its details (if necessary, its parent component).
2. Define a Function and Function Failure of the Component. If no Function andFunction Failure is defined, a blank one will be created. Function and Function Failures with no Failure Modes will be automatically deleted.
3. Define a Failure mode and its details. Failure Modes without a What value are automatically deleted as What is treated as a mandatory field.
4. Create/allocate an activity and its details to that Failure Mode.
5. Allocate Labour to the Activity.
6. Allocate Material to the Activity.
7. Allocate Custom Costs to the Activity.

If you want to create a similar row, use Excel's function to duplicate the row above. For this import, Tactics data should be grouped next to similar data. This is required when allocating more than 5 activity resources of the same type to the same activity, it is heavily recommended for general use as well.

The diagram below is a breakdown of the Single Sheet Tactics Import and how data should flow and be grouped from left -> right.

High-Level Exports

High-Level Exports are available on each data type's tab in the Tactics module. These Exports only export the necessary fields of that data type e.g. Failure Mode or Activities. 

   

   

These exports are from the specified location and all locations below and are available on locations- even those that don't have tactics - particularly helpful for making changes at the fleet/group level or higher.

 

Using this export, viewing and changing a fleet of assets or multiple different asset's activities is easier.

Common issues to consider:

• If there isn't a value in the token field then the data will be treated as a creation.
• Only dropdown values can be selected e.g. Constraints, Strategy Types, Custom Fields.
• Relationships will need to be unique:
  • Allocations, where the values are provided, need to be unique unless a token is provided: 
    • Two 'Motors' in a Site's Material Configuration
    • Two Parent folders/components called 'Engine'
• If there is an 'Accept Changes' column, only Y-marked rows will be affected.
• If columns or values in the top 10 rows are edited, the import's durability is forfeited.
• No formulas in imported cells.