4 Synchronization of Maintenance Information

4.1 Synchronizing Data Function

This section describes how the Synchronizing Data Function works in the MADE Import Capability. The MADE Import feature has a Synchronizing Data Function which reads the data to be imported and checks it against the data already in the model. The Synchronizing Data Function will identify the new data which is being imported into the model, and provides details on what data is being overwritten in the MADE Project. The user can then choose which model items can be altered with the new information and continue the import as above.

Below is an example of the Synchronizing Data Function given some changes to the XLSX file for Maintenance Information.

4.2 Prerequisites & Dependencies

Prerequisites

• Existing Project — A project is required with model items to assign Maintenance Information to perform the synchronization.
• Configuration Creation — A configuration is required to be defined. This is required for MADE to read in the XLSX file and the data within it. Refer to the Import Configuration User Guide.

Dependencies

• System Model — Data that is imported from the MADE Import capability is stored on Model Items.

4.3 Synchronizing Data Function - Example

In this Synchronizing Data Function Example, the following changes (highlighted in red in the source spreadsheet) have been made to the XLSX file used in the Maintenance Import section.

Figure 12 ("Adjustment to data input") shows the "Maintenance Actions" worksheet with columns: Parent Item Name, Parent Item Number, Name, Maintenance Action ID, Active?, Description, Maintenance Type, Location, Inspection Interval (hrs), Maintenance Interval (hrs). One data row: Coupling | A101 | CBM Action | 001 | Yes | Action description | Condition-based - Repair | Remote depot (changed) | 500 (changed, highlighted red) | 35087.

The same process is followed as discussed in Step 6 of the Step-by-Step Process Flow (see maintenance-import-guide-background-and-process-flow.md), with the exception that in the Synchronize Model window, the "Current Value" column is populated (since data already exists on the model items and is being compared/overwritten, rather than imported fresh).

Figure 13 ("Import Wizard – Synchronize Model with adjusted data") shows the Synchronize Model page with (MA2) Maintenance Action 2 selected under (SS1) Driveline. Details panel comparing Current Value vs New Value:

Property	Current Value	New Value
Name	Maintenance...	Maintenance...
Maintenance ... (ID)	MA2	MA2
Active?	No	No
Description	asdfghjkl;'457	asdfghjkl;'457
Inspection Int...	2.00	2.00
Location	Field	Local Depot
Maintenance ... (Interval)	200.00	200.00
Maintenance ... (Type)	Breakdown - ...	Breakdown - ...

In the Synchronize Model window, the new changes to the Maintenance Information appear in bold when an item is selected. For example, the changes being made for CBM Action are to the Location (Field → Remote/Local Depot) and Inspection Interval (100 → 500), which can be seen in the comparison above.

If the user accepts the changes to be made to the Maintenance Actions, then checking the items which require changes and selecting "Finish", the changes to the item will be committed to the model.

Figure 14 ("Verification of adjusted import data") shows the "Subsystem 1" Maintenance Actions editor after the synchronization was committed: Maintenance Actions list (MA2 - Maintenance Action 2, MA1 - Maintenance Action 1); Maintenance Action Details for MA2: Action ID = MA2, Action Name = Maintenance Action 2, Description = asdfghjkl;'457, Maintenance Type = Breakdown - Replace, Continuous Monitoring unchecked, Maintenance interval = 200.000 hours, Inspection interval = N/A hours, Effectiveness Factor = 0.00E+00, Location of Maintenance = Local Depot, CCMR unchecked; Tasks and Personnel grid: MT2 "Maintenance Task 2" (Downtime unchecked, Duration 2.00 hrs, Rate $975.00/person/hr, #Personnel 2, Total $3,900.00); Summary: "4 of 4 Failures linked", "2.00 hrs / $5,850.00" — confirming the Location and interval changes from the synchronized XLSX were successfully committed to the model item.